-
Notifications
You must be signed in to change notification settings - Fork 27
Open espi meeting minutes, 30 april 2012
Open ESPI Meeting
30 April 2012
9PT/10MT/12:00ET US
Attendees:
Anne HendryDave Krinkel
Peter Michalek
Dave Mollerstuen
Ron Pasquarelli
Jeremy Roberts
Andrew Steckley
Agenda:
-
OpenESPI source code architecture and repository (continued from last week)
-
DB support and incorporating SDG&E data
-
Further thoughts on time zone rationalization
-
Spring framework and OAuth implementation update
-
Developing an architecture to support porting
-
Ids, links, organization of data blocks issue
-
Connectivity Week plug-fest / demo progress (follow on to last week's discussion)
-
Plug-In web page: http://www.connectivityweek.com/2012/#plug
-
CW Green Button activity: http://www.connectivityweek.com/2012/#topic_149
Discussion:
-
OpenESPI source code architecture and repository (continued from last week)
-
DB support and incorporating SDG&E data
-
Further thoughts on time zone rationalization
-
Spring framework and OAuth implementation update
-
Developing an architecture to support porting
-
Ids, links, organization of data blocks issue
Discussion focused on the need for Green Button test development. Peter M. and Dave M. might be able to take some tasks, depending on need. Peter has downloaded the VM. Suggests creating a document that is an overview showing which files are being generated from the system (Spring, etc) and which are ones that need to be coded, just to get the basics laid out. See links to resources below and on the GreenButton site. It was suggested the information be consolidated in one (or perhaps two) places at most to make it easier for developers to find the relevant information.
Discussion continued on developing a test harness for creating the Golden Unit against which certification will be done. Right now the complexity level seems high: DataCustodian is over 770 files, although only a few of them need development/changes as most are auto-generated. It would be helpful to define the architecture independent of the specific implementation technology. It appears quite heavyweight when compared to other APIs in mashups like Google or social APIs, usually using simple JASON. If it can be simplified, believe we'll see an acceleration in outside development. It would help if the implementation could also be viewable in the source tree, not necessarily requiring EA.
Perhaps additional documentation on the VM to describe the tools and technologies contained there would be helpful. All the tools in the VM are open source. More documentation should also point to the NAESB standard so developers can connect the implementation to the standard. It would help to have one place from which you could reference all the documentation.
-
Connectivity Week plug-fest / demo progress (follow on to last week's discussion)
-
Plug-In web page: http://www.connectivityweek.com/2012/#plug
-
CW Green Button activity: http://www.connectivityweek.com/2012/#topic_149
Discussion deferred to next week.
Energy OS home page: http://energyos.org/
OpenESPI home page: http://www.openespi.org/
OpenESPI minutes / call info: https://github.com/energyos/OpenESPI/wiki/Open-ESPI-Meetings
General OpenESPI information: https://github.com/energyos/OpenESPI/wiki/
Ubuntu Virtual Machine distribution: http://www.openespi.org/vm.html
VM setup instructions: https://github.com/energyos/OpenESPI/wiki/Virtual-Machine-Setup
OpenESPI source code repository: https://github.com/energyos/OpenESPI
GitHub issues: https://github.com/energyos/OpenESPI/issues
Relevant OpenADE issues: http://osgug.ucaiug.org/HelpDesk/Lists/servicerequests/GreenButton.aspx
GB Initiative: http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/GreenButtonInitiative
GB Home: http://www.greenbuttondata.org/