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

FIWARE.Request.Lab.Berlin.UAT | 7 Regions tested: "create a VM" scenario

    Details

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

      Description

      Dear FIWARE teams,

      in terms of our survey for European Pioneers we have executed a User
      Acceptance Test nailed down to the most essential end-user scenario for 7
      regions listed below:

      „I want to be able to get a shell access with a public IP to an instance in
      a simple and straightforward way“.

      We are available that Terms of Usage are changing soon and ID verfication
      will be required to access public IPs, but this is not the issue here.

      We have tried today to create an instance in each region with the following
      results. (Account name for admins to look up the logs:
      christian.bonkowski@iais.fraunhofer.de
      <christian.bonkowski@iais.fraunhofer.de> , instance name: test-iais)
      Every time we expected that same steps are required to create a VM with a
      public IP and shell acccess. We assume also that not every potential
      customer with overall intermediate skill level has enough knowledge to
      manually configure a network.

      Typical error pattern in many cases was, there is a default network which
      cannot be used without an error, and custom network usage can also result in
      an error.

      Region

      Public IP allowed

      Manual

      Details

      UAT synopsis

      UAT: get IP+VM shell

      Lannion

      Yes

      Yes

      Manual 12 pages, not very straightforward.

      With manual acceptable but not competitive.

      PASS

      Spain

      Yes

      No

      No Networks/Router, auto-assign of int. IP

      Allocation of public IP easy.

      PASS

      Trento

      No

      No

      Much trial&error required

      Admin skills needed for network

      FAIL

      Waterford

      Yes

      No

      Manual network config

      Undefined error on IP assign.

      FAIL

      Berlin

      No

      No

      Manual network config

      No public IP available.

      FAIL

      Pragua

      Yes

      No

      As in Spain, no networks

      IP ok. Error on instance creation.

      FAIL

      Mexico

      Yes

      No

      Own network = no instance

      400 error on instance launch.

      FAIL

      We recommend a to implement a formal quality assurance process based on an
      audit so that all regions can implement same must-have common functionality
      at least for this one scenario, if possible. Think of McDonlads: you get
      identical Cola &BigMac offer everywhere but some regions have got their own
      food specials.

      Additionally, most successful regions like Spain might want to share their
      knowledge with other regions.

      Kind regards / viele Grüße & Servus

      Peter Muryshkin, M. Sc.

      Skype ID: peter_iais

      LinkedIn: http://de.linkedin.com/in/muryshkin

      ----------------------------------------------------------------------------
      ------

      NetMedia / B3-342

      Fraunhofer IAIS

      Schloss Birlinghoven 1

      53754 St. Augustin, Germany

      T: +49 2241 14 3413

      Email: <Peter.Muryshkin@iais.fraunhofer.de>
      Peter.Muryshkin@iais.fraunhofer.de

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

      [Created via e-mail received from: "Muryshkin, Peter" <Peter.Muryshkin@iais.fraunhofer.de>]

        Issue Links

          Activity

          Hide
          BerlinSupportTeam Berlin Node Helpdesk added a comment -

          Berlin node is passing internal sanity check.

          Show
          BerlinSupportTeam Berlin Node Helpdesk added a comment - Berlin node is passing internal sanity check.
          Hide
          peter Peter Muryshkin added a comment -

          Hi,

          please check here:

          http://fi-health.lab.fi-ware.eu/RegionSanityCheck/

          Today's status says, 2 tests are failing. Is this information now obsolete?

          kind regards
          Peter

          Show
          peter Peter Muryshkin added a comment - Hi, please check here: http://fi-health.lab.fi-ware.eu/RegionSanityCheck/ Today's status says, 2 tests are failing. Is this information now obsolete? kind regards Peter
          Hide
          BerlinSupportTeam Berlin Node Helpdesk added a comment -

          You're right.

          The first test is failing with:
          "NotFound: FloatingIpPoolNotFound: Floating ip pool not found."
          This i probably because we should change the network names. See
          https://jira.fi-ware.org/browse/NODEM-201

          The second test is failing, because the sanity check tries to use a tenant network that is already in use. Berlin node is not supporting overlapping CIDR for tenant networks.
          Invalid input for operation: Requested subnet with cidr: 10.250.251.0/24 for network: e53a89e8-88ba-4a18-b8b2-fb631c980608 overlaps with another subnet.'

          Therefore the sanity check needs to be modified for the Berlin node.
          Who is responsible for that? What is the process to contact the maintainer of the sanity check?

          Show
          BerlinSupportTeam Berlin Node Helpdesk added a comment - You're right. The first test is failing with: "NotFound: FloatingIpPoolNotFound: Floating ip pool not found." This i probably because we should change the network names. See https://jira.fi-ware.org/browse/NODEM-201 The second test is failing, because the sanity check tries to use a tenant network that is already in use. Berlin node is not supporting overlapping CIDR for tenant networks. Invalid input for operation: Requested subnet with cidr: 10.250.251.0/24 for network: e53a89e8-88ba-4a18-b8b2-fb631c980608 overlaps with another subnet.' Therefore the sanity check needs to be modified for the Berlin node. Who is responsible for that? What is the process to contact the maintainer of the sanity check?
          Hide
          peter Peter Muryshkin added a comment -

          Hi,

          I know so far only that there is a GitHub project containing the tests.
          In terms of homogenization, I would say that node-specific information should be implemented as test configuration which is launched in a test which is same for all.

          Anyway, check here:
          https://github.com/telefonicaid/fiware-health/tree/develop/fiware-region-sanity-tests

          Does this help or should I research for more information that might help you?

          kind regards
          Peter Muryshkin

          Show
          peter Peter Muryshkin added a comment - Hi, I know so far only that there is a GitHub project containing the tests. In terms of homogenization, I would say that node-specific information should be implemented as test configuration which is launched in a test which is same for all. Anyway, check here: https://github.com/telefonicaid/fiware-health/tree/develop/fiware-region-sanity-tests Does this help or should I research for more information that might help you? kind regards Peter Muryshkin

            People

            • Assignee:
              BerlinSupportTeam Berlin Node Helpdesk
              Reporter:
              peter Peter Muryshkin
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: