You are on page 1of 10

HP Cloud Service Automation

Overview of Sequenced and Topology Designs
Release 4.00

Contents
The Goal ....................................................................................................................................................... 2
HP CSA Service Designs ............................................................................................................................ 2
Sequenced Model Designs ........................................................................................................................................2
Subscriber Options and Actions ............................................................................................................................. 4
Service Pricing .......................................................................................................................................................5
Sequenced Subscriptions ......................................................................................................................................5
Topology Model Designs ............................................................................................................................................6
Topology Designer, Cloud OS, and OpenStack .....................................................................................................7
Creating and Associating Components in a Topology Design................................................................................7
Topology Components ...........................................................................................................................................8
Component Relationships ......................................................................................................................................9
Profiles ...................................................................................................................................................................9
Publishing and Pricing ............................................................................................................................................9
Topology Subscriptions ........................................................................................................................................ 10

© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only
warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein
should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Restricted rights legend: Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211
and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S.
Government under vendor's standard commercial license.
Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. AMD is a trademark of Advanced Micro Devices, Inc. Intel and Xeon
are trademarks of Intel Corporation in the U.S. and other countries. Oracle and Java are registered trademarks of Oracle and/or its affiliates.

easy. HP provides a broad range of sample content for the Sequenced model.00 environment. usually without modification. modify. select available service options. Service designs encapsulate manual IT processes to deploy. HP CSA Service Designs The “recipes” for creating service offerings are defined using HP CSA service designs. and retire a variety of services in an automatic and repeatable manner. Service designs describe subscription options. and reliable provisioning of cloud services to customers. and the processes that realize the requests. Subscribers use the Marketplace Portal to browse through the available offerings.Overview of Sequenced and Topology Designs The Goal The goal of HP Cloud Service Automation (HP CSA) is to provide fast. provider resources. and place orders. HP CSA 4.20 can be run in a CSA 4. HP Cloud Service Automation Page 2 of 10 . This model works well when automating and aligning an IT process with a customer business process. Content developed for HP CSA 3.00 supports two models for service designs: the Sequenced model and the Topology model. Sequenced Model Designs The Sequenced model is used when Developers want total control of the components and actions used in the lifecycle of a service.

Designers can use predefined components from the CSA palette. When a Subscriber no longer needs a subscription. The hierarchy describes components.Overview of Sequenced and Topology Designs The Sequenced model allows Designers to define a hierarchy of components that describe the elements of a service. network elements. or may modify or create their own. HP Cloud Service Automation Page 3 of 10 . the subscription can expire or be cancelled. and the steps for deploying. modifying. and applications. storage. Resource bindings: A component can be bound to a resource offering. releasing resources. such as String. which in turn specifies logic and a series of lifecycle actions. HP CSA components have three features:    Properties. defined actions automate the critical steps in the IT deployment process. or Boolean. and retiring that service. Figure 1: Sequence Model Components Figure 2: Sequence Component Design When a Subscriber places an order. Properties serve as the data fields in a CSA process. Lifecycle actions: Automation actions that fire as the component moves through the CSA deployment lifecycle. Integer. and licenses. At specified points in the lifecycle. such as servers. the service design is realized as the components progress through the HP CSA lifecycle. HP CSA then guides the process to un-deploy a service. such as virtual machines.

After a subscription has been deployed. Modify actions are defined by the Developer and exposed in a Subscriber interface. HP OO supports direct interaction with software. When an order is placed.Overview of Sequenced and Topology Designs Figure 3: Lifecycle Sequence Lifecycle actions usually invoke run-book automation in HP Operations Orchestration (HP OO). network. provisioning of virtual machines. Figure 4: HP Operations Orchestration Flow Subscriber Options and Actions Developers using the Sequenced model can specify service options to expose to a Subscriber. application retirement. HP OO has a large library of flows that can be modified or used as examples for run-book automation. Designers use Operations Orchestration Studio to customize these actions (referred to as “flows” in HP OO). HP Cloud Service Automation Page 4 of 10 . application configuration. For example. and more. a Subscriber can specify the number of servers and a naming convention for any new servers. the Subscriber-specified values are passed into the HP CSA deployment process. Designers can create actions that include sophisticated REST API sequences. and hardware subsystems. the Subscriber can modify settings for a service. error handling.

After the pricing and other service details have been specified. a billing period. Service offerings also allow prices to automatically adjust based on the selected Subscriber options. The results of the subscription (and control over the running instance) are made available in the Subscription Details section of the Marketplace Portal. Service offerings include details like names. the design can be used in one or more service offerings. and a currency. Pricing information includes a base price. description.Overview of Sequenced and Topology Designs Figure 5: Designing Subscriber Options Service Pricing After a Sequenced design has been created. HP Cloud Service Automation Page 5 of 10 . the service offering can be added to a Subscriber catalog. and price. HP Operations Orchestration executes the required calls into other applications and systems. the design is realized through lifecycle stages. Figure 6: Pricing for Sequence Design with Options Sequenced Subscriptions When a Subscriber requests a service based on a Sequenced Model Design.

A Topology Developer creates services by specifying high-level components.Overview of Sequenced and Topology Designs Topology Model Designs The HP CSA 4. The implementation logic is automatically provided by HP CSA. so that the design references the resources.00 Topology Designer enables rapid development of services based on HP Cloud OS. Since HP Cloud OS is constantly adding new functionality. Figure 7: Example Topology Design HP Cloud Service Automation Page 6 of 10 . and relationships. Before a Topology design can be created. each provider may furnish a version-specific description of objects and capabilities. options. properties. and relationships of that particular instance. HP CSA queries a HP Cloud OS provider.

HP Cloud OS in turn interacts with one or more OpenStack instances.00 Topology Designer interacts with HP Cloud OS. The first thing that a Developer does is to specify a CloudOS resource. Cloud OS. Figure 9: Cloud OS Objects HP Cloud Service Automation Page 7 of 10 . and OpenStack Creating and Associating Components in a Topology Design The Topology designer provides an intuitive interface for placing design objects.Overview of Sequenced and Topology Designs Topology Designer. and OpenStack The CSA 4. Figure 8: Interaction between the Topology Designer. so that the design references the resources and properties of that particular Cloud OS instance. A mouse click brings up the available Cloud OS objects. Cloud OS.

for example. and a set of properties that must be defined. others represent Cloud OS-specific concepts. Icon Name Description Properties OpenStack Relationship Server Group A collection of servers  # of instances  OS image  Machine flavor  Key Name Each server in the server group corresponds to an OpenStack “instance” (virtual machine) Volume Group A unique volume that to be attached to the booted VM image  Volume Each volume in a volume group corresponds to an OpenStack (Cinder service) virtual disk volume Network Segment An L2 network connection. a description. Topology Components Each component has a name. Some of the Cloud OS components have close relationships to the underlying OpenStack components. a public WAN  External network Router Connects network segments HP Cloud Service Automation An OpenStack network on a public subnet An OpenStack (Neutron service) router Page 8 of 10 .Overview of Sequenced and Topology Designs The components placed in the design represent objects to be realized in runtime subscriptions. similar to a VLAN  Type  Network Corresponds to selecting a subnet in an OpenStack network External Network Segment A network segment that connects to the “outside” of the Cloud OS environment.

Profiles A powerful feature of the HP CSA Topology designer is the support of profiles. After all of the required details have been added. This feature is valuable for customizing a design for scalability or specific customer requirements. service offerings define the details of a service. Profiles allow a Developer both to reuse a design. and the nature of the connection is pre-determined by the Cloud OS logic. The logic is built in. Topology components have actions that can be executed by the Subscriber after the service is deployed. Sample actions might be to reboot or flex up a server. and to customize the properties for every component. and the profiles have been built. These actions are defined by the Cloud OS provider instance. A warning icon [ ] appears if the definition of an object is incomplete. the Topology model allows the developer to specify price based on the design profiles. the service offering can be added to one or more HP CSA Subscriber catalogs. such as the customervisible name. Developers specify component property values. Subscriber options. In addition to properties. and pricing. Developers can also specify whether a value can be overridden by a Subscriber. and implemented in the underlying Cloud OS logic. the Developer is not responsible for the logic of realizing objects. description. Only components with supported relationships can be connected. Component Relationships The Topology designer allows the Developer to define relationships between components. After all of the design components and relationships have been specified. Publishing and Pricing After a design is complete. the design must be saved and then “published”. Whereas the Sequenced model establishes a price using a base price and options. As with the Sequenced Model. HP Cloud Service Automation Page 9 of 10 . In the topology context. This is done by dragging a connection from one component to another. publishing means that the design can now be used to create a service offering. the developer should find and fix any validation errors.Overview of Sequenced and Topology Designs When creating Topology designs.

the information in the design is passed to HP Cloud OS to be realized. The results of the subscription (and control actions on the running instance) are made available in the Subscription Details section of the Marketplace Portal.Overview of Sequenced and Topology Designs Figure 10: Publishing and Pricing Topology Subscriptions When a Subscriber requests a service based on a Topology Model design. HP Cloud Service Automation Page 10 of 10 .