...
Deployment Configuration and Strategy
| Parameter | Sub-Category-1 | Sub-Category-2 | Description | Example Value |
| physical_provisioner | ||||
| deployment_strategy | Name of the strategy to use. User can use the one that is defined in airshipit/treasuremap/global/deployment See below. | deployment-strategy | ||
| deploy_interval | ||||
| deploy_timeout | ||||
| destroy_interval | ||||
| destroy_timeout | ||||
| join_wait | ||||
| prepare_node_interval | ||||
| prepare_node_timeout | ||||
| prepare_site_interval | ||||
| prepare_site_timeout | ||||
| verify_interval | ||||
| verify_timeout | ||||
| kubernetes | ||||
| node_status_interval | ||||
| node_status_timeout | ||||
| kubernetes_provisioner | ||||
| drain_timeout | ||||
| drain_grace_period | ||||
| clear_labels_timeout | ||||
| remove_etcd_timeout | ||||
| etcd_ready_timeout | ||||
| armada+ | ||||
| get_releases_timeout | ||||
| get_status_timeout | ||||
| manifest+ | ||||
| post_apply_timeout | ||||
| validate_design_timeout | ||||
| Deployment-Strategy | ||||
| groups | named sets of nodes that will be deployed together. | |||
| name | name of the group | masters | ||
| critical | if this group is required to continue to additional phases of deployment | true | ||
| depends_on | Group names that must be successful before this group can be processed | [] | ||
| selectors | A list of identifying information to indicate the nodes that are members of this group | |||
| node_names | node01 | |||
| node_labels | ucp_control_plane: enabled | |||
| node_tags | control | |||
| rack_names | rack01 | |||
| success_criteria | A list of identifying information to indicate the nodes that are members of this group. When no criteria are specified, it means that no checks are done - processing continues as if nothing is wrong | |||
| percent_successful_nodes | The calculated success rate of nodes completing the deployment phase. | 75 would mean that 3 of 4 nodes must complete the phase successfully | ||
| minimum_successful_nodes | An integer indicating how many nodes must complete the phase to be considered successful | 3 | ||
| maximum_failed_nodes | An integer indicating a number of nodes that are allowed to have failed the deployment phase and still consider that group successful. | 0 | ||
Typical Ordering of groups:
__________ __________________
| ntp-node | | monitoring-nodes | ---------- ------------------ | ____V__________ | control-nodes | --------------- |_________________________ | | ______V__________ ______V__________ | compute-nodes-1 | | compute-nodes-2 | ----------------- -----------------
Profiles
There are two important categories of profiles that the user should create to match their environment:
...