../_images/preview.png

Self Service via the Service Catalog

SCOPE_ENV

Scalr provides Cloud Deployment Self Service via the Service Catalog. This capability enables simple deployment of even the most complex cloud based services and applications at the click of a button. The Service Catalog is available to all types of users of Scalr including development teams, QA and non-technical end-users. In the case of non-technical end users Scalr can be configured to provide only the Service Catalog functionality by associating end user teams with restricted Access Control Lists. This results in end users seeing a very limited set of menu options.

../_images/sc_user_menu.png

The Service Catalog provides a list of predefined offerings that contain all the necessary configuration details to create Applications and deploy them to the Cloud. Users can select an offering from the list and then request to create an application from it. The user will be prompted for various input according to configuration before the Application is launched.

The Service Catalog itself is accessed from the Main Menu.

Clicking on SC1 itself opens the list of available offerings to allow users to request applications. “My Applications” opens the screen of already created applications.

Requesting Applications

The Service Catalog selection screen will, by default, show all available offerings. Offerings can optionally be grouped into Categories by the person who sets up the Service Catalog. Users can refine the list of available offerings by selecting a category from the search bar drop down and/or by typing filter text into the search bar.

../_images/sc_select.png

Click on the REQ button to start the Application creation dialogue.

In the simplest case users may only be asked to provide a name for the new application before reviewing and launching. At the other extreme the user could be asked to enter a number of choices and detail. The amount of input required is governed by the configuration of the offering and any Policies that are in place for the Environment.

The following screens walk through an example where significant user input is required.

Set the name and Project

../_images/simple_2_general.png

Choose the Cloud, Location and cloud specific parameters

Note that the input parameters are tailored to the chosen cloud.

M1 MAWS

Note how mandatory parameters can be highlighted in red if incomplete or invalid entries are submitted.

Review and Launch

Review the deployment parameters and then Create and Launch.

../_images/review.png

If any amendments are required click on the appropriate “STEP” tab on the left hand side to make the changes.

Managing Applications

After launching the application the “MY APPLICATIONS” will be displayed and will show the status of the Application request.

../_images/apps_prov.png

This screen can also be accessed from the MENU_ENV.

../_images/sc_user_menu.png

From here applications can be Started, Suspended, Terminated (Stop), Deleted and Locked. The Delete and Start buttons are only visible when an application is in a Stopped stated. The Lock button disables the the other available buttons to minimise the risk of accidentally changing the state of an application.

ACT1 ACT2

Click on the Application to see more details including a list of the Servers that are being launched and their IP Addresses.

../_images/app_svr_detail.png

Access to the dashboard for each server is through the DASH button alongside each server in the list. This gives access to full details of each server, including the Health statistics.

../_images/svr_dash.png