Merge pull request #9 from ryanpetrello/master

More documentation tinkering.
This commit is contained in:
Ryan Petrello 2015-04-03 12:35:35 -04:00
commit a3f3a10fa4
2 changed files with 4 additions and 4 deletions

View File

@ -15,7 +15,7 @@ as a service):
.. image:: _static/neutron-canonical.png
When we add Akanda into the mix, we're able to replace these agents with
a virtualized software router that manages layer 3 routing and other advanced
a virtualized Service VM that manages layer 3 routing and other advanced
networking services, significantly lowering the barrier of entry for operators
(in terms of deployment, monitoring and management):
@ -36,13 +36,13 @@ From an architectural perspective, Akanda is composed of a few subprojects:
* | :ref:`akanda-rug <rug>`
A service for managing the creation, configuration, and health of Akanda
Software Routers in an OpenStack cloud. The :py:mod:`akanda-rug` acts in part as
Serivce VMs in an OpenStack cloud. The :py:mod:`akanda-rug` acts in part as
a replacement for Neutron's various L3-L7 agents by listening for
Neutron AMQP events and coalescing them into software
router API calls (which configure and manage embedded services on the
Service VM). Additionally, :py:mod:`akanda-rug` contains a health monitoring
component which monitors health and guarantees uptime for existing
software routers.
Service VMs.
* | :ref:`akanda-appliance <appliance>`

View File

@ -12,7 +12,7 @@ OpenStack operators for real OpenStack clouds. Originally developed by
`DreamCompute <https://dreamhost.com/compute/cloud>`_, Akanda eliminates the
need for complex SDN controllers, overlays, and multiple plugins by providing
a simple integrated networking stack (routing, firewall, and load balancing via
a :ref:`virtual software router <appliance>`) for connecting and securing
a :ref:`virtual Service VM <appliance>`) for connecting and securing
multi-tenant OpenStack environments.
Narrative Documentation