| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Six package is not used anymore
Change-Id: Ie72645229f23692d6bf87e58dd8ef212dd91189c
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now in the basic client:
- Boot from volume enhancements
- Update keypair
Now in OSC:
- Force delete cluster
- Update keypair
- Boot from volume enhancements
- Decommision specific node (only via --json)
Change-Id: I031fdb6f7754f6cf242bfae6f10ed05249c07dac
Story: 2003092
Task: 23183
Task: 29740
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I24552338a3b8234abb718579c7eb73409be34f02
|
|/
|
|
|
|
|
| |
APIv2 has been experimental; we've made a change to endpoint for the
creation of multiple clusters.
Change-Id: Idc37b263ceabc9edaf6cab5e24fa83c836edc16d
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Support of all APIv2 features carried from APIv1 ("feature parity")
* Minimum amount of docs to pass the gate
* Endpoint manipulation and version discovery handled by keystoneauth
* APIv2 feature: decommision of specific instances (doc change only)
* APIv2 feature: force delete (new method)
Unit tests will arrive in a future patch.
bp v2-api-experimental-impl
Co-Authored-By: Monty Taylor <mordred@inaugust.com>
Change-Id: I32178439fe85cc6d5faf4ac2e33ae80c08619de5
|
|
|
|
|
|
|
|
|
|
| |
Now we are working on pagination and sorting ability
in Sahara API. This changes support work
with sorting abilities.
Change-Id: I824690f106bd81cc2ee949a65ba129c7ccf21d90
bp: pagination
Depends-on: Icb83422a516961acd7c1c20a88cb0bb816c6bc81
|
|
|
|
|
|
|
|
|
| |
Now we are working on pagination ability in Sahara API.
This changes support work with new abilities.
Change-Id: Idf96a82b0f49bd288eb3fd9bfa82f92074ea4e7c
bp: pagination
Depends-on: I50fa225361617e835c314e873035704b9fe811d0
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
added method to verify cluster, also added
support in the new CLI.
Depends-On: I1b975c9a5e5241c660de66a04bf559fc8f960873
Implements blueprint: cluster-verification
Change-Id: I598753cbb33d7781b646e726ad8d614e924e4876
|
|/
|
|
|
|
|
|
|
|
| |
Adding a sentinel object that will be used as a default
value in update methods. This object will allow to
distinguish whether a field should be unset or should
not be updated.
Change-Id: Ie6679c8f64623e8570176b8009380b08de2be6a5
Closes-bug: #1534050
|
|
|
|
|
|
|
|
| |
Saharaclient API docs now can be autogenerated, that
prevents them from manual update. Also docstrings
were added to describe some unclear parameters.
Change-Id: Ibf9fdf332c91cdfb18d6f8ec5429a39dc2862494
|
|
|
|
|
|
|
|
|
|
| |
Now allowing the shares parameter to be passed on
a cluster update call. It is optional and defaults to
None.
Change-Id: I1a16bff7bd3d20a4253a66bedc86d8c1c72328a6
Partial-Implements: bp sahara-add-shares-to-clusters
Depends-On: I33971eb495c5a318ba17a4b3f98534b9e8776deb
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It implements PATCH updates for clients, updates
support for all objects and is_public/is_protected
support. It's a combination of parts of the
follwing patches (squashed to make review and merge
gating easier and faster):
I3abc57b43d825d69129f9c0b2058d1e2a004c832
I0d1d892ce11c9a3b46c8583ed58f9131a0f915a3
Co-Authored-By: luhuichun <huichun.lu@intel.com>
Co-Authored-By: Andrey Pavlov <apavlov@mirantis.com>
Co-Authored-By: Vitaly Gridnev <vgridnev@mirantis.com>
Change-Id: I5a0156b7effc59ef3d183b0caacb6980c27f425c
Partially-Implements: blueprint api-for-objects-update
Partially-Implements: blueprint shared-protected-resources
|
|
|
|
|
|
|
|
|
|
|
|
| |
Manually mounting shares to every node in a large cluster would be a tedious
and error-prone process. Auto-mounting shares that are requested for use in
either the data source or binary storage case might be feasible for some use
cases. However, outside of our (optional) EDP interface this functionality
would never be usable. As such, it is best to provide the user an API for
mounting of shares onto Sahara clusters.
Change-Id: Ib897d3fefaea146150963e25fbaaec80e197ca36
Implements: blueprint mount-share-api
|
|
|
|
|
|
|
|
| |
This change will allow switch off autoconfiguration, when it's needed.
Partial-Implements blueprint: recommend-configuration
Change-Id: Iaf546262a68b74d9463c476097f0d5596cc38f96
|
|
|
|
|
|
|
| |
This patch allows the user to use the client to create multiple clusters
Change-Id: I3b48d6ede758e86e8cbc5bbccc069c4c24b53a44
Partially-implements: bp simultaneously-creating-multiple-clusters
|
|
|
|
|
|
|
|
|
|
| |
Cluster get operation now supports show_events flag to display provision
progress.
Removed events endpoint as it is going to be removed from the API.
Partially implements bp: event-log
Change-Id: I6892c8be2f8daaa215732f5e58524620cb9a1f85
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is no sense in validation on client side. I believe we
don't want to have all validation logic in two places.
Also, the current validation was wrong for several reasons:
1. Wrong APIException usage (see bug description)
2. It required default_image_id for the cluster. Image could be
set in each node group individually.
3. It required cluster_configs that is not mandatory
So, the only correct check was for node_groups field, but still
I don't think that client is the right place for checking such
things. If one day we will allow clusters with no nodegroups
client should allow that without modifications.
Change-Id: I3a7bf39b102b699e8f4a1e493314412cfd26ee2e
Closes-Bug: #1420569
|
|
|
|
|
|
|
|
|
|
|
|
| |
Each of the list() methods now supports an extra
parameter, search_opts, which is a dict that will
contain search fields and values to limit the result
sets. The changes here will also rely upon changes
to the Sahara service to support query-style
parameters.
Change-Id: I26986cbc153c3f8ad74b52d91086afbdfbd93926
Implements: bp enable-result-filtering
|
|
Exchange the contents of the saharaclient and savannaclient directories
so that 'savannlient' is the effective alias and 'saharaclient' contains
all of the source code.
* Change all of the imports that reference savannaclient to saharaclient
* Change paths that reference savannaclient (under doc)
* Leave variable and class names unchaned at this point
* Leave references to python_savannaclient unchanged since the top
* level dir name has not yet changed
Partial-implements: blueprint savanna-renaming-client
Change-Id: I83cb21922ae5a8cec291990b3ab67bb9e3cb2d62
|