Racks become available on Thursday this week. Equipment will be racked and cabled from Thursday onwards.

40G interconnect cables are about to be ordered

No new switch required (different from what we thought just before the break: The ARM servers only have 4 ports. The Intel NICs are full height and won't fit the 1/2 height ARM server form factor. This frees up some ports, hence no additional switch is needed)

Summary of equipment status: All Cisco gears shipped. Intel NICs are on back order, and Ray to follow-up with CDW. Lincoln added that Racks and power strips have been ordered by UNH. After the meeting, received an email that HPE equipments are shipping and Ray will get the tracking info.

Review status of cabling: Lincoln uploaded a couple of documents at
PHAROS-335
-
Getting issue details...STATUS
that include cabling diagram. Consensus was to continue the discussion via the JIRA ticket.

Review of JIRA tickets for MVP: Didn't have nearly enough time to discuss the topic, but people noted that we need to add new capabilities to the existing LaaS dashboard. A suggestion was made to have an hour long meeting next week to continue discussion on both cabling and open items for the MVP

"Governance" of the LaaS initiative: Consensus to keep this initiative within the Pharos project.

Equipment: Expected arrival at UNH is around Christmas. UNH will have someone on site to receive the equipment.

Rack & cable up: Expected to happen 1st week of January (if equipment is received by the end of 2017)

UNH already has pieces of the solution available – e.g. bare metal automated install (for Ubuntu, Centos); OPNFV virtual deploys (Fuel, Joid). Portal is lagging behind - https://wiki.opnfv.org/display/INF/Dashboard+Roadmap – Portal was built as an intern project and requires a set of enhancements to be useable for LaaS. Portal is hosted by LF right now. Now major benefits to change this. We’ll keep things as they are for now.

Initial offering / MVP:

Automated install of a single bare metal server. User should be able to choose from at least 3 images (covering the main distros: Centos, Ubuntu, Suse)

Reservation will follow fixed timeslots (e.g. 1 week). All reservations will initially be synched to allow for easier system maintenance (e.g. all reservations end always on Sunday, midnight PT).

Next steps:

AI Lincoln: Create cabling plan for server/switches

AI Fatih: Create Jira tickets for tasks (mostly focused on Portal) – using https://wiki.opnfv.org/display/INF/Dashboard+Roadmap as starting point. We plan to use Jira components. Tickets will be created under Pharos project but should differentiate LaaS and Dashboard.

AI Ray: Find a room/time for F2F discussions at the hackfest.

Next meeting: Tuesday Dec/5, 9am PT – Frank to send out invite/webex.

No labels

Overview

Content Tools

Powered by a free Atlassian Confluence Open Source Project License granted to Open Platform for NFV (OPNFV). Evaluate Confluence today.