Sorry, we did the best to get it in... Risk looks high to me. We also
update OpenStack itself from stable/icehouse, which is also risky; +
Mellanox & NSX. To avoid broken master, I'd go with merged, seems to be
working version of ML2, and merge Andrew's patchset into 6.0.
Mike Scherbakov
#mihgen
O
Andrew
AFAIK, extended tests on full HA envs failed due to errors in deployment of
secondary controllers. There is new patchset on review, but I am not sure
that this code is passing extended tests. If it does, then we can consider
merge of your code if it is working with NSX and Mellanox code. I
All issues should be resolved, and CI is passing. Please start testing.
On Thu, Jul 17, 2014 at 4:30 AM, Vladimir Kuklin
wrote:
> Andrew, we have extended system tests passing with our current pacemaker
> corosync code. Either it is your environment or some bug we cannot
> reproduce. Also, it m
Andrew, we have extended system tests passing with our current pacemaker
corosync code. Either it is your environment or some bug we cannot
reproduce. Also, it may be related to puppet ordering issues thus trying to
start some services before some others. As [2] is the only issue you are
pointing a
[2] still has no positive progress, simply making puppet stop the
services isn't all that usefull, will need to move towards always
using over-ride files
[3] is closed as it hasn't occurred in two days
[4] may be closed as its not occuring in CI or on my testing anymore
[5] is closed, was due to [
[2] appears to be made worse, if not caused by neutron services
autostarting with debian, no patch yet, need to add mechanism to ha
layer to generate override files.
[3] appears to have stopped with this mornings master
[4] deleting the cluster, and restarting mostly removed this, was
getting issue
[1] fixed in https://review.openstack.org/#/c/107046/
Thanks for report a bug.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Andrew,
[2] may be due to agents failing to start. Incorrect agents configuration
will lead to agents unability to start and pacemaker timeouts. [3] I do not
see failures in rabbit service as I see that it succesfully transitioned
from stopped to running state. [4] Swift error shows that you have
Friday, resolved the haproxy / vip issue. It was due to loosing
net.ipv4.ip_forward [1] and then we regressed back to not working at
all in HA or Simple. There was also an issue with the neutron keystone
call being cached oddly causing a trace. Removing the ability to cache
the object appears to ha
Retested today
ubuntu single nova vlan - works
centos single nova dhcp - works
ubuntu single neutron gre - works
centos single neutron vlan - works
centos ha(1) neutron vlan - fail haproxy issue
ubuntu ha(1) neutron gre - fail haproxy issue.
haproxy / vip issue:
due to whatever reason that I have
We had a call between Andrew (@xarses), Vladimir Kuklin (@aglarendil) and
myself (@mihgen) today to finally sort out Neutron ML2 integration in Fuel.
We didn't have @xenolog on the call, but hopefully he is more or less fine
with all below, and kindly request him to confirm :)
Discussed following t
>
> Teams from MElanox and VMware based their work on current implementation
> of Neutron
Mlnx appears to not set any neutron settings, so wont be enabled correctly
with out some more TLC
(
https://wiki.openstack.org/wiki/Mellanox-Neutron-Icehouse-Redhat#Neutron_Server_Node
)
NSX appears to be us
After review https://review.openstack.org/#/c/103280/ I have following
thoughts. This patch looks fine, but huge and has lot of changes in
deployment logic. Parallel teams work (vmware, melanox) depends on current
implementation of Neutron in FUEL. I have a some dreads, that they can’t
refactor his
https://review.openstack.org/#/c/103280/ Appears to be in good shape
for https://blueprints.launchpad.net/fuel/+spec/ml2-neutron and has
started passing CI (CentOS). Please review.
On Wed, Jul 2, 2014 at 7:03 AM, Vladimir Kuklin wrote:
> Guys, as we are working on 2 separate implementations of ML
Guys, as we are working on 2 separate implementations of ML2 plugin
support, I suggest to split it into 2 blueprints:
1. https://blueprints.launchpad.net/fuel/+spec/ml2-neutron - this blueprint
is initial ML2 support and is being implemented by Sergey Vasilenko
(@xenolog) and is almost ready and b
15 matches
Mail list logo
