# Question: QuantumServicesInsertion; quantum/services

Hi Quantum experts!

points to a new directory path "/quantum/quantum/services/"

However, the only "services" directory I find on github ( https://github.com/openstack/quantum/tree/master/quantum (https://github.com/openstack/quantum/...) ) is under plugins/cisco ( https://github.com/openstack/quantum/tree/master/quantum/plugins/cisco (https://github.com/openstack/quantum/...) ).

Thus, I assume that this wrapper does not work with OVS, yes ?

If that is the case, is there any plan to provide the similar for OVS ?

Thanks! Piyanai

edit retag close merge delete

Sort by » oldest newest most voted

adding edgar to the thread, as he has been working on this.

with a few minor tweaks, this service insertion capability can be used across all plugins.

edgar and I spoke a while back about plans to move this functionality more to be a separate utility/library, outside of the main quantum service. If the code continues to depend on a mysql database, it will probably just be its own separate utility/library. Otherwise it may just get folded into the python-quantumclient library.

more

Hello Piyanai,

We are planning to remove the mysql dependency and also to move this code into the python-quantumclient repository as Dan has already mentioned. Once we are done with those two things, this library should be agnostic to any plugin available in Quantum.

more

Thank you Dan and Edgar for the clarification. That helps.

Wonder if the two items mentioned had been planned to be done in essex rc ?

Or perhaps, this is for Folsom ?

I think this is more a completeness of feature according to the original blueprint rather than a bug. But if it would help, I can create a bug report for tracking. Please let me know.

more

Hi,

You are absolutely right, network services insertion should be discussed during Folsom Summit. I have already submitted a session proposal and I will work on updating the blueprint. Based on some discussions with Dan and Monthy, it seems that the right place for this kind of libraries will be on the Quantum Client code and it should work for all PlugIns supported by Quantum Server.

So I am planning to work on that for Folsom first release. However, let's have a discussion for that during the summit and close the gap on this topics.

Thanks,

Edgar

-----Original Message----- From: bounces@canonical.com [mailto:bounces@canonical.com] On Behalf Of Piyanai Saowarattitada Sent: Monday, March 19, 2012 4:11 PM To: Edgar Magana (eperdomo) Subject: Re: [Question #186990]: Question: QuantumServicesInsertion;quantum/services

Status: Answered => Open


Piyanai Saowarattitada is still having a problem:

Thank you Dan and Edgar for the clarification. That helps.

Wonder if the two items mentioned had been planned to be done in essex rc ?

Or perhaps, this is for Folsom ?

I think this is more a completeness of feature according to the original blueprint rather than a bug. But if it would help, I can create a bug report for tracking. Please let me know.

You received this question notification because you are a direct subscriber of the question.

more

Hi Edgar,

Based on some discussions with Dan and Monthy, it seems that the right place for this kind of libraries will be on the Quantum >Client code and it should work for all PlugIns supported by Quantum Server.

Definitely agree with this general school of thought here as long as we make it a choice for plugins to use the insertion library/utility rather than dictating that this service(s) insertion is the only insertion "library" of its kind to be supported by Quantum which I don't think is the intention here, but want to make sure I understand what is being planed here.

Really glad to see the discussion proposal for this topic at http://summit.openstack.org/ . Hopefully, the session will get accepted - it's in "Unreviewed" state at the moment.

Unfortunately, I do not have ticket to the summit next month. Do you plan on having remote participation for your session ? Recall seeing Stefano's remote participation planing - https://lists.launchpad.net/openstack/msg08360.html (https://lists.launchpad.net/openstack...) .

I am marking this problem as "solved" because - there is a discussion proposal planed (and hopefully accepted) for the Folsom summit next month. - planed release target time frame - Folsom first release.

Thanks! Piyanai

more

# Get to know Ask OpenStack

Resources for moderators

## Stats

Seen: 43 times

Last updated: Mar 20 '12