=====================================
#opendaylight-meeting: simplifyingodl
=====================================


Meeting started by dfarrell07 at 16:04:14 UTC.  The full logs are
available at
http://meetings.opendaylight.org/opendaylight-meeting/2018/simplifyingodl/opendaylight-meeting-simplifyingodl.2018-12-13-16.04.log.html
.



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

* LINK: https://zoom.us/j/664690256  (dfarrell07, 16:05:09)
* LINK:
  https://docs.google.com/document/d/1-MaazB2rGQt_Ci9tMH8G6GNYfcFsJ9bMmCSsLHRwsqU
  (dfarrell07, 16:09:33)
* going through existing doc, linked above  (dfarrell07, 16:11:56)
* jiraj has done his homework, has some extra slides/ideas to talk
  through  (dfarrell07, 16:12:16)
* LINK: https://www.youtube.com/watch?v=nr5nFfWIqhQ  (tbachman,
  16:12:54)
* jiraj talks through example of how Java EE reasoned themselves through
  similar challenges  (dfarrell07, 16:14:34)
* one step to start would be to identify key services, start thinking of
  as microservices  (dfarrell07, 16:15:57)
* there are about 33 services jiraj id'd as being critical to their
  Lightly usage  (dfarrell07, 16:16:14)
* nice slide showing services in netvirt and how they might be grouped
  into microservices  (dfarrell07, 16:17:15)
* would be not so hard with stateless services, but some extra
  considerations for stateful services  (dfarrell07, 16:18:35)
* analysis of netvirt shows that it's not reasonable to break down to
  one bundle per microservice  (dfarrell07, 16:20:50)
* tomp talks about cross-ties between services that also require some
  grouping  (dfarrell07, 16:21:43)
* also need lots of consideration about what the logical chunk of work a
  microserv would handle - what are responsibilities, what does provide
  (dfarrell07, 16:23:27)
* also need to consider what wires will consist of between microservs
  (dfarrell07, 16:24:07)
* options for wires are things like rest, grpc, rabbitmq, kafka, etc
  (dfarrell07, 16:24:35)
* ODL <3's tbachman ;*  (dfarrell07, 16:25:25)
* discussion about when things are broken apart, will need to consider
  if will use existing APIs or build new ones  (dfarrell07, 16:27:21)
* perhaps obviously, need to make sure chunks of microservs are logical
  chunks that make sense to folks  (dfarrell07, 16:29:58)
* discussion about memory spaces, how data store would work if not
  shared  (dfarrell07, 16:32:23)
* juraj says would likely need to include mdsal in all microservs to
  start with  (dfarrell07, 16:33:03)
* tomp says the data store APIs would need some sort of implementation
  locally, even if fake, but need something to make the APIs work
  (dfarrell07, 16:34:01)
* LuisGomez reminds us that jsonrcp project might be useful for this
  distributed data question  (dfarrell07, 16:36:12)
* vorburger points out that it would of course be nice just not to have
  shared state, LuisGomez agrees  (dfarrell07, 16:37:34)
* could have one microserv that has config data store that many
  microservs could access, and not bother with operational data in each
  microserv, there but not HAish  (dfarrell07, 16:41:02)
* tomp points out that some of these microservs will be HA  (dfarrell07,
  16:41:29)
* some microservs could just be recreated if die, but others might need
  active HAish  (dfarrell07, 16:42:23)
* using an etcd back mdsal would of course also be an option, in
  particular in k8s, see vorburgers work here  (dfarrell07, 16:44:16)
* vorburger's current poc is looking like should be able to make hidden
  to services on top  (dfarrell07, 16:44:57)
* lumina has learned some hard lessons about using ha data store vs
  external data store; also that it's painful to support both; also that
  it would be great if we could all work on some same solution upstream
  (dfarrell07, 16:47:08)
* lots of discussion about not needing to replicate/protect nearly as
  much data as we do today, operational data generated by microservs for
  internal use for example  (dfarrell07, 16:50:23)
* but also need to consider how a microserv would get operational data
  if a pervious version of it died - how would it get back to having the
  same opp data; hot stand-by is one option; replaying data is one we do
  in some contexts today  (dfarrell07, 16:52:14)
* tomp likes eventual consistency with cold standbys, if can make
  application work that way  (dfarrell07, 16:53:48)
* other apps may have different HA needs  (dfarrell07, 16:56:15)
* need to choose one application to use as first, poc; would very likely
  choose netvirt because lots of activity, interest  (dfarrell07,
  16:56:38)
* but eventually solution needs to apply to all of ODL, all
  companies/usages if at all possible  (dfarrell07, 16:56:57)
* Quan  (XiongQuan, 17:00:01)



Meeting ended at 17:00:09 UTC.



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

* dfarrell07 (46)
* tbachman (14)
* odl_meetbot (5)
* abhijitk (4)
* vpickard (2)
* XiongQuan (1)
* jamoluhrsen (1)
* vthapar (0)
* skitt (0)
* vorburger (0)
* faseelak (0)
* premsankar (0)
* anipbu (0)
* rovarga_ (0)



Generated by `MeetBot`_ 0.1.4