CloudCenter 4.8 has reached End of Life (EOL) as of November 14, 2018. See End of Support Notices for additional context.

Topology Modeler


The CloudCenter metadata descriptors are categorized in the following tabs:

  • Basic Information
  • Global Parameters
  • Topology Modeler

This section provides details on each tab.

Basic Information Tab

The CloudCenter platform models N-tier applications (or application profiles) based on basic information, parameters, topology-specific services and properties that you define for each application. This information provides the metadata descriptors (JSON objects) for each application and the CloudCenter platform stores the metadata information in the CCM server to determine cloud-compatibility and application benchmarks when deploying  your application.

This tab collect basic information about the application such as Name, Version, Description, Category, Tags, Metadata, and other details when creating the profile.

The Protocol field provides an additional None option (in addition to HTTP, HTTPS, None, and Both) when modeling N-tier applications. If you select None, the CloudCenter platform does not add any access link URL in the application deployment detail page.

The HTTP, HTTPS, or Both option selection using a standard or non-standard port is only for the proper application access link URL setting. Be sure to verify that the top tier application firewall rules is set accordingly. The top application tier is set to use firewall rules specified in the service definition by default (for example, the Apache service opens port 80 and 443). Based on the application's requirement, however, users can modify this rule in the application profile.

When checked, the Enable microsegmentation option allows the provider application tier (for example, the database tier) firewall rule is automatically set to only allow the consumer application tier (for example, the App tier) to connect to the service specific port (for example, TCP Port 3306).

This feature is only supported for clouds powered by Cisco ACI. If the application is deployed to other clouds, this firewall rule is ignored. See Security and Firewall Rules for additional context on microsegmentation.

In this tab, you can also add metadata tags that are carried over with the job/deployment when submitted.

Global Parameters Tab

The parameters defined in the Global Parameters tab apply to all tiers and steps in the application or application profile.

The Using Parameters page explains the differences between defining parameters at different levels.

The Troubleshooting Parameters page explains the process and a use case for global parameters.

The Topology Modeler Tab

The Topology tab contains three main sections:

  • Topology Modeler Graphical Workflow: The graphical workflow for each application. When you click on a specific tier in the graphical workflow for each application, you see the configurable parameters and fields for that tier.
  • Topology Modeler Services: Type and group of the defined or selected service.
  • Topology Modeler Properties: Application properties defined using service parameters to further qualify application actions.

The Topology Modeler Graphical Workflow

Use the CCM UI's Topology Modeler to define the application architecture and components. The Topology Modeler allows users to model complex application topologies rapidly in a simple, cloud-agnostic fashion and maintains intricate service dependencies. This Topology Modeler also allows users to plug in custom scripts (application configuration scripts) and services. See Parameters and Macros for additional information.

Indicator ColorApplication Tier Status
Blinking YellowThe application tier is in the pre-initialization state.
Blinking GreenThe application tier is initializing.
Solid GreenThe application tier is up and running.
Solid RedThe application tier has an error.

Topology Modeler Services

Use the Services palette to identify the required services for your application. The CloudCenter platform allows users to select CloudCenter-supported services or define (admins only) custom services via the Services framework. Admins can choose to make the custom services available to all users within a tenant.

When you add a service, the newly-created service is displayed on the Services palette in the Topology Modeler.

Custom Services Group

The CloudCenter platform also allows you to import a custom service (container or image) or define a custom service to launch a VM on the cloud, install component(s), configure component(s), start the script, scale component(s), and shutdown/delete component(s). You can further qualify each service by defining property parameters specific to each instance of this service.

CloudCenter provides the following custom services in the Custom Services group:

Topology Modeler Properties

The Properties palette allows you to specify scripts or binaries to install, customize, configure, start, stop, upgrade, or run the application for any given tier.

The parameters specified in the Global Parameters tab apply to the entire application. The parameters specified in this section only apply to a specific tier within the application.

The configurable fields for each tier are available in the following groups:

  • General Settings: Name, Version, Revision, Description, Category, Tags, Help Link, and Logo for this application.
  • Service Initialization: Service actions (pre-start, post-start, pre-stop, post-stop) that references stored scripts or URLs.
  • External Initialization: Execute additional scripts before or after a service is launched, started, or terminated.

  • Firewall Rules: Access (dynamically open ports between VMs and clouds as specified) and networking restrictions for this application.

  • Deployment Parameters: The global or tier/step specific system- or user-defined variables for which values can be provided at deployment time.

  • Minimum Hardware Specifications: CPUs, memory, storage, network speed, and architecture directives.

  • Environment Variables: Arguments (values) that influence how a process should run between tiers or steps.

  • Node Initialization and Clean Up: References to scripts or binaries that may be required to install, customize, configure, start, and run the VM.

  • Migration: Backup and restore information to move application(s) between clouds.

  • Upgrade: Upgrade types for this application and dependent scripts, if applicable.

See Service Properties for detailed information.

  • No labels
© 2017-2019 Cisco Systems, Inc. All rights reserved