Open Stack

Awesome progress folks! So glad to see this well defined!
I always wanted to have a “safe” environment for these discussions.

Edgar

From: Chris Morgan <mihalis68 at gmail.com>
Date: Tuesday, May 17, 2016 at 9:34 AM
To: Matt Jarvis <matt.jarvis at datacentred.co.uk>
Cc: OpenStack Operators <openstack-operators at lists.openstack.org>
Subject: Re: [Openstack-operators] Updated definition of 'users'

The openstack operators meetings have a preference for 'users'
vs. 'vendors' since the vendors have every opportunity to get their
message across at the Summit in the vendor sessions, the marketplace
etc. Meanwhile, operators need a venue to share frank, unfettered,
possibly highly critical info about products and core openstack
components.

For the purposes of getting the meet ups organised then, the following
definition is proposed:

Updated Definition:

All attendees at an OpenStack operators mid-cycle meetup ('the
meetup') should be willing and able to discuss issues arising from
operating OpenStack cloud at some kind of scale, including
ideally having direct experience of OpenStack cloud operation
or expectation of that in future. Representatives from organisations
having both a vendor and a user role in the OpenStack community should
wear their user hat for the purposes of the meetup. Attendance by
those fitting these guidelines is highly encouraged.

On Tue, May 17, 2016 at 12:31 PM, Chris Morgan <mihalis68 at gmail.com<mailto:mihalis68 at gmail.com>> wrote:
Sorry for spamming the list. It appeared that I wasn't getting through so I tried again! Oops...

On Tue, May 17, 2016 at 12:30 PM, Matt Jarvis <matt.jarvis at datacentred.co.uk<mailto:matt.jarvis at datacentred.co.uk>> wrote:
We've noticed that as well, is everyone getting strange bounces from openstack-private ? Any list admins lurking here ?

On 17 May 2016 at 17:20, Chris Morgan <mihalis68 at gmail.com<mailto:mihalis68 at gmail.com>> wrote:
very good point. Currently a bit flustered by apparent bounces however. Will fix this though

On Tue, May 17, 2016 at 12:19 PM, Matt Jarvis <matt.jarvis at datacentred.co.uk<mailto:matt.jarvis at datacentred.co.uk>> wrote:
Hi Chris

Good round up and a good start on the definition. Don't forget the public cloud operators though, it's not all about private cloud ;)

On 17 May 2016 at 16:51, Chris Morgan <mihalis68 at gmail.com<mailto:mihalis68 at gmail.com>> wrote:
I'm new to this, but here goes:

Meeting held on IRC today at 14:00 UTC to jumpstart a new process for
arranging OpenStack operators mid-cycle meetups.

Nice minutes from Tom here
http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-05-17-14.00.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__eavesdrop.openstack.org_meetings_ops-5Fmeetups-5Fteam_2016_ops-5Fmeetups-5Fteam.2016-2D05-2D17-2D14.00.html&d=CwMFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lwZuG4NOftZbxYYQJvUA5UIXmDlS3ReVflxt7Ua88mk&s=Vpa6pdUgbko19uN8L5iKXp3B8b_emZNoqQlINOIbwyI&e=>

etherpad here : https://etherpad.openstack.org/p/ops-meetups-team<https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_ops-2Dmeetups-2Dteam&d=CwMFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lwZuG4NOftZbxYYQJvUA5UIXmDlS3ReVflxt7Ua88mk&s=L6-re0FOo_x3xEKIyWgCnhaAfTYZnUrg24cUzv0CJnw&e=>

In short there was consensus behind the mailing list locking in a
region and approximate time slot for each meetup and then making an
open call for meeting hosts/"underwriters". The region would be one of
: north america, europe or APAC in such a way as to oppose the region
of the following OpenStack summit. There is also desire to cap numbers
and somehow encourage operators/users and discourage vendors from
attending without getting to the level of having to vet
individuals. To that end I volunteered to propose a definition of
users, and so here goes:

------

The openstack operators meetings have a preference for 'users'
vs. 'vendors' since the vendors have every opportunity to get their
message across at the Summit in the vendor sessions, the marketplace
etc. Meanwhile, operators need a venue to share frank, unfettered,
possibly highly critical info about products and core openstack
components.

For the purposes of getting the meet ups organised then, the following
definition is proposed:

Definition:

All attendees at an OpenStack operators mid-cycle meetup ('the
meetup') should be willing and able to discuss issues arising from
operating OpenStack for private cloud at some kind of scale, including
ideally having direct experience of OpenStack private cloud operation
or expectation of that in future. Representatives from organisations
having both a vendor and a user role in the OpenStack community should
wear their user hat for the purposes of the meetup. Attendance by
those fitting these guidelines is highly encouraged.


--
Chris Morgan <mihalis68 at gmail.com<mailto:mihalis68 at gmail.com>>

_______________________________________________
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<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=CwMFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lwZuG4NOftZbxYYQJvUA5UIXmDlS3ReVflxt7Ua88mk&s=CfkGWk6R9b1M5OrGMfoMxfbEhnnSpNLIY38WIIuXmqo&e=>


DataCentred Limited registered in England and Wales no. 05611763



--
Chris Morgan <mihalis68 at gmail.com<mailto:mihalis68 at gmail.com>>


DataCentred Limited registered in England and Wales no. 05611763



--
Chris Morgan <mihalis68 at gmail.com<mailto:mihalis68 at gmail.com>>



--
Chris Morgan <mihalis68 at gmail.com<mailto:mihalis68 at gmail.com>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160519/30144de5/attachment.html>