The following sequence diagrams illustrate the inner working of Magic Castle
once terraform apply
is called. Some details were left out of the diagrams,
but every diagram is followed by references to the code files that were used
to build it.
puppet-magic_castle.git
does not have to refer toComputeCanada/puppet-magic_castle.git
repo. Users can use their own fork. See the developer documentation for more details.
magic_castle:/common/design/main.tf
magic_castle:/openstack/network-1.tf
magic_castle:/openstack/network-2.tf
magic_castle:/common/instance_config/main.tf
magic_castle:/openstack/infrastructure.tf
magic_castle:/common/cluster_config/main.tf
magic_castle:/dns/cloudflare/main.tf
magic_castle:/dns/acme/main.tf
config_git_url repo
does not have to refer toComputeCanada/puppet-magic_castle.git
repo. Users can use their own fork. See the developer documentation for more details.- While the diagram represents each step as completed sequentially, each node provisioning is independent. The only step that requires synchronisation between nodes and the management node is the puppet certificate generation.