Configuration-based installation of OpenShift and Cloud Pak for Data/Integration/Watson AIOps on various private and public cloud infrastructure providers. Deployment attempts to achieve the end-state defined in the configuration. If something fails along the way, you only need to restart the process to continue the deployment.
When running with ./cp-deploy.sh env download --skip-mirror-images on the low-side we had used --skip-mirror-images to avoid a large download of images we already had in a private registry on the high side.
However, this command does not download the CASE files which are also required to install on the high-side even if you already have the images in a private registry as was the case for us. Therefore, to get the CASE files, we had to run the command without the --skip-mirror-images so we effectively had to download the images twice even through we did not need to use the ones downloaded by the Deployer.
Therefore, we believe that this command should always download the CASE files even if --skip-mirror-images is present (as they are relatively small) or we need to have a new option to force the downloading of CASEs when --skip-mirror-images is used.
When running with
./cp-deploy.sh env download --skip-mirror-imageson the low-side we had used--skip-mirror-imagesto avoid a large download of images we already had in a private registry on the high side.However, this command does not download the CASE files which are also required to install on the high-side even if you already have the images in a private registry as was the case for us. Therefore, to get the CASE files, we had to run the command without the
--skip-mirror-imagesso we effectively had to download the images twice even through we did not need to use the ones downloaded by the Deployer.Therefore, we believe that this command should always download the CASE files even if
--skip-mirror-imagesis present (as they are relatively small) or we need to have a new option to force the downloading of CASEs when--skip-mirror-imagesis used.