[Fiware-testbed] composition editor link to ADD

[Sandfuchs, Thorsten]

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!





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-testbed/attachments/20120402/da256c2e/attachment.html>