Versions Compared

Old Version 37

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

Saved on

compared with

New Version Current

changes.mady.by.user Emma Foley

Saved on

Key

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

Meeting info can be found in the calendar. Caution, the time in calendar is given in UTC.

Mar 26, 2019

  • This kind of meeting notes is hard to follow. I/we should improve
  • Sunku shared the closed loop platform architecture

Mar 19, 2019

Mar 12, 2019

Mar 05, 2019

Feb 26, 2019

Feb 12, 2019

  • https://wiki.opnfv.org/display/SWREL/Hunter+Scenario+Status scenarios: do we want them?
  • apex integration "planned", but not listed right now.
    • Follow-up with Akhila on that topic
  • docs: what is up to date, and what is not?
  • jenkins
    • hunter jobs missing
  • evolving scope of barometer?
    • into analytics
    • concerned about missing innovation
    • evolution required

January, 29 2019

  • Caution: next meeting will be at 10 am UTC (alternating with late meeting)

January 22, 2019

    • demonstrate SA in a box using a set of metrics/events internally to AT&T to cut down the costs
    • Take it through ECOMP control loop -> then define set of metrics for automation 
    • Alok will share findings as they progress
    • working with Intel team to go through setup details
  • its in line with how TST008 spec written. The spec provides what additional info to be included for a set of technology/feature to go with the plugin

January 15, 2019

  • barometer-kolla integration
  • ves updates still pending
  • alerting via prometheus/alertmanager
    • snmp traps

January 08, 2019

    • ves updates
    • minimal service assurance demo working out-of-the box
    • collectd container on dockerhub is 5.8.0
    • bar-collectd vs. barometer-collectd (duplication, description needed)
    • benchmarking of collectd?

December 18, 2018

December 11, 2018

Lightning Talk Notes

  • What is Barometer?
    • A project for building a scalable metrics platform for NFV environments and enables the monitoring of infrastructure that hosts our virtual network functions (VNFs).
    • We can monitor platform components like CPU, memory, load, cache, thermals, fan speeds, voltages and machine check exceptions
    • We’re including both the tools such as collectd and the installation utilities along with the definition of metrics and events that are critical for NFV infrastructure monitoring, because the tools without definitions is not a solution.
    • Focus is on collection of metrics, not necessarily the storage or analysis of data. We leave that up to higher level orchestration systems to leverage the data for business logic and decision making. We can leverage things like machine learning and big data analytics to provide proactive changes rather than reactive (traditional monitoring), but our involvement in that is at the collection of metrics and events.
    • Standards involvement -- TST_008 / IFA_027
  • Why use barometer?
    • Leverages collectd for metrics and events gathering. It’s robust with a strong upstream community and has been around for several years, meaning that it’s a stable application to build from with a lot of functionality.
    • Extensible through the plugin framework, and we’ve been adding functionality over the last several months to solve for use cases that weren’t previously solved for.
    • Can be used wherever Linux is available, including whitebox switches and routers.
  • What are we solving for?
    • Providing an implementation of collectd in cloud platform environments that are implementing for NFV so that we can find deficiencies and further enhance collectd through the plugin system
  • Who is using barometer?
    • Red Hat is leveraging the work done in the barometer project within the service assurance framework in order to provide the various metrics and events required by telco operators, edge providers, cloud providers, and other highly available environments.
    • Used by both OPNFV Yardstick for test analysis and OPNFV Bottlenecks
  • How can I use barometer?
    • Barometer is being packaged as a Docker container, so it’s easy to install into your environment without a lot of risk.
    • Also have influxdb container image to show an implementation with data storage

December 04, 2018

November 27, 2018

November 20, 2018

  • There's going to be a Plugfest in early January. Unclear if anyone from Barometer is going to attend
  • Release plan discussion
    • Barometer Release Plan
      • Improvements in documentation
      • Add support for alternative TSDB like prometheus
      • apex integration?
      • install mcelog manually/from ansible; Ubuntu 18.04 apparently dropped the daemon from default install
      • change ansible playbooks to allow configuration of "container type" to be installed: master (from collectd master), experimental (collectd master + selected patches), stable (latest collectd release)
      • Barometer cloud native support: gRPC plugin of collectd to integrate with projects like clover

November 13, 2018

...

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

...

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…

October 23, 2018

  • 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

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:
  • Release status
    • Need a stable branch

October 09, 2018

Meeting Minutes:

  • collectd documentation
    • DPDK
      • Is it considered open source?
      • Is there anything specific to DPDK or are they just mirroring standard parameters?
        • I.e. Is there overlap?  
      • Should add DPDK specific metrics!
    • DPDK telemetry
      • DPDKSTATs replacement
      • Maybe have a small presentation at a later date for input.
    • REDFISH?
    • MCELOG
    • RAS – x86 specific
    • RDT – x86 specific

Agenda:

  • Release status
    • Need a stable branch
  • Tour of Prometheus 

October 02, 2018

Meeting minutes:

  • Need a JIRA item for Ansible scripts
    • Remaining documentation for Ansible scripts
    • 1,2 issues – scaling, etc...  
    • One command install
    • Moved to Centos 5.7 / Ubuntu 18.04
    • Show internal – One click install
  • Demo
    • Video – 5 minutes to monitoring your NFVi
  • Prometheus waiting on Ansible
  • Participation in https://openmetrics.io/

Notes from last meeting:

Demo from Barometer:

-       Possibly create a demo and record it?

-       Demo around containers/VM with metrics

-       Float around few ideas, get comments over next calls

-       Find a new way to use Barometer, would be good

-       Demo ideas:

  • Barometer for system tests/debugging.
    • Look at network interfaces, OVS stats, etc., to track whats happening in an openstack deployment
  • Need to know if there are any openstack deployments already available in opnfv pods
  • Have a real time demo to show graphana dashboards in opnfv pods 

Agenda:

...

Virt plugin should be enhanced to provide the following additional details:

...

Image RemovedBAROMETER-99 - Virt plugin enhancement -- VM names OPEN

...

Image RemovedBAROMETER-96 - Enable OVS-DPDK PMD Statistics OPEN

...

Image RemovedBAROMETER-109 - ovs-events link status OPEN

...

The DMA Local Agent will provide the following features:

  • Local processing of metrics – Allows metrics to be sampled at a higher rate than storage rate for detection of short-lived conditions.
  • Runtime configuration of collectd – Collectd configuration can be managed remotely with the Local Agent providing the writing of collectd configuration and collectd restart.
  • Simple OpenStack metadata discovery – Provide runtime information related to the mapping between virtual and physical elements.  The metadata can be attached to metric sent by collectd.

...

Image RemovedBAROMETER-95 - The DMA project will provide additional functional for the Barometer project OPEN

...

Image RemovedBAROMETER-94 - The DMA project will exist as a container separate from the collectd container OPEN

...

The ovs stats plugin collects the right set of data in case the dpdk interfaces are mapped directly under the ovs bridge. But for the use case where a bonding interface is needed underneath the ovs bridge, ovs stats cannot pull the dpdk interface statistics.

 

...

Image RemovedBAROMETER-92 - Collectd ovs_stats plugin does not collect dpdk interface statistics if under bond interface OPEN

...

Updates from last week:

-       Changed the Kolla container to include almost all Collectd plugins, taken from latest stable branch

  • Plugins are still taken from RPM build, relying on release version of Collectd
  • Not included plugins would gaming plugins, etc.
  • This is a great progress

-       No new updates about community release of Collectd

  • Intel team will prioritize backporting once Ansible script work is done

-       Collectd code reviews:

  • Lot of PRs, will take some time
  • The DPDK patch got merged, need to backport to 5.8
  • Sunku will ask the patch author to backport

-       Ansible scripts work:

  • Testing/validation on Ubuntu 16.04, 18.04 & Centos 7.5
  • Centos 7.3 had docker issues, related to docker missing packages
  • Latest docker Images is based on 7.5.3
  • Centos 7.5 images (qcow2) have different naming scheme, very similar to Ubuntu 18.04
  • There shouldn’t be any regressions, upgrading from 7.3 to 7.5.
  • We can look in to if we need to on 7.3
  • Require your help to review as patches are upstreamed

-       Milestone 8 – Oct 30th

  • Its not being pushed back

-       Review help:

  • Have 4 to 5 reviews pending in Barometer gerrit
  • Require reviews
  • Prometheus and Barometer
    • Should Barometer participate in the standardization effort under way in Prometheus.  (Yes!)
          • Driven by Prometheus for data format
          • Mentioned at Fosdem & Prometheus conference
          • Standard is named as open metrics, submitted to IEEE
          • Gone quite far, need 3 implementations of metrics format for this standard
          • Google is doing one implementation, 2nd one by Prometheus community
          • Trying to standardize data exchange format
          • While Prometheus only supports metrics, standards also supports logs.
          • Value of all this info is the correlation part
          • Matthias would send more info.
          • Need to make sure it wont impact our implementations of metrics in hardware/infrastructure level
          • The community is not generally attuned to lower layers.
    • Bring Barometer’s experience in monitoring the infrastructure.
    • End result could be too PaaSy ;)

09/25/2018

Meeting minutes:

Demo from Barometer:

-       Possibly create a demo and record it?

-       Demo around containers/VM with metrics

-       Float around few ideas, get comments over next calls

-       Find a new way to use Barometer, would be good

-       Demo ideas:

  • Barometer for system tests/debugging.
    • Look at network interfaces, OVS stats, etc., to track whats happening in an openstack deployment
  • Need to know if there are any openstack deployments already available in opnfv pods
  • Have a real time demo to show graphana dashboards in opnfv pods

 

Updates:

-       Changed the Kolla container to include almost all Collectd plugins, taken from latest stable branch

  • Plugins are still taken from RPM build, relying on release version of Collectd
  • Not included plugins would gaming plugins, etc.
  • This is a great progress

-       No new updates about community release of Collectd

  • Intel team will prioritize backporting once Ansible script work is done

-       Collectd code reviews:

  • Lot of PRs, will take some time
  • The DPDK patch got merged, need to backport to 5.8
  • Sunku will ask the patch author to backport

-       Ansible scripts work:

  • Testing/validation on Ubuntu 16.04, 18.04 & Centos 7.5
  • Centos 7.3 had docker issues, related to docker missing packages
  • Latest docker Images is based on 7.5.3
  • Centos 7.5 images (qcow2) have different naming scheme, very similar to Ubuntu 18.04
  • There shouldn’t be any regressions, upgrading from 7.3 to 7.5.
  • We can look in to if we need to on 7.3
  • Require your help to review as patches are upstreamed

-       Milestone 8 – Oct 30th

  • Its not being pushed back

-       Review help:

  • Have 4 to 5 reviews pending in Barometer gerrit
  • Require reviews

 

  • Gambia release behindRelease Plan Items
  • https://jira.opnfv.org/browse/BAROMETER-99
  • https://jira.opnfv.org/browse/BAROMETER-96
  • Ansible scripts update
    • https://gerrit.opnfv.org/gerrit/#/c/61575/5
    • Need to have the experimental Barometer container
      • Need a place to send interested parties so they can try out newest features
      • Early feedback is key
      • Showing the host naming in virt plugin in experimental container would be good.
      • If we have hardware, we can have virtualized RDO installed quickly in barometer opnfv pod
        • A simple 1 controller/1 compute node running barometer container each, also on the pod host itself would be good to show metrics collection across all layers.
        • Listing the steps in barometer wiki would be helpful
        • Possibly have a packstack installation on a single machine.
  • Prometheus and Barometer
    • Should Barometer participate in the standardization effort under way in Prometheus.  (Yes!)
          • Driven by Prometheus for data format
          • Mentioned at Fosdem & Prometheus conference
          • Standard is named as open metrics, submitted to IEEE
          • Gone quite far, need 3 implementations of metrics format for this standard
          • Google is doing one implementation, 2nd one by Prometheus community
          • Trying to standardize data exchange format
          • While Prometheus only supports metrics, standards also supports logs.
          • Value of all this info is the correlation part
          • Matthias would send more info.
          • Need to make sure it wont impact our implementations of metrics in hardware/infrastructure level
          • The community is not generally attuned to lower layers.
    • Bring Barometer’s experience in monitoring the infrastructure.
    • End result could be too PaaSy ;)

 

09/18/2018

    • Introductions: Vinay Kumar
      • Joined with RedHat, Metrics & Monitoring.
      • Looking in to Gnocchi, AODH, Ceilometer, etc. Interested in integrating Collectd with OpenStack.
    • Necessity of gRPC interface for collectd.
      • Clover project and cloud native WG have proposal to integrate most of OPNFV projects with gRPC interface.
      • GRPC is hot, good thing is binary format is very compact, while http is very verbose using up a lot of bandwidth
      • ONAP talks a lot on using GRPC instead of kafka
      • No downside on having GRPC
      • Good to float the idea within Collectd community
      • Florian & others added in write_prometheus, to enable cloud native
        • It creates a scrape target
        • Superior from Collectd exporter from Prometheus itself
      • Real key is to provide correlation between app metrics and infrastructure metrics. Have them be in common data definitions & timestamps.
        • Collectd timestamps are when metrics are generated
        • Prometheus timestamp is when it gets scraped
        • There is a disconnect
      • We need to keep reminding CN folks about correlation on time/locality, between virtual/physical
      • Need to check for direct integration between Jaeger and Collectd
      • A list of metrics/capabilities through node_exporter in Prometheus might be helpful.
        • Strengths, missing metrics?
        • Get stuff in to node_exporter?
        • CN folks might know as they are from different community than OpenStack, as there are different tools, etc.
      • Aaron to help us out here to get started! 
      • Al to contribute here.
    • Importance of having “hostname” as uniform reporting instead of IPv4 address:
      • Memcached plugin is special -> provide both hostname & IPv4 address. Opened a PR in PuppetCollectd to fix proper reporting.
      • It would be good to have additional text along with hostname, like rack name, tag datacenters
      • Need to work with plugin authors

September 11, 2018

...

Good discussion last week around what service providers really want to use related to telemetry.  Do they need to install additional agents for monitoring?

  • Node Exporter vs. Collectd vs. No additional agents

    • Not everything is nor will be cloud native -- Providing native poll interfaces may not be possible

    • Node Exporter is the Prometheus / cloud native agent for collecting data from the hardware.

    • Collectd is the historical metrics / events collection agent.  

  • Multi-VIM environments

    • Need a solution across all environments

    • Need a solution for baremetal, switches, SDN, etc...

...

Filed exception for MS5

  • Missed Sept 11th meeting -- Will be covered in next meeting.

...

Gambia release behind

...

Milestones

...

  • Test case implementation completed.

  • Preliminary documentation completed.

  • Complete documentation compliance table for MS6.

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

...

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

  • Any project not yet branched will be branched by LF.

...

https://jira.opnfv.org/browse/BAROMETER-106

  • Available in Gerrit

...

https://jira.opnfv.org/browse/BAROMETER-92

...

https://gerrit.opnfv.org/gerrit/#/c/61591/1

  • Add support for 'collectd-master' container

  • Need reviewers

...

Release Plan Items

September 04, 2018

...

Good discussion around what service providers really want to use related to telemetry

  • Node Exporter vs. Collectd vs. No additional agents

    • Not everything is or will be cloud native

  • Multi-VIM environments

...

Filed exception for MS5

  • In approval process

...

Milestones

...

  • Test case implementation completed.

  • Preliminary documentation completed.

  • Complete documentation compliance table for MS6.

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

...

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

  • Any project not yet branched will be branched by LF.

...

Thanks for the heads up on Doc change Emma

...

https://jira.opnfv.org/browse/BAROMETER-92

...

https://gerrit.opnfv.org/gerrit/#/c/61591/1

  • Add support for 'collectd-master' container

  • Need reviewers

...

Release Plan Items

...

https://jira.opnfv.org/browse/BAROMETER-106

  • Fix functest

  • Waiting internal review

...

https://jira.opnfv.org/browse/BAROMETER-92

...

https://jira.opnfv.org/browse/BAROMETER-98

...

https://jira.opnfv.org/browse/BAROMETER-102

  • 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)

 

08/28/2018

...

Filed exception for MS5

...

Milestones

...

  • Scenario integration completed

  • All scenarios have deploy jobs in OPNFV CI

  • Scenario status page is locked. No new scenarios may be added. However, scenario owners may request the removal of a scenario.

...

  • Test case implementation completed.

  • Preliminary documentation completed.

  • Complete documentation compliance table for MS6.

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

...

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

  • Any project not yet branched will be branched by LF.

...

Dev Updates

08/21/2018

 

08/14/2018

...

Dev Updates

...

https://jira.opnfv.org/browse/BAROMETER-106

  • Waiting internal review

  • Week 33?

...

https://jira.opnfv.org/browse/BAROMETER-92

...

https://jira.opnfv.org/browse/BAROMETER-98

...

https://jira.opnfv.org/browse/BAROMETER-102

  • 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)

...

https://jira.opnfv.org/browse/BAROMETER-96

...

https://jira.opnfv.org/browse/BAROMETER-99

...

https://jira.opnfv.org/browse/BAROMETER-111

  • Red Fish

  • Collectd module completed

...

Upcoming milestones (Update with outcome)

  • MS6 -- August 24

    • Test cases implemented, preliminary documentation completed, and stable branch open

    • Major feature should at least be proposed and partly reviewed at this time.

    • Functest support should be mostly done (tests upstreamed for collectd-plugins), bug fixes are okay after this date but no new tests.

  • MS7 -- September 14

    • Stable branch window close

...

  • Contact maintainers and ask “what can I do to help?”

  • Also, join #collectd on Freenode if possible

  • Won’t make Gambia, given that we would need to provide config, docs, validation in Barometer once it is closed; However, we should continue to help.

...

New RFEs (NEEDINFO)

...

OPNFV Testing Harmonization

...

Self-healing Sig Update

08/07/2018

...

Dev Updates

...

https://jira.opnfv.org/browse/BAROMETER-106

  • Waiting internal review?

...

https://jira.opnfv.org/browse/BAROMETER-92

...

https://jira.opnfv.org/browse/BAROMETER-98

...

https://jira.opnfv.org/browse/BAROMETER-102

  • 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)

...

https://jira.opnfv.org/browse/BAROMETER-96

...

https://jira.opnfv.org/browse/BAROMETER-99

...

https://gerrit.opnfv.org/gerrit/#/c/59209/

...

Upcoming milestones (Update with outcome)

  • MS6 -- August 24

    • Test cases implemented, preliminary documentation completed, and stable branch open

    • Major feature should at least be proposed and partly reviewed at this time.

    • Functest support should be mostly done (tests upstreamed for collectd-plugins), bug fixes are okay after this date but no new tests.

  • MS7 -- September 14

    • Stable branch window close

...

  • Contact maintainers and ask “what can I do to help?”

  • Also, join #collectd on Freenode if possible

  • Won’t make Gambia, given that we would need to provide config, docs, validation in Barometer once it is closed; However, we should continue to help.

...

Barometer-related paper submissions

  • KubeCon

    • Monitoring Tug of War: Matching Cloud Native and Infrastructure Monitoring (Sunku/Aaron)

  • OpenStack

    • DMA Team

    • Barometer on the Edge

  • OpenSource Summit (LinuxCon)

    • Barometer has two Prom dates

  • ONS Europe

    • DMA -- Tomo/Aaron

...

OPNFV Testing Harmonization

...

Self-healing Sig Update

07/30/2018

·        Dev Updates

o   https://jira.opnfv.org/browse/BAROMETER-106

[ELF] Patches created; waiting internal approval to upstream

o   https://gerrit.opnfv.org/gerrit/#/c/59635/

§  Write redis plugin enable

§  Need +1

o   https://gerrit.opnfv.org/gerrit/#/c/59209/

o   Upcoming milestones

§  MS6 -- August 24

·        Test cases implemented, preliminary documentation completed, and stable branch open

·        Need to have development “mostly” complete by then

[ELF] Major feature should at least be proposed and partly reviewed at this time.

Functest support should be mostly done (tests upstreamed for collectd-plugins), bug fixes are okay after this date but no new tests.

§  MS7 -- September 14

·        Stable branch window close

·        Need feedback on the following list of collect plugins

o   https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&component=collectd&known_name=collectd-all&list_id=9166173&product=Red%20Hat%20OpenStack&query_based_on=collectd-all&query_format=advanced

o   Feedback will help prioritize work

·        Need to offer help to collectd to get the next release out (5.9)  

o   Contact maintainers and ask “what can I do to help?”

o   Also, join #collectd on Freenode if possible

[ELF] Not likely to be available for Gambia, given that we would need to provide config, docs, validation in Barometer once it is closed; However, we should continue to help.

·        Openstack voting has begun

o   https://www.openstack.org/summit/berlin-2018/vote-for-speakers/#/22013

o   https://www.openstack.org/summit/berlin-2018/vote-for-speakers/#/22000

[ELF] There was a very short voting period this time around, and it’s already closed

AOB:

-        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/03/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

  • Prometheus / collectd native times stamp

06/12/2018

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

  • 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

    • 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...

05/22/2018

05/08/2018 --

  • Gambia release planning

    • Gambia release will concentrate on maintenance and support of plugins delivered in Fraser release.

    • Need to check on status of ovs-dpdk-stats, ovs-dpdk-events plugins

    • One or two features might be added -- TBD

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

  • Standards

  • VES

  • Prometheus

05/01/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

    • 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?

  • What are tentative development goals for the Gambia release?

...

RPMs / Container build

...

The weekly meeting takes place on Tuesdays at 15:00 Irish Standard time (UTC)

Meeting is held on zoom: https://zoom.us/j/92950950555?pwd=K2tWZWovWXJWTmNuZHIxNGlZWkpHQT09 and IRC #opnfv-meeting.


Standing agenda items

  • TSC updates
  • CI status
  • Release updates
  • Action item review


Next meeting

The next meeting takes place on , at 15h00 UTC (15h00 Ireland/Dublin).

Agenda

  • TSC updates
    • There are some proposed changes the charter to remove the restrictions on membership composition.
  • CI status
    • stable/moselle container jobs are not building/pushing; seems to be a timing issue, the job ran before the stable/moselle
  • Release updates
  • Action item review

2022 Meetings

04-Oct-22

  • TSC updates
  • CI status
  • Release updates
  • Action item review

20-Sept-22

  • TSC updates
  • CI status
    • Moselle container jobs are failing
  • Release updates
    • M2 has been approved
    • M3 is November 8th
    • There was a brief discussion about having a community release manager instead of a LF staff release manager
      • More details will be shared next week about role/responsibility of a community release manager
  • Action item review
    • (Emma) Check on Moselle job failures

13-Sep-22

  • TSC updates
    • TSC elections are coming up; the active contributors list is available: https://wiki.anuket.io/x/NgLxAQ
    • There will be an election to fill the vacant seat left by Cedric Ollivier; timeline TBD, must be run within 30 days of notification
  • CI status
    • Moselle jobs container jobs are failing.
  • Release updates
    • M2 has been pushed to September 20th
  • Action item review

06-Sep-22

  • TSC updates
  • CI status
    • Moselle container jobs are failing
  • Release updates
    • M2 is scheduled for Sept 13
  • Action item review

16-Aug-22

  • TSC updates
    • A new docs project was proposed; scope needs to be clarified and some questions addressed
    • No stable branches were created for moselle for barometer, vineperf or kuberef; Cedric pointed to the solution, and offered to do the final creation step.
  • CI status
    • Moselle jobs exist but are failing because there is no moselle branch
  • Release updates
  • Action item review

19-Jul-22

  • TSC updates
    • release retrospective took place; mostly regarding docs
  • CI status
    • All jobs are passing
  • Release updates
    • Release cycle starting August 2nd
    • M1 is August 16th
  • Action item review

28-Jun-22

  • TSC updates
    • CFP deadline for ONE summit is July 10th
  • CI status
    • All jobs are passing
  • Release updates
  • Action item review

14-Jun-22

  • TSC updates
  • CI status
    • Jobs seem to be working again
  • Release updates
    • Moselle is almost over; branch cutting and job creation pending
    • Nile kickoff has been pushed out to give people a chance to decompress and deal with any delays in Moselle.
  • Action item review

31-May-22

24-May-2022

  • TSC updates
    • Topics are due for developer event in Porto
    • There will be one virtual-only track
  • Release update
    • Today is M4; no action needed - all high priority items are resolved
    • TSC was asked to approve the milestone; there were no objections
  • Ci status
    • All green, but nothing seems to have run recently; barometer-daily-lakelse has not run for over a month; barometer-daily-master has not run for 2 weeks

03-May-2022

  • CI status
    • All green
  • Release update
    • TSC approved M3 today

26-Apr-2022

  • TSC Updates
  • CI status
    • All is green
  • Release updates
    • M3 was push out by 2 weeks
  • Action item review

19-Apr-2022 (Cancelled)

  • TSC Updates
  • CI status
    • All is green
  • Release updates
    • M3 is April 19th
      • High priority Jira issues resolved (closed or assigned to future release)
      • Preliminary documentation completed (confirmed by DOCs team)
  • Action item review

12-Apr-2022

  • TSC Updates
  • CI status
    • All is green
  • Release updates
  • Action item review

05-Apr-2022

  • TSC Updates
    • Airship project is proposed for archiving
  • CI status
    • Everything is green
  • Release updates
    • M3 is mid-April
  • Action item review

22-Mar-2022

15-Mar-2022

08-Mar-2022

01-Mar-2022

  • TSC updates
  • CI status
  • Release updates
    • Reminder from dmcbride to update documentation on what we're planning to do for the release.
    • Plans should include CentOS Stream
    • TODO(Emma) Update release documentation
  • Action item review

22-Feb-2022

15-Feb-2022

  • TSC updates
    • CLA and gitlab migration are under discussion
  • CI status
    • Looks good
  • Release updates
    • Moselle M2 is mid-March
  • Action item review
    • Emma to update meeting time to 2 hours earlier

07-Feb-2022

  • TSC updates
    • Gitlab migration was discussed
  • CI status
    • Everything is working
  • Release updates
    • Moselle M2 is mid March
  • Action item review
    • Update meeting time – proposed to move it 2 hours earlier

25-Jan-2022

18-Jan-2022

  • Release updates
    • Moselle is kicking off
  • CI status
    • All are green!
  • TSC updates
  • Standards updates

11-Jan-2022

  • cancelled

04-Jan-2022

  • Release updates
    • Tasks complete for Lakelse M5
  • CI status
    • All green, and Lakelse jobs are up
  • TSC updates
  • Standards updates

2021 Meetings

14-December-2021

  • Lakelse updates
    • exception approved for barometer m5 until December 17th
  • CI status
    • All green!
  • TSC updates
  • Standards updates

07-December-2021

30-November-2021

  • Lakelse Updates
    • TSC approved M4
  • CI status
    • Everything is passing!
  • TSC updates
  • Standards updates

    • The TST008 update is that the ETSI Editors contacted Al today to say that their editing process (on the approved text) has begun.

23-November-2021

  • Lakelse Updates
    • Release will be early next year
  • CI status
    • Everything is passing!
  • TSC updates
  • Standards updates
    • No comment; remote consensus process closed; Document number updated to NFV(21)000243, and it's now considered "done"; expected actions from editors to update style and references;

16-November-2021

  • Lakelse Updates
    • M4 is up today, which applies to specification projects
    • There was a discussion on moving the release schedule so Lakelse finishes later
  • CI status
    • Everything is passing
  • TSC updates
  • Standards updates

09-November-2021

...

...

...

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

  • 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

  • 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?

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

04/17/2018 --

  • 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

  • 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)

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.

...

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

    • +/73001 will hopefully address these, as the failures both appear to be due to an issue in systems/centos/8/build_base_machine.sh
  • TSC Updates
  • Standards updates
  • Thoth
    • Action(Emma): Investigate collectd failures on POD-18

02-November-2021

26-October-2021

19-October-2021

12-October-2021

05-October-2021

  • Lakelse update
    • M3 is October 19th
  • CI status
    • Everything is passing
  • TSC Updates
    • Nominations are open for the 2022 TSC memberships
  • Standards updates
    • No updates; latest meeting was post-poned
  • Committer clean-up
    • Process for removing committers:- either a committer steps down voluntarily or can be removed by a 2/3 majority vote.
    • Action(Emma) Reach out to Calin about stepping down

28-September-2021

  • Lakelse update
  • CI status
  • TSC Updates
    • Nominations are open for the 2022 TSC memberships
  • Standards updates
    • A complete working group review of the document is happening, then it will be submitted for full approval.
  • Committer clean-up
    • Emma did not check the existing process
    • Emma e-mailed Aaron about stepping down as a committer - he agreed
    • Al e-mailed Maryam about stepping down as committer - she sadly agreed
    • Action(Emma): Check the existing process for removing committers;
    • Action(Emma) Reach out to Calin about stepping down

21-September-2021

31-August-2021

  • Lakelse updates
    • Today is M2 - scope freeze
  • CI status
  • Standards updates
    • The ETSI-NFV test working group accepted the contribution on storage!
  • AoB

24-August-2021

  • Lakelse updates
    • Need to add Lakelse labels to Jira items
  • CI status
  • Standards updates
    • Updated draft of TST-008 to include storage metrics
  • AoB

17-August-2021

  • Lakelse updates:
    • M2 (scope freeze) is  
    • Discussions/triaging/scoping of RA reqs into to Jira items is taking place in the Release meeting for the next 2 weeks.
  • Ci status
    • No status change
  • Standards updates
    • no status change
  • AoB

10-August-2021

  • Lakelse updates:
    • M2 (scope freeze) is  
    • Discussions/triaging/scoping of RA reqs into to Jira items is taking place in the Release meeting for the next 3 weeks.
  • Ci status
    • Everything looks fine (some older jobs are failing, but that's nothing to worry about)
  • Standards updates
    • No updates
  • AoB

03-August-2021

  • Lakelse updates:
    • M2 (scope freeze) is  
    • Discussions/triaging/scoping of RA reqs into to Jira items is taking place in the Release meeting for the next 4 weeks.
  • Ci status
    • barometer-daily-master is working again!
  • Thoth, possible demo/collab, discussion on the weekly tech discuss and weekly AI/ML meeting.
    • Thoth project got approved at this week's TSC!
  • AoB

13-Jul-2021

  • Announcement: Meetings are cancelled the next two weeks for vacation time
  • Lakelse updates:
    • M2 (scope freeze) is  
  • Ci status: barometer-daily-master is mostly working; there's an issue in uploading the artifacts, I've logged a ticket to get it investigated.
  • Gitlab transition:
    • ETA is mid-August
  • AI/ML project, possible demo/collab, discussion on the weekly tech discuss and weekly AI/ML meeting.
  • AoB

06-Jul-2021

Older meetings






Table of Contents

03/20/18 --

  • 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

  • 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

03/13/18 --

  • Functest debug and then power loss ;(

03/06/18 --

  • 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

  • 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?

02/27/18 --

  • Milestone 5 approaching

    • Thanks for the help on Apex and Barometer

    • Tracked down issue with deploy

  • Standards Update

  • VES Update

  • Barometer containers to be part of RDO release

    • Team to work on building Kolla containers

    • AMQP1.0 container being built

02/20/18 --

  • Collectd on Cumulus

    • Open Compute / Networking

  • Standards Updates?

  • VES Updates?

  • Development

    • Apex scenarios are currently failing

    • Ansible script reviews in progress

    • MS5 approaching

  • Barometer next?

02/13/18 --

  • 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

  • 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

    • ??

·         Filed exception for MS5

...