- update_keypair now only in v2 schema
- tenant_id->project_id in cluster provision steps
- tenant_id->project_id in referenced job binaries in job templates
- proper check for job template existence, to fail early (as intended)
- hadoop_version->plugin_version for query string filter
- unbreak some data source stuff (related to tenant_id->project_id)
- fix omission of show_progress from cluster GET query string whitelist
- job_id->job_template_id for v2 jobs
- add missing release note info for strict query string checking
- release notes for all the rest
Change-Id: Idea117c406b5ab9b8d85ccf8adb175053416d6ff
Story: 2004505
Task: 28822
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
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
hadoop_version should be changed to plugin_version.
This patch only changes json requests, the complete
change should be done when APIv2 is stable
and APIv1 deprecated. Along with this should be a
data model change as well.
Partial-Implements: bp v2-api-experimental-impl
Change-Id: Id59703ce49741d024ac9dee09d28f8f515c9806a
this change implements basic things requried for
cluster verifications:
* API modifications;
* DB implementation and conductor ops;
* basic health checks;
* periodic job.
Partially implements blueprint: cluster-verification
Change-Id: I1b975c9a5e5241c660de66a04bf559fc8f960873
In order to allow the shares to be updated on a running
cluster, the cluster update operation has been updated
to allow the shares element.
Change-Id: I33971eb495c5a318ba17a4b3f98534b9e8776deb
Partial-Implements: bp sahara-add-shares-to-clusters
Adding shared across tenants and protected from modifictaion
resources support. Implemented for clusters, cluster templates,
node group templates, data sources, job executions, jobs,
job binaries and job binary internals.
Changes:
* Added validation checks to service.validations.acl
* Changed validation schema's to support "is_public"
and "is_protected" fields
* Added validation of "is_protected" field for update(scale/cancel)
and delete methods of corresponding resources
* Extended get and list methods outputs with "is_public" resources
* Added unit tests for "is_public" and "is_protected" resources
Change-Id: I1a3cb14b8de70256e6aa27312dde341e85fc376c
Partially-Implements: blueprint shared-protected-resources
Adding ability to edit clusters (only description and name
at this moment)in order to change their public/protected
attributes later
APIImpact
PATCH /v1.1/{tenant_id}/clusters/{cluster_id}
Partially implements:: blueprint api-for-objects-update
Change-Id: I7b86362e4db576ba5cdb20dff1ae904497a1852a
Jeremy Freudberg