-
Notifications
You must be signed in to change notification settings - Fork 70
Using default templates
Sergei Pogrebnyak edited this page May 1, 2018
·
12 revisions
Use one of these templates to register a target installation node:
- New local node
- New remote Linux node
- New remote Windows node
- Existing remote node
- local node that runs Command Central itself. This is only suitable for local development, but the easiest option to get started with
Apply one of the runtime templates onto the node defined above. Make sure you match product and fix repositories with the release version of the target node
sagcc exec templates composite apply <TEMPLATE_ALIAS> nodes=<NODE_ALIAS> \
repo.product=<PRODUCT_REPO_NAME> \
repo.fix=<FIX_REPO_NAME> \
[... other required parameters defined in the template]
--sync-job --wait 360
Please see README.md in each template folder for details, For example sag-um-server
- Open Command Central Web UI Stacks
- Add new stack by clicking
(+)
icon - Add new Infrastructure layer
- Select type of the layer
- Choose the operating system and available bootstrap installer for it
- Provide required additional parameters
- Finish the wizard
- Wait until provision jobs complete. Optionally use Jobs view to monitor
- Add new Runtime layer
- Select type of the layer
- Select product and fix repositories
- Select exactly one node on which to provision the layer runtimes
- Review and adjust optional parameters as needed
- Finish the wizard
- Wait until provision jobs complete. Optionally use Jobs view to monitor
- Add additional Runtime layers as needed to build the stack