+1. Its relatively easy to write some cron jobs that look at your images and tell you want containers have out of date rpms and need upgrading. its much harder when there are pip packages/virtualenvs involved. Having a nice way to let ops know (or automation know) that there are potential non system packages involved brings needed attention to them.
Thanks, Kevin ________________________________________ From: Jeffrey Zhang [zhang.lei....@gmail.com] Sent: Tuesday, July 26, 2016 5:38 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [kolla] Binary containers with pip install? On Tue, Jul 26, 2016 at 5:00 PM, Dave Walker <em...@daviey.com> wrote: > - Add support to have per project build type, but this is likely a testing > scenario that cannot be reasonably assured. I think this is another feature we can overwrite some variables in certain image. > - Allow source installs in binary containers, but track it as a TODO bug > "Please package foo" (Launchpad has great support for linking to other bug > trackers). Then once this bug is closed, proper binary support can be > resolved. This has the benefit of 'best-effort' towards binary, with a > clear intent to move across. It also allows more testing of the binary > parts that are present, with just the source parts as required. (this is my > favourite) Love this too. Maybe we need a WARNING to the stdout to tell the operators. -- Regards, Jeffrey Zhang Blog: http://xcodest.me __________________________________________________________________________ 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
