<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
Salvatore,</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
It would be great if you could include in this proposal the previous Services Insertion BP:</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<a href="https://blueprints.launchpad.net/quantum/+spec/services-insertion-wrapper">https://blueprints.launchpad.net/quantum/+spec/services-insertion-wrapper</a></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
It is also fully described here:</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<a href="http://wiki.openstack.org/QuantumServicesInsertion">http://wiki.openstack.org/QuantumServicesInsertion</a></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
I see a lot of common work between these two proposals, actually this one should be an extension of previous BP instead of having a new one. The mayor point of contribution in your BP is the API side that in the previous summit we decided to not targeted but
for Grizzly is a great opportunity. So, in terms of common areas I found these ones: </div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
You described three insertion points: network-level, router-level and port-level. The first and the second ones are exactly on the same lines that what is explained in the previous BP named as: In-Path (Bump in the Wire) and Out-of-Path (Redirection) insertion
models, the third one is a new one and I completely agree with it.</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
I don’t think that floating IPs is really a good example of Services Insertion, it is just a functionality that it was needed for nova parity but a formal L3 service is indeed required. We could also take a look to the work that Sumit presented last summit:</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<a href="http://wiki.openstack.org/quantum-l3">http://wiki.openstack.org/quantum-l3</a></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<br>
</div>
<div><font face="Calibri,sans-serif">In terms of Tenant vs Provider perspective, what is exactly the proposal? Is this API tenant facing, provider or both?</font></div>
<div><font face="Calibri,sans-serif">I</font><font face="Calibri,sans-serif"> believe it should be for both, you can have services insertion at SP level and also per tenants.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">API description in slide 10 is not really clear, I think we should just have one resource, SERVICE with all required CRUD operations, what do you think? Could you explain a little bit more on this area?</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">Scenario 1 in slide 14 is great, actually this is what we call In-Path service insertion, so we are in the same page.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">Scenario 2 in slide 15 is not very clear, how the traffic is redirected to the LB services in this example? Could you bring some light on this?</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">Scenario 3 is actually the realistic one, is what we call Out-of-Path service insertion, so we are good there.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">I</font><font face="Calibri,sans-serif"> think the API should be exclusively for managing services insertion but in slide 18 you mention "Tenant APIs for handling services types" what do you mean with that? How different
is that one from the SP one?</font></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
We did not have enough time during the summit to discuss about this but I hope we can continue this discussion over the mailing list. This is a very exiting work and we want to work together on the development.</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
Thanks,</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
Edgar Magana</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<br>
</div>
<span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Salvatore Orlando <<a href="mailto:sorlando@nicira.com">sorlando@nicira.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, October 23, 2012 5:15 PM<br>
<span style="font-weight:bold">To: </span>OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>[openstack-dev] [Quantum] Advanced service insertion<br>
</div>
<div><br>
</div>
<div>
<div>
<div>Hi all,</div>
<div><br>
</div>
The blueprint for advanced services insertion has been registered and can be found here: <a href="https://blueprints.launchpad.net/quantum/+spec/quantum-service-insertion">https://blueprints.launchpad.net/quantum/+spec/quantum-service-insertion</a>
<div>The design specification is about 75% complete - your feedback is more than welcome.</div>
<div><br>
</div>
<div>Please use this email thread for discussing design details, unless you feel there's a more suitable medium.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Salvatore</div>
</div>
</div>
</span>
</body>
</html>