[openstack-dev] [ironic] Boot from Volume meeting?
jim at jimrollenhagen.com
Wed Mar 1 20:10:07 UTC 2017
On Wed, Mar 1, 2017 at 9:07 AM, Dmitry Tantsur <dtantsur at redhat.com> wrote:
> Thanks for writing this!
> On 02/28/2017 03:42 PM, Julia Kreger wrote:
>> Greetings fellow ironic humanoids!
>> As many have known, I've been largely attempting to drive Boot from
>> Volume functionality in ironic over the past two years. Largely, in a
>> slow incremental approach, which is in part due to how I perceived it
>> to best fit into the existing priorities when the discussions started.
>> During PTG there was quite the interest by multiple people to become
>> involved and attempt to further Boot from Volume forward this cycle. I
>> would like to move to having a weekly meeting with the focus of
>> integrating this functionality into ironic, much like we did with the
>> tighter neutron integration.
>> I have two reasons for proposing a new meeting:
>> * Detailed technical status updates and planning/co-ordination would
>> need to take place. This would functionally be noise to a large number
>> of contributors in the ironic community.
>> * Many of these details would need need to be worked out prior to the
>> first part of the existing ironic meeting for the weekly status
>> update. The update being a summary of the status of each sub team.
>> With that having been said, I'm curious if we could re-use the
>> ironic-neutron meeting time slot  for this effort. That meeting
>> was cancelled just after the first of this year . In it's place I
>> think we should have a general purpose integration meeting, that could
>> be used as a standing meeting, specifically reserved at this time for
>> Boot from Volume work, but could be also by any integration effort
>> that needs time to sync-up in advance of the existing meeting.
> I'm in favor of a generic meeting. I'm not sure it's worth taking the
> whole 1 hour slot though. I think that the BFV one might only take half of
> slot, where the second half maybe taken by another integration subteam.
> Speaking of which, I propose the networking subteam to start (continue?)
> having their own meeting as well. There is a lot of stuff going on that is
> hard to catch up with.
We stopped that meeting because it had turned into a status update. We just
rolled it back up into the usual subteam updates.
I'd like to leave it to the folks working on that to decide if they need a
meeting to keep up with everything.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev