Open Stack

Salvatore,

It would be great if you could include in this proposal the previous Services Insertion BP:
https://blueprints.launchpad.net/quantum/+spec/services-insertion-wrapper

It is also fully described here:
http://wiki.openstack.org/QuantumServicesInsertion

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:

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.

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:
http://wiki.openstack.org/quantum-l3

In terms of Tenant vs Provider perspective, what is exactly the proposal? Is this API tenant facing, provider or both?
I believe it should be for both, you can have services insertion at SP level and also per tenants.

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?

Scenario 1 in slide 14 is great, actually this is what we call In-Path service insertion, so we are in the same page.

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?

Scenario 3 is actually the realistic one, is what we call Out-of-Path service insertion, so we are good there.

I 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?

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.

Thanks,

Edgar Magana

From: Salvatore Orlando <sorlando at nicira.com<mailto:sorlando at nicira.com>>
Reply-To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Tuesday, October 23, 2012 5:15 PM
To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] [Quantum] Advanced service insertion

Hi all,

The blueprint for advanced services insertion has been registered and can be found here: https://blueprints.launchpad.net/quantum/+spec/quantum-service-insertion
The design specification is about 75% complete - your feedback is more than welcome.

Please use this email thread for discussing design details, unless you feel there's a more suitable medium.

Regards,
Salvatore
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121027/e64fdef8/attachment.html>