Open Stack

Hi all,

we have puppet module for ovs deployments with dpdk support
https://github.com/openstack/networking-ovs-dpdk/tree/master/puppet
and we would like to adapt it in a way that it can be used within upstream neutron module
e.g. to introduce class like this
neutron::agents::ml2::ovsdpdk

Current code works as follows:

-          Openstack with installed vanilla ovs is a kind of precondition

-          Ovsdpdk puppet module installation is triggered afterwards and it replace vanilla ovs by ovsdpdk

(in order to have some flexibility and mostly due to performance reasons we are building ovs from src code)

https://github.com/openstack/networking-ovs-dpdk/blob/master/puppet/ovsdpdk/files/build_ovs_dpdk.erb

-          As a part of deployments we have several shell scripts, which are taking care of build and configuration stuff

I assume that some parts of our code can be easily rewritten to start using standard providers other parts might be rewritten to ruby …
We would like to introduce neutron::agents::ml2::ovsdpdk as adequate solution with existing neutron::agents::ml2::ovs and not just patching it.

Actually I have following questions:
Q1) Will it be acceptable if we move build logic before deployment and resulting rpm/deb will be installed instead of ovs package during deployment ?
Q2) Do we need to rewrite bash logic into ruby code ?
Q3) Do we need to raise separate blueprint, which has to be approved  before starting adaptations ?

Thanks for any response,
Michal
--------------------------------------------------------------
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160302/a41fc016/attachment.html>