Thank you all for the acceptance.
Regards,
Madhuri
On Mon, Mar 14, 2016 at 10:09 PM, Serg Melikyan
wrote:
> Granted
>
> On Mon, Mar 14, 2016 at 4:09 AM, Nikolay Starodubtsev <
> nstarodubt...@mirantis.com> wrote:
>
>> Hi,
>> I don't like when we need to break rules, but in this case I agree wit
Granted
On Mon, Mar 14, 2016 at 4:09 AM, Nikolay Starodubtsev <
nstarodubt...@mirantis.com> wrote:
> Hi,
> I don't like when we need to break rules, but in this case I agree with
> Kirill. As far as the plugin is not something which can broke general
> murano functionality, I'm for FFE.
>
>
>
> N
Hi,
I don't like when we need to break rules, but in this case I agree with
Kirill. As far as the plugin is not something which can broke general
murano functionality, I'm for FFE.
Nikolay Starodubtsev
Software Engineer
Mirantis Inc.
Skype: dark_harlequine1
2016-03-14 11:58 GMT+03:00 Kirill
I’m going to advocate for this FFE. Even though it’s very late to ask for FFE,
I believe, that this commit is very low-risk/high reward (the plugin is not
enabled by default). I believe that code is in good shape (I remember +2 it at
some point) and would very much like to see this in.
Serg, do
Hi All,
I would like to request a feature freeze exception for "Magnum/Murano
rationalization" [1], Magnum app to deploy Kubernetes/Mesos/Swarm cluster.
The patch is on review[2].
I am looking for your decision about considering this change for a FFE.
[1]
https://blueprints.launchpad.net/murano/+
