[Fiware-incense-coaching] blueprint in trento node 2

[Davide Comba]

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

Linkedin
 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-incense-coaching/attachments/20160428/6462d481/attachment.html>