kvm: Use -display none rather than -nographic

[ganeti-local] / doc / design-query2.rst

diff --git a/doc/design-query2.rst b/doc/design-query2.rst
index b069b26..4c7b52d 100644 (file)
--- a/doc/design-query2.rst
+++ b/doc/design-query2.rst
@@ -100,6 +100,8 @@ items:
   Jobs
 ``lock``
   Locks
+``os``
+  Operating systems
 
 .. _data-query:
 
@@ -284,6 +286,10 @@ A field definition is a dictionary with the following entries:
   formatting any unknown types the same way as "other", which should be
   a string representation in most cases.
 
+``doc`` (string)
+  Human-readable description. Must start with uppercase character and
+  must not end with punctuation or contain newlines.
+
 .. TODO: Investigate whether there are fields with floating point
 .. numbers
 
@@ -322,7 +328,7 @@ methods.  Unavailable values are set to ``None``. If unknown fields were
 requested, the whole query fails as the client expects exactly the
 fields it requested.
 
-.. _luxi:
+.. _query2-luxi:
 
 LUXI
 ++++
@@ -337,7 +343,7 @@ as filters. Two new calls are introduced:
   Execute a query on items, optionally filtered. Takes a single
   parameter, a :ref:`query object <data-query-request>` encoded as a
   dictionary and returns a :ref:`data query response
-  <data-query-response`.
+  <data-query-response>`.
 ``QueryFields``
   Return list of supported fields as :ref:`field definitions
   <field-def>`. Takes a single parameter, a :ref:`fields query object
@@ -386,7 +392,7 @@ Other discussed solutions
 
 Another solution discussed was to add an additional column for each
 non-static field containing the status. Clients interested in the status
-could explicitely query for it.
+could explicitly query for it.
 
 .. vim: set textwidth=72 :
 .. Local Variables: