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

FIWARE.Request.Lab.Spain.Unable to allocate floating IPs

        Details

        • Type: extRequest
        • Status: Closed
        • Priority: Major
        • Resolution: Done
        • Fix Version/s: Sprint 4.1.1
        • Component/s: FIWARE-LAB-HELP
        • Labels:
          None
        • HD-Node:
          Spain

          Description

          Dear FI-LAB staffers,
          I get the following error when I try to add some floating IPs to my
          instances within the FI-LAB region (which is the default one). The error
          doesn't contain much information, unfortunately: "Error: undefined. Cause:
          unknow".

          Here's how I do this:

          • ensure some instances are up,
          • go to http://cloud.lab.fi-ware.org/#nova/access_and_security/
          • notice that the list of Floating IPs is empty
          • click "Allocate IP to Project"
          • in the new dialog, I can select "net8300"
          • I also see a green bar on the right telling me that there's one available
            IP address, and that "Floating IP" is zero right now
          • however, when I click "Allocate IP", the error shown above is returned

          The same also happens for the Trento and Berlin regions. I was able to
          allocate a floating IP in Waterford.

          With kind regards,
          Jan

          –
          Trojitá, a fast Qt IMAP e-mail client – http://trojita.flaska.net/
          _______________________________________________
          Fiware-lab-help mailing list
          Fiware-lab-help@lists.fi-ware.org
          https://lists.fi-ware.org/listinfo/fiware-lab-help

            Activity

            Ascending order - Click to sort in descending order
            FIWARE-LAB-HELP FIWARE-LAB-HELP created issue -
            Hide
            Permalink
            FIWARE-LAB-HELP FIWARE-LAB-HELP added a comment -

            Hi

            Thanks for contacting us. Regarding FI-LAB, we were running out of floating IP. You should be able to obtain one now.
            Regards,
            Henar

            ----Mensaje original----
            De: fiware-lab-help-bounces@lists.fi-ware.org fiware-lab-help-bounces@lists.fi-ware.org En nombre de Jan Kundrát
            Enviado el: domingo, 18 de mayo de 2014 23:48
            Para: fiware-lab-help@lists.fi-ware.org
            Asunto: [Fiware-lab-help] Unable to allocate floating IPs

            Dear FI-LAB staffers,
            I get the following error when I try to add some floating IPs to my instances within the FI-LAB region (which is the default one). The error doesn't contain much information, unfortunately: "Error: undefined. Cause:
            unknow".

            Here's how I do this:

            • ensure some instances are up,
            • go to http://cloud.lab.fi-ware.org/#nova/access_and_security/
            • notice that the list of Floating IPs is empty
            • click "Allocate IP to Project"
            • in the new dialog, I can select "net8300"
            • I also see a green bar on the right telling me that there's one available IP address, and that "Floating IP" is zero right now
            • however, when I click "Allocate IP", the error shown above is returned

            The same also happens for the Trento and Berlin regions. I was able to allocate a floating IP in Waterford.

            With kind regards,
            Jan

            –
            Trojitá, a fast Qt IMAP e-mail client – http://trojita.flaska.net/ _______________________________________________
            Fiware-lab-help mailing list
            Fiware-lab-help@lists.fi-ware.org
            https://lists.fi-ware.org/listinfo/fiware-lab-help

            ________________________________

            Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
            This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
            http://www.tid.es/ES/PAGINAS/disclaimer.aspx
            _______________________________________________
            Fiware-lab-help mailing list
            Fiware-lab-help@lists.fi-ware.org
            https://lists.fi-ware.org/listinfo/fiware-lab-help

            Show
            FIWARE-LAB-HELP FIWARE-LAB-HELP added a comment - Hi Thanks for contacting us. Regarding FI-LAB, we were running out of floating IP. You should be able to obtain one now. Regards, Henar ---- Mensaje original ---- De: fiware-lab-help-bounces@lists.fi-ware.org fiware-lab-help-bounces@lists.fi-ware.org En nombre de Jan Kundrát Enviado el: domingo, 18 de mayo de 2014 23:48 Para: fiware-lab-help@lists.fi-ware.org Asunto: [Fiware-lab-help] Unable to allocate floating IPs Dear FI-LAB staffers, I get the following error when I try to add some floating IPs to my instances within the FI-LAB region (which is the default one). The error doesn't contain much information, unfortunately: "Error: undefined. Cause: unknow". Here's how I do this: ensure some instances are up, go to http://cloud.lab.fi-ware.org/#nova/access_and_security/ notice that the list of Floating IPs is empty click "Allocate IP to Project" in the new dialog, I can select "net8300" I also see a green bar on the right telling me that there's one available IP address, and that "Floating IP" is zero right now however, when I click "Allocate IP", the error shown above is returned The same also happens for the Trento and Berlin regions. I was able to allocate a floating IP in Waterford. With kind regards, Jan – Trojitá, a fast Qt IMAP e-mail client – http://trojita.flaska.net/ _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help
            Hide
            Permalink
            FIWARE-LAB-HELP FIWARE-LAB-HELP added a comment -

            On Monday, 19 May 2014 08:08:15 CEST, HENAR MUÑOZ FRUTOS wrote:
            > Thanks for contacting us. Regarding FI-LAB, we were running out
            > of floating IP. You should be able to obtain one now.

            Dear Henar, thank you. However, it seems that I am only able to add a
            single floating IP address in total to my VMs, which means that the rest of
            them have no means of being accessed remotely. How is that supposed to be
            handled?

            Please note that the FI-LAB region does not allow me (at least not from the
            dashboard) to define a custom network and use it for setting up my own
            router, etc. Could you please comment on what is the desired scenario for
            using this service?

            With kind regards,
            Jan

            –
            Trojitá, a fast Qt IMAP e-mail client – http://trojita.flaska.net/
            _______________________________________________
            Fiware-lab-help mailing list
            Fiware-lab-help@lists.fi-ware.org
            https://lists.fi-ware.org/listinfo/fiware-lab-help

            Show
            FIWARE-LAB-HELP FIWARE-LAB-HELP added a comment - On Monday, 19 May 2014 08:08:15 CEST, HENAR MUÑOZ FRUTOS wrote: > Thanks for contacting us. Regarding FI-LAB, we were running out > of floating IP. You should be able to obtain one now. Dear Henar, thank you. However, it seems that I am only able to add a single floating IP address in total to my VMs, which means that the rest of them have no means of being accessed remotely. How is that supposed to be handled? Please note that the FI-LAB region does not allow me (at least not from the dashboard) to define a custom network and use it for setting up my own router, etc. Could you please comment on what is the desired scenario for using this service? With kind regards, Jan – Trojitá, a fast Qt IMAP e-mail client – http://trojita.flaska.net/ _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help
            Hide
            Permalink
            FIWARE-LAB-HELP FIWARE-LAB-HELP added a comment -

            Hi

            The current FI-LAB version doesn't provide networking capabilities. I will do it in short term. Now, you can access to the VM by the floating IP. Regarding the number of floating IPs, the quotas only provide 1 IP, since we are running out of IP. Anyway, you can access to the rest of VMs using the private network.
            Regards,
            Henar

            ----Mensaje original----
            De: fiware-lab-help-bounces@lists.fi-ware.org fiware-lab-help-bounces@lists.fi-ware.org En nombre de Jan Kundrát
            Enviado el: lunes, 19 de mayo de 2014 12:05
            Para: fiware-lab-help@lists.fi-ware.org
            Asunto: Re: [Fiware-lab-help] Unable to allocate floating IPs

            On Monday, 19 May 2014 08:08:15 CEST, HENAR MUÑOZ FRUTOS wrote:
            > Thanks for contacting us. Regarding FI-LAB, we were running out of
            > floating IP. You should be able to obtain one now.

            Dear Henar, thank you. However, it seems that I am only able to add a single floating IP address in total to my VMs, which means that the rest of them have no means of being accessed remotely. How is that supposed to be handled?

            Please note that the FI-LAB region does not allow me (at least not from the
            dashboard) to define a custom network and use it for setting up my own router, etc. Could you please comment on what is the desired scenario for using this service?

            With kind regards,
            Jan

            –
            Trojitá, a fast Qt IMAP e-mail client – http://trojita.flaska.net/ _______________________________________________
            Fiware-lab-help mailing list
            Fiware-lab-help@lists.fi-ware.org
            https://lists.fi-ware.org/listinfo/fiware-lab-help

            ________________________________

            Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
            This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
            http://www.tid.es/ES/PAGINAS/disclaimer.aspx
            _______________________________________________
            Fiware-lab-help mailing list
            Fiware-lab-help@lists.fi-ware.org
            https://lists.fi-ware.org/listinfo/fiware-lab-help

            Show
            FIWARE-LAB-HELP FIWARE-LAB-HELP added a comment - Hi The current FI-LAB version doesn't provide networking capabilities. I will do it in short term. Now, you can access to the VM by the floating IP. Regarding the number of floating IPs, the quotas only provide 1 IP, since we are running out of IP. Anyway, you can access to the rest of VMs using the private network. Regards, Henar ---- Mensaje original ---- De: fiware-lab-help-bounces@lists.fi-ware.org fiware-lab-help-bounces@lists.fi-ware.org En nombre de Jan Kundrát Enviado el: lunes, 19 de mayo de 2014 12:05 Para: fiware-lab-help@lists.fi-ware.org Asunto: Re: [Fiware-lab-help] Unable to allocate floating IPs On Monday, 19 May 2014 08:08:15 CEST, HENAR MUÑOZ FRUTOS wrote: > Thanks for contacting us. Regarding FI-LAB, we were running out of > floating IP. You should be able to obtain one now. Dear Henar, thank you. However, it seems that I am only able to add a single floating IP address in total to my VMs, which means that the rest of them have no means of being accessed remotely. How is that supposed to be handled? Please note that the FI-LAB region does not allow me (at least not from the dashboard) to define a custom network and use it for setting up my own router, etc. Could you please comment on what is the desired scenario for using this service? With kind regards, Jan – Trojitá, a fast Qt IMAP e-mail client – http://trojita.flaska.net/ _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help
            mev Manuel Escriche made changes -
            Field Original Value New Value
            Assignee Manuel Escriche [Administrator] [ mev ] Henar Muñoz [ henar ]
            henar Henar Muñoz made changes -
            Status To Do [ 10001 ] In Progress [ 3 ]
            henar Henar Muñoz made changes -
            Resolution Done [ 10000 ]
            Status In Progress [ 3 ] Done [ 10000 ]
            mev Manuel Escriche made changes -
            Component/s FIWARE-LAB-HELP [ 10279 ]
            mev Manuel Escriche made changes -
            Workflow Basic Workflow [ 12414 ] FW eRequest Workflow [ 16253 ]
            Issue Type Question [ 10004 ] eRequest [ 10101 ]
            FI-WARE Environment FI-LAB [ 10100 ]
            Resolution Done [ 10000 ]
            mev Manuel Escriche made changes -
            Resolution Done [ 10000 ]
            mev Manuel Escriche made changes -
            Workflow FW eRequest Workflow [ 16253 ] eRequest Workflow-2 [ 16632 ]
            mev Manuel Escriche made changes -
            Status Done [ 10000 ] In Progress [ 3 ]
            mev Manuel Escriche made changes -
            Status In Progress [ 3 ] Done [ 10000 ]
            mev Manuel Escriche made changes -
            Workflow eRequest Workflow-2 [ 16632 ] FW eRequest Workflow [ 16840 ]
            mev Manuel Escriche made changes -
            Fix Version/s Sprint 4.1.1 [ 10737 ]
            mev Manuel Escriche made changes -
            Reporter FIWARE-LAB-HELP [ fiware-lab-help ] FW External User [ fw.external.urser ]
            backlogmanager Backlog Manager made changes -
            Summary [Fiware-lab-help] Unable to allocate floating IPs FIWARE.Request.Lab.Unable to allocate floating IPs
            mev Manuel Escriche made changes -
            Workflow FW eRequest Workflow [ 16840 ] FW extRequest Workflow-II [ 40947 ]
            Status Done [ 10000 ] Closed [ 6 ]
            Issue Type eRequest [ 10101 ] extRequest [ 10104 ]
            mev Manuel Escriche made changes -
            HD-Node Spain [ 10846 ]
            backlogmanager Backlog Manager made changes -
            Summary FIWARE.Request.Lab.Unable to allocate floating IPs FIWARE.Request.Lab.Spain.Unable to allocate floating IPs
            Transition Time In Source Status Execution Times Last Executer Last Execution Date
            To Do To Do In Progress In Progress
            		15d 20h 51m 1 Henar Muñoz 10/Oct/14 11:24 AM
            Done Done In Progress In Progress
            		12d 11h 5m 1 Manuel Escriche 22/Oct/14 10:29 PM
            In Progress In Progress Done Done
            		1m 53s 2 Manuel Escriche 22/Oct/14 10:31 PM
            Done Done Closed Closed
            		446d 11h 38m 1 Manuel Escriche 12/Jan/16 9:10 AM

              People

              • Assignee:
                henar Henar Muñoz
                Reporter:
                fw.ext.user FW External User
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: