How IBM’s Red Hat Acquisition Redefines the Cloud

IBM recently announced its $34 billion acquisition of Red Hat. This blockbuster deal signals a sea change in cloud as IT managers broaden their view of what cloud is and how it’s most effectively deployed. With Red Hat, IBM is positioned to lead in the multi-cloud world.

IBM recently announced its $34 billion acquisition of Red Hat. This blockbuster deal signals a sea change in cloud as IT managers broaden their view of what cloud is and how it’s most effectively deployed. With Red Hat, IBM is positioned to lead in the multi-cloud world.

Prior to this acquisition, IBM already was a full-featured cloud provider, with both on-prem and cloud-based elements in their portfolio.

With Red Hat, IBM now adds two new dimensions:

  • Fluid application and data migration:  Red Hat brings Linux-based tools, including containers, the OpenShift container platform, and Kubernetes orchestration. Part of the multi cloud promise is to make clouds interchangeable with seamless workload and data migration. This helps make that possible.
  • Multi-cloud interoperability: Orchestration, of course, is only half of the puzzle. The other half is broad platform interoperability, something the open source Red Hat platform was built to deliver.

Why Enabling the Multi-Cloud Matters

Enabling the multi cloud may seem like a curious move for a cloud provider. After all, it makes it easier for your customers to go to the competition! But it’s a savvy move for two reasons:

Users are going to the multi-cloud anyway

In a recent IDC survey, IT managers report that 75% of workloads would ideally run in a diverse cloud world, not just on a single public cloud. The customers will go to the provider that enables their preferred model.

 

multi cloud combines public cloud and private cloud

Enabling the multi cloud drives dominance

Being open actually drives customers to you. Gartner stated this about the multi cloud:

  • “Most organizations will pursue a multi cloud strategy, although most will also designate a primary cloud provider for a particular purpose, and are likely to have 80% or more of those types of workloads in their primary provider.”

By this thinking, the vendor who best enables the multi-cloud will also reap the preponderance of the revenue.

Cloudian Delivers on the Multi-Cloud Vision Today

Cloudian has been promoting the multi cloud vision since January 2018. With the launch of HyperStore 7, Cloudian began supporting multi cloud deployments across private cloud and public clouds including AWS, GCP, and Azure.

Cloudian links divergent environments with:

  • A single view of data, combining private + public clouds
  • Common API across clouds
  • Single-point management

IBM, in fact, mirrored these same values in their Red Hat announcement. Here’s a deal summary, annotated with Cloudian points:

IBM Red Hat multi cloud benefits mirror Cloudian object storage benefits

 

HyperStore 7 Converges the Clouds

HyperStore 7 is a scale-out object storage platform and multi-cloud controller in a single software image. Deployed on prem or in the cloud, it enables all cloud types:

  • Private cloud: Deploy on-prem or as a hosted private cloud for scalable storage
  • Hybrid cloud: Link to any cloud (AWS, GCP, Azure) and replicate or migrate data using policy-based tools — without middleware or 3rd party software
  • Multi cloud: Deploy in multiple clouds to provide single-API connectivity and a common management framework

Combine these capabilities to create whatever management model your use case demands.

Multicloud architecture combines object storage and cloud interoperability

 

The Multi-Cloud Takes Shape

With Red Hat, IBM has advanced the multi-cloud conversation, further validating an important market direction. Ultimately, both consumers and cloud providers will benefit as open solutions expand the possibilities for everyone.

In the early days of cloud, the providers were walled gardens with unique APIs and proprietary management tools. The web also started as a walled garden (anyone remember Prodigy and AOL?). While web fortunes were made in those early days, the fastest part of the web growth curve starting after the walls came down. The same could well happen here.

Learn more about Cloudian HyperStore Multi-Cloud at https://cloudian.com.

 

YOU MAY ALSO BE INTERESTED IN:

Object Storage vs Block Storage: What’s the Difference?

Private Cloud Storage

IBM Spectrum Protect with Amazon S3 Cloud Storage

IBM Spectrum Protect (formerly IBM Tivoli Storage Manager) solution provides the following benefits:

  • Supports software-defined storage environments
  • Supports cloud data protection
  • Easily integrates with VMware and Hyper-V
  • Enables data protection by minimizing data loss with frequent snapshots, replication, and DR management
  • Reduce the cost of data protection with built-in efficiencies such as source-side and target-side deduplication

IBM Spectrum Protect has also enhanced its offerings by providing support for Amazon S3 cloud storage (version 7.1.6 and later) and IBM Spectrum Protect version 7.1.6 was just released on June 17th, 2016. I was actually a little nervous and excited at the same time. Why? Because Cloudian HyperStore has a S3 guarantee. What better way to validate that guarantee than by trying a plug-and-play with a solution that has just implemented support for Amazon S3?

Overview of IBM Spectrum Protect with Amazon S3 cloud storage

And the verdict? Cloudian HyperStore configured as “Cloud type: Amazon S3” works right off the bat with IBM Spectrum Protect. You can choose to add a cloud storage pool from the V7.1.6 Operations Center UI or use the Command Builder. The choice is yours.

We’ll look at both the V7.1.6 Operations Center UI and the Command Builder to add our off-premise cloud storage.

NOTE: Cloudian HyperStore can be deployed as your on-premise S3 cloud storage but it has to be identified as an Amazon S3 off-premise cloud storage and you have to use a signed SSL certificate.

Here’s how you can add an Amazon S3 cloud storage or a Cloudian HyperStore S3 cloud storage into your IBM Spectrum Protect storage pool:

From the V7.1.6 Operations Center UI

 

From the V7.1.6 Operations Center console, select “+Storage Pool”.

Adding 'Storage Pool' to the IBM Spectrum Protect V7.1.6 Operations Center console

In the “Add Storage Pool:Identity” pop-up window, provide the name of your cloud storage and the description. In the next step of the “Add Storage Pool:Type”, select “Container-based storage:Off-premises cloud”.

IBM Spectrum Protect cloud storage description

Click on “Next” to continue. The next step in the “Add Storage Pool:Credentials” page is where it gets exciting. This is where we provide the information for:

  • Cloud type: Amazon S3 (Amazon S3 cloud type is also used to identify a Cloudian HyperStore S3)
  • User Name: YourS3AccessKey
  • Password: YourS3SecretKey
  • Region: Specify your Amazon S3 region (for Cloudian HyperStore S3, select “Other”)
  • URL: If you had selected an Amazon S3 region, this will dynamically update to the Amazon region’s URL. If you are using a Cloudian HyperStore S3 cloud storage, input the S3 Endpoint Access (HTTPS).

Complete the process by clicking on “Add Storage Pool”.

IBM Spectrum Protect

NOTE: Be aware that there is currently no validation performed to verify your entries when you click on “Add Storage Pool”. Your S3 cloud storage pool will be created. I believe the IBM Spectrum Protect group is addressing this with a validation process for the creation of a S3 cloud storage pool. I hope the step-by-step process that I have provided will help minimize errors with your Amazon S3 cloud storage pool setup.

From the V7.1.6 Operations Center Command Builder

 

From the V7.1.6 Operations Center Command Builder, you can use the following define stgpool command and you are done adding your off-premise S3 cloud storage pool:

  • define stgpool YourCloudName stgtype=cloud pooltype=primary cloudtype=s3 cloudurl=https://s3.cloudianstorage.com:443 access=readwrite encrypt=yes identity=YourS3AccessKey password=YourS3SecretKey description=”Cloudian”

NOTE: You can review the server instance dsmffdc log if there’s errors. It is located in the server instance directory. There’s also a probability that the signed SSL certificate might not be correct.

For example:

06-20-2016 11:58:26.150][ FFDC_GENERAL_SERVER_ERROR ]: (sdcloud.c:3145) com.tivoli.dsm.cloud.api.ProviderS3 handleException com.amazonaws.AmazonClientException Unable to execute HTTP request: com.ibm.jsse2.util.h: PKIX path building failed: java.security.cert.CertPathBuilderException: unable to find valid certification path to requested target
[06-20-2016 11:58:26.150][ FFDC_GENERAL_SERVER_ERROR ]: (sdcntr.c:8166) Error 2903 creating container ibmsp.a79378e1333211e6984b000c2967bf98/1-a79378e1333211e6984b000c2967bf98
[06-20-2016 11:58:26.150][ FFDC_GENERAL_SERVER_ERROR ]: (sdio.c:1956) Did not get cloud container. rc = 2903

 

Importing A Signed SSL Certificate

 

You can use the IBM Spectrum Protect keytool –import command to import the signed SSL certificate. However, before you perform the keytool import process, make a copy of the original Java cacerts.

The Java cacerts is located in IBM_Spectrum_Protect_Install_Path > TSM > jre > security directory.

You can run the command from IBM_Spectrum_Protect_Install_Path > TSM > jre > bin directory.
For example, on Windows:

    • ./keytool –import ../lib/security/cacerts –alias Cloudian –file c:/locationofmysignedsslcert/admin.crt

 

Enter the keystore password when prompted. If you haven’t updated your keystore password, the default is changeit and you should change it for production environments. When you are prompted to “Trust this certificate?”, input “yes”.

NOTE: Keep track of the “Valid from: xxxxxx” of your signed SSL certificate, you will have to import a new certificate when the current one expires.

By the way, if you encounter error “ANR3704E sdcloud.c(1636): Unable to load the jvm for the cloud storage pool on Windows 2012R2”, update the PATH environment variable on the Spectrum Protect Server:
IBM_Spectrum_Install_Path\Tivoli\TSM\jre\bin\j9vm and also set the JVM_LIB to jvm.dll.

Here’s what your Amazon S3 cloud storage type looks like from IBM Spectrum Protect V7.1.6 Operations Center console:

Operations Center console final result after adding Amazon S3 cloud storage to IBM Spectrum Protect V7.1.6

And you’re off! If you encounter any issues during this process, feel free to reach out to our support team.

You can also learn more by downloading our solution brief.