PUBLIC MARKS from camel with tags network & xen

This guide shows the types of networks Xen can be used on, or to set-up. It uses default configurations of xen, in their most simplest form. Firewalls and security is not discussed here. Feel free to email the author comments at: sburke[at]burkesys.com Xen is used from Debian, and the following setup should be the same for Ubuntu and all other setups of Xen 3.

This has been tested on Xen 2.0.7-1 with Shorewall 3.0.3-1. This Howto presupposes you already have a base Xen install. If not, and you are unfamiliar with Xen, then you probably want to start with the Xen_Debian_Quick_Start. If you do have such a system and you used the default, networking should be running relatively seemlessly. These configurations are only if you want to switch to routed networking (and have a bit more control). There is nothing particularly funky about them, but I haven't had a chance to change it, and that was the first thing that came off of my fingers when I created this page

Openfiler is a powerful, intuitive browser-based network storage software distribution. Openfiler ScreenshotsOpenfiler delivers file-based Network Attached Storage and block-based Storage Area Networking in a single framework. Openfiler is built on the rPath Linux metadistribution and is distributed as a stand-alone Linux distribution. The entire software stack interfaces with third-party software that is all open source. File-based networking protocols supported by Openfiler include: NFS, SMB/CIFS, HTTP/WebDAV and FTP. Network directories supported by Openfiler include NIS, LDAP (with support for SMB/CIFS encrypted passwords), Active Directory (in native and mixed modes) and Hesiod. Authentication protocols include Kerberos 5. Openfiler includes support for volume-based partitioning, iSCSI (target and initiator), scheduled snapshots, resource quota, and a single unified interface for share management which makes allocating shares for various network file-system protocols a breeze.

This guide is the first of a series in which I give you detailed step-by-step instructions on how to build a virtual cluster with Xen. The cluster thus built might not be appropriate for your case, and does reflect the author's preferences and/or needs, but if you are new to clusters or Xen, it will hopefully help you get started with both. The goal is to start it simple and then add more complexity as we progress, so in this first guide I show you how to get do the basics: * A Xen installation, the creation of 5 virtual machines (one to act as the master and four slaves), * Shared storage through NFS, * The network configuration on which to build the virtual cluster. The network structure of this first attempt will be very simple, the master having two network cards, one to the outside world and the other one connected through a switch to the slaves.

Xen is great. But installing more than one network card became a pain when I tried it the first time. There are some documents describing the principle but I was unable to find a real life example somewhere else. So this is a summary about how it works here now. Using a bridge for a Dom is generally a good idea but then all packets traversing the bridge can be intercepted by any Dom that is using the same bridge. Having a single network card in a Xen landscape also means that theoretically each Dom would be able to sniff all packets traversing this single network card including packets to and from other Doms. A solution is to have more than one network card attached to Xen using a single network card for a single dom. The scenario described here has a server with 3 network cards installed. The first card should be used to access Dom0 and some other DomNs while the second and third network card should be used to purely access Dom1 rsp. Dom2. The Dom configuration file just needs to select the appropriate bridge for each dom.

BixData is a system, application, and network monitoring tool which allows you to easily monitor nearly every aspect of your servers. The newly released version 2.6 is the only application that has the ability to control both Xen and VMWare virtual machines. You can control both VM Hosts (the computer that's running the VM software) and VM Guests (the virtual machines running on the hosts).