Hi Henk,
I tried to incorporate the provisioning of GE via own Hardware into account with my 4 delivery channels, outlined below.
Depending on whether you need to install the specific hardware on the testbed or locally on client side, you would either fill out B-"specific hardware"- or D-"specific hardware"-requirements.
As the tabular is very flexible as it is not strongly typed, any text pointing the testbed to special deployment scenarios can be inserted in these categories - other information then becomes optional (meaning: the OS of the terminal is not relevant if it is completed provided to the "client"- landscape or the "testbed"-landscape as an appliance). Perhaps we can make it more explicit which information to gather in these columns (I only could come up with an example of needed "usb-ports" - but if you know more possible examples, please just add them).
If you think we need a separate delivery channel, then don't hesitate to address and gather the needed information in a new section E). I'm not a domain expert in the hardware provision you are mentioning.
For the provisioning of GEs in the testbed itself I think it is not needed at first to explain which kind of demonstrations one would envision. For this information we need a separate UC or trial-specific questionnaire, which gathers the information you were outlining (when to test what to whom, what traffic to plan for, distribution channels, etc pp). I think we should really establish a separate second questionnaires, as this information can only be provided by the users of the testbed and not the GE providers themselves. This will not only help to plan the trials, it will as well help in setup the testbeds 1 2 3...
Just for reference, the complete list of requirement/specifications I yet came up with. As already outlined in my first posting: anybody is free to add or delete requirements, as I don't think I got all relevant data already in these lists.
Happy Easter to all of you
/Thorsten
1. "Testbed software specification" should incorporate:
A) Virtual appliance delivery in testbed
o Virtual machine container name
o Guest-OS
o Guest-Architecture (64bit/32bit)
o Number of CPUs
o RAM (Min and Max)
o Expected file-system sizes and storage requirements
B) Software delivery in testbed
o Depending software packages (Java /
o Depending software services (J2EE server / tomcat / webserver / ...)
o Depending hardware requirements (if any)
o Specific hardware dependencies (# USB ports, ...)
o Depending system requirements (architecture, OS, # of CPU, RAM, ...)
C) Software as a service delivery in testbed
o Hostname, port and protocol to reach the software provided as a service
o User/password (if any for integration testing)
D) "software installation delivery for local clients"
o Supported client operating system and archictecture (WIN/OSX/Linux 64/32bit)
o Software-Download-reference (Link to installation package)
o Installation Description (Link to configuration and installation guide)
o Estimated hardware requirements (PC/RAM/Install-size)
o Depending software packages (Java / ...))
o Specific hardware dependencies (# USB ports, special hardware...)
From: Heijnen Henk [mailto:henk.heijnen at technicolor.com]
Sent: Donnerstag, 5. April 2012 13:33
To: Sandfuchs, Thorsten; Moltchanov Boris; Marika Stålnacke; stefano de panfilis
Cc: fiware-testbed at lists.fi-ware.eu
Subject: RE: [Fiware-testbed] URGENT: GEI technical pages
Dear all,
I believe we must take into account products that are not virtualizable, that run on specific dedicated HW (for example, the Cloud Proxy GE which runs on dedicated HW) or that directly impact the network itself (for example, what ALU brings to T7.3) or that deals with terminals (IoT devices / gateway).
I don't think we can characterize these kind of devices with the list you provide.
Also, for this "non virtual-machines-hosted-stuff", we need to explain what will be shown (testbed 1, 2, 3) and what kind of integration will be done with the cloud-based applications (example: for TestBed1, the cloud proxy will not interface with the cloud but with a PC that simulates the cloud). We need to know how many instantiations of these bricks will be needed and where they will be tested and to whom (and when) they will be demonstrated ???
Regards
H
Henk HEIJNEN
Manager, Cooperative Projects
[cid:image001.jpg at 01CD1336.A4C04C40] [cid:image002.png at 01CD1336.A4C04C40]
Technology & Research
Funded & Cooperative Programs
1, Avenue de Belle Fontaine - CS 17616
35576 Cesson-Sévigné cedex - FRANCE
Tél: +33 2 99 27 33 08 - GSM: +33 6 72 39 26 24
From: fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten
Sent: jeudi 5 avril 2012 13:18
To: Moltchanov Boris; Marika Stålnacke; stefano de panfilis
Cc: fiware-testbed at lists.fi-ware.eu
Subject: Re: [Fiware-testbed] URGENT: GEI technical pages
Then it probably makes sense to add to my list of requested attributes another section:
We had already "Virtual appliance delivery", "software as a service delivery" and "software delivery" (for all of them I would add a 'to the testbed').
Then we could introduce a forth delivery channel:
D) "software installation delivery for local clients"
o Supported client operating system and archictecture (WIN/OSX/Linux 64/32bit)
o Software-Download-reference (Link to installation package)
o Installation Description (Link to configuration and installation guide)
o Estimated hardware requirements (PC/RAM/Install-size)
o Depending software packages (Java / ...))
o Specific hardware dependencies (# USB ports, special hardware...)
As this is as well needed for the Tools Chapter I think it will be highly beneficial to enable this delivery channel formally.
Best,
/Thorsten
From: fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] On Behalf Of Moltchanov Boris
Sent: Donnerstag, 5. April 2012 12:26
To: Marika Stålnacke; stefano de panfilis
Cc: fiware-testbed at lists.fi-ware.eu
Subject: Re: [Fiware-testbed] URGENT: GEI technical pages
Right, it should be also indicated in that testbed snapshot map including a sort of sw repository with its relative instructions for those components, which are used locally on their "customer" (UCP) side, additionally to the components hosted in the testbed, thus "remote" for UCP.
BR,
B
From: Marika Stålnacke [mailto:marika.stalnacke at ericsson.com]
Sent: Thursday, April 05, 2012 12:20 PM
To: Moltchanov Boris; stefano de panfilis
Cc: fiware-testbed at lists.fi-ware.eu
Subject: RE: [Fiware-testbed] URGENT: GEI technical pages
Hi
reservations for misunderstandings on my part: I miss somewhere to inform that a GE needs to be run "locally". As an example: the IoT Gateway. Each UseCase project needs a local machine that meets the listed requirements. They then need access to download gateway SW and any necessary installation instructions. Optionally of course the Testbed could offer to ship ready-installed machines, but I don't think we should do that.
Hope you understand what I mean.
Other than that I think this table is a good thing. I assume we will now expect GE providers to update the new table, and not the "old" fact finding page?
Happy Easter everyone!
/Marika
________________________________
From: fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] On Behalf Of Moltchanov Boris
Sent: den 5 april 2012 11:30
To: stefano de panfilis
Cc: fiware-testbed at lists.fi-ware.eu
Subject: Re: [Fiware-testbed] URGENT: GEI technical pages
Well, not exactly what I was suggestion, but in order to remediate and be ok then, I agree (a green card ;-) on my side) if the milestones will be the hyperlink to the short documents or web-pages with the very short and synthetic view on its respective topic, e.g. Testbed Basic Infrastructure Available -> IP addresses, port numbers, access credentials for creation and administration of the VMs, the infrastructural diagram showing the overall testbed with the nodes, VMs, connections and another service nodes. + Progress shall not be percentage - for my "technical" as stated in my initial proposal it is useless, and I wish to know the technical issues, state, aspects and not % number (not management) I wish prefer to know (by a link or a short description + link) what and where is installed is running and what its "under construction" status, - a sort of board diary where me or anyone else may see what is going on on the testbad and how to use/access it.
BR,
B
From: ste.depanfilis at gmail.com [mailto:ste.depanfilis at gmail.com] On Behalf Of stefano de panfilis
Sent: Thursday, April 05, 2012 11:14 AM
To: Moltchanov Boris
Cc: Sandfuchs, Thorsten; fiware-testbed at lists.fi-ware.eu
Subject: Re: [Fiware-testbed] URGENT: GEI technical pages
oooops!!!
here it is
https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit
ciao,
stefano
2012/4/5 Moltchanov Boris <boris.moltchanov at telecomitalia.it<mailto:boris.moltchanov at telecomitalia.it>>
Dear Stefano,
may you please provide the correct link to the cockpit?
Thanks.
BR,
B
From: fiware-testbed-bounces at lists.fi-ware.eu<mailto:fiware-testbed-bounces at lists.fi-ware.eu> [mailto:fiware-testbed-bounces at lists.fi-ware.eu<mailto:fiware-testbed-bounces at lists.fi-ware.eu>] On Behalf Of stefano de panfilis
Sent: Wednesday, April 04, 2012 10:10 PM
To: Sandfuchs, Thorsten; fiware-testbed at lists.fi-ware.eu<mailto:fiware-testbed at lists.fi-ware.eu>
Subject: [Fiware-testbed] URGENT: GEI technical pages
dear thorsten and all,
combing the suggestions from boris, thorsten and the table paolo built for d10.1.a i now we do have for each gei a specific "testbed technical" page.
you can access it from the v1 cockpit at "fiware-testbed at lists.fi-ware.eu<mailto:fiware-testbed at lists.fi-ware.eu>" <fiware-testbed at lists.fi-ware.eu<mailto:fiware-testbed at lists.fi-ware.eu>>
actually only three pages have been created (you can easily find them ... ;-) ) to see how the result looks like. indeed, i think it is a good work.
anyway, before to go ahead i need the green card (or additional comments and suggestions) from all of you, but in particular from boris, henke, paolo and thorsten.
I have also updated the "facts finding" page with the answers (pascal, pier, boris) to my email of this morning.
my best wishes for an happy easter to you and your beloved!!!
ciao,
stefano
2012/4/2 Sandfuchs, Thorsten <thorsten.sandfuchs at sap.com<mailto:thorsten.sandfuchs at sap.com>>
Hi stefano,
I send you a link to an example specification which does not include the software requirements we gathered in the fact-finding. As I said, I don't know who did define the general set of headlines in these articles, but we should drive for a "testbed software specification" subheading, where we incorporate the fact-finding information on software and network requirements.
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Apps.CompositionEditor
General list of open specifications (for app & services):
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Architecture_of_Applications_and_Services_Ecosystem_and_Delivery_Framework
(part of the architecture: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture)
1. Network-specification should incorporate:
- List of open network ports and protocols (80/HTTP, 443/HTTPS, 22/SSH, 21/FTP, ...)
- Expected depending available internet services (e.g. DNS, Mail, NTP, ...)
- Specific firewall requirements (explicitly open or closed ports INPUT/OUTPUT)
- Specific routing requirements (default routes and specific routes to other GEs)
2. "Testbed software specification" should incorporate:
A) Virtual appliance delivery
o Virtual machine container name
o Guest-OS
o Guest-Architecture (64bit/32bit)
o Number of CPUs
o RAM (Min and Max)
o Expected file-system sizes and storage requirements
B) Software delivery
o Depending software packages (Java /
o Depending software services (J2EE server / tomcat / webserver / ...)
o Depending hardware requirements (if any)
o Specific hardware dependencies (# USB ports, ...)
o Depending system requirements (architecture, OS, # of CPU, RAM, ...)
C) Software as a service delivery
o Hostname, port and protocol to reach the software provided as a service
o User/password (if any for integration testing)
I compiled these two lists just out of my head - perhaps we should reiterate the list in the team, as it is highly likely that I missed something.
I just got a note that Juanjo is preparing new templates for the open specifications - perhaps the right place for the gathering of the above information is: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.1 Or should I incorporate this list in https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/FI-WARE_Integration_Plan#The_Integration_Testing_Plan ?
Stefano: would please decide which option to take and respectively address Juanjo with the request?
Thanks and best regards,
/Thorsten
--
Thorsten Sandfuchs
SAP AG
SAP Research Center Karlsruhe
Vincenz-Priessnitz-Strasse 1
D - 76131 Karlsruhe
www.sap.com<http://www.sap.com>
Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx
Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.
This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
Please consider the environment before printing this mail!
--
Stefano De Panfilis
Chief Innovation Officer
Engineering Ingegneria Informatica S.p.A.
via Riccardo Morandi 32
00148 Roma
Italy
tel (direct): +39-068307-4295<tel:%2B39-068307-4295>
tel (secr.): +39-068307-4513<tel:%2B39-068307-4513>
fax: +39-068307-4200<tel:%2B39-068307-4200>
cell: +39-335-7542-567<tel:%2B39-335-7542-567>
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.
This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
Rispetta l'ambiente. Non stampare questa mail se non è necessario.
--
Stefano De Panfilis
Chief Innovation Officer
Engineering Ingegneria Informatica S.p.A.
via Riccardo Morandi 32
00148 Roma
Italy
tel (direct): +39-068307-4295
tel (secr.): +39-068307-4513
fax: +39-068307-4200
cell: +39-335-7542-567
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-testbed/attachments/20120405/dfe17693/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 16662 bytes
Desc: image001.jpg
URL: <https://lists.fiware.org/private/old-fiware-testbed/attachments/20120405/dfe17693/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 2226 bytes
Desc: image002.png
URL: <https://lists.fiware.org/private/old-fiware-testbed/attachments/20120405/dfe17693/attachment.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy