Chassis alone is a management module too, rather than simply grouping nodes (as enclosure). Some chassis has individual fans, powers, even mini-switches. It normally also act as a supervisor of nodes udner it, to perform discovery, rescue tasks, which are not possible for node itself alone. It is wise to keep it in the API, for future extension (which will certainly happen).
Huang Kai -----Original Message----- From: Lucas Alvares Gomes [mailto:lucasago...@gmail.com] Sent: Monday, March 23, 2015 5:53 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Ironic] 'Chassis' element in Ironic Hi, > In one of the Ironic IRC meetings, a discussion on whether to retain > the ‘Chassis’ element in Ironic or not came up. > > I am interested to know whether this is still valid and a decision is > to be made on whether the component is retained or not. > Even tho the Chassis resource in our API is not being very used, right now the only thing it does is to group nodes*, one thing is: We can't simply remove it from the v1 API so, it will be there. For future versions of the API maybe we can group nodes differently, using a label for example. But we don't have plans for a new version of the API yet and v1 will still be supported for some time. * We could use Chassis for more things, multi-node actions. Cheers, Lucas __________________________________________________________________________ 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 __________________________________________________________________________ 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
