Also very important to understand that if task is mapped to role
controller, but node where you want to apply that task doesn't have this
role - it wont be executed.
Is there a particular reason why we want to restrict a user to run an
arbitrary task on a server, even if server doesn't have
On Sat, Feb 7, 2015 at 9:42 AM, Andrew Woodward xar...@gmail.com wrote:
Dmitry,
thanks for sharing CLI options. I'd like to clarify a few things.
Also very important to understand that if task is mapped to role
controller, but node where you want to apply that task doesn't have this
role -
Dmitriy,
Thank you for the excellent run-down of the CLI commands. I assume this
will make its way into the developer documentation? I would like to know if
you could point me to more information about the inner workings of granular
deployment. Currently it's challenging to debug issues related
Thank you for the excellent run-down of the CLI commands. I assume this
will make its way into the developer documentation? I would like to know if
you could point me to more information about the inner workings of granular
deployment. Currently it's challenging to debug issues related to
On Fri, Feb 6, 2015 at 11:16 PM, Mike Scherbakov mscherba...@mirantis.com
wrote:
Dmitry,
thanks for sharing CLI options. I'd like to clarify a few things.
Also very important to understand that if task is mapped to role
controller, but node where you want to apply that task doesn't have
Dmitry,
thanks for sharing CLI options. I'd like to clarify a few things.
Also very important to understand that if task is mapped to role
controller, but node where you want to apply that task doesn't have this
role - it wont be executed.
Is there a particular reason why we want to restrict a
Hello folks,
Not long ago we added necessary commands in fuel client to work with
granular deployment configuration and API.
So, you may know that configuration is stored in fuel-library, and uploaded
into database during
bootstrap of fuel master. If you want to change/add some tasks right on
