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
New pull request - https://gerrit.opnfv.org/gerrit/#/c/53805/9
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
Used to be tracked on wiki
We need to track open pull requests and put them on Barometer development update page: https://wiki.opnfv.org/display/fastpath/Barometer+Development+Updates
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)
...