Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

PaaS resources and PaaS resource pools overview

Like compute resources, platform-as-a-service (PaaS) resources are also infrastructure resources, but PaaS resources are infrastructure in the form of software elements that provide environments for hosting platform services. For example, a relational database management system (RDBMS) provides a software system to deliver a relational database service.

BMC Database Automation is the default resource provider for database resources. 

On-premise PaaS resources are onboarded and grouped into PaaS resource pools based on administrative policies. For example, PaaS resources might be pooled by the service levels (such as Platinum, Gold, and Silver) or the tenants they are intended to support. PaaS resources can be consumed only after they are added to a PaaS resource pool.

PaaS resource pools allow for easier management of the resources in those pools. They also let cloud administrators see the overall capacity of the resources in a pool. 

Currently, cloud administrators can create the following types of PaaS resource pools:

  • Database system pools—Pools of relational database management systems.  Because resources in BMC Cloud Lifecycle Management pools are considered interchangeable, all database management systems within the same pool must be compatible. BMC Database Automation determines compatibility. Loosely, database systems are compatible if they belong to the same product family and their versions are compatible. For example, two Oracle RAC 11.2g systems are compatible (irrespective of the number of cluster nodes in the system) while an Oracle single instance node is incompatible with an Oracle RAC system. 

After a cloud administrator creates network containers, PaaS resource pools are mapped to network containers. In this way, network resources provide the organization for PaaS resource pools. Multiple PaaS resource pools can be mapped to individual network containers. For example, a cloud administrator might map some higher-performing PaaS pools to a Production Environment network container, and lower-performing PaaS pools to a Pre-production Environment network container.

Cloud administrators can tag PaaS resource pools to automate placement decisions. For more information about tags, see Policy management overview.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments