> On May 25, 2016, at 13:53, jason wrote:
>
> Thanks, and yes you got my point, my "automatically ", means after a new node
> has been discovered , the deployement process starts automatically. Cron may
> help, but what if I need more info to check if that new discovered node
> deserves to be
Hi Aleksandr,
Thanks for the examples! That will really help me a lot.
On May 25, 2016 6:26 PM, "Aleksandr Didenko" wrote:
> Hi,
>
> +1 to Igor. It should be easily doable via some sort of "watcher" script
> (run it as a daemon or under cron), that script should:
>
> - watch for new nodes in 'dis
Hi Igor,
Thanks, and yes you got my point, my "automatically ", means after a new
node has been discovered , the deployement process starts automatically.
Cron may help, but what if I need more info to check if that new discovered
node deserves to be a compute node or not? Can the cron script get
Hi,
+1 to Igor. It should be easily doable via some sort of "watcher" script
(run it as a daemon or under cron), that script should:
- watch for new nodes in 'discover' state. CLI example:
fuel nodes
- assign new nodes to env with compute role. CLI example:
fuel --env $ENV_ID node set --node
Hey Jason,
What do you mean by "automatically"?
You need to assign "compute" role on that discovered node, and hit "Deploy
Changes" button. If you really want to deploy any new discovered node
automatically, I think you can create some automation script and put it under
cron.
Hope it helps,
I
Hi All,
Is there any way for fuel to deploy a newly discovered node as a compute
node automatically? I followed the openstack doc for fuel but did not get
any answer.
__
OpenStack Development Mailing List (not for usage questi
