This commit allows users to create a new keypair to access to
the running cluster when the cluster's keypair is deleted. But
the name of new keypair should be same as the deleted one, and
the new keypair is available for cluster scaling.
we can implement it via update_keypair parameter.
Change-Id: I3bc0ba52ceebff8ae128321aeb9fdbb5769baaf5
Closes-Bug:#1745142
When creating a cluster, validate node processes as early as we can.
(The config-recommending step may have some impact on validity, so we
must leave that as the first call.)
Note that there has been a desire mentioned to move the node process
validation to occur during cluster template creation. Unfortunately the
amount of refactoring needed makes the task too daunting to be
completed now.
Change-Id: Ib5c91e062b32a83268d178417cbc5120d4c57934
Creation of a single cluster and creation of multiple clusters will now
share an API endpoint (in the APIv2 case). More specifically, the
original single-cluster endpoint will accept a `count` parameter in the
request and the multiple-cluster endpoint has been removed.
We can make this kind of change because APIv2 is still experimental.
Also, when creating multiple clusters, the response will now contain
all details about the clusters; previously, the response simply gave
cluster IDs.
Change-Id: I90faf4956a8ea4b4ae31a29382732771fdfddecb
Story: 2002099
Task: 19777
* Add force delete operation to engine using stack abandon
* Basic unit tests for force delete
* Necessary removal of "direct engine" code
* Change schema of APIv2 cluster delete to allow force delete
* Unit tests for new cluster delete schema
* Basic docs about force delete
* Release note
bp sahara-force-delete
Partial-Bug: #1647411
Change-Id: Ida72677c0a4110cb78edf9d62d8330cd4608ff76
Adding the option to decommission specific node from cluster.
Partially implements bp: decommission-specific-instance
Change-Id: I1a858fecc1b32f91c76aea6db14e0d5a419211d1
This change renames the service api modules to be organized under the
sahara.service.api package. A v2 package has been added which holds the
equivalent v10 and v11 functions. To make the api version setup
transparent to the caller, the global OPS variable has been refactored
into the base sahara.service.api package.
Changes
* create sahara/service/api package
* rename sahara/service/api.py to sahara/service/api/v10.py
* rename sahara/service/edp/api.py to sahara/service/api/v11.py
* correct occurances of old imports in code and tests
* rename sahara/tests/unit/service/test_api.py to
sahara/tests/unit/service/api/test_v10.py
* add initial v2 equivalents for current api services
* move global OPS object into the sahara.service.api package
* add documentation for the api service layer
Partial-Implements: bp v2-api-experimental-impl
Depends-On: I16918a30a862b42edd7a982caf555be618199ac3
Change-Id: Iefbedbc76ac620ff012bcaf536c17637b6252a15
Zhuang Changkun