osc container-infrastructure clustertemplate create

Create new cluster template

Usage: osc container-infrastructure clustertemplate create [OPTIONS] --image-id <IMAGE_ID>

Options:

  • --apiserver-port <APISERVER_PORT>

  • --cluster-distro <CLUSTER_DISTRO>

  • --coe <COE> — Specify the Container Orchestration Engine to use. Supported COEs include kubernetes. If your environment has additional cluster drivers installed, refer to the cluster driver documentation for the new COE names

    Possible values: kubernetes

  • --created-at <CREATED_AT>

  • --dns-nameserver <DNS_NAMESERVER> — The DNS nameserver for the servers and containers in the cluster to use. This is configured in the private Neutron network for the cluster. The default is 8.8.8.8

  • --docker-storage-driver <DOCKER_STORAGE_DRIVER> — The name of a driver to manage the storage for the images and the container’s writable layer. The default is devicemapper

  • --docker-volume-size <DOCKER_VOLUME_SIZE> — The size in GB for the local storage on each server for the Docker daemon to cache the images and host the containers. Cinder volumes provide the storage. The default is 25 GB. For the devicemapper storage driver, the minimum value is 3GB. For the overlay storage driver, the minimum value is 1GB

  • --driver <DRIVER>

  • --external-network-id <EXTERNAL_NETWORK_ID> — The name or network ID of a Neutron network to provide connectivity to the external internet for the cluster. This network must be an external network, i.e. its attribute router:external must be True. The servers in the cluster will be connected to a private network and Magnum will create a router between this private network and the external network. This will allow the servers to download images, access discovery service, etc, and the containers to install packages, etc. In the opposite direction, floating IPs will be allocated from the external network to provide access from the external internet to servers and the container services hosted in the cluster

  • --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

  • --hidden <HIDDEN> — Indicates whether the ClusterTemplate is hidden or not, the default value is false

  • --http-proxy <HTTP_PROXY> — The IP address for a proxy to use when direct http access from the servers to sites on the external internet is blocked. This may happen in certain countries or enterprises, and the proxy allows the servers and containers to access these sites. The format is a URL including a port number. The default is None

  • --https-proxy <HTTPS_PROXY> — The IP address for a proxy to use when direct https access from the servers to sites on the external internet is blocked. This may happen in certain countries or enterprises, and the proxy allows the servers and containers to access these sites. The format is a URL including a port number. The default is None

  • --image-id <IMAGE_ID> — The name or UUID of the base image in Glance to boot the servers for the cluster. The image must have the attribute os_distro defined as appropriate for the cluster driver

  • --insecure-registry <INSECURE_REGISTRY>

  • --keypair-id <KEYPAIR_ID> — 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

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

  • --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

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

  • --network-driver <NETWORK_DRIVER> — The name of a network driver for providing the networks for the containers. Note that this is different and separate from the Neutron network for the cluster. The operation and networking model are specific to the particular driver

  • --no-proxy <NO_PROXY> — When a proxy server is used, some sites should not go through the proxy and should be accessed normally. In this case, users can specify these sites as a comma separated list of IPs. The default is None

  • --project-id <PROJECT_ID>

  • --public <PUBLIC> — Access to a cluster template is normally limited to the admin, owner or users within the same tenant as the owners. Setting this flag makes the cluster template public and accessible by other users. The default is not public

  • --registry-enabled <REGISTRY_ENABLED> — Docker images by default are pulled from the public Docker registry, but in some cases, users may want to use a private registry. This option provides an alternative registry based on the Registry V2: Magnum will create a local registry in the cluster backed by swift to host the images. The default is to use the public registry

  • --server-type <SERVER_TYPE> — The servers in the cluster can be vm or baremetal. This parameter selects the type of server to create for the cluster. The default is vm

    Possible values: bm, vm

  • --tags <TAGS> — Administrator tags for the cluster template

  • --tls-disabled <TLS_DISABLED> — Transport Layer Security (TLS) is normally enabled to secure the cluster. In some cases, users may want to disable TLS in the cluster, for instance during development or to troubleshoot certain problems. Specifying this parameter will disable TLS so that users can access the COE endpoints without a certificate. The default is TLS enabled

  • --updated-at <UPDATED_AT>

  • --user-id <USER_ID>

  • --uuid <UUID>

  • --volume-driver <VOLUME_DRIVER> — The name of a volume driver for managing the persistent storage for the containers. The functionality supported are specific to the driver