[Fiware-friendly-testing-coordination] Start of activities linked to friendly testing of FIWARE

Juanjo Hierro juanjose.hierro at telefonica.com
Fri Oct 10 04:14:05 CEST 2014

Previous message: [Fiware-friendly-testing-coordination] Start of activities linked to friendly testing of FIWARE by FEMTO-ST
Next message: [Fiware-friendly-testing-coordination] Start of activities linked to friendly testing of FIWARE
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Dear Paulo,

I have just added the people of your team to the fiware-friendly-testing mailing list.

PLEASE stick to the concrete friendly testing plan of GEris and functionality of the FIWARE Lab that was assigned to your team. That was specified in the first message that I sent to you (subject "Start of activities linked to friendly testing of FIWARE")

I frankly got scared when I read your statement "Meanwhile we started browsing the public websites and documentation, performing registration and downloading and performing ad-hoc experiments with a few enablers. Similar work has been started for the Labs, with some experiments performed by Patricio".

If we do not coordinate the actions and stick to the distribution of work, we will end in chaos and replicating efforts among the different teams. Bear in mind that there are other teams different than yours also involved in this Task Force. We have carefully designed a distribution of the testing activities to be performed.

Best regards,

-- Juanjo

-------------
Telefonica - Product Development and Innovation (PDI)
website: www.tid.es<http://www.tid.es>
email: juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Coordinator
and Chief Architect

You can follow FI-WARE at:
website: http://www.fi-ware.org
facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
twitter: http://twitter.com/FIware
linkedIn: http://www.linkedin.com/groups/FIWARE-4239932

On 10/10/14 03:27, Paulo Simoes wrote:

Dear Fernando, all,

Attached please find the names and contacts of the complete team.

As for the PhC, I propose we try to reserve a weekly slot for regular PhC.
Please provide 2 or 3 alternatives, so we can match them with our own availabilities.

Meanwhile we started browsing the public websites and documentation, performing registration and downloading and performing ad-hoc experiments with a few enablers. Similar work has been started for the Labs, with some experiments performed by Patricio.

We plan to create a journal to register all our findings and recommendations. Probably JIRA will be the right tool for this (with adequate configurations), and the question would be:

a) to create this journal in the FIWARE JIRA, with support from the persons in charge of FIWARE's JIRA.
b) to create a separate JIRA deployment at OneSource, also made accessible to selected FIWARE people.

Meanwhile we drafted a first proposal for our workplan for Phase 1 (October 7 to November 14):

Week 1 (starting 7/October):
- registration, study of available documentation, downloads, ad-hoc local deployments, ad-hoc creation of virtual machines at the lab.

Week 2-Week 3 (Phase 1, Step 1):
- (week 2:) definition of KPIs, draft user stories, identification of all the GEris to cover in Phase 1, definition of structured outputs of our testing, definition of the roadmap for each of the 4 testers.
- (week 2-3) testing of the enablers in local computers.
- (week 2-3) testing of basic Lab setups

Week 4-Week 5 (Phase 1, Step 2):
- (week 4-5) testing of the enablers in Lab deployments.
- (week 4-5) testing of advanced Lab setups
- (end of week 5): production of an internal and interim deliverable reporting the work done so far (in addition to the journals, which are important to provide early feedback to the FIWARE team).

Phase 2 (14/November to 31/December):
- Development and documentation of open source code for example applications.
(to be defined during the first phase)
- Helping to improve existing documentation and, overall, tutorials (written or video tutorials)

Regards,

-- PS

On 08/10/14 10:24, FERNANDO LOPEZ AGUILAR wrote:
Dear Simoes,

Like Juanjo mentioned in the previous email, I was coordinating the activities regarding the Cloud friendly testing. I suppose, that the person who will be working on it, should be Patricio, correct me if I am wrong. When the complete team is defined we will define the way of working and the different tasks to be developed in a PhC.

Best regards,
Fernando.-

De: Paulo Simoes <psimoes at onesource.pt<mailto:psimoes at onesource.pt>>
Organización: OneSource Lda.
Fecha: Tuesday 7 October 2014 07:57
Para: JUAN JOSE HIERRO SUREDA <juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>>, "Thomas.Bohnert at zhaw.ch<mailto:Thomas.Bohnert at zhaw.ch>" <Thomas.Bohnert at zhaw.ch<mailto:Thomas.Bohnert at zhaw.ch>>, "luis.cordeiro at onesource.pt<mailto:luis.cordeiro at onesource.pt>" <luis.cordeiro at onesource.pt<mailto:luis.cordeiro at onesource.pt>>
CC: fla <fernando.lopezaguilar at telefonica.com<mailto:fernando.lopezaguilar at telefonica.com>>, Leandro Guillen <leandro.guillen at imdea.org<mailto:leandro.guillen at imdea.org>>, MIGUEL CARRILLO PACHECO <miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>>, MANUEL ESCRICHE VICENTE <manuel.escrichevicente at telefonica.com<mailto:manuel.escrichevicente at telefonica.com>>
Asunto: Re: Start of activities linked to friendly testing of FIWARE

Dear Juanjo,

I confirm your proposal is fine with us.

We will start this process immediately. Today we will organize the work internally and by the end of the day we'll provide more feedback on the team organization and on how we'll conduct our work and reporting.

Regards,

-- Paulo Simões

On 07/10/14 03:19, Juanjo Hierro wrote:
Dear Paulo,

Let's start to work involving the resources you have listed plus one additional. We would like to involve 4 engineers. We understand that project management activities are not strictly necessary. There will be people from FIWARE assigned to coordination. Nevertheless, if you want to charge a bit % on those type of activities is fine. Since it is not true that we will spend exactly 4*3 = 12 PMs starting now until end of the year, I understand that we may go for allocating that effort of 9 PMs and assume that the % of coordination is part of that. Consequently, we would have an overall funding assigned of 6.000 € * 12 PMs = 72.000 €. Note that this would require that you add a fourth developer in a matter of few days, preferably this week.

Is it fine with you? If so, the following are the instructions to follow to start the activity. Please confirm urgently that this is ok.

This Task Force is targeted to identify the issues that any developer may find when they try to approach FIWARE for the first time, even if (s)he hasn't had the opportunity to attend any of our Bootcamps or Technical Workshops. The difference here is that you are a friendly tester, that is, you will report and properly document the issues that you find (while other developers may decide to give up when they find the first issue). This will allow us to understand what has to be fixed.

The Task Force will be organized in two phases:

* In a first phase of the Task Force, which we expect (hopefully :-) that may last one or one and a half month, you will focus on:
* Regarding the Cloud, Store, Mashup-Wirecloud, Data and Account Management portals available on the FIWARE Lab (http://lab.fiware.org)
* Make sure that everything works fine and it is intuitive enough
* Make sure that there is enough helpful and accurate documentation as well as video tutorials
* Regarding individual FIWARE components (referred as FIWARE GEris which is the acronym of FIWARE Generic Enabler reference implementation) published in the FIWARE Catalogue (http://catalogue.fiware.org):
* In a first step, make sure that their software can be downloaded, deployed, configured and used locally by a regular developer, using info available on the FIWARE Catalogue.
* In a second step, make sure that they can be deployed and configured as dedicated instances on the FIWARE Lab (using dedicated VM images, recipes and blueprints) and both dedicated and global instances running on the FIWARE Lab can be used by a regular developer, using info available on the FIWARE Catalogue and the resources available on the FIWARE Lab

* In a second phase (since end of first phase until the end of the year), you will focus on:
* Develop and document the open source code for example applications you will be asked to develop (to be defined during the first phase)
* Help to improve existing documentation and, overall, tutorials (written or video tutorials)

I won't give you more details on how things can be done because part of your job is to try what third developers will try with not much more info than the above :-)

Whenever you identify a problem to be fixed or a suggestion/request for an enhancement, please drop an email to the following help-desk addresses:

* fiware-lab-help at lists.fi-ware.org<mailto:fiware-lab-help at lists.fi-ware.org>: to be used when the problem/enhancement to be reported has to do with the FIWARE Lab environment
* problem/enhancements on functionalities offered through any of the FIWARE Lab portals: Cloud, Store, Mashup, Account, Data, Help&Info
* problem/enhancements trying to deploy (instantiate) and configure FIWARE GEri on the FIWARE Lab using Cloud deployment tools (creation of VM images with preinstalled GEris, usage of recipes, usage of blueprint templates)
* problem/enhancements trying to get access to a FIWARE GEri instance available on the FIWARE Lab: either a private dedicated instance previously deployed by you or a global instance available for all developers
* fiware-tech-help at lists.fi-ware.org<mailto:fiware-tech-help at lists.fi-ware.org>: to be used when the problem/enhancement to be reported has to do with individual FIWARE components
* downloading, installing and configuring a FIWARE GEri on your local premises, using available documentation
* downloading, installing and configuring a FIWARE GEri on a VM previously deployed on the FIWARE Lab
* getting access and programming with the APIs provided by FIWARE GEri instances you have deployed (you are asked to try the tutorials provided and then event try something on your own)

Nevertheless, don't get too much worried about what mailing list you should use (third developers may also not perform the best choice ;-) We will deal with that and make sure things are handled properly.

For your info, any time you send a message to any of the above channels, a ticket will be created in a JIRA HelpDesk ticketing system. Then the 1st and 2nd level support teams will analyze it, in the most trivial cases respond directly your request for help and if they don't know how to do it, they will pass the ticket to someone from the FIWARE development teams who will take care of it.

You will see that the HelpDesk may answer you that you have asked to solve a problem they believe should be answered on StackOverflow for the sake of other programmers. If so, please formulate your question there. We have decided to use StackOverflow as our forum for developers. There are a number of tags, the more general "fiware" tag but also tags associated to the most popular FIWARE GEris like "fiware-orion", "fiware-wirecloud", you can use to ask question about FIWARE on StackOverflow. Of course, after some time, once you get more experienced using FIWARE, you may decide to go for asking the question directly on StackOverflow.

Fernando López <fernando.lopezaguilar at telefonica.com><mailto:fernando.lopezaguilar at telefonica.com> will coordinate all the tests dealing with the Cloud, Store, Mashup-Wirecloud, Data and Account Management portals available on the FIWARE Lab.

Leandro Guillén <leandro.guillen at imdea.org><mailto:leandro.guillen at imdea.org> will coordinate all the tests dealing with individual FIWARE components published on the FIWARE Catalogue.

You may ask any question you may have by sending a message to fiware-friendly-testing-coordination at lists.fi-ware.org<mailto:fiware-friendly-testing-coordination at lists.fi-ware.org>. If you don't get any answer, please contact Fernando and Leandro directly (they are in the mailing list though).

Regarding the tests to be done by Bitergia, we would like that your three developers focus on the following tasks:

* Patricio Batista: testing of FIWARE Cloud functionalities on the FIWARE Lab
* João Gonçalves: testing GEris of the Advanced Web-based UI chapter of FIWARE published on the FIWARE Catalogue (remember the two consecutive steps to be performed when carrying out testing of individual FIWARE components)
* Hugo Fonseca: testing GEris of the Kurento FIWARE GEri published on the FIWARE Catalogue (remember the two consecutive steps to be performed when carrying out testing of individual FIWARE components)
* OneSource developer 4: testing of the Complex Event Processing - ProTON GEris published on the FIWARE Catalogue (remember the two consecutive steps to be performed when carrying out testing of individual FIWARE components)

Some last remarks:

* We know that you are a experienced developer. Therefore, you may infer how some little issue you find can be overcome. However, please report that issue so that we can fix it. Take into account that some third developers may not be so much experienced, therefore they may not be able to overcome the same issue. Of course, don't wait for the issue to get solved in order to continue with testing.
* Issue your reports in english and try to provide as much details as possible to make our task easier and solve issues as fast as possible.
* Any typo or improvement on language of available documentation is welcome.
* Don't focus just on issues/problems. Any suggestion for enhancement is welcome.
* If you are blocked at any point and you don't know how to continue, please let us know. Send an email to fiware-friendly-testing-coordination at lists.fi-ware.org<mailto:fiware-friendly-testing-coordination at lists.fi-ware.org>

Let's rock !!

Best regards,

-- Juanjo Hierro

FI-WARE (European Future Internet Core Platform) Coordinator
and Chief Architect

On 06/10/14 00:23, Paulo Simoes wrote:
On 05/10/14 21:23, Thomas Michael Bohnert wrote:
Paulo,

Can you add some info about the staff profiles that you plan to assign to this important task? (Software developers and System Engineers/Operators would be needed - ideally experiences ones).

Thanks, Thomas

Dear Thomas, all,
(please excuse the long reply)

The final selection of staff to involve still depends on assessing all the required skills and technologies that are required to use the FI-WARE components. Nevertheless, next I provide the profiles of three people that immediately came to my mind and may be assigned to the project.

Hugo Fonseca. Before joining OneSource he worked for several years in the development of RCS and WebRTC platforms, including software design and development. Before that he was involved in quality assurance and software testing (mostly for unified communications suites and mobile banking applications). At OneSource Hugo is mostly involved with one of our clients, focusing on improving the security, QoS/QoE and functionalities of the white-label communications suites this client provides to several telcos worldwide (cloud-based managed PBX solutions, contact centers and rich communication suites for enterprise markets).

João Gonçalves is mostly a software engineer. One of the most recent applications he has developed is an advanced live video-to-video (v2v) communications platform, integrated with operator’s resource management frameworks, that in the context of the Livecity PSP Project is being used in several applications with real users: telemedicine, support of first responder teams, education and remotely provided public services. In addition to the core and the plug-in interfaces of the v2v platform, João also designed and assembled the wearable v2v device that is being used by first responder teams in Ireland and Germany. This v2v platform was awarded as the Best Demonstration at FIA-2014 (Athens).

Patricio Batista started his career as a network and systems administrator. Later on he evolved to systems design and integration. He is quite experienced on deploying, integrating, configuring and managing distributed systems, as well as on virtualized and cloud-based infrastructures. It is difficult to mention all the projects he has been involved in, but he has, for instance, designed a platform that one of our clients uses to receive and analyze in real-time (for risk and fraud prevention purposes) tenths of thousands of credit card transactions per second.

In addition to people with these or similar profiles, we also intend to involve a project manager with experience on FP7 Projects, such as Bruno Sousa or Luís Cordeiro.

Bruno Sousa owns a PhD in Information Science and Technology, and he authored tenths of research papers in journals, book chapters and conference proceedings. He has participated in European R&D projects such as FP6 EuQos, FP6 WEIRD, FP7 CityFlow, FP7 MCN and FP7 SALUS. Before returning to the University to get his PhD Bruno has led for several years the development and integration of backoffice applications for “La Redoute/Redcats”, a large European home-shopping retailer.

Luis Cordeiro has been actively involved in European research projects such as FP6 EUQOS, FP6 WEIRD, FP7 LiveCity, FP7 CityFlow, FP7 SALUS and FP7 Mobile Cloud Networks. He has several publications in journals, book chapters, conferences and Internet Drafts in the areas of Signaling, end-to-end QoS and Network Management. In addition to those research activities, he also led tenths of application development projects.

Regards,

-- Paulo

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição

________________________________

Previous message: [Fiware-friendly-testing-coordination] Start of activities linked to friendly testing of FIWARE by FEMTO-ST
Next message: [Fiware-friendly-testing-coordination] Start of activities linked to friendly testing of FIWARE
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Fiware-friendly-testing-coordination mailing list

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