|
|
|
Administration |
|
|
Multi-tenant support
Details
|
Supported
vCommander supports the concept of organizations to provide segregation between groups
|
CloudCenter supports enterprise marketplace and multi-tenant federated administration
http://cdn2.hubspot.net/hub/194983/file-2531464664-pdf/docs/CliQr_Multi-Tenancy_and_Multi-User_Model-1.pdf
|
Supported
https://access.redhat.com/articles/2037663?tour=7#multi-tenancy
|
|
|
API published : click on details (i) for link
The vCommander REST API provides a comprehensive set of features, which are are highly beneficial to dev/test lab automation,
multi-tenant customer onboarding, and synchronization of asset inventory with third-party systems, to name a few.
http://ftp.embotics.com/REST/v2.5/vCommander%20REST%20API%20Getting%20Started%20Guide%20v2.5.pdf
|
API published : click on details (i) for link
http://docs.cliqr.com/display/40API/CloudCenter+API+Overview
CliQr API Version 1.0 provides APIs (except as identified for deprecated APIs/attributes) to support the following CloudCenter releases:
CloudCenter 4.x
CloudCenter 3.x
|
Supported
https://github.com/ManageIQ/manageiq_docs
|
|
|
|
Configuration Management |
|
|
|
Supported
You can configure vCommander to use the Chef IT automation platform. Requested VMs can be automatically deployed and configured as Chef nodes.
http://www.embotics.com/documentation/index.html?chef_integration.htm
|
Supported
Existing investments in Chef can be reused within CloudCenter for software orchestration, with CliQr providing key Governance and Management tools for the full lifecycle of an application
http://cdn2.hubspot.net/hub/194983/file-2664100894-pdf/CliQr-CloudCenter-Chef-0315-WEB.pdf
|
Not supported
http://manageiq.org/documentation/faq/#does-manageiq-support-docker
|
|
|
Supported
You can configure vCommander to use the Puppet Labs® IT automation system, Puppet. When you integrate vCommander with Puppet, you can automate repetitive configuration tasks for VMs provisioned with vCommander.
http://www.embotics.com/documentation/index.html?puppet_integration.htm
|
Supported
Existing investments in Puppet can be reused within CloudCenter. In this mode, Puppet is used for software orchestration and CloudCenter provides Governance and Management tools for the full lifecycle of an application.
There is a service script available that installs, configures, starts and stops the Puppet Agent.
|
Supported through Red Hat Satellite integration
Puppet is supported through Red Hat Satellite integration.
|
|
|
Supported
|
Supported
Existing investments in Ansible can be reused within CloudCenter for software installation, with CloudCenter providing key Governance and Management tools for the full lifecycle of an application
|
Supported
NEW
Ansible is now included, can also be connected to an external Ansible Tower integration http://cloudformsblog.redhat.com/2017/05/31/red-hat-cloudforms-4-5-ga/
|
|
|
Supported
|
Supported
Existing investments in SaltStack can be reused within CloudCenter for software installation, with CloudCenter providing key Governance and Management tools for the full lifecycle of an application
|
Not supported
http://manageiq.org/documentation/faq/#does-manageiq-support-docker
|
|
Ability to patch managed systems
Details
|
Supported using scripting
User can apply update scripts that can be integrated into the vCommander change management workflows
|
Supported
User run-time lifecycle actions include upgrade or patch a specific tier or component within a tier.
|
Supported through Red Hat Satellite and Red Hat Ansible Tower integration
NEW
Supported through Red Hat Satellite and Red Hat Ansible Tower integration
|
|
|
|
Networking |
|
|
|
Network Fencing isolation (Vmware only)
Provides the ability to deploy vCenter services to isolated networks where IP and MAC address conflicts are not possible, called fenced networks. To do so, a virtual router is deployed with the VMs or virtual services when you define a service as fenced. The deployment of the vRouter is handled entirely by vCommander, so you do not have to import the template or take any other action outside vCommander to make it available for use.
|
Supports Cisco ACI
SDN Support only for ACI (Cisco APIC release 3.0 and 3.1). NSX support dropped in Version 4.8
|
Supported and can also leverage Ansible
NEW
It had been implemented at customers. Control usually requires Ansible integration. http://cloudformsblog.redhat.com/2017/01/04/announcing-cloudforms-4-2/
|
|
Public cloud networking
Details
|
Supports operational views. Deployment limited to use of templates (eg cloudformations)
Operational view capability summarised at http://docs.embotics.com/views_menu.htm
For details on network control see
http://docs.embotics.com/feature_support_matrix.htm
|
CloudCenter uses public cloud native networking APIs to instantiate policy
Supports AWS ELB,HAProxy,Nginx
|
Supported
NEW
Supported: http://cloudformsblog.redhat.com/2017/01/04/announcing-cloudforms-4-2/
|
|
|
|
User-Defined Actions |
|
|
Conditional Actions
Details
|
Supported
You can specify that workflow steps are executed only when specified conditions are met. Setting conditions can help you:
• Make a workflow more flexible - for example, you might want to install an antivirus program only on Windows VMs.
• Add an extra level of approval to a workflow - for example, if the user requests resource changes.
You can also make an entire workflow conditional by adding only a single conditional step to it.
http://www.embotics.com/documentation/index.html?manage_workflows.htm
|
Supported
Policy / triggered and conditional-based actions available through policy and action library administration.
|
Supported
Through policies or workflows
|
|
Pre- and Post-Install Actions
Details
|
Supported
Using Embotics® vCommander™, you can set up approval workflows pre-deployment, and completion
workflows post-deployment to help manage the service request process.
In addition, command workflows can be defined to allow tasks or commands to be carried out on deployed VMs.
http://www.embotics.com/documentation/index.html?manage_workflows.htm
|
Supported using pre- and post-install scripts
|
Supported
Through policies or workflows
|
|
Scheduled Actions
Details
|
Supported
vCommander provides a method of scheduling several types of tasks. Examples of these tasks are:
• Running a saved search
• Ggenerating a report
• Scanning a guest OS
• Purging historical data
http://www.embotics.com/documentation/index.html?scheduling_tasks.htm
|
Supported
Its possible to schedule deployment, scaling, and termination dates through policies.
|
Supported
Through policies or workflows
|
|
|
|
Orchestration & Workflow |
|
|
|
Supported
Using Embotics® vCommander™, you can set up approval workflows and completion workflows to help manage the service request process, and in addition, command workflows to allow tasks or commands to be carried out on deployed VMs.
http://www.embotics.com/documentation/index.html?manage_workflows.htm
|
Integration with Cisco UCS Director and ServiceNow
CloudCenter provides Cisco Unified Computing Systems Director (UCSD) integration that enables you to invoke UCSD callout workflows and ServiceNow workflows.
|
Supported
CF is itself an orchestrator
|
|
3rd Party Orchestration
Details
|
Supported via scripting framework
vCommander can call out to any other orchestration tool, like vRealize Orchestrator, HP Operations Orchestation, etc. Essentially if it has an API, then vCommander’s existing orchestration engine can call out to a third party passing the relevant context (tenant, application, cloud details, etc.).
http://www.embotics.com/support/kb/vcommander-scripting/
|
Not supported
|
Achievable through APIs or dedicated connector
Not out of the box, but achievable through APIs or dedicated connector
|
|
|
Supported
vCommander workflows allow you to add hooks in the workflows which are triggered by events. These can be triggered through a manual task, a scheduled task, a provisioning action, lifecycle activity, etc. When these events occur, there is the ability to trigger any arbitrary workflow. It is through this method that Webhooks is integrated as an orchestration tool http://www.embotics.com/support/kb/vcommander-scripting/
|
Not Supported
|
Achievable through APIs or dedicated connector
Not out of the box, but achievable through APIs or dedicated connector
|
|
|
|
Third-Party Automation |
|
|
|
Supported
capabilities for bi-directional integration between Embotics vCommander and the ServiceNow IT Service Management (ITSM) platform.
Integration provides streamlined automation of key processes and maintenance of accurate data within the Configuration Management Database (CMDB).
http://info.embotics.com/embotics_servicenow
|
Supported
Release 4.8.2 added a menu option Service Now Management
|
Supported
https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.6/html/integration_with_servicenow/index
|
|
3rd Party Automation
Details
|
Supported via scripting framework
vCommander’s workflow engine has the ability to integrate with 3rd party systems using various methods like calling out to
APIs, CLIs and scripts. It is through this method that HP Server Automation is integrated as a workflow tool
http://www.embotics.com/support/kb/vcommander-scripting/
|
Not Supported
|
Achievable through APIs or dedicated connector
Not out of the box, but achievable through APIs or dedicated connector
|
|
|
Supported
|
Limited capability
By making using of custom scripts, it is possible to integrate with CMDB solutions.
|
Has native CMDB; third-party support requires integration
CF provides a native CMDB, but there no existing out of the box integration with 3rd party CMDB. All of the information is available, and this type of interaction with 3rd party CMDB is available through professional services.
|
|
|
|
User-Defined Properties |
|
|
Automatic hostname creation
Details
|
Supported
Integration provides streamlined automation of key processes and maintenance of accurate data within the Configuration Management Database (CMDB).
|
Supported
Using CloudCenter Marco Replacement or Hostname Callout
|
Supported
Through policies or workflows
|
|
Configuration tags
Details
|
Supported
|
Supported
|
Supported
Tagging / Autotagging engine
|
|
|
|
Placement |
|
|
Best Execution Venue -Â Performance
Details
|
Supported
vCommander can use performance and capacity information to select the correct provisioning destination
|
Supported
The CloudCenter platform automates benchmarking the price, performance and price-performance index of each actual application, simultaneously across any cloud, instance type or provider, so you can pick your target before you deploy. Â Â http://info.cliqr.com/hubfs/2015-Whitepapers/CliQr-CloudCenter-Full-Lifecycle-Management-062415.pdf
|
Possible using analysis methods
Throught drift analysis you can obtain all the info to take the decision and/or build a related custom report
|
|
Best Execution Venue - Security
Details
|
Supported
Intelligent Placement features and policies, ensuring workloads are provisioned to the optimal cloud based on business priorities including resource consumption, cost, placement attributes and per-destination quotas.
|
Not supported
|
Possible using analysis methods
Throught drift analysis you can obtain all the info to take the decision and/or build a related custom report
|
|
Best Execution Venue - Cost
Details
|
Supported
Intelligent Placement features and policies, ensuring workloads are provisioned to the optimal cloud based on business priorities including resource consumption, cost, placement attributes and per-destination quotas.
|
Supported
The CloudCenter platform automates benchmarking the price, performance and price-performance index of each actual application, simultaneously across any cloud, instance type or provider, so you can pick your target before you deploy. Â Â http://info.cliqr.com/hubfs/2015-Whitepapers/CliQr-CloudCenter-Full-Lifecycle-Management-062415.pdf
|
Possible using analysis methods
Throught drift analysis you can obtain all the info to take the decision and/or build a related custom report
|
|
|
Supported
vCommanders robust policy engine automates VM lifecycle management.
http://www.embotics.com/documentation/index.html?vm_lifecycle_mgmt.htm
|
Supported
|
Supported
|
|
|
|
Provisioning |
|
|
Bare-metal provisioning
Details
|
Supported with use of 3rd party PXE boot solutions
|
Limited capability
Only available for IBM SoftLayer Public Clouds.
|
supported with Red Hat Satellite (Foreman)
http://manageiq.org/blog/2015/06/manageiq-botvinnik-control-all-the-things/
|
|
|
|
Reconfiguration & Expiration |
|
|
Ability to change VM configuration
Details
|
Supported
In vCommander, you can request a service, copy a new service request to quickly create a new one, or request a change
to a service the same way that a Service Portal user can make those requests. If workflows have been configured, the
requested service or change request automatically goes through the workflow process.
http://www.embotics.com/documentation/index.html?request_service_main.htm
|
Supported
Actions library provides the ability to define Day 2 operations as VM actions (like, stop, start, reboot, attach volume, take snapshot, etc.) and execute them on the VMs in your datacenter.
|
Supported
NEW
Virtual Machine Reconfiguration supported (RHEV, vSphere, OpenStack)https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.2/html-single/support_matrix/
|
|
Live change VM resources
Details
|
Supported
In vCommander, you can request a service, copy a new service request to quickly create a new one, or request a change
to a service the same way that a Service Portal user can make those requests. If workflows have been configured, the
requested service or change request automatically goes through the workflow process.
http://www.embotics.com/documentation/index.html?request_service_main.htm
|
Supported
As long as a OS reboot isnt necessary
|
Supported
If supported by the underlying provider
|
|
Scheduled expiration
Details
|
Supported
You can set expiry dates for existing services manually, or, set expiry information for new services in one of the following ways:
• Through the Default Attributes policy, which you can use to assign new services to an expiry group
• Through a completion workflow with a Set Expiry Date step
• When manually deploying a requested service, or when manually cloning a VM
http://www.embotics.com/documentation/index.html?managing_an_expiry_date.htm
|
Supported via aging policies
|
Supported
Through provisioning options or policies
|
|
|
|
Uptime Management |
|
|
Continuous Infrastructure Testing
Details
|
Supported
vCommander is continuosly verifying connections to critial managed systems, cloud APIs and other infrastructure like Active Directory.
|
Supported
A monitor service is included
|
Can be configured
Performance, health and drift analysis
|
|
|
Supported
http://support.embotics.com/support/solutions/articles/8000036815-embotics-vcommander-high-availability
|
HA Supported for the CMP application
See: http://docs.cloudcenter.cisco.com/display/CCD48/HA+Virtual+Appliance+Architecture
|
Offloaded to the underlying provider
Offloaded to the underlying provider
|