1 |
8723c9b2
|
hq
|
# Origo OS
|
2 |
95b003ff
|
Origo
|
|
3 |
f8711929
|
Origo
|
<p style="text-align: center;"><img src="./static/img/logo-icon.png" alt="Stabile Logo" width="80"/></p>
|
4 |
|
|
|
5 |
8723c9b2
|
hq
|
Origo OS, also known by its code name, Stabile, is a open source software platform for infrastructure orchestration. It is distributed in the hope of being useful, but without any warranty what so ever.
|
6 |
95b003ff
|
Origo
|
|
7 |
8723c9b2
|
hq
|
This is the source code distribution of Origo OS, and is intended for developers who want to contribute or explore the inner workings of the system. For general product information please see https://www.origo.io.
|
8 |
95b003ff
|
Origo
|
|
9 |
6479cd73
|
hq
|
The authoritative repo is: https://gitlab.origo.io/origosys/stabile.
|
10 |
|
|
The repo is also mirrored to: https://github.com/origosys/stabile.
|
11 |
3e3d0999
|
hq
|
|
12 |
d24e3aeb
|
hq
|
If you want to install the binary release and help us test the software, please read the EULA (https://www.origo.io/info/stabiledocs/licensing/origo-os-eula), the documentation (https://www.origo.io/os/), before proceeding with the quick-start guide (https://www.origo.io/os/single-node-quick-start). Be sure to provide feedback, so we can fix problems and bugs.
|
13 |
95b003ff
|
Origo
|
|
14 |
8723c9b2
|
hq
|
In short Origo OS aims to make it easier to manage VM's, storage and networking in an organized manner. Origo OS is also useful for application distribution, since preconfigured collections of virtual servers can be packaged in a simple format and distributed.
|
15 |
95b003ff
|
Origo
|
|
16 |
8723c9b2
|
hq
|
* Origo OS is based on Ubuntu Linux
|
17 |
|
|
* Origo OS is designed to run on x86 hardware
|
18 |
|
|
* Origo OS is packaged and distributed to Engines as debian (.deb) packages for Ubuntu 18.04
|
19 |
95b003ff
|
Origo
|
|
20 |
8723c9b2
|
hq
|
In an Origo OS-managed collection of servers, one server functions as the **administration server**
|
21 |
95b003ff
|
Origo
|
|
22 |
|
|
The administration server handles the following tasks:
|
23 |
|
|
|
24 |
|
|
* Orchestrates compute, networking and storage ressources
|
25 |
|
|
* Provides API and web UI
|
26 |
|
|
* Routes network traffic to and from the compute nodes
|
27 |
|
|
* Provides boot services for the compute nodes
|
28 |
|
|
* Provides shared NFS storage for the compute nodes
|
29 |
|
|
|
30 |
|
|
The other servers in the collection function as **compute nodes**.
|
31 |
|
|
|
32 |
7ac77ddd
|
hq
|
The compute nodes are stateless PXE-booted servers. Once booted they auto-join the "cloud" and make their ressources available for running virtual servers. A compute node may have local storage attached, typically an SSD or NVMe. A compute node without local storage uses shared storage provided by the administration server via NFS.
|
33 |
95b003ff
|
Origo
|
|
34 |
|
|
The compute nodes handle the following tasks:
|
35 |
|
|
|
36 |
|
|
* Run virtual servers
|
37 |
|
|
* Report CPU, memory and storage usage to the administration server
|