1 ==============================================================================
2 Readme for collectd docker container in barometer project
3 ==============================================================================
5 This text file includes information about environment preparation and
6 deployment collectd in docker container
10 2. SYSTEM REQUIREMENTS
14 ------------------------------------------------------------------------------
17 This Dockerfile provides instruction for building collect in isolated container
19 ------------------------------------------------------------------------------
20 2. SYSTEM REQUIREMENTS
24 ------------------------------------------------------------------------------
27 To build docker container run
28 sudo docker build -f ./docker/barometer-collectd/Dockerfile .
29 from barometer folder.
31 To run builded image run
34 sudo docker run -ti --net=host -v `pwd`/../src/collectd_sample_configs:/opt/collectd/etc/collectd.d \
35 -v /var/run:/var/run -v /tmp:/tmp --privileged <image id> /run_collectd.sh
37 To make some changes run
38 sudo docker run -ti --net=host -v `pwd`/../collectd_sample_configs:/opt/collectd/etc/collectd.d \
39 -v /var/run:/var/run --privileged <image id> /bin/bash
41 /opt/collectd/sbin/collectd -f
43 ------------------------------------------------------------------------------
46 To check if container works properly additional packages should be installed
50 To simulate mcelog message use instruction in http://artifacts.opnfv.org/barometer/docs/index.html#mcelog-plugin
52 git clone https://github.com/andikleen/mce-inject
61 if runs multiple times mcelog service shoud be restarted(cause mcelog make test exits closes mcelog)
64 http://artifacts.opnfv.org/barometer/docs/index.html#virt-plugin
65 Check that libvirtd is running on the remote host
66 systemctl status libvirtd
68 virsh perf instance-00000003
69 sudo virsh perf instance-00000003 --enable cpu_cycles --live
70 sudo virsh perf instance-00000003 --enable cmt --live
71 sudo virsh perf instance-00000003 --enable mbmt --live
72 sudo virsh perf instance-00000003 --enable mbml --live
73 sudo virsh perf instance-00000003 --enable instructions --live
74 sudo virsh perf instance-00000003 --enable cache_references --live
75 sudo virsh perf instance-00000003 --enable cache_mises --live
76 sudo virsh perf instance-00000003 --enable cache_misses --live
79 To successfuly run ovs plugins in Docker you need an ovs instance to connect to
81 sudo yum install -y openvswitch-switch
82 sudo service openvswitch-switch start
83 sudo ovs-vsctl set-manager ptcp:6640
85 Alternatively you can build ovs from source
86 yum -y install make gcc openssl-devel autoconf automake rpm-build \
87 redhat-rpm-config python-devel openssl-devel kernel-devel \
88 kernel-debug-devel libtool wget python-six selinux-policy-devel
89 mkdir -p ~/rpmbuild/SOURCES
91 wget http://openvswitch.org/releases/openvswitch-2.5.3.tar.gz
92 tar xfz openvswitch-2.5.3.tar.gz
93 sed 's/openvswitch-kmod, //g' rhel/openvswitch.spec > rhel/openvswitch_no_kmod.spec
94 rpmbuild -bb --nocheck rhel/openvswitch_no_kmod.spec
96 yum install -y openvswitch-2.5.3-1.x86_64.rpm
97 sudo systemctl start openvswitch.service
98 sudo ovs-vsctl set-manager ptcp:6640
100 To check if connection is successfull please check
102 319efc53-b321-49a9-b628-e8d70f9bd8a9
104 is_connected: true - can be a marker that ovs plugins successfully connected