-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Top Posting to stay with the flow...
I am largely +1 on the plan as well, however ansible-container itself is very immature at this point and we should do a bit of due diligence around the space to quantify challenges and how they map to the user stories side of things. A huge +1 to aligning with their roadmaps and ensuring that we get upstream + downstream buy in for the feature space we are going to work on from the devtools side. regards, On 08/08/16 14:54, Mitchell Harpur wrote: > +1 for Ansible. Its my opinion that it should be the tool to use > accross the board. > > Imaging we could just use ansible and VM's where neccesary (win + > mac) to simplify our provisioning development,deployment,promotion > experience (remove the need for vagrant) > > Mitch > > > ----- Original Message ----- From: "Dusty Mabe" > <[email protected]> To: [email protected], > [email protected] Sent: Friday, August 5, 2016 8:21:04 AM > Subject: [Devtools] Future Focus of Tools Deploy Team: Ansible > Container & Kompose > > > Hey Everyone, > > Last week the Devtools Deploy team had a meeting to discuss our > goals around Ansible and Atomic App, based on the requirements > coming from our PM and engineering teams. We are concerned that we > have too many tools in this space - in particular we think that we > end up spending a lot of time explaining the differences between > these tools, rather than working on solving real use cases. > > We think that Ansible itself has an interesting end-to-end story > for people looking to deploy applications, and we think that > working with Ansible, and in particular the ansible-container > project could solve a number of the use cases we want to look at. > As one of our first goals we want to bring some of the deployment > support we have in Atomic App to ansible container - we intend to > make PRs based on our experience. We are hoping to become tightly > integrated with their team and share the same roadmap when it comes > to that tool. > > We also want to get more involved in existing upstream communities > that are centered around Kubernetes/OpenShift. We have already > started to get involved with the Kompose project [1] and we want to > evaluate Helm [2] packaging and how it relates to Kompose and see > where the good things about Nulecule can be brought to the table > there. > > As a result of focusing on Ansible and Kompose/Helm for the next 6 > months, it does mean we will slow down our work on Atomic App. One > thing we do want to do is merge the Nulecule and Atomic App > repositories so that it is less confusing to approach that project. > We'll be merging the Nulecule repository into the Atomic App > repository and Nulecule will become an implementation detail for > Atomic App. After the merge we'll let it rest for a while and > re-evaluate it in some time. > > Questions/Concerns? > > Dusty > > [1] - https://github.com/skippbox/kompose [2] - > https://github.com/kubernetes/helm > > _______________________________________________ Devtools mailing > list [email protected] > https://www.redhat.com/mailman/listinfo/devtools > > _______________________________________________ Devtools mailing > list [email protected] > https://www.redhat.com/mailman/listinfo/devtools > - -- Karanbir Singh, Project Lead, The CentOS Project, London, UK Red Hat Ext. 8274455 | DID: 0044 207 009 4455 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJXqJJ6AAoJEI3Oi2Mx7xbteMoH/2emVmpBympdly7nuQLAJ8w4 aWC8SLS1OJl6yNB3l4eoHQNKEb22vHkuCUBW6LTdHPmv70JpzYm3ZwilYJ78mNc8 ZTWN3PHT/+d7CDOajpv5kh9aSFLukm2KVXTk4+3Ck8xBRIZGvK33bSXHSO41c9SK n4OouRabdP1t+phf9z46R5O32x1nhdrDS6G2xZnicGZZ3oSwVWplf/vYUMmT1QXY pcOHL3haN0AJsOJaqqFtKIKtvGS4QgxU+W29fLe3Et9g9alWqup4v6Jwwv8BSnE+ qZYicPOd+mv2kEbDlRJVW+gy6cO6hMzSMVvozBqL8Ks6Q5z/MuYc9LebaI6WJt8= =LROd -----END PGP SIGNATURE----- _______________________________________________ Devtools mailing list [email protected] https://www.redhat.com/mailman/listinfo/devtools
