The stable/kilo is currently having issues with tests (both stable and
functional) this CR https://review.openstack.org/#/c/205059/ is meant to
fix that, and currently it does fix the unit and doc tests. But I haven't
been able to fix the functional tests. I'm about to start travelling so I
won't b
Hi, all,
This issue has already been resolved.
Thanks a lot.
Xiexs
From: Xie, Xianshan [mailto:[email protected]]
Sent: Friday, August 07, 2015 3:15 PM
To: [email protected]
Subject: [openstack-dev] [CI] nodepool.DiskImageUpdater: Broken pipe error
Hi, everyone,
The Broken
On Fri, Aug 07 2015, Michael Krotscheck wrote:
> Here's the thing. If the middleware is _optional_ like keystone auth, then
> including it via paste.ini makes way more sense. In fact, keystone auth has
> gone to great lengths to have no dependencies for that very same reason.
> If, instead, the mi
Hi Jamie
nice presentation, thanks for sharing it. I have forwarded it to my
students working on federation aspects of Horizon.
About public federated cloud access, the way you envisage it, i.e. that
every user will have his own tailored (subdomain) URL to the SP is not
how it works in the real w
On 07/08/2015 00:11, Dolph Mathews wrote:
>
> As a federated end user in a public cloud, I'd be happy to have a
> custom URL / bookmark for my IdP / domain (like
> http://customer-x.cloud.example.com/ or
> http://cloud.example.com/customer-x) that I need to know to kickoff
>
Hi Tang,
The domain name is not important here, also the master found the log server
using the host you have mentioned in the vars.sh file [1].
[1]
https://github.com/rasselin/os-ext-testing-data/blob/master/vars.sh.sample#L10
On Fri, Aug 7, 2015 at 9:47 AM, Tang Chen wrote:
> Hi Asselin,
>
>
Thanks a lot Juan for your response:)
One question I had was the barbican.sh script would run only the unit tests
after the barbican installation right.
The functional tests needs to be runned explicitly using tox utility.
Thanks and Regards,
Asha Seshagiri
On Sat, Aug 8, 2015 at 3:45 AM, Juan An
Hi
So adding a deprecation warning but saying the “the code is there but not
tested” in Liberty isn’t really doing it right. The deprecation warning should
come in a release where the code is still tested and working (so there is no
danger in breaking customers), but they are warned that they
