Re: [opnfv-tech-discuss] Poll for Bottlenecks weekly meeting

[Yuyang (Gabriel)]

Hi,

As a last reminder, please vote for suitable time slot.
The time slot poll will be closed by the end of this week.

Thanks,
Gabriel

From: Yuyang (Gabriel)
Sent: Wednesday, August 23, 2017 12:24 PM
To: Yuyang (Gabriel); test...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org; Brattain, Ross B; 'S, Deepak'; liyin (F); 
Manuel Rebellon; wangyaoguang (A); AMIT KUMAR JAISWAL
Subject: RE: Poll for Bottlenecks weekly meeting

Hi,

Update the link to be more intuitional for the slots.
New: https://doodle.com/poll/rxuqui5d36zpb87i
Old: 
http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_67b7da959a92a74a=df8502f07aa5938f

Best,
Gabriel

From: test-wg-boun...@lists.opnfv.org 
[mailto:test-wg-boun...@lists.opnfv.org] On Behalf Of Yuyang (Gabriel)
Sent: Wednesday, August 23, 2017 11:12 AM
To: test...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org; 
Brattain, Ross B; 'S, Deepak'; liyin (F); Manuel Rebellon; wangyaoguang (A); 
AMIT KUMAR JAISWAL
Subject: [test-wg] Poll for Bottlenecks weekly meeting

Hi,

Bottlenecks project is about to change the meeting slot to be more adaptive to 
different time zones.
According the remaining slots in https://wiki.opnfv.org/display/meetings, a 
poll has been created at following address.
Please vote the feasible time slot before August 30th.
http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_67b7da959a92a74a=df8502f07aa5938f


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

[opnfv-tech-discuss] [Bottlenecks] Minutes of Bottlenecks Discussion on Aug. 31st, 2017

[Yuyang (Gabriel)]

Minutes of Bottlenecks Discussion on Aug. 31st, 2017

  *   Date and Time
 *   Thursday at 
0100-0200
 UTC, Aug. 31st, 2017
 *   Thursday at 0900-1000 Beijing, Aug. 31st, 2017
 *   Wednesday at 1800-1900 PDT, Aug. 31st, 2017
  *   Minutes
 *   Yang Yu
  *   Participants (4 peoples):
 *   Ross
 *   Ace Lee
 *   Kubi
Agenda:

  *   Yarkstick Cooperation on Scale up/out
  *   Stress Testing Discuss & Release Discuss
  *   Action Items Review
Discussion & Action Item

1.  IRC Minutes

  *   
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-yardstick/2017/opnfv-yardstick.2017-08-31-01.10.html

2.  Action Items

  *   Ross make python file for the super template
  *   Ace will ask Deepak if Vacl need the support of DPDK multiqueue.
  *   gabriel will re-send the email and ask the interns to vote

3.  Work Plan Review

  *   https://wiki.opnfv.org/display/bottlenecks/Release+Plan
  Euphrates:

  *   How to use Quota - Prakash
 *   Reliability project in Openstack - Prakash
 *   WIKI page restructured for closely updating project details @done 
(17-05-11 09:20)
 *   Testing framework
*   General env pre commond for all test cases? Maybe different test 
cases call diffrent functions?
  *   Requirments investigation of DPDK and SR-IOV in Bottlenecks
 *   Which categories we should put them in?
 *   What the structure of their report?
 *   Is there any existing implementation we could use?
 *   Do we need to separate the env pre and test executing operations?
  *   Test report
 *   (Automatically) Test result report to MongoDB
 *   Landing page (on-going, in plan)
  *   Stress testing
 *   Implementing the rest stress test cases discussed during Danube
 *   Collect stress test case
 *   Request/maintaining long duration pod
 *   Work with VSPERF & StorPerf
 *   Scale Up/Out cooperation with Yardstick
  *   Initiate Tuning Test
 *   Ceph Tuning ( installer deployment tuning?)
 *   Comparison results
  *   Initiate Container Testing
 *   K8S, OpenRetriever,  unicore
 *   Work with installers team for Kola deployment testing
 *   Prakash to check OpenStack for Kola testing
  *   Testing Framework Refactoring
 *   Overall framework design
 *   Determine requirements & Initiate the overall framework design
 *   Unified entrance/top logic for system limit/tuning test
 *   Initiate top logic design & investigation
 *   Separated monitoring module
*   Work with StorPerf & VSPERF adding monitoring function
*   Monitoring using yardstick? Barometer?
 *   Stand-alone & offline
  *   More Contributors in Bottlenecks
 *   Intern projects
 *   Integrate upstream
 *   More contributors in project



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

[opnfv-tech-discuss] [StorPerf] Weekly Meeting

[Beierl, Mark]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Beierl, Mark":MAILTO:mark.bei...@emc.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:When: Thursday\, August 31\, 2017 10:00 AM-11:00
  AM. (UTC-05:00) Eastern Time (US & Canada)\nWhere: https://global.gotomee
 ting.com/join/819733085\n\n*~*~*~*~*~*~*~*~*~*\n\nHello\,\n\nPlease join u
 s for the weekly StorPerf team meeting at its new time of 14:00 UTC Thursd
 ay.\n\nhttps://global.gotomeeting.com/join/819733085\n#opnfv-meeting\n\nht
 tps://wiki.opnfv.org/display/meetings/Storperf\n
SUMMARY;LANGUAGE=en-US:[StorPerf] Weekly Meeting
DTSTART;TZID=Eastern Standard Time:20170831T10
DTEND;TZID=Eastern Standard Time:20170831T11
UID:4C5AEB77-D003-492B-BD78-809B84E592B6
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170830T213427Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/819733085
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2115563791
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT5M
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [KVM] Nomination of Committer promotion for Sundar Nadathur

[Paladugula, ShravaniX]

+1

From: Reddy, Raghuveer
Sent: Tuesday, August 22, 2017 4:14 PM
To: OPNFV Tech 
>
Cc: Nadathur, Sundar 
>; Reddy, Raghuveer 
>
Subject: [KVM] Nomination of Committer promotion for Sundar Nadathur

I would like to nominate Sundar Nadathur as committer to kvmfornfv project

The motivation for nominating Sundar to committer on the NFV Hypervisors-kvm 
project is due to his commitment of providing value to the project through 
consistent high quality and valuable contributions. His active participation 
through patch submissions and code reviews for the KVM4NFV project has been 
invaluable to the project.

Please provide a +1/-1 vote before the end of next week, Sept. 1st.

Regards,

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

[opnfv-tech-discuss] [vsperf] Meeting notes for VSPERF weekly meeting - 30 Aug 2017

[Christian Trautman]

Meeting notes for today. 

Minutes: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-30-15.03.html
 
Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-30-15.03.txt
 
Log: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-30-15.03.log.html
 

Talk to you all next week. 

-Christian, 

- Original Message -

From: "Christian Trautman"  
To: "ALFRED C MORTON (AL)"  
Cc: opnfv-tech-discuss@lists.opnfv.org 
Sent: Wednesday, August 30, 2017 10:17:30 AM 
Subject: Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 
30 Aug 2017 

I'll see if I can do take the meeting notes. Just need to find a quick how to 
before the meeting. 

-Christian, 

- Original Message -

From: "ALFRED C MORTON (AL)"  
To: "Trevor Cooper" , 
opnfv-tech-discuss@lists.opnfv.org 
Cc: "Sridhar Rao" , "MartinX Klozik" 
, "Bill Michalowski" , 
"Christian Trautman" , "Mars Toktonaliev (Nokia - 
US/Irving)"  
Sent: Wednesday, August 30, 2017 8:31:08 AM 
Subject: RE: [vsperf] Agenda for VSPERF weekly meeting - 30 Aug 2017 



Thanks for letting us know, Trevor. 



I will use the organizer credentials to start the 

meeting at 1100 EDT. I’m in the office today, and 

despite filling an exception with IT, my IRC access 

is blocked. 



So, I could use some help with IRC minutes. 



see others at the meeting, 

Al 







From: Cooper, Trevor [mailto:trevor.coo...@intel.com] 
Sent: Tuesday, August 29, 2017 9:39 PM 
To: opnfv-tech-discuss@lists.opnfv.org 
Cc: MORTON, ALFRED C (AL); Sridhar Rao; Klozik, MartinX; Bill Michalowski; 
Christian Trautman; Mars Toktonaliev (Nokia - US/Irving) 
Subject: [vsperf] Agenda for VSPERF weekly meeting - 30 Aug 2017 




I am unable to attend the vsperf weekly meeting tomorrow … some suggestions for 
agenda topics are … 



- TREX integration / testing https://gerrit.opnfv.org/gerrit/#/c/34561/ 
(Latency statistics are affecting Trex performance so they are disabled by 
default, Sridhar configuration files in Jira, …) 

- Test API patch … was merged https://gerrit.opnfv.org/gerrit/#/c/40005/ 

- CI POD tuning (tests and documentation) 





Previous Minutes 

- Ww34 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-23-14.59.html
 

- ww33 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-16-14.57.html
 

- ww32 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-09-14.45.html
 


- ww31 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-02-14.55.html
 


- ww30 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-07-26-15.03.html
 






Time: Wednesday UTC 15h00, Ireland (UTC/GMT +1) 16h00, PDT 8h00 (UTC/GMT -7) … 
Currently observing daylight saving 



IRC: freenode https://freenode.net/ channel: #opnfv-vswitchperf 
http://webchat.freenode.net/?channels=opnfv-vswitchperf 



Audio: https://global.gotomeeting.com/join/391235029 

You can also dial in using your phone. United States: +1 (571) 317-3116 Access 
Code: 391-235-029 

Phone numbers from other countries are here … 
https://wiki.opnfv.org/display/meetings 



/Trevor 


___ 
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] [KVM] Nomination of Committer promotion for Shravani Paladugula

[Nadathur, Sundar]

+1

Regards,
Sundar

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Sun, Jiming
Sent: Thursday, August 24, 2017 9:47 PM
To: Reddy, Raghuveer ; OPNFV Tech 

Cc: Paladugula, ShravaniX 
Subject: Re: [opnfv-tech-discuss] [KVM] Nomination of Committer promotion for 
Shravani Paladugula

+1

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Reddy, 
Raghuveer
Sent: Thursday, August 24, 2017 9:46 PM
To: OPNFV Tech 
>
Cc: Paladugula, ShravaniX 
>
Subject: [opnfv-tech-discuss] [KVM] Nomination of Committer promotion for 
Shravani Paladugula

I would like to nominate Shravani Paladugula as committer to kvmfornfv project

The motivation for nominating Shravani to committer on the NFV Hypervisors-kvm 
project is due to her commitment of providing value to the project through 
consistent high quality and valuable contributions. Her active participation 
through patch submissions and code reviews and validation for the KVM4NFV 
project has been invaluable to the project.

Please provide a +1/-1 vote before the end of next week, Sept. 1st.

Regards,

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

[opnfv-tech-discuss] XCI Meeting Minutes - August 30th

[Fatih Degirmenci]

Hi,

Meeting minutes are available on 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-pharos/2017/opnfv-pharos.2017-08-30-13.00.txt
 
/Fatih

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

[opnfv-tech-discuss] [man-wg] Meeting #43 Summary of todays meeting - focus vIMS

[Prakash Ramchandran]

Hi all,

Here is the summary of mano-wg meeting #34
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-08-30-13.57.html

Please  note we will have a presentation in Tech meeting and test-wg this week 
on Clearwater vIMS from MANO VNF perspective updating on what was done in OPNFV 
 from B to E release.

Thanks
Prakash
___
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 Helpdesk #45048] [linuxfoundation.org #45048] RE: [OPNFV] 2 questions on OPNFV docker repo

[cedric.olliv...@orange.com via RT]

Hello,

Yes, all the repos were created but several of them were dummy (the automated 
builds were not created).
I think all Dockerfiles were not published when Trevor initiated the 
repositories.

I fixed the dependencies. Now only functest-core is built when a new change is 
pushed.
All other images are built when a new opnfv/functest-core image is published.

Build.sh is up-to-date and can be used if you prefer select releng for building 
them.
https://git.opnfv.org/functest/tree/build.sh

I'm updating the wiki as well to stop referring to the temporarily repo.
https://wiki.opnfv.org/display/functest/Run+Alpine+Functest+containers

Cédric

-Message d'origine-
De : Aric Gardner via RT [mailto:opnfv-helpd...@rt.linuxfoundation.org] 
Envoyé : mercredi 30 août 2017 14:41
À : RICHOMME Morgan IMT/OLN
Cc : OLLIVIER Cédric IMT/OLN; opnfv-tech-discuss@lists.opnfv.org; 
tbramw...@linuxfoundation.org
Objet : Re: [opnfv-tech-discuss] [OPNFV Helpdesk #45048] [linuxfoundation.org 
#45048] RE: [OPNFV] 2 questions on OPNFV docker repo

Hi Cedric.

I'm a bit confused. I thought Trevor took care of this. and checking I see all 
of your repos in the hub.
Is there something further that needs to be done?
Attached is a picture. dockerhub doesn't like copy paste.

-Aric


On Wed, Aug 30, 2017 at 7:32 AM, cedric.olliv...@orange.com via RT 
 wrote:
> Hello,
>
> To be precise, I setup automated builds via Docker to allow testing our 
> Alpine containers during the development cycle via my public repository.
> I think they have been copied (badly partially for settings) for building the 
> official images (opnfv/functest-xxx) which is not mandatory for us.
> I agree we could build them via a Jenkins job and we have already written the 
> entry point as it was firstly introduced:
> https://git.opnfv.org/functest/tree/build.sh
>
> Here we simply ask for creating the remaining containers which are only 
> available in my repo and for fixing the possible issues in the current 
> building dependencies.
>   - components
>   - features
>   - vnf
>
> As the development is finished, we would like to switch to right containers 
> hosted by OPNFV.
>
> As Morgan highlighted, the current situation can easily create congestion.
> It works for ollivier because I sync my repo every hour and because I only 
> build containers for Functest.
>
> Cédric
>
> -Message d'origine-
> De : Fatih Degirmenci [mailto:fatih.degirme...@ericsson.com]
> Envoyé : mercredi 30 août 2017 12:07
> À : RICHOMME Morgan IMT/OLN; Trevor Bramwell; 
> opnfv-helpd...@rt.linuxfoundation.org
> Cc : OLLIVIER Cédric IMT/OLN; opnfv-tech-discuss@lists.opnfv.org
> Objet : Re: [opnfv-tech-discuss] [OPNFV] 2 questions on OPNFV docker 
> repo
>
> Hi,
>
> About using docker hub for builds; I thought the docker builds would remain 
> on OPNFV Jenkins due to the limitation you highlighted below and the other 
> limitations/potential issues we summarized in earlier discussions. [1] I 
> might have missed to followup discussions that have happened during the 
> summer period so I'd be happy to catch up and read the reasons behind this.
>
> If you still think of moving to docker hub for builds, we need to think and 
> have a long term strategy rather than just moving builds to there and getting 
> paid service as it will limit our ability to improve how we are doing things 
> for test projects or projects that are building docker images.
>
> [1] 
> https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-July/017177.
> html
>
> /Fatih
>
> On 2017-08-30, 11:43, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf 
> of morgan.richo...@orange.com"  behalf of morgan.richo...@orange.com> wrote:
>
> Hi,
>
> 2 pending questions regarding the way we are managing our docker 
> files
>
> 1) Cedric sent a mail 2 weeks ago ([OPNFV Helpdesk #42909] New Functest
> Docker repositories) in order to create new docker repositories:
> opnfv/functest-features, opnfv/functest-components and 
> opnfv/functest-vnf
>
> As it has not been done yet we are currently using Cedric's private
> docker repo (where he customized the different hook)
> ollivier/functest-components,  ollivier/functest-features and
> ollivier/functest-vnf and we referenced them in releng
>
> But, of course, it would make more sense to rely on official OPNFV
> docker...
>
> José asked Trevor B. to create the first repo (opnfv/functest-core,
> opnfv/functest-healthcheck and opnfv/functest-smoke) before he left in 
> PTO.
>
> Cedric asked for the new repo on this mail thread. Should we create a
> new ticket?
>
> BTW it seems that there is an issue on the hooks used for OPNFV docker
> repos. Builds must be done in a precise order (core must be built prior
> to any other built), which seems not the case on OPNFV docker hub.
> Cedric detailed the issue and the fix 

[opnfv-tech-discuss] [OPNFV Helpdesk #45048] [linuxfoundation.org #45048] Re: [OPNFV] 2 questions on OPNFV docker repo

[ahot...@cisco.com via RT]

Few comments on this

  *   To Fatih’s point (also developed in the thread [1]) and t repeat myself, 
we need to converge on the issue of container versioning first before deciding 
on which toolchain to use (internal Jenkins build or dockerhub build server). 
From what I can see dockerhub builds may have some restrictions in the way you 
can tag your images, let’s just make sure it works with whatever versioning 
scheme we decide to use. We will get more and more containers built, if we 
don’t get versioning right it will be real hard to track artifacts to code 
commits
  *   I have not followed the thread but I’m curious to know why a container 
build order is needed (given that containers by design are independent of other 
containers at the build level)

Thanks

  Alec


From:  on behalf of 
"morgan.richo...@orange.com" 
Date: Wednesday, August 30, 2017 at 2:43 AM
To: Trevor Bramwell , 
"opnfv-helpd...@rt.linuxfoundation.org" 
Cc: OLLIVIER Cédric IMT/OLN , 
"opnfv-tech-discuss@lists.opnfv.org" 
Subject: [opnfv-tech-discuss] [OPNFV] 2 questions on OPNFV docker repo

Hi,

2 pending questions regarding the way we are managing our docker files

1) Cedric sent a mail 2 weeks ago ([OPNFV Helpdesk #42909] New Functest
Docker repositories) in order to create new docker repositories:
opnfv/functest-features, opnfv/functest-components and opnfv/functest-vnf

As it has not been done yet we are currently using Cedric's private
docker repo (where he customized the different hook)
ollivier/functest-components,  ollivier/functest-features and
ollivier/functest-vnf and we referenced them in releng

But, of course, it would make more sense to rely on official OPNFV
docker...

José asked Trevor B. to create the first repo (opnfv/functest-core,
opnfv/functest-healthcheck and opnfv/functest-smoke) before he left in PTO.

Cedric asked for the new repo on this mail thread. Should we create a
new ticket?

BTW it seems that there is an issue on the hooks used for OPNFV docker
repos. Builds must be done in a precise order (core must be built prior
to any other built), which seems not the case on OPNFV docker hub.
Cedric detailed the issue and the fix (screenshots) in the same mail thread.

Any help will be welcome to reference official sources.

2) At the moment the Docker automated builds are used per gerrit merge
for all OPNFV projects. As we are using a basic account and the number
of docker produced within OPNFV is increasing there is a high risk of
congestion.

Could it be possible to migrate to an account allowing parallel builds
(https://hub.docker.com/billing-plans/).

The cost is reasonable, we could start with a Medium or Large one.

As docker management is transverse, widely used by testing projects, Who
should take the lead to ask for such change to the TSC? Releng? Infra
Group? Testig group?

Any comment welcome

/Morgan

_

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

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

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


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

Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 30 Aug 2017

[MORTON, ALFRED C (AL)]

Thanks, I can talk you through it, I think.

Will try to join from my iPad, too, but not for
any sort of real typing...

From: Christian Trautman [mailto:ctrau...@redhat.com]
Sent: Wednesday, August 30, 2017 10:18 AM
To: MORTON, ALFRED C (AL)
Cc: Trevor Cooper; opnfv-tech-discuss@lists.opnfv.org; Sridhar Rao; MartinX 
Klozik; Bill Michalowski; Mars Toktonaliev (Nokia - US/Irving)
Subject: Re: [vsperf] Agenda for VSPERF weekly meeting - 30 Aug 2017

I'll see if I can do take the meeting notes. Just need to find a quick how to 
before the meeting.

-Christian,


From: "ALFRED C MORTON (AL)" >
To: "Trevor Cooper" >, 
opnfv-tech-discuss@lists.opnfv.org
Cc: "Sridhar Rao" >, 
"MartinX Klozik" >, 
"Bill Michalowski" >, 
"Christian Trautman" >, "Mars 
Toktonaliev (Nokia - US/Irving)" 
>
Sent: Wednesday, August 30, 2017 8:31:08 AM
Subject: RE: [vsperf] Agenda for VSPERF weekly meeting - 30 Aug 2017

Thanks for letting us know, Trevor.

I will use the organizer credentials to start the
meeting at 1100 EDT.  I’m in the office today, and
despite filling an exception with IT, my IRC access
is blocked.

So, I could use some help with IRC minutes.

see others at the meeting,
Al


From: Cooper, Trevor [mailto:trevor.coo...@intel.com]
Sent: Tuesday, August 29, 2017 9:39 PM
To: 
opnfv-tech-discuss@lists.opnfv.org
Cc: MORTON, ALFRED C (AL); Sridhar Rao; Klozik, MartinX; Bill Michalowski; 
Christian Trautman; Mars Toktonaliev (Nokia - US/Irving)
Subject: [vsperf] Agenda for VSPERF weekly meeting - 30 Aug 2017


I am unable to attend the vsperf weekly meeting tomorrow … some suggestions for 
agenda topics are …



-  TREX integration / testing 
https://gerrit.opnfv.org/gerrit/#/c/34561/
 (Latency statistics are affecting Trex performance so they are disabled by 
default, Sridhar configuration files in Jira, …)

-  Test API patch … was merged 
https://gerrit.opnfv.org/gerrit/#/c/40005/
-  CI POD tuning (tests and documentation)





Previous Minutes

-  Ww34 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-23-14.59.html

-  ww33 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-16-14.57.html

-  ww32 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-09-14.45.html

-  ww31 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-02-14.55.html

-  ww30 

Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 30 Aug 2017

[Christian Trautman]

I'll see if I can do take the meeting notes. Just need to find a quick how to 
before the meeting. 

-Christian, 

- Original Message -

From: "ALFRED C MORTON (AL)"  
To: "Trevor Cooper" , 
opnfv-tech-discuss@lists.opnfv.org 
Cc: "Sridhar Rao" , "MartinX Klozik" 
, "Bill Michalowski" , 
"Christian Trautman" , "Mars Toktonaliev (Nokia - 
US/Irving)"  
Sent: Wednesday, August 30, 2017 8:31:08 AM 
Subject: RE: [vsperf] Agenda for VSPERF weekly meeting - 30 Aug 2017 



Thanks for letting us know, Trevor. 



I will use the organizer credentials to start the 

meeting at 1100 EDT. I’m in the office today, and 

despite filling an exception with IT, my IRC access 

is blocked. 



So, I could use some help with IRC minutes. 



see others at the meeting, 

Al 







From: Cooper, Trevor [mailto:trevor.coo...@intel.com] 
Sent: Tuesday, August 29, 2017 9:39 PM 
To: opnfv-tech-discuss@lists.opnfv.org 
Cc: MORTON, ALFRED C (AL); Sridhar Rao; Klozik, MartinX; Bill Michalowski; 
Christian Trautman; Mars Toktonaliev (Nokia - US/Irving) 
Subject: [vsperf] Agenda for VSPERF weekly meeting - 30 Aug 2017 




I am unable to attend the vsperf weekly meeting tomorrow … some suggestions for 
agenda topics are … 



- TREX integration / testing https://gerrit.opnfv.org/gerrit/#/c/34561/ 
(Latency statistics are affecting Trex performance so they are disabled by 
default, Sridhar configuration files in Jira, …) 

- Test API patch … was merged https://gerrit.opnfv.org/gerrit/#/c/40005/ 

- CI POD tuning (tests and documentation) 





Previous Minutes 

- Ww34 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-23-14.59.html
 

- ww33 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-16-14.57.html
 

- ww32 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-09-14.45.html
 


- ww31 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-02-14.55.html
 


- ww30 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-07-26-15.03.html
 






Time: Wednesday UTC 15h00, Ireland (UTC/GMT +1) 16h00, PDT 8h00 (UTC/GMT -7) … 
Currently observing daylight saving 



IRC: freenode https://freenode.net/ channel: #opnfv-vswitchperf 
http://webchat.freenode.net/?channels=opnfv-vswitchperf 



Audio: https://global.gotomeeting.com/join/391235029 

You can also dial in using your phone. United States: +1 (571) 317-3116 Access 
Code: 391-235-029 

Phone numbers from other countries are here … 
https://wiki.opnfv.org/display/meetings 



/Trevor 

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

Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 30 Aug 2017

[MORTON, ALFRED C (AL)]

Thanks for letting us know, Trevor.

I will use the organizer credentials to start the
meeting at 1100 EDT.  I'm in the office today, and
despite filling an exception with IT, my IRC access
is blocked.

So, I could use some help with IRC minutes.

see others at the meeting,
Al

From: Cooper, Trevor [mailto:trevor.coo...@intel.com]
Sent: Tuesday, August 29, 2017 9:39 PM
To: opnfv-tech-discuss@lists.opnfv.org
Cc: MORTON, ALFRED C (AL); Sridhar Rao; Klozik, MartinX; Bill Michalowski; 
Christian Trautman; Mars Toktonaliev (Nokia - US/Irving)
Subject: [vsperf] Agenda for VSPERF weekly meeting - 30 Aug 2017


I am unable to attend the vsperf weekly meeting tomorrow ... some suggestions 
for agenda topics are ...



-  TREX integration / testing 
https://gerrit.opnfv.org/gerrit/#/c/34561/
 (Latency statistics are affecting Trex performance so they are disabled by 
default, Sridhar configuration files in Jira, ...)

-  Test API patch ... was merged 
https://gerrit.opnfv.org/gerrit/#/c/40005/
-  CI POD tuning (tests and documentation)





Previous Minutes

-  Ww34 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-23-14.59.html

-  ww33 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-16-14.57.html

-  ww32 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-09-14.45.html

-  ww31 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-02-14.55.html

-  ww30 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-07-26-15.03.html


Time: Wednesday UTC 15h00, Ireland (UTC/GMT +1) 16h00, PDT 8h00 (UTC/GMT -7) 
... Currently observing daylight saving

IRC: freenode 
https://freenode.net/
 channel: #opnfv-vswitchperf 
http://webchat.freenode.net/?channels=opnfv-vswitchperf

Audio: 
https://global.gotomeeting.com/join/391235029
You can also dial in using your phone.  United States: +1 (571) 317-3116  
Access Code: 391-235-029
Phone numbers from other countries are here ... 

[opnfv-tech-discuss] [OPNFV Helpdesk #45048] [linuxfoundation.org #45048] RE: [OPNFV] 2 questions on OPNFV docker repo

[cedric.olliv...@orange.com via RT]

Hello,

To be precise, I setup automated builds via Docker to allow testing our Alpine 
containers during the development cycle via my public repository.
I think they have been copied (badly partially for settings) for building the 
official images (opnfv/functest-xxx) which is not mandatory for us.
I agree we could build them via a Jenkins job and we have already written the 
entry point as it was firstly introduced:
https://git.opnfv.org/functest/tree/build.sh

Here we simply ask for creating the remaining containers which are only 
available in my repo and for fixing the possible issues in the current building 
dependencies.
  - components
  - features
  - vnf

As the development is finished, we would like to switch to right containers 
hosted by OPNFV.

As Morgan highlighted, the current situation can easily create congestion.
It works for ollivier because I sync my repo every hour and because I only 
build containers for Functest.

Cédric

-Message d'origine-
De : Fatih Degirmenci [mailto:fatih.degirme...@ericsson.com] 
Envoyé : mercredi 30 août 2017 12:07
À : RICHOMME Morgan IMT/OLN; Trevor Bramwell; 
opnfv-helpd...@rt.linuxfoundation.org
Cc : OLLIVIER Cédric IMT/OLN; opnfv-tech-discuss@lists.opnfv.org
Objet : Re: [opnfv-tech-discuss] [OPNFV] 2 questions on OPNFV docker repo

Hi,

About using docker hub for builds; I thought the docker builds would remain on 
OPNFV Jenkins due to the limitation you highlighted below and the other 
limitations/potential issues we summarized in earlier discussions. [1] I might 
have missed to followup discussions that have happened during the summer period 
so I'd be happy to catch up and read the reasons behind this.

If you still think of moving to docker hub for builds, we need to think and 
have a long term strategy rather than just moving builds to there and getting 
paid service as it will limit our ability to improve how we are doing things 
for test projects or projects that are building docker images.

[1] https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-July/017177.html
 
/Fatih

On 2017-08-30, 11:43, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
morgan.richo...@orange.com"  wrote:

Hi,

2 pending questions regarding the way we are managing our docker files

1) Cedric sent a mail 2 weeks ago ([OPNFV Helpdesk #42909] New Functest 
Docker repositories) in order to create new docker repositories: 
opnfv/functest-features, opnfv/functest-components and opnfv/functest-vnf

As it has not been done yet we are currently using Cedric's private 
docker repo (where he customized the different hook) 
ollivier/functest-components,  ollivier/functest-features and 
ollivier/functest-vnf and we referenced them in releng

But, of course, it would make more sense to rely on official OPNFV 
docker...

José asked Trevor B. to create the first repo (opnfv/functest-core, 
opnfv/functest-healthcheck and opnfv/functest-smoke) before he left in PTO.

Cedric asked for the new repo on this mail thread. Should we create a 
new ticket?

BTW it seems that there is an issue on the hooks used for OPNFV docker 
repos. Builds must be done in a precise order (core must be built prior 
to any other built), which seems not the case on OPNFV docker hub. 
Cedric detailed the issue and the fix (screenshots) in the same mail thread.

Any help will be welcome to reference official sources.

2) At the moment the Docker automated builds are used per gerrit merge 
for all OPNFV projects. As we are using a basic account and the number 
of docker produced within OPNFV is increasing there is a high risk of 
congestion.

Could it be possible to migrate to an account allowing parallel builds 
(https://hub.docker.com/billing-plans/).

The cost is reasonable, we could start with a Medium or Large one.

As docker management is transverse, widely used by testing projects, Who 
should take the lead to ask for such change to the TSC? Releng? Infra 
Group? Testig group?

Any comment welcome

/Morgan


_

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

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

[opnfv-tech-discuss] [Bottlenecks] Bottlenecks weekly meeting August 31th 2017

[Yuyang (Gabriel)]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Australia Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Yuyang (Gabriel):MAILTO:gabriel.yuy...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -discuss:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Brattain, 
 Ross B":MAILTO:ross.b.bratt...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'S, Deepak
 '":MAILTO:deepa...@intel.com
DESCRIPTION;LANGUAGE=zh-CN:Hi\,\n\nThe Bottlenecks weekly meeting will be h
 eld at 1:00-2:00 UTC\, Thursday\, 9:00-10:00 Beijing Time\, Thursday\, PDT
  18:00-19:00 Wednesday.\nWelcome to join our discussion. Details of this m
 eeting are shown below.\n\nAgenda:\n   1.   Discussion with Yardstick abou
 t the scaling test\n   2.   Stress testing Discussion\n   3.   Bottlenecks
  E Rel. Discussion\n   4.   Action Item Review\n\nMeeting Resources\nPleas
 e join the meeting from your computer\, tablet or smartphone.\nhttps://glo
 bal.gotomeeting.com/join/391235029\n   You can also dial in using your pho
 ne.\n   United States (Toll-free): 1 877 309 2070\n   United States : +1 (
 312) 757-3119\n\n\nAccess Code: 882-532-573\n\n\n
SUMMARY;LANGUAGE=zh-CN:[Bottlenecks] Bottlenecks weekly meeting August 31th
  2017
DTSTART;TZID=W. Australia Standard Time:20170831T09
DTEND;TZID=W. Australia Standard Time:20170831T10
UID:04008200E00074C5B7101A82E008C0E94C4DC021D301000
 01000A389A10C48672B48B762799319E5C09C
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170830T104633Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=zh-CN:https://global.gotomeeting.com/join/391235029
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-2065791007
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [OPNFV Helpdesk #45048] [linuxfoundation.org #45048] Re: [OPNFV] 2 questions on OPNFV docker repo

[fatih.degirme...@ericsson.com via RT]

Hi,

About using docker hub for builds; I thought the docker builds would remain on 
OPNFV Jenkins due to the limitation you highlighted below and the other 
limitations/potential issues we summarized in earlier discussions. [1]
I might have missed to followup discussions that have happened during the 
summer period so I'd be happy to catch up and read the reasons behind this.

If you still think of moving to docker hub for builds, we need to think and 
have a long term strategy rather than just moving builds to there and getting 
paid service as it will limit our ability to improve how we are doing things 
for test projects or projects that are building docker images.

[1] https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-July/017177.html
 
/Fatih

On 2017-08-30, 11:43, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
morgan.richo...@orange.com"  wrote:

Hi,

2 pending questions regarding the way we are managing our docker files

1) Cedric sent a mail 2 weeks ago ([OPNFV Helpdesk #42909] New Functest 
Docker repositories) in order to create new docker repositories: 
opnfv/functest-features, opnfv/functest-components and opnfv/functest-vnf

As it has not been done yet we are currently using Cedric's private 
docker repo (where he customized the different hook) 
ollivier/functest-components,  ollivier/functest-features and 
ollivier/functest-vnf and we referenced them in releng

But, of course, it would make more sense to rely on official OPNFV 
docker...

José asked Trevor B. to create the first repo (opnfv/functest-core, 
opnfv/functest-healthcheck and opnfv/functest-smoke) before he left in PTO.

Cedric asked for the new repo on this mail thread. Should we create a 
new ticket?

BTW it seems that there is an issue on the hooks used for OPNFV docker 
repos. Builds must be done in a precise order (core must be built prior 
to any other built), which seems not the case on OPNFV docker hub. 
Cedric detailed the issue and the fix (screenshots) in the same mail thread.

Any help will be welcome to reference official sources.

2) At the moment the Docker automated builds are used per gerrit merge 
for all OPNFV projects. As we are using a basic account and the number 
of docker produced within OPNFV is increasing there is a high risk of 
congestion.

Could it be possible to migrate to an account allowing parallel builds 
(https://hub.docker.com/billing-plans/).

The cost is reasonable, we could start with a Medium or Large one.

As docker management is transverse, widely used by testing projects, Who 
should take the lead to ask for such change to the TSC? Releng? Infra 
Group? Testig group?

Any comment welcome

/Morgan


_

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

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

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



___
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] 2 questions on OPNFV docker repo

[Fatih Degirmenci]

Hi,

About using docker hub for builds; I thought the docker builds would remain on 
OPNFV Jenkins due to the limitation you highlighted below and the other 
limitations/potential issues we summarized in earlier discussions. [1]
I might have missed to followup discussions that have happened during the 
summer period so I'd be happy to catch up and read the reasons behind this.

If you still think of moving to docker hub for builds, we need to think and 
have a long term strategy rather than just moving builds to there and getting 
paid service as it will limit our ability to improve how we are doing things 
for test projects or projects that are building docker images.

[1] https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-July/017177.html
 
/Fatih

On 2017-08-30, 11:43, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
morgan.richo...@orange.com"  wrote:

Hi,

2 pending questions regarding the way we are managing our docker files

1) Cedric sent a mail 2 weeks ago ([OPNFV Helpdesk #42909] New Functest 
Docker repositories) in order to create new docker repositories: 
opnfv/functest-features, opnfv/functest-components and opnfv/functest-vnf

As it has not been done yet we are currently using Cedric's private 
docker repo (where he customized the different hook) 
ollivier/functest-components,  ollivier/functest-features and 
ollivier/functest-vnf and we referenced them in releng

But, of course, it would make more sense to rely on official OPNFV 
docker...

José asked Trevor B. to create the first repo (opnfv/functest-core, 
opnfv/functest-healthcheck and opnfv/functest-smoke) before he left in PTO.

Cedric asked for the new repo on this mail thread. Should we create a 
new ticket?

BTW it seems that there is an issue on the hooks used for OPNFV docker 
repos. Builds must be done in a precise order (core must be built prior 
to any other built), which seems not the case on OPNFV docker hub. 
Cedric detailed the issue and the fix (screenshots) in the same mail thread.

Any help will be welcome to reference official sources.

2) At the moment the Docker automated builds are used per gerrit merge 
for all OPNFV projects. As we are using a basic account and the number 
of docker produced within OPNFV is increasing there is a high risk of 
congestion.

Could it be possible to migrate to an account allowing parallel builds 
(https://hub.docker.com/billing-plans/).

The cost is reasonable, we could start with a Medium or Large one.

As docker management is transverse, widely used by testing projects, Who 
should take the lead to ask for such change to the TSC? Releng? Infra 
Group? Testig group?

Any comment welcome

/Morgan


_

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

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

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


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

[opnfv-tech-discuss] [OPNFV] 2 questions on OPNFV docker repo

[morgan.richomme]

Hi,

2 pending questions regarding the way we are managing our docker files

1) Cedric sent a mail 2 weeks ago ([OPNFV Helpdesk #42909] New Functest 
Docker repositories) in order to create new docker repositories: 
opnfv/functest-features, opnfv/functest-components and opnfv/functest-vnf


As it has not been done yet we are currently using Cedric's private 
docker repo (where he customized the different hook) 
ollivier/functest-components,  ollivier/functest-features and 
ollivier/functest-vnf and we referenced them in releng


But, of course, it would make more sense to rely on official OPNFV 
docker...


José asked Trevor B. to create the first repo (opnfv/functest-core, 
opnfv/functest-healthcheck and opnfv/functest-smoke) before he left in PTO.


Cedric asked for the new repo on this mail thread. Should we create a 
new ticket?


BTW it seems that there is an issue on the hooks used for OPNFV docker 
repos. Builds must be done in a precise order (core must be built prior 
to any other built), which seems not the case on OPNFV docker hub. 
Cedric detailed the issue and the fix (screenshots) in the same mail thread.


Any help will be welcome to reference official sources.

2) At the moment the Docker automated builds are used per gerrit merge 
for all OPNFV projects. As we are using a basic account and the number 
of docker produced within OPNFV is increasing there is a high risk of 
congestion.


Could it be possible to migrate to an account allowing parallel builds 
(https://hub.docker.com/billing-plans/).


The cost is reasonable, we could start with a Medium or Large one.

As docker management is transverse, widely used by testing projects, Who 
should take the lead to ask for such change to the TSC? Releng? Infra 
Group? Testig group?


Any comment welcome

/Morgan

_

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

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

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

[opnfv-tech-discuss] [mano-wg] Meeting #43 Aug 30, Wednesday : 14.00 UTC /7.00 PDT - Clearwater vIMS Deployment & Testing

[Prakash Ramchandran]

Hi all,
Please join the Meeting#43 focusing on vIMS Deployment & Testing.
We will have a HEAT Clearwater Demo to share.
Thanks
Prakash.
Meeting Details

Meeting Times: Every  Wednesday (7.00 am PST)  at 14.00 UTC, Other  Ad-hoc 
meeting as per Project requests

For IRC can use can use http://webchat.freenode.net/

IRC#opnfv-mano (meetbot is set for meeting minutes )

OPNFV MNAO WG Meeting

GOTOMEETING

1. Please join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/391235029
(in case of GTM fails join IRC using webchat link above and get the new GTM 
link/ meeting number)

2. Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States (Toll Free): 1 877 309 2073
United States: +1 (312) 757-3136
Thanks
Prakash



.Agenda - Refer link https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111

1. Agenda Bashing

2. Actions items to review from Meeting#42 -  Orchestra -( Unit-test + 
Mock) , 
Opera , Auto - workload and Edge 
Cloud

3. Other items that are pending from Meeting#42 - Orchestra - test-wg 
follow-up, Opera - None, Auto- EUAG and XCI

4. mano-wg report for August 
2017.- 
Clearwater-vIMS-Testing
 / Modeling 
Requirements
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss