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<mailto: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<mailto: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: <https://lists.fiware.org/private/fiware-demo/attachments/20130528/9b314550/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy