Add file to the reno documentation build to show release notes for
stable/train.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/train.
Change-Id: I330926727ecf0b41450d5317cafea642a70c1d35
Sem-Ver: feature
Add file to the reno documentation build to show release notes for
stable/stein.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/stein.
Change-Id: Ia92f14cdde8a34306bacc85cbad0eacb09a03425
Sem-Ver: feature
This commit adds Tacker driver and unit tests. Which creates
corresponding datasource on service startup and allows congress
to maintain Tacker's VNF and VNFD data via populating data to tables
vnfs and vnfds respectively. Based on which rules
can be created and actions can be executed on tacker service.
Change-Id: I281e8ff508dd066514694419c5aae6a991ab307c
Partially-Implements: blueprint add-tacker-datasource-driver
This commit will add servers.addresses table that will contain
fields: server_id, network_name, address, version, mac_address
and address_type of servers. Which will inturn help in
mapping with Tacker VNF instances via IP address of instances.
Change-Id: I22dfcaed1ac7a1da41636a49585ef30e0eaabba7
Partially-Implements: blueprint add-tacker-datasource-driver
Adds basic comparison, arithmetic and bit arithmetic to Z3 theories.
Builtins depend on the kind of theory in use. Z3 builtins are the only
polymorphic predicates of the engine.
Change-Id: Icb68c71ec29604638282a34d34ce06f1e1d69275
Implements: blueprint alternative-engine-z3
This commit adds the functionality of congress-status CLI for performing
upgrade checks as part of the Stein cycle upgrade-checkers goal.
It only includes a sample check which must be replaced by real checks in
future.
Change-Id: I27204c1c2dce2443eaa18a85144cbc892d61b551
Story: 2003657
Task: 26125
Basic structure for the integration of Z3 into Congress.
Defines a Z3Theory as an alternative to nonrecursive theories.
Defines a Z3Context for executing Z3Theory content.
Z3 must be installed manually and is not in the requirements
devstack will install Z3 if ENABLE_CONGRESS_Z3 is set.
Limitations:
* No built-ins
* Typechecking does not support sub-typing (will be done later through built-ins).
Partially-implements: blueprint alternative-engine-z3
Change-Id: I87ff439a3ed4a3e83c78c98add7d94275f716a01
This commit adds the release notes for the feature enable-drivers-by-default
bp
Implements blueprint enable-drivers-by-default
Change-Id: Ica46299952acce4396e83b1e1c49e58b0ed6ab85
Moved to upgrade section because the deprecation had
already taken place back in Kilo.
An upgrading deployer may not carefully look at deprecation
section because newly deprecated things are expected to
remain available for a time. Upgrade section notes more
immediate issues for upgrader.
Change-Id: I9e1b98b8f304f46da05aa72aed84e7ce0b22e098
This commit removes the deprecated nova hosts table from the
nova driver. It uses superseded hypervisor list instead.
Ref: I85a287ff2666c2dcdcbbc8fd6c2e285176f7a67a
Closes-Bug: #1755156
Change-Id: I6cfdc72332fa7a03a65793beffd246d07c3a1f07
Swift client does not always handle unversioned identity URL
properly. Leading to authorization failure because keystone cannot
handle incorrect path, returning 404.
To work around the issue, congress swift driver
specifies the version in url if none is already provided.
Partial-Bug: 1677380
Change-Id: I8df7dac60e4f7cb3c2ec792e13f687d5844c8409
Mistral driver and unit tests. Allows congress to
create workflows and trigger execution in Mistral.
Also configures mistral for gate integration tests.
Tempest tests in separate patch.
Implements blueprint add-mistral-driver
Change-Id: I79d3b9c2f659302f43164d5eef3b23ddf2f2d056
Full automatic documentation of the options for the agent part.
Documentation of the deployment of an agent.
Documentation of the devstack deployment.
Change-Id: If9f7e5b7bc23f28b3c310ee0c8642ed46048fb99
Implements: blueprint configuration-files-validation
Co-Authored-By: Pierre Crégut <pierre.cregut@orange.com>
Co-Authored-By: Valentin Matton <vmatt.openstack@gmail.com>
Releasenotes are version independent, so remove version/release display.
This is needed for new release notes publishing, see
I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting
at
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html
Change-Id: Iaa7b81302a8d53da7dad0101f8732a0fb64f4616
This commit removes the ceilometer datasource driver support in congress, as
ceilometer API is removed in Queens release.
Reference:https://review.openstack.org/#/c/512286/
Change-Id: Ib7ade0951f8a85102d95a0f01c3d63337f6b2404
Closes-Bug: #1729761
Because of temporarily very unstable gate so close to RC1 deadline,
aggregating several RC1 targeted changes into one patch to make
deadline.
Included changes:
Temporarily disabled replica tempest test because of instability.
Update URL home-page in documents according to document migration
Author: Luong Anh Tuan <tuanla@vn.fujitsu.com>
Policy library loads only .yaml, .yml
Also skip-continue rather than exit congress on loading failure
(for example because of incorrect format or file system error)
Update auth_url in manual testing script
To work with latest keystone/devstack.
Add sample outputs from manual testing scripts
Add documentation and update release notes for policy library
Add auto-generated config reference
Part of doc-migration work
Closes-Bug: 1706158
Change-Id: If2606739f02418d14251dccc4d3a5f9fe10ca48f
A new congress/encryption.py module handles all aspects of
encryption.
The datasource DB interface class encapsulates all the
encryption (on write) and decryption (on read).
A new config option `encryption_key_path` has been added to the
DEFAULT section
to specify the path to the directory containing encryption keys for
encrypting secret fields in datasource config. The default value
works for most deployments.
A new key is automatically generated and placed in the
`key_path` directory if none exists.
Temporarily disabled an HA test which fails because the test
set up needs to be updated (the way popen starts the replicas,
they do not have permission to access the encryption keys set
up by the original congress instance. See this output for more
detail:
http://logs.openstack.org/35/487235/3/check/gate-congress-dsvm-api-mysql-ubuntu-xenial/f53656f/testr_results.html.gz
(OSError: [Errno 13] Permission denied: '/etc/congress/keys/aes_key')
Change-Id: I49a71bb398383f93cd2ea93e054a9a27a45c4660
DB interface for adding, getting, and deleting library policies
A DSE service for adding, getting, and deleting library policies
Alembic migration script for adding the new DB table
policy library API model
Tempest smoke test
Closes-Bug: 1693617
Partially implements: blueprint policy-library
Change-Id: I15dda797e6e29ff5155f5758d93d68499539f8fc
This commit adds tempest tests for keystonev3 driver
Also removes/fixes broken columns in the `users` table.
Closes-Bug:#1689471
Change-Id: I8ca8d2121b167f884ac2282a30a6214ba29cb56e
The following information is added: encrypted, availability_zone,
replication_status, multiattach, snapshot_id, source_volid,
consistencygroup_id, migration_status, attachments.
We discussed on IRC how to deal with changes to the data schema. There
was some agreement that versioning the schema was the most complete
solution.
But at the moment and in the medium term, we do not have much need for
understanding the different versions in code (ie. a version parameter
gets passed to the driver when creating a datasource). So in this
patch, I propose to document the cinder driver schema version as 2.1
(and the original version 2.0 to coincide with the cinder client
version used.) Rules written for 2.0 is compatible with 2.1 driver.
But rules written for 2.1 schema may not be compatible with the 2.0
driver.
The schema version is helpful so that when a policy is documented
with the schema version it is based on, users can figure out whether
it is compatible with a particular install of congress drivers.
At the same time, we avoid some implementation and maintenance
complexity by maintaining only the latest minor version of each major
version.
Note: the backward compatibility of this change would be achieved with
positional argument padding under review here:
https://review.openstack.org/#/c/448828/
Closes-bug: 1674537
Change-Id: Ia0f2f17b4e25f70600175ababb35805fbcdd3142
Previously, builtins and helper tables were in the same namespace.
This is problematic because whenever we introduce a new builtin,
it would override any helper tables that a user had written
using that same name.
In this change, all builtins are prefixed with builtin: so we are free
to add as many new builtins as we like. So that we can officially
deprecate the bare version of builtins (i.e. builtins not prefixed
by builtin:), the bare version is still allowed. Once the deprecation
period is over, we will remove support for bare builtins.
Change-Id: I0438826289a4219b9d1043f8132ba5d193e8751b
Nate Johnston
OpenStack Release Bot