Overview¶
Claugine has two parts that work as one system.
- The platform
- OpenNebula front ends with their clusters of hosts, built on your infrastructure and its network underlay: the host operating system, OpenNebula for cloud management and VyOS for routing, all installed by Claugine. See Infrastructure and Platforms.
- The portal
- The only interface to the platforms. It deploys and maintains them (underlay management) and provides IaaS to end customers (service management). See Portal.
How the docs are organized¶
| Section | What it covers |
|---|---|
| Infrastructure | The underlay, hardware and other resources needed to deploy a platform |
| Data flows and structures | Every object, term, data structure and how the components interact |
| Platforms | Where Claugine starts: platform types, sites, clusters, datastores |
| Portal | The interface: underlay management and service management |
| Running the portal | Installing the portal, its architecture, updates, backup and restore |
| Roles | The full workflow of requests and approvals, and each role |
| Platform services | What projects get: resource pools, storage, network |
What you need, and what Claugine does¶
| You provide | Claugine provides |
|---|---|
| Hardware and landscape: storage presenting its resources, a network ready to carry traffic, delegated subnets, hosts reachable over IPMI | Installation of the entire service from green field, fully automated: host OS, OpenNebula, VyOS |
| Time to agree on technical details | An inventory that describes your platform |
| Your own instance of the Claugine portal | |
| Automated day-2 and day-3 operations through the portal |
Once the platform is deployed, the portal is the only interface you need for your cloud.