[Starlingx-discuss] Docker image list
Hello Starlingxer,
As you know many docker images are pulled during starlingx deployment. It may be fast to pull all these images in America, but it's very slow in China. To speed up starlingx deployment, I have set up a private docker registry for which I sync images every night from upstream registries by cron job. I installed starlingx without using my private docker registry so that I can get the upstream docker image list. Every item in the list is synced every day.
This works fine except that the docker image list changes sometimes. In this case, I would have to collect the image list by deploying without using private docker registry, which is very slow. So I wonder if it's possible to publish the docker image list file together with ISO and tarball on CENGN. I know we do sanity tests for each ISO, maybe we can run 'docker images' in sanity test to collect the docker image list?
Thanks, Cheng
On Mon, Jun 24, 2019 at 2:45 AM Li, Cheng1 cheng1.li@intel.com wrote:
Hello Starlingxer,
As you know many docker images are pulled during starlingx deployment. It may be fast to pull all these images in America, but it’s very slow in China.
To speed up starlingx deployment, I have set up a private docker registry for which I sync images every night from upstream registries by cron job.
I installed starlingx without using my private docker registry so that I can get the upstream docker image list. Every item in the list is synced every day.
This works fine except that the docker image list changes sometimes. In this case, I would have to collect the image list by deploying without using private docker registry, which is very slow.
So I wonder if it’s possible to publish the docker image list file together with ISO and tarball on CENGN. I know we do sanity tests for each ISO, maybe we can run ‘docker images’ in sanity test to collect the docker image list?
I'd love to see the same thing. For the workshop we did at the last summit I would have to deploy, then note what images were deployed, then download them all. Not automatable. If we could publish a list of images per release that would help immensely. :)
Thanks, Curtis
Thanks,
Cheng
Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Echo this request. Publishing a list of images per release is really helping a lot of developers especially who is working behind proxy.
Thanks. BR Austin Sun.
From: Curtis [mailto:serverascode@gmail.com] Sent: Monday, June 24, 2019 7:39 PM To: Li, Cheng1 cheng1.li@intel.com Cc: starlingx-discuss@lists.starlingx.io; Xu, Chenjie chenjie.xu@intel.com Subject: Re: [Starlingx-discuss] Docker image list
On Mon, Jun 24, 2019 at 2:45 AM Li, Cheng1 <cheng1.li@intel.commailto:cheng1.li@intel.com> wrote: Hello Starlingxer,
As you know many docker images are pulled during starlingx deployment. It may be fast to pull all these images in America, but it’s very slow in China. To speed up starlingx deployment, I have set up a private docker registry for which I sync images every night from upstream registries by cron job. I installed starlingx without using my private docker registry so that I can get the upstream docker image list. Every item in the list is synced every day.
This works fine except that the docker image list changes sometimes. In this case, I would have to collect the image list by deploying without using private docker registry, which is very slow. So I wonder if it’s possible to publish the docker image list file together with ISO and tarball on CENGN. I know we do sanity tests for each ISO, maybe we can run ‘docker images’ in sanity test to collect the docker image list?
I'd love to see the same thing. For the workshop we did at the last summit I would have to deploy, then note what images were deployed, then download them all. Not automatable. If we could publish a list of images per release that would help immensely. :)
Thanks, Curtis
Thanks, Cheng
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.iomailto:Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
-- Blog: serverascode.comhttp://serverascode.com
In Mexico we have the same issue. To workaround I created this tool[0] to get the images from the chart tarball and thus be able to populate internal registries. Although this doesn’t work for images required during the ansible playbook run.
For example, this is the output of today’s chart[1].
I hope this can help in the meanwhile an official list is provided.
-[0] https://gitlab.com/erichcm/stx-charts -[1] docker.io/starlingx/stx-fm-rest-api:master-centos-stable-latest docker.io/openstackhelm/magnum:ocata quay.io/attcomdev/ubuntu-source-gnocchi-metricd:3.0.3 gcr.io/google_containers/defaultbackend:1.0 quay.io/attcomdev/ubuntu-source-gnocchi-api:3.0.3 docker.io/openstackhelm/libvirt:ubuntu-xenial-1.3.1-1ubuntu10.24 docker.io/openstackhelm/mariadb:10.2.18 docker.io/prom/memcached-exporter:v0.4.1 docker.io/kolla/ubuntu-source-aodh-evaluator:ocata docker.io/openstackhelm/heat:newton quay.io/attcomdev/ubuntu-source-gnocchi-statsd:3.0.3 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 docker.io/starlingx/stx-mariadb:master-centos-stable-latest docker.io/kolla/ubuntu-source-ceilometer-api:ocata docker.io/starlingx/stx-nova-api-proxy:master-centos-stable-latest docker.io/openstackhelm/horizon:ocata docker.io/port/ceph-config-helper:v1.10.3 docker.io/openstackhelm/heat:ocata-ubuntu_xenial docker.io/openstackhelm/openvswitch:v2.8.1 docker.io/osixia/keepalived:1.4.5 docker.io/mariadb:10.2.13 docker.io/kolla/ubuntu-source-nova-novncproxy:ocata docker.io/postgres:9.5 docker.io/kolla/ubuntu-source-panko-api:ocata quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 docker.io/openstackhelm/ceph-daemon:latest docker.io/kolla/ubuntu-source-ceilometer-central:ocata docker.io/openstackhelm/ironic:ocata docker.io/kolla/ubuntu-source-aodh-notifier:ocata docker.io/memcached:1.5.5 docker.io/nginx:1.13.3 docker.io/mongo:3.4.9-jessie docker.io/prom/mysqld-exporter:v0.10.0 docker.io/openstackhelm/neutron:ocata-sriov-1804 docker.io/docker:17.07.0 docker.io/kolla/ubuntu-source-ceilometer-compute:ocata docker.io/openstackhelm/cinder:ocata docker.io/xrally/xrally-openstack:1.3.0 docker.io/kolla/ubuntu-source-panko-base:ocata docker.io/rabbitmq:3.7-management docker.io/openstackhelm/barbican:ocata docker.io/openstackhelm/heat:ocata docker.io/starlingx/stx-heat:master-centos-stable-latest docker.io/openstackhelm/glance:ocata docker.io/kolla/ubuntu-source-ceilometer-notification:ocata docker.io/openstackhelm/keystone:ocata docker.io/rabbitmq:3.7.13 docker.io/kbudde/rabbitmq-exporter:v0.21.0 docker.io/openstackhelm/placement:ocata-ubuntu_xenial quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 docker.io/openstackhelm/neutron:ocata docker.io/openstackhelm/heat:pike docker.io/starlingx/stx-keystone-api-proxy:master-centos-stable-latest docker.io/kolla/ubuntu-source-aodh-api:ocata docker.io/kolla/ubuntu-source-aodh-listener:ocata docker.io/openstackhelm/nova:ocata docker.io/kolla/ubuntu-source-nova-spicehtml5proxy:ocata quay.io/attcomdev/ubuntu-source-gnocchi-base:3.0.3 docker.io/kolla/ubuntu-source-nova-compute-ironic:ocata docker.io/kolla/ubuntu-source-ceilometer-base:ocata docker.io/kolla/ubuntu-source-ceilometer-collector:ocata docker.io/kolla/ubuntu-source-aodh-base:ocata docker.io/rabbitmq:3.7.13-management
From: "Sun, Austin" austin.sun@intel.com Date: Monday, June 24, 2019 at 8:21 AM To: Curtis serverascode@gmail.com, "Li, Cheng1" cheng1.li@intel.com Cc: "starlingx-discuss@lists.starlingx.io" starlingx-discuss@lists.starlingx.io, "Xu, Chenjie" chenjie.xu@intel.com Subject: Re: [Starlingx-discuss] Docker image list
Echo this request. Publishing a list of images per release is really helping a lot of developers especially who is working behind proxy.
Thanks. BR Austin Sun.
From: Curtis [mailto:serverascode@gmail.com] Sent: Monday, June 24, 2019 7:39 PM To: Li, Cheng1 cheng1.li@intel.com Cc: starlingx-discuss@lists.starlingx.io; Xu, Chenjie chenjie.xu@intel.com Subject: Re: [Starlingx-discuss] Docker image list
On Mon, Jun 24, 2019 at 2:45 AM Li, Cheng1 <cheng1.li@intel.commailto:cheng1.li@intel.com> wrote: Hello Starlingxer,
As you know many docker images are pulled during starlingx deployment. It may be fast to pull all these images in America, but it’s very slow in China. To speed up starlingx deployment, I have set up a private docker registry for which I sync images every night from upstream registries by cron job. I installed starlingx without using my private docker registry so that I can get the upstream docker image list. Every item in the list is synced every day.
This works fine except that the docker image list changes sometimes. In this case, I would have to collect the image list by deploying without using private docker registry, which is very slow. So I wonder if it’s possible to publish the docker image list file together with ISO and tarball on CENGN. I know we do sanity tests for each ISO, maybe we can run ‘docker images’ in sanity test to collect the docker image list?
I'd love to see the same thing. For the workshop we did at the last summit I would have to deploy, then note what images were deployed, then download them all. Not automatable. If we could publish a list of images per release that would help immensely. :)
Thanks, Curtis
Thanks, Cheng
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.iomailto:Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
-- Blog: serverascode.comhttp://serverascode.com
On Mon, Jun 24, 2019 at 8:59 AM Cordoba Malibran, Erich erich.cordoba.malibran@intel.com wrote:
docker.io/openstackhelm/magnum:ocata docker.io/kolla/ubuntu-source-aodh-evaluator:ocata docker.io/openstackhelm/heat:newton docker.io/kolla/ubuntu-source-ceilometer-api:ocata docker.io/openstackhelm/horizon:ocata
[...]
Why are these showing up with 'ocata' and 'newton' in the names/tags? Presumably we are not using Ocata or Newton releases. Is this an artifact of how OpenStack-Helm works?
dt
I don't think all of those images are downloaded during the application-apply, due to overrides selecting a more recent version.
The three phases are where images are downloaded are:
- Initial phase (ansible) - Platform-integ-apps (after unlock) - Stx-openstack (after application-apply)
Would authoring and maintaining a document with these images and versions be a decent way to manage this. (probably in starlingx/config) Or is running scripts the preferred approach?
The readme.rst for starlingx/config is light on contents at the moment https://opendev.org/starlingx/config/src/branch/master/README.rst
Al
-----Original Message----- From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: Monday, June 24, 2019 10:50 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Docker image list
On Mon, Jun 24, 2019 at 8:59 AM Cordoba Malibran, Erich erich.cordoba.malibran@intel.com wrote:
docker.io/openstackhelm/magnum:ocata docker.io/kolla/ubuntu-source-aodh-evaluator:ocata docker.io/openstackhelm/heat:newton docker.io/kolla/ubuntu-source-ceilometer-api:ocata docker.io/openstackhelm/horizon:ocata
[...]
Why are these showing up with 'ocata' and 'newton' in the names/tags? Presumably we are not using Ocata or Newton releases. Is this an artifact of how OpenStack-Helm works?
dt
On 6/26/19 9:48 AM, Bailey, Henry Albert (Al) wrote:
I don't think all of those images are downloaded during the application-apply, due to overrides selecting a more recent version.
The three phases are where images are downloaded are:
- Initial phase (ansible)
- Platform-integ-apps (after unlock)
- Stx-openstack (after application-apply)
Would authoring and maintaining a document with these images and versions be a decent way to manage this. (probably in starlingx/config) Or is running scripts the preferred approach?
I think that since this is dynamic information, it might be better as a script than a fixed document.
Sau!
The readme.rst for starlingx/config is light on contents at the moment https://opendev.org/starlingx/config/src/branch/master/README.rst
Al
-----Original Message----- From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: Monday, June 24, 2019 10:50 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Docker image list
On Mon, Jun 24, 2019 at 8:59 AM Cordoba Malibran, Erich erich.cordoba.malibran@intel.com wrote:
docker.io/openstackhelm/magnum:ocata docker.io/kolla/ubuntu-source-aodh-evaluator:ocata docker.io/openstackhelm/heat:newton docker.io/kolla/ubuntu-source-ceilometer-api:ocata docker.io/openstackhelm/horizon:ocata
[...]
Why are these showing up with 'ocata' and 'newton' in the names/tags? Presumably we are not using Ocata or Newton releases. Is this an artifact of how OpenStack-Helm works?
dt
IS this what you are looking for?
http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/images-cento...
On 2019-06-24 9:20 a.m., Sun, Austin wrote:
Echo this request. Publishing a list of images per release is really helping a lot of developers especially who is working behind proxy.
Thanks.
BR Austin Sun.
*From:*Curtis [mailto:serverascode@gmail.com] *Sent:* Monday, June 24, 2019 7:39 PM *To:* Li, Cheng1 cheng1.li@intel.com *Cc:* starlingx-discuss@lists.starlingx.io; Xu, Chenjie chenjie.xu@intel.com *Subject:* Re: [Starlingx-discuss] Docker image list
On Mon, Jun 24, 2019 at 2:45 AM Li, Cheng1 <cheng1.li@intel.com mailto:cheng1.li@intel.com> wrote:
Hello Starlingxer, As you know many docker images are pulled during starlingx deployment. It may be fast to pull all these images in America, but it’s very slow in China. To speed up starlingx deployment, I have set up a private docker registry for which I sync images every night from upstream registries by cron job. I installed starlingx without using my private docker registry so that I can get the upstream docker image list. Every item in the list is synced every day. This works fine except that the docker image list changes sometimes. In this case, I would have to collect the image list by deploying without using private docker registry, which is very slow. So I wonder if it’s possible to publish the docker image list file together with ISO and tarball on CENGN. I know we do sanity tests for each ISO, maybe we can run ‘docker images’ in sanity test to collect the docker image list?
I'd love to see the same thing. For the workshop we did at the last summit I would have to deploy, then note what images were deployed, then download them all. Not automatable. If we could publish a list of images per release that would help immensely. :)
Thanks,
Curtis
Thanks, Cheng _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io <mailto:Starlingx-discuss@lists.starlingx.io> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
--
Blog: serverascode.com http://serverascode.com
Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
No, this is the list of images we build. The request is for a list of non-starlingx-built images that are pulled at runtime.
From: Scott Little [mailto:scott.little@windriver.com] Sent: Thursday, June 27, 2019 11:06 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Docker image list
IS this what you are looking for?
http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/images-cento...
On 2019-06-24 9:20 a.m., Sun, Austin wrote:
Echo this request. Publishing a list of images per release is really helping a lot of developers especially who is working behind proxy.
Thanks. BR Austin Sun.
From: Curtis [mailto:serverascode@gmail.com] Sent: Monday, June 24, 2019 7:39 PM To: Li, Cheng1 cheng1.li@intel.commailto:cheng1.li@intel.com Cc: starlingx-discuss@lists.starlingx.iomailto:starlingx-discuss@lists.starlingx.io; Xu, Chenjie chenjie.xu@intel.commailto:chenjie.xu@intel.com Subject: Re: [Starlingx-discuss] Docker image list
On Mon, Jun 24, 2019 at 2:45 AM Li, Cheng1 <cheng1.li@intel.commailto:cheng1.li@intel.com> wrote: Hello Starlingxer,
As you know many docker images are pulled during starlingx deployment. It may be fast to pull all these images in America, but it’s very slow in China. To speed up starlingx deployment, I have set up a private docker registry for which I sync images every night from upstream registries by cron job. I installed starlingx without using my private docker registry so that I can get the upstream docker image list. Every item in the list is synced every day.
This works fine except that the docker image list changes sometimes. In this case, I would have to collect the image list by deploying without using private docker registry, which is very slow. So I wonder if it’s possible to publish the docker image list file together with ISO and tarball on CENGN. I know we do sanity tests for each ISO, maybe we can run ‘docker images’ in sanity test to collect the docker image list?
I'd love to see the same thing. For the workshop we did at the last summit I would have to deploy, then note what images were deployed, then download them all. Not automatable. If we could publish a list of images per release that would help immensely. :)
Thanks, Curtis
Thanks, Cheng
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.iomailto:Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
-- Blog: serverascode.comhttp://serverascode.com
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.iomailto:Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Here is a Launchpad so that this activity does not get forgotten, in case anyone wants to pursue it https://bugs.launchpad.net/starlingx/+bug/1834504
Al
From: Penney, Don [mailto:Don.Penney@windriver.com] Sent: Thursday, June 27, 2019 11:11 AM To: Little, Scott; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Docker image list
No, this is the list of images we build. The request is for a list of non-starlingx-built images that are pulled at runtime.
From: Scott Little [mailto:scott.little@windriver.com] Sent: Thursday, June 27, 2019 11:06 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Docker image list
IS this what you are looking for?
http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/images-cento...
On 2019-06-24 9:20 a.m., Sun, Austin wrote:
Echo this request. Publishing a list of images per release is really helping a lot of developers especially who is working behind proxy.
Thanks. BR Austin Sun.
From: Curtis [mailto:serverascode@gmail.com] Sent: Monday, June 24, 2019 7:39 PM To: Li, Cheng1 cheng1.li@intel.commailto:cheng1.li@intel.com Cc: starlingx-discuss@lists.starlingx.iomailto:starlingx-discuss@lists.starlingx.io; Xu, Chenjie chenjie.xu@intel.commailto:chenjie.xu@intel.com Subject: Re: [Starlingx-discuss] Docker image list
On Mon, Jun 24, 2019 at 2:45 AM Li, Cheng1 <cheng1.li@intel.commailto:cheng1.li@intel.com> wrote: Hello Starlingxer,
As you know many docker images are pulled during starlingx deployment. It may be fast to pull all these images in America, but it’s very slow in China. To speed up starlingx deployment, I have set up a private docker registry for which I sync images every night from upstream registries by cron job. I installed starlingx without using my private docker registry so that I can get the upstream docker image list. Every item in the list is synced every day.
This works fine except that the docker image list changes sometimes. In this case, I would have to collect the image list by deploying without using private docker registry, which is very slow. So I wonder if it’s possible to publish the docker image list file together with ISO and tarball on CENGN. I know we do sanity tests for each ISO, maybe we can run ‘docker images’ in sanity test to collect the docker image list?
I'd love to see the same thing. For the workshop we did at the last summit I would have to deploy, then note what images were deployed, then download them all. Not automatable. If we could publish a list of images per release that would help immensely. :)
Thanks, Curtis
Thanks, Cheng
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.iomailto:Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
-- Blog: serverascode.comhttp://serverascode.com
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.iomailto:Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
participants (9)
-
Bailey, Henry Albert (Al)
-
Cordoba Malibran, Erich
-
Curtis
-
Dean Troyer
-
Li, Cheng1
-
Penney, Don
-
Saul Wold
-
Scott Little
-
Sun, Austin