<div dir="ltr">Looking through the schedule of keystone-tagged sessions, it appears we have a conflict between one of the BM/VM sessions [0] and keystone's project on-boarding session [1].<div><br></div><div>I wouldn't be opposed to shuffling, but I assume it's too late for that? If we can get a good idea of who is going to show up for the project on-boarding session and set a schedule, we might just be able to start it at 11:45 AM instead of 11:00. This would avoid the conflict, not requiring late shuffling of sessions. It might also allow the team scheduled before keystone to run over in their on-boarding session if needed.</div><div><br></div><div>I'd be fine doing that if we can get a rough idea of attendance, what people want information on, and plan accordingly. </div><div><br></div><div>Let's use this thread to air some of that out. Thoughts?</div><div><br></div><div><br></div><div>Thanks,</div><div><br></div><div>Lance</div><div><br></div><div>[0] <a href="https://www.openstack.org/summit/boston-2017/summit-schedule/events/18794/operating-the-vm-and-baremetal-platform-22">https://www.openstack.org/summit/boston-2017/summit-schedule/events/18794/operating-the-vm-and-baremetal-platform-22</a></div><div>[1] <a href="https://www.openstack.org/summit/boston-2017/summit-schedule/events/18712/keystone-project-onboarding">https://www.openstack.org/summit/boston-2017/summit-schedule/events/18712/keystone-project-onboarding</a></div></div>