[Fiware-testbed] R: Overwriting GEs in the testbed

[Paolo Zampognaro]

Dear Thierry,

 

the installation cycle should be executed “entirely” for a specific GE
release. 

 

-If we change anything on the testbed after the 1st sanity check, do we have
to ask for another one, or under which conditions do we need another one?

--> If you have changed the GE after the sanity check execution then you
have to re-install it. Then you have to put the cockpit progress value to
40% (if no new requirements are need) from which you, and testbed team, can
continue with the next steps. The “state” value must be changed as well also
in the traker naturally.

 

-If we add new features we should have to provide a new version of all
guides and manuals and of course a new Unit Test Plan so a new sanity check

--> If you add new feature you are updating the GE (probably you are working
on anew GE version). Then you have to repeat the entire installation cycle.
Again, also in this case, if no new requirements are needed, you can start
from the 40% value in the cockpit wiki page and proceed with the next ones.
Again the “state” value must be changed as well also in the traker
naturally.

 

I hope this can provide some clarifications,

 

Cheers,

 

Paolo

 

 

 

 

 

Paolo Zampognaro

R & D Laboratory

paolo.zampognaro at eng.it

________________________________________

Engineering Ingegneria Informatica S.p.a.

via Emanuele Gianturco, 15 - 80142 Napoli – (IT)

tel.: (+39) 0816103524  

mobile.: (+39) 3451227587

www.eng.it 

 

-----Messaggio originale-----
Da: fiware-testbed-bounces at lists.fi-ware.eu
[mailto:fiware-testbed-bounces at lists.fi-ware.eu] Per conto di
thierry.nagellen at orange.com
Inviato: mercoledì 17 ottobre 2012 11.55
A: Miguel Carrillo; fiware-testbed at lists.fi-ware.eu; Juanjo Hierro
Oggetto: Re: [Fiware-testbed] Overwriting GEs in the testbed

 

Dear all,

 

I have a more general question regarding the process to update code, running
softwares but also documentations. We discuss this point during the IoT
weekly meeting this morning and it is not clear for me if we have clear
guidelines for that.

For example some open questions:

-If we change anything on the testbed after the 1st sanity check, do we have
to ask for another one, or under which conditions do we need another one?

-If we add new features we should have to provide a new version of all
guides and manuals and of course a new Unit Test Plan so a new sanity check

 

I know that we have many things to do but because of the changes on the
testbed and of course new releases we need some guidelines because the UC
projects (or external people) could find a Unit Test Plan which would not be
compliant with the running software version on the testbed.

 

Thanks for your comments

 

BR

Thierry

 

-----Message d'origine-----

De : fiware-testbed-bounces at lists.fi-ware.eu
[mailto:fiware-testbed-bounces at lists.fi-ware.eu] De la part de Miguel
Carrillo

Envoyé : mercredi 17 octobre 2012 10:06

À : fiware-testbed at lists.fi-ware.eu

Objet : [Fiware-testbed] Overwriting GEs in the testbed

 

Dear all,

 

Now that the 2nd delivery of the 1st Release is coming, we have to see what
to do with the GEs that are going to be resubmitted. As far as I can see,
all the GEs are new to the Testbed apart from those in IoT. We do not see
the need to keep to separate arrays of VM (one for R1.1 and another one for
R1.2) so we will just overwrite the old GEs with the new ones. This will be
announced to the UCs to avoid any possible misunderstandings.

 

Best regards

 

Miguel

 

--

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

      _/          _/_/                     Miguel Carrillo Pacheco

     _/   _/     _/  _/   Telefónica       Distrito Telefónica

    _/ _/_/_/   _/   _/   Investigación y  Edifico Oeste 1, Planta 9

   _/   _/     _/  _/     Desarrollo       Ronda de la Comunicación S/N

  _/          _/_/                         28050 Madrid (Spain)

                                           Tel:  (+34) 91 483 26 77

 

                                           e-mail: mcp at tid.es

 

Follow FI-WARE on the net

 

        Website:  http://www.fi-ware.eu

        Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242

        Twitter:  http://twitter.com/Fiware

        LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932

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

 

 

________________________________

 

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
nuestra política de envío y recepción de correo electrónico en el enlace
situado más abajo.

This message is intended exclusively for its addressee. We only send and
receive email on the basis of the terms set out at:

http://www.tid.es/ES/PAGINAS/disclaimer.aspx

_______________________________________________

Fiware-testbed mailing list

Fiware-testbed at lists.fi-ware.eu

http://lists.fi-ware.eu/listinfo/fiware-testbed

 

____________________________________________________________________________
_____________________________________________

 

Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu
ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,

France Telecom - Orange decline toute responsabilite si ce message a ete
altere, deforme ou falsifie. Merci.

 

This message and its attachments may contain confidential or privileged
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and
delete this message and its attachments.

As emails may be altered, France Telecom - Orange is not liable for messages
that have been modified, changed or falsified.

Thank you.

 

_______________________________________________

Fiware-testbed mailing list

Fiware-testbed at lists.fi-ware.eu

http://lists.fi-ware.eu/listinfo/fiware-testbed

 

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