Skip to content

Platform users guide

Visible to platform users only. Every platform user uses two-factor authentication. Roles are given with the invitation, and one person can hold several. Approvals that need two roles are given separately for each role, even by the same person.

Super admin

  • Everything. Administration → Users: add and invite platform users with roles, lock/unlock, archive (roles are cleared; invite back to return), and delete users who never accepted. Tenant users of every organization.
  • Settings: approvals, corporate domains, the password policy (length, character rules, forbidden characters, password history, name/email check), platform health period.
  • Audit log and the internal documentation.
  • Approves in any role nobody active holds, and previews or re-runs deployments.

Resource manager

  • Approval requests: names the tenant, places it on a platform and shared cluster, confirms resources and reserves the addresses. Approves resource and network changes.
  • Organizations: type, sales rep, KAM, contracts and balance confirmations. The sales rep directory.
  • Infrastructure: sites, server profiles, hosts, storage, networks, platforms, clusters, secrets, templates and capacity.

Support engineer

  • Approves corporate tenants when that approval is on. Assigns L2 VLANs and carries out network requests.
  • Infrastructure: as the resource manager. News: announcements, incidents and the service status on the front page.
  • Can be a user of corporate tenants.

Sales manager and key account manager

  • Sales manager: owns cloud organizations, invites new organizations, approves their tenants when sales approval is on, and changes the stage (poc → client).
  • Key account manager: looks after cloud organizations together with the sales rep and sees their organizations and tenants.

Infrastructure in short

  • All infrastructure data lives in the portal and is edited only in the portal: lists, details of the selected item, add and edit in dialogs.
  • Site: code, time, NTP/DNS, management hosts and ports. Tabs: platforms, clusters, IP subnets, hosts, storage, networks.
  • Server profiles: the hardware of a server model, including boot disk volumes and NICs (type, speed, model, port count and names). Check compares every host of a profile with it. A host added without a profile gets one detected or created from its hardware.
  • Storage: NFS (one target, volumes with exports and clients), iSCSI (several targets, port, volumes with devices and IQNs) or local (a device of a host).
  • Platform: datastores on storage volumes (VMs, images, files, backups) and networks on site networks (802.1Q VLAN or an existing bridge, with ranges). Clusters take hosts, datastores and networks of their platform.
  • Networks: type, VLAN, subnet, ranges and BGP: local AS, delegated subnets, then the route reflector, igw and (for exchange networks) egw peer groups, each with hosts generated from a range and a password from Secrets.
  • Secrets: BGP password sets (rrs, igw, egw), databases (name, user, password), OpenNebula (linux user and oneadmin passwords), ssh keys. New passwords follow the policy.