*** sajuptpm has joined #edge-computing-group | 00:05 | |
*** sajuptpm has quit IRC | 00:05 | |
*** dpaterson has joined #edge-computing-group | 00:14 | |
*** sajuptpm has joined #edge-computing-group | 00:17 | |
*** sajuptpm has quit IRC | 00:17 | |
*** sajuptpm has joined #edge-computing-group | 00:33 | |
*** sajuptpm has quit IRC | 00:33 | |
*** sajuptpm has joined #edge-computing-group | 00:49 | |
*** sajuptpm has quit IRC | 00:51 | |
*** dpaterson has quit IRC | 00:59 | |
*** sajuptpm has joined #edge-computing-group | 01:01 | |
*** sajuptpm has quit IRC | 01:01 | |
*** dpaterson has joined #edge-computing-group | 01:03 | |
*** sajuptpm has joined #edge-computing-group | 01:08 | |
*** sajuptpm has quit IRC | 01:08 | |
*** sajuptpm has joined #edge-computing-group | 01:53 | |
*** sajuptpm has quit IRC | 01:53 | |
*** sajuptpm has joined #edge-computing-group | 02:04 | |
*** sajuptpm has quit IRC | 02:05 | |
*** sajuptpm has joined #edge-computing-group | 02:21 | |
*** sajuptpm has quit IRC | 02:22 | |
*** sajuptpm has joined #edge-computing-group | 02:33 | |
*** sajuptpm has quit IRC | 02:33 | |
*** dpaterson has quit IRC | 02:59 | |
*** sajuptpm has joined #edge-computing-group | 03:53 | |
*** sajuptpm has quit IRC | 03:54 | |
*** sajuptpm has joined #edge-computing-group | 04:44 | |
*** sajuptpm has quit IRC | 04:45 | |
*** sajuptpm has joined #edge-computing-group | 04:56 | |
*** sajuptpm has quit IRC | 04:56 | |
*** sajuptpm has joined #edge-computing-group | 05:12 | |
*** sajuptpm has quit IRC | 05:13 | |
*** trevor_intel has joined #edge-computing-group | 05:13 | |
*** sajuptpm has joined #edge-computing-group | 05:24 | |
*** sajuptpm has quit IRC | 05:24 | |
*** sajuptpm has joined #edge-computing-group | 05:40 | |
*** sajuptpm has quit IRC | 05:41 | |
*** sajuptpm has joined #edge-computing-group | 05:52 | |
*** sajuptpm has quit IRC | 05:52 | |
*** trevor_intel has quit IRC | 05:59 | |
*** jesslampe has joined #edge-computing-group | 06:19 | |
*** sajuptpm has joined #edge-computing-group | 06:37 | |
*** sajuptpm has quit IRC | 06:37 | |
*** jesslampe has quit IRC | 06:43 | |
*** sajuptpm has joined #edge-computing-group | 06:53 | |
*** sajuptpm has quit IRC | 06:54 | |
*** epalper has joined #edge-computing-group | 07:05 | |
*** sajuptpm has joined #edge-computing-group | 07:30 | |
*** sajuptpm has quit IRC | 07:39 | |
*** sajuptpm has joined #edge-computing-group | 07:57 | |
*** sajuptpm has quit IRC | 11:37 | |
*** sajuptpm has joined #edge-computing-group | 11:42 | |
*** sajuptpm_ has joined #edge-computing-group | 11:43 | |
*** sajuptpm has quit IRC | 11:47 | |
*** rosmaita has joined #edge-computing-group | 11:53 | |
*** trevor_intel has joined #edge-computing-group | 13:08 | |
*** dpaterson has joined #edge-computing-group | 13:13 | |
*** wangzhh has joined #edge-computing-group | 13:48 | |
*** esarault has joined #edge-computing-group | 14:00 | |
dpaterson | o/ | 14:01 |
---|---|---|
csatari | Hi | 14:02 |
csatari | #startmeeting review_of_dublin_edge_notes | 14:02 |
openstack | Meeting 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:02 |
*** openstack changes topic to " (Meeting topic: review_of_dublin_edge_notes)" | 14:02 | |
openstack | The meeting name has been set to 'review_of_dublin_edge_notes' | 14:02 |
*** jesslampe has joined #edge-computing-group | 14:02 | |
csatari | #topic Roll Call | 14:02 |
*** openstack changes topic to "Roll Call (Meeting topic: review_of_dublin_edge_notes)" | 14:02 | |
dpaterson | here | 14:02 |
csatari | #info Gergely Csatari | 14:02 |
esarault | #info Eric Sarault | 14:03 |
dpaterson | #info David Paterson | 14:03 |
csatari | #topic Action items | 14:04 |
*** openstack changes topic to "Action items (Meeting topic: review_of_dublin_edge_notes)" | 14:04 | |
*** jesslampe has quit IRC | 14:04 | |
csatari | #link https://etherpad.openstack.org/p/Dublin-edge-notes-wiki | 14:05 |
csatari | I had no time to work on them this week. | 14:05 |
csatari | Next week will be better :) | 14:05 |
csatari | #info No progress | 14:05 |
esarault | Don'T be too harsh on yourself ;) | 14:05 |
csatari | I'm doing my best :) | 14:06 |
csatari | Okay, lets jump to the review part. | 14:06 |
csatari | #topic Review of 5.3.2.10 Flavors source side | 14: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_side | 14:07 |
esarault | Nothing to add | 14:08 |
csatari | If 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 side | 14: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_side | 14:09 |
csatari | Moving on | 14:10 |
csatari | #topic Review of 5.3.2.12 Projects source side | 14: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_side | 14:10 |
csatari | Here I talk about Quotas sometime. | 14:10 |
csatari | That should be changed to Project. | 14:11 |
csatari | #action (5.3.2.12) Change Quotas to Projects. | 14:11 |
csatari | Can we have some inconsistency when projects are copied? | 14:13 |
csatari | Most probably not, but I will check what data is stored in a project. | 14:14 |
dpaterson | Sorry 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 |
csatari | No, in this case there is a separate synchronisastion service doing the creation of projects and users. | 14:17 |
csatari | And yes, I think we should describe the Keystone federation case also. | 14:17 |
csatari | However 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_synchronsation | 14:18 |
dpaterson | csatari: that's the topic? | 14:19 |
csatari | yes | 14:19 |
csatari | What is described in the Dublin edge notes is "2.4 Keystone API Synchronization & Fernet Key Synchronization" without the fernet keys. | 14:20 |
csatari | And the question is if we should also describe "2.1 Several keystone instances with federation and API synchronsation" as an alternative approach. | 14:21 |
csatari | Or totally replace the API Synchronisation way. | 14:21 |
dpaterson | csatari: looking, I was in Dublin but not in Edge track until just recently | 14:22 |
csatari | In 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 |
csatari | We 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_synchronsation | 14:26 |
csatari | This ^^^ will affect all Keystone metadata related requirements. My plan is to describe a separate set of requirements for both of these options. | 14:28 |
dpaterson | csatari: The Keyston sycronization service you are calling out is referring to the starlingx syncronization serivce correct? | 14:28 |
csatari | StarlingX synsh service is one implementation of it. | 14:28 |
csatari | When 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 |
csatari | We wanted to develop Kingbird further or start a new project to do this. | 14:30 |
csatari | StarlingX 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 bits | 14:30 |
csatari | Yes. | 14:30 |
dpaterson | #csatari: and kingbird looks pretty inactive | 14:30 |
csatari | Yes. | 14:31 |
csatari | But I would not like to drop the idea of an independent synch service. | 14:32 |
dpaterson | csatari: This might sound old school but was using distributed LDAP discussed as a viable model? | 14:32 |
csatari | No it was not discussed. | 14:32 |
csatari | In some meeting Keysone people stated that LDAP is not an IDP, but something else. | 14:32 |
csatari | This is all what I remember :) | 14:33 |
dpaterson | csatari: with LDAP master/replicas you would get eventual consistancy for free | 14:33 |
dpaterson | So instead of keystone database for auth realm use ldap (apache directory or openldap) | 14:33 |
csatari | And can Keystone use LDAP as a backend database? | 14:34 |
dpaterson | Yes | 14:34 |
dpaterson | always been supported | 14:34 |
dpaterson | as far as I know | 14:34 |
csatari | And can we synch all needed Keystone data with this method? | 14:35 |
dpaterson | csatari: could solve a lot of the discussion points without the need of an external syncronization service. | 14:36 |
dpaterson | That I am not sure about | 14:36 |
*** mugsie has quit IRC | 14:36 | |
*** mugsie has joined #edge-computing-group | 14:36 | |
*** mugsie has quit IRC | 14:36 | |
*** mugsie has joined #edge-computing-group | 14:36 | |
csatari | Okay. Let's add it to the Keystone alternatives list and start a discussion on the mailing lists. | 14:37 |
dpaterson | I 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 database | 14:37 |
dpaterson | It 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 |
csatari | Okay, 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 database | 14:38 |
csatari | #action Start a mail discussion about the Keystone with distributed LDAP backend alternative | 14:39 |
dpaterson | csatari: and under Keystone database replication, is this specifically Galera? Do we want to call out specific relational database distros that might work? | 14:39 |
csatari | The 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_Replication | 14:43 |
dpaterson | from 2007 | 14:43 |
csatari | :) | 14:44 |
csatari | #topic Review of 5.3.2.13 Projects receiver side | 14: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_side | 14:46 |
csatari | Moving on. | 14:49 |
csatari | #topic Review of 5.3.2.14 Quotas source side | 14:49 |
*** openstack changes topic to "Review of 5.3.2.14 Quotas source side (Meeting topic: review_of_dublin_edge_notes)" | 14:49 | |
dpaterson | csatari: an issue with syncronization service vai API is that it needs to be in lockstep with any schema changes | 14:49 |
csatari | #link https://wiki.openstack.org/w/index.php?title=OpenStack_Edge_Discussions_Dublin_PTG#Quotas_source_side | 14:49 |
csatari | With API changes not (db) schema changes. | 14:50 |
dpaterson | Yes, you are right | 14:50 |
csatari | the issue with db synchronisation is that it should clockstep db schema changes. | 14:50 |
csatari | An independent syncronisation service can support several versions of API-s. | 14:51 |
dpaterson | yup | 14:51 |
csatari | Even several VIM-s, but let's not go that far now. | 14:51 |
csatari | Okay, lets start the wrapup. | 14:52 |
csatari | #topic Wrapup | 14: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 CET | 14:54 |
csatari | #info We will contiue from 3.2.15 Quotas receiver side | 14: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 |
csatari | That is it for today. | 14:56 |
csatari | Have a nice day. | 14:56 |
csatari | #endmeeting | 14:56 |
*** openstack changes topic to "Finishing up (Meeting topic: Review of Dublin edge notes II)" | 14:56 | |
dpaterson | you too | 14:56 |
openstack | Meeting ended Thu Jul 12 14:56:26 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:56 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes/2018/review_of_dublin_edge_notes.2018-07-12-14.02.html | 14:56 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes/2018/review_of_dublin_edge_notes.2018-07-12-14.02.txt | 14:56 |
openstack | Log: http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes/2018/review_of_dublin_edge_notes.2018-07-12-14.02.log.html | 14:56 |
csatari | Thanks for the discussion. | 14:56 |
dpaterson | csatari; thank you! | 14:56 |
*** jesslampe has joined #edge-computing-group | 14:57 | |
*** esarault has quit IRC | 15:00 | |
*** jesslampe has quit IRC | 15:02 | |
*** jesslampe has joined #edge-computing-group | 15:02 | |
*** sajuptpm_ has quit IRC | 15:25 | |
*** jesslampe has quit IRC | 15:37 | |
*** sajuptpm has joined #edge-computing-group | 15:44 | |
*** sajuptpm has quit IRC | 15:52 | |
*** sajuptpm has joined #edge-computing-group | 16:12 | |
*** sajuptpm has quit IRC | 16:41 | |
*** sajuptpm has joined #edge-computing-group | 17:22 | |
*** sajuptpm has quit IRC | 17:22 | |
*** rosmaita has quit IRC | 17:33 | |
*** epalper has quit IRC | 17:38 | |
*** rosmaita has joined #edge-computing-group | 17:43 | |
*** epalper has joined #edge-computing-group | 18:27 | |
*** epalper has quit IRC | 18:28 | |
*** sajuptpm has joined #edge-computing-group | 18:56 | |
*** sajuptpm has quit IRC | 18:56 | |
*** sajuptpm has joined #edge-computing-group | 19:12 | |
*** sajuptpm has quit IRC | 19:13 | |
*** sajuptpm has joined #edge-computing-group | 19:24 | |
*** sajuptpm has quit IRC | 19:24 | |
*** trevor_intel has quit IRC | 19:32 | |
*** sajuptpm has joined #edge-computing-group | 19:40 | |
*** sajuptpm has quit IRC | 19:41 | |
*** sajuptpm has joined #edge-computing-group | 19:48 | |
*** sajuptpm has quit IRC | 19:48 | |
*** trevor_intel has joined #edge-computing-group | 20:05 | |
*** sajuptpm has joined #edge-computing-group | 20:25 | |
*** sajuptpm has quit IRC | 20:25 | |
*** dpaterson has quit IRC | 20:30 | |
*** sajuptpm has joined #edge-computing-group | 20:36 | |
*** sajuptpm has quit IRC | 20:37 | |
*** sajuptpm has joined #edge-computing-group | 20:48 | |
*** sajuptpm has quit IRC | 20:48 | |
*** sajuptpm has joined #edge-computing-group | 20:53 | |
*** sajuptpm has quit IRC | 20:53 | |
*** sajuptpm has joined #edge-computing-group | 21:15 | |
*** sajuptpm has quit IRC | 21:16 | |
*** sajuptpm has joined #edge-computing-group | 21:27 | |
*** sajuptpm has quit IRC | 21:27 | |
*** sajuptpm has joined #edge-computing-group | 21:33 | |
*** sajuptpm has quit IRC | 21:33 | |
*** sajuptpm has joined #edge-computing-group | 21:49 | |
*** sajuptpm has quit IRC | 21:50 | |
*** sajuptpm has joined #edge-computing-group | 22:01 | |
*** sajuptpm has quit IRC | 22:01 | |
*** sajuptpm has joined #edge-computing-group | 22:07 | |
*** sajuptpm has quit IRC | 22:07 | |
*** sajuptpm has joined #edge-computing-group | 22:23 | |
*** sajuptpm has quit IRC | 22:25 | |
*** sajuptpm has joined #edge-computing-group | 22:35 | |
*** sajuptpm has quit IRC | 22:35 | |
*** sajuptpm has joined #edge-computing-group | 22:41 | |
*** sajuptpm has quit IRC | 22:41 | |
*** rosmaita has quit IRC | 22:59 | |
*** markvoelker has quit IRC | 23:59 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!