Open Stack

Hello,

I think we need to increase the cap for real operators and not vendors but I have not attended the Ops meetups WG meetings so I do not know all the context about it.

BTW. DO we have a place and date for the next mid-cycle one?

Edgar

On 6/2/16, 1:16 PM, "Melvin Hillsman" <mrhillsman at gmail.com> wrote:

>Apologies,
>
>* On a side note, can we decide on a [email-subject-tag] to help filter these in [Openstack-operators]
>* Suggestion: [ops-meetups-team]
>
>For the delay that is since rain and Houston, TX fight a lot and rain is winning these days unfortunately. I was tasked with submitting to the ML a request to discuss how do we handle the waiting list for those who are not able to attend the Ops Midcycle due to the cap. Looking at EventBrite [ https://urldefense.proofpoint.com/v2/url?u=https-3A__www.eventbrite.com_support_articles_en-5FUS_How-5FTo_how-2Dto-2Dset-2Dup-2Dan-2Devent-2Dwaitlist-3Flg-3Den-5FUS&d=CwIGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=Izi115xT_K7kOrj3J8Dp44KcJDfJFyu8Tb_oYoroJng&s=nw_xXhA2xGfTOF5BCsJDlFzdMK7SbxZIyNcY0HqN0Bg&e=  ] if we are going to do a waitlist, this looks like a great option where basically we get details about the attendees we need and the waitlist is automatically created once the cap is hit.
>
>Playing devil’s advocate, my only apprehension to this process is should the waitlist be large, and there is a significant reason for someone who attended a previous Ops Midcycle to need to attend the next, how would that be handled? I am sure there are other potential issues that can be identified.
>
>Kind regards,
>--
>Melvin Hillsman
>Ops Technical Lead
>OpenStack Innovation Center 
>mrhillsman at gmail.com
>phone: (210) 312-1267
>mobile: (210) 413-1659
>Learner | Ideation | Belief | Responsibility | Command
>https://urldefense.proofpoint.com/v2/url?u=http-3A__osic.org&d=CwIGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=Izi115xT_K7kOrj3J8Dp44KcJDfJFyu8Tb_oYoroJng&s=pu6FOfWP0tAP8vf2pfzIrBPY1jdEnfIjOcI4ZUUA5dU&e= 
>
>
>
>
>
>
>
>On 6/1/16, 11:33 PM, "Tom Fifield" <tom at openstack.org> wrote:
>
>>Hello all,
>>
>>Thank you very much to the dozen of you who participated in our second 
>>meeting. We had some fantastic discussion, summarised below (the meeting 
>>overview can be found at [3] and the full log at [4]).
>>
>>
>>==Next Meeting==
>>Unless there is further discussion, this the next meeting is at:
>>
>>==> Tuesday, 14 of Jun at 1400 UTC[1] in #openstack-operators
>>
>>[2] will be kept up to date with information about the meeting time and 
>>agenda
>>
>>
>>==August Meetup==
>>Since there really isn't a lot of time left and we have proposals 
>>already, we decided for this time we would not do the open call.
>>So, gfa, shintano and I will be working behind the scenes with Bestbuy 
>>(Seattle) and Bloomberg (NYC) a little bit to get further details on 
>>their venues - we will report to the group as soon as we have some 
>>progress so we can make a decision for the August meetup.
>>
>>
>>
>>==Meetup size==
>>We had a great discussion on meetup size and it's looking like 150-200 
>>is the proposal, please participate in Matt Jarvis' thread at:
>>
>>https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_pipermail_openstack-2Doperators_2016-2DJune_010607.html&d=CwIGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=Izi115xT_K7kOrj3J8Dp44KcJDfJFyu8Tb_oYoroJng&s=x-Ny3jYrVkAxC5Ma-R7qRPQaTq_j3-TL5AF1WT6Z-48&e= 
>>
>>
>>
>>
>>==Waitlist management==
>>There was a good proposal on how to manage the waitlist (give those that 
>>missed out first go at the next one). mrhillsman will write that up and 
>>send it through to the list shortly.
>>
>>
>>
>>
>>Regards,
>>
>>
>>Tom
>>
>>
>>[1] 
>>https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_worldclock_fixedtime.html-3Fmsg-3DOps-2BMeetups-2BTeam-26iso-3D20160614T22-26p1-3D241&d=CwIGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=Izi115xT_K7kOrj3J8Dp44KcJDfJFyu8Tb_oYoroJng&s=_tbRGlaHlXJZc78QnSYGEx_TAvFkkpOAswKsr6wnUQA&e= 
>>
>>[2] https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.openstack.org_wiki_Ops-5FMeetups-5FTeam-23Meeting-5FInformation&d=CwIGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=Izi115xT_K7kOrj3J8Dp44KcJDfJFyu8Tb_oYoroJng&s=3GqOnGDbijK8PjA-WRrrZdpx5PavL8UmOBJ4E6izO0M&e= 
>>
>>[3] 
>>https://urldefense.proofpoint.com/v2/url?u=http-3A__eavesdrop.openstack.org_meetings_ops-5Fmeetups-5Fteam_2016_ops-5Fmeetups-5Fteam.2016-2D05-2D31-2D14.01.html&d=CwIGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=Izi115xT_K7kOrj3J8Dp44KcJDfJFyu8Tb_oYoroJng&s=WbHrH47xBUdxEDDBapu5uqcHGEur4HZBdORgXqXIPMY&e= 
>>
>>[4] 
>>https://urldefense.proofpoint.com/v2/url?u=http-3A__eavesdrop.openstack.org_meetings_ops-5Fmeetups-5Fteam_2016_ops-5Fmeetups-5Fteam.2016-2D05-2D31-2D14.01.log.html&d=CwIGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=Izi115xT_K7kOrj3J8Dp44KcJDfJFyu8Tb_oYoroJng&s=Jj57ejUOvlaWUnOmPq4VJd_dD3LOHLe7dIccNV7Rj7w&e= 
>>
>>_______________________________________________
>>OpenStack-operators mailing list
>>OpenStack-operators at lists.openstack.org
>>https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=CwIGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=Izi115xT_K7kOrj3J8Dp44KcJDfJFyu8Tb_oYoroJng&s=mBAjocP2sK04R3nFaMwcM0fhbgj0v2UJ7MHeupOck3U&e= 
>
>
>_______________________________________________
>OpenStack-operators mailing list
>OpenStack-operators at lists.openstack.org
>https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=CwIGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=Izi115xT_K7kOrj3J8Dp44KcJDfJFyu8Tb_oYoroJng&s=mBAjocP2sK04R3nFaMwcM0fhbgj0v2UJ7MHeupOck3U&e=