16:13:40 #startmeeting openstack_ansible_meeting 16:13:42 Meeting started Tue Jan 22 16:13:40 2019 UTC and is due to finish in 60 minutes. The chair is jrosser. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:13:43 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:13:45 The meeting name has been set to 'openstack_ansible_meeting' 16:13:48 Woot:) 16:13:53 thanks jrosser 16:13:56 o/ everyone 16:13:59 :) thanks jrosser 16:14:03 Then #topic roll call:) 16:14:04 \o/ 16:14:19 I'm helping:) 16:14:22 #topic roll call 16:14:29 o/ 16:14:38 sorry i have no clue here 16:14:52 No prob, the bot I know:) 16:15:00 jrosser: you're doing great :) 16:15:08 o/ 16:15:09 o/ 16:15:13 \o/ 16:15:14 cloudnull, DimGR, d34dh0r53, hughsaunders, b3rnard0, palendae, odyssey4me, serverascode, rromans, erikmwilson, mancdaz, _shaps_, BjoernT, claco, echiu, dstanek, jwagner, ayoung, prometheanfire, evrardjp, arbrandes, scarlisle, luckyinva, ntt, javeriak, spotz, vdo, jmccrory, alextricity25, jasondotstar, admin0, michaelgugino, ametts, bgmccollum, darrenc, JRobinson__, colinmcnamara, thorst, adreznec, eil397, 16:15:14 qwang,nishpatwa_, cathrichardson, drifterza, hwoarang, cshen, ullbeking, mnaser, nicolasbock, jrosser, cjloader, antonym, dcdamien 16:15:15 \o 16:15:33 So whenever you want to put a bug up do #link change a topic is #topic 16:15:34 o/ 16:15:40 \o 16:15:51 CeeMac https://www.freedesktop.org/software/systemd/man/systemd-journal-remote.service.html systemd-journal-remote is just receiver, pusher part should be something other 16:15:53 And we all ran our first meeting, you've got an easy crowd here:) 16:15:55 I need to submit PRs and bug reports, but there are deployments making me mad 16:16:04 #topic highlights from last week 16:16:16 Sadly I don't much highlights from last week 16:16:20 in the wiki 16:16:36 anything big which happened last week that is worth mentioning? 16:16:53 o/ 16:17:18 Pretty quiet week I believe 16:17:20 odyssey4me: an upgrade job passed? thats pretty cool 16:17:23 ostackz, yep. the way i understand it, systemd-journal-upload should be running on the other hosts and configured to send to the log_hosts (systemd-journal-remote) 16:17:32 I am not sure it is shareable tempest runned using os_tempest in tripleo job http://logs.openstack.org/00/627500/65/check/tripleo-ci-centos-7-standalone-os-tempest/198ae77/logs/undercloud/var/log/tempest/stestr_results.html.gz 16:17:46 ostackz, think it should be configured by this https://github.com/openstack/openstack-ansible/blob/master/playbooks/infra-journal-remote.yml 16:17:52 there is one still needs to be fixed https://review.openstack.org/#/c/627782/4 not sure if it is an upgrade issue or a tempest issue 16:18:12 chandankumar: CeeMac guilhermesp could we keep all those conversations for open discussion please? 16:18:14 ok - onward if theres nothing else? 16:18:23 jrosser: is trying to have a meeting in here :p 16:18:31 jrosser: onwards! 16:18:34 #topic bug triage 16:18:42 #link 16:19:03 you can just paste the first line of each bug there 16:19:16 like this: 16:19:19 #link https://bugs.launchpad.net/openstack-ansible/+bug/1812543 16:19:20 Launchpad bug 1812543 in openstack-ansible "Ceph production example in openstack-ansible: devices definition missing" [Undecided,New] 16:19:26 #link https://bugs.launchpad.net/openstack-ansible/+bug/1812543 16:20:05 ok on this one... 16:20:17 evrardjp, sorry, i'll pipe down 16:21:01 part of the issue here is that the ceph example config is really just indicative 16:21:18 and also doesnt get tested 16:21:37 CeeMac: hehe, its fine to talk, but wait for the appropriate topic during meeting time :) 16:21:45 jrosser: agreed 16:21:51 is that a hard requirement? 16:22:03 it's also up to the deployer to read ceph-ansible bits I guess 16:22:11 but it's maybe worth pointing out? 16:22:36 also there is a choice between external vs. OSA deployed ceph and that config probably addresses neither of those cases 16:22:48 yup 16:22:58 in the past I used to define a different user_variables...like a user_ceph_variables.yml. But I think worth it to document and offer the option for the user to add the configs in user_variables 16:23:11 I think it's worth mentioning this conversation in the bug 16:23:28 and I'dmark the bug as confirmed 16:23:35 agreed 16:23:46 for severity I'd say it prevents ppl from deploying and is not really user friendly so I'd put that in medium 16:23:59 we need to refactor this page 16:24:49 guilhermesp for simplicity in documentation, we stick to referring to user_variables.yml - it helps to be consistent 16:24:56 and it's less confusing 16:25:00 i cant set severity it seems 16:25:08 advanced users will understand that more can be used 16:25:17 makes sense odyssey4me 16:25:30 we need to signpost what the options are 16:25:54 https://bugs.launchpad.net/openstack-ansible/+bug/1812541 16:25:55 Launchpad bug 1812541 in openstack-ansible "Ceph production example in openstack-ansible: cidr_networks not found" [Undecided,New] 16:25:59 ^ this is the same thing 16:26:05 yup 16:26:08 jrosser what's your launchpad ID? 16:26:18 So close as duplicate 16:26:46 jrosser I see jrosser & jonathan-rosser 16:26:49 odyssey4me: "Jonathan Rosser (jrosser)" in the top right of launchpad 16:28:31 jrosser ok, you should now be able to change bugs 16:28:58 is there a proper way to make duplicate? 16:29:45 https://bugs.launchpad.net/openstack-ansible/+bug/1812245 16:29:46 Launchpad bug 1812245 in openstack-ansible "Config Template doesn't respect variable names sections" [Undecided,New] 16:30:06 'Mark as duplicate' on the top right 16:30:35 that sounds like a nasty templating bug 16:30:47 I would not be surprised of the issue there 16:31:01 odyssey4me: cheers got it 16:32:12 Kevin Carter (cloudnull) proposed openstack/openstack-ansible master: Fix journal remote playbook https://review.openstack.org/632505 16:32:21 ok, we should probably assign this one if it's 'nasty bug' 16:32:54 CeeMac ostackz ^ - noticed https://pasted.tech/pastes/ebbdb7ea6b5f48b125b2bfa01830e703a3d68057 - looks like the service was not running as expected. 16:33:05 * cloudnull goes back to lurking 16:33:40 any takers? 16:34:40 https://pasted.tech/pastes/0049908c08a574a116b54aa714ed769672350538.raw - now i see my remote journals 16:34:45 I don't have the time to take it jrosser 16:34:53 but it sounds like high 16:34:55 * cloudnull reading the bug 16:35:53 jrosser assign it to me, ill have a crack at that 16:35:57 maybe this weekend 16:36:01 cloudnull: cheers 16:36:10 https://bugs.launchpad.net/openstack-ansible/+bug/1812185 16:36:12 Launchpad bug 1812185 in openstack-ansible "cannot create volume from image" [Undecided,New] 16:36:21 jrosser: don't forget #link :) 16:36:31 you can copy paste the whole line, super easy :p 16:36:39 ok :) 16:37:20 #link https://bugs.launchpad.net/openstack-ansible/+bug/1812185 16:37:21 Launchpad bug 1812185 in openstack-ansible "cannot create volume from image" [Undecided,New] 16:37:24 :) 16:37:42 interesting, would that be following a sha bump? 16:38:19 I am curious why it would start to appear, would it have passed upstream testing without noticing? 16:38:29 I think this needs further triage 16:38:56 "To enable the Block Storage services to create a new volume by cloning Image- Volume, set the following options in the DEFAULT section of the cinder.conf file" 16:39:12 ^ 16:39:33 jrosser: where did you see that? 16:39:41 https://docs.openstack.org/cinder/latest/admin/blockstorage-volume-backed-image.html 16:39:44 I did have a """"problem"""" like this 16:39:53 """""fixed"""" reading the docs hahah 16:40:04 guilhermesp: do you have a patch for this? 16:40:11 not yet =/ 16:40:17 I have a bunch to submit 16:40:23 guilhermesp: that sounds like a valid patch then 16:40:34 this bug can be assigned to me 16:40:39 great, thanks 16:40:42 jrosser: should we mark this as confirmed, medium, and assign guilhermesp? 16:40:53 guilhermesp: thanks! 16:40:58 np! 16:41:08 Yep 16:41:31 #link https://bugs.launchpad.net/openstack-ansible/+bug/1811826 16:41:32 Launchpad bug 1811826 in openstack-ansible "Octavia api fails to start because libpython2.7 is missing" [Undecided,New] 16:42:53 slightly surprised we pass tests if that is missing 16:42:56 jrosser: could that have appeared after our relatively recent cleanups? 16:43:06 jrosser: yup worrying 16:43:20 the patch which removes a ton from the lxc base image is not merged 16:43:21 maybe it's not properly tested in the role 16:43:30 oh I see 16:43:35 I thought it was 16:44:00 no there is work to do in tempest before that can happen 16:44:10 it's plausable that changes in the openstack_hosts role removed things which osoctavia relied on being there 16:45:21 Chandan Kumar proposed openstack/openstack-ansible-os_tempest master: [DNM] public subnet allocation pool https://review.openstack.org/632508 16:45:27 odyssey4me: oh I see 16:46:16 theres nothing merged in octavia for quite a long time, something could easily have gone awry here 16:46:25 openstack-hosts is an important enough role to maybe try to fanout or periodic test of other roles would be good 16:47:47 i'll poke at this 16:47:48 I guess it needs further testing/validation ? 16:48:22 evrardjp I'm working on that, yeah - once we've moved over to using the integrated build for all tests, that'll happen automatically. 16:48:24 it's only 12 minutes remaining, should we just to open discussion? 16:48:37 just move* 16:48:47 or simply move 16:48:49 yes 16:48:54 #topic open discussion 16:49:12 first (redrobot) New roles for HSM Client Software management 16:49:15 o/ 16:49:32 hello o/ 16:49:47 Heya! So I talked to spotz and mnaser about this not too long ago. 16:50:10 is that linked to ansible-hardening? 16:50:12 I'm part of Barbican core, and we've been working on automating the Barbican deployment using HSMs as the backend. 16:50:23 k 16:50:37 * evrardjp listens carefully 16:50:43 We've got a couple of ansible roles that we would like to add to the openstack-ansible umbrella 16:50:52 each role targets a specific HSM 16:50:56 * cloudnull is also listening carefully :) 16:51:02 #link https://github.com/dmend/ansible-role-atos-hsm 16:51:12 #link https://github.com/dmend/ansible-role-thales-hsm 16:51:34 We're using those to install the required HSM Client software on the nodes running barbican 16:51:48 We've already merged code into TripleO to make use of the roles 16:52:08 and we'd prefer them to be hosted in openstack-ansible instead of my personal github 16:52:21 redrobot: is it only for software,or also configuration of barbican? We'd like to separate those 16:52:36 the roles only do the client software configuration 16:52:42 the barbican bits are part of THT 16:52:51 (tripleo heat templates) 16:53:02 ok 16:53:15 I submitted the required changes to governance and openstack-infra 16:53:18 #link https://review.openstack.org/#/c/631324/ 16:53:21 oh great 16:53:24 #link https://review.openstack.org/#/c/631326/ 16:53:26 I guess mnaser should vote there 16:53:33 we're just waiting on +1s from mnaser 16:53:45 yep, I _think_ I've done all the legwork 16:54:06 Also, I'd welcome any feedback on the roles to get them up to your standards if they're not there yet. 16:54:27 I think it would make sense if you were core on those roles 16:54:41 as you have knowledge we don't have 16:54:47 agreed. I think the openstack-infra patch adds a new review team 16:54:56 if you need more ppl to help you you should tell mnaser 16:55:07 the idea was to add myself and probably Ade Lee (barbican PTL) to the team as well as your core team 16:55:26 I go over and review there when I have time but yeah they were looking for more folks in Vancouver 16:55:47 redrobot: both the roles will be discovered by tripleo quickstart as setup.cfg confirms that 16:56:14 on infra as a whole that is 16:56:30 I see 16:57:03 Anyway, I mainly wanted to get these patches on your radar 16:57:31 redrobot: cool, thanks 16:57:36 thank you! 16:57:38 thanks redrobot 16:57:44 ok, lets see whats next.... 16:57:46 second (anyone) how are things going with mitogen? folks using it? 16:57:56 It seems a good idea to collaborate on those redrobot 16:57:57 * cloudnull wants to use it 16:58:12 cloudnull: I tried, but had an issue, cannot remember something with lxc I think 16:58:14 i'm using it all the time outside OSA, and seems OK 16:58:16 cloudnull: I don't have cycle to continue to work with dw 16:58:30 but you might have to fiddle a bit 16:58:39 jrosser: is now more experienced there: ) 16:58:43 reloated - https://review.openstack.org/#/c/591236/ 16:58:45 there was a whole heap of bugfixes commited this week 16:58:47 ** related 16:59:05 and it feels *exceedingly* close to being able to to end-end OSA deploy with it 16:59:34 the only thing missing is wiring OSA physical_host into the mitogen_via setting 17:00:31 chandankumar: tempest things are still on the 'open discussion' list - is there anything we need to cover? 17:00:31 ok. 17:00:57 I think it's time to wrap up for today 17:01:08 pabelanger I wonder if the issue with lxc was something fixed in the recent patch release ? 17:01:19 * cloudnull needs to find more time to tinker 17:01:19 jrosser: you can do that with the static inventory that's shipped by default in osa 17:01:43 jrosser: https://github.com/openstack/openstack-ansible/blob/master/inventory/inventory.ini 17:01:44 jrosser: openstack-ansible-functional-centos-7 is broken currnetly may be something wrong with public network cidr or allocation pool 17:02:02 I have to run 17:02:03 for example 17:02:11 ttyl everyone, and thanks jrosser for chairing 17:02:11 ok - any more meeting things? 17:02:27 #endmeeting