Extension of storage reporting design doc
This patch rewrites and extends the design doc about storage reportingwith respect to disk templates and storage types. In constrast to theprevious version, we now consider disk templates as the user-facingentity, that the user can dis/enable for the cluster. Storage types...
Document procedure to downgrade a cluster
This is based on the --donwgrade option of cfgupgrade, first introduced in1709435e.
Signed-off-by: Bernardo Dal Seno <bdalseno@google.com>Reviewed-by: Guido Trotter <ultrotter@google.com>
Fix error in the developer notes
The version numbers of two programs had been swapped.
Signed-off-by: Michele Tartara <mtartara@google.com>Reviewed-by: Helga Velroyen <helgav@google.com>
Add dependency on PyYAML in devnotes
This is required because of 0e79564a; otherwise, the pylint-qa target willfail.
Update installation documentation
Some required dependencies were missing from the installation instructions.
Add DCStatus data type for the data collectors
Also adds the DCStatusCode, part of DCStatus, and the addStatusutility function for adding the "status" field to an already existingJSValue.
The design document is updated to have the status codes sorted by increasing...
Export the dcVersionInformation for the Drbd collector
Also, update the JSON output (and the design document) so that it is notin camelcase anymore. This is part of a bigger effort to remove camelcasefrom the exposed JSON.
Signed-off-by: Michele Tartara <mtartara@google.com>...
Change format of the empty status message
Having 'null' instead of an empty string for an empty status messageincreases the complexity of the code with no real improvement.
This patch modifies the monitoring agent design document solving this issue.
Refactor ispecs in ipolicy structures
Minimum and maximum instance specs are put together into a single elementof the instance policy. This is in preparation for introducing multiplemin/max specs.
Signed-off-by: Bernardo Dal Seno <bdalseno@google.com>...
Amend partitioned design doc for multiple ispecs
There will be only one standard specification in instance policies.
View revisions
Also available in: Atom