12:58:55 <bh526r> #startmeeting Weekly Technical Discussion
12:58:55 <collabot`> Meeting started Mon Jun 24 12:58:55 2019 UTC.  The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:58:55 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
12:58:55 <collabot`> The meeting name has been set to 'weekly_technical_discussion'
12:59:05 <bh526r> #topic Roll Call
12:59:11 <bh526r> #info Bin Hu
12:59:47 <bh526r> #info Cedric Ollivier
13:00:00 <bh526r> #info Mark Shostak
13:00:11 <bh526r> #info Greg Oberfield
13:00:20 <bh526r> #info Sridhar Rao
13:00:43 <bh526r> #info Matt McEuen
13:00:52 <bh526r> #info Trevor Cooper
13:02:09 <ollivier> #info Cédric Ollivier
13:02:32 <bh526r> #info Al Morton
13:02:39 <bh526r> #info Georg Kunz
13:04:08 <bh526r> #topic Continue to Discuss New Project Proposal "Airship-based Infrastructure Deployment and Lifecycle Management"
13:04:29 <bh526r> #link https://wiki.opnfv.org/display/PROJ/Project+Proposals+Airship
13:04:41 <acmacm> Al Morton
13:04:54 <trevor_intel> #info Trevor Cooper
13:05:15 <bh526r> #info Greg Oberfield from AT&T gave an update of resolved comments after communicating with stakeholders
13:05:36 <bh526r> #info Two major comments/comments are addressed
13:06:42 <bh526r> #info First major comment/concern: "Why multiple Installers and how to address fragmentation issues in the past?"
13:10:06 <bh526r> #info Greg and team communicated community, and explained that the root cause of prior fragmentation issue is lacking a standard definition of NFVi
13:10:19 <bh526r> #info Mark Beierl
13:10:45 <bh526r> #info Cedric full agrees that multiple installers is not an issue at all
13:11:20 <bh526r> #info The main issue is lacking common definition, and loses lots of end users
13:11:43 <bh526r> #info Daniel Balsiger
13:12:08 <bh526r> #info Pierre Lynch
13:12:16 <bh526r> #info Parth
13:13:02 <bh526r> #info Cedric asked why Airship cannot be merged with XCI, and MaaS
13:13:56 <bh526r> #info #info Matt explained that Airship 1.0 used MaaS for bare metal provisioning, which was the best tool at that time
13:14:50 <bh526r> #info With Airship 2.0 work in progress, we are going to leverage k8s Cluster API for bare metal provisioning
13:15:20 <bh526r> #info i.e. metal3 project, and lots of plugins for AWS, Google cloud etc.
13:15:38 <bh526r> #info The 1st driver to leverage is Ironic
13:16:00 <bh526r> #info And Kubeadm support as tooling for k8s itself
13:16:26 <bh526r> #info We are behind those projects for k8s cluster for bare metal provisioning
13:17:36 <bh526r> #info Lots of installers there, e.g. Ansible/Kubespray/Bifrost in XCI, and Airship isn't intended to support other installers, which is out of scope of mission of Airship
13:17:56 <bh526r> #info Each installer can focus on its good, and particular use cases
13:18:22 <bh526r> #info Cedric agreed that we shouldn't merge them together
13:19:07 <bh526r> #info Greg agreed to add this point in presentation why XCI and Airship are not appropriate to merge together
13:23:42 <bh526r> #info Continue to capture the resolved comments from Greg's update slides:
13:24:16 <bh526r> #info Re: multiple installers: multiple installers bring more choices for end users, and encourages technological innovation
13:24:45 <bh526r> #info With standard definition of common NFVi, all installers will implement it with the same result. Thus fragmentation issue goes away. And end users will have more choices when shopping on market
13:25:16 <bh526r> #info Team will ensure level playground of all technologies / installers – no privilege for any installer or technology
13:25:49 <bh526r> #info 2nd Resolved comments "How to add new features in Airship, e.g. DPDK, and bring new resources?"
13:26:19 <bh526r> #info All new feature work in Airship is happening in OpenStack:
13:26:54 <bh526r> #link https://airship.atlassian.net/projects/AIR/issues
13:27:16 <bh526r> #info DPDK, Tungsten Fabric etc. is happening in OSH, and brought to Airship on June 18 to bring new NFV features (upstream)
13:27:33 <bh526r> #info Features are market-driven. Business will invest resources if they see ROI, i.e. benefit end users.
13:27:52 <bh526r> #info Airship 2.0 is modular design, e.g. something for host provisioning + Airship for workloads on top of cluster
13:29:48 <bh526r> #info Because Manuel is on vacation and absent from discussion today but he made comments last week, Bin indicated that team communicated with Manuel offline and resolved his comments and concerns. Manuel agreed to move forward and bring Airship proposal for TSC creation review and approval.
13:31:30 <bh526r> #info Because no further comments, and all comments and concerns are resolved, group reaches consensus and agrees to recommend "Airship-based Infrastructure Deployment and Lifecycle Management" project proposal for TSC creation review and approval.
13:32:15 <bh526r> #topic AOB
13:32:35 <bh526r> #info Bin asked everyone to propose items for discussion for future meetings
13:32:45 <bh526r> #info Meeting adjourned
13:33:55 <bh526r> #endmeeting