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
CA file is not uploaded because we made a mistake
in name vc_ca_file.
Fix typos vc_ca_file -> vcenter_ca_file to get correct
certificate files for cinder and compute item in
orchestrator serializer.
Change-Id: I531a1d6fb7d8cf28df644f8d2301cec4f437a996
Closes-bug: #1623478
CA certificate verification should be available only if
Bypass verification is disabled.
Partial-Bug: 1616438
Change-Id: Ib83210f52c7874398fcb1791e51091e05151273f
Depends-On: Id38bf7c74869fa60852ca1cb2ccaa9c63412cf64
* 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
nailgun.errors have a huge set of exceptions but without hierarchy. This
patch remove exception generation from dict and make it explicitly with
python classes and add some exceptions hierarchy. Now all network errors
inherit from NetworkException and same for other exceptions.
Change-Id: I9a2c6b358ea02a16711da74562308664ad7aed97
Closes-bug: #1566195
Added support for the following custom control types:
* text_list
* textarea_list
Implements: blueprint dynamic-fields
Change-Id: I3b8b0068c98cdc5823534ea9721a17a3d1ee92fe
This is redesign of plugins architecture in order to store
the plugin's attributes in a separate table, not in cluster
attributes, so it will be possible to remove connection between
plugin and cluster when a plugin gets deleted.
Added ability to work with different versions of a plugin.
User can choose the preferred version in UI.
The test "test_plugin_generator" was removed because no longer
relevant.
Closes-Bug: #1440046
Implements: blueprint store-plugins-attributes
Change-Id: I52115f130bf1c7c80c66e18d0bf9f7acb16dd56c
This change introduces new field 'restrictions' for networks
On cluster create and on attributes update, network metadata validates
restrictions if specified.
Networks with restrictions should be created or removed depends on cluster
attributes matches specified restrictions.
Implements: blueprint fuel-integrate-ironic (partially)
Change-Id: I65a0d27e7c4c95360d4745f7e9cdd948bb20fdd3
Logic for processing limits ported from UI side
DocImpact related to: bp create-role-with-nailgun-api
Change-Id: I321cf8ff0c6e63312d908f409131fe93fb388ae4
* provides implementation for checking
restrictions which behavior desribed in openstack.yaml
file for attributes and vmware_attribute on nailgun side.
* pre-deployment checking for vmware consistency
Change-Id: I2124bbf3fd8d2f7fd586c9859f63b169354b8ad7
Currently we haven't possibility to handle restrictions
and limits in nailgun. Validation logic declaratively
described in openstack.yaml so we need engine to process
it. Idea based on discussion in comments for
https://review.openstack.org/#/c/146235/. This commit
provides simple interface for expression parser which
can check 'restrictions' section in YAML file.
Change-Id: I76ea7aced08cd46d8ef240aa6c5976c317fdc7cb
Andreas Jaeger