The translation from JSON source data to tabular Congress data places the
limited resources of Congress developers in the way of the Congress users
having the flexibility to quickly try/use any data source and data field as
the need arises in their policy use cases. This spec is a proposal to
experiment with removing the translation step, thus retaining the source JSON
data model, as a promising way to overcome the limitation.
Change-Id: I9838e4bfb051fb8d9e1e83920e2253e1d6495ab7
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: I51fb01c0ae18ba2c249646d1197922a3f9297f7a
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
There are no stein specs, so using a glob pattern to include them in the
output causes a warning which then breaks the build. Comment that
toctree out for now.
Change-Id: I97ca5dae30e59023256e6368aa98953f7cb157dd
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I5a5adee7eec53a696f90baa69c9b6abd2e569165
Story: #2002586
Task: #24290
According to Openstack summit session [1],
stestr is maintained project to which all Openstack projects should migrate.
Let's switch to stestr as other projects have already moved to it.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: I7daa364d2016e1b7951e6240b3254287361f9d0f
Z3 is an open source automatic theorem prover developed by Microsoft.
This spec describes how to add Z3 as an alternative Datalog engine
in Congress.
Change-Id: Ie1e891408c3f03618926cff4d88e7904b0c0e370
In preparation to support more policy engines in addition to the standard
Congress policy engine (e.g., ones based on SQL, influxDB, or Z3), we need
explicit typing of table columns in the data sources and the
data service engine. This spec proposes to support explicit typing, including
custom types, in an extensible, evolutionary, and backwards-compatible manner.
Change-Id: I389ff5fc8c7cdf9ca3b145c5eb8826f6e6cd28fa
Curly quotes(Chinese punctuation) usually input from Chinese input method.
When read from english context, it makes some confusion.
Change-Id: I555d5cd51457984050a8822e777b4e82e15c5d99
This specification introduces a datasource driver and agents to collect
configuration files handled by the oslo-config library on the different
nodes and make them available to the congress datalog engine as a
datasource.
Change-Id: I5683a839e8fb85d7d44fd01e8800481fd2bd3fbb
Implements: blueprint configuration-files-validation
Co-Authored-By: Valentin Matton <vmatt.openstack@gmail.com>
Co-Authored-By: Pierre Crégut <pierre.cregut@orange.com>
PollingDataSource class polls all data from related services once
the DataSource is initialized. If the polling spends long time
to fetch the data, even though any policy rule doesn't use some
of the DataSource's translator, it causes performance issue.
This spec resolves the performance issue by diasbling translator
to poll data.
blueprint selectable-translator
Change-Id: Ie00cf5a8f8fc160de62d2013c4fb6113b6ba624f
Some applications require Congress to be highly available (HA). Some
applications require a Congress policy engine to handle a high volume
of queries (high throughput - HT).
This spec describes how we can support several deployment schemes that
address some HA and HT requirements.
blueprint high-availability-design
Change-Id: I0ce2fc3895f022d3b363c9674c6dafbbc7447c75
Currently, Congress only has datasource drivers which polls data
from cloud service. This spec proposes a push type datasource driver
which receives data from cloud service.
blueprint push-type-datasource-driver
Change-Id: Ie8e76547ff0f9f67e0aeb05b36ee1b66e8b4cb61
The current nova provides availability zones but nova data source
driver does not support it. In order to give more flexible and
extensible usage, we need to add it to nova driver.
Change-Id: I6f34216b4a47a0e58973fc8a5ef6072923077603
Since some sentences exceeded a maximum of 79 charaters,
runtests job generated AssertionError during testr like:
'AssertionError: False is not true' and 'Line limited to
a maximum of 79 characters.'
This bug fix is for running tox and for Jenkins test.
Change-Id: I6b7292f49daf57b0ba1c2663df8369a20bde5d3e
Currently, API process relies on d6cage in its class. This change
removes the dependencies for new Congress distributed architecture.
blueprint dist-remove-d6cage-from-api
Change-Id: I2bc361e574e57c348e4838d586226f20a64ae98a
Currently Congress specs sphinx doc build broken,
all of the rst files can't be built into html files,
so previewing the html format of specs is impossible.
Fix it so that we can review specs in human readable way.
Some format issues exist in current rst files, so fix these
at the same time so that tox py27 and docs build can pass.
Change-Id: I0dcdfb315e8314fb54d7333c2395d41ff6a0c9a6
The Congress API should be able to list current
supported API versions. Export the version list
API, and show the current API details, include:
id, status, update time, links, like other
OpenStack project: nova, neutron and etc.
APIImpact
DocImpact
blueprint api-version
Change-Id: I766a1e9e6ef0b78661ee556b586ec849f2904942
Nate Johnston