15:03:21 <bramwelt> #startmeeting infra-wg
15:03:21 <collabot> Meeting started Mon Oct 21 15:03:21 2019 UTC.  The chair is bramwelt. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:03:21 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:03:21 <collabot> The meeting name has been set to 'infra_wg'
15:03:27 <bramwelt> #chair jentoio
15:03:27 <collabot> Current chairs: bramwelt jentoio
15:03:34 <bramwelt> #topic Agenda Bashing
15:05:18 <bramwelt> #link https://wiki.opnfv.org/display/INF/2019-10-21+Infra-WG+Meeting
15:06:58 <bramwelt> #info One central place for meeting details
15:07:22 <bramwelt> #info Confusing when there are multiple places for meeting agendas/schedules
15:07:35 <jentoio> #link https://wiki.opnfv.org/display/INF/Infra+Working+Group
15:07:48 <jentoio> #link https://wiki.opnfv.org/display/meetings/Infra+Working+Group+Meeting
15:09:21 <bramwelt> #info Jack plans on running meeting initially
15:12:18 <bramwelt> #agree Meeting details will stay in INFRA space and be linked to the meeting space https://wiki.opnfv.org/display/INF/Infra+Working+Group
15:13:52 <bramwelt> #info Jack plans to move the meeting notes under INFRA
15:13:54 <bramwelt> #link https://wiki.opnfv.org/display/INF/Meeting+notes
15:15:17 <bramwelt> #info Discussion on how to manage and organize meeting minutes
15:16:23 <bramwelt> #action bramwelt to clean up minutes to be in individual pages
15:16:36 <bramwelt> #info Jack moving minutes from Meeting space to Infra space
15:19:42 <bramwelt> #action Jack to clean up the infra-wg page under the Meeting space and point to the agenda
15:21:13 <bramwelt> #info Discuss agenda
15:22:45 <bramwelt> #topic Pharos
15:22:57 <bramwelt> #info Jack plans to reach out to community lab owners and get a status update
15:23:17 <bramwelt> #info Will try to encourage lab owners to come to infra-wg
15:23:31 <bramwelt> #info Jack also planning on cleaning up Pharos JIRA
15:23:53 <bramwelt> #info Infra wiki needs to be cleaned up / archived / migrated
15:25:06 <bramwelt> #info Lincoln mentions Pharos spec being updated, LaaS gives you one-click-openstack
15:25:31 <bramwelt> #info What is the outlook for the infra projects?
15:25:56 <bramwelt> #info Jack mentioned Parker should be part of infra-wg given the nature of LaaS
15:26:47 <bramwelt> #info Also mentions Pharos direction towards PDF/SDF and refresh of Pharos specification
15:27:16 <bramwelt> #info Lincoln mentioned discussions at CNTT around Pharos spec and PDF
15:28:34 <bramwelt> #info There wasn't take up in the structure and content of the PDF/SDF previously, and the hope is CNTT/RI will help drive and align that content
15:29:27 <bramwelt> #info PDF/SDF very helpful for Lab owners as it provides a single description of the environment and makes it helpful to determine what the infrastructure looks like
15:30:40 <bramwelt> #info Jack explains context of SDF being collection of components needed for the scenario - CNTT will help set what those scenarios should be and determine the selection of components
15:31:22 <bramwelt> #info PDF defines hardware in OPNFV configurations (RAM, Disk, CPU, NICs)
15:31:54 <bramwelt> #info SDF defines deployment configuration (networks, IPs)
15:33:39 <bramwelt> #info Lincoln suggest RI is it's own scenario - Consumability of that scenario for XCI or Airship shouldn't differ - That part of the SDF was missed before
15:34:05 <bramwelt> #info Discussions still needed on implementation and consumability of SDF
15:35:02 <bramwelt> #info Jack hasn't been able to attend F2F where the SDF may have been discussed to provide feedback
15:36:47 <bramwelt> #info Michael asks if Pharos or Infra should be driving those specifications?
15:37:38 <bramwelt> #info Jack states it hasn't been clear where that should happen as the discussion have taken place outside those projects
15:38:53 <bramwelt> #info Lincoln suggests Infra helps provide/locate hardware for projects to help meet needs for reference implementation - LaaS doesn't care so much about the format, but the agreement on the content
15:40:44 <bramwelt> #info More requirements need to be gathered from CNTT to determine new specifications - networking infra (10/25g?), size of machines, etc
15:42:07 <bramwelt> #info Mark mentions '10 server' was not a random selection.
15:43:34 <bramwelt> #info Jack explains process around Pharos specification work in the past - installer -> hardware -> deploy -> testing -> ovp
15:43:52 <bramwelt> #undo
15:43:52 <collabot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x22fd2d0>
15:44:16 <bramwelt> #info Jack explains how process around Pharos specification may work in the future - installer -> hardware -> deploy -> testing -> ovp
15:45:26 <bramwelt> #info Pharos spec wasn't able to get to 'sizing' in the past
15:46:02 <bramwelt> #info Discussion on LaaS being used to help determine specification
15:47:25 <bramwelt> #info Lincoln explains dimensions of flexibility in LaaS comes from the network configurations, but not hardware (currently) - Machines are static hardware
15:48:38 <bramwelt> #info Jack explains LaaS is closer to cloud hardware
15:50:41 <bramwelt> #info All labs except LaaS at UNH are static
15:51:34 <bramwelt> #info Lincoln explains how labs may transition from static to dynamic LaaS
15:52:59 <bramwelt> #info LaaS vision is that given a PDF -> hardware is returned configured as specified, and given SDF -> servers are configured to match the scenario needs
15:54:37 <bramwelt> #info LaaS goal is to provide community way to provision hardware easily through the UI
15:57:37 <bramwelt> #info Mark asks what the overlap between installers and LaaS is?
15:57:48 <bramwelt> #info Lincoln answers there is 0 overlap
15:58:40 <bramwelt> #info Installers are still needed to provide a deployment of OpenStack
16:00:31 <bramwelt> #info LaaS does not provide the VM images need to do the deployment either
16:01:20 <bramwelt> #info Jack mentions LaaS, Pharos, and infra projects have been involved in the space for a while and it's great to have more people involved and interested
16:03:15 <bramwelt> #info Mark asks why each POD has individual IP?
16:04:10 <bramwelt> #info Jack explains it's a benefit to reduce confusion around address space
16:04:56 <bramwelt> #endmeeting