Thursday, 2018-07-12

*** sajuptpm has joined #edge-computing-group00:05
*** sajuptpm has quit IRC00:05
*** dpaterson has joined #edge-computing-group00:14
*** sajuptpm has joined #edge-computing-group00:17
*** sajuptpm has quit IRC00:17
*** sajuptpm has joined #edge-computing-group00:33
*** sajuptpm has quit IRC00:33
*** sajuptpm has joined #edge-computing-group00:49
*** sajuptpm has quit IRC00:51
*** dpaterson has quit IRC00:59
*** sajuptpm has joined #edge-computing-group01:01
*** sajuptpm has quit IRC01:01
*** dpaterson has joined #edge-computing-group01:03
*** sajuptpm has joined #edge-computing-group01:08
*** sajuptpm has quit IRC01:08
*** sajuptpm has joined #edge-computing-group01:53
*** sajuptpm has quit IRC01:53
*** sajuptpm has joined #edge-computing-group02:04
*** sajuptpm has quit IRC02:05
*** sajuptpm has joined #edge-computing-group02:21
*** sajuptpm has quit IRC02:22
*** sajuptpm has joined #edge-computing-group02:33
*** sajuptpm has quit IRC02:33
*** dpaterson has quit IRC02:59
*** sajuptpm has joined #edge-computing-group03:53
*** sajuptpm has quit IRC03:54
*** sajuptpm has joined #edge-computing-group04:44
*** sajuptpm has quit IRC04:45
*** sajuptpm has joined #edge-computing-group04:56
*** sajuptpm has quit IRC04:56
*** sajuptpm has joined #edge-computing-group05:12
*** sajuptpm has quit IRC05:13
*** trevor_intel has joined #edge-computing-group05:13
*** sajuptpm has joined #edge-computing-group05:24
*** sajuptpm has quit IRC05:24
*** sajuptpm has joined #edge-computing-group05:40
*** sajuptpm has quit IRC05:41
*** sajuptpm has joined #edge-computing-group05:52
*** sajuptpm has quit IRC05:52
*** trevor_intel has quit IRC05:59
*** jesslampe has joined #edge-computing-group06:19
*** sajuptpm has joined #edge-computing-group06:37
*** sajuptpm has quit IRC06:37
*** jesslampe has quit IRC06:43
*** sajuptpm has joined #edge-computing-group06:53
*** sajuptpm has quit IRC06:54
*** epalper has joined #edge-computing-group07:05
*** sajuptpm has joined #edge-computing-group07:30
*** sajuptpm has quit IRC07:39
*** sajuptpm has joined #edge-computing-group07:57
*** sajuptpm has quit IRC11:37
*** sajuptpm has joined #edge-computing-group11:42
*** sajuptpm_ has joined #edge-computing-group11:43
*** sajuptpm has quit IRC11:47
*** rosmaita has joined #edge-computing-group11:53
*** trevor_intel has joined #edge-computing-group13:08
*** dpaterson has joined #edge-computing-group13:13
*** wangzhh has joined #edge-computing-group13:48
*** esarault has joined #edge-computing-group14:00
dpatersono/14:01
csatariHi14:02
csatari#startmeeting review_of_dublin_edge_notes14:02
openstackMeeting started Thu Jul 12 14:02:17 2018 UTC and is due to finish in 60 minutes.  The chair is csatari. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: review_of_dublin_edge_notes)"14:02
openstackThe meeting name has been set to 'review_of_dublin_edge_notes'14:02
*** jesslampe has joined #edge-computing-group14:02
csatari#topic Roll Call14:02
*** openstack changes topic to "Roll Call (Meeting topic: review_of_dublin_edge_notes)"14:02
dpatersonhere14:02
csatari#info Gergely Csatari14:02
esarault#info Eric Sarault14:03
dpaterson#info David Paterson14:03
csatari#topic Action items14:04
*** openstack changes topic to "Action items (Meeting topic: review_of_dublin_edge_notes)"14:04
*** jesslampe has quit IRC14:04
csatari#link https://etherpad.openstack.org/p/Dublin-edge-notes-wiki14:05
csatariI had no time to work on them this week.14:05
csatariNext week will be better :)14:05
csatari#info No progress14:05
esaraultDon'T be too harsh on yourself ;)14:05
csatariI'm doing my best :)14:06
csatariOkay, lets jump to the review part.14:06
csatari#topic Review of 5.3.2.10 Flavors source side14:06
*** openstack changes topic to "Review of 5.3.2.10 Flavors source side (Meeting topic: review_of_dublin_edge_notes)"14:06
csatari#link https://wiki.openstack.org/w/index.php?title=OpenStack_Edge_Discussions_Dublin_PTG#Flavors_source_side14:07
esaraultNothing to add14:08
csatariIf no comments lets move forward (I already have an action to generalize the synch service)14:08
csatari#topic Review of 5.3.2.11 Flavors receiver side14:08
*** openstack changes topic to "Review of 5.3.2.11 Flavors receiver side (Meeting topic: review_of_dublin_edge_notes)"14:08
csatari#link https://wiki.openstack.org/w/index.php?title=OpenStack_Edge_Discussions_Dublin_PTG#Flavors_receiver_side14:09
csatariMoving on14:10
csatari#topic Review of 5.3.2.12 Projects source side14:10
*** openstack changes topic to "Review of 5.3.2.12 Projects source side (Meeting topic: review_of_dublin_edge_notes)"14:10
csatari#link https://wiki.openstack.org/w/index.php?title=OpenStack_Edge_Discussions_Dublin_PTG#Projects_source_side14:10
csatariHere I talk about Quotas sometime.14:10
csatariThat should be changed to Project.14:11
csatari#action (5.3.2.12) Change Quotas to Projects.14:11
csatariCan we have some inconsistency when projects are copied?14:13
csatariMost probably not, but I will check what data is stored in a project.14:14
dpatersonSorry but when you say copy project are you referring to Keystone Federation creating shadow projects and users?14:15
csatari#action (5.3.2.12) Check if the data in a project can be inconsistent during the synchronisation (e.g.: if there are uuid-s there which are valid only olcally)14:15
csatariNo, in this case there is a separate synchronisastion service doing the creation of projects and users.14:17
csatariAnd yes, I think we should describe the Keystone federation case also.14:17
csatariHowever these two alre alternatives on some level.14:17
dpaterson#link https://wiki.openstack.org/wiki/Keystone_edge_architectures#Several_keystone_instances_with_federation_and_API_synchronsation14:18
dpatersoncsatari: that's the topic?14:19
csatariyes14:19
csatariWhat is described in the Dublin edge notes is "2.4 Keystone API Synchronization & Fernet Key Synchronization" without the fernet keys.14:20
csatariAnd the question is if we should also describe "2.1 Several keystone instances with federation and API synchronsation" as an alternative approach.14:21
csatariOr totally replace the API Synchronisation way.14:21
dpatersoncsatari: looking, I was in Dublin but not in Edge track until just recently14:22
csatariIn my personal opinion there will be no single option selected for these different issues, so the best would be to describe both of these alternatives in the wiki.14:23
csatariWe can always delete if an idea turns out to be non working.14:23
csatari#action Add Requirements for the "2.1 Several keystone instances with federation and API synchronsation" option from https://wiki.openstack.org/wiki/Keystone_edge_architectures#Several_keystone_instances_with_federation_and_API_synchronsation14:26
csatariThis ^^^ will affect all Keystone metadata related requirements. My plan is to describe a separate set of requirements for both of these options.14:28
dpatersoncsatari: The Keyston sycronization service you are calling out is referring to the starlingx syncronization serivce correct?14:28
csatariStarlingX synsh service is one implementation of it.14:28
csatariWhen we defined it we did not know that WindRiver implemented it and we did not know that it will be open sourced under the name StarlingX.14:29
csatariWe wanted to develop Kingbird further or start a new project to do this.14:30
csatariStarlingX synch service is also based on Kingbird by the way.14:30
dpaterson#csatari: From Monday's Edge meeting it looks like starlingx syncronization service is pretty dependent on starlingx specific bits14:30
csatariYes.14:30
dpaterson#csatari: and kingbird looks pretty inactive14:30
csatariYes.14:31
csatariBut I would not like to drop the idea of an independent synch service.14:32
dpatersoncsatari:  This might sound old school but was using distributed LDAP discussed as a viable model?14:32
csatariNo it was not discussed.14:32
csatariIn some meeting Keysone people stated that LDAP is not an IDP, but something else.14:32
csatariThis is all what I remember :)14:33
dpatersoncsatari: with LDAP master/replicas you would get eventual consistancy for free14:33
dpatersonSo instead of keystone database for auth realm use ldap (apache directory or openldap)14:33
csatariAnd can Keystone use LDAP as a backend database?14:34
dpatersonYes14:34
dpatersonalways been supported14:34
dpatersonas far as I know14:34
csatariAnd can we synch all needed Keystone data with this method?14:35
dpatersoncsatari: could solve a lot of the discussion points without the need of an external syncronization service.14:36
dpatersonThat I am not sure about14:36
*** mugsie has quit IRC14:36
*** mugsie has joined #edge-computing-group14:36
*** mugsie has quit IRC14:36
*** mugsie has joined #edge-computing-group14:36
csatariOkay. Let's add it to the Keystone alternatives list and start a discussion on the mailing lists.14:37
dpatersonI will take an AI to see what support there is, if it's auth only or if Projects/ACL/RBAC are part of ldap schema or does that data still have to live in relational database14:37
dpatersonIt may allow auth only and depend on keystone database for everything else, not sure.14:38
csatari#action Add an alternative to the Keystone alternatives wiki for Keystone with distributed LDAP backend.14:38
csatariOkay, thanks.14:38
csatari#action dpaterson to check what support there is, if it's auth only or if Projects/ACL/RBAC are part of ldap schema or does that data still have to live in relational database14:38
csatari#action Start a mail discussion about the Keystone with distributed LDAP backend alternative14:39
dpatersoncsatari: and under Keystone database replication, is this specifically Galera? Do we want to call out specific relational database distros that might work?14:39
csatariThe description is technology agnostic, but if we can add in a note database distros what can actually do the work that is usefull information.14:40
dpaterson#link https://www.researchgate.net/publication/4284466_Enhancing_Edge_Computing_with_Database_Replication14:43
dpatersonfrom 200714:43
csatari:)14:44
csatari#topic Review of 5.3.2.13 Projects receiver side14:45
*** openstack changes topic to "Review of 5.3.2.13 Projects receiver side (Meeting topic: review_of_dublin_edge_notes)"14:45
csatari#link https://wiki.openstack.org/w/index.php?title=OpenStack_Edge_Discussions_Dublin_PTG#Projects_receiver_side14:46
csatariMoving on.14:49
csatari#topic Review of 5.3.2.14 Quotas source side14:49
*** openstack changes topic to "Review of 5.3.2.14 Quotas source side (Meeting topic: review_of_dublin_edge_notes)"14:49
dpatersoncsatari: an issue with syncronization service vai API is that it needs to be in lockstep with any schema changes14:49
csatari#link https://wiki.openstack.org/w/index.php?title=OpenStack_Edge_Discussions_Dublin_PTG#Quotas_source_side14:49
csatariWith API changes not (db) schema changes.14:50
dpatersonYes, you are right14:50
csatarithe issue with db synchronisation is that it should clockstep db schema changes.14:50
csatariAn independent syncronisation service can support several versions of API-s.14:51
dpatersonyup14:51
csatariEven several VIM-s, but let's not go that far now.14:51
csatariOkay, lets start the wrapup.14:52
csatari#topic Wrapup14:53
*** openstack changes topic to "Wrapup (Meeting topic: review_of_dublin_edge_notes)"14:53
csatari#info Next Thursday we will have the Keystone testing meeting in the same time as this meeting, so we will skip the review.14:53
csatari#info Next meeting is 26.07.2018 16 CET14:54
csatari#info We will contiue from 3.2.15 Quotas receiver side14:54
csatari#info I try to organize a meeting to discuss about https://wiki.openstack.org/wiki/Image_handling_in_edge_environment but that will be in a different timeslot than this one as we are parallel to the Glance meeing and I would like to invite Glance experts.14:56
csatariThat is it for today.14:56
csatariHave a nice day.14:56
csatari#endmeeting14:56
*** openstack changes topic to "Finishing up (Meeting topic: Review of Dublin edge notes II)"14:56
dpatersonyou too14:56
openstackMeeting ended Thu Jul 12 14:56:26 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes/2018/review_of_dublin_edge_notes.2018-07-12-14.02.html14:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes/2018/review_of_dublin_edge_notes.2018-07-12-14.02.txt14:56
openstackLog:            http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes/2018/review_of_dublin_edge_notes.2018-07-12-14.02.log.html14:56
csatariThanks for the discussion.14:56
dpatersoncsatari; thank you!14:56
*** jesslampe has joined #edge-computing-group14:57
*** esarault has quit IRC15:00
*** jesslampe has quit IRC15:02
*** jesslampe has joined #edge-computing-group15:02
*** sajuptpm_ has quit IRC15:25
*** jesslampe has quit IRC15:37
*** sajuptpm has joined #edge-computing-group15:44
*** sajuptpm has quit IRC15:52
*** sajuptpm has joined #edge-computing-group16:12
*** sajuptpm has quit IRC16:41
*** sajuptpm has joined #edge-computing-group17:22
*** sajuptpm has quit IRC17:22
*** rosmaita has quit IRC17:33
*** epalper has quit IRC17:38
*** rosmaita has joined #edge-computing-group17:43
*** epalper has joined #edge-computing-group18:27
*** epalper has quit IRC18:28
*** sajuptpm has joined #edge-computing-group18:56
*** sajuptpm has quit IRC18:56
*** sajuptpm has joined #edge-computing-group19:12
*** sajuptpm has quit IRC19:13
*** sajuptpm has joined #edge-computing-group19:24
*** sajuptpm has quit IRC19:24
*** trevor_intel has quit IRC19:32
*** sajuptpm has joined #edge-computing-group19:40
*** sajuptpm has quit IRC19:41
*** sajuptpm has joined #edge-computing-group19:48
*** sajuptpm has quit IRC19:48
*** trevor_intel has joined #edge-computing-group20:05
*** sajuptpm has joined #edge-computing-group20:25
*** sajuptpm has quit IRC20:25
*** dpaterson has quit IRC20:30
*** sajuptpm has joined #edge-computing-group20:36
*** sajuptpm has quit IRC20:37
*** sajuptpm has joined #edge-computing-group20:48
*** sajuptpm has quit IRC20:48
*** sajuptpm has joined #edge-computing-group20:53
*** sajuptpm has quit IRC20:53
*** sajuptpm has joined #edge-computing-group21:15
*** sajuptpm has quit IRC21:16
*** sajuptpm has joined #edge-computing-group21:27
*** sajuptpm has quit IRC21:27
*** sajuptpm has joined #edge-computing-group21:33
*** sajuptpm has quit IRC21:33
*** sajuptpm has joined #edge-computing-group21:49
*** sajuptpm has quit IRC21:50
*** sajuptpm has joined #edge-computing-group22:01
*** sajuptpm has quit IRC22:01
*** sajuptpm has joined #edge-computing-group22:07
*** sajuptpm has quit IRC22:07
*** sajuptpm has joined #edge-computing-group22:23
*** sajuptpm has quit IRC22:25
*** sajuptpm has joined #edge-computing-group22:35
*** sajuptpm has quit IRC22:35
*** sajuptpm has joined #edge-computing-group22:41
*** sajuptpm has quit IRC22:41
*** rosmaita has quit IRC22:59
*** markvoelker has quit IRC23:59

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!