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

FIWARE.Request.Lab.Mexico.FW: Problem accessing HealthBail VM at FIWARE Lab

    Details

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

      Description

      Dear PiraeusN node team,

      We have a VM in the FIWARE Lab, assigned to the PiraeusN node, which has been created under my email address and is named:

      HOSTNAME: healthbail-dev
      Floating IP: 207.249.127.175

      Our HealthBail VM seems to be down and we are performing tests and evaluation on the HealthBail platform. I attach a couple of screenshots with the errors we get. Could you check this?

      Thank you in advance.

      Regards,

      Vasilis

      [Description: Description: Description: Description: Description: cid:image002.png@01CDB5D2.96C69A10]

      Vasilis Tountopoulos<v.tountopoulos@atc.gr> | Electrical and Computer Engineer, PhD | Deputy Head, Technical Implementation, Innovation Lab<http://ilab.atc.gr/>
      Tel: +30 210 6874300 | Fax: +30 210 6855564 | www.atc.gr<http://www.atc.gr/> | [cid:image002.png@01CE879D.7D53EB30] <http://www.linkedin.com/company/204698?trk=tyah> ATC on LinkedIn<http://www.linkedin.com/company/204698?trk=tyah>

      Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
      Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
      _______________________________________________
      Fiware-lab-help mailing list
      Fiware-lab-help@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-lab-help
      [Created via e-mail received from: Vasilis Tountopoulos <v.tountopoulos@atc.gr>]

      1. signature.asc
        0.2 kB
        FW External User
      1. image005.png
        4 kB
      2. image006.png
        0.4 kB
      3. Screen Shot 2016-02-18 at 17.35.39.png
        197 kB
      4. Screen Shot 2016-02-18 at 17.36.37.png
        198 kB

        Activity

        Hide
        fw.ext.user FW External User added a comment -

        Dear,

        I’ve just forwarded your request to the specific support.

        Daniele

        Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
        Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
        _______________________________________________
        Fiware-lab-help mailing list
        Fiware-lab-help@lists.fiware.org
        https://lists.fiware.org/listinfo/fiware-lab-help

        Show
        fw.ext.user FW External User added a comment - Dear, I’ve just forwarded your request to the specific support. Daniele Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost. Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one. _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fiware.org https://lists.fiware.org/listinfo/fiware-lab-help
        Hide
        neuropublic PiraeusN Node Helpdesk added a comment -

        Assigning this to PiraeusU helpdesk team. We got no such VM and the specified IP range is not ours. I assume it is the common Piraeus name that causes the problem.

        Show
        neuropublic PiraeusN Node Helpdesk added a comment - Assigning this to PiraeusU helpdesk team. We got no such VM and the specified IP range is not ours. I assume it is the common Piraeus name that causes the problem.
        Hide
        UPRC PiraeusU Node Helpdesk added a comment -

        Dear all,

        it seems that this particular description of the VM do not correspond to some instance on PiraeusU node.
        So please contact the user so as to clarify where the VM is hosted, as well as to provide some further info such as the instance id.

        Best Regards,
        PiraeusU node team.

        Show
        UPRC PiraeusU Node Helpdesk added a comment - Dear all, it seems that this particular description of the VM do not correspond to some instance on PiraeusU node. So please contact the user so as to clarify where the VM is hosted, as well as to provide some further info such as the instance id. Best Regards, PiraeusU node team.
        Hide
        neuropublic PiraeusN Node Helpdesk added a comment -

        Since according to RIPE the mentioned addresses belong to Mexico i forward you the request.

        Show
        neuropublic PiraeusN Node Helpdesk added a comment - Since according to RIPE the mentioned addresses belong to Mexico i forward you the request.
        Hide
        internetdelfuturo Mexico Node Support added a comment -

        Dear Vasilis,

        Sorry for the large delay for giving answer to your ticket.

        Let me comment that we had several issues related to the creation of virtual machines in the Mexican Node. This issues came from the incompatibility of our version of OpenStack with the version of FIWARE Spain and also with the configuration of our software infraestructure. This problem has been solved and we assume that the access to the virtual machines is also solved. Also you can reboot your virtual machine (from your FILab account, section "console"). So, with the reboot, the virtual machine take the appropriate settings.

        Could you please comment us if you problem has been solved?

        Mexican FIWARE Node Team

        Show
        internetdelfuturo Mexico Node Support added a comment - Dear Vasilis, Sorry for the large delay for giving answer to your ticket. Let me comment that we had several issues related to the creation of virtual machines in the Mexican Node. This issues came from the incompatibility of our version of OpenStack with the version of FIWARE Spain and also with the configuration of our software infraestructure. This problem has been solved and we assume that the access to the virtual machines is also solved. Also you can reboot your virtual machine (from your FILab account, section "console"). So, with the reboot, the virtual machine take the appropriate settings. Could you please comment us if you problem has been solved? Mexican FIWARE Node Team

          People

          • Assignee:
            internetdelfuturo Mexico Node Support
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: