Open Stack

On 12/10/17 17:51, Zane Bitter 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.
> 

Personally I do not think there is a single "user" persona we can use.

We have users that vary from "I used to use ESXi to get a server, now I
go to https://cloud.example.com/horizon and click "Create" to "I am
deploying a Kubernetes cluster, and I need a base IaaS for network,
compute and storage."

Because of how I have spent most of my time in OpenStack, I think I tend
to be biased towards "integrators" - people writing software that needs
to be generic, to work on a lot of different OpenStack clouds (e.g.
Kubernetes OpenStack Cloud Provider, installers for products that run in
different versions of OpenStack (in cloud) or tools like Terraform /
Ansible that interact with the APIs).

There is no one size / shape fits all OpenStack topology, and that
flexibility is why I can have OpenStack run reliably on a couple of
workstations, and others can scale it to hundreds of thousands of cores.
This unfortunately makes life difficult for people who try to be
generic, or write tools that manage "OpenStack" as a thing, instead of a
style / distro / implementation of OpenStack.


> __________________________________________________________________________
> 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171013/873b65df/attachment.sig>