Tuesday, 2020-03-03

*** diablo_rojo has quit IRC00:01
*** mattw4 has quit IRC00:05
*** ykatabam has quit IRC00:06
*** ykatabam has joined #openstack-meeting00:08
*** slaweq has joined #openstack-meeting00:11
*** slaweq has quit IRC00:17
*** tetsuro has joined #openstack-meeting00:42
*** tetsuro has quit IRC00:47
*** tetsuro has joined #openstack-meeting00:47
*** diablo_rojo has joined #openstack-meeting00:47
*** jmasud has quit IRC00:53
*** jmasud has joined #openstack-meeting00:55
*** jgriffith has quit IRC01:10
*** jgriffith has joined #openstack-meeting01:10
*** slaweq has joined #openstack-meeting01:11
*** slaweq has quit IRC01:16
*** ijw has quit IRC01:25
*** jamesmcarthur has joined #openstack-meeting01:45
*** hyunsikyang has quit IRC01:54
*** ykatabam has quit IRC02:07
*** gyee has quit IRC02:08
*** slaweq has joined #openstack-meeting02:11
*** jamesmcarthur has quit IRC02:13
*** yamamoto has joined #openstack-meeting02:14
*** slaweq has quit IRC02:15
*** jamesmcarthur has joined #openstack-meeting02:21
*** mhen has quit IRC02:29
*** diablo_rojo has quit IRC02:33
*** enriquetaso has joined #openstack-meeting02:43
*** jamesmcarthur has quit IRC02:50
*** rcernin_ has joined #openstack-meeting02:52
*** jamesmcarthur has joined #openstack-meeting02:53
*** rcernin has quit IRC02:55
*** ykatabam has joined #openstack-meeting02:56
*** jamesmcarthur has quit IRC02:58
*** jamesmcarthur has joined #openstack-meeting03:04
*** enriquetaso has quit IRC03:05
*** slaweq has joined #openstack-meeting03:11
*** slaweq has quit IRC03:16
*** apetrich has quit IRC03:17
*** ykatabam has quit IRC03:23
*** ykatabam has joined #openstack-meeting03:26
*** ykatabam has quit IRC03:47
*** jamesmcarthur has quit IRC03:50
*** ykatabam has joined #openstack-meeting03:54
*** tashiromt has joined #openstack-meeting04:10
*** slaweq has joined #openstack-meeting04:11
*** ricolin has quit IRC04:15
*** slaweq has quit IRC04:17
*** bbowen has joined #openstack-meeting04:22
*** links has joined #openstack-meeting04:38
*** hyunsikyang has joined #openstack-meeting04:43
*** jmasud has quit IRC04:53
*** tashiromt has quit IRC04:53
*** jmasud has joined #openstack-meeting04:54
*** ociuhandu has joined #openstack-meeting04:55
*** masahito has joined #openstack-meeting04:56
*** ociuhandu has quit IRC04:59
*** jamesdenton has quit IRC05:03
*** jamesdenton has joined #openstack-meeting05:03
*** slaweq has joined #openstack-meeting05:11
*** slaweq has quit IRC05:16
*** rcernin_ has quit IRC05:24
*** ykatabam has quit IRC05:27
*** ykatabam has joined #openstack-meeting05:28
*** ykatabam has quit IRC05:31
*** ykatabam has joined #openstack-meeting05:32
*** ykatabam has quit IRC05:33
*** vesper has quit IRC05:34
*** vesper11 has joined #openstack-meeting05:37
*** macz_ has joined #openstack-meeting05:50
*** macz_ has quit IRC05:55
*** enriquetaso has joined #openstack-meeting06:06
*** igordc has joined #openstack-meeting06:09
*** slaweq has joined #openstack-meeting06:11
*** igordc has quit IRC06:13
*** slaweq has quit IRC06:16
*** dmacpher has quit IRC06:17
*** toabctl has quit IRC06:18
*** toabctl has joined #openstack-meeting06:22
*** lajoskatona has joined #openstack-meeting06:25
*** lajoskatona has left #openstack-meeting06:25
*** dmacpher has joined #openstack-meeting06:28
*** brinzhang has joined #openstack-meeting06:32
*** diablo_rojo has joined #openstack-meeting06:33
*** brinzhang_ has joined #openstack-meeting06:35
*** brinzhang has quit IRC06:38
*** brinzhang has joined #openstack-meeting06:40
*** brinzhang has quit IRC06:41
*** brinzhang has joined #openstack-meeting06:41
*** brinzhang_ has quit IRC06:43
*** brinzhang has quit IRC06:46
*** brinzhang has joined #openstack-meeting06:46
*** brinzhang has quit IRC06:48
*** brinzhang has joined #openstack-meeting06:49
*** enriquetaso has quit IRC06:51
*** maohongbo has joined #openstack-meeting06:56
*** brinzhang_ has joined #openstack-meeting06:59
*** brinzhang has quit IRC07:02
*** diablo_rojo has quit IRC07:09
*** slaweq has joined #openstack-meeting07:11
*** ykatabam has joined #openstack-meeting07:12
*** rcernin has joined #openstack-meeting07:13
*** ykatabam has quit IRC07:13
*** ykatabam has joined #openstack-meeting07:13
*** slaweq has quit IRC07:16
*** ijw has joined #openstack-meeting07:30
*** ricolin has joined #openstack-meeting07:33
*** keiko-k has joined #openstack-meeting07:42
*** e0ne has joined #openstack-meeting07:48
*** e0ne has quit IRC07:48
*** maciejjozefczyk has joined #openstack-meeting07:48
*** tpatil has joined #openstack-meeting07:51
*** keiko-k has quit IRC07:52
*** slaweq has joined #openstack-meeting07:52
*** keiko-k has joined #openstack-meeting07:54
*** maciejjozefczyk has quit IRC07:55
*** e0ne has joined #openstack-meeting07:57
*** bbowen has quit IRC07:57
*** bbowen has joined #openstack-meeting07:57
*** takahashi-tsc has joined #openstack-meeting08:02
*** yasufum has joined #openstack-meeting08:02
*** e0ne has quit IRC08:02
*** e0ne has joined #openstack-meeting08:03
*** e0ne has quit IRC08:05
*** bbowen has quit IRC08:08
*** bbowen has joined #openstack-meeting08:08
*** njohnston has quit IRC08:14
*** e0ne has joined #openstack-meeting08:17
*** nitinuikey has joined #openstack-meeting08:19
*** pbhole has joined #openstack-meeting08:21
*** yamamoto has quit IRC08:22
*** manuvakery has quit IRC08:27
*** yamamoto has joined #openstack-meeting08:27
*** tesseract has joined #openstack-meeting08:30
*** masahito has quit IRC08:37
*** masahito has joined #openstack-meeting08:38
*** rpittau|afk is now known as rpittau08:41
*** rcernin has quit IRC08:41
*** ralonsoh has joined #openstack-meeting08:42
*** masahito has quit IRC08:42
*** maohongbo1 has joined #openstack-meeting08:47
*** maohongbo has quit IRC08:47
*** maohongbo1 is now known as maohongbo08:47
*** brinzhang has joined #openstack-meeting08:47
*** brinzhang has quit IRC08:49
*** brinzhang has joined #openstack-meeting08:49
*** brinzhang_ has quit IRC08:50
*** brinzhang has quit IRC08:51
*** brinzhang has joined #openstack-meeting08:52
*** imalinovskiy has joined #openstack-meeting08:53
*** brinzhang has quit IRC08:53
*** brinzhang has joined #openstack-meeting08:54
*** jmasud has quit IRC08:55
*** jmasud has joined #openstack-meeting08:56
*** masahito has joined #openstack-meeting08:58
*** keiko-k has quit IRC08:58
*** maohongbo1 has joined #openstack-meeting08:58
*** maohongbo has quit IRC08:59
*** maohongbo1 is now known as maohongbo08:59
*** apetrich has joined #openstack-meeting09:00
*** maohongbo has quit IRC09:03
*** ociuhandu has joined #openstack-meeting09:06
*** e0ne has quit IRC09:12
*** ociuhandu has quit IRC09:12
*** ociuhandu has joined #openstack-meeting09:15
*** yasufum has left #openstack-meeting09:21
*** tpatil has quit IRC09:23
*** tesseract has quit IRC09:25
*** nitinuikey has quit IRC09:25
*** tesseract has joined #openstack-meeting09:26
*** Lucas_Gray has joined #openstack-meeting09:29
*** rubasov has joined #openstack-meeting09:36
*** ociuhandu has quit IRC09:37
*** yamamoto has quit IRC09:42
*** ijw has quit IRC09:43
*** ijw_ has joined #openstack-meeting09:43
*** ociuhandu has joined #openstack-meeting09:45
*** ykatabam has quit IRC09:50
*** ociuhandu has quit IRC09:58
*** yamamoto has joined #openstack-meeting09:58
*** rcernin has joined #openstack-meeting10:05
*** brinzhang_ has joined #openstack-meeting10:11
*** brinzhang has quit IRC10:15
*** ykatabam has joined #openstack-meeting10:20
*** ykatabam has left #openstack-meeting10:22
*** brinzhang has joined #openstack-meeting10:24
*** ociuhandu has joined #openstack-meeting10:25
*** ociuhandu has quit IRC10:27
*** brinzhang_ has quit IRC10:27
*** ociuhandu has joined #openstack-meeting10:27
*** rcernin has quit IRC10:37
*** masahito has quit IRC10:38
*** rcernin has joined #openstack-meeting10:38
*** takahashi-tsc has quit IRC10:38
*** ociuhandu has quit IRC10:39
*** brinzhang_ has joined #openstack-meeting10:42
*** brinzhang_ has quit IRC10:43
*** brinzhang_ has joined #openstack-meeting10:44
*** brinzhang has quit IRC10:45
*** brinzhang_ has quit IRC10:45
*** brinzhang_ has joined #openstack-meeting10:46
*** pbhole has quit IRC10:48
*** brinzhang has joined #openstack-meeting11:01
*** Lucas_Gray has quit IRC11:01
*** brinzhang_ has quit IRC11:03
*** ociuhandu has joined #openstack-meeting11:12
*** rpittau is now known as rpittau|bbl11:17
*** trident has quit IRC11:46
*** david-lyle has joined #openstack-meeting11:47
*** dklyle has quit IRC11:47
*** trident has joined #openstack-meeting11:49
*** Lucas_Gray has joined #openstack-meeting11:50
*** rcernin has quit IRC11:52
*** Lucas_Gray has quit IRC11:55
*** tetsuro has quit IRC11:57
*** imalinovskiy_ has joined #openstack-meeting12:01
*** imalinovskiy has quit IRC12:03
*** imalinovskiy has joined #openstack-meeting12:08
*** enriquetaso has joined #openstack-meeting12:08
*** imalinovskiy_ has quit IRC12:09
*** nicolasbock has joined #openstack-meeting12:14
*** Lucas_Gray has joined #openstack-meeting12:20
*** brinzhang has quit IRC12:21
*** brinzhang has joined #openstack-meeting12:22
*** brinzhang_ has joined #openstack-meeting12:26
*** brinzhang has quit IRC12:29
*** Lucas_Gray has quit IRC12:31
*** masahito has joined #openstack-meeting12:40
*** bbowen has quit IRC12:42
*** masahito has quit IRC12:44
*** bbowen has joined #openstack-meeting12:46
*** yamamoto has quit IRC12:52
*** jmasud has quit IRC12:53
*** jmasud has joined #openstack-meeting12:55
*** brinzhang has joined #openstack-meeting13:03
*** rpittau|bbl is now known as rpittau13:04
*** yamamoto has joined #openstack-meeting13:06
*** ociuhandu has quit IRC13:06
*** brinzhang_ has quit IRC13:06
*** ociuhandu has joined #openstack-meeting13:07
*** Lucas_Gray has joined #openstack-meeting13:11
*** e0ne has joined #openstack-meeting13:12
*** ociuhandu has quit IRC13:12
*** enriquetaso has quit IRC13:13
*** brinzhang_ has joined #openstack-meeting13:17
*** yamamoto has quit IRC13:29
*** moguimar has quit IRC13:32
*** moguimar has joined #openstack-meeting13:33
*** njohnston has joined #openstack-meeting13:37
*** zigo has quit IRC13:58
ricolin#startmeeting automation14:00
openstackMeeting started Tue Mar  3 14:00:15 2020 UTC and is due to finish in 60 minutes.  The chair is ricolin. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: automation)"14:00
openstackThe meeting name has been set to 'automation'14:00
*** eharney has joined #openstack-meeting14:02
*** e0ne has quit IRC14:03
ricolinfor information14:03
ricolinWe already got some nice work going on with auto-scaling CI env14:03
ricolinhttps://review.opendev.org/#/q/status:open+branch:master+topic:autoscaling-with-monasca14:03
ricolincurrently heat+monasca14:03
ricolinshould do the some for heat+telemetry as well if time allows14:04
ricolinHope we can get autoscaling cross project gate accepted in heat and monasca before end of this cycle14:05
ricolinnothing going on for self-healing I believe14:05
*** links has quit IRC14:05
ricolinthat's all for update from my side14:06
ricolin#endmeeting14:06
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:06
openstackMeeting ended Tue Mar  3 14:06:29 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/automation/2020/automation.2020-03-03-14.00.html14:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/automation/2020/automation.2020-03-03-14.00.txt14:06
openstackLog:            http://eavesdrop.openstack.org/meetings/automation/2020/automation.2020-03-03-14.00.log.html14:06
*** witek has joined #openstack-meeting14:07
witekhello14:07
ricolinwitek, :)14:08
witekhow are you doing?14:08
ricolinMy schedule is all mess up due to COVID-1914:09
ricolinwhich including my honeymoon:(14:09
ricolinbesides that everything is doing great:)14:09
* ricolin still working on reschedule part of the honeymoon so it might still happening14:10
witektaking into account the circumstances, honeymoon will be more fun later...14:10
ricolinwitek, agree14:10
ricolinHow's everything there14:11
witekthe number of cases in Germany increases but it's not comparable to China14:11
witekwe've got 170 cases currently14:11
witekin Europe Italy is most affected14:12
ricolinhope everything under control now?14:12
witekyes, seems so14:13
ricolinand hope no new cases in Munich14:13
witekI guess 3 new cases since last week14:13
*** enriquetaso has joined #openstack-meeting14:14
ricolinIf that number can stay for two weeks will be more solid I think14:14
witekyeah14:15
ricolinTaiwan got few cases grow since this two weeks, it's now 41 cases totally14:15
ricolinand all seems under control14:15
witekis your everyday life somehow affected, like closed shops or restaurants?14:16
ricolinNot really, people mostly wearing mask when in public but not open space, so things going just fine.14:18
*** yamamoto has joined #openstack-meeting14:18
witekfingers crossed14:18
*** lpetrut has joined #openstack-meeting14:18
ricolinI guess that's some lesson we learn when SARS happened14:18
ricolinBTW regarding  the auto-scaling CI, I will take another deep look to make sure the test is reasonable to use, but generally I think it's ready for heat and monasca to cross gating with it14:21
ricolinhttps://review.opendev.org/#/c/709278/14:21
witekthanks, haven't seen that one14:22
witekwhen will this job be triggered?14:23
*** yamamoto has quit IRC14:23
*** senrique_ has joined #openstack-meeting14:24
witekdo you intend to run it additionally to the job in Heat repo?14:24
*** enriquetaso has quit IRC14:27
ricolinwitek, yeah, I think so14:30
ricolinsince the test env are all different,14:30
witeknice, we can then add this job to our checks14:31
witekin Monasca14:31
ricolinIf we have good confident with the job, we can put it in check14:31
*** zigo has joined #openstack-meeting14:32
ricolinwitek, let me find some time tomorrow to collect feedback from other heat members14:33
witek+!14:33
witek+114:33
ricolinIf everything goes well, we can start adopt that job for both team14:33
*** links has joined #openstack-meeting14:37
*** links has quit IRC14:37
*** brinzhang has quit IRC14:39
*** brinzhang has joined #openstack-meeting14:40
*** ijw_ has quit IRC14:41
*** maciejjozefczyk has joined #openstack-meeting14:46
*** artom has joined #openstack-meeting14:51
*** shintaro has joined #openstack-meeting14:56
ricolin#startmeeting multi_arch15:01
openstackMeeting started Tue Mar  3 15:01:10 2020 UTC and is due to finish in 60 minutes.  The chair is ricolin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: multi_arch)"15:01
openstackThe meeting name has been set to 'multi_arch'15:01
ricolin#topic roll call15:01
*** openstack changes topic to "roll call (Meeting topic: multi_arch)"15:01
ricolino/15:01
* ricolin knows that jeremyfreudberg will not join this time15:02
*** ociuhandu has joined #openstack-meeting15:03
ricolinWe already make some productive discussion earlier today, so feel free to take a look15:05
ricolin#link http://eavesdrop.openstack.org/meetings/multi_arch/15:05
ricolin:)15:06
ricolin#endmeeting15:06
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:06
openstackMeeting ended Tue Mar  3 15:06:31 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/multi_arch/2020/multi_arch.2020-03-03-15.01.html15:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/multi_arch/2020/multi_arch.2020-03-03-15.01.txt15:06
openstackLog:            http://eavesdrop.openstack.org/meetings/multi_arch/2020/multi_arch.2020-03-03-15.01.log.html15:06
*** masahito has joined #openstack-meeting15:10
*** brinzhang_ has quit IRC15:11
*** masahito has quit IRC15:14
*** jamesmcarthur has joined #openstack-meeting15:23
*** lpetrut has quit IRC15:23
*** ociuhandu has quit IRC15:39
*** tesseract has quit IRC15:43
*** tesseract has joined #openstack-meeting15:53
*** shintaro has quit IRC15:58
*** senrique_ has quit IRC16:02
*** mattw4 has joined #openstack-meeting16:11
*** jamesmcarthur has quit IRC16:23
*** jamesmcarthur has joined #openstack-meeting16:23
*** e0ne has joined #openstack-meeting16:25
*** gyee has joined #openstack-meeting16:27
*** jmasud has quit IRC16:29
*** brinzhang_ has joined #openstack-meeting16:29
*** jamesmcarthur has quit IRC16:30
*** brinzhang has quit IRC16:32
*** rubasov has quit IRC16:38
*** macz_ has joined #openstack-meeting16:39
*** macz_ has quit IRC16:44
*** macz_ has joined #openstack-meeting16:47
*** senrique_ has joined #openstack-meeting16:50
*** jamesmcarthur has joined #openstack-meeting16:54
*** maciejjozefczyk has quit IRC16:55
*** imalinovskiy has quit IRC16:56
*** tesseract has quit IRC16:58
*** jamesmcarthur has quit IRC17:03
*** rpittau is now known as rpittau|afk17:10
*** brinzhang has joined #openstack-meeting17:19
*** ociuhandu has joined #openstack-meeting17:21
*** brinzhang_ has quit IRC17:22
*** ociuhandu_ has joined #openstack-meeting17:40
*** ociuhandu has quit IRC17:43
*** ociuhandu_ has quit IRC17:44
*** diablo_rojo has joined #openstack-meeting17:57
*** igordc has joined #openstack-meeting17:59
*** Lucas_Gray has quit IRC18:12
*** witek has quit IRC18:17
*** yamamoto has joined #openstack-meeting18:21
*** jamesmcarthur has joined #openstack-meeting18:22
*** yamamoto has quit IRC18:26
*** senrique_ has quit IRC18:58
*** senrique_ has joined #openstack-meeting18:59
*** vishalmanchanda has quit IRC18:59
clarkbanyone else here for the infra meeting?19:00
clarkbwe shall get started momentarily19:01
ianwo/19:01
clarkb#startmeeting19:02
openstackclarkb: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'19:02
clarkbbah19:02
clarkb#startmeeting infra19:02
openstackMeeting started Tue Mar  3 19:02:09 2020 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: infra)"19:02
openstackThe meeting name has been set to 'infra'19:02
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2020-March/006605.html Our Agenda19:02
clarkb#topic Announcements19:03
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:03
clarkbfungi is largely afk this week as are ttx. They have meeting topics that we'll probably go through quickly as a result19:03
clarkb#topic Actions from last meeting19:03
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:03
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-02-25-19.01.txt minutes from last meeting19:03
clarkbWe have one action from the last meeting. ttx was to write an xwiki spec. This happend and we'll talk about it in the next section of the meeting19:04
clarkb#topic Specs19:04
*** openstack changes topic to "Specs (Meeting topic: infra)"19:04
clarkbwe'll start with the xwiki spec.19:04
clarkb#link https://review.opendev.org/#/c/710057/ xwiki for wikis19:04
clarkbThis hasn't gotten any reviews yet, but there was good discussion on IRC (in the meeting and out) last week. If you've got thoughts on this your reviews are much appreciated19:05
clarkbfrickler and corvus in particular seemed to have some good initial thoughts19:05
clarkbNext is the cleanup of python tooling on our CI images.19:05
clarkb#link https://review.opendev.org/#/c/709579/ Cleaning up python dev tools on our CI images.19:05
clarkbinfra-root I think this one is ready to go up for approval19:05
clarkbis there any objection to that? many of you have already reviewd it. Looks like we are missing fungi though.19:06
* diablo_rojo sneaks into the back of the room19:06
clarkbmaybe hold off until fungi can ack or nack?19:06
clarkbor do you think we have had sufficient input? ianw mordred you've both been involved in this one so your thoughts on it would be great19:06
clarkb(as far as proceeding, I Think you've both acked the review)19:07
clarkbhrm we may not have quorum here today (yet). I'll wait a couple more minutes to see if others are able to drop in19:08
ianwpersonally it's probably sufficient, as we can stage it in without affecting prodcution19:08
clarkbianw: thats a good point.19:09
corvusi'm here, just quiet19:09
fungiyeah, sorry, i can try to take a look in a bit19:09
clarkbok why don't we say end of clarkb business thursday? that should give fungi time to fit review into travel schedule19:09
clarkbI'm reluctant to prolong this as we just had another virtualenv issue this week19:10
clarkbI think making progress on this spec will be a g ood thing for the transition from python2 to python3 as that happens around us19:10
clarkbNext up is the website acitivty sites spec19:11
clarkb#link https://review.opendev.org/#/c/709236/ Website activity stats19:11
clarkbfungi: I think proper reivew on this one from you would be great. But its also less urgent imo19:11
fungii'm probably mostly okay with both of those since they were written as an upshot of discussions i was involved in, but i'll check to make sure they reflect what i remember19:11
clarkbfungi: ok, if you manage to review this one by EOD thurday I'll approve it too if there aer no new concerns, but if not I think we can pick it up next week19:12
clarkbThank you to everyone that has reviewed the specs19:12
clarkb#topic Priority Efforts19:13
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:13
clarkb#topic OpenDev19:13
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:13
clarkbThere was some excitement around opendev governance recently. The initial change I pushed to openstack/governance merged, but then was reverted19:13
clarkbmnaser has pushed a new change for that and is trying to solicit more feedback19:13
clarkb#link https://review.opendev.org/#/c/710020/ Split OpenDev out of OpenStack governance.19:13
clarkbit seems that there is new concern over what opendev would be post split and one of the suggestions is that it could be a pilot project under the OSF19:14
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2020-March/006603.html OpenDev as OSF pilot project19:14
*** AJaeger has joined #openstack-meeting19:14
fungii'm still not convinced that's necessary, but willing to entertain if it makes some stakeholders more comfortable19:15
*** Shrews has joined #openstack-meeting19:15
clarkbjbryce wrote ^ to start that conversation. I'm not opposed initially, but have asked for more information on what would be required of us to make that happen as well as how we see the pilot project criteria applying to opendev19:15
clarkbIf you've got thoughts on that I'm happy to hear them either directly or on the mailing list. Will do my best to stay on top of that input19:15
corvusi also don't object but19:16
corvusi also am not sure we need to block on that19:16
corvusi don't think we're being as successful as we would like to be in growing the opendev community apart from openstack-infra19:17
corvusand i think further delay is not going to help that19:17
clarkbcorvus: I agree. Personally I thought what we had was sufficient with the understanding that we are making incremental changes19:17
clarkbbut I'm also not sure we can assert that more strongly that we have without using the "fork" work19:17
corvusso it would be nice if we could make progress before everyone burns out on the idea19:17
clarkb*word19:17
clarkb++19:17
clarkbcorvus: I think that is good feedback for mnaser and the rest of the TC19:18
clarkbI'll try to pass it along19:18
corvus2 years is a long time :)19:19
mordredo/19:19
*** eharney has quit IRC19:19
mordred(sorry - was letting myself be distracted by mailing list threads)19:19
*** masahito has joined #openstack-meeting19:20
clarkbcorvus: maybe you can send a short response to jbryce? Then I can make sure the TC is trackign that thread?19:20
clarkbIf not I can try to summarize your thoughts and send it instead19:20
mordredI agree with the above re: don't object and also don't need to block19:20
corvusclarkb: sure i'll reply19:21
clarkbthank you19:21
*** ralonsoh has quit IRC19:21
clarkbOn the operational side of things we have master builds of gitea working now19:22
mordredI started looking yesterday evening at the template diffs19:22
mordredbut then EODd19:22
clarkbwe need to check for template changes and probably don't want to deploy "master" because templates and other things can change under us. But if we wanted to we could likely deploy gitea with the commit cache in the near future19:22
mordredmight allow us to provide feedback to lunny19:23
clarkbmordred: one thing I wondered about is how difficult it would be to deploy a specific gitea backend with a different docker image19:24
clarkbmordred: I think that would require us to use a different docker compose config file template but should be doable.19:24
clarkbthen we could monitor memory use and measure performance improvement/impact19:24
mordredclarkb: I mean - we could put in an ansible variable with an image tag19:24
*** masahito has quit IRC19:24
mordredand then set different host_var overrides19:25
mordredso I thnik it would be pretty easy19:25
clarkbah ya19:25
clarkbmaybe doing that real soon now is worthwhile with a single backend19:25
clarkband if there are problems we can remove it from the haproxy config19:25
*** mattw4 has quit IRC19:25
mordredyeah. we might want to put in a sha pin to the override-checkout and add a different tag name on the output image19:26
mordredso that we could bump the sha we're working with later19:26
clarkbmy biggest concern is the gitea team does seem to curate releases for when they think the software is ready. They also put together pretty comprehensive release notes. W'd lack that in this case19:26
mordredyeah19:26
clarkbOk we can discuss further outside the meeting. Lets move on19:27
clarkb#topic Update Configuration Management19:27
*** openstack changes topic to "Update Configuration Management (Meeting topic: infra)"19:27
clarkbmordred: are there updates on gerrit images? Possibly related to jeepyb and bazel and stuff19:28
mordredwell - it all broke again19:28
mordredbut this: https://review.opendev.org/#/c/711072/ should fix the builds19:29
mordredother than that - next up on gerrit is manage-projects19:29
mordredturns out I missed that when doing review-dev - so solving it is the next task19:30
mordredI think we should split manage-projects from the service stuff so we can retire remote-puppet-git and instead just have a playbook that applies project-config changes to all the places19:30
mordredbut I'm not all the way to having a stepwise plan for doing any of that in a sane way19:31
clarkbremote-puppet-git?19:31
mordredyeah - that's the playbook that currently runs things on review19:31
clarkboh right19:32
mordredthat's spread across gerrit and gitea and does the gitea service stuff as well19:32
corvusmordred: so we'd pull the project-management stuff out of puppet?19:32
clarkbrefactoring the puppet and ansible to be just cleaner ansible19:32
mordredcorvus: more that I think we shoudlnt' copy the structure in the ansible replacement19:33
corvusah ok19:33
mordredand I *think* it might be easier to do that as part of adding manage-projects support19:33
mordredto the review-dev ansible19:33
corvusmordred: other than run manage-projects, what else is involved?19:34
mordredwe clone project-config, then we copy of a bunch of files around to different places19:34
corvusfor gerrit?  what files?19:34
corvusthe acls?19:35
mordredprojects.yaml, projects.ini, acls dir19:35
mordredit's also possible it's easier than my brain is making it right now19:35
mordredbut the puppet-project-config indirection is ... challenging to follow19:35
corvusmordred: well, i agree with "the review playbook should run manage projects" which seems the overall goal19:36
corvushrm, it has to interact with gitea though, right?19:37
mordredwell -I'm not actually convinced in the fullness of time that that should be the goal. I think having a service-review and a service-prjojects playbook might serve us better19:37
mordredyeah19:37
clarkbmordred: corvus: and order the playbooks to enforce the current ordering we get in a single playbook?19:37
mordredso I think we really want service-review.yaml that deals with gerrit config managemnt, service-gitea that deals with teh same for gitea, and service-project-config that applies project-config to the gitea and gerrit services19:37
clarkbaha19:37
clarkbthat makes sense to me19:37
mordredBUT - that might be too big of a change for this effort19:37
mordredor it might be the _easier_ way to do this effort19:38
corvusmordred: it looks like remote_puppet_git is basically already that, it just runs puppet on review19:38
mordredcorvus: yeah - but puppet on review runs manage-projects19:38
corvusyes19:38
corvusmordred: okay, so service-review should not run manage-projects.  remote_puppet_git should be updated to run manage-projects.  then it should be renamed.19:38
mordredcorvus: yeah19:39
*** raildo_ has joined #openstack-meeting19:39
*** raildo has quit IRC19:39
corvusmordred: i think we could just do that as part of the switch19:39
corvusto do it earlier means extracting that from puppet19:39
mordredyeah. and actually - thanks, this has been helpful to my brain19:40
corvusto do it as part of the switch may slightly entend the period where we can't create new projects, but i'm not worried about that19:40
mordredyeah19:40
corvuss/entend/extend/19:40
AJaegerwe have currently very few project creation requests...19:40
AJaegerso, unless there's a deadline - like a summit - we can easily block a few days or even more than a week19:41
clarkb++19:41
mordredcool19:41
clarkbespecially if we communicate it in advance19:41
clarkb"do this now or wait a while"19:41
corvusi'd expect the worst case to be like a day :)19:41
mordredI also looked BRIEFLY at the idea of "replace manage-projects with some ansible like gitea"19:42
mordredbut I think that should be a followup - there's a few potential gotchas19:42
clarkbI've still got test changes up for manage projects which can help us limp it along too19:42
mordredthere are a few things jeepyb is taking care of though that we no longer care about19:42
AJaegercorvus: a day? not a problem...19:42
clarkband then transition that into testing for new tooling19:42
clarkbas a time check we've got ~17 minutes left. Should we continue on to the next several subjects?19:43
mordredyeah. I'm good on this one if y'all are19:43
clarkb(I doubt we'll solve the refactor here)19:43
corvus++19:43
clarkb#topic General Topics19:43
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:43
clarkbfungi: I don't think there has been any new progress on the wiki puppetry. If you are still here can you confirm?19:44
funginope19:44
clarkbok19:44
fungi(no progress, and i'm not here to confirm)19:44
clarkbianw: static.openstack.org -> static.opendev.org transition19:45
clarkbianw: are we basically done at this point?19:45
ianwjust cleanup now19:45
ianware we still ok with removing logs.openstack.org dns19:45
clarkbianw: our rotation time period was 30 days prior to switching to swift, we transitioned to swift well over 30 days ago. I think I'm good19:45
clarkbwe could potentially have logs.openstack.org redirect to zuul.openstack.org/builds19:46
clarkbbut I doubt even that is necessary19:46
ianwthere's some puppet cleanup https://review.opendev.org/#/q/status:open+topic:static-services19:46
clarkb#link https://review.opendev.org/#/q/status:open+topic:static-services cleanup static.openstack.org now that all services are hosted by static.opendev.org19:46
ianwright, in the spec we would remove the dns, just checking we're still ok with it19:46
clarkbI'm ok with it19:46
ianwfiles.openstack.org and static-old.openstack.org are now idle19:46
AJaegerlet's remove them as well19:47
AJaegerianw: but first change https://opendev.org/zuul/zuul-jobs/src/branch/master/test-playbooks/base-roles/validate-host.yaml#L13 ;)19:48
AJaegerthat's the only reason to keep files.o.o19:48
*** maciejjozefczyk has joined #openstack-meeting19:48
ianwheh well actually files.openstack.org is a CNAME now to static ... i should of said the host files02.openstack.org19:49
ianwbut agree we could change that for completeness19:49
*** eharney has joined #openstack-meeting19:50
clarkbalright sounds like that may be it on static19:52
clarkbNow for the last subject19:52
clarkbIRC channel usage.19:52
clarkbfrickler brings up that we have redundant channels between #openstack-infra and #opendev and that we mirror bot events to both19:53
clarkbthinking about what corvus said before about how we've not effectively been building the opendev community much outside of openstack, maybe we should just transition channels sooner than later?19:53
AJaegerthat's one reason why I'm staying out of #opendev - there're only bots with the same information I saw elsewhere already19:53
clarkbfrickler: ^ I'm not sure if you are still around today, but happy to hear if you have specific thoughts too19:54
AJaegerWith the opendev split, we split repos into openstack and opendev - should we do the same for notifications?19:54
fricklerI don't have a solution, but my main concern are duplicated bot msgs, yes19:54
corvusif we're going to start using #opendev, i think we're going to need to really decide to do it as a team and make an effort19:55
AJaegerSo, whatever stays in openstack , goes to #openstack-infra, what moves out goes to #opendev?19:55
clarkbcorvus: ya and have a flag day and if questions pop up that are opdnev specific in -infra really push people to move19:55
clarkbAJaeger: yes I think that makes sense19:55
clarkbwe might mirror project-config on the short term since it still handles both19:55
AJaegerI volunteer to propose a change...19:55
AJaeger(if there is merit)19:55
corvusthe main thing i worry about with channels is that if we're mising important information in one, then it becomes less useful19:55
corvusi'm happy to have the list reduced, but we should be careful19:56
corvuslike openstack/project-config should probably go to both right now.19:56
clarkbcorvus: agreed19:56
AJaegerI'm fine duplicating a few projects - but not *all* of them19:56
corvusand if we remove zuul/* from one, we should remove it from the other too19:56
fricklermaybe we need to move completely, redirect #openstack-infra to #opendev19:56
fricklerlike with other retired channels19:56
clarkbfrickler: maybe we can consider that option if -infra goes idle after an initial split?19:57
clarkbI'm worried we can't accurately predict now if there would still be openstack specific chatter in -infra or not19:57
fricklercause for most infra issues that pop up, I think its difficult to say whether they are opendev or not19:57
clarkbthis is true19:57
clarkbusually we have to investigate before things fall one way or the other19:57
fricklerand "customers" can tell even less19:58
clarkbI'll have to think on that a bit more I guess. My initial thought was definitely to keep both19:58
clarkband accept a period where we'll have to manage transition and point people in the correct location19:58
clarkbbut that is an excellent point about how this might be difficult19:58
corvusbut if every "my devstack-based job failed" question goes to #opendev, then i think that's going to turn off potential non-openstack contributors19:59
AJaegerlet's cleanup the channels - I'll first cleanup #opendev, then #openstack-infra...19:59
clarkbcorvus: ya19:59
clarkbso maybe we start with two channels (its easier to start there and go to one if we decide that works than it is to redirect and then unsplit later)19:59
clarkbfrickler: ^ do yu think that is an acceptable incremental state to be in?19:59
clarkb(also as a time check we are now at time. There is no meeting after us so we can finish this topic before ending the meeting)20:00
fricklersure, let's try and see where we end at20:00
clarkbAJaeger: ^ I think that means you can proceed with your planned changes20:01
AJaegerack20:01
clarkbIf there are other thoughts that come up on this subject feel free to discuss further in -infra or on the reviews20:01
clarkband with that I think we should let people eat dinner/lunch/breakfast20:01
clarkbthank you all20:01
clarkb#endmeeting20:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:01
openstackMeeting ended Tue Mar  3 20:01:44 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-03-03-19.02.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-03-03-19.02.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-03-03-19.02.log.html20:01
*** ociuhandu has joined #openstack-meeting20:10
*** ociuhandu has quit IRC20:15
*** Shrews has left #openstack-meeting20:21
*** AJaeger has left #openstack-meeting20:23
*** trident has quit IRC20:23
*** maciejjozefczyk has quit IRC20:23
*** maciejjozefczyk has joined #openstack-meeting20:24
*** trident has joined #openstack-meeting20:26
*** rmascena__ has joined #openstack-meeting20:26
*** raildo_ has quit IRC20:29
*** jamesmcarthur has quit IRC20:36
*** jamesmcarthur has joined #openstack-meeting20:37
*** jamesmcarthur has quit IRC20:38
*** senrique_ has quit IRC20:40
*** slaweq has quit IRC20:46
*** jonmills_nasa has joined #openstack-meeting20:51
*** oneswig has joined #openstack-meeting20:52
*** janders has joined #openstack-meeting20:57
*** jmasud has joined #openstack-meeting20:57
*** nicolasbock has quit IRC20:58
*** martial_ has joined #openstack-meeting20:59
martial_Hello friends21:00
oneswigGreetings21:00
oneswiglet us get on with the show!21:00
jandersg'day! :)21:00
jonmills_nasahowdy21:00
oneswigyou driving today martial_? :-)21:00
martial_one topic? sure21:01
*** jamesmcarthur has joined #openstack-meeting21:01
martial_#startmeeting scientific-sig21:01
openstackMeeting started Tue Mar  3 21:01:25 2020 UTC and is due to finish in 60 minutes.  The chair is martial_. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: scientific-sig)"21:01
openstackThe meeting name has been set to 'scientific_sig'21:01
martial_#chair oneswig21:01
openstackCurrent chairs: martial_ oneswig21:01
martial_Good day/evening/morning everybody and welcome to the 2020 March 3rd edition of the famous Scientific SIG weekly IRC meeting21:02
jonmills_nasagee...that openstack-discuss mailing list has been kinda wild lately, huh?21:02
oneswignot been following it recently - any specific threads?21:02
*** rbudden has joined #openstack-meeting21:02
jonmills_nasawell there's the debacle over the glance team rejecting the OSC client, in favor of python-glanceclient21:03
rbuddenhello21:03
oneswigI saw that go by21:03
oneswigwhy oh why?21:03
jonmills_nasamultiple governane questions from Mohammed Naser21:04
jandersg'day all21:04
jonmills_nasathe think about OpenDev splitting off from OpenStack?21:04
jonmills_nasajust curious what folks think about stuff like that21:04
martial_The OpenDev part, I think is not crazy21:05
martial_they had one during the past Summit (was it in Vancouver last year?)21:06
martial_no, Denver21:06
martial_will see what happens with the Open Infra shift21:07
martial_#topic UKRI cloud workshop21:08
*** openstack changes topic to "UKRI cloud workshop (Meeting topic: scientific-sig)"21:08
martial_Stig?21:08
*** igordc has quit IRC21:08
oneswigjonmills_nasa: that's quite a long thread... sorry was distracted21:08
*** igordc has joined #openstack-meeting21:08
oneswigI've been up to London, for https://cloud.ac.uk21:09
jonmills_nasayeah no worries, and i don't want to distract us if there's specific business.21:09
oneswigIt's an annual 1-day conference for the UK research sector on cloud compute.21:09
*** igordc has quit IRC21:10
oneswigIn recent years it has been an interesting bellweather for public vs private cloud (for example)21:10
jonmills_nasaso how's it looking for private cloud?21:11
oneswigOver recent years the presentation content has shown maturing content, in terms of the form cloud adoption is taking21:11
*** slaweq has joined #openstack-meeting21:11
oneswigWell, I don't know if there's an unbiased estimate of that but the presentation content covered a lot more private cloud than last time.21:11
*** igordc has joined #openstack-meeting21:12
oneswigSome promising presentations from a year ago on managing costs in public cloud had no follow-up this year, which was a pity.21:12
*** igordc has quit IRC21:12
oneswigAt the end, someone summed up along the lines of "I can't believe after all these years it's still a question of someone getting their credit card out"21:12
jonmills_nasaha21:13
martial_that last one seems strange ... of course compute requires money to run21:13
oneswigSome good presentations from CERN, Sanger, Vscaler/Genomics England - and our gang at StackHPC21:13
oneswigmartial_: more about the means than the money21:13
oneswigIt was also observed that in the whole schedule, there were zero public cloud user stories involving significant data.21:14
martial_🙌21:14
oneswig(as in volumes of data)21:14
jonmills_nasanot even archival data?  what's that arctic service they have....21:15
martial_agreed, volumes" of data is different from user to user21:15
martial_we have a 100TB use case but that is small21:15
oneswigThe hybrid story and the auto-cluster-deployment story - both looking strong21:15
*** slaweq has quit IRC21:16
oneswigjonmills_nasa: I think the access times for archival data make it only suitable for archive...21:16
jonmills_nasai've never understood the hybrid story, when storage is involved.  any efficiency gained in compute seems like it would be lost in data transfers21:16
oneswigI spoke in a session on controlled-access data - life sciences etc.  That got a good discussion going.21:16
oneswigjonmills_nasa: you're right, it only works if there's lots of compute to not very much data.21:17
martial_well there is a possible hybrid conversation: you ETL the data on the large cluster, push the dataset to be worked on to the public cloud and can then use specific compute components as needed to get the result21:17
martial_it is a fairly common exercise in data optimization21:18
martial_trick is that it requires some understanding of how to get to the result21:18
oneswigJohn, Pierre and Steve from our firm gave a highly compressed overview of autoscaling, reservations and preemption - in 15 minutes.21:18
martial_that is cool:)21:19
*** ijw has joined #openstack-meeting21:20
oneswigcollectively the fight against resource contention we termed "the coral reef cloud"21:20
martial_pretty but fragile?21:21
*** Lucas_Gray has joined #openstack-meeting21:22
oneswigThe analogy was the fight for space on the sea bed.21:22
oneswigOr perhaps "keep your friends close, and anenomes closer" perhaps? :-)21:22
jonmills_nasaugh21:22
oneswigsorry21:23
oneswigThis might be useful for a future hands-on conference workshop: https://www.instancehub.com/21:23
oneswigCurrently an academic's side project21:24
jonmills_nasaSSL error, won't load in chrome21:24
oneswigfunny, you're the second person to say that, seems to work for most21:25
martial_weird, works for me21:25
jonmills_nasamaybe it's my gov computer rejecting it21:25
martial_wish OpenStack passport would offer similar service21:25
oneswigmartial_: that would indeed be cool.21:26
*** jmlowe_ has joined #openstack-meeting21:26
martial_oh and do not forget to write an abstract for SuperComp Cloud for ISC :)21:27
oneswigThere were also some interesting benchmarks on Oracle bare metal cloud21:27
oneswigmartial_: thanks for the reminder!21:27
martial_(saw Mike join, just posting everywhere :) )21:27
jmlowe_excellent!21:28
jmlowe_10 min late, 20 min fiddling with my irc client21:29
jonmills_nasaall federal travel is in jeopardy at this moment FYI (due to coronavirus)21:29
jmlowe_this makes me very unhappy21:29
martial_not entirely surprised that said21:29
jmlowe_although it does seem to have increased the availability of upgrades21:29
jandershaha21:30
oneswigDefinitely a move not to shake hands at today's event.  (I only forgot a couple of times)21:31
jonmills_nasaand, assuming rbudden and I would be allowed to Vancouver in June for OpenDev....we don't even know if that's the correct conference to attend, or if it should be the Summit in Berlin in Oct (which may be yet harder to attend)21:32
rbuddenyeah, travel at the moment is interesting… even just heading on-base next week21:33
martial_Vancouver is PTG only, no presentation21:33
oneswigThe way I see it, OpenDev could be a good opportunity to share knowledge from one deployment to another in a hands-on way.21:33
rbuddenbut as Jonathan mentioned we are actively looking at whether the OpenDev event or the Berlin Summit is the better option21:33
martial_the "Summit" is Berlin21:33
jmlowe_I'm leaning towards Berlin these days21:34
jonmills_nasaBerlin, being in Oct, may hopefully far away in time from this coronavirus mess, but it does fall in a new fiscal year, which is also messy for approvals.  but yeah21:35
martial_🤷21:35
martial_Stig anything else on the UKRI topic?21:36
oneswigI don't think so thanks martial_21:36
martial_we are already well into AOB :) so let's make it official after this21:37
martial_#topic SuperComp Cloud at ISC21:37
*** openstack changes topic to "SuperComp Cloud at ISC (Meeting topic: scientific-sig)"21:37
martial_Mike?21:37
jmlowe_um, yes, we need submissions21:37
jmlowe_https://sites.google.com/view/supercompcloud21:38
martial_2nd Workshop on Interoperability of Supercomputing and Cloud Technologies21:38
jmlowe_Extended Abstract Submission Deadline: March 20, 202021:39
oneswigThe "interoperability" part was only lightly covered last time... are there specific themes?21:39
jmlowe_There's 15 of them listed on the website21:39
jmlowe_can copy and paste if desired21:39
oneswigah, just saw that.21:40
jmlowe_It's quite broad, covers most anything that touches on cloudy and HPC type things21:40
jmlowe_right down to workforce development for these types of environments21:41
martial_Working on an abstract on our end21:41
jmlowe_the program committee is let's say friendly21:42
martial_and not for the topic everybody was waiting for :)21:42
martial_    #topic Spanish Inquisition21:42
martial_oops21:42
*** mattw4 has joined #openstack-meeting21:42
jmlowe_I was not expecting that21:42
martial_#topic AOB21:42
*** openstack changes topic to "AOB (Meeting topic: scientific-sig)"21:42
martial_got a few minutes it look like21:43
oneswigNobody expects the spanish inquisition! :-)21:45
jonmills_nasa@one21:45
martial_I see a couple people still awake :)21:45
jonmills_nasaoneswig we continue playing with monasca21:45
oneswigjonmills_nasa: daveholland from the Sanger was asking recently about CloudKitty21:46
jonmills_nasai'd say my general impression is that it feels more substantial than ceilometer.  i kinda dig it21:46
oneswigGood to hear it.  We find there's quite a bit of config you need to apply to make it useful - alarms etc.21:47
*** jmlowe__ has joined #openstack-meeting21:47
jonmills_nasaso just got monasca-agent working with multi-tenant support (there's docs for it....kinda buried).  hopefully can replace ceilometer-compute agents21:47
oneswigTrying to gather more helpful dashboards than the standard21:47
oneswigjonmills_nasa: just reminded me I have a patch up for that for monitoring unmounted disks (very helpful for Bluestore Ceph, for example)21:48
oneswigjust need to ... document and unit-test21:48
*** jmlowe_ has quit IRC21:48
jonmills_nasawhile monasca-agent can report on disk size (cinder volume size) for billing purposes, what it can't report on is the cinder volume_type, which makes it hard to bill more for faster disk vs slower or standard disk21:49
jonmills_nasaso i may still use the cinder-volume-audit cron script to send to ceilosca to monasca21:50
jmlowe__How's the data usage of monasca, looked like they were making all the same mistakes ceilometer made in the bad old days, last time I checked21:51
jmlowe__I remember a Mirantis writeup where a 100 node cluster would produce 6TB of ceilometer data per day21:51
jonmills_nasaumm...i just set an influxdb retention period and don't worry about it21:51
oneswigjonmills_nasa: unless you can get a hint from (eg) lsblk -o '+...', that kind of infrastructure data would have to come from outside the agent's scope.21:51
jmlowe__ah, ok, they are putting the measurements in influx and not mongodb21:52
oneswigjmlowe__: have a blog post in the wings on writing to Influxdb databases per tenancy, which helps a lot with that.21:52
jonmills_nasajmlowe__ correct, and I am also turning off unnecessary metrics21:52
jonmills_nasai.e. metrics I'll never bill on21:52
*** maciejjozefczyk has quit IRC21:52
*** ykatabam has joined #openstack-meeting21:53
*** jmasud has quit IRC21:53
jmlowe__that could be fun, billing only on unusual metrics21:53
oneswigbilling according to PID for example?21:53
jmlowe__compute is free, $100/per console session21:54
jonmills_nasaor billing for dropped tx packets on your tun device21:54
*** Lucas_Gray has quit IRC21:54
jmlowe__$1k per security group change21:55
martial_(5 minutes warning)21:55
jonmills_nasai'm done21:55
oneswigI knew there was something21:55
*** rcernin has joined #openstack-meeting21:56
oneswig#link metrics exported as an Oslo module https://review.opendev.org/#/c/704733/21:56
oneswigwe get similar data in "black box" fashion from HAProxy but this has the potential to be insightful on cloud scaling and performance issues.21:57
oneswigFrom the Large Scale SIG, there was a request for "scaling stories" to be added here - https://etherpad.openstack.org/p/scaling-stories21:58
martial_with that, we are reaching the end of our time21:58
oneswigWhat they are looking for is what broke, how it was observed, and how to fix/avoid it.21:59
oneswigThanks all21:59
martial_Thanks everybody21:59
martial_#endmeeting21:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"21:59
openstackMeeting ended Tue Mar  3 21:59:36 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-03-03-21.01.html21:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-03-03-21.01.txt21:59
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-03-03-21.01.log.html21:59
*** jonmills_nasa has quit IRC21:59
oneswigUntil next time!21:59
*** oneswig has quit IRC21:59
*** jmlowe__ has left #openstack-meeting22:01
*** jmasud has joined #openstack-meeting22:02
*** slaweq has joined #openstack-meeting22:11
*** jmasud has quit IRC22:11
*** jmasud has joined #openstack-meeting22:12
*** jmasud_ has joined #openstack-meeting22:14
*** slaweq has quit IRC22:16
*** jmasud has quit IRC22:17
*** rbudden has quit IRC22:17
*** jmasud_ has quit IRC22:24
*** jmasud has joined #openstack-meeting22:24
*** jamesmcarthur has quit IRC22:24
*** jmasud has quit IRC22:24
*** jamesmcarthur has joined #openstack-meeting22:27
*** jmasud has joined #openstack-meeting22:31
*** hyunsikyang__ has joined #openstack-meeting22:33
*** hyunsikyang has quit IRC22:37
*** jmasud has quit IRC22:39
*** mattw4 has quit IRC22:41
*** brinzhang_ has joined #openstack-meeting22:42
*** janders has quit IRC22:45
*** brinzhang has quit IRC22:45
*** mattw4 has joined #openstack-meeting22:47
*** kozhukalov has joined #openstack-meeting22:51
*** mattw4 has quit IRC22:53
*** jmasud has joined #openstack-meeting22:58
*** mattw4 has joined #openstack-meeting23:00
*** mattw4 has quit IRC23:03
*** jamesmcarthur has quit IRC23:06
*** slaweq has joined #openstack-meeting23:11
*** slaweq has quit IRC23:16
*** jamesmcarthur has joined #openstack-meeting23:16
*** jmasud has quit IRC23:17
*** rmascena__ has quit IRC23:18
*** jamesmcarthur has quit IRC23:20
*** masahito has joined #openstack-meeting23:21
*** masahito has quit IRC23:26
*** jamesmcarthur has joined #openstack-meeting23:32
*** jmasud has joined #openstack-meeting23:33
*** brinzhang has joined #openstack-meeting23:33
*** brinzhang_ has quit IRC23:36
*** jmasud has quit IRC23:39
*** jamesmcarthur has quit IRC23:53

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