Service blueprints overview
This topic provides an overview of service blueprints. The following topics discuss two key elements of service blueprints:
What are service blueprints?
When contractors build houses, they use blueprints designed by an architect to guide them. The blueprints typically contain a variety of specifications: one house might have three bedrooms and two baths, while another house might have only one bedroom and one bathroom, and so on.
In the same way, service blueprints enable you to design, manage, and build the underlying components, operations, and resource sets that define services. The service blueprint for a small application might have all its components (for example, web server, application server, and database server) deployed on one virtual machine (VM). But the service blueprint for a large application might distribute these components among a mixture of VMs and physical systems (for example, the web server and application server might be on VMs while the database server is on a physical Solaris computer).
You use service blueprints to provision systems with appropriate hardware and software, and make them ready for network operation. The following figure illustrates how pieces designed in a blueprint are mapped to a small pet store service offering. The service offering is a specific service available in the Service Catalog. End users can request the service offering through the Request Entry Console in BMC Service Request Management.
The following video provides a brief overview of the value of using service blueprints.
When creating a service blueprint, you define the service and how it is deployed:
- Service definitions of applications or server instances specify the topology (number of tiers), configuration, operating systems, and software packages that need to be provisioned to "stand up" an application or server.
- Service deployment definitions for each service blueprint specify a set of one or more ways in which the blueprint could be instantiated when it is provisioned.
For example, in a blueprint for a pet store application, one service is related to three deployments — Small, Medium, and Large — that are mapped to a service offering in the Service Catalog. The Small deployment definition for the pet store application might use a single resource set that consists of one VM to support all three tiers: web, business logic, and database. In contrast, the Large deployment definition might distribute the application component to three different resource sets, each corresponding to a different application tier.