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

fix(all): bad relative path fixed

Browse Source
This commit is contained in:
Olivier Lambert 2016-07-04 17:22:10 +02:00
parent a7bdd1798e
commit cdf3c16cd9
17 changed files with 29 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/acls.md
View File

@ -7,13 +7,13 @@ ACLs are the permissions for your users or groups. The ACLs view can be accessed
3. Choose the role for this ACL
4. Click on "Create"
![](./assets/createacl.png)
![](../assets/createacl.png)
> Pro tip: you can click to add multiple objects at the same time!
Your ACL is now available in the right list:
![](./assets/acllist.png)
![](../assets/acllist.png)
You can edit/remove existing ACLs here.

2
doc/administration.md
View File

@ -197,7 +197,7 @@ You can change the CPU Weight in the VM view. Values are:
* Normal
* Double (x2)
![](./assets/cpu_weight.png)
![](../assets/cpu_weight.png)
By default, each VM has a weight of 256.

2
doc/architecture.md
View File

@ -16,7 +16,7 @@ Your XOA is connected to all your hosts, or on the pool master only if you are u
## Xen Orchestra (XO)
![](./assets/xo-arch.jpg)
![](../assets/xo-arch.jpg)
Xen Orchestra itself is built as a modular solution. Each part has its role:
- the core is "[xo-server](https://github.com/vatesfr/xo-server)", a daemon dealing directly with XenServer or XAPI capable hosts. This is where users are stored, and it's the center point for talking to your whole Xen infrastructure.

2
doc/built-in.md
View File

@ -5,6 +5,6 @@ This method is the default one. Creating a user is very simple:
1. Go into the Settings view, select "Users"
2. You can create a *user* or an *admin*, with his password (or generate one)
![](./assets/usercreation.png)
![](../assets/usercreation.png)
By default, a *user* won't have any permission. At the opposite, an *admin* will have every rights.

2
doc/full_backups.md
View File

@ -30,7 +30,7 @@ Just read twice the UI when you add a SMB store. If you have:
You'll have to fill it like this:
![](./assets/smb_fill.png)
![](../assets/smb_fill.png)
**PATH TO BACKUP is only needed if you have subfolders in your share.**

2
doc/github.md
View File

@ -12,7 +12,7 @@ When you got your `clientID` and your `clientSecret`, you can configure them in
Be sure to activate the plugin after you save the configuration (button on top). When it's done, you'll see a link in the log in view, this is where you'll go to authenticate:
![](./assets/githubconfig.png)
![](../assets/githubconfig.png)
## Debugging

2
doc/google.md
View File

@ -28,7 +28,7 @@ In Settings, then Plugins, expand the Google plugin detail and provide:
* a `clientSecret`, e.g `HTDb8I4jXiLRMaRL15qCffQ`
* the `callbackURL`, e.g `http://xo.company.net/signin/google/callback`
![](./assets/googleconfig.png)
![](../assets/googleconfig.png)
Be sure to activate the plugin after you save the configuration (button on top).

2
doc/invoices.md
View File

@ -4,6 +4,6 @@ You can find all your invoices in your member zone: https://xen-orchestra.com/#!
Get in the "Invoices" tab:
![](./assets/invoices.png)
![](../assets/invoices.png)
You can download your invoice in PDF format, by clicking in the "Export" row, on the invoice name with the PDF extension.

2
doc/ldap.md
View File

@ -4,7 +4,7 @@ XO currently support connection to LDAP directories, like *Open LDAP* or *Active
To configure your LDAP, go need to go in the *Plugins* section in the "Settings" view. Then configure it:
![LDAP plugin settings](./assets/ldapconfig.png)
![LDAP plugin settings](../assets/ldapconfig.png)
Don't forget to save the configuration, and also check if the plugin is activated (green button on top).

2
doc/plugins.md
View File

@ -6,7 +6,7 @@ Xen Orchestra plugins allow to extend features without rewriting the core of the
You can see your installed plugins in "Settings" then "Plugins" page:
![](./assets/plugins.png)
![](../assets/plugins.png)
Every plugin configuration should be done in the web interface.

2
doc/reseller.md
View File

@ -8,7 +8,7 @@ The reseller/partner program allows you to buy XOAs and to assign them to your f
You need to be registered first. Then go on [the partner page here](https://xen-orchestra.com/#!/partner) and click on the "Register button":
![](./assets/partner_request.png)
![](../assets/partner_request.png)
Now, you just have to wait for us to accept your request. As soon it's done, you access to your partner zone, [at the same partner page](https://xen-orchestra.com/#!/partner).

2
doc/resources_delegation.md
View File

@ -21,4 +21,4 @@ Groups can be created and managed in the "Groups" view inside "Settings" menu.
Any group can be edited as you like after its creation.
![](./assets/groups.png)
![](../assets/groups.png)

2
doc/saml.md
View File

@ -10,7 +10,7 @@ The first time a user signs in, XO will create a new XO user with the same ident
In the "Settings" then "Plugins" view, expand the SAML plugin configuration. Then provide the needed fields:
![](./assets/samlconfig.png)
![](../assets/samlconfig.png)
Save the configuration and then activate the plugin (button on top).

6
doc/self_service.md
View File

@ -8,7 +8,7 @@ The self-service feature is the possibility for users to create new VMs. That's
To create a new set of resources, go inside the "Self Service" section in the main menu:
![](./assets/selfservice_menu.png)
![](../assets/selfservice_menu.png)
### Create a set
@ -46,11 +46,11 @@ When you click on create, you can see the resource set and remove or edit it:
As soon a user is inside a resource set, it displays a new button in its main view: the gree icon with the "plus" sign:
![](./assets/selfservice_newvm.png)
![](../assets/selfservice_newvm.png)
Now, the user can create a VM with only the resources given in the set:
![](./assets/selfservice_createvm.png)
![](../assets/selfservice_createvm.png)
And the recap before creation:

4
doc/through_purchase_department.md
View File

@ -12,11 +12,11 @@ In means, there will be:
When you created an account as a purchaser (eg: "purchase.dept@example.com"), you need to go inside the member zone:
![](./assets/member_purchase.png)
![](../assets/member_purchase.png)
Now, **click on the Purchaser tab**:
![](./assets/purchaser_button.png)
![](../assets/purchaser_button.png)
Your request will be sent to us, and we'll unlock you the purchaser feature.

10
doc/updater.md
View File

@ -18,7 +18,7 @@ The updater is configurable directly in the web interface, or via the CLI.
By default for a new XOA, you'll have this icon in the top right:
![](./assets/updater_notreg.png)
![](../assets/updater_notreg.png)
It means your appliance is not registered. Click on this icon and follow the next step.
@ -26,7 +26,7 @@ It means your appliance is not registered. Click on this icon and follow the nex
Updates and trial will be available as soon as you registered your appliance. To register, use your https://xen-orchestra.com credentials you gave to download it previously (your email and your password):
![](./assets/updater_reg.png)
![](../assets/updater_reg.png)
#### Check for new versions
@ -36,19 +36,19 @@ The updater will check for new versions periodically. Nevertheless, if you want
If a new version is found, you'll have an upgrade button displayed:
![](./assets/regupdate.png)
![](../assets/regupdate.png)
**In case where the updater is updated itself, you should have to refresh manually the status panel!**
This could be done by clicking on the refresh white icon:
![](./assets/refreshupdater.png)
![](../assets/refreshupdater.png)
#### Proxy configuration
If you are behind a proxy, you can edit your proxy settings in this panel:
![](./assets/regproxy.png)
![](../assets/regproxy.png)
### From the CLI

10
doc/xo-server.md
View File

@ -10,27 +10,27 @@ As a daemon, XO-server is always up. In this way, it can listen and record every
Contrary to XenCenter, each Xen Orchestra's client is connected to one XO-Server, and not all the Xen servers. With a traditional architecture:
![](./assets/without-xo.jpg)
![](../assets/without-xo.jpg)
You can see how we avoid a lost of resources and bandwidth waste with a central point:
![](./assets/with-xo.jpg)
![](../assets/with-xo.jpg)
### Events
Legacy interfaces use the "pull" model, requesting data every "x" seconds:
![](./assets/noevent.jpg)
![](../assets/noevent.jpg)
It's **not scalable** and slow.
With XO < 3.4, we used events in this way:
![](./assets/semievent.jpg)
![](../assets/semievent.jpg)
But interface was still lagging behind the server. With XO 3.4, we got a full event system, allowing instant display of what's happening on your infrastructure:
![](./assets/fullevent.jpg)
![](../assets/fullevent.jpg)
### A proxy for your hosts