14:01:17 <jaosorior> #startmeeting tripleo
14:01:18 <openstack> Meeting started Tue Sep 18 14:01:17 2018 UTC and is due to finish in 60 minutes.  The chair is jaosorior. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:19 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:23 <openstack> The meeting name has been set to 'tripleo'
14:01:28 <jaosorior> #topic agenda
14:01:31 <jaosorior> * Review past action items
14:01:33 <jaosorior> * One off agenda items
14:01:35 <jaosorior> * Squad status
14:01:36 <holser_> o/
14:01:37 <jaosorior> * Bugs & Blueprints
14:01:39 <jaosorior> * Projects releases or stable backports
14:01:41 <jaosorior> * Specs
14:01:43 <jaosorior> * open discussion
14:01:43 <jfrancoa> o/
14:01:45 <jaosorior> Anyone can use the #link, #action and #info commands, not just the moderatorǃ
14:01:47 <jaosorior> Hey folks! who's around?
14:01:50 <fultonj|afk> o/
14:01:52 <marios> o/ hello
14:01:52 <rascasoft> o/
14:01:54 <iranzo> hi
14:01:55 <weshay> 0/
14:01:56 <ksambor> \o
14:01:57 <chem> o/
14:01:57 <gfidente> o/
14:02:04 <slagle> hi
14:02:04 <mwhahaha> hi2u
14:02:09 <fhubik> hey
14:02:21 <rlandy> o/
14:02:28 <beagles> o/
14:02:32 <rfolco> o/
14:02:47 <jrist> o/
14:02:49 <dpeacock> o7
14:02:56 <rdopiera> hi, I'm trying oooquickstart with rhos-14 and I'm getting an import error for zmq. I'm being told that zmq shouldn't be used in osp14, is it something I'm doing wrong? I'm using all the defaults
14:03:00 <holser_> o/
14:03:02 <EmilienM> hi (half here)
14:03:07 <jrist> haha o7, is that like a salute?
14:03:15 <rdopiera> uh, sorry, it seems there is a meeting
14:03:18 <rdopiera> I will come later
14:03:23 <dpeacock> jrist: yeah I saw tengu do it once and figured it looked a little cool
14:03:51 <owalsh> o/
14:03:55 <panda> o/
14:04:05 <mschuppert> o/
14:04:09 <mwhahaha> yea it's a salute
14:04:14 <jrist> dpeacock+1
14:04:25 <jaosorior> #topic review past action items
14:04:32 <jaosorior> None.
14:04:45 <jaosorior> #topic one off agenda items
14:04:47 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-meeting-items
14:05:06 <redrobot> o/
14:06:06 <jaosorior> #topic Stein forum topic proposals
14:06:22 <jaosorior> So... we have until the 26th of September to propose topics for the Stein Summit
14:06:28 <jrist> jaosorior: are we past one off agenda items?
14:06:30 <jaosorior> Here's the etherpad:
14:06:40 <abishop> o/
14:06:41 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-forum-stein
14:06:51 <jaosorior> jrist: no, this is one of the "one off agenda items"
14:07:07 <jrist> oh ok :)
14:07:11 <jrist> thanks
14:07:19 <jaosorior> So, if you have a topic to bring up to the Summit, which is coming soon, please add it to the etherpad.
14:07:37 <jaosorior> #topic citellus POC
14:07:39 <jaosorior> iranzo: ^^
14:07:44 <iranzo> jaosorior: yup :)
14:08:08 <iranzo> weshay++ some months ago worked on a review at https://review.openstack.org/#/c/553571/4 )
14:08:23 <iranzo> that used a set of scripts that are used by support folks
14:08:30 <iranzo> to detect known issues on osp deployments
14:08:39 <iranzo> from either live systems or sosreports
14:09:01 <iranzo> unlike others, goal was to enable operators, and sysadmins in general to run them and of course write new ones
14:09:07 <iranzo> by using bash or other languages of choice
14:09:17 <iranzo> and some common agreements (return codes and stderr for messages)
14:09:33 <iranzo> it can drop a json that can be parsed later by other tools to get overall status
14:10:03 <iranzo> so... thoughts?
14:10:14 <iranzo> review was 'rechecked' as it passed some time ago, but to get updated results
14:10:16 <ooolpbot> https://bugs.launchpad.net/tripleo/+bug/1786764
14:10:16 <openstack> Launchpad bug 1786764 in tripleo "Wrong versions of tripleo-common in container images updated in CI" [Critical,In progress] - Assigned to Emilien Macchi (emilienm)
14:10:16 <ooolpbot> https://bugs.launchpad.net/tripleo/+bug/1792296
14:10:17 <ooolpbot> https://bugs.launchpad.net/tripleo/+bug/1792343
14:10:18 <ooolpbot> https://bugs.launchpad.net/tripleo/+bug/1792560
14:10:18 <ooolpbot> https://bugs.launchpad.net/tripleo/+bug/1792862
14:10:19 <ooolpbot> https://bugs.launchpad.net/tripleo/+bug/1792870
14:10:19 <openstack> Launchpad bug 1792296 in tripleo "Overcloude deploy error:Timed out waiting for messages from Execution" [Critical,In progress] - Assigned to Quique Llorente (quiquell)
14:10:20 <ooolpbot> https://bugs.launchpad.net/tripleo/+bug/1792872
14:10:20 <ooolpbot> https://bugs.launchpad.net/tripleo/+bug/1792892
14:10:20 <openstack> Launchpad bug 1792343 in tripleo "[tripleo] rocky baremetal deployment fails with jq: error: Could not open file /var/lib/heat-config/deployed/<id>.notify.json" [Critical,Triaged] - Assigned to Quique Llorente (quiquell)
14:10:21 <openstack> Launchpad bug 1792560 in tripleo "Upgrades in CI still using Q->master instead of R->master release" [Critical,In progress] - Assigned to Jiří Stránský (jistr)
14:10:21 <jaosorior> iranzo: I see the POC patch is for CI; how would that be used?
14:10:23 <openstack> Launchpad bug 1792862 in tripleo "[master] Telemetry Tempest integration tests failed giving Unable to complete operation on subnet b13c76ec-c851-48d0-91a9-245a2fdcad9b: One or more ports have an IP allocation from this subnet." [Critical,Fix committed] - Assigned to Mehdi Abaakouk (sileht)
14:10:24 <openstack> Launchpad bug 1792870 in tripleo "[Rocky] FS01 periodic job failed at overcloud prepare image giving Error: Unable to establish IPMI v2 / RMCP+ session\n'.: ProcessExecutionError: Unexpected error while running command" [Critical,Triaged] - Assigned to Quique Llorente (quiquell)
14:10:25 <openstack> 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 Quique Llorente (quiquell)
14:10:26 <openstack> Launchpad bug 1792892 in tripleo "Undercloud upgrades fails at ERROR! Invalid callback for stdout specified: yaml" [Critical,In progress] - Assigned to Quique Llorente (quiquell)
14:10:40 <jrist> ah that bot is well timed
14:10:45 <weshay> capturing errors and making it easy to find the associated data is awesome..
14:10:51 <iranzo> jaosorior: ^
14:10:57 <weshay> citellus looked pretty awesome
14:11:02 <weshay> iranzo++
14:11:06 <iranzo> weshay++
14:11:11 <jaosorior> weshay, iranzo: It sounded really nice; that's why I asked iranzo to bring it up here :D
14:11:17 <mwhahaha> we need to find a better way to package/deploy that
14:11:22 <mwhahaha> right now i'd be -2 on that review
14:11:28 <iranzo> it is delivered as pip package if needed
14:11:28 <jaosorior> just asking for more details cause I'm interested.
14:11:32 <iranzo> that is build automatically
14:11:33 <weshay> ya.. that was not ready for merge
14:11:34 <jrist> that website isn't working
14:11:36 <iranzo> or a container
14:11:40 <chem> weshay: iranzo do we have a exemple of the kind of check it will be used for ?
14:11:42 <jrist> can someone summarize? is it just about associated data?
14:11:42 <weshay> mwhahaha, jaosorior so we need to think about not adding to  CI
14:11:47 <iranzo> chem: yes, one sec
14:11:54 <weshay> mwhahaha, jaosorior we need to think about adding it to the project
14:11:57 <jrist> oh nevermind, it had an extra )
14:12:01 <iranzo> chem: https://asciinema.org/a/169814
14:12:06 <mwhahaha> i don't know if w ewant to add it to the project
14:12:08 <iranzo> asciicinema of operation
14:12:25 <iranzo> and as example of checks: non configured token expirations, wrong ntp sync setup
14:12:32 <mwhahaha> distributing it as a container might be interesting
14:12:34 <iranzo> like when people used chronyc instead of  ntpd
14:12:48 <weshay> mwhahaha, iranzo getting consensus on the tool to use for error detection is difficult at best
14:12:52 <iranzo> missing support in system for virtualization, etc
14:12:54 <slagle> what is citellus-master.tgz? is that a tarball of the citellus git repo?
14:13:03 <iranzo> slagle: yes, its an old tarball of the repo
14:13:20 <slagle> iranzo: can we do that a different way? just use git clone or something
14:13:23 <mwhahaha> i would rather see it added as a new service rather than added to quickstart or integrated into tripleo itself
14:13:39 <mwhahaha> it might make sense to have it on the undercloud itself
14:13:40 <iranzo> slagle: yes or even add it to the requirements.txt
14:13:46 <weshay> +1
14:13:58 <chem> iranzo: hum so static report of sosreport, nice.  Plugged into the ci it would only check logs then, no triggering another process
14:14:01 <iranzo> from undercloud, you can pass an ansible-host-file that uploads executes and brings back data from the hosts
14:14:15 <chem> iranzo: (afraid of timeout in ci)
14:14:24 <iranzo> chem: yes, and the json can be easily parsed for the errors
14:14:41 <iranzo> let me show you one example of the json
14:14:45 <weshay> if I recall it was all very fast.. a number of seconds
14:14:53 <iranzo> web UI: https://htmlpreview.github.io/?https://github.com/citellusorg/citellus/blob/master/doc/sampleweb/citellus.html
14:15:05 <iranzo> https://github.com/citellusorg/citellus/blob/master/doc/sampleweb/citellus.json
14:15:07 <iranzo> json generated
14:15:11 <iranzo> yes, it runs usually under 10 seconds
14:15:16 <iranzo> (for the sosreport check)
14:15:18 <mwhahaha> it seems like something that should be integrated with the UI itself
14:15:31 <iranzo> for live it can take a bit more because of system logs parsed, etc
14:15:39 <iranzo> but it's not like a century
14:15:47 <iranzo> goal was always to make it damn fast and easy to get new things there
14:15:54 <iranzo> to highlight what could go wrong
14:16:09 <iranzo> even you can define sizing data based on number of cpus, etc and report if a setting is not 'suited' to host setup
14:16:12 <iranzo> if you want to give hints there
14:16:17 <jaosorior> weshay, iranzo: so, is that a service that would constantly be running on the nodes? or is it a one-off script you run and pulls down a bunch of info?
14:16:43 <iranzo> I would say a one-off executed as part of the tests could be ok
14:16:50 <iranzo> in support we used it to check what customers had wrongly setup
14:16:55 <iranzo> based on our past experience
14:17:07 <iranzo> and test 'id's' are unique so you can define which ones should be reported or not
14:17:13 <iranzo> based on regexps to the full path
14:17:19 <iranzo> like "all for openstack", or all for "clock"
14:17:24 <chem> mwhahaha: if it's in the product then maybe that could be used for the 2 days validation framework currently WIP by Tengu
14:17:29 <iranzo> or report openstack issues but not bugzillas
14:17:47 <mwhahaha> chem: yea that was my thought as it makes sense to have available on the undercloud for subsequent runs
14:17:54 <mwhahaha> but it's a delivery thing into tripleo
14:17:58 <mwhahaha> ie rpm or containers or whatever
14:18:12 <iranzo> when it checks several hosts, it also aggregates data and shows a combined status, also reporting things that could be problematic
14:18:19 <iranzo> think of different OS releases
14:18:21 <iranzo> on the same environment
14:18:25 <iranzo> or sharing same iscsi initiatior name
14:18:27 <mwhahaha> it's likely that we'd want it wrapped up in a container so it could be pulled in on the undercloud and executed via the UI/CLI
14:18:30 <iranzo> among different hosts
14:19:10 <jaosorior> iranzo, weshay: does the POC patch have an output already from the deployment?
14:19:12 <mwhahaha> so i think it's a good idea to have, but we need to figure out the best way to integrate the execution/results
14:19:13 <iranzo> mwhahaha: I've made some attempts to use an Super privileged container, but still require work, as the actual 'tests' are written for either checking the path in sosreport or the path in a live system
14:19:13 <chem> mwhahaha: that would be cool
14:19:18 <weshay> jaosorior, it's so old
14:19:25 <weshay> I'll refresh it at some point
14:19:30 <jaosorior> sure
14:19:31 <iranzo> so trying to run 'live' against a folder might give some strange output for some commands
14:19:36 <chem> iranzo: seems like all feature are there :)
14:19:52 <chem> citellus++ :)
14:19:59 <iranzo> think of 'rpm -qa' inside the container instead of the actal 'host' folder
14:20:15 * weshay notes.. it would be very cool to have the same tool used to diagnose errors up and down stream
14:20:21 <iranzo> yes!
14:20:48 <mwhahaha> so it sounds like there's more work on the citellus front to figure out distribution
14:20:49 <weshay> which is why I would hope we can avoid making this a ci project
14:21:09 <jaosorior> weshay, iranzo: So, the tool does sound quite cool. But yeah, like mwhahaha said, it would be best if we could have it packaged and integrated properly.
14:21:12 <iranzo> the list of plugins in the tarball is at this commit: https://github.com/citellusorg/citellus/tree/1ee1c6a36f51e8a7c809d5162004fb57ee99b168
14:21:18 <iranzo> jaosorior: what kind of packaging do you mean?
14:21:30 <iranzo> project has automatic creationg via dockerhub of container and pypi package upload
14:21:31 <weshay> iranzo, jaosorior ok.. the ci team will help get it packaged
14:21:35 <iranzo> ok
14:22:00 <mwhahaha> so we need it rpm'd to be properly integrated
14:22:02 <jaosorior> mwhahaha: well, the patch does say POC in the title. I assumed weshay and iranzo meant to show how it works.
14:22:05 <weshay> +1
14:22:06 <mwhahaha> then we'd like to have it work from in a container
14:22:11 <mwhahaha> cause that's what we have
14:22:14 <weshay> sure
14:22:15 <geneliu> Hello everyone, a quick question: Is containerized undercloud installation available on Queens? (I know it's the default of Rocky)
14:22:22 <mwhahaha> geneliu: no
14:22:27 <iranzo> jaosorior: I can show it :) what do you use? bjns? asciinema?
14:22:54 <jaosorior> iranzo: asciinema is fine :)
14:22:54 <weshay> flash cards
14:22:58 <jaosorior> lol
14:23:14 <mwhahaha> poster board diorama
14:23:21 <mwhahaha> must include at least 2 historical figures
14:23:34 <mwhahaha> weshay may be used as 1 of the figures
14:23:36 <iranzo> jaosorior: then https://asciinema.org/a/169814 should work
14:23:56 <iranzo> for later processing I would just run and get the json or report to console the 'failed' tests
14:24:16 <iranzo> internally it uses 'priority' which is the likelyhood of a test failing being bringing down your environment
14:24:21 <iranzo> and can be also be filtered based on it
14:24:29 <jaosorior> weshay: so, the CI team would help with the packaging/containerization of citellus?
14:24:34 <iranzo> and tests are 'info', 'skipped' 'ok' or 'failed'
14:25:02 <weshay> so first steps would be to package and containerize?
14:25:02 <iranzo> and this is for the old-group processing https://asciinema.org/a/170429
14:25:18 <iranzo> (now just outputs a json to make it more easily consumible basd on the information generated)
14:25:22 <geneliu> thanks for the answer, mwhahaha!
14:25:52 <jaosorior> weshay: yeah.
14:26:20 <rook> Trying to deploy rocky with OVN, and getting :   resources.ServiceChain: Property error: resources[43].properties: Property DockerOvnMetadataImage not assigned
14:27:06 <mwhahaha> rook: you're missing the ovn metadata container from the prepare (also we're in a meeting)
14:27:07 <rook> Where must this get defined -- and why isn't it defined in the environment file passed ?
14:27:20 <rook> erm
14:27:21 <rook> looking
14:28:03 <iranzo> any other question about the tool? something I missed?
14:28:22 <openstackgerrit> Alex Schultz proposed openstack/tripleo-quickstart-extras master: Revert "Revert "Add ability to have dlrn build all the packages at once""  https://review.openstack.org/603406
14:28:38 <jaosorior> iranzo: not from my side. I like it though
14:28:56 <iranzo> there's a recording from devconf.cz in youtube
14:28:58 <iranzo> let me find uri
14:29:08 <iranzo> https://www.youtube.com/watch?v=SDzzqrUdn5A&t=1257s&index=1&list=LLyqRUm2tl7NOBlSL4Gz0e_Q
14:29:22 <jaosorior> #link https://www.youtube.com/watch?v=SDzzqrUdn5A&t=1257s&index=1&list=LLyqRUm2tl7NOBlSL4Gz0e_Q
14:29:31 <iranzo> and project uri
14:29:36 <iranzo> #link https://citellus.org
14:29:44 <iranzo> #link https://github.com/citellusorg/citellus
14:29:54 <openstackgerrit> Alex Schultz proposed openstack/tripleo-quickstart-extras master: Revert "Revert "Add ability to have dlrn build all the packages at once""  https://review.openstack.org/603406
14:29:57 <jaosorior> iranzo: thanks
14:30:03 <iranzo> jaosorior++ to you
14:30:03 <weshay> iranzo, is this tool mostly used w/ tirpleo?
14:30:09 <weshay> tripleo
14:30:16 <iranzo> weshay: no, it can be used even outside triple-O
14:30:29 <weshay> I'll catch up later
14:30:33 <weshay> thanks iranzo++
14:30:35 <iranzo> and has little dependencies so if properly written, the bash scripts for tests, coudl be run on any platfrom
14:30:47 <iranzo> we do use them even for openshift (reduced number of plugins)
14:30:58 <iranzo> general systems with services like firewall, containers, clock sync, etc
14:31:09 <iranzo> it's pretty generic as the project itself runs the plugins
14:31:19 <iranzo> and each plugin 'decides' if have or not to run based on the requirements
14:31:38 <iranzo> think for example of something checking galera db status, if the package/process is not there, the plugins skips itself
14:32:00 <iranzo> so can be used for testing the deployed status or even infra for other projects
14:32:25 <iranzo> weshay++
14:32:50 <jaosorior> lets move to the next topic in the agenda
14:32:54 <jaosorior> #topic Workflow for wrapping register, introspect and provide
14:32:58 <jaosorior> jrist: ^^
14:33:43 <jaosorior> akrivoka: ^^
14:34:50 <jrist> yeah so
14:34:53 <jrist> this was proposed last year
14:34:56 <jrist> this time. ;)
14:35:02 <jrist> it was recently abandoned due to age
14:35:12 <jrist> we're just wondering if this has priority or what
14:35:32 <jrist> because it really didn't get many reviews or attention, despite asking
14:35:42 <jrist> maybe akrivoka can chime in
14:36:08 <jrist> and maybe someone like dtantsur or bfournie
14:37:09 <jaosorior> jrist: sure, feedback from them, and if we can get d0ugal to look at it again for the mistral side of things, it would be good.
14:38:24 <jrist> ok so I am bringing it up here because it has been difficult getting feedback from everyone
14:38:28 <jaosorior> jrist: this would be shared by the CLI and the UI, right?
14:38:35 <jrist> that is definitely the purpose
14:39:22 <jaosorior> Added myself as a reviewer; I'll give it a check, but would sure hope that dtantsur and d0ugal would look at it as well.
14:40:10 <jaosorior> jrist: thanks for bringing it up
14:40:31 <jaosorior> #topic Squad status
14:40:33 <jaosorior> ci
14:40:35 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-ci-squad-meeting
14:40:37 <jaosorior> upgrade
14:40:39 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-upgrade-squad-status
14:40:41 <jaosorior> containers
14:40:43 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-containers-squad-status
14:40:45 <jaosorior> integration
14:40:47 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-integration-squad-status
14:40:49 <jaosorior> ui/cli
14:40:51 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-ui-cli-squad-status
14:40:53 <jaosorior> validations
14:40:55 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-validations-squad-status
14:40:57 <jaosorior> networking
14:40:59 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-networking-squad-status
14:41:01 <jaosorior> workflows
14:41:03 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-workflows-squad-status
14:41:05 <jaosorior> security
14:41:07 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-security-squad
14:41:09 <jaosorior> edge
14:41:11 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-edge-squad-status
14:42:13 <jaosorior> So, from the security squad side, we'll be working on reviving the patches that restrict SSH access for the overcloud (namely https://review.openstack.org/#/c/582437/ and https://review.openstack.org/#/c/582436/ )
14:42:31 <jaosorior> other than this, not a lot to share
14:42:41 <jaosorior> any other squad that would like to share some highlights?
14:42:48 <slagle> it seems 1400UTC thursday will be a good time for the edge squad meeting
14:43:01 <slagle> i'll send an update to the ML, and let's plan to meet this thursday
14:43:13 <jaosorior> slagle++
14:45:11 <jaosorior> any other updates from other squads?
14:45:38 <weshay> jaosorior, ci notes are summed up in the etherpad
14:45:48 <jaosorior> great, thanks!
14:46:05 <jaosorior> #topic bugs & blueprints
14:46:08 <jaosorior> #link https://launchpad.net/tripleo/+milestone/rocky-rc2
14:46:10 <jaosorior> #link https://launchpad.net/tripleo/+milestone/stein-1
14:46:12 <jaosorior> For Stein we currently have 28 blueprints open in Launchpad.
14:46:14 <jaosorior> Bugs: 12 rocky-rc2, 772 (+32) stein-1.  103 (0) open Storyboard bugs.
14:46:16 <jaosorior> #link https://storyboard.openstack.org/#!/project_group/76
14:47:03 <mwhahaha> we have a whole bunch of alert bugs open
14:47:12 <mwhahaha> would be nice to get those addressed this week
14:47:37 <jaosorior> they're all assigned to folks, so hopefully they do get addressed :)
14:48:21 <jaosorior> #topic projects releases or stable backports
14:48:30 <mwhahaha> we're going to cut rc2 this week
14:48:42 <mwhahaha> which if nothing major is wrong, will be the ga for rocky
14:49:37 * fultonj hopes to land https://review.openstack.org/#/q/topic:bug/1769769+(status:open+OR+status:merged) in rocky
14:49:43 <mwhahaha> so if there are any major blockers for rocky, please raise them now
14:50:16 <jaosorior> mwhahaha: well, TLS everywhere is broken for rocky. Hope to get support for owalsh (and maybe beagles) on that.
14:50:21 <openstackgerrit> Ronelle Landy proposed openstack/tripleo-quickstart-extras master: Resolve get_build_command output before container_build_id  https://review.openstack.org/602734
14:51:01 <beagles> mwhahaha: there may be some openvswitch upgrade from queens to rocky as well - looking into this right now
14:51:02 <mwhahaha> k those will likely need to follow up after GA
14:51:27 <beagles> mwhahaha: it won't affect things until we have a 2.10 package though
14:51:33 <mwhahaha> k
14:52:37 <jaosorior> #topic specs
14:52:40 <jaosorior> #link https://review.openstack.org/#/q/project:openstack/tripleo-specs+status:open
14:52:54 <jaosorior> it's a good time to review specs folks!
14:54:06 <jaosorior> #topic open discussion
14:54:11 <fultonj> standalone installer works w/ ceph; docs patch https://review.openstack.org/#/c/602710
14:54:17 <jaosorior> Anything else folks want to bring up to the meeting?
14:54:18 <weshay> nice
14:54:21 <weshay> fultonj++
14:54:26 <jaosorior> fultonj: nice!
14:54:35 <weshay> FYI.. ci folks will be on irc to help, chat etc
14:54:49 <weshay> we may also be on bluejeans..
14:55:11 <jaosorior> weshay++
14:55:17 <marios> 7050859455 weshay community call next
14:55:56 <fultonj> is there a plan to replace some scenario ci jobs with stand alone versions?
14:56:11 <fultonj> i remember the topic came up at PTG but doesn't sure if there's a squad with a todo list for it
14:56:55 <marios> fultonj: right i dont think we've planned the work items or assigned to anyone yet
14:57:02 <marios> fultonj: but there was no opposition at ptg at least
14:57:29 <mwhahaha> i think we'll do that after we get a fedora28 standalone going
14:57:39 <fultonj> mwhahaha: ok, that makes sense
14:57:41 <marios> fultonj: so i guess tripleo ci team will at least be involved there but it would likely require input from other squads too
14:57:42 <mwhahaha> it's part of further optimizations, we've got some other hurdles first
14:57:48 <mwhahaha> like tempest on standalone (still not merged)
14:59:41 <weshay> stupid mirrors
14:59:56 <jaosorior> Anything else folks want to bring up?
15:00:32 <jaosorior> Alright! thanks for joinin!
15:00:34 <jaosorior> #endmeeting