Dear Berlin support team,

Please directly send your answer to the user (hefernan@vub.ac.be)!

Thanks in advance!
Best,
Sandor
– on behalf of level-1 support team

Dear Helio,

I've just forwarded your email to the operators of Berlin node. They
will directly contact you soon.

Best regards,
Sandor
– On behalf of FIWARE level-1 support team

–
Sándor Laki
EU FP7 FI-PPP XIFI project,
Wigner Research Centre for Physics,
Hungarian Academy of Sciences
Konkoly Thege Miklós út 29-33.
H-1121, Budapest, Hungary
Cell: +36 70 374 2646
Skype: sandor.laki

XIFI: https://fi-xifi.eu/home.html
FI-PPP: http://www.fi-ppp.eu/

_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help

Dear Fiware tech support team,

Adding to the issues found I have also realized a couple of technical errors
too:

1) While deploying an instance, sometimes even when you specify that
only one should be created, the system creates 2. This might be the reason
why some of the nodes are running low on capacity? If everyone using the
systems has double time instances created this might cause a big issue.

2) In the Gent node (of my account, hefermam@vub.ac.be
<hefermam@vub.ac.be> ) I have 4 IP allocated

Allocate IP to Project

10.0.136.59

-

Federation-Net

10.0.136.60

-

Federation-Net

10.0.136.61

-

Federation-Net

10.0.136.62

-

Federation-Net

Which doesn’t makes sense as the quota is of 2. The system gives an error
when opening the allocate IP

Pool

ERROR: You exceeded the limit of Floating IPs

Description

Allocate a floating IP from a given floating ip pool.

Project Quotas

Floating IP (4)

-2 Available

So the issue is why it already allowed to go beyond the quota! And I believe
myself did not do 4 allocations. These might be perhaps related to the
double executions mentioned on point 1?

3) When trying to remove one of the extra allocated IP you get

Error: Error releasing floating IP 10.0.136.59. Cause: 503 Error

Hope this report can add some more color on the problems you are
experiencing.

Best regards

Helio

From: Sándor Laki laki.sandor@wigner.mta.hu
Sent: lunes, 02 de febrero de 2015 10:32
To: Helio Fernandez; fiware-lab-help@lists.fi-ware.org
Subject: Re: [Fiware-lab-help] FI-Lab Assistance

Dear Helio,

I've just forwarded your email to the operators of Berlin node. They will
directly contact you soon.

Best regards,
Sandor
– On behalf of FIWARE level-1 support team

2015.02.02. 10:27 keltezéssel, Helio Fernandez írta:

Hello,

I’m trying to launch an instance on the node of Berlin. There is no
possibility to add an IP address to the instance. This is a very impotant
issue as it makes virtually impossible to access the instance. Could you
give me further assistance?

Best regards

Helio

From: Helio Fernandez [ <hefernan@vub.ac.be>
hefernan@vub.ac.be]
Sent: jueves, 29 de enero de 2015 23:05
To: ' <fiware-lab-help@lists.fi-ware.org>
fiware-lab-help@lists.fi-ware.org'
Subject: FI-Lab Assistance

Hello,

I’m trying to set an IP address to one of my instance. It always gives an
error

undefined. Cause: 400 Error

{"badRequest": {"message": "Error. Unable to associate floating ip", "code":
400}}

OkCancel

Both the IP and the instance are in the berlin node.

Best regards

Helio

Please apologize,
floating IPs are a very scarce resource that users usually allocate but don't free up anymore.
We need to release some manually.
We are doing that frequently but they are usually allocated almost immediately again.
Please try to allocate an IP again after some time (you are actually allocating 2 at least - one for a default gateway and one for each publicly exposed VM).
Whe cannot guarantee availability of publicc IPs.

The observation that sometimes 2 instead of 1 VM are created is new to us.
We did not observe that before.
Would you kindly provide more information if possible, for example the precise time, so we can dig into the log files.

The issue that you are not able to release an allocated IP has also not observed before, but it fits into a commonly known symptom.
It seems to be related to the state of a VM marked as in error.
The IP has been release but not removed from the internal database since the command did not complete.
We will try to verify and remove this - but it will take some time.

Thank you for pointing us to this issue.

Dear technical team,

Do you have any updates o that matter? The platform continues to look
inoperative.

Best regards

Helio

From: Sándor Laki laki.sandor@wigner.mta.hu
Sent: lunes, 02 de febrero de 2015 10:32
To: Helio Fernandez; fiware-lab-help@lists.fi-ware.org
Subject: Re: [Fiware-lab-help] FI-Lab Assistance

Dear Helio,

I've just forwarded your email to the operators of Berlin node. They will
directly contact you soon.

Best regards,
Sandor
– On behalf of FIWARE level-1 support team

2015.02.02. 10:27 keltezéssel, Helio Fernandez írta:

Hello,

I’m trying to launch an instance on the node of Berlin. There is no
possibility to add an IP address to the instance. This is a very impotant
issue as it makes virtually impossible to access the instance. Could you
give me further assistance?

Best regards

Helio

From: Helio Fernandez hefernan@vub.ac.be
Sent: jueves, 29 de enero de 2015 23:05
To: 'fiware-lab-help@lists.fi-ware.org
<fiware-lab-help@lists.fi-ware.org> '
Subject: FI-Lab Assistance

Hello,

I’m trying to set an IP address to one of my instance. It always gives an
error

undefined. Cause: 400 Error

{"badRequest": {"message": "Error. Unable to associate floating ip", "code":
400}}

OkCancel

Both the IP and the instance are in the berlin node.

Best regards

Helio

Sorry - we freed up 6 floating IPs on Wednesday last week.
They have been consumed almost immediately.
We will try to free up once more.