Deployment artifacts proposal

[chouseknecht]

ISSUE TYPE

• Feature Pull Request

SUMMARY

Adds proposal to change the artifacts produced by deploy.

Rather than producing a monolithic playbook, produce a better organized solution that relies on an Ansible role and uses the new K8s modules.

[TomasTomecek]

where will the role(s) be placed?

[chouseknecht]

@TomasTomecek

Was thinking we would continue writing artifacts into the ansible-deployment subdirectory that deploy adds to the project.

[TomasTomecek]

I was just curious where would the generated role(s) be placed. You wrote that

Produce a portable, better organized deployment artifact that uses an Ansible role...

When I look at the proposed directory hierarchy, I'm not sure which directory will have the resulting, generated role(s).

Also, what will be the default action of the root playbook project-name.yml?

[chouseknecht]

I'm thinking the playbook is really simple. Maybe something like the following:

- name: my-project
  hosts: all
  gather_facts: no
  roles:
    - role: my-project-role
      tags:
      - always

[chouseknecht]

@TomasTomecek

This was my thinking for the role. It would just be written out in it's own directory, rather than placing it under a /roles subdirectory. I should call this directory project-name-role to be more clear.

[TomasTomecek]

oh right, makes perfect sense now; feel free to leave it as it is

[TomasTomecek]

Good proposal!

[ehelms]

This might be leaping ahead, and more of "phase 2" but potentially good for the proposal itself. I do find the various tags useful for large operations. But I also find myself wanting to more easily re-build and re-deploy a single or set of services rather than the entire stack. If the role design could somehow facilitate that, through tags or variables that would allow faster development, testing and deployment cycles.