Open Stack

I used to be able to say "my OpenStack background is in Operations" but
that isn't strictly true anymore. I've now spent the majority of my time
doing what is considered 'developer' work. One thing is for certain though,
I have never stopped building OpenStack for what I see as the "hypothetical
OpenStack user".

The majority of these users in my experince are actually small-to-medium
businesses. While the large companies of the world certainly drive alot of
OpenStack, the users that I see are much smaller than that. Small 5-10 node
clusters. That is who I am building OpenStack for. That happens to also be
the group that I am in personally, as thats what I run at my house.

Most of my focus is on lowering the bar to use services to give these
small-to-medium businesses the least amount of work to do to gain access to
almost everything OpenStack has to offer with a very small operational
overhead for the team. My personal experince with this is currently it can
take a small team months to get a working openstack deployment, and then
simply maintaining that deployment will consume the rest of thier time.
This leads to OpenStack deployments that are years out of date on an island
that has no real upgrade path anymore and a general sense that "OpenStack
is bad" internally. I am building OpenStack for users so that this stops
happening.

Thanks,
SamYaple

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-Octo
> ber/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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171013/6897ff8e/attachment.html>