<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Could we move Functional Tests to Thursday? I have a hands-on workshop at wed 4:30-6:00 pm.</div><div class=""><br class=""></div><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Best Regards,</div><div class="">Ethan Lynn</div><div class=""><a href="mailto:xuanlangjian@gmail.com" class="">xuanlangjian@gmail.com</a></div><div class=""><br class=""></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Apr 20, 2016, at 09:26, Zane Bitter <<a href="mailto:zbitter@redhat.com" class="">zbitter@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 19/04/16 18:04, Steve Baker wrote:<br class=""><blockquote type="cite" class="">On 19/04/16 20:29, Steven Hardy wrote:<br class=""><blockquote type="cite" class="">On Tue, Apr 19, 2016 at 04:24:46PM +1200, Steve Baker wrote:<br class=""><blockquote type="cite" class=""> All of the TripleO design summit sessions are on Thursday afternoon in<br class=""> slots which clash with Heat sessions. Heat is a core component of TripleO<br class=""> and as a contributor to both projects I was rather hoping to attend as<br class=""> many of both sessions as possible - I don't think I'm alone in this<br class=""> desire.<br class=""><br class=""> Is it possible that some horse trading could take place to reduce the<br class=""> clashes? Maybe TripleO sessions could move to Wednesday morning?<br class=""></blockquote>Yes I agree this is unfortunate. I already queried the clashes wrt the<br class="">contributor meetups, and was told we can only adjust if we can find another<br class="">project willing to switch - I'm Open to negotiation if any other PTLs wish<br class="">to change sessions at this late stage.<br class=""><br class="">I see the current Heat schedule has SoftwareDeployment improvements [1] and<br class="">Issues with very large stacks [2] at non-conflicting times, which is good<br class="">as these are probably amongst the top priorities for TripleO (other than<br class="">performance improvements, which relates to very-large-stacks).<br class=""><br class="">One observation I would make is that Heat does have a pretty large number<br class="">of sessions (12 in total plus meetup), this is always going to present<br class="">challenges from a scheduling point of view - perhaps we can ask for a<br class="">volunteer or two (other than myself) from the Heat community who is willing<br class="">to cover at least the Upgrades fishbowl[3] and Composable Services<br class="">workroom[4] sessions if we can't resolve the conflicts.<br class=""><br class="">Thanks,<br class=""><br class="">Steve<br class=""><br class="">[1]<a href="https://www.openstack.org/summit/austin-2016/summit-schedule/events/9115" class="">https://www.openstack.org/summit/austin-2016/summit-schedule/events/9115</a><br class="">[2]<a href="https://www.openstack.org/summit/austin-2016/summit-schedule/events/9117" class="">https://www.openstack.org/summit/austin-2016/summit-schedule/events/9117</a><br class="">[3]<a href="https://www.openstack.org/summit/austin-2016/summit-schedule/events/9118" class="">https://www.openstack.org/summit/austin-2016/summit-schedule/events/9118</a><br class="">[4]<a href="https://www.openstack.org/summit/austin-2016/summit-schedule/events/9292" class="">https://www.openstack.org/summit/austin-2016/summit-schedule/events/9292</a><br class=""></blockquote><br class="">I think we could reduce the topic overlap just by shuffling the heat<br class="">sessions.<br class=""><br class="">Thomas, what do you think of the following?<br class="">Swap work sessions "Release model and versioning" and "Validation<br class="">improvements"<br class=""><a href="https://www.openstack.org/summit/austin-2016/summit-schedule/events/9240" class="">https://www.openstack.org/summit/austin-2016/summit-schedule/events/9240</a><br class="">https://www.openstack.org/summit/austin-2016/summit-schedule/events/9247<br class="">This would let me attend the tripleo CI work session, and the release<br class="">model session which I proposed ;)<br class=""></blockquote><br class="">I'm driving the validation improvements session, but I don't care about the conflicting TripleO session "Reducing the CI pain" so that's OK.<br class=""><br class=""><blockquote type="cite" class="">Swap work sessions "Performance improvements" and "hot-parser"<br class=""><a href="https://www.openstack.org/summit/austin-2016/summit-schedule/events/9236" class="">https://www.openstack.org/summit/austin-2016/summit-schedule/events/9236</a><br class="">https://www.openstack.org/summit/austin-2016/summit-schedule/events/9248<br class=""></blockquote><br class="">I think this is a no-go because it would put the hot-parser session on at the same time as the Tacker/heat-translator joint session that will necessarily have a bunch of the same people in it.<br class=""><br class=""><blockquote type="cite" class="">This will make the performance work session before the performance<br class="">fishbowl, but I'm sure we could make that work. Its not like we need the<br class="">fishbowl to solicit areas of improvement.<br class=""></blockquote><br class="">Umm, I thought that was the idea.<br class=""><br class="">I need to be at both of those Heat ones anyway, so this doesn't really help me. I'd rather have the DLM session in this slot instead. (The only sessions I can really skip are the Release Model, Functional Tests and DLM.) That would give us:<br class=""><br class=""> Heat TripleO<br class=""><br class=""> Wed 3:30 Release Model<br class=""> Wed 4:30 HOT Parser<br class=""> Wed 5:20 Functional Tests<br class=""><br class=""> Thu 1:30 DLM Upgrades<br class=""> Thu 2:20 Convergence switchover Containers<br class=""> Thu 3:10 Convergence cleanup Composable Roles<br class=""> Thu 4:10 Performance API<br class=""> Thu 5:00 Validation CI<br class=""><br class="">I think that way Steve and I could probably both cover upgrades, and he could cover the rest.<br class=""><br class="">I'd like to get to the composable roles and containers sessions too, but we'd have to rejig basically every Heat session and I think it's too late to be doing that.<br class=""><br class="">cheers,<br class="">Zane.<br class=""><br class="">__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></div></blockquote></div><br class=""></body></html>