Hi,
may you help this INCENSe SME/Startup?

regards,
P.

Hi,
Thank you for taking the time to check this issue I was having.

When I sent this email I was using a network I created on fiware for testing, named "My_net", where I was having the issue. Now I'm using node-int-net, as sugested in a previous email and it is working fine. I'm being able to access the instances.

Thank you.

Arthur

Date: Fri, 31 Jul 2015 07:37:00 +0100
From: coaches-help-desk-jira@fi-ware.org
To: arthurmvieira@hotmail.com
Subject: [FI-WARE-JIRA] (HELC-905) [Fiware-incense-coaching] Issue with new VMs in Fiware Cloud

Hi
I can see you have two VMs, one with public IP and another with private one. I can access to the one with public IP. So.. what is the problem?
Regards,
Henar
ssh root@130.206.117.94
The authenticity of host '130.206.117.94 (130.206.117.94)' can't be established.
RSA key fingerprint is 86:5d:7e:d8:93:2b:62:74:f8:9c:3f:f7:01:71:c0:cf.
Are you sure you want to continue connecting (yes/no)?

Message Title

FW External User created an issue

Help-Coaches-Desk / HELC-905

[Fiware-incense-coaching] Issue with new VMs in Fiware Cloud

Issue Type:

extRequest

Assignee:

Henar Muñoz

Components:

INCENSe

Created:

24/Jul/15 11:02 AM

Priority:

Major

Reporter:

FW External User

Hello,
I'm contacting because I've been developing our fiware aplication, but I'm having some issues in using Fiware-Lab's Cloud.
I'm not being able to create instances running on a network, sharing security group and keypair, nor with new ones.
I associate the public IP to the new instance, make sure port 22 (and also port 80) on the security group are open and I'm also configuring access to the private key I downloaded, with the command "$ chmod 600 key.pem".
When I try to access the instance through ssh, using the new key, the terminal hangs and gives no response.
More details:
With one older working instance i start to create another:- I create a new security group and open ports 22 and 80 on it. - Then I create a keypair and download the private part. (also tryied with same key and security group of the working instance)- Following, I Launch a new instance, naming it and sellecting a flavor, then, I select the new keypair and security group just created (or old ones), followed by selecting the network already existing. This way both instances will be in the same network and able to comunicate even with only one external IP.

After finnishing the creation of the instance, in Security, I dissociate the public IP from the working instance and associate it to the new instance. So it should be working.

Lastly I go to my terminal, change the file configuration with "$ chmod 600 key.pem" and then try to access the public IP through ssh.At this point the terminal cursor drops one line and hangs there. I can wait for timeout or escape with Ctrl+C.
Normally I would get a message telling me that the server fingerprint has changed. In that case I erase it and make a fresh connection to the new instance.
I tried several images. In the past I was able to creat accessible instances with the same security group and keypair as of the working instance, but didn't try with diferent ones.
I hope this is enough to characterize the issue. If more information is needed please ask.

Thank you
Arthur VieiraGeratriz, Portugal
_______________________________________________
Fiware-incense-coaching mailing list
Fiware-incense-coaching@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-incense-coaching
[Created via e-mail received from: Arthur Vieira <arthurmvieira@hotmail.com>]

Add Comment

This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814)

Hello,
I'm having the same issue again with the Instances created on the Fi-Cloud.

Now I have 3 instances in node-int-net-01. CEP_TD1 and Orion_TD, that I created last week, I believe, are working instances that I'm able to access via ssh.IDAS_TD is a new instance of eidas-sbc-img that I have created today and am not able to access via ssh. When trying to access the instance the terminal either hangs or gives the message "ssh: connect to host 130.206.117.94 port 22: No route to host".
This instance is using it's own ssh keypair and security group. I have ports 22 and 80 opened in this sec. grp.

I tried recreating it several times and have also tried creating other Instances from images I know to work, like cep. And have also tried several keypair and security group combinations. The behaviour was the same.
I will leave this IDAS_TD instance running so you can check the issue, but I may re-associate the external IP to another instance to keep developing with what I have.
If you need more from me, let me know.
Thank you,
Arthur
Date: Fri, 31 Jul 2015 07:37:00 +0100
From: coaches-help-desk-jira@fi-ware.org
To: arthurmvieira@hotmail.com
Subject: [FI-WARE-JIRA] (HELC-905) [Fiware-incense-coaching] Issue with new VMs in Fiware Cloud

Hi
I can see you have two VMs, one with public IP and another with private one. I can access to the one with public IP. So.. what is the problem?
Regards,
Henar
ssh root@130.206.117.94
The authenticity of host '130.206.117.94 (130.206.117.94)' can't be established.
RSA key fingerprint is 86:5d:7e:d8:93:2b:62:74:f8:9c:3f:f7:01:71:c0:cf.
Are you sure you want to continue connecting (yes/no)?

Message Title

FW External User created an issue

Help-Coaches-Desk / HELC-905

[Fiware-incense-coaching] Issue with new VMs in Fiware Cloud

Issue Type:

extRequest

Assignee:

Henar Muñoz

Components:

INCENSe

Created:

24/Jul/15 11:02 AM

Priority:

Major

Reporter:

FW External User

Hello,
I'm contacting because I've been developing our fiware aplication, but I'm having some issues in using Fiware-Lab's Cloud.
I'm not being able to create instances running on a network, sharing security group and keypair, nor with new ones.
I associate the public IP to the new instance, make sure port 22 (and also port 80) on the security group are open and I'm also configuring access to the private key I downloaded, with the command "$ chmod 600 key.pem".
When I try to access the instance through ssh, using the new key, the terminal hangs and gives no response.
More details:
With one older working instance i start to create another:- I create a new security group and open ports 22 and 80 on it. - Then I create a keypair and download the private part. (also tryied with same key and security group of the working instance)- Following, I Launch a new instance, naming it and sellecting a flavor, then, I select the new keypair and security group just created (or old ones), followed by selecting the network already existing. This way both instances will be in the same network and able to comunicate even with only one external IP.

After finnishing the creation of the instance, in Security, I dissociate the public IP from the working instance and associate it to the new instance. So it should be working.

Lastly I go to my terminal, change the file configuration with "$ chmod 600 key.pem" and then try to access the public IP through ssh.At this point the terminal cursor drops one line and hangs there. I can wait for timeout or escape with Ctrl+C.
Normally I would get a message telling me that the server fingerprint has changed. In that case I erase it and make a fresh connection to the new instance.
I tried several images. In the past I was able to creat accessible instances with the same security group and keypair as of the working instance, but didn't try with diferent ones.
I hope this is enough to characterize the issue. If more information is needed please ask.

Thank you
Arthur VieiraGeratriz, Portugal
_______________________________________________
Fiware-incense-coaching mailing list
Fiware-incense-coaching@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-incense-coaching
[Created via e-mail received from: Arthur Vieira <arthurmvieira@hotmail.com>]

Add Comment

This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814)

Hi
The image eidas-sbc-img is not working. I have just set it as private. Thus, you should delete your VM and deploy another image.
Regards,
Henar