| *** trevor_intel has joined #edge-computing-group | 01:20 | |
| *** trevor_intel has quit IRC | 02:53 | |
| *** jaosorior has quit IRC | 05:41 | |
| *** ricardoas has quit IRC | 06:20 | |
| *** epalper has joined #edge-computing-group | 06:40 | |
| *** ianychoi has quit IRC | 08:39 | |
| *** jaosorior has joined #edge-computing-group | 09:15 | |
| *** cdent has joined #edge-computing-group | 11:20 | |
| *** cdent has quit IRC | 12:29 | |
| *** ianychoi has joined #edge-computing-group | 12:46 | |
| *** esarault has joined #edge-computing-group | 12:56 | |
| esarault | So I'll take it that there's no meeting today? | 14:10 |
|---|---|---|
| csatari | Hi | 14:14 |
| esarault | Hi :) | 14:15 |
| csatari | Sorry I missed my notification for this meeting. | 14:15 |
| csatari | Shall we still go for it? | 14:15 |
| esarault | Sorry 'bout not making it for the F2F in Vancouver, we ended up having a crowd towars the end of the marketplace and couldn't make it out of the booth | 14:16 |
| esarault | Sure, unless we want to reschedule if we're missing quorum or key contributors | 14:16 |
| ildikov | I'm here to lurk :) | 14:17 |
| csatari | I think any discussions are good. | 14:17 |
| csatari | Let's go for it. | 14:17 |
| csatari | #startmeeting Review of Dublin edge notes 04 | 14:18 |
| openstack | Meeting started Thu Jun 14 14:18:28 2018 UTC and is due to finish in 60 minutes. The chair is csatari. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:18 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:18 |
| *** openstack changes topic to " (Meeting topic: Review of Dublin edge notes 04)" | 14:18 | |
| openstack | The meeting name has been set to 'review_of_dublin_edge_notes_04' | 14:18 |
| csatari | #topic Roll Call | 14:18 |
| *** openstack changes topic to "Roll Call (Meeting topic: Review of Dublin edge notes 04)" | 14:18 | |
| csatari | #info Gergely Csatari | 14:19 |
| csatari | #topic Correction of previous comments | 14:20 |
| *** openstack changes topic to "Correction of previous comments (Meeting topic: Review of Dublin edge notes 04)" | 14:20 | |
| csatari | I've corrected the comments received so far. | 14:21 |
| csatari | #info Status of the comments are maintained here: https://etherpad.openstack.org/p/Dublin-edge-notes-wiki | 14:21 |
| csatari | There are quite big changes in some chapters. | 14:22 |
| csatari | #info https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Example_of_Remote_and_Original_sites have big changes | 14:23 |
| csatari | I'm not sure if we should recheck these during these meeting or just handle incoming comments if anyone has any. | 14:24 |
| csatari | I would not like end up with 100 meetings just for reviewing this page ;) | 14:24 |
| esarault | Not sure either, its aint like I'm going to argue over the KEystone and Glance points | 14:25 |
| csatari | Lets just record this to the minutes and go on ;) | 14:25 |
| csatari | #info Any comments to the already checked sections are welcome on edge-computing@lists.openstack.org | 14:26 |
| csatari | Okay, lets jump into the requirements | 14:26 |
| csatari | #topic Review of 5.3 Requirements | 14:27 |
| *** openstack changes topic to "Review of 5.3 Requirements (Meeting topic: Review of Dublin edge notes 04)" | 14:27 | |
| csatari | #link https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Requirements | 14:27 |
| csatari | If no comments for that one sentence lets move. | 14:28 |
| esarault | Yeah the outcome will depend heavily on Kingbird | 14:29 |
| csatari | Skipping the empty chapters. | 14:29 |
| csatari | Well, the point would be to define requirements to Kingbird or other projects. | 14:30 |
| esarault | Ok then | 14:30 |
| esarault | Dsicovery of data source section | 14:30 |
| esarault | Are we expecting some sort of broadcast capabilities? | 14:30 |
| csatari | #topic Review of 5.3.2.1 Discovering of data sources | 14:31 |
| *** openstack changes topic to "Review of 5.3.2.1 Discovering of data sources (Meeting topic: Review of Dublin edge notes 04)" | 14:31 | |
| esarault | Or would this be reported to amaster entity | 14:31 |
| csatari | I think we discussed a cascaded architecture. | 14:32 |
| esarault | Some tiered reporting basically? | 14:32 |
| esarault | X amount of nodes call back to their "masters" | 14:32 |
| esarault | then those call back to theirs, until back to "root" | 14:33 |
| *** trevor_intel has joined #edge-computing-group | 14:33 | |
| csatari | When an edge cloud instance is "switched on" it should be able to find an other edge cloud instance which have the data. | 14:33 |
| esarault | Ok | 14:33 |
| csatari | yes | 14:33 |
| esarault | Broadcasting? | 14:33 |
| csatari | How it is done I have no idea ;) | 14:33 |
| esarault | TherE's just things to keep in mind on that point. Not every network will allow broadcasting constantly | 14:34 |
| esarault | Should be a notion of being able to "call back home" knowing where the home is supposed to be made when broadcasting on the network is not a viable route | 14:34 |
| csatari | Should I add a note about this? | 14:34 |
| esarault | If you believe it brings value please do so | 14:34 |
| csatari | sure | 14:34 |
| esarault | Taking for granted everyone is goign to allow broadcasting on their network is very unlikely | 14:35 |
| csatari | #action csatari 5.3.2.1 add a note that broadcasting might not be possible in every network, so some alternative solution should be found. | 14:35 |
| csatari | Any comments to this or to 5.3.1.1 An edge cloud site should be aware of its location? | 14:36 |
| esarault | Nope, that's it for me | 14:37 |
| csatari | #topic Review of 5.3.2.2 Registering for synchronisation | 14:37 |
| *** openstack changes topic to "Review of 5.3.2.2 Registering for synchronisation (Meeting topic: Review of Dublin edge notes 04)" | 14:37 | |
| csatari | #link https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Registering_for_synchronisation | 14:37 |
| esarault | For Registering for synch, 1. there's a typo right before the word API, 2. I think this'll address the "call back home" capability so this looks good | 14:37 |
| esarault | Home being the active edge instance(s) | 14:38 |
| csatari | #action csatari 5.3.2.2 Fix reistration | 14:39 |
| csatari | 2) okay | 14:39 |
| csatari | #topic Review of 5.3.2.3 Advertise metadata data source service | 14:39 |
| *** openstack changes topic to "Review of 5.3.2.3 Advertise metadata data source service (Meeting topic: Review of Dublin edge notes 04)" | 14:39 | |
| csatari | #link https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Advertise_metadata_data_source_service | 14:40 |
| esarault | So here's a quesiton I have regarding authentication | 14:40 |
| esarault | How can a node apply for registration if it isn't known in keystone | 14:41 |
| esarault | Does Kingbird have a seperate list of authotized instances? | 14:41 |
| esarault | which is then synchronized to Keystone if and only if approved | 14:42 |
| esarault | or is there some Keystone implication when trying to register | 14:42 |
| csatari | Here we are discussing OpenStack instances not nodes, but maybe that is irrelevant for the question. | 14:42 |
| esarault | Well, let's see I have a new geo I want to join to the Edge Federation let's say | 14:43 |
| esarault | And not just a node level | 14:43 |
| csatari | I think the list of authrized instances should be dynamic. | 14:44 |
| esarault | Do we expect the ability to add a new geo directly via Kingbird? How do the two Keystone instance sin each of those are synchronized? Which one takes over the other given the are now "one"? | 14:44 |
| csatari | My thinking: 1) The new edge cloud insance finds its "master" edge cloud instance | 14:45 |
| csatari | (It could either find Keystone first and ask for Kingbirds API or can find Kingbird directly) | 14:46 |
| csatari | For this we will need "Advertise metadata data source service" in the "master" | 14:47 |
| csatari | 2) The new edge cloud instance registers for synchrnoisation to the master | 14:47 |
| csatari | For this we will need "Registering for synchronisation" | 14:47 |
| csatari | Kingbird in the "master" edge cloud instance records the new edge cloud instance as a client for synchronisation and drops the current metadata to it. | 14:48 |
| esarault | And my point is around this is where do we draw the line on what we expose of the existing environment for proper segregation of traffic until the new edge region is deemed "trustworthy and secure". Which service are we willing to expose, a discovery service running in Keybird or an active Keystone instance running production workloads that if compromised, could bring an entire | 14:49 |
| esarault | region down. My understanding here is that Keybird would act as the gateway before allowing a new region to go talk to the active master Keystone | 14:49 |
| csatari | Aham. Good point. | 14:50 |
| esarault | I do agree on 1) and 2) but the security side of thing here is not to be underestimated. | 14:51 |
| esarault | I see this as the first place I would go top onto to bring the region down | 14:51 |
| esarault | *would go tap | 14:51 |
| csatari | Should I add an authentication of the registering edge cloud instance requirement? | 14:51 |
| esarault | I believe so | 14:51 |
| esarault | This could be MAC adress filtering, IP ranges whitelisting | 14:52 |
| esarault | The ability to define who's able to call to the edge instance | 14:52 |
| csatari | I was thinking about some key exchange thing. | 14:53 |
| esarault | Would work too | 14:53 |
| csatari | Whitelist should be distributed to every "master" edge cloud instances. | 14:54 |
| csatari | #action csatari Add a new requirement to authenticate the registering edge cloud instances. | 14:54 |
| csatari | I can add these options and we can discuss it later. | 14:54 |
| esarault | Sure thing | 14:54 |
| csatari | Okay anything else for 5.3.2.3 Advertise metadata data source service ? | 14:55 |
| csatari | #topic Review of 5.3.2.4 User management data source side | 14:55 |
| *** openstack changes topic to "Review of 5.3.2.4 User management data source side (Meeting topic: Review of Dublin edge notes 04)" | 14:55 | |
| csatari | #link https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#User_management_data_source_side | 14:56 |
| csatari | #topic Next steps | 14:57 |
| *** openstack changes topic to "Next steps (Meeting topic: Review of Dublin edge notes 04)" | 14:57 | |
| csatari | #info We will continue from 5.3.2.5 User management data receiver side | 14:58 |
| csatari | I will start oranizing the next one. | 14:58 |
| csatari | Sorry for being late. | 14:58 |
| csatari | Should we keep doodling the time or should we go for a fixed time? | 14:59 |
| csatari | For me doodling is a bit better due to my hectic calendar. | 14:59 |
| *** epalper has quit IRC | 14:59 | |
| csatari | But maybe a fixed time would result in better participation . . . | 14:59 |
| *** epalper has joined #edge-computing-group | 14:59 | |
| esarault | Fixed time would be better it hink | 14:59 |
| csatari | Okay, then let me do a doodle for a fixed time :) | 15:00 |
| esarault | Otherwise you get these BS ad-hoc meetings that end up taking priority for all the wrong reasons | 15:00 |
| csatari | okay | 15:00 |
| esarault | I'm not one for sugar coating things :p | 15:00 |
| csatari | #action csatari to organize a fixed time meeting for the reviews | 15:00 |
| csatari | 😄 | 15:01 |
| esarault | Alright, see you next week, was a short but useful session ^^ | 15:01 |
| csatari | Thanks esarault for your comments anf thanks ildikov for lurking. | 15:01 |
| csatari | I will not mis sthe first part of the next one ;) | 15:02 |
| csatari | #endmeeting | 15:02 |
| *** openstack changes topic to "Finishing up (Meeting topic: Review of Dublin edge notes II)" | 15:02 | |
| openstack | Meeting ended Thu Jun 14 15:02:13 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:02 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes_04/2018/review_of_dublin_edge_notes_04.2018-06-14-14.18.html | 15:02 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes_04/2018/review_of_dublin_edge_notes_04.2018-06-14-14.18.txt | 15:02 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes_04/2018/review_of_dublin_edge_notes_04.2018-06-14-14.18.log.html | 15:02 |
| ildikov | csatari: thanks for running the meeting! | 15:02 |
| csatari | My pleasure. | 15:02 |
| *** trevor_intel has quit IRC | 15:12 | |
| *** trevor_intel has joined #edge-computing-group | 15:48 | |
| *** epalper has quit IRC | 17:34 | |
| *** esarault has quit IRC | 20:34 | |
| *** trevor_intel has quit IRC | 22:29 | |
| *** markvoelker has quit IRC | 23:46 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!