Archive for the ‘Eucalyptus’ Category
Table of Contents
- Introduction to UEC and its components
- Installation & Configuration
- Web Interface
- Image Management
- Instance Management
- Storage Management
- Network Management
- Euca Commands
This is a live book and will be updated on an ongoing basis based on your feedback and comments.
In System mode, CC generates and assigns a random MAC address to the VM instance while requesting NC to bring up the instance. NC attaches the VM instance’s virtual NIC to the physical NIC on the node through a bridge. This mode requires that the Nodes are connected to the enterprise network directly. Instances obtain an IP address using DHCP, just as physical machines on the network do.
This mode is very easy to setup as it does not have any additional prerequisites in terms of networking, except for a running DHCP server on enterprise network, and is a good way to get started with Eucalyptus, particularly if you want to set it up on your laptop/desktop to get a basic understanding.
This mode of networking is similar to “Bridged Networking” that hypervisors like VMware, VirtualBox etc. offer or like “tap” networking offered by KVM/Qemu.
Introduction to UEC and its components
The following sections describe how to install and configure a basic UEC setup spanning 3 servers. 2 Servers(Server1 and Server2) will run Lucid 64-bit server version and the third server will run Lucid Desktop 64-bit version(Client1). We have decided on installing the Desktop version on Client1 so that we can use Firefox or other browsers to access the web interface of UEC and also to use RDP/VNC clients during the image creation process.
What we have used as a sample setup is a typical minimal Eucalyptus setup. Client1 above need not be a dedicated machine. If you need to setup Eucalyptus on a single server, you can refer to UEC: CC and NC on a single machine . However, such a setup will not support Managed and Managed-NOVLAN modes of networking. Read the rest of this entry »
Eucalyptus Machine Image(EMI)
A Eucalpyptus Machine Image(EMI) is a combination of a virtual disk image(s), kernel and ramdisk images as well as an xml file containing meta data about the image. These images reside on WS3 and used as templates for creating instances on UEC. Each Linux EMI is a combination of the following:
- An XML file with a name like “karmic.img.manifest.xml” with information about one or more hard disk images, a kernel image and a ram disk image (id – emi-65440E7E)
- An XML file with a name like “vmlinuz-2.6.28-11-server.manifest.xml” with information about the corresponding kernel image(id – eki-39FC1244)
- An XML file with a name like “initrd.img-2.6.28-11-server.manifest.xml” with information about the corresponding ramdisk image(id – eri-71ED1322)
Each of these images has its own ID that can be used while running the instances. More on this in the chapter on “Managing Instances” Read the rest of this entry »