On Sat, May 21, 2016 at 2:09 AM, Jeremy Stanley wrote:
> On 2016-05-20 09:52:39 +0800 (+0800), Gerard Braad wrote:
>> It seems jenkins updates the information, but this happens from a
>> working copy
> I'm not sure why "it seems jenkins updates the information" as it
> definitely doesn't. You can
On 19/05/16 17:49 -0400, Zane Bitter wrote:
On 19/05/16 04:20, Thomas Herve wrote:
On Wed, May 18, 2016 at 8:49 PM, Zane Bitter wrote:
I've been lobbying the Mistral developers for $SUBJECT since, basically,
forever.[1][2][3] I like to think after a couple of years I succeeded in
changing thei
Henry is talking about drivers which CURRENTLY support networking-sfc.
In my understanding, ODL driver for networking-sfc is ongoing.
2016-05-23 13:22 GMT+09:00 Elzur, Uri :
> ODL has support for sfc w NSH. Why would ONOS count as backend and ODL not?
>
> Uri
>
> Sent from my iPhone
>
> On May 21,
+1
Best regards,
Kairat Kushaev
On Sat, May 21, 2016 at 1:00 AM, Nikhil Komawar
wrote:
> Hello all,
>
>
> I want to propose having a dedicated virtual sync next week Thursday May
> 26th at 1500UTC for one hour on the Import Refactor work [1] ongoing in
> Glance. We are making a few updates to t
ODL has support for sfc w NSH. Why would ONOS count as backend and ODL not?
Uri
Sent from my iPhone
On May 21, 2016, at 11:26 AM, Henry Fourie
mailto:louis.fou...@huawei.com>> wrote:
Doug,
Networking-sfc API currently has two reference SFC implementations that are
open source:
the OVS driv
Hi all,
Previously Magnum used LBaaS v1. Now LBaaS v1 is deprecated, so we want to
replace it by LBaaS v2. But I met a problem in my patch
https://review.openstack.org/#/c/314060/. I could not figure out why it
didn't work. It seems there are some errors in
http://logs.openstack.org/60/314060/5/ch
Hi, Zane, I think you must be interested in this:
https://review.openstack.org/#/c/308664/
Regards!
---
Lingxian Kong
On Fri, May 20, 2016 at 9:49 AM, Zane Bitter wrote:
> On 19/05/16 04:20, Thomas Herve wrote:
>>
>> On Wed, May 18, 2016 at 8:49 PM, Zane Bitter
Hi all,
This is a reminder that we are going to have the second Higgins team meeting at
tomorrow. Hope to see you all there.
https://wiki.openstack.org/wiki/Higgins#Agenda_for_2016-05-24_0300_UTC
Best regards,
Hongbin
__
Op
> Can we get another nova-core to take a final look at the above patch and
> approve it? That would get the Hyper-V CI tests passing for all open
> Nova patches.
Yep, I was following it all last week waiting for that CI pass report. I
would have been on this already, but unlike you, I know how to
Hello Novaites,
I've noticed that the Intel NFV CI has been failing all test runs for
quite some time (at least a few days), always failing the same tests
around shelve/unshelve operations.
The shelve/unshelve Tempest tests always result in a timeout exception
being raised, looking similar t
The Hyper-V CI system is failing all rescue/unrescue tests with errors
similar to this one:
(tempest.api.compute.servers.test_server_rescue_negative.ServerRescueNegativeTestJSON)_StringException:
Traceback (most recent call last):
File "tempest/test.py", line 279, in setUpClass
six.rerai
This is a little different because it also requires scheduling to multiple
segments (i.e. one network will have DHCP instances on every segment).
There may be some overlap in filtering candidate agents based on their
connectivity properties, but a lot of it will be orthogonal.
On Sun, May 22, 2016
Hi all,
At the Kolla meeting last week, I brought up some of the challenges around the
bootstrapping
process in Kubernetes. The main highlight revolved around how the
bootstrapping process will
work.
Currently, in the kolla-kubernetes spec [1], the process for bootstrapping
involves
outside o
changing pipeline only requires restart ceilometer-agent-compute or
ceilometer-agent-central service, no need to restart nova-compute or
ceilometer-collector
the question is not suitable for dev mailing list, and you have provided
too less info:
* what change do you made? paste the diff
* what do
Hi All,
I'm running with Kilo and I want to make changes to my ceilometer pipeline file
(changing the rate of sampling, in this case). What I did was:
(1) make the changes,
(2) restart the ceilometer agents on the compute [service
openstack-ceilometer-compute restart]
(3) restart the nova agent
Today the DHCP schedulers have support for ‘AZ hints’. My understanding is that
a segment is a subset of an AZ. So why are we not able to leverage that logic
or make it more generic?
Thanks
Gary
On 5/22/16, 4:02 AM, "Carl Baldwin" wrote:
>On Fri, May 20, 2016 at 1:44 PM, Brandon Logan
> wrote:
Thanks!
On 5/22/16 8:46 AM, Djimeli Konrad wrote:
> Hello Nikhil,
>
> I have submitted a prototype solution to the problem
> https://review.openstack.org/319659 . I know it is not very exhaustive
> or efficient, but I would like to get your review and option on the issue.
>
> Thanks
> Konrad
>
--
Hello Nikhil,
I have submitted a prototype solution to the problem
https://review.openstack.org/319659 . I know it is not very exhaustive or
efficient, but I would like to get your review and option on the issue.
Thanks
Konrad
__
Hi all,
We are about to merge Mellanox Cinder CI setup[1] with Mellanox CI[2].
Please note that Mellanox CI[2] will use one account[3] for all its OpenStack
CI activity[4]
FYI.
Lenny Verkhovsky ( lennyb )
[1] https://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_Cinder_CI
[2] https://wiki.o
No problem, I'll do that :)
From: Weyl, Alexey (Nokia - IL) [mailto:alexey.w...@nokia.com]
Sent: Wednesday, May 18, 2016 11:25 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [vitrage] Yaml file validation for Static Physical
datasource
Hi Liat,
I have noticed that you are wor
20 matches
Mail list logo
