[openstack-tc] Finalizing Barcelona cross-project workshops schedule

John Garbutt john at johngarbutt.com
Wed Oct 5 14:33:11 UTC 2016


Looks good. I really appreciate rolling upgrade being in an ops friendly slot.

Personally, I think it means I can't attend either part of
"Experiences with project decomposition", but thats is only a soft
conflict.

Thanks,
John

On 5 October 2016 at 15:29, Doug Hellmann <doug at doughellmann.com> wrote:
> This looks good to me. Thanks, Thierry!
>
>> On Oct 5, 2016, at 6:42 AM, Thierry Carrez <thierry at openstack.org> wrote:
>>
>> Hi, TC members,
>>
>> At the meeting yesterday we worked on the schedule for the cross-project
>> workshops. We had known issues (conflicts for dhellmann), I found a few
>> new constraints (ops are pretty busy at 2:15pm with AUC/UC sessions) and
>> we discussed separating the two "project decomposition" sessions to
>> sleep on it and allow to take input from other sessions (like the
>> proprietary drivers one)...
>>
>> So I tweaked it again to solve those constraints and here is what I came
>> up with:
>>
>> Tuesday (25th) -----------------------------
>> 3:55 - 4:35pm
>>    2. Discuss community-wide release goals
>>    14. Unified capabilities discovery API
>> 5:05 - 5:45pm
>>    13. Experiences with project decomposition (part 1)
>>    6. Cross-Service Communication
>> 5:55 - 6:35pm
>>    5. Where to draw the line for proprietary code with drivers
>>    4. Python 3 Integration Testing
>>
>> Wednesday (26th) ---------------------------
>> 11:25 - 12:05pm (place ops-oriented stuff here)
>>    10. Architecture Working Group Fishbowl
>>    3. Ocata Goal: Remove Incubated Oslo Code
>> 12:15 - 12:55pm (place ops-oriented stuff here)
>>    7. Stewardship Working Group (SWG) discussion
>>    11. Rolling upgrades, and the road to zero-downtime
>> 2:15 - 2:55pm
>>    13. Experiences with project decomposition (part 2)
>>    16. Driver Log Validation
>>
>> The only soft conflict I detected here is thingee not being able attend
>> decomposition part 2, but I couldn't find a way to fix that that would
>> not create a hard conflict for dhellmann. I may have missed some other
>> constraint though! Let me know how well that works for you...
>>
>> --
>> Thierry Carrez (ttx)
>>
>> _______________________________________________
>> OpenStack-TC mailing list
>> OpenStack-TC at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc
>
>
> _______________________________________________
> OpenStack-TC mailing list
> OpenStack-TC at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc



More information about the OpenStack-TC mailing list