Open Stack

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 $NEW_NODE_ID --role compute
- update networks assignment for new node. CLI example:
  fuel node --node $NEW_NODE_ID --network --download
  # edit /root/node_$NEW_NODE_ID/interfaces.yaml
  fuel node --node $NEW_NODE_ID --network --upload
- deploy changes. CLI example:
  fuel deploy-changes --env $ENV_ID

Regards,
Alex

On Wed, May 25, 2016 at 12: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/3b466cbf/attachment.html>