BU Priority Overview

Red Hat Cloud Services should be an ever-present and leading player in the cloud-native IT space. As such, there are strong usage patterns that customers rely on when using public cloud resources, and the one that drives this priority is that of automation or more specifically, the practice/concept of Infrastructure-as-code. Customers can more swiftly and efficiently provision cloud resources using infrastructure-as-code automation tools, and they have informed us that they wish to do so with our managed OpenShift services just the same.

Goals

• reduce field and customer RFE submission frequency related to infra-as-code by offering infrastructure-as-code automation capable tools and APIs for all appropriate Red Hat cloud services
• give our customers confidence and support in the use of infrastructure-as-code without products and services, just as would be expected from using infra-as-code with the hyperscalers
• measurably improve our APIs to improve security, extensibility and supportability for Red Hat and our customers
• release reliable, stable, secure and industry-standard tools in alignment with our cloud provider partners and relevant ecosystems
• contribute positively to the infrastructure-as-code opensource ecosystem

State of the Business

Delivering fully-functional APIs and Infra-as-code tools to our customers and field teams will allow for vast business growth for our cloud-native services, because many customers consider this kind of functionality as a deal-blocker or highly critical to cloud-journey success.  Infrastructure-as-code automation tools also enable customers to build vast cloud architectures with high efficiency, which drives business to Red Hat services and products, offering very high value to customers.

The Red Hat APIs that serve this business priority will need additional focus to ultimately achieve it.

Execution Plans

• We must continue to drive the existing backlog of improvements and projects that this BU Priority depends on, while also including new capabilities that are always incoming.
• A strong partnership with the Ansible BU and community will also be needed.
• A relationship with the Hashicorp Terraform ecosystem and business unit would be a strong benefit to the outcome of this goal.