[opnfv-tech-discuss] Opening nominations for the OPNFV Technical Steering Committee #election

[David McBride]

Today,

In accordance with the schedule

approved by TSC, we begin nominations for a new TSC, consisting of 15
members, per the Community Election Procedure
.  Nominations
will close on July 9 at 5 p.m. (Pacific).

Both the nominator and the nominee must be an active contributor, defined
as having a score of at least 20 on this list
.
Alternatively, per the election procedure, a person may be an active
contributor if an exception was requested for them by a PTL during the
active contributor data review period that concludes today.  This is
indicated by a comment in the notes column of the list
.

You may nominate yourself, or another individual, as long as that
individual agrees to the nomination.  To submit a nomination, please reply
to this email and include the nominees name, organization, and a brief
statement about the nominees qualifications and contributions.

As I received nominations, I will post the information to this wiki page
.

Thank you for your participation in this important activity for the OPNFV
community.  Please let me know if you have any questions.

David

-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23271): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23271
Mute This Topic: https://lists.opnfv.org/mt/32163206/21656
Mute #election: https://lists.opnfv.org/mk?hashtag=election&subid=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] Hunter reelease community awards #hunter # release #awards

[David McBride]

FINAL REMINDER

Nominations close at 5 p.m. (Pacific) today.

On Mon, Jun 17, 2019 at 12:38 PM David McBride 
wrote:

> Reminder.. nomination deadline is this Friday, June 21.
>
> On Wed, Jun 12, 2019 at 3:06 AM David McBride <
> dmcbr...@linuxfoundation.org> wrote:
>
>> Team,
>>
>> The TSC agreed on Tuesday to extend the award nomination deadline to June
>> 21.
>>
>> We still do not have enough nominations, so please keep sending them to
>> me.  Let me know if you have any questions.
>>
>> David
>>
>> On Tue, Jun 4, 2019 at 8:56 PM David McBride <
>> dmcbr...@linuxfoundation.org> wrote:
>>
>>> +Min Yu 
>>>
>>> Thanks to everyone who has provided nominations.  Please keep sending
>>> them to me.  We still need more nominations for all categories.
>>>
>>> I'm publishing the nominations here
>>> .
>>>
>>> David
>>>
>>> On Sun, Jun 2, 2019 at 3:03 PM David McBride <
>>> dmcbr...@linuxfoundation.org> wrote:
>>>
 Reminder...

 I've received very few nominations, so far.  I know that there are
 folks doing good work for the OPNFV community.  Let's make sure they get
 recognized. Please send me those nominations.

 On Wed, May 29, 2019 at 1:35 PM David McBride <
 dmcbr...@linuxfoundation.org> wrote:

> I forgot to ask for a nominating statement.  Sorry for the oversight.
>
> Please specify the following:
>
>- Nominees name
>- Nominees organization
>- Nominees e-mail address
>- Award Category (see list above)
>- Brief nominating statement explaining why the individual
>deserves an award
>
>
> On Tue, May 28, 2019 at 11:34 AM David McBride <
> dmcbr...@linuxfoundation.org> wrote:
>
>> Team,
>>
>> With the Hunter 8.0 release behind us. I'd like to kick off the
>> nomination period for community awards.  Per the community awards
>> procedure, we have the following award categories (with the number of
>> winners in parentheses).
>>
>>- Code development (3)
>>- Community support/leadership (3)
>>- Integration (3)
>>- Testing (3)
>>- Interns (2)
>>
>>
>> Please send your nominations for the above categories by responding
>> to this email by 12 noon, Pacific, on June 7.
>>
>> In your nomination, please specify:
>>
>>- Nominees name
>>- Nominees organization
>>- Nominees e-mail address
>>- Award Category (see list above)
>>
>> After I receive the nominations, I'll send a SurveyMonkey link to the
>> tech-discuss list for voting.
>>
>> Unfortunately, there is not sufficient time prior to the LFN
>> DDF+Plugfest to complete the nomination and vote, so the award winners 
>> will
>> be announced via email some time in the second half of June.
>>
>> Please let me know if you have any questions.
>>
>> David
>>
>> --
>> *David McBride*
>> Release Manager, OPNFV
>> Mobile: +1.805.276.8018
>> Email/Google Talk: dmcbr...@linuxfoundation.org
>> Skype: davidjmcbride1
>> IRC: dmcbride
>>
>
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
>


 --
 *David McBride*
 Release Manager, OPNFV
 Mobile: +1.805.276.8018
 Email/Google Talk: dmcbr...@linuxfoundation.org
 Skype: davidjmcbride1
 IRC: dmcbride

>>>
>>>
>>> --
>>> *David McBride*
>>> Release Manager, OPNFV
>>> Mobile: +1.805.276.8018
>>> Email/Google Talk: dmcbr...@linuxfoundation.org
>>> Skype: davidjmcbride1
>>> IRC: dmcbride
>>>
>>
>>
>> --
>> *David McBride*
>> Release Manager, OPNFV
>> Mobile: +1.805.276.8018
>> Email/Google Talk: dmcbr...@linuxfoundation.org
>> Skype: davidjmcbride1
>> IRC: dmcbride
>>
>
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
>


-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23270): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23270
Mute This Topic: https://lists.opnfv.org/mt/31825133/21656
Mute #hunter: https://lists.opnfv.org/mk?hashtag=hunter&subid=2783016
Mute #awards: https://lists.opnfv.org/mk?hashtag=awards&subid=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] ACTION NEEDED - Please verify community award nominations #awards #hunter

[David McBride]

Team,

Nominations will close in a few hours. Please take a few moments to verify
that your nominations are properly recorded
. If you notice
a problem, please notify me ASAP.

I will start the vote on Monday.  Thanks.

David

-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23269): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23269
Mute This Topic: https://lists.opnfv.org/mt/32163014/21656
Mute #awards: https://lists.opnfv.org/mk?hashtag=awards&subid=2783016
Mute #hunter: https://lists.opnfv.org/mk?hashtag=hunter&subid=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] Hunter 8.1 release - June 28 #release #hunter

[David McBride]

Team,

Hunter 8.1 is scheduled to be release on June 28.

Here are the detailed activities:

   - Weds, June 26 / Complete formal testing
   - Thurs, June 27 / Updaate documentation and cleanup JIRA
   - Fri, June 28 / tag for release

Installer owners and scenario owners, please check the status of CI for
your project.  Please ensure that scenarios are deploying successfully and
passing health check.  Also, scenario owners, please check the intent-to-
release columns on the scenario status page
 for accuracy.

Let me know if you have any questions.

David
-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23268): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23268
Mute This Topic: https://lists.opnfv.org/mt/32161644/21656
Mute #release: https://lists.opnfv.org/mk?hashtag=release&subid=2783016
Mute #hunter: https://lists.opnfv.org/mk?hashtag=hunter&subid=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] Active Contributor List for the 2019 Community Elections #election

[David McBride]

Team,

Today is the final day (June 21, 5 p.m. Pacific) to provide feedback on the
active contributor data.  Note that we have had 3 exception requests to add
individuals to the active contributor list.  Today is also the last day for
TSC members to voice objection to any of those requests.

Let me know if you have any questions.

David

On Mon, Jun 17, 2019 at 1:09 PM David McBride 
wrote:

> Reminder... active contributor list review ends this Friday, June 21.
>
> On Fri, Jun 7, 2019 at 11:44 AM David McBride <
> dmcbr...@linuxfoundation.org> wrote:
>
>> Team,
>>
>> Per the schedule
>> 
>> approved by the TSC earlier this year, the active contributor list
>>  has
>> been published.  Per the community election procedure
>> , the
>> list will be available for review until June 21 at 5 p.m. (Pacific) by
>> project PTLs.
>>
>> In accordance with the election procedure, nominees to the TSC are
>> qualified by having a contribution count of 20 or more on the active
>> contributor list. However, an individual who scores less than 20 may become
>> eligible to be nominated if an OPNFV PTL makes a request
>> 
>> on their behalf.  TSC nominations will begin on June 14, in accordance with
>> the approved schedule.
>>
>> Note that the active contributor list contains 116 names.  This is
>> approximately half of what it was one year ago.  For this reason, we will
>> consider reducing the size of the TSC at the next TSC meeting on June 11.
>>
>> Please let me know if you have any questions.
>>
>> David
>>
>> --
>> *David McBride*
>> Release Manager, OPNFV
>> Mobile: +1.805.276.8018
>> Email/Google Talk: dmcbr...@linuxfoundation.org
>> Skype: davidjmcbride1
>> IRC: dmcbride
>>
>
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
>


-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23267): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23267
Mute This Topic: https://lists.opnfv.org/mt/31977855/21656
Mute #election: https://lists.opnfv.org/mk?hashtag=election&subid=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] DOVETAIL + XCI , Successful Execution

[Panagiotis Karalis]

Hi all,



After my first attempt, which was not so succeed [1], I tried something 
different and using a proper approach.

I've deployed from scratch the XCI installer, having as XCI scenario 
os-nosdn-nofeature-noha.



The results of those tests were much better:



1-  The test scenarios which are related to the healthcheck suite, are run 
properly using the opnfv/functest-healthcheck image (attached logs).

2-  Whatever I have tried from custom tempest test scenarios which are 
related to the opnfv/functest-smoke image, are run properly (attached logs).



The investigation for the rest categories of test scenarios is in progress.

I have uploaded a patch with the impact on dovetail.

The patch is in progress, nothing stable yet.



[1] XCI scenario = os-odl-sfc-noha and executing the SFC test cases (attached 
email)



Have a nice weekend!

BR

Panos





Panagiotis Karalis
Software Engineer

SDN/NFV Team
__
Intracom Telecom
19.7 km Markopoulou Ave., Peania, GR 19002
t:   +30 2106671499
  pkara...@intracom-telecom.com
  www.intracom-telecom.com



















JOIN US

MWC Shanghai

26-28 June
Shanghai, China



GITEX Technology Week

6-10 October

Dubai, UAE



MWC Los Angeles

22-24 October

Los Angeles, USA



Futurecom

28-31 October
Sao Paulo, Brazil



AfricaCom

12-14 November
Cape Town, South Africa



MWC Barcelona

24-27 February 2020

Barcelona, Spain



The information in this e-mail message and any attachments are intended only 
for the individual or entity to whom it is addressed and may be confidential. 
If you have received this transmission in error, and you are not an intended 
recipient, be aware that any copying, disclosure, distribution or use of this 
transmission or its contents is prohibited. Intracom Telecom and the sender 
accept no liability for any loss, disruption or damage to your data or computer 
system that may occur while using data contained in, or transmitted with, this 
email. Views or opinions expressed in this message may be those of the author 
and may not necessarily represent those of Intracom Telecom.





--- Begin Message ---
Hi all,



After an initiative, I've started with a first attempt to introduce the XCI in 
the dovetail and as I promised to David,

I' m sending you this email with my progress so far.

Specifically, I tried to deployed the dovetail on XCI installer and run TCs 
through dovetail tool.



XCI details:

-  OS: Ubuntu (check the rest requirements [1])

-  Flavor: mini (for more details [1])

-  Deploy Scenario: os-odl-sfc-noha and follow the rest instructions 
for SFC deployment with XCI [2]

Waiting until  the XCI deployment is completed.



After that, the dovetail tool installation takes place following  the relevant 
instructions from UG [3] in OPNFV VM of XCI (ssh root@192.168.122.2 
 ).



My first action was to verify that the containers which have been downloaded 
via dovetail project were run properly.

So, using the functest-features:gambia container , I was trying to run 
different test scenarios.

At this point, I noticed that the only scenario that was running properly (for 
my configuration setup and environment) was the SFC test cases.



After that I tried to run the same scenario through dovetail:

-  I prepared a patch in order to trigger this scenario [4].

-  I prepared the env_config.sh and pod.yaml files according to the XCI 
topology and configuration

-  I added in the 'env_config.sh' of dovetail the following parameters

o   DEPLOY_SCENARIO=os-odl-sfc-noha

o   INSTALLER_TYPE=osa

o   INSTALLER_IP=192.168.122.2

o   EXTERNAL_NETWORK=ext-net



The result was partially successfully.

The test scenario has been started and the OS components are created 
successfully (like routes, networks  etc).

At the end, I got an error which seems more or less related to my environment.

As far as I remember, I got the same error when I tried to run the SFC test 
case directly through functest-features:gambia



Another alternative that I tried after the aforementioned results



I used the patch [5] changing the relationship between the SFC test cases and 
the XCI installer.

[This patch makes the SFC TCs independently from each installer, so the 
information like the server's IP is fetched directly from a yaml file that 
prepared by user or by dovetail (the pod.yaml in our case)]  and not by 
installer.



Using this patch, I have skipped the step to add the above parameters in the 
environment file (env_config.sh), since this information is retrieved directly 
from pod.yaml which is copied in the container from dovetail.



BUT the important thing is that the results are much better.



The investigation is in progress! :)



Let me know if there are questions / comments about the above steps or results.

Moreover, If someone have ti

[opnfv-tech-discuss] [functest] a question about using tempest_custom/blacklist.yaml

[xudan]

Hi all,

As Cedric suggested in the Plugfest, Dovetail can use blacklist.yaml to exclude 
some sub test cases from the whole test list (e.g. patrole, refstack_defcore).
I have tried to use blacklist.yaml for patrole and it almost works well except 
a tiny issue.
The scenario condition in tempest_custom/blacklist.yaml seems to be exactly 
match [1] while there is another rally/blacklist.yaml supports to use regular 
expression [2] to match scenarios.
For Dovetail, it should exclude the sub test cases in blacklist for all 
scenarios even the arbitrary strings set by users.
Is there any solution for this? Do I miss something?

BR,
Dan Xu


[1] 
https://github.com/opnfv/functest/blob/stable/hunter/functest/opnfv_tests/openstack/tempest/tempest.py#L369-L375
[2] 
https://github.com/opnfv/functest/blob/stable/hunter/functest/opnfv_tests/openstack/rally/rally.py#L301-L320

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23265): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23265
Mute This Topic: https://lists.opnfv.org/mt/32156487/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] [Yardstick] - Yardstick testcase issues

[jai.parkash via Lists.Opnfv.Org]

Hi Rex,

I have rename the external network to external name this step completed but 
found new error.
Kindly help me find-out the solution.

2019-06-21 07:07:45,947 [DEBUG] yardstick.benchmark.runners.duration 
duration.py:48 class is 
2019-06-21 07:07:45,948 [DEBUG] yardstick.ssh.athena ssh.py:156 user:ubuntu 
host:192.168.28.182
2019-06-21 07:07:46,953 [DEBUG] yardstick.ssh.athena ssh.py:382 Ssh is still 
unavailable: SSHError("Exception  was raised during 
connect. Exception value is: timeout('timed out',)",)
2019-06-21 07:07:48,956 [DEBUG] yardstick.ssh.athena ssh.py:382 Ssh is still 
unavailable: SSHError("Exception  was raised during 
connect. Exception value is: timeout('timed out',)",)
2019-06-21 07:07:50,958 [DEBUG] yardstick.ssh.athena ssh.py:382 Ssh is still 
unavailable: SSHError("Exception  was raised during 
connect. Exception value is: timeout('timed out',)",)
2019-06-21 07:07:52,961 [DEBUG] yardstick.ssh.athena ssh.py:382 Ssh is still 
unavailable: SSHError("Exception  was raised during 
connect. Exception value is: timeout('timed out',)",)
2019-06-21 07:07:54,963 [DEBUG] yardstick.ssh.athena ssh.py:382 Ssh is still 
unavailable: SSHError("Exception  was raised during 
connect. Exception value is: timeout('timed out',)",)
2019-06-21 07:07:56,966 [DEBUG] yardstick.ssh.athena ssh.py:382 Ssh is still 
unavailable: SSHError("Exception  was raised during 
connect. Exception value is: timeout('timed out',)",)
2019-06-21 07:07:58,968 [DEBUG] yardstick.ssh.athena ssh.py:382 Ssh is still 
unavailable: SSHError("Exception  was raised during 
connect. Exception value is: timeout('timed out',)",)
2019-06-21 07:08:00,970 [DEBUG] yardstick.ssh.athena ssh.py:382 Ssh is still 
unavailable: SSHError("Exception  was raised during 
connect. Exception value is: timeout('timed out',)",)
2019-06-21 07:08:02,973 [DEBUG] yardstick.ssh.athena ssh.py:382 Ssh is still 
unavailable: SSHError("Exception  was raised during 
connect. Exception value is: timeout('timed out',)",)
2019-06-21 07:08:04,976 [DEBUG] yardstick.ssh.athena ssh.py:382 Ssh is still 
unavailable: SSHError("Exception  was raised during 
connect. Exception value is: timeout('timed out',)",)
2019-06-21 07:08:06,978 [DEBUG] yardstick.ssh.athena ssh.py:382 Ssh is still 
unavailable: SSHError("Exception  was raised during 
connect. Exception value is: timeout('timed out',)",)
2019-06-21 07:08:08,981 [DEBUG] yardstick.ssh.athena ssh.py:382 Ssh is still 
unavailable: SSHError("Exception  was raised during 
connect. Exception value is: timeout('timed out',)",)
2019-06-21 07:08:10,984 [DEBUG] yardstick.ssh.athena ssh.py:382 Ssh is still 
unavailable: SSHError("Exception  was raised during 
connect. Exception value is: timeout('timed out',)",)

Thanks and Regards
[cid:image001.gif@01D193DD.A31B0ED0]
Jai Parkash
Consultant-Storage Engineering
[Tel]  +91 124 435 8000
[Cel] +91 9717433445
[CVS]   7357 3801
[Email] jai.park...@orange.com
[cid:image007.png@01D2B436.8F6329C0] Plazza 
SkillCenter
www  Sharepoint 
SkillCenter
* Contact the SkillCenter    ( 
DL CORP-STORAGE SKILL-CENTER )
Tower B, 8th Floor, DLF Infinity Towers,
DLF Cyber City Phase - II,
Gurgaon - 122002, Haryana, INDIA
[OINIS_vignette_2017]


From: Limingjiang (Rex) [mailto:limingji...@huawei.com]
Sent: 21 June 2019 07:31
To: PARKASH Jai TGI/OLN
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [Yardstick] - Yardstick testcase issues

The log shows that Yardstick is calling Heat to create the stack.
I think you may need to check Openstack Heat logs to see why the stack creating 
is blocked.

Below is what the stack resources look like when stack is successfully created. 
Compared to your print, the problem may happen on the floating ip creating.

root@b96ea8d56b3c:/home/opnfv/repos/yardstick# openstack stack resource list 
demo-4a2fea01
++-++-+--+
| resource_name  | physical_resource_id 
   | resource_type  | 
resource_status | updated_time |
++-++-+--+
| athena.demo-4a2fea01-fip-assoc | 2846 
   | OS::Neutron::FloatingIPAssociation | 
CREATE_COMPLETE | 2018-10-25T09:15:13Z |
| demo-4a2fea01-test-subnet  | 2e24549d-5903-4023-84c7-12a02da0ad23 
   | OS::Neutron::Subnet