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

2017-08-15 Thread HU, BIN
BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Pacific Standard Time BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:-0700 TZOFFSETTO:-0800 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02000

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

2017-08-15 Thread HU, BIN
Good discussion and suggestion, thank you Alec and Mark. We can discuss this on Thursday. I put it on the agenda “Container Versioning / Naming Schema for x86 and ARM”. Talk to you all on Thursday Bin From: Beierl, Mark [mailto:mark.bei...@dell.com] Sent: Tuesday, August 15, 2017 10:23 AM To: A

Re: [opnfv-tech-discuss] [infra] Proposal for LaaS Hardware

2017-08-15 Thread Bryan Sullivan
Fatih, Do "2 x 10 Gbps NICs" suffice for Pharos POD servers? I thought the NIC requirements were more substantial. IMO we should require at least IPMI + 3 NICs (Admin/PXE, Private, Public). The lab we are building as described at https://wiki.opnfv.org/display/joid/MAAS+as+Lab+Admin+Server wil

[opnfv-tech-discuss] [infra] Proposal for LaaS Hardware

2017-08-15 Thread Fatih Degirmenci
Hi, Please see the proposal regarding the number of servers and hardware specs for LaaS from the links below. · Number of x86 and ARM servers: https://wiki.opnfv.org/display/INF/Lab+as+a+Service#LabasaService-LaaS-NumberofServers · Definition of hardware for x86 and ARM: https://wi

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

2017-08-15 Thread Beierl, Mark
Hello, Alec. Fair questions, but in the ARM pods there are not necessarily x86 servers to act as the host for the container. It is also my desire to support ARM for the various pods we have, and not make it difficult for them to run. We already support ARM containers for functest, yardstick,

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

2017-08-15 Thread Alec Hothan (ahothan)
We need to look at the impact on versioning since the docker container tag reflects the release (e.g. euphrates-5.0.0), since this proposal prepends an arch field (x86-euphrates-5.0.0 ?). How many OPNFV containers will have to support more arch than just x86? I was under the impression that most

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

2017-08-15 Thread Beierl, Mark
Hello, Is this the right place to discuss changing the docker image names from containing the architecture to having the tag contain it instead? For example (from a previous email): Alpine tags as follows: multiarch/alpine:x86-latest-stable multiarch/alpine:aarch64-latest-stable Vs. in OPNFV

[opnfv-tech-discuss] Topics for Weekly Technical Discussion this Thursday 08/17/2017

2017-08-15 Thread HU, BIN
Hello community, Just a friendly reminder that if you want to discuss any item/topic/issue at our weekly technical discussion this Thursday 08/17, please feel free to let me know. Thanks Bin ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lis

[opnfv-tech-discuss] [openretriever]openretriever weekly meeting

2017-08-15 Thread 贾玄
BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 16.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST X-MS-OLK-FORCEINSPECTOROPEN:TRUE BEGIN:VTIMEZONE TZID:China Standard Time BEGIN:STANDARD DTSTART:16010101T00 TZOFFSETFROM:+0800 TZOFFSETTO:+0800 END:STANDARD END:VTIMEZONE BEGIN:VEVENT ATTENDEE;