Nicola
Have you tried docker-machine ssh (https://docs.docker.com/machine/reference/ssh/) ?
--Ken

Comment by nicola.prunella@terasrl.it :

Hi Ken,

first of all I have followed this: http://simple-docker-hosting-on-fiware-cloud.readthedocs.io/en/latest/install/index.html

Then:
1.
root@default:/mnt/sdb3/fiware# docker-machine version
docker-machine version 0.6.0, build e27fb87
root@default:/mnt/sdb3/fiware# export OS_REGION_NAME='Spain2'
root@default:/mnt/sdb3/fiware# export OS_TENANT_NAME='lprunella cloud'
root@default:/mnt/sdb3/fiware# export OS_USERNAME='nicola.prunella@terasrl.it'
root@default:/mnt/sdb3/fiware# export OS_PASSWORD='Psynergia1'
root@default:/mnt/sdb3/fiware# export OS_AUTH_URL='http://cloud.lab.fi-ware.org:
4730/v2.0/'
root@default:/mnt/sdb3/fiware# export OS_AUTH_STRATEGY='keystone'
root@default:/mnt/sdb3/fiware# docker-machine create -d openstack --openstack-ss
h-user="ubuntu" --openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14
.04" -openstack-net-name="node-int-net-01" --openstack-floatingip-pool="public
ext-net-01" --openstack-sec-groups="docker-machine-sg" docker-host
Creating CA: /root/.docker/machine/certs/ca.pem
Creating client certificate: /root/.docker/machine/certs/cert.pem
Running pre-create checks...
Creating machine...
(docker-host) Creating machine...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with ubuntu(upstart)...
Installing Docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: docker-machine env docker-host

2.
root@default:/mnt/sdb3/fiware# docker-machine env docker-host
Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "130.206.122.75:2376": dial tcp 130.206.122.75:2376: i/o timeout
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which will stop running containers.

3.
root@default:/mnt/sdb3/fiware# docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
6432e0ccba2d: Pull complete
95f1eedc264a: Pull complete
Digest: sha256:548e9719abe62684ac7f01eea38cb5b0cf467cfe67c58b83fe87ba96674a4cdd
Status: Downloaded newer image for hello-world:latest

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
1. The Docker client contacted the Docker daemon.
2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
3. The Docker daemon created a new container from that image which runs the
executable that produces the output you are currently reading.
4. The Docker daemon streamed that output to the Docker client, which sent it
to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker Hub account:
https://hub.docker.com

For more examples and ideas, visit:
https://docs.docker.com/engine/userguide/

As you can see the second step goes into error , however the docker-host is up and running and it respond to docker run hello-world

Thank you

----Messaggio originale----
Da: Help-Desk jira-help-desk@fi-ware.org
Inviato: giovedì 4 agosto 2016 11:32
A: nicola.prunella@terasrl.it
Cc: antonio.sacchetti@terasrl.it; antonio.lobefaro@terasrl.it; massimiliano.siliberti@terasrl.it
Oggetto: [FIWARE-JIRA] (HELP-6903) FIWARE.Request.Lab.ssh.

From FIWARE JIRA - Main Help Desk ----

-------------------------------------------------------------------------------
Comments:

Kenneth Nagin - Today 12:31 PM
------------------
Nicola
Have you tried docker-machine ssh (https://docs.docker.com/machine/reference/ssh/) ?
--Ken

Pasquale Andriani - 26/Jul/16 12:55 PM
------------------
Dear Kennet, I'm re-assigning this ticket as suggested by Josè.
May you help this INCENCe SME in using Docker? Please find the problem described in the previous comments.

Thanks in advance,
P.

José Ignacio Carretero Guarde - 25/Jul/16 2:58 PM
------------------
--openstack-private-key-file="id_rsa_priv.ppk"

The .ppk key is just to be used with putty. docker-machine, as far as I know, used the original id_rsa key. — However, if you have problems with the enabler, you could also ask the GEOwner (http://catalogue.fiware.org/enablers/docker) as I'm not an expert on "docker machine".

Regards,
José Ignacio.

Pasquale Andriani - 22/Jul/16 7:10 PM
------------------
Hi Josè, it seems that the problem is not solved yet. May you follow up with some more hint for Nicola?

Thanks in advance,
P.

FW External User - 20/Jul/16 5:43 PM
------------------
Comment by nicola.prunella@terasrl.it :

Hi,

1. i have allocated new floating ip

2. i have already generated a key pair ( id_rsa, id_rsa.pub) and this keys are located at /root/.ssh/

3. now i import public key at the Nova database with the command:

/root/.docker/machine/machines# nova keypair-add --pub_key /root/.ssh/id_rsa.pub KEY_NAME

4. To ensure that the key pair has been successfully imported:

root@formica-VirtualBox:~/.docker/machine/machines# nova keypair-list

---------------------------------------------------------+

---------------------------------------------------------+

---------------------------------------------------------+

5. with puttygen i produce id_rsa_priv.ppk from id_rsa

6. root@formica-VirtualBox:~/.docker/machine/machines# ls

id_rsa_priv.ppk id_rsa.pub

docker-machine create -d openstack

--openstack-ssh-user="ubuntu"

--openstack-flavor-id="2"

--openstack-image-name="base_ubuntu_14.04"

--openstack-net-name="node-int-net-01"

--openstack-floatingip-pool="public-ext-net-01"

--openstack-sec-groups="docker-machine-sg"

--openstack-private-key-file="id_rsa_priv.ppk"

--openstack-keypair-name="KEY_NAME" docker-host

Running pre-create checks...

Creating machine...

(docker-host) Creating machine...

Waiting for machine to be running, this may take a few minutes...

Detecting operating system of created instance...

Waiting for SSH to be available...

Error creating machine: Error detecting OS: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded

r

Best regards

Nicola

Da: Help-Desk jira-help-desk@fi-ware.org
Inviato: mercoledì 20 luglio 2016 12:52
A: nicola.prunella@terasrl.it
Oggetto: [FIWARE-JIRA] (HELP-6903) FIWARE.Request.Lab.ssh.

Hi,

The assignation of the floating IP to the VM and the fact that It didn't finished, could have been a temporary problem with Openstack, which can usually be corrected removing and adding again the IP to the server.

Docker Machine deploys VMs and it install docker-engine inside the VMs, and it works.

Regards,
José Ignacio.

<https://jira.fiware.org/secure/ViewProfile.jspa?name=fw.ext.user> FW External User created an issue

<https://jira.fiware.org/browse/HELP> Help-Desk / <https://jira.fiware.org/browse/HELP-6903> extRequest <https://jira.fiware.org/browse/HELP-6903> HELP-6903

<https://jira.fiware.org/browse/HELP-6903> FIWARE.Request.Lab.ssh.

Issue Type:

extRequest <https://jira.fiware.org/images/icons/issuetypes/defect.png> extRequest

Assignee:

<https://jira.fiware.org/secure/ViewProfile.jspa?name=jicg> José Ignacio Carretero Guarde

Components:

FIWARE-LAB-HELP

Created:

12/Jul/16 1:11 PM

Priority:

Major <https://jira.fiware.org/images/icons/priorities/major.png> Major

Reporter:

<https://jira.fiware.org/secure/ViewProfile.jspa?name=fw.ext.user> FW External User

Hi,

we have account on Spain2 (nicola.prunella@terasrl.it) and we have launched
fiware docker-host machine

docker-machine create -d openstack --openstack-ssh-user="ubuntu"
--openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14.04"
--openstack-net-name="node-int-net-01"
--openstack-floatingip-pool="public-ext-net-01"
--openstack-sec-groups="docker-machine-sg" docker-host

It is now up and running .

Now we would like to ssh on this host but:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ssh -i
server-key.pem ubuntu@130.206.115.30

############################################################################
######

NOTE: You have accessed a system owned by FIWARE Lab. You must have
authorisation

before using it, and your use will be strictly limited to that indicated in
the

authorisation.

Unauthorised access to this system or improper use of the same is prohibited
and

is against the FIWARE Terms & Conditions Policy and the legislation in
force. The

use of this system may be monitored.

############################################################################
#####

Permission denied (publickey).

The system have also created the following files:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ll

totale 40

drwx------ 2 root root 4096 giu 23 15:55 ./

drwx------ 3 root root 4096 giu 23 15:31 ../

r ------- 1 root root 1029 giu 23 15:35 ca.pem

r ------- 1 root root 1070 giu 23 15:35 cert.pem

r ------- 1 root root 3271 giu 23 15:36 config.json

rw ------ 1 root root 1675 giu 23 15:31 id_rsa

r ------- 1 root root 381 giu 23 15:31 id_rsa.pub

r ------- 1 root root 1675 giu 23 15:35 key.pem

r ------- 1 root root 1679 giu 23 15:35 server-key.pem

r ------- 1 root root 1123 giu 23 15:35 server.pem

Thank you

Best regards

< <http://www.terasrl.it/> http://www.terasrl.it/> per firma posta

FW External User - 15/Jul/16 3:05 PM
------------------
Comment by nicola.prunella@terasrl.it :

Hi Josè i have followed this sequence of operations:

apt-get install python-novaclient

/root/.docker/machine/machines#nova keypair-add KEY_NAME > MY_KEY.PEM

/root/.docker/machine/machines#nova keypair-add --pub_key /root/.ssh/id_rsa KEY_NAME

root@formica-VirtualBox:/root/.ssh# nova keypair-list

root@formica-VirtualBox:/root/.ssh# nova keypair-show KEY_NAME

KEY_NAME is automatically imported in FIWARE cloud Keypairs

With puttygen I have obtained the private part and named it like MY_KEY_PRIV.ppk

And finally:

docker-machine create -d openstack --openstack-ssh-user="ubuntu"

--openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14.04" openstack-private-key-file="keypair-dockerprivatekey.ppk"

--openstack-net-name="node-int-net-01"

--openstack-floatingip-pool="public-ext-net-01"

--openstack-sec-groups="docker-machine-sg"

--openstack-private-key-file="MY_KEY_PRIV.ppk"

--openstack-keypair-name="KEY_NAME"

--docker-host

This command creates the vm in Fiware ( it is up and running) but this command doesn’t terminate : Waiting for SSH to be available.

With Putty I can connect to the instance with public ip ( 130.206.115.30) and my PPK keypair : MY_KEY_PRIV.ppk

Inside the instance I notice that docker was not installed

Thank you

Best regards

Da: Help-Desk jira-help-desk@fi-ware.org
Inviato: mercoledì 13 luglio 2016 19:58
A: nicola.prunella@terasrl.it
Oggetto: [FIWARE-JIRA] (HELP-6903) FIWARE.Request.Lab.ssh.

When you can create one or more keypairs. But you MUST tell what keypair you'll be using (even though you only have one).

Docker machine command has parameter (--openstack-keypair-name=$KEYPAIRNAME). That's the way you can tell your new instance what keypair it must use. No .pem is supposed to be used.

If you are not sure about the .pem file you should use, you can easily add a new keypair.

So, to sum up:
docker-machine create -d openstack --openstack-ssh-user="ubuntu"
--openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14.04"
--openstack-net-name="node-int-net-01"
--openstack-floatingip-pool="public-ext-net-01"
--openstack-sec-groups="docker-machine-sg" docker-host
--openstack-keypair-name=$KEYPAIRNAME

Regards,
José Ignacio.

<https://jira.fiware.org/secure/ViewProfile.jspa?name=fw.ext.user> FW External User created an issue

<https://jira.fiware.org/browse/HELP> Help-Desk / <https://jira.fiware.org/browse/HELP-6903> extRequest <https://jira.fiware.org/browse/HELP-6903> HELP-6903

<https://jira.fiware.org/browse/HELP-6903> FIWARE.Request.Lab.ssh.

Issue Type:

extRequest <https://jira.fiware.org/images/icons/issuetypes/defect.png> extRequest

Assignee:

<https://jira.fiware.org/secure/ViewProfile.jspa?name=jicg> José Ignacio Carretero Guarde

Components:

FIWARE-LAB-HELP

Created:

12/Jul/16 1:11 PM

Priority:

Major <https://jira.fiware.org/images/icons/priorities/major.png> Major

Reporter:

<https://jira.fiware.org/secure/ViewProfile.jspa?name=fw.ext.user> FW External User

Hi,

we have account on Spain2 ( <nicola.prunella@terasrl.it> nicola.prunella@terasrl.it) and we have launched
fiware docker-host machine

docker-machine create -d openstack --openstack-ssh-user="ubuntu"
--openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14.04"
--openstack-net-name="node-int-net-01"
--openstack-floatingip-pool="public-ext-net-01"
--openstack-sec-groups="docker-machine-sg" docker-host

It is now up and running .

Now we would like to ssh on this host but:

<root@formica-VirtualBox:~/.docker/machine/machines/docker-host#> root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ssh -i
server-key.pem <ubuntu@130.206.115.30> ubuntu@130.206.115.30

############################################################################
######

NOTE: You have accessed a system owned by FIWARE Lab. You must have
authorisation

before using it, and your use will be strictly limited to that indicated in
the

authorisation.

Unauthorised access to this system or improper use of the same is prohibited
and

is against the FIWARE Terms & Conditions Policy and the legislation in
force. The

use of this system may be monitored.

############################################################################
#####

Permission denied (publickey).

The system have also created the following files:

<root@formica-VirtualBox:~/.docker/machine/machines/docker-host#> root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ll

totale 40

drwx------ 2 root root 4096 giu 23 15:55 ./

drwx------ 3 root root 4096 giu 23 15:31 ../

r ------- 1 root root 1029 giu 23 15:35 ca.pem

r ------- 1 root root 1070 giu 23 15:35 cert.pem

r ------- 1 root root 3271 giu 23 15:36 config.json

rw ------ 1 root root 1675 giu 23 15:31 id_rsa

r ------- 1 root root 381 giu 23 15:31 id_rsa.pub

r ------- 1 root root 1675 giu 23 15:35 key.pem

r ------- 1 root root 1679 giu 23 15:35 server-key.pem

r ------- 1 root root 1123 giu 23 15:35 server.pem

Thank you

Best regards

< <http://www.terasrl.it/> http://www.terasrl.it/> per firma posta

FW External User - 12/Jul/16 4:03 PM
------------------
Comment by nicola.prunella@terasrl.it :

Hi Josè,
when for the first time i issued the command to create the machine i haven't any keypair. After the creation of this machine I have received from openstack/fiware the relative keypair that I have supposed to use after for the connection:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ssh -i server-key.pem ubuntu@130.206.115.30

Infact server-key.pem is one of the files that were created on my machine:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ll

totale 40

drwx------ 2 root root 4096 giu 23 15:55 ./

drwx------ 3 root root 4096 giu 23 15:31 ../

r------- 1 root root 1029 giu 23 15:35 ca.pem

r------- 1 root root 1070 giu 23 15:35 cert.pem

r------- 1 root root 3271 giu 23 15:36 config.json

rw------ 1 root root 1675 giu 23 15:31 id_rsa

r------- 1 root root 381 giu 23 15:31 id_rsa.pub

r------- 1 root root 1675 giu 23 15:35 key.pem

r------- 1 root root 1679 giu 23 15:35 server-key.pem

r------- 1 root root 1123 giu 23 15:35 server.pem

Maybe this supposition was wrong?

Thank you

Best regards

----Messaggio originale----
Da: Help-Desk jira-help-desk@fi-ware.org
Inviato: martedì 12 luglio 2016 13:52
A: nicola.prunella@terasrl.it
Oggetto: [FIWARE-JIRA] (HELP-6903) [Fiware-incense-coaching] ssh

Dear,

Pleast, take a look at docker-machine documentation: https://docs.docker.com/machine/drivers/openstack/

You should add --openstack-keypair-name to your command so it cat use your keypair.

Regards,
José Ignacio.

-------------------------------------------------------------------------------
José Ignacio Carretero Guarde created HELP-6903:
---------------------------------------------------

Summary: [Fiware-incense-coaching] ssh
Key: HELP-6903
URL: https://jira.fiware.org/browse/HELP-6903
Project: Help-Desk
Issue Type: extRequest
Components: FIWARE-LAB-HELP
Reporter: FW External User
Assignee: Spain Node Support Team

Hi,

we have account on Spain2 (nicola.prunella@terasrl.it) and we have launched fiware docker-host machine

docker-machine create -d openstack --openstack-ssh-user="ubuntu"
--openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14.04"
--openstack-net-name="node-int-net-01"
--openstack-floatingip-pool="public-ext-net-01"
--openstack-sec-groups="docker-machine-sg" docker-host

It is now up and running .

Now we would like to ssh on this host but:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ssh -i server-key.pem ubuntu@130.206.115.30

############################################################################
######

NOTE: You have accessed a system owned by FIWARE Lab. You must have authorisation

before using it, and your use will be strictly limited to that indicated in the

authorisation.

Unauthorised access to this system or improper use of the same is prohibited and

is against the FIWARE Terms & Conditions Policy and the legislation in force. The

use of this system may be monitored.

############################################################################
#####

Permission denied (publickey).

The system have also created the following files:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ll

totale 40

drwx------ 2 root root 4096 giu 23 15:55 ./

drwx------ 3 root root 4096 giu 23 15:31 ../

r------- 1 root root 1029 giu 23 15:35 ca.pem

r------- 1 root root 1070 giu 23 15:35 cert.pem

r------- 1 root root 3271 giu 23 15:36 config.json

rw------ 1 root root 1675 giu 23 15:31 id_rsa

r------- 1 root root 381 giu 23 15:31 id_rsa.pub

r------- 1 root root 1675 giu 23 15:35 key.pem

r------- 1 root root 1679 giu 23 15:35 server-key.pem

r------- 1 root root 1123 giu 23 15:35 server.pem

Thank you

Best regards

<http://www.terasrl.it/> per firma posta

José Ignacio Carretero Guarde - 12/Jul/16 2:51 PM
------------------
The issue has been emailed:

• Time sent: 12/Jul/16 1:51 PM
• To: nicola.prunella@terasrl.it
• with subject: *(HELP-6903) [Fiware-incense-coaching] ssh *
  

Dear,

Pleast, take a look at docker-machine documentation: https://docs.docker.com/machine/drivers/openstack/

You should add --openstack-keypair-name to your command so it cat use your keypair.

Regards,
José Ignacio.

Pasquale Andriani - 12/Jul/16 2:13 PM
------------------
Hi, may you help this INCENSe SME ?

Thanks in advance,
P.

------------------------
Issue id: HELP-6903
Description:
Hi,

we have account on Spain2 (nicola.prunella@terasrl.it) and we have launched
fiware docker-host machine

docker-machine create -d openstack --openstack-ssh-user="ubuntu"
--openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14.04"
--openstack-net-name="node-int-net-01"
--openstack-floatingip-pool="public-ext-net-01"
--openstack-sec-groups="docker-machine-sg" docker-host

It is now up and running .

Now we would like to ssh on this host but:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ssh -i
server-key.pem ubuntu@130.206.115.30

############################################################################
######

NOTE: You have accessed a system owned by FIWARE Lab. You must have
authorisation

before using it, and your use will be strictly limited to that indicated in
the

authorisation.

Unauthorised access to this system or improper use of the same is prohibited
and

is against the FIWARE Terms & Conditions Policy and the legislation in
force. The

use of this system may be monitored.

############################################################################
#####

Permission denied (publickey).

The system have also created the following files:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ll

totale 40

drwx------ 2 root root 4096 giu 23 15:55 ./

drwx------ 3 root root 4096 giu 23 15:31 ../

r------- 1 root root 1029 giu 23 15:35 ca.pem

r------- 1 root root 1070 giu 23 15:35 cert.pem

r------- 1 root root 3271 giu 23 15:36 config.json

rw------ 1 root root 1675 giu 23 15:31 id_rsa

r------- 1 root root 381 giu 23 15:31 id_rsa.pub

r------- 1 root root 1675 giu 23 15:35 key.pem

r------- 1 root root 1679 giu 23 15:35 server-key.pem

r------- 1 root root 1123 giu 23 15:35 server.pem

Thank you

Best regards

<http://www.terasrl.it/> per firma posta

Nicola:
Sorry we are not being more helpful.
Did you see this discussion https://github.com/docker/toolbox/issues/346.
Maybe there are some hints on what to try.

--Ken

Nicola:
You might want to check out our FIWARE Docker Container Service (FDCS).
FDCS exposes the docker API so that you can use your local docker clients to remotely manage their docker containers on the FIWARE Lab. You won't have to mess with docker-machine or managing docker hosts, since FDCS does that for you. Contact me if you are interested.
See
https://github.com/fiware-docker/docker-container-service
http://catalogue.fiware.org/enablers/docker/instances

Ken

Comment by nicola.prunella@terasrl.it :

Hi Ken,
yes we are interested about FDCS. Please let me know how to get a FIWARE Docker Container Service Account.

Thank you
Best regards

Nicola

Inviato: lunedì 22 agosto 2016 11:09
A: nicola.prunella@terasrl.it
Cc: antonio.sacchetti@terasrl.it; antonio.lobefaro@terasrl.it; massimiliano.siliberti@terasrl.it
Oggetto: [FIWARE-JIRA] (HELP-6903) FIWARE.Request.Lab.ssh.

From FIWARE JIRA - Main Help Desk ----

-------------------------------------------------------------------------------
Comments:

Kenneth Nagin - Today 12:08 PM
------------------
Nicola:
You might want to check out our FIWARE Docker Container Service (FDCS).
FDCS exposes the docker API so that you can use your local docker clients to remotely manage their docker containers on the FIWARE Lab. You won't have to mess with docker-machine or managing docker hosts, since FDCS does that for you. Contact me if you are interested.
See
https://github.com/fiware-docker/docker-container-service
http://catalogue.fiware.org/enablers/docker/instances

Ken

Kenneth Nagin - 11/Aug/16 5:25 PM
------------------
Nicola:
Sorry we are not being more helpful.
Did you see this discussion https://github.com/docker/toolbox/issues/346.
Maybe there are some hints on what to try.

--Ken

FW External User - 05/Aug/16 11:16 AM
------------------
Comment by nicola.prunella@terasrl.it :

Hi Ken,

first of all I have followed this: http://simple-docker-hosting-on-fiware-cloud.readthedocs.io/en/latest/install/index.html

Then:
1.
root@default:/mnt/sdb3/fiware# docker-machine version docker-machine version 0.6.0, build e27fb87 root@default:/mnt/sdb3/fiware# export OS_REGION_NAME='Spain2'
root@default:/mnt/sdb3/fiware# export OS_TENANT_NAME='lprunella cloud'
root@default:/mnt/sdb3/fiware# export OS_USERNAME='nicola.prunella@terasrl.it'
root@default:/mnt/sdb3/fiware# export OS_PASSWORD='Psynergia1'
root@default:/mnt/sdb3/fiware# export OS_AUTH_URL='http://cloud.lab.fi-ware.org:
4730/v2.0/'
root@default:/mnt/sdb3/fiware# export OS_AUTH_STRATEGY='keystone'
root@default:/mnt/sdb3/fiware# docker-machine create -d openstack --openstack-ss h-user="ubuntu" --openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14
.04" -openstack-net-name="node-int-net-01" --openstack-floatingip-pool="public
ext-net-01" --openstack-sec-groups="docker-machine-sg" docker-host Creating CA: /root/.docker/machine/certs/ca.pem
Creating client certificate: /root/.docker/machine/certs/cert.pem
Running pre-create checks...
Creating machine...
(docker-host) Creating machine...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with ubuntu(upstart)...
Installing Docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: docker-machine env docker-host

2.
root@default:/mnt/sdb3/fiware# docker-machine env docker-host Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "130.206.122.75:2376": dial tcp 130.206.122.75:2376: i/o timeout You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which will stop running containers.

3.
root@default:/mnt/sdb3/fiware# docker run hello-world Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
6432e0ccba2d: Pull complete
95f1eedc264a: Pull complete
Digest: sha256:548e9719abe62684ac7f01eea38cb5b0cf467cfe67c58b83fe87ba96674a4cdd
Status: Downloaded newer image for hello-world:latest

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
1. The Docker client contacted the Docker daemon.
2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
3. The Docker daemon created a new container from that image which runs the
executable that produces the output you are currently reading.
4. The Docker daemon streamed that output to the Docker client, which sent it
to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker Hub account:
https://hub.docker.com

For more examples and ideas, visit:
https://docs.docker.com/engine/userguide/

As you can see the second step goes into error , however the docker-host is up and running and it respond to docker run hello-world

Thank you

----Messaggio originale----
Da: Help-Desk jira-help-desk@fi-ware.org
Inviato: giovedì 4 agosto 2016 11:32
A: nicola.prunella@terasrl.it
Cc: antonio.sacchetti@terasrl.it; antonio.lobefaro@terasrl.it; massimiliano.siliberti@terasrl.it
Oggetto: [FIWARE-JIRA] (HELP-6903) FIWARE.Request.Lab.ssh.

From FIWARE JIRA - Main Help Desk ----

-------------------------------------------------------------------------------
Comments:

Kenneth Nagin - Today 12:31 PM
------------------
Nicola
Have you tried docker-machine ssh (https://docs.docker.com/machine/reference/ssh/) ?
--Ken

Pasquale Andriani - 26/Jul/16 12:55 PM
------------------
Dear Kennet, I'm re-assigning this ticket as suggested by Josè.
May you help this INCENCe SME in using Docker? Please find the problem described in the previous comments.

Thanks in advance,
P.

José Ignacio Carretero Guarde - 25/Jul/16 2:58 PM
------------------
--openstack-private-key-file="id_rsa_priv.ppk"

The .ppk key is just to be used with putty. docker-machine, as far as I know, used the original id_rsa key. — However, if you have problems with the enabler, you could also ask the GEOwner (http://catalogue.fiware.org/enablers/docker) as I'm not an expert on "docker machine".

Regards,
José Ignacio.

Pasquale Andriani - 22/Jul/16 7:10 PM
------------------
Hi Josè, it seems that the problem is not solved yet. May you follow up with some more hint for Nicola?

Thanks in advance,
P.

FW External User - 20/Jul/16 5:43 PM
------------------
Comment by nicola.prunella@terasrl.it :

Hi,

1. i have allocated new floating ip

2. i have already generated a key pair ( id_rsa, id_rsa.pub) and this keys are located at /root/.ssh/

3. now i import public key at the Nova database with the command:

/root/.docker/machine/machines# nova keypair-add --pub_key /root/.ssh/id_rsa.pub KEY_NAME

4. To ensure that the key pair has been successfully imported:

root@formica-VirtualBox:~/.docker/machine/machines# nova keypair-list

---------------------------------------------------------+

---------------------------------------------------------+

---------------------------------------------------------+

5. with puttygen i produce id_rsa_priv.ppk from id_rsa

6. root@formica-VirtualBox:~/.docker/machine/machines# ls

id_rsa_priv.ppk id_rsa.pub

docker-machine create -d openstack

--openstack-ssh-user="ubuntu"

--openstack-flavor-id="2"

--openstack-image-name="base_ubuntu_14.04"

--openstack-net-name="node-int-net-01"

--openstack-floatingip-pool="public-ext-net-01"

--openstack-sec-groups="docker-machine-sg"

--openstack-private-key-file="id_rsa_priv.ppk"

--openstack-keypair-name="KEY_NAME" docker-host

Running pre-create checks...

Creating machine...

(docker-host) Creating machine...

Waiting for machine to be running, this may take a few minutes...

Detecting operating system of created instance...

Waiting for SSH to be available...

Error creating machine: Error detecting OS: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded

r

Best regards

Nicola

Da: Help-Desk jira-help-desk@fi-ware.org
Inviato: mercoledì 20 luglio 2016 12:52
A: nicola.prunella@terasrl.it
Oggetto: [FIWARE-JIRA] (HELP-6903) FIWARE.Request.Lab.ssh.

Hi,

The assignation of the floating IP to the VM and the fact that It didn't finished, could have been a temporary problem with Openstack, which can usually be corrected removing and adding again the IP to the server.

Docker Machine deploys VMs and it install docker-engine inside the VMs, and it works.

Regards,
José Ignacio.

<https://jira.fiware.org/secure/ViewProfile.jspa?name=fw.ext.user> FW External User created an issue

<https://jira.fiware.org/browse/HELP> Help-Desk / <https://jira.fiware.org/browse/HELP-6903> extRequest <https://jira.fiware.org/browse/HELP-6903> HELP-6903

<https://jira.fiware.org/browse/HELP-6903> FIWARE.Request.Lab.ssh.

Issue Type:

extRequest <https://jira.fiware.org/images/icons/issuetypes/defect.png> extRequest

Assignee:

<https://jira.fiware.org/secure/ViewProfile.jspa?name=jicg> José Ignacio Carretero Guarde

Components:

FIWARE-LAB-HELP

Created:

12/Jul/16 1:11 PM

Priority:

Major <https://jira.fiware.org/images/icons/priorities/major.png> Major

Reporter:

<https://jira.fiware.org/secure/ViewProfile.jspa?name=fw.ext.user> FW External User

Hi,

we have account on Spain2 (nicola.prunella@terasrl.it) and we have launched
fiware docker-host machine

docker-machine create -d openstack --openstack-ssh-user="ubuntu"
--openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14.04"
--openstack-net-name="node-int-net-01"
--openstack-floatingip-pool="public-ext-net-01"
--openstack-sec-groups="docker-machine-sg" docker-host

It is now up and running .

Now we would like to ssh on this host but:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ssh -i
server-key.pem ubuntu@130.206.115.30

############################################################################
######

NOTE: You have accessed a system owned by FIWARE Lab. You must have
authorisation

before using it, and your use will be strictly limited to that indicated in
the

authorisation.

Unauthorised access to this system or improper use of the same is prohibited
and

is against the FIWARE Terms & Conditions Policy and the legislation in
force. The

use of this system may be monitored.

############################################################################
#####

Permission denied (publickey).

The system have also created the following files:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ll

totale 40

drwx------ 2 root root 4096 giu 23 15:55 ./

drwx------ 3 root root 4096 giu 23 15:31 ../

r ------- 1 root root 1029 giu 23 15:35 ca.pem

r ------- 1 root root 1070 giu 23 15:35 cert.pem

r ------- 1 root root 3271 giu 23 15:36 config.json

rw ------ 1 root root 1675 giu 23 15:31 id_rsa

r ------- 1 root root 381 giu 23 15:31 id_rsa.pub

r ------- 1 root root 1675 giu 23 15:35 key.pem

r ------- 1 root root 1679 giu 23 15:35 server-key.pem

r ------- 1 root root 1123 giu 23 15:35 server.pem

Thank you

Best regards

< <http://www.terasrl.it/> http://www.terasrl.it/> per firma posta

FW External User - 15/Jul/16 3:05 PM
------------------
Comment by nicola.prunella@terasrl.it :

Hi Josè i have followed this sequence of operations:

apt-get install python-novaclient

/root/.docker/machine/machines#nova keypair-add KEY_NAME > MY_KEY.PEM

/root/.docker/machine/machines#nova keypair-add --pub_key /root/.ssh/id_rsa KEY_NAME

root@formica-VirtualBox:/root/.ssh# nova keypair-list

root@formica-VirtualBox:/root/.ssh# nova keypair-show KEY_NAME

KEY_NAME is automatically imported in FIWARE cloud Keypairs

With puttygen I have obtained the private part and named it like MY_KEY_PRIV.ppk

And finally:

docker-machine create -d openstack --openstack-ssh-user="ubuntu"

--openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14.04" openstack-private-key-file="keypair-dockerprivatekey.ppk"

--openstack-net-name="node-int-net-01"

--openstack-floatingip-pool="public-ext-net-01"

--openstack-sec-groups="docker-machine-sg"

--openstack-private-key-file="MY_KEY_PRIV.ppk"

--openstack-keypair-name="KEY_NAME"

--docker-host

This command creates the vm in Fiware ( it is up and running) but this command doesn’t terminate : Waiting for SSH to be available.

With Putty I can connect to the instance with public ip ( 130.206.115.30) and my PPK keypair : MY_KEY_PRIV.ppk

Inside the instance I notice that docker was not installed

Thank you

Best regards

Da: Help-Desk jira-help-desk@fi-ware.org
Inviato: mercoledì 13 luglio 2016 19:58
A: nicola.prunella@terasrl.it
Oggetto: [FIWARE-JIRA] (HELP-6903) FIWARE.Request.Lab.ssh.

When you can create one or more keypairs. But you MUST tell what keypair you'll be using (even though you only have one).

Docker machine command has parameter (--openstack-keypair-name=$KEYPAIRNAME). That's the way you can tell your new instance what keypair it must use. No .pem is supposed to be used.

If you are not sure about the .pem file you should use, you can easily add a new keypair.

So, to sum up:
docker-machine create -d openstack --openstack-ssh-user="ubuntu"
--openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14.04"
--openstack-net-name="node-int-net-01"
--openstack-floatingip-pool="public-ext-net-01"
--openstack-sec-groups="docker-machine-sg" docker-host
--openstack-keypair-name=$KEYPAIRNAME

Regards,
José Ignacio.

<https://jira.fiware.org/secure/ViewProfile.jspa?name=fw.ext.user> FW External User created an issue

<https://jira.fiware.org/browse/HELP> Help-Desk / <https://jira.fiware.org/browse/HELP-6903> extRequest <https://jira.fiware.org/browse/HELP-6903> HELP-6903

<https://jira.fiware.org/browse/HELP-6903> FIWARE.Request.Lab.ssh.

Issue Type:

extRequest <https://jira.fiware.org/images/icons/issuetypes/defect.png> extRequest

Assignee:

<https://jira.fiware.org/secure/ViewProfile.jspa?name=jicg> José Ignacio Carretero Guarde

Components:

FIWARE-LAB-HELP

Created:

12/Jul/16 1:11 PM

Priority:

Major <https://jira.fiware.org/images/icons/priorities/major.png> Major

Reporter:

<https://jira.fiware.org/secure/ViewProfile.jspa?name=fw.ext.user> FW External User

Hi,

we have account on Spain2 ( <nicola.prunella@terasrl.it> nicola.prunella@terasrl.it) and we have launched
fiware docker-host machine

docker-machine create -d openstack --openstack-ssh-user="ubuntu"
--openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14.04"
--openstack-net-name="node-int-net-01"
--openstack-floatingip-pool="public-ext-net-01"
--openstack-sec-groups="docker-machine-sg" docker-host

It is now up and running .

Now we would like to ssh on this host but:

<root@formica-VirtualBox:~/.docker/machine/machines/docker-host#> root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ssh -i
server-key.pem <ubuntu@130.206.115.30> ubuntu@130.206.115.30

############################################################################
######

NOTE: You have accessed a system owned by FIWARE Lab. You must have
authorisation

before using it, and your use will be strictly limited to that indicated in
the

authorisation.

Unauthorised access to this system or improper use of the same is prohibited
and

is against the FIWARE Terms & Conditions Policy and the legislation in
force. The

use of this system may be monitored.

############################################################################
#####

Permission denied (publickey).

The system have also created the following files:

<root@formica-VirtualBox:~/.docker/machine/machines/docker-host#> root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ll

totale 40

drwx------ 2 root root 4096 giu 23 15:55 ./

drwx------ 3 root root 4096 giu 23 15:31 ../

r ------- 1 root root 1029 giu 23 15:35 ca.pem

r ------- 1 root root 1070 giu 23 15:35 cert.pem

r ------- 1 root root 3271 giu 23 15:36 config.json

rw ------ 1 root root 1675 giu 23 15:31 id_rsa

r ------- 1 root root 381 giu 23 15:31 id_rsa.pub

r ------- 1 root root 1675 giu 23 15:35 key.pem

r ------- 1 root root 1679 giu 23 15:35 server-key.pem

r ------- 1 root root 1123 giu 23 15:35 server.pem

Thank you

Best regards

< <http://www.terasrl.it/> http://www.terasrl.it/> per firma posta

FW External User - 12/Jul/16 4:03 PM
------------------
Comment by nicola.prunella@terasrl.it :

Hi Josè,
when for the first time i issued the command to create the machine i haven't any keypair. After the creation of this machine I have received from openstack/fiware the relative keypair that I have supposed to use after for the connection:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ssh -i server-key.pem ubuntu@130.206.115.30

Infact server-key.pem is one of the files that were created on my machine:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ll

totale 40

drwx------ 2 root root 4096 giu 23 15:55 ./

drwx------ 3 root root 4096 giu 23 15:31 ../

r------- 1 root root 1029 giu 23 15:35 ca.pem

r------- 1 root root 1070 giu 23 15:35 cert.pem

r------- 1 root root 3271 giu 23 15:36 config.json

rw------ 1 root root 1675 giu 23 15:31 id_rsa

r------- 1 root root 381 giu 23 15:31 id_rsa.pub

r------- 1 root root 1675 giu 23 15:35 key.pem

r------- 1 root root 1679 giu 23 15:35 server-key.pem

r------- 1 root root 1123 giu 23 15:35 server.pem

Maybe this supposition was wrong?

Thank you

Best regards

----Messaggio originale----
Da: Help-Desk jira-help-desk@fi-ware.org
Inviato: martedì 12 luglio 2016 13:52
A: nicola.prunella@terasrl.it
Oggetto: [FIWARE-JIRA] (HELP-6903) [Fiware-incense-coaching] ssh

Dear,

Pleast, take a look at docker-machine documentation: https://docs.docker.com/machine/drivers/openstack/

You should add --openstack-keypair-name to your command so it cat use your keypair.

Regards,
José Ignacio.

-------------------------------------------------------------------------------
José Ignacio Carretero Guarde created HELP-6903:
---------------------------------------------------

Summary: [Fiware-incense-coaching] ssh
Key: HELP-6903
URL: https://jira.fiware.org/browse/HELP-6903
Project: Help-Desk
Issue Type: extRequest
Components: FIWARE-LAB-HELP
Reporter: FW External User
Assignee: Spain Node Support Team

Hi,

we have account on Spain2 (nicola.prunella@terasrl.it) and we have launched fiware docker-host machine

docker-machine create -d openstack --openstack-ssh-user="ubuntu"
--openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14.04"
--openstack-net-name="node-int-net-01"
--openstack-floatingip-pool="public-ext-net-01"
--openstack-sec-groups="docker-machine-sg" docker-host

It is now up and running .

Now we would like to ssh on this host but:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ssh -i server-key.pem ubuntu@130.206.115.30

############################################################################
######

NOTE: You have accessed a system owned by FIWARE Lab. You must have authorisation

before using it, and your use will be strictly limited to that indicated in the

authorisation.

Unauthorised access to this system or improper use of the same is prohibited and

is against the FIWARE Terms & Conditions Policy and the legislation in force. The

use of this system may be monitored.

############################################################################
#####

Permission denied (publickey).

The system have also created the following files:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ll

totale 40

drwx------ 2 root root 4096 giu 23 15:55 ./

drwx------ 3 root root 4096 giu 23 15:31 ../

r------- 1 root root 1029 giu 23 15:35 ca.pem

r------- 1 root root 1070 giu 23 15:35 cert.pem

r------- 1 root root 3271 giu 23 15:36 config.json

rw------ 1 root root 1675 giu 23 15:31 id_rsa

r------- 1 root root 381 giu 23 15:31 id_rsa.pub

r------- 1 root root 1675 giu 23 15:35 key.pem

r------- 1 root root 1679 giu 23 15:35 server-key.pem

r------- 1 root root 1123 giu 23 15:35 server.pem

Thank you

Best regards

<http://www.terasrl.it/> per firma posta

José Ignacio Carretero Guarde - 12/Jul/16 2:51 PM
------------------
The issue has been emailed:

• Time sent: 12/Jul/16 1:51 PM
• To: nicola.prunella@terasrl.it
• with subject: *(HELP-6903) [Fiware-incense-coaching] ssh *
  

Dear,

Pleast, take a look at docker-machine documentation: https://docs.docker.com/machine/drivers/openstack/

You should add --openstack-keypair-name to your command so it cat use your keypair.

Regards,
José Ignacio.

Pasquale Andriani - 12/Jul/16 2:13 PM
------------------
Hi, may you help this INCENSe SME ?

Thanks in advance,
P.

------------------------
Issue id: HELP-6903
Description:
Hi,

we have account on Spain2 (nicola.prunella@terasrl.it) and we have launched
fiware docker-host machine

docker-machine create -d openstack --openstack-ssh-user="ubuntu"
--openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14.04"
--openstack-net-name="node-int-net-01"
--openstack-floatingip-pool="public-ext-net-01"
--openstack-sec-groups="docker-machine-sg" docker-host

It is now up and running .

Now we would like to ssh on this host but:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ssh -i
server-key.pem ubuntu@130.206.115.30

############################################################################
######

NOTE: You have accessed a system owned by FIWARE Lab. You must have
authorisation

before using it, and your use will be strictly limited to that indicated in
the

authorisation.

Unauthorised access to this system or improper use of the same is prohibited
and

is against the FIWARE Terms & Conditions Policy and the legislation in
force. The

use of this system may be monitored.

############################################################################
#####

Permission denied (publickey).

The system have also created the following files:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ll

totale 40

drwx------ 2 root root 4096 giu 23 15:55 ./

drwx------ 3 root root 4096 giu 23 15:31 ../

r------- 1 root root 1029 giu 23 15:35 ca.pem

r------- 1 root root 1070 giu 23 15:35 cert.pem

r------- 1 root root 3271 giu 23 15:36 config.json

rw------ 1 root root 1675 giu 23 15:31 id_rsa

r------- 1 root root 381 giu 23 15:31 id_rsa.pub

r------- 1 root root 1675 giu 23 15:35 key.pem

r------- 1 root root 1679 giu 23 15:35 server-key.pem

r------- 1 root root 1123 giu 23 15:35 server.pem

Thank you

Best regards

<http://www.terasrl.it/> per firma posta

Kenneth Nagin - 04/Aug/16 12:31 PM
------------------
Nicola
Have you tried docker-machine ssh (https://docs.docker.com/machine/reference/ssh/) ?
--Ken

Pasquale Andriani - 26/Jul/16 12:55 PM
------------------
Dear Kennet, I'm re-assigning this ticket as suggested by Josè.
May you help this INCENCe SME in using Docker? Please find the problem described in the previous comments.

Thanks in advance,
P.

José Ignacio Carretero Guarde - 25/Jul/16 2:58 PM
------------------
--openstack-private-key-file="id_rsa_priv.ppk"

The .ppk key is just to be used with putty. docker-machine, as far as I know, used the original id_rsa key. — However, if you have problems with the enabler, you could also ask the GEOwner (http://catalogue.fiware.org/enablers/docker) as I'm not an expert on "docker machine".

Regards,
José Ignacio.

Pasquale Andriani - 22/Jul/16 7:10 PM
------------------
Hi Josè, it seems that the problem is not solved yet. May you follow up with some more hint for Nicola?

Thanks in advance,
P.

FW External User - 20/Jul/16 5:43 PM
------------------
Comment by nicola.prunella@terasrl.it :

Hi,

1. i have allocated new floating ip

2. i have already generated a key pair ( id_rsa, id_rsa.pub) and this keys are located at /root/.ssh/

3. now i import public key at the Nova database with the command:

/root/.docker/machine/machines# nova keypair-add --pub_key /root/.ssh/id_rsa.pub KEY_NAME

4. To ensure that the key pair has been successfully imported:

root@formica-VirtualBox:~/.docker/machine/machines# nova keypair-list

---------------------------------------------------------+

---------------------------------------------------------+

---------------------------------------------------------+

5. with puttygen i produce id_rsa_priv.ppk from id_rsa

6. root@formica-VirtualBox:~/.docker/machine/machines# ls

id_rsa_priv.ppk id_rsa.pub

docker-machine create -d openstack

--openstack-ssh-user="ubuntu"

--openstack-flavor-id="2"

--openstack-image-name="base_ubuntu_14.04"

--openstack-net-name="node-int-net-01"

--openstack-floatingip-pool="public-ext-net-01"

--openstack-sec-groups="docker-machine-sg"

--openstack-private-key-file="id_rsa_priv.ppk"

--openstack-keypair-name="KEY_NAME" docker-host

Running pre-create checks...

Creating machine...

(docker-host) Creating machine...

Waiting for machine to be running, this may take a few minutes...

Detecting operating system of created instance...

Waiting for SSH to be available...

Error creating machine: Error detecting OS: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded

r

Best regards

Nicola

Da: Help-Desk jira-help-desk@fi-ware.org
Inviato: mercoledì 20 luglio 2016 12:52
A: nicola.prunella@terasrl.it
Oggetto: [FIWARE-JIRA] (HELP-6903) FIWARE.Request.Lab.ssh.

Hi,

The assignation of the floating IP to the VM and the fact that It didn't finished, could have been a temporary problem with Openstack, which can usually be corrected removing and adding again the IP to the server.

Docker Machine deploys VMs and it install docker-engine inside the VMs, and it works.

Regards,
José Ignacio.

<https://jira.fiware.org/secure/ViewProfile.jspa?name=fw.ext.user> FW External User created an issue

<https://jira.fiware.org/browse/HELP> Help-Desk / <https://jira.fiware.org/browse/HELP-6903> extRequest <https://jira.fiware.org/browse/HELP-6903> HELP-6903

<https://jira.fiware.org/browse/HELP-6903> FIWARE.Request.Lab.ssh.

Issue Type:

extRequest <https://jira.fiware.org/images/icons/issuetypes/defect.png> extRequest

Assignee:

<https://jira.fiware.org/secure/ViewProfile.jspa?name=jicg> José Ignacio Carretero Guarde

Components:

FIWARE-LAB-HELP

Created:

12/Jul/16 1:11 PM

Priority:

Major <https://jira.fiware.org/images/icons/priorities/major.png> Major

Reporter:

<https://jira.fiware.org/secure/ViewProfile.jspa?name=fw.ext.user> FW External User

Hi,

we have account on Spain2 (nicola.prunella@terasrl.it) and we have launched
fiware docker-host machine

docker-machine create -d openstack --openstack-ssh-user="ubuntu"
--openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14.04"
--openstack-net-name="node-int-net-01"
--openstack-floatingip-pool="public-ext-net-01"
--openstack-sec-groups="docker-machine-sg" docker-host

It is now up and running .

Now we would like to ssh on this host but:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ssh -i
server-key.pem ubuntu@130.206.115.30

############################################################################
######

NOTE: You have accessed a system owned by FIWARE Lab. You must have
authorisation

before using it, and your use will be strictly limited to that indicated in
the

authorisation.

Unauthorised access to this system or improper use of the same is prohibited
and

is against the FIWARE Terms & Conditions Policy and the legislation in
force. The

use of this system may be monitored.

############################################################################
#####

Permission denied (publickey).

The system have also created the following files:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ll

totale 40

drwx------ 2 root root 4096 giu 23 15:55 ./

drwx------ 3 root root 4096 giu 23 15:31 ../

r ------- 1 root root 1029 giu 23 15:35 ca.pem

r ------- 1 root root 1070 giu 23 15:35 cert.pem

r ------- 1 root root 3271 giu 23 15:36 config.json

rw ------ 1 root root 1675 giu 23 15:31 id_rsa

r ------- 1 root root 381 giu 23 15:31 id_rsa.pub

r ------- 1 root root 1675 giu 23 15:35 key.pem

r ------- 1 root root 1679 giu 23 15:35 server-key.pem

r ------- 1 root root 1123 giu 23 15:35 server.pem

Thank you

Best regards

< <http://www.terasrl.it/> http://www.terasrl.it/> per firma posta

FW External User - 15/Jul/16 3:05 PM
------------------
Comment by nicola.prunella@terasrl.it :

Hi Josè i have followed this sequence of operations:

apt-get install python-novaclient

/root/.docker/machine/machines#nova keypair-add KEY_NAME > MY_KEY.PEM

/root/.docker/machine/machines#nova keypair-add --pub_key /root/.ssh/id_rsa KEY_NAME

root@formica-VirtualBox:/root/.ssh# nova keypair-list

root@formica-VirtualBox:/root/.ssh# nova keypair-show KEY_NAME

KEY_NAME is automatically imported in FIWARE cloud Keypairs

With puttygen I have obtained the private part and named it like MY_KEY_PRIV.ppk

And finally:

docker-machine create -d openstack --openstack-ssh-user="ubuntu"

--openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14.04" openstack-private-key-file="keypair-dockerprivatekey.ppk"

--openstack-net-name="node-int-net-01"

--openstack-floatingip-pool="public-ext-net-01"

--openstack-sec-groups="docker-machine-sg"

--openstack-private-key-file="MY_KEY_PRIV.ppk"

--openstack-keypair-name="KEY_NAME"

--docker-host

This command creates the vm in Fiware ( it is up and running) but this command doesn’t terminate : Waiting for SSH to be available.

With Putty I can connect to the instance with public ip ( 130.206.115.30) and my PPK keypair : MY_KEY_PRIV.ppk

Inside the instance I notice that docker was not installed

Thank you

Best regards

Da: Help-Desk jira-help-desk@fi-ware.org
Inviato: mercoledì 13 luglio 2016 19:58
A: nicola.prunella@terasrl.it
Oggetto: [FIWARE-JIRA] (HELP-6903) FIWARE.Request.Lab.ssh.

When you can create one or more keypairs. But you MUST tell what keypair you'll be using (even though you only have one).

Docker machine command has parameter (--openstack-keypair-name=$KEYPAIRNAME). That's the way you can tell your new instance what keypair it must use. No .pem is supposed to be used.

If you are not sure about the .pem file you should use, you can easily add a new keypair.

So, to sum up:
docker-machine create -d openstack --openstack-ssh-user="ubuntu"
--openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14.04"
--openstack-net-name="node-int-net-01"
--openstack-floatingip-pool="public-ext-net-01"
--openstack-sec-groups="docker-machine-sg" docker-host
--openstack-keypair-name=$KEYPAIRNAME

Regards,
José Ignacio.

<https://jira.fiware.org/secure/ViewProfile.jspa?name=fw.ext.user> FW External User created an issue

<https://jira.fiware.org/browse/HELP> Help-Desk / <https://jira.fiware.org/browse/HELP-6903> extRequest <https://jira.fiware.org/browse/HELP-6903> HELP-6903

<https://jira.fiware.org/browse/HELP-6903> FIWARE.Request.Lab.ssh.

Issue Type:

extRequest <https://jira.fiware.org/images/icons/issuetypes/defect.png> extRequest

Assignee:

<https://jira.fiware.org/secure/ViewProfile.jspa?name=jicg> José Ignacio Carretero Guarde

Components:

FIWARE-LAB-HELP

Created:

12/Jul/16 1:11 PM

Priority:

Major <https://jira.fiware.org/images/icons/priorities/major.png> Major

Reporter:

<https://jira.fiware.org/secure/ViewProfile.jspa?name=fw.ext.user> FW External User

Hi,

we have account on Spain2 ( <nicola.prunella@terasrl.it> nicola.prunella@terasrl.it) and we have launched
fiware docker-host machine

docker-machine create -d openstack --openstack-ssh-user="ubuntu"
--openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14.04"
--openstack-net-name="node-int-net-01"
--openstack-floatingip-pool="public-ext-net-01"
--openstack-sec-groups="docker-machine-sg" docker-host

It is now up and running .

Now we would like to ssh on this host but:

<root@formica-VirtualBox:~/.docker/machine/machines/docker-host#> root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ssh -i
server-key.pem <ubuntu@130.206.115.30> ubuntu@130.206.115.30

############################################################################
######

NOTE: You have accessed a system owned by FIWARE Lab. You must have
authorisation

before using it, and your use will be strictly limited to that indicated in
the

authorisation.

Unauthorised access to this system or improper use of the same is prohibited
and

is against the FIWARE Terms & Conditions Policy and the legislation in
force. The

use of this system may be monitored.

############################################################################
#####

Permission denied (publickey).

The system have also created the following files:

<root@formica-VirtualBox:~/.docker/machine/machines/docker-host#> root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ll

totale 40

drwx------ 2 root root 4096 giu 23 15:55 ./

drwx------ 3 root root 4096 giu 23 15:31 ../

r ------- 1 root root 1029 giu 23 15:35 ca.pem

r ------- 1 root root 1070 giu 23 15:35 cert.pem

r ------- 1 root root 3271 giu 23 15:36 config.json

rw ------ 1 root root 1675 giu 23 15:31 id_rsa

r ------- 1 root root 381 giu 23 15:31 id_rsa.pub

r ------- 1 root root 1675 giu 23 15:35 key.pem

r ------- 1 root root 1679 giu 23 15:35 server-key.pem

r ------- 1 root root 1123 giu 23 15:35 server.pem

Thank you

Best regards

< <http://www.terasrl.it/> http://www.terasrl.it/> per firma posta

FW External User - 12/Jul/16 4:03 PM
------------------
Comment by nicola.prunella@terasrl.it :

Hi Josè,
when for the first time i issued the command to create the machine i haven't any keypair. After the creation of this machine I have received from openstack/fiware the relative keypair that I have supposed to use after for the connection:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ssh -i server-key.pem ubuntu@130.206.115.30

Infact server-key.pem is one of the files that were created on my machine:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ll

totale 40

drwx------ 2 root root 4096 giu 23 15:55 ./

drwx------ 3 root root 4096 giu 23 15:31 ../

r------- 1 root root 1029 giu 23 15:35 ca.pem

r------- 1 root root 1070 giu 23 15:35 cert.pem

r------- 1 root root 3271 giu 23 15:36 config.json

rw------ 1 root root 1675 giu 23 15:31 id_rsa

r------- 1 root root 381 giu 23 15:31 id_rsa.pub

r------- 1 root root 1675 giu 23 15:35 key.pem

r------- 1 root root 1679 giu 23 15:35 server-key.pem

r------- 1 root root 1123 giu 23 15:35 server.pem

Maybe this supposition was wrong?

Thank you

Best regards

----Messaggio originale----
Da: Help-Desk jira-help-desk@fi-ware.org
Inviato: martedì 12 luglio 2016 13:52
A: nicola.prunella@terasrl.it
Oggetto: [FIWARE-JIRA] (HELP-6903) [Fiware-incense-coaching] ssh

Dear,

Pleast, take a look at docker-machine documentation: https://docs.docker.com/machine/drivers/openstack/

You should add --openstack-keypair-name to your command so it cat use your keypair.

Regards,
José Ignacio.

-------------------------------------------------------------------------------
José Ignacio Carretero Guarde created HELP-6903:
---------------------------------------------------

Summary: [Fiware-incense-coaching] ssh
Key: HELP-6903
URL: https://jira.fiware.org/browse/HELP-6903
Project: Help-Desk
Issue Type: extRequest
Components: FIWARE-LAB-HELP
Reporter: FW External User
Assignee: Spain Node Support Team

Hi,

we have account on Spain2 (nicola.prunella@terasrl.it) and we have launched fiware docker-host machine

docker-machine create -d openstack --openstack-ssh-user="ubuntu"
--openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14.04"
--openstack-net-name="node-int-net-01"
--openstack-floatingip-pool="public-ext-net-01"
--openstack-sec-groups="docker-machine-sg" docker-host

It is now up and running .

Now we would like to ssh on this host but:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ssh -i server-key.pem ubuntu@130.206.115.30

############################################################################
######

NOTE: You have accessed a system owned by FIWARE Lab. You must have authorisation

before using it, and your use will be strictly limited to that indicated in the

authorisation.

Unauthorised access to this system or improper use of the same is prohibited and

is against the FIWARE Terms & Conditions Policy and the legislation in force. The

use of this system may be monitored.

############################################################################
#####

Permission denied (publickey).

The system have also created the following files:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ll

totale 40

drwx------ 2 root root 4096 giu 23 15:55 ./

drwx------ 3 root root 4096 giu 23 15:31 ../

r------- 1 root root 1029 giu 23 15:35 ca.pem

r------- 1 root root 1070 giu 23 15:35 cert.pem

r------- 1 root root 3271 giu 23 15:36 config.json

rw------ 1 root root 1675 giu 23 15:31 id_rsa

r------- 1 root root 381 giu 23 15:31 id_rsa.pub

r------- 1 root root 1675 giu 23 15:35 key.pem

r------- 1 root root 1679 giu 23 15:35 server-key.pem

r------- 1 root root 1123 giu 23 15:35 server.pem

Thank you

Best regards

<http://www.terasrl.it/> per firma posta

José Ignacio Carretero Guarde - 12/Jul/16 2:51 PM
------------------
The issue has been emailed:

• Time sent: 12/Jul/16 1:51 PM
• To: nicola.prunella@terasrl.it
• with subject: *(HELP-6903) [Fiware-incense-coaching] ssh *
  

Dear,

Pleast, take a look at docker-machine documentation: https://docs.docker.com/machine/drivers/openstack/

You should add --openstack-keypair-name to your command so it cat use your keypair.

Regards,
José Ignacio.

Pasquale Andriani - 12/Jul/16 2:13 PM
------------------
Hi, may you help this INCENSe SME ?

Thanks in advance,
P.

------------------------
Issue id: HELP-6903
Description:
Hi,

we have account on Spain2 (nicola.prunella@terasrl.it) and we have launched
fiware docker-host machine

docker-machine create -d openstack --openstack-ssh-user="ubuntu"
--openstack-flavor-id="2" --openstack-image-name="base_ubuntu_14.04"
--openstack-net-name="node-int-net-01"
--openstack-floatingip-pool="public-ext-net-01"
--openstack-sec-groups="docker-machine-sg" docker-host

It is now up and running .

Now we would like to ssh on this host but:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ssh -i
server-key.pem ubuntu@130.206.115.30

############################################################################
######

NOTE: You have accessed a system owned by FIWARE Lab. You must have
authorisation

before using it, and your use will be strictly limited to that indicated in
the

authorisation.

Unauthorised access to this system or improper use of the same is prohibited
and

is against the FIWARE Terms & Conditions Policy and the legislation in
force. The

use of this system may be monitored.

############################################################################
#####

Permission denied (publickey).

The system have also created the following files:

root@formica-VirtualBox:~/.docker/machine/machines/docker-host# ll

totale 40

drwx------ 2 root root 4096 giu 23 15:55 ./

drwx------ 3 root root 4096 giu 23 15:31 ../

r------- 1 root root 1029 giu 23 15:35 ca.pem

r------- 1 root root 1070 giu 23 15:35 cert.pem

r------- 1 root root 3271 giu 23 15:36 config.json

rw------ 1 root root 1675 giu 23 15:31 id_rsa

r------- 1 root root 381 giu 23 15:31 id_rsa.pub

r------- 1 root root 1675 giu 23 15:35 key.pem

r------- 1 root root 1679 giu 23 15:35 server-key.pem

r------- 1 root root 1123 giu 23 15:35 server.pem

Thank you

Best regards

<http://www.terasrl.it/> per firma posta