-
Story
-
Resolution: Done
-
Critical
-
None
-
None
-
False
-
-
False
-
-
1) Customer account name and number:
Customer account name :NUCLEAR REGULATION AUTHORITY
Account number:MDM-286886
2) Any specific SFDC case numbers associated with this request:
Oppty:5725940
Add support: Red Hat build of Apache Camel for Quarkus on ROSA HCP. Its supported configuration page just says it supports ROSA, and doesn't mention specifically classic or HCP. So, it's understandable that the customer thinks Red Hat build of Apache Camel for Quarkus should support any ROSA.
https://access.redhat.com/articles/7037134
https://access.redhat.com/articles/6507531#camel-44-ga
As Red Hat build of Apache Camel for Quarkus on ROSA HCP is not tested yet, there may be unknown bugs that the customer may encounter.
In addition to Red Hat build of Apache Camel for Quarkus, the customer is planning to use 3scale and Quarkus. ROSA HCP seems to be a more efficient option and the future recommended version. So, any App Dev BU products should support it.
About the importance of this opportunity:
This is the first project to deploy the main system of Nuclear Regulation Authority to a public cloud, and this must be won in order to build the other important system scheduled for CY25 on Red Hat products based architecture.
In addition, each municipality (22 municipalities) has a system for measuring and observing radioactivity as Edge. This is strategically very important as the architecture will be a hybrid cloud configuration of Edge and public cloud (3 or 4 municipalities will be renewed each year after CY25).
Business impact for the Japanese public sector
This is the first ROSA and Middleware project in the government cloud for Japanese public offices (including local governments), and this is a must-win deal to accumulate results in the future business in the Japanese public sector.
QE requirements:
- figure out an access to the ROSA HCP variant
- develop an automation so that Camel team has access to the ROSA type HCP
- test camel quarkus product 1st
- test strategy is to execute the same set of tests as on ROSA -> focusing on interactions with OCP + all supported extension are smoke tests in a consumer/producer fashion
- in case there is an issue with provisioning, QE can one time access by Steve O'Keefe or QE can contact 3Scale team (Andrew Mackenzie or 3Scale QE)