Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
Sender Email:
-
HD-Node:Trento
Description
After the first phase of testing in previous weeks, we have tried to put into practice directly our real case which should send 3-4 data every second measured by our own sensor.
To do this we decided to simulate directly from visual studio the call to Orion and then save to mongodb. We then decide when to use cosmos to store historical data older than one month taking into account performance issues.
We followed this webminar: https://www.youtube.com/watch?v=tzjCA1Uhhe8, then we tried to make a software in C # (in the video java is used , we could not find the code) that makes the http connection with context broker and send an XML to instruct Orion. But, even in this case could not connect. So we tried to use a blueprint (in the first part of the testing we had done everything right from centos machine with the json file and the mongodb was updated). But, we were unable to connect to the virtual machine.
So we created an instance of blueprint from the 'orion-cluster' to try other ways, but after creating the virtual machine it returns this error:
Status: ERROR
Error: Error installing a product. Description:com.telefonica.euro_iaas.paasmanager.exception.ProductInstallatorException: Error installing product orion-0.19.0 Error invokg SDC to Install Productorion-0.19.0 0.19.0 SDCException. com.telefonica.euro_iaas.sdc.exception.SdcRuntimeException: com.telefonica.euro_iaas.sdc.exception.CanNotCallChefException: Node ooot-orion-1-61b73b is not registered in ChefServer: com.telefonica.euro_iaas.sdc.exception.SdcRuntimeException: com.telefonica.euro_iaas.sdc.exception.CanNotCallChefException: Node ooot-orion-1-61b73b is not registered in ChefServer. com.telefonica.euro_iaas.sdc.exception.SdcRuntimeException: com.telefonica.euro_iaas.sdc.exception.CanNotCallChefException: Node ooot-orion-1-61b73b is not registered in ChefServer
The machine that we used for the first part of the test was saved and put into snapshot, but this morning I we found out that it's gone. Why we couldn't find the snapshot?
In snapshot images are not saved? We saw that we only have 3 instances available and that the blueprint of the tests required all we thought. we'd saved our centos machine and try the orion-cluster machine, thinking that if necessary would be sufficient to delete the machines created by blueprint and restore the saved snapshot machine, isn't this the way forward?
Now we have practically realized the potential of this infrastructure through all the tests, which is very good. Our need right now would be to move from the test phase to the physical resource utilization: We will need to switch to Orion to exploit useful information for managing our tables and our infrastructure directly from c # code (we prefer to use the json because of space, but also in xml can fit).
So this is to kindly ask you how should we proceed? Is it better to start from a clean centos machine and install all or use blueprint to get something that already works? If all goes well from instances of the image of blueprint, what could be causing the blocking error mentioned above?
Thank you for your attention,
Best regards.
Davide Comba|midori
Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-incense-coaching@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-incense-coaching mailing list
Fiware-incense-coaching@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-incense-coaching
[Created via e-mail received from: Davide Comba <davide.comba@midorisrl.eu>]
Issue Links
- relates to
-
HELC-1383
FIWARE.Request.Coach.INCENSe.blueprint in trento node 2
-
- Closed
-
Activity
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
1h 23m | 1 | Trento Node Team | 02/May/16 12:15 PM | |||||
|
5d 21h 49m | 1 | Pasquale Andriani | 09/May/16 10:02 AM | |||||
|
1d 1h 43m | 2 | Trento Node Team | 09/May/16 11:48 AM | |||||
|
1d 23h 43m | 2 | Trento Node Team | 11/May/16 11:32 AM |
| Fix Version/s | 2021 [ 12600 ] |
| Summary | FIWARE.Request.Lab.blueprint in trento node 2. | FIWARE.Request.Lab.Trento.blueprint in trento node 2. |
| HD-Node | Trento [ 10923 ] |
| Resolution | Done [ 10000 ] | |
| Status | Answered [ 10104 ] | Closed [ 6 ] |
| Status | In Progress [ 3 ] | Answered [ 10104 ] |
Hi all,
By analysing the user request the issue seems to be an image-specific issue
or refer to any missing configuration of the instance.
There are no issue on the infrastructure side.
We advice you to forward the support request to the Spanish team
as they are responsible for the Fiware images and related components.
BR
Trento Node Team
Comment by davide.comba@midorisrl.eu :
Good morning, I checked today and the image of our virtual machine is still on the snapshot, so this problem is solved.
I tried to connect to the virtual machine with c# orion at url http://130.206.80.40:1026/ (http://orion.lab.fi-ware.org:1026/) and everything works (I take the token with iDAS, then put it in c # and use it).
Changing the url and put the ip of our real virtual machine, however, does not return to me the token and refuses me the connection.
How can I send the json and populate from outside the architecture of my virtual machine?
For now I have configured orion context Brokers and mongo db, I need to configure also IDAS?
Thanks.
Best regards.
Davide Comba|midori
> Date: Tue, 3 May 2016 11:14:00 +0100
>
| Resolution | Done [ 10000 ] | |
| Status | Closed [ 6 ] | In Progress [ 3 ] |
Comment by davide.comba@midorisrl.eu :
Good morning, I checked today and the image of our virtual machine is still on the snapshot, so this problem is solved.
I tried to connect to the virtual machine with c# orion at url http://130.206.80.40:1026/ (http://orion.lab.fi-ware.org:1026/) and everything works (I take the token with iDAS, then put it in c # and use it).
Changing the url and put the ip of our real virtual machine, however, does not return to me the token and refuses me the connection.
How can I send the json and populate from outside the architecture of my virtual machine?
For now I have configured orion context Brokers and mongo db.
Thanks.
Best regards.
Davide Comba|midori
> Date: Tue, 3 May 2016 11:14:00 +0100
>
| Summary | [Fiware-incense-coaching] blueprint in trento node 2 | FIWARE.Request.Lab.blueprint in trento node 2. |
| HD-Enabler | Unknown [ 10910 ] | |
| HD-Node | Unknown [ 10852 ] |
| Resolution | Done [ 10000 ] | |
| Status | Answered [ 10104 ] | Closed [ 6 ] |
| Status | In Progress [ 3 ] | Answered [ 10104 ] |
The issue has been emailed:
- Time sent: 03/May/16 12:13 PM
- To: davide.comba@midorisrl.eu
- with subject: *(
HELP-6520) [Fiware-incense-coaching] blueprint in trento node 2 *
OK ,
Anyway, as mentioned before, in the image section we made available
the image of your VM form the OLD node in case you may need it (backuped yesterday ).
BR
Trento Node Team
OK,
Anyway, as mentioned before, in the image section we made available
the image of your VM form the OLD node in case you may need it.
BR
Trento Node Team
Comment by davide.comba@midorisrl.eu :
Yes, now we proceed from a clean CentOSand install, and abandon the test of blueprint.
We will need to switch to Orion to exploit useful information for managing our tables and our infrastructure directly from c # code (we prefer to use the json because of space, but also in xml can fit). We followed this webminar: https://www.youtube.com/watch?v=tzjCA1Uhhe8, then we tried to make a software in C # (in the video java is used , we could not find the code) that makes the http connection with context broker and send an XML to instruct Orion, but don't work. Now we retry to recover the situation (because the machine that we have used is deleted) and if don't work we will ask you again!
Davide Comba|midori
> Date: Tue, 3 May 2016 10:23:00 +0100
>
The issue has been emailed:
- Time sent: 03/May/16 11:22 AM
- To: davide.comba@midorisrl.eu
- with subject: *(
HELP-6520) [Fiware-incense-coaching] blueprint in trento node 2 *
This is quite strange.
Anyway, let us know how the testing proceed in case of support.
Can we close the ticket than ?
BR
Trento Node team
This is quite strange.
Anyway, let us know how the testing proceed in case of support.
Can we close the ticket than ?
BR
Trento Node team
Comment by davide.comba@midorisrl.eu :
As written in the request, the other day we followed the same procedure, but in the morning of the day after the snapshot was gone, so we deleted the test machines and restored what we were using to avoid the risk of losing it. Now we have made another instance snapshot and proceed with testing.
Davide Comba|midori
> Date: Tue, 3 May 2016 09:52:00 +0100
> From: jira-help-desk@fi-ware.org
> To: davide.comba@midorisrl.eu
> Subject: [FIWARE-JIRA] (HELP-6520) [Fiware-incense-coaching] blueprint in trento node 2
>
>
>
The issue has been emailed:
- Time sent: 03/May/16 10:51 AM
- To: davide.comba@midorisrl.eu
- with subject: *(
HELP-6520) [Fiware-incense-coaching] blueprint in trento node 2 *
Hi Davide,
The snapshot of the instances or volumes will appear in the "snapshot" section.
In this case, we made the snapshot of your previous vm and from it created an image, that's why it appears in the "images" section. This is the correct migration procedure.
Please inform us if you need further help ?
BR
Trento Node Team
Hi Davide,
The snapshot of the instances or volumes will appear in the "snapshot" section.
In this case, we made the snapshot of your previous vm and from it created an image, that's why it appears in the "images" section. This is the correct migration procedure.
Please inform us if you need further help ?
BR
Trento Node Team
Comment by davide.comba@midorisrl.eu :
Good, I understand: if I create a snapshot the image of my instance appear in the 'Image' section and not in 'Snapshot' section. Correct?
Davide Comba|midori
> Date: Mon, 2 May 2016 16:40:00 +0100
> From: jira-help-desk@fi-ware.org
> To: davide.comba@midorisrl.eu
> Subject: [FIWARE-JIRA] (HELP-6520) [Fiware-incense-coaching] blueprint in trento node 2
>
>
>
The issue has been emailed:
- Time sent: 02/May/16 5:39 PM
- To: davide.comba@midorisrl.eu
- with subject: *(
HELP-6520) [Fiware-incense-coaching] blueprint in trento node 2 *
Hi Davide,
We managed to get a snapshot from your vm,centos_midori, from the "old" node and created the snapshot in the new node and will be available in the "images" section.
You can use it to redeplo your instance as in the "old" node.
Waiting for your feedback,
BR
Trento Node Team
Hi Davide,
We managed to get a snapshot from your vm,centos_midori, from the "old" node
and created the snapshot in the new node and will be available in the "images" section.
You can use it to redeplo your instance as in the "old" node.
Waiting for your feedback,
BR
Trento Node Team
Comment by davide.comba@midorisrl.eu :
Yes, this morning I have deleted all the machines created by blueprint and I have mounted a new instance from our originale image, because the snapshop probably don't work correctly and today the image on old trento node are delete if I understand correctly.
Regards
Davide Comba|midori
> Date: Mon, 2 May 2016 13:28:00 +0100
>
| Sender Email | davide.comba@midorisrl.eu |
The issue has been emailed:
- Time sent: 02/May/16 2:27 PM
- To: davide.comba@midorisrl.eu
- with subject: *(
HELP-6520) [Fiware-incense-coaching] blueprint in trento node 2 *
Hi Davide,
We have checked your instance:
centos_midori_big_explain | 898dd676d12e42088963fa632761b73b | ACTIVE | - | Running | node-int-net-01=192.168.111.21, 185.38.252.58 |
it is Active and btw with no problem in ssh accessing.
$ ssh root@185.38.252.58
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
Can you confirm ?
Regards
Trento Node team
Hi Davide,
We have checked your instance:
centos_midori_big_explain | 898dd676d12e42088963fa632761b73b | ACTIVE | - | Running | node-int-net-01=192.168.111.21, 185.38.252.58 |
it is Active and btw with no problem in ssh accessing.
$ ssh root@185.38.252.58
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
Can you confirm ?
Regards
Trento Node team
| Status | Open [ 1 ] | In Progress [ 3 ] |
The issue has been emailed:
- Time sent: 02/May/16 12:15 PM
- To: davide.comba@midorisrl.eu
- with subject: *(
HELP-6520) [Fiware-incense-coaching] blueprint in trento node 2 *
Hi all,
If you would like to deploy a blueprint, but successively facing problems it is better to open a ticket to the Spain Team that are the people in charge of the blueprint feature.
Otherwise, if you prefer to start from a clean CentOSand install what you need, we can provide you support.
In order to connect to the VMs you should insert in the sec-group-rules used the port 22 as a rule.
Waiting for your answer
Regards
Trento Node Team
Hi all,
If you would like to deploy a blueprint, but successively facing problems it is better to open a ticket to the Spain Team that are the people in charge of the blueprint feature.
Otherwise, if you prefer to start from a clean CentOSand install what you need, we can provide you support.
In order to connect to the VMs you should insert in the sec-group-rules used the port 22 as a rule.
Waiting for your answer
Regards
Trento Node Team
| Assignee | Trento Node Team [ trentonodeteam ] |
Hi, may you help this INCENSe SME to solve their issue?
Thanks in advance,
P.
| HD-Enabler | Unknown [ 10910 ] | |
| HD-Node | Unknown [ 10852 ] |
The issue has been emailed:
HELP-6520) FIWARE.Request.Lab.blueprint in trento node 2. *Hi all,
By analysing the user request the issue seems to be an image-specific issue
or refer to any missing configuration of the instance.
There are no issue on the infrastructure side.
We advice you to forward the support request to the Spanish team
as they are responsible for the Fiware images and related components.
BR
Trento Node Team