NuKVM/xen-orchestra
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

type/grammar fixes part 10 (#132)

Browse Source 
* Clarification, update links, organize

* add nfs warning, fix debian version

* add ENOSPC troubleshooting

* add more enospc detail

* add note on editing username

* Documentation typo/grammar cleanup part 9

* grammar cleanup v10

* grammar editing v10
This commit is contained in:
Jon Sands 2018-05-17 14:15:02 -04:00 committed by Olivier Lambert
parent 5f14d84ad2
commit 65cd32125b
3 changed files with 29 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/patching.md
View File

@ -1,23 +1,23 @@
# Patching
Patching a host manually could be time consuming (and boring). That's why we provide the high level feature of downloading and applying all missing patches automatically.
Patching a host manually can be time consuming (and boring). That's why we provide the high level feature of downloading and applying all missing patches automatically.
## XOA smart patching system
Your XOA will check for missing patching on official Citrix servers. They will be displayed if any:
Your XOA will check the official Citrix servers for missing patches. They will be displayed if any:
* in dashboard view
* in pool view (plus the number of missing patches in a red pill)
* in pool view (plus the number of missing patches in a red box)
* in host view (in patching tab, same red pill)
### Installing patches
When you click on "Install all patches", XOA will automatically, at the same time (streaming all operations):
When you click on "Install all patches", XOA will do all of the following automatically:
* fetch all missing patches on Citrix servers
* fetch all missing patches from Citrix servers
* unzip them
* upload them
* apply them in correct order
* apply them in the correct order
You can see more screenshots here: https://xen-orchestra.com/blog/hotfix-xs70e004-for-xenserver-7-0/
@ -26,7 +26,7 @@ You can see more screenshots here: https://xen-orchestra.com/blog/hotfix-xs70e00
## Notes on patching
* Xen Orchestra won't reboot your hosts automatically. That's your call to choose when to do it.
* Patching doesn't mean to reboot every time. Check the "Guidance" row: if "restartHost" is displayed, it means you need to reboot to have the patch fully apply (see screenshot below)
* XO will install all patching without rebooting: that's not an issue. Even applying patches manually, **it's not mandatory to reboot after each patch**.
* Patching doesn't always require rebooting. Check the "Guidance" row: if "restartHost" is displayed, it means you need to reboot to have the patch fully applied (see screenshot below)
* XO will install all patches without rebooting: that's not an issue. Even applying patches manually, **it's not mandatory to reboot after each patch**.
![](./assets/xo5patching.png)

28
docs/vm_creation.md
View File

@ -2,7 +2,7 @@
## Create a new VM
A new VM can be created via the "New" item in the main menu (bottom):
A new VM can be created via the "New" button in the main menu (bottom):
![](./assets/xo5vmcreatemenu.png)
@ -14,11 +14,11 @@ Or in the home view:
### Select your Pool
Because Xen Orchestra can be connected to multiple pools, you must select on which one you want to create your VMs:
Because Xen Orchestra can be connected to multiple pools, you must select which one you want to create your VMs on:
![](./assets/xo5createonpool.png)
On which **host** the VM will actually run will depend of various settings (local SR or not, RAM available etc.)
On which **host** the VM will actually run on will depend of various settings (local SR or not, RAM available etc.)
### Infos category
@ -28,27 +28,27 @@ The next step is to select a template:
![](./assets/xo5createwithtemplate.png)
> What is a XenServer template? It could be 2 things: first an "empty" template, meaning containing only configuration for your future VM, like guiding you for some info (minimum disk size, RAM and CPU, BIOS settings if HVM etc.) Or it could be a previous VM you converted into a template: in this case, creating a VM will clone existing disks.
> What is a XenServer template? It can be 2 things: first an "empty" template, meaning it contains only the configuration for your future VM, such as example settings (minimum disk size, RAM and CPU, BIOS settings if HVM etc.) Or it could be a previous VM you converted into a template: in this case, creating a VM will clone the existing disks.
#### Name and description
Those values can be changed anytime after your VM is created.
These values can be changed anytime after your VM is created.
#### Multiple VMs
You can create multiple VMs at once by toggling the *Multiple VMs* option. The `{name}` pattern is the "Name" field of the VM. By default, it will start with number 1 and so on. You can change this via the "First index" field.
You can create multiple VMs at once by toggling the *Multiple VMs* option. The `{name}` pattern is the "Name" field of the VM. By default, it will start with number 1 and increment up. You can change this via the "First index" field.
Click on refresh icon to take the change into account:
Click on the refresh icon to see the change:
![](./assets/xo5multiplevms.png)
### Performances
### Performance
This is where you are configuring VM performances: number of vCPUs, RAM, CPU weight and cap.
This is where you can configure VM performance options: number of vCPUs, RAM, CPU weight and cap.
#### CPU weight and cap
CPU weight default number is `256` which means it will be scheduled by Xen like any other VMs on the host where it runs. If you raise it, eg with `512`, CPUs on this VM will be scheduled twice more than another one. If you diminish it, with `64` for example, it will be schedule 4 times less.
The default CPU weight is `256` which means it will be scheduled by Xen like any other VMs on the host it runs from. If you raise it, eg with `512`, CPUs on this VM will be scheduled with twice the priority as others. If you decrease it, with `64` for example, it will be scheduled with 4 times less priority.
What about cap? It's the maximum amount of CPUs a VM can consume, using a 100 base (1 vCPU: 100). Default is 0 and means no upper cap.
@ -60,23 +60,23 @@ Depending of your template type (with existing disks or not, PV vs HVM) this pan
#### HVM templates without existing disks
You can choose to boot on a ISO or using PXE:
You can choose to boot from an ISO or using PXE:
![](./assets/xo5installsettings.png)
#### PV templates
Those templates will use PV configuration in order to boot: either from the right ISO or network URL. PV Args can be used to modified kernel parameters, but it's a very advanced setting you shouldn't play with.
These templates will use PV configuration in order to boot: either from the right ISO or network URL. PV Args can be used to modify kernel parameters, but it's a very advanced setting you shouldn't play with.
#### Template with existing disks
Because there is already disks installed, you shouldn't have "Install settings" *per se*. But you can use our Config drive setup if your template already have CloudInit installed!
Because there is already disks installed, you shouldn't have "Install settings" *per se*. But you can use our `config drive` setup if your template already has CloudInit installed!
Please refer to the [XenServer CloudInit section](cloudinit.md) for more.
### Interfaces
This is the network part of the VM configuration: in general, MAC field is kept empty (autogenerated from XenServer). We also select the management network by default, but you can change it to reflect your own network configuration.
This is the network section of the VM configuration: in general, MAC field is kept empty (autogenerated from XenServer). We also select the management network by default, but you can change it to reflect your own network configuration.
### Disks

14
docs/vm_import_export.md
View File

@ -1,18 +1,18 @@
# VM import and export
Xen Orchestra can import and export VM in XVA format (XenServer format) or import OVA files (OVF1 format).
Xen Orchestra can import and export VM's in XVA format (XenServer format) or import OVA files (OVF1 format).
> We are supporting OVA import from VirtualBox. Feel free to report issues with OVA from other virtualization platform.
> We support OVA import from VirtualBox. Feel free to report issues with OVA from other virtualization platforms.
## Import
### XVA files
To import a XVA file, just go to the New/Import menu:
To import an XVA file, just go to the New/Import menu:
![](./assets/xoa5import.png)
Select the target pool and SR where the VM will be imported. Then, drag and drop your file and click on import button.
Select the target pool and SR where the VM will be imported. Then, drag and drop your file and click on the import button.
### OVA files
@ -20,15 +20,15 @@ OVA files contains extra info that you need to check before importing, like name
![](https://xen-orchestra.com/blog/content/images/2016/08/xo5import2.png)
When you are OK with those settings, just click on "Import" button.
When you are OK with these settings, just click on the "Import" button.
## Export
> Exported VMs are in XVA format
Just go in the VM that you want to export, and click on the "Export" button in the toolbar. You'll download instantly a compressed XVA file.
Just access the page for the VM that you want to export, and click on the "Export" button in the toolbar. You'll instantly download a compressed XVA file.
It works even if the VM is running, because we'll export automatically a snapshot of this VM.
It works even if the VM is running, because we'll automatically export a snapshot of this VM.
### Snapshot export