09/18/2018
- Filed exception for MS5
- Sept 18th meeting for approval
- Gambia release
is - Filed exception for MS5
- behind
- Milestones
: - MS6 9/07/18 (PAST)
- 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.
- Exception request is approved
- MS7 9/21/18
- Last day that projects may request creation of the stable branch for their project.
- Any project not yet branched will be branched by LF.
- Exception request is approved
- We could cherrypick items and create a stable branch.
- MS6 9/07/18 (PAST)
- Agree on "definition of done" →
- Have the Collectd PRs tracked through Barometer showcased thru experimental containers
- Experimental container are WIP
- Need to follow this for individual items in Jira too, update DoD value in every Jira item
- https://jira.opnfv.org/browse/BAROMETER-106
- Available in Gerrit
- https://jira.opnfv.org/browse/BAROMETER-92
- Collectd ovs_stats plugin does not collect dpdk interface statistics if under bond interface
- Tracked with https://github.com/collectd/collectd/issues/2858
- PR submitted --https://github.com/collectd/collectd/pull/2865
- This option seems to be the most popular
- Looking for reviewers and feedback!
- https://gerrit.opnfv.org/gerrit/#/c/61591/1
- Add support for 'collectd-master' container
- Need reviewers
- The CI integration part is WIP, Radek/Emma are following up
- Review: Ansible scripts
- https://gerrit.opnfv.org/gerrit/#/c/61575/
- Need reviews
- Need to have in Gambia
- Release Plan Items
- https://jira.opnfv.org/browse/BAROMETER-99
- Virt plugin enhancement -- VM names
- https://github.com/collectd/collectd/pull/2807
- Milestone 5.9
- Work completed, needs to be merged into collectd
- https://jira.opnfv.org/browse/BAROMETER-96
- Enable OVS-DPDK PMD Statistics
- Some related merges upstream in OVS
- https://github.com/openvswitch/ovs/commit/971f4b394c6e8480300494787fe919869ff3886c
- https://jira.opnfv.org/browse/BAROMETER-99
- Introductions: Vinay Kumar
- Joined with RedHat, Metrics & Monitoring.
- Looking in to Gnocchi, AODH, Ceilometer, etc. Interested in integrating Collectd with OpenStack.
- Introductions: Vinay Kumar
- 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.
- Necessity of gRPC interface for collectd.
- 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
sds- Importance of having “hostname” as uniform reporting instead of IPv4 address:
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
Did new contributors get added?
Yes!
Plugfest (Al Morton)
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…
...