Platform users guide¶
Visible to platform users only. Every user uses two-factor authentication. Roles are given with the invitation, and one person can hold several. A person holding several roles approves once for all of them.
Super admin¶
- Everything. Administration → Users, tabs Platform and Organizations: invite users with their roles, add users to invite later (when Settings → Customer → Customers → New users allows it), send or resend invitations, lock/unlock, tick roles in the user's row, archive (roles are cleared; invite back to return). Users are never deleted. The last active holder of a role can't be locked or archived.
- The super admin role is given or taken through a request that other super admins confirm within 48 hours: 2 must agree with 2 or 3 super admins, 3 with 4 or more, the one asking counting as one (see Roles and organizations). Confirm or decline on top of Administration → Users → Platform.
- Act as (on the dashboard, next to the greeting): see the portal as any user who is not archived. It is read only: nothing is carried out or saved; Stop acting in the banner ends it.
- Settings: Customer (the provider: name, e-mail, Customer Portal and Admin Portal (kept, not used yet; the certificate carries the Customer Portal's name), the logo, browser icon and colours; the internal domain of the hosts, new users and corporate domains; countries; approvals), Security (one row per password rule: length, password history, character rules, allowed and forbidden symbols, personal data; the igw ssh port range), Mail (the sender, DKIM, e-mail to organization users and to platform users, the mail sender public IPs, the DNS records and what DNS has, the e-mail templates in HTML), Reports (the e-mail reports of each role), Backups (the portal and the platforms, to a local folder and/or an S3 bucket), Platforms (the baseline: the base OS, OpenNebula and FRR releases of every platform, the OpenNebula repository; the installation media for host deployments), Portal (the nodes with Update OS, Update portal, Change encryption key and Switch over, automatic updates and the licence; lists, history, timers).
- Logs and Tasks.
- Approves in any role nobody active holds, and previews or re-runs deployments.
Resource manager¶
- Approval requests: names the project, places it on a platform and shared cluster, confirms resources and reserves the addresses. Approves resource and network changes. Moves a project to another organization (Edit project → Move to another).
- Organizations: approves registrations and assigns the platform users; edits an organization (short name, sales rep, KAM, notes), archives it, orders a project for it (+ Project). Adds the organization's users. The sales rep directory.
- Projects: edits a project (short name, stage, status, review date, project admin, support engineer, notes).
- Infrastructure: sites, hardware profiles, hosts, storage, networks, platforms, clusters, secrets, templates and capacity.
Support engineer¶
- Approves corporate projects when that step is ticked in Settings → Customer → Approvals; projects are provisioned by themselves after the last approval. Sets the VLAN of L2 channels and changes the size of internet gateways.
- Is set on each project; a project without its own takes the organization's.
- Infrastructure: as the resource manager. News: announcements, incidents and the service status on the front page.
- Can be a project admin or project user of corporate projects.
Sales manager and key account manager¶
- Sales manager (the organization's manager): full rights over the organizations they are set on and all their projects: edits the organization, orders its projects, adds, changes and removes their resources, deletes a project, invites, locks and unlocks its users and gives the project admin role. Adds new organizations and becomes their sales rep. Approves their projects when sales approval is on and a project moved to their organization, and changes the stage (poc → client). Does not change an organization's sales rep, key account manager or resource manager, and does not archive users. A sales rep with an e-mail of a corporate domain can also be the (optional) sales rep of a corporate organization.
- Key account manager: the organizations they are set on are read only to them, except that they invite, lock and unlock the organization's users and add, change and remove the resources of its projects. Does not order or delete projects.
- Both see the resource manager's dashboard, for their own organizations and projects. Both are set on the organization, not on its projects. The rights side by side: What each role may do.
Weekly reports and Analysis¶
- Weekly reports (Settings → Reports): Super admin, Support, Sales (manager and KAM) and Resources, each to every holder of its roles with an e-mail address (blocked and archived users left out). A support engineer, a manager and a KAM get their own organizations only; the super admin and the resource manager get everything. Each starts with its Totals (counts, with what was new, updated and archived in the period); the tables of each report: Reports.
- Analysis (Enterprise; a menu item below Projects): the super admin and the resource manager see all organizations, the support engineer, the manager and the KAM their own. Summary is the Dashboard's view with the Platforms, Backups and Portal updates tables; Usage shows each project's connections and resources as in use / allocated, and is e-mailed as PDF, CSV or XLSX. See Analysis.
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.
- IP subnets (a site's tab): the public and private ranges projects get addresses from. The type is detected from the address; a subnet can't be changed once added (only its max allowed prefix, and the routing of one not routed by BGP) and is deleted only while unused. Details: Network design.
- Hardware profiles → Servers (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. A verified profile also names its boot storage, the firmware versions a host must have, its BIOS settings and the iLO services left on. Boot storage: how a host's boot device is split when it is deployed (the installation brings standard).
- Hosts: Deploy (a planned host) and Reinstall (a host in use) install a host from scratch; Retire (super admins) moves its VMs away, removes it from OpenNebula and shuts it down. See Deploying a KVM host and Retiring a KVM host.
- 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, the IP subnets an exchange network carries (several, of its type), then the route reflector, igw and (for exchange networks) egw peer groups, each with hosts generated from a range and a password from Secrets. A core-lm network (one per site) is the live migration network of the hosts.
- Secrets: BGP password sets (rrs, igw, egw), databases (name, user, password), OpenNebula (linux user and oneadmin passwords), ssh keys. New passwords follow the policy.