00:07:59 #startmeeting Ansible Azure Working Group 00:07:59 Meeting started Thu Sep 13 00:07:59 2018 UTC. 00:07:59 This meeting is logged and archived in a public location. 00:07:59 The chair is jborean93. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:07:59 Useful Commands: #action #agreed #halp #info #idea #link #topic. 00:07:59 The meeting name has been set to 'ansible_azure_working_group' 00:08:15 #topic tags 00:08:26 #charp Kylie_ yungez zikalino82 00:08:34 * jborean93 sigs 00:08:38 #chair Kylie_ yungez zikalino82 00:08:38 Current chairs: Kylie_ jborean93 yungez zikalino82 00:08:48 god I'm horrible at typing today 00:09:21 We got one question about tags. You could tag VMs with different tags. For example you tag 30 VMs as tag1, 30 VMs as tag2, and 30 VMs as tag3. 00:10:21 It is ok to execute tasks for different tags. But how to assign one task to both tag1 and tag2 VMs? 00:10:58 so these are Azure tags or Ansible tags? 00:11:51 Azure tags (dynamic inventory). 00:12:01 Let me attach original question from customer here. 00:12:06 https://www.irccloud.com/pastebin/t93qdo3O/ 00:12:51 Wait a min. I don't think this is Azure specific. I think this is a common Ansible question but we don't have experience on it. 00:12:57 is there more to it, that seems to be a statement? 00:14:33 Above way does not work. 00:15:19 I'm not really seeing the question sorry, it does sound more workflow specific than an Azure issue 00:16:34 so these are not tags, these are inventory groups...... 00:16:37 The customer wants to tag host 1 w/ tag0 and tag1, host 2 w/ tag0 and tag2, host 3 w/ tag0 and tag2. And run "set up" for all tag0 machines and install ngnix on tag1, install JVM on tag2. This the workflow she expects. But she tried and above workflow does not work. 00:17:13 or not? 00:17:39 sounds like when she creates the VM she creates the tags according to whatever criteria. THen you can use the dynamic inventory to run the next play based on the tag groups it creates 00:17:57 yep zikalino82 seems to be right 00:18:28 Yes. But it does not work. 00:18:49 Can one machine be defined into different groups? 00:19:00 in Ansible yes 00:19:21 what exactly doesn't work 00:19:49 for example, at my previous workplace we had servers in AWS, we created an Application and Environment tag 00:20:15 WHen running the play, we could limit or target specific plays to hosts in 1 or multiple groups 00:22:23 The customer defined above tags/groups, then used one playbook to run tasks and found out those tasks were not executed on those groups actually. 00:22:48 In theory, it should work. Right? 00:23:22 if they set it up right yes, considering it doesn't and we don't have concrete examples of their plays I would say they have implemented it incorrectly 00:23:58 kylie, let's look at inventory code then. will also check the new inventory 00:24:19 I see. Let me ask full playbooks for further analysis. 00:24:23 Thank you all. 00:24:36 I think all are preparing AnsibleFest. Jordan, will you be there? 00:24:46 yep, having the actual code they are working with helps to see what exactly they are doing and potentially a way to run it yourself and debug 00:24:51 no I won't be at AnsibleFest 00:25:09 good luck with the talks though 00:25:55 Thank you:). No more topic from me. 00:26:30 thank you:) 00:26:33 no topics from me 00:26:37 have a good day 00:26:42 byeby 00:26:44 byebye 00:26:57 #endmeeting