Zahos:
In order solve the timeout problem we need to to know the IP from which you will be launching docker machine. Could you provide this to Theofanis?

--Ken

> Re: [FI-WARE-JIRA] (HELP-4623) [Fiware-tech-help] Working with >Docker Docker Image and FIWare Lab
>zahos pap
>to:
>Kenneth Nagin, John Sokianos, super mario, Dimitris Karantonis
>06/10/2015 07:47 PM
>Hide Details
>From: zahos pap <zacpapac04@gmail.com>
>To: Kenneth Nagin/Haifa/IBM@IBMIL, John Sokianos ><ysokianos@gmail.com>, super mario <mariosprotos@gmail.com>, >Dimitris Karantonis <dkarantonis@gmail.com>
>History: This message has been forwarded.
>
>Hi Ken,
>Thanks for your response. Unfortunately we have an account only to this >node (PiraeusN). and we have no access to Spain2 and Crete node.
>It will be very helpful to work successfully with docker machine in order to >sync our lab with FIware-Lab.
>Thanks a lot,
>
>Zahos,
>>On Tue, Oct 6, 2015 at 5:44 PM, Kenneth Nagin <NAGIN@il.ibm.com> >>wrote:

>>Dear Zahos:
>>I am able to reproduce your problem on the PiraeusN node, but I still >>don't know what is the root cause. Fortunately, I see that it does not >>occur some other nodes that I have tried, namely Spain2 and Crete.
>>I will keep investigating the problem, but a work around would be to try >>on another node if you have access.

>>> Dear Sir/Madam,
>>> I would link to ask, if it is possible to use the FIWare Lab in conjunction
>>> with Docker.
>>> I found a presentation of Docker machine and Fiware at
>>> http://www.slideshare.net/knagin/simple-docker-hosting-on-fiware-lab
>>> however when I tried it I was getting the message
>>> Error creating machine: Get
>>> http://185.23.171.2:9696/v2.0/networks?name=node-int-net-01: dial tcp
>>> 185.23.171.2:9696: i/o timeout
>>> You will want to check the provider to make sure the machine and associated
>>> resources were properly removed.
>>> I am using the PiraeusN nodewith flavour 5(Beezon) for the
>>> zacpapac04 cloud (ID 9ffd757da2984ba39948e27640d5862d)
>>> Any suggestions?
>>> Thanks,
>>> BeeZon IoT Solutions
>>> Zacharias Papachristos
>>> Thanks,
>>> 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-tech-help@lists.fiware.org) instead of the old one.
>>> _______________________________________________
>>> Fiware-tech-help mailing list
>>> Fiware-tech-help@lists.fiware.org
>>> https://lists.fiware.org/listinfo/fiware-tech-help
>>> [Created via e-mail received from: zahos pap >>><zacpapac04@gmail.com>]

>>>--Ken

Re: Calls to openstack timeout on PiraeusN
Theofanis Katsiaounis
to:
Kenneth Nagin
07/10/2015 05:46 PM
Cc:
Álvaro Alonso
Hide Details
From: Theofanis Katsiaounis <th_katsiaounis@neuropublic.gr>
To: Kenneth Nagin/Haifa/IBM@IBMIL
Cc: Álvaro Alonso <aalonsog@dit.upm.es>

Dear Kenneth,
the case is just as you describe it. Openstack calls are allowed only to the FIWARE cloud portal IP.
We've actually been running like that since the beginning of the project but i will be happy to add to the access list the user's real IP.

Regards
Theofanis Katsiaounis

On 07/10/2015 05:37 μμ, Kenneth Nagin wrote:

Dear Theofanis:

I am the lead of the FIWARE cloud chapter and also responsible for the Docker GE.

I have received a help desk issue (https://jira.fiware.org/browse/HELP-4623) from a user of the PiraeusN. I suspect it is related to how the PiraeusN firewall is configured to handle openstack calls or
something else about your openstack configuration.

The background is that I created a tutorial on how a FIWARE developer could create and manage their docker hosts and containers on the FIWARE Lab remotely using their local docker client.
This is the tutorial http://www.slideshare.net/knagin/simple-docker-hosting-on-fiware-lab
It describes how to use docker machine to deploy docker hosts on a OpenStack provider, i.e. FIWARE. I've validated the instructions on a few of the FIWARE nodes, i.e. Spain2, Crete, and Lanion,
However it times out when doing its first simple query to Openstack after clearing its credentials with the Keystone identity manager.

The user followed the instructions on PiraeusN, but docker machine times out after getting the authorization token from Keystone. The timeout occurs when it tries to verify the network:
> http://185.23.171.2:9696/v2.0/networks?name=node-int-net-01:dial tcp
> 185.23.171.2:9696: i/o timeout

I tried a similar operation outside docker machine to list volumes and I also see a timeout:
>panic: Post http://185.23.171.2:8776/v1/34b51f78d6b8422bb7cff7f75be5543b/volumes:dial tcp 185.23.171.2:8776: i/o timeout

Is it possible that you have your firewall configured to only allow the Cloud Portal GUI to interact with openstack?

Best Regards,

Kenneth Nagin
Ph: +972-4-8296227
Cell: 054-6976227
Fx: +972-4- 8296114
http://researcher.ibm.com/view.php?person=il-NAGIN

Αποποίηση ευθυνών / Disclaimer

Theofanis:
Have you added Zahos's IP to the openstack user list?

Best Regards,

Kenneth Nagin
Ph: +972-4-8296227
Cell: 054-6976227
Fx: +972-4- 8296114
http://researcher.ibm.com/view.php?person=il-NAGIN

zahos pap <zacpapac04@gmail.com> wrote on 08/10/2015 06:09:49 PM:

> From: zahos pap <zacpapac04@gmail.com>
> To: th_katsiaounis@neuropublic.gr
> Cc: Kenneth Nagin/Haifa/IBM@IBMIL, super mario
> <mariosprotos@gmail.com>, John Sokianos <ysokianos@gmail.com>,
> Dimitris Karantonis <dkarantonis@gmail.com>
> Date: 08/10/2015 06:09 PM
> Subject: Re: [FI-WARE-JIRA] (HELP-4623) [Fiware-tech-help] Working
> with Docker Docker Image and FIWare Lab
>
> Hi Theodore and Ken,

> I suppose that you need the ip only to investigate the problem as
> this ip will not be the only one using the docker-machine.

> I tested the docker machine from ip 46.177.161.53

> Best regards,

> Zacharias Papachristos,
> Beezon IoT Solutions,
>
> On Thu, Oct 8, 2015 at 11:48 AM, Help-Desk <jira-help-desk@fi-ware.org> wrote:
> Zahos:
> In order solve the timeout problem we need to to know the IP from
> which you will be launching docker machine.  Could you provide this
> to Theofanis?
>
> --Ken
>
>
> > Re: [FI-WARE-JIRA] (HELP-4623) [Fiware-tech-help] Working with
> >Docker Docker Image and FIWare Lab
> >zahos pap
> >to:
> >Kenneth Nagin, John Sokianos, super mario, Dimitris Karantonis
> >06/10/2015 07:47 PM
> >Hide Details
> >From: zahos pap <zacpapac04@gmail.com>
> >To: Kenneth Nagin/Haifa/IBM@IBMIL, John Sokianos ><ysokianos@gmail.com
> >, super mario <mariosprotos@gmail.com>, >Dimitris Karantonis <
> dkarantonis@gmail.com>
> >History: This message has been forwarded.
> >
> >Hi Ken,
> >Thanks for your response. Unfortunately we have an account only to
> this >node (PiraeusN). and we have no access to Spain2 and Crete node.
> >It will be very helpful to work successfully with docker machine in
> order to >sync our lab with FIware-Lab.
> >Thanks a lot,
> >
> >Zahos,
> >>On Tue, Oct 6, 2015 at 5:44 PM, Kenneth Nagin <NAGIN@il.ibm.com> >>wrote:
>
> >>Dear Zahos:
> >>I am able to reproduce your problem on the PiraeusN node, but I
> still >>don't know what is the root cause.   Fortunately,  I see
> that it does not >>occur some other nodes that I have tried, namely
> Spain2 and Crete.
> >>I will keep investigating the problem,  but a work around would be
> to try >>on another node if you have access.
>
> >>> Dear Sir/Madam,
> >>> I would link to ask, if it is possible to use the FIWare Lab in
> conjunction
> >>> with Docker.
> >>> I found a presentation of Docker machine and Fiware at
> >>> http://www.slideshare.net/knagin/simple-docker-hosting-on-fiware-lab
> >>> however when I tried it I was getting the message
> >>> Error creating machine: Get
> >>> http://185.23.171.2:9696/v2.0/networks?name=node-int-net-01: dial tcp
> >>> 185.23.171.2:9696: i/o timeout
> >>> You will want to check the provider to make sure the machine andassociated
> >>> resources were properly removed.
> >>> I am using the PiraeusN nodewith flavour 5(Beezon) for the
> >>> zacpapac04 cloud (ID 9ffd757da2984ba39948e27640d5862d)
> >>> Any suggestions?
> >>> Thanks,
> >>> BeeZon IoT Solutions
> >>> Zacharias Papachristos
> >>> Thanks,
> >>> 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-tech-
> help@lists.fiware.org) instead of the old one.
> >>> _______________________________________________
> >>> Fiware-tech-help mailing list
> >>> Fiware-tech-help@lists.fiware.org
> >>> https://lists.fiware.org/listinfo/fiware-tech-help
> >>> [Created via e-mail received from: zahos pap >>><zacpapac04@gmail.com>]
>
> >>>--Ken
>
>

> -------------------------------------------------------------------------------
> Kenneth Nagin created HELP-4623:
> -----------------------------------
>
>              Summary: [Fiware-tech-help] Working with Docker Docker
> Image and FIWare Lab
>                  Key: HELP-4623
>                  URL: https://jira.fiware.org/browse/HELP-4623
>              Project: Help-Desk
>           Issue Type: extRequest
>           Components: FIWARE-TECH-HELP
>             Reporter: FW External User
>
> This email was generated by the FIWARE JIRA (http://jira.fiware.org).

Hi Kenneth,
Yes we have added the IP to the access lists.

Regards,
fanis

From: Help-Desk <jira-help-desk@fi-ware.org>
To: <th_katsiaounis@neuropublic.gr>
Cc: <nagin@il.ibm.com>, <zacpapac04@gmail.com>, <mariosprotos@gmail.com>, <ysokianos@gmail.com>, <dkarantonis@gmail.com>
Sent: 14/10/2015 11:07 AM
Subject: [FI-WARE-JIRA] (HELP-4623) [Fiware-tech-help] Working with Docker Docker Image and FIWare Lab

Theofanis:
Have you added Zahos's IP to the openstack user list?  

Best Regards,

Kenneth Nagin
Ph: +972-4-8296227
Cell: 054-6976227
Fx: +972-4- 8296114
http://researcher.ibm.com/view.php?person=il-NAGIN

zahos pap <zacpapac04@gmail.com> wrote on 08/10/2015 06:09:49 PM:

-------------------------------------------------------------------------------
Kenneth Nagin created HELP-4623:
-----------------------------------

            Summary: [Fiware-tech-help] Working with Docker Docker Image and FIWare Lab
                Key: HELP-4623
                URL: https://jira.fiware.org/browse/HELP-4623
            Project: Help-Desk
         Issue Type: extRequest
         Components: FIWARE-TECH-HELP
           Reporter: FW External User

This email was generated by the FIWARE JIRA (http://jira.fiware.org).

Αποποίηση ευθυνών / Disclaimer

Zacharias:
Did you try docker-machine access now that your IP is added
to the PiraeusN openstack user list?

Best Regards,

Kenneth Nagin
Ph: +972-4-8296227
Cell: 054-6976227
Fx: +972-4- 8296114
http://researcher.ibm.com/view.php?person=il-NAGIN

Hi all,

I checked it again.

It seems that the problem has been resolved. However, I would like to
mention the command docker-machine ls which shows docker machines status,
shows the machines in timeout state.
The machines created successfully in FIWARE lab with label Running.
Also I had tested the docker-compose and docker-swarm with no problem.
Also for testing I build a apache2 server and works perfectly.
The same for the Orion Context Broker. We have no problem.

The only issue is the docker-machine command
Also, I would to ask that configuration works only from my ip?
If we want to test it from IP we must ask you, or is it open for whole
PiraeusN node?

I Have attach o docx with pictures about the steps and the problem.

Best Regards,

On Thu, Oct 15, 2015 at 4:57 PM, Help-Desk <jira-help-desk@fi-ware.org>

Dear Zacharias,
the commands work only form your IP. We would be happy to add further IP
addresses upon request.
As far as the docker problem is concerned we will take a look although
i do not really know if there is much we can do.

Regards
PiraeusN Node Helpdesk Team

Αποποίηση ευθυνών / Disclaimer

Hi Theofanis,

I would like to add 2 more IP to PiraeusN openstack node, if it is possible

• 79.167.133.241
• 51.254.200.160

Best Regards,

Zacharias Papachristos,

BeeZon IoT solutions,

On Tue, Oct 20, 2015 at 4:28 PM, Theofanis Katsiaounis <

Dear Zacharias,
access has been granted to the requested IP's.

Best Regards,
Theofanis Katsiaounis

Αποποίηση ευθυνών / Disclaimer