HPE OneSphere

HPE OneSphere

HPE OneSphere was a cloud management platform offered by Hewlett Packard Enterprise (HPE). It was designed to simplify the management of hybrid cloud environments, which typically involve a combination of on-premises infrastructure and resources hosted in public and private clouds.

What are the Goals of the App

I have worked on many features in OneSphere. But here I am showcasing the feature, onboarding Kubernetes on bare-metal.
Easily onboard Kubernetes on bare-metal and manage the clusters from OneSphere.

The problem

Deploying Kubernetes on bare metal servers presents challenges related to hardware compatibility, provisioning complexity, and security, highlighting the need for streamlined solutions and expertise to ensure a successful and secure deployment. And also consider the time consumed to onboard.

The Solution

Streamline the process of attaching nodes and automate the process of creating a master node. Reduce the manual intervention

Building Persona

Task flow

Competitive Analysis

Company Name Product Offering Unique Value Proposition Features

Hewlett Packard Enterprise (HPE)

HPE OneSphere (Cloud Management)

Simplified hybrid cloud management and Kubernetes orchestration.

  • Multi-cloud management
  • Unified interface
  • Cost management
  • Resource provisioning
  • Analytics and insights 
  • Security and compliance

VMware

VMware Tanzu (Kubernetes Platform)

Comprehensive Kubernetes management and development platform.

  • Kubernetes cluster provisioning
  • Application deployment and scaling
  • Monitoring and logging
  • CI/CD integration
  • Multi-cloud support

Red Hat (now part of IBM)

  • OpenShift (Kubernetes Platform)

OpenShift (Kubernetes Platform)

  • Kubernetes orchestration
  • Developer tools and APIs 
  • Security and compliance 
  • CI/CD pipeline integration
  • Extensive partner ecosystem

Google Cloud

Google Kubernetes Engine (GKE)

Managed Kubernetes service on Google Cloud Platform.

  • Automated cluster management
  • Seamless integration with GCP services
  • Scalability and high availability
  • Kubernetes Engine Marketplace

Microsoft

Azure Kubernetes Service (AKS)

Managed Kubernetes container orchestration service on Azure.

  • Integrated with Azure DevOps
  • Monitoring and diagnostics
  • Enterprise-grade security
  • Serverless Kubernetes with Azure Functions

Amazon Web Services (AWS)

Amazon Elastic Kubernetes Service (EKS)

Managed Kubernetes service on AWS.

  • Automatic updates and patching
  • Integration with AWS services
  • Scalable and highly available
  • AWS Marketplace for Kubernetes applications

Wire Frames

User Testing

Conducted multiple rounds of user testing 

  1. First, we did preference testing to understand which design is better than the other designs
  2. Made some modifications based on the feedback received from stakeholders
  3. Conducted moderated user testing on the new design to understand what can be made better and whether users are able to relate to the work they perform
  4. Finally we developed both the options and did a AB testing.

Following are some of the findings from these tests

0
Users tested
0
Users felt its the easiest method
0
Users unable to find which nodes were master nodes
0
mintes to complete the task

Few Verbatiums from the test

Attaching nodes was relatively quick and easy. I had no issues with figuring out how to go about doing this.
I believe that this would be the absolute easiest way to attach nodes, It is quicker and much more efficient than the previous method.
I believe all three nodes were attached as a master node to the cluster. I could be wrong but this is what I can recall

Even though the process was easy for the users, 2 users were unable to understand which node was attached as the master node.  So we went back to the drawing board and made some changes to address that and tested it again. 

Final Designs