Open Stack

No sads Rainya, you have superuser.openstack.org and an existing User
Committee that has already done a ton of work around that particular
OpenStack persona. :)

It's the next layer that the end-user effort is working on, and to me this
next frontier exploration explains why definitions are crucial for focusing
efforts.

Anne


On Fri, Aug 22, 2014 at 5:22 PM, Rainya Mosher <rainya.mosher at rackspace.com>
wrote:

>
> Sadness, but I understand. Thanks for the clarification!
>
> Rainya Mosher
> Dev Manager, PSST Release & Deploy
> 210.316.5065 (mobile)
> ----------------------------------------------
> Strategic • Activator • Connectedness • Individualization • Communication
>
> Hope is not a strategy, but it can help you get out of bed in the morning.
> ~RFM
>
>
>
>
> On 8/22/14, 4:55 PM, "Ruben Orduz" <ruben.orduz at RACKSPACE.COM> wrote:
>
> >Hi Rainya,
> >
> >For the sake of this definition, I’d say yes, your group would be
> >considered operators and outside our target audience.
> >
> >Best,
> >Ruben
> >
> >On Aug 22, 2014, at 5:42 PM, Rainya Mosher <rainya.mosher at RACKSPACE.COM>
> >wrote:
> >
> >>
> >> I like that a definition is being created and thank you for not wanting
> >>to
> >> leave out the operators and deployers. As a deployer of an OpenStack
> >> cloud, how does the definition "An OpenStack end user is anyone who
> >> interacts with and makes use of an OpenStack cloud via its public APIs²
> >> apply to the end users that deploy the OpenStack software itself? I ask
> >> because when my team and I do a public cloud deploy, we don¹t actually
> >> interact with the public api for any openstack service. It is all done
> >> through orchestration and ssh at the instance and host level.
> >>
> >> Is the idea that we would fall into the operator / maintainer category?
> >>Or
> >> is this function out of scope for this conversation? Cheers!
> >>
> >>
> >> Rainya Mosher
> >> Dev Manager, PSST Release & Deploy
> >> 210.316.5065 (mobile)
> >> ----------------------------------------------
> >> Strategic € Activator € Connectedness € Individualization €
> >>Communication
> >>
> >> I am an artist. This means I live in a perverse fantasy world with
> >> unrealistic expectations. Thank you for understanding.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> On 8/22/14, 3:31 PM, "Ruben Orduz" <ruben.orduz at RACKSPACE.COM> wrote:
> >>
> >>> I like this definition quite a bit, but I¹d tweak it to just this:
> >>>
> >>> "An OpenStack end user is anyone who interacts with and makes use of an
> >>> OpenStack cloud via its public APIs²
> >>>
> >>> My 2c
> >>>
> >>> Best,
> >>> Ruben
> >>>
> >>> On Aug 22, 2014, at 4:11 PM, Everett Toews
> >>><everett.toews at RACKSPACE.COM>
> >>> wrote:
> >>>
> >>>>
> >>>> Here's a straw man definition for end user to stimulate discussion.
> >>>>The
> >>>> public API is a good point of delineation.
> >>>>
> >>>>
> >>>> An OpenStack end user is anyone who interacts with an OpenStack cloud
> >>>> via its public APIs. That is, anyone who develops, deploys, or
> >>>>maintains
> >>>> software that uses an OpenStack cloud via any technology that
> >>>>interacts
> >>>> with its public APIs.
> >>>>
> >>>>
> >>>> Thoughts here?
> >>>>
> >>>
> >>>
> >>> _______________________________________________
> >>> User-committee mailing list
> >>> User-committee at lists.openstack.org
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
> >>
> >
>
> _______________________________________________
> User-committee mailing list
> User-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20140822/06ae4cdb/attachment-0001.html>