Admin portal & deployment portal
Admin Portal & Deployment Portal
With the cloud-native technology stack come the features required to maintain an installation of our software via a unified web portal UI. Partners and clients can manage the implementation using their own interfaces or use our portal to call various APIs and perform the required functions. The web-based portal can be used with any public / private cloud or on-premises implementation.
The portal currently serves two user communities:
- Cluster administrators: at a large implementation of platform providers, the cluster admin manages deploying the software to the tenants.
- Tenant administrators: administrators at the individual tenant (or administrators at small or on-premises installations) manage their own deployment.
A ‘Deployment’ is a tenant-level instance. It has a unique Deployment ID, for which the tenant gets licensed. To consume any LumenVox product a Deployment must be created with a Deployment ID, and this can be instantly accomplished via the portal.
For reasons of security and segregation of duties between the two types of users, we offer two interfaces:
- Admin Portal – for the cluster admin, who sets up each licensed tenant with their connection strings, encryption, and passwords to services and databases.
- Deployment Portal – for the tenant admins, who can only access their own deployment. Within it they can customize the default configuration by tweaking parameters and options, verify that all services are up and running, and run diagnostics if there’s a problem.
The Admin Portal has an access point into the Deployment Portal, via a Deployment Portal button, available in Deployment Details page.
In some implementations, the cluster admin might be the one performing administration for the deployments. In other implementations it will be more appropriate for the cluster admin to have no such access. We make it easy for IT to control this by firewall rules, white-listing access by using the host site name format: ingress_host_name.client_hostname_suffix
For example:
- admin-portal.testmachine.com
- deployment-portal.testmachine.com
Customers can choose the ports that are exposed externally. The two portals are exposed on separate (configurable) ports to aid with firewall and access configuration.
If using self-signed certificates, then the following steps must be taken should you wish to view the portal from your desktop. Please see instructions in http://lumenvox.capacity.com/folder/742e9d30-05e6-4787-b79e-4737c13fda36.