In the case of telcos, where there is a tight maintenance window and network constraints, it is not possible to perform upgrades using the CDN. The approach that we are following, is to create local mirrors, and point the undercloud/overcloud to use those. We are using the following article as a base: https://access.redhat.com/articles/2377701 However, this is still a manual process. Repo creation, undercloud configuration to point to local mirror, still needs to be done manually. Also we miss to document the UpgradeInitCommand, needed to go through major upgrades. The deploy/upgrade process shall support enabling local mirrors, and automate it as much as possible.
I think we should limit the scope on this to the original bug title. Given the existence of a local mirror, we should provide hooks to point to that content in preference to the CDN. I explicitly think we should not automate the repo mirroring itself.
Marius, Are you easily able to validate if the current workflow of the upgrade can consume a local repo on the undercloud ? (configure the upgradeinitcommand to point the yum repo to an undercloud local mirror ?
(In reply to mathieu bultel from comment #2) > Marius, > Are you easily able to validate if the current workflow of the upgrade can > consume a local repo on the undercloud ? (configure the upgradeinitcommand > to point the yum repo to an undercloud local mirror ? I'll give it a try next week and get back with the instructions to this BZ.
I think this is already cover at [1], if it's not please re-open the bugzilla. [1]https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2/html-single/framework_for_upgrades_13_to_16.2/index#configuring-the-overcloud-for-a-leapp-upgrade_preparing-overcloud