Define Business Logic Required For Building Assemble Modules

The Orchestrator is purposefully designed to be modular and, except for the Orchestrate module itself, all pieces are user replaceable.

For others to implement their own replacement Assemble module, we need to define the integration specifications.

Expected Outputs:

  • Defines the required business logic for a custom Ansible inventory
  • How do we properly group primary and secondary sites? maybe site_name and primary_site_name; if they are not the same then it's a secondary?
  • Define all variables to be set that are not easily calculated in Ansible
    • internal_address
    • external_address
    • site_name: the site a node belongs to
    • primary_site_name: the primary site that a node reports to (see above question)
    • others to be determined in course of spike

For more information; see the extra-vars simplification research spike issue.

Added context from #202 (closed):

  1. Many of our largest customers run GitLab on prem on their own hardware and they want full control over setting up the hardware.
Edited by Robert Marshall