Re: [openstack-dev] [kolla] Looking for Docker images for Cinder, Glance etc for oVirt
Leni, Reading their website, they reference the “kollagllue’ namespace. That hasn’t been used for 2+ years (we switched to kolla). They also said a “recent” change in the imges was made to deploy via Ansible “and they weren’t ready for that yet”. That was 3 years ago. I think those docs are all pretty old and could use some validation from the ovirt folks. -Original Message- From: Leni Kadali MutungiReply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Saturday, July 8, 2017 at 11:03 AM To: openstack-dev , "de...@ovirt.org" Cc: users Subject: [openstack-dev] [kolla] Looking for Docker images for Cinder, Glance etc for oVirt Hello all. I am trying to use the Cinder and Glance Docker images you provide in relation to the setup here: http://www.ovirt.org/develop/release-management/features/cinderglance-docker-integration/ I tried to run `sudo docker pull kollaglue/centos-rdo-glance-registry:latest` and got an error of not found. I thought that it could possible to use a Dockerfile to spin up an equivalent of it, so I would like some guidance on how to go about doing that. Best practices and so on. Alternatively, if it is possible, may you point me in the direction of the equivalent images mentioned in the guides if they have been superseded by something else? Thanks. CCing the oVirt users and devel lists to see if anyone has experienced something similar. -- - Warm regards Leni Kadali Mutungi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [kolla] Looking for Docker images for Cinder, Glance etc for oVirt
Hello, Unfortunately we still don't have proper dockerhub uploading mechanism, that's in progress. For now you need to build your own images, here's doc for that: https://docs.openstack.org/kolla/latest/image-building.html Also feel free to join us on #openstack-kolla irc if you have further questions. Cheers, Michal On 8 July 2017 at 11:03, Leni Kadali Mutungiwrote: > Hello all. > > I am trying to use the Cinder and Glance Docker images you provide in > relation to the setup here: > http://www.ovirt.org/develop/release-management/features/cinderglance-docker-integration/ > > I tried to run `sudo docker pull > kollaglue/centos-rdo-glance-registry:latest` and got an error of not > found. I thought that it could possible to use a Dockerfile to spin up > an equivalent of it, so I would like some guidance on how to go about > doing that. Best practices and so on. Alternatively, if it is > possible, may you point me in the direction of the equivalent images > mentioned in the guides if they have been superseded by something else? > Thanks. > > CCing the oVirt users and devel lists to see if anyone has experienced > something similar. > > -- > - Warm regards > Leni Kadali Mutungi > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [kolla] Looking for Docker images for Cinder, Glance etc for oVirt
Hello all. I am trying to use the Cinder and Glance Docker images you provide in relation to the setup here: http://www.ovirt.org/develop/release-management/features/cinderglance-docker-integration/ I tried to run `sudo docker pull kollaglue/centos-rdo-glance-registry:latest` and got an error of not found. I thought that it could possible to use a Dockerfile to spin up an equivalent of it, so I would like some guidance on how to go about doing that. Best practices and so on. Alternatively, if it is possible, may you point me in the direction of the equivalent images mentioned in the guides if they have been superseded by something else? Thanks. CCing the oVirt users and devel lists to see if anyone has experienced something similar. -- - Warm regards Leni Kadali Mutungi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command
On 2017-07-07 18:03:11 -0500 (-0500), Monty Taylor wrote: > On 07/07/2017 12:12 PM, Jeremy Stanley wrote: [...] > > Better still, something like `tox -e venv -- sphinx-build` would > > be more in keeping with the spirit of the PTI to ensure projects > > don't encapsulate any secret sauce into a separate "docs" tox > > env and so can have their documentation built correctly via a > > more standard (for the Python ecosystem) command line. [...] > I'm starting to be of the opinion that we may be stretching things > a little far with the tox -evenv -- in this case and making it > harder not easier. [...] Sure, I agree that the tox invocation is more of an implementation detail. My concern is over making sure that projects don't each end up with their own bespoke docs building process behind some opaque entrypoint on which we've standardized. If we simply say `tox -e docs` is required then we'll end up with a number of projects calling wrapper scripts from that which do all manner of badness before (hopefully still at least) invoking sphinx-build. Sphinx already provides turing-complete flexibility on its own, so when fancy features are required we should do that by improving themes and adding plugins rather than through random hacky wrapper scripts. The detailed plan you outlined in your message (elided for the sake of brevity) seems fine to me. Thanks! -- Jeremy Stanley signature.asc Description: Digital signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev