Cisco Openstack h.0

This release contains all upstream stable branch patches for OpenStack core components including Nova, Neutron, Cinder, Glance, Keystone, Horizon, Heat, Ceilometer, and Swift as of 2013.2.1. This release also features Puppet automation updates from StackForge.

Getting the Source and Installing the Release
--------------------------------------------------------------
Information about how to install Cisco OpenStack Edition - Havana can be found here:

http://docwiki.cisco.com/wiki/Openstack:Havana-Openstack-Installer

Note that the instructions provided will install the latest stable maintenance patches for Havana, which may be newer than those in the h.0 release. If you need to specifically install the versions of the packages released in h.0 even though newer maintenance updates are available, you can modify your apt configuration to point to our h.0 snapshot repository. Execute these steps:

1.) Edit /etc/apt/sources.list.d/cisco-openstack-mirror_havana.list and change the following lines:

deb http://openstack-repo.cisco.com/openstack/cisco havana main
deb-src http://openstack-repo.cisco.com/openstack/cisco havana main

to:

deb http://openstack-repo.cisco.com/openstack/cisco havana/snapshots/h.0 main
deb-src http://openstack-repo.cisco.com/openstack/cisco havana/snapshots/h.0 main

2.) Run "apt-get update" as root or via sudo. You may see a harmless warning of the form "Conflicting distribution: http://openstack-repo.cisco.com/openstack/cisco havana/snapshots/h.0 Release (expected havana/snapshots but got havana)". The warning is simply informational and lets you know that you are using a snapshot repository.

3.) To ensure changes are propagated by Puppet, modify /usr/share/puppet/modules/cobbler/templates/preseed.erb on your build node. Change lines 106 and 107 from:

in-target echo "Adding Cisco repo..."; if [ ! -d /etc/apt/sources.list.d ] ; then mkdir -p /target/etc/apt/sources.list.d;fi; echo "deb http://openstack-repo.cisco.com/openstack/cisco havana main" > /target/etc/apt/sources.list.d/cisco-openstack-mirror_havana.list; \
in-target echo "deb-src http://openstack-repo.cisco.com/openstack/cisco_supplemental havana main" > /target/etc/apt/sources.list.d/cisco_supplemental-openstack-mirror_havana.list; \

to:

in-target echo "Adding Cisco repo..."; if [ ! -d /etc/apt/sources.list.d ] ; then mkdir -p /target/etc/apt/sources.list.d;fi; echo "deb http://openstack-repo.cisco.com/openstack/cisco havana/snapshots/h.0 main" > /target/etc/apt/sources.list.d/cisco-openstack-mirror_havana.list; \
in-target echo "deb-src http://openstack-repo.cisco.com/openstack/cisco_supplemental havana/snapshots/h.0 main" > /target/etc/apt/sources.list.d/cisco_supplemental-openstack-mirror_havana.list; \

Then run "puppet apply -v /etc/puppet/manifests/site.pp" to apply the changes to the preseed template.

Note that you may also choose to run bleeding-edge (and not fully vetted) code by using "havana-proposed" in place of "havana/snapshots/h.0" in the above instructions. This is recommended only for developers who expect things to be broken occasionally and is strongly discouraged for production environments.

The source code for this release has been posted to GitHub. Look for the "h.0" tag in the repositories listed here:

https://github.com/CiscoSystems/

Limitations:
----------------
We do not support Trove, Marconi, Savanna, Ironic, or other incubated projects in this release although relevant repositories may be made available for customers to experiment with on their own.

The h.0 release of Cisco OpenStack Installer is the first release based on a new data-driven model. Setup is therefore substantially different than in Grizzly releases, but the resulting installation options are also substantially more flexible. Customers should take care to read installation instructions carefully. Questions may be addressed to openstack-support@cisco.com or https://answers.launchpad.net/openstack-cisco and Cisco engineers will respond on a best effort basis.

Customers deploying Ceph should take note of deployment considerations here:

http://docwiki.cisco.com/wiki/Openstack:Havana-Openstack-Installer#Adding_Ceph_to_nodes

Ceph RBD can be used as a backend for Glance and/or Cinder in this release. The module used to deploy Ceph in Grizzly release of Cisco OpenStack Installer has been replaced with a new module based on ceph-deploy, which dramatically speeds up deployment times and doesn't require multiple catalog runs. However, the ceph-deploy tool uses hostname information (e.g. via DNS) to accomplish it's tasks. Customers should therefore ensure that the IP address that the hostname of the initial mon node resolves to is also be configured in user.common.yaml as the inital mon, and the ceph networks should be on the same subnet as that IP address. Otherwise, cephdeploy may fail to set up the cluster properly.

Compressed Active/Active HA Deployments
--------------------------------------------
This release features experimental support for a new "compressed" HA model in which a full high availability model can be achieved on as little as 3 physical nodes. There are some known issues with this deployment mode, so it is not recommended for novices. Namely, connections to the backend Galera database through HAProxy may fail during the setup process, resulting in some database tables not being created. The issue can generally be corrected by running database migrations manually, but other issues may result from the initial failed connection that require further intervention. We expect to resolve these issues and move the Compressed HA model from experimental to supported status in a future release.

The 13-node "Full HA" model will also be supported in a future release.

All-in-One Deployment Model
-----------------------------------------
The h.0 release includes an "all in one" deployment model that allows users to combine compute and control functions on a single server. The AIO model in h.0 differs from the model provided in g.3 in that it now includes support for Swift Proxy and Storage node roles as well. The all-in-one deployment model can be used in place of a traditional control node to add additional compute/storage capacity to a multi-node cloud by allowing instances to be launched on control nodes.