What's New

IBM Cloud Private V2.1 – Deploy Kubernetes and Cloud Foundry with ease in your data center

Share this post:

IBM Cloud Private is focused on enabling your enterprise to make the journey to cloud. Whether you’re starting with more automation to manage virtual machines or building 12-factor apps on top of container platforms like Kubernetes, all of the pieces are available in one packaged offering from IBM.

Start your journey to cloud by setting up Kubernetes from IBM Cloud Private on your laptop (https://github.com/IBM/deploy-ibm-cloud-private) or deploying it for your own technology demonstration on VMWare, OpenStack, bare metal, or your Infrastructure as a Service provider.

We are very pleased to announce the release of IBM Cloud Private V2.1!

Bring economies of public cloud to your private data center

We continue to deliver a full featured Kubernetes 1.7 offering that is now certified against the Cloud Native Computing Foundation Conformance Tests (https://github.com/cncf/k8s-conformance). With an integrated installer, we make it easy to bring the full power of the Kubernetes to your own data center and integrate it with your own corporate identity, role-based access control, and operations policies.

We are now introducing a brand new delivery vehicle for our Cloud Foundry Platform as a Service. We make it easy to bring together all of the parts of Cloud Foundry by using containerized packaging and automation to quickly stand up your Cloud Foundry clusters faster than before. We now support many more client-driven customizations than our existing fully managed IBM Bluemix Local offering provides. We are also bringing IBM’s own management console that is built to manage Cloud Foundry for IBM Bluemix Public and Dedicated to the platform, which allows you to use world-class operations visibility across all of your data centers.

IBM Cloud Private Overview

Accelerate your journey to cloud

But there’s more! With this major update to our existing IBM Cloud Private offering, we made a number of enhancements that I’d like to highlight for you.

REVAMPED USER EXPERIENCE: More consistent with IBM Bluemix — providing access to your apps, operations consoles, and a much enhanced app catalog of IBM and third-party software. It’s easy to get started if you’re already familiar with Kubernetes, or use one of the guided wizards to create your apps.

Create deployments easily from the web console

RICH APP CATALOG: IBM and open source software to make it easy to get access to the services you need in development and production. We’re using the open Helm format to package these “charts” out of the box and to allow you to add your own charts to your cluster as well.

A rich app catalog makes it easy to deploy IBM and open source software

IBM WebSphere Liberty, IBM Node SDK, Db2, Db2 Data Warehouse, Data Science Experience, IBM Integration Broker, and many others are available with this release, with more to come. In addition, PostgresSQL; MongoDB; Elasticsearch, Logstash, and Kibana (ELK);  Prometheus; and Grafana are also available.

PROVISION APPS AND MIDDLEWARE FROM THE WEB CONSOLE OR COMMAND LINE: With just a few pieces of information to customize the chart for your needs. In this example, we’re provisioning MongoDB — we indicate how much persistent storage we need and the system takes care of the rest. Many software packages support out of the box options to scale up or down based on the needs of the developer or operator.

Provision software easily from the built-in app catalog

When you deploy any of these helm charts, all of the resources that are created are easily available from a single dashboard, with support to drill in to get more details. We can drill in to see the pieces that were setup for us — persistent storage, secrets, configmaps, deployments, stateful sets, or whatever was required for the software package.

View release details for deployed charts

OPEN SERVICE BROKER APIs OUT OF THE BOX: In addition to your own private Helm chart repository, we have integrated the Open Service Broker API-compliant community project, Service Catalog. By using the Service Catalog, you can extend your IBM Cloud Private platform through Service Brokers, which make it easy to provision slices of middleware based on app needs. The most basic Service Brokers might just deploy a Helm chart for the software package; others might create a database or a set of message queues for an app. Service Brokers offer more fine grained control over how you enable developers to use the platform.

Streamline app updates and ongoing operations

DEPLOYING SOFTWARE IS ONLY THE FIRST STEP: Operating middleware and apps is critical to to your business. We make it easy to get a handle on how to understand the current health of apps by including a built-in operations stack for monitoring, metering, alerting, and log collection.

Operations dashboards are available out of the box

ENSURE COMPLIANCE WITH ROLE BASED ACCESS CONTROL: In the enterprise, access control means the difference between compliance and being at risk of failing an audit. Integrating common identity management across Kubernetes, the operations stack, the built-in Image Registry, Service Brokers, Metering, and other services deployed on the platform like Cloud Automation Manager. We also deliver a simple definition of Teams, Users, Roles, and associated Resources as well to give you fine grained access control across the platform.

Manage Teams and RBAC with IBM Cloud Private

SECURE DEVOPS WITH IBM VULNERABILITY ADVISOR: As images are built and published to the cluster registry, Vulnerability Advisor scans images and configurations to meet established security best practices. Common Vulnerabilities and Exposures (CVE)s are automatically identified and flagged in apps that you build or images you consume upstream.

Vulnerability Advisor In IBM Cloud Private

Scale your private cloud within your data center

And of course, in the world of cloud, automation is the key to scale. All of our services are available via command line interface, REST API, or both. A newly available `bx pr` command line plug-in for the Bluemix CLI makes it easy to configure your local environment to work with many remote clusters.

Configure access to your cluster via kubectl

CLUSTER FEDERATION FOR MULTI-DATA CENTER MANAGEMENT: We also introduced support for Kubernetes 1.7 cluster federation as a tech preview. With cluster federation, you can treat a collection of Kubernetes clusters like one large virtual cluster across many data centers. Federation makes it easier to manage complex High Availability/Disaster Recovery scenarios for your enterprise by making it easy to scale apps across many geographic regions.

MULTI-ARCHITECTURE CLUSTERS: And of course, many enterprises are multi-architecture. In V1.2, we offered support for Intel, Power, and GPU-based workers. With V2.1, we have introduced support to run workers on Linux on IBM Z (zLinux). Many workloads are available out of the box in V2.1 which run on all supported architectures, and we will continue to add additional workloads over time.

Port your apps across many cloud providers

DEPLOY ACROSS MULTIPLE CLOUDS: Containerization of apps brings with it an entirely new dimension to portable, multi-cloud workloads — but some workloads still need to run in virtual machines. IBM Cloud Automation Manager extends IBM Cloud Private with capabilities to manage workloads in both private and public clouds.  CAM is easily provisioned from the App Catalog to manage virtual machines by using the open source, multi-cloud Terraform language. With CAM, you can quickly provision infrastructure and deliver application environments reliably and repeatably in IBM Cloud Public, VMware, AWS EC2, OpenStack, and Microsoft Azure.  After they’re provisioned, all resources are available in a unified dashboard to provide consistency across multi-cloud environments.

Deploy to Multiple Clouds with IBM Cloud Automaiton Manager

GET STARTED QUICKLY WITH COMMUNITY EDITION: We continue our support for our Community Edition to enable developers to get started with the platform hassle-free — if you can pull images from DockerHub, you can get started today! For more information about getting started with IBM Cloud Private CE, see the IBM Cloud Private technical community.
 

Try IBM Cloud Private today!

 
For established enterprises, our fully supported product offering offers Highly Available (HA) configurations of the Kubernetes cluster management plane and well-established IBM Support Lifecycle Agreements (SLA).

It’s been a lot of fun working on these capabilities for our users. I’ve only scratched the surface of what’s available on the platform today. We invite you to join our open community on ibm-cloud-tech.slack.com and give us your feedback, or ask questions on StackOverflow tagged ibm-cloud-private.

Add Comment
3 Comments

Leave a Reply

Your email address will not be published.Required fields are marked *


Denilson Nastacio

I tried the self-contained example and received this:

==> icp: Starting cfc-worker2
==> icp: error: Failed to run: /usr/bin/lxd forkstart cfc-worker2 /var/lib/lxd/containers /var/log/lxd/cfc-worker2/lxc.conf:
==> icp: Try `lxc info –show-log local:cfc-worker2` for more info
The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong.

Reply

    Denilson Nastacio

    More details (not much) about the error, by logging in to the VirtualBox (5.1.28 on MacOS Sierra) :

    ssh vagrant@192.168.27.100
    The authenticity of host ‘192.168.27.100 (192.168.27.100)’ can’t be established.
    ECDSA key fingerprint is SHA256:s6TtuBDr5iBjWO9atbRydfyuY8+dAz45l408mEpfc04.
    Are you sure you want to continue connecting (yes/no)? yes
    Warning: Permanently added ‘192.168.27.100’ (ECDSA) to the list of known hosts.
    vagrant@192.168.27.100‘s password:
    Welcome to Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-92-generic x86_64)

    * Documentation: https://help.ubuntu.com
    * Management: https://landscape.canonical.com
    * Support: https://ubuntu.com/advantage

    54 packages can be updated.
    17 updates are security updates.

    *** System restart required ***
    Last login: Wed Oct 25 14:58:35 2017
    vagrant@master:~$ lxc info –show-log local:cfc-worker2
    Name: cfc-worker2
    Remote: unix://
    Architecture: x86_64
    Created: 2017/10/25 14:41 UTC
    Status: Stopped
    Type: persistent
    Profiles: default, cfc-worker2

    Log:

    lxc 20171025144218.978 ERROR lxc_conf – conf.c:run_buffer:416 – Script exited with status 1.
    lxc 20171025144218.979 ERROR lxc_start – start.c:lxc_init:450 – Failed to run lxc.hook.pre-start for container “cfc-worker2”.
    lxc 20171025144218.979 ERROR lxc_start – start.c:__lxc_start:1314 – Failed to initialize container “cfc-worker2”.
    lxc 20171025144218.979 WARN lxc_commands – commands.c:lxc_cmd_rsp_recv:177 – Command get_cgroup failed to receive response: Connection reset by peer.

    Reply

Denilson Nastacio

Simply running “vagrant destroy” then “vagrant up” made the problem go away. Folks more experienced with Vagrant over here tell me they sometimes see that behavior with Vagrant.

I can see the dashboard now, quite impressed at how you managed to pack a whole lab in that footprint.

Nicely done!

Reply
More What's New Stories

Tutorials to get your mobile development up and running

Recently, we announced new tutorials to get you started on IBM Cloud. In continuation of our effort to bring in structured and well-defined tutorials, we are adding a mobile section

Continue reading

IBM Cloud Container Service – Simplified Region Switching

The IBM Cloud Container Service combines Docker and Kubernetes to deliver powerful tools, an intuitive user experiences, and built-in security and isolation to enable rapid delivery of applications all while leveraging Cloud Services including cognitive capabilities from Watson.

Continue reading

Resource Groups and Access Management

Once you've created resource groups, let's take a look at some best practices on how to manage access for those groups.

Continue reading