Tricircle (now turn to be dedicated for cross Neutron networking automation) would like to have one BoF session and design session (or combined?) in Barcelona summit, is it possible to have a meeting room for that.
Tricircle splitting is ongoing, wiki/design doc update started, and draft is ready for review, the source code cleaning starts soon, hopefully will be ready before Barcelona summit. A blue print has been registered to track the splitting: https://blueprints.launchpad.net/tricircle/+spec/make-tricircle-dedicated-for-networking-automation-across-neutron Best Regards Chaoyi Huang(joehuang) From: Vitaly Gridnev [vgrid...@mirantis.com] Sent: 18 September 2016 22:48 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [all] Barcelona Design Summit track layout Hi Thierry, As we discussed during the last meeting, we agreed that 6wr + cm is absolutely enough for sahara. So, we can release one working room for other projects (for example Wed, 3:05 to 3:45) On Fri, Sep 16, 2016 at 5:22 PM, Thierry Carrez <thie...@openstack.org<mailto:thie...@openstack.org>> wrote: Hi everyone, I mapped the slot allocation (which I sent on Tuesday) to the available rooms in Barcelona, trying to take into account all the constraints you submitted and to avoid conflicts with talks on the conference side. Here is the result: https://docs.google.com/spreadsheets/d/1TQ-RSlbiBBEclkonIbfUP7R1ExZSJylF1uiEKV2G_Cw/pubhtml?gid=1107826458&single=true This is a pretty brittle (and unfun to build) house of cards, so I'd rather minimize the number of changes we push to it at this stage. A few things: 1. If you have a *hard* conflict that I failed to take into account (like the PTL is giving a talk during the one and only fishbowl room the team has), let me know and I'll try to find someone you could swap with. 2. If you already know that you won't be using a given slot, let me know which one(s) ASAP and I'll remove your team from it to make it available for others. (NB: Freezer already gave up 2 wr slots) 3. If you would like to swap two slots, make sure both PTLs agree and let me know. I'll check that it doesn't create other conflicts and make it happen. 4. If you're an official or prospective team and you notice an empty slot that you'd like to use, let me know which one. I'll collect the requests and try to satisfy them. Note that the page will be refreshed as teams liberate extra slots they don't plan to use -- come back often! Priority will be given to teams which don't have representation at all. 5. We have to make the schedule "official" and push it to the main event schedule very soon. Please suggest all changes before end of next week (September 25) -- after that the layout will be frozen as we map it to real room numbers and publish it. Thanks! -- Thierry Carrez (ttx) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best Regards, Vitaly Gridnev, Project Technical Lead of OpenStack DataProcessing Program (Sahara) Mirantis, Inc
__________________________________________________________________________ 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
