How an engagement works¶
A Claugine deployment follows the same sequence every time.
- Prepare the hardware and the landscape. You have, or acquire, the hardware that will run your clients' virtual machines, and prepare the landscape: storage presenting its resources, a network ready to carry traffic, delegated subnets, and hosts reachable over IPMI. See Infrastructure.
- Plan it together. We go through the technical details of the implementation with you and plan the inventory.
- Install everything automatically. Claugine installs the entire service from green field: your own portal first, then, from the inventory entered in it, the hosts' operating systems, OpenNebula and VyOS, in a fully automated way.
- Run it from the portal. From then on the portal is the only interface for your cloud — for maintaining the platform, for your team and for your clients' projects.
What the portal assumes today
Claugine is not tied to one country. Every organization has a country, and its tax ID follows it: in Kazakhstan the IIN or BIN, in the United Arab Emirates the TRN, elsewhere the country's tax or registration number. The portal's home country and the other countries it takes are a setting (Settings → Customer → Countries); the city is typed in. The portal's time zone defaults to Asia/Almaty and is set when the portal is installed; the corporate e-mail domains are a setting (Settings → Customer → Customers). See the Portal reference.