Re: [opnfv-tech-discuss] My Status

[Julien]

Good news, Jack.

I wish you will achieve great progress in your new job and OPNFV.

BR/Julien

Jack Morgan  于2019年10月11日周五 上午7:32写道：

> OPNFV,
>
> As some of you might have heard, I have left Intel recently. I have
> decided to move on to other opportunities and in the process of
> investigating them now. Please use this email to contact me or connect
> via LinkedIn, https://www.linkedin.com/in/jentoio/
>
> I've served on the OPNFV TSC this year as a replacement for Emma Foley
> but my TSC term ended last month. I've also returned as the PTL for
> Pharos and plan to continue to support this project. Now, that I have a
> little more free time, I hope to plug into OPNFV more moving forward.
>
>
> Kinds Regards,
>
> --
> Jack Morgan
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#23644):
> https://lists.opnfv.org/g/opnfv-tech-discuss/message/23644
> Mute This Topic: https://lists.opnfv.org/mt/34481131/557159
> Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
> Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  [
> julien...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23645): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23645
Mute This Topic: https://lists.opnfv.org/mt/34481131/21656
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] [opnfv-tsc] [infra-wg][pharos] Welcome Jack to be the next Pharos PTL.

[Julien]

There are 10 active committers in Pharos and 8 of them have cast their vote
in Gerrit. There are 8 "+1" in Gerrit [1]. It has met the rule of "simple
majority".

Now Jack Morgan(jack.mor...@intel.com) has become the next Pharos PTL.
Congratulations.

[1] https://gerrit.opnfv.org/gerrit/#/c/67269/

BR/Julien

Julien via Lists.Opnfv.Org 于2019年3月17日周日
上午12:43写道：

> Hi, Pharos committers,
>
> I have submitted the patch for the new PTL. Please cast your vote in
> review [1]  in a week.
>
> [1]. https://gerrit.opnfv.org/gerrit/#/c/67269/
>
> BR,
> Julien
>
> Julien via Lists.Opnfv.Org 于2019年3月14日周四
> 下午11:45写道：
>
>> Thanks for all,
>>
>
>> I have received Jack's nomination from Parker, and Jack accepted the
>> nomination.
>>
>> I will initiate a vote on the Gerrit. But I can not access community
>> Gerrit either https://gerrit.opnfv.org or ssh for now.
>> I don't know there is anything wrong.
>>
>> BR,
>> Julien
>>
> Jack Morgan 于2019年2月27日周三 下午11:43写道：
>>
>>> Thanks, Julien for all your work this past year. Thanks to Parker for
>>> the nomination. I accept.
>>>
>>
>>> On 2/27/19 7:22 AM, Parker Berberian wrote:
>>>
>>> Hi,
>>>
>>> Thank you Julien for your kind words and your work as PTL.
>>>
>>> I nominate Jack as new PTL.
>>>
>>> -Parker
>>>
>>> On Wed, Feb 27, 2019 at 9:35 AM Julien  wrote:
>>>
>>>> Hi Pharos team,
>>>>
>>>> I'd like to step down Pharos PTL.
>>>>
>>>> I have worked for Pharos for several releases and served as the Pharos
>>>> PTL in last year. My internal duty had some changes in the middle of last
>>>> year, and I don't have enough time to still work as Pharos PTL. I don't
>>>> have enough contributions recently either.
>>>>
>>>> Thanks to Parker, Trevor, Alex and Jack. LaaS can be released and
>>>> served the community with your contribution. I'm regrated that I don't have
>>>> any contributions to LaaS. Infra is very important in both community and my
>>>> company. I would like to involve some activities in Pharos and give my
>>>> contributions as possible.
>>>>
>>>> I hope the Pharos team will make more achievements in the future.
>>>>
>>>> With this email, I also call for nomination for the new PTL. If any
>>>> committer would like to take the role, please announce your nomination by
>>>> replying to this email.
>>>>
>>>> The new PTL nomination will be open for 2 weeks until 13 March. Then I
>>>> will initiate a vote in the gerrit system.
>>>>
>>>> Best Regards,
>>>> Julien
>>>> -=-=-=-=-=-=-=-=-=-=-=-
>>>> Links: You receive all messages sent to this group.
>>>>
>>>> View/Reply Online (#5063):
>>>> https://lists.opnfv.org/g/opnfv-tsc/message/5063
>>>> Mute This Topic: https://lists.opnfv.org/mt/30152547/1217375
>>>> Group Owner: opnfv-tsc+ow...@lists.opnfv.org
>>>> Unsubscribe: https://lists.opnfv.org/g/opnfv-tsc/unsub  [
>>>> pberber...@iol.unh.edu]
>>>> -=-=-=-=-=-=-=-=-=-=-=-
>>>>
>>>
>>>
>>> --
>>>
>>> Parker Berberian
>>>
>>> UNH InterOperability Laboratory
>>>
>>> 21 Madbury Rd, Suite 100, Durham, NH 03824
>>> <https://maps.google.com/?q=21+Madbury+Rd,+Suite+100,+Durham,+NH+03824=gmail=g>
>>>
>>> pberber...@iol.unh.edu
>>>
>>> www.iol.unh.edu
>>>
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>> Links: You receive all messages sent to this group.
>>>
>>> View/Reply Online (#5064): https://lists.opnfv.org/g/opnfv-tsc/message/5064
>>> Mute This Topic: https://lists.opnfv.org/mt/30152547/1198612
>>> Group Owner: opnfv-tsc+ow...@lists.opnfv.org
>>> Unsubscribe: https://lists.opnfv.org/g/opnfv-tsc/unsub  [j...@jento.io]
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>>
>>>
>>> --
>>> Jack Morgan
>>>
>>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>>
>> View/Reply Online (#22919):
>> https://lists.opnfv.org/g/opnfv-tech-discuss/message/22919
>> Mute This Topic: https://lists.opnfv.org/mt/30153051/557159
>> Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
>> Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  [
>> julien...@gmail.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#22932):
> https://lists.opnfv.org/g/opnfv-tech-discuss/message/22932
> Mute This Topic: https://lists.opnfv.org/mt/30153051/557159
> Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
> Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  [
> julien...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22949): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22949
Mute This Topic: https://lists.opnfv.org/mt/30522029/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] [opnfv-tsc] [infra-wg][pharos] step down as Pharos PTL

[Julien]

Hi, Pharos committers,

I have submitted the patch for the new PTL. Please cast your vote in review
[1]  in a week.

[1]. https://gerrit.opnfv.org/gerrit/#/c/67269/

BR,
Julien

Julien via Lists.Opnfv.Org 于2019年3月14日周四
下午11:45写道：

> Thanks for all,
>
> I have received Jack's nomination from Parker, and Jack accepted the
> nomination.
>
> I will initiate a vote on the Gerrit. But I can not access community
> Gerrit either https://gerrit.opnfv.org or ssh for now.
> I don't know there is anything wrong.
>
> BR,
> Julien
> Jack Morgan 于2019年2月27日周三 下午11:43写道：
>
>> Thanks, Julien for all your work this past year. Thanks to Parker for the
>> nomination. I accept.
>>
>
>> On 2/27/19 7:22 AM, Parker Berberian wrote:
>>
>> Hi,
>>
>> Thank you Julien for your kind words and your work as PTL.
>>
>> I nominate Jack as new PTL.
>>
>> -Parker
>>
>> On Wed, Feb 27, 2019 at 9:35 AM Julien  wrote:
>>
>>> Hi Pharos team,
>>>
>>> I'd like to step down Pharos PTL.
>>>
>>> I have worked for Pharos for several releases and served as the Pharos
>>> PTL in last year. My internal duty had some changes in the middle of last
>>> year, and I don't have enough time to still work as Pharos PTL. I don't
>>> have enough contributions recently either.
>>>
>>> Thanks to Parker, Trevor, Alex and Jack. LaaS can be released and served
>>> the community with your contribution. I'm regrated that I don't have any
>>> contributions to LaaS. Infra is very important in both community and my
>>> company. I would like to involve some activities in Pharos and give my
>>> contributions as possible.
>>>
>>> I hope the Pharos team will make more achievements in the future.
>>>
>>> With this email, I also call for nomination for the new PTL. If any
>>> committer would like to take the role, please announce your nomination by
>>> replying to this email.
>>>
>>> The new PTL nomination will be open for 2 weeks until 13 March. Then I
>>> will initiate a vote in the gerrit system.
>>>
>>> Best Regards,
>>> Julien
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>> Links: You receive all messages sent to this group.
>>>
>>> View/Reply Online (#5063):
>>> https://lists.opnfv.org/g/opnfv-tsc/message/5063
>>> Mute This Topic: https://lists.opnfv.org/mt/30152547/1217375
>>> Group Owner: opnfv-tsc+ow...@lists.opnfv.org
>>> Unsubscribe: https://lists.opnfv.org/g/opnfv-tsc/unsub  [
>>> pberber...@iol.unh.edu]
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>>
>>
>>
>> --
>>
>> Parker Berberian
>>
>> UNH InterOperability Laboratory
>>
>> 21 Madbury Rd, Suite 100, Durham, NH 03824
>> <https://maps.google.com/?q=21+Madbury+Rd,+Suite+100,+Durham,+NH+03824=gmail=g>
>>
>> pberber...@iol.unh.edu
>>
>> www.iol.unh.edu
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>>
>> View/Reply Online (#5064): https://lists.opnfv.org/g/opnfv-tsc/message/5064
>> Mute This Topic: https://lists.opnfv.org/mt/30152547/1198612
>> Group Owner: opnfv-tsc+ow...@lists.opnfv.org
>> Unsubscribe: https://lists.opnfv.org/g/opnfv-tsc/unsub  [j...@jento.io]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
>>
>> --
>> Jack Morgan
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#22919):
> https://lists.opnfv.org/g/opnfv-tech-discuss/message/22919
> Mute This Topic: https://lists.opnfv.org/mt/30153051/557159
> Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
> Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  [
> julien...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22932): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22932
Mute This Topic: https://lists.opnfv.org/mt/30153051/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] [opnfv-tsc] [infra-wg][pharos] step down as Pharos PTL

[Julien]

Thanks for all,

I have received Jack's nomination from Parker, and Jack accepted the
nomination.

I will initiate a vote on the Gerrit. But I can not access community Gerrit
either https://gerrit.opnfv.org or ssh for now.
I don't know there is anything wrong.

BR,
Julien


Jack Morgan 于2019年2月27日周三 下午11:43写道：

> Thanks, Julien for all your work this past year. Thanks to Parker for the
> nomination. I accept.
>
> On 2/27/19 7:22 AM, Parker Berberian wrote:
>
> Hi,
>
> Thank you Julien for your kind words and your work as PTL.
>
> I nominate Jack as new PTL.
>
> -Parker
>
> On Wed, Feb 27, 2019 at 9:35 AM Julien  wrote:
>
>> Hi Pharos team,
>>
>> I'd like to step down Pharos PTL.
>>
>> I have worked for Pharos for several releases and served as the Pharos
>> PTL in last year. My internal duty had some changes in the middle of last
>> year, and I don't have enough time to still work as Pharos PTL. I don't
>> have enough contributions recently either.
>>
>> Thanks to Parker, Trevor, Alex and Jack. LaaS can be released and served
>> the community with your contribution. I'm regrated that I don't have any
>> contributions to LaaS. Infra is very important in both community and my
>> company. I would like to involve some activities in Pharos and give my
>> contributions as possible.
>>
>> I hope the Pharos team will make more achievements in the future.
>>
>> With this email, I also call for nomination for the new PTL. If any
>> committer would like to take the role, please announce your nomination by
>> replying to this email.
>>
>> The new PTL nomination will be open for 2 weeks until 13 March. Then I
>> will initiate a vote in the gerrit system.
>>
>> Best Regards,
>> Julien
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>>
>> View/Reply Online (#5063):
>> https://lists.opnfv.org/g/opnfv-tsc/message/5063
>> Mute This Topic: https://lists.opnfv.org/mt/30152547/1217375
>> Group Owner: opnfv-tsc+ow...@lists.opnfv.org
>> Unsubscribe: https://lists.opnfv.org/g/opnfv-tsc/unsub  [
>> pberber...@iol.unh.edu]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
>
>
> --
>
> Parker Berberian
>
> UNH InterOperability Laboratory
>
> 21 Madbury Rd, Suite 100, Durham, NH 03824
> <https://maps.google.com/?q=21+Madbury+Rd,+Suite+100,+Durham,+NH+03824=gmail=g>
>
> pberber...@iol.unh.edu
>
> www.iol.unh.edu
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#5064): https://lists.opnfv.org/g/opnfv-tsc/message/5064
> Mute This Topic: https://lists.opnfv.org/mt/30152547/1198612
> Group Owner: opnfv-tsc+ow...@lists.opnfv.org
> Unsubscribe: https://lists.opnfv.org/g/opnfv-tsc/unsub  [j...@jento.io]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
> --
> Jack Morgan
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22919): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22919
Mute This Topic: https://lists.opnfv.org/mt/30153051/21656
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] [infra-wg][pharos] step down as Pharos PTL

[Julien]

Hi Pharos team,

I'd like to step down Pharos PTL.

I have worked for Pharos for several releases and served as the Pharos PTL
in last year. My internal duty had some changes in the middle of last year,
and I don't have enough time to still work as Pharos PTL. I don't have
enough contributions recently either.

Thanks to Parker, Trevor, Alex and Jack. LaaS can be released and served
the community with your contribution. I'm regrated that I don't have any
contributions to LaaS. Infra is very important in both community and my
company. I would like to involve some activities in Pharos and give my
contributions as possible.

I hope the Pharos team will make more achievements in the future.

With this email, I also call for nomination for the new PTL. If any
committer would like to take the role, please announce your nomination by
replying to this email.

The new PTL nomination will be open for 2 weeks until 13 March. Then I will
initiate a vote in the gerrit system.

Best Regards,
Julien
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22867): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22867
Mute This Topic: https://lists.opnfv.org/mt/30152546/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] [opnfv-tsc] [announce][election] Opening nominations for OPNFV Technical Steering Committee (TSC)

[Julien]

Hi David,


I would like to nominate myself to OPNFV TSC.



   - Name of the nominee: Julien Zhang
   - The nominee’s organization: ZTE
   - Nomination statement:

I'm the chief architect of Cloud and NFV technology in ZTE. I'm focusing on
infrastructure projects in OPNFV, such as Pharos and Cloud Edge. I'm
working on turning NFV cloud-native in the community. I have served OPNFV
TSC from 2015 and I'm familiar with any requirement of the TSC.


BR

Julien


David McBride 于2018年8月25日周六 上午1:48写道：

> Team,
>
> Today, we begin nominations for a new TSC, consisting of 15 members, in
> accordance with the Community Election Procedures
> <https://wiki.opnfv.org/display/DEV/Community+Election+Procedure>.
> Individuals who are eligible to both vote and run for a TSC position are
> those with 20 or more contributions on this list of active contributors
> <https://wiki.opnfv.org/display/DEV/2018+Consolidated+Contributions>.
> Before nominating someone, please consult the list and verify that the
> individual has 20 or more contributions.  You may find a schedule of
> election activities here
> <https://wiki.opnfv.org/display/DEV/2018+TSC+and+TSC+Chair+Election+Schedule+of+Activities>
> .
>
> *PTL Input to the Active Contributor List*
> Note that the election procedures have a provision for adding and
> individual to the active contributor list, who has less than 20
> contributions, yet who has make significant contributions to the OPNFV
> community.  Per the election procedure:
>
>
>
> *PTLs have an input on the "active contributor list" compiled over a
> 2-week review period (with a view that this step primarily targets at
> making sure qualified people that haven't been identified via the metric
> get added to the list)*
>
> I am working with the TSC to define a specific process for this
> situation.  In the mean time, if you are a PTL, and you would like to add
> someone to the active contributor list, please contact me directly with the
> name and a brief statement about why they should be included on the list.
> Note that this action simply adds them to the active contributor list, they
> still must be nominated, separately.  Also, note that the 2-week review
> period for the active contributor list, cited in the election procedure,
> ends on Aug 31.
>
> *Nomination procedure*
>
>1. You may nominate yourself, or someone else.
>   - Remember that *both you and the person nominated* must be on the 
> active
>   contributor list
>   <https://wiki.opnfv.org/display/DEV/2018+Consolidated+Contributions> 
> with
>   20 or more contributions.
>   - If you nominate someone else, I will confirm with that person
>   that they accept the nomination.
>2. Announce the nomination with a "reply all" to this email prior to 5
>p.m. (PT), Sept 7.
>3. Please include the following information:
>   - Name of the nominee
>   - The nominee's organization
>   - A brief statement about the nominees qualifications and
>   contributions to the OPNFV community.
>4. Nominations close at 5 p.m. (PT) on Sept 7.  See the entire
>election schedule here
>
> <https://wiki.opnfv.org/display/DEV/2018+TSC+and+TSC+Chair+Election+Schedule+of+Activities>
>.
>
> As nominees are accepted, I will post the nominee information on this page
> <https://wiki.opnfv.org/display/DEV/2018+Election+Nominees>.
>
> 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 (#21979): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/21979
Mute This Topic: https://lists.opnfv.org/mt/25267175/21656
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] [infra][pharos] Have all installers supported PDF 1.0 yet?

[Julien]

Hi, installer PTLs:

According to the TSC meeting on March 20th, 2018, TSC has approved the 3
stages for PDF 1.0. State2 is relevant with installers. Has your project
finished the PDF 1.0 integration? If it has been finished, has your project
provided the relevant IDF yet? It is the base of Phase3. I would like to
check the status of each community lab. For now, I don't find new PDF files
in Pharos repo.

FYR:
*Stage2: June 15th*
*- Any installer team fails to do this should need to come to TSC and ask
for exception request or should be subject to consequences.*

*Stage3: August 15th*
*- Final date for all community labs to adapt PDF/IDF and LaaS to use
PDF/IDF*

BR,
Julien

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

View/Reply Online (#21808): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/21808
Mute This Topic: https://lists.opnfv.org/mt/24819483/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] 答复: [announce] moving on....

[Julien]

Ray,

Thank you very much to welcome us to join the community. I'm very
appreciated what you have done to help us.
Wish you best.

BR,
Julien





Chigang (Justin) 于2018年6月21日周四 下午7:28写道：

> Ray,
>
>
>
> It is my honor to work with you in OPNFV, I was impressed by your
> professionalism and seriousness and hope you get well in new path.
>
>
>
> Regards
>
> Justin
>
>
>
> *发件人**:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *代表 *Manuel Buil
> *发送时间:* 2018年6月21日 16:19
> *收件人:* Raymond Paik ; opnfv-tech-discuss <
> opnfv-tech-discuss@lists.opnfv.org>
> *主题:* Re: [opnfv-tech-discuss] [announce] moving on
>
>
>
> ooh :(
>
>
>
> It was great working with you and you should be proud of the work you did
> in OPNFV! I really hope you are not going too far ;)
>
>
>
> All the best!
>
> Manuel
>
>
>
> On Sun, 2018-06-17 at 12:31 -0700, Raymond Paik wrote:
>
> All,
>
>
>
> I shared this news with some of the community members over the past
> several days, and I wanted to notify the rest of the community.
>
>
>
> I recently made a difficult decision to pursue a new opportunity outside
> of the LF.  Having been involved in OPNFV since the formation days, the
> thought of leaving the community isn't easy.  This is especially the case
> since I just spent the entire week with many community members at ETSI
> during the Plugfest.  I was again reminded that I'm part of a wonderful &
> motivated community.
>
>
>
> My last day at the Linux Foundation is on June 22nd, and I'm working with
> both Phil & Heather on transition plans so that things don't get dropped.
>
>
>
> I sincerely hope that our paths will cross again.  I'm still going to be
> involved in open source software, so I'm definitely not going too far.
> Wherever and whenever our paths cross, I hope we can share a drink soon
>
>
>
> Regards,
>
>
>
> Ray
>
> ___
>
> 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 mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources collection

[Julien]

Hi,

For we don't have enough resources for Jenkins logs or other reasons, for
example, they are not valuable any more, the Jenkins system may delete some
of the historical records. Someday, you may find that the record indicated
by build_id won't exist in the future. It is OK if it does not exist in my
opinion.

Julien,
BR

David McBride <dmcbr...@linuxfoundation.org>于2018年4月26日周四 上午11:53写道：

> Hi Jack,
>
> Sorry for the slow response.  I've been busy with the Fraser release.
>
> Comments
>
>1. I didn't understand point 1 about the build_id.  I thought that was
>the purpose of the Jenkins macro that Julien developed.  What am I missing?
>2. I'd like to see Health Check broken out as a separate column from
>Functest.
>3. The installer drop-down just lists "Fuel".  We need to include both
>Fuel@x86 and Fuel@aarm64.
>
> Thanks for your effort in pushing this forward.
>
> David
>
>
> On Sun, Apr 22, 2018 at 8:49 PM, Chenjiankun (JackChan) <
> chenjiank...@huawei.com> wrote:
>
>> Hi David,
>>
>>
>>
>> As discussed in the previous Email, I have create a first version of
>> scenario results table(we can call it gating reporting J), see:
>>
>>  http://116.66.187.136:9998/index.html
>>
>> Patch see:
>>
>>  https://gerrit.opnfv.org/gerrit/#/c/56179/
>>
>>
>>
>> For now, I have added four filters:
>>
>> 1.   Scenario
>>
>> 2.   Version
>>
>> 3.   Installer
>>
>> 4.   Iteration(we will query the last 10 days data, the default
>> iteration is 10, if all record is more than 10, it will only 10 record)
>>
>>
>>
>> For now, we still have some problems to solve:
>>
>> 1. build_id(Jenkins id), we don’t have a unified ID to mark the
>> whole Jenkins jobs(deployment + functest + yardstick), for now, I use the
>> build_tag(e.g. jenkins-functest-fuel-baremetal-daily-master-131, the
>> project:functest and installer:fuel are in build_tag) to index, so we can
>> only show the functest result.
>>
>> 2.   Jenkins job results, depend on build_id, we can’t show all
>> results(deployment + functest + yardstick, only functest for now). And each
>> projects need to upload their results(UNTRIGGERED, PASS, FAIL).
>>
>> 3.   Deployment results, for now, only daisy upload its deployment
>> result, we need ask each installer to upload deployment results, only
>> build_id ready, we can show all results.
>>
>> 4.   Statistic results, depend on projects upload their results
>>
>>
>>
>> It is the first version, we will add more functions step by step after
>> the above issue solved.
>>
>> @All, if you have any suggestions, please let me know.
>>
>>
>>
>> BRs,
>>
>> Jack Chan
>>
>>
>>
>> *发件人:* chenjiankun
>> *发送时间:* 2018年1月22日 17:02
>> *收件人:* 'David McBride'
>> *抄送:* TECH-DISCUSS OPNFV; tro...@redhat.com; Brattain, Ross B; Rao,
>> Sridhar; OLLIVIER Cédric IMT/OLN; mark.bei...@dell.com; Yuyang
>> (Gabriel); ALFRED C 'MORTON ' (acmor...@att.com); emma.l.fo...@intel.com;
>> Liyin (Ace); Wangwulin (Linda); georg.k...@ericsson.com; Serena Feng;
>> Julien
>> *主题:* RE: [opnfv-tech-discuss][test-wg]Requirements for test resources
>> collection
>>
>>
>>
>> Thanks, David.
>>
>>
>>
>> According your descriptions, I have created a demo table as below(wish I
>> do not misunderstanding your meaning):
>>
>>
>>
>> *scenario *
>>
>> *date *
>>
>> *Jenkins *
>>
>> *Version *
>>
>> *Installer *
>>
>> *Deployment *
>>
>> *Functest *
>>
>> *yardstick *
>>
>> os-nosdn-nofeature-ha
>>
>> 2018-01-21
>>
>> Jenkins id
>>
>> euphrates
>>
>> compass
>>
>> pass
>>
>> pass
>>
>> pass
>>
>> 2018-01-21
>>
>> Jenkins id
>>
>> euphrates
>>
>> compass
>>
>> fail
>>
>> not trigger
>>
>> not trigger
>>
>> statistic
>>
>> 8/9/10
>>
>> (pass:8,triggered:9, total:10)
>>
>> 6/7/8
>>
>> 6/7/8
>>
>>
>>
>>
>>
>> This last line in table body is the statistics information, and lines
>> above are the detailed information(and it can be folded).
>>
>> The score 8/9/10 is pass/triggered/total. Total means should run,
>> triggered means actually run.
>>
>>

Re: [opnfv-tech-discuss] [opnfv-tsc] Summary of Weekly Technical Community Discussion Thursday April 12, 2018

[Julien]

Hi Bin,

Can you send me the model files in ONAP which can be used in Pharos?



HU, BIN <bh5...@att.com>于2018年4月12日周四 下午6:50写道：

> Hello community,
>
>
>
> Thank you all for attending the technical discussion today.
>
>
>
> Today, we discussed Fraser Release Checkpoint led by David McBride
> <https://wiki.opnfv.org/display/~dmcbride>. David will ask PTLs to report
> most recent status on Monday 4/16. And TSC will discuss and make
> “go”/”no-go” decision based on the information from David.
>
>
>
> We then discussed Pharos 2.0 proposal by Julien
> <https://wiki.opnfv.org/display/~Julien-zte>. Bin and Julien will sync up
> in terms of the infrastructure resource model in ONAP and the Pharos spec
> in OPNFV.
>
>
>
> For more details, please refer to the meeting minutes page [1], which
> includes attendees list and IRC log [2].
>
>
>
> On April 19th next week, we will discuss:
>
> -  A new project proposal Capstone
> <https://wiki.opnfv.org/download/attachments/2925877/Capstone%20project%20proposal.pdf?version=1=1521822665000=v2>
> by Jing Lu <https://wiki.opnfv.org/display/~JingLu5>.
>
> -  Test Framework Capability to Conduct Self-Test against a
> Known-Good DUT by Cedric Ollivier
> <https://wiki.opnfv.org/display/~ollivier>.
>
>
>
> Thanks
>
> Bin
>
>
>
> [1] https://wiki.opnfv.org/display/PROJ/Tc+Minutes+20180412
>
> [2]
> http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-04-12-13.00.html
>
>
> ___
> 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] [Fuel] [Danube] openstack step in fuel install fails with pacemaker

[Julien]

Hi,

I meet the same issue a month ago. It is because that Ubuntu release
16.04.04 LTS in March 2018, while it is only 16.04.02 LTS when Danube
released. There are some of the packages updated from the Ubuntu OS. They
are not compatible with Fuel installers' packages.

There are other packages issues when you even resolved this one. The only
possible way is to set up a local apt repo with the version 16.04.03 at
most.

BR,
Julien



Damon <da...@gladbach.com>于2018年4月9日周一 上午11:41写道：

>
>
> OPNFV – Danube 3.0 Fuel install error.
>
> I am getting this error during the openstack install process.  I have
> installed OS using fuel many times before on previous Openstack releases,
> and never ran into this.
>
> It says pacemaker can’t install without corosync, but corosync does appear
> to be installed.  Would anyone know why I’m seeing this error?
>
>
>
> Tried this with a single controller and a dual one, same result.  Node is
> simple KVM, standard OVS VLAN config, with cinder as storage.
>
>
>
> This is the command the install script seems to be failing at:
>
>
>
> root@node-10:~# /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold
> -o APT::Get::AllowUnauthenticated=1 install pacemaker
>
> Reading package lists...
>
> Building dependency tree...
>
> Reading state information...
>
> Some packages could not be installed. This may mean that you have
>
> requested an impossible situation or if you are using the unstable
>
> distribution that some required packages have not yet been created
>
> or been moved out of Incoming.
>
> The following information may help to resolve the situation:
>
>
>
> The following packages have unmet dependencies:
>
> pacemaker : Depends: corosync (>= 2.3.0) but it is not going to be
> installed
>
> E: Unable to correct problems, you have held broken packages.
>
> root@node-10:~#
>
>
>
> Coroysnc appears to be installed passed the required version.
>
>
>
> ||/ Name  Version
> ArchitectureDescription
>
>
> +++-=-===-===-
>
> ii  corosync  2.3.5-3ubuntu2.1
> amd64   cluster engine daemon and utilities
>
> root@node-10:~#
>
>
>
>
>
> Puppet log, which is basically the output of the failed command.
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) E: Unable to correct
> problems, you have held broken packages.
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) pacemaker : Depends:
> corosync (>= 2.3.0) but it is not going to be installed
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) The following packages
> have unmet dependencies:
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure)
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) The following
> information may help to resolve the situation:
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) or been moved out of
> Incoming.
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) distribution that some
> required packages have not yet been created
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) requested an impossible
> situation or if you are using the unstable
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) Some packages could not
> be installed. This may mean that you have
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) Reading state
> information...
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) Building dependency
> tree...
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) change from purged to
> present failed: Execution of '/usr/bin/apt-get -q -y -o
> DPkg::Options::=--force-confold -o APT::Get::AllowUnauthenticated=1 install
> pacemaker' returned 100: Reading package lists...
>
>
>
>
> ___
> 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] [pharos][infra-wg] PDF Sepc 1.0

[Julien]

Hi OPNFV lab owners,

According to TSC meeting on Mar. 30th, the first 3 stages has been approved
by the TSC(https://wiki.opnfv.org/display/meetings/tsc#TSC-March20,2018)
"*TSC approved the PDF spec 1.0 as mandatory baseline for CI in Pharos pods
and the three staged introduction time plan"*

If the CI POD does not meet the requirement, you should give an exception
request to the TSC.

As for stage 1, there is only one week left.
Please submit your PDFs patches and Infra and Pharos team will help to
review your patches.

BR,
Julien

Julien <julien...@gmail.com>于2018年3月19日周一 下午8:40写道：

> Hi OPNFV lab owners,
>
> I got the email list from [1]. If you are not the correct person, please
> correct me.
>
> With the help of the community, we have implemented most the PDF features
> for the physical POD.
> According to the discussion in INFRA WG and TC, we propose the PDF Spec
> 1.0 to the TSC to be approved at this week's TSC meeting.
> Currently, 17 PDF files have been submitted from 8 Labs.
>
> You can get detail PDF specifications on the link[2].
> The schedule of the PDF in the proposal is listed here.
>
>- Stage1: April 15th
>Final date for lab owners to create PDFs for CI resources
>- Stage2: June 15th
>2.1 Final date for installers to use PDF/IDF for production
>2.2 Final date for CI PODs to adopt PDF/IDF
>- Stage3: August 15th
>3.1 Final date for all community labs to adopt PDF/IDF
>3.2 Final date for LaaS to adopt PDF/IDF
>
>
> I would like to double check with you about your plan to meet the
> schedule.
> Can you provide all the PDF files of your PODs according to the schedule?
> If yes, what's your plan?
>
> [1], https://wiki.opnfv.org/display/pharos/Community+Labs
> [2],
> https://docs.google.com/viewer?url=https%3A%2F%2Fwiki.opnfv.org%2Fdownload%2Fattachments%2F2925933%2FPDF%2520-report.pdf%3Fversion%3D1%26modificationDate%3D1520873681000%26api%3Dv2=true=false=1
>
>
> If you have any question about PDF Spec 1.0, please contact me or INFRA WG.
>
> BR,
> Julien
>
___
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] Red-lined TSC Charter Document

[Julien]

Hi Ray,

*"Cap per company:*

   - *Each organization can have a maximum of 2 TSC reps." in url:
**https://wiki.opnfv.org/display/DEV/Community+Election+Procedure
   <https://wiki.opnfv.org/display/DEV/Community+Election+Procedure> *


I would suggest using the same word for company and organization in this
description, and maybe company here is better.


BR,
Julien

Raymond Paik <rp...@linuxfoundation.org>于2018年4月4日周三 上午7:49写道：

> Just update the wiki page incorporating Wenjing's feedback.  Take a look
> at the TSC Chair election section at
> https://wiki.opnfv.org/display/DEV/Community+Election+Procedure and let
> me know if there are other questions/feedback.
>
> Thanks,
>
> Ray
>
> On Mon, Apr 2, 2018 at 1:50 PM, Raymond Paik <rp...@linuxfoundation.org>
> wrote:
>
>> Wenjing:
>>
>> Good points.  Yes, I'll go ahead and update the wiki in the next few days.
>>
>> Thanks,
>>
>> Ray
>>
>> On Mon, Apr 2, 2018 at 1:35 PM, Wenjing Chu <wenjing@huawei.com>
>> wrote:
>>
>>> In the wiki page:
>>> https://wiki.opnfv.org/display/DEV/Community+Election+Procedure:
>>>
>>>
>>>
>>> The TSC member election is scheduled on “mid-September” with
>>> flexibility, but the TSC chair wording is still hard-coded to September 7.
>>> I think that should be modified to be consistent – so that the newly
>>> elected TSC members choose the Chair, not the outgoing TSC.
>>>
>>>
>>>
>>> If that is indeed the intent here, which I assume so, then we should
>>> revise the wiki text as soon as possible.
>>>
>>>
>>>
>>> Another problem with the wiki section related to Chair election is its
>>> reference to the OPNFV By-Law
>>>
>>> ” (per section 5.5(b) of the OPNFV Bylaws
>>> <https://www.opnfv.org/about/bylaws-and-policies/bylaws>)”.
>>>
>>> That is no longer valid. We should refer to the OPNFV Technical Charter
>>> (or LFN’s) instead.
>>>
>>>
>>>
>>> Regards
>>>
>>> Wenjing
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
>>> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Raymond Paik
>>> *Sent:* Wednesday, March 28, 2018 4:12 PM
>>> *To:* opnfv-tech-discuss <opnfv-tech-discuss@lists.opnfv.org>;
>>> opnfv-...@lists.opnfv.org
>>> *Subject:* [opnfv-tech-discuss] Red-lined TSC Charter Document
>>>
>>>
>>>
>>> All,
>>>
>>>
>>>
>>> Please find attached red-lined TSC Charter document that reflects
>>> OPNFV's move to a merit-based TSC. The new text was heavily borrowed from 
>>> OpenDaylight's
>>> Charter
>>> <https://www.opendaylight.org/wp-content/uploads/sites/14/2018/01/ODL-Technical-Charter-LF-Projects-LLC-FINAL.pdf>
>>>  as
>>> they already migrated to a merit-based TSC.  The details on size,
>>> eligibility, election timing, etc. will be updated on the wiki if/when
>>> community decides to make any tweaks.
>>>
>>>
>>>
>>> Please let me know if you have any questions/feedback.  The plan is to
>>> vote on this during the TSC meeting April 10th (after ~2 week review
>>> period).
>>>
>>>
>>>
>>> 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] [pharos][infra-wg] PDF Sepc 1.0

[Julien]

Hi OPNFV lab owners,

I got the email list from [1]. If you are not the correct person, please
correct me.

With the help of the community, we have implemented most the PDF features
for the physical POD.
According to the discussion in INFRA WG and TC, we propose the PDF Spec 1.0
to the TSC to be approved at this week's TSC meeting.
Currently, 17 PDF files have been submitted from 8 Labs.

You can get detail PDF specifications on the link[2].
The schedule of the PDF in the proposal is listed here.
- Stage1: April 15th
Final date for lab owners to create PDFs for CI resources
- Stage2: June 15th
2.1 Final date for installers to use PDF/IDF for production
2.2 Final date for CI PODs to adopt PDF/IDF
- Stage3: August 15th
3.1 Final date for all community labs to adopt PDF/IDF
3.2 Final date for LaaS to adopt PDF/IDF

I would like to double check with you about your plan to meet the schedule.
Can you provide all the PDF files of your PODs according to the schedule?
If yes, what's your plan?

[1], https://wiki.opnfv.org/display/pharos/Community+Labs
[2],
https://docs.google.com/viewer?url=https%3A%2F%2Fwiki.opnfv.org%2Fdownload%2Fattachments%2F2925933%2FPDF%2520-report.pdf%3Fversion%3D1%26modificationDate%3D1520873681000%26api%3Dv2=true=false=1


If you have any question about PDF Spec 1.0, please contact me or INFRA WG.

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

Re: [opnfv-tech-discuss] Updated invitation: OPNFV Plugfest planning bi-weekly @ Every 2 weeks from 7am to 7:45am on Monday from Mon Mar 12 to Mon May 21 (PDT) (opnfv-tech-discuss@lists.opnfv.org)

[Julien]

Hi Ray,

Is the location and date of the next plugfest determined yet?


于2018年3月3日周六 上午6:35写道：

> *This event has been changed.*
> more details »
> 
> OPNFV Plugfest planning bi-weekly
>
> *When*
> *Changed: *Every 2 weeks from 7am to 7:45am on Monday from Mon Mar 12 to
> Mon May 21 Pacific Time
> *Where*
> https://zoom.us/j/363757257 (map
> 
> )
> *Calendar*
> opnfv-tech-discuss@lists.opnfv.org
> *Who*
> •
> Raymond Paik - organizer
> •
> opnfv-tech-discuss@lists.opnfv.org
>
> Time: Mar 12, 2018 7:00 AM Pacific Time (US and Canada)
>
> Every 2 weeks on Mon, until May 21, 2018, 6 occurrence(s)
> Mar 12, 2018 7:00 AM
> Mar 26, 2018 7:00 AM
> Apr 9, 2018 7:00 AM
> Apr 23, 2018 7:00 AM
> May 7, 2018 7:00 AM
> May 21, 2018 7:00 AM
> Please download and import the following iCalendar (.ics) files to your
> calendar system.
> Weekly:
> https://zoom.us/meeting/363757257/ics?icsToken=779cac7ddb247bd3f70cd89a5b955c69d96826610957daa59f31f17a1d231d0b
> 
>
> Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/363757257
> 
>
> Or iPhone one-tap :
> US: +16699006833 <+1%20669-900-6833>,,363757257# or +16465588656
> <+1%20646-558-8656>,,363757257#
> Or Telephone:
> Dial(for higher quality, dial a number based on your current location):
> US: +1 669 900 6833 <+1%20669-900-6833> or +1 646 558 8656
> <+1%20646-558-8656> or +1 877 369 0926 <+1%20877-369-0926> (Toll Free) or +1
> 855 880 1246 <+1%20855-880-1246> (Toll Free)
> Meeting ID: 363 757 257
> International numbers available:
> https://zoom.us/zoomconference?m=zRVuS5g8Aj97M1nBofTz6twgQLqImEt7
> 
>
> Going?   All events in this series:   *Yes
> 
> - Maybe
> 
> - No
> *
> more options »
> 
>
> Invitation from Google Calendar 
>
> You are receiving this courtesy email at the account
> opnfv-tech-discuss@lists.opnfv.org because you are an attendee of this
> event.
>
> To stop receiving future updates for this event, decline this event.
> Alternatively you can sign up for a Google account at
> https://www.google.com/calendar/ and control your notification settings
> for your entire calendar.
>
> Forwarding this invitation could allow any recipient to modify your RSVP
> response. Learn More
> .
> ___
> 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] [releng] Secrets in environment variables

[Julien]

Hi Luke,

Yes, you can inject a secret string in the jjb :

wrappers:
 - credentials-binding:
 - zip-file:
credential-id: b3e6f337-5d44-4f57-921c-1632d796caa6
variable: CONFIG_ZIP
 - file:
credential-id: b3e6f337-5d44-4f57-921c-1632d796caab
variable: config_file
 - username-password:
credential-id: b3e6f337-5d44-4f57-921c-1632d796caac
variable: config_username_password
 - text:
credential-id: b3e6f337-5d44-4f57-921c-1632d796caad
variable: config_text

it supports file, text, username-password, etc. It can not be echo/cat
during the CI execution.
It requires a Credentials Binding plugin.
@Trevor, Aric, can you double check is it installed already?
We use this method to avoid API token leak issue in internal CI.

[1], https://docs.openstack.org/infra/jenkins-job-builder/wrappers.html
[2], https://wiki.jenkins.io/display/JENKINS/Credentials+Binding+Plugin


Luke Hinds 于2018年2月20日周二 下午4:11写道：

> Hi,
>
> Do we have the capability to handle (inject?) environment variable secrets
> in our CI that are set during a build?
>
> I am looking at introducing virus total checks into anteater and this
> needs an API key which we don't want to share in the open.
>
> Currently I have the code look for the key in the environment, rather then
> a config file..is this workable?
>
> e.g...
>
> export VT_KEY=''
> echo $VT_KEY
> 
> --
> Luke Hinds | NFV Partner Engineering | CTO Office | Red Hat
> e: lhi...@redhat.com | irc: lhinds @freenode | t: +44 12 52 36 2483
> ___
> 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] Issues with Anteater pretest process

[Julien]

Hi Bryan,

I have happened to work together with Luke on this project for some time.
It's really cool.
Thanks for your interests.

For the anteater container is already there in the docker hub, you can
directly use it without building from the very beginning.
Luke, you can help to verify the steps.

Several steps,
1. docker pull opnfv/releng-anteater
2. take Pharos project for example
3. docker run -it opnfv/releng-anteater -v
/Users/julien/Documents/git/opnfv/pharos:/home/opnfv/anteater/pharos
   I only map Pharos repo into the container to
/home/opnfv/anteater/pharos.
   any target path is OK.
4. /home/opnfv/venv/bin/anteater -p pharos *--path pharos/*

You can get some helpful info through:

/home/opnfv/venv/bin/anteater -h
Anteater - CI Gate Checks.

Usage:
  anteater (-p |--project)  [(-ps |--patchset) ]
  anteater (-p |--project)  [--path ]
  anteater (-h | --help)
  anteater --version

Options:
  -h --help Show this screen.
  --version Show version.

The only thing I want to mention is that *project_path* is a  *mandatory*
argument when you want to scan for the whole project.
-p project: to indicate which project to scan for we have some exceptions
name with this project name.

5. You can get the report log in .reports sub-directory besides terminal
[opnfv@c96175c845be anteater]$ ll .reports/
total 76
-rw-rw-r-- 1 opnfv opnfv 48546 Feb  7 06:14 anteater.log
-rw-rw-r-- 1 opnfv opnfv  9444 Feb  7 06:14 binaries-pharos.log
-rw-rw-r-- 1 opnfv opnfv  8630 Feb  7 06:14 contents-pharos.log
-rw-rw-r-- 1 opnfv opnfv  1030 Feb  7 06:14 licence-pharos.log

Regards,
Julien

Fatih Degirmenci <fatih.degirme...@ericsson.com>于2018年2月7日周三 上午3:38写道：

> Hi Bryan,
>
>
>
> Anteater is used for gating patches coming to OPNFV projects. See the
> Jenkins job configuration to see patches of which projects are gated.
>
>
>
>
> https://gerrit.opnfv.org/gerrit/gitweb?p=releng.git;a=blob;f=jjb/ci_gate_security/opnfv-ci-gate-security.yml
>
>
>
> And see the script that is executed by Jenkins job.
>
>
>
>
> https://gerrit.opnfv.org/gerrit/gitweb?p=releng.git;a=blob;f=jjb/ci_gate_security/anteater-security-audit.sh
>
>
>
> Adding Luke who is maintaining Anteater.
>
>
>
> /Fatih
>
>
>
> *From: *<opnfv-tech-discuss-boun...@lists.opnfv.org> on behalf of
> "SULLIVAN, BRYAN L (BRYAN L)" <bryan.sulli...@research.att.com>
> *Date: *Tuesday, 6 February 2018 at 17:54
> *To: *"opnfv-tech-discuss@lists.opnfv.org" <
> opnfv-tech-discuss@lists.opnfv.org>
> *Subject: *Re: [opnfv-tech-discuss] Issues with Anteater pretest process
>
>
>
> Hi all,
>
>
>
> Is anyone using this toolset for a project? I am trying to follow the
> instructions as below (I did figure out that you have to clone anteater
> first… that needs to be updated on the wiki).
>
>
>
> But the rest of the instructions just don’t work. It’s not clear how to
> run the anteater process once in the container. “anteater” is not in the
> path, and running “pip install .” on the root folder seems to build
> something, but it’s still not in the path and it’s not clear how to invoke
> the tool.
>
>
>
> Anyone supporting this tool – please respond asap so I can get an
> impression if I should continue down this path.
>
>
>
> Thanks,
>
> Bryan Sullivan | AT
>
>
>
> *From:* SULLIVAN, BRYAN L (BRYAN L)
> *Sent:* Tuesday, February 06, 2018 6:43 AM
> *To:* 'opnfv-tech-discuss@lists.opnfv.org' <
> opnfv-tech-discuss@lists.opnfv.org>
> *Subject:* Issues with Anteater pretest process
>
>
>
> Hi all,
>
>
>
> I’m starting to look at the pretest process for Anteater patches as
> described under “How can I test my entire project or pretest a patch?” at
> https://wiki.opnfv.org/pages/viewpage.action?pageId=11700198. The first
> instruction is not working:
>
>
>
> if you would like to perform a full retrospective check of your project,
> you can do so on any machine capable of running Docker. Follow these steps..
>
> Pull the anteater Docker image and build.
>
> docker build -t anteater .
>
>
>
> That command (docker build) is for building a container based upon a
> Dockerfile. It seems there’s a missing step – clone the Anteater repo and
> cd to the folder that contains the Anteater Dockerfile. Is that what was
> intended?
>
>
>
> Thanks,
>
> Bryan Sullivan | AT
>
>
> ___
> 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] [ovn4nfv] Request for PODs

[Julien]

Hi Trinath,

Your requirements is not clear enough, can you give more detail information:
1. For development test or CI test?
2. What's the current status of ovn scenario with installer Apex and JOID?

You can bring this topic to INFRA WG meeting on Monday.

Regards/Julien


Trinath Somanchi <trinath.soman...@nxp.com>于2018年2月2日周五 下午7:49写道：

> Hi POD teams –
>
>
>
> Please help me find vPODs  with APEX for development and testing.
>
>
>
>
>
> / Trinath Somanchi,
>
> NXP SDN/NFV Team.
>
>
>
>
>
>
>
> *From:* Trinath Somanchi
> *Sent:* Tuesday, January 16, 2018 12:04 PM
> *To:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* [ovn4nfv] Request for PODs
>
>
>
> Hi-
>
>
>
> For project OVN4NFV, to test OVN scenarios We require JOID or APEX based
> POD(s).
>
>
>
> Kindly please let me know the procedure to apply.
>
>
>
> Thanking you.
>
>
>
> /
>
>   Trinath Somanchi,
>
>NXP SDN/NFV Team.
>
>
> ___
> 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] [pharos] [infra] POD Descriptor File documentation for OPNF Docs hackfest?

[Julien]

Hi Alex,

I would like to support it.
I'm not sure whether we can provide it before version 1.0 released.
Currently, I suggest only cares about net_config to save time.

BR/Julien


Alexandru Avadanii <alexandru.avada...@enea.com>于2018年1月30日周二 上午4:48写道：

> Hi, Julien,
>
> Yes, there’s no `idf.yaml` (let’s call it a spec file), like we have for
> PDF.
>
> If we decide to add it, I can help fill in the Fuel section, the other
> installer teams will have to propose a format for each of their sections.
>
>
>
> BR,
>
> Alex
>
>
>
>
>
> *From:* Julien [mailto:julien...@gmail.com]
> *Sent:* Saturday, January 27, 2018 11:51 AM
> *To:* Alexandru Avadanii
> *Cc:* Rautakumpu, Mika (Nokia - FI/Espoo);
> opnfv-tech-discuss@lists.opnfv.org; Jack Morgan
> *Subject:* Re: [opnfv-tech-discuss] [pharos] [infra] POD Descriptor File
> documentation for OPNF Docs hackfest?
>
>
>
> Hi Alex,
>
>
>
> You have listed all the most important information about PDF.
>
> We will migrate all the definition and description into gerrit repo and
> release it in readthedocs together with all infra projects.
>
> I find that in our repo, we miss the idf.yaml for reference.
>
>
>
> BR/Julien
>
>
>
>
>
> Alexandru Avadanii <alexandru.avada...@enea.com>于2018年1月26日周五 上午3:28写道：
>
> Hi, Mika,
>
> Original documentation [1, 2, 3].
>
>
>
> However, I think the best reference is the schema file itself [6].
>
> Additional information about eyaml encryption can be found at [5].
>
> OPNFV Pharos docs has a small chapter about PDF [7], but I don’t think
> it’s detailed enough.
>
> Recent plumbing additions (related to PDF/IDF) were summarized in [4]
> (meanwhile all of that was merged).
>
>
>
> Jack, Julien, please let us know if we missed anything. Also, I think you
> wanted to maintain a wiki page for PDF – any updates on that?
>
>
>
> BR,
>
> Alex
>
>
>
> [1] https://wiki.opnfv.org/display/INF/POD+Descriptor
> <https://url10.mailanyone.net/v1/?m=1efN8Q-0001QK-6I=57e1b682=flivH33ibFJ9W9c-Dk8rwTtPHxbaiDgcwaoiavY5w-Uuu_zIz5LyJSNhMmAbYhJT_bmvUGrbY2djor9UOn4w5uzJonIH3QqN07_2Nh8KnWuEBBbNHXKIj_FeFNRIp2P2me6xOLmxUpZfFVmUvRmXFviomAYme8Yu9ZvRZDC0GcT4L09Mz0nCvYUsfrzrPBo2XDsGnFOMCtP58-R2FuVXE5YQMuN9zOr1lJzlEbKUs_4khivUmzWmZTPrpslPNz7t>
>
> [2]
> https://www.slideshare.net/OPNFV/how-to-reuse-opnfv-testing-components-in-telco-validation-chain?next_slideshow=1
> <https://url10.mailanyone.net/v1/?m=1efN8Q-0001QK-6I=57e1b682=CW9SyFf2jNnBx15OYIQDpBB9PG0f6TCuKDo-eR3wcTSkCCZXXXOKLr4OxHjv1WcJRT4Xzl-vPgb2Z68SYyjo08QjuS88oyYGgUS3j5xzvpUzx0xFvCLAKlGMS70d3LOprCtzicz-grKk7psvFDe1y4_RnhPilf21YJu2lup3Qto90QebeQb3znjIFmn0bfI6kvxGfL6eaRfXKirkIYuz77oDzxA7vGTed-r7za0dfIde9h9v-GT3LnZHdFHP8b2nVhgMNqYuDx0vIcyrlo-iedSxQnSJNNXqzDjN2yKtnr_rufeJ6cBKKmLImJrhRsEiUW-4J2GrimRnVxwxU_hSGA>
>
> [3] https://www.youtube.com/watch?v=iZcJQO9BAsU
> <https://url10.mailanyone.net/v1/?m=1efN8Q-0001QK-6I=57e1b682=utGwXzptpCoijlD06qkR5HCPcouOdlo_0Gt2s5hRE23dbcCIOZAWlGWh7REyLvwGcKcSjc-68IrVmKV9dZSzJogWABQKMKb2PFugpNTh5jPq81b61R-5EnvxsgxZEx5uvV9AbD9YJ2Voda6oWxO0YsdS9GuXf1aD1xsTjukHIiEhyjpQqJFBCHOTLDb1rUpyFDm12OLpXKxYeozTsPOgmwUBtMB_YwjIWmZW55aw2yqHsmbih5ASOPaPq66GhkFG>
>
> [4]
> https://www.mail-archive.com/opnfv-tech-discuss@lists.opnfv.org/msg08008.html
> <https://url10.mailanyone.net/v1/?m=1efN8Q-0001QK-6I=57e1b682=-W3HYHkaYwO9NYwKOpjWdWVWc3VR0g1OncwBKwj5H6O1ud6NM0R097lnwiCD04SDzv0Nu_83wa1ODeZ1OeRkJZBgnAvJvGfBEFkk6AfZY8vNVVF2wXcjN9Ty9gIjHXeQjt6ZinqEYFk19Sb_yyGg3vEAhp_eN7AQV3NypO1r5twPmszKHI25-CJrxq9lj476V_2Hjmy2JwET3TA77Wyv2hNvOh344exGy5M_30lZ8JMxQ1TC0oAJt6j6Q-l9uqoviAk-Xcyi4R0zauVzxSppnqWqFhedFwAh96lBM-rm0Cg>
>
> [5]
> https://github.com/opnfv/pharos/blob/master/config/utils/README.eyaml.rst
> <https://url10.mailanyone.net/v1/?m=1efN8Q-0001QK-6I=57e1b682=KT3Wwl7qPikoda7ZcRQdVirchR7Vh0Le8pQ9WtOo3h01T01G6XlmduLtGWDtfVDEMQ6qaIdppLA1hYzBWYv-gce_cpE681ABYhhlCqrxfyO_f4G2TR-v9igqjTHD_L1Lnk9K2tjUogmSiutmSF0oKlvmXRco-A85djBQNedqQifMdL4BKlXAI1mPU1HE3ViWvamJVflSTtKGNw_36yXNUBiUoKmBI2sOHNw-G0jwob9to8CZMoxuQnaZZfX5edtE0dpPQ39-dB_B4rpcrYKn8vp3uQ2XuHNXMykkXrr9B5c>
>
> [6] https://github.com/opnfv/pharos/blob/master/config/pdf/pod1.yaml
> <https://url10.mailanyone.net/v1/?m=1efN8Q-0001QK-6I=57e1b682=osRuADhxi8100Hk0INKkv_awPHDJgsXLmY_rayqMSgAN7L-kuWxZwhBMpKv2AhxEaft9PW6YY-WyWr6hgYECi4CevMQaWagV811TsdtEqhAS9m1WMvGbZ6nxl8n-l9VIbobTBmlFxNloTuLDfIujdTprEgdpxP6BJalwP3JgCJfXlCKyg9lqkM4lHf5VgJphL09-pLRLSVlQOUpMFfkSkYUcqlX1cokm9ICRKVa7-oKpRF5myyBgG9iSbYxfOfgh7cozDyOycEC78SgbEgihNw>
>
> [7]
> http://docs.opnfv.org/en/latest/submodules/pharos/docs/release/release-notes/lab-description/pdf.html
> <https://url10.mailanyone.net/v1/?m=1efN8Q-0001QK-6I=57e1b682=_2cTi7k6-doWmNTeQ

Re: [opnfv-tech-discuss] [opnfv-tsc] Trialing Zoom conferencing tool for TSC meetings

[Julien]

Hi Ray,

It's great! It's valuable for ASIA members esp in China. I usually lost
20-30% percent of voice in GTM and re-connect several times.

BR/Julien

Raymond Paik <rp...@linuxfoundation.org>于2018年1月31日周三 下午6:23写道：

> All,
>
> As I mentioned last week, I'd like to try out the Zoom conferencing tool
> for TSC meetings for a few weeks.  If all goes well, we'll migrate to Zoom
> for OPNFV meetings (incl. project team calls) in the next month or so.
>
> I updated the meeting logistics info on the TSC wiki (
> https://wiki.opnfv.org/display/meetings/TSC#TSC-February6,2018), and
> here's the Zoom info for the TSC call:
>
> Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/412267106
>
> Or iPhone one-tap :
>
> US: +16465588656 <+1%20646-558-8656>,,412267106#  or +16699006833
> <+1%20669-900-6833>,,412267106#
>
> Or Telephone:
>
> Dial(for higher quality, dial a number based on your current location):
>
> US: +1 646 558 8656 <+1%20646-558-8656>  or +1 669 900 6833
> <+1%20669-900-6833>  or +1 855 880 1246 <+1%20855-880-1246> (Toll Free)
> or +1 877 369 0926 <+1%20877-369-0926> (Toll Free)
>
> Meeting ID: 412 267 106
>
> International numbers available:
> https://zoom.us/zoomconference?m=YmfdIHzdm1cE0Fm9KwGrCvlr_puNua4X
>
> I'll send out another reminder before the call next week.
>
> 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] [test-wg]Requirements for test resources collection

[Julien]

Hi Jack,

I have finished the macro, but it failed for a Jenkins plugin is missing. I
cc the issue email to you, which will be discussed in the infra meeting.

BR/Julien

David McBride <dmcbr...@linuxfoundation.org>于2018年1月27日周六 上午12:13写道：

> +Julien
>
> Jack,
>
> I like the table format and the filtering options that you proposed.  Also
> +1 to Serena's suggestion to break out the health check data.
>
> I think that Julien is working on a Jenkins macro to enable the test API
> to retrieve the "jenkins id".  Julien - please confirm.
>
> David
>
> On Tue, Jan 23, 2018 at 10:53 PM, chenjiankun <chenjiank...@huawei.com>
> wrote:
>
>> Hi Serena,
>>
>>
>>
>> Thanks for your information updating.
>>
>> I am so glad to see TestAPI is ready to collecting deployment results,
>> and it would be much more convenient.
>>
>> One question: does all installer will push result to DB, or just Daisy
>> for now?
>>
>>
>>
>> For the Jenkins id, it means a combination of deployment + functest +
>> yardstick job. I am not sure if there are a ‘jenkins_id’ for now. This
>> field is for identify the combination jobs.
>>
>> For the second comment, maybe there are some misunderstanding, as David’s
>> requirements, we will show data last x iterations(not days), so I think
>> there will be no such problems.
>>
>> For the healthcheck column, I totally agree with you. But maybe it will
>> depend on functest to upload test result independently.
>>
>>
>>
>> What’s your opinions? @David, @Serena
>>
>>
>>
>> BRs,
>>
>> Jack Chan
>>
>>
>>
>> *发件人:* SerenaFeng(zte) [mailto:serena.feng.711+...@gmail.com]
>> *发送时间:* 2018年1月22日 18:08
>> *收件人:* chenjiankun
>> *抄送:* David McBride; Serena Feng; TECH-DISCUSS OPNFV
>> *主题:* Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources
>> collection
>>
>>
>>
>> Hi David & Jack,
>>
>>
>>
>> Thanks for mentioning the task, an interface for collecting deployment
>> results has been ready in TestAPI[1],
>>
>> the Macro for pushing deployment result is also ready by Jelien[2], I
>> believe it will facilitate all the installers' work,
>>
>> currently, Julien is working on pushing daisy results to TestAPI
>> leveraging that Macro, I think it will be finished soon.
>>
>>
>>
>> And regarding how to show all the information in a table, I suggest we
>> can take a look at Jack's proposal first.
>>
>>
>>
>> @Jack, a few comments:
>>
>> 1. what's the opinion of jenkins id?
>>
>> 2. for a scenario-installer combination, some will not run once in a
>> day(trigger multiple times or run in multiple pods),
>>
>> in this case, a simple pass/fail will be too vague, and to facilitate
>> the support of data iteration, I would suggest
>>
>> leveraging 8/9/10(8 passed, 9 triggered, 10total), delete the
>> final statistic line
>>
>> 3. how about adding a healthcheck column(functest-healthcheck test
>> cases), to see if the installer meets the milestone 3.0
>>
>>
>>
>>
>>
>> [1]: https://gerrit.opnfv.org/gerrit/#/c/49895/
>>
>> [2]: https://gerrit.opnfv.org/gerrit/#/c/48515/
>>
>>
>>
>> BRs
>>
>> Serena
>>
>>
>>
>> On Mon, Jan 22, 2018 at 5:02 PM chenjiankun <chenjiank...@huawei.com>
>> wrote:
>>
>> Thanks, David.
>>
>>
>>
>> According your descriptions, I have created a demo table as below(wish I
>> do not misunderstanding your meaning):
>>
>>
>>
>> *scenario *
>>
>> *date *
>>
>> *Jenkins *
>>
>> *Version *
>>
>> *Installer *
>>
>> *Deployment *
>>
>> *Functest *
>>
>> *yardstick *
>>
>> os-nosdn-nofeature-ha
>>
>> 2018-01-21
>>
>> Jenkins id
>>
>> euphrates
>>
>> compass
>>
>> pass
>>
>> pass
>>
>> pass
>>
>> 2018-01-21
>>
>> Jenkins id
>>
>> euphrates
>>
>> compass
>>
>> fail
>>
>> not trigger
>>
>> not trigger
>>
>> statistic
>>
>> 8/9/10
>>
>> (pass:8,triggered:9, total:10)
>>
>> 6/7/8
>>
>> 6/7/8
>>
>>
>>
>>
>>
>> This last line in table body is the statistics information, and lines
>> above are the detailed info

Re: [opnfv-tech-discuss] [pharos] [infra] POD Descriptor File documentation for OPNF Docs hackfest?

[Julien]

Hi Alex,

You have listed all the most important information about PDF.
We will migrate all the definition and description into gerrit repo and
release it in readthedocs together with all infra projects.
I find that in our repo, we miss the idf.yaml for reference.

BR/Julien


Alexandru Avadanii <alexandru.avada...@enea.com>于2018年1月26日周五 上午3:28写道：

> Hi, Mika,
>
> Original documentation [1, 2, 3].
>
>
>
> However, I think the best reference is the schema file itself [6].
>
> Additional information about eyaml encryption can be found at [5].
>
> OPNFV Pharos docs has a small chapter about PDF [7], but I don’t think
> it’s detailed enough.
>
> Recent plumbing additions (related to PDF/IDF) were summarized in [4]
> (meanwhile all of that was merged).
>
>
>
> Jack, Julien, please let us know if we missed anything. Also, I think you
> wanted to maintain a wiki page for PDF – any updates on that?
>
>
>
> BR,
>
> Alex
>
>
>
> [1] https://wiki.opnfv.org/display/INF/POD+Descriptor
>
> [2]
> https://www.slideshare.net/OPNFV/how-to-reuse-opnfv-testing-components-in-telco-validation-chain?next_slideshow=1
>
> [3] https://www.youtube.com/watch?v=iZcJQO9BAsU
>
> [4]
> https://www.mail-archive.com/opnfv-tech-discuss@lists.opnfv.org/msg08008.html
>
> [5]
> https://github.com/opnfv/pharos/blob/master/config/utils/README.eyaml.rst
>
> [6] https://github.com/opnfv/pharos/blob/master/config/pdf/pod1.yaml
>
> [7]
> http://docs.opnfv.org/en/latest/submodules/pharos/docs/release/release-notes/lab-description/pdf.html
>
>
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Rautakumpu,
> Mika (Nokia - FI/Espoo)
> *Sent:* Thursday, January 25, 2018 1:01 PM
> *To:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* [opnfv-tech-discuss] [pharos] [infra] POD Descriptor File
> documentation for OPNF Docs hackfest?
>
>
>
> Hi all,
>
>
>
> Is there any PDF documentation available at the moment? My plan is to
> participate OPNFV docs Hackfest next week and if there is no documentation
> from PDF, it could be one area that I could hack.
>
>
>
> Br,
>
> Mika Rautakumpu
>
>
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] commit info

[Julien]

Hi,

For I can not find your patches in https://gerrit.opnfv.org. I do believe
that you don't send your patch for review.

If you want to send a patch for review, please try it in terminal like
below:

git review -v

As in your screenshot, I guess you don't have git-review package installed
through pip in MINGW. You only can use "git review" command if you have
installed git-review.


张晨 于2018年1月25日周四 下午12:48写道：

> hi eric,
>
> i dont know where to find my commit link, here is my git log， plz help
>
>
>
> Thx！
> Chen
>
>
> —— 原始邮件 ——
>
> 发件人：eric.dm...@wipro.com "eric.dm...@wipro.com"
> 时 间：2018/01/23 11:18:29 星期二
> 收件人："zhangchen@chinatelecom.cn" "zhangchen@chinatelecom.cn"
> 抄送人：
> 主 题：commit info
>
> hello, please send me the link where I can find your commit, I am still
> learning my way around.
>
> Thanks
>
> Eric Maye
> 470-274-4670 <0470%20274%204670>
>
>
>
>
> Eric Maye
>
> 470-274-4670 <0470%20274%204670>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments. WARNING: Computer viruses can be
> transmitted via email. The recipient should check this email and any
> attachments for the presence of viruses. The company accepts no liability
> for any damage caused by any virus transmitted by this email.
> www.wipro.com
> __
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> __
> ___
> 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] Gerrit groups proposal

[Julien]

Hi Alex,

I update Pharos group name to "pharos-review" to keep the same format.


Alexandru Avadanii 于2018年1月26日周五 上午3:07写道：

> Hi, all,
> I've recently pushed a few Gerrit changes in Pharos that affect different
> installers and noticed it is hard to track down the appropriate committers
> to add as reviewers for each project.
> That's why I want to suggest we create more Gerrit groups.
>
> Pharos, Fuel and Armband already do that - to add all project committers
> as reviewers to a change one can use 'Pharos', 'fuel-review' or
> 'armband-review' groups.
> This makes it easier to track down & add committers one by one, and also
> reduces the number of mails Gerrit sends out during that operation.
>
> Afaik, any committer can create a Gerrit group. But if you do that, please
> align to the naming convention used so far: Gerrit group name == project
> name; eventually add a suffix, like '-review' if there's already an entity
> with that name, which was the case for Fuel.
>
> BR,
> Alex
> ___
> 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] [opnfv-tsc] [dovetail]step down the dovetail PTL and call for new PTL

[Julien]

Hongbo,

You have done lots of work to push forward the progress of Dovetail. Thanks
for your contribution and involvements.

BR/Julien


Tianhongbo <hongbo.tianhon...@huawei.com>于2018年1月27日周六 上午10:21写道：

> Hi：
>
> Add TSC
>
>
> Hongbo
>
> -Original Message-
> From: Dave Neary [mailto:dne...@redhat.com]
> Sent: 2018年1月27日 10:10
> To: Tianhongbo <hongbo.tianhon...@huawei.com>; 'Christopher Price' <
> christopher.pr...@ericsson.com>; 'marko.a.kui...@nokia.com' <
> marko.a.kui...@nokia.com>; 'Rautakumpu, Mika (Nokia - FI/Espoo)' <
> mika.rautaku...@nokia.com>; 'sheng-ann...@ericsson.com' <
> sheng-ann...@ericsson.com>; 'yangjian...@chinamobile.com' <
> yangjian...@chinamobile.com>; 'zhang.ju...@zte.com.cn' <
> zhang.ju...@zte.com.cn>; 'HU, BIN' <bh5...@att.com>; 'l...@biigroup.cn' <
> l...@biigroup.cn>; 'Tetsuya Nakamura' <t.nakam...@cablelabs.com>; Wenjing
> Chu <wenjing@huawei.com>; Christopher Donley (Chris) <
> christopher.don...@huawei.com>; 'Jose Lausuch' <jose.laus...@ericsson.com>;
> 'Shobhan AyyadevaraSesha (sayyadev)' <sayya...@cisco.com>; 'Canio Cillis'
> <canio.cil...@de.ibm.com>; 'Marco Varlese' <marco.varl...@suse.com>;
> 'Kedalagudde, Meghashree Dattatri' <
> meghashree.dattatri.kedalagu...@intel.com>; 'Lawrence Lamers' <
> ljlam...@vmware.com>; 'Georg Kunz' <georg.k...@ericsson.com>; 'Maria
> Toeroe' <maria.toe...@ericsson.com>; 'Rathnakumar Kayyar' <
> rkay...@lcnpl.com>; 'Gabor Halász' <gabor.hal...@ericsson.com>; 'Pierre
> Lynch' <ply...@ixiacom.com>; 'rgri...@linuxfoundation.org' <
> rgri...@linuxfoundation.org>; 'Ganesh Rajan' <gan...@pensanetworks.com>;
> 'Ahmed Elbornou (amaged)' <ama...@cisco.com>; 'Csatari, Gergely (Nokia -
> HU/Budapest)' <gergely.csat...@nokia.com>; 'GUPTA, ALOK' <ag1...@att.com>;
> xudan (N) <xuda...@huawei.com>; 'DRUTA, DAN' <dd5...@att.com>; Hesham
> ElBakoury <hesham.elbako...@huawei.com>; 'Tallgren, Tapio (Nokia -
> FI/Espoo)' <tapio.tallg...@nokia.com>; 'Vul, Alex' <alex@intel.com>;
> 'Reid Cheng (xincheng)' <xinch...@cisco.com>; 'Tomasini, Lorenzo' <
> lorenzo.tomas...@fokus.fraunhofer.de>; 'Bernier, Daniel' <
> daniel.bern...@bell.ca>; 'Seiler, Glenn' <glenn.sei...@windriver.com>;
> 'Lingli Deng' <denglin...@chinamobile.com>; 'Juraj Linkes -X (jlinkes -
> PANTHEON TECHNOLOGIES at Cisco)' <jlin...@cisco.com>; 'Ray Wong' <
> ray.w...@deltaww.com>; 'Wee Kok Liang Edmund' <edmund...@singtel.com>;
> 'Charles Hale' <charlie.h...@us.ibm.com>; 'Cooper, Trevor' <
> trevor.coo...@intel.com>; 'Andrew Veitch' <andrew.vei...@netcracker.com>;
> 'Alan McNamee' <alan...@openet.com>; 'James Buchanan' <
> jbucha...@advaoptical.com>; 'Masood Ul Amin' <masood.a...@aricent.com>;
> yunchao hu <yunchao...@huawei.com>; 'Mark Voelker' <mvoel...@vmware.com>;
> 'SULLIVAN, BRYAN L' <bs3...@att.com>; 'Catherine Cuong Diep' <
> cd...@us.ibm.com>; 'Aron Wahl' <a.w...@f5.com>; 'Jose Angel Lausuch' <
> jalaus...@suse.com>; Henry Fourie <louis.fou...@huawei.com>; 'Frattura,
> David' <david.fratt...@dell.com>; 'Pauls, Michael' <
> michael.pa...@tu-berlin.de>
> Subject: Re: [dovetail]step down the dovetail PTL and call for new PTL
>
> Hongbo,
>
> Thank you for your service as Dovetail PTL, Hongbo! Best of luck in your
> future role, I am glad that you got to see a Dovetail release.
>
> Regards,
> Dave.
>
> On 01/26/2018 07:41 PM, Tianhongbo wrote:
> > Hi all：
> >
> >
> >
> > I have been Dovetail PTL for 2 releases, and I am  Lucky  to see the
> > first official Dovetail released.
> >
> > Thanks all committers and contributors. Thanks for community support.
> >  Without your help, this cannot happen.
> >
> >
> >
> >
> >
> > But I have been reassigned to a new role internally and will resign as
> > PTL. Georg Kunz has agreed to step forward as a candidate for the new
> > PTL. Thanks Georg. Georg has made a lot of contribution to Dovetail. I
> > believe he can be a great PTL going forward. I’d also like to ask if
> > there are other committers who’d like to volunteer as a candidate.
> > Please respond in the next few days by 1/31 if anyone is interested
> >
> >
> >
> >
> >
> > Best regards
> >
> >
> >
> > Hongbo
> >
>
> --
> Dave Neary - NFV/SDN Community Strategy
> Open Source and Standards, Red Hat - http://community.redhat.com
> Ph: +1-978-399-2182 <+1%20978-399-2182> / Cell: +1-978-799-3338
> <+1%20978-799-3338>
> ___
> 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] New Adventures

[Julien]

Dan,

You have done us great help during these years. Thanks for your great
contrition and amazing achievements in OPNFV.

Julien

Tallgren, Tapio (Nokia - FI/Espoo) <tapio.tallg...@nokia.com>于2018年1月18日周四
下午5:53写道：

> Dan,
>
> Thanks for all the great work you have done in OPNFV and especially for
> the effort you have put into fixing issues with our hardware. It's been
> great working with you!
>
> -Tapio
>
> 
> From: opnfv-tech-discuss-boun...@lists.opnfv.org <
> opnfv-tech-discuss-boun...@lists.opnfv.org> on behalf of HU, BIN <
> bh5...@att.com>
> Sent: Wednesday, January 17, 2018 11:43:01 PM
> To: Dan Radez; opnfv-tech-discuss@lists.opnfv.org
> Subject: Re: [opnfv-tech-discuss] New Adventures
>
> Dan,
>
> You will be truly missed. I am sure our path will cross again somewhere.
>
> All the best in new adventure.
>
> Bin
>
> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Dan Radez
> Sent: Wednesday, January 17, 2018 11:56 AM
> To: opnfv-tech-discuss@lists.opnfv.org
> Subject: [opnfv-tech-discuss] New Adventures
>
> With a new year I have been assigned to a new primary project.
>
> I've enjoyed my time with OPNFV and want to say thank you to the community
> and leadership for the past three years of working together.
> It's been a pleasure to work along side of you all.
>
> I'll be around less but not inaccessible. I'll be working to hand off my
> tasks over the next couple weeks so they can be carried forward. Please be
> in contact with me if I'm not already in discussion with you about certain
> tasks.
>
> Happy New Year!
>
> Dan Radez
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_mailman_listinfo_opnfv-2Dtech-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=z7L52BOPjADgdI6kGIBakeWjVrD0tXk5Db3YhnwPU5I=jOeoBeRD8JLSbjhYBxZoe62CMkl3Z0FT606ZD86FRrY=
> ___
> 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 mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] opnfv gerrit page update

[Julien]

Hi Royta,

It's useful. If possible, I suggest to just put a *logo *to avoid the main
page is too congested.

I completely agree that Gerrit "as the main portal site for day-to-day
development".

Ryota Mibu <r-m...@cq.jp.nec.com>于2018年1月18日周四 上午12:35写道：

> Julien,
>
>
>
>
>
> I mean the #2 propose is to add links on top of all pages in gerrit. And
> by those links, you can go JIRA, Wiki and other pages useful for
> developers. You can see it in ONAP and ODL gerrit which Trevor Bramwell is
> pointing [1,2].
>
>
>
>
>
> BR,
>
> Ryota
>
>
>
> *From:* Julien [mailto:julien...@gmail.com]
> *Sent:* Wednesday, January 17, 2018 12:12 AM
> *To:* Juvonen, Tomi (Nokia - FI/Espoo) <tomi.juvo...@nokia.com>
> *Cc:* Mibu Ryota(壬生 亮太) <r-m...@cq.jp.nec.com>;
> opnfv-tech-discuss@lists.opnfv.org
> *Subject:* ##freemail## Re: [opnfv-tech-discuss] opnfv gerrit page update
>
>
>
> Hi Royta,
>
>
>
> +1 for the logo
>
>
>
> For links, I wonder shall we add a link to the website or add the links in
> each patch?
>
> In Gerrit, we can add "JIRA: PROJECT_NAEM-xxx" to track the Jira ticket. I
> don't know how to track others. It's useful to support in each patch.
>
>
>
>
>
> Juvonen, Tomi (Nokia - FI/Espoo) <tomi.juvo...@nokia.com>于2018年1月16日周二 下午
> 3:07写道：
>
> +1
>
> I think this is a create idea. Already using too many open tabs in browser
> in daily work.
>
> Br,
> Tomi
>
> > -Original Message-
> > From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-
> > boun...@lists.opnfv.org] On Behalf Of Ryota Mibu
> > Sent: Monday, January 15, 2018 5:57 PM
> > To: opnfv-tech-discuss@lists.opnfv.org
> > Subject: [opnfv-tech-discuss] opnfv gerrit page update
> >
> > Hi OPNFV developers,
> >
> >
> > I'd like to gather comments on the following ideas for our gerrit page
> update
> > (https://gerrit.opnfv.org/gerrit/).
> >
> >   1. Logo in gerrit page
> >
> > Add OPNFV logo in our gerrit page, so that we can easily identify
> OPNFV gerrit
> > page among other gerrit pages of other upstream projects. Icon in
> browser tab
> > should be changed to OPNFV leaf logo as well.
> >
> >   2. Links to developer pages
> >
> > Add links to Jira, Jenkins, Artifacts and other developer pages.
> That will enable
> > developer to use the gerrit page as a main portal site for day-to-day
> > development, rather than Jira. What we can expect more is an increase of
> > reviews, which is very important in open source projects.
> >
> > I believe these proposals are bringing only benefits. But if there is a
> problem
> > with such updates, we need to know before bad things happen.
> >
> >
> > Thanks,
> > Ryota
> >
> > > -Original Message-
> > > From: Trevor Bramwell via RT [mailto:
> opnfv-helpd...@rt.linuxfoundation.org]
> > > Sent: Saturday, January 13, 2018 3:15 AM
> > > To: Mibu Ryota(壬生 亮太) <r-m...@cq.jp.nec.com>
> > > Subject: [OPNFV Helpdesk #50899] opnfv logo in gerrit page
> > >
> > > Hi Ryota,
> > >
> > > I think this is a great idea! It should probably be floated by the TSC
> first so we
> > don't surprise anyone with changes
> > > to the Gerrit UI.
> > >
> > > My idea would be to add not just the logo but also link to Jira,
> Jenkins,
> > Artifacts, etc.
> > >
> > > We actually do this for a couple other networking projects (ODL[1],
> ONAP[2],
> > etc.) so I definitely think they'll be receptive
> > > as it helps align us with the networking umbrella projects.
> > >
> > > Would you mind getting it added to the agenda for the next TSC call, or
> > starting a discussion on the mailing list, please?
> > >
> > > Regards,
> > > Trevor Bramwell
> > >
> > > [1] https://git.opendaylight.org/gerrit/#/q/status:open
> > > [2] https://gerrit.onap.org/r/#/q/status:open
> > >
> > > On Wed Jan 10 00:17:54 2018, r-m...@cq.jp.nec.com wrote:
> > > > Hi,
> > > >
> > > >
> > > > Could you add OPNFV logo(s) in our gerrit page?
> > > >
> > > > This will help many developers find out OPNVF gerrit tab in their
> > > > browser quickly, especially developers who uses other project's
> > > > gerrit.
> > > >
> > > > Note, this can be a low priority request. I don't know how other
> > > &

Re: [opnfv-tech-discuss] [Pharos] Stepping down as PTL

[Julien]

Hi Jack,

It's my honor to with you in Pharos project and INFRA WG. We have achieved
much progress including specification documents, Dashboard, Pharos Labs all
over the world, number of committers, and recent PDFs under your
leadership. The community shall slow down without your help.

Thanks for your trust and nomination.

BR/Julien



Fatih Degirmenci <fatih.degirme...@ericsson.com>于2018年1月17日周三 下午4:13写道：

> Hi,
>
>
>
> +2.
>
>
>
> Welcome Julien. Looking forward to your guidance and support with Infra!
>
>
>
> Jack,
>
>
>
> It’s been a pleasure working with you and facing/tackling all the
> challenges together. We made a lot of progress when it comes to Infra,
> thanks to your leadership and contributions.
>
> Apart from OPNFV itself, you have been very important to cross-community
> collaboration and helped us a lot to keep things moving.
>
>
>
> Also, I am grateful for your patience, positive attitude and more
> importantly for your friendship.
>
> I will continue bugging you with my endless complaints no matter how much
> you stay involved in OPNFV because I know I’ll get the help when needed.
>
>
>
> Thank you.
>
>
>
> /Fatih
>
>
>
> *From: *<opnfv-tech-discuss-boun...@lists.opnfv.org> on behalf of Jack
> Morgan <jack.mor...@intel.com>
> *Date: *Wednesday, 17 January 2018 at 08:07
> *To: *"opnfv-tech-discuss@lists.opnfv.org" <
> opnfv-tech-discuss@lists.opnfv.org>
> *Subject: *[opnfv-tech-discuss] [Pharos] Stepping down as PTL
>
>
>
> OPNFV,
>
> It is with great sorrow that I'm announcing that I will be stepping down
> as the Pharos PTL. It has been nearly two years since I took over the PTL
> role and I hope my contributions have been beneficial. I really appreciate
> all the help and support I've received from the community. I feel I've
> really gained from the experience.
>
> In the meanwhile, I would like to nominate Julien Zhang as the next Pharos
> PTL. He has been very active in the Pharos project this past year not just
> with gerrit patches, but also in documentation, Infra WG meetings and other
> Pharos projects.
>
>
>
> Committers, please vote +2/-2 for Julien as Pharos PTL.
>
>
>
> Thanks,
>
> --
>
> Jack Morgan
>
> ___
> 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] opnfv gerrit page update

[Julien]

Hi Royta,

+1 for the logo

For links, I wonder shall we add a link to the website or add the links in
each patch?
In Gerrit, we can add "JIRA: PROJECT_NAEM-xxx" to track the Jira ticket. I
don't know how to track others. It's useful to support in each patch.


Juvonen, Tomi (Nokia - FI/Espoo) 于2018年1月16日周二
下午3:07写道：

> +1
>
> I think this is a create idea. Already using too many open tabs in browser
> in daily work.
>
> Br,
> Tomi
>
> > -Original Message-
> > From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-
> > boun...@lists.opnfv.org] On Behalf Of Ryota Mibu
> > Sent: Monday, January 15, 2018 5:57 PM
> > To: opnfv-tech-discuss@lists.opnfv.org
> > Subject: [opnfv-tech-discuss] opnfv gerrit page update
> >
> > Hi OPNFV developers,
> >
> >
> > I'd like to gather comments on the following ideas for our gerrit page
> update
> > (https://gerrit.opnfv.org/gerrit/).
> >
> >   1. Logo in gerrit page
> >
> > Add OPNFV logo in our gerrit page, so that we can easily identify
> OPNFV gerrit
> > page among other gerrit pages of other upstream projects. Icon in
> browser tab
> > should be changed to OPNFV leaf logo as well.
> >
> >   2. Links to developer pages
> >
> > Add links to Jira, Jenkins, Artifacts and other developer pages.
> That will enable
> > developer to use the gerrit page as a main portal site for day-to-day
> > development, rather than Jira. What we can expect more is an increase of
> > reviews, which is very important in open source projects.
> >
> > I believe these proposals are bringing only benefits. But if there is a
> problem
> > with such updates, we need to know before bad things happen.
> >
> >
> > Thanks,
> > Ryota
> >
> > > -Original Message-
> > > From: Trevor Bramwell via RT [mailto:
> opnfv-helpd...@rt.linuxfoundation.org]
> > > Sent: Saturday, January 13, 2018 3:15 AM
> > > To: Mibu Ryota(壬生 亮太) 
> > > Subject: [OPNFV Helpdesk #50899] opnfv logo in gerrit page
> > >
> > > Hi Ryota,
> > >
> > > I think this is a great idea! It should probably be floated by the TSC
> first so we
> > don't surprise anyone with changes
> > > to the Gerrit UI.
> > >
> > > My idea would be to add not just the logo but also link to Jira,
> Jenkins,
> > Artifacts, etc.
> > >
> > > We actually do this for a couple other networking projects (ODL[1],
> ONAP[2],
> > etc.) so I definitely think they'll be receptive
> > > as it helps align us with the networking umbrella projects.
> > >
> > > Would you mind getting it added to the agenda for the next TSC call, or
> > starting a discussion on the mailing list, please?
> > >
> > > Regards,
> > > Trevor Bramwell
> > >
> > > [1] https://git.opendaylight.org/gerrit/#/q/status:open
> > > [2] https://gerrit.onap.org/r/#/q/status:open
> > >
> > > On Wed Jan 10 00:17:54 2018, r-m...@cq.jp.nec.com wrote:
> > > > Hi,
> > > >
> > > >
> > > > Could you add OPNFV logo(s) in our gerrit page?
> > > >
> > > > This will help many developers find out OPNVF gerrit tab in their
> > > > browser quickly, especially developers who uses other project's
> > > > gerrit.
> > > >
> > > > Note, this can be a low priority request. I don't know how other
> > > > developers think though.
> > > >
> > > >
> > > > I'm not sure how we can config, but [1] tells that we need to config
> > > > /etc/gitweb.conf file and set '$logo' and '$favicon'. My suggestion
> of
> > > > images is the following:
> > > >
> > > > [logo] https://www.opnfv.org/wp-
> > > > content/uploads/sites/12/2016/11/opnfv_logo_wp.png
> > > >
> > > > [favicon]
> > > >
> > https://pbs.twimg.com/profile_images/606521736071401472/iRMp9gPD_400x
> > 4
> > > > 00.jpg
> > > >
> > > >
> > > > [1] https://gerrit-review.googlesource.com/Documentation/config-
> > > > gitweb.html
> > > >
> > > >
> > > > BR,
> > > > Ryota
> > >
> > >
> > >
> >
> > ___
> > 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 mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [container4nfv][clover]container4nfv has supported k8s 1.9

[Julien]

Hi Xuan,

I would like to check the codes and structures in project's repo.
Thanks for your information.

贾玄 <jiax...@chinamobile.com>于2018年1月14日周日 下午7:50写道：

> Hi Julien：
>
>From my understanding, istio and other features can be deployed as
> an application on kubernetes. It sounds like nginx application on
> kubernetes.
>
>In container4nfv, there will be an directory in repo named
> *NFV-PAAS*. All the architecture/application such as istio, prothemus,
> Harbor and so on will be written in that repo.  Other intallers could
> launch our scripts to deploy these features.
>
>Please keep in touch.
>
>
>
> Xuan Jia
>
> Project Manager
>
> Big Data & IT Technology Research Center China Mobile Research Institute
>
> 32 Xuanwumen West Street, Xicheng Distirct, Beijing 100032, China
>
> Mobile: (+86) 13811000575 <138%201100%200575>
>
> E-mail: jiax...@chinamobile.com
>
>
>
> *发件人:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *代表 *Julien
> *发送时间:* 2018年1月14日 16:49
> *收件人:* Yapeng Wu <yapen...@gmail.com>
>
> *抄送:* opnfv-tech-discuss@lists.opnfv.org
> *主题:* Re: [opnfv-tech-discuss] [container4nfv][clover]container4nfv has
> supported k8s 1.9
>
>
>
> Amazing! Great success has been achieved.
>
>
>
> Can these features be supported in any installer projects besides vagrant?
> Can they keep up with this container4nfv?
>
>
>
> BR/Julien
>
>
>
>
>
> Yapeng Wu <yapen...@gmail.com>于2018年1月13日周六 上午4:16写道：
>
> Hello, Xuan and other Clover folks,
>
> I tested K8S 1.9 installation, it works fine. On top of it, I can install
> istio 0.4 successfully.
>
>
>
> Cheers,
>
> Yapeng
>
>
>
> On Thu, Jan 11, 2018 at 2:11 PM, Stephen Wong <stephen.kf.w...@gmail.com>
> wrote:
>
> Hi Xuan,
>
>
>
> Great! Thanks!
>
>
>
> - Stephen
>
>
>
> On Thu, Jan 11, 2018 at 6:31 AM, 贾玄 <jiax...@chinamobile.com> wrote:
>
> Hi cloverer:
>
>
>
>Container4NFV has supported K8S 1.9 installation.
> https://github.com/opnfv/container4nfv/tree/master/src/vagrant/kubeadm_basic
> , Please check it if it’s working or not. Feel free to give your
> feedback.
>
>
>
>Thanks
>
>
>
> Xuan Jia
>
> E-mail: jiax...@chinamobile.com
>
>
>
>
>
> ___
> 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 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] Collecting questions for the Biterg Dashboard Training //RE: Issues/Needs/requirements for Biterg dashboard

[Julien]

Hi Mark and all,

I wonder whether there is any channel to collect responses about the data
on git/wiki/mailing list to make the dashboard easier to usage.
There are too many raw data.

BR/Julien

Beierl, Mark <mark.bei...@dell.com>于2018年1月12日周五 上午4:54写道：

> Hello, folks.
>
> This is the test results dashboard, not analytics on git/wiki/mailing
> list, etc, usage.  Bitergia has a second contract with LF to provide
> visualizations for the various test projects output.  Hope that clears
> things up :)
>
> Regards,
> Mark
>
> *Mark Beierl*
> SW System Sr Principal Engineer
> *Dell **EMC* | Cloud & Communication Service Provider Solution
> mobile +1 613 314 8106 <1-613-314-8106>
> mark.bei...@dell.com
>
> On Jan 11, 2018, at 11:12, SULLIVAN, BRYAN L (BRYAN L) <
> bryan.sulli...@research.att.com> wrote:
>
> If it results in some gaps being better socialized and prioritized, it's a
> good idea to meet. E.g. I sent a request back in Nov and got no response...
> it was:
>
> I’d like the ability to view/download the full set of data for a
> particular query, e.g. as you have from stackalytics (setting for “Show 
> entries”).
>
> Thanks,
> Bryan Sullivan | AT
>
> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org [
> mailto:opnfv-tech-discuss-boun...@lists.opnfv.org
> <opnfv-tech-discuss-boun...@lists.opnfv.org>] On Behalf Of Dave Neary
> Sent: Thursday, January 11, 2018 6:50 AM
> To: Yuyang (Gabriel) <gabriel.yuy...@huawei.com>; '
> opnfv-tech-discuss@lists.opnfv.org' <opnfv-tech-discuss@lists.opnfv.org>;
> test...@lists.opnfv.org
> Cc: Alberto Pérez García-Plaza <alpgar...@bitergia.com>; Alvaro del
> Castillo <a...@bitergia.com>; Jesus M. Gonzalez-Barahona <j...@bitergia.com>
> Subject: Re: [opnfv-tech-discuss] Collecting questions for the Biterg
> Dashboard Training //RE: Issues/Needs/requirements for Biterg dashboard
>
> Hi,
>
> Is the goal to get a better idea of how we can use the dashboard ("How
> can I tell how many companies were active in a project between date 1
> and date 2, excluding LF employees? What data sources are available for
> query?" type questions), or is it to identify qualitative questions we
> would like to answer with data ("Are we keeping participants over time?
> Are there projects for which timely  patch review/acknowledgement of
> issues is a challenge?") - understanding the goal of the tutorial would
> help with identifying the right questions to ask.
>
> Thanks,
> Dave.
>
> On 01/11/2018 04:40 AM, Yuyang (Gabriel) wrote:
>
> Hi Community,
>
>
>
> As discussed, Biterg will arrange a training session of OPNFV statistics
> dashboard for the community in test working group meeting.
>
> Basically, it will last about 1 hour as the usual first training
> covering the needs of navigating through panels, filtering the relevant
> results, sharing and exporting capabilities, etc.
>
> Before this wonderful thing could happen, it would better if you look at
> the dashboard first and feedback questions regarding the operations,
> visualizations,  settings, statistics results and etc. as input for the
> training.
>
> So that the training session could meet your needs in more efficient
> manner.
>
>
>
> During last Testperf meeting, we have already discussed some needs and
> questions which are listed below. Please post your questions/needs behind.
>
> 1.   How the commit number is calculated? What are involved in this
> metric? Including review?
>
> 2.   When searching commit number for a specific person, there will
> be other persons involved in the results page. Are these persons for the
> calculation of reviews?
>
> 3.   How should I search for the statistics results (commits, code
> line, patchsets, etc., ) of a project with aggregation results of
> companies, persons involved in this project
>
> 4.   Needs for comprehensive introduction of the dashboard including
> every operations, filtering relevant information, where the dashboard
> retrieve datas, etc.?
>
>
>
> Thanks,
>
> Gabriel
>
>
>
> *From:*Yuyang (Gabriel)
> *Sent:* Thursday, January 04, 2018 9:43 AM
> *To:* 'Alberto Pérez García-Plaza' <alpgar...@bitergia.com>
> *Cc:* 'Alvaro del Castillo' <a...@bitergia.com>; 'Raymond Paik'
> <rp...@linuxfoundation.org>; 'mark.bei...@emc.com'
> <mark.bei...@emc.com>; 'Brandon Wick' <bw...@linuxfoundation.org>;
> 'jalaus...@suse.com' <jalaus...@suse.com>; 'Rao, Sridhar'
> <sridhar@spirent.com>; 'Jesus M. Gonzalez-Barahona'
> <j...@bitergia.com>; 'cedric.olliv...@orange.com'
> <cedr

Re: [opnfv-tech-discuss] [container4nfv][clover]container4nfv has supported k8s 1.9

[Julien]

Amazing! Great success has been achieved.

Can these features be supported in any installer projects besides vagrant?
Can they keep up with this container4nfv?

BR/Julien


Yapeng Wu <yapen...@gmail.com>于2018年1月13日周六 上午4:16写道：

> Hello, Xuan and other Clover folks,
>
> I tested K8S 1.9 installation, it works fine. On top of it, I can install
> istio 0.4 successfully.
>
> Cheers,
> Yapeng
>
> On Thu, Jan 11, 2018 at 2:11 PM, Stephen Wong <stephen.kf.w...@gmail.com>
> wrote:
>
>> Hi Xuan,
>>
>> Great! Thanks!
>>
>> - Stephen
>>
>> On Thu, Jan 11, 2018 at 6:31 AM, 贾玄 <jiax...@chinamobile.com> wrote:
>>
>>> Hi cloverer:
>>>
>>>
>>>
>>>Container4NFV has supported K8S 1.9 installation.
>>> https://github.com/opnfv/container4nfv/tree/master/src/vagrant/kubeadm_basic
>>> , Please check it if it’s working or not. Feel free to give your feedback.
>>>
>>>
>>>
>>>Thanks
>>>
>>>
>>>
>>> Xuan Jia
>>>
>>> E-mail: jiax...@chinamobile.com
>>>
>>>
>>>
>>> ___
>>> 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 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] [test-wg] Monitoring dashboard for long duration test

[Julien]

It's really cool.

As Kubi mentioned, it is useful to support POD level metrics info including
containers, nodes, disk/memory usage.
For network traffic, it is too sensitive when we use the instant traffic,
can we provide the daily data?
The config file "prototype_prometheus_dashboard" in review is 2000 lines
long. I suggest to use a simple Jinja2 template to produce this file. It
will more easily to use and maintain.

BR/Julien



Rutuja Surve <rutuja.r.su...@gmail.com>于2017年11月26日周日 下午6:05写道：

> Hi Kubi,
> Thanks for reviewing the dashboard.
> It is possible to monitor multiple hosts (the jump server and its
> corresponding compute and controller nodes) with this dashboard. The
> 'instance' parameter for every metric corresponds to the IP address of the
> node, hence its possible to filter it by node IP. The whole physical
> deployment is configured in the pod.yaml file where we can see information
> regarding the compute and controller nodes.
> We have scripts for installing the statistics collecting daemons (Cadvisor
> and Collectd) on the jump-server and the client nodes (Compute and
> controller) that send the metrics to the jump server.
> The 'Load' corresponds to the CPU load and can be best explained with this
> Prometheus query that is used for collecting it:
>
> node_load1{instance=~\"$server:.*\"} / count by(job, instance)(count
> by(job, instance, cpu)(node_cpu{instance=~\"$server:.*\"}))
>
> CPU Usage per container corresponds to :
>
> sum(rate(container_cpu_usage_seconds_total{name=~\".+\"}[$interval])) by
> (name) * 100
>
> So, if the sum of the rate for a particular interval exceeds 1, it can
> cross 100% and reach upto 400%. It's more about how the query is framed.
> The network traffic apparently monitors the http port of the host.
>
> Do let me know if you have more questions.
>
> Thanks,
>
> Rutuja
>
>
>
>
>
>
>
> On Wed, Nov 22, 2017 at 8:25 AM, Gaoliang (kubi) <jean.gaoli...@huawei.com
> > wrote:
>
>> Hi Rutuja,
>>
>>
>>
>> The dashboard looks pretty good J
>>
>>
>>
>> Only few questions about the dashboard.
>>
>>
>>
>> What kind of  SUT you can monitor?  A single host or 5 hosts (OPNFV
>> physical HA deployment)?  It seems that It can be filtered by Node IP. Do
>> we have a whole view for a physical deployment POD?
>>
>>
>>
>> What does the “Load” mean? CPU Load?  Why “CPU usage” can go to 400%?
>> Does the “Network Traffic” monitor one port or all of the ports of host?
>>
>>
>>
>> Regards,
>>
>>
>>
>> Kubi
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From:* test-wg-boun...@lists.opnfv.org [mailto:
>> test-wg-boun...@lists.opnfv.org] *On Behalf Of *Rutuja Surve
>> *Sent:* Tuesday, November 21, 2017 4:42 PM
>> *To:* opnfv-tech-discuss@lists.opnfv.org; test...@lists.opnfv.org
>> *Subject:* [test-wg] Monitoring dashboard for long duration test
>>
>>
>>
>> Hi,
>>
>> I am currently working on Bottlenecks intern project focusing on
>> monitoring/dashboarding for long duration test.
>> We have been closing to a protoype. We need your opinions/comments on how
>> to organize the dashboard, what metrics/plugins should be included, etc.
>> The screenshots/details for the pre-protoype dashboard are provided
>> below. Please comment on that.
>> Currently, we do not have a public access to the dashboard. If you'd like
>> to know more details/operations, please refer to the gerrit patch:
>>
>> https://gerrit.opnfv.org/gerrit/#/c/47567/
>>
>> and give your review there or attend the Bottlenecks meeting tomorrow
>> (Wednesday) at 8.30 am IST where I will provide regular reports for the
>> progress and show customization of the dashboard.
>>
>>
>> Also find the screenshot-pdf of the dashboard attached with this e-mail.
>> We are using Prometheus for querying and as datasource, Cadvisor and
>> Collectd plugins for collecting system metrics and Grafana for displaying
>> the dashboard.
>>
>> Thanks,
>> Rutuja
>>
>>
>>
>
> ___
> 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] [infra][releng] proposal for RELENG project to take ownership of docker build resources

[Julien]

+1

I think the requirements in the community will be met when more scenarios
and more use cases listed as mentioned.


于2017年11月2日周四 下午5:21写道：

> +1
>
>
>
> My only concern is to get the same capabilities via RELENG than the Docker
> Automated tools or Travis-ci.
>
>
> https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-October/018536.html
>
>
>
> But we are working on that point :
>
> https://gerrit.opnfv.org/gerrit/#/c/46111/
>
>
>
> Cédric
>
>
>
> *De :* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *De la part de* David McBride
> *Envoyé :* mardi 31 octobre 2017 22:56
> *À :* TECH-DISCUSS OPNFV
> *Cc :* infra...@lists.opnfv.org; test-wg
> *Objet :* [opnfv-tech-discuss] [infra][releng] proposal for RELENG
> project to take ownership of docker build resources
>
>
>
> please +1, 0, or -1 to indicate your position
>
>
>
> Team,
>
>
>
> This topic came up during our release meeting two weeks ago.  I took an
> action to get a discussion started in the infra meeting.
>
>
>
> The proposal is for the RELENG project to take ownership of docker build
> resources (scripts,config files, etc.)
> 
>  for the purpose of providing a common docker build capability available to
> all users of OPNFV CI.  Active committers to these resources will remain
> unchanged.
>
>
>
> We had a good discussion on Monday.  There was general consensus that this
> proposal makes sense.  The minutes are here
> .
>
>
>
>
> I took an action at the infra meeting to start a discussion on the mailing
> list to seek additional feedback.  Please respond to this email to indicate
> whether you support the proposal.  Also feel free to add your comments.
> Thanks.
>
>
>
> David
>
>
>
>
> --
>
> *David McBride*
>
> Release Manager, OPNFV
>
> Mobile: +1.805.276.8018
>
> Email/Google Talk: dmcbr...@linuxfoundation.org
>
> Skype: davidjmcbride1
>
> IRC: dmcbride
>
> _
>
> 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
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [fuel] How to use packetary to create local repo for fuel

[Julien]

Hi

Fuel uses "fuel-mirror" to create mirrors for Fuel since Fuel9.

Since Euphrates, Mirantis abandoned Fuel and use MCP instead. They are
completely different architecture. I don't suggest to use Danube3.0
of Fuel, if you don't have exercises of Fuel previously.

Julien


np4gs3 <13787110...@163.com>于2017年10月27日周五 上午2:37写道：

> Hi,
> I use Fuel to deployment the OPNFV-D3,but my lab without internet
> access,So I use my notebook to create the fuel master VM.I want use the VM
> to build the local mirror repo . I known the packetary tools is the only
> tools to do it ,but I can not find the ubuntu_mirrors.yaml and
> ubuntu_packages.yaml to create mirrors.
> I read the packetary doc and edit the ubuntu_mirrors.yaml list below:
> - name: "mos9.0-ubuntu"
>   uri: "http://mirror.seed-cz1.fuel-infra.org/mos-repos/ubuntu/9.0/;
>   suite: "mos9.0"
>   section: ["main", "restricted"]
>   priority: 1000
>path: "/tmp/mirrors/ubuntu"
>
> - name: "mos9.0-ubuntu"
>   uri: "http://mirror.seed-cz1.fuel-infra.org/mos-repos/ubuntu/9.0/;
>   suite: "mos9.0"
>   section: ["main", "restricted"]
>   priority: 1000
>path: "/tmp/mirrors/ubuntu"
>
>
>   - name: "ubuntu"
> uri: http://archive.ubuntu.com/ubuntu/
> priority: null
> section:  ["main", "universe", "multiverse"]
> suite: "xenial"
> type: deb
> uri: http://archive.ubuntu.com/ubuntu/
> path: "/tmp/mirrors/ubuntu"
>
>   - name: "ubuntu-updates"
> priority: null
> section:  ["main", "universe", "multiverse"]
> suite: "xenial-updates"
> type: deb
> uri: http://archive.ubuntu.com/ubuntu/
> path: "/tmp/mirrors/ubuntu"
>
>   - name: ubuntu-security
> priority: null
> section: ["main", "universe", "multiverse"]
> suite: "xenial-security"
> type: deb
> uri: http://archive.ubuntu.com/ubuntu/
> path: "/tmp/mirrors/ubuntu"
>
>   - name: mos
> priority: 1050
> section: ["main", "restricted"]
> suite: "mos10.0"
> type: deb
> uri: http://10.10.10.2:8080/newton-10.0/ubuntu/x86_64
> path: "/tmp/mirrors/mos-repos "
>
>   - name: mos-updates
> priority: 1050
> section: ["main", "restricted"]
> suite: "mos10.0-updates"
> type: deb
> uri: http://mirror.fuel-infra.org/mos-repos/ubuntu/10.0/
> path: "/tmp/mirrors/mos-repos "
>
>   - name: mos-security
> priority: 1050
> section: ["main", "restricted"]
> suite: "mos10.0-security"
> type: deb
> uri: http://mirror.fuel-infra.org/mos-repos/ubuntu/10.0/
> path: "/tmp/mirrors/mos-repos "
>
>   - name: mos-holdback
> priority: 1100
> section: ["main", "restricted"]
> suite: "mos10.0-holdback"
> type: deb
> uri: http://mirror.fuel-infra.org/mos-repos/ubuntu/10.0/
> path: "/tmp/mirrors/mos-repos "
>
>   - name: Auxiliary
> priority: 1150
> section: ["main", "restricted"]
> suite: "auxiliary"
> type: deb
> uri: http://10.10.10.2:8080/newton-10.0/ubuntu/auxiliary
> path: "/tmp/mirrors/mos-repos "
>
> BUT there some errors when I  used this file ,So I need help for create
> local mirror .Thanks
>
>
>
>
> ___
> 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] PDF success story with Fuel/MCP on ericsson-pod1

[Julien]

It's great！
Thanks for your reminding. Re-support MCP in our PODS is in the schedule :)

Julien

HU, BIN <bh5...@att.com>于2017年10月28日周六 下午2:43写道：

> Great, congratulations.
>
> Bin
>
> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Alexandru
> Avadanii
> Sent: Friday, October 27, 2017 4:02 PM
> To: opnfv-tech-discuss <opnfv-tech-discuss@lists.opnfv.org>
> Subject: [opnfv-tech-discuss] PDF success story with Fuel/MCP on
> ericsson-pod1
>
> Hi,
> Today we re-enabled ericsson-pod1 as a Fuel CI POD in OPNFV, only by
> populating the PDF/IDF correctly.
> A big thank you to Dianfeng for helping us fill in the missing data, as
> well as Fatih and Aric for their support along the way!
>
> This is the validation we were looking for when we added PDF support in
> Fuel/MCP.
> Since lf-pod2 and ericsson-pod1 have quite different network layouts, we
> expected some tweaking to be required, but that was not the case.
>
> Note that our PDFs use the net_config section (which I would very much
> like to improve going forward), while the IDFs only describe the names of
> jumphost network bridges and PCI bus information for target node interfaces
> (for DPDK binding).
>
> I know ZTE has 1 or 2 Fuel PODs, which should also work with the new Fuel,
> provided thier PDFs are aligned with lf-pod2/ericsson-pod1.
>
> BR,
> Alex
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_mailman_listinfo_opnfv-2Dtech-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=86LlzA3fuV6NB613uBvbMKwrXZB1YU5TA-DShh_g12Y=bUh4RMHsW7A-wZfjytTkh50gcS1nhRkmXvINEvg7M10=
> ___
> 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] Support of new types in TOSCA

[Julien]

cc to Shang's another email-box.


Julien <julien...@gmail.com>于2017年10月16日周一 上午9:12写道：

> Hi Serena,
>
> It's a great news for TOSCA supported in Verigraph. It will make TOSCA
> template more useful and enhance Parser ecosystem. Currently Parser is
> integrating with ONAP project.
>
> If it is reasonable, we can add it in Parser project. Let's discuss this
> issue in email or with a meeting.
> Xiaodong, can you hold a team meeting using zoom?
>
> BR/Julien
>
>
> Serena Spinoso <serena.spin...@polito.it>于2017年10月7日周六 下午10:38写道：
>
>> Hi Shang, All,
>>
>> we would like to add the support of TOSCA in Verigraph, but we noticed
>> that our catalogue of network functions does not exactly match with the
>> types of nodes offered by TOSCA. That is the reason why we would kindly
>> ask you how we can add new node types in TOSCA and, in turn, in Parser.
>>
>> Thanks a lots.
>>
>> Serena
>>
>> --
>> Research Fellow
>> Politecnico di Torino
>> DAUIN - Dipartimento di Automatica e Informatica
>> Email: serena.spin...@polito.it
>>
>> ___
>> 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] [Infra] Infra WG Weekly Meeting Minutes - Oct. 9th

[Julien]

Hi David,

I agree your comments about net_config in [2]. Before my holiday maybe I
make a mistake that I think IDF is used for infrastructure network
descriptor.
For Jobs naming, I think in Kubernetes, we still need to resolve the usage
of network and storage, while these features are not well supported in the
Kubernetes community. Control is equivalent to Master, and Minion is
equivalent to Minion. It is difficult to define one set of names to meet
all the requirement. If someday VMware or HyperV is introduced into the
community as VIM, the names are meaningful to the new VIMs?


<david.blaisonn...@orange.com>于2017年10月16日周一 下午4:26写道：

> Hi everyone,
>
> I agree that the PDF/IDF definitions must be fixed ASAP.
>
>- *About net_config in IDF*: I think it is a bad idea. As i answer in
>the patch #42233 [2], if the L3 network is configured in the infra
>(firewall, router, ...), and not configurable by the installer, it must
>stay in the PDF. If the PDF leaves an empty L3 network section, it could be
>fixed by the installer, and configured in the IDF.
>- *About net_config as proposed by **Guillermo Herrero in #42893 [1]:*
>+1 with an official naming less openstack 'like'. For a better
>understanding and writing by infra ops, can we authorize comments
>describing what is this network in simple name (and openstack 'like' naming
>if the author like it)? We must consider that ops may not use the same
>convention in the data center, and pdf writting must not be painful.
>- *Jobs naming: *Today, jobs in IDF are also openstack centric and can
>only describe a ha or noha mode, but not both, I propose in #42233[2] that
>we use 'infra', 'worker' and 'infra_or_worker' as naming for main node's
>job. This will let SDF file describing what is the mapping  to openstack,
>k8s or any other vim naming.
>- *storage definition in shared IDF part [3]*: Julien propose to add
>the storage definition in IDF, I agree, but it must be consolidated. I will
>comment in the patch
>
> BR
>
> David
>
> [1] https://gerrit.opnfv.org/gerrit/#/c/42893
> <https://gerrit.opnfv.org/gerrit/#/c/42893/6/labs/lf/pod4.yaml>
> <https://gerrit.opnfv.org/gerrit/#/c/42893/6/labs/lf/pod4.yaml>
> <https://gerrit.opnfv.org/gerrit/#/c/42893/6/labs/lf/pod4.yaml>[2]
> https://gerrit.opnfv.org/gerrit/#/c/42233
> <https://gerrit.opnfv.org/gerrit/#/c/42233>
>
> <https://gerrit.opnfv.org/gerrit/#/c/42893/6/labs/lf/pod4.yaml>[3]
> https://gerrit.opnfv.org/gerrit/#/c/44603/1/labs/att/idf-pod1.yaml
> <https://gerrit.opnfv.org/gerrit/#/c/42233>
>
>
> --
> David BLAISONNEAU
> NFV platforms DevOPS - OPNFV contributor
> Orange - IMT / OLN / CNC / NCA / SINA
>
> tel: +33 (0)2 96 07 27 93 <+33%202%2096%2007%2027%2093>
> email: david.blaisonn...@orange.com
> 2, avenue Pierre Marzin 22307 LANNION Cedex - France
>
> Le 16/10/2017 à 02:25, Julien a écrit :
>
> Hi Alex,
>
> It's a great news.
> 2 PODs in our lab reserved for MCP are blocked to deploy in master branch.
> Can you give me a PDF/IDF link which are used now, then we will submit
> PDF/IDF patches according to your version.
>
> For **net_config**, I personally suggest to move it to IDF and get the
> template/format approved ASSP, for it is really important to us.
>
> BR/Julien
>
> Alexandru Avadanii <alexandru.avada...@enea.com>于2017年10月15日周日 下午9:44写道：
>
>> Hi,
>>
>> Fuel has been using PDF and IDF for weeks now.
>>
>> We still rely on net_config, which is out of spec, to map between PDF
>> networks and the network role within the installer.
>>
>> Apart from net_config, we still need to sort out the mapping between
>> interfaces indexes in PDF and the interface names inside OS (e.g. iface 0 =
>> eno1, iface 2 = enp1s0f1).
>>
>>
>>
>> For net_config, Guillermo proposed an alternative as a comment in [1],
>> which imo is closer to the hardware view of the setup (especially the
>> port_matrix part).
>>
>> For iface name mapping, we will probably add it to IDF as a Fuel-specific
>> section for now (no PoC proposed yet).
>>
>>
>>
>> BR,
>>
>> Alex
>>
>>
>>
>> [1] https://gerrit.opnfv.org/gerrit/#/c/42893/6/labs/lf/pod4.yaml
>>
>>
>>
>>
>>
>> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
>> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Julien
>> *Sent:* Sunday, October 15, 2017 12:38 PM
>> *To:* Jack Morgan; opnfv-tech-discuss
>> *Subject:* Re: [opnfv-tech-discuss] [Infra] Infra WG Weekly Meeting
>> Minutes - Oct. 9th
>>
>>
&

Re: [opnfv-tech-discuss] Support of new types in TOSCA

[Julien]

Hi Serena,

It's a great news for TOSCA supported in Verigraph. It will make TOSCA
template more useful and enhance Parser ecosystem. Currently Parser is
integrating with ONAP project.

If it is reasonable, we can add it in Parser project. Let's discuss this
issue in email or with a meeting.
Xiaodong, can you hold a team meeting using zoom?

BR/Julien


Serena Spinoso <serena.spin...@polito.it>于2017年10月7日周六 下午10:38写道：

> Hi Shang, All,
>
> we would like to add the support of TOSCA in Verigraph, but we noticed
> that our catalogue of network functions does not exactly match with the
> types of nodes offered by TOSCA. That is the reason why we would kindly
> ask you how we can add new node types in TOSCA and, in turn, in Parser.
>
> Thanks a lots.
>
> Serena
>
> --
> Research Fellow
> Politecnico di Torino
> DAUIN - Dipartimento di Automatica e Informatica
> Email: serena.spin...@polito.it
>
> ___
> 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] Swift Support

[Julien]

Hi Mark,

It may be widely used in IT such as Image/Video/File storage. In NFV
scenario, Swift may be not a good use case.
Traditional telco products don't produce, transfer and consume these files.
Maybe it is useful in Edge computing.

Julien

Beierl, Mark <mark.bei...@dell.com>于2017年10月11日周三 下午10:21写道：

> Hello,
>
> I was wondering what installers or use cases we have in OPNFV for Swift
> object storage.  One of the planning activities for StorPerf Fraser would
> be Swift profiling, but I am not sure how useful that is to the community.
>
> Regards,
> Mark
>
> *Mark Beierl*
> SW System Sr Principal Engineer
> *Dell **EMC* | Office of the CTO
> mobile +1 613 314 8106 <1-613-314-8106>
> mark.bei...@dell.com
>
> ___
> 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] [docs] Fuel and Armband merged documentation

[Julien]

I prefer to maintain it in installer project. If the affected content can
be documented in installer project properly, it will be easier for
maintainer, developer and end user.

Julien

Alexandru Avadanii <alexandru.avada...@enea.com>于2017年10月15日周日 下午11:27写道：

> Hi,
> During the E release cycle, Fuel and Armband projects merged their
> documentation(s).
> Currently, the contents of Fuel's 'docs/' dir describe usage for both
> architecture.
> To keep the old behavior unchanged, we duplicated that docs dir in Armband
> for now.
>
> Going forward, I think building the same documentation twice is wasteful
> and unnecessary.
> How do you think we should proceed in this case?
>
> We can agree that Armband project won't publish any docs going further,
> and just remove the docs dir from our repo.
> Or we can add a stub pointing to the Fuel project.
>
> Please let us know what you think.
>
> Thank you,
> Alex
> ___
> 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] [announce] user support topic for the TSC call

[Julien]

I just want to simplify the tools, one use case with one tool.
If we have multiple choice, I don't know which will be chosen and which
will be supported. For an end user, I care about how long it will take me
to get the feedback for my question. It may have duplicated threads in the
different tools.

Jira is good tools for issues, but I don't think it is suitable for
questions and supports. Title and content search are mostly used in
questions/forum, while it is not strong enough in Jira. From the history of
the website(ask.opnfv.org), we can find that it is not active enough, and
less response. If we agree to use that tool, and make it the only one, I
think it will be more and more useful to us.

BR/Julien



Beierl, Mark <mark.bei...@dell.com>于2017年10月16日周一 上午4:14写道：

> So far I have had a good experience with users reporting issues via JIRA.
> I must admit the askbot site has not been very useful for me at this time.
>
> Perhaps we need to highlight it more in the user guides?  I know I have
> not done that.
>
> Regards,
> Mark
>
> *Mark Beierl*
> SW System Sr Principal Engineer
> *Dell **EMC* | Office of the CTO
> mobile +1 613 314 8106 <1-613-314-8106>
> mark.bei...@dell.com
>
> On Oct 15, 2017, at 15:19, Raymond Paik <rp...@linuxfoundation.org> wrote:
>
> All,
>
> I'd like to propose having a discussion on user support in an upcoming TSC
> call.  We have two primary channels for user support which are opnfv-user
> mailing list plus our Askbot site (https://ask.opnfv.org/questions/).
>
> Over the past several quarters the activity on the Askbot site in
> particular has gone down (see
> https://opnfv.biterg.io:443/goto/5f1aedc882d4c3e33a1e3bab812e353e), and
> I'd like to start a discussion on support channel for OPNFV users plus
> other tools (e.g. documentation, wiki, etc.).
>
> I'll add this as a topic for the TSC call on the 17th, but I think it'd
> also make sense to have follow-up discussions with anyone interested in
> participating following the TSC call.
>
> In the mean time, if you have any suggestions or thoughts on this topic,
> please feel free to chime in
>
> Thanks,
>
> Ray
>
> ___
> 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 mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Infra] Infra WG Weekly Meeting Minutes - Oct. 9th

[Julien]

Hi Alex,

It's a great news.
2 PODs in our lab reserved for MCP are blocked to deploy in master branch.
Can you give me a PDF/IDF link which are used now, then we will submit
PDF/IDF patches according to your version.

For **net_config**, I personally suggest to move it to IDF and get the
template/format approved ASSP, for it is really important to us.

BR/Julien

Alexandru Avadanii <alexandru.avada...@enea.com>于2017年10月15日周日 下午9:44写道：

> Hi,
>
> Fuel has been using PDF and IDF for weeks now.
>
> We still rely on net_config, which is out of spec, to map between PDF
> networks and the network role within the installer.
>
> Apart from net_config, we still need to sort out the mapping between
> interfaces indexes in PDF and the interface names inside OS (e.g. iface 0 =
> eno1, iface 2 = enp1s0f1).
>
>
>
> For net_config, Guillermo proposed an alternative as a comment in [1],
> which imo is closer to the hardware view of the setup (especially the
> port_matrix part).
>
> For iface name mapping, we will probably add it to IDF as a Fuel-specific
> section for now (no PoC proposed yet).
>
>
>
> BR,
>
> Alex
>
>
>
> [1] https://gerrit.opnfv.org/gerrit/#/c/42893/6/labs/lf/pod4.yaml
>
>
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Julien
> *Sent:* Sunday, October 15, 2017 12:38 PM
> *To:* Jack Morgan; opnfv-tech-discuss
> *Subject:* Re: [opnfv-tech-discuss] [Infra] Infra WG Weekly Meeting
> Minutes - Oct. 9th
>
>
>
> Hi Jack and Infra team:
>
>
>
> This week I have a chance to directly discuss with installer team: Apex
> and Compass. I still can not contact Joid.
>
>
>
> This is the status of PDF in each installer:
>
>
>
> Apex: Not started, won't support in E release, and I have submitted a Jira
> ticket in Apex.
>
> Compass: Not started, and plan to support in F release
>
> Daisy: PDF is supported and used in CI PODs for deployment, while IDF is
> not used for now
>
> Fuel: Started, not finished yet
>
> Joid: No response in email and IRC(#opnfv-joid)
>
>
>
> I would like to suggest to clear PDF/IDF patches in gerrit, let's make an
> acceptable template and update them in the future, then the lab owners can
> submit their PDF/IDF and used for deployment.
>
>
>
> BR/Julien
>
> Jack Morgan <jack.mor...@intel.com>于2017年10月10日周二 上午12:38写道：
>
> October 9th
>
> *Agenda:*
>
> 1.Status update on PDF
>
> · complete discussion from last week as this is a deliverable for
> Euphrates release
>
> 2.LaaS and Dashboard integration Lincoln Lavoie
> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X=57e1b682=1IFLKZX5m-w0jQVJ5jKOFTYO7F6xOB6uhW0HliHa_qhFYHQbCgqPd_7z-PcOplBM_XsJaRrrND6tLlpvnOy0EcMi4rQvCGaIpiDit0Qn_vrbvc6Gc0p2_RpO8QfVna-rnESF04QP9JvQWJFXbJhH3nRZChwv5eW5YyfcgFFvvHVdOUepLOAmoKkBh_gKXbqLV4ztzfr9Ep4FoNlyp1oBXLgwPyiG7PIJsLaJ2sJKsHXGr_L8E2HcfSyqQoDRggGk>
>
> 3.Infra documentation on RTD - patch 40329
> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X=57e1b682=R3smn9KMUV4coY97MEbnSr5yc5wbiwHo7iTzbVVVZh-UBn7Uy7tj2tVtmNc9P1mkm4ETDwfjFlxDyAnXoZCzhWjT303o6iJAPB2lvRWP5MIR2nr24v2kpxlc_4CpgzBsyF18_RiEJ4PWRTWFPTIvXRKUnXJVi9zDFMhtXih8jGtlqajSV3QK60gIg1N0U-pi-PuGQ4RqO7K3HorX0WIlk4ArP9cBsrOFwcCQhC2B7GS5vSuQ5c44O6O2YghGUOwJ>
>  merged,
> what else?
>
> a. Discussion of Infra documentation
>
> 4.Zuul v3, Fatih Degirmenci
> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X=57e1b682=is70_YbviOZLKdDVg7G0GT7mi7Pl9P_RyyejcRkSk_KH3oTKeyS91Pg1hiWAr8WXwM6yRk7-4DYMolLZrkoPAZ6q1XXAAqJEZtjAsmWXXmy2siatCe_SAW7UeY-LCC0qoOWJ6IETo_Nl2CphSsrk54HFtmxMs0lEBgbHRtrWg6dv8zy8OpIfPu6tzbQc3Wes09BKcPdkbKJqzPrpYKzYDBaKoZa0gYRhcKUlILQ08wv_jTlIQxPZPimLlv-fLQGB>
>
>  .  possibility to start a prototype?
>
> 5.Follow up on security audit job logs  RELENG-272
> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X=57e1b682=wES3NshmpEfrUpqgTRuPoxbpwEKKOxH1CrN36Clv-z6aP_TkC9pTSo5yr7EiwrjUtZcASXoX_Oxg-OA4r4pCnfD6Hcq8CRpOAxcT4L_U8V2ky7mRNosDfSOakUCa2e_hZynjMk9YFWCXVX9GbVIY1hZScJomcqpT31hdUrGI_qf8wc296mZ3nom_L8FFhfokwmSveMkkFnEnQBE3UKuLehAh5euUhR_gWP3BjwYjgTqx3KE--iIta3bm3GbfWt3v>
>  - Ericsson Build 3 not reporting failures to comments *IN PROGRESS*
>
> 6.F Release participation
>
> 7.Review actions items
>
> *Minutes (*link
> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X=57e1b682=khjviKurcBef762jqBOj6fK_jj_cnNMQ5SK34IPrXlkXWn8QLrfOTumzKM-Tv0Q3F_8Rmz7mV609OlH00ThzNKaIGHQIJtz13i_VlrOhPsAlTE8u7GeApYKuFjipEF1Vm6Gnb4rJvDGQHAV5vPnYSrwTwaelmjOOjN1Ybzhk1nMlx3sfjUjTOe5PC-j8b63pcjJJ7QOWD13lQNjHi2165tv_c6Y3qS2zgKsISbCE4HDXMyauI6HVrW8I4PB9HKdOzXbve8QfgIEARROwdJN9-uL6

Re: [opnfv-tech-discuss] [Infra] Infra WG Weekly Meeting Minutes - Oct. 9th

[Julien]

Hi Jack and Infra team:

This week I have a chance to directly discuss with installer team: Apex and
Compass. I still can not contact Joid.

This is the status of PDF in each installer:

Apex: Not started, won't support in E release, and I have submitted a Jira
ticket in Apex.
Compass: Not started, and plan to support in F release
Daisy: PDF is supported and used in CI PODs for deployment, while IDF is
not used for now
Fuel: Started, not finished yet
Joid: No response in email and IRC(#opnfv-joid)

I would like to suggest to clear PDF/IDF patches in gerrit, let's make an
acceptable template and update them in the future, then the lab owners can
submit their PDF/IDF and used for deployment.

BR/Julien

Jack Morgan <jack.mor...@intel.com>于2017年10月10日周二 上午12:38写道：

> October 9th
>
> *Agenda:*
>
>1. Status update on PDF
>   - complete discussion from last week as this is a deliverable for
>   Euphrates release
>2. LaaS and Dashboard integration Lincoln Lavoie
><https://wiki.opnfv.org/display/%7Elylavoie>
>3. Infra documentation on RTD - patch 40329
><https://gerrit.opnfv.org/gerrit/#/c/40329/> merged, what else?
>   1. Discussion of Infra documentation
>   4. Zuul v3, Fatih Degirmenci
><https://wiki.opnfv.org/display/%7Efdegir>
>   1. possibility to start a prototype?
>5. Follow up on security audit job logs  RELENG-272
><https://jira.opnfv.org/browse/RELENG-272> - Ericsson Build 3 not
>reporting failures to comments IN PROGRESS
>6. F Release participation
>7. Review actions items
>
> *Minutes (*link
> <http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-10-09-15.01.html>
> *)*
>
>1. *Status update on PDF *
>   - David_Orange reports that IDF is mostly complete and haven't
>   heard any feedback during the last week on his patch below
>   - work in progress patch
>   https://gerrit.opnfv.org/gerrit/#/c/42233/5/labs/orange/idf-pod1.yaml
>   - current SDF patch https://gerrit.opnfv.org/gerrit/#/c/36977/
>2. *LaaS and Dashboard integration*
>   - lylavoie is working on LF hosting issues with bramwelt but will
>   focus on it after the release
>   - requirements gathering and plan is being tracked via Dashboard
>   Roadmap <https://wiki.opnfv.org/display/INF/Dashboard+Roadmap>
>3. *Infra documentation on RTD*
>   - initial patch 40329 <https://gerrit.opnfv.org/gerrit/#/c/40329/> has
>   been merged, what else needs to be migrated
>   - bramwelt has some documentation to post but not sure which
>   project it goes
>4. *AoB*
>   - bryan_att mentioned that the Equifax breach was due to Apache
>   structs vulnerability
>   - bryan_att suggests we need some discussion on potential scanner
>   tools for production deployments
>   - Luke will investigate ODL scanning and bryan_att will bring it up
>   at the TSC
>   - jmorgan1 mentions this is a good Plugfest topic
>5. *Action Items*
>   - contact installer PTLs support of PDF in Euphrates
>   - Fuel/MCP and Daisy4NFV has support for PDF, Compass4NFV will
>  delay working on it until F release
>  - Apex and Joid have not responded to emails
>   - closed and new action items below
>
> *Closed Actions:*
>
>- Contact installer PTLs for support of PDF in Euphrates julien zhang
><https://wiki.opnfv.org/display/%7EJulien-zte>
> - Submit patches to add lab owners and others to Pharos repo Aric Gardner
><https://wiki.opnfv.org/display/%7Eagardner>
>- Reach out to lab owners to collect feedback on including username
>and password in PDF Jack Morgan
>- Reach out to Luke Hinds <https://wiki.opnfv.org/display/%7Elukehinds> to
>security projects input on passwords in PDF Aric Gardner
><https://wiki.opnfv.org/display/%7Eagardner>
>- Create wiki page to track next steps and features for Laas/dashboard
>effort Lincoln Lavoie <https://wiki.opnfv.org/display/%7Elylavoie>
>- Reach out to Joid, Apex and Compass need to provide a contact for
>PDF effort julien zhang <https://wiki.opnfv.org/display/%7EJulien-zte>
>- create POC on encryption option Aric Gardner
><https://wiki.opnfv.org/display/%7Eagardner>
>-
>
> *New Actions:*
>
>- work on putting infrastructure documentation structure in place Trevor
>Bramwell <https://wiki.opnfv.org/display/%7Ebramwelt>
>- work with lylavoie to get CI Pods displayed on labs.opnfv.org Trevor
>Bramwell <https://wiki.opnfv.org/display/%7Ebramwelt>
>
> --
> Jack Morgan
> OPNFV Pharos Intel Lab
>
> ___
> 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] [opnfv-tsc] [qtip] stepping down as QTIP PTL after E release

[Julien]

Thanks Yujun,

Under your leadership, QTIP project has made a great progress. More and
more integration features have been implemented besides stability, It's
also an model to cooperate with upstream and other projects in the
community.

Yujun Zhang (ZTE) 于2017年10月9日周一 下午4:24写道：

> Hi all,
>
> I have decided to step down as PTL for QTIP after E release.
>
> I took the role since the end of C release. It has been a pleasant journey
> to travel across Danube and Euphrates and now it is time for a new leader
> to navigate the project in Fraser.
>
> I will stay onboard as a committer and continue to explore in OPNFV.
>
> Thanks all.
>
> --
> Yujun Zhang
>
> --
> Yujun Zhang
> ___
> 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] PDF feedback and questions from our experience with Fuel

[Julien]

Hi Alex,

Thanks for the conclusions of current working items in PDF.

Some response from my side:
1. 'vlan: 0' vs 'vlan: native':
'vlan: native' is easier for understanding. it is not fixed and a
specific vlan id will be required, while vlan 0 has some special meaning.
2. 'disk_rotation: ssd' or 'disk_rotation: 15000' for SSD drives.
disk_rotation is not valid for ssd.
3. 'features: dpdk|sriov' vs 'features: dpdk, sriov':
agree with David, yaml list is better
4. 'features: null' vs 'features: ' vs omitting it altogether: 'features:
[]' or omitting;
same as #3
5. inconsistent node naming:
the lab/pod can be identified by the full directory path. suggest to
use a clean and simple name without pod name in it. such as : pod1-node1
6. Address/netmask:
   when we use ifconfig, it is the simplest method to describe
address/netmask. It is "address" and "netmask" in interfaces(Ubuntu). How
about to support both of them.
7. 'os' in POD nodes:
Only in jumphost, for installer will be deployed in a VM in the
jumphost. It is meaningful for the installers.
8. IPMI interface MAC on the 'interfaces' list:
MAC address is not valid for IPMI access, we can cancel it.

About yamllint, I think when we finish the template, we can add a schema
for the PDF file and use it to verify the content.
About the interface names, I prefer to keep the original and easy
understandable names, such as: admin, management, public, etc.

BR/Julien


<david.blaisonn...@orange.com>于2017年9月26日周二 下午4:54写道：

> Hi,
>
> I hope I don't offend you about net_config, it is an hard subject, not
> easy to summarize, and born during summer holidays without everyone around
> the gerrit pit.
>
> About network naming, I understand the need of anonymize the networks
> parts to not over specify the installer level, but by calling them
> 'networkX' we will lost a precious information: 'how this network is
> prepared' by ops in network and security aspects. You may had already talk
> about that yesterday (sorry for missing it, job and child schedules
> collision), but simple networking questions must be answered when preparing
> a network mapping: Is this network NATed to outside ? does this network can
> talk to one other ? are some ip/ports opened at firewall level ? In Orange
> side, and for security aspects, we isolate some networks: Public can not
> talk to admin, storage is isolated and is not NATed to outside... Using
> 'admin', 'storage', 'public' naming give a part of the information, but
> 'networkX' don't, except if we are adding a description in the PDF like
> flow matrix, or we add external source, like the wiki. How do you think to
> handle that part ?
>
> This raise a more general question, is there recommendations about network
> topology and security rules in OPNFV pods or each lab is follow its own
> rules ?
>
> For C section, here are my answers:
>
> 1. 'vlan: 0' vs 'vlan: native': OK for native if 0 have a special meaning
> 2. 'disk_rotation: ssd' or 'disk_rotation: 15000' for SSD drives. Is
> disk_rotation enough to specify a disk performances? don't we also need the
> size of the cache ? we would better talk about bandwidth if we want also
> use it for ssd ? Maybe Bottlenecks project can help us.
> 3. 'features: dpdk|sriov' vs 'features: dpdk, sriov': it seems to be a
> collision between PDF specs and the yaml one. If it is a list we should
> simplify the installer parsing by using a yaml list: [ x, y, z] or a dashed
> list
> 4. 'features: null' vs 'features: ' vs omitting it altogether: 'features:
> []' or omitting; the first is yaml compliant with a list, the second is to
> simplify the pdf.
> 5. inconsistent node naming: in my opinion, this part shall be reserved
> for the ops, it is the only way for them to map a node with a physical
> server in the DC (except the ipmi address that is not the simple way to
> find a node). All values shall be authorized, but recommandation can be
> made on 'pod-')
> 6. Address/netmask: isn't netmask information in address overlaping with
> net_config netmasks ?
> 7. 'os' in POD nodes: Only in jumphost
> 8. IPMI interface MAC on the 'interfaces' list: no, it overlaps with
> remote_management/mac_address and is not seen from the os.
>
> Thanks again for this huge work of listing all pending points.
>
>
> BR
>
> David
>
>
>
> --
> David BLAISONNEAU
> NFV platforms DevOPS - OPNFV contributor
> Orange - IMT / OLN / CNC / NCA / SINA
>
> tel: +33 (0)2 96 07 27 93 <+33%202%2096%2007%2027%2093>
> email: david.blaisonn...@orange.com
> 2, avenue Pierre Marzin 22307 LANNION Cedex - France
>
> Le 25/09/2017 à 20:02, Alexandru Avadanii a écrit :
>
> Hi,
>
> The part about net_config was confusing because it was not (yet) part of
> the

Re: [opnfv-tech-discuss] [infra] [pharos] Splitting up the Pharos Repo

[Julien]

+1, PDF is better than template.

in the future, this file will be evolved into a pdf yaml schema file. It
can be directly used to verify the content in PDF.


Jack Morgan <jack.mor...@intel.com>于2017年9月20日周三 下午9:17写道：

> Thanks Julien for feedback. I made one small suggestions below, what do
> you think? thanks
>
> On 09/19/2017 10:52 PM, Julien wrote:
>
> Hi Trevor,
>
> Thanks for following these changes in pharos.
> Agree to merge LaaS and PDF changes.
>
> some comments:
>
>  pharos
>   - INFO
>   - config
> - pod1.yaml   ==> /template/pod1.yaml
>
> can we use pdf instead of template? config/pdf/pod1.yaml
>
> - installers
> - utils
>
>  pharos-tools
>   - lass-fog  ==> laas
>   - pharos-dashboard ==> dashboard
>   - pharos-validator==> validator
>
> BR/Julien
>
> Trevor Bramwell <tbramw...@linuxfoundation.org>于2017年9月20日周三 上午6:37写道：
>
>> Hi All,
>>
>> Yesterday in the Infra-WG we discussed[1] splitting up the Pharos
>> repository due to it's growing size. Jack and I discussed further how
>> he'd like the repo split up and I wanted to share with you our plans,
>> most of which will start tomorrow:
>>
>>  * Merging Peter's[2] patchsets for LaaS
>>
>>  * Merging Alex patchsets to move the PDF generator[3] work out of
>> securedlab and add pharos as a submodule of securedlab[4].
>>
>>  * Splitting out the pharos tools directory into it's own repo
>> pharos-tools using git-filter-branch:
>>
>>   git filter-branch -d pharos --tag-name-filter cat
>> --subdirectory-filter tools -- --all
>>
>>  * Updating the pharos git repository to remove the tools directory and
>> gitobjects created by those commits.
>>
>>  * Updating any related Jenkins jobs.
>>
>> The new structure of the repos would look like this:
>>
>>  pharos
>>   - INFO
>>   - config
>> - pod1.yaml
>> - installers
>> - utils
>>
>>  pharos-tools
>>   - lass-fog
>>   - pharos-dashboard
>>   - pharos-validator
>>
>>
>> If anything doesn't line up with what we talked about Jack, please
>> correct me!
>>
>> Regards,
>> Trevor bramwell
>>
>> [1]
>> http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-09-18-15.02.html
>> [2]
>> https://gerrit.opnfv.org/gerrit/#/q/owner:%22Parker+Berberian%22+status:open
>> [3]
>> https://gerrit.opnfv.org/gerrit/#/q/status:open+project:pharos+branch:master+topic:copy-pdf-from-securedlab
>> [4]
>> https://gerrit.opnfv.org/gerrit/#/q/status:open+project:securedlab+branch:master+topic:use-pharos-pdf
>> ___
>> opnfv-tech-discuss mailing list
>> opnfv-tech-discuss@lists.opnfv.org
>> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>>
>
>
> ___
> opnfv-tech-discuss mailing 
> listopnfv-tech-discuss@lists.opnfv.orghttps://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>
> --
> Jack Morgan
> OPNFV Pharos Intel Lab
>
> ___
> 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] [infra] [pharos] Splitting up the Pharos Repo

[Julien]

Hi Trevor,

Thanks for following these changes in pharos.
Agree to merge LaaS and PDF changes.

some comments:

 pharos
  - INFO
  - config
- pod1.yaml   ==> /template/pod1.yaml
- installers
- utils

 pharos-tools
  - lass-fog  ==> laas
  - pharos-dashboard ==> dashboard
  - pharos-validator==> validator

BR/Julien

Trevor Bramwell <tbramw...@linuxfoundation.org>于2017年9月20日周三 上午6:37写道：

> Hi All,
>
> Yesterday in the Infra-WG we discussed[1] splitting up the Pharos
> repository due to it's growing size. Jack and I discussed further how
> he'd like the repo split up and I wanted to share with you our plans,
> most of which will start tomorrow:
>
>  * Merging Peter's[2] patchsets for LaaS
>
>  * Merging Alex patchsets to move the PDF generator[3] work out of
> securedlab and add pharos as a submodule of securedlab[4].
>
>  * Splitting out the pharos tools directory into it's own repo
> pharos-tools using git-filter-branch:
>
>   git filter-branch -d pharos --tag-name-filter cat
> --subdirectory-filter tools -- --all
>
>  * Updating the pharos git repository to remove the tools directory and
> gitobjects created by those commits.
>
>  * Updating any related Jenkins jobs.
>
> The new structure of the repos would look like this:
>
>  pharos
>   - INFO
>   - config
> - pod1.yaml
> - installers
> - utils
>
>  pharos-tools
>   - lass-fog
>   - pharos-dashboard
>   - pharos-validator
>
>
> If anything doesn't line up with what we talked about Jack, please
> correct me!
>
> Regards,
> Trevor bramwell
>
> [1]
> http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-09-18-15.02.html
> [2]
> https://gerrit.opnfv.org/gerrit/#/q/owner:%22Parker+Berberian%22+status:open
> [3]
> https://gerrit.opnfv.org/gerrit/#/q/status:open+project:pharos+branch:master+topic:copy-pdf-from-securedlab
> [4]
> https://gerrit.opnfv.org/gerrit/#/q/status:open+project:securedlab+branch:master+topic:use-pharos-pdf
> ___
> 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] [infra][pharos]Is PDF feature supported by installer project now?

[Julien]

Hi, dear installer PTLs,

In this week's infra WG meeting, we discuss whether PDF(Pod Description
File) can be released or not. We want to know current status of each
installer project. As I can find in the wiki, all the installer projects
 in OPNFV, including Apex, Compass, Daisy, Fuel/MCP and Joid will attend
Euphrates release[1].

Currently, some PDF files have been submitted by pharos lab owners
including Ericsson, Intel, LF and ZTE. Several labs' PDF files including
ARM, BII, Huawei and Nokia are in review[2]. Aric has finished some
installer transfer script in scuredlab repo[3] using jinja template.

This feature is planned to released in Euphrates. If it is not supported
yet, can you share us current status and your plan.

[1]: https://wiki.opnfv.org/display/SWREL/Euphrates+Scenario+Status
[2]: https://gerrit.opnfv.org/gerrit/#/q/project:+securedlab+status:open
[3]: https://gerrit.opnfv.org/gerrit/#/admin/projects/securedlab

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

Re: [opnfv-tech-discuss] Topics for Weekly Technical Discussion

[Julien]

Hi Bob,

We are considering to setup a new ARM POD in our lab, and I plan only 5
blade servers with ARM CPU. I wonder I can still use a x86_64 server as the
jumphost for this ARM POD. I don't expect it will be blocked by another arm
server.

BR/Julien


Alec Hothan (ahothan) <ahot...@cisco.com>于2017年9月8日周五 上午6:31写道：

> Hi Trevor,
>
>
>
> Thanks for getting back on this. I agree there is not much incentive to
> run TRex on ARM at this point.
>
> ARM pods that want to do data plane benchmarking can use a HW traffic
> generator or run Trex on an Intel jump host.
>
>
>
> Thanks
>
>
>
>   Alec
>
>
>
>
>
>
>
> *From: *"Cooper, Trevor" <trevor.coo...@intel.com>
> *Date: *Thursday, September 7, 2017 at 2:37 PM
> *To: *"Alec Hothan (ahothan)" <ahot...@cisco.com>, "Beierl, Mark" <
> mark.bei...@dell.com>
>
>
> *Cc: *"opnfv-tech-discuss@lists.opnfv.org" <
> opnfv-tech-discuss@lists.opnfv.org>, "HU, BIN" <bh5...@att.com>, Raymond
> Paik <rp...@linuxfoundation.org>
>
> *Subject: *RE: [opnfv-tech-discuss] Topics for Weekly Technical Discussion
>
>
>
> Hi Alec …
>
>
>
> VSPERF does not currently plan to support TREX on ARM … it’s not clear
> what the benefit of this work would be given that there are multiple
> traffic generator options. The Pharos POD specification doesn’t have any
> bearing on components such as traffic generators.  We have found that
> software traffic generators have a wide variety of capabilities.
>
>
>
> /Trevor
>
>
>
>
>
>
>
>
>
> *From:* Alec Hothan (ahothan) [mailto:ahot...@cisco.com]
> *Sent:* Thursday, August 17, 2017 7:47 AM
> *To:* Beierl, Mark <mark.bei...@dell.com>
> *Cc:* opnfv-tech-discuss@lists.opnfv.org; HU, BIN <bh5...@att.com>;
> Raymond Paik <rp...@linuxfoundation.org>; Cooper, Trevor <
> trevor.coo...@intel.com>
> *Subject:* Re: [opnfv-tech-discuss] Topics for Weekly Technical Discussion
>
>
>
> [+Trevor to get vsperf point of view]
>
>
>
> Mark,
>
>
>
> Adding ARM artifacts is probably not that much work for python apps, for
> C/C++ apps that use DPDK it can be a lot more work.
>
> I just checked with the Trex team and as I suspected Trex is not available
> on ARM today. Somebody will have to try it out on an ARM server - meaning,
> it will take some work to compile Trex, link to DPDK and test it thoroughly
> to be on par with its x86 version – and a whole lot more people will have
> to maintain one more arch. The port might work right away or it might be
> pretty messy. I wonder if Trevor has a plan for TRex on ARM…
>
> From what I can see, to run data plane performance test with TRex on ARM
> pod will require an x86 server until Trex is validated on ARM.
>
>
>
> Thanks
>
>
>
> Alec
>
>
>
>
>
> *From: *"Beierl, Mark" <mark.bei...@dell.com>
> *Date: *Thursday, August 17, 2017 at 6:21 AM
> *To: *"Alec Hothan (ahothan)" <ahot...@cisco.com>
> *Cc: *"opnfv-tech-discuss@lists.opnfv.org" <
> opnfv-tech-discuss@lists.opnfv.org>, "HU, BIN" <bh5...@att.com>, Raymond
> Paik <rp...@linuxfoundation.org>
> *Subject: *Re: [opnfv-tech-discuss] Topics for Weekly Technical Discussion
>
>
>
> Alec,
>
>
>
> It is completely up to you how you want to structure your project and your
> deliverables.  If you don't want the extra hassle of supporting ARM, then
> don't.
>
>
>
> As for my project and the other ones that happen to support ARM, we will
> continue this discussion to see what makes sense.
>
>
>
> Regards,
>
> Mark
>
>
>
> *Mark Beierl*
>
> SW System Sr Principal Engineer
>
> *Dell **EMC* | Office of the CTO
>
> mobile +1 613 314 8106 <1-613-314-8106>
>
> *mark.bei...@dell.com <mark.bei...@dell.com>*
>
>
>
> On Aug 16, 2017, at 21:02, HU, BIN <bh5...@att.com> wrote:
>
>
>
> Alec,
>
>
>
> Thank you for your input, and letting know you won’t be able to make the
> meeting tomorrow.
>
>
>
> Mark,
>
>
>
> Do you still want to discuss in the meeting tomorrow? (my only concern is
> the attendance, which  may not warrant an effective live discussion.
>
>
>
> Or do you think the discussion on mailing list should be good enough?
>
>
>
> If we all think the discussion on mailing list is good enough, we don’t
> need to discuss it in the meeting tomorrow.
>
>
>
> Thanks
>
> Bin
>
>
>
> *From:* Alec Hothan (ahothan) [mailto:ahot...@cisco.com
> <ahot...@ci

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 <rp...@linuxfoundation.org>于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
> <https://wiki.opnfv.org/display/DEV/Nominees+for+2017+Elections>.  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 <rp...@linuxfoundation.org>于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
> <https://wiki.opnfv.org/display/DEV/Nominees+for+2017+Elections>.  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-wg][pharos] How to access securedlab

[Julien]

Hi all,

Some of the lab owners have the issue to access the securedlab repo, so
they can not submit the PDFs for their PODs. I don't find any document in
Pharos either.

This topic has been discussed in this week's infra working group meeting.
We have achieved an agreement that all the contributors in Pharos project
can access securedlab repo.

Here are the steps:
step1: send an email to help desk(opnfv-helpd...@rt.linuxfoundation.org) +
Jack(jack.mor...@intel.com, PTL) + Julien(julien...@gamil.com proxy for
Jack) to join as a contributor of Pharos Project (if you don't have a LF
account, please register one first)
step2: accept the invitation through email from Linux Foundation

Then, you can access the repo. Now it is actually easier than before.
I will also update this steps in Pharos document.

BR/Julien


Julien <julien...@gmail.com>于2017年8月11日周五 下午10:22写道：

> Dear POD owners,
>
> According to the discussion in the TSC in March and in the Plugfest
> meeting in Paris, in Euphrates release, all the PODs will provide PDF(Pod
> Description File) files in securedlab repo.  The PDF will be consumed by
> the all the installers to deploy and will be used in the pharos dashboard(
> http://labs.opnfv.org) and maybe testapi(
> http://testresults.opnfv.org/test/api/v1/results?project=functest=1).
> They also will be consumed by the scenario(DF) in dynamic CI in the next
> release.
>
> I find your name in wiki page
> https://wiki.opnfv.org/display/pharos/Community+Labs , and your PODs are
> still active. Please correct me if I make some mistakes.
>
> Ericsson, Intel, LF and ZTE have submitted patches to provide their PDFs
> and I wonder what's your plan and the target.
>
> The PDFs submitted already can be founded in
> https://gerrit.opnfv.org/gerrit/gitweb?p=securedlab.git;a=tree, this link
> is only can be viewed by lab owners(labs listed in pharos documents
> currently) and infra working group members.
>
> BR/Julien
>
>
___
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-project-leads] [release][euphrates] Milestone 6 - August 25

[Julien]

Hi David,

Here is Pharos project update,
Pharos infra features won't be tested through yardstick or functest. PDF is
the new added feature while stored in secoredlab repo.

1. Here are the CI output:
https://build.opnfv.org/ci/job/validate-jinja2-templates-master/77/console
2. document: newly build document link is
http://artifacts.opnfv.org/pharos/docs/index.html, and the compliance page
updated.

David McBride 于2017年8月25日周五 上午6:49写道：

> Team,
>
> As you know, MS6 is scheduled for tomorrow, August 25.  MS6 has two
> requirements:
>
>1. Complete test case implementation for test cases documented in the
>test case database for MS2.
>2. Complete preliminary documentation.  This means, at a minimum,
>committing the directory structure to your repo and adding placeholder
>files for the documents that you intend to deliver.
>
> Compliance verification:
>
>1. Please send me a link to the console output of your test cases
>running under Jenkins in OPNFV CI.
>2. Please complete the documentation compliance page for MS6 for your
>project.
>
> Let me know if you have questions.  Thanks.
>
> David
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
> ___
> opnfv-project-leads mailing list
> opnfv-project-le...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-project-leads
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [infra-wg][pharos]about the PDF of community PODs

[Julien]

Dear POD owners,

According to the discussion in the TSC in March and in the Plugfest meeting
in Paris, in Euphrates release, all the PODs will provide PDF(Pod
Description File) files in securedlab repo.  The PDF will be consumed by
the all the installers to deploy and will be used in the pharos dashboard(
http://labs.opnfv.org) and maybe testapi(
http://testresults.opnfv.org/test/api/v1/results?project=functest=1).
They also will be consumed by the scenario(DF) in dynamic CI in the next
release.

I find your name in wiki page
https://wiki.opnfv.org/display/pharos/Community+Labs , and your PODs are
still active. Please correct me if I make some mistakes.

Ericsson, Intel, LF and ZTE have submitted patches to provide their PDFs
and I wonder what's your plan and the target.

The PDFs submitted already can be founded in
https://gerrit.opnfv.org/gerrit/gitweb?p=securedlab.git;a=tree, this link
is only can be viewed by lab owners(labs listed in pharos documents
currently) and infra working group members.

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

Re: [opnfv-tech-discuss] Jump server common configuration for PXE/admin network - questions

[Julien]

please refer to my inline comments.

Alexandru Avadanii <alexandru.avada...@enea.com>于2017年8月7日周一 上午3:30写道：

> Hi,
> I am looking at integrating Fuel@OPNFV/MCP with our OPNFV baremetal PODs
> (both x86_64 and aarch64).
> Right now I am playing with MaaS and its network configuration.
>
> The old Fuel@OPNFV was relying on the jump server's "pxebr" bridge
> interface, which is supposed to reach all baremetal nodes, for PXE-booting
> purposes.
> If we want to reuse this interface as-is, we need to make sure "pxebr"
> will also have internet access, one way or another, on all PODs supporting
> Fuel@OPNFV deploys.
>
Julien: no directly internet access is required for "pxebr", but the node
which Fuel master deployed should have internet access.
  During the deployment, Fuel master will the check the internet
accessible through ping during configure stage and fetch packages during
the deployment.
  Usually the deploy the Fuel master as VM and all the response in
the following based on this assumption.

>
> Afaik, each POD is configured differently, the customizations ranging from
> different IP/subnets to totally different layouts.
> E.g. Armband used to have 2 network attached to its old Fuel Master node:
> - 1 x PXE/admin - no external configuration, TFTP/DNS/DHCP was provided by
> Fuel Master node - hooked up to a port in our dumb version of "pxebr";
> - 1 x public - external gateway, no external DHCP - hooked up to jump
> server's "public" bridge;
> However, x86 PODs running Fuel were configured to use only:
> - 1 x PXE/admin interface, hooked to "pxebr", which also had external
> internet access (NAT-ed?), but no external DHCP/DNS in order not to
> conflict with the ones provided by Fuel Master;
>
> Going forward, I would like to align the new network requirements between
> our PODs and the rest of the OPNFV pool, so here are some questions:
> - is PXE/admin interface (connected to "pxebr") supposed to always have
> internet access? If so, how? NAT on the jump server? Or external gateway?
> Can we assume this is going to happen for all PODs, or should we support
> different configurations as well?
>
Julien: Use static route is OK and SNAT should be used for Fuel master.
please also check whether the firewall in the jumpser blocks the packages.

> - is LOM (the network used to access baremetal nodes IPMI interfaces)
> routed to PXE/admin or public, or is it a separate, independent network?
> This seems to vary from POD to POD.
>
Julien: I would prefer a separate network. You can refer the configuration
in securedlab repo.

> - is LOM expected to have external DNS/DHCP, or is this up to the team
> responsible for POD config?
>
Julien: Usually we configure the LOM address statically or we can not keep
consistent relationship with hardware and management IP address.

>
> Thanks,
> Alex
> ___
> 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] Kernel version and Docker build failures (aka Shrenik, you were right)

[Julien]

Thanks Mark,

It's really annoying for different capabilities, different suggestions for
docker to be used in different OS.
It has caused our labs fail for several times.



Beierl, Mark 于2017年7月29日周六 上午9:12写道：

> Hello,
>
> Well I have had a little journey down the road of obscure bugs this past
> week.  I messed up the docker installation on Intel pod 24, and so had to
> re-install it.  From that point forward, I got this really annoying error
> when attempting to upgrade python's setuptools:
>
> OSError: [Errno 22] Invalid argument:
> '/usr/lib/python2.7/site-packages/pkg_resources/_vendor/packaging'
>
> If I started a new container, entered it and executed the pip install of
> newer version of setuptools, it worked just fine.  Of course, this
> container build step worked on my laptop, on Ericsson slave 3, etc, etc.
>
> I turned to our good friends in the Apex team for help.  When I was
> chatting with Tim Rozet he mentioned that they switched to overlay instead
> of loop devices due to having problems with loop devices.  Great!  I'll try
> that.
>
> Did a little reading of some sites from Tim, plus this particularly
> helpful one [1].  Turns out that when I reinstalled docker, it was a newer
> version that already uses overlays.  So I didn't have to change anything.
> But still it wasn't working.  Then I re-read [1].  To quote:
>
> "While testing overlay on kernel 3.10, I got errors while running docker
> build. Specifically I got errors when doing an rm on files of an underlying
> layer."
>
> Oh.  Upgrade of setuptools is removing the previous version.  From an
> underlying layer!  Quick: uname -a.  Yes!  I was on 3.10.
>
> Upgrade to 4.10 as per the instructions in [1] and it's all working
> again.  Hopefully this long rant might save someone else headache in the
> future.
>
> [1] https://adminswerk.de/overlayfs-docker-storage-driver-centos-7/
>
> Regards,
> Mark
>
> *Mark Beierl*
> SW System Sr Principal Engineer
> *Dell **EMC* | Office of the CTO
> mobile +1 613 314 8106 <1-613-314-8106>
> mark.bei...@dell.com
>
> ___
> 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] Lab as a Service - Installer Support

[Julien]

Hi,

Can we start from "standalone machines for virtual deployments"? Then we
can start new pods from the pharos dashboard and let the developers to use
it. In last OPNFV summit, there is a presentation using multiple VMs to
quick deployment a new environment, instead of from the ISO. Shall we try
this type of method?

About the security, is there a good way for the lab owner to allocate
several virtual pods in the the same physical lab under the same
jenkins/dashboard and keep the users separate by each other.

/Julien


liangqi (D) <liang...@huawei.com>于2017年7月19日周三 上午9:20写道：

> Hi Lincoln,
>
>
>
> Understood, that is great.
>
>
>
> Regards,
> QiLiang
> --
> *From:* Lincoln Lavoie [lylav...@iol.unh.edu]
> *Sent:* Wednesday, July 19, 2017 2:35
>
> *To:* liangqi (D)
> *Cc:* Luke Hinds; opnfv-tech-discuss
> *Subject:* Re: [opnfv-tech-discuss] Lab as a Service - Installer Support
> Hi QiLiang,
>
> We will likely contribute the scripts at some point, but right now, they
> are pretty specific to our environment, i.e. servers, addressing, etc.
> We're working to abstract this and make them more modular, which will make
> it easier to add the other scenarios, etc,  Once we have that playing nice
> it will be easier to share / contribute.
>
> Cheers,
> Lincoln
>
> On Tue, Jul 18, 2017 at 2:51 AM, liangqi (D) <liang...@huawei.com> wrote:
>
>> Hi Lincoln,
>>
>> Got it, thanks. So the users can get a pod with user specific opnfv
>> scenario installed, or a pod with user specific OS-only installed.
>>
>> BTW, I'm curious about how do the labaas's pods managed. Do the scripts
>> opensourced, can I get the code?
>>
>> Regards,
>> QiLiang
>> --
>> *From:* Lincoln Lavoie [lylav...@iol.unh.edu]
>> *Sent:* Tuesday, July 18, 2017 0:42
>> *To:* liangqi (D)
>> *Cc:* Luke Hinds; opnfv-tech-discuss
>> *Subject:* Re: [opnfv-tech-discuss] Lab as a Service - Installer Support
>>
>> Hi QiLiang,
>>
>> Some answer inline below, at least for how we've set stuff up so far.
>>
>>
>>
>> On Mon, Jul 17, 2017 at 11:56 AM, liangqi (D) <liang...@huawei.com>
>> wrote:
>>
>>> I can give some support from compass side. Also I'm recently working on
>>> opnfv installers' quickstart wrapper scripts(
>>> https://gerrit.opnfv.org/gerrit/#/c/36711/ ). Hope the scipts could
>>> ease developers/users better use the labaas resources.
>>>
>>>
>>>
>>> Here are three questions, after checked the wiki page:
>>>
>>> - How do the Laas resources allocated? Allocated as vpods pool and
>>> BM(1+3+2) pods pool?
>>>
>> We have systems setup to allow two virtual pods per hardware node to run
>> in the lab.  This is based on RAM/Disk/etc.  Access to a pod resource would
>> be scheduled through the Pharos dashboard system.
>>
>>
>>> - How do the vpods' and BM jumpserver's operating systems installed,
>>> manually pre installed by lab admin or auto installed trigger by jenkins
>>> when the pod is allocated?
>>>
>> We've built up some scripts and support to allow the virtual pod to be
>> "spun up" by the request through the dashboard.  This isn't actually hooked
>> up to Jenkins, if I understand it correctly, it's its own thing.  We are
>> trying to keep the system admin out of the request path.  This does depend
>> on the installer supporting a virtual deployment and a "hands off"
>> deployment approach.
>>
>> This will likely start with basic requests, i.e. one 1 or 2 scenarios
>> supported and go out from there.  We're also planning a developer version,
>> where the actual OPNFV deployment doesn't occur, so the developer can login
>> and pull their own artifacts onto the system to deploy from, etc.  Because
>> the systems are self contained and "throw away."  We'll be able to give
>> root access onto the environment for each Pod User.  At the end of the
>> Pod's lifetime, it just gets deleted.
>>
>>
>>> - Do laas pods share the same jenkins master with other opnfv pods or
>>> the laas will host a jenkins master to manage all the laas resources?
>>>
>> No, see above.
>>
>>
>>>
>>>
>>> Regards,
>>> QiLiang
>>> --
>>> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [
>>> opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of Luke Hinds [
>>> lhi...@redhat.com]
>>> *Sent:* Monday, July 17, 201

Re: [opnfv-tech-discuss] [anteater] build log for anteator

[Julien]

Oh,

I understand the issue: no output of the detailed log of the Jenkins task.

Luke, I will deal with this.


Luke Hinds 于2017年7月13日周四 下午10:13写道：

> How do you mean by build log Yujun? I am always interested in feedback /
> improvements.
>
>
> On Wed, Jul 12, 2017 at 4:10 AM, Yujun Zhang (ZTE) <
> zhangyujun+...@gmail.com> wrote:
>
>> I notices a warning on license header in
>> https://gerrit.opnfv.org/gerrit/#/c/36839/
>>
>> [image: Screen Shot 2017-07-12 at 11.03.55 AM.png]
>>
>> However the build log is not posted. It's OK for now since the failure is
>> clear enough. But it would be nice to have the build log as well as other
>> CI jobs.
>>
>> --
>> Yujun
>>
>> --
>> Yujun Zhang
>>
>> ___
>> opnfv-tech-discuss mailing list
>> opnfv-tech-discuss@lists.opnfv.org
>> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>>
>>
>
>
> --
> Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
> e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44
> 12 52 36 2483
> ___
> 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] [opnfv-tsc] TSC vote requested for Danube 3.0 release

[Julien]

Sorry for the late email.

My vote is -1

Personally I suggest to drop Danube release 3 and let's focus on the
release of Euphrates 1.0.
Currently most of the installers are busy on integrating and it is still a
challenge for them. I would like to give the installers more time and
resources in the next release.


Julien


Raymond Paik <rp...@linuxfoundation.org>于2017年7月13日周四 下午9:29写道：

> Thank to everyone who sent your votes.
>
> There were eleven +1 votes and one -1 vote, thus the release date of July
> 14th has been approved.
> (Trevor, Ross, and Viktor sent their +1 votes just to me via email.  They
> are proxies for Brian Skerry, Jack, and Tapio respectively.)
>
> Ray
>
> On Thu, Jul 13, 2017 at 12:02 AM, Juraj Linkes -X (jlinkes - PANTHEON
> TECHNOLOGIES at Cisco) <jlin...@cisco.com> wrote:
>
>> +1
>>
>>
>>
>> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
>> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Raymond Paik
>> *Sent:* Tuesday, 11 July, 2017 17:50
>> *To:* opnfv-...@lists.opnfv.org
>> *Cc:* opnfv-tech-discuss@lists.opnfv.org
>> *Subject:* [opnfv-tech-discuss] TSC vote requested for Danube 3.0 release
>>
>>
>>
>> All,
>>
>>
>>
>> After checking with several scenarios owners during the Release call
>> today, there was a consensus that people were ready to tag for the Danube
>> 3.0 release on July 14th.  There were some scenarios with degradation
>> compared to 1.0 or 2.0 releases, but they would be explained in
>> documentations (e.g. due to upstream bug).
>>
>>
>>
>> So, I'd like to ask the TSC members to vote on the following by 5pm
>> Pacific Time July 12th.
>>
>>
>>
>> "Does the TSC approve the Danube 3.0 release date of July 14?  (+1, 0,
>> -1)"
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Ray
>>
>
> ___
> opnfv-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] Multiple docker containers from one project

[Julien]

Hi Mark,

Yes, there may be some some configuration files or entry point shell file
in the sub-directory. We can keep in the same sub-directory and it can be
supported well.

Can you list some use case for the docker to contain other files in
parents' directory? Maybe it also can be supported during the bootup time.


Beierl, Mark <mark.bei...@dell.com>于2017年7月10日周一 上午7:26写道：

> My only concern is for dockerfiles that do a "COPY . /home" in them. That
> means all the code would be located under the docker directory.
>
> I suppose multiple ../ paths can be used instead.
>
> Regards,
> Mark
>
> *Mark Beierl*
> SW System Sr Principal Engineer
> *Dell **EMC* | Office of the CTO
> mobile +1 613 314 8106 <1-613-314-8106>
> mark.bei...@dell.com
>
> On Jul 9, 2017, at 19:03, Julien <julien...@gmail.com> wrote:
>
> Hi Cédric,
>
> Patch in  https://gerrit.opnfv.org/gerrit/#/c/36963/ is exact what I
> mean. Let's collect the opinions from the releng team.
>
> Julien
>
>
>
> Cedric OLLIVIER <ollivier.ced...@gmail.com>于2017年7月10日周一 上午4:15写道：
>
>> Hello,
>>
>> Please see https://gerrit.opnfv.org/gerrit/#/c/36963/ which introduces
>> several containers for Functest too.
>> I think the tree conforms with the previous requirements.
>>
>> Automating builds on Docker Hub is a good solution too.
>>
>> Cédric
>>
>> 2017-07-09 12:10 GMT+02:00 Julien <julien...@gmail.com>:
>>
>>> Hi Jose,
>>>
>>> According to the current implementation, current script only support one
>>> Dockerfile, my personal suggestion is:
>>> 1. list all the sub-directory which contains "Dockerfile"
>>> 2. build for each sub-directory fetched in #1
>>> 3. for the names, in the top directory using the project name, in the
>>> sub-directory using: project_name-sub_directory_name
>>> not too much changes for current script and easy for project to manage.
>>>
>>> /Julien
>>>
>>> Beierl, Mark <mark.bei...@dell.com>于2017年7月7日周五 下午11:35写道：
>>>
>>>> Hello,
>>>>
>>>> Having looked over the docker-hub build service, I also think this
>>>> might be the better approach.  Less code for us to maintain, and the merge
>>>> job from OPNFV Jenkins can use the web hook to remotely trigger the job on
>>>> docker-hub.
>>>>
>>>> Who has the opnfv credentials for docker-hub, and the credentials for
>>>> the GitHub mirror that can set this up?  Is that the LF Helpdesk?
>>>>
>>>> Regards,
>>>> Mark
>>>>
>>>> *Mark Beierl*
>>>> SW System Sr Principal Engineer
>>>> *Dell **EMC* | Office of the CTO
>>>> mobile +1 613 314 8106 <1-613-314-8106>
>>>> mark.bei...@dell.com
>>>>
>>>> On Jul 7, 2017, at 11:01, Xuan Jia <jason.jiax...@gmail.com> wrote:
>>>>
>>>> +1 Using build service from docker-hub
>>>>
>>>>
>>>> On Thu, Jul 6, 2017 at 11:42 PM, Yujun Zhang (ZTE) <
>>>> zhangyujun+...@gmail.com> wrote:
>>>>
>>>>> Does anybody consider using the build service from docker-hub[1] ?
>>>>>
>>>>> It supports multiple Dockerfile from same repository and easy to
>>>>> integrate with OPNFV Github mirror.
>>>>>
>>>>> [1]: https://docs.docker.com/docker-hub/builds/
>>>>>
>>>>>
>>>>> On Thu, Jul 6, 2017 at 11:02 PM Jose Lausuch <
>>>>> jose.laus...@ericsson.com> wrote:
>>>>>
>>>>>> Hi Mark,
>>>>>>
>>>>>>
>>>>>>
>>>>>> I would incline for option 1), it sounds better than searching for a
>>>>>> file. We could define specific values of DOCKERFILE var for each project.
>>>>>>
>>>>>>
>>>>>>
>>>>>> /Jose
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> *From:* Beierl, Mark [mailto:mark.bei...@dell.com]
>>>>>> *Sent:* Thursday, July 06, 2017 16:18 PM
>>>>>> *To:* opnfv-tech-discuss@lists.opnfv.org
>>>>>> *Cc:* Julien <julien...@gmail.com>; Fatih Degirmenci <
>>>>>> fatih.degirme...@ericsson.com>; Jose Lausuch <
>>>>>> jose.laus...@ericsson.com>
>>>>>> *Subject:* Re: [opnfv-tech

Re: [opnfv-tech-discuss] Multiple docker containers from one project

[Julien]

Hi Cédric,

Patch in  https://gerrit.opnfv.org/gerrit/#/c/36963/ is exact what I mean.
Let's collect the opinions from the releng team.

Julien



Cedric OLLIVIER <ollivier.ced...@gmail.com>于2017年7月10日周一 上午4:15写道：

> Hello,
>
> Please see https://gerrit.opnfv.org/gerrit/#/c/36963/ which introduces
> several containers for Functest too.
> I think the tree conforms with the previous requirements.
>
> Automating builds on Docker Hub is a good solution too.
>
> Cédric
>
> 2017-07-09 12:10 GMT+02:00 Julien <julien...@gmail.com>:
>
>> Hi Jose,
>>
>> According to the current implementation, current script only support one
>> Dockerfile, my personal suggestion is:
>> 1. list all the sub-directory which contains "Dockerfile"
>> 2. build for each sub-directory fetched in #1
>> 3. for the names, in the top directory using the project name, in the
>> sub-directory using: project_name-sub_directory_name
>> not too much changes for current script and easy for project to manage.
>>
>> /Julien
>>
>> Beierl, Mark <mark.bei...@dell.com>于2017年7月7日周五 下午11:35写道：
>>
>>> Hello,
>>>
>>> Having looked over the docker-hub build service, I also think this might
>>> be the better approach.  Less code for us to maintain, and the merge job
>>> from OPNFV Jenkins can use the web hook to remotely trigger the job on
>>> docker-hub.
>>>
>>> Who has the opnfv credentials for docker-hub, and the credentials for
>>> the GitHub mirror that can set this up?  Is that the LF Helpdesk?
>>>
>>> Regards,
>>> Mark
>>>
>>> *Mark Beierl*
>>> SW System Sr Principal Engineer
>>> *Dell **EMC* | Office of the CTO
>>> mobile +1 613 314 8106 <1-613-314-8106>
>>> mark.bei...@dell.com
>>>
>>> On Jul 7, 2017, at 11:01, Xuan Jia <jason.jiax...@gmail.com> wrote:
>>>
>>> +1 Using build service from docker-hub
>>>
>>>
>>> On Thu, Jul 6, 2017 at 11:42 PM, Yujun Zhang (ZTE) <
>>> zhangyujun+...@gmail.com> wrote:
>>>
>>>> Does anybody consider using the build service from docker-hub[1] ?
>>>>
>>>> It supports multiple Dockerfile from same repository and easy to
>>>> integrate with OPNFV Github mirror.
>>>>
>>>> [1]: https://docs.docker.com/docker-hub/builds/
>>>>
>>>>
>>>> On Thu, Jul 6, 2017 at 11:02 PM Jose Lausuch <jose.laus...@ericsson.com>
>>>> wrote:
>>>>
>>>>> Hi Mark,
>>>>>
>>>>>
>>>>>
>>>>> I would incline for option 1), it sounds better than searching for a
>>>>> file. We could define specific values of DOCKERFILE var for each project.
>>>>>
>>>>>
>>>>>
>>>>> /Jose
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *From:* Beierl, Mark [mailto:mark.bei...@dell.com]
>>>>> *Sent:* Thursday, July 06, 2017 16:18 PM
>>>>> *To:* opnfv-tech-discuss@lists.opnfv.org
>>>>> *Cc:* Julien <julien...@gmail.com>; Fatih Degirmenci <
>>>>> fatih.degirme...@ericsson.com>; Jose Lausuch <
>>>>> jose.laus...@ericsson.com>
>>>>> *Subject:* Re: [opnfv-tech-discuss] Multiple docker containers from
>>>>> one project
>>>>>
>>>>>
>>>>>
>>>>> Ideas:
>>>>>
>>>>>
>>>>>
>>>>>- Change the DOCKERFILE parameter in releng jjb so that it can
>>>>>accept a comma delimited list of Dockerfile names and paths.  Problem
>>>>>with this, of course, is how do I default it to be different for 
>>>>> StorPerf
>>>>>vs. Functest, etc?
>>>>>- Change the opnfv-docker.sh to search for the named DOCKERFILE in
>>>>>all subdirectories.  This should cover the .aarch64 and vanilla docker 
>>>>> file
>>>>>cases.
>>>>>
>>>>>
>>>>>
>>>>> Please +1/-1 or propose other ideas, thanks!
>>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> Mark
>>>>>
>>>>>
>>>>>
>>>>> *Mark Beierl*
>>>>>
>>>>> SW System Sr Principal Engineer
>>>>&

Re: [opnfv-tech-discuss] Multiple docker containers from one project

[Julien]

Hi Jose,

According to the current implementation, current script only support one
Dockerfile, my personal suggestion is:
1. list all the sub-directory which contains "Dockerfile"
2. build for each sub-directory fetched in #1
3. for the names, in the top directory using the project name, in the
sub-directory using: project_name-sub_directory_name
not too much changes for current script and easy for project to manage.

/Julien

Beierl, Mark <mark.bei...@dell.com>于2017年7月7日周五 下午11:35写道：

> Hello,
>
> Having looked over the docker-hub build service, I also think this might
> be the better approach.  Less code for us to maintain, and the merge job
> from OPNFV Jenkins can use the web hook to remotely trigger the job on
> docker-hub.
>
> Who has the opnfv credentials for docker-hub, and the credentials for the
> GitHub mirror that can set this up?  Is that the LF Helpdesk?
>
> Regards,
> Mark
>
> *Mark Beierl*
> SW System Sr Principal Engineer
> *Dell **EMC* | Office of the CTO
> mobile +1 613 314 8106 <1-613-314-8106>
> mark.bei...@dell.com
>
> On Jul 7, 2017, at 11:01, Xuan Jia <jason.jiax...@gmail.com> wrote:
>
> +1 Using build service from docker-hub
>
>
> On Thu, Jul 6, 2017 at 11:42 PM, Yujun Zhang (ZTE) <
> zhangyujun+...@gmail.com> wrote:
>
>> Does anybody consider using the build service from docker-hub[1] ?
>>
>> It supports multiple Dockerfile from same repository and easy to
>> integrate with OPNFV Github mirror.
>>
>> [1]: https://docs.docker.com/docker-hub/builds/
>>
>>
>> On Thu, Jul 6, 2017 at 11:02 PM Jose Lausuch <jose.laus...@ericsson.com>
>> wrote:
>>
>>> Hi Mark,
>>>
>>>
>>>
>>> I would incline for option 1), it sounds better than searching for a
>>> file. We could define specific values of DOCKERFILE var for each project.
>>>
>>>
>>>
>>> /Jose
>>>
>>>
>>>
>>>
>>>
>>> *From:* Beierl, Mark [mailto:mark.bei...@dell.com]
>>> *Sent:* Thursday, July 06, 2017 16:18 PM
>>> *To:* opnfv-tech-discuss@lists.opnfv.org
>>> *Cc:* Julien <julien...@gmail.com>; Fatih Degirmenci <
>>> fatih.degirme...@ericsson.com>; Jose Lausuch <jose.laus...@ericsson.com>
>>> *Subject:* Re: [opnfv-tech-discuss] Multiple docker containers from one
>>> project
>>>
>>>
>>>
>>> Ideas:
>>>
>>>
>>>
>>>- Change the DOCKERFILE parameter in releng jjb so that it can
>>>accept a comma delimited list of Dockerfile names and paths.  Problem
>>>with this, of course, is how do I default it to be different for StorPerf
>>>vs. Functest, etc?
>>>- Change the opnfv-docker.sh to search for the named DOCKERFILE in
>>>all subdirectories.  This should cover the .aarch64 and vanilla docker 
>>> file
>>>cases.
>>>
>>>
>>>
>>> Please +1/-1 or propose other ideas, thanks!
>>>
>>>
>>>
>>> Regards,
>>>
>>> Mark
>>>
>>>
>>>
>>> *Mark Beierl*
>>>
>>> SW System Sr Principal Engineer
>>>
>>> *Dell **EMC* | Office of the CTO
>>>
>>> mobile +1 613 314 8106 <1-613-314-8106>
>>>
>>> *mark.bei...@dell.com <mark.bei...@dell.com>*
>>>
>>>
>>>
>>> On Jun 24, 2017, at 04:05, Jose Lausuch <jose.laus...@ericsson.com>
>>> wrote:
>>>
>>>
>>>
>>> +1
>>>
>>>
>>>
>>> No need for an additional repo, the logic can be in Releng..
>>>
>>> Functest will probably move to different containers some time soon, so
>>> that is something we could also leverage.
>>>
>>>
>>>
>>> -Jose-
>>>
>>>
>>>
>>>
>>>
>>> On 23 Jun 2017, at 18:39, Julien <julien...@gmail.com> wrote:
>>>
>>>
>>>
>>> Agree,
>>>
>>>
>>>
>>> If StorPerf can list some rules and examples, current scripts can be
>>> adapted for multiple docker image building and other project can use this
>>> type of changes. It is not deserved to add a new repo just for build a new
>>> image.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Fatih Degirmenci <fatih.degirme...@ericsson.com>于2017年6月21日周三 上午2:26写道：
>>>
>>> Hi Mark,
>>>
>>>
>

Re: [opnfv-tech-discuss] multi-site next step ?

[Julien]

Maybe we'd better add a new scenario for multisite in OPNFV. In this
scenario installer will support requirements as you listed.
Currently all installers install everything from the very beginning
including keystone. If external keystone can be used as an internal
keystone's backend, it is easier for installers. I am not sure about this
configuration.


/Julien

joehuang <joehu...@huawei.com>于2017年6月24日周六 下午4:56写道：

> Hello, Faith,
>
> Thank you for the information.
>
> Except the Tricircle installation with OSA scripts, installer to support
> multi-site installation is also very important, either using shared
> KeyStone for multi-region deployment or KeyStone federation for multi-cloud
> deployment:
>
> 1. Each OpenStack instance can be installed with specified region name
> 2. the KeyStone endpoint used inside all services can be
> configured(KeyStone may be not in the same region), or federation configure
> could be configured.
> 3. Multiple OpenStack instances deployments.
> 4. compute nodes IP are routable if tunneling is expected to be
> established from compute node to compute node directly, or deploy L2
> gateway in each OpenStack instance if L2GW will be used instead, L2GW can
> be ping-able with each other. Tricircle also support SDN controller as
> backend in local Neutron, and offload the networking automation to SDN
> controller if SDN controller itself support cross site tenant networking.
>
> Best Regards
> Chaoyi Huang (joehuang)
> --
> *From:* Fatih Degirmenci [fatih.degirme...@ericsson.com]
> *Sent:* 23 June 2017 18:40
> *To:* joehuang
> *Cc:* valentin.bouc...@orange.com; opnfv-tech-discuss; BLAISONNEAU David
> IMT/OLN
> *Subject:* Re: [opnfv-tech-discuss] multi-site next step ?
>
> Hi Joe,
>
> As Valentin summarized, XCI uses OSA directly from upstream and deploys
> OpenStack from master so there is no dependency to OPNFV installers. All
> the features/scenarios are/will be implemented in upstream, getting part of
> the upstream.
>
> XCI provides sandbox for the developers to use to  integrate their
> features to upstream OSA. It is available for quite some time and used for
> adding support for ODL, Tacker, OVS NSH and enabling SFC. Sandbox lets you
> deploy OpenStack using VMs with number of different flavors. Baremetal also
> works and we will enable those jobs in OPNFV CI soon.
>
> The provisioning is done by bifrost (standalone ironic) which is an
> upstream project as well.
>
> We are also in the process of setting up 3rd Party CI for OSA which will
> provide feedback on the patches you and/or others might be proposing to
> upstream from OPNFV directly on OpenStack Gerrit.
>
> You can take a look at the documentation from below links and ask any
> questions you might have via mail or on #opnfv-pharos irc channel.
>
> https://wiki.opnfv.org/display/INF/OpenStack
> https://wiki.opnfv.org/display/INF/XCI+Developer+Sandbox
>
> /Fatih
>
> On 23 Jun 2017, at 09:28, joehuang <joehu...@huawei.com> wrote:
>
> Hi, Valentin,
>
> Good idea, would like to know how many installers support OSA(OpenStack
> Ansible), and contributors are needed :)
>
> Best Regards
> Chaoyi Huang (joehuang)
> --
> *From:* valentin.bouc...@orange.com [valentin.bouc...@orange.com]
> *Sent:* 22 June 2017 20:06
> *To:* joehuang; opnfv-tech-discuss
> *Cc:* BLAISONNEAU David IMT/OLN; Fatih Degirmenci
> *Subject:* RE:[opnfv-tech-discuss] multi-site next step ?
>
> Hello Chaoyi,
>
> It's great summary of all work in OPNFV and also in OpenStack Tricircle !
>
> For my part, I use Tricircle for the OPNFV demo, and I think the current
> fonctionnality is fine ! Of course, I found some bugs and now it's fixed.
>
> I think for the next step, It's more the integration and deployment of an
> OpenStack with Tricircle. Yes, it can be supported with OPNFV installer but
> I think the best way is to integrate that in OpenStack upstream installer
> like openstack-ansible. Tricircle is an OpenStack project so the
> integration in OSA make sense. In addition, some people in the community
> works on the integration of OSA in OPNFV (Fatih and Yolanda and several
> Suse guys on XCI and David Blaisonneau with OSA on baremetal). It would
> be cool to have a os-nosdn-multisite-ha scenario based on OSA!
>
> We can also deploy tricircle in real context, like Windriver guys aksing
> in the end of our session. 2 or more site with some latency between each
> site.
>
> Best regards,
> Valentin
> --
> *De :* opnfv-tech-discuss-boun...@lists.opnfv.org [
> opnfv-tech-discuss-boun...@lists.opnfv.org] de la part de joehuang [
> joehu...@huawei.com]
> *Envoyé 

Re: [opnfv-tech-discuss] [infra][releng] verify-status plugin for gerrit

[Julien]

Hi Luke,

For avoiding to import new plugins to the gerrit server, my team has
developed a local plugin for chrome, which can implement the same features
as Openstack Infra team does. We use the most of the code from Openstack
Infra.
This plugin is in link
https://chrome.google.com/webstore/detail/jenkins-jobs-show-in-gerr/mhdfkoddkdgcfmmhljfhekpadgmniagd.
It is open source also, please refer to:
https://github.com/openzero-team/toggle-ci . Wen juan is responsible for
the plugin development.

Currently, it can filter out the CI results, but job execution table does
not be shown in the gerrit main page. I think there are some different
configuration between Openstack and OPNFV gerrit system. If we want to get
better effect, I remember some configuration changes would be introduces in
gerrit.conig. It has supported in our local gerrit system. I just don't
remember the details and will give what's change tomorrow.

Aric, what's you opinion about this feature.

BR/Julien

Luke Hinds <lhi...@redhat.com>于2017年6月25日周日 下午7:01写道：

> Have we considered using the verify-status plugin for gerrit?
>
> I feel this may be a useful addition and will make it easier to visually
> separate user comments from ci-voting jobs.
>
> There is a screencapture on the following documentation link that shows
> the difference that it makes.
>
>
> https://gerrit.googlesource.com/plugins/verify-status/+doc/master/src/main/resources/Documentation/about.md
>
> --
> Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
> e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44
> 12 52 36 2483
> ___
> 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] Multiple docker containers from one project

[Julien]

Agree,

If StorPerf can list some rules and examples, current scripts can be
adapted for multiple docker image building and other project can use this
type of changes. It is not deserved to add a new repo just for build a new
image.



Fatih Degirmenci 于2017年6月21日周三 上午2:26写道：

> Hi Mark,
>
> It is perfectly fine to have different build processes and/or number of
> artifacts for the projects from releng point of view.
>
> Once you decide what to do for storperf, we can take a look and adapt
> docker build job/script to build storperf images, create additional repos
> on docker hub to push images and activate the builds when things are ready.
>
> /Fatih
>
> On 20 Jun 2017, at 19:18, Beierl, Mark  wrote:
>
> Hello,
>
> I'd like to poll the various groups about ideas for how to handle this
> scenario.  I have interns working on breaking down services from StorPerf
> into different containers.  In one case, it will be a simple docker compose
> that is used to fire up existing containers from the repos, but the other
> case requires more thought.
>
> We are creating a second container (storperf-reporting) that will need to
> be built and pushed to hub.docker.com.  Right now the build process for
> docker images lives in releng, and it only allows for one image to be
> built.  Should I be requesting a second git repo in this case, or should we
> look at changing the releng process to allow multiple docker images to be
> build?
>
> Regards,
> Mark
>
> *Mark Beierl*
> SW System Sr Principal Engineer
> *Dell **EMC* | Office of the CTO
> mobile +1 613 314 8106 <1-613-314-8106>
> mark.bei...@dell.com
>
> ___
> 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 mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [opnfv-tsc] New meeting time for the TSC call

[Julien]

Thanks all of you for this type of update.



于2017年6月22日周四 下午5:07写道：

> +1/+1
> same position than Dave
>
> Morgan
>
> On 22/06/2017 10:36, Dave Neary wrote:
> > +1 for time change. I am fortunate to be in a time zone where it does
> > not affect me much.
> >
> > Also +1 for cancelling July 4 meeting.
> >
> > Thanks,
> > Dave.
> >
> > On 06/22/2017 03:39 PM, Frank Brockners (fbrockne) wrote:
> >>
> >>
> >> +1 for the move to 6am PT
> >>
> >> +1 for canceling the call on Jul/4^th – unless we have a pressing item
> >> on the agenda (i.e. this assumes that we have D3.0 released by then –
> >> otherwise we might want to consider keeping the call).
> >>
> >>
> >>
> >> Frank
> >>
> >>
> >>
> >> *From:*opnfv-tsc-boun...@lists.opnfv.org
> >> [mailto:opnfv-tsc-boun...@lists.opnfv.org] *On Behalf Of *Raymond Paik
> >> *Sent:* Mittwoch, 21. Juni 2017 07:03
> >> *To:* opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org
> >> *Subject:* [opnfv-tsc] New meeting time for the TSC call
> >>
> >>
> >>
> >> All,
> >>
> >>
> >>
> >> As discussed on the TSC call today, I'd like to propose changing the TSC
> >> meeting time to 6am Pacific Time.  This would make it slightly easier
> >> for community members in Asia to join the weekly call.  Obviously, an
> >> earlier start will make things a little painful for people in Pacific
> >> Timezone (myself included).  However, there were no objections from west
> >> coasters when I asked people a few months ago.
> >>
> >>
> >>
> >> This change won't take effect right away, but we could start in
> >> mid-July.  I need to thank the Doctor team for agreeing to move their
> >> weekly meeting to make this possible.   If you have any major
> >> concerns/objections about the proposed change, please let me know by the
> >> end of this week (23rd).
> >>
> >>
> >>
> >> Speaking of July, the first Tuesday in July is the Independence Day
> >> holiday in the US and many folks here in the US will be on Holiday that
> >> week.  Is everyone OK with canceling the TSC call in the first week of
> July?
> >>
> >>
> >>
> >> 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
> 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] [opnfv-tsc] Vote for the new Danube 3.0 release date

[Julien]

+1

Dave Neary 于2017年6月10日周六 上午3:02写道：

> +1
>
> Dave.
>
> On 06/07/2017 09:04 PM, Raymond Paik wrote:
> > TSC members,
> >
> > Apologies for a little delay on this.
> >
> > As David communicated
> > 
> > yesterday, he is recommending postponing the Danube 3.0 release date to
> > June 23rd (2-week delay) as community members experienced technical
> > issues over the weekend.
> >
> > I'd like to start an email vote among the TSC members on the following:
> >
> > "Does the TSC approve changing the Danube 3.0 release date to June 23,
> > 2017?  (+1, 0, -1)"
> >
> > Could you send me your vote by 6pm Pacific Time on June 8th (Thursday)?
> >
> > Thanks,
> >
> > Ray
> >
> >
> > ___
> > opnfv-tsc mailing list
> > opnfv-...@lists.opnfv.org
> > https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
> >
>
> --
> Dave Neary - NFV/SDN Community Strategy
> Open Source and Standards, Red Hat - http://community.redhat.com
> Ph: +1-978-399-2182 <+1%20978-399-2182> / Cell: +1-978-799-3338
> <+1%20978-799-3338>
> ___
> 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 heterogeneous build practice discussions at the developer event in beijing

[Julien]

Hi Chris,

Good idea, and I will attend the discussion then. Is this topic relevant
with Lab as a service?

Regards,
Julien


Christopher Price <christopher.pr...@ericsson.com>于2017年5月17日周三 下午4:52写道：

> Hi Pharos project,
>
>
>
> I have proposed a “birds of a feather” session on the Monday design summit
> at 14:30 to discuss a topic related to Pharos - Infrastructure build
> practices; scale up, constrained and on premise devices.
>
>
>
> I’d like to start dialogs around how we can approach evaluating and
> documenting additional build practices in NFV environments from scaling up
> beyond the minimum Pharos POD, to small form CO equipment, to residential
> on-premise devices.
>
>
>
> The idea is not to resolve these topics during the session, more to
> identify how to structure dialogs and contributions to OPNFV when we want
> to investigate and align on these physical forms.  Please try to make the
> time to come along if you can, it is scheduled for the time-slot after the
> OPNFV Infra Discussions topic.  It may be the “OPNFV Infra Discussions”
> topic is the right place to discuss these topics, if that is the right
> approach I would be happy to have this topic called out explicitly in one
> of those time-slots rather than as a separate topic.  (not fussed either
> way, I thought a BoF would be an easy way to incubate a dialog.)
>
>
>
> / Chris
>
>
>
>
>
>
> ___
> 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] [release][danube] OPNFV Danube 2.0 has been released

[Julien]

Hi Ray,

I just give one of these links,  and there are many records about this. I
don't remember the exact record about this for discussed years ago.

In our CI system, we use source code or ISO to deploy the environment from
installer and then perform the tests. I don't think there are changes for
this since brahmaputra. I don't know RPM method is covered by CI either.

Regards,
Julien



Raymond Paik <rp...@linuxfoundation.org>于2017年5月9日周二 下午12:13写道：

> Julien,
>
> Based on the minutes, it says Arno will support iso and script based
> deployment, but too early to decide on packaging options for future
> releases (incl. Brahmaputra).
>
> I'm not sure if I understand your concerns on RPMs from Apex.  Could you
> elaborate further?
>
> Thanks,
>
> Ray
>
> On Mon, May 8, 2017 at 4:03 PM, Julien <julien...@gmail.com> wrote:
>
>> Hi David,
>>
>> This issue has been discussed in the TSC meeting. I don't know this
>> conclusion about *"Packaging is a community decision made by the
>> installer teams and the dependent scenario owners and project teams"* is
>> approved by TSC. I just remember ISO and source code are two alternatives.
>> *"In particular, RPM is standard for Red Hat OSs"*
>> If it is RHEL, it is licensed and not suitable. In OPNFV, we only use
>> community version, ie. CentOS. If we release RPMs in Cent OS, shall we
>> release deb packages for Ubuntu OS?
>>
>> I'm sorry that I can not go to openstack summit.
>>
>> There are some records in TSC meeting such as July 14th, 2015, and
>> original link is:
>> http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-07-14-14.00.html
>> .
>>
>> Regards,
>> Julien
>>
>> David McBride <dmcbr...@linuxfoundation.org>于2017年5月8日周一 下午11:38写道：
>>
>>> Hi Julien,
>>>
>>> "Apex" is the project name for TripleO in OPNFV.  However, "TripleO" is
>>> the name of the installer.  Also, "TripleO" is well known outside of OPNFV,
>>> whereas "Apex" is unique to OPNFV.
>>>
>>> Packaging is a community decision made by the installer teams and the
>>> dependent scenario owners and project teams.  So far, I've never heard any
>>> complaints from members or end users about packaging.  However, this topic
>>> might be worth bringing up at the EUAG in case there are some issues that
>>> I'm unaware of.
>>>
>>> I think that having packaging for each installer that is appropriate and
>>> has community/user consensus is more important than forcing the same
>>> packaging across all installers (i.e. "consistency is the hobgoblin of
>>> little minds").  In particular, RPM is standard for Red Hat OSs, therefore,
>>> it makes sense that TripleO would be released on RPM.
>>>
>>> If you are at OpenStack this week, I'd be happy to discuss this with you
>>> further F2F.
>>>
>>> David
>>>
>>> On Sat, May 6, 2017 at 4:37 AM, Julien <julien...@gmail.com> wrote:
>>>
>>>> Hi David,
>>>>
>>>> In our installer projects, there are Apex, Compass, Fuel, and Juju
>>>> released in Danube. I wonder why use the name TripleO instead of Apex?
>>>>
>>>> I have discussed at Arno and Brahmaputra about how to release OPNFV
>>>> artifacts, and the conclusion is in ISO or source codes. Why release RPMs
>>>> for Apex? It is different from other installers. The release content or
>>>> list are different in OPNV download page. It is really strange.
>>>>
>>>> BR,
>>>> Julien
>>>>
>>>>
>>>> David McBride <dmcbr...@linuxfoundation.org>于2017年5月6日周六 上午5:20写道：
>>>>
>>>>> TSC members,
>>>>>
>>>>> I'm pleased to let you know that OPNFV Danube 2.0 has been released.
>>>>> Software and documentation may be accessed here
>>>>> <https://www.opnfv.org/software/downloads>.
>>>>>
>>>>> Congratulations to everyone in the community that worked hard to make
>>>>> this happen.  Please let me know if you have questions or comments.
>>>>>
>>>>> David
>>>>>
>>>>> --
>>>>> *David McBride*
>>>>> Release Manager, OPNFV
>>>>> Mobile: +1.805.276.8018
>>>>> Email/Google Talk: dmcbr...@linuxfoundation.org
>>>>> Skype: davidjmcbride1
>>>>> IRC: dmcbride
>>>>> ___
>>>>> opnfv-tech-discuss mailing list
>>>>> opnfv-tech-discuss@lists.opnfv.org
>>>>> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>>>>>
>>>>
>>>
>>>
>>> --
>>> *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] [release][danube] OPNFV Danube 2.0 has been released

[Julien]

Hi David,

This issue has been discussed in the TSC meeting. I don't know this
conclusion about *"Packaging is a community decision made by the installer
teams and the dependent scenario owners and project teams"* is approved by
TSC. I just remember ISO and source code are two alternatives.
*"In particular, RPM is standard for Red Hat OSs"*
If it is RHEL, it is licensed and not suitable. In OPNFV, we only use
community version, ie. CentOS. If we release RPMs in Cent OS, shall we
release deb packages for Ubuntu OS?

I'm sorry that I can not go to openstack summit.

There are some records in TSC meeting such as July 14th, 2015, and original
link is:
http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-07-14-14.00.html
.

Regards,
Julien

David McBride <dmcbr...@linuxfoundation.org>于2017年5月8日周一 下午11:38写道：

> Hi Julien,
>
> "Apex" is the project name for TripleO in OPNFV.  However, "TripleO" is
> the name of the installer.  Also, "TripleO" is well known outside of OPNFV,
> whereas "Apex" is unique to OPNFV.
>
> Packaging is a community decision made by the installer teams and the
> dependent scenario owners and project teams.  So far, I've never heard any
> complaints from members or end users about packaging.  However, this topic
> might be worth bringing up at the EUAG in case there are some issues that
> I'm unaware of.
>
> I think that having packaging for each installer that is appropriate and
> has community/user consensus is more important than forcing the same
> packaging across all installers (i.e. "consistency is the hobgoblin of
> little minds").  In particular, RPM is standard for Red Hat OSs, therefore,
> it makes sense that TripleO would be released on RPM.
>
> If you are at OpenStack this week, I'd be happy to discuss this with you
> further F2F.
>
> David
>
> On Sat, May 6, 2017 at 4:37 AM, Julien <julien...@gmail.com> wrote:
>
>> Hi David,
>>
>> In our installer projects, there are Apex, Compass, Fuel, and Juju
>> released in Danube. I wonder why use the name TripleO instead of Apex?
>>
>> I have discussed at Arno and Brahmaputra about how to release OPNFV
>> artifacts, and the conclusion is in ISO or source codes. Why release RPMs
>> for Apex? It is different from other installers. The release content or
>> list are different in OPNV download page. It is really strange.
>>
>> BR,
>> Julien
>>
>>
>> David McBride <dmcbr...@linuxfoundation.org>于2017年5月6日周六 上午5:20写道：
>>
>>> TSC members,
>>>
>>> I'm pleased to let you know that OPNFV Danube 2.0 has been released.
>>> Software and documentation may be accessed here
>>> <https://www.opnfv.org/software/downloads>.
>>>
>>> Congratulations to everyone in the community that worked hard to make
>>> this happen.  Please let me know if you have questions or comments.
>>>
>>> David
>>>
>>> --
>>> *David McBride*
>>> Release Manager, OPNFV
>>> Mobile: +1.805.276.8018
>>> Email/Google Talk: dmcbr...@linuxfoundation.org
>>> Skype: davidjmcbride1
>>> IRC: dmcbride
>>> ___
>>> opnfv-tech-discuss mailing list
>>> opnfv-tech-discuss@lists.opnfv.org
>>> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>>>
>>
>
>
> --
> *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-security] [Infra][Pharos][Releng][Octopus][Security] Infra Working Group Meeting

[Julien]

Hi Team,

I have finished the migration of stackalytics.com for OPNFV:
* using review data from gerrit.opnfv.org
* using the release cycles(such as arno, brahmaputra, etc) of OPNFV instead
of Openstack
* fix double commits log of opnfvdocs
* not necessary to add project repo in config file when using gerrit server

If you have interests, I can have a demo in the next meeting. Currently
stackalytics.com can support **only one ** gerrit server(that's
review.openstack.org). Many codes are affected if more gerrit servers will
be supported. The most affected issue is that **no other release cycles**
besides openstack itself can be supported in the code, and this affects the
foundation of the project. Bitegia(https://opnfv.biterg.io) only provides
the raw data, and not efficient for usage. There are also some miss-counts
in the bitegia.

If the community can hold the service, it will be better.

Regards,
Julien


Ulrich Kleber <ulrich.kle...@huawei.com>于2017年5月3日周三 下午10:24写道：

> When: Occurs every Monday effective 08-May-17 until 26-Jun-17 from 17:00
> to 18:00 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna.
> Where: GTM 819733085 and IRC #opnfv-meeting
>
> Note: The GMT offset above does not reflect daylight saving time
> adjustments.
>
> *~*~*~*~*~*~*~*~*~*
>
> The "Infra Working Group" plans and tracks *infrastructure cross project
> initiatives.*
> We report our efforts up to the TSC to ensure the community is able to
> provide sufficient resources for development and release infrastructure.
> *Topics and meeting agenda at*
> *https://wiki.opnfv.org/display/INF/Infra+Working+Group*
> <https://wiki.opnfv.org/display/INF/Infra+Working+Group>
> *Minutes at* *Infra Working Group Meeting*
> <https://wiki.opnfv.org/display/meetings/Infra+Working+Group+Meeting>
>
>- Weekly on *Monday* at *8:00 PST* or *15:00 UTC (during US daylight
>saving)*
>- GTM Link *https://global.gotomeeting.com/join/819733085*
><https://global.gotomeeting.com/join/819733085>
>- IRC #opnfv-meeting - *freenode.net* <http://freenode.net/>
>- Chaired by *Ulrich Kleber* (meetings chaired by Infra PTLs on a
>2-month basis)
>- You can also dial in using your phone with Access Code: 819-733-085
>
>
>- United States +1 (312) 757-3126 <+1%20312-757-3126>
>- Australia +61 2 8355 1040 <+61%202%208355%201040>
>- Austria +43 7 2088 0034
>- Belgium +32 (0) 28 93 7018
>- Canada +1 (647) 497-9350 <+1%20647-497-9350>
>- Denmark +45 69 91 88 64 <+45%2069%2091%2088%2064>
>- Finland +358 (0) 923 17 0568
>- France +33 (0) 170 950 592
>- Germany +49 (0) 692 5736 7211 <+49%2069%20257367211>
>- Ireland +353 (0) 15 360 728
>- Italy +39 0 247 92 13 01
>- Netherlands +31 (0) 208 080 219
>- New Zealand +64 9 280 6302 <+64%209-280%206302>
>- Norway +47 75 80 32 07 <+47%2075%2080%2032%2007>
>- Spain +34 911 82 9906 <+34%20911%2082%2099%2006>
>- Sweden +46 (0) 853 527 836
>- Switzerland +41 (0) 435 0167 13
>- United Kingdom +44 (0) 330 221 0086 <+44%20330%20221%200086>
>
>
>
> ___
> opnfv-security mailing list
> opnfv-secur...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-security
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] On Stress Test Demo//RE: [test-wg] Notes from OPNFV Plugfest meeting - "Testing group Euphrates collaborative work"

[Julien]

Hi,

That's why I send this email. it has no voice, so it is not easy for me to
understand this demo.
I don't know what is on going.

Regards,
Julien

Yuyang (Gabriel) <gabriel.yuy...@huawei.com>于2017年5月7日周日 下午2:26写道：

> Hi Julien,
>
>
> I dont find any voice here. Could you help point out where the voice 
> appears，so we could look into it?
>
> Thanks in advance!
> Gabriel
>
>
> Sent from HUAWEI AnyOffice
> *发件人： *Julien
> *收件人： *于洋; Alec Hothan (ahothan); morgan.richo...@orange.com; Cooper,
> Trevor; opnfv-tech-discuss; test...@lists.opnfv.org;
> *主题： *Re: [opnfv-tech-discuss] On Stress Test Demo//RE: [test-wg] Notes
> from OPNFV Plugfest meeting - "Testing group Euphrates collaborative work"
> *时间： *2017-05-06 16:27:03
>
>
> Hi Yuyang,
>
> The video in youtube has voice? Is it correct?
>
> Julien
>
>
> Yuyang (Gabriel) <gabriel.yuy...@huawei.com>于2017年5月5日周五 下午3:07写道：
>
>> Hi Alec,
>>
>>
>>
>> Please see my answers inline!
>>
>>
>>
>> Thanks!
>>
>> Gabriel
>>
>>
>>
>> *From:* Alec Hothan (ahothan) [mailto:ahot...@cisco.com]
>> *Sent:* Friday, May 05, 2017 11:11 AM
>> *To:* Yuyang (Gabriel); morgan.richo...@orange.com; Cooper, Trevor;
>> opnfv-tech-discuss@lists.opnfv.org; test...@lists.opnfv.org
>> *Subject:* Re: [opnfv-tech-discuss] On Stress Test Demo//RE: [test-wg]
>> Notes from OPNFV Plugfest meeting - "Testing group Euphrates collaborative
>> work"
>>
>>
>>
>> Hi Gabriel,
>>
>>
>>
>> Regarding TC1, do you have the results and original chart available
>> somewhere (the chart in the picture and in the slides is kind of small).
>>
>> Gabriel: We do not have the original results and chart now since this is
>> one time result that we have when we do local test. We have discussed the
>> results plotting within Testperf.
>>
>> The test results will be shown in the community ELK maintained by
>> bitergia in Q2.
>>
>> Some results could be found in the community CI, e.g.,
>> https://build.opnfv.org/ci/view/bottlenecks/job/bottlenecks-compass-posca_stress_traffic-baremetal-daily-danube/5/console
>>
>>
>>
>> Do you also have a detailed description of the test:
>>
>> Gabriel: I assume you ask detailed about TC3 here, since we only run TC1
>> on vPOD or bare mental POD.
>>
>> · what kind of packet gen you are running in the first VM and
>> what kind of forwarder you are running in the second VM
>>
>> Gabriel: For TC3, we use netperf to send packet and retransmit it in the
>> second VM.
>>
>> · what flavor
>>
>> Gabriel: Bottlenecks calls yardstick to do each test, the flavor is
>> specified in Yardstick, i.e., yardstick-flavor: nova flavor-create
>> yardstick-flavor 100 512 3 1.
>>
>> · what vswitch was used
>>
>> Gabriel: OVS is used. If you have any recommendation, please also inform
>> us :)
>>
>> · how are the VMs placed (wrt compute node, numa node)
>>
>> Gabriel: VMs are created by using heat client without specifying how and
>> where to place them
>>
>> · I assume the test will ramp up the number of VM pairs, if so
>> how do you synchronize your VM starts/measurements (VMs don’t tend to all
>> start the test at the same time due to the latency for bringing up
>> individual VMs)
>>
>> Gabriel: Yes, the VMs will not start to ping simultaneously. We
>> can only simultaneously sent the request to create all the VMs, waiting for
>> the creation and then to the ping operation.
>>
>> · How do you track drop rate and latency across VM pairs
>>
>> Gabriel: I assume you mean the packet drop rate and latency here. For
>> these metrics, we use netperf to do the monitoring
>>
>>
>>
>> Gabriel: you could also do the test locally. For more information, please
>> refer to the link below.
>>
>> *Bottlenecks Testing Guide:*
>> http://docs.opnfv.org/en/stable-danube/submodules/bottlenecks/docs/testing/developer/devguide/posca_guide.html
>>
>>
>>
>>
>>
>>
>>
>> Thanks!
>>
>>
>>
>>   Alec
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From: *<opnfv-tech-discuss-boun...@lists.opnfv.org> on behalf of
>> "Yuyang (Gabriel)" <gabriel.yuy...@huawei.com>
>> *Date: *Thursday, May 4, 2017 at 7:48 PM
>> *To: *"morgan.richo...@orange.com" 

Re: [opnfv-tech-discuss] [Infra][Pharos] About pharos wiki pages

[Julien]

That's fine!

I am also interested in how ReadTheDocs can support for each project
besides the normal release docs of OPNFV.


Jack Morgan <jack.mor...@intel.com>于2017年4月27日周四 下午8:55写道：

> Julien,
>
> We had some discussion about moving community labs documentation into
> ReadTheDocs in the near future while at Plugfest. Let's discuss at a future
> Infra WG meeting. Hopefully, this will fix our issues we have with
> documenting community labs in the wiki.
>
> On 04/10/2017 12:14 AM, Julien wrote:
>
> Hi,
>
> In our early Infra WG meeting, we discussed to include the content of
> Pharos documents in wiki.opnfv.org to avoid duplicated contents, and it
> works. While I find all the images in the included page are missing. For
> example, in page https://wiki.opnfv.org/display/pharos/ZTE+SH+Testlab,
> which includes page content from
> http://artifacts.opnfv.org/pharos/colorado/docs/labs_zte-sh-lab-single/index.html,
> all the PODs' topology pictures are missing. Inspecting this page I find
> that it use a relative file path "_images/zte_sh_lab_topology.png" which
> does not exist in wiki.opnfv.org.
>
> When I try to use another html macro "*html include replace*" and set the
> container to "iframe", it turns out "html-include-replace license
> problem: EXPIRED". I wonder this plugin is limited or actually expired.
>
> any idea to help to resolve current issue is welcome.
>
>
> --
> Jack Morgan
> OPNFV Pharos Intel Lab
>
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Danube release community awards

[Julien]

Hi Ray,

I would like to nominate Yujun Zhang(zhang.yuj...@zte.com.cn) for the award
of "code development". He has make a great achievement in Danube release.
His contribution is listed in the top 3[1].

I also want to nominate him for award of "Community support/leadership". He
leads QTIP project to release normally after absent in Colorado. He manage
to re-active the project to avoid to be archived in the community. He also
leads the cooperation with Doctor project in OPNFV and Vitrage project in
Openstack.

data list:
- [1]:
http://stackalytics.com/?project_type=opnfv-group=commits=ocata


Raymond Paik 于2017年4月11日周二 上午12:08写道：

> All,
>
> I'm kicking off the nomination period for the Community Awards following
> the Danube release.  As announced in February, 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)
>
> If you're interested in nominating community members for any of the
> categories above, could you send them to me by 5pm Pacific Time on May 17th
> (Monday)?
>
> I'll be sending out a SurveyMonkey link for voting to opnfv-tech-discuss
> on May 19th.
>
> Thanks,
>
> Ray
> ___
> 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] [Infra][Pharos] About pharos wiki pages

[Julien]

Hi,

In our early Infra WG meeting, we discussed to include the content of
Pharos documents in wiki.opnfv.org to avoid duplicated contents, and it
works. While I find all the images in the included page are missing. For
example, in page https://wiki.opnfv.org/display/pharos/ZTE+SH+Testlab,
which includes page content from
http://artifacts.opnfv.org/pharos/colorado/docs/labs_zte-sh-lab-single/index.html,
all the PODs' topology pictures are missing. Inspecting this page I find
that it use a relative file path "_images/zte_sh_lab_topology.png" which
does not exist in wiki.opnfv.org.

When I try to use another html macro "*html include replace*" and set the
container to "iframe", it turns out "html-include-replace license problem:
EXPIRED". I wonder this plugin is limited or actually expired.

any idea to help to resolve current issue is welcome.

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

Re: [opnfv-tech-discuss] VNF to demonstrate VNF high availability across VIM

[Julien]

Hi Joehuang,

I'm working for ZTE. During the demo, it is shining if we can demo some
VNFs in SampleVNF project on multi-site environment.
This solution will attract VNF vendors to adopt.

Are these works finished in OPNFV or Upstream Openstack project?

BR,
Julien

joehuang <joehu...@huawei.com>于2017年4月1日周六 上午9:01写道：

> Hello, Julien,
>
> Welcome to join the PoC demo in OPNFV Beijing Summit, Do you have some
> application to be deployed in the multi-site environment? And may I know
> which company you are working for, so that we can list you in the PoC demo.
>
> Best Regards
> Chaoyi Huang (joehuang)
> ------
> *From:* Julien [julien...@gmail.com]
>
> *Sent:* 31 March 2017 18:51
> *To:* joehuang; opnfv-tech-discuss; victor.mora...@intel.com; Meimei
> *Subject:* Re: [opnfv-tech-discuss] VNF to demonstrate VNF high
> availability across VIM
> Hi Joehuang,
>
> Thanks for clarification this use case. It is actually very cool and I
> expect to attend the demo in the summit.
>
> BR,
> Julien
>
>
> joehuang <joehu...@huawei.com>于2017年3月30日周四 下午3:11写道：
>
> Hello, Julien,
>
> Both should works, you can make one VNF being deployed into two OpenStack
> instances, or make two VNFs work in load-balancing mode.
>
> Currently Tricircle support associating one VIP in two OpenStack instances
> (through allowed address pair), it's up to VNFs how to make use of the
> enabling networking capabilities by Tricircle.
>
> Best Regards
> Chaoyi Huang (joehuang)
> --
> *From:* Julien [julien...@gmail.com]
> *Sent:* 30 March 2017 14:58
> *To:* joehuang; opnfv-tech-discuss; victor.mora...@intel.com; Meimei
> *Subject:* Re: [opnfv-tech-discuss] VNF to demonstrate VNF high
> availability across VIM
>
> Hi Joehuang,
>
> It's amazing.
>
> According to the content "*show how a VNF can run in 2 OpenStack
> instances*" and the link
> https://git.opnfv.org/multisite/tree/docs/requirements/VNF_high_availability_across_VIM.rst.
> I'm not sure that it is one VNF or two VNFs(active VNF + standby VNF) in
> the Demo.
>
> If it is one VNF, is it possible:
> 1. Some VMs in active mode are in openstack1, and other VMs in active mode
> are in openstack2;
> 2. Can VMs working in load balance mode across openstack1 and openstack2?
>
>
> BR,
> Julien
>
>
> joehuang <joehu...@huawei.com>于2017年3月16日周四 上午10:44写道：
>
> Hello,
>
> In multisite, we have one use cases ever discussed:
>
> a VNF (telecom application) should, be able to realize high availability 
> deployment across
> OpenStack instances.
>
> For more detail of such an use cases, you can refer to
> https://git.opnfv.org/multisite/tree/docs/requirements/VNF_high_availability_across_VIM.rst
>
>
> Now, it's time to bring it into reality.
>
> After Tricircle provides cross OpenStack L2/L3 networking automation
> capability based on VxLAN, we'd like to have a demo in OPNFV Beijing
> summit to show how a VNF can run in 2 OpenStack instances and achieve high
> availability regardless how much nine, planned or unplanned downtime of
> an OpenStack cloud would be.
>
> The VNF will work in cluster, active/active or active/standby mode, and it
> was deployed into two OpenStack instances, overlay VxLAN network will
> provide network plane for session/or other data replication between VNF
> parts, and also provide the VIP for VNF to provide service, if the VNF is
> running in active/standby, the standby VNF can take over the VIP and
> continue to provide service after the master or the openstack cloud is
> failed.
>
> If you are interested in such an use case, please join us, help would be
> appreciated:
>
> 1. Provide or integrate sample VNF which is able to be deployed into
> multiple OpenStack instances to reach cloud level redundancy/failure escape.
> 2. Joint demo in Beijing OPNFV summit.
> 3. Build multi-site general infrastructure in E-release for
> CI/Functest/3rd party service, to provide general multi-region
> environment for services like Tricircle/Kingbird/Domino/Tacker which deal
> with multi-region functionalities.
>
>
> Best Regards
> Chaoyi Huang (joehuang)
> ___
> 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] [Parser]PTL non-candidacy for E release

[Julien]

Hi Howard,

You have done a great job as the Parser PTL and lead the team to achieve
great success. The assets in our project not only includes commits in
project, technique documents revised, but also a cooperative team built
from the world and governance agreed.

We have been working together from the creation of the project and I
witness Howard contributes much more than he stated in the email. He helped
the team to communicate with each other and expand the use cases in
community and upstream, etc.

Thanks for all your contribution for Parser project! You have set a good
example for the team.

I also want to nominate Shang xiaodong for the next PTL. He has been the
most active committer in recent two versions in Parser. He introduce more
features for Tosca template, with which a telecom VNF can be deployed with
the Parser, he is also active in the relevant upstream openstack projects
and OASIS group for the project evolution. He is also working on API
gateway to integrate all the submodules in Parser.

BR,
Julien



Zhipeng Huang <zhipengh...@gmail.com>于2017年3月30日周四 下午3:35写道：

> Hi Team,
>
> I've just finished the tagging for danube.1.0 on Parser repo, and I want
> to inform you about my decision on the project leadership.
>
> It has been my honor to serve as the caretaking PTL for Parser since the
> very beginning of the project. With the help of all our contributors and
> committers alike, Parser has grown from a simple integration project that
> provide a simple translation functionality, to a full fledged project that
> has provided various functionalities on template translation as well as
> pre-validation.
>
> I still remembered how we add the yang2tosca in B release, how we have
> folks from Domino to help on the policy2tosca in C release, and how we have
> the wonderful verigraph team from Itlay Durin Polytech to come onboard and
> a new microservice gateway designed for D release.
>
> Aside of the technical works, we also have laid grounds for our project
> governance structure. We are among very few projects that actually have a
> governance document that describe how we want to promote a contributor to a
> committer role.
>
> It has been an amazing journey for me, both personally and technically. I
> hope these past two years I have contributed as I thought I would to the
> project that help Parser to grow as all other team members wanted. However
> as a firm believer of custom and tradition (and common law system in large
> :P), and also taking into account that I have been occupied with too many
> other tasks that prevent me from fully engaging in Parser's work, I think 2
> years would be enough for a caretaking PTL to serve, and that is why I
> decide to step down from PTL position starting E release. It is time for a
> new leadership to shepherd the team.
>
> I'm confident that whoever the next PTL might be would do a better and
> greater job than I could. I'm hereby calling for the election for the next
> PTL, and hope that our current committers are willing to nominate
> themselves.
>
> At the mean time before the new PTL is elected, I will serve as the
> interim lead and handle all the necessary matters.
>
> Thank you very much and best wishes.
>
> --
> Zhipeng (Howard) Huang
>
> Standard Engineer
> IT Standard & Patent/IT Prooduct Line
> Huawei Technologies Co,. Ltd
> Email: huangzhip...@huawei.com
> Office: Huawei Industrial Base, Longgang, Shenzhen
>
> (Previous)
> Research Assistant
> Mobile Ad-Hoc Network Lab, Calit2
> University of California, Irvine
> Email: zhipe...@uci.edu
> Office: Calit2 Building Room 2402
>
> OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
> ___
> 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] VNF to demonstrate VNF high availability across VIM

[Julien]

Hi Joehuang,

Thanks for clarification this use case. It is actually very cool and I
expect to attend the demo in the summit.

BR,
Julien


joehuang <joehu...@huawei.com>于2017年3月30日周四 下午3:11写道：

> Hello, Julien,
>
> Both should works, you can make one VNF being deployed into two OpenStack
> instances, or make two VNFs work in load-balancing mode.
>
> Currently Tricircle support associating one VIP in two OpenStack instances
> (through allowed address pair), it's up to VNFs how to make use of the
> enabling networking capabilities by Tricircle.
>
> Best Regards
> Chaoyi Huang (joehuang)
> ------
> *From:* Julien [julien...@gmail.com]
> *Sent:* 30 March 2017 14:58
> *To:* joehuang; opnfv-tech-discuss; victor.mora...@intel.com; Meimei
> *Subject:* Re: [opnfv-tech-discuss] VNF to demonstrate VNF high
> availability across VIM
>
> Hi Joehuang,
>
> It's amazing.
>
> According to the content "*show how a VNF can run in 2 OpenStack
> instances*" and the link
> https://git.opnfv.org/multisite/tree/docs/requirements/VNF_high_availability_across_VIM.rst.
> I'm not sure that it is one VNF or two VNFs(active VNF + standby VNF) in
> the Demo.
>
> If it is one VNF, is it possible:
> 1. Some VMs in active mode are in openstack1, and other VMs in active mode
> are in openstack2;
> 2. Can VMs working in load balance mode across openstack1 and openstack2?
>
>
> BR,
> Julien
>
>
> joehuang <joehu...@huawei.com>于2017年3月16日周四 上午10:44写道：
>
> Hello,
>
> In multisite, we have one use cases ever discussed:
>
> a VNF (telecom application) should, be able to realize high availability 
> deployment across
> OpenStack instances.
>
> For more detail of such an use cases, you can refer to
> https://git.opnfv.org/multisite/tree/docs/requirements/VNF_high_availability_across_VIM.rst
>
>
> Now, it's time to bring it into reality.
>
> After Tricircle provides cross OpenStack L2/L3 networking automation
> capability based on VxLAN, we'd like to have a demo in OPNFV Beijing
> summit to show how a VNF can run in 2 OpenStack instances and achieve high
> availability regardless how much nine, planned or unplanned downtime of
> an OpenStack cloud would be.
>
> The VNF will work in cluster, active/active or active/standby mode, and it
> was deployed into two OpenStack instances, overlay VxLAN network will
> provide network plane for session/or other data replication between VNF
> parts, and also provide the VIP for VNF to provide service, if the VNF is
> running in active/standby, the standby VNF can take over the VIP and
> continue to provide service after the master or the openstack cloud is
> failed.
>
> If you are interested in such an use case, please join us, help would be
> appreciated:
>
> 1. Provide or integrate sample VNF which is able to be deployed into
> multiple OpenStack instances to reach cloud level redundancy/failure escape.
> 2. Joint demo in Beijing OPNFV summit.
> 3. Build multi-site general infrastructure in E-release for
> CI/Functest/3rd party service, to provide general multi-region
> environment for services like Tricircle/Kingbird/Domino/Tacker which deal
> with multi-region functionalities.
>
>
> Best Regards
> Chaoyi Huang (joehuang)
> ___
> 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] [opnfvdocs] About docs CI jobs

[Julien]

Hi Sofia,

"number of executors" can be increased in Jenkins master. If it is
required, we can seek help from Aric.

Thanks,
Julien

Sofia Wallin <sofia.wal...@ericsson.com>于2017年3月14日周二 下午6:46写道：

> Hi Julien,
>
> We currently have 2 jobs running since we are migrating all documentation
> to readthedocs, opnfv-docs-verify-master will be disable by the end of
> Danube release cycle.
>
> Today we are forcing the builds to run on particular machines (lf-build1
> or lf-build2) since these support submodules. I don’t know if it’s
> possible to increase the number of executors, if this could be an easy
> solution.
>
>
>
> I happily welcome all feedback and potential improvements for the E
> release.
>
>
>
> Regards,
>
> Sofia
>
>
>
> *From:* Julien [mailto:julien...@gmail.com]
> *Sent:* den 10 mars 2017 10:30
> *To:* Sofia Wallin <sofia.wal...@ericsson.com>; TECH-DISCUSS OPNFV (
> opnfv-tech-discuss@lists.opnfv.org) <opnfv-tech-discuss@lists.opnfv.org>;
> Fatih Degirmenci <fatih.degirme...@ericsson.com>
> *Subject:* [opnfvdocs] About docs CI jobs
>
>
>
> Hi Sofia,
>
>
>
> Currently there are two verify docs jobs in OPNFV:
>
> 1. opnfv-docs-verify-master
>
> 2. docs-verify-rtd-master
>
>
>
>
>
> The first job existed earlier before the *opnfvdocs* project created, and
> they works for the same purpose. Shall we merge them two?
>
>
>
> The other issues existed :
>
> 1. The job 'docs-verify-rtd-master' uses submodule to fetch all the OPNFV
> projects' docs triggered by any project, which makes the projects affected
> by each other. Any issue in one project will affect others. It is not
> necessary. This will also make the building process occupy more time. The
> jobs 'opnfv-docs-verify-master' does well.
>
> 2. opnfv-docs-verify-master does not output the building result to the
> artifactory, so we can not check the results.
>
> 3. the jobs of opnfvdoc fixed the Jenkins slave's label with lf-build1 or
> lf-build2 .  Currently, the resources in lf-build are in short and the many
> jobs are in the queue. Shall we set it to opnfv-build to all the jobs.
>
> 4. There are lots of warnings in logs of Job 'docs-verify-rtd-master'.
>
>
>
> In next release I hope I can introduce sphinx docker to faster current
> verify job.
>
>
>
> Best Regards,
>
> Julien
>
>
>
>
>
>
>
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [opnfvdocs] About docs CI jobs

[Julien]

Hi Sofia,

Currently there are two verify docs jobs in OPNFV:
1. opnfv-docs-verify-master
2. docs-verify-rtd-master


The first job existed earlier before the *opnfvdocs* project created, and
they works for the same purpose. Shall we merge them two?

The other issues existed :
1. The job 'docs-verify-rtd-master' uses submodule to fetch all the OPNFV
projects' docs triggered by any project, which makes the projects affected
by each other. Any issue in one project will affect others. It is not
necessary. This will also make the building process occupy more time. The
jobs 'opnfv-docs-verify-master' does well.
2. opnfv-docs-verify-master does not output the building result to the
artifactory, so we can not check the results.
3. the jobs of opnfvdoc fixed the Jenkins slave's label with lf-build1 or
lf-build2 .  Currently, the resources in lf-build are in short and the many
jobs are in the queue. Shall we set it to opnfv-build to all the jobs.
4. There are lots of warnings in logs of Job 'docs-verify-rtd-master'.

In next release I hope I can introduce sphinx docker to faster current
verify job.

Best Regards,
Julien



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

Re: [opnfv-tech-discuss] New project directory page on the wiki

[Julien]

It's great!

Is it possible to add the date when the project got passed and archived?


Raymond Paik 于2017年3月4日周六 上午1:09写道：

> Yes, adding "one-liners" is the next area for improvement.
>
> We'll have to use the page properties feature (learning this from Mark),
> but that'll have to be added to all the project spaces (50+ of them).
> Hopefully I can take a look at that soon :-)
>
> Ray
>
> On Thu, Mar 2, 2017 at 11:25 PM, Tapio Tallgren 
> wrote:
>
> Looks good to me! It makes sense to automate as much as possible the
> maintenance of project information, since otherwise the information easily
> gets out of sync.
>
> Would it be possible to add the project one-liners as suggested in one of
> the comments?
>
> -Tapio
>
>
>
> On 03/03/2017 08:53 AM, Raymond Paik wrote:
>
> All,
>
> I decided to replace the old "approved projects" page (
> https://wiki.opnfv.org/display/PROJ/Approved+Projects) with a full
> project directory page (
> https://wiki.opnfv.org/display/PROJ/Project+Directory) that Mark Beierl
> started last year.  I made some updates and checked to make sure all
> projects are listed, but please let me know if you feel there are errors.
>
> This new page has a couple of benefits.  First, we no longer have separate
> project categories of requirements, integration & testing, development,
> etc. so the new page reflects the current project lifecycle.  Secondly, the
> new directory page is automatically updated when a newly approved project
> space is created so there's no need to make manual updates.  (Someone from
> the LF team will create a new project space on the wiki when a project gets
> approved)
>
> Fear not, the old "approved projects" is still there as a child page under
> the new project directory page.  As I noted on the page however, the old
> page will not be maintained.  Once people get used to the new directory
> page, I'll go ahead and delete the approved projects page in a few months.
>
> Thanks,
>
> Ray
>
>
>
> ___
> opnfv-tech-discuss mailing 
> listopnfv-tech-discuss@lists.opnfv.orghttps://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 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] [daisy] Does Daisy Installer run in a VM?

[Julien]

Hi Fatih

Daisy can run on both environments. In OPNFV, it runs on a libvirt VM by
default. It has no requirements on the host OS, Ubuntu and CentOS both are
OK.

Thanks,
Julien



Fatih Degirmenci <fatih.degirme...@ericsson.com>于2017年3月1日周三 上午6:18写道：

Hi Daisy Team,



Can you please let us know if you run Daisy installer directly on Jumphost
or in a VM?



The reason for this question is that this is a goal of the Infra team so we
can help ensure some strategic things for CI/CD:

-  Jumphosts are stable, i.e. installers do not pollute the
jumphost (sometimes resulting in need to redeploy the jumphost)

-  Jumphosts are consistent, e.g. we can use a common Jumphost host
OS (e.g. Ubuntu) and run all installer ISOs in VMs on the jumphost

-  We can migrate to dynamic POD allocation, given the two
capabilities above



This is a key need of development lab users also, who probably don’t have
the automated tools for POD deployment such as OPNFV CI/CD uses, and who
can spend a lot of time having to reinstall jumphosts to switch between
OPNFV distros.



Does Daisy support the installer ISO being booted:

1)   in a libvirt (qemu+kvm) VM

2)   on a generic jumphost (i.e. Ubuntu or Centos)



/Fatih
___
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] Adding Multi-Calendar to Project or WG wiki pages

[Julien]

Same as Prakash.

I find nothing when I open the page in edit mode. I wonder how to include a
existed calendar into this page.

Thanks, Julien

2017-01-18 1:03 GMT+08:00 Prakash Ramchandran <
prakash.ramchand...@huawei.com>:

> Hi all,
>
>
>
> Is there  a procedure to follow to add this to Project or WG wiki pages?
>
> This link was presented today at TSC,
>
> https://wiki.opnfv.org/display/ds/Multi+Calendar+Example
>
> Can someone point where is the details for this to implement?
>
>
>
> Thanks
>
> Prakash
>
>
>
> *Prakash Ramchandran*
>
> [image: logo_huawei]* R USA*
>
> *FutureWei Technologies, Inc*
>
> Email: prakash.ramchand...@huawei.com <s.c...@huawei.com>
>
> Work:  +1 (408) 330-5489
>
> Mobile: +1 (408) 406-5810
>
> 2330 Central Expy, Santa Clara, CA 95050, USA
>
>
>
>
>
>
>
>
>
> ___
> 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] [OPNFV] Sorry, I could not continue working with you on OPNFV Escalator.

[Julien]

Dear Jie,

Thanks for your contribution for and leading on Escalator project!
Welcome Kong Wei

BR,
Julien


2017-01-17 16:16 GMT+08:00 <hu@zte.com.cn>:

>
> Dear Escalator Team and OPNFV folks,
>
>
> Due to lack of time to work on OPNFV Escalator, I have to step off from
> the position of Escalator Project Lead in 2017.  As my final proposal, I
> recommand Mr. Kong Wei (kong.w...@zte.com.cn) to take over Escalator
> Project now.  Hope you can agree with me.
>
>
> Thanks for your contribution and support to OPNFV Escalator!  And wish we
> would meet in the future.
>
>
> With Best Regrads,
>
> Jie Hu  *胡捷 *
>
> ZTE Corporation
>
>
>
> ___
> 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