Add support for WebSphere Liberty Operator

[git4rk]

• Add a new tab, Configure operator, after Configure application
• Add param IBM Supported: yes/no (default: no)

• If IBM Supported is yes, display these three required params

  • Accept license: checkbox (default: unchecked)

    • I accept the terms on the license agreement corresponding to the version of IBM Program in the application container by setting this value to true. See https://ibm.biz/was-license for the license agreement applicable to this IBM Program. You must accept the license for the installation to work.

  • Edition: drop down with following 3 values (default: none selected)

    • "IBM WebSphere Application Server"
    • "IBM WebSphere Application Server Liberty Core"
    • "IBM WebSphere Application Server Network Deployment"
    • Help text: Product edition

  • Product entitlement source: drop down with following 4 values (default: none selected)

    • "Standalone"
    • "IBM WebSphere Hybrid Edition"
    • "IBM Cloud Pak for Applications"
    • "IBM WebSphere Server Family Edition"
    • Help text: Entitlement source for the product

Notes:

• If IBM Supported is no, install Open Liberty Operator
• If IBM Supported is yes, install WebSphere Liberty Operator
• Use Edition and Product entitlement source values in app deploy yaml
• App deploy yaml also needs Metric parameter. Set it to "Processor Value Unit (PVU)” for "Standalone” and "IBM WebSphere Server Family Edition”, otherwise set it to "Virtual Processor Core (VPC)”.

[majguo]

Based on the procedure of deployment, WLO/OLO should be installed before deploying application image. As a result, I think we should add new tab Configure operator before the existing tab Configure application.

[edburns]

Based on the procedure of deployment, WLO/OLO should be installed before deploying application image. As a result, I think we should add new tab Configure operator before the existing tab Configure application.

I agree with @majguo here. @git4rk can you please weigh in?

[gcharters]

I like the design and agree with Configure operator coming before Configure application. I think we will need some informational text to explain what "IBM Supported" means. Must have licenses to cover deployment, blah, blah.

I think we should also install the License Service operator for supported deployments and provide instructions for where to access the information from it.

[gcharters]

I’ve thought about this a bit more and think the above approach is not quite right.

The license information being provided is specific to the container being deployed. A single operator instance can deploy multiple containers, each under different licenses (e.g. Liberty Core, Liberty Base).

I think we should update the Configure application tab to be: Configure Operator and application (should Operator be uppercase because it’s a specific thing? :/). Feel free to choose a better name. Maybe just Operator and application or Configure deployment.

We should add a param at the top: IBM Supported or Trial: yes/no (default: no)

The rest of the proposal remains the same.

Help information for the new param should say: “Choose yes if your deployments are to be supported under existing WebSphere entitlements (this includes supported deployments of Open Liberty). Choose yes if you are deploying WebSphere Liberty under the Trial license terms. Choose no if you are deploying Open Liberty unsupported”

[majguo]

Thanks @git4rk, @edburns & @gcharters for your comments.

I created the mockup, and you can preview the UI changes using the Create UI Definition Sandbox:

• Open Create UI Definition Sandbox in a new tab of browser.
• Open UI source code createUiDefinition.json in a new tab of the browser.
• Replace the content of work area in Create UI Definition Sandbox with the content of UI source code createUiDefinition.json.
• Click Preview at the left-bottom of Create UI Definition Sandbox.

Also attached the screenshots for quick overview:

• IBM supported: No (default)

• IBM supported: Yes

Please review and respond if you have any comments.

[gcharters]

@majguo this looks good to me.

[majguo]

Per my testing and this doc, IBM WebSphere Server Family Edition should be changed to IBM WebSphere Application Server Family Edition. The screenshot above is also updated.

[git4rk]

@gcharters @edburns @majguo Based on our recent experience/discussion (outside of this offering), I think we need to revisit the design:

• License acceptance and entitlement information applies to WebSphere Liberty Application, not to WLO (WLO is Apache 2.0)
• If customer does not want to deploy an application then we should not require them to accept the license and provide entitlement details.

So, I think, the UI should be like: