ab93e636b8
Brief Summary:
Added Modules and Lab Sections of Aptira's Existing
OpenStack Training Docs. Please do refer Full Summary
for more details.
For those who want to review this and save some time on
building it, I have hosted the content on
http://office.aptira.in
Please talk to Sean Robetrs if you are concerened about
repetition of Doc Content or similar issues like short URLs
etc., this is supposed to be a rough patch and not final.
Full Summary:
Added the following modules.
1. Module001 - Introduction To OpenStack.
- Brief Overview of OpenStack.
- Basic Concepts
- Detailed Description of Core
Projects (Grizzly) under OpenStack.
- All But Networking and Swift.
2. Module002 - OpenStack Networking In detail.
3. Module003 - OpenStack Object Storage In detail.
4. Lab001 - OpenStack Control Node and Compute Node.
5. Lab002 - OpenStack Network Node.
Full Summary added due to the size of the commit. I Apologize
for the size of this commit and will try not to commit huge
content like in this patch. The reason for the size of this
commit is to meet OpenStack Training Sprint day.
bp/training-manuals
Change-Id: Ie3c44527992868b4d9571b66cc1c048e558ec669
72 lines
3.6 KiB
XML
72 lines
3.6 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<chapter xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink"
|
|
version="5.0"
|
|
xml:id="module002-ch004-floating-ips">
|
|
<title>Floating IP Addresses And Security Rules</title>
|
|
<para>OpenStack Networking has the concept of Fixed IPs and
|
|
Floating IPs. Fixed IPs are assigned to an instance on
|
|
creation and stay the same until the instance is explicitly
|
|
terminated. Floating ips are ip addresses that can be
|
|
dynamically associated with an instance. This address can be
|
|
disassociated and associated with another instance at any
|
|
time.</para>
|
|
<para>Various tasks carried out by Floating IP's as of
|
|
now.</para>
|
|
<itemizedlist>
|
|
<listitem>
|
|
<para>create IP ranges under a certain group, only
|
|
available for admin role.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>allocate an floating IP to a certain tenant,
|
|
only available for admin role.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>deallocate an floating IP from a certain
|
|
tenant</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>associate an floating IP to a given
|
|
instance</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>disassociate an floating IP from a certain
|
|
instance</para>
|
|
</listitem>
|
|
</itemizedlist>
|
|
<para>Just as shown by above figure, we will have
|
|
nova-network-api to support nova client floating
|
|
commands. nova-network-api will invoke quantum cli lib
|
|
to interactive with quantum server via API. The data
|
|
about floating IPs will be store in to quantum DB.
|
|
Quantum Agent, which is running on compute host will
|
|
enforce the floating IP.</para>
|
|
<para><guilabel>Multiple Floating
|
|
IP Pools</guilabel></para>
|
|
<para>The L3 API in OpenStack Networking supports multiple
|
|
floating IP pools. In OpenStack Networking, a floating
|
|
IP pool is represented as an external network and a
|
|
floating IP is allocated from a subnet associated with
|
|
the external network. Since each L3 agent can be
|
|
associated with at most one external network, we need
|
|
to invoke multiple L3 agent to define multiple
|
|
floating IP pools. 'gateway_external_network_id'in L3
|
|
agent configuration file indicates the external
|
|
network that the L3 agent handles. You can run
|
|
multiple L3 agent instances on one host.</para>
|
|
<para>In addition, when you run multiple L3 agents, make
|
|
sure that handle_internal_only_routersis set to
|
|
Trueonly for one L3 agent in an OpenStack Networking
|
|
deployment and set to Falsefor all other L3 agents.
|
|
Since the default value of this parameter is True, you
|
|
need to configure it carefully.</para>
|
|
<para>Before starting L3 agents, you need to create
|
|
routers and external networks, then update the
|
|
configuration files with UUID of external networks and
|
|
start L3 agents.</para>
|
|
<para>For the first agent, invoke it with the following
|
|
l3_agent.ini where handle_internal_only_routers is
|
|
True.</para>
|
|
</chapter> |