Huaqiang 1d0c3c3a62 cachetune schema: a looser check for the order of <cache> and <monitor> element
Originally, inside <cputune/cachetune>, it requires the <cache> element to
be in the position before <monitor>, and following configuration is not
permitted by schema, but it is better to let it be valid.

  <cputune>
    <cachetune vcpus='0-1'>
      <monitor level='3' vcpus='0-1'/>
            ^
            |__ Not permitted originally because it is in the place
                before <cache> element.

      <cache id='0' level='3' type='both' size='3' unit='MiB'/>
      <cache id='1' level='3' type='both' size='3' unit='MiB'/>
    </cachetune>
    ...
  </cputune>

And, let schema do more strict check by identifying following configuration to
be invalid, due to <cachetune> should contain at least one <cache> or <monitor>
element.

  <cputune>
    <cachetune vcpus='0-1'>
        ^
        |__ a <cachetune> SHOULD contain at least one <cache> or <monitor>

    </cachetune>
    ...
  </cputune>

Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Signed-off-by: Huaqiang <huaqiang.wang@intel.com>
2019-12-13 15:31:26 +00:00
..
2019-12-13 14:57:32 +01:00
2019-10-15 11:25:25 +02:00
2019-10-15 11:25:25 +02:00
2019-10-15 11:25:25 +02:00
2019-10-15 11:25:25 +02:00
2019-10-16 12:06:44 +02:00
2019-10-15 11:25:25 +02:00
2019-10-15 11:25:25 +02:00
2019-10-15 11:25:25 +02:00
2019-10-15 11:25:25 +02:00
2018-12-17 17:52:46 +01:00
2019-10-15 11:25:25 +02:00
2019-10-15 11:25:25 +02:00
2019-11-18 18:49:02 +01:00
2019-10-15 11:25:25 +02:00
2019-10-15 11:25:25 +02:00
2019-10-15 11:25:25 +02:00
2019-10-15 11:25:25 +02:00
2019-10-15 11:25:25 +02:00
2019-11-14 19:02:31 +01:00
2016-09-14 13:18:07 +02:00
2019-10-15 11:25:25 +02:00
2019-12-09 14:06:15 +01:00
2019-12-09 14:06:15 +01:00