Open Stack

Personally I'd prefer OpenStack to follow some of K8s deployment patterns.
OpenStack has grown to an enormous size and it really painful to operate it
at scale. My suggestion would be to focus on improvement of consumption
models. 'Dockerization' of the release artifacts would be very useful. Also
current approach to configuration management relying on tens *conf files
distributed in hundreds directories is difficult to understand and maintain
in the longer term. Why don't move all config to etcd or MySQL? Do we need
all these *conf files? This is operator's pain point and leads
Puppet/Chef/Ansible/Saltstack folks spending hundreds of hours in a
suboptimal way.

On Thu, Feb 16, 2017 at 8:28 PM, Tim Bell <Tim.Bell at cern.ch> wrote:

>
> On 16 Feb 2017, at 19:42, Fox, Kevin M <Kevin.Fox at pnnl.gov> wrote:
>
> +1. The assumption was market forces will cause the best OpenStack
> deployment tools to win. But the sad reality is, market forces are causing
> people to look for non OpenStack solutions instead as the pain is still too
> high.
>
> While k8s has a few different deployment tools currently, they are focused
> on getting the small bit of underlying plumbing deployed. Then you use the
> common k8s itself to deploy the rest. Adding a dashboard, dns, ingress,
> sdn, other component is easy in that world.
>
> IMO, OpenStack needs to do something similar. Standardize a small core and
> get that easily deployable, then make it easy to deploy/upgrade the rest of
> the big tent projects on top of that, not next to it as currently is being
> done.
>
> Thanks,
> Kevin
>
>
> Unfortunately, the more operators and end users question the viability of
> a specific project, the less likely it is to be adopted.
>
> It is a very very difficult discussion with an end user to explain that
> function X is no longer available because the latest OpenStack upgrade had
> to be done for security/functional/stability reasons and this
> project/function is not available.
>
> The availability of a function may also have been one of the positives for
> the OpenStack selection so finding a release or two later that it is no
> longer in the portfolio is difficult.
>
> The deprecation policy really helps so we can give a good notice but this
> assumes an equivalent function is available. For example, the built in Nova
> EC2 to EC2 project was an example where we had enough notice to test the
> new solution in parallel and then move with minimum disruption.  Moving an
> entire data centre from Chef to Puppet or running a parallel toolchain, for
> example, has a high cost.
>
> Given the massive functionality increase in other clouds, It will be tough
> to limit the OpenStack offering to the small core. However, expanding with
> unsustainable projects is also not attractive.
>
> Tim
>
>
> ________________________________________
> From: Joshua Harlow [harlowja at fastmail.com]
> Sent: Thursday, February 16, 2017 10:24 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [chef] Making the Kitchen Great Again: A
> Retrospective on OpenStack & Chef
>
> Alex Schultz wrote:
>
> On Thu, Feb 16, 2017 at 9:12 AM, Ed Leafe<ed at leafe.com>  wrote:
>
> On Feb 16, 2017, at 10:07 AM, Doug Hellmann<doug at doughellmann.com>  wrote:
>
> When we signed off on the Big Tent changes we said competition
> between projects was desirable, and that deployers and contributors
> would make choices based on the work being done in those competing
> projects. Basically, the market would decide on the "optimal"
> solution. It's a hard message to hear, but that seems to be what
> is happening.
>
> This.
>
> We got much better at adding new things to OpenStack. We need to get
> better at letting go of old things.
>
> -- Ed Leafe
>
>
>
>
> I agree that the market will dictate what continues to survive, but if
> you're not careful you may be speeding up the decline as the end user
> (deployer/operator/cloud consumer) will switch completely to something
> else because it becomes to difficult to continue to consume via what
> used to be there and no longer is.  I thought the whole point was to
> not have vendor lock-in.  Honestly I think the focus is too much on
> the development and not enough on the consumption of the development
> output.  What are the point of all these features if no one can
> actually consume them.
>
>
> +1 to that.
>
> I've been in the boat of development and consumption of it for my
> *whole* journey in openstack land and I can say the product as a whole
> seems 'underbaked' with regards to the way people consume the
> development output. It seems we have focused on how to do the dev. stuff
> nicely and a nice process there, but sort of forgotten about all that
> being quite useless if no one can consume them (without going through
> much pain or paying a vendor).
>
> This has or has IMHO been a factor in why certain are companies (and the
> people they support) are exiting openstack and just going elsewhere.
>
> I personally don't believe fixing this is 'let the market forces' figure
> it out for us (what a slow & horrible way to let this play out; I'd
> almost rather go pull my fingernails out). I do believe it will require
> making opinionated decisions which we have all never been very good at.
>
> __________________________________________________________________________
> 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
>
> __________________________________________________________________________
> 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
>
>
>
> __________________________________________________________________________
> 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
>
>


-- 
Adam Heczko
Security Engineer @ Mirantis Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170216/dcc71679/attachment.html>