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

2018-08-27 Thread 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-discu

Re: [opnfv-tech-discuss] #infra #laas Deciding on LaaS usage policy

2018-08-27 Thread Lincoln Lavoie
Hi Trevor, Does the LFN accounting system (i.e. what the dashboard performs authentication against) have any info tied to a user for the LFN project they participate in? To limit to 4 bookings per project, we'd need a source of truth for that. Another approach would be to present the user with a

Re: [opnfv-tech-discuss] #infra #laas Deciding on LaaS usage policy

2018-08-27 Thread Parker Berberian
Hi Trevor and Lincoln, I just want these points to be kept in mind: - Users can design and book 'PODs' of any size (up to a max that it TBD). Especially as LaaS expands beyond OPNFV, it may not be helpful to limit our thinking to just the Pharos spec. - a significant feature of this LaaS 2.0 relea

Re: [opnfv-tech-discuss] #infra #laas Deciding on LaaS usage policy

2018-08-27 Thread Aric Gardner
Hi Parker, Lincoln, Just a note, if we ask for a project name when booking we can turn that into a github url and grab that projects info file, which can inform us on things like project committers and project lead. example for project opnfv/releng: https://github.com/opnfv/releng/blob/master/INF

Re: [opnfv-tech-discuss] #infra #laas Deciding on LaaS usage policy

2018-08-27 Thread Frank Brockners via Lists.Opnfv.Org
Hi Aric, I like that suggestion – and we might consider a tiered approach: · Single server booking: Open to all (like what we have right now) · Multi-server booking: Allow only PTLs to book resources. When booking, you need to supply a link to the INFO file on git to authorize your

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

2018-08-27 Thread Yeleswarapu, Ramamani
Hi David, Please count me in. Thanks, Ramamani (Rama). From: opnfv-tech-discuss@lists.opnfv.org [mailto:opnfv-tech-discuss@lists.opnfv.org] On Behalf Of David McBride Sent: Friday, August 24, 2018 1:00 PM To: Foley, Emma L ; TECH-DISCUSS OPNFV Cc: tim.irn...@ericsson.com; Tapio Tallgren Sub

Re: [opnfv-tech-discuss] #infra #laas Deciding on LaaS usage policy

2018-08-27 Thread Parker Berberian
Hi all, This path makes sense to me. Is there an official list of OPNFV / LFN projects for us to use? I can use all opnfv/* projects on github with INFO.yaml files. Will all 7 LFN projects have a similar structure? Thanks, Parker On Mon, Aug 27, 2018 at 11:20 AM, Frank Brockners (fbrockne) < fb

Re: [opnfv-tech-discuss] #infra #laas Deciding on LaaS usage policy

2018-08-27 Thread Aric Gardner
Hi Parker, Most LFN projects will have INFO files already, those that do not will have them added in the near future. The url to fetch the info files (or have the user provide them) is: https://raw.githubusercontent.com/$LFNproject/$repo/master/INFO.yaml LFNproject is one of onap opnfv acumos

Re: [opnfv-tech-discuss] [OVN4NFV] [Container4NFV] OVN Changes

2018-08-27 Thread David McBride
Hi Trinath and Srini, Have you decided on a date for the presentation? Thanks. David On Tue, Aug 21, 2018 at 10:17 AM HU, BIN wrote: > Next Thursday is fine. > > > > Based on discussion in release meeting today, Trinath will send a proposal > to the mailing list, along with a suggested date t

Re: [opnfv-tech-discuss] [OVN4NFV] [Container4NFV] OVN Changes

2018-08-27 Thread Srini
Hi, I indicated to Bin that I would be able to present on coming Thursday. Thanks Srini From: David McBride [mailto:dmcbr...@linuxfoundation.org] Sent: Monday, August 27, 2018 4:05 PM To: Bin Hu Cc: Addepalli, Srinivasa R ; Trinath Somanchi ; TECH-DISCUSS OPNFV ; Trevor Bramwell ; tim.irn..

[opnfv-tech-discuss] FW: Yardstick weekly meeting - Aug 28

2018-08-27 Thread limingjiang
BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:UTC BEGIN:STANDARD DTSTART:16010101T00 TZOFFSETFROM:+ TZOFFSETTO:+ END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T00 TZOFFSETFROM:+ TZOFFSETTO:+ END:DAYLIGHT END:VTIMEZONE BEG

[opnfv-tech-discuss] [OVN4NFV] Weekly Meeting (28 August 2018)

2018-08-27 Thread Trinath Somanchi
Hi OVN4NFV Team - Please find the agenda for today's IRC based weekly meeting - at https://wiki.opnfv.org/display/OV/Meeting+Agenda Tuesday (Weekly) meetings Meeting Time: 1530 to 1630 UTC *EST/ET:* 1030 to 1130 HRS *PST/PT:* 0730 to 0830 HRS *IST:* 2100 to 2200 HRS (Please co-relate with

Re: [opnfv-tech-discuss] #infra #laas Deciding on LaaS usage policy

2018-08-27 Thread Frank Brockners via Lists.Opnfv.Org
IMHO it would be best to have the user provide the INFO.yaml link - and then just check that the repo belongs to an LFN project (just check the domain name). This mitigates the need to walk repo trees. We should also limit things to LFN projects, given that it is LFN that pays for the service.