Split out the XenCenter conventions

Signed-off-by: David Scott <[email protected]>

Author: David Scott

_data/navbar.yml

@@ -25,6 +25,7 @@
   - xen-api/consoles.md
   - xen-api/install-vms.md
   - xen-api/networking.md
+  - xen-api/xencenter.md
   - xen-api/udhcp.md
   - xen-api/index.html
 - title: Xapi

xen-api/extensions.md

@@ -23,29 +23,3 @@ If it is a Linux-based VM, install the COMPANY\_TOOLS and use the `xenstore-read
 > **Note**
 >
 > Only prefixes beginning with `vm-data` are permitted, and anything not in this name-space will be silently ignored when starting the VM.
-
-Internationalization for SR names
----------------------------------
-
-The SRs created at install time now have an `other_config` key indicating how their names may be internationalized.
-
-`other_config["i18n-key"]` may be one of
-
--   `local-hotplug-cd`
-
--   `local-hotplug-disk`
-
--   `local-storage`
-
--   `xenserver-tools`
-
-Additionally, `other_config["i18n-original-value-<field name>"]` gives the value of that field when the SR was created. If XenCenter sees a record where `SR.name_label` equals `other_config["i18n-original-value-name_label"]` (that is, the record has not changed since it was created during XenServer installation), then internationalization will be applied. In other words, XenCenter will disregard the current contents of that field, and instead use a value appropriate to the user's own language.
-
-If you change `SR.name_label` for your own purpose, then it no longer is the same as `other_config["i18n-original-value-name_label"]`. Therefore, XenCenter does not apply internationalization, and instead preserves your given name.
-
-Hiding objects from XenCenter
------------------------------
-
-Networks, PIFs, and VMs can be hidden from XenCenter by adding the key `HideFromXenCenter=true` to the `other_config` parameter for the object. This capability is intended for ISVs who know what they are doing, not general use by everyday users. For example, you might want to hide certain VMs because they are cloned VMs that shouldn't be used directly by general users in your environment.
-
-In XenCenter, hidden Networks, PIFs, and VMs can be made visible, using the View menu.

xen-api/xencenter.md

@@ -0,0 +1,32 @@
+---
+title: XenCenter
+layout: default
+---
+
+XenCenter uses some conventions on top of the XenAPI:
+
+Internationalization for SR names
+---------------------------------
+
+The SRs created at install time now have an `other_config` key indicating how their names may be internationalized.
+
+`other_config["i18n-key"]` may be one of
+
+-   `local-hotplug-cd`
+
+-   `local-hotplug-disk`
+
+-   `local-storage`
+
+-   `xenserver-tools`
+
+Additionally, `other_config["i18n-original-value-<field name>"]` gives the value of that field when the SR was created. If XenCenter sees a record where `SR.name_label` equals `other_config["i18n-original-value-name_label"]` (that is, the record has not changed since it was created during XenServer installation), then internationalization will be applied. In other words, XenCenter will disregard the current contents of that field, and instead use a value appropriate to the user's own language.
+
+If you change `SR.name_label` for your own purpose, then it no longer is the same as `other_config["i18n-original-value-name_label"]`. Therefore, XenCenter does not apply internationalization, and instead preserves your given name.
+
+Hiding objects from XenCenter
+-----------------------------
+
+Networks, PIFs, and VMs can be hidden from XenCenter by adding the key `HideFromXenCenter=true` to the `other_config` parameter for the object. This capability is intended for ISVs who know what they are doing, not general use by everyday users. For example, you might want to hide certain VMs because they are cloned VMs that shouldn't be used directly by general users in your environment.
+
+In XenCenter, hidden Networks, PIFs, and VMs can be made visible, using the View menu.