Uploaded image for project: 'Help-Coaches-Desk'
  1. Help-Coaches-Desk
  2. HELC-1440

FIWARE.Request.Coach.INCENSe.Question on Market / Node

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Component/s: INCENSe
    • Labels:
      None

      Description

      Hello,

      I had this question:

      In the Mashup Market place I can not add / install new items,
      I get the error, using the Marketplace "Fiware Lab":

      Connection error: No resource retrieved.

      I also tried adding a new market place and launched instances therefore.
      When adding the market place i used their IP, e.g.

      http://192.168.100.234:8080/WMarket

      where the IP address is the IP of the instance.

      As I can not run the latest Orion Context Broker 5.2.
      Which would be the most updated node / could my account be moved there?

      Thanks a lot!

      Ridha
      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-incense-coaching@lists.fiware.org) instead of the old one.
      _______________________________________________
      Fiware-incense-coaching mailing list
      Fiware-incense-coaching@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-incense-coaching

      [Created via e-mail received from: Ridha Azaiz <ridha@aerialpower.com>]

        Issue Links

          Activity

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

          Comment by ridha@aerialpower.com :
          Hello,

          my default Fiware Lab Mashup / Marketplace still seems malfunctioning.
          (connection error).

          Do you think my account will be moved?
          If any easier, I do not mind if the account is closed/removed and opened
          new on Spain2.

          Kind Regards,

          Ridha

          Show
          fw.ext.user FW External User added a comment - Comment by ridha@aerialpower.com : Hello, my default Fiware Lab Mashup / Marketplace still seems malfunctioning. (connection error). Do you think my account will be moved? If any easier, I do not mind if the account is closed/removed and opened new on Spain2. Kind Regards, Ridha
          Hide
          pandriani Pasquale Andriani added a comment -

          Hi Ridha,
          please send a different email (with a different subject) for each question not related the "change FIWARE Lab node" issue, otherwise I cannot involve relevant people that will help you.

          Regards,
          P.

          Show
          pandriani Pasquale Andriani added a comment - Hi Ridha, please send a different email (with a different subject) for each question not related the "change FIWARE Lab node" issue, otherwise I cannot involve relevant people that will help you. Regards, P.
          Hide
          fw.ext.user FW External User added a comment -

          Comment by ridha@aerialpower.com :
          Thanks a lot!

          talking about IP addresses -

          I read about Idas and Figway, and in Step 3.1 it talks about Problems
          with being behind a NAT when using Figway:

          https://www.fiware.org/tag/figway/

          Where as in a "native IDAS implementation" the NAT problem is not mentioned:

          https://www.fiware.org/devguides/connection-to-the-internet-of-things/how-to-read-measures-captured-from-iot-devices/

          So would NAT be only a problem when using Figway when not using / having
          a router to configure?

          As a workaround I see a VPN or reversed SSH tunnel, albeit for VPN it
          might have to be a be an openVPN protocol as Microsoft's protocol can be
          NAT complicit i believe to have read.

          R

          Show
          fw.ext.user FW External User added a comment - Comment by ridha@aerialpower.com : Thanks a lot! talking about IP addresses - I read about Idas and Figway, and in Step 3.1 it talks about Problems with being behind a NAT when using Figway: https://www.fiware.org/tag/figway/ Where as in a "native IDAS implementation" the NAT problem is not mentioned: https://www.fiware.org/devguides/connection-to-the-internet-of-things/how-to-read-measures-captured-from-iot-devices/ So would NAT be only a problem when using Figway when not using / having a router to configure? As a workaround I see a VPN or reversed SSH tunnel, albeit for VPN it might have to be a be an openVPN protocol as Microsoft's protocol can be NAT complicit i believe to have read. R
          Hide
          pandriani Pasquale Andriani added a comment -

          Hi Ridha,
          I would ask to move your account to Spain2 node.

          Moreover:

          • about Orion different versions, please refer to the available documentation on FIWARE Catalogue.

          I will be back to you once your account will be moved.

          Regards,
          P.

          Show
          pandriani Pasquale Andriani added a comment - Hi Ridha, I would ask to move your account to Spain2 node. Moreover: read this - http://joseignaciocarretero.blogspot.it/2014/09/fiware-lab-only-one-single-ip-per-user.html - to access more than one VM with only 1 public IP about Orion different versions, please refer to the available documentation on FIWARE Catalogue. I will be back to you once your account will be moved. Regards, P.
          Hide
          fw.ext.user FW External User added a comment -

          Comment by ridha@aerialpower.com :
          Hi,

          With the default Marketplace "Fiware Lab" I get the red connection
          error, so I had thought to run my own WMarket might be a solution,
          unless this is a temporary problem.

          I can not allocate a new floating IP as my limit (1) is exceeded
          as I already have a floating IP on my Orion instance.

          On Orion,is there a lot different between R4.4 and R5.2?
          (e.g. NGSIv2 might not be in use in R4.4).

          Yes if the things can not be resolved maybe the node is not so good.

          Thanks for the quick reply,

          Ridha

          Show
          fw.ext.user FW External User added a comment - Comment by ridha@aerialpower.com : Hi, With the default Marketplace "Fiware Lab" I get the red connection error, so I had thought to run my own WMarket might be a solution, unless this is a temporary problem. I can not allocate a new floating IP as my limit (1) is exceeded as I already have a floating IP on my Orion instance. On Orion,is there a lot different between R4.4 and R5.2? (e.g. NGSIv2 might not be in use in R4.4). Yes if the things can not be resolved maybe the node is not so good. Thanks for the quick reply, Ridha
          Hide
          pandriani Pasquale Andriani added a comment -

          Hi Ridha,
          if you want to run your own WMarket instance and you want to access it from your browser, you have to use a public ip address to be assigned to your vm. Please you can refer to http://fiware-cloud-portal.readthedocs.io/en/latest/user_guide/#user-guide "Edit Security section" to know about how to assign a floating ip to your vm.

          If you are still unable to make it work, please let me know and I will ask to move your account to Spain2 node.

          Regards,
          P.

          Show
          pandriani Pasquale Andriani added a comment - Hi Ridha, if you want to run your own WMarket instance and you want to access it from your browser, you have to use a public ip address to be assigned to your vm. Please you can refer to http://fiware-cloud-portal.readthedocs.io/en/latest/user_guide/#user-guide "Edit Security section" to know about how to assign a floating ip to your vm. If you are still unable to make it work, please let me know and I will ask to move your account to Spain2 node. Regards, P.

            People

            • Assignee:
              pandriani Pasquale Andriani
              Reporter:
              fw.ext.user FW External User
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: