Document building a new container image with VMware VixDiskLib Installed for vSphere SmartState

[agrare]

Due to the VMware redistribution restrictions on the VixDiskLib SDK we cannot simply bundle the library with our appliances or container images.

The customer has to download the VDDK library using their VMware account, accept the VMware terms of service, and install the library on the MIQ filesystem.

For appliances this is relatively easy: https://www.manageiq.org/docs/reference/latest/installing_on_vmware_vsphere/index.html#installing-vmware-vddk-on-manageiq
For podified the customer has to build a container image with this applied on top of our released worker image and tell the operator to use that image for the vmware-operations-worker

[dehawkins512]

@agrare Hi Adam, Are there some steps outlined somewhere I can use to get this doc started? I'm not familiar with these steps. Has someone tested this? re: "build a container image with this applied on top of our released worker image and tell the operator to use that image for the vmware-operations-worker".

[agrare]

Hey @dehawkins512 I don't have steps to build the container image but https://access.redhat.com/documentation/en-us/red_hat_cloudforms/5.0/html/installing_red_hat_cloudforms_on_vmware_vsphere/additional-configuration-vmware#installing-vmware-vddk is how to setup vddk on an appliance and will have similar steps except for the container image building part

cc @Fryguy

[jxadro]

Which is the operator and the image that should be modified?

[b1stern]

@Fryguy @dehawkins512 Have we documented these steps? I need to get this up and running in my environment. Can someone walk me through the process?

[dehawkins512]

@b1stern I do not have the steps documented yet.
@Fryguy Who can step through this and help Ben, then share the specifics so I can doc?
re: For podified the customer has to build a container image with this applied on top of our released worker image and tell the operator to use that image for the vmware-operations-worker.

[Fryguy]

Upstream and downstream are going to be different. For upstream you can just specify the image in the CR, I think - @bdunne? (see below) For downstream we can take that offline ;)

https://github.com/ManageIQ/manageiq-pods/blob/d421748130f0cc6ed739fd0ca56752a9c0b94f8f/manageiq-operator/deploy/crds/manageiq.org_manageiqs_crd.yaml#L41-L44

https://github.com/ManageIQ/manageiq-pods/blob/d421748130f0cc6ed739fd0ca56752a9c0b94f8f/manageiq-operator/deploy/crds/manageiq.org_manageiqs_crd.yaml#L240-L247

[Fryguy]

@bdunne @agrare This came up again recently, and I think we have more experience now to help document this. Can you both together lay out the steps needed (upstream and possibly downstream) to create an image with the VDDK, and get it patched into an existing system. We may also need a note on upgrades after applying the image patch, since the user would have to patch on the next version too.

[bdunne]

ManageIQ/manageiq-pods#666
ManageIQ/manageiq-pods#538

[Fryguy]

Oh, we need to get that into proper documentation, cause that's hidden where it is.

[Fryguy]

@bdunne I guess the problem I see there is that the user has to build it from scratch...I was expecting them to build it on top of an existing "release" image.