Managing a large amount of Ansible roles












0














We are working on converting our project to Ansible. Due to the scale of the project, we will need a large amount of roles (30+). Where we're running into problems is how to store and manage these roles. Things we have considered:



1) Github repo per role -> This is unrealistic. We don't want to manage 30+ git repositories simply for the purpose of maintaining our roles
2) Ansible Galaxy -> This would be valuable if we could have a local instance of Ansible Galaxy, but the central instance won't work
3) We can simply store the roles in a flat directory, however we lose the benefit of being able to version them in this case. There is also the matter of how to automatically push our ansible roles directories to the ansible controller host into the correct directory



Is there a solution I'm missing?






ansible ansible-role







share|improve this question






















  • Is there any issue having all the roles in a git repo? Is because you want to have a requirements.yml for those roles?
    – imjoseangel
    Nov 16 '18 at 5:49










  • Are the roles truly functionally separate? If not, then it may make sense to combine some of them into a few roles using tags or conditionals to manage execution.
    – Michael Gardner
    Nov 16 '18 at 12:13
















0














We are working on converting our project to Ansible. Due to the scale of the project, we will need a large amount of roles (30+). Where we're running into problems is how to store and manage these roles. Things we have considered:



1) Github repo per role -> This is unrealistic. We don't want to manage 30+ git repositories simply for the purpose of maintaining our roles
2) Ansible Galaxy -> This would be valuable if we could have a local instance of Ansible Galaxy, but the central instance won't work
3) We can simply store the roles in a flat directory, however we lose the benefit of being able to version them in this case. There is also the matter of how to automatically push our ansible roles directories to the ansible controller host into the correct directory



Is there a solution I'm missing?






ansible ansible-role







share|improve this question






















  • Is there any issue having all the roles in a git repo? Is because you want to have a requirements.yml for those roles?
    – imjoseangel
    Nov 16 '18 at 5:49










  • Are the roles truly functionally separate? If not, then it may make sense to combine some of them into a few roles using tags or conditionals to manage execution.
    – Michael Gardner
    Nov 16 '18 at 12:13














0












0








0







We are working on converting our project to Ansible. Due to the scale of the project, we will need a large amount of roles (30+). Where we're running into problems is how to store and manage these roles. Things we have considered:



1) Github repo per role -> This is unrealistic. We don't want to manage 30+ git repositories simply for the purpose of maintaining our roles
2) Ansible Galaxy -> This would be valuable if we could have a local instance of Ansible Galaxy, but the central instance won't work
3) We can simply store the roles in a flat directory, however we lose the benefit of being able to version them in this case. There is also the matter of how to automatically push our ansible roles directories to the ansible controller host into the correct directory



Is there a solution I'm missing?






ansible ansible-role







share|improve this question













We are working on converting our project to Ansible. Due to the scale of the project, we will need a large amount of roles (30+). Where we're running into problems is how to store and manage these roles. Things we have considered:



1) Github repo per role -> This is unrealistic. We don't want to manage 30+ git repositories simply for the purpose of maintaining our roles
2) Ansible Galaxy -> This would be valuable if we could have a local instance of Ansible Galaxy, but the central instance won't work
3) We can simply store the roles in a flat directory, however we lose the benefit of being able to version them in this case. There is also the matter of how to automatically push our ansible roles directories to the ansible controller host into the correct directory



Is there a solution I'm missing?






ansible ansible-role




ansible ansible-role






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 15 '18 at 17:04









pasquerspasquers

239217




239217












  • Is there any issue having all the roles in a git repo? Is because you want to have a requirements.yml for those roles?
    – imjoseangel
    Nov 16 '18 at 5:49










  • Are the roles truly functionally separate? If not, then it may make sense to combine some of them into a few roles using tags or conditionals to manage execution.
    – Michael Gardner
    Nov 16 '18 at 12:13


















  • Is there any issue having all the roles in a git repo? Is because you want to have a requirements.yml for those roles?
    – imjoseangel
    Nov 16 '18 at 5:49










  • Are the roles truly functionally separate? If not, then it may make sense to combine some of them into a few roles using tags or conditionals to manage execution.
    – Michael Gardner
    Nov 16 '18 at 12:13
















Is there any issue having all the roles in a git repo? Is because you want to have a requirements.yml for those roles?
– imjoseangel
Nov 16 '18 at 5:49




Is there any issue having all the roles in a git repo? Is because you want to have a requirements.yml for those roles?
– imjoseangel
Nov 16 '18 at 5:49












Are the roles truly functionally separate? If not, then it may make sense to combine some of them into a few roles using tags or conditionals to manage execution.
– Michael Gardner
Nov 16 '18 at 12:13




Are the roles truly functionally separate? If not, then it may make sense to combine some of them into a few roles using tags or conditionals to manage execution.
– Michael Gardner
Nov 16 '18 at 12:13












1 Answer
1






active

oldest

votes


















2














I would suggest keeping the roles in a single git repo.



For the automatic push to the ansible controller, you could either create a standalone playbook that uses the git module to retrieve the appropriate version of the roles. This could then be run on a regular basis (or scheduled via cron).



Alternatively, you could add the git retrieval to your existing playbooks, and then it would check/update the roles prior to executing them.






share|improve this answer

















  • 1




    I concur. I had close to 100 different Ansible roles and around a dozen playbooks using those roles for one project I worked on. All of them were stored in a single repo. Worked just fine. I didn't automatically pick up the new roles when running the playbooks. I made sure the directory was up to date manually, but it was just me and one other. So, we didn't have to worry a lot about not knowing when there were updates. :)
    – Lewis M
    Nov 16 '18 at 12:34










  • One followup to this, is how do you manage individual versions of the roles? For example certain roles require significantly different configuration based off of the version (Tomcat is a good example). So to install a specific role version we need to be able to reference it by version
    – pasquers
    Nov 16 '18 at 14:49










  • @pasquers So typically I use Tagging, and/or Variables that will retrieve the specific configuration values that I want. Then you can have multiple variable files under /var or /default that get referenced based on Tags or Version settings. Using jinja templates would be another possiblity.
    – Michael Gardner
    Nov 20 '18 at 13:50











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53324561%2fmanaging-a-large-amount-of-ansible-roles%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









2














I would suggest keeping the roles in a single git repo.



For the automatic push to the ansible controller, you could either create a standalone playbook that uses the git module to retrieve the appropriate version of the roles. This could then be run on a regular basis (or scheduled via cron).



Alternatively, you could add the git retrieval to your existing playbooks, and then it would check/update the roles prior to executing them.






share|improve this answer

















  • 1




    I concur. I had close to 100 different Ansible roles and around a dozen playbooks using those roles for one project I worked on. All of them were stored in a single repo. Worked just fine. I didn't automatically pick up the new roles when running the playbooks. I made sure the directory was up to date manually, but it was just me and one other. So, we didn't have to worry a lot about not knowing when there were updates. :)
    – Lewis M
    Nov 16 '18 at 12:34










  • One followup to this, is how do you manage individual versions of the roles? For example certain roles require significantly different configuration based off of the version (Tomcat is a good example). So to install a specific role version we need to be able to reference it by version
    – pasquers
    Nov 16 '18 at 14:49










  • @pasquers So typically I use Tagging, and/or Variables that will retrieve the specific configuration values that I want. Then you can have multiple variable files under /var or /default that get referenced based on Tags or Version settings. Using jinja templates would be another possiblity.
    – Michael Gardner
    Nov 20 '18 at 13:50
















2














I would suggest keeping the roles in a single git repo.



For the automatic push to the ansible controller, you could either create a standalone playbook that uses the git module to retrieve the appropriate version of the roles. This could then be run on a regular basis (or scheduled via cron).



Alternatively, you could add the git retrieval to your existing playbooks, and then it would check/update the roles prior to executing them.






share|improve this answer

















  • 1




    I concur. I had close to 100 different Ansible roles and around a dozen playbooks using those roles for one project I worked on. All of them were stored in a single repo. Worked just fine. I didn't automatically pick up the new roles when running the playbooks. I made sure the directory was up to date manually, but it was just me and one other. So, we didn't have to worry a lot about not knowing when there were updates. :)
    – Lewis M
    Nov 16 '18 at 12:34










  • One followup to this, is how do you manage individual versions of the roles? For example certain roles require significantly different configuration based off of the version (Tomcat is a good example). So to install a specific role version we need to be able to reference it by version
    – pasquers
    Nov 16 '18 at 14:49










  • @pasquers So typically I use Tagging, and/or Variables that will retrieve the specific configuration values that I want. Then you can have multiple variable files under /var or /default that get referenced based on Tags or Version settings. Using jinja templates would be another possiblity.
    – Michael Gardner
    Nov 20 '18 at 13:50














2












2








2






I would suggest keeping the roles in a single git repo.



For the automatic push to the ansible controller, you could either create a standalone playbook that uses the git module to retrieve the appropriate version of the roles. This could then be run on a regular basis (or scheduled via cron).



Alternatively, you could add the git retrieval to your existing playbooks, and then it would check/update the roles prior to executing them.






share|improve this answer












I would suggest keeping the roles in a single git repo.



For the automatic push to the ansible controller, you could either create a standalone playbook that uses the git module to retrieve the appropriate version of the roles. This could then be run on a regular basis (or scheduled via cron).



Alternatively, you could add the git retrieval to your existing playbooks, and then it would check/update the roles prior to executing them.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 16 '18 at 12:25









Michael GardnerMichael Gardner

5,08951829




5,08951829








  • 1




    I concur. I had close to 100 different Ansible roles and around a dozen playbooks using those roles for one project I worked on. All of them were stored in a single repo. Worked just fine. I didn't automatically pick up the new roles when running the playbooks. I made sure the directory was up to date manually, but it was just me and one other. So, we didn't have to worry a lot about not knowing when there were updates. :)
    – Lewis M
    Nov 16 '18 at 12:34










  • One followup to this, is how do you manage individual versions of the roles? For example certain roles require significantly different configuration based off of the version (Tomcat is a good example). So to install a specific role version we need to be able to reference it by version
    – pasquers
    Nov 16 '18 at 14:49










  • @pasquers So typically I use Tagging, and/or Variables that will retrieve the specific configuration values that I want. Then you can have multiple variable files under /var or /default that get referenced based on Tags or Version settings. Using jinja templates would be another possiblity.
    – Michael Gardner
    Nov 20 '18 at 13:50














  • 1




    I concur. I had close to 100 different Ansible roles and around a dozen playbooks using those roles for one project I worked on. All of them were stored in a single repo. Worked just fine. I didn't automatically pick up the new roles when running the playbooks. I made sure the directory was up to date manually, but it was just me and one other. So, we didn't have to worry a lot about not knowing when there were updates. :)
    – Lewis M
    Nov 16 '18 at 12:34










  • One followup to this, is how do you manage individual versions of the roles? For example certain roles require significantly different configuration based off of the version (Tomcat is a good example). So to install a specific role version we need to be able to reference it by version
    – pasquers
    Nov 16 '18 at 14:49










  • @pasquers So typically I use Tagging, and/or Variables that will retrieve the specific configuration values that I want. Then you can have multiple variable files under /var or /default that get referenced based on Tags or Version settings. Using jinja templates would be another possiblity.
    – Michael Gardner
    Nov 20 '18 at 13:50








1




1




I concur. I had close to 100 different Ansible roles and around a dozen playbooks using those roles for one project I worked on. All of them were stored in a single repo. Worked just fine. I didn't automatically pick up the new roles when running the playbooks. I made sure the directory was up to date manually, but it was just me and one other. So, we didn't have to worry a lot about not knowing when there were updates. :)
– Lewis M
Nov 16 '18 at 12:34




I concur. I had close to 100 different Ansible roles and around a dozen playbooks using those roles for one project I worked on. All of them were stored in a single repo. Worked just fine. I didn't automatically pick up the new roles when running the playbooks. I made sure the directory was up to date manually, but it was just me and one other. So, we didn't have to worry a lot about not knowing when there were updates. :)
– Lewis M
Nov 16 '18 at 12:34












One followup to this, is how do you manage individual versions of the roles? For example certain roles require significantly different configuration based off of the version (Tomcat is a good example). So to install a specific role version we need to be able to reference it by version
– pasquers
Nov 16 '18 at 14:49




One followup to this, is how do you manage individual versions of the roles? For example certain roles require significantly different configuration based off of the version (Tomcat is a good example). So to install a specific role version we need to be able to reference it by version
– pasquers
Nov 16 '18 at 14:49












@pasquers So typically I use Tagging, and/or Variables that will retrieve the specific configuration values that I want. Then you can have multiple variable files under /var or /default that get referenced based on Tags or Version settings. Using jinja templates would be another possiblity.
– Michael Gardner
Nov 20 '18 at 13:50




@pasquers So typically I use Tagging, and/or Variables that will retrieve the specific configuration values that I want. Then you can have multiple variable files under /var or /default that get referenced based on Tags or Version settings. Using jinja templates would be another possiblity.
– Michael Gardner
Nov 20 '18 at 13:50


















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53324561%2fmanaging-a-large-amount-of-ansible-roles%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Guess what letter conforming each word

Image
6 $begingroup$ This is an entry in the Fortnightly Topic Challenge #41: Short and Sweet. 1 letter only could be mean anything . With an additional letter in front , could be used as medicine component and something you definitely learn or at least heard once. Add another letter in front , you would possibly hear that many times . Add an additional letter in front , you would found an independent country . With an additional letter, in the end , you would found something related to apple . Add another letter in the end , you would found something bad . Hint: Each letter is unique . word knowledge letters chemistry share | improve this question ...
Read more

Port of Spain

Image
For ports in the country of Spain, see List of ports in Spain. City in City of Port of Spain, Trinidad and Tobago Port of Spain City City of Port of Spain Top to bottom (left to right): Skyline of Port of Spain from Gulf of Paria; National Academy for the Performing Arts, Independence Square, Eric Williams Plaza; MovieTowne, Port of Port of Spain Motto(s):  "We Gather Strength As We Go Along" Port of Spain Coordinates: 10°40′N 61°31′W  /  10.667°N 61.517°W  / 10.667; -61.517 Coordinates: 10°40′N 61°31′W  /  10.667°N 61.517°W  / 10.667; -61.517 Country   Trinidad and Tobago Jurisdiction City of Port of Spain Settled 1560 Incorporated (town) 1853 Incorporated (city) 1914 Government  • Mayor Joel Martinez  • Governing body City Corporation Area [1]  • City 12 km 2 (5 sq mi) Elevation [2] 66 m (217 ft) Population (2011) [1]  • City 37,074  • Rank 3rd  • Density 3,090/km 2 (8,000/sq mi)...
Read more

Run scheduled task as local user group (not BUILTIN)

Image
0 I am trying to run a scheduled task with User Group (not a single user). This is working fine when I in the field "when running a task, use the following user account:" insert BUILTIN User Group (for example: Administrators or Users). But when I try it with the created Local User Group (example: TestGroup) it is not working. The Users in the TestGroup are the same as in the Administrators group. What could be the problem? Are there some restrictions to the Created User Group compared to BUILTINUsers? scheduled-tasks taskscheduler windowstaskschedule share | improve this question asked Nov 15 '18 at 15:36 Far...
Read more