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
openstack-dev was decomissioned this night in https://review.openstack.org/621258
Update openstack-dev to openstack-discuss
Change-Id: I77b9a66a6f315096dd5c9ef3de558839778372d9
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
We are updating all Python projects to publish artifacts to PyPI. The name
"congress" is already taken there by another project, and they have not
responded to our request to claim the name. We therefore need to change
the dist name used to package congress. We have some other projects
publishing using an "openstack-" prefix, so I propose using the name
"openstack-congress". This will not change the imports or anything else
about how the code works, just how it is packaged.
Change-Id: I076a4025c40e71845e62fe1747cb7c33a477ea16
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Because we have policy in code, we should be able to use the
oslo.policy CLI scripts to produce sample policy files and render
complete policies based on overrides on disk. This was broken
because Congress did not properly expose the appropriate end point.
This commit exposes a get_enforcer() that substitutes an empty list
in place of arguments passed in through the system.
Based on: https://review.openstack.org/#/c/530828/
Change-Id: Ia5f1f949b2dc97cce4227a8dd6819b4354867b97
Closes-Bug: 1793343
driver name: monasca_webhook
column names renamed to clarify the top level metric info
is only the first metric attached to the alarm.
Change-Id: I9746e29db36550572f877c65e05509fe1e3bac86
Accepts POST webhook notifications [1] at
/v1/data-sources/<data-source-name>/webhook
On alarm activate notification from Vitrage, a new alarm row [2]
is created in Congress vitrage data source service.
On alarm deactivate notification from Vitrage, the corresponding
alarm row is deleted in Congress vitrage data source service.
A retry policy on the sender side would be helpful to avoid
notifications being lost to transient issues
(example from zaqar [3]).
Nonetheless, it is still possible that an alarm deactivate
notification is missed, and an alarm row remains in Congress
indefinitely.
To clean-up these rows, the optional config
'hours_to_keep_alarm' sets the approximate number of hours
before an active alarm row is deleted from Congress.
[1] Expected payload format:
{
"notification": "vitrage.alarm.activate",
"payload": {
"vitrage_id": "2def31e9-6d9f-4c16-b007-893caa806cd4",
"resource": {
"vitrage_id": "437f1f4c-ccce-40a4-ac62-1c2f1fd9f6ac",
"name": "app-1-server-1-jz6qvznkmnif",
"update_timestamp": "2018-01-22 10:00:34.327142+00:00",
"vitrage_category": "RESOURCE",
"vitrage_operational_state": "OK",
"vitrage_type": "nova.instance",
"project_id": "8f007e5ba0944e84baa6f2a4f2b5d03a",
"id": "9b7d93b9-94ec-41e1-9cec-f28d4f8d702c"
},
"update_timestamp": "2018-01-22T10:00:34Z",
"vitrage_category": "ALARM",
"state": "Active",
"vitrage_type": "vitrage",
"vitrage_operational_severity": "WARNING",
"name": "Instance memory performance degraded"
}
}
https://docs.openstack.org/vitrage/latest/contributor/notifier-webhook-plugin.html
[2] alarms table schema:
'name'
'state'
'type'
'operational_severity',
'vitrage_id'
'update_timestamp'
'receive_timestamp'
'resource_name'
'resource_id'
'resource_vitrage_id'
'resource_project_id'
'resource_operational_state'
'resource_type'
[3] https://docs.openstack.org/zaqar/pike/user/notification_delivery_policy.html
Change-Id: I1943cb81eadb1abba9e62d3d886778a09ec63118
This commit loads all datasources drivers by default without the need
of config option. The config option 'drivers' would be deprecated as it
is required to update manually on newly supported drivers for each release
and also error prone.
To disable any of the drivers, can be disabled using the config option
'disabled_drivers'
For example,
disabled_drivers = plexxi, murano
TODO: Support disabled_drivers option to disable the datasource drivers
Partially-Implements blueprint enable-drivers-by-default
Change-Id: I5f9878d07c2e1487f8f14f7cd1948560327d8083
New project congress-tempest-plugin is created, so removing the intree
tempest tests repo
Implements blueprint split-tempest-plugin
Change-Id: Iab440c040453d0ec6a886bf8a0096b566c9ff10b
With an effort to move policy in code, review [1]
removed policy.json from congress repo but missed
to remove reference from setup.cfg.
This patch removes the reference from setup.cfg.
[1] https://review.openstack.org/#/c/503167/
Change-Id: I62b14ddc5ccf3f0362a11b0fc773ccd92c325b93
This commit registers default policies in code. For the
Register and Document Policy in Code community goal.
bp policy-and-docs-in-code
Closes-Bug: 1724714
Change-Id: I1eea53adc19247d8b982c3e22184e8a1e2fb875c
This is the agent part of the blueprint.
Implementation of a datasource that transcribes the content
of configuration files managed by oslo-config in Congress
tables.
The datasource uses a set of agents deployed on the nodes
to access the configuration files.
Change-Id: I56750cfd72ad43d8af123d151f70d1d76568a456
Implements: blueprint configuration-files-validation
Co-Authored-By: Valentin Matton <vmatt.openstack@gmail.com>
Co-Authored-By: Pierre Crégut <pierre.cregut@orange.com>
In order to make it simpler to use the default
configuration files when deploying services
from source, the files are added to pbr's
data_files section so that the files are
included in the built wheels and therefore
deployed with the code. Packaging and deployment
tools can then more easily use the default files
if they wish to.
This pattern is already established with similar
files for neutron, designate and glance as has
been mentioned in the related bug report.
Change-Id: I0bbb00b68fb73fe35aeeb06c0690249fd46b646f
Closes-Bug: #1718356
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
The gating on python 3.4 is restricted to <= Mitaka. This is due to
the change from Ubuntu Trusty to Xenial, where only python3.5 is
available. There is no need to continue to keep these settings.
Change-Id: Id1bc631d1d301a990ae2618e3d081b9b926e1c55
This commit moves the horizon code from contrib/horizon to
congress_dashboard to install as plugin. Added README for the same.
http://docs.openstack.org/developer/horizon/tutorials/plugin.html
Note: Passes basic testing with v2 authentication
This commit doesn't address issue with V3 authentication.It is being
fixed as part of Bug: #1602837
Implements: blueprint congress-horizon-plugin
Change-Id: I06da4a47f61739635e6f1756f773b236ebde55c9
Now that there is a passing gate job, we can claim support for
Python 3.5 in the classifier. This patch also adds the convenience py35 venv.
Change-Id: I1020c9f8f7d29b03b0fd460cbc22a0238725ea8e
The folder congress_tempest_tests has to be packaged in order for the
Debian packaging CI to work. Otherwise, we get:
ImportError: No module named congress_tempest_tests.plugin
when running templest.
Please allow this distribution specific patch to reach upstream.
Change-Id: If14b5afec201068af7cc6fc903cdf6fa72887c2a
Restored and updated the permanent symlinks and updated setup.cfg
to facilitate proper standalone installation of antlr3 w congress.
Change-Id: I7b603bcf3785374d5e83d0e5a98669dbd93d8cd9
The default values needed for congress's implementation of cors
middleware have been moved from paste.ini into the configuration
hooks provided by oslo.config. Furthermore, these values have been
added to the default initialization procedure. This ensures
that if a value remains unset in the configuration file, it will
fallback to using sane defaults. It also ensures that an operator
modifying the configuration will be presented with that same
set of defaults.
Change-Id: I2edc24e4d47c4d664dd31c407d46e42fefdb1488
Closes-Bug: #1551836
OpenStack projects are no longer being tested under Python 2.6, so
remove the trove classifier implying that this project supports 2.6.
Closes-Bug:#1519510
Change-Id: I4207349597abc8d3d05d6d210d35f438534a5997
Having a local copy of a library is a bad practice. Files are
duplicated on the system, it's harder to update it.
For example, the local copy of dateutil 1.5 is not compatible with
Python 3.
Replace the local copy with a dependency to dateutil, at least the
version 2.4.2. dateutil 2.4.2 is compatible with Python 3.
Partially implements blueprint: support-python3
Change-Id: I366c8004e5eb683b41fec2c31cf4a5afdb48180c
Tempest plugin framework provides more flexibility for projects.
With this plugin, it's not requiring the tests live in the tempest
tree.
Change-Id: I8681140d02926b4b3e6af84b8f03b9385e62cc72
congress.conf.sample is out of date, some important options don't
present, like: api_workers, and some option name are wrong, like:
datasource_drivers
We should use oslo-config-generator to generate all the options
automatically.
Change-Id: Id898840667116278c55e4a7568cf80497db4833f
Closes-Bug: #1488405
These files are generated from congress/datalog/Congress.g,
but (i) they change rarely and so no one remembers to run
make and (ii) they require Java to generate. So it's
better for end-users and most developers to check the files in
and just have the people changing the grammar remember to
check in the generated files.
Closes-bug: 1387209
Change-Id: Ia315fc28570edfaa7d8b223c46f514fb7e34921e
This patch adds the framework necessary for data passed in through
the api to be persisted. This patch leverages alembic which provides
several different interfaces for us to handle schema changes. This patch
also adds the initial schema for the policy_rules table which will hold
policy rule data.
Note: lots of this code was shamelessly stolen from neutron :)
Implements blueprint persistent-storage-for-api
Change-Id: I7c85f94cd4c77703debd51d101f221ec33274346
Previously we had not updated setup.cfg to properly install dateutil.
All the tests ran fine, but 'python setup.py install' did not put
dateutil in the proper place, which made the server fail when installed.
Change-Id: Icc468ff41c0d1a70c5dccb9966ce7ed41207c67e