I am planning on looking into Murano later this year so I'd be interested
in helping review this code. I'm puppet-core so feel free to add me to
reviews and I can look as time permits.
On Wed, Jun 17, 2015 at 9:49 AM, Serg Melikyan smelik...@mirantis.com
wrote:
Emilien,
Thank you for your
Hi Emilien,
I would like to answer your question regarding
stackforge/puppet-murano repository asked in different thread:
Someone from Fuel team created first the module in Fuel, 6 months ago
[1] and 3 months later someone from Fuel team created an empty
repository in Stackforge [2]. By the
Hi Serg,
On 06/17/2015 05:35 AM, Serg Melikyan wrote:
Hi Emilien,
I would like to answer your question regarding
stackforge/puppet-murano repository asked in different thread:
Someone from Fuel team created first the module in Fuel, 6 months ago
[1] and 3 months later someone from Fuel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/17/2015 08:53 AM, Emilien Macchi wrote:
Hi Serg,
On 06/17/2015 05:35 AM, Serg Melikyan wrote:
Hi Emilien,
I would like to answer your question regarding
stackforge/puppet-murano repository asked in different thread:
Someone from
Thank you for sharing link to list of things that new module should
satisfy to! It will be really helpful even if list will change over
time. At least we have pointers how to start making our module
compliant.
Regarding figuring out permissions - I don't mind if we will set
puppet-core as group
On 06/17/2015 09:50 AM, Serg Melikyan wrote:
Thank you for sharing link to list of things that new module should
satisfy to! It will be really helpful even if list will change over
time. At least we have pointers how to start making our module
compliant.
Regarding figuring out permissions
Hi guys!
* Do not merge a patch without at least one review from both groups
* Collaborate to make the module compliant
I'm strongly agree with it, because it'll help to avoid some mistakes.
Also, someone from puppet-manager-core may to prompt what are we doing
wrong or better way for
Emilien,
Thank you for your proposal, I completely agree with it:
* Move the module under the big tent
Proposed change in infra [1] and corresponding change in governance [2]
* Adding Puppet OpenStack group part of core permissions
I've added puppet-manager-core to puppet-murano-core
* Keep
