Cisco Openstack g.2

This release contains all upstream stable branch patches for OpenStack core components including Nova, Quantum, Cinder, Glance, Keystone, Horizon, and Swift as of 2013.1.3 plus additional patches accepted to the stable branch since 2013.1.3 was released. Client libraries have been updated to newer versions and tested as well. This release also features Puppet automation updates from StackForge.

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

http://docwiki.cisco.com/wiki/OpenStack:Grizzly-Multinode

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

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

deb ftp://ftpeng.cisco.com/openstack/cisco grizzly main
deb-src ftp://ftpeng.cisco.com/openstack/cisco grizzly main

to:

deb ftp://ftpeng.cisco.com/openstack/cisco grizzly/snapshots/g.2 main
deb-src ftp://ftpeng.cisco.com/openstack/cisco grizzly/snapshots/g.2 main

2.) Run "apt-get update" as root or via sudo. You may see a harmless warning of the form "Conflicting distribution: ftp://ftpeng.cisco.com grizzly/snapshots/g.2 Relase (expected grizzly/snapshots but got grizzly)". 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 /etc/puppet/manifests/core.pp on your build node. Change line 26 (https://github.com/CiscoSystems/grizzly-manifests/blob/g.2/manifests/core.pp#L26) to read "grizzly/snapshots/g.2" instead of "grizzly". Similarly, change line 66 (https://github.com/CiscoSystems/grizzly-manifests/blob/g.2/manifests/core.pp#L66) to "grizzly/snapshots/g.2" instead of "grizzly".

Note that you may also choose to run bleeding-edge (and not fully vetted) code by using "grizzly-proposed" in place of "grizzly/snapshots/g.2" 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 "g.2" tag in the repositories listed here:

https://github.com/CiscoSystems/

Limitations:
----------------
We do not support Heat, Ceilometer, or other incubated projects in this release although relevant repositories are available for customers to experiment with on their own.

Customers deploying Swift with Cisco OpenStack Installer should take note that storage nodes need to be brought up before the Swift proxy node. Further information is available in the installation instructions here:

http://docwiki.cisco.com/wiki/OpenStack:Grizzly-Multinode#Deploying_Swift

Similarly, customers deploying Ceph should take note of deployment considerations here:

http://docwiki.cisco.com/wiki/OpenStack:Grizzly-Multinode#Deploying_Ceph

Ceph RBD can be used as a backend for Glance as of this release. This release also supports creating Cinder volumes backended by Ceph in a variety of different configurations with the limitation that MON and OSD roles cannot be deployed to the same node (see above link for more details on deploying Ceph with COI).

This release contains preliminary deployment automation support for the Cisco plugin. There are some known issues for l3 traffic flowing to an external network by a bridge other than br-ex due to a known limitation of upstream Puppet code. We expect this issue to be fully addressed in the next release.

Active/Active HA Deployments
--------------------------------------------
This release features optional support for automated deployments of OpenStack using an active/active HA architecture. The active/active HA architecture uses MySQL Galera, RabbitMQ clustering and mirrored queues, HAProxy and Keepalived, Swift as backend storage for Glance, and provider networks to provide an active/active HA solution and requires a minimum of 13 nodes to deploy. A deployment guide for active/active HA can be found here:

http://docwiki.cisco.com/wiki/OpenStack_Grizzly_Release:_High-Availability_Automated_Deployment_Guide

For those who do not wish to use the automated HA deployment method, a manual method is described in the manual deployment guide here:

http://docwiki.cisco.com/wiki/COE_Grizzly_Release:_High-Availability_Manual_Installation_Guide

Simple Network Model:
---------------------------------
Cisco OpenStack Installer uses Quantum to provide networking services. A number of network models are possible with appropriate modifications to the Puppet manifests supplied here. Cisco has tested a simple network model that can serve as a starting point for COI users. The simple network model uses a single "control" node on which most OpenStack control services are run and multiple compute nodes. Network segmentation is provided by Open vSwitch via GRE tunneling. Two physically or logically (VLAN) separated IP networks with an external router or layer-3 switch that provides connectivity between these two networks are deployed: one to provide connectivity for OpenStack API endpoints, Open vSwitch (OVS) GRE endpoints, and OpenStack/UCS management. The second network is used by OVS as the physical bridge interface and by Quantum as the public network. More information can be found in our installation instructions here:

http://docwiki.cisco.com/wiki/OpenStack:Grizzly-Multinode