Allow cluster config directly return configs instead of writing file.
This is useful when using magnum client utils from non-commandline
interfaces.
Change-Id: Ie6717e1f2d673fe3e92c58a926a82f255a6d20ca
The v1alpha1 version is removed in kubernetes 1.24. v1beta1 was added in
Kubernetes 1.11 and should be supported through existing versions.
Change-Id: I446b8c1c9b46fb8d70317f271a6a650d2a1bbefa
Cluster health_status_reason is also a dict like the template labels,
so we need to handle this in the same way.
Change-Id: I0841ef30f568640839746f2223ba0fb621e2005c
Task: 39081
Story: 2007242
Add embed certs to kubernetes config file to cluster config
Add option --output-certs to cluster config enabling the output of the
certificates files (ca, key, cert). This is for compatibility with tools
that require the certificates in separate files.
Change-Id: I595d243bc9f30d813af06aad46a9037afe383ab5
Story: 1774643
Task: 21668
Now we are handling the label values converting them as a dictionary.
But as magnum-api only accepts the input as string. We are converting
the dictionary into string and passing to magnum-api. It is parsing
the string to dictionary and storing the label value a dictionary.
Change-Id: I2cec19e24c6dd32e209ca65a26a2f1999d8289e0
Depends-on: I4d64da78dc4ed4d5599533b54861b65bce609c28
Closes-Bug: #1659189
The user admin needs to have system:master in the organization
and needs to be named admin.
Closes-Bug: #1689849
Change-Id: If43c3d0a0d83c42ff1fceffe4bcc333b31dbdaab
Move certificate generation and config generation
in magnum utils so that all clusters_shell, bays_shell
and OSC can use.
* Remove / from context name (see #1705480)
* Use absolute paths for the certificates in kubeconfig
It's the same principle like #1614682
Change-Id: I5b8bb11b199b7646a984c7171f3853d3e73923ec
Implements: blueprint openstackclient-support
Related-Bug: #1705480
Related-Bug: #1614682
Magnum allows "labels" to be Dict of string, but currently
magnumclient creates a list of values if same key is specified
more than once when creating a baymodel.
Now if two labels of same key are passed to baymodel-create
the first value is joined with second using comma.
Change-Id: Idcee5c27e29b8d6889fd2c9fa839202ffb8a2f4e
Closes-Bug: #1521461
mesos_slave_executor_environment_variables is a file path to deliver
the data for mesos executor environment variables, and validate the
file if existing or matching the json form.
Change-Id: Iaeb912184f8789321526887d25e281b5181089ef
Partially-Implements:blueprint mesos-slave-flags
Now using 'comma' split the labels list result in the fail when some
value in labels list has comma, for example, mesos_slave_isolation=
docker/runtime,filesystem/linux
The patch fix the bug that some value in labels list has comma will
fail.
Change-Id: I1553b512e4e2efa7677efadf44e959f1601d39ad
Closes-Bug: #1578498
When running the command "magnum container-list --limit -1 --bay
swarmbay" with "--limit -1" , it can get the containers successfully.
Change-Id: I359a9b90bd80cfeb97db2ada8fb1ada0f5eb127e
Closes-Bug: #1562790
* can use commas or semicolons in label list
* add two tests, all semicolons and mixed
semicolons and commas
Closes-bug: #1497042
Change-Id: I6c243b09343b92fc54a991facf874d1e5f0f1f51
Since oslo-incubator is no longer maintained[1] after
90ae25e38915cc502d9e9c52d59e8fb668a72ae1. We should cleanup
the deprecated code.
This patch do the following cleanup actions:
1. Use magnumclient.i18n instead of
magnumclient.openstack.common._i18n.
2. Use magnumclient.exceptions instead of the deprecated
magnumclient.openstack.common.apiclient.exceptions[2].
[1] http://lists.openstack.org/pipermail/openstack-dev/2015-November/
079343.html
[2] https://github.com/openstack/python-magnumclient/blob/master/
magnumclient/openstack/common/apiclient/exceptions.py#L25
Change-Id: I6fae1f84d211d661bb363e43167cdf8b6b06fd4d
Partial-Bug: #1529316
v1 shell has many sub command. It is difficult to add more test
and functions. Actually we have forgotten to add some tests for
these sub-commands.
This patch splits these.
Change-Id: I6b80b621311442df987e6ff031e8c77cf4bb7095
Closes-Bug: #1515109
Adds labels attribute and associated tools/tests to the magnum
client.
Implements: blueprint extend-client-network-attributes
Change-Id: Ie8465275646b82aa9bd7a9de756c519bdd6ec0e2
Users can use these commands to add/remove/update bay attribute(s):
magnum bay-update <bay_id> replace <path=value>
magnum bay-update <bay_id> add <path=value>
magnum bay-update <bay_id> remove <path=value>
For example, this command updates the node_count attribute of a bay:
magnum bay-update 0aab40ba-3f48-4e6e-88a6-247be18b9711 replace node_count=1
Change-Id: If003beaca8e7e8bbdff2cf24d2810b0db9efdf41
Implements: blueprint update-node-count
ricolin