Weekly Update: As the progress of the project stands right now the following has been implemented on the end of the IoT server;
1) APIs updated according to the requirements of required library <http://visjs.org/> 2) Device hierarchy visualization completed and rendered successfully Work in progress at the time of writing is as follows; 1) Fine tuning visualization to produce clearer outputs End of month goals; 1) Testing Efficiency of visualization with mock 100 device organization configuration using JMeter script 2) Creating REST API to get entire network organization as Tree JSON object. On Thu, Oct 5, 2017 at 6:12 PM, Nuwan Jayawardene <[email protected]> wrote: > Monthly update: > > *The previous state of the project was put on hold to perform a design > review and proceed forward with any feedback received.* > > As the progress of the project stands right now the following has been > implemented on the end of the IoT server; > > 1) Held design review and gained feedback with regards to changes that > need to be done on the implementation so far > 2) Implemented desired changes and redid project from scratch to match new > requirements > 3) Selected suitable library for the visualization of the network > hierarchy. Studied the required data structure needed for the visualization > 4) Successfully completed APIs with data structure needed for the library > > Work in progress at the time of writing is as follows; > > 1) Building the UI component such that a preliminary visualization can be > done before moving onto fine tuning and advanced work. > > End of month goals; > > 1) Having workable UI providing Device Organization information > 2) Finalizing required APIs and adding new ones according to the > requirements of the UI > > On Fri, Sep 1, 2017 at 3:12 PM, Nuwan Jayawardene <[email protected]> wrote: > >> Monthly update: >> >> As the progress of the project stands right now the following has been >> implemented on the end of the IoT server; >> >> 1) Main APIs have been implemented and published >> 2) Integration test scripts were written >> 3) Integration tests run and build successful >> >> Work in progress at the time of writing is as follows; >> >> 1) Understanding the UUF framework to develop the UI component >> >> End of month goals; >> >> 1) Having workable UI providing Device Organization information >> 2) Finalizing required APIs and adding new ones according to the >> requirements of the UI >> >> On Wed, Aug 23, 2017 at 2:14 PM, Nuwan Jayawardene <[email protected]> >> wrote: >> >>> Monthly update: >>> >>> As the progress of the project stands right now the following has been >>> implemented on the end of the IoT server; >>> >>> 1) Device organization database tables and DAO functionality >>> 2) Unit tests for the Device Organization DAO functionality tested and >>> builds successful >>> 3) OSGi service implemented and APIs published exposing the Device >>> Organization meta data handling operations >>> >>> Work in progress at the time of writing is as follows; >>> >>> 1) Implementing and publishing each individual API and checking for >>> errors and issues >>> >>> End of month goals; >>> >>> 1) Write integration tests to check APIs when building the final pack >>> >>> On Fri, Jul 28, 2017 at 3:13 PM, Nuwan Jayawardene <[email protected]> >>> wrote: >>> >>>> Overview >>>> >>>> As the product stands right now, WSO2 IoT Server only has the >>>> capability to detect and manage devices in direct connection with it. It >>>> has no capability to detect nor manage any device(s) connected via one or a >>>> network of IoT gateways. Providing this capability to the IoT server will >>>> give us benefits in the long run such as; >>>> >>>> >>>> 1. >>>> >>>> Enabling more efficient edge analytics. >>>> 2. >>>> >>>> Enabling legacy devices to connect to IoT server thus widening >>>> applicable use cases and scope. >>>> 3. >>>> >>>> Enabling better organizational structure to a complex network of >>>> devices. >>>> 4. >>>> >>>> Enabling more security features to be added locally (to gateways) >>>> as well as to IoTS itself. >>>> 5. >>>> >>>> Enabling M2M connectivity features. >>>> >>>> >>>> Current state >>>> >>>> The project I am currently working on is based on programming the >>>> capability for IoTS server to detect and manage edge devices connected >>>> through a IoT gateway or a series of gateways. >>>> >>>> This will be achieved by making modifications to the agents running on >>>> edge devices as well as the gateway to gather additional metadata along >>>> with modifications on the server side to retrieve and process this meta >>>> data. >>>> >>>> >>>> *High level view of architecture* >>>> >>>> [image: High-level architecture.png] >>>> >>>> >>>> In the case of edge devices the modifications will allow for detection >>>> of any parent device they are connected to. In the case of the IoT gateway, >>>> the modifications will allow for the detection of a parent device as well >>>> as child devices connected to it. >>>> >>>> >>>> *Development phases* >>>> >>>> >>>> >>>> Phases >>>> >>>> Deliverables >>>> >>>> State >>>> >>>> Phase 1 >>>> >>>> Developing gateway agent to store metadata on connected devices >>>> >>>> (On hold) >>>> >>>> Developing an edge device agent to communicate with gateway >>>> >>>> To be developed >>>> >>>> Developing IoTS side capability to interface with gateway and >>>> understand metadata. >>>> >>>> In progress >>>> >>>> Phase 2 >>>> >>>> Develop IoTS side capability to map networked devices >>>> >>>> To be developed >>>> >>>> Develop visual dashboard to view connected devices in UI >>>> >>>> To be developed >>>> >>>> Develop capability for fault detection of an edge device >>>> >>>> To be developed >>>> >>>> Phase 3 >>>> >>>> Research and develop M2M connectivity functionality to both IoTS and >>>> Gateways >>>> >>>> To be developed >>>> >>>> >>>> Suggestions and feedback are appreciated. >>>> >>>> -- >>>> *Nuwan Jayawardene* >>>> *Software Engineering intern* >>>> *WSO2, Inc.:http://wso2.com <http://wso2.com/>* >>>> *lean.enterprise.middleware* >>>> *Mobile :- +94 71 1813299 <+94%2071%20181%203299>* >>>> >>>> >>>> - *Linkedin* *:- **https://www.linkedin.com/in/nuwa >>>> <https://www.linkedin.com/in/nuwanjaya/>**njaya/ >>>> <https://www.linkedin.com/in/nuwanjaya/>* >>>> - * <https://www.wso2.com/signature>* >>>> >>>> >>> >>> >>> -- >>> *Nuwan Jayawardene* >>> *Software Engineering intern* >>> *WSO2, Inc.:http://wso2.com <http://wso2.com/>* >>> *lean.enterprise.middleware* >>> *Mobile :- +94 71 1813299 <+94%2071%20181%203299>* >>> >>> >>> - *Linkedin* *:- **https://www.linkedin.com/in/nuwa >>> <https://www.linkedin.com/in/nuwanjaya/>**njaya/ >>> <https://www.linkedin.com/in/nuwanjaya/>* >>> - * <https://www.wso2.com/signature>* >>> >>> >> >> >> -- >> *Nuwan Jayawardene* >> *Software Engineering intern* >> *WSO2, Inc.:http://wso2.com <http://wso2.com/>* >> *lean.enterprise.middleware* >> *Mobile :- +94 71 1813299 <+94%2071%20181%203299>* >> >> >> - *Linkedin* *:- **https://www.linkedin.com/in/nuwa >> <https://www.linkedin.com/in/nuwanjaya/>**njaya/ >> <https://www.linkedin.com/in/nuwanjaya/>* >> - * <https://www.wso2.com/signature>* >> >> > > > -- > *Nuwan Jayawardene* > *Software Engineering intern* > *WSO2, Inc.:http://wso2.com <http://wso2.com/>* > *lean.enterprise.middleware* > *Mobile :- +94 71 1813299 <+94%2071%20181%203299>* > > > - *Linkedin* *:- **https://www.linkedin.com/in/nuwa > <https://www.linkedin.com/in/nuwanjaya/>**njaya/ > <https://www.linkedin.com/in/nuwanjaya/>* > - * <https://www.wso2.com/signature>* > > -- *Nuwan Jayawardene* *Software Engineering intern* *WSO2, Inc.:http://wso2.com <http://wso2.com/>* *lean.enterprise.middleware* *Mobile :- +94 71 1813299* - *Linkedin* *:- **https://www.linkedin.com/in/nuwa <https://www.linkedin.com/in/nuwanjaya/>**njaya/ <https://www.linkedin.com/in/nuwanjaya/>* - * <https://www.wso2.com/signature>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
