Makes sense to me.
Opened a bug to track the migration of agents/n1kv_vem.pp out of
puppet-neutron during the M-cycle:
https://bugs.launchpad.net/puppet-neutron/+bug/1501535
Thanks.
Steven Hillman
On 9/29/15, 9:23 AM, "Emilien Macchi" wrote:
>My suggestion:
>
>* patch master to send deprecatio
On 09/29/2015 12:23 PM, Emilien Macchi wrote:
> My suggestion:
>
> * patch master to send deprecation warning if third party repositories
> are managed in our current puppet-neutron module.
> * do not manage third party repositories from now and do not accept any
> patch containing this kind of
My suggestion:
* patch master to send deprecation warning if third party repositories
are managed in our current puppet-neutron module.
* do not manage third party repositories from now and do not accept any
patch containing this kind of code.
* in the next cycle, we will consider deleting legacy
On 09/25/2015 12:14 PM, Edgar Magana wrote:
> Hi There,
>
> I just added my comment on the review. I do agree with Emilien. There should
> be specific repos for plugins and drivers.
>
> BTW. I love the sdnmagic name ;-)
>
> Edgar
>
>
>
>
> On 9/25/15, 9:02 AM, "Emilien Macchi" wrote:
>
>
Hi There,
I just added my comment on the review. I do agree with Emilien. There should be
specific repos for plugins and drivers.
BTW. I love the sdnmagic name ;-)
Edgar
On 9/25/15, 9:02 AM, "Emilien Macchi" wrote:
>In our last meeting [1], we were discussing about whether managing or
>n
In our last meeting [1], we were discussing about whether managing or
not external packaging repositories for Neutron plugin dependencies.
Current situation:
puppet-neutron is installing (packages like neutron-plugin-*) &
configure Neutron plugins (configuration files like
/etc/neutron/plugins/*.i