IBM Cloud Orchestrator 2.5 comes with a set of interesting new features.
First of all the support for OpenStack Kilo; this opens the door to a set of very interesting scenarios related to software defined environments (think about the neutron capabilities in Kilo). Moreover you can now either leverage the OpenStack distribution provided by IBM (IBM Cloud Manager with OpenStack 4.3) or another OpenStack distribution based on Kilo. Orchestrating workloads on a non IBM OpenStack distribution does no longer rely on the Public Cloud Gateway.
The list of supported public clouds has been enriched with the addition of Microsoft Azure: from IBM Cloud Orchestrator self service user interface you can now register and manage Microsoft Azure regions, deployment artifacts and manage resources.
The pattern engine is now based on OpenStack Heat, no more proprietary technology involved; the user experience has been enhanced allowing to store and select heat templates from the self service UI.
The installation procedure has been simplified; the number of needed servers has been shrunk to reduce hardware requirements, a prerequisite checker has been added to enable a fast detection of possible failure points.
For further information visit IBM Cloud Orchestrator 2.5 knowledge center
IBM Cloud Orchestrator 2.5 announcement letter is here