On Jun 18, 2013, at 2:41 AM, Luke Gorrie <[email protected]> wrote:
> 
> 
> 12 jun 2013 kl. 09:25 skrev Andre Pech:
> 
>> As promised at the ml2 kickoff meeting last week, attached is our basic 
>> proposal for the ml2 mechanism driver API.
> 
> Great, that is fast work!
> 
>> After getting more familiar with the ml2 plugin code and looking at some of 
>> the other blueprints that are looking to make use of the MechanismDriver, 
>> we've instead gone with a more simple passthrough model using the existing 
>> plugin language of create_network / update_network / delete_network / 
>> create_port / update_port / delete_port.
> 
> Is it intentional to exclude create_subnet / update_subnet / delete_subnet, 
> which are also a part of the QuantumPluginBaseV2 API?
> 
> We have currently included Subnets in the data model that we want to 
> synchronize via our mechanism driver. So I would like to either include these 
> subnet-related callbacks in the MechanisnDriver API, or find a good reason to 
> eliminate Subnets from our data model so that they don't need to be 
> synchronized.
> 
> Kyle, do you guys have the same issue with the OpenDaylight plugin?
> 
We will want subnets for the ODL ML2 driver as well, so I think we'll want them 
here as well. Luke, maybe add these comments into the MechanismDriver review 
here:

https://review.openstack.org/#/c/33201/6

Thanks,
Kyle

> Thanks very much Andre & Arista gang for hacking this up so quickly. I am 
> excited to get started on our mechanism driver.
> 
> Cheers,
> -Luke
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> [email protected]
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to