Log In
Back to Designs page

Table of Contents

Related Research

No research entries have been linked to this design.

Resources

Questionnaire results
UXR case study

Additional tags

# acm 1 # caas 1 # caas operator 1 # cluster as a service 3 # cluster creation 2 # cluster templates 1 # developer portal 1 # mce 1 # multi cluster engine 1 # pain points 1

Cluster templates and Developer portal - Questionnaire results

Shiran Hirshberg avatar

Author: Shiran Hirshberg | Last edit: August 01, 2023 | Design type: Research | Product area: Cluster as a Service, OpenShift

Cluster templates and Developer portal - Questionnaire results

Background

We had an opportunity to participate in the OpenShift Commons conference held on June 21, 2023. We had a UXD booth and asked potential users some questions in an online short questionnaire.
Together with the research team, the PM, the dev team, and UX, we gathered in this Miro board, and later on we rewrite it here.

The goal of this questionnaire

We want to ask people at this conference several questions to learn about their needs, current pain points, and features they may need/want to have to ease their daily work. We will focus on questions related to the Template Catalog and talk with both personas: Central-IT/DevOps and developers.

Results and insights

You can find the results summary deck here.

We talked with 32 people who participated in this conference, people who work at large-size companies/organizations such as banking, the Ministry of Defence, IDF, Elbit health care, and more. Half of them are DevOps engineers and some developers and central ITs/Administrators.
18 of the 32 people agreed we will reach out to them later on and left their contact info.

Getting a cluster takes a long time when participants ask administrators for clusters/environments:

  • Getting an empty cluster from the admin can take around a week, sometimes even a month or more
  • Installing a cluster by yourself can take about a day and some have mentioned a week
  • Participants who create clusters themselves and use a self-service portal create empty clusters fast (5 minutes).
  • Developers mostly want a ready-to-use environment
    • For those who use a self-service portal, they said they get a ready-to-use cluster in an hour

The majority of participants who request clusters from admin also keep the clusters as long as they need them

Participants who create clusters themselves tend to create clusters more frequently (daily or weekly)

Having restrictions and quotas by hardware resource is the most suitable solution for the participants:

Restricting by number of clusters is also a suitable solution for many participants 

An empty cluster will not suffice for most participants  

The day-2 configurations increase the time it takes to make a cluster useful (some mentioned it can take a week or a month to reach this state)