From 7ae217e764c5bd1fcdc99f4062e2bd3d851e9cf4 Mon Sep 17 00:00:00 2001 From: Megan Rossetti Date: Mon, 14 Jul 2014 15:35:14 -0400 Subject: [PATCH] clean-up of module001-ch004-openstack-architecture Replaced Folsom with Icehouse Made some minor sentance structure changes Updated two sections per comments Closes-Bug #1282197 Change-Id: Ic5c5ca7a366657a4c0ec93fc31f94b7deaebabfd --- .../common/section_openstack-architecture.xml | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-) diff --git a/doc/training-guides/common/section_openstack-architecture.xml b/doc/training-guides/common/section_openstack-architecture.xml index 10e01f4b..1af629e0 100644 --- a/doc/training-guides/common/section_openstack-architecture.xml +++ b/doc/training-guides/common/section_openstack-architecture.xml @@ -152,13 +152,11 @@ as previously described: nova-volume manages the creation, attaching and - detaching of z volumes to compute instances (similar - functionality to Amazon’s Elastic Block Storage). It can + detaching of z volumes to compute instances, which has a similar + functionality to Amazon’s Elastic Block Storage. It can use volumes from a variety of providers such as iSCSI or - Rados Block Device in Ceph. A new OpenStack project, - Cinder, will eventually replace nova-volume functionality. - In the Folsom release, nova-volume and the Block Storage - service will have similar functionality. + Rados Block Device in Ceph. The OpenStack Block Storage project, + Cinder, has replaced the nova-volume functionality. The nova-network worker daemon is very similar to @@ -167,8 +165,7 @@ as previously described: network (such as setting up bridging interfaces or changing iptables rules). This functionality is being migrated to Neutron, a separate OpenStack project. In the - Folsom release, much of the functionality will be - duplicated between nova-network and Neutron. + Icehouse release, the functionality is duplicated between nova-network and Neutron. The nova-schedule process is conceptually the simplest @@ -181,8 +178,7 @@ as previously described: The queue provides a central hub for passing messages between daemons. This is usually implemented with RabbitMQ today, but could be any AMQP message queue (such as Apache - Qpid). New to the Folsom release is support for Zero - MQ. + Qpid and ZeroMQ). The SQL database stores most of the build-time and