Re: [libvirt] [PATCH v2 6/6] tools: make virt-host-validate check CPU vulnerabilities
On Tue, 2019-10-01 at 16:44 +0200, Martin Kletzander wrote:
On Mon, Sep 30, 2019 at 04:30:18PM +0100, Daniel P. Berrangé wrote:
> Of course you could define everything via a set of structs in the
> code, but its crazy to do that as you've now hardcoded everything
> at build time, pointlessly throwing away the key extensibility
> benefit of having it defined via a data file.
Except when you are using extensive conditionals or building the fact from
multiple pieces information using, for example, boolean expressions. At that
point you are creating a programming language on top of markup language.
I agree.
It just occurred to me that this is pretty much exactly what Ansible
does. It makes sense for them to do so, because the primary use case
is for people to define their own rules, so the people writing YAML
will far outnumber those responsible of the underlying Python engine.
I don't think this would be the case for virt-host-validate.
--
Andrea Bolognani / Red Hat / Virtualization