I also provide link to BSA ready content to be used with this stack. The list of this content will grow over the time and you're welcome to participate on adding more. To see how the BSA content needs to be design you can look on what has been already created and read this documentation.
BRPM: from 4.3
BSA: from 8.2
|BRPM Automation - BSA - bsa_generatepackage_deploy||This automation generate a Bladelogic package from the build of an application module and then deploy the package to the targets corresponding to a defined blueprint in the targeted environment|
|BRPM Automation - BSA - bsa_execute_action||This automation allows to select an action that is in fact a BlPackage and then to deploy this package to all targets of an environment for a specific blueprint.|
|BRPM Automation - BSA - bsa_provision_middleware||This automation allows to select a provisioning action that is in fact a BlPackage and then to deploy this package to all target servers that are selected. The provisioning actions proposed are those for a specific blueprint if one is specified, else they're coming from a generic library.|
|BRPM Automation - BSA - bsa_getprovaction||This resource automation provides a list of provisioning actions. This list will depend of the blueprint that has been defined in the same step.|
|BRPM Automation - BSA - bsa_getservers||This resource automation is to browse servers in BSA allowing a multiple selection of servers or/and server groups.|
|BRPM Automation - BSA - bsa_componentbuilders||This resource automation is to provide a list of component to select a component to be used for Bladelogic package creation.|
|BRPM Automation - BSA - bsa_requiredpackageproperties||This resource automation provides a list of local properties of a package for which there is no possible mapping regarding the properties that can be found in the BRPM context of the request and the targeted BSA component.|
|BRPM Automation - BSA - bsa_getaction||This resource automation provides a list of actions that can apply for a blueprint. This list will depend of the blueprint that has been defined in the same step.|
|BRPM Automation - BSA - bsa_deployphases||This resource automation allow to specify if a BSA deployment will run the simulate phase before deploying and/or if it will use indirect staging.|
|BRPM Automation - BSA - bsa_getenvironment||This resource automation is to provide a list of environment (in bladelogic side, an environment is a component group with DESCRIPTION property set to Environment).|
|BRPM Automation - BSA - bsa_targetblueprint||This resource automation is to provide a list of blueprint. In BSA side a blueprint is a component template with DESCRIPTION porperty set to Blueprint.|
|BRPM Automation - BSA - bsa_app_package_folders||This resource automation is to allow to browse the BSA Depot folders and to select a depot folder.|
|BRPM Automation - BSA - bsa_deployjob_folders||This resource automation allows to browse the BSA Jobs folders to select.|
|BRPM Automation - BSA -bsa_requiredpackageproperties_servers||This resource automation provides the list of local properties of a package for which there is no possible mapping regarding the properties that can be found in the BRPM context of the request.|
Content stack is a set of BSA contents that have been build to well work together and to manage a specific service. The following list reference stacks that are designed to with this RPM/RLM integration stack. To work out of the box:
- provisioning actions have to be imported in folder "/BRPM/Provisioning/<Component Template name>/"
- management actions have to be imported in folder "/BRPM/Actions/<Component Template name>/"
<Component template name> is the name of the component template that represent the service (so the name of the blueprint). This component template is part of the BSA content stack.
|Content stack - Tomcat||Content stack to deploy and manage tomcat. It allows to provision tomcat instances, to deploy and undeploy application on tomcat instances|
MORE BSA CONTENT STACKS TO COME
Generic content is content that can be used for any services/blueprints. Depending on where you want to use them:
- actions for blueprint have to be imported in folder "/BRPM/Actions/<blueprint name>/". So you may copy the same content in different folders if you want to use it for different Blueprints.
- in provisioning action context, you have to import in folder "/BRPM/Provisioning/Generic/"
|Blade ZipKit - Generic action: ExtractZip - Unix||This package is to unzip an archive file on Linux|
|Blade ZipKit - Generic action: RemoveFileDir - Unix||This package is for deleting files or directories on Unix|
|Blade ZipKit - Generic action: CopyFileDir - Unix||This package is to copy a file or a directory from a source path to a target path|
MORE BSA GENERIC CONTENT TO COME