update readme

This commit is contained in:
Roni Väyrynen
2021-07-06 14:35:57 +03:00
committed by GitHub
parent 0179267574
commit 7e42ade20a

View File

@@ -9,24 +9,27 @@
Script to install/update [Xen Orchestra](https://xen-orchestra.com/#!/) and all of it's dependencies on multiple different Linux distributions. Separate script to be used on XenServer/XCP-ng host that installs a readymade appliance utilizing the same installer script.
#### What is Xen Orchestra?
### What is Xen Orchestra?
Xen Orchestra is a web interface used to manage XenServer/XCP-ng hosts and pools. It runs separately and one can manage multiple different virtualization environments from one single management interface.
Xen Orchestra is developed by company called [Vates](https://vates.fr/). They offer Xen Orchestra as a turnkey appliance with different pricing models for different needs. This is the preferred method of using Xen Orchestra product as each of the plans come with support. I highly recommend using the official appliance to support a great product and it's development now, and in the future.
Xen Orchestra is developed by company called [Vates](https://vates.fr/). They offer Xen Orchestra as a turnkey appliance with different pricing models for different needs and even a free version with limited capabilities. This is the preferred and only supported method of using Xen Orchestra product as the appliance goes through QA and each of the plans come with support. I highly recommend using the official appliance if you plan on using Xen Orchestra in production environment, to support a great product and it's development now, and in the future.
#### Why to use this script?
### Why to use this script?
If you're a home user/enthusiast with simple environment you want to manage but can't justify the cost of Xen Orchestra appliance.
If you're a home user/enthusiast with simple environment you want to manage but can't justify the cost of Xen Orchestra appliance and don't need the support for it.
Since Xen Orchestra is open source and majority of the features included in the official appliance are part of the sources, one can build it on their own. This [procedure](https://xen-orchestra.com/docs/from_the_sources.html) is even documented.
Since Xen Orchestra is open source and majority of the paid features included in the official appliance are part of the sources, one can build it themself. This [procedure](https://xen-orchestra.com/docs/from_the_sources.html) is even documented. Note that even though this method is documented, it's not supported way of using Xen Orchestra and is intended to be used only for testing purposes and not in production.
This script offers an easy way to install all dependencies, fetch source code, compile it and do all the little details for you which you'd have to do manually otherwise. Other than that, it follows the steps described in the official documentation. All source code for Xen Orchestra is by default pulled from the official [repository](https://github.com/vatesfr/xen-orchestra). Note that even though this method is documented, it's not supported and using this script has no support whatsoever from Xen Orchestra team. Any issue you may have, please report it first to this repository.
This script offers an easy way to install all dependencies, fetch source code, compile it and do all the little details for you which you'd have to do manually otherwise. Other than that, it follows the steps described in the official documentation. All source code for Xen Orchestra is by default pulled from the official [repository](https://github.com/vatesfr/xen-orchestra).
**This script is not supported or endorsed by Xen Orchestra. Any issue you may have, please report it first to this repository.**
The very first version of this script i did purely for myself. Now i'm mainly trying to keep it up to date for others who might already rely on it frequently. My intentions are to offer an easy way for people to get into Xen Orchestra without restricted features which could potentially help this piece of software to evolve and grow.
#### Preparations
### Preparations
First thing you need is a VM (or even a physical machine if you wish) where to install the software. This should have at least 4GB of RAM and ~1GB of free disk space. Having more CPU does speed a the build procedure a bit but isn't really a requirement. 2vCPU's on most systems are more than fine.
@@ -46,7 +49,7 @@ I suggest using a fresh OS installation and not to use the VM for anything else
If you plan on using the prebuilt appliance VM for XenServer/XCP-ng, see the appliance section below.
#### Installation
### Installation
Start by cloning this repository to the machine you wish to install to.
@@ -120,7 +123,7 @@ deb:
- gnupg (debian 10)
```
#### Appliance
### Appliance
If you need to import an appliance directly to your host, you may use xo-appliance.sh script for this. It'll download a prebuilt Debian 10 image which has Xen Orchestra and XenOrchestraInstallerUpdater installed.
@@ -146,12 +149,12 @@ This image is updated weekly. Latest build date and MD5 checksum can be checked
Built and tested on XCP-ng 7.x
#### Tests and appliance image
### Tests and appliance image
I run my own little implementation of automation consisting of ansible and virtual machines to test the installation on regular bases with CentOS 8, Ubuntu 20 and Debian 10. Test results are visible in badges on top of this readme.
Appliance image is also built by me and distributed from webservers i maintain.
#### Contributing
### Contributing
Pull requests and issues (either real issues or just suggestions) are more than welcome. Note that i do not wish to make any modifications to Xen Orchestra source code as part of this script.