Ok, thanks for the replies. Seems at least the non k8s images are in use by tripleo and so will remain untouched. caoyuan has a similar patch open to just remove the k8s related images so please have a look and vote on that instead: https://review.openstack.org/#/c/576911/

I'm not sure we need a deprecation cycle on the k8s images given they were directly related to kolla-k8s, that said, we need to remember there are other consumers outside these projects so if people feel we should keep them for a cycle please let me know.

On 26/06/18 16:51, Andy Smith wrote:
Also commented as tripleo is using qdrouterd.

It's use in kolla-ansible
https://github.com/openstack/kolla-ansible/tree/master/ansible/roles/qdrouterd

and bp
https://blueprints.launchpad.net/kolla/+spec/dispatch-router-messaging-component

Thanks,
Andy

On Tue, Jun 26, 2018 at 10:52 AM Alex Schultz <aschu...@redhat.com <mailto:aschu...@redhat.com>> wrote:

    On Tue, Jun 26, 2018 at 8:05 AM, Paul Bourke <paul.bou...@oracle.com
    <mailto:paul.bou...@oracle.com>> wrote:
     > Hi all,
     >
     > At the weekly meeting a week or two ago, we mentioned removing
    some old /
     > unused images from Kolla in the interest of keeping the gate run
    times down,
     > as well as general code hygiene.
     >
     > The images I've determined that are either no longer relevant, or
    were
     > simply never made use of in kolla-ansible are the following:
     >
     > * almanach
     > * certmonger
     > * dind
     > * qdrouterd
     > * rsyslog
     >
     > * helm-repository
     > * kube
     > * kubernetes-entrypoint
     > * kubetoolbox
     >
     > If you still care about any of these or I've made an oversight,
    please have
     > a look at the patch [0]
     >

    I have commented as tripleo is using some of these. I would say that
    you shouldn't just remove these and there needs to be a proper
    deprecation policy. Just because you aren't using them in
    kolla-ansible doesn't mean someone isn't actually using them.

    Thanks,
    -Alex

     > Thanks!
     > -Paul
     >
     > [0] https://review.openstack.org/#/c/578111/
     >
     >
    __________________________________________________________________________
     > OpenStack Development Mailing List (not for usage questions)
     > Unsubscribe:
    openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
    <http://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://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 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

Reply via email to