Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
HD-Chapter:IoT
-
HD-Enabler:IDAS
Description
Responsible:
Bitergia Team <fiware-testing@bitergia.com>
Description:
On a previous email in response to another issue, Carlos Ralli Ucendo commented:
For installing the software we encourage you to wait for the above-described re-factorization to happen (IoT Agents will be provided in Jan 2015 together with installation documents). however, you may try to deploy your own image please login in our Cloud at https://cloud.lab.fi-ware.org , then go to the images folder (https://cloud.lab.fi-ware.org/#nova/images/) and then select the one called ³eidas-sbc-img² and deploy it for your own usage.
We've tried to use the suggested image eidas-sbc-img to create an instance to make some tests of the platform, but, though the instance seems to start, and appears as running on the cloud portal, we still have no access to it.
The instance has the keypair and security group to allow ssh access. Once started, the instance is assigned an internal IP (10.0.8.x) and after waiting a few minutes (just in case the boot process is slow) there's still no access to the instance (from another instance). We've also tried to run an nmap from another instance, but this results in no data from the instance.
This is from the instance with the floating IP to another running instance:
root@sandbox:~# nmap -P0 10.0.5.228 Starting Nmap 6.40 ( http://nmap.org ) at 2014-11-17 13:26 CET Nmap scan report for test-idm.novalocal (10.0.5.228) Host is up (0.00051s latency). Not shown: 999 closed ports PORT STATE SERVICE 22/tcp open ssh MAC Address: FA:16:3E:69:01:1F (Unknown) Nmap done: 1 IP address (1 host up) scanned in 30.25 seconds
And this is to the IDAS instance:
root@sandbox:~# nmap -P0 10.0.8.73
Starting Nmap 6.40 ( http://nmap.org ) at 2014-11-17 13:27 CET
Nmap done: 1 IP address (0 hosts up) scanned in 0.44 seconds
We thought that maybe it was a problem with the image format (AMI), because trying to create instances with other of the available AMI images yield the same result, but some of them do work as expected, so maybe its something wrong with the image.
Could you check the image?
Tested GE(s):
IDAS
Environment:
FIWARE Lab
Instance:
Own instance on cloud.lab.fi-ware.org
–
David Muriel.
_______________________________________________
Fiware-tech-help mailing list
Fiware-tech-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-tech-help
Activity
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
108d 2h 11m | 1 | Carlos Ralli Ucendo | 05/Mar/15 4:24 PM | |||||
|
28s | 1 | Carlos Ralli Ucendo | 05/Mar/15 4:24 PM | |||||
|
18h 25m | 1 | Carlos Ralli Ucendo | 06/Mar/15 10:49 AM |
| Fix Version/s | 2021 [ 12600 ] |
| HD-Enabler | IDAS [ 10884 ] | |
| HD-Chapter | IoT [ 10839 ] |
| Summary | FIWARE.Request.Lab.IoT.IDAS.ImageAvailableNotWorking | FIWARE.Request.Tech.IoT.IDAS.ImageAvailableNotWorking |
| Summary | FIWARE.Bug.IoT.IDAS.ImageAvailableNotWorking | FIWARE.Request.Lab.IoT.IDAS.ImageAvailableNotWorking |
| Resolution | Done [ 10000 ] | |
| Status | Answered [ 10104 ] | Closed [ 6 ] |
| Summary | [Fiware-tech-help] [Chp - IoT][IDAS] IDAS image available on cloud.lab.fi-ware.org is not working | FIWARE.Bug.IoT.IDAS.ImageAvailableNotWorking |
| Status | In Progress [ 3 ] | Answered [ 10104 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Component/s | FIWARE-TECH-HELP [ 10278 ] |
| Attachment | vnc-eidas-sbc-img-error.jpg [ 12499 ] |
We've been able to access the instance console through vnc. It seems the instance does not even reach the image boot screen.
| Assignee | Carlos Ralli Ucendo [ ralli ] |
| Field | Original Value | New Value |
|---|---|---|
| Description |
Responsible: Bitergia Team <fiware-testing@bitergia.com> Description: On a previous email in response to another issue, Carlos Ralli Ucendo commented: > For installing the software we encourage you to wait for the above-described re-factorization to happen (IoT Agents will be provided in Jan 2015 together with installation documents). however, you may try to deploy your own image please login in our Cloud at https://cloud.lab.fi-ware.org , then go to the images folder (https://cloud.lab.fi-ware.org/#nova/images/) and then select the one called ³eidas-sbc-img² and deploy it for your own usage. We've tried to use the suggested image eidas-sbc-img to create an instance to make some tests of the platform, but, though the instance seems to start, and appears as running on the cloud portal, we still have no access to it. The instance has the keypair and security group to allow ssh access. Once started, the instance is assigned an internal IP (10.0.8.x) and after waiting a few minutes (just in case the boot process is slow) there's still no access to the instance (from another instance). We've also tried to run an nmap from another instance, but this results in no data from the instance. This is from the instance with the floating IP to another running instance: > root@sandbox:~# nmap -P0 10.0.5.228 > > Starting Nmap 6.40 ( http://nmap.org ) at 2014-11-17 13:26 CET > Nmap scan report for test-idm.novalocal (10.0.5.228) > Host is up (0.00051s latency). > Not shown: 999 closed ports > PORT STATE SERVICE > 22/tcp open ssh > MAC Address: FA:16:3E:69:01:1F (Unknown) > > Nmap done: 1 IP address (1 host up) scanned in 30.25 seconds And this is to the IDAS instance: > root@sandbox:~# nmap -P0 10.0.8.73 > > Starting Nmap 6.40 ( http://nmap.org ) at 2014-11-17 13:27 CET > Nmap done: 1 IP address (0 hosts up) scanned in 0.44 seconds We thought that maybe it was a problem with the image format (AMI), because trying to create instances with other of the available AMI images yield the same result, but some of them do work as expected, so maybe its something wrong with the image. Could you check the image? Tested GE(s): IDAS Environment: FIWARE Lab Instance: Own instance on cloud.lab.fi-ware.org -- David Muriel. _______________________________________________ Fiware-tech-help mailing list Fiware-tech-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-tech-help |
Responsible: Bitergia Team <fiware-testing@bitergia.com> Description: On a previous email in response to another issue, Carlos Ralli Ucendo commented: bq. For installing the software we encourage you to wait for the above-described re-factorization to happen (IoT Agents will be provided in Jan 2015 together with installation documents). however, you may try to deploy your own image please login in our Cloud at https://cloud.lab.fi-ware.org , then go to the images folder (https://cloud.lab.fi-ware.org/#nova/images/) and then select the one called ³eidas-sbc-img² and deploy it for your own usage. We've tried to use the suggested image eidas-sbc-img to create an instance to make some tests of the platform, but, though the instance seems to start, and appears as running on the cloud portal, we still have no access to it. The instance has the keypair and security group to allow ssh access. Once started, the instance is assigned an internal IP (10.0.8.x) and after waiting a few minutes (just in case the boot process is slow) there's still no access to the instance (from another instance). We've also tried to run an nmap from another instance, but this results in no data from the instance. This is from the instance with the floating IP to another running instance: {code} root@sandbox:~# nmap -P0 10.0.5.228 Starting Nmap 6.40 ( http://nmap.org ) at 2014-11-17 13:26 CET Nmap scan report for test-idm.novalocal (10.0.5.228) Host is up (0.00051s latency). Not shown: 999 closed ports PORT STATE SERVICE 22/tcp open ssh MAC Address: FA:16:3E:69:01:1F (Unknown) Nmap done: 1 IP address (1 host up) scanned in 30.25 seconds {code} And this is to the IDAS instance: {code} root@sandbox:~# nmap -P0 10.0.8.73 Starting Nmap 6.40 ( http://nmap.org ) at 2014-11-17 13:27 CET Nmap done: 1 IP address (0 hosts up) scanned in 0.44 seconds {code} We thought that maybe it was a problem with the image format (AMI), because trying to create instances with other of the available AMI images yield the same result, but some of them do work as expected, so maybe its something wrong with the image. Could you check the image? Tested GE(s): IDAS Environment: FIWARE Lab Instance: Own instance on cloud.lab.fi-ware.org -- David Muriel. _______________________________________________ Fiware-tech-help mailing list Fiware-tech-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-tech-help |
David,
As said in my previous communication, we are significantly improving IDAS because of the installation process. Therefore, please use IDAS as a service as described in the catalogue and stay tuned for the new installation process to be published at the end of the next release 4.2 (end of April).
Best regards,