14:00:32 #startmeeting TripleO Edge Squad Meeting 14:00:33 Meeting started Thu Oct 4 14:00:32 2018 UTC and is due to finish in 60 minutes. The chair is slagle. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:34 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:37 The meeting name has been set to 'tripleo_edge_squad_meeting' 14:00:47 ping slagle, emilien, csatari, jaosorior, owalsh, fultonj, gfidente, hjensas, jtomasek,thrash, bogdando, dtantsur, rbrady 14:00:50 #info remove or update your nick from the Meeting Template on the etherpad if you want (or don't want) to be ping'd for the start of the meeting 14:00:52 o/ 14:00:53 #link https://etherpad.openstack.org/p/tripleo-edge-squad-status 14:00:55 o/ 14:00:56 o/ 14:00:59 Anyone can use the #link, #action, #help, #idea, #agreed, and #info commands, not just the moderatorǃ 14:01:02 o/ 14:01:29 #topic Agenda 14:01:29 * Review past action items 14:01:29 * One off items 14:01:30 * Goals for the week 14:02:22 #topic Review past action items 14:02:39 * slagle all: review https://etherpad.openstack.org/p/tripleo-edge-mvp and discuss (slagle, 14:10:04) 14:02:50 we said we'd review that etherpad from bogdando 14:03:03 i see comments from a few folks 14:03:20 i reviewed it, especially around Goal 4 since that was the ask 14:03:35 me too 14:03:46 i found it a little difficult to understnad, but I left some comments there 14:04:20 bogdando: anything we should talk about now? 14:04:22 bogdando: perhaps you could take a look and we can continue the discussion on the etherpad for now? 14:04:32 mwhahaha, EmilienM: hi. could you please approve https://review.openstack.org/#/c/587015/ ? thanks! 14:04:44 jaosorior: i know nova is one, i'd have to run a test to find all the rest 14:05:39 #agreed continue disucssion in etherpad 14:05:45 hehe :) 14:05:48 ok, next up 14:05:54 * slagle fultonj to get feedback from tripleo CI group on https://blueprints.launchpad.net/tripleo/+spec/split-controlplane-ci (fultonj, 14:29:39) 14:06:36 slagle, fultonj: yes, pleae let's keep it for offline 14:07:00 that AI will be ongoing 14:07:11 planning to... 14:07:13 1. prototype 14:07:30 2. then get feedback on submission which uses standlone like https://github.com/openstack-infra/tripleo-ci/blob/master/zuul.d/standalone-jobs.yaml#L14 14:07:38 still workkig on prototype 14:08:12 ok sounds good 14:08:24 how is that going? 14:08:36 or is that the next action item we were going to discuss... 14:08:36 #info - following https://etherpad.openstack.org/p/tripleo-compute-standalone 14:08:36 #info - few days ago ran into http://paste.openstack.org/show/731116 14:08:37 #info - Why is RoleNetIpMap missing new edge node 192.168.24.3? http://paste.openstack.org/show/731120 14:08:44 #info - Stack knows about new node http://paste.openstack.org/show/731121 14:08:44 #info - Reproducing in my env today and might ping for help if still stuck 14:08:45 #info - https://gitlab.com/fultonj/tripleo-standalone-edge 14:09:17 slagle: that's what i'm currently stuck on perhaps after meeting and after i reproduce i could get help dubbing? 14:09:20 debugging* 14:09:34 * dtantsur thinks fultonj just invented twitter over irc 14:10:00 fultonj: sure, it probably didn't find an IP for the compute node 14:10:17 maybe a problem with DeployedServerPortMap or HostnameMap 14:10:17 URGENT TRIPLEO TASKS NEED ATTENTION 14:10:18 https://bugs.launchpad.net/tripleo/+bug/1792872 14:10:19 https://bugs.launchpad.net/tripleo/+bug/1793665 14:10:20 https://bugs.launchpad.net/tripleo/+bug/1795718 14:10:20 Launchpad bug 1792872 in tripleo "[queens] overcloud prepare image failed by giving IronicAction.node.set_provision_state failed: 'NoneType' object has no attribute '__getitem_" [Critical,Triaged] - Assigned to Marios Andreou (marios-b) 14:10:21 Launchpad bug 1793665 in tripleo "multinode-oooq-container scenarios and Fs016/17/20 periodic jobs fails on validate-tempest: Unexpected response code received" [Critical,In progress] - Assigned to Juan Antonio Osorio Robles (juan-osorio-robles) 14:10:22 Launchpad bug 1795718 in tripleo "Exception: Error inspecting image: docker://docker.io/ server misbehaving" [Critical,Triaged] 14:10:57 #action fultonj and slagle to continue debugging standalone edge deployment 14:11:04 thanks slagle 14:11:13 o/ 14:11:55 * slagle fultonj try standalone for https://blueprints.launchpad.net/tripleo/+spec/split-controlplane-ci based on https://github.com/openstack-infra/tripleo-ci/blob/master/zuul.d/standalone-jobs.yaml#L14 (fultonj, 14:38:07) 14:12:00 alright, we just discussed that 14:12:14 so moving on 14:12:22 #topic One Off 14:12:29 #info - abishop not here but made progress on active/active cinder in standalone 14:12:56 and cinder AZs 14:13:00 #action https://etherpad.openstack.org/p/tripleo-edge-mvp is needs clarification for the special snowflakes, what do we understand as that when comparing it to the federated openstack services (perhaps) 14:13:16 dtantsur: ^^ 14:13:35 just captured the irc logs, not really invented those snowflakes :) 14:13:52 not sure I get it, what's the question for me? 14:14:21 bogdando: the only context i was able to capture from the etherpad was that it was implied that "using ansible" = "special snowflake" 14:14:28 dtantsur: yes please as I think when we were talking about architecture differences for undercloud vs overcloud, we used that term 14:14:45 so i don't understand what is meant by special snowflake 14:15:07 let's probably try use less metaphors and more specific wording? 14:15:17 dtantsur: +1 14:15:31 agreeing on terms is already a goal 1 :D 14:16:00 w.r.t terms i think it helps to be consistent with edge working group 14:16:34 fultonj: yes, so one of the things I was going to do try and do over the next week is gather all the links/references that we've been compiling into a single spot 14:16:44 perhaps the sqaud etherpad for now 14:17:14 I think what is meant under "special snowflake" here is actually a concern about growing the amount of logic specific to tripleo 14:17:22 b/c there was also some confusion around "Far Edge" in the etherpad. it's a thing that's been defined outside of TripleO, so we need to understand what is meant by it 14:17:26 as opposed to tripleo relying more on other upstream openstack projects 14:17:45 * dtantsur is the primary hater of the term "Far Edge" 14:17:55 https://www.dropbox.com/s/255x1cao14taer3/MVP-Architecture_edge-computing_PTG.pptx?dl=0# 14:18:11 how do I block IRC messages containing ^^^ 14:18:14 ? 14:18:14 dtantsur: understood :) but you'd have to convince the Edge WG to not use it 14:18:17 ^ i don't love the term but i'll use it because others do outside of tripleo in the dge working group 14:18:31 slagle, dtantsur: updated special snowflakes 14:18:34 https://etherpad.openstack.org/p/tripleo-edge-mvp 14:18:59 slagle: maybe I'm just the grumpy old man here :) 14:19:20 dtantsur: nah :). i hear where you're coming from 14:19:26 I suspect the "Edge" terminology makes good marketing, so we may not be able to change it globally 14:19:48 dtantsur: honestly it was driven by groups who are already actually deploying this stuff. and they found it useful to have these classifications 14:20:04 slagle: did I wrote that right? 14:20:09 then I guess we should just start our documentation with a glossary :) 14:20:12 which is a good idea anyway 14:20:20 dtantsur: ^^ please take a look that etherpad for 11th time :) 14:20:30 line 24-27 14:20:44 bogdando: can we s/special snowflake/something non-metaphoric/g please? 14:20:55 go for it! 14:21:03 I have a gut feeling it's not used exactly in this sense, but as a non-native speaking I cannot grasp it in full 14:21:18 dtantsur: as for tripleo growing more logic that is not openstack, not sure i totally agree there. tripleo is part of openstack, as are all the other deployment projects 14:21:38 just please make sure it not gets too much of tripleo specific! :) 14:21:40 slagle: right, it's not necessary a bad thing 14:21:55 but it's maintenance cost, and if we can avoid it - let's avoid it 14:21:59 as every vendor these days seems like has a bunch of snowflakes for Edge thene 14:22:02 theme* 14:22:02 dtantsur: openstack doesn't have a tenant facing API service for software config/deployment that is sufficient enough for openstack or edge deployment 14:22:10 Heat is about it 14:22:12 e.g. in metalsmith case, the metalsmith library is under ironic governance, so we share its maintenance 14:22:22 we could write this code in tripleo-common, then we would have to maintain it 14:22:24 and i don't plan on using Heat to deploy thousands of edge nodes :) 14:22:30 lol, yeah 14:23:32 * dtantsur ponders an openstack software config service 14:23:32 i do think it's important that we drive things with existing or new consistent interfaces. for now, that means t-h-t 14:24:06 so i look at ansible/config-download as a potential way to scale that to the edge 14:25:10 anyway, for me personally the most interesting things is what (if anything) happens with bm provisioning and management 14:26:22 #action slagle to work on documenting some terms and gathering links/references 14:26:45 bogdando: for distributed undercloud, what exactly is the goal? is it federation to make is possible (fast) to deploy to edge from centre, a local undercloud at each edge to tolerate network partitions, both, neither? 14:27:06 my concerns were around replacing ironic as an operator facing API (or completely) with something specific to tripleo 14:27:23 this is *probably* where the snowflakes speech came from 14:27:47 owalsh: that's the question, and I don't think we have solved it yet 14:27:59 dtantsur: for bm? i don't think there's any reason to do that. i'm not aware of anything going in that direction 14:28:15 dtantsur: ack 14:28:21 dtantsur: so both :-) 14:29:03 slagle: the question is how deeply we change the bm management workflow on the central undercloud (the Edge layer if I'm not mixing things up again) 14:29:57 (it may not feel the right question for right now, but the resulting architecture of the undercloud may depend on it) 14:32:24 well maybe the new workflow will be used for both 14:32:32 or should be 14:32:36 +1 14:33:34 anything else before we wrap up? 14:33:59 #endmeeting