<div dir="ltr">I will join you. Thanks!</div><div class="gmail_extra"><br clear="all"><div><div dir="ltr">Filipe Manco<br><div><a href="http://about.me/fmanco" target="_blank">http://about.me/fmanco</a></div></div></div>
<br><br><div class="gmail_quote">2013/7/10 Kyle Mestery (kmestery) <span dir="ltr"><<a href="mailto:kmestery@cisco.com" target="_blank">kmestery@cisco.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Jul 9, 2013, at 8:40 PM, Filipe Manco <<a href="mailto:filipe.manco@gmail.com">filipe.manco@gmail.com</a>> wrote:<br>
><br>
> Hi Kyle<br>
><br>
> I already looked at the blueprints and I want to integrate my work with ML2, mainly because I want users to able to keep the traditional networking models working in parallel (and I think ML2 is the best way to do this comparing with the meta plugin).<br>
><br>
> To be honest, the integration with Neutron and the ML2 was what took most of the time when writing the blueprint, but although I talk about it on the blueprint I still not sure about the best way to do it.<br>
><br>
> About the concept of segments I don't think they fit. From what I understand a segment, in the context of ML2, represents part of the virtual network that uses some technology to connect a set of VMs, so if I delete a segment those VMs will loose connectivity. In the context of my blueprint a segment (or cSegment as I called it) represents a domain where I can create virtual links across a set of nodes. If I delete a cSegment that doesn't mean any VM will loose connectivity, what will happen is that the network is remapped and the traffic will cross another cSegment or another set of cSegments.<br>
><br>
</div>I think what you've mentioned here is valid, yes, and is a slight deviation between the way segments in ML2 work on your cSegments. It looks like we would need to add your new constructs into the ML2 API to achieve what you're looking for.<br>
<div class="im"><br>
> Something that I would like you (or other guys from ML2) to comment is how to integrate new operations (beyond the ones related with the base data model) in the ML2 interfaces. The MechanismDriver interface supports operations on ports and networks, but as you can see I have new entities. My idea is that there should be no changes to the original interfaces, because this are specific to a type of network. What do you think?<br>
><br>
</div>I'll have a look at this tomorrow and give you more detailed feedback. If you want, you can join us in the ML2 meeting at 1400UTV meeting on #openstack-meeting and I'll save some time at the end of the meeting to discuss your blueprint.<br>
<br>
Thanks!<br>
<span class="HOEnZb"><font color="#888888">Kyle<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
> It would help me if you have the time to take a look at the blueprint and comment on the ML2 parts.<br>
><br>
> Thanks for your help!<br>
><br>
> Filipe Manco<br>
> <a href="http://about.me/fmanco" target="_blank">http://about.me/fmanco</a><br>
><br>
><br>
> 2013/7/9 Kyle Mestery (kmestery) <<a href="mailto:kmestery@cisco.com">kmestery@cisco.com</a>><br>
> On Jul 9, 2013, at 11:18 AM, Filipe Manco <<a href="mailto:filipe.manco@gmail.com">filipe.manco@gmail.com</a>> wrote:<br>
> ><br>
> > Hi all,<br>
> ><br>
> > Just published a blueprint for some work I'm starting right now. I would appreciate if someone can take a look and give some comments.<br>
> ><br>
> > <a href="https://blueprints.launchpad.net/neutron/+spec/campus-network" target="_blank">https://blueprints.launchpad.net/neutron/+spec/campus-network</a><br>
> ><br>
> > Thank you<br>
> ><br>
> Hi Filipe:<br>
><br>
> At first glance, there appears to be a lot of overlap with ML2 here. Have you looked at the ML2 blueprints, and the specific use case of multi-segment networks? The ML2 team is working hard to close ML2 blueprints in H2/H3, perhaps some of your ideas could be incorporated here?<br>
><br>
> Here is the ML2 Meeting page which has links to the blueprints we're tracking:<br>
><br>
> <a href="https://wiki.openstack.org/wiki/Meetings/ML2" target="_blank">https://wiki.openstack.org/wiki/Meetings/ML2</a><br>
><br>
> Thanks,<br>
> Kyle<br>
><br>
> ><br>
> > Filipe Manco<br>
> > <a href="http://about.me/fmanco" target="_blank">http://about.me/fmanco</a><br>
> > _______________________________________________<br>
> > OpenStack-dev mailing list<br>
> > <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>