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

FIWARE.Request.Lab.Spain.Serious problems identified by developers using the FIWARE Lab Cloud (reported by CreateFI FIWARE accelerator project)

    Details

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

      Description

      -------- Original Message --------
      Subject: CreatiFI - Technical Support (continued)
      Date: Mon, 29 Sep 2014 17:12:48 +0200
      From: Ingrid Willems <ingrid.willems@iminds.be><ingrid.willems@iminds.be>
      To: De Lama Sanchez, Nuria <nuria.delama@atos.net><nuria.delama@atos.net>
      CC: juanjose.hierro@telefonica.com<juanjose.hierro@telefonica.com> <juanjose.hierro@telefonica.com><juanjose.hierro@telefonica.com>, Fabio Antonelli <fabio.antonelli@create-net.org><fabio.antonelli@create-net.org>, Philippe Seynaeve <philippe.seynaeve@iminds.be><philippe.seynaeve@iminds.be>, Pieter Ballon <pieter.ballon@iminds.be><pieter.ballon@iminds.be>

      Dear Nuria,

      As to our email conversation of last week concerning the technical problems we were encountering, please find herewith an overview of the most urgent issues. I would like to thank Fabio Antonelli (CREATE-NET), who is providing technical support in the CreatiFI consortium, for the consolidation of below issues from multiple sources.

      The most urgent, identified problems are linked to the FIWARE Cloud Portal of FI-LAB. It is the first touch point, the entry point for developers wanting to explore FIWARE. They start with checking the cloud infrastructure, instantiating some VMs with some GEs deployed in order to start using the environment for development.

      Upon receiving complaints on the FI-LAB portal, we verified the specific actions that caused problems. We have listed the most urgent/blocking issues,this first set of show stoppers, as we deem it important to understand how to solve them.

      Let me be very humble. Some problems might arise from lack of knowledge about the infrastructure on our side. We used all available documentation to conduct the tests; nevertheless the portal seems under continuos development / ongoing maintenance as it is not always reachable, the interfaces freezes regularly. We tested the below described activities multiple times, but we were not able to successfully use the cloud portal.

      Blocking problems:

      1. Creation of a new VM from an existing image and access for starting the development activities:

      Using the FIWARE cloud portal (FI-LAB), it was possible to create a new VM (with different flavours, on different nodes), but the access to the created VM was possible only under the following conditions:

      • with SUCCESS: only on the Spain node, using a ssh terminal.
      • FAILURE:
      • on ANY tested node (Spain, Trento, Berlin): no way to access the VM using the FI-LAB GUI “Virtual Machine display”. Tried on different nodes, different browser without success. Seems a GUI problem.
      • on Trento node: the VM creation process is blocked on step "3.Networking”:
      • case A: no predefined available network is present at step 3 of the workflow; trying to create an own network from the cloud portal is not possible, so no further steps for finishing the creation of a VM is possible;
      • case B: now (why we didn’t see it in the previous tests?) we see an internal network available to be associated to the VM; associating it we can finally successfully create the VM. Later, after allocating an IP to the project and trying to associate it to the newly cerated VM we get a generic error (floating IP -> Associate IP : Error: cause: unknown). Not being able to allocate a public IP to the VM we cannot make it accessible via ssh.
      • on Berlin node: no key pair is available from the previously created ones; trying to create a new key pair generates an error (Error creating key pair. Cause: 500 Error). Neither the import of a self-generated key pair works. Without a key pair the workflow of VM creation is not possible.

      Looking forward to your feedback.

      Kind regards,

      Ingrid

      http://www.iminds.be/%7E/media/iminds/images/logos/footers/logo_ilaboIngrid Willems
      Entrepreneur in Residence

      iMinds vzw | Gaston Crommenlaan 8 box 102 | 9050 Ghent | Belgium | www.iminds.be<http://www.iminds.be>

      T: | F: +32 9 331 48 05<tel:%2B32%209%20331%2048%2005> | M:

      http://www.iminds.be/%7E/media/Images/conf2014_mailfooter_september<http://www.iminds.be/en/iminds-the-conference-2014>

      ________________________________

      Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

      The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

      Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição

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

        Activity

        FIWARE-LAB-HELP FIWARE-LAB-HELP created issue -
        mev Manuel Escriche made changes -
        Field Original Value New Value
        Link This issue is cloned by HELP-308 [ HELP-308 ]
        mev Manuel Escriche made changes -
        Description


        -------- Original Message --------
        Subject: CreatiFI - Technical Support (continued)
        Date: Mon, 29 Sep 2014 17:12:48 +0200
        From: Ingrid Willems <ingrid.willems@iminds.be><mailto:ingrid.willems@iminds.be>
        To: De Lama Sanchez, Nuria <nuria.delama@atos.net><mailto:nuria.delama@atos.net>
        CC: juanjose.hierro@telefonica.com<mailto:juanjose.hierro@telefonica.com> <juanjose.hierro@telefonica.com><mailto:juanjose.hierro@telefonica.com>, Fabio Antonelli <fabio.antonelli@create-net.org><mailto:fabio.antonelli@create-net.org>, Philippe Seynaeve <philippe.seynaeve@iminds.be><mailto:philippe.seynaeve@iminds.be>, Pieter Ballon <pieter.ballon@iminds.be><mailto:pieter.ballon@iminds.be>


        Dear Nuria,

        As to our email conversation of last week concerning the technical problems we were encountering, please find herewith an overview of the most urgent issues. I would like to thank Fabio Antonelli (CREATE-NET), who is providing technical support in the CreatiFI consortium, for the consolidation of below issues from multiple sources.

        The most urgent, identified problems are linked to the FIWARE Cloud Portal of FI-LAB. It is the first touch point, the entry point for developers wanting to explore FIWARE. They start with checking the cloud infrastructure, instantiating some VMs with some GEs deployed in order to start using the environment for development.

        Upon receiving complaints on the FI-LAB portal, we verified the specific actions that caused problems. We have listed the most urgent/blocking issues,this first set of show stoppers, as we deem it important to understand how to solve them.

        Let me be very humble. Some problems might arise from lack of knowledge about the infrastructure on our side. We used all available documentation to conduct the tests; nevertheless the portal seems under continuos development / ongoing maintenance as it is not always reachable, the interfaces freezes regularly. We tested the below described activities multiple times, but we were not able to successfully use the cloud portal.

        Blocking problems:

        1. Creation of a new VM from an existing image and access for starting the development activities:

        Using the FIWARE cloud portal (FI-LAB), it was possible to create a new VM (with different flavours, on different nodes), but the access to the created VM was possible only under the following conditions:

          * with SUCCESS: only on the Spain node, using a ssh terminal.
          * FAILURE:
             * on ANY tested node (Spain, Trento, Berlin): no way to access the VM using the FI-LAB GUI “Virtual Machine display”. Tried on different nodes, different browser without success. Seems a GUI problem.
             * on Trento node: the VM creation process is blocked on step "3.Networking”:
                * case A: no predefined available network is present at step 3 of the workflow; trying to create an own network from the cloud portal is not possible, so no further steps for finishing the creation of a VM is possible;
                * case B: now (why we didn’t see it in the previous tests?) we see an internal network available to be associated to the VM; associating it we can finally successfully create the VM. Later, after allocating an IP to the project and trying to associate it to the newly cerated VM we get a generic error (floating IP -> Associate IP : Error: cause: unknown). Not being able to allocate a public IP to the VM we cannot make it accessible via ssh.
             * on Berlin node: no key pair is available from the previously created ones; trying to create a new key pair generates an error (Error creating key pair. Cause: 500 Error). Neither the import of a self-generated key pair works. Without a key pair the workflow of VM creation is not possible.

        Usability problems:

        2. Inconsistent FIWARE cloud portal GUI:

        The GUI, tested on different browsers, seems to suffer of caching and refresh problems. We experienced strange visualisation problems (for example, when changing the node - e.g. Spain, Berlin, etc.- the GUI doesn’t refresh presented info, such as list of VMs created on the various nodes; same for key pairs available on the various nodes). At the end, we discovered that performing a “clear cache” on browsers, the info is presented again in a consistent way.

        3. Slow FIWARE cloud portal GUI refresh:

        When changing the project or the nodes, refresh time can be long and no progress bar is displayed. This leads to potential inconsistencies in the displayed information and becomes confusing for the user to understand which info is effectively displayed at a given time.

        Need clarifications on available configurations in the FIWARE cloud portal:

        4. Undocumented/unclear features:

          * On the different nodes there are different sets of available images of VMs. Is this the expected behaviour? Different nodes (e.g. Spain, Trento, Berlin) will host different types of VMs?
          * There is no clear indication which images are released with an already pre-installed generic enabler. This can be guessed by the name of the image file, but also in this case not all GEs are available, different sets are available in the different nodes. Is there a document mapping GEs to VM images?
          * Available images seem to host (maximum) one pre-installed GE. What happens if I need to instantiate more than one GE within the same VM (for some architectural reason?) Do we have to start with an image hosting a preinstalled GE and then install manually the other needed GEs? What about using the blueprints? In the last case, we don’t see GEs available in the software catalog. So, how is the suggested way to proceed?

        Looking forward to your feedback.

        Kind regards,

        Ingrid



        [http://www.iminds.be/%7E/media/iminds/images/logos/footers/logo_ilabo]Ingrid Willems
        Entrepreneur in Residence



        iMinds vzw | Gaston Crommenlaan 8 box 102 | 9050 Ghent | Belgium | www.iminds.be&lt;http://www.iminds.be>

        T: | F: +32 9 331 48 05<tel:%2B32%209%20331%2048%2005> | M:

        [http://www.iminds.be/%7E/media/Images/conf2014_mailfooter_september]<http://www.iminds.be/en/iminds-the-conference-2014>



        ________________________________

        Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

        The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

        Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição

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

        -------- Original Message --------
        Subject: CreatiFI - Technical Support (continued)
        Date: Mon, 29 Sep 2014 17:12:48 +0200
        From: Ingrid Willems <ingrid.willems@iminds.be><mailto:ingrid.willems@iminds.be>
        To: De Lama Sanchez, Nuria <nuria.delama@atos.net><mailto:nuria.delama@atos.net>
        CC: juanjose.hierro@telefonica.com<mailto:juanjose.hierro@telefonica.com> <juanjose.hierro@telefonica.com><mailto:juanjose.hierro@telefonica.com>, Fabio Antonelli <fabio.antonelli@create-net.org><mailto:fabio.antonelli@create-net.org>, Philippe Seynaeve <philippe.seynaeve@iminds.be><mailto:philippe.seynaeve@iminds.be>, Pieter Ballon <pieter.ballon@iminds.be><mailto:pieter.ballon@iminds.be>


        Dear Nuria,

        As to our email conversation of last week concerning the technical problems we were encountering, please find herewith an overview of the most urgent issues. I would like to thank Fabio Antonelli (CREATE-NET), who is providing technical support in the CreatiFI consortium, for the consolidation of below issues from multiple sources.

        The most urgent, identified problems are linked to the FIWARE Cloud Portal of FI-LAB. It is the first touch point, the entry point for developers wanting to explore FIWARE. They start with checking the cloud infrastructure, instantiating some VMs with some GEs deployed in order to start using the environment for development.

        Upon receiving complaints on the FI-LAB portal, we verified the specific actions that caused problems. We have listed the most urgent/blocking issues,this first set of show stoppers, as we deem it important to understand how to solve them.

        Let me be very humble. Some problems might arise from lack of knowledge about the infrastructure on our side. We used all available documentation to conduct the tests; nevertheless the portal seems under continuos development / ongoing maintenance as it is not always reachable, the interfaces freezes regularly. We tested the below described activities multiple times, but we were not able to successfully use the cloud portal.

        Blocking problems:

        1. Creation of a new VM from an existing image and access for starting the development activities:

        Using the FIWARE cloud portal (FI-LAB), it was possible to create a new VM (with different flavours, on different nodes), but the access to the created VM was possible only under the following conditions:

          * with SUCCESS: only on the Spain node, using a ssh terminal.
          * FAILURE:
             * on ANY tested node (Spain, Trento, Berlin): no way to access the VM using the FI-LAB GUI “Virtual Machine display”. Tried on different nodes, different browser without success. Seems a GUI problem.
             * on Trento node: the VM creation process is blocked on step "3.Networking”:
                * case A: no predefined available network is present at step 3 of the workflow; trying to create an own network from the cloud portal is not possible, so no further steps for finishing the creation of a VM is possible;
                * case B: now (why we didn’t see it in the previous tests?) we see an internal network available to be associated to the VM; associating it we can finally successfully create the VM. Later, after allocating an IP to the project and trying to associate it to the newly cerated VM we get a generic error (floating IP -> Associate IP : Error: cause: unknown). Not being able to allocate a public IP to the VM we cannot make it accessible via ssh.
             * on Berlin node: no key pair is available from the previously created ones; trying to create a new key pair generates an error (Error creating key pair. Cause: 500 Error). Neither the import of a self-generated key pair works. Without a key pair the workflow of VM creation is not possible.

        Looking forward to your feedback.

        Kind regards,

        Ingrid



        [http://www.iminds.be/%7E/media/iminds/images/logos/footers/logo_ilabo]Ingrid Willems
        Entrepreneur in Residence



        iMinds vzw | Gaston Crommenlaan 8 box 102 | 9050 Ghent | Belgium | www.iminds.be&lt;http://www.iminds.be>

        T: | F: +32 9 331 48 05<tel:%2B32%209%20331%2048%2005> | M:

        [http://www.iminds.be/%7E/media/Images/conf2014_mailfooter_september]<http://www.iminds.be/en/iminds-the-conference-2014>



        ________________________________

        Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

        The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

        Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição

        _______________________________________________
        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 -
        Comment [ Request split for its allocation ]
        mev Manuel Escriche made changes -
        Assignee Manuel Escriche [Adm] [ mev ] Henar Muñoz [ henar ]
        mev Manuel Escriche made changes -
        Component/s FIWARE-LAB-HELP [ 10279 ]
        mev Manuel Escriche made changes -
        Workflow Basic Workflow [ 15390 ] FW eRequest Workflow [ 16309 ]
        Status To Do [ 10001 ] Open [ 1 ]
        Issue Type Question [ 10004 ] eRequest [ 10101 ]
        FI-WARE Environment FI-LAB [ 10100 ]
        mev Manuel Escriche made changes -
        Workflow FW eRequest Workflow [ 16309 ] eRequest Workflow-2 [ 16492 ]
        mev Manuel Escriche made changes -
        Workflow eRequest Workflow-2 [ 16492 ] FW eRequest Workflow [ 16868 ]
        mev Manuel Escriche made changes -
        Reporter FIWARE-LAB-HELP [ fiware-lab-help ] FW External User [ fw.external.urser ]
        henar Henar Muñoz made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        henar Henar Muñoz made changes -
        Resolution Done [ 10000 ]
        Status In Progress [ 3 ] Done [ 10000 ]
        mev Manuel Escriche made changes -
        Fix Version/s Sprint 4.1.2 [ 10738 ]
        backlogmanager Backlog Manager made changes -
        Summary [Fiware-lab-help] Serious problems identified by developers using the FIWARE Lab Cloud (reported by CreateFI FIWARE accelerator project) FIWARE.Request.Lab.Serious problems identified by developers using the FIWARE Lab Cloud (reported by CreateFI FIWARE accelerator project)
        mev Manuel Escriche made changes -
        Workflow FW eRequest Workflow [ 16868 ] FW extRequest Workflow-II [ 41011 ]
        Status Done [ 10000 ] Closed [ 6 ]
        Issue Type eRequest [ 10101 ] extRequest [ 10104 ]
        mev Manuel Escriche made changes -
        mev Manuel Escriche made changes -
        HD-Node Spain [ 10846 ]
        backlogmanager Backlog Manager made changes -
        Summary FIWARE.Request.Lab.Serious problems identified by developers using the FIWARE Lab Cloud (reported by CreateFI FIWARE accelerator project) FIWARE.Request.Lab.Spain.Serious problems identified by developers using the FIWARE Lab Cloud (reported by CreateFI FIWARE accelerator project)

          People

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

            Dates

            • Created:
              Updated:
              Resolved: