Dear Massimiliano,

I just received the answer to the internal query I sent this morning. The answer is that this is enabled in the Spanish node. Are you talking about a different node?

Best regards,

Miguel
El 14/01/2015 a las 10:03, Massimiliano Nigrelli escribió:
To whom it may concern,
we would need the Open Stack metadata service to be enabled in order to use the Monitoring GE (as suggested by Panos-Synelixis / Pablo-Telefonica......see a couple of e-mails below).

Please let us know when this will be done.

Regards,

Massimiliano

-------- Messaggio Inoltrato --------
Oggetto: RE: Σχετ: Σχετ: R: Σχετ: Monitoring VMs
Data: Tue, 13 Jan 2015 18:12:55 +0000
Mittente: PABLO RODRIGUEZ ARCHILLA <pablo.rodriguezarchilla@telefonica.com><pablo.rodriguezarchilla@telefonica.com>
A: Massimiliano Nigrelli <massimiliano.nigrelli@eng.it><massimiliano.nigrelli@eng.it>
CC: Panos Trakadas <ptrak@synelixis.com><ptrak@synelixis.com>, Leandro Lombardo <leandro.lombardo@eng.it><leandro.lombardo@eng.it>, FERNANDO LOPEZ AGUILAR <fernando.lopezaguilar@telefonica.com><fernando.lopezaguilar@telefonica.com>, 'Pellegrino Dario' <dario.pellegrino@eng.it><dario.pellegrino@eng.it>, Luigi Briguglio <Luigi.Briguglio@eng.it><Luigi.Briguglio@eng.it>, Pasquale Andriani <pasquale.andriani@eng.it><pasquale.andriani@eng.it>, pkarkazis@synelixis.com<pkarkazis@synelixis.com> <pkarkazis@synelixis.com><pkarkazis@synelixis.com>

Sorry for the inconvenience, but some questions need to be clarified:

1) We (TID) are the owners of FIWARE’s Monitoring GEi (the “i” stands for “implementation”). We will be pleased to solve any issue regarding this enabler. Please note that our GEi depends on an existing monitoring tool (for example, Nagios) to monitor the resources, including VMs.

2) Due to several reasons, XIFI (another FI-PPP project related to FIWARE) decided to bypass Nagios or any other monitoring tool for the VMs, and use the DEM module instead: this is Synelixis responsibility and our current recommendation for the monitoring of VMs.

3) In either case, we all depend on the underlying cloud infrastructure (FIWARE Lab) and, particularly, on the OpenStack Metadata Service.

For any issue related to FIWARE Lab Cloud, please refer to http://help.lab.fi-ware.org/. If, as Panos suggests, the metadata service isn’t available, you should open a ticket in FIWARE Lab Support.

Hope this clarifies a little.

Best regards.

–
Pablo Rodríguez Archilla

FIWARE Initiative

(+34) 958 53 79 02 / 91 31 29119

Product Innovation

pablo.rodriguezarchilla@telefonica.com<pablo.rodriguezarchilla@telefonica.com> 

Telefónica I+D

Edificio I+D Armilla (Parque Tecnológico de la Salud), Granada, Spain

Il 09/01/2015 12:55, Panos Trakadas ha scritto:

Hi Leandro,
Happy new year!
It seems that .
Please see this link: Metadata service - OpenStack Cloud Administrator Guide - current<http://docs.openstack.org/admin-guide-cloud/content/section_metadata-service.html> and especially the section "Run the metadata service".
Also, note that metadata service supports two sets of APIs: an OpenStack metadata API and an EC2-compatible API.
At your disposal for further clarifications.
Best regards,
Panos.

Da: Leandro Lombardo leandro.lombardo@eng.it
Inviato: martedì 23 dicembre 2014 12:43
A: 'Panos Trakadas'
Cc: 'FERNANDO LOPEZ AGUILAR'; 'PABLO RODRIGUEZ ARCHILLA'; Massimiliano Nigrelli; 'Pellegrino Dario'; Luigi Briguglio; Pasquale Andriani
Oggetto: R: Σχετ: Monitoring VMs

Hi Panos and Pablo,
thanks for your answer.
I have tried to install DEM monitor in one of our VMs (Ubuntu 12.04.02), apparently the installation is ok but the DEM module does not write on Orion.

@Panos, I have some questions for you.

• Please, find attached the monitoring.cfg file, is this correct? (The private ip of our Orion VM is 10.0.0.90).
• If I try to check open stack metadata API with the “curl http://169.254.169.254/openstack/latest/meta_data.json” I get a result that is different from the output mentioned in the guide ( {"random_seed":"qmsKI/YXTisafsEEueV8J4HZdKPu0yXH…… ):
Is this correct?
root@finesce-wp4-dev-server:~# curl http://169.254.169.254/openstack/latest/meta_data.json
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04

When I have started the vmonitorS service I got the correct message as written in the “PDEM_ver1.0-1.pdf” guide:
root@finesce-wp4-dev-server:~# $sudo service vmonitorS start
Starting NG Service Update ...
Update service started!

The log file is created but nothing is written on Orion. (find attached the monitor.log file)
Where am I wrong?

Thanks in advance
Leandro

Da: Panos Trakadas ptrak@synelixis.com
Inviato: lunedì 22 dicembre 2014 15:16
A: PABLO RODRIGUEZ ARCHILLA; leandro.lombardo@eng.it<leandro.lombardo@eng.it>
Cc: FERNANDO LOPEZ AGUILAR
Oggetto: Σχετ: Monitoring VMs

Hi Leandro,

Passive DEM component is the latest version of DEM.
You can find it here: https://xifisvn.res.eng.it/wp3/software/DEM_Adapter/PDEMv1.0/
Download it, either for Ubuntu or CentOS (depending on the OS of the VMs you want to monitor).
Installation procedure is included in the abovementioned folder.
After installation, please modify the configuration file as mentioned in the instructions.
The whole procedure is straightforward, however, if you need assistance please do not hesitate to contact me.

Best regards,
Panos.

Dear Miguel,
our VMs are deployed on the Spanish node.

So please, tell us what to do next.

Regards,

Massimiliano

–
===============================================================

Massimiliano Nigrelli
Direzione Ricerca e Innovazione - R&D Lab
massimiliano.nigrelli@eng.it

Engineering Ingegneria Informatica S.p.A.
Viale Regione Siciliana, 7275 - 90146 Palermo (Italy)

Phone: +39 091.75.11.847

============================================================

_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help

Dear Massimiliano,

Can you explain me a bit more what is the problem with the metadata? I think it is working. –

@panos - May I ask what requests does the DEM component send to the metadata server? Does that component requiere a minimun version of (Openstack) metadata server? – If I knew the queries needed by the component, I would test wheather the Metadata is working or not.

Thank you all,

Best regards,
José Ignacio.

El 14/01/15 a las 16:21, Massimiliano Nigrelli escribió:
Dear Miguel,
our VMs are deployed on the Spanish node.

So please, tell us what to do next.

Regards,

Massimiliano

Il 14/01/2015 15:35, MIGUEL CARRILLO PACHECO ha scritto:
Dear Massimiliano,

I just received the answer to the internal query I sent this morning. The answer is that this is enabled in the Spanish node. Are you talking about a different node?

Best regards,

Miguel
El 14/01/2015 a las 10:03, Massimiliano Nigrelli escribió:
To whom it may concern,
we would need the Open Stack metadata service to be enabled in order to use the Monitoring GE (as suggested by Panos-Synelixis / Pablo-Telefonica......see a couple of e-mails below).

Please let us know when this will be done.

Regards,

Massimiliano

-------- Messaggio Inoltrato --------
Oggetto: RE: Σχετ: Σχετ: R: Σχετ: Monitoring VMs
Data: Tue, 13 Jan 2015 18:12:55 +0000
Mittente: PABLO RODRIGUEZ ARCHILLA <pablo.rodriguezarchilla@telefonica.com><pablo.rodriguezarchilla@telefonica.com>
A: Massimiliano Nigrelli <massimiliano.nigrelli@eng.it><massimiliano.nigrelli@eng.it>
CC: Panos Trakadas <ptrak@synelixis.com><ptrak@synelixis.com>, Leandro Lombardo <leandro.lombardo@eng.it><leandro.lombardo@eng.it>, FERNANDO LOPEZ AGUILAR <fernando.lopezaguilar@telefonica.com><fernando.lopezaguilar@telefonica.com>, 'Pellegrino Dario' <dario.pellegrino@eng.it><dario.pellegrino@eng.it>, Luigi Briguglio <Luigi.Briguglio@eng.it><Luigi.Briguglio@eng.it>, Pasquale Andriani <pasquale.andriani@eng.it><pasquale.andriani@eng.it>, pkarkazis@synelixis.com<pkarkazis@synelixis.com> <pkarkazis@synelixis.com><pkarkazis@synelixis.com>

Sorry for the inconvenience, but some questions need to be clarified:

1) We (TID) are the owners of FIWARE’s Monitoring GEi (the “i” stands for “implementation”). We will be pleased to solve any issue regarding this enabler. Please note that our GEi depends on an existing monitoring tool (for example, Nagios) to monitor the resources, including VMs.

2) Due to several reasons, XIFI (another FI-PPP project related to FIWARE) decided to bypass Nagios or any other monitoring tool for the VMs, and use the DEM module instead: this is Synelixis responsibility and our current recommendation for the monitoring of VMs.

3) In either case, we all depend on the underlying cloud infrastructure (FIWARE Lab) and, particularly, on the OpenStack Metadata Service.

For any issue related to FIWARE Lab Cloud, please refer to http://help.lab.fi-ware.org/. If, as Panos suggests, the metadata service isn’t available, you should open a ticket in FIWARE Lab Support.

Hope this clarifies a little.

Best regards.

–
Pablo Rodríguez Archilla

FIWARE Initiative

(+34) 958 53 79 02 / 91 31 29119

Product Innovation

pablo.rodriguezarchilla@telefonica.com<pablo.rodriguezarchilla@telefonica.com> 

Telefónica I+D

Edificio I+D Armilla (Parque Tecnológico de la Salud), Granada, Spain

Il 09/01/2015 12:55, Panos Trakadas ha scritto:

Hi Leandro,
Happy new year!
It seems that .
Please see this link: Metadata service - OpenStack Cloud Administrator Guide - current<http://docs.openstack.org/admin-guide-cloud/content/section_metadata-service.html> and especially the section "Run the metadata service".
Also, note that metadata service supports two sets of APIs: an OpenStack metadata API and an EC2-compatible API.
At your disposal for further clarifications.
Best regards,
Panos.

Da: Leandro Lombardo leandro.lombardo@eng.it
Inviato: martedì 23 dicembre 2014 12:43
A: 'Panos Trakadas'
Cc: 'FERNANDO LOPEZ AGUILAR'; 'PABLO RODRIGUEZ ARCHILLA'; Massimiliano Nigrelli; 'Pellegrino Dario'; Luigi Briguglio; Pasquale Andriani
Oggetto: R: Σχετ: Monitoring VMs

Hi Panos and Pablo,
thanks for your answer.
I have tried to install DEM monitor in one of our VMs (Ubuntu 12.04.02), apparently the installation is ok but the DEM module does not write on Orion.

@Panos, I have some questions for you.

• Please, find attached the monitoring.cfg file, is this correct? (The private ip of our Orion VM is 10.0.0.90).
• If I try to check open stack metadata API with the “curl http://169.254.169.254/openstack/latest/meta_data.json” I get a result that is different from the output mentioned in the guide ( {"random_seed":"qmsKI/YXTisafsEEueV8J4HZdKPu0yXH…… ):
Is this correct?
root@finesce-wp4-dev-server:~# curl http://169.254.169.254/openstack/latest/meta_data.json
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04

When I have started the vmonitorS service I got the correct message as written in the “PDEM_ver1.0-1.pdf” guide:
root@finesce-wp4-dev-server:~# $sudo service vmonitorS start
Starting NG Service Update ...
Update service started!

The log file is created but nothing is written on Orion. (find attached the monitor.log file)
Where am I wrong?

Thanks in advance
Leandro

Da: Panos Trakadas ptrak@synelixis.com
Inviato: lunedì 22 dicembre 2014 15:16
A: PABLO RODRIGUEZ ARCHILLA; leandro.lombardo@eng.it<leandro.lombardo@eng.it>
Cc: FERNANDO LOPEZ AGUILAR
Oggetto: Σχετ: Monitoring VMs

Hi Leandro,

Passive DEM component is the latest version of DEM.
You can find it here: https://xifisvn.res.eng.it/wp3/software/DEM_Adapter/PDEMv1.0/
Download it, either for Ubuntu or CentOS (depending on the OS of the VMs you want to monitor).
Installation procedure is included in the abovementioned folder.
After installation, please modify the configuration file as mentioned in the instructions.
The whole procedure is straightforward, however, if you need assistance please do not hesitate to contact me.

Best regards,
Panos.

Hi Jose,
DEM collects data from the VM metadata and send them to the Context Broker.For this particular case, we looked at the configuration file and the log file that ENG sent. The conclusions are the following:1. DEM has been installed correctly (service is running).2. DEM tries to read data from metadata by issuing (curl http://169.254.169.254/openstack/latest/meta_data.json).3. The response is the following (according to ENG email, below):
root@finesce-wp4-dev-server:~# curlhttp://169.254.169.254/openstack/latest/meta_data.json 1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10 2007-12-15 2008-02-01 2008-09-01 2009-04-04
From this response, we assume that probably the cause of the problem is that the OpenStack metadata is not enabled on the Spanish node (only EC2 is enabled by default as far as i know). DEM collects no data and so it does not send to the CB.
Best,
Panos.

Απο: JOSE IGNACIO CARRETERO GUARDE <joseignacio.carreteroguarde@telefonica.com>
Προς: Massimiliano Nigrelli <massimiliano.nigrelli@eng.it>; MIGUEL CARRILLO PACHECO <miguel.carrillopacheco@telefonica.com>; "fiware-lab-help@lists.fi-ware.org" <fiware-lab-help@lists.fi-ware.org>
Κοιν.: "pkarkazis@synelixis.com" <pkarkazis@synelixis.com>; PABLO RODRIGUEZ ARCHILLA <pablo.rodriguezarchilla@telefonica.com>; Leandro Lombardo <Leandro.Lombardo@eng.it>; HENAR MUÑOZ FRUTOS <henar.munozfrutos@telefonica.com>; "Pasquale.Andriani@eng.it" <Pasquale.Andriani@eng.it>; Panos Trakadas <ptrak@synelixis.com>; Pellegrino Dario <Dario.Pellegrino@eng.it>
Στάλθηκε: 5:27 μ.μ. Τετάρτη, 14 Ιανουαρίου 2015
Θέμα: Re: [Fiware-lab-help] [FINESCE WP4] Trying to use Monitoring GE - OpenStack metadata service to be enabled

Dear Massimiliano,

Can you explain me a bit more what is the problem with the metadata? I think it is working. –

@panos - May I ask what requests does the DEM component send to the metadata server? Does that component requiere a minimun version of (Openstack) metadata server? – If I knew the queries needed by the component, I would test wheather the Metadata is working or not.

Thank  you all,

Best regards,
José Ignacio.

El 14/01/15 a las 16:21, Massimiliano Nigrelli escribió:

Dear Miguel,
our VMs are deployed on the Spanish node.

So please, tell us what to do next.

Regards,

Massimiliano

Il 14/01/2015 15:35, MIGUEL CARRILLO PACHECO ha scritto:

Dear Massimiliano,

I just received the answer to the internal query I sent this morning. The answer is that this is enabled in the Spanish node. Are you talking about a different node?

Best regards,

Miguel
El 14/01/2015 a las 10:03, Massimiliano Nigrelli escribió:

To whom it may concern,
we would need the Open Stack metadata service to be enabled in order to use the Monitoring GE (as suggested by Panos-Synelixis / Pablo-Telefonica......see a couple of e-mails below).

Please let us know when this will be done.

Regards,

Massimiliano

-------- Messaggio Inoltrato --------

#yiv7038956400 #yiv7038956400 – filtered

#yiv7038956400 filtered

#yiv7038956400 filtered

#yiv7038956400 filtered

#yiv7038956400 filtered

#yiv7038956400 filtered

#yiv7038956400 filtered

#yiv7038956400 filtered

#yiv7038956400 p.yiv7038956400MsoNormal, #yiv7038956400 li.yiv7038956400MsoNormal, #yiv7038956400 div.yiv7038956400MsoNormal

#yiv7038956400 a:link, #yiv7038956400 span.yiv7038956400MsoHyperlink

#yiv7038956400 a:visited, #yiv7038956400 span.yiv7038956400MsoHyperlinkFollowed

#yiv7038956400 p

#yiv7038956400 pre

#yiv7038956400 p.yiv7038956400MsoAcetate, #yiv7038956400 li.yiv7038956400MsoAcetate, #yiv7038956400 div.yiv7038956400MsoAcetate

#yiv7038956400 p.yiv7038956400MsoListParagraph, #yiv7038956400 li.yiv7038956400MsoListParagraph, #yiv7038956400 div.yiv7038956400MsoListParagraph

#yiv7038956400 span {}#yiv7038956400 p.yiv7038956400msonormal, #yiv7038956400 li.yiv7038956400msonormal, #yiv7038956400 div.yiv7038956400msonormal

#yiv7038956400 p.yiv7038956400msoacetate, #yiv7038956400 li.yiv7038956400msoacetate, #yiv7038956400 div.yiv7038956400msoacetate

#yiv7038956400 p.yiv7038956400msolistparagraph, #yiv7038956400 li.yiv7038956400msolistparagraph, #yiv7038956400 div.yiv7038956400msolistparagraph

#yiv7038956400 p.yiv7038956400msochpdefault, #yiv7038956400 li.yiv7038956400msochpdefault, #yiv7038956400 div.yiv7038956400msochpdefault

#yiv7038956400 p.yiv7038956400msonormal1, #yiv7038956400 li.yiv7038956400msonormal1, #yiv7038956400 div.yiv7038956400msonormal1

#yiv7038956400 p.yiv7038956400msochpdefault1, #yiv7038956400 li.yiv7038956400msochpdefault1, #yiv7038956400 div.yiv7038956400msochpdefault1

#yiv7038956400 span.yiv7038956400msohyperlink {}#yiv7038956400 span.yiv7038956400msohyperlinkfollowed {}#yiv7038956400 span.yiv7038956400msohyperlink1 {}#yiv7038956400 span.yiv7038956400msohyperlinkfollowed1 {}#yiv7038956400 span.yiv7038956400estilocorreo171 {}#yiv7038956400 span.yiv7038956400stilemessaggiodipostaelettronica31 {}#yiv7038956400 span.yiv7038956400stilemessaggiodipostaelettronica32 {}#yiv7038956400 span.yiv7038956400stilemessaggiodipostaelettronica33 {}#yiv7038956400 p.yiv7038956400msonormal2, #yiv7038956400 li.yiv7038956400msonormal2, #yiv7038956400 div.yiv7038956400msonormal2

#yiv7038956400 span.yiv7038956400msohyperlink2

#yiv7038956400 span.yiv7038956400msohyperlinkfollowed2

#yiv7038956400 p.yiv7038956400msoacetate1, #yiv7038956400 li.yiv7038956400msoacetate1, #yiv7038956400 div.yiv7038956400msoacetate1

#yiv7038956400 p.yiv7038956400msolistparagraph1, #yiv7038956400 li.yiv7038956400msolistparagraph1, #yiv7038956400 div.yiv7038956400msolistparagraph1

#yiv7038956400 p.yiv7038956400msochpdefault2, #yiv7038956400 li.yiv7038956400msochpdefault2, #yiv7038956400 div.yiv7038956400msochpdefault2

#yiv7038956400 p.yiv7038956400msonormal11, #yiv7038956400 li.yiv7038956400msonormal11, #yiv7038956400 div.yiv7038956400msonormal11

#yiv7038956400 p.yiv7038956400msochpdefault11, #yiv7038956400 li.yiv7038956400msochpdefault11, #yiv7038956400 div.yiv7038956400msochpdefault11

#yiv7038956400 span.yiv7038956400msohyperlink11

#yiv7038956400 span.yiv7038956400msohyperlinkfollowed11

#yiv7038956400 span.yiv7038956400estilocorreo1711

#yiv7038956400 span.yiv7038956400stilemessaggiodipostaelettronica311

#yiv7038956400 span.yiv7038956400stilemessaggiodipostaelettronica321

#yiv7038956400 span.yiv7038956400stilemessaggiodipostaelettronica331

#yiv7038956400 span.yiv7038956400HTMLconformatoprevioCar

#yiv7038956400 span.yiv7038956400EstiloCorreo49

#yiv7038956400 span.yiv7038956400TextodegloboCar

#yiv7038956400 .yiv7038956400MsoChpDefault

#yiv7038956400 filtered

#yiv7038956400 div.yiv7038956400WordSection1 {}#yiv7038956400 filtered {}#yiv7038956400 filtered

#yiv7038956400 filtered

#yiv7038956400 filtered

#yiv7038956400 filtered

#yiv7038956400 filtered

#yiv7038956400 filtered

#yiv7038956400 filtered

#yiv7038956400 filtered

#yiv7038956400 filtered

#yiv7038956400 ol

#yiv7038956400 ul

#yiv7038956400 Sorry for the inconvenience, but some questions need to be clarified:   1)     We (TID) are the owners of FIWARE’s Monitoring GEi (the “i” stands for “implementation”). We will be pleased to solve any issue regarding this enabler. Please note that our GEi depends on an existing monitoring tool (for example, Nagios) to monitor the resources, including VMs. 2)     Due to several reasons, XIFI (another FI-PPP project related to FIWARE) decided to bypass Nagios or any other monitoring tool for the VMs, and use the DEM module instead: this is Synelixis responsibility and our current recommendation for the monitoring of VMs. 3)     In either case, we all depend on the underlying cloud infrastructure (FIWARE Lab) and, particularly, on the OpenStack Metadata Service.   For any issue related to FIWARE Lab Cloud, please refer tohttp://help.lab.fi-ware.org/. If, as Panos suggests, the metadata service isn’t available, you should open a ticket in FIWARE Lab Support.   Hope this clarifies a little.   Best regards.     –

  Il 09/01/2015 12:55, Panos Trakadas ha scritto:  
Hi Leandro, Happy new year! It seems that     . Please see this link:Metadata service  OpenStack Cloud Administrator Guide   current and especially the section "Run the metadata service". Also, note that metadata service supports two sets of APIs: an OpenStack metadata API and an EC2-compatible API. At your disposal for further clarifications. Best regards, Panos.     Da: Leandro Lombardo leandro.lombardo@eng.it
Inviato: martedì 23 dicembre 2014 12:43
A: 'Panos Trakadas'
Cc: 'FERNANDO LOPEZ AGUILAR'; 'PABLO RODRIGUEZ ARCHILLA'; Massimiliano Nigrelli; 'Pellegrino Dario'; Luigi Briguglio; Pasquale Andriani
Oggetto: R: Σχετ: Monitoring VMs   Hi Panos and Pablo,   thanks for your answer. I have tried to install DEM monitor in one of our VMs (Ubuntu 12.04.02), apparently the installation is ok but the DEM module does not write on Orion.   @Panos, I have some questions for you.   ·        Please, find attached the monitoring.cfg file, is this correct? (The private ip of our Orion VM is 10.0.0.90). ·        If I try to check open stack metadata API with the “curlhttp://169.254.169.254/openstack/latest/meta_data.json”I get a result that is different from the output mentioned in the guide ({"random_seed":"qmsKI/YXTisafsEEueV8J4HZdKPu0yXH…… ):   Is this correct? root@finesce-wp4-dev-server:_{# curlhttp://169.254.169.254/openstack/latest/meta_data.json 1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10 2007-12-15 2008-02-01 2008-09-01 2009-04-04   When I have started the vmonitorS service I got the correct message as written in the “PDEM_ver1.0-1.pdf”  guide: root@finesce-wp4-dev-server:}# $sudo service vmonitorS start Starting NG Service Update ... Update service started!   The log file is created but  nothing is written on Orion. (find attached the monitor.log file) Where am I wrong?   Thanks in advance Leandro   Da: Panos Trakadas ptrak@synelixis.com
Inviato: lunedì 22 dicembre 2014 15:16
A: PABLO RODRIGUEZ ARCHILLA; leandro.lombardo@eng.it
Cc: FERNANDO LOPEZ AGUILAR
Oggetto: Σχετ: Monitoring VMs   Hi Leandro,   Passive DEM component is the latest version of DEM. You can find it here:https://xifisvn.res.eng.it/wp3/software/DEM_Adapter/PDEMv1.0/ Download it, either for Ubuntu or CentOS (depending on the OS of the VMs you want to monitor). Installation procedure is included in the abovementioned folder. After installation, please modify the configuration file as mentioned in the instructions. The whole procedure is straightforward, however, if you need assistance please do not hesitate to contact me.   Best regards, Panos.   Απο: PABLO RODRIGUEZ ARCHILLA <pablo.rodriguezarchilla@telefonica.com>
Προς: "leandro.lombardo@eng.it" <leandro.lombardo@eng.it>
Κοιν.: Panos Trakadas <ptrak@synelixis.com>; FERNANDO LOPEZ AGUILAR <fernando.lopezaguilar@telefonica.com>
Στάλθηκε: 3:21 μ.μ. Δευτέρα, 22 Δεκεμβρίου 2014
Θέμα: Monitoring VMs   Hi, Leandro.   Related to our discussion regarding issue HELP-1525, let me put my colleagues Panos and Fernando in the loop. First of all, let me quote an excerpt of our conversation to give them some context: “[…] I am going to give you details about the scenario where we are working on FINESCE (which is 2nd phase project, like FITMAN). We have to integrate FIWARE GEs in the architecture of an energy marketplace (which is the output of FINESCE WP4). We have set up a couple of VMs into FI-Lab; there, both all the software developed within FINESCE Wp4 and our “private” instance of GEs (such as ORION or PROTON) are running. We need to increase the number of GEs we have to integrate as our target KPI is very ambitious. We thought we could have used Monitoring GE in order to monitor the state of our private instance of GEs. […]”   In order to monitor instances (VMs), you’ll need theXIFI’s DEM module installed on them, and an instance of Orion Context Broker that will receive monitoring data. @Panos could help you with DEM, while we (Fernando and myself) could give support regarding Context Broker. Please do NOT pay attention toDEM’s architecture design as it is outdated: neither Nagios nor Event Broker nor NGSI Adapter are now required.   “[…] would you provide a panel to be used by FI-Lab users? […]”   Yes. Currently, there are two panels available: theinfographic panel and the status panel. Monitoring data (both current and historical) are processed and stored, and will eventually be accessible for users.   “[…] More, if we would like to monitor the VM where our instance of ORION is running, for instance, would we need to have an agent installed on it? Would you be in charge for the installation? Where would we eventually look for the monitored behavior? Would we need some special credentials to access the monitoring panel? […]”   The aforementioned DEM module is part of a broaderFederation Monitoring component. If you take a look at its data model, the GE’s deployed at particular VMs are “service” objects. I’m not sure if, in this moment, DEM is collecting information about VM’s services (maybe @Panos could clarify).   Hope this explanation helps.   Best regards.       –

   
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    
  – ===============================================================   Massimiliano Nigrelli Direzione Ricerca e Innovazione - R&D Lab massimiliano.nigrelli@eng.it   Engineering Ingegneria Informatica S.p.A. Viale Regione Siciliana, 7275 - 90146 Palermo (Italy)   Phone: +39 091.75.11.847   ============================================================  

– ===============================================================   Massimiliano Nigrelli Direzione Ricerca e Innovazione - R&D Lab massimiliano.nigrelli@eng.it   Engineering Ingegneria Informatica S.p.A. Viale Regione Siciliana, 7275 - 90146 Palermo (Italy)   Phone: +39 091.75.11.847   ============================================================

– ===============================================================   Massimiliano Nigrelli Direzione Ricerca e Innovazione - R&D Lab massimiliano.nigrelli@eng.it   Engineering Ingegneria Informatica S.p.A. Viale Regione Siciliana, 7275 - 90146 Palermo (Italy)   Phone: +39 091.75.11.847   ============================================================

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-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help

–

Please update your address book with my new e-mail address: miguel.carrillopacheco@telefonica.com

----------------------------------------------------------------------
/ _// Miguel Carrillo Pacheco
_/ _/ _/ _/ Telefónica Distrito Telefónica
/ _//_/ _/ _/ Investigación y Edifico Oeste 1, Planta 9
_/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N
/ _// 28050 Madrid (Spain)
Tel: (+34) 91 483 26 77

e-mail: miguel.carrillopacheco@telefonica.com

Follow FIWARE on the net

Website: http://www.fiware.org
Facebook: https://www.facebook.com/eu.fiware
Twitter: http://twitter.com/Fiware
LinkedIn: https://www.linkedin.com/groups/FIWARE-4239932
----------------------------------------------------------------------

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

–
===============================================================

Massimiliano Nigrelli
Direzione Ricerca e Innovazione - R&D Lab
massimiliano.nigrelli@eng.it

Engineering Ingegneria Informatica S.p.A.
Viale Regione Siciliana, 7275 - 90146 Palermo (Italy)

Phone: +39 091.75.11.847

============================================================

_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help

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-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help

The problem is the compatibility. Our version of Openstack is too old, I'm affraid.

Sorry for the inconveniences, but it won't work.

Regards,
José Ignacio.

El 14/01/2015 17:28, Panos Trakadas <ptrak@synelixis.com> escribió:
Hi Jose,

DEM collects data from the VM metadata and send them to the Context Broker.
For this particular case, we looked at the configuration file and the log file that ENG sent. The conclusions are the following:
1. DEM has been installed correctly (service is running).
2. DEM tries to read data from metadata by issuing (curl http://169.254.169.254/openstack/latest/meta_data.json).
3. The response is the following (according to ENG email, below):

root@finesce-wp4-dev-server:~# curl http://169.254.169.254/openstack/latest/meta_data.json
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04

From this response, we assume that probably the cause of the problem is that the OpenStack metadata is not enabled on the Spanish node (only EC2 is enabled by default as far as i know). DEM collects no data and so it does not send to the CB.
Best,
Panos.

Hi Jose,Which release of OpenStack is installed?Panos.

Απο: JOSE IGNACIO CARRETERO GUARDE <joseignacio.carreteroguarde@telefonica.com>
Προς: "fiware-lab-help@lists.fi-ware.org" <fiware-lab-help@lists.fi-ware.org>; Massimiliano Nigrelli <massimiliano.nigrelli@eng.it>; MIGUEL CARRILLO PACHECO <miguel.carrillopacheco@telefonica.com>; Panos Trakadas <ptrak@synelixis.com>
Κοιν.: "Pasquale.Andriani@eng.it" <Pasquale.Andriani@eng.it>; Leandro Lombardo <Leandro.Lombardo@eng.it>; Pellegrino Dario <Dario.Pellegrino@eng.it>; HENAR MUÑOZ FRUTOS <henar.munozfrutos@telefonica.com>; PABLO RODRIGUEZ ARCHILLA <pablo.rodriguezarchilla@telefonica.com>; "pkarkazis@synelixis.com" <pkarkazis@synelixis.com>
Στάλθηκε: 11:36 μ.μ. Τετάρτη, 14 Ιανουαρίου 2015
Θέμα: Re: Σχετ: [Fiware-lab-help] [FINESCE WP4] Trying to use Monitoring GE - OpenStack metadata service to be enabled

The problem is the compatibility. Our version of Openstack is too old, I'm affraid.Sorry for the inconveniences, but it won't work.Regards,
José Ignacio.El 14/01/2015 17:28, Panos Trakadas <ptrak@synelixis.com> escribió:

Hi Jose,
DEM collects data from the VM metadata and send them to the Context Broker.For this particular case, we looked at the configuration file and the log file that ENG sent. The conclusions are the following:1. DEM has been installed correctly (service is running).2. DEM tries to read data from metadata by issuing (curlhttp://169.254.169.254/openstack/latest/meta_data.json).3. The response is the following (according to ENG email, below):
root@finesce-wp4-dev-server:~# curl http://169.254.169.254/openstack/latest/meta_data.json1.02007-01-192007-03-012007-08-292007-10-102007-12-152008-02-012008-09-012009-04-04
From this response, we assume that probably the cause of the problem is that the OpenStack metadata is not enabled on the Spanish node (only EC2 is enabled by default as far as i know). DEM collects no data and so it does not send to the CB.
Best,
Panos.

Απο: JOSE IGNACIO CARRETERO GUARDE <joseignacio.carreteroguarde@telefonica.com>
Προς: Massimiliano Nigrelli <massimiliano.nigrelli@eng.it>; MIGUEL CARRILLO PACHECO <miguel.carrillopacheco@telefonica.com>; "fiware-lab-help@lists.fi-ware.org" <fiware-lab-help@lists.fi-ware.org>
Κοιν.: "pkarkazis@synelixis.com" <pkarkazis@synelixis.com>; PABLO RODRIGUEZ ARCHILLA <pablo.rodriguezarchilla@telefonica.com>; Leandro Lombardo <Leandro.Lombardo@eng.it>; HENAR MUÑOZ FRUTOS <henar.munozfrutos@telefonica.com>; "Pasquale.Andriani@eng.it" <Pasquale.Andriani@eng.it>; Panos Trakadas <ptrak@synelixis.com>; Pellegrino Dario <Dario.Pellegrino@eng.it>
Στάλθηκε: 5:27 μ.μ. Τετάρτη, 14 Ιανουαρίου 2015
Θέμα: Re: [Fiware-lab-help] [FINESCE WP4] Trying to use Monitoring GE - OpenStack metadata service to be enabled

Dear Massimiliano,

Can you explain me a bit more what is the problem with the metadata? I think it is working. –

@panos - May I ask what requests does the DEM component send to the metadata server? Does that component requiere a minimun version of (Openstack) metadata server? – If I knew the queries needed by the component, I would test wheather the Metadata is working or not.

Thank  you all,

Best regards,
José Ignacio.

El 14/01/15 a las 16:21, Massimiliano Nigrelli escribió:

Dear Miguel,
our VMs are deployed on the Spanish node.

So please, tell us what to do next.

Regards,

Massimiliano

Il 14/01/2015 15:35, MIGUEL CARRILLO PACHECO ha scritto:

Dear Massimiliano,

I just received the answer to the internal query I sent this morning. The answer is that this is enabled in the Spanish node. Are you talking about a different node?

Best regards,

Miguel
El 14/01/2015 a las 10:03, Massimiliano Nigrelli escribió:

To whom it may concern,
we would need the Open Stack metadata service to be enabled in order to use the Monitoring GE (as suggested by Panos-Synelixis / Pablo-Telefonica......see a couple of e-mails below).

Please let us know when this will be done.

Regards,

Massimiliano

-------- Messaggio Inoltrato --------

#yiv4260874247 #yiv4260874247 – -- filtered

#yiv4260874247 filtered

#yiv4260874247 filtered

#yiv4260874247 filtered

#yiv4260874247 filtered

#yiv4260874247 filtered

#yiv4260874247 filtered

#yiv4260874247 filtered

#yiv4260874247 p.yiv4260874247MsoNormal, #yiv4260874247 li.yiv4260874247MsoNormal, #yiv4260874247 div.yiv4260874247MsoNormal

#yiv4260874247 a:link, #yiv4260874247 span.yiv4260874247MsoHyperlink

#yiv4260874247 a:visited, #yiv4260874247 span.yiv4260874247MsoHyperlinkFollowed

#yiv4260874247 p

#yiv4260874247 pre

#yiv4260874247 p.yiv4260874247MsoAcetate, #yiv4260874247 li.yiv4260874247MsoAcetate, #yiv4260874247 div.yiv4260874247MsoAcetate

#yiv4260874247 p.yiv4260874247MsoListParagraph, #yiv4260874247 li.yiv4260874247MsoListParagraph, #yiv4260874247 div.yiv4260874247MsoListParagraph

#yiv4260874247 p.yiv4260874247msonormal, #yiv4260874247 li.yiv4260874247msonormal, #yiv4260874247 div.yiv4260874247msonormal

#yiv4260874247 p.yiv4260874247msoacetate, #yiv4260874247 li.yiv4260874247msoacetate, #yiv4260874247 div.yiv4260874247msoacetate

#yiv4260874247 p.yiv4260874247msolistparagraph, #yiv4260874247 li.yiv4260874247msolistparagraph, #yiv4260874247 div.yiv4260874247msolistparagraph

#yiv4260874247 p.yiv4260874247msochpdefault, #yiv4260874247 li.yiv4260874247msochpdefault, #yiv4260874247 div.yiv4260874247msochpdefault

#yiv4260874247 p.yiv4260874247msonormal1, #yiv4260874247 li.yiv4260874247msonormal1, #yiv4260874247 div.yiv4260874247msonormal1

#yiv4260874247 p.yiv4260874247msochpdefault1, #yiv4260874247 li.yiv4260874247msochpdefault1, #yiv4260874247 div.yiv4260874247msochpdefault1

#yiv4260874247 p.yiv4260874247msonormal2, #yiv4260874247 li.yiv4260874247msonormal2, #yiv4260874247 div.yiv4260874247msonormal2

#yiv4260874247 span.yiv4260874247msohyperlink2

#yiv4260874247 span.yiv4260874247msohyperlinkfollowed2

#yiv4260874247 p.yiv4260874247msoacetate1, #yiv4260874247 li.yiv4260874247msoacetate1, #yiv4260874247 div.yiv4260874247msoacetate1

#yiv4260874247 p.yiv4260874247msolistparagraph1, #yiv4260874247 li.yiv4260874247msolistparagraph1, #yiv4260874247 div.yiv4260874247msolistparagraph1

#yiv4260874247 p.yiv4260874247msochpdefault2, #yiv4260874247 li.yiv4260874247msochpdefault2, #yiv4260874247 div.yiv4260874247msochpdefault2

#yiv4260874247 p.yiv4260874247msonormal11, #yiv4260874247 li.yiv4260874247msonormal11, #yiv4260874247 div.yiv4260874247msonormal11

#yiv4260874247 p.yiv4260874247msochpdefault11, #yiv4260874247 li.yiv4260874247msochpdefault11, #yiv4260874247 div.yiv4260874247msochpdefault11

#yiv4260874247 span.yiv4260874247msohyperlink11

#yiv4260874247 span.yiv4260874247msohyperlinkfollowed11

#yiv4260874247 span.yiv4260874247estilocorreo1711

#yiv4260874247 span.yiv4260874247stilemessaggiodipostaelettronica311

#yiv4260874247 span.yiv4260874247stilemessaggiodipostaelettronica321

#yiv4260874247 span.yiv4260874247stilemessaggiodipostaelettronica331

#yiv4260874247 span.yiv4260874247HTMLconformatoprevioCar

#yiv4260874247 span.yiv4260874247EstiloCorreo49

#yiv4260874247 span.yiv4260874247TextodegloboCar

#yiv4260874247 .yiv4260874247MsoChpDefault

#yiv4260874247 filtered

#yiv4260874247 filtered

#yiv4260874247 filtered

#yiv4260874247 filtered

#yiv4260874247 filtered

#yiv4260874247 filtered

#yiv4260874247 filtered

#yiv4260874247 filtered

#yiv4260874247 filtered

#yiv4260874247 filtered

#yiv4260874247 ol

#yiv4260874247 ul

#yiv4260874247 Sorry for the inconvenience, but some questions need to be clarified: 1)     We (TID) are the owners of FIWARE’s Monitoring GEi (the “i” stands for “implementation”). We will be pleased to solve any issue regarding this enabler. Please note that our GEi depends on an existing monitoring tool (for example, Nagios) to monitor the resources, including VMs.2)     Due to several reasons, XIFI (another FI-PPP project related to FIWARE) decided to bypass Nagios or any other monitoring tool for the VMs, and use the DEM module instead: this is Synelixis responsibility and our current recommendation for the monitoring of VMs.3)     In either case, we all depend on the underlying cloud infrastructure (FIWARE Lab) and, particularly, on the OpenStack Metadata Service. For any issue related to FIWARE Lab Cloud, please refer tohttp://help.lab.fi-ware.org/. If, as Panos suggests, the metadata service isn’t available, you should open a ticket in FIWARE Lab Support. Hope this clarifies a little. Best regards.  --

 Il 09/01/2015 12:55, Panos Trakadas ha scritto: 
Hi Leandro,Happy new year!It seems that     .Please see this link:Metadata service  OpenStack Cloud Administrator Guide   current and especially the section "Run the metadata service".Also, note that metadata service supports two sets of APIs: an OpenStack metadata API and an EC2-compatible API.At your disposal for further clarifications.Best regards,Panos.  Da: Leandro Lombardo leandro.lombardo@eng.it
Inviato: martedì 23 dicembre 2014 12:43
A: 'Panos Trakadas'
Cc: 'FERNANDO LOPEZ AGUILAR'; 'PABLO RODRIGUEZ ARCHILLA'; Massimiliano Nigrelli; 'Pellegrino Dario'; Luigi Briguglio; Pasquale Andriani
Oggetto: R: Σχετ: Monitoring VMs Hi Panos and Pablo,  thanks for your answer.I have tried to install DEM monitor in one of our VMs (Ubuntu 12.04.02), apparently the installation is ok but the DEM module does not write on Orion. @Panos, I have some questions for you. ·        Please, find attached the monitoring.cfg file, is this correct? (The private ip of our Orion VM is 10.0.0.90).·        If I try to check open stack metadata API with the “curlhttp://169.254.169.254/openstack/latest/meta_data.json”I get a result that is different from the output mentioned in the guide ({"random_seed":"qmsKI/YXTisafsEEueV8J4HZdKPu0yXH…… ):  Is this correct?root@finesce-wp4-dev-server:_{# curl http://169.254.169.254/openstack/latest/meta_data.json1.02007-01-192007-03-012007-08-292007-10-102007-12-152008-02-012008-09-012009-04-04 When I have started the vmonitorS service I got the correct message as written in the “PDEM_ver1.0-1.pdf”  guide: root@finesce-wp4-dev-server:}# $sudo service vmonitorS startStarting NG Service Update ...Update service started! The log file is created but  nothing is written on Orion. (find attached the monitor.log file)Where am I wrong? Thanks in advanceLeandro Da: Panos Trakadas ptrak@synelixis.com
Inviato: lunedì 22 dicembre 2014 15:16
A: PABLO RODRIGUEZ ARCHILLA; leandro.lombardo@eng.it
Cc: FERNANDO LOPEZ AGUILAR
Oggetto: Σχετ: Monitoring VMs Hi Leandro, Passive DEM component is the latest version of DEM.You can find it here:https://xifisvn.res.eng.it/wp3/software/DEM_Adapter/PDEMv1.0/Download it, either for Ubuntu or CentOS (depending on the OS of the VMs you want to monitor).Installation procedure is included in the abovementioned folder.After installation, please modify the configuration file as mentioned in the instructions.The whole procedure is straightforward, however, if you need assistance please do not hesitate to contact me. Best regards,Panos. Απο: PABLO RODRIGUEZ ARCHILLA <pablo.rodriguezarchilla@telefonica.com>
Προς: "leandro.lombardo@eng.it" <leandro.lombardo@eng.it>
Κοιν.: Panos Trakadas <ptrak@synelixis.com>; FERNANDO LOPEZ AGUILAR <fernando.lopezaguilar@telefonica.com>
Στάλθηκε: 3:21 μ.μ. Δευτέρα, 22 Δεκεμβρίου 2014
Θέμα: Monitoring VMs Hi, Leandro. Related to our discussion regarding issue HELP-1525, let me put my colleagues Panos and Fernando in the loop. First of all, let me quote an excerpt of our conversation to give them some context:“[…] I am going to give you details about the scenario where we are working on FINESCE (which is 2nd phase project, like FITMAN). We have to integrate FIWARE GEs in the architecture of an energy marketplace (which is the output of FINESCE WP4). We have set up a couple of VMs into FI-Lab; there, both all the software developed within FINESCE Wp4 and our “private” instance of GEs (such as ORION or PROTON) are running. We need to increase the number of GEs we have to integrate as our target KPI is very ambitious.We thought we could have used Monitoring GE in order to monitor the state of our private instance of GEs. […]” In order to monitor instances (VMs), you’ll need theXIFI’s DEM module installed on them, and an instance of Orion Context Broker that will receive monitoring data. @Panos could help you with DEM, while we (Fernando and myself) could give support regarding Context Broker. Please do NOT pay attention toDEM’s architecture design as it is outdated: neither Nagios nor Event Broker nor NGSI Adapter are now required. “[…] would you provide a panel to be used by FI-Lab users? […]” Yes. Currently, there are two panels available: theinfographic panel and the status panel. Monitoring data (both current and historical) are processed and stored, and will eventually be accessible for users. “[…] More, if we would like to monitor the VM where our instance of ORION is running, for instance, would we need to have an agent installed on it? Would you be in charge for the installation? Where would we eventually look for the monitored behavior? Would we need some special credentials to access the monitoring panel? […]” The aforementioned DEM module is part of a broaderFederation Monitoring component. If you take a look at its data model, the GE’s deployed at particular VMs are “service” objects. I’m not sure if, in this moment, DEM is collecting information about VM’s services (maybe @Panos could clarify). Hope this explanation helps. Best regards.   --

  
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  
 -- ===============================================================  Massimiliano NigrelliDirezione Ricerca e Innovazione - R&D Labmassimiliano.nigrelli@eng.it  Engineering Ingegneria Informatica S.p.A.Viale Regione Siciliana, 7275 - 90146 Palermo (Italy)  Phone: +39 091.75.11.847  ============================================================ 

– ===============================================================  Massimiliano NigrelliDirezione Ricerca e Innovazione - R&D Labmassimiliano.nigrelli@eng.it  Engineering Ingegneria Informatica S.p.A.Viale Regione Siciliana, 7275 - 90146 Palermo (Italy)  Phone: +39 091.75.11.847  ============================================================

– ===============================================================  Massimiliano NigrelliDirezione Ricerca e Innovazione - R&D Labmassimiliano.nigrelli@eng.it  Engineering Ingegneria Informatica S.p.A.Viale Regione Siciliana, 7275 - 90146 Palermo (Italy)  Phone: +39 091.75.11.847  ============================================================

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-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help

–

Please update your address book with my new e-mail address: miguel.carrillopacheco@telefonica.com

----------------------------------------------------------------------
/ _// Miguel Carrillo Pacheco
_/ _/ _/ _/ Telefónica Distrito Telefónica
/ _//_/ _/ _/ Investigación y Edifico Oeste 1, Planta 9
_/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N
/ _// 28050 Madrid (Spain)
Tel: (+34) 91 483 26 77

e-mail: miguel.carrillopacheco@telefonica.com

Follow FIWARE on the net

Website: http://www.fiware.org
Facebook: https://www.facebook.com/eu.fiware
Twitter: http://twitter.com/Fiware
LinkedIn: https://www.linkedin.com/groups/FIWARE-4239932
----------------------------------------------------------------------

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

–
===============================================================

Massimiliano Nigrelli
Direzione Ricerca e Innovazione - R&D Lab
massimiliano.nigrelli@eng.it

Engineering Ingegneria Informatica S.p.A.
Viale Regione Siciliana, 7275 - 90146 Palermo (Italy)

Phone: +39 091.75.11.847

============================================================

_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help

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

_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help