Overview of the OpenStack Provider
OpenStack is a global collaboration of developers and cloud computing technologists that produces the open source cloud computing platform for public and private clouds.
This topic contains the following sections:
Product overview
The OpenStack integration with BMC Cloud Lifecycle Management enables you to leverage the cloud computing services of the OpenStack Provider from the BMC Cloud Lifecycle Management Administration Console. You can use BMC Cloud Lifecycle Management to provision infrastructure from OpenStack.
With OpenStack Provider integration with BMC Cloud Lifecycle Management, you can perform the following actions:
- Onboard and offboard a Logical Data Center.
- Register an OpenStack Provider instance.
- Provision new VMs that are based on OpenStack templates or a customized template.
- Place VMs on specific subnets.
- Start, stop, shut down, suspend, and resume provisioned VMs.
- Modify memory and CPU values of provisioned VMs.
- Add disks for provisioned VMs.
- Decommission provisioned machines.
- Extend the commission length of provisioned VMs.
- Install software on provisioned VMs (both pre- and postprovisioning).
- Add a local user on provisioned VMs (both pre- and postprovisioning).
- Manage tenant or user quota in BMC Cloud Lifecycle Management.
- Create multiple OpenStack accounts.
Use the OpenStack public cloud (Cloudwatt).
Allow SSH Keypair during provisioning.
- Use the Self Service feature. See Managing-the-OpenStack-service-offerings and Managing-OpenStack-services for details.
- Monitor server and tenant details of the OpenStack Provider by using the Value Dashboard. See Monitoring-server-and-tenant-usage for details.
- Request and manage OpenStack services and servers using either the legacy or the new My Cloud Services Console. See Managing-the-OpenStack-service-offerings, Managing-OpenStack-services and Managing-OpenStack-servers for details.
Supported releases of OpenStack
The following components of the OpenStack releases (along with the respective API details) are supported in BMC Cloud Lifecycle Management 4.6.00 and its service packs and patches:
OpenStack | OpenStack | API version | Supported New in 4.6.07 | Supported | Supported |
|---|---|---|---|---|---|
Keystone | Kilo | v2 | Yes | Yes | Yes |
Juno | v2 | Yes | Yes | Yes | |
Liberty | v2 | No | Yes | No | |
Mitaka | v2 | No | Yes | No | |
Icehouse | v2 | Yes | No | No | |
Ocata | v3 | Yes | No | No | |
Nova | Kilo | v2 | Yes | Yes | Yes |
Juno | v2 | Yes | Yes | Yes | |
Liberty | v2 | No | Yes | No | |
Mitaka | v2 | No | Yes | No | |
Icehouse | v2 | Yes | No | No | |
Ocata | v2 | Yes | No | No | |
Glance | Kilo | v2 | No | Yes | Yes |
Juno | v2 | No | Yes | Yes | |
Liberty | v2 | No | Yes | No | |
Mitaka | v2 | No | Yes | No | |
Icehouse | v2 | Yes | No | No | |
Ocata | v2 | Yes | No | No | |
Cinder | Kilo | v2 | Yes | Yes | Yes |
Juno | v2 | Yes | Yes | Yes | |
Liberty | v2 | Yes | Yes | No | |
Mitaka | v2 | Yes | Yes | No | |
Icehouse | v2 | Yes | No | No | |
Ocata | v2 | Yes | No | No |
High-level tasks for setting up an OpenStack Provider
The following sections lists the high-level tasks that you must complete to set up an OpenStack Provider for a private and public cloud and initiate an OpenStack service instance.
Process stage | Role | Task |
|---|---|---|
Cloud Administrator | You must install or upgrade the OpenStack Provider first before using it. Note: Before installing or upgrading an OpenStack Provider ensure that the prerequisites are met. See Prerequisites-for-installing-the-OpenStack-Provider for details. | |
Cloud Administrator | Typically you perform the activities of the setup phase of your OpenStack Provider only once. These activities include configuring the OpenStack Provider and setting up the OpenStack private or public cloud account credentials details in the BMC Cloud Lifecycle Management to auto-onboard the OpenStack Snapshots and Images as DML entries in the BMC Cloud Lifecycle Management application. Note: For the custom Glance images, you must connect to the OpenStack server and set a property name os_name in the Glance image. See Note for setting os_name property. | |
Cloud Administrator | After you have configured the OpenStack account, you must configure the following resources in BMC Cloud Lifecycle Management to provision an OpenStack service:
| |
Cloud Administrator | In this final phase, you prepare and initiate the service offering request, as described in the following topics: | |
Cloud Administrator, Tenant Administrator, End User | You can request an OpenStack cloud service from the BMC Cloud Lifecycle Management – by using the new My Cloud Services Console or the legacy My Cloud Services Console See also Considerations for requesting an OpenStack service on behalf of another user. | |
Cloud Administrator, End User | You can perform several operations on your OpenStack services (start, stop, shut down, decommission, restart, share, and transfer ownership). Note: You can only start, stop, shut down, decommission and restart the OpenStack services by using the new My Cloud Services Console. See Managing cloud services for details of these operations.
| |
Cloud Administrator, End User | You manage your OpenStack servers by using the new My Cloud Services console and the legacy My Cloud Services Console. For details, see the following sections in Managing-OpenStack-servers :
Note: Removing a disk, and suspending and resuming an OpenStack server are not supported by the new My Cloud Services Console. As a best practice, perform these operations by using the legacy My Cloud Services Console. |
OpenStack construct mappings
The following table lists BMC Cloud Lifecycle Management objects and describes how they correspond to OpenStack constructs:
BMC Cloud Lifecycle Management object mappings for the OpenStack Provider
BMC Cloud Lifecycle Management object | OpenStack construct | Notes |
|---|---|---|
Logical Data Center | Tenant, project | This object is represented by a project in the OpenStack Provider. |
Network/Subnet | Network | This object is represented by the network/subnet defined in the OpenStack environment. |
Logical network | Network | This object is represented by the network defined in the OpenStack Provider. |
Virtual guest | OpenStack virtual machine (VM) | None. |
IP address | IP address | None. |
System disk | Root disk, Ephemeral disk, Volume | System disk is created with the combination of Root disk and Ephemeral disk defined as part of Flavor. Volumes attached to VMs in the OpenStack Provider are also created as System disk in BMC Cloud Lifecycle Management. |
Operating system | Operating system | The OpenStack Provider creates VMs through available Images. The operating system properties must be defined as metadata of the Image. |
Server network interface | Network Interface Cards (NICs) | None. |
Limitations
- BMC Cloud Lifecycle Management does not synchronize modified or deleted OpenStack templates.
- When you deregister an OpenStack Provider instance, the OpenStack installable resources are not removed automatically.
- Registering an OpenStack Provider instance with an incorrect OpenStack user name and password does not produce an error.
- Any operation that exceeds the poll time that is specified during provider registration fails in BMC Cloud Lifecycle Management, but is updated in the OpenStack Provider. In this situation, resources are not synchronized.
Yes