[opnfv-tech-discuss] Nominees for Committers-at-Large TSC & Committer Board elections

[Raymond Paik]

All,

Thanks for sending in your nominations for Committers-at-Large TSC and
Committer Board elections.  The nomination window is now closed.  You can
find the list of nominees below (plus on the wiki
 with
nomination statements).

We do have an impressive line up nominees and as Wenjing noted, this is a
testament to the high calibre of our community.  By 8am Pacific Time on
Monday (Sept. 11), eligible committers
 will
be receiving separate Condorcet ballots for the two elections.  I will be
administering the TSC election, and my colleague Min (copied) will be
administering the Board election.

Thanks and please let me know if you have any questions.

Ray
===
[Committers-at-Large TSC]

   - Bin Hu
   - Cédric Ollivier
   - Cristina Pauna
   - Fatih Degirmenci
   - Gabriel/Yuyang
   - Georg Kunz
   - Jose Lausuch
   - Kubi/Gaoliang
   - Maryam Tahhan
   - Prakash Ramchandran
   - Serena Feng
   - Tina Tsou
   - Yujun Zhang

[Committer Board]

   - Dave Neary
   - Hongbo Tian
___
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-tsc] [announce] Opening nominations for Committers-at-Large TSC & Committer Board elections

[Yujun Zhang (ZTE)]

Yes, I accept the nomination.

On Fri, Sep 8, 2017 at 10:38 PM Raymond Paik 
wrote:

> Thanks Julien...
>
> Yujun, do you accept the nomination?
>
> Ray
>
> On Fri, Sep 8, 2017 at 7:06 AM, Julien  wrote:
>
>> Hi all,
>>
>> I would like to nominate Yujun (ZTE) for the TSC at-large
>> election. He has done a great work as QTIP PTL. He has enough knowledge
>> in open source community. He has worked for several open source projects
>> before joining in OPNFV. During his leadership QTIP project cooperates with
>> not only  OPNFV projects but also Openstack projects and great success has
>> been achieved.
>>
>> BR/Julien
>>
>>
>> Raymond Paik 于2017年9月4日周一 上午1:43写道：
>>
>>> All,
>>>
>>> I'm kicking off the nomination process for Committers-at-Large TSC
>>> (electing 5 members) plus the Committer Board (electing 1) elections.
>>>
>>> The list of eligible committers who can run for & vote in both elections
>>> are posted here, and I want to encourage all eligible committers to
>>> nominate community members who can represent the OPNFV technical community
>>> in both the TSC and the Board.  Self nominations are also welcome.   As I
>>> mentioned earlier in the week, I hope to see a diverse group of community
>>> members represented--in terms of geography, gender, projects,  service
>>> providers/vendors, etc.--in the nominations.
>>>
>>> Nominations should be posted to opnfv-tech-discuss & opnfv-tsc mailing
>>> lists by 5pm Pacific Time on September 8th (Friday).  You are welcome to
>>> reply to this email or if you're sending out a separate note, please
>>> include phrases like "Committer Board nomination" or "Committer-at-Large
>>> TSC nomination" in email subjects.  In nomination statements, please list
>>> the following information:
>>>
>>>- Which election (TSC vs. Board) the nomination is for
>>>- Name of the nominee
>>>- Organization
>>>- A brief description of nominee's qualifications
>>>
>>> As nominations are accepted, I will add them to this page
>>> .
>>> There will be separate Condorcet ballot for these two elections, and they
>>> will be sent out by September 11th.
>>>
>>> Thanks,
>>>
>>> Ray
>>>
>>> ___
>>> opnfv-tsc mailing list
>>> opnfv-...@lists.opnfv.org
>>> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
>>>
>>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
-- 
Yujun Zhang
___
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][euphrates] stable branch window

[David McBride]

Reminder...

The stable branch window closes as of MS7, one week from today, on
September 15 at 12 p.m. (PT). PTLs - please contact Aric as soon as you're
ready to branch.  Aric will branch any projects that have not already been
branched on Sept 15.

Let me know if you have any questions.

David

On Tue, Aug 29, 2017 at 3:23 PM, David McBride  wrote:

> Team,
>
> As you know, MS6 was this past Friday, Aug 25.  In addition to the
> requirements associated with MS6, this milestone also marks the opening of
> the stable branch window, which subsequently ends with MS7 on Sept 15.
>
> This means that PTLs may request to branch their project any time before
> Sept 15.  Note that I erroneously told the release meeting this morning
> that PTLs may create their own branch.  That's not the case.  Instead,
> please contact Aric (copied) and request that he create the branch for you.
>
> Also, as a reminder, we have changed the version number format as of the
> Euphrates release.
>
>- 5.0.0 - Euphrates initial release version
>- 5.1.0 - Euphrates SR1
>- 5.2.0 - Euphrates SR2
>
> 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
___
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-tsc] [announce] Opening nominations for Committers-at-Large TSC & Committer Board elections

[SerenaFeng(zte)]

Hi,

Thanks Julien!
Yes, I accept the nomination.

BRs
Serena

On Fri, Sep 8, 2017 at 10:37 PM Raymond Paik 
wrote:

> Thanks Julien...
>
> Serena, do you accept the nomination?
>
> Ray
>
>
> On Fri, Sep 8, 2017 at 6:50 AM, Julien  wrote:
>
>> Hi all,
>>
>> I would like to nominate Serena (ZTE) for the TSC at-large
>> election. She has done a great work in Functest, Releng and QTIP project.
>> As an active committer, she is in charge of TestAPI development, which is
>> consumed by more and more projects, from the basic data store to cli, web
>> portal and CI/CD procedure. She is also an active mentor in community, and
>> she has worked with intern in several projects. I believe she has enough
>> skills and capability for TSC member.
>>
>> BR/Julien
>>
>> Raymond Paik 于2017年9月4日周一 上午1:43写道：
>>
>>> All,
>>>
>>> I'm kicking off the nomination process for Committers-at-Large TSC
>>> (electing 5 members) plus the Committer Board (electing 1) elections.
>>>
>>> The list of eligible committers who can run for & vote in both elections
>>> are posted here, and I want to encourage all eligible committers to
>>> nominate community members who can represent the OPNFV technical community
>>> in both the TSC and the Board.  Self nominations are also welcome.   As I
>>> mentioned earlier in the week, I hope to see a diverse group of community
>>> members represented--in terms of geography, gender, projects,  service
>>> providers/vendors, etc.--in the nominations.
>>>
>>> Nominations should be posted to opnfv-tech-discuss & opnfv-tsc mailing
>>> lists by 5pm Pacific Time on September 8th (Friday).  You are welcome to
>>> reply to this email or if you're sending out a separate note, please
>>> include phrases like "Committer Board nomination" or "Committer-at-Large
>>> TSC nomination" in email subjects.  In nomination statements, please list
>>> the following information:
>>>
>>>- Which election (TSC vs. Board) the nomination is for
>>>- Name of the nominee
>>>- Organization
>>>- A brief description of nominee's qualifications
>>>
>>> As nominations are accepted, I will add them to this page
>>> .
>>> There will be separate Condorcet ballot for these two elections, and they
>>> will be sent out by September 11th.
>>>
>>> Thanks,
>>>
>>> Ray
>>>
>>> ___
>>> opnfv-tsc mailing list
>>> opnfv-...@lists.opnfv.org
>>> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
>>>
>>
> ___
> opnfv-tsc mailing list
> opnfv-...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [dovetail] [docs] Dovetail docs

[Georg Kunz]

Hi Wenjing,

> On that note, we probably need some help in the process of properly
> release/publish docs. Can we have a volunteer?

Picking up this point here. The obvious choice would be to publish our 
documentation on docs.opnfv.org and link those from cvp.opnfv.org. We should 
have a chat with the docs folks on how to get Dovetail integration done. I can 
take the initial discussions.

@Sofia: shall we have a chat next week?

Cheers
Georg


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

Re: [opnfv-tech-discuss] [dovetail] Dovetail team gerrit group

[Wenjing Chu]

Thanks Georg!

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Georg Kunz
Sent: Friday, September 08, 2017 11:21 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [dovetail] Dovetail team gerrit group

Hi Dovetailers,

As briefly discussed during today's project meeting, I have created a group 
called "Dovetail Team" in Gerrit [1] to simplify adding reviewers to patches. 
Right now, the group contains the committers listed in the project's INFO file 
[2]. However, I named the group "Dovetail Team" instead of "Dovetail 
Committers" to keep it open for everyone interested in reviewing our work.

So, if you want to be included in this group, let me know (or maybe you can 
even add yourself using the link below).

[1] https://gerrit.opnfv.org/gerrit/#/admin/groups/63,members
[2] 
https://gerrit.opnfv.org/gerrit/gitweb?p=dovetail.git;a=blob;f=INFO;h=470b7ca884bcb76f73fee7ba7772fa857e1b0373;hb=refs/heads/master

Cheers
Georg
___
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-tsc] [announce] Opening nominations for Committers-at-Large TSC & Committer Board elections

[Tim Rozet]

I would like to nominate Dave Neary for Committer Board nomination.  Dave has 
been an active TSC member since the beginning of OPNFV and has always provided 
the community with technical and open source guidance.  Dave is also a commiter 
of the dovetail project and member of the C committee.


Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Raymond Paik" 
To: "Dan Lilliehorn" 
Cc: opnfv-...@lists.opnfv.org, "svc-armband" , 
opnfv-tech-discuss@lists.opnfv.org
Sent: Friday, September 8, 2017 11:56:35 AM
Subject: Re: [opnfv-tech-discuss] [opnfv-tsc] [announce] Opening nominations 
for Committers-at-Large TSC & Committer Board elections

Thanks Dan... Noted that Cristina has accepted the nomination. 

Ray 

On Fri, Sep 8, 2017 at 8:51 AM, Dan Lilliehorn < dan.lillieh...@enea.com > 
wrote: 





Hi all 



I’m proud to hereby nominate Cristina Pauna of the ARMBand project to the role 
as a Committer-at-large representative on the OPNFV TSC. 



Cristina is one of the most experienced members of the ARMBand team and has 
recently taken over the scrum master role for the Enea ARMBand team (which also 
means she’s the primary representative for the project in eg the OPNFV release 
meetings). 

Among many contributive efforts to the ARMBand project, the ARM infrastructure 
in OPNFV and OPNFV in general her most significant contributions have been in 
the functest scope. 

She was the first to get deployment of OPNFV on virtual ARM PODs working, which 
is an important part of running eg functest on ARM-based Jenkins slaves. 

Also, she has been the ARMBand point of contact in our discussions with eg the 
Doctor and Dovetail projects. 



I’m confident Cristina would be a creative and driving contributor in the TSC 
as she is in ARMBand. 

And her charm and great sense of humor is a great contribution to any group! J 



This nomination is endorsed by Bob and Cristina has already accepted to be 
nominated (she asked me to relay this as she may not have access to email 
during the weekend). 



Best Regards and Have a Great Weekend! 



-- 

Dan Lilliehorn 

Director of Cloud Technologies 

Research & Development 

Email dan.lillieh...@enea.com 

Phone +46 709 71 4494 



Enea Software AB 

Jan Stenbecks Torg 17 

Box 1033, SE-164 21 Kista, Sweden 

Phone +46 8 507 140 00 



www.enea.co m 





This message, including attachments, is CONFIDENTIAL. It may also be privileged 
or otherwise protected by law. If you received this email by mistake please let 
us know by reply and then delete it from your system; you should not copy it or 
disclose its contents to anyone. All messages sent to and from Enea may be 
monitored to ensure compliance with internal policies and to protect our 
business. Emails are not secure and cannot be guaranteed to be error free as 
they can be intercepted, amended, lost or destroyed, or contain viruses. The 
sender therefore does not accept liability for any errors or omissions in the 
contents of this message, which arise as a result of email transmission. Anyone 
who communicates with us by email accepts these risks. 



From: opnfv-tsc-boun...@lists.opnfv.org [mailto: 
opnfv-tsc-boun...@lists.opnfv.org ] On Behalf Of Raymond Paik 
Sent: den 3 september 2017 19:43 
To: opnfv-tech-discuss@lists.opnfv.org ; opnfv-...@lists.opnfv.org 
Subject: [opnfv-tsc] [announce] Opening nominations for Committers-at-Large TSC 
& Committer Board elections 





All, 





I'm kicking off the nomination process for Committers-at-Large TSC (electing 5 
members) plus the Committer Board (electing 1) elections. 





The list of eligible committers who can run for & vote in both elections are 
posted here , and I want to encourage all eligible committers to nominate 
community members who can represent the OPNFV technical community in both the 
TSC and the Board. Self nominations are also welcome. As I mentioned earlier in 
the week, I hope to see a diverse group of community members represented--in 
terms of geography, gender, projects, service providers/vendors, etc.--in the 
nominations. 





Nominations should be posted to opnfv-tech-discuss & opnfv-tsc mailing lists by 
5pm Pacific Time on September 8th (Friday). You are welcome to reply to this 
email or if you're sending out a separate note, please include phrases like 
"Committer Board nomination" or "Committer-at-Large TSC nomination" in email 
subjects. In nomination statements, please list the following information: 


* Which election (TSC vs. Board) the nomination is for 
* Name of the nominee 
* Organization 
* A brief description of nominee's qualifications 


As nominations are accepted, I will add them to this page . There will be 
separate Condorcet ballot for these two elections, and they will be sent out by 
September 11th. 





Thanks, 





Ray 





___
opnfv-tech-discuss mailing list

[opnfv-tech-discuss] [dovetail] Dovetail team gerrit group

[Georg Kunz]

Hi Dovetailers,

As briefly discussed during today's project meeting, I have created a group 
called "Dovetail Team" in Gerrit [1] to simplify adding reviewers to patches. 
Right now, the group contains the committers listed in the project's INFO file 
[2]. However, I named the group "Dovetail Team" instead of "Dovetail 
Committers" to keep it open for everyone interested in reviewing our work.

So, if you want to be included in this group, let me know (or maybe you can 
even add yourself using the link below).

[1] https://gerrit.opnfv.org/gerrit/#/admin/groups/63,members
[2] 
https://gerrit.opnfv.org/gerrit/gitweb?p=dovetail.git;a=blob;f=INFO;h=470b7ca884bcb76f73fee7ba7772fa857e1b0373;hb=refs/heads/master

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

[opnfv-tech-discuss] OpenContrail support in OPNFV

[Stuart Mackie]

Original reply got caught by some Microsoft security “feature”


We didn’t make it with Danube due to lack of OpenContrail support for Mikata in 
time.

We are very close to a working deployment with Euphrates (but fighting a 
hardware issue in our lab right now). We should make it into Euphrates release. 
These are “vanilla” OpenContrail scenarios just testing with Tempest and Rallye 
– but include all the standard OpenContrail features, like L2/L3 networks, L3 
services like ACL-based network policy, ECMP, service chaining, BGP peering 
from controller to gateways, BPGaaS in vRouter, etc.

What specific requirements do you have?

Stuart
-914 886 2534


On 9/8/17, 1:08 PM, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
SULLIVAN, BRYAN L (BRYAN L)"  wrote:

Hi all,

Whoever is working on any OCL scenarios for Danube or Euphrates, please let 
me know the status of that work, e.g. which scenarios are deployable, and what 
is the latest build that is deployable. We had not been actively testing with 
OCL but it is a key part of our AIC (AT Integrated Cloud) platform, and I 
need to be sure that it's included in OPNFV supported scenarios. So though we 
are not the technical experts that would develop the scenarios, we would like 
to work with whoever is, to test the scenarios and ensure that they are 
supported in Dovetail asap.

Looking forward to any advice on this.
…
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] OpenContrail support in OPNFV

[Stuart Mackie]

We didn’t make it with Danube due to lack of OpenContrail support for Mikata in 
time. 

We are very close to a working deployment with Euphrates (but fighting a 
hardware issue in our lab right now). We should make it into Euphrates release. 
These are “vanilla” OpenContrail scenarios just testing with Tempest and Rallye 
– but include all the standard OpenContrail features, like L2/L3 networks, L3 
services like ACL-based network policy, ECMP, service chaining, BGP peering 
from controller to gateways, BPGaaS in vRouter, etc.

What specific requirements do you have?

Stuart
-914 886 2534

On 9/8/17, 1:08 PM, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
SULLIVAN, BRYAN L (BRYAN L)"  wrote:

Hi all,

Whoever is working on any OCL scenarios for Danube or Euphrates, please let 
me know the status of that work, e.g. which scenarios are deployable, and what 
is the latest build that is deployable. We had not been actively testing with 
OCL but it is a key part of our AIC (AT Integrated Cloud) platform, and I 
need to be sure that it's included in OPNFV supported scenarios. So though we 
are not the technical experts that would develop the scenarios, we would like 
to work with whoever is, to test the scenarios and ensure that they are 
supported in Dovetail asap.

Looking forward to any advice on this.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


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

Re: [opnfv-tech-discuss] [dovetail] Where to find the latest documentation

[Ildiko Vancsa]

Hi Wenjing,

Thank you for the wiki update with the links to the artifacts, it helps to find 
the right bits and pieces to read.

Best Regards,
Ildikó


> On 2017. Sep 6., at 12:30, Wenjing Chu  wrote:
> 
> They are all automatically rendered and updated continuously as part of 
> normal dev process - please look at the artifact repos/URLs for HTML.
> 
> The wiki page is manual and for developers to coordinate their work only. 
> These are works in progress, none is published yet, if that's what you are 
> looking for. 
> 
> On that note, we probably need some help in the process of properly 
> release/publish docs. Can we have a volunteer?
> 
> Regards
> Wenjing
> 
> -Original Message-
> From: Ildiko Vancsa [mailto:ildiko.van...@gmail.com] 
> Sent: Tuesday, September 05, 2017 5:28 PM
> To: Wenjing Chu 
> Cc: opnfv-tech-discuss@lists.opnfv.org
> Subject: Re: [opnfv-tech-discuss] [dovetail] Where to find the latest 
> documentation
> 
> Hi Wenjing,
> 
> Thank you for the update.
> 
> I hoped there’s a published version which is updated continuously, but I will 
> check the open reviews in the meantime and keep an eye on the wiki for the 
> updates.
> 
> Thanks and Best Regards,
> Ildikó
> 
> 
>> On 2017. Sep 5., at 10:52, Wenjing Chu  wrote:
>> 
>> Hi Ildiko,
>> 
>> We are at the last few days of having the documentation ready for review. 
>> I'll be updating the wiki with the rendered docs in the next few days.
>> Thanks for checking in and the links should be coming up soon.
>> 
>> Regards
>> Wenjing
>> 
>> -Original Message-
>> From: opnfv-tech-discuss-boun...@lists.opnfv.org 
>> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ildiko 
>> Vancsa
>> Sent: Tuesday, September 05, 2017 10:04 AM
>> To: opnfv-tech-discuss@lists.opnfv.org
>> Subject: [opnfv-tech-discuss] [dovetail] Where to find the latest 
>> documentation
>> 
>> Hi Dovetail Team,
>> 
>> I’m trying to catch up on the work you are doing to get a better view on the 
>> plans on the certification and testing activities. I checked the wiki page 
>> and found Gerrit review links on documentation changes and test plans, but I 
>> couldn’t find a link to the latest version of the docs.
>> 
>> Could you please point me to where to find the latest rendered version of 
>> the documentation that you’re working on?
>> 
>> Thanks and Best Regards,
>> Ildikó Váncsa
>> Ecosystem Technical Lead, OpenStack Foundation 
>> ___
>> opnfv-tech-discuss mailing list
>> opnfv-tech-discuss@lists.opnfv.org
>> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> 

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

[opnfv-tech-discuss] OpenContrail support in OPNFV

[SULLIVAN, BRYAN L (BRYAN L)]

Hi all,

Whoever is working on any OCL scenarios for Danube or Euphrates, please let me 
know the status of that work, e.g. which scenarios are deployable, and what is 
the latest build that is deployable. We had not been actively testing with OCL 
but it is a key part of our AIC (AT Integrated Cloud) platform, and I need to 
be sure that it's included in OPNFV supported scenarios. So though we are not 
the technical experts that would develop the scenarios, we would like to work 
with whoever is, to test the scenarios and ensure that they are supported in 
Dovetail asap.

Looking forward to any advice on this.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [barometer] Weekly Call

[Tahhan, Maryam]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:GMT Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T01
TZOFFSETFROM:+
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Tahhan, Maryam":MAILTO:maryam.tah...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Power, Da
 mien":MAILTO:damien.po...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Mcmahon, 
 Tony B":MAILTO:tony.b.mcma...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Campbell,
  Wesley":MAILTO:wesley.campb...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Ray, Bj":M
 AILTO:bj@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Duignan, 
 Andrew":MAILTO:andrew.duig...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Parker, 
 Daniel'":MAILTO:daniel.par...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Foley, Em
 ma L":MAILTO:emma.l.fo...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Pavan Gup
 ta:MAILTO:pavan.gu...@calsoftinc.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Korynkevy
 ch, RomanX":MAILTO:romanx.korynkev...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Mario To
 rrecillas Rodriguez':MAILTO:mario.rodrig...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Chornyi, 
 TarasX":MAILTO:tarasx.chor...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'GUPTA, A
 LOK'":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'MORTON, 
 ALFRED C (AL)'":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Lawrence
  Lamers':MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Shobhan 
 AyyadevaraSesha (sayyadev)':MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Seiler, G
 lenn (Wind River)":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Scott Ma
 nsfield':MAILTO:scott.mansfi...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Bernier,
  Daniel (520165)'":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Canio Ci
 llis':MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Tomasini
 , Lorenzo'":MAILTO:lorenzo.tomas...@fokus.fraunhofer.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Srinivas
 a Chaganti':MAILTO:schaga...@versa-networks.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Laporte,
  Laurent [CTO]'":MAILTO:laurent.lapo...@sprint.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Ola Lilj
 edahl':MAILTO:ola.liljed...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Jaggi, M
 anish'":MAILTO:manish.ja...@cavium.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Gabor Ha
 lász':MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='杨艳':
 MAILTO:yangya...@chinamobile.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'SULLIVAN
 , BRYAN L'":MAILTO:bs3...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Andrew V
 eitch':MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'DRUTA, D
 AN'":MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Javier A
 rauz':MAILTO:j.javier.ar...@gmail.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Sen, Pro
 dip'":MAILTO:prodip@hpe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Alan McN
 amee':MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Kedalagud
 de, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Gherghe, 
 Calin":MAILTO:calin.gher...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Murthy, K
 rishna J":MAILTO:krishna.j.mur...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Pierre L
 ynch':MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Sun, Ning"
 :MAILTO:ning@intel.com

Re: [opnfv-tech-discuss] [Auto] Error when create onap pods using kubernetes

[Michael O'Brien]

Tina,
 Definitely, I will be at the OPNFV meeting on Monday – thanks for the 
invite.
 /michael

From: Tina Tsou [mailto:tina.t...@arm.com]
Sent: Friday, September 8, 2017 00:20
To: Michael O'Brien 
Cc: huangxiangyu ; 
opnfv-tech-discuss@lists.opnfv.org; onap-disc...@lists.onap.org
Subject: Re: [opnfv-tech-discuss] [Auto] Error when create onap pods using 
kubernetes

Dear Michael,

Would you like to attend next Monday 6am PT's Auto meeting? So we can keep the 
communication with all the Auto committers by screen sharing.

Meeting information is at the wiki page.
https://wiki.opnfv.org/pages/viewpage.action?pageId=12390343

Thank you,
Tina

On Sep 7, 2017, at 8:59 PM, Michael O'Brien 
> wrote:
Harry,
   Hi, some comments.
   The nginx containers – we are not deploying these, since they are in the 
default namespace they don’t look part of a normal rancher setup as well – I am 
curious where these 2 pods came from and why you would need a reverse proxy – 
also verify you are running rancher on 8880 to avoid 80/8080 conflicts with 
these.
I am suspicious of this reverse proxy – I would expect your forwarding 
issues stem from these 2 servers – normally used to manage a private subnet – 
they might not be handling IPV6 traffic (I remember an issue with this in 
general from a couple years ago)

default   nginx-deployment-431080787-6chxv   1/1   Running  
  0  1d
default   nginx-deployment-431080787-9nswb   1/1   Running  
  0  1d

I would recommend you run on Ubuntu 16.04 not 14 – may work OK but all our 
examples assume 16 and we have not tested 14 (note that I had issues with 17).
In a build before last Saturday – I did see the same 3 pods fail to come up 
vnc-portal, sdc-be and sdc-fe – make sure you have pulled from master this week 
- (try a git pull) – then reset your config pod via the following if any new 
content comes in.
https://wiki.onap.org/display/DW/ONAP+on+Kubernetes#ONAPonKubernetes-Delete/Rerunconfig-initcontainerfor/dockerdata-nfsrefresh

The aai-gremlin pod is not required and can be ignored for now – but it 
normally starts up – see the OOM-Kubernetes status section on

https://wiki.onap.org/display/DW/ONAP+master+branch+Stabilization#ONAPmasterbranchStabilization-20170907:OOMKubernetes

 thank you
 /michael



From: huangxiangyu [mailto:huangxiang...@huawei.com]
Sent: Thursday, September 7, 2017 22:56
To: Michael O'Brien >; 
Tina Tsou >
Cc: 
opnfv-tech-discuss@lists.opnfv.org; 
onap-disc...@lists.onap.org
Subject: 答复: [opnfv-tech-discuss] [Auto] Error when create onap pods using 
kubernetes

Hi Michael

Here the environment info：
Distributor ID: Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04
Codename:   trusty

I didn’t check the pod status after I saw the Error message. Seems this ipv6 
error didn't stop pod creating process maybe this error only leads to no ipv6 
address for every pod.
Here the pods status:
NAMESPACE NAME   READY STATUS   
  RESTARTS   AGE
default   nginx-deployment-431080787-6chxv   1/1   Running  
  0  1d
default   nginx-deployment-431080787-9nswb   1/1   Running  
  0  1d
kube-system   heapster-4285517626-7vnf3  1/1   Running  
  0  7d
kube-system   kube-dns-646531078-x4h83   3/3   Running  
  0  7d
kube-system   kubernetes-dashboard-716739405-6pz6n   1/1   Running  
  20 7d
kube-system   monitoring-grafana-3552275057-03wqg1/1   Running  
  0  7d
kube-system   monitoring-influxdb-4110454889-527nw   1/1   Running  
  0  7d
kube-system   tiller-deploy-737598192-5d3hc  1/1   Running  
  0  7d
onap  config-init0/1   
Completed  0  1d
onap-aai  aai-dmaap-522748218-2jc3p  1/1   Running  
  0  1d
onap-aai  aai-kafka-2485280328-3kd9x 1/1   Running  
  0  1d
onap-aai  aai-resources-353718113-3h81b  1/1   Running  
  0  1d
onap-aai  aai-service-3321436576-twmwf   1/1   Running  
  0  1d
onap-aai  aai-traversal-338636328-vxxd3  1/1   Running  
  0  1d
onap-aai  aai-zookeeper-1010977228-xtflg 1/1   Running  
  0  1d
onap-aai  

Re: [opnfv-tech-discuss] [opnfv-tsc] [announce] Opening nominations for Committers-at-Large TSC & Committer Board elections

[Dan Lilliehorn]

Hi all

I’m proud to hereby nominate Cristina Pauna of the ARMBand project to the role 
as a Committer-at-large representative on the OPNFV TSC.

Cristina is one of the most experienced members of the ARMBand team and has 
recently taken over the scrum master role for the Enea ARMBand team (which also 
means she’s the primary representative for the project in eg the OPNFV release 
meetings).
Among many contributive efforts to the ARMBand project, the ARM infrastructure 
in OPNFV and OPNFV in general her most significant contributions have been in 
the functest scope.
She was the first to get deployment of OPNFV on virtual ARM PODs working, which 
is an important part of running eg functest on ARM-based Jenkins slaves.
Also,  she has been the ARMBand point of contact in our discussions with eg the 
Doctor and Dovetail projects.

I’m confident Cristina would be a creative and driving contributor in the TSC 
as she is in ARMBand.
And her charm and great sense of humor is a great contribution to any group! ☺

This nomination is endorsed by Bob and Cristina has already accepted to be 
nominated (she asked me to relay this as she may not have access to email 
during the weekend).

Best Regards and Have a Great Weekend!

--
Dan Lilliehorn
Director of Cloud Technologies
Research & Development
Email  dan.lillieh...@enea.com
Phone  +46 709 71 4494

Enea Software AB
Jan Stenbecks Torg 17
Box 1033, SE-164 21 Kista, Sweden
Phone  +46 8 507 140 00

www.enea.com

[cid:image002.png@01D00576.7D651240]
This message, including attachments, is CONFIDENTIAL. It may also be privileged 
or otherwise protected by law. If you received this email by mistake please let 
us know by reply and then delete it from your system; you should not copy it or 
disclose its contents to anyone. All messages sent to and from Enea may be 
monitored to ensure compliance with internal policies and to protect our 
business. Emails are not secure and cannot be guaranteed to be error free as 
they can be intercepted, amended, lost or destroyed, or contain viruses. The 
sender therefore does not accept liability for any errors or omissions in the 
contents of this message, which arise as a result of email transmission. Anyone 
who communicates with us by email accepts these risks.

From: opnfv-tsc-boun...@lists.opnfv.org 
[mailto:opnfv-tsc-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: den 3 september 2017 19:43
To: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org
Subject: [opnfv-tsc] [announce] Opening nominations for Committers-at-Large TSC 
& Committer Board elections

All,

I'm kicking off the nomination process for Committers-at-Large TSC (electing 5 
members) plus the Committer Board (electing 1) elections.

The list of eligible committers who can run for & vote in both elections are 
posted 
here,
 and I want to encourage all eligible committers to nominate community members 
who can represent the OPNFV technical community in both the TSC and the Board.  
Self nominations are also welcome.   As I mentioned earlier in the week, I hope 
to see a diverse group of community members represented--in terms of geography, 
gender, projects,  service providers/vendors, etc.--in the nominations.

Nominations should be posted to opnfv-tech-discuss & opnfv-tsc mailing lists by 
5pm Pacific Time on September 8th (Friday).  You are welcome to reply to this 
email or if you're sending out a separate note, please include phrases like 
"Committer Board nomination" or "Committer-at-Large TSC nomination" in email 
subjects.  In nomination statements, please list the following information:

  *   Which election (TSC vs. Board) the nomination is for
  *   Name of the nominee
  *   Organization
  *   A brief description of nominee's qualifications
As nominations are accepted, I will add them to this 
page.
  There will be separate Condorcet ballot for these two elections, and they 
will be sent out by September 11th.

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] [Pharos] Pharos lab for ARM band

[Alexandru Avadanii]

Hi,
We don't have such patches, nor do we plan to support old Fuel any more.
We actually don't intend to mix architectures for the new Fuel either, at least 
not in the near future.

If you want to support this use-case, you will have to implement it yourself.
I do think the new Fuel is friendlier to this scenario, but again, we never 
looked into it.

BR,
Alex


From: Srikanth Lingala [mailto:srikanth.ling...@nxp.com]
Sent: Friday, September 08, 2017 4:21 PM
To: Alexandru Avadanii; opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Cc: svc-armband; Bob Monkman; Shai Tsur; Gorja Gorja; Trinath Somanchi; 
Veera.reddy B
Subject: RE: [Pharos] Pharos lab for ARM band

OK...So, If I apply some patches to Fuel and rebuild Fuel ISO, can I deploy 
with mixed (x86 and aarch64) targets in Pharos POD?
If so, can you please point me to those patches?

Regards,
Srikanth.

From: Alexandru Avadanii [mailto:alexandru.avada...@enea.com]
Sent: Friday, September 08, 2017 5:54 PM
To: Srikanth Lingala 
>; 
opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Cc: svc-armband >; Bob 
Monkman >; Shai Tsur 
>; Gorja Gorja 
>; Trinath Somanchi 
>; Veera.reddy B 
>
Subject: RE: [Pharos] Pharos lab for ARM band

Hi,
That is correct, everything is now AArch64 in our PODs.

BR,
Alex


From: Srikanth Lingala [mailto:srikanth.ling...@nxp.com]
Sent: Friday, September 08, 2017 11:48 AM
To: Alexandru Avadanii; 
opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Cc: svc-armband; Bob Monkman; Shai Tsur; Gorja Gorja; Trinath Somanchi; 
Veera.reddy B
Subject: RE: [Pharos] Pharos lab for ARM band

Hi Alex,
Thanks for the details.
I viewed the following link for reference:
https://wiki.opnfv.org/display/pharos/Enea+Hosting

So, in the current ENEA Pharos lab, you are using ARM based machines as OS 
Controller nodes, Compute nodes and even Jump Host node. Not using any hybrid 
POD (with combination of x86 and ARM machines as nodes). Right?

Regards,
Srikanth.

From: Alexandru Avadanii [mailto:alexandru.avada...@enea.com]
Sent: Friday, September 08, 2017 12:49 AM
To: Srikanth Lingala 
>; 
opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Cc: svc-armband >; Bob 
Monkman >; Shai Tsur 
>
Subject: RE: [Pharos] Pharos lab for ARM band

Hi, Srikanth,
I'm glad to hear about new AArch64 hardware joining OPNFV.

First, note that Pharos specs require 5 nodes, which depending on the scenario 
can be used as 3 controllers + 2 computes, or 1 controller + computes.
This makes it hard to mix x86 and ARM targets in a Pharos POD. Therefore, this 
is not supported by OPNFV Danube 3.0 Fuel - it is not impossible, but it is out 
of our current scope.
To add some complexity to that, we have the additional jump server host, which 
used to be x86 up to and including the Danube release cycle; starting with the 
E release, Armband only support all-AArch64 PODs, including the jump host.

Also note that the old Fuel (used up to and including Danube) was replaced by 
the new Fuel, based on Mirantis Cloud Platform (MCP), which on its own means a 
lot of changes in the way we build and provision the OS images (bootstrap and 
final image) on the AArch64 nodes.
Starting with the E release, there is no more bootstrap building, all images 
(Ubuntu Xenial) are fetched from official Ubuntu Cloud Archive (UCA) repos and 
used as-is.

As for old bootstrap building, x86 instructions still apply [1], with only one 
extra arg required (--target_arch=arm64).

To summarize, I recommend looking into the current Armband/Fuel codebase 
(master branch) and prepare for using MCP-based Fuel instead of the old Danube 
codebase.
To add a lab in OPNFV, you will need 6 x AArch64 nodes (5 for the cluster and 
one for the jump host).

BR,
Alex

[1] 

Re: [opnfv-tech-discuss] [opnfv-tsc] [announce] Opening nominations for Committers-at-Large TSC & Committer Board elections

[Jose Lausuch]

Hi,

Thank you Rosella!
Yes, I accept the nomination.

Regards,
Jose

> On 08 Sep 2017, at 16:37, Raymond Paik  wrote:
> 
> Thanks Rossella
> 
> Jose, do you accept the nomination?
> 
> Ray
> 
> On Fri, Sep 8, 2017 at 3:57 AM, Rossella Sblendido  > wrote:
> Hi all,
> 
> I'd like to nominate Jose Lausuch for the Committers-at-Large TSC board.
> Jose has done a great job as Functest PTL for Danube and Euphrates. He
> got a developer award in Beijing and has server as a mentor for the
> internship program. He's a very active and respected member of the
> community, he could be a great addition to the TSC.
> 
> Rossella
> 
> On 09/03/2017 07:42 PM, Raymond Paik wrote:
> > All,
> >
> > I'm kicking off the nomination process for Committers-at-Large TSC
> > (electing 5 members) plus the Committer Board (electing 1) elections.
> >
> > The list of eligible committers who can run for & vote in both elections
> > are posted here  Committers for 
> > Elections>, and I want
> > to encourage all eligible committers to nominate community members who
> > can represent the OPNFV technical community in both the TSC and the
> > Board.  Self nominations are also welcome.   As I mentioned earlier in
> > the week, I hope to see a diverse group of community members
> > represented--in terms of geography, gender, projects,  service
> > providers/vendors, etc.--in the nominations.
> >
> > Nominations should be posted to opnfv-tech-discuss & opnfv-tsc mailing
> > lists by 5pm Pacific Time on September 8th (Friday).  You are welcome to
> > reply to this email or if you're sending out a separate note, please
> > include phrases like "Committer Board nomination" or "Committer-at-Large
> > TSC nomination" in email subjects.  In nomination statements, please
> > list the following information:
> >
> >   * Which election (TSC vs. Board) the nomination is for
> >   * Name of the nominee
> >   * Organization
> >   * A brief description of nominee's qualifications
> >
> > As nominations are accepted, I will add them to this page
> >  > >.  There
> > will be separate Condorcet ballot for these two elections, and they will
> > be sent out by September 11th.
> >
> > Thanks,
> >
> > Ray
> >
> >
> >
> > ___
> > opnfv-tsc mailing list
> > opnfv-...@lists.opnfv.org 
> > https://lists.opnfv.org/mailman/listinfo/opnfv-tsc 
> > 
> >
> 

___
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-tsc] [announce] Opening nominations for Committers-at-Large TSC & Committer Board elections

[Tianhongbo]

yes，I humble accept it.
thanks
--
田红波 hongbo
M:+86-13501965752
E:hongbo.tianhon...@huawei.com
产品与解决方案-云核心网NFV研究部
Products & Solutions-NFV Research Dept,CCN
发件人：Raymond Paik
收件人：Wenjing Chu,
抄 送：opnfv-tsc,opnfv-tech-discuss,
时间：2017-09-08 05:54:38
主 题：Re: [opnfv-tech-discuss] [opnfv-tsc] [announce] Opening nominations for 
Committers-at-Large TSC & Committer Board elections

Wenjing, thanks for getting things started on the board as well.

Hongbo & Morgan, do you accept your nominations (for Morgan there are actually 
2 nominations for TSC & Board)?

Cheers,

Ray

On Thu, Sep 7, 2017 at 11:48 AM, Wenjing Chu 
> wrote:
It’s great to see all the high caliber candidates for  Committers-at-Large TSC 
members – a good sign for a vibrate community.

In that spirit, I like to start with the committer board nomination as well.

I like to nominate Hongbo Tian (Huawei) for committer board member. Hongbo has 
been the long time PTL of dovetail dedicating a lot of hard work to help bring 
Dovetail to near its first launch. He’s also a big contributor to and an 
organizer of each of the Plugfests. The board can benefit from more voices from 
the trenches.

I’d also like to nominate Morgan Richomme (Orange) for another term of 
committer Board member and committer-at-large TSC member. Not only that Morgan 
is uniquely qualified based on his leadership in Functest (the first and only 
project graduated from incubation so far) and test working group, and Pharos, 
but also that his collaborative and constructive style brings huge value to a 
project – and similarly to the TSC and board. So I hope Morgan can step forward 
for both again.

Regards
Wenjing

On 03/09/2017 19:42, Raymond Paik wrote:
All,

I'm kicking off the nomination process for Committers-at-Large TSC (electing 5 
members) plus the Committer Board (electing 1) elections.

The list of eligible committers who can run for & vote in both elections are 
posted here, and I want to 
encourage all eligible committers to nominate community members who can 
represent the OPNFV technical community in both the TSC and the Board.  Self 
nominations are also welcome.   As I mentioned earlier in the week, I hope to 
see a diverse group of community members represented--in terms of geography, 
gender, projects,  service providers/vendors, etc.--in the nominations.

Nominations should be posted to opnfv-tech-discuss & opnfv-tsc mailing lists by 
5pm Pacific Time on September 8th (Friday).  You are welcome to reply to this 
email or if you're sending out a separate note, please include phrases like 
"Committer Board nomination" or "Committer-at-Large TSC nomination" in email 
subjects.  In nomination statements, please list the following information:

  *   Which election (TSC vs. Board) the nomination is for
  *   Name of the nominee
  *   Organization
  *   A brief description of nominee's qualifications
As nominations are accepted, I will add them to this 
page.  There 
will be separate Condorcet ballot for these two elections, and they will be 
sent out by September 11th.

Thanks,

Ray





___

opnfv-tsc mailing list

opnfv-...@lists.opnfv.org

https://lists.opnfv.org/mailman/listinfo/opnfv-tsc



--

Morgan Richomme

Orange/ IMT/ OLN/ CNC/ NCA/ SINA



Network architect for innovative services

Future of the Network community member

Open source Orange community manager





tel. +33 (0) 296 072 106

mob. +33 (0) 637 753 326

morgan.richo...@orange.com

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org

Re: [opnfv-tech-discuss] [opnfv-tsc] [announce] Opening nominations for Committers-at-Large TSC & Committer Board elections

[Raymond Paik]

Thanks Julien...

Serena, do you accept the nomination?

Ray

On Fri, Sep 8, 2017 at 6:50 AM, Julien  wrote:

> Hi all,
>
> I would like to nominate Serena (ZTE) for the TSC at-large
> election. She has done a great work in Functest, Releng and QTIP project.
> As an active committer, she is in charge of TestAPI development, which is
> consumed by more and more projects, from the basic data store to cli, web
> portal and CI/CD procedure. She is also an active mentor in community, and
> she has worked with intern in several projects. I believe she has enough
> skills and capability for TSC member.
>
> BR/Julien
>
> Raymond Paik 于2017年9月4日周一 上午1:43写道：
>
>> All,
>>
>> I'm kicking off the nomination process for Committers-at-Large TSC
>> (electing 5 members) plus the Committer Board (electing 1) elections.
>>
>> The list of eligible committers who can run for & vote in both elections
>> are posted here, and I want to encourage all eligible committers to
>> nominate community members who can represent the OPNFV technical community
>> in both the TSC and the Board.  Self nominations are also welcome.   As I
>> mentioned earlier in the week, I hope to see a diverse group of community
>> members represented--in terms of geography, gender, projects,  service
>> providers/vendors, etc.--in the nominations.
>>
>> Nominations should be posted to opnfv-tech-discuss & opnfv-tsc mailing
>> lists by 5pm Pacific Time on September 8th (Friday).  You are welcome to
>> reply to this email or if you're sending out a separate note, please
>> include phrases like "Committer Board nomination" or "Committer-at-Large
>> TSC nomination" in email subjects.  In nomination statements, please list
>> the following information:
>>
>>- Which election (TSC vs. Board) the nomination is for
>>- Name of the nominee
>>- Organization
>>- A brief description of nominee's qualifications
>>
>> As nominations are accepted, I will add them to this page
>> .  There
>> will be separate Condorcet ballot for these two elections, and they will be
>> sent out by September 11th.
>>
>> Thanks,
>>
>> Ray
>>
>> ___
>> opnfv-tsc mailing list
>> opnfv-...@lists.opnfv.org
>> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
>>
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [Infra] Infra Working Group Meeting

[Morgan, Jack]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Morgan, Jack":MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-discuss (opnfv-tech-discuss@lists.opnfv.org):MAILTO:opnfv-tech-discuss@l
 ists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:The "Infra Working Group" plans and tracks infra
 structure cross project initiatives.\nWe report our efforts up to the TSC 
 to ensure the community is able to provide sufficient resources for develo
 pment and release infrastructure.\n\nTopics and meeting agenda at https://
 wiki.opnfv.org/display/INF/Infra+Working+Group\n\nMinutes at Infra Working
  Group Meeting\n•   Weekly on Monday at 8:00 PST or 15:00 UTC (during US 
 daylight saving)\n•   GTM Link https://global.gotomeeting.com/join/8
 19733085\n•   IRC #opnfv-meeting - freenode.net\n•   Chaired by Jack Morgan for Sep/Oct (meetings chaired by Infra
  PTLs on a 2-month basis)\n•   You can also dial in using your phone
  with Access Code: 819-733-085\n•   United States +1 (312) 757-3126\
 n•   Australia +61 2 8355 1040\n•   Austria +43 7 2088 0034\n
 •   Belgium +32 (0) 28 93 7018\n•   Canada +1 (647) 497-9350\n
 •   Denmark +45 69 91 88 64\n•   Finland +358 (0) 923 17 0568\
 n•   France +33 (0) 170 950 592\n•   Germany +49 (0) 692 5736 
 7211\n•   Ireland +353 (0) 15 360 728\n•   Italy +39 0 247 92 
 13 01\n•   Netherlands +31 (0) 208 080 219\n•   New Zealand +6
 4 9 280 6302\n•   Norway +47 75 80 32 07\n•   Spain +34 911 82
  9906\n•   Sweden +46 (0) 853 527 836\n•   Switzerland +41 (0)
  435 0167 13\n•   United Kingdom +44 (0) 330 221 0086\n\n\n
RRULE:FREQ=WEEKLY;UNTIL=20171030T15Z;INTERVAL=1;BYDAY=MO;WKST=SU
SUMMARY;LANGUAGE=en-US:[Infra] Infra Working Group Meeting
DTSTART;TZID=Pacific Standard Time:20170911T08
DTEND;TZID=Pacific Standard Time:20170911T09
UID:04008200E00074C5B7101A82E00870E1F2547328D301000
 01000EEF1D970747D1A4D850E95CE45D80869
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170908T142313Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:GTM 819733085 and IRC #opnfv-meeting
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-2090297375
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:TRUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
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-tsc] [announce] Opening nominations for Committers-at-Large TSC & Committer Board elections

[Julien]

Hi all,

I would like to nominate Yujun (ZTE) for the TSC at-large
election. He has done a great work as QTIP PTL. He has enough knowledge in
open source community. He has worked for several open source projects
before joining in OPNFV. During his leadership QTIP project cooperates with
not only  OPNFV projects but also Openstack projects and great success has
been achieved.

BR/Julien


Raymond Paik 于2017年9月4日周一 上午1:43写道：

> All,
>
> I'm kicking off the nomination process for Committers-at-Large TSC
> (electing 5 members) plus the Committer Board (electing 1) elections.
>
> The list of eligible committers who can run for & vote in both elections
> are posted here, and I want to encourage all eligible committers to
> nominate community members who can represent the OPNFV technical community
> in both the TSC and the Board.  Self nominations are also welcome.   As I
> mentioned earlier in the week, I hope to see a diverse group of community
> members represented--in terms of geography, gender, projects,  service
> providers/vendors, etc.--in the nominations.
>
> Nominations should be posted to opnfv-tech-discuss & opnfv-tsc mailing
> lists by 5pm Pacific Time on September 8th (Friday).  You are welcome to
> reply to this email or if you're sending out a separate note, please
> include phrases like "Committer Board nomination" or "Committer-at-Large
> TSC nomination" in email subjects.  In nomination statements, please list
> the following information:
>
>- Which election (TSC vs. Board) the nomination is for
>- Name of the nominee
>- Organization
>- A brief description of nominee's qualifications
>
> As nominations are accepted, I will add them to this page
> .  There
> will be separate Condorcet ballot for these two elections, and they will be
> sent out by September 11th.
>
> Thanks,
>
> Ray
>
> ___
> opnfv-tsc mailing list
> opnfv-...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
>
___
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-tsc] [announce] Opening nominations for Committers-at-Large TSC & Committer Board elections

[Julien]

Hi all,

I would like to nominate Serena (ZTE) for the TSC at-large
election. She has done a great work in Functest, Releng and QTIP project.
As an active committer, she is in charge of TestAPI development, which is
consumed by more and more projects, from the basic data store to cli, web
portal and CI/CD procedure. She is also an active mentor in community, and
she has worked with intern in several projects. I believe she has enough
skills and capability for TSC member.

BR/Julien

Raymond Paik 于2017年9月4日周一 上午1:43写道：

> All,
>
> I'm kicking off the nomination process for Committers-at-Large TSC
> (electing 5 members) plus the Committer Board (electing 1) elections.
>
> The list of eligible committers who can run for & vote in both elections
> are posted here, and I want to encourage all eligible committers to
> nominate community members who can represent the OPNFV technical community
> in both the TSC and the Board.  Self nominations are also welcome.   As I
> mentioned earlier in the week, I hope to see a diverse group of community
> members represented--in terms of geography, gender, projects,  service
> providers/vendors, etc.--in the nominations.
>
> Nominations should be posted to opnfv-tech-discuss & opnfv-tsc mailing
> lists by 5pm Pacific Time on September 8th (Friday).  You are welcome to
> reply to this email or if you're sending out a separate note, please
> include phrases like "Committer Board nomination" or "Committer-at-Large
> TSC nomination" in email subjects.  In nomination statements, please list
> the following information:
>
>- Which election (TSC vs. Board) the nomination is for
>- Name of the nominee
>- Organization
>- A brief description of nominee's qualifications
>
> As nominations are accepted, I will add them to this page
> .  There
> will be separate Condorcet ballot for these two elections, and they will be
> sent out by September 11th.
>
> Thanks,
>
> Ray
>
> ___
> opnfv-tsc mailing list
> opnfv-...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Weekly Technical Discussion #100

[HU, BIN]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="HU, BIN":MAILTO:bh5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:https://global.gotomeeting.com/join/819733085\n+
 1 (312) 757-3126 / Access Code: 819-733-085\n\nHello community:\n\nThis is
  our 100th weekly technical discussion at 6am PDT / 9am EDT Thursday Septe
 mber 21st\, 2017\, which is 13:00 UTC. Yeah\, I cannot believe it will be 
 the 100th discussion since our community was founded almost 3 years ago. C
 ongratulations to everyone in the community!\n\nWe will continue to discus
 s the CD-Friendly Release Model based on XCI driven by Fatih Degirmenci.\n\nYou can find your local time here htt
 p://www.timeanddate.com/worldclock/fixedtime.html?msg=OPNFV-Technical-Disc
 ussion=20170921T13=1.\n\nPlease refer to https://wiki.opnfv.org/dis
 play/PROJ/Weekly+Technical+Discussion for details of dialing logistics and
  tentative agenda.\n\nPlease let me know if you want to add anything to ag
 enda for discussion in the community.\n\nFor your convenience:\n-   Go
 To Meeting: https://global.gotomeeting.com/join/819733085\n-   You can
  also dial in using your phone:\no   United States (Long distance): +1
  (312) 757-3126 / Access Code: 819-733-085\no   More phone numbers: ht
 tps://global.gotomeeting.com/819733085/numbersdisplay.html\n\nThanks\nBin\
 n\n\n
SUMMARY;LANGUAGE=en-US:Weekly Technical Discussion #100
DTSTART;TZID=Pacific Standard Time:20170921T06
DTEND;TZID=Pacific Standard Time:20170921T07
UID:04008200E00074C5B7101A82E0087005322F6D28D301000
 01000C99D45EFBD835A4B8773DE3A2C60D3B7
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170908T134008Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US: +1 (312) 757-3126 / Access Code: 819-733-085
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2114492385
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Summary of Weekly Technical Community Discussion Thursday September 07

[HU, BIN]

Hello community,



Thank you all for attending the technical discussion yesterday.



Fatih introduced Release Process 
Proposal and 
Onboarding Projects/Scenarios to 
XCI. The slides 
deck v1 is 
here.



Team had a great discussion on many details of execution, including CD release 
model, versioning/tagging, way of working etc. For more details, please refer 
to meeting minutes page [1], which includes attendees list and IRC log [2].



After discussion, Fatih kindly revised the slides deck, and the updated slides 
deck v2 is available 
here.
 Fatih will give an update of discussion to TSC on 9/19, and we will continue 
to discuss this CD-friendly XCI-based release model on 9/21.



Because many folks will attend OpenStack PTG in Denver next week, I suggest 
that we cancel our weekly discussion next week (9/14), and resume on 9/21 to 
continue the discussion of the new slides 
deck.



Thanks

Bin



[1] https://wiki.opnfv.org/display/PROJ/Tc+Minutes+20170907

[2] 
http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-09-07-13.00.html



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

Re: [opnfv-tech-discuss] [Pharos] Pharos lab for ARM band

[Srikanth Lingala]

OK...So, If I apply some patches to Fuel and rebuild Fuel ISO, can I deploy 
with mixed (x86 and aarch64) targets in Pharos POD?
If so, can you please point me to those patches?

Regards,
Srikanth.

From: Alexandru Avadanii [mailto:alexandru.avada...@enea.com]
Sent: Friday, September 08, 2017 5:54 PM
To: Srikanth Lingala ; opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Cc: svc-armband ; Bob Monkman ; Shai 
Tsur ; Gorja Gorja ; Trinath Somanchi 
; Veera.reddy B 
Subject: RE: [Pharos] Pharos lab for ARM band

Hi,
That is correct, everything is now AArch64 in our PODs.

BR,
Alex


From: Srikanth Lingala [mailto:srikanth.ling...@nxp.com]
Sent: Friday, September 08, 2017 11:48 AM
To: Alexandru Avadanii; 
opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Cc: svc-armband; Bob Monkman; Shai Tsur; Gorja Gorja; Trinath Somanchi; 
Veera.reddy B
Subject: RE: [Pharos] Pharos lab for ARM band

Hi Alex,
Thanks for the details.
I viewed the following link for reference:
https://wiki.opnfv.org/display/pharos/Enea+Hosting

So, in the current ENEA Pharos lab, you are using ARM based machines as OS 
Controller nodes, Compute nodes and even Jump Host node. Not using any hybrid 
POD (with combination of x86 and ARM machines as nodes). Right?

Regards,
Srikanth.

From: Alexandru Avadanii [mailto:alexandru.avada...@enea.com]
Sent: Friday, September 08, 2017 12:49 AM
To: Srikanth Lingala 
>; 
opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Cc: svc-armband >; Bob 
Monkman >; Shai Tsur 
>
Subject: RE: [Pharos] Pharos lab for ARM band

Hi, Srikanth,
I'm glad to hear about new AArch64 hardware joining OPNFV.

First, note that Pharos specs require 5 nodes, which depending on the scenario 
can be used as 3 controllers + 2 computes, or 1 controller + computes.
This makes it hard to mix x86 and ARM targets in a Pharos POD. Therefore, this 
is not supported by OPNFV Danube 3.0 Fuel - it is not impossible, but it is out 
of our current scope.
To add some complexity to that, we have the additional jump server host, which 
used to be x86 up to and including the Danube release cycle; starting with the 
E release, Armband only support all-AArch64 PODs, including the jump host.

Also note that the old Fuel (used up to and including Danube) was replaced by 
the new Fuel, based on Mirantis Cloud Platform (MCP), which on its own means a 
lot of changes in the way we build and provision the OS images (bootstrap and 
final image) on the AArch64 nodes.
Starting with the E release, there is no more bootstrap building, all images 
(Ubuntu Xenial) are fetched from official Ubuntu Cloud Archive (UCA) repos and 
used as-is.

As for old bootstrap building, x86 instructions still apply [1], with only one 
extra arg required (--target_arch=arm64).

To summarize, I recommend looking into the current Armband/Fuel codebase 
(master branch) and prepare for using MCP-based Fuel instead of the old Danube 
codebase.
To add a lab in OPNFV, you will need 6 x AArch64 nodes (5 for the cluster and 
one for the jump host).

BR,
Alex

[1] 
https://docs.openstack.org/fuel-docs/latest/userdocs/fuel-install-guide/bootstrap/bootstrap_troubleshoot.html


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Srikanth 
Lingala
Sent: Thursday, September 07, 2017 8:35 PM
To: opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [Pharos] Pharos lab for ARM band

Hi,
We want to setup Pharos lab for ARM band machines. For that, I am using OPNFV 
Danube 3.0 release (Fuel 

Re: [opnfv-tech-discuss] [Pharos] Pharos lab for ARM band

[Alexandru Avadanii]

Hi,
That is correct, everything is now AArch64 in our PODs.

BR,
Alex


From: Srikanth Lingala [mailto:srikanth.ling...@nxp.com]
Sent: Friday, September 08, 2017 11:48 AM
To: Alexandru Avadanii; opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Cc: svc-armband; Bob Monkman; Shai Tsur; Gorja Gorja; Trinath Somanchi; 
Veera.reddy B
Subject: RE: [Pharos] Pharos lab for ARM band

Hi Alex,
Thanks for the details.
I viewed the following link for reference:
https://wiki.opnfv.org/display/pharos/Enea+Hosting

So, in the current ENEA Pharos lab, you are using ARM based machines as OS 
Controller nodes, Compute nodes and even Jump Host node. Not using any hybrid 
POD (with combination of x86 and ARM machines as nodes). Right?

Regards,
Srikanth.

From: Alexandru Avadanii [mailto:alexandru.avada...@enea.com]
Sent: Friday, September 08, 2017 12:49 AM
To: Srikanth Lingala 
>; 
opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Cc: svc-armband >; Bob 
Monkman >; Shai Tsur 
>
Subject: RE: [Pharos] Pharos lab for ARM band

Hi, Srikanth,
I'm glad to hear about new AArch64 hardware joining OPNFV.

First, note that Pharos specs require 5 nodes, which depending on the scenario 
can be used as 3 controllers + 2 computes, or 1 controller + computes.
This makes it hard to mix x86 and ARM targets in a Pharos POD. Therefore, this 
is not supported by OPNFV Danube 3.0 Fuel - it is not impossible, but it is out 
of our current scope.
To add some complexity to that, we have the additional jump server host, which 
used to be x86 up to and including the Danube release cycle; starting with the 
E release, Armband only support all-AArch64 PODs, including the jump host.

Also note that the old Fuel (used up to and including Danube) was replaced by 
the new Fuel, based on Mirantis Cloud Platform (MCP), which on its own means a 
lot of changes in the way we build and provision the OS images (bootstrap and 
final image) on the AArch64 nodes.
Starting with the E release, there is no more bootstrap building, all images 
(Ubuntu Xenial) are fetched from official Ubuntu Cloud Archive (UCA) repos and 
used as-is.

As for old bootstrap building, x86 instructions still apply [1], with only one 
extra arg required (--target_arch=arm64).

To summarize, I recommend looking into the current Armband/Fuel codebase 
(master branch) and prepare for using MCP-based Fuel instead of the old Danube 
codebase.
To add a lab in OPNFV, you will need 6 x AArch64 nodes (5 for the cluster and 
one for the jump host).

BR,
Alex

[1] 
https://docs.openstack.org/fuel-docs/latest/userdocs/fuel-install-guide/bootstrap/bootstrap_troubleshoot.html


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Srikanth 
Lingala
Sent: Thursday, September 07, 2017 8:35 PM
To: opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [Pharos] Pharos lab for ARM band

Hi,
We want to setup Pharos lab for ARM band machines. For that, I am using OPNFV 
Danube 3.0 release (Fuel ISO).
Is it possible to deploy an OpenStack setup with x86 machine as OS Controller 
and ARM machine as OS Compute node?
And also, can anyone give me some reference links to build a bootstrap image 
(for Fuel deployment) for baremetal ARM machines?

Regards,
Srikanth.
___
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-tsc] [announce] Opening nominations for Committers-at-Large TSC & Committer Board elections

[Rossella Sblendido]

Hi all,

I'd like to nominate Jose Lausuch for the Committers-at-Large TSC board.
Jose has done a great job as Functest PTL for Danube and Euphrates. He
got a developer award in Beijing and has server as a mentor for the
internship program. He's a very active and respected member of the
community, he could be a great addition to the TSC.

Rossella

On 09/03/2017 07:42 PM, Raymond Paik wrote:
> All, 
> 
> I'm kicking off the nomination process for Committers-at-Large TSC
> (electing 5 members) plus the Committer Board (electing 1) elections.  
> 
> The list of eligible committers who can run for & vote in both elections
> are posted here , and I want
> to encourage all eligible committers to nominate community members who
> can represent the OPNFV technical community in both the TSC and the
> Board.  Self nominations are also welcome.   As I mentioned earlier in
> the week, I hope to see a diverse group of community members
> represented--in terms of geography, gender, projects,  service
> providers/vendors, etc.--in the nominations.  
> 
> Nominations should be posted to opnfv-tech-discuss & opnfv-tsc mailing
> lists by 5pm Pacific Time on September 8th (Friday).  You are welcome to
> reply to this email or if you're sending out a separate note, please
> include phrases like "Committer Board nomination" or "Committer-at-Large
> TSC nomination" in email subjects.  In nomination statements, please
> list the following information:   
> 
>   * Which election (TSC vs. Board) the nomination is for
>   * Name of the nominee
>   * Organization
>   * A brief description of nominee's qualifications
> 
> As nominations are accepted, I will add them to this page
> .  There
> will be separate Condorcet ballot for these two elections, and they will
> be sent out by September 11th.  
> 
> Thanks, 
> 
> Ray
> 
> 
> 
> ___
> opnfv-tsc mailing list
> opnfv-...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
> 
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Pharos] Pharos lab for ARM band

[Srikanth Lingala]

Hi Alex,
Thanks for the details.
I viewed the following link for reference:
https://wiki.opnfv.org/display/pharos/Enea+Hosting

So, in the current ENEA Pharos lab, you are using ARM based machines as OS 
Controller nodes, Compute nodes and even Jump Host node. Not using any hybrid 
POD (with combination of x86 and ARM machines as nodes). Right?

Regards,
Srikanth.

From: Alexandru Avadanii [mailto:alexandru.avada...@enea.com]
Sent: Friday, September 08, 2017 12:49 AM
To: Srikanth Lingala ; opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Cc: svc-armband ; Bob Monkman ; Shai 
Tsur 
Subject: RE: [Pharos] Pharos lab for ARM band

Hi, Srikanth,
I'm glad to hear about new AArch64 hardware joining OPNFV.

First, note that Pharos specs require 5 nodes, which depending on the scenario 
can be used as 3 controllers + 2 computes, or 1 controller + computes.
This makes it hard to mix x86 and ARM targets in a Pharos POD. Therefore, this 
is not supported by OPNFV Danube 3.0 Fuel - it is not impossible, but it is out 
of our current scope.
To add some complexity to that, we have the additional jump server host, which 
used to be x86 up to and including the Danube release cycle; starting with the 
E release, Armband only support all-AArch64 PODs, including the jump host.

Also note that the old Fuel (used up to and including Danube) was replaced by 
the new Fuel, based on Mirantis Cloud Platform (MCP), which on its own means a 
lot of changes in the way we build and provision the OS images (bootstrap and 
final image) on the AArch64 nodes.
Starting with the E release, there is no more bootstrap building, all images 
(Ubuntu Xenial) are fetched from official Ubuntu Cloud Archive (UCA) repos and 
used as-is.

As for old bootstrap building, x86 instructions still apply [1], with only one 
extra arg required (--target_arch=arm64).

To summarize, I recommend looking into the current Armband/Fuel codebase 
(master branch) and prepare for using MCP-based Fuel instead of the old Danube 
codebase.
To add a lab in OPNFV, you will need 6 x AArch64 nodes (5 for the cluster and 
one for the jump host).

BR,
Alex

[1] 
https://docs.openstack.org/fuel-docs/latest/userdocs/fuel-install-guide/bootstrap/bootstrap_troubleshoot.html


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Srikanth 
Lingala
Sent: Thursday, September 07, 2017 8:35 PM
To: opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [Pharos] Pharos lab for ARM band

Hi,
We want to setup Pharos lab for ARM band machines. For that, I am using OPNFV 
Danube 3.0 release (Fuel ISO).
Is it possible to deploy an OpenStack setup with x86 machine as OS Controller 
and ARM machine as OS Compute node?
And also, can anyone give me some reference links to build a bootstrap image 
(for Fuel deployment) for baremetal ARM machines?

Regards,
Srikanth.
___
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-tsc] [announce] Opening nominations for Committers-at-Large TSC & Committer Board elections

[morgan.richomme]

Hi,

thanks Wenjing!

I unfortunately cannot accept the nominations.
There are currently some internal reorganization on my side (as in LF 
networking projects...) preventing me to be fully involved in OPNFV 
after Euphrates, which is a prerequisite to apply for these positions.


/Morgan


On 07/09/2017 23:53, Raymond Paik wrote:

Wenjing, thanks for getting things started on the board as well.

Hongbo & Morgan, do you accept your nominations (for Morgan there are 
actually 2 nominations for TSC & Board)?


Cheers,

Ray

On Thu, Sep 7, 2017 at 11:48 AM, Wenjing Chu > wrote:


It’s great to see all the high caliber candidates for
 Committers-at-Large TSC members – a good sign for a vibrate
community.

In that spirit, I like to start with the committer board
nomination as well.

I like to nominate Hongbo Tian (Huawei) for committer board
member. Hongbo has been the long time PTL of dovetail dedicating a
lot of hard work to help bring Dovetail to near its first launch.
He’s also a big contributor to and an organizer of each of the
Plugfests. The board can benefit from more voices from the trenches.

I’d also like to nominate Morgan Richomme (Orange) for another
term of committer Board member and committer-at-large TSC member.
Not only that Morgan is uniquely qualified based on his leadership
in Functest (the first and only project graduated from incubation
so far) and test working group, and Pharos, but also that his
collaborative and constructive style brings huge value to a
project – and similarly to the TSC and board. So I hope Morgan can
step forward for both again.

Regards

Wenjing


On 03/09/2017 19:42, Raymond Paik wrote:

All,

I'm kicking off the nomination process for Committers-at-Large
TSC (electing 5 members) plus the Committer Board (electing 1)
elections.

The list of eligible committers who can run for & vote in both
elections are posted here
, and I want
to encourage all eligible committers to nominate community
members who can represent the OPNFV technical community in
both the TSC and the Board.  Self nominations are also
welcome.   As I mentioned earlier in the week, I hope to see a
diverse group of community members represented--in terms of
geography, gender, projects,  service providers/vendors,
etc.--in the nominations.

Nominations should be posted to opnfv-tech-discuss & opnfv-tsc
mailing lists by 5pm Pacific Time on September 8th (Friday). 
You are welcome to reply to this email or if you're sending

out a separate note, please include phrases like "Committer
Board nomination" or "Committer-at-Large TSC nomination" in
email subjects.  In nomination statements, please list the
following information:

  * Which election (TSC vs. Board) the nomination is for
  * Name of the nominee
  * Organization
  * A brief description of nominee's qualifications

As nominations are accepted, I will add them to this page
. 
There will be separate Condorcet ballot for these two

elections, and they will be sent out by September 11th.

Thanks,

Ray




___

opnfv-tsc mailing list

opnfv-...@lists.opnfv.org 

https://lists.opnfv.org/mailman/listinfo/opnfv-tsc


-- 


Morgan Richomme

Orange/ IMT/ OLN/ CNC/ NCA/ SINA

  


Network architect for innovative services

Future of the Network community member

Open source Orange community manager

  

  


tel. +33 (0) 296 072 106

mob. +33 (0) 637 753 326

morgan.richo...@orange.com 


_

  


Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

  


This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this 

[opnfv-tech-discuss] Illustration for landing pages

[morgan.richomme]

Hi Brandon

do you think LF design team could create 2 illustrations for 2 landing 
pages where we have OPNFV resources
- one for the testing landing page (submenu: reporting, dashboarding, 
testAPI, test DB,..)

- one for the VNF kanding page (submenu: catalog)

note that we already integrated the icons provided for the project 
http://testresults.opnfv.org/testing/#!/select/visual

but a landing page for the root addresses will be more user friendly
http://testresults.opnfv.org
http://vnf.opnfv.org (DNS config in progress)

and additionnaly if we may have "fun" default error page (404 / 500) it 
will be cool...


at the moment
http://testresults.opnfv.org/ => welcome to Nginx (default)
http://testresults.opnfv.org/sdfdsf => default nginx error page

/Morgan


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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