Open Stack

Hi,
thanks Nikhil.
My availability considering what was proposed:
2000 UTC - OK
1100 UTC - OK

On Tue, May 31, 2016 at 11:13 PM, Nikhil Komawar <nik.komawar at gmail.com>
wrote:

> Hey,
>
>
> Thanks for your interest.
>
> Sorry about the confusion. Please consider the same time for Thursday
> June 9th.
>
>
> Thur June 9th proposed time:
>
> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016&month=6&day=9&hour=11&min=0&sec=0&p1=881&p2=196&p3=47&p4=22&p5=157&p6=87&p7=24&p8=78&p9=283
>
>
> Alternate time proposal:
>
> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016&month=6&day=9&hour=23&min=0&sec=0&p1=881&p2=196&p3=47&p4=22&p5=157&p6=87&p7=24&p8=78&p9=283
>
>
> Overall time planner:
>
> http://www.timeanddate.com/worldclock/meetingtime.html?iso=20160609&p1=881&p2=196&p3=47&p4=22&p5=157&p6=87&p7=24&p8=78&p9=283
>
>
>
> It will really depend on who is strongly interested in the discussions.
> Scheduling with EMEA, Pacific time (US), Australian (esp. Eastern) is
> quite difficult. If there's strong interest from San Jose, we may have
> to settle for a rather awkward choice below:
>
>
>
> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016&month=6&day=9&hour=4&min=0&sec=0&p1=881&p2=196&p3=47&p4=22&p5=157&p6=87&p7=24&p8=78&p9=283
>
>
>
> A vote of +1, 0, -1 on these times would help long way.
>
>
> On 5/31/16 4:35 PM, Belmiro Moreira wrote:
> > Hi Nikhil,
> > I'm interested in this discussion.
> >
> > Initially you were proposing Thursday June 9th, 2016 at 2000UTC.
> > Are you suggesting to change also the date? Because in the new
> > timeanddate suggestions is 6/7 of June.
> >
> > Belmiro
> >
> > On Tue, May 31, 2016 at 6:13 PM, Nikhil Komawar <nik.komawar at gmail.com
> > <mailto:nik.komawar at gmail.com>> wrote:
> >
> >     Hey,
> >
> >
> >
> >
> >
> >     Thanks for the feedback. 0800UTC is 4am EDT for some of the US
> >     Glancers :-)
> >
> >
> >
> >
> >
> >     I request this time which may help the folks in Eastern and Central
> US
> >
> >     time.
> >
> >
> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016&month=6&day=7&hour=11&min=0&sec=0&p1=881&p2=196&p3=47&p4=22&p5=157&p6=87&p7=24&p8=78
> >
> >
> >
> >
> >
> >     If it still does not work, I may have to poll the folks in EMEA on
> how
> >
> >     strong their intentions are for joining this call.  Because
> >     another time
> >
> >     slot that works for folks in Australia & US might be too inconvenient
> >
> >     for those in EMEA:
> >
> >
> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016&month=6&day=6&hour=23&min=0&sec=0&p1=881&p2=196&p3=47&p4=22&p5=157&p6=87&p7=24&p8=78
> >
> >
> >
> >
> >
> >     Here's the map of cities that may be involved:
> >
> >
> http://www.timeanddate.com/worldclock/meetingtime.html?iso=20160607&p1=881&p2=196&p3=47&p4=22&p5=157&p7=87&p8=24&p9=78
> >
> >
> >
> >
> >
> >     Please let me know which ones are possible and we can try to work
> >     around
> >
> >     the times.
> >
> >
> >
> >
> >
> >     On 5/31/16 2:54 AM, Blair Bethwaite wrote:
> >
> >     > Hi Nikhil,
> >
> >     >
> >
> >     > 2000UTC might catch a few kiwis, but it's 6am everywhere on the
> east
> >
> >     > coast of Australia, and even earlier out west. 0800UTC, on the
> other
> >
> >     > hand, would be more sociable.
> >
> >     >
> >
> >     > On 26 May 2016 at 15:30, Nikhil Komawar <nik.komawar at gmail.com
> >     <mailto:nik.komawar at gmail.com>> wrote:
> >
> >     >> Thanks Sam. We purposefully chose that time to accommodate some
> >     of our
> >
> >     >> community members from the Pacific. I'm assuming it's just your
> >     case
> >
> >     >> that's not working out for that time? So, hopefully other
> >     Australian/NZ
> >
> >     >> friends can join.
> >
> >     >>
> >
> >     >>
> >
> >     >> On 5/26/16 12:59 AM, Sam Morrison wrote:
> >
> >     >>> I’m hoping some people from the Large Deployment Team can come
> >     along. It’s not a good time for me in Australia but hoping someone
> >     else can join in.
> >
> >     >>>
> >
> >     >>> Sam
> >
> >     >>>
> >
> >     >>>
> >
> >     >>>> On 26 May 2016, at 2:16 AM, Nikhil Komawar
> >     <nik.komawar at gmail.com <mailto:nik.komawar at gmail.com>> wrote:
> >
> >     >>>>
> >
> >     >>>> Hello,
> >
> >     >>>>
> >
> >     >>>>
> >
> >     >>>> Firstly, I would like to thank Fei Long for bringing up a few
> >     operator
> >
> >     >>>> centric issues to the Glance team. After chatting with him on
> >     IRC, we
> >
> >     >>>> realized that there may be more operators who would want to
> >     contribute
> >
> >     >>>> to the discussions to help us take some informed decisions.
> >
> >     >>>>
> >
> >     >>>>
> >
> >     >>>> So, I would like to call for a 2 hour sync for the Glance
> >     team along
> >
> >     >>>> with interested operators on Thursday June 9th, 2016 at 2000UTC.
> >
> >     >>>>
> >
> >     >>>>
> >
> >     >>>> If you are interested in participating please RSVP here [1], and
> >
> >     >>>> participate in the poll for the tool you'd prefer. I've also
> >     added a
> >
> >     >>>> section for Topics and provided a template to document the
> >     issues clearly.
> >
> >     >>>>
> >
> >     >>>>
> >
> >     >>>> Please be mindful of everyone's time and if you are proposing
> >     issue(s)
> >
> >     >>>> to be discussed, come prepared with well documented &
> >     referenced topic(s).
> >
> >     >>>>
> >
> >     >>>>
> >
> >     >>>> If you've feedback that you are not sure if appropriate for the
> >
> >     >>>> etherpad, you can reach me on irc (nick: nikhil).
> >
> >     >>>>
> >
> >     >>>>
> >
> >     >>>> [1]
> >     https://etherpad.openstack.org/p/newton-glance-and-ops-midcycle-sync
> >
> >     >>>>
> >
> >     >>>> --
> >
> >     >>>>
> >
> >     >>>> Thanks,
> >
> >     >>>> Nikhil Komawar
> >
> >     >>>> Newton PTL for OpenStack Glance
> >
> >     >>>>
> >
> >     >>>>
> >
> >     >>>>
> >
>  __________________________________________________________________________
> >
> >     >>>> OpenStack Development Mailing List (not for usage questions)
> >
> >     >>>> Unsubscribe:
> >     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> >     <
> http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
> >
> >     >>>>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >     >>>
> >
>  __________________________________________________________________________
> >
> >     >>> OpenStack Development Mailing List (not for usage questions)
> >
> >     >>> Unsubscribe:
> >     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> >     <
> http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
> >
> >     >>>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >     >> --
> >
> >     >>
> >
> >     >> Thanks,
> >
> >     >> Nikhil
> >
> >     >>
> >
> >     >>
> >
> >     >> _______________________________________________
> >
> >     >> OpenStack-operators mailing list
> >
> >     >> OpenStack-operators at lists.openstack.org
> >     <mailto:OpenStack-operators at lists.openstack.org>
> >
> >     >>
> >
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> >
> >     >
> >
> >     >
> >
> >
> >
> >     --
> >
> >
> >
> >     Thanks,
> >
> >     Nikhil
> >
> >
> >
> >
> >
> >
>  __________________________________________________________________________
> >
> >     OpenStack Development Mailing List (not for usage questions)
> >
> >     Unsubscribe:
> >     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> >     <
> http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
> >
> >     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> >
> >
> >
> >
> >
> __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
>
>
> --
>
> Thanks,
> Nikhil
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160601/e9148a4c/attachment.html>