Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
Sender Email:
-
HD-Node:Berlin
Description
Hi,
I've sent a few error reports before. I forgot to mention that those
happened using the Budapest region. I thought I'd give the Berlin one a
try. For Berlin, I'm both able to import an SSH public key (see my report
erlier about the problem in the Budapest region) and the security group
editing is faster (adding a rule is usually on the order of magnitude of
1-2 secs).
However, in Berlin, I'm not able to get a public IP. I tried allocating
from both federation-ext-net-01 and public-ext-net-01 (no idea what the
difference is), but neither works:
The error message I get is not very useful: {"computeFault": {"message":
"The server has either erred or is incapable of performing the requested
operation.", "code": 500}}
Cheers,
Laszlo
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help
[Created via e-mail received from: =?UTF-8?B?TMOhc3psw7MgTcOhcmFp?= <atleta@psychask.com>]
Activity
Field | Original Value | New Value |
---|---|---|
Component/s | FIWARE-LAB-HELP [ 10279 ] |
Assignee | Berlin Node Helpdesk [ supportteam ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Resolution | Done [ 10000 ] | |
Status | In Progress [ 3 ] | Closed [ 6 ] |
Sender Email | atleta@psychask.com |
Summary | [Fiware-lab-help] Can't allocate public IP address in the Berlin region | FIWARE.Request.Lab.Can't allocate public IP address in the Berlin region. |
HD-Node | Berlin [ 10914 ] |
Summary | FIWARE.Request.Lab.Can't allocate public IP address in the Berlin region. | FIWARE.Request.Lab.Berlin.Can't allocate public IP address in the Berlin region. |
Fix Version/s | 2021 [ 12600 ] |
Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
---|---|---|---|---|---|---|---|---|---|
|
2d 20h 57m | 1 | Berlin Node Helpdesk | 05/May/15 4:20 PM | |||||
|
23d 18h | 1 | Berlin Node Helpdesk | 29/May/15 10:21 AM |
Dear User, the Berlin node is currently short on floating IPs.
We will inform you when there are public IPs available again.
This will happen most likely past the current upgrade.
Please note that in order to provide a public IP to you we are required by law to receive your contact Information (e.g. Name, Company, e-mail). We would also need your tenant ID (project ID) to assign the IP to the correct project, and we would need the protocols and ports to open up for this IP in the infrastructure's firewall.
Ideally this should match the security rules that you apply to your instances.
Please note: The Berlin node is currently under maintenance and will be available again at or after Thursday, May 7th. We are upgrading to a new OpenStack release and will increase our resource offerings for a better user experience. When logging in again, you will find a snapshot of your current instances (if any) under the "Images" or "Snapshot" tab that you just need to re-instantiate.