Creating a django - Python Web framework 1.5 on RHEL 5.9 service offering
This topic describes the tasks that you must perform in BMC Cloud Lifecycle Management to create the service offering that the end user can then use to provision the application infrastructure (for example, an OS and an application package).
It includes the following topics:
To create the service and the service offering
In the BMC Cloud Lifecycle Management Administrator console, you must add a service and a service offering.
For django service blueprint, create a service and service offering based on the available deployment model. The django ZipKit supports single-tier service deployment model. In the single tier deployment model, django is installed on one instance of a server.
To create a service
To create a service offering
To make the provisioning request
- Access Workspaces > Service Instances to display the Service Instances workspace, and click New Service Request.
In the New Service Request dialog box, click the server provisioning service you want to display the Submit Request dialog box.To complete the Service Request for CMS Drupal 7, specify the following Parameters:
Parameter
Description
Django DB Name
Django Database Name
Django Project Name
Django Project Name
MySQL Port No
MySQL User Defined Port No, eg. 3309 etc
MySQL Root Password
MySQL Root User Password to Set
Confirm
MySQL Root User Password to Set
Project Password
Django Admin Password
Confirm
Django Admin Password
Project Username
Django Admin User
- Enter the data in the required fields to complete the request for an instance of the service request. You can click Next to review the details.
- Click Submit. The request is added to the Pending Activity list in the Service Instances window.
The request status is displayed in the Pending Activity list of the Service Instances window. You can double-click on the service request to see its detailed information.
For more detailed procedures, see Requesting-cloud-services and Requesting-cloud-services-in-the-legacy-console.
To validate the provisioned components
After provisioning the blueprint, you can validate the django components setup in your environment.
Component name | How to verify | Results |
---|---|---|
To verify django admin URL | To verify django installation, visit following URL: http://ServerIPAddress/ProjectName/admin Note: Edit the URL as per your environment. | This displays django - Python Web framework admin console login page.
|
To verify django on provisioned machine | To verify django on provisioned machine, run the following command: python -c "import django; print(django.get_version())"
| This command displays django version. |
To verify MySQL | To verify MySQL on provisioned machine, run the following command: mysql -v | This command displays MySQL version. |
To verify Apache Web Server | To verify Apache Web Server on provisioned machine, run the following command: httpd -v | This command displays Apache version. |
Where to go next
Once you have created the service offering, the cloud end user can request a service offering from the My Cloud Services Console. To view a list of tasks the cloud end user can perform to manage your cloud services, see Managing-cloud-resources in the BMC Cloud Lifecycle Management online technical documentation.