Service Designs

Create, configure, and modify service designs to provide on-demand, automated service delivery. Service designs are the recipes for automating the cloud, and include reusable service components. Service components and their relationships in a service design define the framework for creating the service.

Service designs also provide a structure for options that consumers can select when ordering a service. You can re-use designs for multiple service offerings, with each service offering customized to meet the needs of different consumer organizations and groups. You can also leverage service designs shipped with CSA as well as exporting and importing designs between CSA systems.

You can create topology and sequenced designs.

Topology design

Topology designs specify components, relationships, and properties. In contrast to sequenced designs, which more explicitly define the provisioning order and the sequence of actions that will run, topology designs are declarative in nature and do not include explicit actions or sequencing. The provisioning sequence is inferred by the relationships that exist between components in a topology design.

Use topology designs for Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS) deployments that are enabled using Chef, Puppet, Server Automation, and OO flow-based components.

Sequenced design

Sequenced designs specify directed execution of the service component lifecycle and provide mechanisms for controlling resource selection as each component is deployed. When creating sequenced designs, associate one or more resource offerings on a service component to constrain provider selection. This association or link ensures that the resource offering will be provisioned when the service component is deployed. You can also associate resource offerings with component templates.

Use sequenced designs for complex services and services that rely on runbook automation, such as integrations with legacy data center systems. Create a sequenced design as a directed component hierarchy to define lifecycle execution. Sequenced designs use components to group multiple automation providers within a single entity, and they permit explicit specification of lifecycle actions.

Subscriber options

Subscriber options enable you to expose service design options in the Offerings area. Subscriber options are sets of options for a service design. The options sets are made available in the Offerings area. You can refine subscriber options by setting pricing for options, hiding options, and setting values for option properties. The subscriber options are then available to subscribers.