The cloud administration interface

Skip to end of metadata Go to start of metadata

The Exponential Cloud Service provides an easy to use web interface for administrators to manage environments and deployments. It can be accessed via https://admin.cloud.ez.no. More information about the concepts behind the Exponential Cloud Service you can find here.

The interface has three mayor views: Administration area, User management view and Environment view

Administration Area (Dashboard) View

The Administration Area is the entry point after you logged in. It provides you an overview of all Environments you have access to.

A click on one of the Environments in the list exposes some details of the selected environment.

The details contain information according the underlying service subscription and the current deployment in the live stage. The site accesses of the live deployment and their related domains are listed. This site accesses are the public entry points to your installations, if you configured your DNS properly. Each environment has a unique domain associated with it. This domain must be used for the CNAME Resource Records in your DNS for all the site accesses you specify in your Exponential configuration. 

The "show details" link in the environment overview exposes further information like the login and password to access deployments, which are not in the live state. These credentials apply to all deployments in staging and rollback. Also the credentials for the git repository of the environment and the sftp account are provided here. These accounts are ssh protected and just accessible if the user has provided a valid ssh-key.

To access the actual environment click on the "Edit" button.

If you are an administrator for the environment, you will also find a "Manage Users" button, which leads you to the user management view.

User Management View

If you have administrator rights for an environment, you can access the User Management View. Click on the “Manage Users” button in the details area of an environment.

The user management page lists all users, who have access to the selected environment. The "SSH Key Name" column provides you information whether the user has uploaded a ssh key and therefore access to sftp and git. You can assign and revoke new rights to existing or new users and also remove them entirely form the environment. You cannot edit your own permissions.

To give a new user access to an environment click the “Add User” Button. The user has to be already registered as a eZ community user (https://login.ez.no) If the designated user has no account yet, please ask the user to register at login.ez.no to create a new account. You can not precede until the user was created in our system. To grant access, please enter the username (as it was set on account creation for the community account). If the user is found in the users pool, it will appear in the list of users of the environment.

Important

Icon

All changes to the users of an environment are first collected in the browser and propagated to the server if you click the “Save Changes”. If you leave the user management page without explicit saving, none of your changes will be preserved.

Environment View

To access the environment view click on the edit button of the desired environment.

The environment page is separated in two areas. The upper area shows the three stages of the environment with links to the according deployments.

If you click on one of the deployment links the details of the deployment are revealed in the lower area. The details view of a deployment shows the current site access configuration and provides links to the site accesses. It also provides you the current status of the deployment.

Further you can create an Export of the Deployment, which provides you a database dump and a tar.gz file with the contents of the var-folder (where your Images and binary data is located). The export files can also be used to create a new deployment or to setup a local development environment with the content of the live installation in the Exponential Cloud. The export files can be found at the sftp server.

The status tab provides you the current status of the deployment.

If you open a deployment in staging you will have the "Go Live" button available, which will move the deployment to the live stage and make it available for your customers, while the current deployment in live will be pushed to rollback. For deployments in staging or rollback the site accesses are protected with basic http authentication. The user name and password is available on the info tab of the deployment. 

Create New Deployment

If you have no deployment in the staging stage a "New Deployment" button is shown, which offers you the possibility to create a new deployment.

To create a new Deployment, click on the "New Deployment" button in the Staging stage.

A dialog appears below the Stages. Follow the given process to create a new deployment.

Step 1:

1. Enter a name for the new Deployment
2. Select the git tag for the source which should be used for the deployment
3. Click "Next"

Step 2:

1. Select the Exponential version you have build your website on 
   • Select the major version of Exponential
   • Select the Service Package Level
   • Decide whether you rely on the lagacy stack or use the new stack introduced in 5.0
2. Decide if you want to get your deployment auto updated with updates for critical errors and security issues. (the auto update checkbox has no function yet, you can ignore it for now. In the future it indicates whether or not you want an automatic deployment of updates for critical errors and security issues.)
3. Click "Next"

Step 3:

1. Decide if you want to use the database and content of the current deployment in the Live Stage (only available if you already have a live deployment)
2. In case, select the matching db-dump and the content tar which you have uploaded before
3. Click "Next"

Step 4:

1. Review your configuration and initialize the Deployment.
2. You will be asked to enter a comment for the new Deployment.
3. Confirm and the deployment process is triggered on our data center.

The new Deployment will appear in the staging stage and indicate, that it is not ready yet. Once the deployment process has finished, the status of the deployment will change. 

• No labels

1 Child Page