[OpenStack Beginner’s Guide for Ubuntu 11.04] OpenStack Commands

Nova Manage commands

OpenStack provides commands for administrative tasks such as user/role management,  network management etc. In all the examples we will use username as “novadmin” and project name as “proj”. All the nova-manage commands will need to be run as “root”. Either run them as root or run them under sudo.

Eucalyptus Beginner’s Guide – UEC edition v2.0 – Maverick

V2.0 of Eucalyptus Beginner’s Guide – UEC edition is out. This covers UEC on Ubuntu 10.10 Maverick Meerkat, based on Eucalyptus 2.0. Please download the PDF and post your comments.

Eucalyptus Beginner’s Guide – Updated v1.1

Due to some changes effected in the latest update of UEC packages on Ubuntu 10.04 Lucid Lynx, we have updated the Eucalyptus Beginner’s Guide to reflect those changes. Thus we have Eucalyptus Beginner’s Guide – Version 1.1. We’re also working on the Eucalyptus Beginner’s Guide on Ubuntu 10.10 Maverick Meerkat. Stay tuned to the blog to stay informed. Feedback is welcome.

Click the following link to download the book:

https://cssoss.wordpress.com/wp-content/uploads/2010/11/eucalyptus-beginners-guide-uec-edition1-1.pdf

Eucalyptus Beginner’s Guide – UEC 10.10 & Eucalyptus 2.0-Image Management

We have noticed a few changes in the way Eucalyptus 1.6 (UEC on Ubuntu 10.04 Lucid Lynx) and 2.0 (UEC on Ubuntu 10.10 Maverick Meerkat) launch instances. These changes have an impact on the bundling procedure. This article takes these changes into account and may be helpful for users of UEC on Ubuntu 10.10 and Eucalyptus 2.0

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 “jaunty.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”