True. A 2port 10GE NIC is ~500 $US. I've already updated the wiki :) Thanks again, Frank
From: Bryan Sullivan [mailto:bls...@hotmail.com] Sent: Mittwoch, 16. August 2017 15:36 To: Frank Brockners (fbrockne) <fbroc...@cisco.com>; Fatih Degirmenci <fatih.degirme...@ericsson.com>; opnfv-tech-discuss@lists.opnfv.org Subject: Re: [infra] Proposal for LaaS Hardware Re budget I don't think 2 or 4 NICs will have much impact given the type of servers we are talking about here (datacenter, production-grade servers). Most I have seen come with 4 NICs onboard and often dedicated IPMI. Thanks, Bryan Sullivan ________________________________ From: Frank Brockners (fbrockne) <fbroc...@cisco.com<mailto:fbroc...@cisco.com>> Sent: Wednesday, August 16, 2017 3:36 AM To: Bryan Sullivan; Fatih Degirmenci; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Subject: RE: [infra] Proposal for LaaS Hardware Bryan, Thanks for raising an important point. IMHO 2 NICs are the minimal setup. This allows for performance focused setups (i.e. traffic enters on one NIC and leaves on another NIC), and it also allows for setups where you use the NICs for different purposes (e.g. dedicate a NIC to the kernel, and another one to VPP). We can of course handle all three "types" of networks (admin, public, tenant/private) using VLAN/VLAN-ranges - but for some deployments a physical decoupling might ease things. Per your suggestion: In order to allow for better flexibility, let's plan with 3 NICs for now. We can always scale back in case there are budget constraints. Lights-out-management is something that is often vendor specific - and it may, or may not require a dedicated port (IPMI 2.0 even runs over VLANs) - but as part of the requirements list, we should spell out that lights-out-management is something we absolutely require. I'll update the wiki accordingly. Thanks, Frank From: opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Bryan Sullivan Sent: Dienstag, 15. August 2017 22:58 To: Fatih Degirmenci <fatih.degirme...@ericsson.com<mailto:fatih.degirme...@ericsson.com>>; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Subject: Re: [opnfv-tech-discuss] [infra] Proposal for LaaS Hardware 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 will be designed that way. Our vision for how we will use this lab (initially, for internal development/CI activities only) is very similar to your vision for LaaS dynamic assignment of server resources. We plan to use MAAS, Ansible, and Jenkins to manage the admin and distribution of development/CI/etc activities across these servers. Thanks, Bryan Sullivan ________________________________ From: opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org> <opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>> on behalf of Fatih Degirmenci <fatih.degirme...@ericsson.com<mailto:fatih.degirme...@ericsson.com>> Sent: Tuesday, August 15, 2017 1:02 PM To: opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Subject: [opnfv-tech-discuss] [infra] Proposal for LaaS Hardware 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://wiki.opnfv.org/display/INF/Lab+as+a+Service#LabasaService-LaaSHardware Please share your thoughts, comments and questions either by replying to this mail, directly on Wiki page, or by joining the Infra WG Meeting on August 21st where this topic will be discussed. /Fatih _______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org<mailto: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
