Re: [opnfv-tech-discuss] TSC Nomination: Cristina Pauna

[Cristina Pauna]

Thank you Manuel, I accept the nomination.

From: Manuel Buil [mailto:mb...@suse.com]
Sent: Thursday, July 4, 2019 9:21 PM
To: TSC OPNFV ; opnfv-tech-discuss@lists.opnfv.org
Cc: Cristina Pauna 
Subject: TSC Nomination: Cristina Pauna

I would like to nominate Cristina Pauna of ENEA to the TSC.

Nomination Statement:

Cristina has been working in OPNFV for several years contributing to FUEL and 
providing help and support to anyone who required it. She has been a great 
community player! During last TSC mandate, she was one of the few who tried to 
change things and had the courage to lead a difficult task of improving, among 
other things, our best practices. I think her perseverance and her willingness 
to improve OPNFV is really valuable for us and that's why I think she should 
continue in the OPNFV TSC.

Regards,
Manuel

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

View/Reply Online (#23327): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23327
Mute This Topic: https://lists.opnfv.org/mt/32310601/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] [fuel] Dovetail jobs failed on arm-pod10

[Cristina Pauna]

Hi all,

The pod is in Enea Lab, we’ll look into it.

Thanks,
Cristina

From: opnfv-tech-discuss@lists.opnfv.org 
[mailto:opnfv-tech-discuss@lists.opnfv.org] On Behalf Of David McBride
Sent: Monday, April 15, 2019 11:25 PM
To: Trevor Bramwell 
Cc: Aric Gardner ; 
opnfv-tech-discuss@lists.opnfv.org; xudan 
Subject: Re: [opnfv-tech-discuss] [fuel] Dovetail jobs failed on arm-pod10

Ok - thanks. Has the lab owner been contacted directly. Who is it?

David

On Mon, Apr 15, 2019 at 11:30 AM Trevor Bramwell 
mailto:tbramw...@linuxfoundation.org>> wrote:
Hey David,

This is on the POD/Lab owner to fix. Neither me nor Aric have have
access to arm-pod10.

I can provide some insight into the error though. There is a system
version of pip installed, which is called from a wrapper script
/usr/local/bin/pip. If anyone runs `sudo pip install --upgrade pip` it
will upgrade the system version of pip, but not the wrapper script
(which comes with the package), causing `pip` to fail, as around version
9/10 they renamed the 'main' function.

To fix this, pip needs to be downgraded on the system (or reinstalled),
and someone needs to find out which script/job/user upgraded pip so the
problem doesn't repeat.

Regards,
Trevor Bramwell

On Mon, Apr 15, 2019 at 07:20:55AM -0700, David McBride wrote:
> +Aric Gardner 
> mailto:agard...@linuxfoundation.org>> +Trevor 
> Bramwell
> mailto:tbramw...@linuxfoundation.org>>
>
> On Mon, Apr 15, 2019 at 2:26 AM xudan 
> mailto:xuda...@huawei.com>> wrote:
>
> > Hi all,
> >
> >
> >
> > All Dovetail jobs failed when running on arm-pod10, refer to
> > https://build.opnfv.org/ci/view/dovetail/job/dovetail-fuel-baremetal-default-optional-master/206/console
> > .
> >
> > The Error message is:
> >
> > Traceback (most recent call last):
> >
> >   File "/usr/local/bin/pip", line 7, in 
> >
> > from pip import main
> >
> > ImportError: cannot import name main
> >
> >
> >
> > I guess it can be fixed after updating the version of pip on arm-pod10.
> > Could someone help to check this?
> >
> > Thanks in advance.
> >
> >
> >
> > Dan Xu
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> >
> > View/Reply Online (#23050):
> > https://lists.opnfv.org/g/opnfv-tech-discuss/message/23050
> > Mute This Topic: 
> > https://lists.opnfv.org/mt/31186195/766177
> > Group Owner: 
> > opnfv-tech-discuss+ow...@lists.opnfv.org
> > Unsubscribe: 
> > https://lists.opnfv.org/g/opnfv-tech-discuss/unsub
> >   [
> > dmcbr...@linuxfoundation.org]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
>
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: 
> dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride

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

Re: [opnfv-tech-discuss] Code and Release improvements

[Cristina Pauna]

Thank you all for replying on this thread, I think it’s important to have a 
healthy debate.

I feel the need to emphasize that this rule cannot be applied to projects with 
only 1 active committer for obvious reasons.

In the discussions held on this topic in the technical meetings, this gerrit 
rule was considered a practice most of the OPNFV projects have already, and it 
was more of a formality to enable it in gerrit. To me it was a no-brainer, I 
wasn’t expecting this to be a sensitive topic and get such strong reactions 
against it. One of these strong reactions is that OPNVF will be dismantled  by 
this gerrit rule. My belief is that we become more responsible and involved 
when we depend on each other. So my expectation is that people who are now 
occasionally noticing a patch and think “I don’t have time to review that, I 
trust the author, he/she can handle whatever he/she made in that patch” to 
shift to “I need to make time to review that patch, the author needs me to”. It 
may be that my assumption is wrong and people just don’t care but I am really 
curious on why do people who think OPNVF will be destroyed by this enforcement 
think that.

Best regards,
Cristina



From: ollivier.ced...@gmail.com [mailto:ollivier.ced...@gmail.com]
Sent: Wednesday, February 13, 2019 10:58 PM
To: ahot...@cisco.com; Manuel Buil ; Cristina Pauna 
; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Code and Release improvements

Hi Alec,

You're right.

It should be noted that we are excluding the oldest opensource projects (Linux, 
GNU/Linux distributions, etc...) from that discussion.
We are just listing few LFN projects and OpenStack (and wrongly in case of ODL 
which has been cited multiple times).

But it's simply related to the average opensource experience in OPNFV.

Cédric

Le mercredi 13 février 2019 à 02:07 +, Alec via Lists.Opnfv.Org a écrit :
Hi Manuel,

I don’t think it is valid to compare large open source projects that have a 
lots of contributors  with smaller ones that are just what they are, niche 
projects.
If you ask a contributor of these high visibility projects if they want to 
contribute to a small niche OPNFV project, I don’t think there will much 
interest and it will not be because of loose commit requirements.

In the past few years I’ve noticed pretty large resource shift from openstack 
related projetcs to orchestration (ONAP), edge cloud and containers/k8s, not 
because there is no more work to do in the traditional openstack/NFVi space but 
because of vendors shift of strategy and priority.
I don’t think having looser commit rules has any bearing in the defection of 
developers (even openstack has been losing a lot of developers and interest 
compared to a few years ago).

BR,

   Alec













From: Manuel Buil mailto:mb...@suse.com>>
Date: Tuesday, February 12, 2019 at 1:57 PM
To: "cedric.olliv...@orange.com<mailto:cedric.olliv...@orange.com>" 
mailto:cedric.olliv...@orange.com>>, "Alec Hothan 
(ahothan)" mailto:ahot...@cisco.com>>, Cristina Pauna 
mailto:cristina.pa...@enea.com>>, 
"opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>" 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] Code and Release improvements

Hello,

This is the last mail I got in this thread but perhaps it is not the last one. 
For unknown reasons, this thread is being flagged as SPAM and I am not sure if 
something got blocked in between (e.g. I never got Alec's mail).

Ok, now I get your points, thanks Alec and Cedric. Unfortunately, I still think 
it is bad if this is not enforced (with temporary exceptions) because of what I 
said in my previous mail. I'd suggest to ask around people working in other 
communities about this (kernel, openstack, CNCF...). Last week I was on a 
business trip and had the opportunity to ask open source people. Everyone I 
asked was surprised and I agreed with a couple of them who said that they would 
never join a project that allows this. If a project does not attract 
developers, allowing to self-merge patches is not going to help, right the 
opposite.

It seems to me, and correct me if I am wrong, that you guys are fine if OPNFV 
becomes a community for multiple projects with only one/two committers (as long 
as those are niche projects (@Alec: what about installers? what about 
yardstick/functest/dovetail?) or projects with an ideally perfect CI). That is 
a vision I don't share and I thought OPNFV in general did not share but I can 
just talk for myself, let's hear some other opinions ;).

Regards,
Manuel

On Mon, 2019-02-11 at 14:41 +, 
cedric.olliv...@orange.com<mailto:cedric.olliv...@orange.com> wrote:

Hello,


New development process enforcement for which developers?
The proposal could maybe make sense in a very active community with lots of 
developers without any automated verification jobs.
Both as

Re: [opnfv-tech-discuss] Code and Release improvements

[Cristina Pauna]

Hi all,

The first proposal from the Code and Release 
Quality<https://etherpad.opnfv.org/p/Code_and_Release_Quality> (Improve 
project's info accuracy) has been approved by the TSC on 5th Feb (see 
TSC-14<https://jira.opnfv.org/browse/TSC-14> for details).

The second proposal (Improve gerrit best practices), although generally well 
received, has raised some concerns and I would like to ask the community for 
more feedback on it.
The proposal is to discourage self-merging patches by adding this into our wiki 
documentation and, in a reasonable timeline to enforce it through gerrit 
(current recommendation is Hunter 8.0 milestone)

The background for this proposal is good practices done in other open source 
communities, which value peer review. Some examples are:

*OpenStack requires 2 committers to give a +2 for any patch: 
https://docs.openstack.org/infra/manual/developers.html#code-review

*Akraino requires contributor diversity (the project demonstrates that 
it has a stable core team of contributors/committers which are affiliated to a 
set of at least three different companies): 
https://wiki.akraino.org/display/AK/Akraino+Technical+Community+Document#AkrainoTechnicalCommunityDocument-3.3.7.3CoreReview

*Blog with gerrit best practices that promotes to not self-approve 
changes and to have at least 2 other people review the change: 
https://blog.simplypatrick.com/html/gerrit-best-practices.html

*Some OPNFV projects already follow this good practice although is not 
enforced by gerrit



Peer reviews are important because they make other members to better understand 
the changes that are happening in a project, give opportunity to have 
architectural discussions, make committers more involved and responsible, and 
improve the overall quality of a project.

Understandably, there have been situations when a project had a single active 
committer, and those can be excepted from the rule for a limited period of 
time. On the long run this type of projects have been proven  to be 
unsustainable anyway (most of them died on their own when the person sustaining 
the project pursues other interests). Exceptions can always be approved if 
there's a good reason for them.

These are some concerns I got over this proposal:

-Code is automatically verified by Jenkins so a Verified +1 from 
Jenkins assures the new code is not breaking anything

o   Peer review is just as important as automatic verification of the patches, 
as it provides all the benefits listed above. One should not exclude the other

-Trivial patches don't need peer review

o   What is trivial and not can be better decided by a second set of eyes (one 
line change can have major impact). Also, it should not matter if a change is 
trivial or not to have proper peer review

-Low number of active developers in OPNFV

o   This is indeed a concern and a reason for which this practice has become so 
common. But unless a project has just 1 active committer, self-approved patches 
should not happen

I would like to know if your projects already has this practice informally, if 
you would like to have it as a hard requirement, and if you have any concerns. 
You can either use this thread or join us on the Technical Discuss meeting this 
Thursday (https://wiki.opnfv.org/display/PROJ/Weekly+Technical+Discussion)

Thanks,
Cristina


From: opnfv-tech-discuss@lists.opnfv.org 
[mailto:opnfv-tech-discuss@lists.opnfv.org] On Behalf Of Cristina Pauna
Sent: Friday, January 25, 2019 11:08 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Code and Release improvements

Hi,

During the end of last year, the TSC formulated the OPNFV's vision for 2019 to 
move to a more devops approach. An area identified to be improved was Code and 
Release, and a process was devised to implement these improvements:


  1.  Gather the proposals from the community in a template format that would 
provide clarity and uniformity (see format and examples in the etherpad)
  2.  Debate the proposals in the Technical meeting and get them into a final 
form. At this time there has to be an owner committed to implement/drive the 
proposal
  3.  Present the proposals that have a final form to the TSC meeting and get 
approval from the TSC (things can go back and forth and be re-considered if the 
TSC doesn't approve)
  4.  Create a Jira for each proposal in the TSC project to track progress of 
the implementation
  5.  Monitor that the proposal is implemented, add comments to the Jira with 
the progress

Etherpad 
https://etherpad.opnfv.org/p/Code_and_Release_Quality<https://url10.mailanyone.net/v1/?m=1gmxT5-0001um-5x=57e1b682=FDUnKnFkmKi1AlQjc46nOjZapvNg4K1i7TDS0fb_8sEsCRLXXgy1mMAMDkdygSTC2gMGyPlgqIOtNkEkJrk4BM6s-4Ri82ZuweI0uy3hQihNODxXoqptZ2bZJkKXIYGg2kP0aMP0342bA3U7-VAN6YplmyUWzyTpTolcnvVDlhbxTybNSAt-bCmTXkmKBsiREApHVewxBMBCvBlnS9W5xAqUIm5lHXNKyJ6nn9F-G6zQzcXeIec--z4EHFwxQHayRevmliMPv6MUbr5lIE7Zy

[opnfv-tech-discuss] Code and Release improvements

[Cristina Pauna]

Hi,

During the end of last year, the TSC formulated the OPNFV's vision for 2019 to 
move to a more devops approach. An area identified to be improved was Code and 
Release, and a process was devised to implement these improvements:


  1.  Gather the proposals from the community in a template format that would 
provide clarity and uniformity (see format and examples in the etherpad)
  2.  Debate the proposals in the Technical meeting and get them into a final 
form. At this time there has to be an owner committed to implement/drive the 
proposal
  3.  Present the proposals that have a final form to the TSC meeting and get 
approval from the TSC (things can go back and forth and be re-considered if the 
TSC doesn't approve)
  4.  Create a Jira for each proposal in the TSC project to track progress of 
the implementation
  5.  Monitor that the proposal is implemented, add comments to the Jira with 
the progress

Etherpad https://etherpad.opnfv.org/p/Code_and_Release_Quality was created to 
gather and debate the proposals. For those of you who want to contribute to the 
improvement of the code and release, go ahead and add your proposals there, as 
well as add your notest on the the existing ones (make sure you add your name 
to your notes). Looking forward to see your input.

Thanks,
Cristina

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

View/Reply Online (#22722): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22722
Mute This Topic: https://lists.opnfv.org/mt/29535315/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] [fuel] Dovetail job failed on 2 fuel pods ericsson-pod1 and arm-pod10

[Cristina Pauna]

Hi Dan,

I changed the pip version on arm-pod10 to 9.0.3 and now the command you are 
trying to execute works.
I don't have access to the Ericsson pod so somebody form that lab should be 
able to help.

Thanks,
Cristina

From: opnfv-tech-discuss@lists.opnfv.org 
[mailto:opnfv-tech-discuss@lists.opnfv.org] On Behalf Of xudan
Sent: Tuesday, December 18, 2018 8:42 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [fuel] Dovetail job failed on 2 fuel pods 
ericsson-pod1 and arm-pod10

Hi all,

I found that Dovetail jobs always failed on ericsson-pod1 and arm-pod10 when 
running on Fuel Gambia [1].
The fail reason on ericsson-pod1 is
Traceback (most recent call last):
  File "/usr/local/bin/pip", line 7, in 
from pip import main
ImportError: cannot import name main

And the fail reason on arm-pod10 is

sudo: pip: command not found

They are all failed when running pip command [2]. Could someone help to have a 
look?

[1] 
https://build.opnfv.org/ci/view/dovetail/job/dovetail-fuel-baremetal-default-mandatory-gambia/
[2] 
https://github.com/opnfv/releng/blob/master/jjb/dovetail/dovetail-run.sh#L290

Thanks,
Dan Xu

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

View/Reply Online (#22585): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22585
Mute This Topic: https://lists.opnfv.org/mt/28790134/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] Issues with Gambia release #release #gambia

[Cristina Pauna]

+1

From: David McBride [mailto:dmcbr...@linuxfoundation.org]
Sent: Thursday, November 1, 2018 8:50 PM
To: TSC OPNFV 
Cc: Bin Hu ; Aric Gardner ; Tim 
Rozet ; huangxiangyu ; Sofia 
Wallin ; Cristina Pauna ; 
Alexandru Avadanii ; TECH-DISCUSS OPNFV 

Subject: Re: Issues with Gambia release #release #gambia

I haven't received any comments or questions, so I'd like to go ahead and start 
an email vote.

TSC members, please respond to this email with +1, 0, or -1.

Does the TSC approve of delaying the release of Gambia 7.0, including 
milestones 8, 9, 10, and 11 by one week, as follows?

  *   Nov 6 - MS8 - end of formal testing
  *   Nov 7 - MS9 - final documentation
  *   Nov 8 - MS10 - JIRA cleanup
  *   Nov 9 - MS11 - project tagging
No other milestones for Gambia or Hunter are affected.

David

On Tue, Oct 30, 2018 at 3:09 PM David McBride 
mailto:dmcbr...@linuxfoundation.org>> wrote:
Team,

As I said during the TSC meeting today, I have some concerns about the status 
of the Gambia release and I am recommending that we delay the release 1 week to 
November 9.

Before we vote on that recommendation, I'd like to explain my concerns and 
allow a day for feedback/discussion.

  *   Apex 
deployments<https://url10.mailanyone.net/v1/?m=1gII35-000kdK-3Q=57e1b682=-VdihvkCcSPBir6vfjAbqLv4bpDMmU3iPIrUwd1EYRCJZXIm4IJlUrhOh2BrjfMdpsoFavyC2R62NpIPoyUqUhYCqt_VMJnJu4axWap5A4SiFgsGcnLOWrLAJjnDjZwh7RmQgP27H5Wer2AQZRLn8-BZTan0yR5nDxmaXLOrdRQSoZxQM3KP3-NuuchQIxgz-LD2SP-CdREw5OpdQy-nZ7wp-AoVHlj5vkpikzreyK8GL6NRfgZ16wEJFUSJ2L90gdOoApncabreRF1fhwfXIQ>.
  Approximately 2/3 of recent deployments have failed.
  *   Compass 
healthcheck<https://url10.mailanyone.net/v1/?m=1gII35-000kdK-3Q=57e1b682=AvnzpI7QY9QNAP6WFS37aVJbCwh5vcQId4ptLEiE57_P5msyZqGenEZHLXORFGVJ1EpAWsAPn4eJSQOxNHnR-lB7BXZvPWHu2DH-o83Exl2dkvdHCzG711QPPMsO78hH5W5lzJpXFReQIy_1TRFQf8x5wX1dy2xHrYxWg7_SEsx5s5qzp2Gt7eri5pY9kZFHKih6HMYwUa0d3I5VxX_cKdJwfCLRFN3IxGhYhkZzdMr7MbKJ805iY20FgH3_7VCmbHq2cyus2eI9YJY4bh1VyuTdTVmHTT5Y0JoFTdq_ZdI>.
  Not running because the initial ping test is failing.
  *   Scenario documentation.  Sofia reports that many scenarios are still 
lacking documentation.
We discussed these issues during the release today.  There was no objection to 
the recommendation to delay the release 1 week.

Please feel free to respond to this email with your comments and questions.  
Let's have a brief email discussion, followed by a vote.  Thanks.

David

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


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

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

View/Reply Online (#22272): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22272
Mute This Topic: https://lists.opnfv.org/mt/27799554/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)

[Cristina Pauna]

Thank you Fatih, I accept the nomination.

Cristina

From: opnfv-tech-discuss@lists.opnfv.org  
On Behalf Of Fatih Degirmenci
Sent: Friday, August 31, 2018 2:58 PM
To: David McBride ; TSC OPNFV 
; TECH-DISCUSS OPNFV 

Cc: Tim Irnich ; Heather Kirksey 

Subject: Re: [opnfv-tech-discuss] [opnfv-tsc] [announce][election] Opening 
nominations for OPNFV Technical Steering Committee (TSC)

Hi all,

I would like to nominate Cristina Pauna to OPNFV TSC.


  *   Name of the nominee: Cristina Pauna
  *   The nominee’s organization: ENEA
  *   Nomination statement:

Cristina is one of the most experienced members of the ARMBand team and she is 
also committer to EdgeCloud project to design and develop the reference 
platform of edge cloud in OPNFV.

She has been one of the ARMBand point of contacts towards other OPNFV projects 
such as Doctor and Dovetail to help ensure that OPNFV community can utilize ARM 
infrastructure in best possible way and get their features validated on them.

Among many contributions to the ARMBand and Fuel projects, the ARM 
infrastructure in OPNFV and OPNFV in general, she has been making significant 
contributions to OPNFV testing and infrastructure projects such as Functest, 
Yardstick, Releng, and Pharos.

She is heavily involved in community-wide discussions and contributed to a 
broad horizontal of topics, from infrastructure and installer to functionality 
and MANO as well as release and documentation.

Cristina’s technical competence, experience, and openness would be very 
valuable addition to TSC.

/Fatih

From: "opnfv-...@lists.opnfv.org<mailto:opnfv-...@lists.opnfv.org>" 
mailto:opnfv-...@lists.opnfv.org>> on behalf of 
David McBride 
mailto:dmcbr...@linuxfoundation.org>>
Date: Friday, 24 August 2018 at 19:48
To: "opnfv-...@lists.opnfv.org<mailto:opnfv-...@lists.opnfv.org>" 
mailto:opnfv-...@lists.opnfv.org>>, 
"opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>" 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Cc: Tim Irnich mailto:tim.irn...@ericsson.com>>, 
Heather Kirksey 
mailto:hkirk...@linuxfoundation.org>>
Subject: [opnfv-tsc] [announce][election] Opening nominations for OPNFV 
Technical Steering Committee (TSC)

Team,

Today, we begin nominations for a new TSC, consisting of 15 members, in 
accordance with the Community Election 
Procedures<https://url10.mailanyone.net/v1/?m=1fvi4M-000HFO-4L=57e1b682=qwZ_crAJOPkXnYBg_-B68T1lVisiugzgFfmxF1LNhXyWW2PHa8HJak8OOF2LHFJB1shVDtA_vWNemeX4RKfTFmszULinDVxy83HZsuqcZOa-ht1PD2IgJws53LB8atgXlsJgHeWCHMooTCXb_XRROZhASNdhtatSQjVwdc4Mw7VzhwWX-K6FRD-LZ3GfxGn0D37iTBaYIC-BssL0Tnp4P_5N_J4CJMafKK32RYCsGZCSoxlpB76ma5nHoCLQEJoSSLlXK7Ym7Pyq6fZUejWfOQ>.
  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://url10.mailanyone.net/v1/?m=1fvi4M-000HFO-4L=57e1b682=C2sXWSM34wo8LhDxFiNwWnhI7GbW9pikHz7mwSQ2VOYH0vrv24_PiEFR2mpTlUYX5EyYVeMWCxTD8j7XiXLQql_IsMpD2rZVaXaaRsxfJYN0uHb1zG_qzdyqHYPsefoaNF3FTI5dAVWVZ5ZnxtE3gkpsHs4mRr-Sxyfp2tPMBS9ProTwvvMhjztdKGw_rZcpv7twt_Se4jPsI4n3Gfn1C3FQ5qTZn1-CONHXzCRv4YtG5Ao4YItr1lGKb2irSyH0pGqznE2Zy5c-KIkdAQaa_g>.
  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://url10.mailanyone.net/v1/?m=1fvi4M-000HFO-4L=57e1b682=1mP0rEIhYvoMA8MnykUbbSWEaE6qfF2YLsENyPmlinFmidfTtNrM9KgrTMKoICK2gUV3jJz4EVt3q1TbpVw_nuZlJZTyu5vxCMum-pP38DAw4QR5OtPgst7ZKfFXWBXK8iAq9QBzr2mj1shPRAxfAA2XOZTuP8nVC-ZXRWg-AH4sIelFJmN0DddJUgKdk2cYRnUunYMXCq3QUMVpx9AK9vfvKcyjxryqDeamVfm0fcNcqkRLWrbyqKOu1XxCkcbZv04gINvsc9t2y5UT4pjBw7Czj-WmBV9RVm8aosCyRZc7VOz0FTdcOOhnZw36GHmt>.

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

Re: [opnfv-tech-discuss] [release] Call for participation - TSC Release Process Working Group

[Cristina Pauna]

I can get involved too.

Thanks,
Cristina

From: opnfv-tech-discuss@lists.opnfv.org  
On Behalf Of Trinath Somanchi
Sent: Saturday, August 25, 2018 4:33 AM
To: David McBride 
Cc: opnfv-tech-discuss@lists.opnfv.org; TSC OPNFV ; 
tim.irn...@ericsson.com; Tapio Tallgren 
Subject: Re: [opnfv-tech-discuss] [release] Call for participation - TSC 
Release Process Working Group

Please count me.

/Trinath

On Tue 21 Aug, 2018, 02:04 David McBride, 
mailto:dmcbr...@linuxfoundation.org>> wrote:
Team,

Tim and Tapio have proposed a Release Process WG for the TSC to help guide the 
evolution of the OPNFV release process.  We'd like to have at least 5 
individuals from different areas of OPNFV, including test, tools, installers, 
infra, and feature projects.

This is a great opportunity to make a meaningful impact on the future of OPNFV. 
 Please respond to this email if you are interested in participating.  Thanks.

David

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


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

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

View/Reply Online (#21848): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/21848
Mute This Topic: https://lists.opnfv.org/mt/24828791/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] [edgecloud]: Where is the wp?

[Cristina Pauna]

Hi Gergely,

We still need to link to the edgecloud documentation to opnfvdocs so that it’s 
visible from project list [1]. I made a patch for it at [2], once that is 
merged we should be able to see it.

Thanks,
Cristina

[1] https://docs.opnfv.org/en/latest/featureprojects.html
[2] https://gerrit.opnfv.org/gerrit/#/c/60925/


From: opnfv-tech-discuss@lists.opnfv.org  
On Behalf Of fuqiao
Sent: Tuesday, August 14, 2018 10:34 AM
To: gergely.csatari ; opnfv-tech-discuss 

Subject: Re: [opnfv-tech-discuss] [edgecloud]: Where is the wp?

Hi，Gergely. From my understanding, you need to follow the opnfv doc chain so as 
to have a document published for the gerrit.
Would you like to have your submission be stand alone from Qihui's submission? 
if yes, I can help by first merge your patch, and creat a doc index for it so 
that you can get a link of opnfv docs



中国移动研究院
网络与IT技术研究所
付乔 15901025951

From: Gergely Csatari
Date: 2018-08-14 14:40
To: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [edgecloud]: Where is the wp?
Hi,

I’ve submitted the deployment scenario change 
[1]
 today and we have the initial change 
[2]
 merged already a week ago. Now it would be nice if I could link the deployment 
scenarios from the OpenStack Edge Computing Groups wiki page 
[3],
 but I do not know to where the whitepaper is published.

Can anyone help me to figure out if the edgecloud documentation 
[4]
 is published and if yes to where if no then what should we do to publish it?

Thanks,
Gerg0

[1]: 
https://gerrit.opnfv.org/gerrit/59763
[2]: 
https://gerrit.opnfv.org/gerrit/58959
[3]: 
https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG
[4]: 
https://github.com/opnfv/edgecloud/tree/master/docs/development/requirements


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

Re: [opnfv-tech-discuss] x86 POD for Auto Project

[Cristina Pauna]

What about intel-pod18 or huawei-pod12. They currently run Joid jobs, but with 
Fraser release done and development for Joid stopped, maybe one of these can be 
repurposed.

Cristina

From: opnfv-tech-discuss@lists.opnfv.org  
On Behalf Of Joe Kidder
Sent: Tuesday, July 3, 2018 5:05 AM
To: wutianw...@huawei.com
Cc: Alec Hothan (ahothan) ; 
opnfv-tech-discuss@lists.opnfv.org; timothy.gres...@intel.com; 
trevor.coo...@intel.com; tina.t...@arm.com; Trevor Bramwell 

Subject: Re: [opnfv-tech-discuss] x86 POD for Auto Project

Wutianwei,
  Would a Huawei x86 pod be available for use by the Auto project for CI 
purposes?

Thank you,
Joe Kidder
Auto Project


On Jul 2, 2018, at 5:13 PM, Trevor Bramwell 
mailto:tbramw...@linuxfoundation.org>> wrote:

Hi Alec,

Thanks for clarifying the use of POD 19. From what I know, most of the
PODs at Intel are being used for development work.

Regards,
Trevor Bramwell

On Mon, Jul 02, 2018 at 03:59:26PM +, Alec Hothan (ahothan) wrote:

please do not divert pod19, it is planned to be used for testing projects. We 
can certainly share it with Auto when not in use.
The main requirement for pod19 is that we can rely on having a stable bare 
metal installer/openstack on it so we can regress on test projects – i.e. pod19 
should not be used for testing installers or for running installer CI jobs. I’m 
not sure what “Auto CI” means exactly, if that relies on a stable openstack 
running, it might work (assuming it does not trash openstack after each run).

Have you looked at other Intel pods? I only know of 2 that are used (12 and 19) 
and it seems there are more than 2 pods…

Thanks

 Alec



From: 
mailto:opnfv-tech-discuss@lists.opnfv.org>> 
on behalf of Trevor Bramwell 
mailto:tbramw...@linuxfoundation.org>>
Date: Monday, July 2, 2018 at 8:40 AM
To: 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Cc: mailto:wutianw...@huawei.com>>, 
mailto:timothy.gres...@intel.com>>, 
mailto:trevor.coo...@intel.com>>, 
mailto:tina.t...@arm.com>>
Subject: [opnfv-tech-discuss] x86 POD for Auto Project

Hi Intel and Huawei Lab Owners,

The Auto project is looking for an x86 POD for running CI jobs on and
I'm reaching out to see if you have any available resources they could
use.

I see Intel POD 19 may be available (now that plugtest is over), and
Huawei POD 6 says it's IDLE. Could either of these or any other PODs be
made available for Auto's CI jobs?

Regards,
Trevor Bramwell

P.S. Trevor Cooper, I just remembered we discussed possibly using POD 19
for test projects, though I don't recall if we reached a decision on
that.








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

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

View/Reply Online (#21511): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/21511
Mute This Topic: https://lists.opnfv.org/mt/23003662/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] [functest] Alpine for arch

[Cristina Pauna]

Hi Cedric,

Which E are you refering to in this email? The one with deadline on 15th 
December?

Cristina

From: cedric.olliv...@orange.com [mailto:cedric.olliv...@orange.com]
Sent: Wednesday, October 11, 2017 7:24 AM
To: RICHOMME Morgan IMT/OLN <morgan.richo...@orange.com>; jalaus...@suse.com; 
Delia Popescu <delia.pope...@enea.com>; Alexandru Avadanii 
<alexandru.avada...@enea.com>; Cristina Pauna <cristina.pa...@enea.com>; 
wangwu...@huawei.com
Cc: opnfv-tech-discuss <opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [functest] Alpine for arch

Hello,

I quickly tested to build aarch64 Functest images via Docker automated builds 
what is impossible (several prerequisites are unmet). I precise the first 
published images were built locally.

I'm thinking about an alternative way which will be too much disruptive for E 
release. Again it will be suitable for my own repositories. But releng should 
have been the target to build all Docker images (I bet it won't be ready for 
E). Today's releng can't meet functest prerequisites about Docker.

I will inform as soon as my own repositories are ready.

Cédric

 Cristina Pauna a écrit 
Hi,

There has been a lot of confusion and changes around this topic and I want to 
clear things up going forward, so we do not waste any of our time.
What I understand from all the disparate discussions around this topic is:

1.   We will not do alpine for E0 release on arm, we are targeting E1/E2

2.   For the Functest-core image we will have 1 Dockerfile for x86, and a 
patch for arm that overrides this Dockerfile; from this file we will create one 
Functest-core image and the architecture will be mentioned in its tag

3.   The subsequent images (Functest-healthcheck, Functest-smoke, etc) will 
be based on the previously built Functest-core image. We will do a manifest to 
choose the correct Functest-core image based on its tag. These dependent  
images will also have its arch in the tag.

4.   The problem we are facing now is how to make sure that for 1 build, 
the Functest-core image always get built before the other ones. For x86 that is 
now done with a workaround directly in dockerhub. The target is to do it with 
Jenkins jobs builders, considering image dependencies.

Is this the approach we are all agreeing on?

Thanks,
Cristina

_



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] [functest] Alpine for arch

[Cristina Pauna]

Hi,

There has been a lot of confusion and changes around this topic and I want to 
clear things up going forward, so we do not waste any of our time.
What I understand from all the disparate discussions around this topic is:

1.   We will not do alpine for E0 release on arm, we are targeting E1/E2

2.   For the Functest-core image we will have 1 Dockerfile for x86, and a 
patch for arm that overrides this Dockerfile; from this file we will create one 
Functest-core image and the architecture will be mentioned in its tag

3.   The subsequent images (Functest-healthcheck, Functest-smoke, etc) will 
be based on the previously built Functest-core image. We will do a manifest to 
choose the correct Functest-core image based on its tag. These dependent  
images will also have its arch in the tag.

4.   The problem we are facing now is how to make sure that for 1 build, 
the Functest-core image always get built before the other ones. For x86 that is 
now done with a workaround directly in dockerhub. The target is to do it with 
Jenkins jobs builders, considering image dependencies.

Is this the approach we are all agreeing on?

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