From fermin at tid.es Thu May 9 19:36:35 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Thu, 09 May 2013 19:36:35 +0200 Subject: [Fiware-demo] Links to example theme and WP contacts Message-ID: <518BDEA3.4030103@tid.es> Hi, These are the links of the example Theme/Epic/Feature description for the Live Demo (based in R1) used during Monday WPL/WPA meeting: FIWARE.Theme.Cross.LiveDemo.MashableApplication * FIWARE.EPIC.Cross.LiveDemo.MashableApplication.Registration * FIWARE.Feature.Cross.LiveDemo.MashableApplication.Registration.RegisterWidget * FIWARE.Epic.Cross.LiveDemo.MashableApplication.Design * FIWARE.Feature.Cross.LiveDemo.MashableApplication.DesignMashup.WorkspaceSelection * FIWARE.Feature.Cross.LiveDemo.MashableApplication.DesignMashup.ResourceCatalogSearch * FIWARE.Feature.Cross.LiveDemo.MashableApplication.DesignMashup.CheckDetailedInfo Note that the description of these issues in the wiki is used to automatically generate the Product Vision Document, as can be seen in the following draft https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Product_Vision_Draft. The home page to the Live Demo information is the following: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Live_Demo_Evolution Thus, if you (as WPL, WPA or GEi owner) think that there is functionality in your WP or GEi that should be included in the Live Demo, please complete a Theme (which its corresponding Epics and Features) in this way, so we can take it into consideration in the backlog. Note that recently FI-WARE methodology has been modified to replace Themes with Epics (and allow Epics as "childs" of Epics). Thus, instead of structuring in Themes/Epic/Feature you can structure on Epic/Epic/Feature, i.e. first level epics and second level epics. If you didn't assisted to last Monday audio and/or have any doubt, don't hesitate to contact me A team composed by UPM and TID have already identified some Themes for the evolution of the Live Demo App based on feedback from Chief Architect and we are currently documenting it this way. We would like to foster the Live Demo App in each one of the chapters, so we would like to define contact point for this in each one of them. In this sense: * WP3: Javier Soriano (UPM) will be the contact point for Live Demo App in WP3 * WP4: Fernando Lopez (TID) (in coordination with Alex) will be the contact point for Live Demo App in WP4 * WP5: Unfortunately neither Carlos nor Thierry where in the audio on Monday. I will talk about this with Carlos when he return from FIA. * WP6: Sergio Garc?a (TID) will be the contact point for Live Demo App in WP6 * WP7: Live Demo functionality has not been identified so far in this chapter. Of course, this is open to Themes/Epic/Features describing functionality involving GEi in this chapter. * WP8: it would be interesting to show the integration of Access Control GE and IDM GE. Who should be the proper contact point? Any feedback or comment is welcome. Thanks! Best regards, ------- Ferm?n PD. A summary os this email is also included in minutes in Monday minutes in https://docs.google.com/document/d/1K-ZlPZHFd-ErVEGHjUhIUO3YdX-ZhXYOHgrmC1C2YLs/edit?pli=1# ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.dallecarbonare at eng.it Fri May 17 17:16:02 2013 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Fri, 17 May 2013 17:16:02 +0200 Subject: [Fiware-demo] Java application/component Message-ID: <519649B2.7000507@eng.it> Dear Ferm?n, I kindly ask you if there is a Java application/component developed in Java that takes part of the Live Demo. If yes, can you provide me the contact person for that? BR Davide From fermin at tid.es Fri May 17 18:06:41 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Fri, 17 May 2013 18:06:41 +0200 Subject: [Fiware-demo] Java application/component In-Reply-To: <519649B2.7000507@eng.it> References: <519649B2.7000507@eng.it> Message-ID: <51965591.7060908@tid.es> Dear Davide, I understand you refer to the "user application" for the Live Demo, not to the GEis (WireCloud, ContextBroker, CEP, Backend Device Management, Location, etc.) As far as I remember, Live Demo App release 1 (i.e. the one used for November 2012 review) has part of its backend developed in Java. However, the current version of Live Demo app backend is based on Node.js. @UPM: could you confirm this, please? Thanks! Best regards, ------ Ferm?n El 17/05/2013 17:16, Davide Dalle Carbonare escribi?: > Dear Ferm?n, > I kindly ask you if there is a Java application/component > developed in Java > that takes part of the Live Demo. > > If yes, can you provide me the contact person for that? > > BR > Davide ________________________________ 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 From fermin at tid.es Mon May 20 19:56:06 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Mon, 20 May 2013 19:56:06 +0200 Subject: [Fiware-demo] Live Demo current (May 20th) status Message-ID: <519A63B6.7010001@tid.es> Hi, Today WPL/WPA meeting minutes (https://docs.google.com/document/d/1HtuHO5BVH9kfYSWV2zA196u-DGqFRiCGo-OoT9K7wUw/edit) includes an snapshoot of the status of Live Demo activities, that I think is interesting to share in the mailing list for your convenience (and for those of you that don't attend to WPL/WPA meetings): Update on May, 20: Current status: * Epic/Features documentation for R1 and R2. UPM is working on the "core" wiki structure. Ongoing. * Widgets adaptation/implementation. UPM is working on it. You can see a snapshot following this link. * Store and marketplace adaptation and integration. UPM is working on it .Ongoing. * History element implementation. Currently, UPM has developed a first implementation using Node.js that makes queries to the Pub/Sub Context Broker and saves the power status history of lamps into a MySQL database. The module also has a Rest API that can be use to query the power status history of a lamp. * Object Storage integration (based in a similar case from ENVIROFI demo). UPM is working on it. Ongoing. * Backend Device Management (IDAS) integration.(including actual sensor data from OutSmart). IDAS is ready to be integrated, pending to define the details in the testbed. * CEP integration. ContextBroker->CEP integration is clear in terms of format/messages. CEP->ContextBroker is still under definition. Working on it in a team with TID, IBM and UPM. * PaaS Manager integration. Chef receipts for deploying ContextBroker GE are ongoing. Chef receipt for deployment user application are ongoing. We plan to have progress on this by the end of the week. * API Access Control: pending of having all the components integrated. * Usage of the Location Platform from WP6. Plan to integrate a simulation of a route and update the position of various mobile users. Need to test coordinates compatibility. It requires to implement a light NGSI-Location API adhoc adaptor. Best regards, ------ Ferm?n ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fermin at tid.es Mon May 27 10:25:25 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Mon, 27 May 2013 10:25:25 +0200 Subject: [Fiware-demo] Live Demo current (May 27th) status Message-ID: <51A31875.7080505@tid.es> Hi, This is a report of current status of Live Demo activities that will be included in today WPL/WPA meeting minutes (). Progress regarding last report on May 20th is highlighted in red. * Epic/Features documentation for R1 and R2. UPM is working on the "core" wiki structure. Ongoing. * Widgets adaptation/implementation. UPM is working on it. The widgets to show History element information will be ready by early this week. * Store and marketplace adaptation and integration. UPM is working on it .Ongoing. * History element implementation. A functional implementation is currently installed and working in the Live Demo testbed, gathering information from contextBroker. * Object Storage integration (based in a similar case from ENVIROFI demo). UPM is working on it. Ongoing. * Backend Device Management (IDAS) integration.(including actual sensor data from OutSmart). Sucessfull integration of IDAS-ContextBrokker-History. * CEP integration. ContextBroker-CEP integration is clear. CEP adaptation completed. Integration work starts on May 27th. * PaaS Manager integration. Chef receipts for deploying ContextBroker GE finished. Chef receipt for deployment user application are finished. Documented as part of Live Demo under theme FIWARE.Theme.Cross.LiveDemo.AutomaticDeployment. * API Access Control: pending of having all the components integrated. * Usage of the Location Platform from WP6. Plan to integrate a simulation of a route and update the position of various mobile users. Compatibility tested. Issues with the LOCS server, it works sometimes, maybe there are issues with the client requests. Checking with Thales. Best regards, ------ Ferm?n ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fermin at tid.es Mon May 27 10:29:48 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Mon, 27 May 2013 10:29:48 +0200 Subject: [Fiware-demo] Live Demo current (May 27th) status In-Reply-To: <51A31875.7080505@tid.es> References: <51A31875.7080505@tid.es> Message-ID: <51A3197C.5070905@tid.es> Hi, Sorry, I missed the URL to the minutes in my previous email: https://docs.google.com/document/d/1h5fQOSjy5_aDO9pQ7_5Y2GQq-Q5mTv0-CjD_giqk-HU/edit?usp=sharing Best regards, ------ Ferm?n El 27/05/2013 10:25, Ferm?n Gal?n M?rquez escribi?: Hi, This is a report of current status of Live Demo activities that will be included in today WPL/WPA meeting minutes (). Progress regarding last report on May 20th is highlighted in red. * Epic/Features documentation for R1 and R2. UPM is working on the "core" wiki structure. Ongoing. * Widgets adaptation/implementation. UPM is working on it. The widgets to show History element information will be ready by early this week. * Store and marketplace adaptation and integration. UPM is working on it .Ongoing. * History element implementation. A functional implementation is currently installed and working in the Live Demo testbed, gathering information from contextBroker. * Object Storage integration (based in a similar case from ENVIROFI demo). UPM is working on it. Ongoing. * Backend Device Management (IDAS) integration.(including actual sensor data from OutSmart). Sucessfull integration of IDAS-ContextBrokker-History. * CEP integration. ContextBroker-CEP integration is clear. CEP adaptation completed. Integration work starts on May 27th. * PaaS Manager integration. Chef receipts for deploying ContextBroker GE finished. Chef receipt for deployment user application are finished. Documented as part of Live Demo under theme FIWARE.Theme.Cross.LiveDemo.AutomaticDeployment. * API Access Control: pending of having all the components integrated. * Usage of the Location Platform from WP6. Plan to integrate a simulation of a route and update the position of various mobile users. Compatibility tested. Issues with the LOCS server, it works sometimes, maybe there are issues with the client requests. Checking with Thales. Best regards, ------ Ferm?n ________________________________ 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-demo mailing list Fiware-demo at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-demo ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.dallecarbonare at eng.it Tue May 28 12:20:33 2013 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Tue, 28 May 2013 12:20:33 +0200 Subject: [Fiware-demo] Live Demo current (May 27th) status In-Reply-To: <51A3197C.5070905@tid.es> References: <51A31875.7080505@tid.es> <51A3197C.5070905@tid.es> Message-ID: <51A484F1.7070207@eng.it> Hi Fermin, can you kindly provide me the end point URL of the PubSub Context Broker you're using? Is it available to IPs enabled in the testbed? thank you, Davide On 27/05/2013 10:29, Ferm?n Gal?n M?rquez wrote: > Hi, > > Sorry, I missed the URL to the minutes in my previous email: > https://docs.google.com/document/d/1h5fQOSjy5_aDO9pQ7_5Y2GQq-Q5mTv0-CjD_giqk-HU/edit?usp=sharing > > Best regards, > > ------ > Ferm?n > > El 27/05/2013 10:25, Ferm?n Gal?n M?rquez escribi?: >> Hi, >> >> This is a report of current status of Live Demo activities that will >> be included in today WPL/WPA meeting minutes (). Progress regarding >> last report on May 20th is highlighted in red. >> >> * Epic/Features documentation for R1 and R2. UPM is working on the >> "core" wiki structure. Ongoing. >> * Widgets adaptation/implementation. UPM is working on it. The >> widgets to show History element information will be ready by >> early this week. >> * Store and marketplace adaptation and integration. UPM is working >> on it .Ongoing. >> * History element implementation. A functional implementation is >> currently installed and working in the Live Demo testbed, >> gathering information from contextBroker. >> * Object Storage integration (based in a similar case from ENVIROFI >> demo). UPM is working on it. Ongoing. >> * Backend Device Management (IDAS) integration.(including actual >> sensor data from OutSmart). Sucessfull integration of >> IDAS-ContextBrokker-History. >> * CEP integration. ContextBroker-CEP integration is clear. CEP >> adaptation completed. Integration work starts on May 27th. >> * PaaS Manager integration. Chef receipts for deploying >> ContextBroker GE finished. Chef receipt for deployment user >> application are finished. Documented as part of Live Demo under >> theme FIWARE.Theme.Cross.LiveDemo.AutomaticDeployment. >> * API Access Control: pending of having all the components integrated. >> * Usage of the Location Platform from WP6. Plan to integrate a >> simulation of a route and update the position of various mobile >> users. Compatibility tested. Issues with the LOCS server, it >> works sometimes, maybe there are issues with the client requests. >> Checking with Thales. >> >> Best regards, >> >> ------ >> Ferm?n >> ------------------------------------------------------------------------ >> >> 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-demo mailing list >> Fiware-demo at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-demo > > > ------------------------------------------------------------------------ > > 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-demo mailing list > Fiware-demo at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-demo -------------- next part -------------- An HTML attachment was scrubbed... URL: From fermin at tid.es Tue May 28 12:59:49 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Tue, 28 May 2013 12:59:49 +0200 Subject: [Fiware-demo] Live Demo current (May 27th) status In-Reply-To: <51A484F1.7070207@eng.it> References: <51A31875.7080505@tid.es> <51A3197C.5070905@tid.es> <51A484F1.7070207@eng.it> Message-ID: <51A48E25.2070401@tid.es> Dear Davide, Could you elaborate a bit more on why do you need the URL? E.g. are you planning to use ContextBroker to register context information ("write" information)? Or are you planning to access the information we also use for Live Demo App ("read" information)? I need to know to avoid any potential conflict with the ongoing activities... Thanks! Best regards, ------ Ferm?n El 28/05/2013 12:20, Davide Dalle Carbonare escribi?: Hi Fermin, can you kindly provide me the end point URL of the PubSub Context Broker you're using? Is it available to IPs enabled in the testbed? thank you, Davide On 27/05/2013 10:29, Ferm?n Gal?n M?rquez wrote: Hi, Sorry, I missed the URL to the minutes in my previous email: https://docs.google.com/document/d/1h5fQOSjy5_aDO9pQ7_5Y2GQq-Q5mTv0-CjD_giqk-HU/edit?usp=sharing Best regards, ------ Ferm?n El 27/05/2013 10:25, Ferm?n Gal?n M?rquez escribi?: Hi, This is a report of current status of Live Demo activities that will be included in today WPL/WPA meeting minutes (). Progress regarding last report on May 20th is highlighted in red. * Epic/Features documentation for R1 and R2. UPM is working on the "core" wiki structure. Ongoing. * Widgets adaptation/implementation. UPM is working on it. The widgets to show History element information will be ready by early this week. * Store and marketplace adaptation and integration. UPM is working on it .Ongoing. * History element implementation. A functional implementation is currently installed and working in the Live Demo testbed, gathering information from contextBroker. * Object Storage integration (based in a similar case from ENVIROFI demo). UPM is working on it. Ongoing. * Backend Device Management (IDAS) integration.(including actual sensor data from OutSmart). Sucessfull integration of IDAS-ContextBrokker-History. * CEP integration. ContextBroker-CEP integration is clear. CEP adaptation completed. Integration work starts on May 27th. * PaaS Manager integration. Chef receipts for deploying ContextBroker GE finished. Chef receipt for deployment user application are finished. Documented as part of Live Demo under theme FIWARE.Theme.Cross.LiveDemo.AutomaticDeployment. * API Access Control: pending of having all the components integrated. * Usage of the Location Platform from WP6. Plan to integrate a simulation of a route and update the position of various mobile users. Compatibility tested. Issues with the LOCS server, it works sometimes, maybe there are issues with the client requests. Checking with Thales. Best regards, ------ Ferm?n ________________________________ 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-demo mailing list Fiware-demo at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-demo ________________________________ 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-demo mailing list Fiware-demo at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-demo ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.dallecarbonare at eng.it Tue May 28 14:42:24 2013 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Tue, 28 May 2013 14:42:24 +0200 Subject: [Fiware-demo] Live Demo current (May 27th) status In-Reply-To: <51A48E25.2070401@tid.es> References: <51A31875.7080505@tid.es> <51A3197C.5070905@tid.es> <51A484F1.7070207@eng.it> <51A48E25.2070401@tid.es> Message-ID: <51A4A630.7030702@eng.it> I definitely want to avoid any sort of conflict too. 1) We plan to use the ContextBroker to demonstrate the Java client generator executing few read/write operations. After that we would like to switch to another instance to prove that the client is independent from the instance/implementation. We can agree that we can use a prefix for our entries to avoid conflicts: can "tls_" work for you? 2) I need to contact someone (operating the testbed, probably) to put in contact with Marcel (in cc). We're looking for a set of runtime information to elaborate and present using TraceAnalyzer. Alternatively, let me know if there are a couple of instances that we can use. thank you and kind regards, Davide On 28/05/2013 12:59, Ferm?n Gal?n M?rquez wrote: > Dear Davide, > > Could you elaborate a bit more on why do you need the URL? E.g. are > you planning to use ContextBroker to register context information > ("write" information)? Or are you planning to access the information > we also use for Live Demo App ("read" information)? > > I need to know to avoid any potential conflict with the ongoing > activities... > > Thanks! > > Best regards, > > ------ > Ferm?n > > El 28/05/2013 12:20, Davide Dalle Carbonare escribi?: >> Hi Fermin, >> can you kindly provide me the end point URL of the >> PubSub Context Broker you're using? >> >> Is it available to IPs enabled in the testbed? >> >> thank you, >> Davide >> >> On 27/05/2013 10:29, Ferm?n Gal?n M?rquez wrote: >>> Hi, >>> >>> Sorry, I missed the URL to the minutes in my previous email: >>> https://docs.google.com/document/d/1h5fQOSjy5_aDO9pQ7_5Y2GQq-Q5mTv0-CjD_giqk-HU/edit?usp=sharing >>> >>> Best regards, >>> >>> ------ >>> Ferm?n >>> >>> El 27/05/2013 10:25, Ferm?n Gal?n M?rquez escribi?: >>>> Hi, >>>> >>>> This is a report of current status of Live Demo activities that >>>> will be included in today WPL/WPA meeting minutes (). Progress >>>> regarding last report on May 20th is highlighted in red. >>>> >>>> * Epic/Features documentation for R1 and R2. UPM is working on >>>> the "core" wiki structure. Ongoing. >>>> * Widgets adaptation/implementation. UPM is working on it. The >>>> widgets to show History element information will be ready by >>>> early this week. >>>> * Store and marketplace adaptation and integration. UPM is >>>> working on it .Ongoing. >>>> * History element implementation. A functional implementation is >>>> currently installed and working in the Live Demo testbed, >>>> gathering information from contextBroker. >>>> * Object Storage integration (based in a similar case from >>>> ENVIROFI demo). UPM is working on it. Ongoing. >>>> * Backend Device Management (IDAS) integration.(including actual >>>> sensor data from OutSmart). Sucessfull integration of >>>> IDAS-ContextBrokker-History. >>>> * CEP integration. ContextBroker-CEP integration is clear. CEP >>>> adaptation completed. Integration work starts on May 27th. >>>> * PaaS Manager integration. Chef receipts for deploying >>>> ContextBroker GE finished. Chef receipt for deployment user >>>> application are finished. Documented as part of Live Demo under >>>> theme FIWARE.Theme.Cross.LiveDemo.AutomaticDeployment. >>>> * API Access Control: pending of having all the components >>>> integrated. >>>> * Usage of the Location Platform from WP6. Plan to integrate a >>>> simulation of a route and update the position of various mobile >>>> users. Compatibility tested. Issues with the LOCS server, it >>>> works sometimes, maybe there are issues with the client >>>> requests. Checking with Thales. >>>> >>>> Best regards, >>>> >>>> ------ >>>> Ferm?n >>>> ------------------------------------------------------------------------ >>>> >>>> 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-demo mailing list >>>> Fiware-demo at lists.fi-ware.eu >>>> https://lists.fi-ware.eu/listinfo/fiware-demo >>> >>> >>> ------------------------------------------------------------------------ >>> >>> 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-demo mailing list >>> Fiware-demo at lists.fi-ware.eu >>> https://lists.fi-ware.eu/listinfo/fiware-demo >> > > > ------------------------------------------------------------------------ > > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fermin at tid.es Tue May 28 16:01:34 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Tue, 28 May 2013 16:01:34 +0200 Subject: [Fiware-demo] Live Demo current (May 27th) status In-Reply-To: <51A4A630.7030702@eng.it> References: <51A31875.7080505@tid.es> <51A3197C.5070905@tid.es> <51A484F1.7070207@eng.it> <51A48E25.2070401@tid.es> <51A4A630.7030702@eng.it> Message-ID: <51A4B8BE.8060506@tid.es> Dear Davide, Thank you for your detailed information. As far as I understand, you don't need to access to the context information used by the Live Demo App, so I think is better to use separate instances. Installing ContextBroker is a matter of minutes and it is definively safer than using the ContextBroker used for Live Demo App. I can install and configure ContextBroker for you if you provide me with one or two VMs to do do. CentOS 6.3 is required as operating system. Note that you don't actually need two VMs: I can install two ContextBroker instances in the same VM running in different ports. Regarding issue 2), I'm not sure that testbed people is in this mailist. If nobody answer to this point, I would suggest to move your request to testbed WP mailing list. Best regards, ------ Fermin El 28/05/2013 14:42, Davide Dalle Carbonare escribi?: I definitely want to avoid any sort of conflict too. 1) We plan to use the ContextBroker to demonstrate the Java client generator executing few read/write operations. After that we would like to switch to another instance to prove that the client is independent from the instance/implementation. We can agree that we can use a prefix for our entries to avoid conflicts: can "tls_" work for you? 2) I need to contact someone (operating the testbed, probably) to put in contact with Marcel (in cc). We're looking for a set of runtime information to elaborate and present using TraceAnalyzer. Alternatively, let me know if there are a couple of instances that we can use. thank you and kind regards, Davide On 28/05/2013 12:59, Ferm?n Gal?n M?rquez wrote: Dear Davide, Could you elaborate a bit more on why do you need the URL? E.g. are you planning to use ContextBroker to register context information ("write" information)? Or are you planning to access the information we also use for Live Demo App ("read" information)? I need to know to avoid any potential conflict with the ongoing activities... Thanks! Best regards, ------ Ferm?n El 28/05/2013 12:20, Davide Dalle Carbonare escribi?: Hi Fermin, can you kindly provide me the end point URL of the PubSub Context Broker you're using? Is it available to IPs enabled in the testbed? thank you, Davide On 27/05/2013 10:29, Ferm?n Gal?n M?rquez wrote: Hi, Sorry, I missed the URL to the minutes in my previous email: https://docs.google.com/document/d/1h5fQOSjy5_aDO9pQ7_5Y2GQq-Q5mTv0-CjD_giqk-HU/edit?usp=sharing Best regards, ------ Ferm?n El 27/05/2013 10:25, Ferm?n Gal?n M?rquez escribi?: Hi, This is a report of current status of Live Demo activities that will be included in today WPL/WPA meeting minutes (). Progress regarding last report on May 20th is highlighted in red. * Epic/Features documentation for R1 and R2. UPM is working on the "core" wiki structure. Ongoing. * Widgets adaptation/implementation. UPM is working on it. The widgets to show History element information will be ready by early this week. * Store and marketplace adaptation and integration. UPM is working on it .Ongoing. * History element implementation. A functional implementation is currently installed and working in the Live Demo testbed, gathering information from contextBroker. * Object Storage integration (based in a similar case from ENVIROFI demo). UPM is working on it. Ongoing. * Backend Device Management (IDAS) integration.(including actual sensor data from OutSmart). Sucessfull integration of IDAS-ContextBrokker-History. * CEP integration. ContextBroker-CEP integration is clear. CEP adaptation completed. Integration work starts on May 27th. * PaaS Manager integration. Chef receipts for deploying ContextBroker GE finished. Chef receipt for deployment user application are finished. Documented as part of Live Demo under theme FIWARE.Theme.Cross.LiveDemo.AutomaticDeployment. * API Access Control: pending of having all the components integrated. * Usage of the Location Platform from WP6. Plan to integrate a simulation of a route and update the position of various mobile users. Compatibility tested. Issues with the LOCS server, it works sometimes, maybe there are issues with the client requests. Checking with Thales. Best regards, ------ Ferm?n ________________________________ 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-demo mailing list Fiware-demo at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-demo ________________________________ 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-demo mailing list Fiware-demo at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-demo ________________________________ 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 ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fermin at tid.es Tue May 28 18:56:17 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Tue, 28 May 2013 18:56:17 +0200 Subject: [Fiware-demo] AutomaticDeployment theme Message-ID: <51A4E1B1.8040106@tid.es> Hi, Recently, we have included a draft of the AutomaticDeployment theme (*) that describes the role of PaaSManager GE (cloud chapter) in Live Demo App in the wiki at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Live_Demo_Evolution#Live_Demo_Evolution. The bussines draft fragment automatically generated from this theme is on https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Product_Vision_Draft#Been_able_to_automatically_deploy_and_configure_software. I think this is an excellent example of how to apply the Agile methodology to Live Demo App, defining Themes/Epics/Features that at the end compose the Business Vision document. Please, take it as an example when you prepare your own contributions to Live Demo App. Thanks to Fernando L?pez and his team for this contribution! Best regards, ------ Ferm?n (*) I know that "Theme" is obsolete in favour of "first Level Epic". However, I think we will keep the old nomenclature for a time, until we have time to change it. ________________________________ 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