Open Stack

This is a great initiative.

Coming from Solum - a project that in on the fringes with regards to user
adoption [1][2], I feel that one of the things that
can help in increasing the adoption is deployment tooling available for
operators. If there is a standardized way to introduce
a project in their OpenStack setups, it is possible that operators would
try it.

Related to the work that would be produced by the group, what is the
thought around where would deployment artifacts live?
Within each individual project's repository? As part of a single deployment
project?

Also, are there any documents with information about constructing
deployment artifacts that we can refer to currently?

Regards,
Devdatta

[1] https://www.dropbox.com/s/jzkuimcc12w3iju/solum-interest-prod.png?dl=0

[2]
https://www.dropbox.com/s/nrlov1w4hn3cv6u/solum-interest-testing.png?dl=0



On Tue, Mar 14, 2017 at 3:31 PM, Emilien Macchi <emilien at redhat.com> wrote:

> OpenStack community has been a welcoming place for Deployment tools.
> They bring great value to OpenStack because most of them are used to
> deploy OpenStack in production, versus a development environment.
>
> Over the last few years, deployment tools project have been trying
> to solve similar challenges. Recently we've seen some desire to
> collaborate, work on common topics and resolve issues seen by all
> these tools.
>
> Some examples of collaboration:
>
> * OpenStack Ansible and Puppet OpenStack have been collaborating on
>   Continuous Integration scenarios but also on Nova upgrades orchestration.
> * TripleO and Kolla share the same tool for container builds.
> * TripleO and Fuel share the same Puppet OpenStack modules.
> * OpenStack and Kubernetes are interested in collaborating on configuration
>   management.
> * Most of tools want to collect OpenStack parameters for configuration
>   management in a common fashion.
> * [more]
>
> The big tent helped to make these projects part of OpenStack, but no
> official
> group was created to share common problems across tools until now.
>
> During the Atlanta Project Team Gathering in 2017 [1], most of current
> active
> deployment tools project team leaders met in a room and decided to start
> actual
> collaboration on different topics.
> This resolution is a first iteration of creating a new working group
> for Deployment Tools.
>
> The mission of the Deployment Working Group would be the following::
>
>   To collaborate on best practices for deploying and configuring OpenStack
>   in production environments.
>
>
> Note: in some cases, some challenges will be solved by adopting a
> technology
> or a tool. But sometimes, it won't happen because of the deployment tool
> background. This group would have to figure out how we can increase
> this adoption and converge to the same technologies eventually.
>
>
> For now, we'll use the wiki to document how we work together:
> https://wiki.openstack.org/wiki/Deployment
>
> The etherpad presented in [1] might be transformed in a Wiki page if
> needed but for now we expect people to update it.
>
> [1] https://etherpad.openstack.org/p/deployment-pike
>
>
> Let's make OpenStack deployments better and together ;-)
> Thanks,
> --
> Emilien Macchi
>
> __________________________________________________________________________
> 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/20170316/8537bdca/attachment.html>