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

FIWARE.Request.General. Fiware compliancy requirements

        Details

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

          Description

          Hi,

          We are developing a smart city platform on Microsoft Azure, and would like to make this fiware compliant.

          However, the fiware website states that OpenStack compatibility is a requirement for fiware compliance?

          Is that a hard requirement? As long as we implement the contextbroker APIs in the platform, does it matter what platform we use?

          Kind regards,

          Mathias Colpaert
          http://www.sirus.be/images/signatures/sirus-sig-logo.png
          Mathias Colpaert
          +32 496 06 23 88<tel:+32%20496%2006%2023%2088> | http://www.sirus.be

          SIRUS
          Delivering Smart Innovation | IoT and Cloud Solutions
          Verlorenbroodstraat 122 bus 8, BE-9820 Merelbeke<https://goo.gl/maps/SMtDTHKW6bk>

          Dit bericht (inclusief de bijlagen) kan vertrouwelijk zijn. Als u dit bericht ten onrechte hebt ontvangen, wordt u verzocht de afzender te informeren en het bericht te wissen. Het is niet toegestaan om dit bericht, geheel of gedeeltelijk, zonder toestemming te gebruiken of te verspreiden. SIRUS sluit elke aansprakelijkheid uit wanneer informatie in deze e-mail niet correct, onvolledig of het niet tijdig overkomt, evenals indien er schade ontstaat ten gevolge van deze e-mail. SIRUS garandeert niet dat het bericht vrij kan zijn van onderschepping of manipulatie daarvan door derden of computerprogramma's die worden gebruikt voor elektronische berichten en het overbrengen van virussen.

          __________________________________________________________________________________________

          You can get more information about our cookies and privacy policies on the following links:

          Fiware-general-help mailing list
          Fiware-general-help@lists.fiware.org
          https://lists.fiware.org/listinfo/fiware-general-help

          [Created via e-mail received from: Mathias Colpaert <mathias.colpaert@sirus.be>]

            Activity

            Hide
            Permalink
            fla Fernando Lopez added a comment -

            The issue has been emailed:

            • Time sent: 20/Dec/18 9:50 AM
            • To: mathias.colpaert@sirus.be
            • with subject: *(HELP-14547) [Fiware-general-help] Fiware compliancy requirements *

            Dear user,

            First of all, sorry for the delay, we could not see this issue before today.

            Regarding your question, it is not mandatory that you use OpenStack to get a solution compliant with FIWARE. OpenStack is the environment that we use for experimentation with the FIWARE Technology. You can use whatever technology that you want because our deployments are based on docker technology.

            Show
            fla Fernando Lopez added a comment - The issue has been emailed: Time sent: 20/Dec/18 9:50 AM To: mathias.colpaert@sirus.be with subject: *( HELP-14547 ) [Fiware-general-help] Fiware compliancy requirements * Dear user, First of all, sorry for the delay, we could not see this issue before today. Regarding your question, it is not mandatory that you use OpenStack to get a solution compliant with FIWARE. OpenStack is the environment that we use for experimentation with the FIWARE Technology. You can use whatever technology that you want because our deployments are based on docker technology.

              People

              • Assignee:
                backlogmanager Backlog Manager
                Reporter:
                fw.ext.user FW External User
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: