Thursday, 2018-06-28

*** jesslampe has joined #edge-computing-group01:11
*** jesslampe has quit IRC01:22
*** jesslampe has joined #edge-computing-group01:25
*** jesslampe has quit IRC01:26
*** jesslampe has joined #edge-computing-group05:35
*** openstackstatus has quit IRC05:51
*** openstackstatus has joined #edge-computing-group05:51
*** ChanServ sets mode: +v openstackstatus05:51
*** epalper has joined #edge-computing-group06:49
*** jesslampe has quit IRC07:59
*** jesslampe has joined #edge-computing-group07:59
*** jesslampe has quit IRC08:04
*** cdent has joined #edge-computing-group09:42
*** jroll has joined #edge-computing-group11:56
*** rosmaita has joined #edge-computing-group12:13
*** cdent has quit IRC12:18
*** rosmaita has quit IRC12:21
*** vrv_ has joined #edge-computing-group12:26
*** rosmaita has joined #edge-computing-group12:29
*** cdent has joined #edge-computing-group12:34
*** cdent has quit IRC13:46
csatariHi all.14:00
*** Arkady_Kanevsky has joined #edge-computing-group14:01
Arkady_Kanevskyhello14:01
csatari#startmeeting review_of_dublin_edge_notes14:01
openstackMeeting started Thu Jun 28 14:01: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:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: review_of_dublin_edge_notes)"14:01
*** rlpple has joined #edge-computing-group14:01
openstackThe meeting name has been set to 'review_of_dublin_edge_notes'14:01
csatari#topic Roll Call14:01
*** openstack changes topic to "Roll Call (Meeting topic: review_of_dublin_edge_notes)"14:01
csatari#info Gergely Csatari14:01
Arkady_Kanevskyhello again14:02
*** rlpple has quit IRC14:02
csatari#link https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG14:02
*** rlpple has joined #edge-computing-group14:02
Arkady_Kanevskyi will have to drop in 15 min14:02
csatariHah, better to hurry , then :)14:03
Arkady_Kanevsky+114:03
csatari#topic Housekeeping14:03
*** openstack changes topic to "Housekeeping (Meeting topic: review_of_dublin_edge_notes)"14:03
Arkady_KanevskyI did had one concern on federation.14:03
*** dpaterson has joined #edge-computing-group14:03
csatari#info We continue from 5.3.2.5 User management data receiver side14:03
Arkady_Kanevskysay we have edge/core that is vmware based, say VIO14:03
csatariOkay, What is it?14:03
dpatersono/14:04
Arkady_KanevskyAnd and far edge is openstack on baremetal.14:04
Arkady_Kanevskyhow does keystone fderation worrk?14:04
*** esarault has joined #edge-computing-group14:05
csatariThe VIO OpenStack should be configured to be an Identity provider14:05
*** cdent has joined #edge-computing-group14:05
csatariWhile the far edge Keystone should be configured to use the remote Identity providesr.14:05
Arkady_KanevskyVIO will use vSsphere for platform and its identity management. Keystone is just a shim on top of it.14:06
*** esarault_ has joined #edge-computing-group14:06
csatariAham. We should ask this from Ketstone guys.14:06
csatari#topic Keystone architectures14:07
*** openstack changes topic to "Keystone architectures (Meeting topic: review_of_dublin_edge_notes)"14:07
Arkady_Kanevskyif kesyotone can use remote ID provider then it will work. probably with local cache for disconnect periods.14:07
Arkady_Kanevskythanks14:07
csatari#info VIO Keystone is only a shim layer on top of vSphere. Is it possible to configure this as an Identity provider?14:07
Arkady_KanevskyI will ask vmware folks14:08
csatariI will add this as a question to https://wiki.openstack.org/wiki/Keystone_edge_architectures14:08
csatariOkay, please report back the result.14:08
csatari#action csatari to add this question to  https://wiki.openstack.org/wiki/Keystone_edge_architectures#Several_keystone_instances_with_federation_and_API_synchronsation14:08
csatari#topic Review of 5.3.2.5 User management data receiver side14:09
*** openstack changes topic to "Review of 5.3.2.5 User management data receiver side (Meeting topic: review_of_dublin_edge_notes)"14:09
*** esarault has quit IRC14:09
csatari#link https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#User_management_data_receiver_side14:10
*** rlpple has quit IRC14:10
csatariI think we should add the option to create shadow users here as it is done with K2K federation.14:11
*** rlpple has joined #edge-computing-group14:11
csatari#action csatari 5.3.2.5 Add the possibility to use shadow users.14:11
dpatersoncsatari: Does all ACL associated with user come along with shadow user?14:12
csatariI think not.14:12
csatariShadow user is created by rules defined on the far side.14:13
dpatersonSo things like object store permissions etc could be an issue at the edge node?14:13
*** kailun has joined #edge-computing-group14:13
*** kailun has quit IRC14:14
csatariAccording to my understanding these can be set using these rules.14:14
csatariMapping rules:  https://docs.openstack.org/keystone/latest/advanced-topics/federation/federated_identity.html#mapping-combinations14:14
dpatersonSo master keystone has to create mappings that will be used for creating shadow users?  Something along those lines?14:14
dpatersoncsatari: tx14:15
csatariNope, the mapping is done in the edge Keystones14:15
Arkady_Kanevskyneed to drop14:15
*** kailun has joined #edge-computing-group14:15
csatariBut the best is to ask it on the DL (any of them) from Keystone guys.14:16
csatariOkay14:16
csatariSee you.14:16
csatariAny more comments to 5.3.2.5 ?14:17
csatari#topic Review of 5.3.2.5 User management data receiver side14:17
*** openstack changes topic to "Review of 5.3.2.5 User management data receiver side (Meeting topic: review_of_dublin_edge_notes)"14:17
csatari#link https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#User_management_data_receiver_side14:18
csatariHere we should also mention the sahdow users case.14:18
*** esarault has joined #edge-computing-group14:19
csatariHah! we just discussed this.14:19
csatari#topic Review of 5.3.2.6 RBAC data source side14:19
*** openstack changes topic to "Review of 5.3.2.6 RBAC data source side (Meeting topic: review_of_dublin_edge_notes)"14:19
*** esarault_ has quit IRC14:21
csatari#info Can we totally rely on K2K federation here or do we still need to synchronise data?14:21
csatariI will ask in mail.14:22
csatari#topic Review of 5.3.2.7 RBAC data receiver side14:24
*** openstack changes topic to "Review of 5.3.2.7 RBAC data receiver side (Meeting topic: review_of_dublin_edge_notes)"14:24
csatari#info Same goes to here as for 5.3.2.614:24
csatariI just saw esarault -s mail.14:26
csatariAm I doing a lonely review here?14:26
*** rlpple has left #edge-computing-group14:30
csatariI think I've lost quorum, so I stop here with the review.14:30
csatari#topic End meeting14:30
*** openstack changes topic to "End meeting (Meeting topic: review_of_dublin_edge_notes)"14:30
csatari#info We will continue from 5.3.2.8 VM images source side14:31
csatari#info Next meeting is on 2018.07.05 16:00 CET on #edge-computing-group14:32
csatari#endmeeting14:32
*** openstack changes topic to "Finishing up (Meeting topic: Review of Dublin edge notes II)"14:32
openstackMeeting ended Thu Jun 28 14:32:15 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes/2018/review_of_dublin_edge_notes.2018-06-28-14.01.html14:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes/2018/review_of_dublin_edge_notes.2018-06-28-14.01.txt14:32
openstackLog:            http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes/2018/review_of_dublin_edge_notes.2018-06-28-14.01.log.html14:32
esarault@csatari, sorry man14:36
esaraultsome shit blew up here, had to take care of it14:36
csatariNo worries.14:37
csatariI hope you managed to solve it.14:37
esaraultI did :)14:37
csatariCool.14:37
csatariLet's continue next week.14:37
esaraultSure thing14:37
*** Arkady_Kanevsky has quit IRC14:55
*** cdent has quit IRC15:16
*** esarault_ has joined #edge-computing-group15:25
*** esarault has quit IRC15:29
*** mbeierl has quit IRC15:44
*** cdent has joined #edge-computing-group15:47
*** mbeierl has joined #edge-computing-group15:53
*** esarault has joined #edge-computing-group16:00
*** esarault_ has quit IRC16:02
*** epalper has quit IRC16:09
jrollchecking out what this group is doing for the first time. is there some sort of architecture diagram for generally what we want "edge" in openstack to look?16:30
*** vrv_ has quit IRC16:55
*** jaosorior has quit IRC17:10
*** esarault_ has joined #edge-computing-group17:31
esarault_@jroll: this is what's been made so far https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Example_of_Remote_and_Original_sites17:32
*** esarault has quit IRC17:33
jrollesarault_: I'll read through that, thanks!17:37
*** jesslampe has joined #edge-computing-group17:39
*** jesslampe has quit IRC17:47
*** esarault has joined #edge-computing-group18:19
*** esarault_ has quit IRC18:22
*** esarault has quit IRC18:34
*** jesslampe has joined #edge-computing-group19:27
*** jesslampe has quit IRC19:35
*** rosmaita has quit IRC21:17
*** cdent has quit IRC21:27
*** dpaterson has quit IRC21:39

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