[openstack-dev] [all][tc] TC Candidates: what does an OpenStack user look like?

Amrith Kumar amrith.kumar at gmail.com
Fri Oct 13 17:17:13 UTC 2017

Zane, thanks for the question.

Let me answer from the perspective of an OpenStack user (I work for
Verizon) and from a developer (both now, and in the past as part of
Tesora). OpenStack has multiple different users:

- Deployers:  People who deploy OpenStack and operate a cloud environment.

- Product Companies: This is a broad collective of things like
solutions providers, distribution providers; companies that don't
operate OpenStack but write and sell software that others can operate
in their OpenStack deployment, and are participants in the OpenStack

- End Users: People who consume OpenStack services (offered by
deployers). This is particularly important in the case of PaaS
projects (like Trove which I work on).

To me, the first (Deployers) and the third (End Users) are top of mind
because that is who we should be building for. I work in a team that
represents these two constituencies, we operate OpenStack and consume
the services of OpenStack.



On Thu, Oct 12, 2017 at 12:51 PM, Zane Bitter <zbitter at redhat.com> wrote:
> (Reminder: we are in the TC election campaigning period, and we all have the
> opportunity to question the candidates. The campaigning period ends on
> Saturday, so make with the questions.)
> In my head, I have a mental picture of who I'm building OpenStack for. When
> I'm making design decisions I try to think about how it will affect these
> hypothetical near-future users. By 'users' here I mean end-users, the actual
> consumers of OpenStack APIs. What will it enable them to do? What will they
> have to work around? I think we probably all do this, at least
> subconsciously. (Free tip: try doing it consciously.)
> So my question to the TC candidates (and incumbent TC members, or anyone
> else, if they want to answer) is: what does the hypothetical OpenStack user
> that is top-of-mind in your head look like? Who are _you_ building OpenStack
> for?
> There's a description of mine in this email, as an example:
> http://lists.openstack.org/pipermail/openstack-dev/2017-October/123312.html
> To be clear, for me at least there's only one wrong answer ("person who
> needs somewhere to run their IRC bouncer"). What's important in my opinion
> is that we have a bunch of people with *different* answers on the TC,
> because I think that will lead to better discussion and hopefully better
> decisions.
> Discuss.
> cheers,
> Zane.
> __________________________________________________________________________
> 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

More information about the OpenStack-dev mailing list