osc container-infrastructure cluster create

Create new cluster

Usage: osc container-infrastructure cluster create [OPTIONS] --cluster-template-id <CLUSTER_TEMPLATE_ID>

Options:

  • --api-address <API_ADDRESS>

  • --cluster-template-id <CLUSTER_TEMPLATE_ID> — The UUID of the cluster template

  • --coe-version <COE_VERSION>

  • --container-version <CONTAINER_VERSION>

  • --create-timeout <CREATE_TIMEOUT> — The timeout for cluster creation in minutes. The value expected is a positive integer and the default is 60 minutes. If the timeout is reached during cluster creation process, the operation will be aborted and the cluster status will be set to CREATE_FAILED

  • --created-at <CREATED_AT>

  • --discovery-url <DISCOVERY_URL> — The custom discovery url for node discovery. This is used by the COE to discover the servers that have been created to host the containers. The actual discovery mechanism varies with the COE. In some cases, Magnum fills in the server info in the discovery service. In other cases, if the discovery_url is not specified, Magnum will use the public discovery service at:

    In this case, Magnum will generate a unique url here for each uster and store the info for the servers.

  • --docker-volume-size <DOCKER_VOLUME_SIZE>

  • --faults <key=value>

  • --fixed-network <FIXED_NETWORK> — The name or network ID of a Neutron network to provide connectivity to the internal network for the cluster

  • --fixed-subnet <FIXED_SUBNET> — Fixed subnet that are using to allocate network address for nodes in cluster

  • --flavor-id <FLAVOR_ID> — The nova flavor ID or name for booting the node servers. The default is m1.small

  • --floating-ip-enabled <FLOATING_IP_ENABLED> — Whether enable or not using the floating IP of cloud provider. Some cloud providers used floating IP, some used public IP, thus Magnum provide this option for specifying the choice of using floating IP. If it’s not set, the value of floating_ip_enabled in template will be used

  • --health-status <HEALTH_STATUS>

    Possible values: healthy, unhealthy, unknown

  • --health-status-reason <key=value>

  • --keypair <KEYPAIR> — The name of the SSH keypair to configure in the cluster servers for ssh access. Users will need the key to be able to ssh to the servers in the cluster. The login name is specific to the cluster driver, for example with fedora-atomic image, default login name is fedora

  • --labels <key=value> — Arbitrary labels in the form of key=value pairs. The accepted keys and valid values are defined in the cluster drivers. They are used as a way to pass additional parameters that are specific to a cluster driver

  • --labels-added <key=value>

  • --labels-overridden <key=value>

  • --labels-skipped <key=value>

  • --links <JSON> — Parameter is an array, may be provided multiple times

  • --master-addresses <MASTER_ADDRESSES> — Parameter is an array, may be provided multiple times

  • --master-count <MASTER_COUNT> — The number of servers that will serve as master for the cluster. The default is 1. Set to more than 1 master to enable High Availability. If the option master-lb-enabled is specified in the cluster template, the master servers will be placed in a load balancer pool

  • --master-flavor-id <MASTER_FLAVOR_ID> — The flavor of the master node for this cluster template

  • --master-lb-enabled <MASTER_LB_ENABLED> — Since multiple masters may exist in a cluster, a Neutron load balancer is created to provide the API endpoint for the cluster and to direct requests to the masters. In some cases, such as when the LBaaS service is not available, this option can be set to false to create a cluster without the load balancer. In this case, one of the masters will serve as the API endpoint. The default is true, i.e. to create the load balancer for the cluster

  • --merge-labels <MERGE_LABELS>

  • --name <NAME> — Name of the resource

  • --node-addresses <NODE_ADDRESSES> — Parameter is an array, may be provided multiple times

  • --node-count <NODE_COUNT> — The number of servers that will serve as node in the cluster. The default is 1

  • --project-id <PROJECT_ID>

  • --stack-id <STACK_ID>

  • --status <STATUS>

    Possible values: adopt-complete, check-complete, create-complete, create-failed, create-in-progress, delete-complete, delete-failed, delete-in-progress, restore-complete, resume-complete, resume-failed, rollback-complete, rollback-failed, rollback-in-progress, snapshot-complete, update-complete, update-failed, update-in-progress

  • --status-reason <STATUS_REASON>

  • --updated-at <UPDATED_AT>

  • --user-id <USER_ID>

  • --uuid <UUID>