Re: [opnfv-tech-discuss] [Fds-dev] [APEX] [Euphrates] Euphrates testing - database issues

2017-08-09 Thread Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco) 
Hi Tim,

There were indeed many more processes than 12 per each openstack service. I'm 
running functest with the configuration and seems to run smoothly.

Could you find out why it hasn't been fixed upstream? 

I also looked at ci results. After Danube we made a number of refactoring 
patches and the version Apex uses is not recent enough (when I use latest 
Carbon the results look better). We also haven't merged all of the patches 
still, so this one is on us.

Juraj

-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com] 
Sent: Tuesday, 08 August, 2017 22:45
To: Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco) 
<jlin...@cisco.com>
Cc: opnfv-tech-discuss@lists.opnfv.org; fds-...@lists.opnfv.org
Subject: Re: [Fds-dev] [APEX] [Euphrates] Euphrates testing - database issues

Juraj,
Now I'm thinking this is the same problem as before.  I see we had this in 
Danube:
https://github.com/opnfv/apex/blob/stable/danube/build/baremetal-environment.yaml

which we are not using in master because this problem was supposed to be fixed 
upstream.  Can you try including this file in your overcloud deployment and see 
if it works?

Thanks,

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco)" 
<jlin...@cisco.com>
To: "Tim Rozet" <tro...@redhat.com>, opnfv-tech-discuss@lists.opnfv.org
Cc: fds-...@lists.opnfv.org
Sent: Friday, August 4, 2017 11:44:16 AM
Subject: RE: [Fds-dev] [APEX] [Euphrates] Euphrates testing - database issues

The box is not OOM – it has more than 200GB spare. One thing I forgot to 
mention was that I let the setup as is for a day or two (without doing anything 
with it) and then the issue appeared.

Juraj

From: Tim Rozet [mailto:tro...@redhat.com]
Sent: Friday, 04 August, 2017 16:09
To: Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco) 
<jlin...@cisco.com>; opnfv-tech-discuss@lists.opnfv.org
Cc: fds-...@lists.opnfv.org
Subject: Re: [Fds-dev] [APEX] [Euphrates] Euphrates testing - database issues

Hi Juraj,
This error looks different than the files limit problem.  This actually looks 
to be an error in the python sqlalchemy call, complaining there isn't enough 
ram to spawn a session thread.  Is your box oom?

You can check the daily job's functest results.  I believe it deployed that 
scenario in the last iteration.  Otherwise ping me Monday with the setup and 
I'll try to debug.



Sent via the Samsung Galaxy S®6 active, an AT 4G LTE smartphone

---- Original message ----
From: "Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco)" 
<jlin...@cisco.com<mailto:jlin...@cisco.com>>
Date: 8/4/17 8:34 AM (GMT-05:00)
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: fds-...@lists.opnfv.org<mailto:fds-...@lists.opnfv.org>
Subject: [Fds-dev] [APEX] [Euphrates] Euphrates testing - database issues

Hi Apex team,

I tried an os-odl-fdio-ha euphrates baremetal deployment and I ran into mariadb 
issues when I ran functest: 
https://paste.fedoraproject.org/paste/R4tBkzeub0N2ksYVMsabNg/raw

I've seen this issue before when the number of open files was too low in 
mariadb, but I seems to be fine:
MariaDB [(none)]> show variables like 'open_files_limit';
+--+---+
| Variable_name| Value |
+--+---+
| open_files_limit | 20485 |
+--+---+

Has anyone seen this with any other scenario?

Juraj
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [APEX] [Euphrates] Euphrates testing - database issues

2017-08-04 Thread Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco) 
Hi Apex team,

I tried an os-odl-fdio-ha euphrates baremetal deployment and I ran into mariadb 
issues when I ran functest: 
https://paste.fedoraproject.org/paste/R4tBkzeub0N2ksYVMsabNg/raw

I've seen this issue before when the number of open files was too low in 
mariadb, but I seems to be fine:
MariaDB [(none)]> show variables like 'open_files_limit';
+--+---+
| Variable_name| Value |
+--+---+
| open_files_limit | 20485 |
+--+---+

Has anyone seen this with any other scenario?

Juraj
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] TSC vote requested for Danube 3.0 release

2017-07-13 Thread Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco) 
+1

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Tuesday, 11 July, 2017 17:50
To: opnfv-...@lists.opnfv.org
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] TSC vote requested for Danube 3.0 release

All,

After checking with several scenarios owners during the Release call today, 
there was a consensus that people were ready to tag for the Danube 3.0 release 
on July 14th.  There were some scenarios with degradation compared to 1.0 or 
2.0 releases, but they would be explained in documentations (e.g. due to 
upstream bug).

So, I'd like to ask the TSC members to vote on the following by 5pm Pacific 
Time July 12th.

"Does the TSC approve the Danube 3.0 release date of July 14?  (+1, 0, -1)"

Thanks,

Ray
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [release][announce] RESPONSE REQUIRED / proposed change to release date for Danube 3.0

2017-06-29 Thread Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco) 
On behalf of Frank Brockners,

+1

Juraj

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of David McBride
Sent: Wednesday, 28 June, 2017 20:11
To: TSC OPNFV 
Cc: TECH-DISCUSS OPNFV 
Subject: [opnfv-tech-discuss] [release][announce] RESPONSE REQUIRED / proposed 
change to release date for Danube 3.0

TSC,

After examining status and considering various alternatives, Ray and I have 
agreed to propose July 14 as the new release date for Danube 3.  We believe 
that this will give project and installer teams time to overcome current 
issues, as well as allowing us to avoid the 4th of July holiday in the U.S., 
when many community members will be away on vacation.

Assuming that the TSC approves this change, then I would suggest the following 
schedule:

  *   July 12 - complete testing
  *   July 13 - finish document updates / update JIRA
  *   July 14 - tag repos and release
  *   Week of July 17 - download page goes live
TSC members, please respond to this email with your vote on the following by 
EOD PT June 30:

Does the TSC approve moving the Danube 3.0 release date to July 14th? (+1, 0, 
-1)

David

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] OPNFV D-release naming

2016-08-29 Thread Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco) 
Danube +1

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Monday, 29 August, 2016 7:03
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] OPNFV D-release naming

All,

As discussed on the last TSC call, I'd like to get the process started for the 
D-release naming.

A quick reminder that we have a river theme for OPNFV releases and our first 3 
release names are Arno (Europe), Brahmaputra (Asia), and Colorado (Americas).  
I'd like to continue the tradition of going to different 
continents/geographies, so we could venture into Africa or return to Europe...

Can you send me your top 2-3 nominations (at most) in the following format by 
5pm Pacific Time on September 2nd?  After I collect all the nominations, I'll 
send out a SurveyMonkey poll so the community can pick the winner

Format: River name (locations)
For example,
· Danube (Austria, Germany, Hungary, etc.)
· Draa (Algeria, Morocco)
· etc.

Thanks,

Ray
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss