Open Stack

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 more
characteristics info about the node? For example , "if the new node has
right amount of nic interfaces, right setting of NUMA etc., then make it a
compute node with the same configuration as others with the same
characteristics".
On May 25, 2016 6:03 PM, "Igor Kalnitsky" <ikalnitsky at mirantis.com> wrote:

> 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,
> Igor
>
> > On May 25, 2016, at 12:33, jason <huzhijiang at gmail.com> wrote:
> >
> > 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 questions)
> > Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160525/c57d4d8a/attachment.html>