The user said:
Hello Henar,

Thanks for your reply. This solved our problem. I had to delete the existing IP address first.

Regards,

René Smit

mail sent

Hi,

any new on that? Applicants told me that you have not contacted them.

Thanks,

Marc Palau
i2CAT - Software Engineering Group

Hi Fernado,

you can contact them through mail:

• René Smit (sdidit@gmail.com) is in charge of this issue
• Arvid Halma (arvid@traffic.direct) is the responsible of the project

I have told them that you will contact by email, please put me in cc to
track it.

Thanks,

Marc Palau
i2CAT - Software Engineering Group

Hi Fernando,

i put the applicants in cc as they will manage the issue directly.

@René: Fernando will take care of the floating IPs issue that you are
facing.

BR

Marc Palau
i2CAT - Software Engineering Group

Dear user,

I need that you give me details about your user account and region (I suppose that you use Spain2 but just to confirm it).

I need this information to check your quotas.

Best regards,
Fernando.-

Renamed attached file: '[FIWARE-JIRA] (HELP-6060) [Fiware-creatifi-coaching] [CreatiFi Brussels Hub] General Support #434: Docker hosting access' to '[FIWARE-JIRA] (HELP-6060) [Fiware-creatifi-coaching] [CreatiFi Brussels Hub] General Support #434_ Docker hosting access' because it contained invalid character(s).

Spam detection software, running on the system "fiware-forge-01", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.

Content preview: René Appearantly, your account has floating IP quota problem.
Your problem is not related to docker-machine or docker. I am go re-assign
the issue to another colleague that should be able help you. Fernando: René
is has account on the Spain region and he is not able to assign Floating
IPs to his project. [...]

Content analysis details: (4.7 points, 4.5 required)

pts rule name description
---- ---------------------- --------------------------------------------------
2.3 FSL_HELO_BARE_IP_1 FSL_HELO_BARE_IP_1
0.0 TVD_RCVD_IP4 TVD_RCVD_IP4
0.0 TVD_RCVD_IP TVD_RCVD_IP
1.2 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
2.3 FM_IS_IT_OUR_ACCOUNT Is it our account?
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS

René
Appearantly, your account has floating IP quota problem.
Your problem is not related to docker-machine or docker.
I am go re-assign the issue to another colleague that should be able help you.

Fernando:
René is has account on the Spain region and he is not
able to assign Floating IPs to his project.

--Ken

> Hello Kenneth,
>
> There is no other instance associated with the IP address. In the
> Security > Floating IPs tab I see one entry for 10.1.65.209, and the
> Instance and Fixed IP Address columns show a '-'.
>
> I do notice that there are no routers defined. But when I try to
> create one, I get:
>
> {"NeutronError": {"message": "Quota exceeded for resources:
> ['router']", "type": "OverQuota", "detail": ""}}
>

Hello Kenneth,

There is no other instance associated with the IP address. In the Security
Fixed IP Address columns show a '-'.

I do notice that there are no routers defined. But when I try to create
one, I get:

{"NeutronError": {"message": "Quota exceeded for resources: ['router']",
"type": "OverQuota", "detail": ""}}

René Smit

2016-03-15 11:49 GMT+01:00 Help-Desk <jira-help-desk@fi-ware.org>:

It is nice to see that we are making progress.
The problem does not seem to related to docker-machine.
There is must be a free floating IP to for the VM.

Do you have another VM running that can be terminated to free up their IP?

If there are no other VMs running then try creating a VM and then associating a floating IP to it.

> From: René Smit <sdidit@gmail.com>
> To: Kenneth Nagin/Haifa/IBM@IBMIL
> Cc: arvid@traffic.direct, Marc Palau <marc.palau@i2cat.net>
> Date: 15/03/2016 11:54 AM
> Subject: Re: [FIWARE-JIRA] (HELP-6060) [Fiware-creatifi-coaching]
> [CreatiFi Brussels Hub] General Support #434: Docker hosting access
>
> Hello Kenneth,
>
> The tenant name was already specified through "export
> OS_TENANT_NAME=displaydirect cloud" (this was in the file that could
> be downloaded from our account). However, as per your direction, I
> specified this on the commandline instead, and this helped get rid
> of the earlier error message. So I decided to change all environment
> variables to commandline parameters, and ended up with the following command:
>
> $ docker-machine create -d openstack --openstack-flavor-id="2" –
> openstack-image-id="3a39252a-ec91-4b7e-a33c-a49f9791712c" –
> openstack-net-name="node-int-net-01" -openstack-floatingip
> pool="federation-ext-net-01" --openstack-sec-groups="dd" –
> openstack-keypair-name="dd" --openstack-private-key-file="dd.pem" –
> openstack-ssh-user="ubuntu" --openstack-tenant-name="displaydirect
> cloud" --openstack-region="Spain2" --openstack-auth-url="http://130.
> 206.84.8:4730/v3/" -openstack-domain-name="default" --openstack
> username="sander@display.direct" --openstack-password="fiware21"
> backoffice-fiware
> Running pre-create checks...
> Creating machine...
> (backoffice-fiware) Creating machine...
> Error creating machine: Error in driver during machine creation:
> Expected HTTP response code [200] when accessing [PUT http://130.
> 206.112.3:9696/v2.0/floatingips/3adffd72-6f39-4602-9839-5ce64c2f1a3b
> ], but got 404 instead
> {"NeutronError": {"message": "External network 38a6b9b6-0ab8-4461-
> bd03-061f3a861090 is not reachable from subnet 69c950ea-5ca6-462e-
> a023-8c022507266c.  Therefore, cannot associate Port
> 0eaa0894-3b9d-441e-8b01-9e388f8ec55a with a Floating IP.", "type":
> "ExternalGatewayForFloatingIPNotFound", "detail": ""}}
>
> Creating the machine now took a lot longer, and I can also see the
> created instance running and active on the dashboard.
> However, as you can see above, I still got an error message, and the
> instance does not have an associated floating IP. When I try to do
> that from the dashboard, I get a similar error:
>
> {"badRequest": {"message": "Unable to associate floating ip 10.1.65.
> 209 to fixed ip 192.168.236.199 for instance d4a48f05-4aac-44f0-
> afa0-69a6347d0d53. Error: External network 38a6b9b6-0ab8-4461-
> bd03-061f3a861090 is not reachable from subnet 69c950ea-5ca6-462e-
> a023-8c022507266c. Therefore, cannot associate Port
> 0eaa0894-3b9d-441e-8b01-9e388f8ec55a with a Floating IP.", "code": 400}}
>
> René Smit

René:
I think the solution to your problem is to user the --openstack-tenant-name flag to specify the tenant with which you defined the security groups. Otherwise the system assumes it the default tenant, <your name> cloud.
Also note the image that you are using (base_ubuntu_14.04) does not allow login to root, so you need to specify --openstack-ssh-user="ubuntu"

--Ken

Since the user wanted to be contacted directly I answered him with this reply:

Maybe I am missing something but at first glance it looks like you have not defined a security group as described in the slides.
Error creating machine: Error in driver during machine creation: Expected HTTP response code [201 202] when accessing [POST http://130.206.112.3:8774/v2/01a4e5ba6dab42278078b555791a4aa5/servers], but got 400 instead {"badRequest": {"message": "Unable to find security_group with name 'dd'", "code": 400}}

I am still waiting for a response.

--Ken

Dear,
given that the issue is related to sensitive data, I suggest you to forward the issue to the Docker owner, Kenneth Nagin, in order to contact in a private way the CreatiFI accelerator. Contact point is Marc Palau: marc.palau@i2cat.net
BR