=====================================================
#opendaylight-persistence: Persistence Weekly Meeting
=====================================================


Meeting started by fabiel at 17:04:07 UTC.  The full logs are available
at
http://meetings.opendaylight.org/opendaylight-persistence/2015/persistence_weekly_meeting/opendaylight-persistence-persistence_weekly_meeting.2015-01-21-17.04.log.html
.



Meeting summary
---------------

* Agenda  (nachiket331, 17:07:20)
* Status Update #info Lithium Release Plan Review #info Questions #topic
  Status Update  (nachiket331, 17:08:25)
* Status Update  (nachiket331, 17:08:44)
* Lithium Release Plan Review  (nachiket331, 17:08:59)
* Questions  (nachiket331, 17:09:11)
* LINK: https://wiki.opendaylight.org/view/Persistence:Main Persistence
  facts page  (nachiket331, 17:09:49)
* LINK: https://wiki.opendaylight.org/view/Persistence:Weekly_Meeting
  Persistence Weekly Meeting  (nachiket331, 17:11:29)
* LINK:
  https://wiki.opendaylight.org/view/Persistence:Lithium_Release_Plan
  Persistence Lithium Release Plan  (nachiket331, 17:11:44)
* LINK: https://jenkins.opendaylight.org/releng/view/persistence/
  Persistence Jenkins Jobs  (nachiket331, 17:11:55)
* LINK: https://sonar.opendaylight.org/dashboard/index/31868 Persistence
  SonarQube  (nachiket331, 17:12:07)
* LINK:
  https://bugs.opendaylight.org/buglist.cgi?bug_status=__open__&order=Importance&product=persistence&query_format=specific
  Persistence Bugs  (nachiket331, 17:12:16)
* Do we need the status column in the release plan ?  (nachiket331,
  17:15:27)
* ACTION: fabiel will upload the persistence release plan to lithium
  release plan for review  (nachiket331, 17:17:17)
* sonar tracks unit test coverage  (nachiket331, 17:18:13)
* ACTION: fabiel or nachiket331 we need to investigate more on how
  system testing and CI is done for persistence. Is it Robot ? we create
  a test app using SQL lite for CI for now ?  (nachiket331, 17:22:06)
* ACTION: we need to investigate what applications will use the database
  ? Can they come with their own database as part of their plugin and
  install the relevant service without having to restart the controller
  ?  (nachiket331, 17:29:00)
* As part of the developer guide, we should include information on
  implementing new database service  (nachiket331, 17:31:31)
* ACTION: update the JPA support section saying we will ship with SQLite
  DB by default  (nachiket331, 17:32:27)
* ACTION: investigate Nexus Repository Binary artifacts. What is it ?
  (nachiket331, 17:36:00)
* ACTION: we will look at an approach to hook persistence into MD-SAL
  framework before API freeze  (nachiket331, 17:40:56)
* ACTION: fabiel will follow up with Uyen to see where the common API
  should be placed ? Two possibilities are persistence or yang-tools
  (nachiket331, 17:45:08)
* ACTION: common can also be in controller itself  (nachiket331,
  17:45:29)
* ACTION: fabiel will update the release plan to update Expected
  dependencies on Other projects. Dependencies are ODL parent,
  controller and yang-tools as of now  (nachiket331, 17:47:50)
* the serialization project proposal that uses SQLite persistence is an
  incompatibility.  (nachiket331, 17:49:16)
* ACTION: we should try to work with serialization project folks and get
  them onboard  (nachiket331, 17:50:08)
* ACTION: we need to work with yang-tools project to get support on
  Identifiable interface definition for Persisted objects  (nachiket331,
  17:51:08)
* No questions  (nachiket331, 17:51:59)
* ACTION: fabiel will update the wiki to accept questions before the
  meeting and also a notes of the meeting  (nachiket331, 17:53:18)



Meeting ended at 17:53:37 UTC.



Action items, by person
-----------------------

* fabiel
  * fabiel will upload the persistence release plan to lithium release
    plan for review
  * fabiel or nachiket331 we need to investigate more on how system
    testing and CI is done for persistence. Is it Robot ? we create a
    test app using SQL lite for CI for now ?
  * fabiel will follow up with Uyen to see where the common API should
    be placed ? Two possibilities are persistence or yang-tools
  * fabiel will update the release plan to update Expected dependencies
    on Other projects. Dependencies are ODL parent, controller and
    yang-tools as of now
  * fabiel will update the wiki to accept questions before the meeting
    and also a notes of the meeting
* nachiket331
  * fabiel or nachiket331 we need to investigate more on how system
    testing and CI is done for persistence. Is it Robot ? we create a
    test app using SQL lite for CI for now ?
* **UNASSIGNED**
  * we need to investigate what applications will use the database ? Can
    they come with their own database as part of their plugin and
    install the relevant service without having to restart the
    controller ?
  * update the JPA support section saying we will ship with SQLite DB by
    default
  * investigate Nexus Repository Binary artifacts. What is it ?
  * we will look at an approach to hook persistence into MD-SAL
    framework before API freeze
  * common can also be in controller itself
  * we should try to work with serialization project folks and get them
    onboard
  * we need to work with yang-tools project to get support on
    Identifiable interface definition for Persisted objects



People present (lines said)
---------------------------

* nachiket331 (34)
* odl_meetbot (3)
* fabiel (2)



Generated by `MeetBot`_ 0.1.4