Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-2380

FIWARE.Request.Lab.Berlin.Error Public IP Region Berlin.

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-LAB-HELP
    • Labels:
      None

      Description

      Dear Lab Developers,

      we tried to allocate a public IP-Address in Region "Berlin" in FIWARE
      Cloud Portal for our Project "Comic", but we got the following error:
      Error: Error allocating IP address. Cause: 500 Error {"computeFault":
      {"message": "The server has either erred or is incapable of performing
      the requested operation.", "code": 500}}

      Can you tell me please, why have we this error message and can you
      allocate a public IP for our account (Login: fiware@digital-worx.de
      <fiware@digital-worx.de>) please.
      We create in Project "Comic" a mobile application. Any communication
      between APP (Mobile) and server without public IP are not possible.

      Tank you for your cooperation & help.

      -------------------------------------
      digital worx GmbH
      Schulze-Delitzsch-Str. 16
      70565 Stuttgart

      Tel. 0711 220 40 93 0
      Fax. 0711 220 40 93 44

      m.ross@digital-worx.de

      http://www.digital-worx.de
      http://www.facebook.com/digital.worx.de

      -------------------------------------

      Geschaeftsfuehrer:
      Sven Rahlfs
      Mirko Ross

      HRB 22 5281 Amtsgericht Stuttgart
      USt.-Id. Nr.: DE218401190

      -------------------------------------

      _______________________________________________
      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: Mirko Ross <m.ross@digital-worx.de>]

      1. signature.asc
        0.2 kB
        Daniele Santoro

        Activity

        Hide
        danieles Daniele Santoro added a comment -

        Dear,

        I know in Berlin networks are managed by Neutron OpenStack component, therefore you may create your network as explained here:
        http://stackoverflow.com/questions/27543127/deploy-vm-in-fiware-lab-nodes-with-neutron. Did you follow the right procedure ?

        In any case another reason could be there are no more public IP available in the pool, so I’ve assigned your request to Berlin support team.

        Best,
        Daniele

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

        Show
        danieles Daniele Santoro added a comment - Dear, I know in Berlin networks are managed by Neutron OpenStack component, therefore you may create your network as explained here: http://stackoverflow.com/questions/27543127/deploy-vm-in-fiware-lab-nodes-with-neutron . Did you follow the right procedure ? In any case another reason could be there are no more public IP available in the pool, so I’ve assigned your request to Berlin support team. Best, Daniele _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help
        Hide
        florian Florian Schreiner added a comment -

        Hi Daniel,

        thanks for your support. Yes, we already checked all points - also as already described in tutorials and stackoverflow. But the public IP could not assigned. For me it looks like public ip's are not available.

        That's quite frustrating, because developers are losing time on fundamental work of setting up the FIWARE GE's in the LAB.

        So we are blocked now. Is there a direct contact on the berlin support team?

        Kind regards

        Mirko

        Show
        florian Florian Schreiner added a comment - Hi Daniel, thanks for your support. Yes, we already checked all points - also as already described in tutorials and stackoverflow. But the public IP could not assigned. For me it looks like public ip's are not available. That's quite frustrating, because developers are losing time on fundamental work of setting up the FIWARE GE's in the LAB. So we are blocked now. Is there a direct contact on the berlin support team? Kind regards Mirko
        Hide
        florian Florian Schreiner added a comment -

        Hi Mirco,

        I have forwarded your E-Mail to the Berlin Node Support directly. They should contact you very soon.

        Best regards,
        Florian

        Show
        florian Florian Schreiner added a comment - Hi Mirco, I have forwarded your E-Mail to the Berlin Node Support directly. They should contact you very soon. Best regards, Florian
        Hide
        BerlinSupportTeam Berlin Node Helpdesk added a comment -

        Sorry, users are consuming and blocking floating IPs quicker than we can recover them since they are not freed up automatically.
        This will remain an issue and cannot be resolved by providing more floating-IPs.
        We will try to release some unused addresses.
        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) or on a different region.
        Public IPs are the most limited resource and availability cannot be guaranteed.

        Show
        BerlinSupportTeam Berlin Node Helpdesk added a comment - Sorry, users are consuming and blocking floating IPs quicker than we can recover them since they are not freed up automatically. This will remain an issue and cannot be resolved by providing more floating-IPs. We will try to release some unused addresses. 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) or on a different region. Public IPs are the most limited resource and availability cannot be guaranteed.

          People

          • Assignee:
            BerlinSupportTeam Berlin Node Helpdesk
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: