Cisco Cisco Intelligent Automation for Cloud 4.3.1 User Guide

149

www.cisco.com

Managing ASAP Stacks and Blueprints

This chapter explains ASAP and its components in the following main topics:









Overview

The Application Stack Automation Pack (ASAP) is designed to provide a launching off point for delivering cloud 
applications through Cisco Prime Service Catalog and Cisco Process Orchestrator. ASAP content extends Cisco IAC with 
Cisco Prime Service Catalog and Cisco Process Orchestrator. Cisco IAC must be installed and operational prior to ASAP 
deployment. 

Understanding ASAP

You can think of a stack blueprint design as a template configuration from which end users can order whole application 
stacks or platforms, configured exactly as specified in the blueprint design. A blueprint designer should create a blueprint 
with sufficient detail so that the end-user who orders from it gets exactly what you intended.



A prerequisite to the design process is defining your target environments; for example, the types platforms you 
intend to deploy application stacks from your blueprints. Blueprint design consists of the folllowing processes:

Creating the specification (the blueprint itself)

Creating an instance of the stack based upon that specification

Testing the instance to ensure your design was detailed enough

Revising the blueprint design accordingly, based upon test results

Getting your design reviewed and approved

Publishing the design so that end-users may order from it

Features

Features for Application Stack Blueprint Design



Adding servers to a stack design



Placing servers into network zones 



Assigning one or more configuration plans (roles) to servers (using Chef and Puppet)