Define use of tags

[joshmoore]

See discussion under #14 (comment)

[manics]

If tags are at the level of tasks in roles (which in #14 would make sense) this needs to managed at the organisation level, since:

• If someone is running a playbook they shouldn't need to read the docs for all roles in the playbook to check what tags are used and their effect
• Tags need to be consistent in terms of what they do across all roles/tasks/playbooks/repos we use
• They become public and exposed to external users of our roles
• If we decide to incorporate roles/playbooks from other sources they'll need to be reviewed to ensure there are no conflicting tags

[joshmoore]

An aside I've mentioned in passing before:

• tags on role inclusion may be an easy first step here.

See:

• https://ansiblemaster.wordpress.com/2017/01/18/using-tags-for-each-role/

 roles:
    - { role: frontend1,
        tags: frontend1 }
    - { role: frontend2, 
        tags: frontend2 }

[kennethgillen]

Current tag set:

2018-04-16 16:48 LS27172:prod-playbooks kenny$ git grep tags | grep -Po '(?<=\btags\: )[^\s]+' | sort | uniq -c | sort -rn
  18 monitoring
  14 lvm
   2 backups
   1 redirect
   1 nginxconf
   1 jekyll

[kennethgillen]

Would @openmicroscopy/devops object to [my introducing a new] tag: network?

I've added it to --skip-tags on my local test deployment of web-proxy, which effectively makes the web-proxy playbook like www https://github.com/openmicroscopy/prod-playbooks/tree/master/k8s where there are bootstrap steps, then config steps which can be reapplied. (skipping since I don't want e.g. production network config or LVM sizes on local Vagrant VM)

There's the same concept for the CI 1.5 servers in this folder - i.e. the bootstrap folder https://github.com/openmicroscopy/prod-playbooks/tree/master/bootstrap

Perhaps all of lvm, network, .. whatever else, should be tagged bootstrap, too?

This concept basically encompasses the issue I had with the ome-dundeeomero playbook back at the start: i.e. there are things commented out which were necessary for the first run, but not subsequent.

Having a folder-per-playbook, with a subfolder called bootstrap would be one way to deal with this, which we decided not to do I think at the start, even though www seems to have gone that way.

[joshmoore]

As an addition to the current list of tags ("v1"), I'm fine with network. That being said:

• It's a quick fix: the prod-playbook playbooks need more refactoring into playbooks and/or roles.
• It's a quick fix: we need to discuss the long-term use of tags.