-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Break out internal roles in claw-playbook #743
Comments
@dannylamb You want that I should make repos in the Islandora-DevOps organization for each of these? Is there a naming structure to follow? |
Yeah, that'd be great. Riffing from claw-playbook I guess we're hyphenating instead of underscoring? I checked galaxy and there didn't seem to be a discernible convention. |
Okay as a note, to find out what platforms are available you can use this API Also what versions of each platform do we want to support and test with? For instance, the above link list 16 versions for Ubuntu. |
Also tags..."Islandora" or "CLAW" or "Islandora-CLAW"? |
Actually tags are a single alpha-numeric term, so for Fedora I'm going with
|
@whikloj We're targeting Ubuntu xenial and Centos 7. I'm assuming this is for advertising what they work on? |
OK, then we target |
Pardon that is |
All split out however I'm wondering if this is an ActiveMQ role that we could put some effort behind. Has some downloads, but is missing xenial support. We could fork it and if it works provide some PRs. I have made the a repo for activemq, so if they are non-responsive we won't have lost this work. Thoughts? Also, I like one of the conventions out there which is providing variables for major, minor and patch version number. Lastly, now I am going to start with some clean up as I found some variable bleed between roles. Perhaps I'll see if I can figure out how to write some tests and use that molecule thing @DiegoPino pointed out. |
Should probably make a PR to remove the broken out roles from claw-playbook, and to add them to requirements.yml so we pull in our own roles from galaxy. I guess making a release for each of them is probably a good idea too. That maybe could be another ticket, just wanted to add my 2c. |
@jonathangreen Don't they need to be in galaxy before we can pull them in? Just because I think @dannylamb will need to create the islandora user account to get the nice |
@whikloj They may just have tags wrong in ansible-galaxy. According to the repo's README it supports 16.04? Maybe we should just give it a try. I'll go make an account for islandora. |
molecule while interesting doesn't work out of the box on my Mac. It could be my docker setup. But I'm not sure. I was following this post which led me to start this branch which is a good start (if I do say so myself). However we will need to consider docker and something along the lines of (but hopefully way simpler than) this |
Whenever we are pulling the roles out, we need to make sure we sync them up first. There are probably other changes, but I wanted to make sure these two PR don't get lost: |
I think we can call this closed! |
In order to get them on galaxy and use them in more complicated multi-server setups, we need to break out our internal roles into their own github repositories in the Islandora-Devops organization.
Current list of roles:
The text was updated successfully, but these errors were encountered: