Versions Compared

Old Version 58

changes.mady.by.user Unknown User (mrunge)

Saved on

compared with

New Version 59

changes.mady.by.user Unknown User (mrunge)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

June 11, 2019, 4 pm UTC

...

  • Builds mostly working.

    • DPDK still not installed correctly, however, have been able to merge remaining Gerrit items as they are not dependent on DPDK.  

    • Trevor is still working on the getting DPDK ready.

  • Merged blocked items into stable/gambia

  • Release Items

    • Complete Testing 12/5

    • Update Docs / JIRA Cleanup 12/6

    • Tag Repos / Release 12/7

    • Release Report

    • Writing release notes for gambia

    • Was able to complete Milestone 7, Stable Branch after build fix

    • Updating Milestone 9, Final documentation

    • Gambia 7.0 was 11/2

    • Gambia 7.1

    • Complete Testing 12/5

    • Update Docs / JIRA Cleanup 12/6

    • Tag Repos / Release 12/7

      • Release Report

    • For those projects that publish docker images, I have noticed that there are some Gambia jobs missing.

    • X86_64 (from releng/jjb/releng/opnfv-docker.yaml):

    • ·         Barometer

    • ·         Clover

    • ·         NFVBench


    • Basically, you just need to edit the file and change frasier to gambia for your specific artifacts.

  • Collectd Updates

    • Octo has been providing reviews

    • Rubenik as well

  • Election

    • Unless I missed a nomination, Matthias Runge will be the sole candidate.

    • Barometer committers will be able to vote on a Gerrit Issue.

    • Since there is only one candidate.  Simple voting.

    • Assumption is that Matthias will preside over the meeting next week

    • Need to organize a JIRA cleanup with Matthias and go over different aspects.

  • FOSDEM

    • Need a room for meetup

    • Nothing available at Red hat

    • Intel, still checking

    • Around 20 people

    • Best idea is to rent a room (share expense between companies)

    • Contact Emma (FOSDEM)

    • Contact Google as well (Octo)

  • Cloud Native

    • Clover

    • gRPC call

    • Prometheus collection

    • ISTIO / Service Mesh

    • gRPC plugin in collectd

    • Go to Clover wiki…

...

  • Build currently broken due to an issue with the build machine.  DPDK seems to have gone missing.

  • Al

    • Added Hugepages to the TST008 document

  • Mathias

    • Talked with CERN team who uses collectd

    • Like the stability, but also frustrated by slowness

    • Have a patch submitted for notification metadata

  • Release

  • All work should be submitted at this point

  • Maybe one additional bug

October 16, 2018

    • All work should be submitted at this point

    • Maybe one additional bug

October 16, 2018

Meeting Minutes:

  • Another week for finishing documentation of docker container install
  • Verifying the manual steps now.
  • Target end of week, beginning of next week.
  • Agenda:

...

September 04, 2018

...

08/21/2018

08/21/2018

 

08/14/2018

 

08/14/2018

08/07/2018


08/07/2018

07/30/2018

·        Dev Updates

...

-        Collectd container split: Need to check whether the separate container build jobs (master and stable) are configured correctly; so we can start adding config and build support for newer features (Emma/Kamil)

 

07/30/2018

 

07/24/2018



 

07/24/2018

...

  • Barometer CI

  • Al

    • TST010 -- Using Barometer test code to invoke faults

  • Lucakz

    • Virt plugin enhancements by end of week

    • 106 WIP

    • John, Prometheus WIP to be removed soon

  • Test lab /hardware for Nokia / RedFish

  • UNH

  • Sunku to send contacts for Intel

    • Pharos Lab

    • Non OpenStack installed hardware

    • UNH

    • Sunku to send contacts for Intel

    • Requestor to send e-mail

  • Prometheus / collectd native times stamp

06/12/2018

    • -mail

  • Prometheus / collectd native times stamp


06/12/2018

  • Development

    • Apologies on the confusion on who would do the work.

    • Thanks for the review

    • Additional clarification added / needed

    • INTEL_PMU loading issue

    • Rename -- Need to check with APEX

    • Yes!

    • ETSI NFVI Testing group might be interested in using Barometer

    • Might use Barometer to collect metrics during API compliance testing

    • Would also like to use fault triggering code from one of the Barometer demos

      • Bring an interface down / up, etc…

    Development

06/05/2018

  • DMA team (Tomo) to present a demo of Local Agent collecting OpenStack metadata.

    • One of the features of the DMA project is to collect virtual infrastructure information from OpenStack and make it available to collectd so that metadata can be added to metrics / events.

    • Tomo gave a demo of Local Agent using OpenStack API to gather metadata information for use by Collectd.

  • Development

    • VM -- Names

    • Proposal

    • Variable defined

  • Nomination of new contributors

  • Self Healing Sig

    • Use case templates about DMA project and local healing

    • What about 5 9’s

    • White paper on Barometer’s role in self-healing / availability

    • Originally discussed in Sydney

    • What should be included and what people care about

    • NEC, Verizon, etc…

    • Focus is HA.

  • Go over monitoring paper

    • Go with Confluence Wiki on Barometer home page

  • New dedicated resource for collectd.

    • Ryan McCabe (Red Hat)

05/29/2018

  • Barometer OS Summit

  • Feedback was good

    • Questions

    • Starting to use collectd, Barometer

    • What different plugins available?  Turns out most are already in Barometer

    • Feedback was good

    • Questions

    • Prometheus was mentioned -- Mostly about host to get data into Prometheus from collectd.  Not necessarily replacing collectd.

  • Virt Plugin

    • 3 missing variables.  

    • Added to JIRA

  • Ovs-stats

    • Extended DPDK stats

    • JC to check

  • PMU Plugin Wiki updates

  • Al Morton

    • List of VES metrics meeting this week

    • Going to agree with Al that IPMI are important.  What will we do with those on ETSI side?

    • Give feedback to Al on VES.

  • NFVI Monitoring White Paper

    • Create google doc

    • Start outline

    • Should cover why to monitor specific metrics / conditions, not just these are the things that are available to monitor.

  • Sunku --

  • Had a chat Sando - Paul

  • Call at end of week

  • Self healing Sig

    • List of projects (OPNFV, etc…, )

    • Sunku to e-mail...

    • Had a chat Sando - Paul

    • Call at end of week

    • Self healing Sig

05/22/2018

...

  • Gambia Release -- traditional release

    • Need scenarios and deliverables defined by May 11

  • Gambia Additions

    • More information added to virt plugin?

    • Cpu pinning

    • NUMA node characteristics

    • What to do about (mostly) static information?

  • Additional plugins?

    • May need modification to RAS

      • MCElog might be incomplete

      • Looking at out of band platform hardware

    • How to get metadata?

    • More information added to virt plugin?

    • Additional plugins?

    • Additional containers?

    • Ceilometer replacement?

      • How to get metadata

    • ?

  • Need code review of container build changes!  Gerrit # -- 53805

  • Standards

  • VES

  • Prometheus

    • Interest in using Prometheus as polling engine / TSDB

    • Prometheus_collectd_exporter vs. Prometheus_node_exporter

04/24/2018 --

  • Gambia Release

    • Traditional, XCI, both?

    • Not clear on XCI requirements.  

    • When do the tests need to be in place for XCI?

    • Traditional, XCI, both?

    • What are tentative development goals for the Gambia release?

  • RPMs / Container build

  • Standards

  • All the info we’re collecting will end up in analytic engines

    • Analytics processing tasks need info all the way down to the agent layer

    • Need to make sure there’s a measurement timestamp to provide context

    • Yes, scope parameter makes that possible

    • Scope must be conveyed with the measurements

    • All the info we’re collecting will end up in analytic engines

    • Does test008 spec have the flexibility to talk about measurement of network interface using a particular VLAN tag?

      • Yes, scope parameter makes that possible

      • Scope must be conveyed with the measurements

  • VES

    • Multi-VM reqs

    VES

    • 6.0 specs on the way (next week)

      • Multi-VM reqs

  • Compass support -- not for Gambia or Fraser?

    • Barometer will be supported in Gambia

  • HA scenario issues with build

    • A problem with OOO?

    • Fails every third build or so.

    • Will be looked at soon (next week)

  • Edge Cloud

    • Requirements

    • Categories

    • Use cases

  • Latency

    • Use cases where latency is critical

    • Example feedback loop?

    • Requirements

    • Latency

    • What does lightweight mean in the context of edge telemetry?

...

  • Spoke with DMA project team.  They are ok with working in a separate container.  They will swing back in a few weeks with a demo.

  • Standards with Al Morton

    • No updates

  • VES with Bryan Sullivan

    • Most work done by Goku

    • Bryan will update VES for latest release to make sure it works with everything

    • Plan is place to move items forward in Barometer

  • RPMs with Leif

    • Making progress

  • Func tests

    • Will not support Compass this cycle

  • Collectd pull requests

  • Release

    • Gambia path or something else?

  • Which track do we follow?

  • Continuous delivery

    • Flexibility with milestones, since you establish them yourself?

    • Bryan doesn’t think we should do traditional path -- not enough resources

    • FCI could be a good thing if it marries VES and Barometer

    • Gambia path or something else?

    • Which track do we follow?

    • Continuous delivery

      • it marries VES and Barometer

  • Edge Cloud

  • What are the requirements?

    • Need categories

    • Always about latency for faults and metrics

    • Framework and edge computing use cases would be good

    • Is VES a good fit?

    • Good for cloud-native

    • What is a cloud?  What value does opensource ecosystem get from:

      • Common telemetry date model

      • Consistent set of mechanisms by which data delivered to collector

  • How lightweight?

    • Less than 1% CPU, and 5% memory

    • Two VES encodings: C and Java

    • Goku: tokenized VES data structure

    • Overhead of data and complexity of stack

    • Go from binary XML to tokenized JSON

    • Current implementation is not lightweight but is “easy”

    • Use gzip, as it is natively available to HTTP stack (works out of box)

    • What are the requirements?

    • Is VES a good fit?

    • How lightweight?

04/10/18 --

  • DMA Project discussion

    • Positive feedback on DMA proposal.  Want to move forward.

    • Work should be done in a separate container.

  • Standards

    • Al has been reviewing Alok’s VES proposals.  Found some VMWare specific items. Vendor-specific provisions are discouraged.  Al to talk with Alok ;).

    • VES is starting to incorporate some TOSCA information.

  • Collectd

    • Emma suggested that all collectd PRs be from the same fork, Barometer, in order to make collectd aware of who the reviews are for.

    • Also, should have more Red Hat people reviewing collectd.  Need to talk with local Red Hatters.

  • VES

    • Bryan returned.  Wants to keep the VES agent development moving forward.  Did not know about DDS messaging stuff in ONAP. However, see’s that Kafka is not set in stone.  What to do at the edge.

  • General

    • Next week I will be out.  Andrew Bays will run meeting.

04/03/18 --

  • DMA Project

  • Presentation given by Tomofumi Hayashi.  Slides available on the wiki.

    • Major takeaways…

    • Run time reconfiguration of collectd.  There were some questions as to whether this should be a feature of something like an Ansible playbook.

    • Topology annotation.  Questions about security and what information would be included.  It was stated that only infrastructure information would be annotated.  

    • Data reduction and analysis at the edge.

    • DMA project should be an add-on.  Might need to be able to “unwind” project in the future.

    • Presentation given by Tomofumi Hayashi.  Slides available on the wiki.

    • Major takeaways…

    • OPNFV Bottlenecks project using Barometer container

  • Development

    • Thanks to Emma for updating the docs and helping track down Funtest issues

    • Still seeing an error with Functest… seems to be related to Functest, not Barometer.  Emma tracked down the internal Barometer issues!

    • Barometer container -> multistage build from RPMs progressing slowly..

  • ONS recap

...

  • Made MS6...

  • Next upcoming milestone, MS7, April 6th -- last day to request a stable branch.  Can request one anytime until then.

  • After than MS8, April 16, completion of testing

  • Current Fraser status

    • api_check failing

    • test_add_remove_volume

    • test_attach_volume_nowait

    • test_detach_volume_nowait

    • ….

    • Perhaps it was a system / connectivity failure?

  • Emma good catch on Hugepages failing fix

    • Gnocchi failures

    • Results not appearing quickly enough due to Gnocchi archive policy

    • Change default policy to High

  • AODH failures

    • Need to modify the tests to perform specific failure action

    • api_check failing

    • Emma good catch on Hugepages failing fix

    • Gnocchi failures

    • AODH failures

      • specific failure action

  • REDFISH Plugin

    • Purpose  -- node or rack?

    • Design review

  • Standards Update

  • VES Updates

  • Progress on ETSI?

  • VES Mobile edge platforms?

  • Is there a cadvisor plugin for collectd?

  • C, Java VES libraries

    • Microservice heatbeat

    • ONAP flow

    • Vendor VNF

    • Closed loop control

    • Services goes into VNF

    • Any missing heatheats

    • At the FM layer

    • Progress on ETSI?

    • VES Mobile edge platforms?

    • Is there a cadvisor plugin for collectd?

    • C, Java VES libraries

    • Microservice heatbeat

03/13/18 --

  • Functest debug and then power loss ;(

...

  • Milestone 5 complete

    • Scenario deployment passed

    • Functest failing

  • MS6 03/16/18

    • Test case implementation completed.

    • Preliminary documentation completed.

    • First day that projects may request creation of the stable branch for their project.

  • APEX

    • Functests failing

    • Virtual deploy -- RDT, Hugepages…  Should we skip during virtual deploy?

    • APEX deployment help -- Aaron has a test setup running and can answer questions.

  • Collectd

    • PRs

    • PRs

  • DMA project would like to have another meeting (possibly at ONS)

  • Did you get your feedback to Alok?  I know I didn’t yet :(.

    • Want to get comments by the 15th

    • Produce a spec update by end of March

    • Have a weekly update

  • VES Update

    • VES Project into ETSI

    • Parts of the project, metric / event definitions, transport

    • Pair things down to what’s important

    • 10’s of collectors at present

  • VES mobile edge platforms

    • CAdvisor plugin for collectd?

    • Maybe try in the Barometer container?

...

  • Should Barometer Graduate? (https://www.opnfv.org/software/technical-project-governance/project-lifecycle)

    • Are we a part of enough scenarios (another installer)?

    • Would be a good recognition of the work done by Barometer

    • Have had good recognition at shows (OpenStack Summit, OPNFV, etc)

    • Bryan would be supportive of applying for graduation

    • No definitive answer, but positive reception

  • Standards Update (Al)

    • Meeting with IFA working group completed work on all measurement content.  Al provided an edit / rewrite of the document and resubmitted.

    • Discussion of GAPs in Baromter

      • https://jira.opnfv.org/browse/BAROMETER-89

  • VES Update

    • Bryan working on Barometer Kubernetes scenario.  Should be ready soon. Barometer as DaemonSet

    • Conversion of VES to gRPC in the testing phase.

  • Development Update

    • Ansible scripts submitted to Gerrit

    • Clarification that plugins not in collectd yet should still make it into Barometer / Fraser

  • (MS5) Scenario integration and feature freeze -- 03/02/18

  • Good discussion on “What’s next for Barometer”

    • Scope expansion -- Should Barometer move beyond metrics / events to policy

    • Scope continuation into container space --

  • OPNFV Barometer people going to ONS in March

    • Aaron

    • Al

    • Bryan

    • ??

...