[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [iot-wg] Updates to Asset Tracker?
|
| Hi Matt,
Sorry I didn’t come back to you earlier.
Like David Woodard from Kura said, Kura-specific issues should be filed against the Kura github repo, or you can also of course engage on the kura-dev mailing list. With regards to the Asset Tracking testbed itself, please use the issue tracker over at https://github.com/eclipselabs/eclipseiot-testbed-assettracking. Please also feel free to open pull requests for any patches you may have.
When it comes to the hosted environment, the demo accessible at https://iot.eclipse.org/testbeds/asset-tracking/demo is effectively hosted on Google Cloud Platform, on a VM where I deployed OpenShift Origin and basically deployed the different pods of the testbed. I am not sure I understand your question on the "parallel version" eclipseiot-testbed-productionperformancemanagement. The Industry 4.0/production performance management testbed is a different testbed, and currently the live demo is hosted and maintained by the Eclipse Unide project team. I would be happy to help you replicate a setup similar to the current GCP-hosted demo, but would also be interested in hearing your requirements in terms of yanking around the testbed, as it might make sense to figure out a way to do this on the existing testbed environment in order to demonstrate the ruggedness of the solution.
HTH Benjamin -
Hello IoT teams: Azul wants to do some experimentation on the Asset Tracker test bed. Part One: We already did our Eclipse Kura pieces and found a bunch of Maven dependency fixes. How best should we report each issue (and upstream any source patches) back to the Kura team and/or to the current Asset Tracker hosts? Part Two: We request a parallel instance of the Kapua/OpenShift/Elastic back end that we can play against without disrupting the existing live system. I don’t know who specifically (Benjamin?) setup the public Asset Tracker, but there already appears to be a parallel version called eclipseiot-testbed-productionperformancemanagement. We would similarly want another parallel version only to give us confidence on a working Asset Tracker system that we can yank around and shove gateway data into, while in parallel we setup our own hosted instance to make the somewhat more invasive data, UI, and stack configuration mods we are considering. BTW, we would gladly bring other IoT WG partners into our effort if anyone is interested in playing together, but today our goal is to learn how to use the current Asset Tracker from its parts in its current form without upsetting other test bed users. Thanks much. Matt Schuetze Azul Product Manager
|
Attachment:
signature.asc
Description: Message signed with OpenPGP
