14:02:40 #startmeeting TripleO Edge Squad Meeting 14:02:42 Meeting started Thu Jan 3 14:02:40 2019 UTC and is due to finish in 60 minutes. The chair is slagle. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:42 ping slagle, csatari, jaosorior, owalsh, fultonj, gfidente, hjensas, jtomasek, bogdando, dtantsur, rbrady, d0ugal, toure 14:02:43 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:02:45 The meeting name has been set to 'tripleo_edge_squad_meeting' 14:02:48 o/ 14:02:51 o/ 14:02:52 o/ 14:02:52 o/ 14:02:58 oh hi :) 14:03:15 wasn't sure if anyone would be around today or not 14:03:39 :D 14:03:46 #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:03:46 \o 14:03:48 #link https://etherpad.openstack.org/p/tripleo-edge-squad-status 14:03:50 Anyone can use the #link, #action, #help, #idea, #agreed, and #info commands, not just the moderatorǃ 14:03:52 #topic Agenda 14:04:13 * Review past action items 14:04:15 * Goals/action items for the week 14:04:19 o/ 14:04:27 #topic Review past action items 14:05:13 * slagle fultonj land split control plane docs patch https://review.openstack.org/#/c/614636 14:05:16 i had an ai for split control plane standalone doc, i think doc is ready to merge 14:05:21 https://review.openstack.org/#/c/614636/ 14:05:42 Alex Schultz proposed openstack/python-tripleoclient master: Expose timezone configuration https://review.openstack.org/628015 14:06:09 i added all suggestions, feel free to suggest more or vote. thanks 14:06:16 i added my +2 back 14:06:26 owalsh: can you review this one as well? 14:06:33 slagle: sure 14:06:55 could we please use the Edge Glossary? 14:07:13 bogdando: ok 14:07:14 for https://review.openstack.org/#/c/614636 14:07:18 thanks 14:07:26 Controller --> "Centralized Data Center" 14:07:33 Compute --> Edge Cloud 14:07:48 bogdando: the docs says Controller and Compute 14:07:51 or Aggregation Edge Layer/ cloudlet 14:08:14 tho the aggregation one implies a middle layer 14:08:29 bogdando: s/Controller/X? 14:08:36 bogdando: s/Compute/Y? 14:08:37 yes 14:08:39 what's X and Y? 14:09:01 i would keep the TripleO specific role names somewhere, b/c that's what we're actually deploying and what works 14:09:17 no need to abstract it behind some other definition 14:09:26 bogdando: X="Centralized Data Center" ? 14:09:42 * dtantsur is impressed we still cannot agree on naming :-P 14:09:48 but we can add the Edge terms as additional vocabulary 14:09:49 yes 14:09:58 derekh: that's kind of why i just said "Controller" and "Compute" 14:10:05 whops.... 14:10:09 dtantsur: i mean, sorry derekh 14:10:16 URGENT TRIPLEO TASKS NEED ATTENTION 14:10:16 https://bugs.launchpad.net/tripleo/+bug/1810054 14:10:18 https://bugs.launchpad.net/tripleo/+bug/1810136 14:10:18 https://bugs.launchpad.net/tripleo/+bug/1810325 14:10:20 Launchpad bug 1810054 in tripleo "mulitnode jobs failing on gathering facts from subnode-2" [Critical,Triaged] - Assigned to Ronelle Landy (rlandy) 14:10:22 Launchpad bug 1810136 in tripleo "standalone-upgrade job failing while upgrading mariadb" [Critical,In progress] - Assigned to Jose Luis Franco (jfrancoa) 14:10:24 Launchpad bug 1810325 in tripleo "standalone tempest fails "Exhausted all hosts available for retrying build failures for instance"" [Critical,Triaged] 14:10:51 bogdando: maybe we can land this one since it's correct as-is, and you can submit a followup for the term discussion? 14:10:53 fultonj: yeah, I'd prefer to keep these as well. my concerns are only with "far edge" and stuff, not with these ones. 14:11:00 sure we can 14:11:07 bogdando: Y="Aggregation Edge Layer/ cloudlet" 14:11:29 i'll use them in the doc but mention the connection in first paragph 14:11:32 let's see how it goes. thanks 14:11:36 hi cgoncalves i have just reported https://bugs.launchpad.net/ubuntu/+source/tripleo-heat-templates/+bug/1810415 14:11:36 Launchpad bug 1810415 in tripleo-heat-templates (Ubuntu) "incorrect datatype for "OctaviaFlavorId" " [Undecided,New] 14:11:38 ok thanks 14:11:47 it would be great if you can have a look 14:11:56 * slagle fultonj get help (perhaps from ci team) for ci inventory for second node for https://review.openstack.org/#/q/topic:bp/split-controlplane-ci 14:12:37 i still have to do that 14:12:51 fultonj: shall we work on this task over the next week? 14:12:58 slagle: yes 14:13:11 ok sounds good 14:13:30 #action fultonj/slagle get help (perhaps from ci team) for ci inventory for second node for https://review.openstack.org/#/q/topic:bp/split-controlplane-ci 14:13:31 Ronelle Landy proposed openstack/tripleo-quickstart master: Modify fs020 parameters to match fs001 more closely https://review.openstack.org/628052 14:13:58 * slagle slagle to draft deployment scaling/management at the edge doc (slagle, 14:13:52) 14:14:27 #link https://docs.google.com/document/d/12tPc4NC5fo8ytGuFZ4DSZXXyzes1x3U7oYz9neaPP_o 14:14:41 I've started the doc, and it's ready for comments and other ideas 14:15:00 it covers some of the existing WIP and some other new ideas 14:15:31 there are some possible next steps documented if there are folks looking for how to get started on some things 14:15:45 nice 14:15:49 indeed 14:16:47 i will probably send this out to the list as well 14:16:54 #action slagle send scaling doc to ML 14:18:05 Alex Schultz proposed openstack/python-tripleoclient master: Use cliff autodoc generation https://review.openstack.org/523510 14:18:18 #topic Goals/action items for the week 14:18:23 pbandark, ack. looking 14:18:50 slagle: think I had an action item to look into nova AZs 14:19:13 oh right 14:19:33 "owalsh to investigate nova AZ config" 14:19:42 from the prior mtng 14:20:07 pbandark, pike? octavia was never tested in pike afaik. much integration work was done in queens and not backported 14:20:35 cgoncalves, i can see same code in the heat template for rocky 14:20:41 it looks reasonably straightforward, just spinning up an env to test it out 14:20:52 and queens 14:21:02 Natal Ngétal proposed openstack/paunch master: [Core] Change openstack-dev to openstack-discuss. https://review.openstack.org/622894 14:21:23 backporting could take some work though 14:21:30 owalsh: ok, is it configuration or actual client commands that need to be run? 14:21:32 pbandark, yeah, the issue would still exist in queens and rocky. I'm just saying you shouldn't be trying on pike anyway 14:21:41 Natal Ngétal proposed openstack/paunch master: [Configuration] Add missing py37 and corrected default envlist. https://review.openstack.org/624611 14:21:53 pbandark, will you be proposing a fix? if so, please add me as reviewer 14:22:07 cgoncalves, ok 14:22:28 #action owalsh continue investigating nova AZ config 14:22:58 slagle: client commands 14:22:59 also this week I'd like to document the split-controlplane deployment from a central undercloud (not using standalone) 14:23:15 slagle: sounds, good 14:23:16 i'll work on that 14:23:39 #action slagle document the split-controlplane deployment from a central undercloud (not using standalone) 14:24:28 i'll also update https://review.openstack.org/#/c/626563/ 14:24:31 #link https://review.openstack.org/#/c/626563/ 14:24:31 slagle: maybe it makes sense to have an edge (or similar) section in the docs? 14:24:37 as the docs patch will need that 14:24:45 thanks cgoncalves psachin 14:24:50 e.g. so that https://docs.openstack.org/tripleo-docs/latest/ ctrl-F "edge" works? 14:24:56 #action slagle update roles patch https://review.openstack.org/#/c/626563/ 14:25:12 fultonj: sounds good to me 14:25:23 we can link to other sections if needed 14:25:45 I did a similar thing for config-download. sort of along the lines of a config-download "User's Guide" 14:25:53 could have an "Edge User's Guide" 14:26:01 I think until we support multiple control planes for edge it makes a little difference to have a dedicated docs 14:26:01 yeah, just like that 14:26:31 just a local vs WAN distributed single control plane, not a bug deal! :) 14:26:39 big* 14:27:30 just adding notes for scale and latency ad hoc is enought IMO 14:27:35 i like it b/c it shows how TripleO can be used for Edge, and adds the context around Edge to our docs, which users might be looking for 14:28:14 even if it's mostly introdcutory text, and then links to other sections. i think that's ok 14:28:27 that doc can then evolve to have the more advanced topics 14:28:58 ok, just not sure i hat would address the expectations of one opening the Edge Guide in the hope to see some real stuff and multiple control planes... 14:28:58 I think it's good to start with something to evolve from and get things out to people early 14:29:06 it would* 14:30:06 or rather set him/her somewhat disappointed to see the same single CP deployment but with scale/latency comments and optimizations 14:30:06 i consider split-controlplane "real stuff" :_ 14:30:08 :) 14:30:11 ;) 14:30:33 right, split control plane worth its dedicated docs 14:31:08 let's work on the patch and we can see how it looks. some context and level setting would be good to document IMO 14:31:18 +1 14:32:03 anything else folks want to address for the upcoming week? 14:33:04 thanks! 14:33:06 #endmeeting