Hi all,
as you have might already heard, I'm no longer involved in Neutron
development due to some changes. Therefore I'm officially stepping down
from the core team because I can't provide same quality reviews as I
tried to do before.
I'd like to thank you all for the opportunity I was given in
Congrats Slawek! I'm sure you'll rock as a driver too!
Kuba
On 27/08/2018 18:42, Miguel Lavalle wrote:
> Dear Neutron team,
>
> In order to help the Neutron Drivers team to perform its very important job
> of guiding the community to evolve the OpenStack Networking architecture to
> meet the
On 31/07/2018 18:46, Matthew Thode wrote:
> On 18-07-31 17:30:02, Jakub Libosvar wrote:
>> Hi all,
>>
>> I want to ask for FFE at this time to bump upper-constraint version of
>> ansible-runner library from 1.0.4 to 1.0.5.
>>
>> Reason: ansible-runner 1.0.4 h
Hi all,
I want to ask for FFE at this time to bump upper-constraint version of
ansible-runner library from 1.0.4 to 1.0.5.
Reason: ansible-runner 1.0.4 has an issue when running with currently
used eventlet version because of missing select.poll() in eventlet [1].
The fix [2] is present in 1.0.5
On 21/04/2018 14:16, Slawomir Kaplonski wrote:
> Hi Neutrinos,
>
> There is time for some spring cleaning now so I went through list of Neutron
> bugs with „gate-failure” tag https://tinyurl.com/y826rccx
> I mark some of them as incomplete if there was not hits of same errors in
> last 30
Thanks for notice. I sent a patch to request a new release:
https://review.openstack.org/#/c/553447/
Jakub
On 15/03/2018 11:28, Jens Harbott wrote:
> The last neutron release for Pike has been made in November, a lot of
> bug fixes have made it into the stable/pike branch, can we please get
> a
Hi all,
I was a bug deputy for the last week and I won't be attending today team
meeting, so here comes my report:
It was very calm, there were no critical bugs reported, some bugs were
already fixed and other got attention and have patches up for review.
Some bugs were also triaged and some
I'm sad reading this. Thanks for everything you did for the community
and best of luck in your new adventures.
Jakub
On 15/12/2017 20:01, Armando M. wrote:
> Hi neutrinos,
>
> To some of you this email may not come as a surprise.
>
> During the past few months my upstream community engagements
Congratulations! Very well deserved! :)
On 01/12/2017 17:45, Lucas Alvares Gomes wrote:
> Hi all,
>
> I would like to welcome Daniel Alvarez to the networking-ovn core team!
>
> Daniel has been contributing with the project for a good time already
> and helping *a lot* with reviews and code.
>
Big +1 for Slawek :)
On 30/11/2017 00:49, Armando M. wrote:
> On 29 November 2017 at 12:27, Korzeniewski, Artur <
> artur.korzeniew...@intel.com> wrote:
>
>> +1 from me , (even though my vote does not count)
>>
>> I know Slawek since Tokyo summit and I’m impressed of his knowledge and
>>
Hi all,
unless there is a person who wants to chair our next Tuesday meeting,
I'd like to cancel it due to OpenStack Summit.
If there is a person who wants to run it, please speak up :)
Thanks,
Jakub
__
OpenStack
Hi all,
I was the bug deputy for the last week and I won't be attending today
the upstream meeting so I'm sending out this report:
There was one critical issue but got attention:
https://bugs.launchpad.net/neutron/+bug/1722967
and just a few bugs that need attention from somebody with broader
+1
On 12/09/2017 21:44, Terry Wilson wrote:
> +1
>
> On Tue, Sep 12, 2017 at 6:23 PM, Miguel Lavalle wrote:
>> Dear Neutrinos,
>>
>> Our social event will take place on Thursday September 12th at 7:30pm. The
>> venue is going to be
On 28/08/2017 21:20, Jeremy Stanley wrote:
> On 2017-08-11 15:31:58 +0200 (+0200), Jakub Libosvar wrote:
> [...]
>> My best hope is they are gonna backport the fix to 4.4.0 and tag a
>> new kernel so we can start running the tests again.
>
> Just to follow up on th
On 24/08/2017 12:47, Ning Yao wrote:
> Hi, all
>
> I encounter a problem about neutron tempest test. I run the tempest
> neutron plugin test against my self-build OpenStack, and I find that
> tempest will run the dvr test and report NotImplementedERROR. I dig
> into the test code and find that
On 10/08/2017 21:16, Jeremy Stanley wrote:
> On 2017-08-10 17:13:58 + (+), Mooney, Sean K wrote:
> [...]
>> so on that it would bre quite trivial to have disk image builder
>> install The linux-image-virtual-hwe-16.04
>> linux-image-virtual-hwe-16.04-edge to pull in a 4.10 or 4.11
>>
On 09/08/2017 18:23, Jeremy Stanley wrote:
> On 2017-08-09 15:29:04 +0200 (+0200), Jakub Libosvar wrote:
> [...]
>> Is it possible to switch used image for jenkins machines to use
>> back the older version? Any other ideas how to deal with the
>> kernel bug?
>
> Mak
] https://review.openstack.org/#/c/492068/1
On 07/08/2017 11:52, Jakub Libosvar wrote:
> Hi all,
>
> as per grafana [1] the functional job is broken. Looking at logstash [2]
> it started happening consistently since 2017-08-03 16:27. I didn't find
> any particular patch in Neutron t
Hi all,
I was bug deputy for the last week and as I'm not gonna attend meeting
today, I'm sending a report here:
There weren't that many urgent things reported last week. Here are some
bugs that needs more eyes:
- https://bugs.launchpad.net/neutron/+bug/1708030 - failure in
functional tests,
Hi all,
as per grafana [1] the functional job is broken. Looking at logstash [2]
it started happening consistently since 2017-08-03 16:27. I didn't find
any particular patch in Neutron that could cause it.
The culprit is that ovsdb starts misbehaving [3] and then we retry calls
indefinitely. We
Hi all,
as sending out a call for help with our precious jobs was very
successful last time and we swept all Python 3 functional from Neutron
pretty fast (kudos the the team!), here comes a new round of failures.
This time I'm asking for your help with
Hi folks,
I'm on personal leave tomorrow and there is also 4th July in the US, so
we're cancelling the meeting tomorrow.
Cheers,
Jakub
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Hi folks,
we've been tracking the OpenStack common goal for Python 3 in our
Neutron CI meetings. As an outcome we created a list of categorized
failures in current non-voting job. There are 250 failures that we split
into 14 categories. The list can be found here:
Hi folks,
due to OpenStack Summit I'm canceling the next Tue May 9th upstream meeting.
Cheers,
Jakub
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
+1
> On 17 Feb 2017, at 2:19 PM, Kevin Benton wrote:
>
> Hi all,
>
> I'm organizing a Neutron social event for Thursday evening in Atlanta
> somewhere near the venue for dinner/drinks. If you're interested, please
> reply to this email with a "+1" so I can get a general
Hi all,
we've been struggling with functional and fullstack jobs for a while
now and we'd like to bring a better stability to it as the failure rate
is still quite high. This is getting annoying, specifically for voting
functional job, which makes it sometimes harder to get some of our
beautiful
Hi,
recently I noticed we got oom-killer in action in one of our jobs [1]. I
saw it several times, so far only with linux bridge job. The consequence
is that usually mysqld gets killed as a processes that consumes most of
the memory, sometimes even nova-api gets killed.
Does anybody know
Sad to see you stepping down. Thanks for making Neutron better and good
luck in your new adventures!
Jakub
On 17/11/2016 19:42, Carl Baldwin wrote:
Neutron (and Openstack),
It is with regret that I report that my work situation has changed such
that I'm not able to keep up with my duties as
On 18/11/2016 12:17, Jakub Libosvar wrote:
On 07/11/2016 23:04, Clark Boylan wrote:
On Mon, Nov 7, 2016, at 01:48 PM, Clark Boylan wrote:
How can you do this? First double check your job logs to see where your
tests are running. The first few lines of your job console logs should
say "
On 07/11/2016 23:04, Clark Boylan wrote:
On Mon, Nov 7, 2016, at 01:48 PM, Clark Boylan wrote:
How can you do this? First double check your job logs to see where your
tests are running. The first few lines of your job console logs should
say "[Zuul] Building remotely on ubuntu-xenial" if
+1
On 14/10/2016 20:30, Miguel Lavalle wrote:
Dear Neutrinos,
I am organizing a social event for the team on Thursday 27th at 19:30.
After doing some Google research, I am proposing Raco de la Vila, which
is located in Poblenou: http://www.racodelavila.com/en/index.htm. The
menu is here:
Hi all,
I promised Armando a braindump of this issue so here it comes:
During my work on fullstack test for VLAN aware VMs I ran into issues
with ARP spoofing. The issue was with subports having different MAC
addresses than MAC address of the parent port. Packets leaving virtual
instance via
On 05/09/16 16:45, Gary Kotton wrote:
Hi,
It is unclear what our policy is with objects. My understanding is that
an object should handle all of the database interaction. Is that not one
of the benefits of the objects? I posted
https://review.openstack.org/#/c/365459 and it has a number of
Hi all,
you might have noticed there was a time period where we run our gate
without functional job. It was my goof that I appended ubuntu-trusty
suffix to functional job [1] while the suffix by default make the job
run on stable branches only. It should be fixed by now [2].
Sorry for
at 1:35 PM, Assaf Muller <as...@redhat.com
<mailto:as...@redhat.com>> wrote:
As Neutron's so called testing lieutenant I would like to
propose
Jakub Libosvar to be a core in the testing area.
Jakub has demonstrated his inherent interest in the
On 04/28/2016 07:29 PM, Martinx - ジェームズ wrote:
> Guys,
>
> I'm trying to enable OVS Firewall Driver in my Cloud Env but, it is not
> working...
>
> I'm trying to replace the following line (openvswitch_agent.ini config
> across the cloud):
You also need to set it for mechanism driver. We are
On 04/11/2016 06:41 PM, Clark Boylan wrote:
> On Mon, Apr 11, 2016, at 03:07 AM, Jakub Libosvar wrote:
>> Hi,
>>
>> recently we hit an issue in Neutron with tests getting stuck [1]. As a
>> side effect we discovered logs are not collected properly which makes it
>
Hi,
recently we hit an issue in Neutron with tests getting stuck [1]. As a
side effect we discovered logs are not collected properly which makes it
hard to find the root cause. The reason of missing logs is that we send
SIGKILL to whatever gate hook is running when we hit the global timeout
per
On 02/03/2016 12:23 PM, Petr Horacek wrote:
> Hello,
>
> would it be possible to change /neutron/agent/ovsdb package into a
> separate library, independent on openstack? It's a pity that there is
> no high-level python library for ovs handling available and your
> implementation seems to be
On 01/14/2016 12:38 AM, Matthew Treinish wrote:
> On Wed, Jan 13, 2016 at 10:47:21PM +, Sean M. Collins wrote:
>> On Wed, Jan 13, 2016 at 03:57:37PM CST, Mooney, Sean K wrote:
>>> One of the ideas that I have been thinking about over the last month or two
>>> is do we
>>> Want to create a
Hi all,
recently I was working on firewall driver [1] that requires latest
features in OVS, specifically conntrack support. In order to get the
driver tested, we need to have the latest OVS kernel modules on machines
running tests but AFAIK there is no stable "2.5 like" release of OVS yet.
On 11/22/2015 07:28 PM, Gal Sagie wrote:
> Hi Fawad,
>
> From what i could understand from Miguel Angel Ajo, someone is working
> on this integration and it
> is suppose to be delivered as part of Mitaka.
> I don't remember the person name, Miguel will sure update shortly.
>
> Gal.
Hi Fawad,
On 07/28/2015 12:09 PM, Wilence Yao wrote:
Hi all,
In devstack, I configured
enable_plugin neutron-lbaas
https://git.openstack.org/openstack/neutron-lbaas
ENABLED_SERVICES+=,q-lbaasv2
so, I can use lbaasv2 api in neutronclient. But I see the agent that's
name is q-lbaasv2
On 05/11/2015 04:13 PM, Kamsali, RaghavendraChari (Artesyn) wrote:
Hi,
I want to use SR-IOV supported nic (intel XL710) NIC for VM
instantiation , so I would like to configure ml2plugin for the intel
XL710 nic , How can could any one help me .
On 01/22/2015 01:00 PM, Ettore zugliani wrote:
I am implementing the precommit part of a mechanism driver (ml2) right
now i'm having problems with sqlalchemy.
I made the class that uses the tables, but when the precommit is called
an error pops up telling that the tables don't exists.
To
It is caused by using old python-openstackclient [1]. We should be using
= 1.0.2 - fix is about to be merged [2].
Kuba
[1] https://bugs.launchpad.net/devstack/+bug/1413252
[2] https://review.openstack.org/#/c/148951/
On 01/22/2015 04:20 AM, Zhou, Zhenzan wrote:
Just noticed that your log has
On 01/14/2015 10:58 AM, yatin kumbhare wrote:
Many of them on gerrit page.
Mine is also one of them.
https://review.openstack.org/#/c/145290/
Regards,
Yatin
The cause is that nova-compute cannot start on stable/juno branch:
On 12/24/2014 10:07 AM, Oleg Bondarev wrote:
On Mon, Dec 22, 2014 at 10:08 PM, Anita Kuno ante...@anteaya.info
mailto:ante...@anteaya.info wrote:
On 12/22/2014 01:32 PM, Joe Gordon wrote:
On Fri, Dec 19, 2014 at 9:28 AM, Kyle Mestery mest...@mestery.com
On 10/22/2014 02:26 AM, Maru Newby wrote:
We merged caching support for the metadata agent in juno, and backported to
icehouse. It was enabled by default in juno, but disabled by default in
icehouse to satisfy the stable maint requirement of not changing functional
behavior.
While
Hi all,
as a part of making db migrations unconditional we need to have all
models easily collectible [1]. Currently we have a head.py file
containing imports to all models. Disadvantage is that all imports need
to be collected manually and maintained in case new module with model is
added to the
On 07/17/2014 12:18 PM, trinath.soman...@freescale.com wrote:
Hi Kevin-
The fix given in the bug report is not working for my CI. I think I need
to wait for the real fix in the main stream.
What version of alembic library did you have at the time of error?
Are you sure you re-run
pip
and Jakub
Libosvar for
their great work on this solution. Also thanks to Salvatore Orlando and
Mark
McClain for mentoring this through to the finish.
[1]
https://wiki.openstack.org/wiki/Governance/TechnicalCommittee/Neutron_Gap_Coverage
[2] https
Hi all,
I'd like to get some opinions on following idea:
Because currently we have (thanks to Ann) WIP of healing script capable
of changing database scheme by comparing tables in the database to
models in current codebase, I started to think whether it could be used
generally to db upgrades
Forgot to add tags, sorry
On 06/09/2014 04:18 PM, Jakub Libosvar wrote:
Hi all,
I'd like to get some opinions on following idea:
Because currently we have (thanks to Ann) WIP of healing script capable
of changing database scheme by comparing tables in the database to
models in current
On 04/22/2014 10:53 AM, Anna Kamyshnikova wrote:
Hello everyone!
I'm working on fixing bug 1307344. I found out solution that will fix
Grenade jobs and will work for online and offline migartions.
https://review.openstack.org/87935 But I faced the problem that Metering
usage won't be fixed
.
Salvatore
On 22 April 2014 11:14, Jakub Libosvar libos...@redhat.com
mailto:libos...@redhat.com wrote:
On 04/22/2014 10:53 AM, Anna Kamyshnikova wrote:
Hello everyone!
I'm working on fixing bug 1307344. I found out solution that will fix
Grenade jobs
On 04/22/2014 03:57 PM, Jakub Libosvar wrote:
On 04/22/2014 02:38 PM, Salvatore Orlando wrote:
When I initially spoke to the infra team regarding this problem, they
suggested that just fixing migrations so that the job could run was
not a real option.
I tend to agree with this statement
Hello,
In Icehouse was introduced new column vif_details and removed
cap_port_filter. During db migration data in cap_port_filter column are
lost and after upgrade the vif_details column is legally empty. This
leads to tempest tests failure when checking port_filter[1].
What would be the impact
Forgot to add tag to subject, sorry about that.
Kuba
On 03/24/2014 05:51 PM, Jakub Libosvar wrote:
Hello,
In Icehouse was introduced new column vif_details and removed
cap_port_filter. During db migration data in cap_port_filter column are
lost and after upgrade the vif_details column
59 matches
Mail list logo