<p dir="ltr">Hi Aleksandr,<br>
Thanks for the examples! That will really help me a lot.</p>
<div class="gmail_quote">On May 25, 2016 6:26 PM, "Aleksandr Didenko" <<a href="mailto:adidenko@mirantis.com">adidenko@mirantis.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div>Hi,<br><br></div>+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:<br><br></div>- watch for new nodes in 'discover' state. CLI example:<br> fuel nodes<br></div>- assign new nodes to env with compute role. CLI example:<br> fuel --env $ENV_ID node set --node $NEW_NODE_ID --role compute<br></div>- update networks assignment for new node. CLI example:<br> fuel node --node $NEW_NODE_ID --network --download<br></div> # edit /root/node_$NEW_NODE_ID/interfaces.yaml<br><div><div> fuel node --node $NEW_NODE_ID --network --upload<br></div><div>- deploy changes. CLI example:<br> fuel deploy-changes --env $ENV_ID<br><br></div><div>Regards,<br></div><div>Alex<br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 25, 2016 at 12:03 PM, Igor Kalnitsky <span dir="ltr"><<a href="mailto:ikalnitsky@mirantis.com" target="_blank">ikalnitsky@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey Jason,<br>
<br>
What do you mean by "automatically"?<br>
<br>
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.<br>
<br>
Hope it helps,<br>
Igor<br>
<span><br>
> On May 25, 2016, at 12:33, jason <<a href="mailto:huzhijiang@gmail.com" target="_blank">huzhijiang@gmail.com</a>> wrote:<br>
><br>
> Hi All,<br>
><br>
> 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.<br>
><br>
</span>> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div>