Re: [ansible-project] Version dependency management
Thanks, Dick. On Friday, January 27, 2017 at 11:23:10 AM UTC-5, Dick Davies wrote: > > Hi Adam > > I'd put the servers into groups, and then use group_vars to set > specific versions. > > On 27 January 2017 at 15:39, Adam Shantz > > wrote: > > Hi all - > > > > We're using Ansible, but haven't gotten super advanced. I have a > challenge > > where I'm doing rolling upgrades across thousands of systems. Due to > > business reasons (i.e. different groups owning different systems, > > applications, and parts of the infrastructure), I can't schedule a mass > > deployment of the latest & greatest software. > > > > I envision we'll get there some day, but in the meantime, I need a way > of > > saying which systems get which versions of software, while also tracking > > which systems have which versions. > > > > For example, if in a (de-normalized) database, it would be something > like: > > > > System | Application Name | Version | Date deployed > > host1| Adam's app | 1.0 | 1/5/2017 > > host1| John's app| 1.0 | 1/5/2017 > > host2| Adam's app | 1.3 | 1/20/2017 > > > > > > Has anyone had to do something like this? If so, can you share your > > experiences, and maybe any management software that has made this easier > for > > you to integrate with Ansible? > > > > Thanks in advance. > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "Ansible Project" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to ansible-proje...@googlegroups.com . > > To post to this group, send email to ansible...@googlegroups.com > . > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/ansible-project/82f50366-f7d4-4f51-9111-093063189f16%40googlegroups.com. > > > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/2bbcc528-d66b-42e7-ae18-e2ab866a00f8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ansible-project] Version dependency management
Hi Adam I'd put the servers into groups, and then use group_vars to set specific versions. On 27 January 2017 at 15:39, Adam Shantz wrote: > Hi all - > > We're using Ansible, but haven't gotten super advanced. I have a challenge > where I'm doing rolling upgrades across thousands of systems. Due to > business reasons (i.e. different groups owning different systems, > applications, and parts of the infrastructure), I can't schedule a mass > deployment of the latest & greatest software. > > I envision we'll get there some day, but in the meantime, I need a way of > saying which systems get which versions of software, while also tracking > which systems have which versions. > > For example, if in a (de-normalized) database, it would be something like: > > System | Application Name | Version | Date deployed > host1| Adam's app | 1.0 | 1/5/2017 > host1| John's app| 1.0 | 1/5/2017 > host2| Adam's app | 1.3 | 1/20/2017 > > > Has anyone had to do something like this? If so, can you share your > experiences, and maybe any management software that has made this easier for > you to integrate with Ansible? > > Thanks in advance. > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ansible-project+unsubscr...@googlegroups.com. > To post to this group, send email to ansible-project@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/82f50366-f7d4-4f51-9111-093063189f16%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAK5eLPT2Re5gJCtq%2Bqwh_BFJaceZ%3DTm2%3DKXcz5erNVxPgTktVA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[ansible-project] Version dependency management
Hi all - We're using Ansible, but haven't gotten super advanced. I have a challenge where I'm doing rolling upgrades across thousands of systems. Due to business reasons (i.e. different groups owning different systems, applications, and parts of the infrastructure), I can't schedule a mass deployment of the latest & greatest software. I envision we'll get there some day, but in the meantime, I need a way of saying which systems get which versions of software, while also tracking which systems have which versions. For example, if in a (de-normalized) database, it would be something like: System | Application Name | Version | Date deployed host1| Adam's app | 1.0 | 1/5/2017 host1| John's app| 1.0 | 1/5/2017 host2| Adam's app | 1.3 | 1/20/2017 Has anyone had to do something like this? If so, can you share your experiences, and maybe any management software that has made this easier for you to integrate with Ansible? Thanks in advance. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/82f50366-f7d4-4f51-9111-093063189f16%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
