Hi Steve,
I'v tried stopping all container then modify VIP then do "kolla-ansible
deploy" again. It works as expected and i saw that the endpoint in keystone
database also changed ...magically.
2016年6月5日 下午3:04，"Steven Dake (stdake)" 写道：
Hu,
Thinking more about my proposed workarounds, I don’t th
On 12 June 2016 at 11:31, Thomas Goirand wrote:
> On 06/11/2016 05:02 AM, Robert Collins wrote:
...
> Then keystone.conf ends up installed in /usr/etc/keystone when setup.py
> install is used. With this configuration, it would be installed
> correctly within a venv.
Except that noone uses 'setup.
Dear Infra folks,
Can someone nudge the banderstanch thingy please?
Release in pypi:
https://pypi.python.org/pypi/os-brick/1.4.0
Error in Nova:
http://logs.openstack.org/40/326940/4/check/gate-nova-python34-db/bd55893/console.html#_2016-06-12_00_50_13_521
Thanks,
Dims
--
Davanum Srinivas :: h
The other issue with pinging is that it could even be a false positive. A
ping might stop working before everything is actually setup (e.g.
forwarding entries on other hosts, etc). An explicit status field on the
data model avoids assumptions.
On Jun 11, 2016 16:42, "Antoni Segura Puimedon" <
toni+
On Fri, Jun 10, 2016 at 6:45 PM, Bilal Baqar wrote:
> Hey James
>
> No problem on my side for this change.
>
> Regards
>
> On Fri, Jun 10, 2016 at 3:25 PM, Neil Jerram wrote:
>
>> Me too.
>>
>> On Fri, Jun 10, 2016 at 10:32 AM Cory Benfield wrote:
>>
>>>
>>> > On 8 Jun 2016, at 11:20, James Pag
On Sat, Jun 11, 2016 at 3:03 PM, Mike Spreitzer wrote:
> What about pinging? BTW, from where would the pings come?
>
> In the Docker/Swarm API today there is no way to disable ping. However,
> once Kuryr's libnetwork plugin is updated so that `docker network connect
> --ip=W.X.Y.Z ...` will lat
On 06/11/2016 05:02 AM, Robert Collins wrote:
> The underlying problem is as you say that distutils and setuptools and
> wheel are all different, and until there is a PEP addressing this
> *and* implemented in both wheel and setuptools, we won't get
> consistent behaviour. I'm pretty sure Daniel Ho
2016-06-10 17:01 GMT-07:00 Assaf Muller :
> On Fri, Jun 10, 2016 at 12:02 PM, Andrea Frittoli
> wrote:
>> Dear all,
>>
>> I'm working on making the client manager in Tempest a stable interface, so
>> that in future it may be used safely by plugins to easily gain access
>> service clients [0].
>>
>
Hi,
It looks Spyros already answered your question:
http://lists.openstack.org/pipermail/openstack-dev/2016-June/097083.html . Is
anything else we can help, or you have further questions?
Best regards,
Hongbin
From: zhihao wang [mailto:wangzhihao...@hotmail.com]
Sent: June-11-16 1:03 PM
To: op
Dear Openstack Dev Members:
I would like to install the Magnum on OpenStack to manage Docker Containers.I
have a openstack Liberty production setup. one controller node, and a few
compute nodes.
I am wondering how can I install Openstack Magnum on OpenStack Liberty on
distributed production
What about pinging? BTW, from where would the pings come?
In the Docker/Swarm API today there is no way to disable ping. However,
once Kuryr's libnetwork plugin is updated so that `docker network connect
--ip=W.X.Y.Z ...` will latch onto a matching pre-existing Neutron Port, if
it exists, the
I believe in this particular case it will just be doing get_port for the
specific ports it is waiting to boot. Not polling every ports status for
the lifetime of the port.
On Fri, Jun 10, 2016 at 11:52 PM, Gary Kotton wrote:
> Hi,
> If this is a handful of get_port then it is ok. If is is list_p
12 matches
Mail list logo
