Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Overview of the Cisco HCS Provider

The Cisco Hosted Collaboration Solution (HCS) enables Cisco partners, typically traditional telecom service providers and large enterprise customers, to provide a wide range of Cisco collaboration applications to their customers in a subscriber-based service offering.

The Cisco HCS supports the following applications:

  • Cisco Unified Communications Manager (formerly CallManager)
  • Cisco Unity Connection
  • Cisco Unified Presence

Currently, Cisco provides one offering per customer. It delivers a preconfigured, pretested solution for HCS (HCS 8.6.2 based on Virtualized Multiservice Data Center 2.3) on a secure, scalable, multitenant Data Center (DC), enabling Managed Service Providers (MSPs) to deliver an integrated and assured offering to end customers. With the Virtualized Multiservice Data Center (VMDC) 2.3 reference architecture and IaaS self-service capabilities, Cisco has automated the orchestration of order to fulfillment of Cisco HCS, where repeatable templated configuration is used to accelerate the onboarding of tenant and associated HCS infrastructure components, leading to a seamless user experience for IaaS and HCS services.

The Cisco HCS integration with BMC Cloud Lifecycle Management and VMDC enables:

  • Accelerated on-boarding of customers
  • Repeatable templated (blueprint based) configuration for HCS services (voice/ presence/ voicemail/ contact center)
  • Provisioning of Cisco HCS services by using Cisco defined custom placement logic, as well as custom host name logic
  • Unified operator experience across IaaS and HCS for provisioning
  • On-demand scalability

This topic contains the following sections:

Key features of version 1.0.00 of the Cisco HCS Provider

Version 1.0.00 of the Cisco HCS Provider contains the following features:

  • Registers a Cisco HCS Provider instance
  • Starts, stops, and decommissions provisioned VMs
  • Modifies memory and CPU values of provisioned VMs
  • Specifies single vCenter accounts
  • Custom provider for provisioning
    • Based on BMC Atrium Orchestrator
    • Uses BMC Cloud Lifecycle Management Generic Adapter-Generic Provider (GA-GP) framework
  • Custom placement provider (compute and storage); support for round-robin placement
  • Custom host name provider; host name assignment with HCS convention
  • Cisco HCS service blueprint (out-of-the-box sample). Service blueprint with different functional components: Cisco Unified Communications Manager (CUCM), Unity and Presence
  • Predefined tag values for resources
  • Installer to install Cisco HCS Provider on BMC Cloud Lifecycle Management

This release contains the Cisco HCS Provider installer, sample blueprints, and tag creation utility.

Product compatibility

This release integrates with the following product versions:

  • BMC Cloud Lifecycle Management 3.1, SP 1
    • BMC Atrium Orchestrator Development Studio Version 7.6.02.04
    • VMware Infrastructure Adapter (20.12.04.00.14)
  • Cisco HCS 8.6.2
  • VMDC 2.3

Known issues

The following table lists the known issues for the Cisco HCS Provider:

Support ID

Tracking ID

Description

 

 

If a host is moved from Cluster A to Cluster B, performing a Refresh on clusters in BMC Cloud Lifecycle Management will result in the correct refresh of the host added to the new cluster but the old cluster (Cluster A) shows a stale entry of the host that was moved to Cluster B. You will see entries of the same host under both cluster A and cluster B in BMC Cloud Lifecycle Management Resources and Cisco HCS metadata form.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*