If it helps, I have some logs from the: * VES Agent (ves_app.log) * VES Collector (monitor.log and collector.log) * collectd-kafka traffic (stdout from the test kafka consumer)
These could be used to correlate what is sent when, and trace back the lineage of values and timestamps as suggested. But I recommend first we get the Barometer team to describe how that lineage is intended to work – and we can then verify it. Thanks, Bryan Sullivan | AT&T From: MORTON, ALFRED C (AL) Sent: Monday, November 27, 2017 6:19 PM To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>; Aaron Smith <aasm...@redhat.com>; opnfv-tech-discuss@lists.opnfv.org Subject: RE: [opnfv-tech-discuss] [barometer] weekly meeting Hi Aaron, Bryan, and all, I’d like to add a brief discussion to the agenda tomorrow, related to the thread that many project members participated in last week, the subject was: “ves_app.py exception when collecting from multiple collectd clients” In short, I’m interested in the steps that measured results follow to arrive at any VIM, and what information accompanies the results. One of our barometer wiki pages gives the collectd 101, https://wiki.opnfv.org/display/fastpath/Collectd+101 gives the contents of a value list for collectd statistics. The most important ones to this discussion are: • Values • Value length: the number of values in the data set. • Time: timestamp at which the value was collected. • Interval: interval at which to expect a new value. • Host: used to identify the host. As I have mentioned before, TST008 requires that measured values be accompanied by the time they are measured. I now wonder if the collectd Time: when the value was “collected” is close enough to the actual time when the hypervisor reads the meter or gauge and passes the value to libvirtd API & virt plugin to ignore the difference (time error). It could simplify life on earth if the error is small. Please give this a little thought before we meet, thanks! Al From: opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, BRYAN L (BRYAN L) Sent: Monday, November 27, 2017 10:15 AM To: Aaron Smith; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Subject: Re: [opnfv-tech-discuss] [barometer] weekly meeting ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. FYI, I updated the VES tools to build a container for the VES Agent (ves_app.py in the Barometer repo). Using it now with the latest tests for the Models kubernetes stack<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_opnfv_models_tree_master_tools&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=9PvLnmbuYxVL8K1S_AO83wjzC7fo0AZBGYdEs3zRm20&s=VFHdVR23prpLP3WM8l6ddGc2dOP8lgNoudF8ZV61kF8&e=>. Also built the VES Collector as a container. Using my personal docker hub account for now: https://hub.docker.com/u/blsaws/<https://urldefense.proofpoint.com/v2/url?u=https-3A__hub.docker.com_u_blsaws_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=9PvLnmbuYxVL8K1S_AO83wjzC7fo0AZBGYdEs3zRm20&s=VIjaf26ZIEFu4jxa8RH4UynLZvr2yv5ZSSUkZ_dngEE&e=> Scripts that build these containers are in the VES repo: https://github.com/opnfv/ves/tree/master/build<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_opnfv_ves_tree_master_build&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=9PvLnmbuYxVL8K1S_AO83wjzC7fo0AZBGYdEs3zRm20&s=saUZH-BOBsoF5Fx4aFz8dao1WQzO2Y4rehaVMBvbsSs&e=> Still trying to figure out how I can do the same with collectd – having to build collectd and librdkafka at deploy time really extends the test cycle, so it’s a priority. Pretty soon I will be using Cloudify-kubernetes blueprints to deploy the Agent, Collector, and other components (Prometheus, InfluxDB, Grafana) as services on the k8s master node (using labels to deploy them there). Thanks, Bryan Sullivan | AT&T From: opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Aaron Smith Sent: Monday, November 27, 2017 6:37 AM To: opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Subject: [opnfv-tech-discuss] [barometer] weekly meeting 11/21/17 -- Small crowd :) Welcomed a new attendee from the ARMBAND project. Container discussion How are the Barometer containers going to be distributed? Docker hub Contact Fativ about access Need to be careful about the underlying OS and available and assuming what packages are available. Install guide should be detailed and include installation of any required rpms, libraries, etc… For example, Ubuntu / MOSS vs. Ubuntu ISO. How to handle kernel versions? Agenda for tomorrow: More discussion on containers, VES, etc... Aaron -- AARON SMITH SENIOR PRINCIPAL SOFTWARE ENGINEER, NFVPE Red Hat <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.redhat.com_&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=KGNFH2ulYHexpHiZBjrMVlElF-irXzw2lkDJENvu6vE&s=zj6bdbP1GMP77eq5qEdnycizsMUhuBpf3SMTte6T6B4&e=> 314 Littleton Rd, Westford, MA 01886 aasm...@redhat.com<mailto:aasm...@redhat.com> M: 617.877.4814<tel:617.877.4814> [https://www.redhat.com/files/brand/email/sig-redhat.png]<https://urldefense.proofpoint.com/v2/url?u=https-3A__red.ht_sig&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=KGNFH2ulYHexpHiZBjrMVlElF-irXzw2lkDJENvu6vE&s=_j-QPESz9SFm6Z_pLNJx5-TI4lhAK3ZcpSpQ0UQFSR0&e=>
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
