Failed to start the record bot and so raw meetings notes in line here:

[07:27] Short meeting today due to folks being still out for holiday

[07:28] We did not have critical mass on the details of pending items for closure on Danube release

[07:31] Bob is wondering about the MS5 milestone, which is closure of scenario integration and may not affect Armband anyways

[07:31] Larry L indicated that there was discussion of slipping MS5 due to delays from infrastructure changes

[07:33] found the email where recommendation to the TSC that we slip MS5 by two weeks to January 27 and MS6 by three weeks to Feb 17

[07:34] This recommendation would not propose to move the release date, but just shrink the time between MS6 and relase March 27- TBD

[07:36] Bob indicated he would like to confer with core engineers in Armband after they return, and decide if we need to have a meeting 13Jan or we can skip to 20Jan to allow us more time to make progress and compile staff to report as Bob is in China 07Jan-13Jan

[07:37] Bob will send a message out on tech discuss once we have more insight into readiness for a report to the team meeting

[07:38] question came up regarding whether Apex Installer/CentOS support was still in the plan

[07:39] Bob indicated that, despite continued delays due to interrupts within the Apex team, we have been assured that the necessary seed work by Red Hat will be picked in early in January.

[07:39] Bob will contact that team for an update today 06Jan

[07:40] Another question came up re: why JOID was displayed as lower priority for Danube.

[07:41] Bob indicated it was merely tied to desire for OS diversity (add CentOS) support which implied Apex, plus, there is a customer who will need Apex support.

[07:42] we already have Ubuntu support, & JOID, which is an alternative Installer for Ubuntu based system, will be added as resources are available.

[07:44] for JOID, as well as any Installer, Armband needs seed work from the project first and Armband engineers did meet with Canonical (JOID ) engineers at OPNFV PLugfest.

[07:45] renewed commitment to collaborate and plan out JOID support, starting with Armband engineer to join JOID meetings, whch have been deferred until new year due to proximity of holiday after Plugfest

Summary: Despite a 1 week setback dues to CI Main Pod Build Server failure, the system is back up and some build issues are to be resolved today or Monday and Functest runs should resume in CI Monday or Tuesday. Previous runs revealed 100% Functest passes but not yet consistent.

An additional 5 servers have been added and now being con figured and put in place over next couple of weeks. Another 5 node pod backfilling for the dedication for CI Main should be ready within 3 weeks waiting on a shipment.

Yarkstick tests all running and results being analyzed. Overall Armband Colorado 1.0 is on track for Fuel-based scenarios. Other details in the Minutes below:

Meeting focused on completing the Fuel 8 port to ARM that is all but complete in successfully provisioning a 5 node HA cluster with base Brahmaputra components, Getting Functest and then YardStick running and release notes completed for the march 24 SR1 release.

Discussing Fuel experience....team has been removing x86-isms from Fuel. Using a small 2 node pod for now until additional 3 servers arrive from supplier. will expand to 5 node within 2-3 weeks. Iben asks if this all being done in one team and could others join in. Joe indicates it is all in house yet- not sure how to open it up just yet. Iben asks if access to the process or code can be opened up for others to help. Joe has to talk to his team internally but notes that the lab in not accessible to any external folks and also wants to balance slowing down internal initial steps with opening it up to external folks ...not quite ready yet.

Iben suggested that not necessarily wanting to get the code but could possibly see the process and logjams and give some advice #action Joe to confer with internal team and see if they can benefit from having a meeting with a couple of external players

We discussed the limitation of these installers being tied to homogenous distro on the nodes. Michael R asked if Docker could help. Joe responded that Docker is not ready yet.

Bob noted that 3 more servers should be shipped any day. Bob will send Joe a status today if vendor replied.

functest status Engineer is going thru the step functest The first blocker is that the test wants to load an Intel specific binary blob called a cirros image to do a quick process check. his image can just be switched with something else

#action Joe kidder to open ticket to Functest team re: this change

Bob asked about Yardstick readiness?

Iben commented that all of the installers are now running Yardstick as well as Functest. Iben noted that other test projects like QTIP and VSPerf only apparently work on 1 lab and therefore may not make B -Release

Bob asks that any volunteers to help look at do discovery on Yardstick and Functest Iben suggests that we need to get more labs up and running and have others trying to get Pharos running Iben notes that if other labs are indeed trying to get up and running, we need to document that #action bob to document the labs that are planning to get ARM servers up and running

Iben asked if we had discussed mixed mode pods .i.e x86 controllers and ARM compute nodes? [Agenda for 23 September

#1) Agenda Bashing

#2) Project scoping for requirements and recruiting help with adding ARM support

There is a table of identified projects marked yes, No , Maybe as to whether we currently think we must spedn cycles to meet the Brahmputra release

Please take a look at this table and volunteer to take 1 or more projects to investigate, contact projects leads and ask questions of team members as to what we would need to do to support ARM servers in the project

#3) Installer investigation (Joe Kidder) - we have identified 2 key installers we should consider and they seem to be aligned with certain linux distributions- Fuel (Ubuntu) and Apex (Foreman) (CentOS)

#4) Pharos Lab conformance for ARM server Pods. We are seeking members familiar with Pharos and Bob will join the meeting this week to begin enquiring as to what we need to do to operate a Pharos compliant lab. Discussion and input needed in the meeting.

#4) Misc open floor and wrap up

{group3}

No labels

Overview

Content Tools

Viewtracker

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