on 02-12-2014 06:51 AM
The Application Stack Accelerator Pack 4.0 (ASAP) for Cisco Intelligent Automation for Cloud includes:
The kit is an extension to Cisco Intelligent Automation for Cloud 4.0 and offers cloud application topology design and orchestration:
Please note that as a cloud accelerator, the content will continue to evolve over time based on feedback from the community. We welcome comments and suggestions and will do our best to respond and update as appropriate.
With regard to support, the first point of contact should be the author and/or this community. If you are having issues, moderators of this forum will determine and advise if a TAC case is appropriate, otherwise issues will be addressed here.
For overviews of blueprint design as well as stack ordering, view the following videos:
Designing Blueprints for Cloud ApplicationsChanges for v2 include:
1. Updated for compatibility with IAC 4.0 Patch 2.
2. Created new Stack Consumption Business Unit OU to be able to assign just the Stack Consumer role
3. Fixed Portal Page Permissions for Blueprints/Stacks (remember to import services AFTER importing portal pages)
4. Enhanced stack provisioing to configure servers in the sequence defined currently for boot sequence. Only the Puppet/Chef server configuration is queued; servers
later in the boot sequence will wait until those earlier have successfully completed (e.g., allowing a DB server to be created before an application server attempts
to create a DB schema and load data there)
5. No longer reboot services upon completion of stack order (no longer be necessary with new provisioning sequence enhancement)
6. Implemented a number of cosmetic fixes.
7. Version numbers are now recorded and incremented with each edit and copy of a blueprint.
Changes for v3:
1. Updated for compatibility with IAC 4.0 Patch 3
2. Added new Delete Blueprint service, which can either remove all service item details for the blueprint or mark the blueprint as deleted, retaining all details
3. Added new blueprint option that instructs the orchestrator to power cycle all servers in the stack in boot sequence after all the servers have been configured by Puppet or Chef.
4. Data retrieval rules have been normalized to work with both MS SQL and Oracle, eliminating the need for separate Catalog Deployer packages for ASAP services
5. ASAP is no longer limited to the four default network zones: Public, Private, Protected Public, Protected Private. It will now recognize all zones as defined in the Network Zone Type standards table (under Stack Design and Management)
6. The My Stacks portlet now includes add on services for individual servers in the stack (similar to My Servers)
7. Several issues reported by the community have been resolved
Changes for v4:
Updated for compatibility with IAC 4.0 Patch 4 (4.0.0.4) and PSC 10 R2 (with patch 1h)
Fixed issues with editing blueprints to add load balancing
Added all of the stack ordering services to list of services that can be configured for approvals
v4 has been uploaded with a new "Intelligent Automation for Stacks" TAP to fix an issue with automation pack dependencies.
A patch is available for an issue with Oracle (e.g., using the IAC appliance). There are 2 Catalog Deployer packages to deploy: ASAP_Software_Applications_Sample_Data (deploy one time only) and Stack_Blueprint_Design_and_Management_Services_v4a_patch (if you are deploying for the first time, use this package INSTEAD of the one from the original v4 kit).
Change Log for Version 6 June 17, 2014
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: