[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Chefs? Salters? Others?

> On Nov 19, 2014, at 03:56, Ewoud Kohl van Wijngaarden <ewoud+openshift kohlvanwijngaarden nl> wrote:
> I'd agree with this. People are going to have existing infrastructures,
> knowledge and training. To get maximum adoption it is good to support
> multiple configuration management solutions.


> What can help with that is reducing the amount of hacks needed. For
> example, in the current puppet module the assets are compiled using bundler
> which I'd consider a problem that could be solved in packaging. That
> would reduce the burden on maintaining multiple installation methods
> (and for simplicity I consider the manual another installation method).
> Having a reliable yum install is a good thing to have anyway :)

As I mentioned to Charles, the packaging and delivery of Origin M5 will be very different and should be vastly simplified in comparison to what we do now for Origin M4.

> On Tue, Nov 18, 2014 at 09:28:29AM -0500, Charles Simpson wrote:
>>> From my perspective, OpenShift is only one part of our infrastructure so
>> moving part of it from Puppet over to Ansible is probably not going to
>> happen. We're going to have to continue to maintain Puppet module(s) - it
>> would be nice to have somewhere public that we could continue to share our
>> code with. If it's not part of OpenShift "officially" (under the openshift
>> GitHub group), we will mostly likely end up writing our own private modules
>> since I can't argue that the public ones are "upstream" or "suggested by
>> the vendor".
>> -- Charles
>> On Mon, Nov 17, 2014 at 12:09 PM, N. Harrison Ripps <nhr redhat com> wrote:
>>> Hey Judd--
>>>> On Nov 17, 2014, at 11:38, Judd Maltin <judd newgoliath com> wrote:
>>>> Hey Folks,
>>>> I was thinking of writing a chef cookbook for Origin v5.  Anyone want to
>>> collaborate out there, or is all the strength really behind puppet?  Other
>>> config mgmnt tools also welcome!
>>> Thanks for chiming in. Your timing is exceptional!
>>> As it happens, I am really interested in having Origin M5 use the same
>>> Ansible-based deployment tools that our ops team will be using for
>>> OpenShift Online. I see two main advantages:
>>> 1. Our community gets to collaborate with the OpenShift ops team. Given
>>> that OpenShift Online is currently hosting two-million-plus applications, I
>>> feel like this is a huge opportunity for us to leverage their expertise.
>>> 2. Rather than focusing our efforts on numerous different tools, if we all
>>> get involved with this project, then we can focus our efforts on making it
>>> the most complete solution it can be.
>>> I don't want to dissuade you from doing similar work in Chef or Puppet.
>>> That said, my vision for the new version of oo-install that will accompany
>>> Origin M5 is one that uses this Ansible playbook:
>>> https://github.com/openshift/openshift-online-ansible
>>> Thanks again for reaching out. Happy to chat with you more about this on
>>> the list or on IRC; I am user 'nhr' on FreeNode, #openshift-dev channel.
>>> --Harrison
>>>> Either way, what repos are folks doing their work in, so I might help
>>> out.
>>>> -judd
> _______________________________________________
> dev mailing list
> dev lists openshift redhat com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]