{"id":7853,"date":"2020-10-23T13:46:08","date_gmt":"2020-10-23T13:46:08","guid":{"rendered":"https:\/\/www.origo.io\/info\/stabile-documentation\/the-basics\/"},"modified":"2025-08-27T13:28:52","modified_gmt":"2025-08-27T11:28:52","slug":"stabile-basics","status":"publish","type":"page","link":"https:\/\/origo.systems\/info\/stabiledocs\/stabile-basics\/","title":{"rendered":"Basics"},"content":{"rendered":"\n<p>Origo OS manages infastructure running virtualized workloads and services. Origo OS supports management through a web client, declarative configuration and automation through the API or the CLI.<\/p>\n<p>Origo OS&#8217;s code-name during development was &#8220;Stabile&#8221;, which is inspired by the use of the word in Ursula K. Le Guin&#8217;s writings.<\/p>\n<h4>Origo OS is all about open infrastructure<\/h4>\n<p>If you have no desire to tinker with hardware, and mainly want to write your code, containerize your application and deploy it to some pre-configured Kubernetes environment, you should probably just look to some of the great cloud offerings out there.<\/p>\n<p>Origo OS tries to fill a gap in the market we feel there is for those who, for whatever reason, prefer to manage their own basic infrastructure on &#8220;bare iron&#8221;.<\/p>\n<h4>What Origo OS is and can do<\/h4>\n<p>Origo OS provides you with:<\/p>\n<ul>\n<li>A managed and scalable environment for deploying and running VM&#8217;s from virtual images using KVM.<\/li>\n<li>A model for assembling collections of pre-configured virtual images, compute, storage and networking ressources into declarative configurations packages which together describe how an application is deployed. We call these packages &#8220;Stacks&#8221;.<\/li>\n<li>A set of pre-built stacks for quickly running and easily managing standard Linux servers, including a Kubernetes stack, which will set up an auto-scalable Kubernetes environment in seconds.<\/li>\n<li>A PXE-boot environment for easy joining of hardware nodes<\/li>\n<li>Automated management of storage ressources using ZFS<\/li>\n<li>Automated management of network routing and network access to your VM&#8217;s using iptables, dnsmasq, proxyarp, Linux bridging, etc.<\/li>\n<li>Automated backup using ZFS storage snapshots<\/li>\n<li>Basic monitoring and reporting<\/li>\n<li>Simple metering suited for billing purposes<\/li>\n<\/ul>\n<h4>What Origo OS is not and cannot do<\/h4>\n<ul>\n<li>Origo OS is not a container orchestration platform. We may provide the ability to run containers directly on Origo OS hardware nodes sometime in the not-too-distant future, but for now, Kubernetes and containers run inside VM&#8217;s on Origo OS.<\/li>\n<li>Origo OS is currently in beta, and should only be installed and used for production environments in close cooperation with Origo Systems.<\/li>\n<\/ul>\n<h4>Components<\/h4>\n<p>If you have read this far, we suggest you strap in, and go ahead with reading about the main components of Origo OS.<\/p>\n<p>The Web Client and the API are organized around the ressources that Origo OS manages and orchestrates. They are:<\/p>\n<ul>\n<li><a href=\"\/info\/stabiledocs\/components\/#engines\">Engines and Nodes<\/a>: The hardware that a Origo OS installation runs on<\/li>\n<li><a href=\"\/info\/stabiledocs\/components#stacks\">Stacks<\/a>: Packaged applications that run on a Origo OS infrastructure<\/li>\n<li><a href=\"\/info\/stabiledocs\/components#servers\">Servers<\/a>: The VM&#8217;s that run on Origo OS nodes<\/li>\n<li><a href=\"\/info\/stabiledocs\/components#images\">Images<\/a>: The virtual images the VM&#8217;s boot from and use for storage<\/li>\n<li><a href=\"\/info\/stabiledocs\/components#network\">Networking<\/a>: Your VM&#8217;s connections to each other and the outside world<\/li>\n<li><a href=\"\/info\/stabiledocs\/components#users\">Users<\/a>: User accounts and their privileges<\/li>\n<\/ul>\n\n\n\n<div style=\"height:100px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Origo OS manages infastructure running virtualized workloads and services. Origo OS supports management through a web client, declarative configuration and automation through the API or the CLI. Origo OS&#8217;s code-name during development was &#8220;Stabile&#8221;, which is inspired by the use of the word in Ursula K. Le Guin&#8217;s writings. Origo<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":729,"menu_order":2,"comment_status":"closed","ping_status":"closed","template":"page-leftsb.php","meta":{"_acf_changed":false,"footnotes":""},"class_list":["post-7853","page","type-page","status-publish","hentry"],"acf":[],"featured_image_src":null,"featured_image_src_square":null,"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/origo.systems\/info\/wp-json\/wp\/v2\/pages\/7853","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/origo.systems\/info\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/origo.systems\/info\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/origo.systems\/info\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/origo.systems\/info\/wp-json\/wp\/v2\/comments?post=7853"}],"version-history":[{"count":50,"href":"https:\/\/origo.systems\/info\/wp-json\/wp\/v2\/pages\/7853\/revisions"}],"predecessor-version":[{"id":13185,"href":"https:\/\/origo.systems\/info\/wp-json\/wp\/v2\/pages\/7853\/revisions\/13185"}],"up":[{"embeddable":true,"href":"https:\/\/origo.systems\/info\/wp-json\/wp\/v2\/pages\/729"}],"wp:attachment":[{"href":"https:\/\/origo.systems\/info\/wp-json\/wp\/v2\/media?parent=7853"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}