Re: [openstack-dev] [Neutron] Mitaka-2

2016-01-25 Thread Lubosz Kosnik

Hello everyone,
I would like to add to that list this [1] and this [2] bug. In my 
opinion they should be fixed ASAP and upstreamed.
Currently I'm working on that and I received feedback from L3 subteam 
and Assaf about implementation and proposed solutions.


Cheers,
Lubosz (diltram) Kosnik

[1] https://bugs.launchpad.net/neutron/+bug/1365461
[2] https://bugs.launchpad.net/neutron/+bug/1375625

On 01/21/2016 01:40 AM, Armando M. wrote:

Hi neutrinos,

The release patch [1] has landed.

The existing workload for the remainder of the cycle is tracked in 
[2]. If you have something shown on this dashboard (or if you don't, 
but you want to), please reach out either via ML (on this thread) or 
on #openstack-neutron.


Cheers,
Armando

[1] https://review.openstack.org/#/c/269265/
[2] https://launchpad.net/neutron/+milestone/mitaka-3


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Neutron] L3-HA - Solution for GW not pingable issue bug/1365461

2016-01-22 Thread Lubosz Kosnik
From the performance perspective it will require additional CPU time 
because of the need to run that bash script.
I will try to prepare it as simple as possible but probability that it 
will kill server when there will be spawned huge amount of routers is 
not so big - after the implementation we can test CPU utilization with 
this validation enabled.


Cheers,
Lubosz (diltram) Kosnik

On 01/22/2016 09:43 AM, Anna Kamyshnikova wrote:

Hi!

This is great that you look into this issue! I think that first 
solution looks more solid, my concern here is how does this will 
affect the performance?


On Thu, Jan 21, 2016 at 12:12 PM, Lubosz Kosnik 
<lubosz.kos...@intel.com <mailto:lubosz.kos...@intel.com>> wrote:


He neutrinos,

Currently I'm working on this bug [1]. Almost one year ago Yoni
Shafrir prepared a patch to fix this issue but he got in review
information that this solution must be changed because it's using
only one script to check the GW availability and because of that
it cannot be used in multi tenat environment.
I tooked his code and was trying to upgrade that code to support
multiple scripts but I was designed separate solution for that.
I would like to know what do you think about this solution.

1. Add bash script generator to neutron/agent/linux/keepalived.py
2. There will be one script per one keepalived instance per node
3. There are two possible solutions for checking is everything is
working OK. Script will verify:
a. That all interfaces are up - internal router interfaces in
namespace, external interface taken from neutron configuration
file and also br-tun/br-int interfaces.
b. That GW is pingable from router NS - there is only one
problem what if GW is not configured in router already - plus we
could ping other network node or other server which IP is
specified in some configuration.

That solution will also fix this issue [2].
I would hear from you what do you think about that two possible
solutions and what do you think about whole solution at all.

Cheers,
Lubosz (diltram) Kosnik

[1] https://bugs.launchpad.net/neutron/+bug/1365461
[2] https://bugs.launchpad.net/neutron/+bug/1375625

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




--
Regards,
Ann Kamyshnikova
Mirantis, Inc


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [Neutron] L3-HA - Solution for GW not pingable issue bug/1365461

2016-01-21 Thread Lubosz Kosnik

He neutrinos,

Currently I'm working on this bug [1]. Almost one year ago Yoni Shafrir 
prepared a patch to fix this issue but he got in review information that 
this solution must be changed because it's using only one script to 
check the GW availability and because of that it cannot be used in multi 
tenat environment.
I tooked his code and was trying to upgrade that code to support 
multiple scripts but I was designed separate solution for that.

I would like to know what do you think about this solution.

1. Add bash script generator to neutron/agent/linux/keepalived.py
2. There will be one script per one keepalived instance per node
3. There are two possible solutions for checking is everything is 
working OK. Script will verify:
a. That all interfaces are up - internal router interfaces in 
namespace, external interface taken from neutron configuration file and 
also br-tun/br-int interfaces.
b. That GW is pingable from router NS - there is only one problem 
what if GW is not configured in router already - plus we could ping 
other network node or other server which IP is specified in some 
configuration.


That solution will also fix this issue [2].
I would hear from you what do you think about that two possible 
solutions and what do you think about whole solution at all.


Cheers,
Lubosz (diltram) Kosnik

[1] https://bugs.launchpad.net/neutron/+bug/1365461
[2] https://bugs.launchpad.net/neutron/+bug/1375625

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [infra] Blocked access to Gerrit account.

2016-01-18 Thread Lubosz Kosnik

Hello everyone,
Yesterday I merged my two accounts on launchpad and after that I cannot 
log in to my account using SSO on OpenStack gerrit.
When I'm logging using my merged account I'm landing in a new account, 
without any reviews, commits and anything else.

Additionally right now there are two available options in owner filter.
When you specify lubosz.kosnik you will see two times the same option 
"Lubosz Kosnik <lubosz.kos...@intel.com" but that are two separate accounts.
Is it possible to merge that two accounts into one or update SSO tokens 
to my old account?

Thank you very much for any help.

---
Lubosz (diltram) Kośnik

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron][L3] Wrong fail over of HA-Router

2016-01-14 Thread Lubosz Kosnik
Here you have an information about that bug - it's a known issue in 
Keepalived v.1.2.7

https://bugs.launchpad.net/neutron/+bug/1497272

Regards,
Lubosz

On 01/14/2016 02:27 AM, Ikuo Kumagai wrote:

Hi All

Could you give me some advice for our problem?

We use Neutron L3-HA.
When I associate/disassociate floating-ip, the state of ha keepalived 
become MASTER/MASTER state. Then
Because at that time,the sending of vrrp packet from MASTER to BACKUP 
stop for 40 seconds.


I checked logs of Keepalived, there is the 40 seconds delay of between 
Log ( Initializing ipvs 2.6) and Log (Opening file ~).

ex is below.
--
Jan 14 09:51:22 stg-anlk-ctrl003 Keepalived_vrrp[1989701]: 
Initializing ipvs 2.6
Jan 14 09:52:02 stg-anlk-ctrl003 Keepalived_vrrp[1989701]: Opening 
file 
'/var/lib/neutron/ha_confs/666d9e40-a95c-44a1-a876-bf44ca281f3e/keepalived.conf'.

--

During this time, the packet of vrrp for MASTER to BACKUP,so BACKUP 
changes to MASTER, and then original MASTER starts sendding  vrrp 
packets again.


The versions of our environment is below
 - Keepalived v1.2.7 (08/14,2013)
 - Linux stg-anlk-ctrl003 3.13.0-74-generic #118-Ubuntu SMP Thu Dec 17 
22:52:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux



We did a adjustement of ha_vrrp_advert_int to avoid this.
But I would like to know why is  the term always 40 seconds.

If you know anything about that please let me know.

Regards
Ikuo Kumagai



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev