Code conventions: Use “.” to source script files
When you have to source a script file, for example ,
a credentials file to gain access to user-only or
admin-only CLI commands, use . instead of source.
See more:
http://docs.openstack.org/contributor-guide/writing-style/code-conventions
Change-Id: I1788a2e5f1d9e067e2411bb159316ca7990fe46f
This last part adds the agent to the devstack deployment, a
basic tempest test of the datasource and gives an example of
its use.
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: Ibda41c44e551e6dc8e5895968018c7169c34c9c8
Implements: blueprint configuration-files-validation
Co-Authored-By: Valentin Matton <vmatt.openstack@gmail.com>
Co-Authored-By: Pierre Crégut <pierre.cregut@orange.com>
The snapshot file support bypasses the database when inserting rules into the
policy engine, so it makes it possible to insert rules into the engine without
the rules being in the db. That means if Congress tries to synchronize rules
with the db, the synchronizer will delete rules from the snapshot because the
rules do not exist in the db.
Change-Id: Icbd6d1e1f1233aa00157d036f697933da07347f7
Modified predeplyent example to reflect the changes in the datasource content.
Also, added predeployment simulation scenario tempest test.
Implements: blueprint murano-driver
Change-Id: I0d5590abe138d62c9283e8476586e3b48ea50fd1
Adds driver to populate datasource tables based on Murano object
model. Excludes python-muranoclient from requirements.txt.
Replaces it with a mock in unit test.
Implements: blueprint murano-driver
Change-Id: I2a9b411bf841e58b7fce4f234f834eb099a332ab
Previously there were no checks on the syntax of policy
statements, besides those ensuring they matched the grammar.
This change adds a number of policy syntax checks.
Change-Id: I0625af891b3da00ed2df2e85bda061d304b26253
Adding realistic (though obviously not perfect)
action descriptions of the core Neutron API.
Networks, subnets, ports are done. Outstanding issues
are listed at the top of examples/neutron.action. Some of these
need to be addressed, but the goal of this was to understand
the extent to which Neutron/Nova/etc. actions could be expressed
and reasoned about. Plan is to revisit the list of issues
after a similar investigation into Nova.
- Added rudimentary tests for networks, subnets, ports.
- Also fixed a bug for theory inclusion in top_down_evaluation.
- Made minor improvements to the code (e.g. there is now a Theory obj
that all the theories inherit from).
- Increased syntax to include several atoms in the head of each rule.
Necessary to describe update sequence for testing Neutron API.
All tests pass
Issue: #
Change-Id: I63b188acbe51b07e0ceffc9c747b5b62c46c92bf
When rule inserted after data and that rule had self-join,
failed to get right result.
This fix first computes self-joins and then ensures to evaluate
all the resulting rules before computing delta rules and inserting them.
Added test to catch this case in the future.
All tests pass
Issue: #
Change-Id: Ie09dbc82c42069e0f4925d2919ba40e88b2d1a92
Renamed 'projection' to 'simulation' and expanded private_public_network
demo script to include simulation.
Issue: #
Change-Id: I3cae526d37425bb53e91034d1af75199c1d83050
The private/public network example now includes
a step that asks for remediations.
All tests pass
Issue: #
Change-Id: I6f341c6cc74040288b4ef67e776bf079f3346624
Also reorganized a bit. Now we can interact with the runtime using just strings.
Useful if (i) accepting updates over the API wire and (ii) policy statements
will most naturally be sent via strings.
See examples/private_public_network.script for the demo
Issue: #
Change-Id: I5804cbe43bbf3eba8936c9d7f65405417c6203e0
Passing all tests.
Also stubbed in high-level interface for explanations and hypotheticals
Issue: #
Change-Id: Ibe536dfa15236457212eb97351b56ed9e28163cc