Differences between revisions 3 and 4
Revision 3 as of 2012-02-13 11:08:49
Size: 1900
Editor: ?dachary
Comment: OpenStack packages
Revision 4 as of 2012-04-23 10:52:32
Size: 1948
Editor: ?dachary
Comment: Add puppet howto
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
The OpenStack Debian packages are maintained by [[https://alioth.debian.org/projects/openstack/|a team]] and can be installed and ready to use by following the instructions from the [[OpenStackHowto|HOWTO]]. The OpenStack Debian packages are maintained by [[https://alioth.debian.org/projects/openstack/|a team]] and can be installed and ready to use by following the instructions from the [[OpenStackHowto|HOWTO]] and [[OpenStackPuppetHowto|Puppet based HOWTO]].

I have transferred this from Cloud as it had started to look more like an OpenStack description than a general Cloud page -- OlivierBerger

The OpenStack Debian packages are maintained by a team and can be installed and ready to use by following the instructions from the HOWTO and Puppet based HOWTO.

OpenStack is a much less mature project [than XCP], but that has really a lot of contributors. Its goal is to be the Apache of the cloud. In other words, it is supposed to become the open source standard that everybody will use. It has a lot of interesting features, but it's a lot harder to setup and understand than XCP. Don't expect to be ready within an hour, you'll need few days, if not weeks, to just understand the basic concepts behind it, and how to set it up. But if you are a service provider, and wish to setup a cloud computing service, then it will be your choice. It has a partial implementation of EC2 and S3 APIs (I wrote partial, but really, everything that you will need is there).

Then, what's also nice, is that if you wish to run Openstack with Xen, you can use OpenStack with XCP. OpenStack will talk directly to XenAPI (which is the API of XCP), instead of using libvirt. It has been designed this way, and not use libvirt, because XenAPI has many concepts that libvirt doesn't, and using libvirt would have been too much limiting features. If you wish to know how to do such a setup, there's a README in the source package of nova (otherwise known as openstack compute). I am not sure if we packaged it yet with the binaries of nova-compute-xen though.

As for an ?EC2 client, you can use euca2ools, also available in SID. These would be what to use if you wish to control OpenStack using the EC2 API (but of course, you can use "nova" on the shell, which uses the native OpenStack compute API).