Before you create an Application Profile, review your architectural requirements to determine the type of profile for your application. Use the following list to understand and discover nuances and dependencies for your application.
|No.||Consideration||Links||Action Items and Details|
|1||Identify the services for your application and determine how these services are dependent on each other?|
See Supported Services.
Identify and provide a top-down hierarchy for these services.
|2||Does you application contain multiple tiers?||See Service Configuration|
For each tier, provide the list of dependent services. The services listed in this section also identify the dependency from the service deployment perspective.
|3||Are you using CloudCenter-supported services?||SeeBundle Store.|
The bundle store contains the agent and service bundles. This repository is hosted by CloudCenter CDN () or can be hosted locally in a private cloud environment using a standard Apache server.
|4||Did you determine the hosting location for your service(s)?||See Package Store if using CloudCenter-supported services.||Every CloudCenter deployment requires a CloudCenter Package Store, a hosting location for all CloudCenter-supported Manual Installation, all services are automatically detected by the Package Store and displayed via the Topology Modeler Properties tab.and other required information. When you complete the CloudCenter|
Are there external services that need to be connected to and communicated with (for example, a new schema on an existing SQL server cluster, a new Virtual IP, VIP, on an existing load balancer, and so forth)?
See External Service.
You can create an application using multiple tiers where you can stipulate each tier to use a different CloudCenter-supportedor externally-provided service (third-party services).
Are you using custom/private services?
Where are the artifacts that are required for these services to be successfully deployed?
|7||Do you have all the dependent application data, files, and packages?||See Artifact Repository||Typically, enterprises maintain application packages, data, and scripts in multiple repositories of their choice. Use the Artifact Repository to attach your own external repository to store and access your files. CloudCenter provides a Repositories tab in the CCM UI for this purpose.|
|8||Have you identified the infrastructure requirements for each service||See Phase 1: Prepare Infrastructure||Based on the number of VM instances that you manage for your enterprise, be sure to address the specific hardware requirements.|
|9||What are the networking requirements for each service to talk to the others?||See Phase 2: Configure Network Rules|
While this section lists all the ports for each, several of them are optional and completely dependent on your deployment requirements.
CloudCenter profiles are generally based on core configuration details, elaborate workflows that describe the sequence of steps required to deploy the application, or run on big-data processing workloads.
Application Profile Type
|For each application profile, identify the category.|
Application (or tier) requirements
See the following links:
For each application (or tier), provide the dependent parameters and scripts.
Port and firewall accessibility
See the following links:
Identify the scripts or dependencies at the time of deployment.
You can attach multiple volumes to all tier types in N-tier applications. For each volume, you must specify the size and can optionally configure the volume type.
Testing and verification
|Refer to your enterprise policies and requirements.|
Be sure to identify you dependent test cases for each profile.
Other Application Dependencies
Besides the information required to model your application ensure to address the following external dependencies:
- Application packages and associated licenses, if applicable.
- Application credentials to access and verify each application, if applicable.
- Infrastructure requirements such as minimum CPUs, memory, storage, and other requirements specific to your application(s).
- No labels