On 04/08/15 00:00, David Medberry wrote:
I think planning for people to leave early is a very poor idea. Planning to make sure things that need to get done first is fine though. Let's not think of the second day as a partial day.
+1, we already do finish a little early on the second day to facilitate these folks. The other thing that may not be immediately clear is that the agenda is also specifically designed so that people who don't care as much can skip the feedback session/summit planning/breakout reports at the end of day 2.
As someone who spends about 30-40 hours on various planes and airports to get to and from this event, I struggle to find significant amounts of sympathy for those who feel it necessary to leave three quarters of the way through to get home "at a reasonable time" ;)
When all is said and done, if our content is compelling, people will stay. So, making our event so damn good that people don't want to leave even after it's finished should probably be our aim :D
Having said this, I don't think it was JJ's intention to do anything other than recognise the tools and mon session as important and make sure it received the most attention possible. That's valid.
Unfortunately, moving it to the previous day would basically just be moving the problem around - we're balancing the time slot used against conflicts in other time slots. Large Deployment Team for example is another very popular session, which has a lot of participant overlap between Monitoring and Tools, so it's probably not a good idea to run those against each other. Which means we're basically at a swap - should Tools be on Day 1, or should LDT be on day 1?
There's some thoughts on scheduling at: https://wiki.openstack.org/wiki/Operations/Meetups#Scheduling , which conclude with "Use best judgement, and get wide feedback.", and it's issues like this which are exactly why we have this email, so ... what do you think we should do? :)
Regards, Tom
On Mon, Aug 3, 2015 at 9:49 AM, JJ Asghar <j...@chef.io <mailto:j...@chef.io>> wrote: On 8/3/15 5:48 AM, Tom Fifield wrote:Hi all, Registrations are going well for our meetup in Palo Alto. If you're on the fence, hopefully this discussion will get you quickly over the line so you don't miss out! http://www.eventbrite.com/e/openstack-ops-mid-cycle-meetup-tickets-17703258924 So, I've taken our suggestions and attempted to wrangle them into something that would fit in the space we have over 2 days. As a reminder, we have two different kind of sessions - General Sessions, which are discussions for the operator community aimed to produce actions (eg best practices, feedback on badness), and**Working groups**focus on specific topics aiming to make concrete progress on tasks in that area. As always, some stuff has been munged and mangled in an attempt to fit it in. For example, we'd expect to talk about Kolla more generally in the context of "Using Containers for Deployment", because there are some other ways to do that too. Similarly, we'd expect the "ops project" discussion to be rolled into the session on the user committee. Anyway, take a look at the below and reply with your comments! Is anything missing? Something look like a terrible idea? Want to completely change the room layout? There's still a little bit of flexibility at this stage. Tuesday Med II Med III Salon A Salon B Bacchus 9:00 - 10:00 Registration 10:00 - 10:30 Introduction 10:30 - 11:15 Burning Issues 11:15 - 11:55 Hypervisor Tuning 11:55 - 12:05 Breakout Explain 12:05 - 13:30 Lunch 13:30 - 15:00 Large Deployments Team Burning Issues Logging WG Upgrades WG Ops Guide Fixing 15:00 - 15:30 Coffee 15:30 - 16:00 Breakout Reports 16:00 - 17:00 Using Containers for Deployment 17:00 - 18:00 Lightening Talks Wednesday Med II Med III Salon A Salon B Bacchus 9:00 - 09:45 CMDB: use cases 9:45 - 10:30 Deployment Tips - read only slaves? admin-only API servers? 10:30 - 11:15 What network model are you using? Are you happy? 11:15 - 11:30 Coffee 11:30 - 12:15 User Committee Discussion 12:15 - 12:20 Breakout Explain 12:20 - 13:30 Lunch 13:30 - 15:00 Tools and Monitoring Product WG Packaging HPC Working Group Ops Tags Team 15:00 - 15:30 Coffee 15:30 - 16:00 Breakout Reports 16:00 - 17:00 Feedback Session, Tokyo Planning There will be a followup email shortly regarding moderators for the sessions - thanks to those who volunteered so far! Regards, TomLooks awesome Tom! I do have one suggestion though. If the Philly Ops meetup was any suggestion, people started leaving by noon the second day to catch flights. Tools and Monitoring, which is always a great topic to discuss, probably should be moved to the first day. Other than that great, and I'm crazy excited! Best Regards, JJ Asghar c:512.619.0722 <tel:512.619.0722> t: @jjasghar irc: j^2 _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org <mailto:OpenStack-operators@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
