Open Stack

Hi,

Iam having essex setup [where we dont have Quantum Network] and now if we
want to have Folsom setup and if we dont want to use L3-Agent and Quantum
router for DNAT of Floating-IPs.

How can we achieve this with Folsom.?

As well i want to understand the real time deployment of Teanant VMs for
Public Access using Public -IPs, I hope it can be achieved in Folsom setup
as well. Can any one give me inputs on this.

Just curious to understand the quantum router use case apart from
NAT,iptable rules any other advantages we have in real time deployments.

please share your understanding and experience.

Thanks in advance.

regards,
balaji

On Mon, Nov 12, 2012 at 6:17 AM, gong yong sheng <gongysh at linux.vnet.ibm.com
> wrote:

>  On 11/10/2012 10:06 PM, balaji patnala wrote:
>
>  Hi Yong,
>
> I downloaded the Quantum Architecture in Folsom Powerpoint prepared by you
> and found that in slide-10:
>
> lL3-agent
> lTo implement floating Ips and other L3 features, such as NAT
> *lOne per network*
>
>
> Can you elaborate on the comment 'one per network' for L3-Agent.
>
>
> # If use_namespaces is set as False then the agent can only configure one
> router.
> # This is done by setting the specific router_id.
> # router_id =
>
> # Each L3 agent can be associated with at most one external network.  This
> # value should be set to the UUID of that external network.  If empty,
> # the agent will enforce that only a single external networks exists and
> # use that external network id
> # gateway_external_network_id =
>
> two options:
> 1. use namespace = False and set router_id to specific one can support
> multi l3-agent,
> or
> 2. create multiples external networks, and use gateway_external_network_id
> = to run multil3-agent
> This way, we must set router's gateway port:
> we can create router with external_gateway_info:
> such as quantum router-create router1 --external_gateway_info
> network_id=<id>
> or quantum router-create router2
> quantum router-gateway-set
>
>
>  As i understood that the L3-Agent will be only one for complete setup.
> If we have more than one Network Node then we must install dhcp-agent and
> L3-Agent in each of these Network Nodes.
>
> So, the comment of 'one per network' is like we can have one
> router/gateway per tenant network.
>
> Can you give us your comments on this.
>
>
> you can reach at this target by creating a router or external network per
> tenant.
>
>  bye,
> balaji
>
>
>
> On Wed, Oct 31, 2012 at 10:38 AM, balaji patnala <patnala003 at gmail.com>wrote:
>
>> Hi Yong,
>>
>> Thanks for information.
>> I think you mean to say that these Quantum Network Node is not per Tenant
>> basis and it can serve all the Tenants of DC setup.
>>
>> Just want to understand what will be the advantages we are thinking of by
>> doing so.
>>
>> Regards,
>> Balaji
>> On Tue, Oct 30, 2012 at 2:26 PM, gong yong sheng <
>> gongysh at linux.vnet.ibm.com> wrote:
>>
>>>  Hi,
>>> In fact, we can split Quantum network Node into two categories:
>>> one is for dhcp, which install ovs agent and dhcp agent. We can have one
>>> such kind of node
>>> one is for l3 agent, we can deal with one external network on one l3
>>> agent. We can have many nodes of this kind.
>>>
>>> Regards,
>>>
>>> Yong Sheng Gong
>>>
>>> On 10/30/2012 02:27 PM, balaji patnala wrote:
>>>
>>> Hi Salvatore,
>>>
>>> Just want to understand more on Network Node in the below given app_demo
>>> page.
>>>
>>> As i see in the setup, it looks like there will be one Quantum Network
>>> Node for one Data centre setup. Please correct me if my assumptions are
>>> wrong.
>>>
>>> This Quantum Network Node will have all the virtual routers, gateway
>>> which can be created with quantum-l3-agent plugin.
>>>
>>> Also my assumption is that this quantum Network Node will serve all the
>>> Tenant virtual gateways and routers created using quantum.
>>>
>>> Please give us some more information on this to understand the setup.
>>>
>>> Also do we have any specific reason for having quantum Network Node
>>> instead of keeping these plugin on the Controller Node similar to earlier
>>> release like Essex.
>>>
>>> Thanks in advance.
>>>
>>> Regards,
>>> Balaji
>>>
>>> On Fri, Oct 26, 2012 at 3:31 PM, Salvatore Orlando <sorlando at nicira.com>wrote:
>>>
>>>> Hi Trinath,
>>>>
>>>> Even if is perfectly reasonable to run the DHCP/L3 agents in the
>>>> controller node, the advice we give in the administration guide is slightly
>>>> different.
>>>> As suggested in [1], the only Quantum component running on the
>>>> controller node should be the API server.
>>>> The DHCP and L3 agents might run in a dedicated "network node". Please
>>>> note you will need also the L2 agent running on that node.
>>>>
>>>> Regards,
>>>> Salvatore
>>>>
>>>> [1]
>>>> http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html
>>>>
>>>>  On 26 October 2012 10:50, Trinath Somanchi <trinath.somanchi at gmail.com
>>>> > wrote:
>>>>
>>>>>  Hi Stackers-
>>>>>
>>>>> I have found many installation and configuration manuals for Openstack
>>>>> Folsom which state the installation and configuration of Quantum-DHCP-Agent
>>>>> in the Controller machine.
>>>>>
>>>>> But I have doubt here,
>>>>>
>>>>> Can't we have the Quantum-DHCP/L3-Agent to be running in the Compute
>>>>> NODE rather than in the controller.
>>>>>
>>>>> How does the Installation and configuration change with this type of
>>>>> Installation?
>>>>>
>>>>> Please guide me on How to achieve the same.
>>>>>
>>>>> Thanking you
>>>>>
>>>>> --
>>>>> Regards,
>>>>> ----------------------------------------------
>>>>> Trinath Somanchi,
>>>>> +91 9866 235 130
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list: https://launchpad.net/~openstack
>>>>> Post to     : openstack at lists.launchpad.net
>>>>> Unsubscribe : https://launchpad.net/~openstack
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to     : openstack at lists.launchpad.net
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to     : openstack at lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121205/45abb7f9/attachment.html>