hi Tom I like your idea on define a generic approach of bay life cycle operations.
Seems current propose is to allow user dynamically adding/deleting nodes from a created bay, what if the master/node flavor in baymodel(bay's flavor) ? if a user add a new node with flavor which is not defined in baymodel, what the behavior should be like, bad request?
Beside, seems we added a new resource 'node' which will represent a node in cluster, then what the node api looks like? how to deail a orphan node? if a node (or node group) is deleted by user from a bay, destroy it(them) or just detach them? We may need to think about node life-cycle too.
We can also define a group nodes as node group to allow user do batch operation.
On 2016年05月16日 17:28, Cammann, Tom wrote:
magnum bay-manage <bay> reset –hard magnum bay-manage <bay> rebuild magnum bay-manage <bay> node-delete <name/uuid> magnum bay-manage <bay> node-add –flavor <flavor> magnum bay-manage <bay> node-reset <name> magnum bay-manage <bay> node-list
-- Best Regards, Eli Qiao (乔立勇) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
