Thanks Deepak,

Yes it's true..that's the beauty of "Quantum". I had just confused
"tenants" word. Now I understood it.

Also, It has been described in "quantum-admin-guide-trunk.pdf".



>
>
> On Sun, Mar 18, 2012 at 12:51 AM, Deepak Garg 
> <deepakgarg.i...@gmail.com>wrote:
>
>> Thanks, Dan.
>> I didn't know that line in the guide is temporary. I thought thats
>> what quantum cli was meant for.
>>
>> @Hitesh
>> The nova api/cli is limited:  e.g. when you type a  $ nova-manage
>> network    you have very limited options
>> on network management. With Quantum, one will be able to create
>> network topology of their choice and connect
>> the vifs of the VMs to those networks. A simple example would be to
>> have three networks - a public A and 2 private networks B,C -> now you
>> will simply be able to attach and detach vifs to your VMs to have it
>> in any one or more of these networks. Now SG rules may be applied on
>> those VMs and these VMs may later be moved to other hosts later. This
>> will involve configure the switches (physical or virtual) which is
>> what 'quantum' is best at and nova can't do this.
>> Hope it helps !
>>
>> Cheers,
>> Deepak
>>
>>
>> On Sun, Mar 18, 2012 at 12:37 AM, hitesh wadekar
>> <hitesh.wade...@gmail.com> wrote:
>> > Hi Dan,
>> >
>> > Nice explanation !!
>> >
>> > It will be great if you could explain more on this with example
>> (likewise
>> > you have given examples for nova+Quantum Manager)  -- > "such that we
>> can
>> > expose the Quantum API directly to tenants for network creation and port
>> > configuration."
>> >
>> > A short description would be help !!! or redirect me any link for this.
>> >
>> > Thanks,
>> > Hitesh
>> >
>> > On Sun, Mar 18, 2012 at 12:20 AM, Dan Wendlandt <d...@nicira.com> wrote:
>> >>
>> >> Hi Deepak,
>> >>
>> >> For essex, the Nova + Quantum integration relies on Nova to do most of
>> the
>> >> work.  For example, when you invoke "nova-manage network create", the
>> >> Quantum Manager code in Nova reaches out and creates a corresponding
>> network
>> >> via the Quantum API.  Also, when you create a virtual server using
>> "nova
>> >> boot", Quantum Manager automatically creates and attaches ports (and
>> does
>> >> the reverse when the VM is destroyed).  Therefore, there's actually no
>> need
>> >> to drive the Quantum CLI directly to provision things.  Thus, the
>> primary
>> >> use is for troubleshooting (i.e., seeing what is provisioned already)
>> >>
>> >> Moving forward in Folsom, we'll be reworking the Nova + Quantum
>> >> integration and improving Quantum Authn/Authz, such that we can expose
>> the
>> >> Quantum API directly to tenants for network creation and port
>> configuration.
>> >>  At that point, the Quantum CLI will be use used more for provisioning
>> new
>> >> networks and configuring network connectivity.
>> >>
>> >> Dan
>> >>
>> >>
>> >> On Sat, Mar 17, 2012 at 12:58 PM, Deepak Garg <
>> deepakgarg.i...@gmail.com>
>> >> wrote:
>> >>>
>> >>> Hi All,
>> >>>
>> >>> In the Admin doc, its written:
>> >>>
>> >>> quantum : a CLI utility for manually driving the Quantum API (note: in
>> >>> most common use
>> >>> cases, the Quantum API is primarily driven by another service, for
>> >>> example OpenStack
>> >>> Nova, and this CLI is used only for simple testing or
>> troubleshooting).
>> >>>
>> >>> Not very sure, but I think we don't have nova apis for  vifs and ports
>> >>> management. If there is
>> >>> please point me to that.
>> >>> If there is not then how is quantum CLI only meant for
>> >>> testing/troubleshooting.
>> >>>
>> >>> Have I misinterpreted something ?
>> >>>
>> >>>
>> >>> Thanks,
>> >>> Deepak
>> >>>
>> >>> --
>> >>> Mailing list: https://launchpad.net/~netstack
>> >>> Post to     : netstack@lists.launchpad.net
>> >>> Unsubscribe : https://launchpad.net/~netstack
>> >>> More help   : https://help.launchpad.net/ListHelp
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> >> Dan Wendlandt
>> >> Nicira Networks: www.nicira.com
>> >> twitter: danwendlandt
>> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> >>
>> >>
>> >> --
>> >> Mailing list: https://launchpad.net/~netstack
>> >> Post to     : netstack@lists.launchpad.net
>> >> Unsubscribe : https://launchpad.net/~netstack
>> >> More help   : https://help.launchpad.net/ListHelp
>> >>
>> >
>> >
>> > --
>> > Mailing list: https://launchpad.net/~netstack
>> > Post to     : netstack@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~netstack
>> > More help   : https://help.launchpad.net/ListHelp
>> >
>>
>
>
-- 
Mailing list: https://launchpad.net/~netstack
Post to     : netstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~netstack
More help   : https://help.launchpad.net/ListHelp

Reply via email to