We are working towards uncapping all the clients, with the exception of neutron client, because they need to make some incompatible changes on their next major release.

On 07/12/2013 12:12 AM, Gareth wrote:
so, what's the final conclusion about this issue?


On Fri, Jul 12, 2013 at 12:11 PM, Gareth <academicgar...@gmail.com
<mailto:academicgar...@gmail.com>> wrote:

    Thanks, Monty

    but in my review https://review.openstack.org/#/c/36684/ , Doug said
    we will go without upper bound with those python-*clients
    and in this one https://review.openstack.org/#/c/36753/ ,
    keystoneclient still keep '<0.4' and requirements test doesn't fail
    in keystoneclient
    (https://jenkins.openstack.org/job/gate-cinder-requirements/96/console
    it failed on glanceclient)




    On Fri, Jul 12, 2013 at 11:54 AM, Monty Taylor <mord...@inaugust.com
    <mailto:mord...@inaugust.com>> wrote:



        On 07/11/2013 11:38 PM, Gareth wrote:
         > I heard there's a talk about this issue in #openstack-infra
        last night
         > (china standard time), what's the conclusion of that?
         >
         > BTW, how to find meeting log of #openstack-infra? I didn't
        find it
         > in http://eavesdrop.openstack.org/

        We don't log it currently. There is a wider conversation going
        on about
        which things we should log and which things we should not log
        ... but
        for the time being I've submitted this:

        https://review.openstack.org/36773

        to add -infra. I think we talk about enough things that have
        ramifications on everyone in there that we should really capture it.
         > On Thu, Jul 11, 2013 at 11:35 PM, Dirk Müller <d...@dmllr.de
        <mailto:d...@dmllr.de>
         > <mailto:d...@dmllr.de <mailto:d...@dmllr.de>>> wrote:
         >
         >     >> See for example
        https://bugs.launchpad.net/horizon/+bug/1196823
         >     > This is arguably a deficiency of mox, which
        (apparently?) doesn't
         >     let us mock properties automatically.
         >
         >     I agree, but it is just one example. other test-only
        issues can
         >     happen as well.
         >
         >     Similar problem: the *client packages are not
        self-contained, they
         >     have pretty strict dependencies on other packages. One
        case I already
         >     run into was a dependency on python-requests: newer
        python-*client
         >     packages (rightfully) require requests >= 1.x. running
        those on a
         >     system that has OpenStack services from Grizzly or Folsom
        installed
         >     cause a conflict: there are one or two that require
        requests to be <
         >     1.0.
         >
         >     When you run gating on this scenario, I think the same
        flipping would
         >     happen on e.g. requests as well, due to *client or the
        module being
         >     installed in varying order.
         >
         >     Greetings,
         >     Dirk
         >
         >     _______________________________________________
         >     OpenStack-dev mailing list
         > OpenStack-dev@lists.openstack.org
        <mailto:OpenStack-dev@lists.openstack.org>
         >     <mailto:OpenStack-dev@lists.openstack.org
        <mailto:OpenStack-dev@lists.openstack.org>>
         > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
         >
         >
         >
        >
        > --
        > Gareth
        >
        > /Cloud Computing, OpenStack, Fitness, Basketball/
        > /OpenStack contributor/
        > /Company: UnitedStack <http://www.ustack.com>/
        > /My promise: if you find any spelling or grammar mistakes in my email
        > from Mar 1 2013, notify me /
        > /and I'll donate $1 or ¥1 to an open organization you specify./
         >
         >
         > _______________________________________________
         > OpenStack-dev mailing list
         > OpenStack-dev@lists.openstack.org
        <mailto:OpenStack-dev@lists.openstack.org>
         > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
         >

        _______________________________________________
        OpenStack-dev mailing list
        OpenStack-dev@lists.openstack.org
        <mailto:OpenStack-dev@lists.openstack.org>
        http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




    --
    Gareth

    /Cloud Computing, OpenStack, Fitness, Basketball/
    /OpenStack contributor/
    /Company: UnitedStack <http://www.ustack.com>/
    /My promise: if you find any spelling or grammar mistakes in my
    email from Mar 1 2013, notify me /
    /and I'll donate $1 or ¥1 to an open organization you specify./




--
Gareth

/Cloud Computing, OpenStack, Fitness, Basketball/
/OpenStack contributor/
/Company: UnitedStack <http://www.ustack.com>/
/My promise: if you find any spelling or grammar mistakes in my email
from Mar 1 2013, notify me /
/and I'll donate $1 or ¥1 to an open organization you specify./


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Sean Dague
http://dague.net

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to