adding images
This commit is contained in:
Anne Gentle
parent
8257fcc259
commit
7712287139
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
|
|
@ -31,8 +31,9 @@ In this mode, each project gets its own VLAN, Linux networking bridge, and subne
|
|||
|
||||
In the VLAN network mode, all the VM instances of a project are connected together in a VLAN with the specified private subnet. Each running VM instance is assigned an IP address within the given private subnet.
|
||||
|
||||
.. todo:: Insert Figure 2 from "An OpenStack Network Overview" contributed by Citrix
|
||||
|
||||
.. image:: /images/Novadiagram.png
|
||||
:width: 790
|
||||
|
||||
While network traffic between VM instances belonging to the same VLAN is always open, Nova can enforce isolation of network traffic between different projects by enforcing one VLAN per project.
|
||||
|
||||
In addition, the network administrator can specify a pool of public IP addresses that users may allocate and then assign to VMs, either at boot or dynamically at run-time. This capability is similar to Amazon's 'elastic IPs'. A public IP address may be associated with a running instances, allowing the VM instance to be accessed from the public network. The public IP addresses are accessible from the network host and NATed to the private IP address of the project.
|
||||
|
|
|
|||
|
|
@ -42,6 +42,9 @@ You can also run with a category argument such as user to see a list of all comm
|
|||
|
||||
These sections describe the available categories and arguments for nova-manage.
|
||||
|
||||
Nova User
|
||||
~~~~~~~~~
|
||||
|
||||
``nova-manage user admin <username>``
|
||||
|
||||
Create an admin user with the name <username>.
|
||||
|
|
|
|||
|
|
@ -42,6 +42,9 @@ You can also run with a category argument such as user to see a list of all comm
|
|||
|
||||
These sections describe the available categories and arguments for nova-manage.
|
||||
|
||||
Nova User
|
||||
~~~~~~~~~
|
||||
|
||||
``nova-manage user admin <username>``
|
||||
|
||||
Create an admin user with the name <username>.
|
||||
|
|
|
|||
|
|
@ -118,13 +118,10 @@
|
|||
segment for each project’s instances that can be accessed via a dedicated
|
||||
VPN connection from the Internet.</p>
|
||||
<p>In this mode, each project gets its own VLAN, Linux networking bridge, and subnet. The subnets are specified by the network administrator, and are assigned dynamically to a project when required. A DHCP Server is started for each VLAN to pass out IP addresses to VM instances from the subnet assigned to the project. All instances belonging to one project are bridged into the same VLAN for that project. The Linux networking bridges and VLANs are created by Nova when required, described in more detail in Nova VLAN Network Management Implementation.</p>
|
||||
<div class="admonition-todo admonition " id="index-0">
|
||||
<p class="first admonition-title">Todo</p>
|
||||
<p class="last">Insert Figure 2 from “An OpenStack Network Overview” contributed by Citrix</p>
|
||||
</div>
|
||||
<img alt="../_images/Novadiagram.png" src="../_images/Novadiagram.png" style="width: 790px;" />
|
||||
<p>While network traffic between VM instances belonging to the same VLAN is always open, Nova can enforce isolation of network traffic between different projects by enforcing one VLAN per project.</p>
|
||||
<p>In addition, the network administrator can specify a pool of public IP addresses that users may allocate and then assign to VMs, either at boot or dynamically at run-time. This capability is similar to Amazon’s ‘elastic IPs’. A public IP address may be associated with a running instances, allowing the VM instance to be accessed from the public network. The public IP addresses are accessible from the network host and NATed to the private IP address of the project.</p>
|
||||
<div class="admonition-todo admonition " id="index-1">
|
||||
<div class="admonition-todo admonition " id="index-0">
|
||||
<p class="first admonition-title">Todo</p>
|
||||
<p class="last">Describe how a public IP address could be associated with a project (a VLAN)</p>
|
||||
</div>
|
||||
|
|
@ -174,7 +171,7 @@ Compute nodes have iptables/ebtables entries created per project and
|
|||
instance to protect against IP/MAC address spoofing and ARP poisoning.</p>
|
||||
<p>The network assignment to a project, and IP address assignment to a VM instance, are triggered when a user starts to run a VM instance. When running a VM instance, a user needs to specify a project for the instances, and the security groups (described in Security Groups) when the instance wants to join. If this is the first instance to be created for the project, then Nova (the cloud controller) needs to find a network controller to be the network host for the project; it then sets up a private network by finding an unused VLAN id, an unused subnet, and then the controller assigns them to the project, it also assigns a name to the project’s Linux bridge, and allocating a private IP within the project’s subnet for the new instance.</p>
|
||||
<p>If the instance the user wants to start is not the project’s first, a subnet and a VLAN must have already been assigned to the project; therefore the system needs only to find an available IP address within the subnet and assign it to the new starting instance. If there is no private IP available within the subnet, an exception will be raised to the cloud controller, and the VM creation cannot proceed.</p>
|
||||
<div class="admonition-todo admonition " id="index-2">
|
||||
<div class="admonition-todo admonition " id="index-1">
|
||||
<p class="first admonition-title">Todo</p>
|
||||
<p class="last">insert the name of the Linux bridge, is it always named bridge?</p>
|
||||
</div>
|
||||
|
|
@ -254,7 +251,7 @@ instance is started on that host</li>
|
|||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<div class="admonition-todo admonition " id="index-3">
|
||||
<div class="admonition-todo admonition " id="index-2">
|
||||
<p class="first admonition-title">Todo</p>
|
||||
<p class="last">need specific Nova configuration added</p>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -67,6 +67,7 @@
|
|||
<ul>
|
||||
<li><a class="reference internal" href="#">The nova-manage command</a><ul>
|
||||
<li><a class="reference internal" href="#introduction">Introduction</a></li>
|
||||
<li><a class="reference internal" href="#nova-user">Nova User</a></li>
|
||||
<li><a class="reference internal" href="#nova-project">Nova Project</a></li>
|
||||
<li><a class="reference internal" href="#nova-role">Nova Role</a></li>
|
||||
<li><a class="reference internal" href="#nova-shell">Nova Shell</a></li>
|
||||
|
|
@ -135,6 +136,9 @@ vpn management, and much more.</p>
|
|||
<p>You can also run with a category argument such as user to see a list of all commands in that category:
|
||||
<tt class="docutils literal"><span class="pre">nova-manage</span> <span class="pre">user</span></tt></p>
|
||||
<p>These sections describe the available categories and arguments for nova-manage.</p>
|
||||
</div>
|
||||
<div class="section" id="nova-user">
|
||||
<h2>Nova User<a class="headerlink" href="#nova-user" title="Permalink to this headline">¶</a></h2>
|
||||
<p><tt class="docutils literal"><span class="pre">nova-manage</span> <span class="pre">user</span> <span class="pre">admin</span> <span class="pre"><username></span></tt></p>
|
||||
<blockquote>
|
||||
Create an admin user with the name <username>.</blockquote>
|
||||
|
|
|
|||
|
|
@ -176,6 +176,15 @@ other ways to interact with the community.</p>
|
|||
<ul class="todo_list simple">
|
||||
</ul>
|
||||
<ul class="todo_list">
|
||||
<li class="todo_p5"><p class="todo_link first"><a class="reference external" href="adminguide/network.vlan.html#index-2"><em>adminguide/network.vlan.rst, line 180</em></a></p>
|
||||
<p class="details">need specific Nova configuration added</p>
|
||||
</li>
|
||||
<li class="todo_p5"><p class="todo_link first"><a class="reference external" href="adminguide/network.vlan.html#index-1"><em>adminguide/network.vlan.rst, line 98</em></a></p>
|
||||
<p class="details">insert the name of the Linux bridge, is it always named bridge?</p>
|
||||
</li>
|
||||
<li class="todo_p5"><p class="todo_link first"><a class="reference external" href="adminguide/network.vlan.html#index-0"><em>adminguide/network.vlan.rst, line 41</em></a></p>
|
||||
<p class="details">Describe how a public IP address could be associated with a project (a VLAN)</p>
|
||||
</li>
|
||||
<li class="todo_p5"><p class="todo_link first"><a class="reference external" href="object.model.html#index-0"><em>object.model.rst, line 4</em></a></p>
|
||||
<p class="details">Add brief description for core models</p>
|
||||
</li>
|
||||
|
|
@ -209,18 +218,6 @@ other ways to interact with the community.</p>
|
|||
<li class="todo_p5"><p class="todo_link first"><a class="reference external" href="cloud101.html#index-0"><em>cloud101.rst, line 75</em></a></p>
|
||||
<p class="details">Use definitions from <a class="reference external" href="http://csrc.nist.gov/groups/SNS/cloud-computing/">http://csrc.nist.gov/groups/SNS/cloud-computing/</a> and attribute NIST</p>
|
||||
</li>
|
||||
<li class="todo_p5"><p class="todo_link first"><a class="reference external" href="adminguide/network.vlan.html#index-3"><em>adminguide/network.vlan.rst, line 179</em></a></p>
|
||||
<p class="details">need specific Nova configuration added</p>
|
||||
</li>
|
||||
<li class="todo_p5"><p class="todo_link first"><a class="reference external" href="adminguide/network.vlan.html#index-2"><em>adminguide/network.vlan.rst, line 97</em></a></p>
|
||||
<p class="details">insert the name of the Linux bridge, is it always named bridge?</p>
|
||||
</li>
|
||||
<li class="todo_p5"><p class="todo_link first"><a class="reference external" href="adminguide/network.vlan.html#index-1"><em>adminguide/network.vlan.rst, line 40</em></a></p>
|
||||
<p class="details">Describe how a public IP address could be associated with a project (a VLAN)</p>
|
||||
</li>
|
||||
<li class="todo_p5"><p class="todo_link first"><a class="reference external" href="adminguide/network.vlan.html#index-0"><em>adminguide/network.vlan.rst, line 34</em></a></p>
|
||||
<p class="details">Insert Figure 2 from “An OpenStack Network Overview” contributed by Citrix</p>
|
||||
</li>
|
||||
<li class="todo_p5"><p class="todo_link first"><a class="reference external" href="adminguide/network.flat.html#index-0"><em>adminguide/network.flat.rst, line 60</em></a></p>
|
||||
<p class="details">add flat network mode configuration examples</p>
|
||||
</li>
|
||||
|
|
|
|||
|
|
@ -60,6 +60,7 @@
|
|||
<li><a class="reference internal" href="#synopsis">SYNOPSIS</a></li>
|
||||
<li><a class="reference internal" href="#description">DESCRIPTION</a></li>
|
||||
<li><a class="reference internal" href="#options">OPTIONS</a><ul>
|
||||
<li><a class="reference internal" href="#nova-user">Nova User</a></li>
|
||||
<li><a class="reference internal" href="#nova-project">Nova Project</a></li>
|
||||
<li><a class="reference internal" href="#nova-role">Nova Role</a></li>
|
||||
<li><a class="reference internal" href="#nova-shell">Nova Shell</a></li>
|
||||
|
|
@ -145,6 +146,8 @@ nova-manage <category> <action> [<args>]</blockquote>
|
|||
<p>You can also run with a category argument such as user to see a list of all commands in that category:
|
||||
<tt class="docutils literal"><span class="pre">nova-manage</span> <span class="pre">user</span></tt></p>
|
||||
<p>These sections describe the available categories and arguments for nova-manage.</p>
|
||||
<div class="section" id="nova-user">
|
||||
<h4>Nova User<a class="headerlink" href="#nova-user" title="Permalink to this headline">¶</a></h4>
|
||||
<p><tt class="docutils literal"><span class="pre">nova-manage</span> <span class="pre">user</span> <span class="pre">admin</span> <span class="pre"><username></span></tt></p>
|
||||
<blockquote>
|
||||
Create an admin user with the name <username>.</blockquote>
|
||||
|
|
@ -163,6 +166,7 @@ Outputs a list of all the user names to the screen.</blockquote>
|
|||
<p><tt class="docutils literal"><span class="pre">nova-manage</span> <span class="pre">user</span> <span class="pre">modify</span> <span class="pre"><accesskey></span> <span class="pre"><secretkey></span> <span class="pre"><admin?T/F></span></tt></p>
|
||||
<blockquote>
|
||||
Updates the indicated user keys, indicating with T or F if the user is an admin user. Leave any argument blank if you do not want to update it.</blockquote>
|
||||
</div>
|
||||
<div class="section" id="nova-project">
|
||||
<h4>Nova Project<a class="headerlink" href="#nova-project" title="Permalink to this headline">¶</a></h4>
|
||||
<p><tt class="docutils literal"><span class="pre">nova-manage</span> <span class="pre">project</span> <span class="pre">add</span> <span class="pre"><projectname></span></tt></p>
|
||||
|
|
|
|||
|
|
@ -2,5 +2,8 @@
|
|||
# Project: nova
|
||||
# Version: 2010.1
|
||||
# The remainder of this file is compressed using zlib.
|
||||
xÚ•’?oÂ0Å÷|
|
||||
Ke¬C³²U°t BEê™ønÛ²<C39B>úéë¿H)†Ò%rîÞ{wþ%ÔȨ{ÂI ª¦Š<C2A6> <EFBFBD>6tÑ‘ tWˆÂ¨`?×AªËƒé»‡ø†£Gã6Š Ñ:44"œ¢•ïê¢Î8…ãt@ª†dôâÎEÓ‰<C393>J&!»Ì¹<3´<Ë1F»ÉF‰h z—\½ ™¹ò„S#Ž^ :t7W«mŸS##)Á<1B>&òb ÄËÐZxaDTh ª9LƒB-ßÁƉÉ`Ù‹»Fºó³=7¬!† îA»’PìÛWŠ ãD1ÐÓ$B{ÆÛ<C386>Q˜'AJ|µû¢<15>^XhnTD÷Û±‰;á |sÏÂó™2åž|‚å¼èاdvõDηð á"ríå` d\b9Öæ$mr&$)oÆHñeÿkeàßptŸÑ±Í8½"kIÇè•y7\^U†×ý ªì%ï$ô‡9‡¦º¼ä-&Wä?Œu¢©
|
||||
xÚť’1oĂ …w˙
|
||||
¤f,N˝f«’ĄCި‘şZ.
°›ô× DrC˘´‹…ďŢ»w|¶=p
|
||||
uGi@×Ló42–-Z˛<5A>á
|
||||
14ěç&HMy°]űßp4âhÜFŃ#Z‡†AD0´»¦h@pÁŕ8
HŐ0˝řsA[Ů3Ĺd—9w<39>g†–g9Ćhă6ŮhůÔ˘w%LŃI–ÉU'ś1z-YßBÜ \îŤ{NŤB¤¤RPP6ňb ÄËĐZŚÂ<C59A>¨0@4=L…Z ßÁĆ‹IoŮ‹űFşół;<3B>°śËĄAű’Ôü{¬;.<2E>ć`¦“ë¸hzÎ`žiâ«ŰtŇAóQµ–ío˙Ĺ&ţ„<C5A3>đÍ?‹‘ĎŔµ-÷ä çEŔ>%łŻ'rc ĎŽ>ŇrFlÖ6
|
||||
˛.*;Ő[(•ürż±±W$Yv ýWó(˙Í…‹u ľ¶'ĺPü5=Ç«Ę𺪺ÜöNBUvÇ›hî »ĘäzŢ6A˘©
|
||||
File diff suppressed because one or more lines are too long
|
|
@ -162,7 +162,10 @@ Nova Floating IPs
|
|||
``nova-manage floating create <host> <ip_range>``
|
||||
|
||||
Creates floating IP addresses for the named host by the given range.
|
||||
floating delete <ip_range> Deletes floating IP addresses in the range given.
|
||||
|
||||
``nova-manage floating delete <ip_range>``
|
||||
|
||||
Deletes floating IP addresses in the range given.
|
||||
|
||||
``nova-manage floating list``
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue