[Starlingx-discuss] [Containers] Deployment status
Hi All, ** Baremetal Environment ** Simplex configuration on BareMetal servers without internet access. SUMMARY: * Worked with Erich and Mingyuan to apply the patch for config_controller (storyboard: https://storyboard.openstack.org/#!/story/2004711) * With these patches, we can define a mirror registry during the `config_controller --kubernetes` . Using the new option, config_controller completed without any issues, pulling the required images from our internal registry. * During system-application apply, there are errors related to images still trying to be downloaded from public registry (overriding private registries definitions): * 2019-02-01T17:51:57.394 controller-0 dockerd[2325]: info time="2019-02-01T17:51:57.394492462Z" level=info msg="Attempting next endpoint for pull after error: Get https://quay.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" * Mingyuan mentioned that another patch is in progress for application-apply. Is somebody going to work on it during CNY? Regards, Cristopher Lemus
Hi Cristopher, I don’t believe the commit you reference is ready to merge, it is currently at -1 It also will not address the application images as you noted below. This is Mingyuan’s story, not sure if someone else was lined up to work on this during CNY. Brent From: Lemus Contreras, Cristopher J [mailto:cristopher.j.lemus.contreras@intel.com] Sent: Tuesday, February 5, 2019 1:46 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] [Containers] Deployment status Hi All, ** Baremetal Environment ** Simplex configuration on BareMetal servers without internet access. SUMMARY: - Worked with Erich and Mingyuan to apply the patch for config_controller (storyboard: https://storyboard.openstack.org/#!/story/2004711) - With these patches, we can define a mirror registry during the `config_controller --kubernetes` . Using the new option, config_controller completed without any issues, pulling the required images from our internal registry. - During system-application apply, there are errors related to images still trying to be downloaded from public registry (overriding private registries definitions): o 2019-02-01T17:51:57.394 controller-0 dockerd[2325]: info time="2019-02-01T17:51:57.394492462Z" level=info msg="Attempting next endpoint for pull after error: Get https://quay.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" - Mingyuan mentioned that another patch is in progress for application-apply. Is somebody going to work on it during CNY? Regards, Cristopher Lemus
Hi Brent, We used the commit to verify it, being that the only option that we have for our lab, is to use a local registry. It helped us to check that config_controller completed without errors. So, basically, we are waiting for the story to be completed to unblock us and fully provision our baremetal environments. Thanks & Regards, Cristopher Lemus From: "Rowsell, Brent" <Brent.Rowsell@windriver.com> Date: Tuesday, February 5, 2019 at 1:10 PM To: "Lemus Contreras, Cristopher J" <cristopher.j.lemus.contreras@intel.com>, "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Subject: RE: [Containers] Deployment status Hi Cristopher, I don’t believe the commit you reference is ready to merge, it is currently at -1 It also will not address the application images as you noted below. This is Mingyuan’s story, not sure if someone else was lined up to work on this during CNY. Brent From: Lemus Contreras, Cristopher J [mailto:cristopher.j.lemus.contreras@intel.com] Sent: Tuesday, February 5, 2019 1:46 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] [Containers] Deployment status Hi All, ** Baremetal Environment ** Simplex configuration on BareMetal servers without internet access. SUMMARY: * Worked with Erich and Mingyuan to apply the patch for config_controller (storyboard: https://storyboard.openstack.org/#!/story/2004711) * With these patches, we can define a mirror registry during the `config_controller --kubernetes` . Using the new option, config_controller completed without any issues, pulling the required images from our internal registry. * During system-application apply, there are errors related to images still trying to be downloaded from public registry (overriding private registries definitions): * 2019-02-01T17:51:57.394 controller-0 dockerd[2325]: info time="2019-02-01T17:51:57.394492462Z" level=info msg="Attempting next endpoint for pull after error: Get https://quay.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" * Mingyuan mentioned that another patch is in progress for application-apply. Is somebody going to work on it during CNY? Regards, Cristopher Lemus
participants (2)
-
Lemus Contreras, Cristopher J
-
Rowsell, Brent