[Fiware-wpl] Public Global instances?

[Heller, Markus]

Hi all, Henar, Stefano, Juanjo,

For clarification, during an internal discussion a question surfaced where I would like to ask you all: A "FI-LAB-run "_not_ provided by the testbed as a service "Global instance with public access - is this foreseen/possible or not?

Example: For WP3 Apps Chapter: For our 3 SAP GE's (Marketplace, Repository, Registry) we want to achieve (after M36) this final situation:


1)      per GE (MP, Repos, Reg) each one is run as "global instance" and each is (already) installed on FI-WARE testbed): only consortium-wide access allowed under CA - no public access allowed

2)      per GE (MP, Repos, Reg) only images (configured images) are put into FI-Lab - public access after successful login - User has to manually creates his own instance of such an image (image provided by SAP)

3)      We do _not_ want to have global instances run on FI-LAB Cloud of our GEs is run on FI-LAB with public access.

To implement this plan, for each GE (MP, Repos, Reg) we need to enter into the "cockpit" https://forge.fi-ware.org/plugins/mediawiki/wiki/testbed/index.php/Testbed_V3_Implementation_Cockpit two entries: one in "global instance (testbed)" (filled in by us already) and one in "configured image" (missing by us as of today).


So comes my question as above:  A "FI-Lab-run (not through testbed) Global instance with public access - is this foreseen or not?

Can a partner have at the same time "two" global instances run for one of his GE's: (1) one global instance (run on Testbed) and (2) another one global instance (run on FI-LAB cloud) - yes or no?


·         If yes: how would a team write this situation (2 Global instances) into the cockpit implementation table - since the existing "GE Global instance" column seems only reserved for test-bed realized global instances...as I see here (yellow marking)...


·         If no: I guess that the different access right models (testbed=consortium only and fi-lab=public) would bring with it that such a public access Global Instance with public access and run in FI-LAB can make sense for some partners (IMHO which is _not_ identical to the consortium-restricted Testbed). Not relevant for us from SAP, but maybe for others.

Note: I guess this discussion topic is basically a matter of branding "FI-Lab" etc. The case that a Testbed-installed global instance is alive - do we in FI-WARE lingo say then that it is part of "FI-LAB" as of today....This would be confusing since (at least I) always connect to "FI-LAB" a certain access model (public, not only consortium-restricted) but how is this seen by you all?

What is your clarification/opinion? Can someone please help me and clarify the current picture as of today?

Best
Markus








Generic Enabler Instances Cockpit
[edit<https://forge.fi-ware.org/plugins/mediawiki/wiki/testbed/index.php?title=Testbed_V3_Implementation_Cockpit&action=edit&section=4>] How to read the cockpit

There are three pairs of progress columns: one for the Global Instance status, the second for the Receipes and the latter for the Configured Image status. The progress values are as follows:

  *   A GEI global instance means provided by the Testbed as a service. It is going to be a GE instance which is going to be shared by all the UCs, and whose service endpoint is going to appear in the catalogue. For Global instances, we have the following progress status:
     *   40%: VM deploy: You should deploy a VM in the testbed to install your GE software. For installing a VM in the testbed, please have a look at the wiki [2].
     *   60%: GE installed. You have installed the GE software in the VM
     *   65%: The Chapter Leader guarantees the correctness of the GEI
     *   70%: Sanity Checks passed. The Testbed Team has passed the sanity checks of your GEI
     *   75%: The GE is correct in the Catalogue, but no Sanity Check performed (this status can only follow the 65%)
     *   80%: The GE is correct in the Catalogue
     *   100%: Integration test (if defined) succesfully passed.

  *   A GE Dedicated Instance can be made available either through a receipe or configured image. It is an instance which can be installed in the UC environment by UC project teams. To allow this, you should create an image of your dedicated instance, using the Cloud capabilities or creating recipes. A webminar on such process is available at [....]. For these instances, the progress values are:
     *   20%: image generated: You have created the GE image by using the Cloud capabilities.
     *   30%: image ok: Testbed people check that this image is ok, deploy a VM from this image and passing sanity checks
     *   40%: recipes generated: You have to create the specific recipe
     *   50%: recipes ok: Testbed people check that the recipes are ok.
     *   60%: Information in the catalogue. The information is stored in the catalogue.

Once installed, the GEI owner puts 60%. ONLY THE TESTBED TEAM CAN ASSIGNS VALUES ABOVE 60%

  *   The "Actual Date" has the following meaning (updated only by the testbed team):
     *   Date at which the "Global Instance" progress up to 100% (real availability of the Global Instance)
     *   Date at which the recipes for creating "Dedicated Instances" progress up to 100% (real availability of the recipes)
     *   Date at which images containing a "Dedicated Instances" progress up to 100% (real availability of the images)
  *   The note should capture (when applicable):
     *   the service end point of the Global Instance
     *   the URL from which to download the recipes
     *   the name of the configured image in the Cloud image catalogue


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20140324/ef4d0cfd/attachment.html>