Hi Valentin,
Sounds like an interesting use case. Typically we've focused on
information available through APIs. In this case the information would be
pulled off the disks of the machines running each service.
Here's the info for our weekly meeting. If you can make that, it's a good
place to
Hi Eric,
Here is the blueprint :
https://blueprints.launchpad.net/congress/+spec/configuration-files-validation
As Pierre Crégut presented it in his reply to Clint, the use of
Congress
we suggested and config management systems complement one
Hi Valentin,
Very cool to hear about your use case and vision! It definitely sounds
like the kind of use case Congress is well-equipped to solve using a
flexible, declarative rule language.
I'd love to explore the use case further (and where it fits along side
config management systems as Clint
This is the classical divide between workflows and business rule engines
and we
think that both are useful. While the first are invaluable to make a
system reach
a correct state, the second describe in a more declarative way what a
correct
state is and can also be used as a global model of the
This is the classical divide between workflows and business rule
engines and we think that both are useful. While the first are
invaluable to make a system reach a correct state, the second
describe in a more declarative way what a correct state is and can
also
Excerpts from valentin.matton's message of 2017-07-04 15:29:25 +0200:
> We would like to use congress to check the consistency of the
> configuration files used by the various Openstack services on different
> nodes.
>
> Although installers do a great job for ensuring that the initial
>
We would like to use congress to check the consistency of the
configuration files used by the various Openstack services on different
nodes.
Although installers do a great job for ensuring that the initial
definition of those files are correct, it may be necessary to tweak
those files on
