Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Existing Tower automation in 'infra-ansible' #1

Open
oybed opened this issue Aug 24, 2018 · 7 comments
Open

Existing Tower automation in 'infra-ansible' #1

oybed opened this issue Aug 24, 2018 · 7 comments

Comments

@oybed
Copy link

oybed commented Aug 24, 2018

For awareness, we have a lot of Tower Automation already in the infra-ansible CoP repo - both roles and playbooks.

There probably is an opportunity for collaboration to avoid dup effort.

@oybed
Copy link
Author

oybed commented Oct 2, 2018

@ericzolf tagging you here in case you didn't see this issue.

@ericzolf
Copy link
Collaborator

ericzolf commented Oct 4, 2018

Yes, sorry for getting mute, it's a fair comment and I have been thinking about it. My first idea would be to rename the repo to automate-redhat, tower just being a sub-directory of it, and put a focus on fostering best practices of automating Red Hat own's products by:

  1. linking to other repositories with automation of Red Hat products (there are many out there)
  2. hosting small pieces of automation and documentation which don't justify an own repo

Does it sound like a plan?

@aoyawale
Copy link

aoyawale commented Oct 9, 2018

probably better we discuss this more in a cop meeting because this is happening everywhere. We have a lot of content that is similar, that can be integrated but, we have no middle ground or who exactly makes the final decision. We are going to have a lot of disagreements on how everything is written.

@oybed
Copy link
Author

oybed commented Oct 16, 2018

@ericzolf the combined repo for automation of many of the Red Hat related products is what infra-ansible already does. Take a look at the roles directory for a better understand of everything that's there. Feel free to contribute there as well.

However, I think what's more of an aim here is to "combine" multiple parallel efforts around the Tower Automation. I'll kick off an e-mail thread to discuss further, as I believe this could live under the Automation CoP - to @jlozadad 's point.

@aoyawale
Copy link

we should also take this into account redhat-cop/infra-ansible#275

@vvaldez
Copy link
Contributor

vvaldez commented Oct 23, 2018 via email

@ericzolf
Copy link
Collaborator

And we've got a few other links from different persons since we started this discussion, internal or external, so we need definitely a strategy on how to get a "best of" of all these and join forces to maintain it.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants