Re: [Openstack-operators] Ops Meetup event sizes

Great feedback Anita - thank you :) On 1 June 2016 at 20:42, Anita Kuno wrote: > On 06/01/2016 03:29 PM, David Medberry wrote: > > On Wed, Jun 1, 2016 at 2:12 AM, Matt Jarvis < > matt.jar...@datacentred.co.uk> > > wrote: > > > >> > >> The general consensus in the

Re: [Openstack-operators] Ops Meetup event sizes

I'll second David's comments, and second the fact that the Manchester layout seemed to work well. The facility in Manchester provided a couple secondary rooms plus a few much smaller rooms which I think generally worked well. Having a tertiary area for meals/"networking" type engagements should

Re: [Openstack-operators] Ops Meetup event sizes

On 06/01/2016 03:29 PM, David Medberry wrote: > On Wed, Jun 1, 2016 at 2:12 AM, Matt Jarvis > wrote: > >> >> The general consensus in the discussions we've had, and from the Austin >> summit sessions and the Manchester feedback session, is that between >> 150-200

Re: [Openstack-operators] Ops Meetup event sizes

On Wed, Jun 1, 2016 at 2:12 AM, Matt Jarvis wrote: > > The general consensus in the discussions we've had, and from the Austin > summit sessions and the Manchester feedback session, is that between > 150-200 attendees should be the maximum size. > Two comments,

Re: [Openstack-operators] Ops Meetup event sizes

+1 On 1 June 2016 at 16:54, Edgar Magana wrote: > I totally second Thierry. That was an excellent description of the > importance of having the Ops sessions in these events. > > Cheers, > > Edgar > > On 6/1/16, 2:49 AM, "Thierry Carrez" wrote: >

Re: [Openstack-operators] Ops Meetup event sizes

I totally second Thierry. That was an excellent description of the importance of having the Ops sessions in these events. Cheers, Edgar On 6/1/16, 2:49 AM, "Thierry Carrez" wrote: >Sam Morrison wrote: >> As an operator what should I prioritise now the main summit is

Re: [Openstack-operators] [osops] OSOps meeting today in #openstack-meeting-4 1900 UTC

unteering. You can review the agenda here. [1] If > you have anything that you think the Operators community can help with, > please come join the conversation. > > > Thanks > > Joe > > > [1] https://etherpad.openstack.org/p/osops-irc-meeting-20160601 > ___

Re: [Openstack-operators] Neutron database upgrade kilo-liberty and parallel Alembic migration branches

> On 01 Jun 2016, at 14:49, Saverio Proto wrote: > > Hello, > > reading this documentation page: > > http://docs.openstack.org/mitaka/networking-guide/migration-neutron-database.html > > I dont get what means having two parallel migration branches. > > Do you have to

[Openstack-operators] Neutron database upgrade kilo-liberty and parallel Alembic migration branches

Hello, reading this documentation page: http://docs.openstack.org/mitaka/networking-guide/migration-neutron-database.html I dont get what means having two parallel migration branches. Do you have to choose one of the branches ? If yes how ? Or it just means that some operations can be safely

[Openstack-operators] [osops] OSOps meeting today in #openstack-meeting-4 1900 UTC

can help with, please come join the conversation. Thanks Joe [1] https://etherpad.openstack.org/p/osops-irc-meeting-20160601 ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman

Re: [Openstack-operators] Ops Meetup event sizes

As an operator what should I prioritise now the main summit is changing, the thing formally known as the summit or the ops mid cycle? Will there be operator sessions at the summit still? Sorry if this has already been mentioned but still not 100% sure how operators fit into the new model.