Organization admin guide¶
1. Register the organization¶
- Open Register. Enter your email, a password (the policy is shown under the field), your name, mobile number (international format, starting with "+"), city (typed in) and photo, the organization's legal name, its country and its tax ID (in Kazakhstan the IIN or BIN).
- Confirm your email with the link the portal sends. The link is valid for 48 hours. The organization is created and you are its admin.
- The registration then waits for approval: a resource manager first, then the sales rep when sales approval is on. Nobody of the organization signs in until it is approved; you get an e-mail when it is.
- If the tax ID is already registered in that country, your registration becomes a join request to that organization's admins instead.
- If the provider's staff invited you, register through the invitation link. You don't need to confirm your email, and the organization is approved from the start.
2. Your organization area¶
| Dashboard | Projects (approved, deployed, waiting), resources in force, running VMs, users, join requests and the latest events. |
| Projects | Your projects, and ordering a new one. |
| Users | Users of the organization, their roles and states, invitations and join requests. |
| Keys | The organization's ssh public keys. The default key goes to the gateway of every new project. |
| Tasks | The work on your projects: deployments, network changes, deletions, checks. |
| Logs | Everything that happened in the organization. |
Every list works the same way: a filter at the top, the add button on the right, and the details of the selected row under the list.
3. Order a project¶
| Short name | 4–15 lowercase latin letters, digits and -, starting with a letter, unique in the organization. The project ID (_<org>_<name>, without -) is built from it and can't be changed later. |
| Type | Cloud. Corporate organizations can also order corporate projects. |
| Stage | POC or client, with the review date. A POC is reviewed within 3 months. |
| Project admin | A user of the organization (in a corporate organization, also a platform user). Gets the project's access details when it is ready. |
| Resources | Site and cluster, vCPU, RAM, storage (defaults 4 / 16 GB / 100 GB), GPU bundles on GPU clusters, backups. |
| Connections | At least one of internet, corporate network (corporate organizations only) and external L2 channel. For the internet, also the speed, the main public prefix and any additional prefixes, each with its base subnet (or auto). |
| Notes | Anything the provider should know. |
With the internet the order also chooses the project's gateway: advanced (the default), the platform's native router, or your own. With your own, nothing is created for you: the address is reserved and your virtual machine takes it.
GPU capacity is ordered in bundles. One bundle is one GPU card together with a fixed share of its server's cores and memory, so a bundle always fits on the machine the card is in. The order form offers the bundles that are still free on the cluster, and the vCPU and memory follow from the number of bundles.
You can cancel an order while it waits for approval. When the last approval is given, provisioning starts by itself and the project page shows its progress; Provision again appears only when it could not start or failed. The project admin then gets the access details by e-mail, and you get the same e-mail when you are not the project admin. See Ordering and provisioning.
4. Users¶
- Invite a person by email and give the role in the invitation: organization admin, read only, or project admin of chosen projects. The person sets a password, photo and two-factor authentication when accepting.
- Resend invitation sends a new invitation to someone who has not accepted one yet.
- Roles are the checkboxes in the user's row: organization admin, project admin (ticking it asks for the projects) and read only.
- Lock / Unlock stops or restores a person's sign-in without changing anything else.
- Archive removes someone: they lose all roles and can't sign in. Invite back returns them, with only the roles given then. Users are never deleted.
- Your organization's sales rep and key account manager can also invite, lock and unlock its users.
- Join requests: users who registered with your organization's tax ID. Accept only users you know.
- On a project page, Invite a user gives a person a role in that project: project admin or project user. A project admin can invite project users only.
- Two-factor authentication is required for every user. Each person sets it up with an authenticator app when they first sign in, and can add passkeys on their profile page (see Project user guide).
5. Run your projects¶
- Resources: request more or fewer vCPU, RAM, storage or backups. The change is applied after approval. Never below what the project uses now: the form shows the usage next to each field, and a resource pool can be removed while VMs are still on it: the request lists them and asks to confirm their deletion. Each resource pool shows its quota and, beside it, what is in use, with a bar that fills as the pool fills; the storage figure is broken into virtual machine disks, images and files. The backup allowance belongs to the site, not to a single resource pool: it is shown and changed on the first resource pool of each site, and the change applies to every pool the project has there.
- Storage split: divide the storage between VM disks, images and files at any time, without approval.
- Networks: request another internet bandwidth (10–1000 Mbps), extra public networks or their removal, replace the main network (for a new public network or a new main one you may choose its base subnet, or leave auto), change corporate prefixes, bind an L2 channel to a network. With resources on two sites, add an internal L2 channel between a network on each site, without approval.
- Access (the project's secrets, kept encrypted; every look is logged): the OpenNebula console link (FireEdge under the platform's public name, e.g.
https://one-dc1.example.com/fireedge/sunstone; the site in the project's resource pools links to it), the OpenNebula admin — show its password, Set a new password (OpenNebula changes too) or Keep the current password (checked by logging in to OpenNebula; nothing is changed) — and the igw login: address, ssh port, user and password. - igw configurations (VyOS igw): keep the running configuration, edit a saved one (saved as a new one), apply one — over ssh, where the portal first keeps the running configuration and commits with an automatic rollback: unless you press Confirm in time (default 60 seconds; VyOS counts whole minutes), the igw goes back by itself — or by making the igw again with it. To roll back, apply the configuration kept before.
- Gateway keys: add or remove the ssh keys of the project gateway.
- Log: every operation on the project: order, approvals, deployment steps, password views and changes.
- Delete a project: press Request deletion. It is carried out after approval. Organization admins ask for it; project admins manage the resources of their projects but cannot delete them. Who may do what: Roles and organizations.