LEaRN The Lafayette Engagement and Research Network

2017-07-24 LEaRN Status Meeting (CGI)

Original CGI Document
SubjectStatus Meeting (CGI)
Project NameLEaRN
Meeting DateJuly 17, 2017
Chairperson
Dial-in Info

Host key: 199735


Join WebEx meeting<https://cgifederal.webex.com/cgifederal/j.php?MTID=m4a162804d9845bdfd1947806438d109a>
Meeting number: 747 675 789
Meeting password: g26tiUHP

Join by phone
Call-in toll-free number: 1-866-5573330 (US)
Call-in number: 1-443-8637759 (US)
Show global numbers<https://www.tcconline.com/offSite/OffSiteController.jpf?cc=6573812350>
Leader PIN: 1146
Conference Code: 657 381 2350

Can't join the meeting? Contact support.<https://cgifederal.webex.com/cgifederal/mc>

IMPORTANT NOTICE: Please note that this WebEx service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. You should inform all meeting attendees prior to recording if you intend to record the meeting.

Time / Location2017-07-17 2:00 PM CST / 1N-09

 

 

Discussion Items

TimeItemOwner(s)Notes
Administrative
5minReview Deadlines 
  • Upcoming Deadlines

    • Sprint completion 7/28/2017
    • August 15th finish prototypes and final design
    • July-Early August, purchasing for devices
    • Early September begin build process of devices with ULL/David Thibodaux students
 O&M

Status update:

  • We need to start thinking when and where we would deploy our next sensor prototypes, and what sensors those prototypes will include.
    • Will discuss this at sensor placement planning meeting tomorrow
  • Deploy new algorithm to sensor boxes after 7/17/2017 at 1pm central
    • Log the current & new algorithms and compare the differences. (Will email LCG to gain access to the sensor boxes after meeting)
    • Did not get to it last week, but will dedicate all work for this Sprint on Wednesday, 7/26/2017.
  • Set up DEV API pointing to new keyspace in Cass cluster
    1. Create ticket for this sprint
    2. Duplicate steps used for Prod API
    3. Confirm steps needed for Thing token validation
 Hardware

Status update:

 Firmware and device management

Status update:

  • Add new datastreams to account for new sensors. (Possibly make new sample.py type of files for specific sensor boxes)
 API

Status update:

  • LEARN-106: Cascade on deletion complete
    • Complete
  • LEARN-154: Ensure HistoricalLocation is created for new locations
    • Complete
  • LEARN-147: Request Bamboo CI build plan for API code
    • Complete
    • Build plan is for Kinota repo, which won't be ready until LEARN-148 and LEARN-187 are complete.
    • Created LEARN-188 as a follow-up issue.
  • LEARN-148: Clean up code for OSS release
    • Waiting for code review
    • Due to upcoming vacation of Miles, Brian (CGI Federal) the code clean up has been broken into two issues. LEARN-187 details the remaining code clean up issues that need to be completed before open source release.
 Visualization and Use Cases

Status update:

  Architecture & AnalyticsChepudira, Karthik (CGI Federal) 

Completed

  • Worked on connectivity between sensors and azure IOT directly via MQTT - Done
  • Setting up MQTT bridge with X.509 certificates - Done
  • Validate mapping for Azure Iot Hub device endpoint and thingid (deviceid) in azure function -Done
  • Plan to setup MQTT broker to map STA topics to Azure IoT topics - Done
  • Automation of device authentication for Azure IoT Hub device - Done
  • Create sensor deployment location plan and provide suggestions
    see 'SensorDeploymentConfiguration.xlsx' file here Sensor locations

Ongoing

  • Make Updates to sensor code (transmit.py) to allow communication directly to azure IoT hub.
  • Creating API things, data streams etc from the device manifest.

TODO

  • Create a POC for creating Air Quality Index for the streaming sensor data
 Outreach
  • GitHub integration with Confluence
    • Flat HTML page output finished
      • Content links need to be filtered/removed/rewritten
      • Dynamic menus filtering for GitHub Pages
    • Then will automate using a cron job running on a VM hosting a Drupal instance
      • This Drupal instance may be running as part of AgileIQ infrastructure
  • GitHub integration with source code
    • Code will be pushed from Bitbucket to GitHub manually for releases as appropriate
 Review Scrum Board 
    

 

 

Decisions

DescriptionOwner(s)
  

Action items

Date Assigned 

DescriptionOwner(s)

Due Date

Completion Date Notes 
 
  •  
      

Risks and Issues

Risk or Issue

Date Identified 

 

DescriptionOwner(s)Follow-up DateNotes 
  
  •  Notes for this item