Hello Pablo,
1) This is the result of the command : SophiaAntipolis2
2) This is the query return when adding line :
Check Monasca recent metadata for region... Could not find these items:
curl -s -S -X GET -H "Accept: application/json" -H "X-Auth-Token:
8daeba15b555460891eaf9e3a08561c0"
"http://130.206.112.3:8070/v2.0/metrics/measurements?name=region.pool_ip&dimensions=region:SophiaAntipolis2&start_time=2016-09-08T07:05:57Z&merge_metrics=true"
Best Regards,
____________________________
*LEFEUVRE Sébastien*
TAS France - WTC 1 - K
1300 route des crêtes - 06560 Valbonne
Tel: +33(0)492945697
Fax: +33(0)492945699
Email: s.lefeuvre at tasgroup.fr <mailto:s.lefeuvre at tasgroup.fr>
Site Web: www.tasfrance.com <http://www.tasfrance.com>
Logo TAS
Le 08/09/2016 à 09:29, PABLO RODRIGUEZ ARCHILLA a écrit :
>
> Good morning, Sébastien.
>
> With respect the error in red, there is a typo in the check script.
> You can fix it just running:
>
> $ sed -i
> 's/REQ_VERSION_CEILOSCA=2015.1-FIWARE/REQ_VERSION_CEILOSCA=2015.1-FIWARE-5.3.3/'
> fiware-check-monitoring.sh
>
> And about the warning, there are a pair of things to check:
>
> 1)What is your region name? Please run this and send me the output
>
> $ awk -F= '/^(os_)?region_name/ {print $2; exit}' /etc/nova/nova.conf
>
> 2)Let’s see the query for metadata. Please edit
> “fiware-check-monitoring.sh” and add this below line 696 (“fi”):
>
> [ -n “$VERBOSE” ] && printf_curl
>
> Then run again the checks, with the --verbose flag. We should see the
> exact curl command to query.
>
> Best regards.
>
> *De:*Sébastien LEFEUVRE [mailto:s.lefeuvre at tasgroup.fr]
> *Enviado el:* miércoles, 7 de septiembre de 2016 15:25
> *Para:* PABLO RODRIGUEZ ARCHILLA
> <pablo.rodriguezarchilla at telefonica.com>; FERNANDO LOPEZ AGUILAR
> <fernando.lopezaguilar at telefonica.com>;
> fiware-lab-help at lists.fiware.org; Pietropaolo Alfonso
> <Alfonso.Pietropaolo at eng.it>
> *CC:* Daniele Santoro <daniele.santoro at create-net.org>; admin at c4itas.eu
> *Asunto:* Re: [Fiware-lab-federation-nodes] New release 5.4.2 of
> FIWARE Monitoring
>
> Hello Pablo,
>
> I have to wait a few more minutes.
>
> I have the result below regarding VM Checks now :
>
> Check Monasca recent measurements for active VM
> 56e96cc4-df3d-4536-8f9e-c3b38e94ebc4... OK (13: cpu_util disk.capacity
> disk.usage instance memory memory.usage memory_util vcpus name host
> status image_ref instance_type)
> Check Monasca recent measurements for active VM
> 8a72365b-afe2-4388-b9e3-2dc777d8e060... OK (13: cpu_util disk.capacity
> disk.usage instance memory memory.usage memory_util vcpus name host
> status image_ref instance_type)
> Check Monasca recent measurements for active VM
> d0ed6534-a3b4-4182-b0d2-cdad96b82a52... OK (13: cpu_util disk.capacity
> disk.usage instance memory memory.usage memory_util vcpus name host
> status image_ref instance_type)
> Check Monasca recent measurements for active VM
> f1e8f465-f045-4cc9-8c6e-995c95b88572... OK (13: cpu_util disk.capacity
> disk.usage instance memory memory.usage memory_util vcpus name host
> status image_ref instance_type)
> Check Monasca recent measurements for active VM
> 12ab2d9f-f07b-4bab-956f-322ffed26e00... OK (13: cpu_util disk.capacity
> disk.usage instance memory memory.usage memory_util vcpus name host
> status image_ref instance_type)
> Check Monasca recent measurements for active VM
> 11f17aca-902c-4637-9010-f68b05698471... OK (13: cpu_util disk.capacity
> disk.usage instance memory memory.usage memory_util vcpus name host
> status image_ref instance_type)
> Check Monasca recent measurements for active VM
> ca2ec9bf-5d7e-4e32-9c2c-62519445378d... OK (13: cpu_util disk.capacity
> disk.usage instance memory memory.usage memory_util vcpus name host
> status image_ref instance_type)
> Check Monasca recent measurements for active VM
> 14088b24-d82f-4cc1-a33a-34610cc53e85... OK (13: cpu_util disk.capacity
> disk.usage instance memory memory.usage memory_util vcpus name host
> status image_ref instance_type)
> Check Monasca recent measurements for active VM
> 4985ec48-0d86-4ba4-8afc-f9b5fb3223bd... OK (13: cpu_util disk.capacity
> disk.usage instance memory memory.usage memory_util vcpus name host
> status image_ref instance_type)
> Check Monasca recent measurements for active VM
> 73fcdf00-2d30-4c29-8563-795a6349f3db... OK (13: cpu_util disk.capacity
> disk.usage instance memory memory.usage memory_util vcpus name host
> status image_ref instance_type)
> Check Monasca recent measurements for active VM
> 43c52503-9c0a-4bfa-97c4-15ee5119d22e... OK (13: cpu_util disk.capacity
> disk.usage instance memory memory.usage memory_util vcpus name host
> status image_ref instance_type)
> Check Monasca recent measurements for active VM
> b0909451-a0d2-42d5-a97c-850ac916e1ec... OK (13: cpu_util disk.capacity
> disk.usage instance memory memory.usage memory_util vcpus name host
> status image_ref instance_type)
>
> However, I still got error (only on 1st controller/3) :
> Check Ceilometer plugin for Monasca (Ceilosca)... 2015.1-FIWARE-5.3.3
> found: 2015.1-FIWARE required
> And warning (on 3 controllers/3) :
> Check Monasca recent metadata for region... Could not find these items:
>
> Best Regards
> ____________________________
> *LEFEUVRE Sébastien*
> TAS France - WTC 1 - K
> 1300 route des crêtes - 06560 Valbonne
> Tel: +33(0)492945697
> Fax: +33(0)492945699
> Email: s.lefeuvre at tasgroup.fr <mailto:s.lefeuvre at tasgroup.fr>
> Site Web: www.tasfrance.com <http://www.tasfrance.com>
> Logo TAS
>
> Le 07/09/2016 à 15:07, PABLO RODRIGUEZ ARCHILLA a écrit :
>
> Hi, Sébastien
>
> Tomorrow morning we’ll check this in detail.
>
> In the meanwhile, and with respect to */”Could not find these
> measurements: memory_util vcpus”/*… Are you sure you have updated
> the configuration files pipeline.yaml and
> monasca_field_definitions.yaml?
>
> Regards.
>
> *De:*Sébastien LEFEUVRE [mailto:s.lefeuvre at tasgroup.fr]
> *Enviado el:* miércoles, 7 de septiembre de 2016 14:43
> *Para:* FERNANDO LOPEZ AGUILAR
> <fernando.lopezaguilar at telefonica.com>
> <mailto:fernando.lopezaguilar at telefonica.com>;
> fiware-lab-help at lists.fiware.org
> <mailto:fiware-lab-help at lists.fiware.org>; Pietropaolo Alfonso
> <Alfonso.Pietropaolo at eng.it> <mailto:Alfonso.Pietropaolo at eng.it>
> *CC:* PABLO RODRIGUEZ ARCHILLA
> <pablo.rodriguezarchilla at telefonica.com>
> <mailto:pablo.rodriguezarchilla at telefonica.com>; Daniele Santoro
> <daniele.santoro at create-net.org>
> <mailto:daniele.santoro at create-net.org>; admin at c4itas.eu
> <mailto:admin at c4itas.eu>
> *Asunto:* Re: [Fiware-lab-federation-nodes] New release 5.4.2 of
> FIWARE Monitoring
>
> Hello Fernando,
>
> Regarding the new Ceilometer - Monasca release below, I follow the
> process but when launching the "./fiware-check-monitoring.sh
> --verbose" script I get the result below :
>
> */FIWARE Lab Monitoring System, release v5.4.2
> [Considering measurements within last 60 minutes]/**/
>
> /**/Check Python interpreter... OK (2.7.6 at /usr/bin/python)
> Check Monasca Agent installation... OK (1.1.21-FIWARE at /opt/monasca)
> Check Monasca Agent configuration... OK
> (/etc/monasca/agent/agent.yaml)
> Check Monasca Agent configuration region... OK
> Check Monasca Agent configuration hostname... controller-1.c4itas.eu
> Check Monasca Agent logfile... /var/log/monasca/agent/forwarder.log
> Check Monasca API URL... http://130.206.112.3:8070/v2.0
> Check Monasca Keystone URL... http://cloud.lab.fiware.org:4731/v3
> Check Monasca Agent username... ceilometer-c4i
> Check Monasca Agent password... ****************
> Check Monasca Agent polling frequency... 600 seconds
> Check Monasca Agent credentials for 'monasca_user' role... OK
> Check Ceilometer polling frequency... 600 seconds
> Check Ceilometer central agent logfile...
> /var/log/ceilometer/ceilometer-agent-central.log
> Check Ceilometer installation path and version... OK (2015.1.1 at
> /usr/lib/python2.7/dist-packages/ceilometer)/**/
> /**/Check Ceilometer plugin for Monasca (Ceilosca)...
> 2015.1-FIWARE-5.3.3 found: 2015.1-FIWARE required/**/
> /**/Check Ceilometer region pollster version... OK (1.0.3)
> Check Ceilometer region pollster class...
> ceilometer.region.region.RegionPollster
> Check Ceilometer publisher for Monasca...
> ceilometer.publisher.monasca_metric_filter.MonascaMetricFilter
> Check Ceilometer storage driver for Monasca...
> ceilometer.storage.impl_monasca_filtered.Connection
> Check Ceilometer entry points at this node... OK
> (poll.central|RegionPollster publisher|MonascaPublisher
> metering.storage|monasca_filtered:Connection)
> Check Ceilometer configuration at this node... OK
> Check Ceilosca configuration at this node... OK
> Check last poll from region pollster at this node... 2016-09-07
> 12:35:26.690 UTC
> Check Monasca metrics for region... OK (4: region.used_ip
> region.pool_ip region.allocated_ip region.sanity_status)/**/
> /**/Check Monasca recent metadata for region... Could not find
> these items:/**/
> /**/Check Monasca recent measurements for region.used_ip... OK (25
> measurements)
> Check Monasca recent measurements for region.pool_ip... OK (25
> measurements)
> Check Monasca recent measurements for region.allocated_ip... OK
> (25 measurements)
> Check Monasca recent measurements for region.sanity_status... OK
> (2 measurements)
> Check last poll from image pollster at this node... 2016-09-07
> 12:35:24.630 UTC
> Check Monasca metrics for image... OK (86 metrics out or 60 images)
> Check Monasca recent measurements for image... OK (10001
> measurements, 86 metrics)
> Check list of compute nodes... compute-2.c4itas.eu
> compute-1.c4itas.eu compute-3.c4itas.eu
> Check execution of remote commands at compute nodes... OK (ssh)
> Check Ceilometer polling frequency at compute node
> compute-2.c4itas.eu... 600 seconds
> Check Ceilometer polling frequency at compute node
> compute-1.c4itas.eu... 600 seconds
> Check Ceilometer polling frequency at compute node
> compute-3.c4itas.eu... 600 seconds
> Check Ceilometer entry points at compute node
> compute-2.c4itas.eu... OK (compute.info cpu memory.usage
> disk.usage disk.capacity)
> Check Ceilometer entry points at compute node
> compute-1.c4itas.eu... OK (compute.info cpu memory.usage
> disk.usage disk.capacity)
> Check Ceilometer entry points at compute node
> compute-3.c4itas.eu... OK (compute.info cpu memory.usage
> disk.usage disk.capacity)
> Check Ceilometer host pollster class at compute node
> compute-2.c4itas.eu... ceilometer.compute.pollsters.host.HostPollster
> Check Ceilometer host pollster class at compute node
> compute-1.c4itas.eu... ceilometer.compute.pollsters.host.HostPollster
> Check Ceilometer host pollster class at compute node
> compute-3.c4itas.eu... ceilometer.compute.pollsters.host.HostPollster
> Check Ceilometer host pollster version at compute node
> compute-2.c4itas.eu... OK (1.0.1)
> Check Ceilometer host pollster version at compute node
> compute-1.c4itas.eu... OK (1.0.1)
> Check Ceilometer host pollster version at compute node
> compute-3.c4itas.eu... OK (1.0.1)
> Check Ceilometer configuration at compute node
> compute-2.c4itas.eu... OK
> Check Ceilometer configuration at compute node
> compute-1.c4itas.eu... OK
> Check Ceilometer configuration at compute node
> compute-3.c4itas.eu... OK
> Check last poll from host pollster at compute node
> compute-2.c4itas.eu... 2016-09-07 12:35:01.671 UTC
> Check last poll from host pollster at compute node
> compute-1.c4itas.eu... 2016-09-07 12:34:33.525 UTC
> Check last poll from host pollster at compute node
> compute-3.c4itas.eu... 2016-09-07 12:35:10.391 UTC
> Check Monasca recent measurements for compute.node.cpu.percent...
> OK (173 measurements, 3 metrics out of 3 compute nodes)
> Check Monasca recent measurements for compute.node.cpu.now... OK
> (8 measurements, 3 metrics out of 3 compute nodes)
> Check Monasca recent measurements for compute.node.cpu.max... OK
> (8 measurements, 3 metrics out of 3 compute nodes)
> Check Monasca recent measurements for compute.node.cpu.tot... OK
> (8 measurements, 3 metrics out of 3 compute nodes)
> Check Monasca recent measurements for compute.node.ram.now... OK
> (8 measurements, 3 metrics out of 3 compute nodes)
> Check Monasca recent measurements for compute.node.ram.max... OK
> (8 measurements, 3 metrics out of 3 compute nodes)
> Check Monasca recent measurements for compute.node.ram.tot... OK
> (8 measurements, 3 metrics out of 3 compute nodes)
> Check Monasca recent measurements for compute.node.disk.now... OK
> (8 measurements, 3 metrics out of 3 compute nodes)
> Check Monasca recent measurements for compute.node.disk.max... OK
> (8 measurements, 3 metrics out of 3 compute nodes)
> Check Monasca recent measurements for compute.node.disk.tot... OK
> (8 measurements, 3 metrics out of 3 compute nodes)
> Check Monasca metrics for nova-api... OK (3 metrics for nova-api)
> Check Monasca metrics for nova-cert... OK (3 metrics for nova-cert)
> Check Monasca metrics for nova-conductor... OK (3 metrics for
> nova-conductor)
> Check Monasca metrics for nova-consoleauth... OK (3 metrics for
> nova-consoleauth)
> Check Monasca metrics for nova-novncproxy... OK (3 metrics for
> nova-novncproxy)
> Check Monasca metrics for nova-objectstore... OK (3 metrics for
> nova-objectstore)
> Check Monasca metrics for nova-scheduler... OK (3 metrics for
> nova-scheduler)
> Check Monasca metrics for neutron-dhcp-agent... OK (3 metrics for
> neutron-dhcp-agent)
> Check Monasca metrics for neutron-l3-agent... OK (3 metrics for
> neutron-l3-agent)
> Check Monasca metrics for neutron-metadata-agent... OK (3 metrics
> for neutron-metadata-agent)
> Check Monasca metrics for neutron-openvswitch-agent... OK (3
> metrics for neutron-openvswitch-agent)
> Check Monasca metrics for neutron-server... OK (3 metrics for
> neutron-server)
> Check Monasca metrics for cinder-api... OK (3 metrics for cinder-api)
> Check Monasca metrics for cinder-scheduler... OK (3 metrics for
> cinder-scheduler)
> Check Monasca metrics for glance-api... OK (3 metrics for glance-api)
> Check Monasca metrics for glance-registry... OK (3 metrics for
> glance-registry)
> Check Monasca recent measurements for nova-api... OK (118
> measurements, 3 resources)
> * Last measurement for controller-1.c4itas.eu: 49.0,
> * Last measurement for controller-2.c4itas.eu: 49.0,
> * Last measurement for controller-3.c4itas.eu: 49.0,
> Check Monasca recent measurements for nova-cert... OK (118
> measurements, 3 resources)
> * Last measurement for controller-1.c4itas.eu: 1.0,
> * Last measurement for controller-2.c4itas.eu: 1.0,
> * Last measurement for controller-3.c4itas.eu: 1.0,
> Check Monasca recent measurements for nova-conductor... OK (118
> measurements, 3 resources)
> * Last measurement for controller-1.c4itas.eu: 17.0,
> * Last measurement for controller-2.c4itas.eu: 17.0,
> * Last measurement for controller-3.c4itas.eu: 17.0,
> Check Monasca recent measurements for nova-consoleauth... OK (118
> measurements, 3 resources)
> * Last measurement for controller-1.c4itas.eu: 1.0,
> * Last measurement for controller-2.c4itas.eu: 1.0,
> * Last measurement for controller-3.c4itas.eu: 1.0,
> Check Monasca recent measurements for nova-novncproxy... OK (118
> measurements, 3 resources)
> * Last measurement for controller-1.c4itas.eu: 1.0,
> * Last measurement for controller-2.c4itas.eu: 1.0,
> * Last measurement for controller-3.c4itas.eu: 1.0,
> Check Monasca recent measurements for nova-objectstore... OK (118
> measurements, 3 resources)
> * Last measurement for controller-1.c4itas.eu: 1.0,
> * Last measurement for controller-2.c4itas.eu: 1.0,
> * Last measurement for controller-3.c4itas.eu: 1.0,
> Check Monasca recent measurements for nova-scheduler... OK (118
> measurements, 3 resources)
> * Last measurement for controller-1.c4itas.eu: 1.0,
> * Last measurement for controller-2.c4itas.eu: 1.0,
> * Last measurement for controller-3.c4itas.eu: 1.0,
> Check Monasca recent measurements for neutron-dhcp-agent... OK
> (118 measurements, 3 resources)
> * Last measurement for controller-1.c4itas.eu: 1.0,
> * Last measurement for controller-2.c4itas.eu: 1.0,
> * Last measurement for controller-3.c4itas.eu: 1.0,
> Check Monasca recent measurements for neutron-l3-agent... OK (118
> measurements, 3 resources)
> * Last measurement for controller-1.c4itas.eu: 1.0,
> * Last measurement for controller-2.c4itas.eu: 1.0,
> * Last measurement for controller-3.c4itas.eu: 1.0,
> Check Monasca recent measurements for neutron-metadata-agent... OK
> (118 measurements, 3 resources)
> * Last measurement for controller-1.c4itas.eu: 17.0,
> * Last measurement for controller-2.c4itas.eu: 17.0,
> * Last measurement for controller-3.c4itas.eu: 25.0,
> Check Monasca recent measurements for neutron-openvswitch-agent...
> OK (118 measurements, 3 resources)
> * Last measurement for controller-1.c4itas.eu: 1.0,
> * Last measurement for controller-2.c4itas.eu: 1.0,
> * Last measurement for controller-3.c4itas.eu: 1.0,
> Check Monasca recent measurements for neutron-server... OK (118
> measurements, 3 resources)
> * Last measurement for controller-1.c4itas.eu: 38.0,
> * Last measurement for controller-2.c4itas.eu: 38.0,
> * Last measurement for controller-3.c4itas.eu: 38.0,
> Check Monasca recent measurements for cinder-api... OK (118
> measurements, 3 resources)
> * Last measurement for controller-1.c4itas.eu: 17.0,
> * Last measurement for controller-2.c4itas.eu: 17.0,
> * Last measurement for controller-3.c4itas.eu: 17.0,
> Check Monasca recent measurements for cinder-scheduler... OK (118
> measurements, 3 resources)
> * Last measurement for controller-1.c4itas.eu: 1.0,
> * Last measurement for controller-2.c4itas.eu: 1.0,
> * Last measurement for controller-3.c4itas.eu: 1.0,
> Check Monasca recent measurements for glance-api... OK (118
> measurements, 3 resources)
> * Last measurement for controller-1.c4itas.eu: 17.0,
> * Last measurement for controller-2.c4itas.eu: 17.0,
> * Last measurement for controller-3.c4itas.eu: 17.0,
> Check Monasca recent measurements for glance-registry... OK (118
> measurements, 3 resources)
> * Last measurement for controller-1.c4itas.eu: 17.0,
> * Last measurement for controller-2.c4itas.eu: 17.0,
> * Last measurement for controller-3.c4itas.eu: 17.0,
> Check Monasca metrics for active VMs... OK (2496 metrics out or 12
> active VMs)/**/
> /**/Check Monasca recent measurements for active VM
> 56e96cc4-df3d-4536-8f9e-c3b38e94ebc4... Could not find these
> measurements: memory_util vcpus
> Check Monasca recent measurements for active VM
> 8a72365b-afe2-4388-b9e3-2dc777d8e060... Could not find these
> measurements: memory_util vcpus
> Check Monasca recent measurements for active VM
> d0ed6534-a3b4-4182-b0d2-cdad96b82a52... Could not find these
> measurements: memory_util vcpus
> Check Monasca recent measurements for active VM
> f1e8f465-f045-4cc9-8c6e-995c95b88572... Could not find these
> measurements: memory_util vcpus
> Check Monasca recent measurements for active VM
> 12ab2d9f-f07b-4bab-956f-322ffed26e00... Could not find these
> measurements: vcpus
> Check Monasca recent measurements for active VM
> 11f17aca-902c-4637-9010-f68b05698471... Could not find these
> measurements: memory_util vcpus
> Check Monasca recent measurements for active VM
> ca2ec9bf-5d7e-4e32-9c2c-62519445378d... Could not find these
> measurements: memory_util vcpus
> Check Monasca recent measurements for active VM
> 14088b24-d82f-4cc1-a33a-34610cc53e85... Could not find these
> measurements: vcpus
> Check Monasca recent measurements for active VM
> 4985ec48-0d86-4ba4-8afc-f9b5fb3223bd... Could not find these
> measurements: memory_util vcpus
> Check Monasca recent measurements for active VM
> 73fcdf00-2d30-4c29-8563-795a6349f3db... Could not find these
> measurements: memory_util vcpus
> Check Monasca recent measurements for active VM
> 43c52503-9c0a-4bfa-97c4-15ee5119d22e... Could not find these
> measurements: vcpus
> Check Monasca recent measurements for active VM
> b0909451-a0d2-42d5-a97c-850ac916e1ec... Could not find these
> measurements: memory_util vcpus/*
>
> Does I miss something ?
>
> Best Regards,
> ____________________________
> *LEFEUVRE Sébastien*
> TAS France - WTC 1 - K
> 1300 route des crêtes - 06560 Valbonne
> Tel: +33(0)492945697
> Fax: +33(0)492945699
> Email: s.lefeuvre at tasgroup.fr <mailto:s.lefeuvre at tasgroup.fr>
> Site Web: www.tasfrance.com <http://www.tasfrance.com>
> Logo TAS
>
> Le 06/09/2016 à 12:30, FERNANDO LOPEZ AGUILAR a écrit :
>
> Dear FIWARE Lab infrastructure owners,
>
> We would like to inform that a new release 5.4.2 of FIWARE
> Monitoring is available, including new features and fixes for
> most of the known bugs. For this reason, we strongly suggest
> all regions to upgrade to this latest release:
>
> https://github.com/SmartInfrastructures/ceilometer-plugin-fiware/releases/tag/v5.4.2
>
> As you can see in the changelog, there are a number of new
> features and fixes with respect former releases 5.3.3 (June)
> and 5.4.1 (July). For your convenience here is a summary of
> files changed on the latest 2 releases:
>
> - From v5.4.1 to v5.4.2
>
> README.md
>
> compute_pollster/host.py
>
> region/region.py
>
> tools/ceilometer_ha_restart.sh
>
> tools/fiware-check-monitoring.sh
>
> tools/monasca_restart.sh
>
> - From v5.3.3 to v5.4.1
>
> README.md
>
> config/compute/etc/ceilometer/pipeline.yaml
>
> config/controller/etc/ceilometer/monasca_field_definitions.yaml
>
> config/controller/etc/ceilometer/pipeline.yaml
>
> region/OSVersionComponent.py
>
> region/region.py
>
> Depending on your current release, the process to upgrade to
> 5.4.2 would require several steps. As a general rule:
>
> 1) Download files (as a tarball) from
> https://github.com/SmartInfrastructures/ceilometer-plugin-fiware/archive/v5.4.2.tar.gz
> and decompress into a temporal folder.
>
> 2) Copy the "fiware-check-monitoring.sh" script located at
> "tools/" into your preferred working directory (could be
> /root) at every Controller and run it with the "--verbose"
> flag. The script will analyze your environment, checking for:
>
> - Latest version of pollsters
>
> - Latest version of configuration files
>
> - Overall status of monitoring and monitored data
>
> 3) Based on the check script output, you should manually
> replace old files, if needed, or copy new ones, following the
> updated installation guide available here:
>
> https://github.com/SmartInfrastructures/ceilometer-plugin-fiware/blob/v5.4.2/README.md
>
> Locate your installation directory of Ceilometer package
> (usually, pip command shows such information):
>
> # pip show ceilometer
>
> ---
>
> Name: ceilometer
>
> Version: 2015.1.1
>
> Location: /usr/lib/python2.7/dist-packages
>
> We refer to such location as $PYTHON_SITE_PKG. Giving that,
> for sure you'll have to update these files:
>
> At the Compute Nodes:
>
> - compute_pollster/host.py ==>
> <PYTHON_SITE_PKG>/ceilometer/compute/pollsters/host.py
>
> At the Controllers:
>
> - region/region.py ==>
> <PYTHON_SITE_PKG>/ceilometer/region/region.py
>
> And also copy new files:
>
> At the Controllers:
>
> - region/OSVersionComponent.py ==>
> <PYTHON_SITE_PKG>/ceilometer/region/OSVersionComponent.py
>
> Finally, some changes have been introduced in the
> configuration files, and the check script should detect
> whether current configuration files need to be updated. These
> files are involved:
>
> At the Compute Nodes:
>
> - /etc/ceilometer/pipeline.yaml
>
> At the Controllers:
>
> - /etc/ceilometer/pipeline.yaml
>
> - /etc/ceilometer/monasca_field_definitions.yaml
>
> You will find samples for those files at "config/" folder of
> the downloaded files. PLEASE BE CAREFUL when merging the
> sample files with your current configuration files (take into
> account the URLs, the refresh intervals, etc.)
>
> 4) Restart Ceilometer and Monasca Agent to apply changes: see
> details in the documentation or use the new support scripts
> under "tools/".
>
> 5) Finally, run the check script once more to verify the
> installation/upgrade
>
> Last but not least, all regions WHICH ARE STILL USING THE OLD
> MONITORING are strongly suggested to upgrade as soon as
> possible to the v5.4.2 release.
>
> Please send an email to fiware-lab-help at lists.fiware.org
> <mailto:fiware-lab-help at lists.fiware.org> if you encounter any
> problem or if you need help, once that the problem is
> resolved, the FIWARE Ops team will close the ticket and
> proceed with the configuration of the Infographics GUI in
> order to receive data from your new monitoring system.
>
> Finally, please remember that the new Karma calculation will
> include a penalization if the node hasn't installed the new
> monitoring architecture.
>
> Best regards,
>
> FIWARE Ops team
>
> ------------------------------------------------------------------------
>
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su
> destinatario, puede contener información privilegiada o
> confidencial y es para uso exclusivo de la persona o entidad
> de destino. Si no es usted. el destinatario indicado, queda
> notificado de que la lectura, utilización, divulgación y/o
> copia sin autorización puede estar prohibida en virtud de la
> legislación vigente. Si ha recibido este mensaje por error, le
> rogamos que nos lo comunique inmediatamente por esta misma vía
> y proceda a su destrucción.
>
> The information contained in this transmission is privileged
> and confidential information intended only for the use of the
> individual or entity named above. If the reader of this
> message is not the intended recipient, you are hereby notified
> that any dissemination, distribution or copying of this
> communication is strictly prohibited. If you have received
> this transmission in error, do not read it. Please immediately
> reply to the sender that you have received this communication
> in error and then delete it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu
> destinatário, pode conter informação privilegiada ou
> confidencial e é para uso exclusivo da pessoa ou entidade de
> destino. Se não é vossa senhoria o destinatário indicado, fica
> notificado de que a leitura, utilização, divulgação e/ou cópia
> sem autorização pode estar proibida em virtude da legislação
> vigente. Se recebeu esta mensagem por erro, rogamos-lhe que
> nos o comunique imediatamente por esta mesma via e proceda a
> sua destruição
>
>
>
>
> _______________________________________________
>
> Fiware-lab-federation-nodes mailing list
>
> Fiware-lab-federation-nodes at lists.fiware.org
> <mailto:Fiware-lab-federation-nodes at lists.fiware.org>
>
> https://lists.fiware.org/listinfo/fiware-lab-federation-nodes
>
> ------------------------------------------------------------------------
>
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su
> destinatario, puede contener información privilegiada o
> confidencial y es para uso exclusivo de la persona o entidad de
> destino. Si no es usted. el destinatario indicado, queda
> notificado de que la lectura, utilización, divulgación y/o copia
> sin autorización puede estar prohibida en virtud de la legislación
> vigente. Si ha recibido este mensaje por error, le rogamos que nos
> lo comunique inmediatamente por esta misma vía y proceda a su
> destrucción.
>
> The information contained in this transmission is privileged and
> confidential information intended only for the use of the
> individual or entity named above. If the reader of this message is
> not the intended recipient, you are hereby notified that any
> dissemination, distribution or copying of this communication is
> strictly prohibited. If you have received this transmission in
> error, do not read it. Please immediately reply to the sender that
> you have received this communication in error and then delete it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu
> destinatário, pode conter informação privilegiada ou confidencial
> e é para uso exclusivo da pessoa ou entidade de destino. Se não é
> vossa senhoria o destinatário indicado, fica notificado de que a
> leitura, utilização, divulgação e/ou cópia sem autorização pode
> estar proibida em virtude da legislação vigente. Se recebeu esta
> mensagem por erro, rogamos-lhe que nos o comunique imediatamente
> por esta mesma via e proceda a sua destruição
>
>
> ------------------------------------------------------------------------
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su
> destinatario, puede contener información privilegiada o confidencial y
> es para uso exclusivo de la persona o entidad de destino. Si no es
> usted. el destinatario indicado, queda notificado de que la lectura,
> utilización, divulgación y/o copia sin autorización puede estar
> prohibida en virtud de la legislación vigente. Si ha recibido este
> mensaje por error, le rogamos que nos lo comunique inmediatamente por
> esta misma vía y proceda a su destrucción.
>
> The information contained in this transmission is privileged and
> confidential information intended only for the use of the individual
> or entity named above. If the reader of this message is not the
> intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly prohibited.
> If you have received this transmission in error, do not read it.
> Please immediately reply to the sender that you have received this
> communication in error and then delete it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu
> destinatário, pode conter informação privilegiada ou confidencial e é
> para uso exclusivo da pessoa ou entidade de destino. Se não é vossa
> senhoria o destinatário indicado, fica notificado de que a leitura,
> utilização, divulgação e/ou cópia sem autorização pode estar proibida
> em virtude da legislação vigente. Se recebeu esta mensagem por erro,
> rogamos-lhe que nos o comunique imediatamente por esta mesma via e
> proceda a sua destruição
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20160908/f1d2cf22/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: boojdkchilkedjdl.gif
Type: image/gif
Size: 1520 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20160908/f1d2cf22/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1520 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20160908/f1d2cf22/attachment-0001.gif>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy