[openstack-dev] Lenovo driver submission requests
Dear Devananda I'm the development leader of Lenovo Cloud Solution. Lenovo is planning to contribute its Ironic driver to the OpenStack community. The Ironic driver developers already registered as OpenStack members and signed agreement with OpenStack org. Sorry for broadcasting the message, but seems we have issue sending mails to GMail account from China. Devananda, do you have alternative mail for follow-up communication? Thanks. Best regards, Huang Kai (黄凯) OpenStack & VDI Leader EBG System Software Solutions huangk...@lenovo.com Ph: +86 18116117520 VOIP: 021-20590074 [Description: Lenovo-For-Those-Who-Do] From: Devananda van der Veen [mailto:devananda@gmail.com] Sent: Tuesday, July 21, 2015 7:30 AM To: OpenStack Development Mailing List Subject: [openstack-dev] [Ironic] No meeting tonight? Hi all, My apologies, but I won't be able to attend the IRC meeting tonight. The agenda is very light (basically non-existent) so I suggest that we just cancel it and meet next Monday. Also, I haven't seen any response to my email (*) from one week ago about the lack of attendance to this (late night for the US) meeting time from the very folks who this meeting is supposed to serve. Thanks, Devananda (*) http://lists.openstack.org/pipermail/openstack-dev/2015-July/069363.html __ 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-dev] Lenovo driver submission requests
Dear Devananda I'm the development leader of Lenovo Cloud Solution. Lenovo is planning to contribute its Ironic driver to the OpenStack community. The Ironic driver developers already registered as OpenStack members and signed agreement with OpenStack org. Sorry for broadcasting the message, but seems we have issue sending mails to GMail account from China. Devananda, do you have alternative mail for follow-up communication? Thanks. Best regards, Huang Kai (黄凯) OpenStack & VDI Leader EBG System Software Solutions huangk...@lenovo.com Ph: +86 18116117520 VOIP: 021-20590074 [Description: Lenovo-For-Those-Who-Do] From: Devananda van der Veen [mailto:devananda@gmail.com] Sent: Tuesday, July 21, 2015 7:30 AM To: OpenStack Development Mailing List Subject: [openstack-dev] [Ironic] No meeting tonight? Hi all, My apologies, but I won't be able to attend the IRC meeting tonight. The agenda is very light (basically non-existent) so I suggest that we just cancel it and meet next Monday. Also, I haven't seen any response to my email (*) from one week ago about the lack of attendance to this (late night for the US) meeting time from the very folks who this meeting is supposed to serve. Thanks, Devananda (*) http://lists.openstack.org/pipermail/openstack-dev/2015-July/069363.html __ 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
Re: [openstack-dev] [Ironic] 'Chassis' element in Ironic
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
