Matt/Emilien,
I'm cool with removing the one-off core group for puppet-monasca and falling
into line with the other modules...
Let me know if you need me to take any action/push a patch..
Thanks,
Brad
Emilien,
I've discussed this with some of the Monasca puppet guys here who are doing
most
Hi Emilien,
I don't think Murano team needs to be core on a Puppet module ether,
current scheme was implemented per your proposal [1] and I am happy
that we are ready to move Murano to the same scheme that is used with
other projects.
I've updated ACL for puppet-murano project:
https://review.ope
On 09/15/2015 07:39 AM, Ivan Berezovskiy wrote:
> Emilien,
>
> puppet-murano module have a bunch of patches from Alexey Deryugin on
> review [0], which implements most of all Murano deployment stuff.
> Murano project was added to OpenStack namespace not so long ago, that's
> why I suggest to hav
Emilien,
puppet-murano module have a bunch of patches from Alexey Deryugin on review
[0], which implements most of all Murano deployment stuff.
Murano project was added to OpenStack namespace not so long ago, that's why
I suggest to have murano-core rights on puppet-murano as they are till all
the
Emilien,
I've discussed this with some of the Monasca puppet guys here who are doing
most of the work. I think it probably makes sense to move to that model
now, especially since the pace of development has slowed substantially. One
blocker before to having it "big tent" was the lack of test cover
Hi,
As a reminder, Puppet modules that are part of OpenStack are documented
here [1].
I can see puppet-murano & puppet-mistral Gerrit permissions different
from other modules, because Mirantis helped to bootstrap the module a
few months ago.
I think [2] the modules should be consistent in govern
