There was the commit that removes vmware. It has alembic migrations,
but doesn't have any tests for that. This commit fixes that.
Change-Id: I66090b0a0d7bfbd8e2365ec027fabfefc9d612da
Closes-Bug: #1668249
CA certificate verification should be available only if
Bypass verification is disabled.
Some changes were made in vmware_attributes_metadata
in openstack.yaml so we have to update releases table
accordingly during upgrade.
Change-Id: Ibc1da57cfda4e732210e5eddb821856f72770dda
Closes-bug: #1616438
The is different migrations in 9.1 version in master branch
and stable branch. Also removed extra migrations from 10.0 version.
Change-Id: I4d79b3f987147efe320d987a8e64a4475c723f52
Since the feature is intended to be delivered within Fuel 9.1, we've got
to move our migrations to proper file. So far 9.0.2 is a codename for
unreleased Fuel version in stable/mitaka. Let's put them here for now,
and rename to 9.1 in the following patch.
Change-Id: I0b9d3989c2281d885274f6d806d85a86c15ba1ec
Blueprint: graph-concept-extension
The transient statuses are not persited in DB because
the status of node should represent the current state
of node, for example: node is provisioned or node is deployed.
The synthetic states: like error, deploying, etc. are used
only for providing additional for user about status of node at this moment.
This statuses can be calculated on demand.
Also node.error_type has type 'String' instead of 'Enum'
Also added handling status 'deleted' in response, which means that node should be deleted from cluster.
Change-Id: If5e79b9274f34e01d2b795491c23361c9050669d
Blueprint: graph-concept-extension
There are 3 new orchestration tasks:
* master_shell
Run task on master node with a context of other node. If 'roles'
selects N nodes, the task will be executed N times.
* erase_node
Erase node. It's necessary task if we want to remove nodes by means
of graphs and not pre-hardcoded actions in Astute.
* move_to_bootstrap
Change node's PXE config to boot via LAN (into bootstrap). As a
previous one, it's necessary task for deletion graph.
Change-Id: Ie8f852762b837a68e0e0b49e11653a8f2e56a014
Blueprint: graph-concept-extension
the following attributes was added:
- node_filter: YAQL expression to select nodes for applying the graph
- node_attributes_on_success: attributes which will be applied to node
if execution of graph completes successfully.
- node_attributes_on_fail: attributes which will be applied to node
if execution of graph fails.
- node_attributes_on_stop: attributes which will be applied to node
if execution of graph interrupts.
Blueprint: graph-concept-extension
Change-Id: I949b3971f62c17b1d243c8ed97e2802afa4e0cce
By introducing transaction manager and moving everything to graphs, we
can't rely anymore on task names as a unique thing for transaction
identifications. Instead, we need to extend tasks model with two
columns - graph_type and dry_run - to make distinguish by executed
graphs.
Co-Authored-By: Igor Kalnitsky <igor@kalnitsky.org>
Change-Id: I967133033eb41143b6acf467702f12de50edb971
Blueprint: graph-concept-extension
* Add ability for handling new predicates for requires
component's property
* Refactoring of exist components validation function
* Update release components according to new DSL model
Implements: blueprint component-registry-improvements
Change-Id: I6175e28118dac494d48968e3f8c51e89ab74a34b
Depends-On: Iab03bf5e36800c8aea0e054719d40ca42a542b73
Size of deployment_info field in tasks table grows as n**2
(depending on number of nodes). If we have 200 nodes, the
size of the structure is about 20Mb. In case of 600 nodes it
would be theoretically about 720Mb, in practice it doesn't fit
into 1Gb.
Good solution is to put common part to separate place. But it's
not so fast. Also it will not help if all nodes will be going to
be deployed with customized deployment info.
Change-Id: Id3154ab423b0863d9cc4952335293bf5fc30df38
Partial-Bug: #1596987
This patch:
* extends current DB model with new entities and provides
related migrations.
* extends plugin sync method to support storing new plugins
attributes.
* provides cosmetic fix for ClusterPlugin model. Lets write table
names in the plural but model names in the singular.
Change-Id: I3edbde1d48461ce3fab7c93f17e2db5332b1f7fb
Implements: blueprint nics-and-nodes-attributes-via-plugin
Curently tasks snapshot field migration is included in 10.0.0
migration. But in stable/mitaka branch it is in 9.0.1. This migration
action should be located consistently in 9.0.1 in all branches.
Change-Id: I235a6ac1ce551370a032b54f350ce2f3f339cb11
Partial-Bug: #1563317
Deployment tasks snapshot is now saving during DeploymentTask message creation
in Transaction.tasks_snapshot field.
Methods:
* attach_tasks_snapshot
* get_tasks_snapshot
are added to Transaction model.
Handler /transactions/:transaction_id/deployment_history/
now showing tasks parameters in output and supporting
request parameter:
/transactions/:transaction_id/deployment_history/?tasks_names=task1,task2
Change-Id: I59446ef456f7d3bd249c686b7a8e1a93a364daf2
Partial-Bug: #1563317
DocImpact
Previous behaviour allowed to create multiple links with the same url
what was occurring during plugin tasks re-run.
Now 409 error is returned when plugin- or cluster-level link creating
or updating with the non-unique URL value.
Plugin developers should handle such exception by themselves
in plugin tasks.
DocImpact
Closes-Bug: #1538209
Change-Id: I1de1e9f3957cbe11e91cd8cd4806ac1cd714d630
Now we get deployment state from DeploymentHistory model. For every task
we get last success transaction and its state.
Change-Id: I2288bc2bc34023c2ca705f1d3cc6ff48347bf549
Closes-bug: #1572226
Andreas Jaeger