Hi Gabriel, Thanks for the note. I raised the general issue of Quantum + Horizon at the team meeting yesterday, as it seemed like none of the quantum related tasks were prioritized, or assigned to a release (and hence, may not be on your radar).
- https://blueprints.launchpad.net/horizon/+spec/improve-quantum-summary-table - https://blueprints.launchpad.net/horizon/+spec/quantum-floating-ip - https://blueprints.launchpad.net/horizon/+spec/quantum-l3-support - https://blueprints.launchpad.net/horizon/+spec/quantum-network-topology - https://blueprints.launchpad.net/horizon/+spec/quantum-security-group - https://blueprints.launchpad.net/horizon/+spec/quantum-vnic-ordering I've asked Akihiro and Nachi to work with you to clean this up. It sounds like the BP you mention below should be a dependency for that last BP in the list. dan On Mon, Dec 10, 2012 at 12:46 AM, Gabriel Hurley <[email protected]>wrote: > I've been looking at the vNIC ordering UI issues and have updated the > related Horizon blueprint's whiteboard: > https://blueprints.launchpad.net/horizon/+spec/orderable-mutiple-choice-field > > However, I'm worried that I won't have the time to code it up myself in > G2, so I'm wondering if anyone from the quantum team would be willing to > try tackling it. I'm happy to provide advice/guidance on the implementation > as progress is made on it. > > I just want to make sure I'm not the blocker on that one. > > All the best, > > - Gabriel > > > -----Original Message----- > > From: Akihiro MOTOKI [mailto:[email protected]] > > Sent: Monday, November 26, 2012 8:52 AM > > To: Gabriel Hurley; [email protected] > > Cc: [email protected]; [email protected] > > Subject: Re: Horizon Quantum related BPs for Grizzly > > > > Hi, > > > > I registered Quantum related Horizon BPs as follows. > > > > [G-2] > > https://blueprints.launchpad.net/horizon/+spec/improve-quantum- > > summary-table > > https://blueprints.launchpad.net/horizon/+spec/quantum-l3-support > > https://blueprints.launchpad.net/horizon/+spec/quantum-floating-ip > > [G-2 or G-3] > > https://blueprints.launchpad.net/horizon/+spec/quantum-security-group > > https://blueprints.launchpad.net/horizon/+spec/quantum-vnic-ordering > > [G-3] (depends on nachi) > > https://blueprints.launchpad.net/horizon/+spec/quantum-network- > > topology > > > > I am not sure how vnic-ordering can be achieved at the moment and some > > investigation for other libraries are needed. > > This is the reason I target vnic-ordering to G-2 or G-3. > > > > > > In addition, network-quotas BP is realted to quantum. > > It requires quota extension for every core plugin. > > https://blueprints.launchpad.net/horizon/+spec/network-quotas > > > > Thanks, > > Akihiro > > > > >>>>> Date: Sun, 25 Nov 2012 12:06:03 -0800 > > >>>>> From: Dan Wendlandt <[email protected]> > > >>>>> Subject: Re: Horizon Quantum related BPs for Grizzly > > > > > > On Sun, Nov 25, 2012 at 8:31 AM, Akihiro MOTOKI > > <[email protected]> wrote: > > > > > > Hi Dan, Gabriel, > > > > > > Sorry for no actions for a pretty long time. > > > I will work hard :) to support them in G-2. > > > I will register BPs from now. > > > > > > >>>>> Date: Wed, 21 Nov 2012 13:20:01 -0800 > > > >>>>> From: Dan Wendlandt <[email protected]> > > > >>>>> Subject: Re: Horizon Quantum related BPs for Grizzly > > > > > > > > Hi Folks, > > > > > > > > Given that we're heading into the Grizzly-2 time period, I > wanted to > > touch base on progress > > > here. > > > > To me the "must haves" for Grizzly are: > > > > > > > - vnic ordering > > > > > > For vnic ordering, we need a new component to select vNICs with > > ordering. > > > > > > Gabriel, do we already have such component? > > > https://blueprints.launchpad.net/horizon/+spec/orderable-mutiple- > > choice-field > > > is related to this. I am not so familiar with such modules. > > > > > > > - l3 configuration (router CRUD, and connecting networks to > routers) > > > > - security group + floating Ips working with quantum. > > > > > > About L3 configuration the way is clear and just I need to work on > it. > > > For Floating IP with quantum, usecase is relatively simple and I > will > > > first sort out the difference in data model between nova and > quantum. > > > The main difference is that floating ip is associated with a VIF > in quantum > > > and we need to modify "associate floating IP" menu. > > > > > > For secgroup in quantum, we first clarify how to use quantum > secgroup. > > > A scenario I think is here: > > > > > http://wiki.openstack.org/Quantum/SecurityGroups#Workflow_scenarios > > > If so, VM launching sequence needs to be modified. > > > > > > That is correct. The common case is that the security groups for a > vnic are > > set when the VM > > > boots. That said, association of a security group with a vnic can > also be > > modified after a VM is > > > booted. The set of rules in a security group can be modified at any > time as > > well. > > > > > > dan > > > > > > > > > > > > Thanks, > > > Akihiro > > > > > > > > > > > Dan > > > > > > > > On Thu, Nov 1, 2012 at 12:35 PM, Gabriel Hurley > > <[email protected]> wrote: > > > > > > > > All generally looks good. A couple quick notes: > > > > > > > > > >>> * quantum-api-directly > > > > > >>> - Summary: To leverage full features of Quantum > such as IP > > > > > overlapping, > > > > > >>> we need to call Quantum API directly instead of > nova proxy. > > > > > >>> - Depends on: query-service-capabilities > > > > > > > > > > > > I'm not sure I follow this. Is this talking about > floating IPs? > > > > > > > > > > Yes. Quantum floating IP support is the target for this BP. > > > > > If there are any ohter topics easily implemented, they can > be > > included. > > > > > quantum security group support plans to be handled in > "quantum- > > security- > > > > > group" BP. > > > > > > > > Pieces where there is functionality overlap between nova > network > > and quantum are > > > encompassed > > > > in https://blueprints.launchpad.net/horizon/+spec/nova-net- > > quantum-abstraction and > > > anything > > > > else where there isn't overlap would obviously just use the > quantum > > API directly because > > > > there's no alternative. > > > > > > Oh, I missed nova-net-quantum-abstraction BP. It covers > "quantum-api- > > directly" > > > I plannedd. nova-net-quantum-abstraction is a broader concept and > this > > work > > > consists of two large items: security group and floating ip. > > > Thsu I will create an indidual BP for security group and floating > ip support > > > to track them. > > > > > > > > >>> * quantum-security-group > > > > > >>> - Summary: Support advanced features of Quantum > security > > group. > > > > > >>> Quantum security group support is being > implemented in > > Grizzly-1. > > > > > >>> Before implementing Horizon support, we need to > discuss > > how to use > > > > > >>> quantum security group combined with Nova. > > > > > >>> - Depends on: quantum-api-directly > > > > > >>> - Depends on: security-group-rules > > > > > > > > > > > > great, both of these make sense. > > > > > > > > > > I have not considered how to use quantum security group > > combined with > > > > > Nova. > > > > > Do you have a concrete plan already? > > > > > > > > I would definitely like to hear more about how this works. > > > > > > -- > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > Dan Wendlandt > > > Nicira, Inc: www.nicira.com > > > twitter: danwendlandt > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- Mailing list: https://launchpad.net/~quantum-core Post to : [email protected] Unsubscribe : https://launchpad.net/~quantum-core More help : https://help.launchpad.net/ListHelp
