Tuesday, 2020-03-17

*** miloa has quit IRC00:04
*** cshen has joined #openstack-ansible00:21
*** cshen has quit IRC00:25
*** cshen has joined #openstack-ansible00:28
*** cshen has quit IRC00:32
*** versionsix has quit IRC00:39
*** tosky has quit IRC00:46
*** nicolasbock has quit IRC01:04
*** boldo has joined #openstack-ansible02:15
*** rh-jelabarre has quit IRC02:35
*** fghaas has joined #openstack-ansible04:13
*** cshen has joined #openstack-ansible04:56
*** udesale has joined #openstack-ansible04:57
*** cshen has quit IRC05:01
*** cshen has joined #openstack-ansible05:12
*** cshen has quit IRC05:17
*** evrardjp has quit IRC05:35
*** evrardjp has joined #openstack-ansible05:36
*** cshen has joined #openstack-ansible06:01
*** cshen has quit IRC06:05
*** gchamoul has quit IRC06:10
*** gchamoul has joined #openstack-ansible06:10
*** cshen has joined #openstack-ansible06:17
*** cshen has quit IRC06:21
*** cshen has joined #openstack-ansible06:23
*** cshen has quit IRC06:27
*** cshen has joined #openstack-ansible07:15
*** ahosam has joined #openstack-ansible07:27
*** miloa has joined #openstack-ansible07:30
*** versionsix has joined #openstack-ansible07:56
*** raukadah is now known as chandankumar07:58
*** DanyC has joined #openstack-ansible08:21
*** andrewbonney has joined #openstack-ansible08:26
*** bjolo has quit IRC08:34
*** DanyC has quit IRC08:37
*** ansmith has joined #openstack-ansible09:11
*** ansmith_ has quit IRC09:12
openstackgerritErik Berg proposed openstack/openstack-ansible stable/rocky: How to upgrade from xenial to bionic on rocky  https://review.opendev.org/71080309:14
*** maharg101 has joined #openstack-ansible09:16
*** tosky has joined #openstack-ansible09:18
*** DanyC has joined #openstack-ansible09:21
*** rpittau|afk is now known as rpittau09:38
*** threestrands has quit IRC09:56
*** DanyC has quit IRC09:56
*** DanyC has joined #openstack-ansible09:56
*** mgariepy has quit IRC10:55
*** nicolasbock has joined #openstack-ansible11:06
*** mgariepy has joined #openstack-ansible11:08
*** jbadiapa has joined #openstack-ansible11:19
*** pcaruana has quit IRC11:21
*** gshippey has joined #openstack-ansible11:30
*** rpittau is now known as rpittau|afk11:34
*** pcaruana has joined #openstack-ansible11:34
*** rpittau|afk is now known as rpittau|bbl11:34
*** nicolasbock has quit IRC11:34
*** nicolasbock has joined #openstack-ansible11:38
*** nicolasbock has quit IRC11:40
*** rh-jelabarre has joined #openstack-ansible12:05
*** DanyC has quit IRC12:38
*** DanyC has joined #openstack-ansible12:40
*** nicolasbock has joined #openstack-ansible12:42
*** rpittau|bbl is now known as rpittau12:51
*** udesale_ has joined #openstack-ansible12:53
*** udesale has quit IRC12:55
*** arxcruz|rover has quit IRC13:00
*** sshnaidm is now known as sshnaidm|afk13:02
*** arxcruz has joined #openstack-ansible13:02
*** arxcruz is now known as arxcruz|rover13:03
*** dave-mccowan has joined #openstack-ansible13:40
*** also_stingrayza is now known as stingrayza13:49
*** joshualyle has joined #openstack-ansible13:51
*** ahosam has quit IRC14:25
*** dwilde has joined #openstack-ansible14:28
*** ansmith has quit IRC14:28
*** ansmith_ has joined #openstack-ansible14:28
chandankumarnoonedeadpunk, Hello14:29
chandankumarnoonedeadpunk, when we are moving c7 master jobs to c8?14:30
noonedeadpunkchandankumar: So I think Ussuri should become upgrade release where both centos7 and centos8 will be present14:33
noonedeadpunkbut as for now centos8 support is not ready yet14:33
mnaserchandankumar, noonedeadpunk: i dont think ussuri can be the upgrade release14:36
mnaserrh is publishing packages only for train afaik14:36
mnaserc7 will not get ussuri packaging, chandankumar can confirm14:36
chandankumarnoonedeadpunk, it is related to this patch https://review.opendev.org/713397 wheere c7 job is failing due to python3 missing14:36
noonedeadpunkmnaser: so they won't do centos7 for ussuri?14:37
chandankumarmnaser, yes c8 has usseri and rest of them has c714:37
mnaserso i think train _is_ the transition release, so we'd have to bckport centos 8 support for ussuri14:37
chandankumarin tripleo land, we almost moved all ussuri jobs to c814:38
noonedeadpunkhm, kinda centos8 packages have been published for train the way after it's release14:38
noonedeadpunkEven the way after osa release14:38
chandankumarnoonedeadpunk, rdo team is working for c8 train, but tripleo team has not yet decided for train14:38
noonedeadpunkI mean that releasing c8 packages for train closer to the U release and not making c7 for U doesn't give normal upgrade for ppl14:40
noonedeadpunkbut yeh14:42
noonedeadpunkthat we have to backport all stuff to train which will eventually broke it at some point....14:42
*** ansmith_ has quit IRC14:43
*** ansmith has joined #openstack-ansible14:44
*** jbadiapa has quit IRC14:45
mnaserchandankumar: so the ideal way would be that we have c8 support in train so that folks can upgrade during train to centos 814:48
mnaserand then upgrade to ussuri14:48
jrosseri was spending time on centos8 but got the point i didnt understand yum/dnf stuff and had to stop14:50
*** sshnaidm|afk is now known as sshnaidm14:57
*** mkuf has joined #openstack-ansible15:04
*** mkuf__ has quit IRC15:06
*** mkuf has quit IRC15:08
*** CeeMac has joined #openstack-ansible15:11
CeeMacahoy hoy15:12
*** alvinstarr has quit IRC15:13
*** cshen has quit IRC15:23
mnaserjrosser: i started and i keep getting carried away into things15:26
*** cshen has joined #openstack-ansible15:29
CeeMacI don't suppose there is any documentation for configuring up custom container to run alongside OSA and be known in the inventory etc?15:31
*** pcaruana has quit IRC15:34
*** gyee has joined #openstack-ansible15:38
*** ahosam has joined #openstack-ansible15:43
*** dave-mccowan has quit IRC15:47
*** ahosam has quit IRC15:49
*** dave-mccowan has joined #openstack-ansible15:53
chandankumarjrosser, for c8, we can focus on dnf and ignore yum15:53
*** jralbert has joined #openstack-ansible15:55
noonedeadpunk#startmeeting openstack_ansible_meeting16:00
openstackMeeting started Tue Mar 17 16:00:26 2020 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: openstack_ansible_meeting)"16:00
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:00
noonedeadpunk#topic office hours16:00
*** openstack changes topic to "office hours (Meeting topic: openstack_ansible_meeting)"16:00
noonedeadpunko/16:00
jrossero/ hello16:06
jralbertHi all16:06
jrosserchandankumar: i still can't make dnf do what i want :)16:06
*** mkuf has joined #openstack-ansible16:08
noonedeadpunkSo, the question raised today was if we can backport and should backport new features to previous branches16:10
*** jbadiapa has joined #openstack-ansible16:10
noonedeadpunkSince we do need to backport centos8 to train, then prohibition for smaller patches (esp non breaking and not changing defaults) looks not logic16:11
noonedeadpunkjrosser: I can recall you've abandoned some of such backports lately16:11
jrosseryes we proposed a backport for os_keystone and OIDC which we shouldnt have16:12
noonedeadpunkAlso I think mnaser is not against of backporting patches that add new functionality to previous branches16:12
jrosserwrt centos 8 i'm not so sure16:13
jrosser*sooo* much change on master for all sorts of py3 things16:13
jralbertRunning a somewhat older release as we do, our site would be very appreciative of backports to older but still supported releases16:13
noonedeadpunkI have not fixed opinion on this as from one side it's convenient to be able to use things right now, but it some sort of risk imo16:14
guilhermespo/16:14
noonedeadpunkjrosser: yeah, that's true... But otherwise we won't have upgrade release for centos?16:14
jrosserjralbert: do you mean OSA things, or openstack itself?16:14
jralbertOSA things particularly, although openstack features backported would be lovely in some cases16:15
noonedeadpunkYeah, opensatck is pretty strict on backporting...16:15
jrosser^ that16:15
noonedeadpunkThe question is if we should stick to the same rules or we can step down from them from times to times16:15
mnaserSo I’ll clarify16:16
mnaserOpenstack is strict on backpprts if your project asserts that it follows the stable policy16:16
mnaserOSA does not actually make that assertion therefore if we were to backport a complete breaking change, it’s not nice, but it’s “okay”16:17
jralbertMy personal view is that OSA's best value is OSA itself, and while I'd love to get later-release openstack features without an upgrade, that's not as valuable to me as fixes in OSA itself being consistent back through supported releases where possible16:17
mnaserI think to me my policy is: “if X can take advantage of this without them affecting any other users because the default behaviour doesn’t change”16:18
mnaserThen that’s ok16:18
openstackgerritMerged openstack/openstack-ansible-os_placement master: Refactor memcached_servers  https://review.opendev.org/71325116:19
mnaserand yeah, like the oidc stuff merging is probably ok with me as long as it didn't change default behaviour16:19
mnaserand if it fundamentally broken then you get points to do whatever the heck you want to it :)16:20
noonedeadpunkOk, so we can backport new features unless it changes default behaviour.16:20
noonedeadpunkAnd we actually trying to avoid changing defaluts wherever possible16:20
openstackgerritMerged openstack/openstack-ansible-os_barbican master: Refactor memcached_servers  https://review.opendev.org/71322716:22
*** cshen has quit IRC16:27
mnasernoonedeadpunk: that's my opinion personally, that way, we're being pretty accomodating to operators but also not breaking our users16:27
openstackgerritMerged openstack/openstack-ansible-os_octavia master: Refactor memcached_servers  https://review.opendev.org/71324816:28
mnaserthoughts jralbert, jrosser16:28
mnaser?16:28
jralbertSounds perfect to me16:28
jrosseryeah - though i'd like to see more eyes on stuff to review16:29
openstackgerritMerged openstack/openstack-ansible-os_sahara master: Refactor memcached_servers  https://review.opendev.org/71325216:30
jrosserand in general some of the larger pieces of work could really use some co-development - there's two of us have had a stab but for various reasons it's stalled16:31
*** mkuf has quit IRC16:32
jrosserjralbert: were you looking to get more involved with work on OSA?16:33
openstackgerritMerged openstack/openstack-ansible-os_ironic master: Refactor memcached_servers  https://review.opendev.org/71323916:33
jralbertYes, our site would like to discuss how we can contribute to the project16:35
jrossermnaser: ^16:35
mnaserjralbert: sure!  i mean, all contributions are open, are you thinking of dedicating some times/resources or special areas you wanna get involved in?16:36
jralbertWell, we're very heavily invested in OSA as both an install/upgrade and operations tool, so our big priority is features around the OSA procedures themselves: scaling, rebuilding nodes, etc16:37
*** cshen has joined #openstack-ansible16:38
jralbertSo right now I'm sad about tags like nova-config not working Rocky; but I'd love to see some improvements to the docs as well, and to general operations support improvements16:39
jralbertAll that said, I want our site to help the project however it needs help; I know that all this stuff gets better if the overall workload can be spread out a bit16:39
jralbertWhat I'm interested in figuring out is what kinds of contributions you'd find useful, and rough idea of how many hours a week we can realistically contribute to that16:40
noonedeadpunkjralbert: tags are fixed in stein:)16:40
jralbertSo I saw :(16:40
jralbertStein's on our roadmap for sure, but we're a fairly big installation relative to our team size, so we can't move that fast16:41
noonedeadpunkit was too much of backport work to do, and not so many ppl cared about it... And now once rocky is EM...16:41
jralbertYep, I understand we're a bit behind the curve16:41
jralbertWe just got to Rocky in Novemver16:41
noonedeadpunkYeah, that's ok16:42
noonedeadpunkSo actually right now we have our hands mostly in supporting rather than bringing new features16:42
noonedeadpunkSo if you see any bugs, or feature missing - feel free to contribute it16:43
noonedeadpunkReally every help is appreciated16:43
*** cshen has quit IRC16:43
jralbertWell, the tags issue is a good example of this: I'm not sure how to make a contribution to improve that16:43
jralbertBut it breaks our workflow pretty badly16:43
noonedeadpunkAlso right now we ahve a lot of deprecated params in configs that needs cleaning up and more stuff...16:43
noonedeadpunkjralbert: at this point, when no releases to rocky can be done, it might be a bit late. But, you can try to backport topic https://review.opendev.org/#/q/static_imports16:45
noonedeadpunkafter we can make rocky bump and you can use stable/rocky isntead of some tag...16:46
mnaserjralbert: it just mostly needs effort for someone to go ahead and backport those changes and test them out.16:46
jralbertHm, okay16:46
noonedeadpunkbut we won't be able to release new tag because of EM16:46
jralbertI wonder if maybe our team should start out with triaging bugs as a way to get into the project and get the lay of the land16:47
noonedeadpunkonce you need reviews don't hesitate to ping cores here :p16:48
*** chandankumar is now known as raukadah16:48
noonedeadpunkoh, our launchpad nowadays... is a bit let down16:48
jralbertThere was a bit of concern from our management that untriaged bugs that hurt us badly might imply the project wasn't still being actively maintained16:48
noonedeadpunkbut help with it is really very appreiated16:49
jralbertOkay, well I think maybe that's how we'll start: some bug triage, and some proposed changes to help us out with things we'd like fixed in Rocky16:50
jralbertDoes that sounds reasonable to you?16:50
jrosserwe had huge success last time we did a bug squash day16:50
mnaserjrosser: i think some bug triage is helpful but mostly proposing changing is the _most_ valuable thing16:50
jrossermaybe nearly 100 dealt with in 24hours16:50
jrossermnaser: i guess that comment is for jralbert but i'd have to add that review effort has to be available to match contributions16:51
mnaserjrosser: i agree. i have personally not been very good at actively doing it, but i think if we maybe try to ping each other16:52
jralbertI hope that once we are a part of things for a while, we'll be able to contribute a team member that you'd be willing to include as a reviewer16:52
mnaserjralbert: i think we all would welcome new cores, we're not a picky bunch.  or i like to think at least :)16:54
jralbertSo there's two main contributors at my site, including me; my colleague has much more experience contributing to large open source projects as a core member, so I will encourage him to come here and introduce himself in the next few days. I will start out with bug triage and proposing backports. I think we can probably contribute 2-4 hours a week,16:55
jralbertbut I don't want to promise anything too firm just yet16:55
*** udesale_ has quit IRC16:57
jrosserjralbert: having some kind of always on irc presence is very handy - also outside the meeting times there is a shortened URL to the review dashbaord in the IRC topic, keeping a regular (daily?) view on that is a good way to keep across whats going on16:58
jrosserand thats the route in to start doing reviews, which anyone can leave a +1/-1 on16:58
jralbertOkay, that's where we'll get started17:00
jralbertWhen my colleague has got a freenode name I'll ask him to come by and introduce himself17:00
jrosserooh time is up17:08
jrosser#endmeeting17:08
*** openstack changes topic to "Launchpad: https://launchpad.net/openstack-ansible || Weekly Meetings: https://wiki.openstack.org/wiki/Meetings/openstack-ansible || Review Dashboard: https://bit.ly/2SAcGAn"17:08
openstackMeeting ended Tue Mar 17 17:08:37 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:08
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2020/openstack_ansible_meeting.2020-03-17-16.00.html17:08
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2020/openstack_ansible_meeting.2020-03-17-16.00.txt17:08
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2020/openstack_ansible_meeting.2020-03-17-16.00.log.html17:08
openstackgerritMerged openstack/openstack-ansible-os_manila master: Refactor memcached_servers  https://review.opendev.org/71324217:10
*** rpittau is now known as rpittau|afk17:10
jralbertThanks for the chat today, looking forward to helping out!17:11
openstackgerritMerged openstack/openstack-ansible-os_magnum master: Refactor memcached_servers  https://review.opendev.org/71324117:18
mnaserjrosser, jralbert : sure please have them come in!17:18
jralbertQuite a few of the open and higher-importance bugs are very old (2+ years) and apply to releases that are now way past support (Ocata, etc). Is it fair game to close these?17:21
noonedeadpunkI'd say yes... But still maybe worth having a brief look as we might still have them not fixed17:25
jralbertAnd do I have the permission to actually modify ticket states, or do I need to ask one of you to do so?17:26
noonedeadpunkmnaser: ^?17:29
noonedeadpunkif it was up to me, I'd probably say yes17:34
*** evrardjp has quit IRC17:35
*** evrardjp has joined #openstack-ansible17:36
*** gshippey has quit IRC17:40
*** maharg101 has quit IRC17:44
noonedeadpunksince we eded up that backports are ok, jrosser you can probably restore https://review.opendev.org/#/c/710758/ ?17:45
*** maharg101 has joined #openstack-ansible17:46
jrosserthat adds fields to defaults17:46
jrosserbut it looks like it handles the case where the new field is undefined17:47
jrosseris anyone doing federation?17:47
*** burkhard has joined #openstack-ansible17:49
*** fghaas has left #openstack-ansible17:52
noonedeadpunkit add defaults but don't change it I guess...18:03
noonedeadpunklike we check here https://review.opendev.org/#/c/710758/1/tasks/main.yml if it's defined18:03
noonedeadpunkrather than suggest that it is18:03
noonedeadpunkso it shouldn't break things theoretically....18:04
noonedeadpunkalso can you take a look at https://review.opendev.org/#/q/owner:%22Erik+Berg%22+status:open+branch:master ?18:09
noonedeadpunkI'm not so big expert but it looks fair?18:09
ebbexnoonedeadpunk: thanks, it's mostly needed for rocky. and/but with those in place we managed to get our production env up to stein.18:13
ebbex(xenial/rocky -> bionic/rocky -> bionic/stein)18:15
noonedeadpunkyeah, it's needed for rocky, but as these patches are applicable for master as well we have to merge master first18:22
noonedeadpunkafter that backports to rocky18:22
noonedeadpunk(as repo_build is not the case since stein)18:23
noonedeadpunkjralbert let's say you can. If you're not sure in smth - feel free to ping us here and ask18:23
jralbertWill do, I'll be cautious18:24
*** pcaruana has joined #openstack-ansible18:27
*** burkhard has quit IRC18:35
*** jralbert has quit IRC18:35
*** DanyC has quit IRC18:44
openstackgerritDmitriy Rabotyagov (noonedeadpunk) proposed openstack/openstack-ansible-os_magnum stable/train: Add ability to create COE template  https://review.opendev.org/71351118:46
openstackgerritDmitriy Rabotyagov (noonedeadpunk) proposed openstack/openstack-ansible-os_magnum stable/train: Add ability to create COE template  https://review.opendev.org/71351118:47
openstackgerritDmitriy Rabotyagov (noonedeadpunk) proposed openstack/openstack-ansible-os_magnum stable/train: Add ability to create COE template  https://review.opendev.org/71351118:47
*** Adri2000 has quit IRC18:53
*** Adri2000 has joined #openstack-ansible18:55
*** waxfire8 has joined #openstack-ansible18:57
*** waxfire has quit IRC18:57
*** waxfire8 is now known as waxfire18:57
*** rh-jlabarre has joined #openstack-ansible19:00
*** rh-jelabarre has quit IRC19:02
mnaserjrosser: honestly if anyone isn't and it's pretty broken in your opinion im just in favour of fixing it19:02
mnaserif anyone comes and complains19:02
mnaserthey can submit a patch too19:02
mnaser:)19:02
jrosseri think it's all OK for SAML, just no support for OIDC at all right now19:03
jrosserbut yes, progress is good :)19:03
mnaserid like to one day be able to use oidc19:03
mnaserbut there's things ahead of that19:03
*** andrewbonney has quit IRC19:06
*** waxfire has quit IRC19:07
*** waxfire has joined #openstack-ansible19:08
*** waxfire has quit IRC19:13
*** waxfire has joined #openstack-ansible19:14
*** rh-jlabarre has quit IRC19:15
*** rh-jelabarre has joined #openstack-ansible19:21
*** openstackgerrit has quit IRC19:33
*** mloza has joined #openstack-ansible19:56
*** macz_ has joined #openstack-ansible20:06
*** DanyC has joined #openstack-ansible20:23
*** openstackgerrit has joined #openstack-ansible20:42
openstackgerritMerged openstack/openstack-ansible-os_heat master: Refactor memcached_servers  https://review.opendev.org/71323420:42
*** joshualyle has quit IRC20:52
*** DanyC has quit IRC20:55
*** DanyC has joined #openstack-ansible20:57
*** idlemind has joined #openstack-ansible21:16
*** ahosam has joined #openstack-ansible21:54
*** ahosam has quit IRC21:54
*** prometheanfire has quit IRC22:01
*** omiday has joined #openstack-ansible22:14
*** omiday has joined #openstack-ansible22:15
*** dwilde has quit IRC22:25
*** noonedeadpunk has quit IRC22:29
*** omiday has quit IRC22:35
*** macz_ has quit IRC23:01
*** macz_ has joined #openstack-ansible23:02
*** macz_ has quit IRC23:16
*** DanyC has quit IRC23:34
*** DanyC has joined #openstack-ansible23:35
*** tosky has quit IRC23:38
*** miloa has quit IRC23:50

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