Tuesday, 2019-07-23

*** gyee has quit IRC00:07
*** nurdie has quit IRC00:40
*** strobelight has joined #openstack-ansible00:45
*** strobelight_ has joined #openstack-ansible00:52
*** strobelight is now known as Guest3214900:52
*** strobelight_ is now known as strobelight00:53
*** Guest32149 has quit IRC00:56
*** TxGirlGeek has joined #openstack-ansible00:58
*** TxGirlGeek has quit IRC01:32
openstackgerritKevin Carter (cloudnull) proposed openstack/ansible-config_template master: Enhance the config_template comment parser  https://review.opendev.org/67217001:32
*** TxGirlGeek has joined #openstack-ansible01:50
*** TxGirlGeek has quit IRC01:54
openstackgerritKevin Carter (cloudnull) proposed openstack/ansible-config_template master: Enhance the config_template comment parser  https://review.opendev.org/67217002:18
*** BjoernT has joined #openstack-ansible02:32
*** BjoernT has quit IRC02:36
*** nurdie has joined #openstack-ansible02:40
*** BjoernT has joined #openstack-ansible02:41
*** nurdie has quit IRC02:45
*** BjoernT has quit IRC02:58
*** BjoernT_ has joined #openstack-ansible02:58
*** nurdie has joined #openstack-ansible03:04
*** BjoernT_ has quit IRC03:07
*** gkadam has joined #openstack-ansible03:49
*** gkadam has quit IRC03:50
*** udesale has joined #openstack-ansible04:01
*** cshen has joined #openstack-ansible04:18
*** ChipOManiac has joined #openstack-ansible04:30
*** pcaruana has joined #openstack-ansible04:43
*** raukadah is now known as chandankumar04:44
*** nurdie has quit IRC05:16
*** TxGirlGeek has joined #openstack-ansible05:16
*** TxGirlGeek has quit IRC05:43
cshengood morning.05:44
cshenI just learned when I run 'openstack-ansible setup-openstack-yml --limit foobar', I have to explicitly add 'localhost' in the limit, so like this 'openstack-ansible setup-openstack.yml --limit localhost,foobar'.05:45
cshenwas it because dynamic inventory doesn't include localhost?05:46
jrossercshen: when you use --limit all other targets are excluded, thats just how ansible works05:51
jrosserand the results can sometimes be unexepected05:51
*** miloa has joined #openstack-ansible05:52
*** jhesketh has quit IRC06:11
*** jhesketh has joined #openstack-ansible06:11
miloaMorning06:34
cshenjrosser: if I run https://opendev.org/openstack/openstack-ansible/src/branch/master/playbooks/os-neutron-install.yml with --limit, I found the first play "Configure Neutron dynamic host groupings" would be skipped, because no host was matched.06:40
cshenSo I need to do "openstack-ansible os-neutron-install.yml --limit localhost,HOST_NAME" to make sure that play will be played.06:40
openstackgerritKevin Carter (cloudnull) proposed openstack/ansible-config_template master: Enhance the config_template comment parser  https://review.opendev.org/67217006:46
jrossercshen: yes, if there are tasks targeting localhost and you exclude localhost with a —limit they will be skipped.06:53
cshenjrosser: thanks.06:53
*** Blinkiz has joined #openstack-ansible06:55
BlinkizHello. I have been stuck for a day now without finding a solution. TASK [python_venv_build : Upgrade pip/setuptools/wheel to the versions we want]06:56
BlinkizTwo infrastructure works alright but the third always fails with a "[Errno 111] Connection refused" against http://192.168.38.9:8181. Doing a nmap from within the infra3_utility_container-24784d93 works against that address.06:58
Blinkizhttps://paste.ubuntu.com/p/KQZ5mnBnnr/06:58
BlinkizWhat is happening here? Why is it failing?07:01
ChipOManiacBlinkiz: Is 38.9 your load-balanced address?07:05
BlinkizChipOManiac, yes, the ipv4 address is used in user_variables.yml,haproxy_keepalived_internal_vip_cidr.07:06
*** rpittau|afk is now known as rpittau07:09
*** vnogin has joined #openstack-ansible07:13
noonedeadpunkmornings07:14
*** vnogin has quit IRC07:16
*** nurdie has joined #openstack-ansible07:17
*** irclogbot_1 has quit IRC07:20
*** openstackstatus has quit IRC07:20
*** zbr_ has joined #openstack-ansible07:20
*** irclogbot_2 has joined #openstack-ansible07:21
*** nurdie has quit IRC07:22
*** zbr has quit IRC07:23
*** mrda has quit IRC07:23
*** mrda has joined #openstack-ansible07:23
*** Anticimex has quit IRC07:24
*** tosky has joined #openstack-ansible07:28
openstackgerritDmitriy Rabotyagov (noonedeadpunk) proposed openstack/openstack-ansible-tests master: Update ansible to 2.8.2  https://review.opendev.org/65965807:28
*** Anticimex has joined #openstack-ansible07:29
*** ChipOManiac has quit IRC07:40
jrosserBlinkiz: if you wget the url from the utility container does it work? and also check that it works more than 3 times one after the other07:42
Blinkizjrosser, thank you for the suggestion. I deleted the container and is now running setup-hosts.yml and soon setup-infrastructure.yml. I try wget if it fails again.07:43
openstackgerritJimmy McCrory proposed openstack/openstack-ansible master: Change haproxy http-check expect for nova_console  https://review.opendev.org/67221507:47
openstackgerritMerged openstack/openstack-ansible-lxc_container_create master: Do not add container /etc/hosts entry for 127.0.1.1  https://review.opendev.org/67070508:01
Blinkizjrosser, When using wget from inside infra3_utility_container-24784d93 I get "Connecting to 192.168.38.9:8181... failed: Connection refused". Doing the same from infra2-utility-container-497e4f58 and it works. Why? :)08:06
jrosserBlinkiz: well i dont know :) but the next thing you can do is to try wget from the utility container to the backend repo servers directly rather than the vip08:09
jrosserthen you'll be able to decide if it is a problem with the vip/loadbalancer, or theres a more general networking problem with your infra3 host / containers08:10
Blinkizjrosser, okay. sure. :)08:15
jrosserBlinkiz: thing is, utility container is the first thing like that which gets made very early in the build, so instinctively i'd say this is a networking issue specific to infra308:16
Blinkizjrosser, So, wget from infra3-utility-container-24784d93 to infra1-repo-container-8e14f718, infra2-repo-container-b4e807fb and infra3-repo-container-0b388e14 works.08:17
jrosserbut it fails to the vip?08:18
Blinkizjrosser, yes.'08:18
jrosserright - so i think that gives you a route to chase down whats wrong, you've definitely got the vip in used_ips?08:19
openstackgerritMerged openstack/openstack-ansible-lxc_hosts stable/rocky: Fix copying apt keys from host to containers  https://review.opendev.org/67012708:19
Blinkizjrosser, I do not have the vip ipv4 in used_ips08:20
*** ivve has joined #openstack-ansible08:22
jrosserBlinkiz: here you see for an AIO the VIP is specifically marked as used https://github.com/openstack/openstack-ansible/blob/master/etc/openstack_deploy/openstack_user_config.yml.aio#L1108:22
*** ChipOManiac has joined #openstack-ansible08:22
Blinkizjrosser, alright, and? :)08:23
Blinkizjrosser, in openstack_user_config.yml.example it says used_ips is optional.08:24
jrosseryou define a range of IP addresses for the mgmt network in your config, and OSA selects random addresses out of that range for the container eth1 interfaces08:24
jrosserso if you have routers, gateways, or whatever else in the mgmt network you need to list those ips so that a container doesnt get put on an already used ip08:26
jrosseryou can check how things have been assigned with ./scripts/invetory_manage.py08:27
chandankumarjrosser: Hello08:27
chandankumarjrosser: what is the ansible version we are using in OSA?08:27
Blinkizjrosser, yeah. No problem there I think. I have listed in "used_ips" all bare metal services in all subnets. ./scripts/invetory_manage.py, let me check!08:27
chandankumarjrosser: with ansible-2.8 testing http://logs.openstack.org/19/667219/5/check/tripleo-ci-centos-7-standalone/a34fc53/job-output.txt.gz#_2019-07-22_10_35_04_99282808:27
jrosserchandankumar: it depends08:27
chandankumarthis error is still poping up08:27
chandankumarin master branches?08:27
jrosserchandankumar: we pin to the version of ansible that is current during each release08:28
jrosserso we're just about to land a patch moving to 2.8.x08:28
jrosserand that will become the version for stable/train forever08:28
openstackgerritArx Cruz proposed openstack/openstack-ansible-os_tempest master: Update stestr_executable variable for RHEL-8  https://review.opendev.org/67222508:30
jrosserchandankumar: now i'm sure i've seen that error08:30
Blinkizjrosser, My ./scripts/invetory_manage.py seems okay. https://paste.ubuntu.com/p/NzC9w4pnmZ/08:31
Blinkizjrosser, How do I troubleshoot haproxy and the vip address?08:32
chandankumarjrosser: yes, last time noonedeadpunk fixed in openstack-ansible-tests side08:32
jrosserBlinkiz: infra3_horizon_container-07e7f66f            | None     | horizon                  | infra3        | None           | 192.168.38.908:33
jrosser^ looks like trouble?08:33
Blinkizjrosser, I do not know, does it? :)08:33
jrosserwell, from earlier in IRC "ChipOManiac> Blinkiz: Is 38.9 your load-balanced address?"08:34
jrosseryou can't have the loadbalancer VIP and one of the horizon containers both have the same IP08:35
BlinkizSo what you are saying is that 192.168.38.9 should be listed in the variable "used_ips"?08:35
jrosserthats what i told you earlier, yes, anything that can't be assinged to a container needs to listed in used_ips08:35
jrosserand i believe that this is why things on infra3 are failing because there is something local on infra3 replying to arp for your vip, but it's actually a horizon container08:36
ChipOManiacBlinkiz: Port 8181 is for the repo container IIRC. That comes through the load-balancer.08:37
jrosserand due to some race condition / arp battle things are working out better for your other hosts, but thats just down to luck imho08:37
ChipOManiacSince 38.9 is assigned to the infra3_horizon_container, there's going to be a conflict.08:37
BlinkizThe problem here is that before deployment 192.168.38.9 is not a used ip. It makes no sense for me to specify it under used_ips. If openstack-ansible creates a IP am assuming openstack-ansible keeps track of it08:37
ChipOManiacBlinkiz: That's true. But since you selected 38.9 it won't be included.08:38
BlinkizIn openstack_user_config.yml.example "used_ips" is explained. It says nothing about the need to specify things openstack-ansible will create.08:39
jrosseropenstack-ansible does not select the internal VIP08:39
jrosserit's user defined, becasue it might be haproxy, or F5 hardware LB or whatever else you want08:39
ChipOManiac^ You specified it in the variables.08:39
noonedeadpunksaw lots ofhttp://logs.openstack.org/26/670126/1/check/openstack-ansible-linters/e94fd11/job-output.txt.gz#_2019-07-23_08_18_02_804948 today08:40
BlinkizMy I suggest that you add in user_variables.yml.prod.example that used IPs here needs to be specified in openstack_user_config.yml under "used_ips" because openstack-ansible do not keep track of this08:44
BlinkizBut I must thank you guys for nice support here. Thank you :)08:46
chandankumarjrosser: https://review.opendev.org/#/c/665244/ fixes the issue last tome08:47
chandankumar*time08:47
*** nurdie has joined #openstack-ansible08:56
*** nurdie has quit IRC09:00
openstackgerritMerged openstack/openstack-ansible-os_keystone master: Remove nginx default conf  https://review.opendev.org/67204009:00
*** namrata has joined #openstack-ansible09:01
openstackgerritChandan Kumar (raukadah) proposed openstack/openstack-ansible-os_tempest master: [WIP]Set fact tempest_install_method var for meta handler  https://review.opendev.org/67223109:02
jrosserchandankumar: noonedeadpunk: really i dont understand why we have this hander at all https://github.com/openstack/ansible-role-python_venv_build/blob/master/handlers/main.yml#L16-L1809:06
chandankumarjrosser: I have also no idea09:06
jrosser"noop (added in Ansible 2.0) This literally does 'nothing'. It is mainly used internally and not recommended for general use."09:06
chandankumarjrosser: will remove the handler part from venv_build?09:07
chandankumarand check what other things are breaking09:07
noonedeadpunkjrosser: can't it restart service somehow?09:07
noonedeadpunknot itself but in complex09:08
noonedeadpunkSince other handlers listen to it https://github.com/openstack/openstack-ansible-os_aodh/blob/master/handlers/main.yml#L1609:10
noonedeadpunkso it kinda triggers real handers outside of this role09:10
jrosseryes just found the same sort of thing https://opendev.org/openstack/openstack-ansible/src/branch/master/playbooks/utility-install.yml#L3509:11
openstackgerritMerged openstack/openstack-ansible-openstack_hosts master: Do not add /etc/hosts entry for 127.0.1.1  https://review.opendev.org/67070609:11
noonedeadpunkchandankumar: maybe I'm not correct (sorry if I am) but I think that we really need ether default or tempest_install_method being defined before checking it's existance09:14
chandankumarnoonedeadpunk: let' see I am testing it here https://review.opendev.org/#/c/667219/09:15
chandankumarin tripleo side tempest_install_method is always distro09:15
noonedeadpunkthe point was about variables scope iirc09:16
*** vnogin has joined #openstack-ansible09:16
chandankumarnoonedeadpunk: ah, got it, once this job finishes, let me check it's existence09:17
jrosserchandankumar: the proper answer i think is that you need to define tempest_install_method in tripleo in a group_vars or whatever that is in scope for the place that handler is run09:17
noonedeadpunkso during role include vars were included form the role which was doing tempest include (and don't have tempest_install_method)09:18
noonedeadpunkbut it's might be related only to OSA, since we're using with_first_found09:18
chandankumarjrosser: noonedeadpunk https://github.com/openstack/tripleo-quickstart-extras/blob/master/playbooks/tempest.yml09:19
chandankumaris the playbook used09:19
chandankumarand is called https://github.com/openstack/tripleo-quickstart-extras/blob/master/playbooks/multinode-standalone.yml#L4909:19
namratajonher the workaround you suggested for WSREP SST method upgrade from xtrabackup-v2 to mariabackup worked for me. Thanks09:20
*** vnogin has quit IRC09:21
jonhernamrata nice, i should not take credit for that though, i don't remember who posted it here09:21
jonheri saerch the irclog here and jrosser sent it to you once already :p i just resent what he already sent to you. anyways, glad it works :)09:22
namrataoh great!09:23
namratajonher I would like to make the contribution for the same in the code. if somebody can help me how to proceed will be very helpful.09:23
namrataIn that case jrosser thanks a lot for sharing the same09:24
jonherif you have not contributed before you have to setup a few things to be able to suggest a change in gerrit: https://docs.openstack.org/infra/manual/developers.html09:25
jonherif you have contributed before, create a review with the changes :)09:25
namrataI have contributed earlier but not in ansible so I dont need to setup the same09:26
*** vnogin has joined #openstack-ansible09:27
openstackgerritMerged openstack/openstack-ansible-os_octavia stable/stein: Use the admin endpoint to upload glance images  https://review.opendev.org/66837409:30
openstackgerritMerged openstack/openstack-ansible-os_octavia stable/rocky: Use the admin endpoint to upload glance images  https://review.opendev.org/66837509:30
jrossernamrata: great that its worked :)09:30
openstackgerritMerged openstack/openstack-ansible-os_octavia stable/rocky: Ensure that admin endpoint is used to configure octavia quota  https://review.opendev.org/66837309:30
namrataso it will be same in the code like running `galera-install.yml -e galera_wsrep_sst_method=rsync -e galera_upgrade=true ` before stup-infrastructure playbook09:31
openstackgerritMerged openstack/openstack-ansible-os_octavia master: Save iptables rules for all Debian derivative operating systems  https://review.opendev.org/66839409:37
jrossernamrata: ideally we update the docs here and the upgrade scripts to handle this all automatically https://docs.openstack.org/openstack-ansible/latest/admin/upgrades/major-upgrades.html09:38
namrataokay so should I add this particular step `galera-install.yml -e galera_wsrep_sst_method=rsync -e galera_upgrade=true` in the upgrade script and document both09:42
jrossernamrata: well i guess this is targetting an R->S upgrade? the code in master will become the T release, and if we are already on T we can assume that the replication type is correct09:45
ChipOManiacAnyone know if Zun can be deployed via openstack-ansible? I can certainly see an os_zun repo but no os-zun-install.yml, so I guess running a setup-openstack.yml won't do much.09:47
jrossernamrata: perhaps it's something to ask at the OSA meeting later today what the right way to do this is?09:48
namrataokay thanks jrosser. i will attend the meeting .09:49
noonedeadpunkChipOManiac: hm, yep, seems that you're right and we're missing zun installation playbook...09:50
noonedeadpunkyou can probably use https://github.com/openstack/openstack-ansible-os_zun/blob/master/tests/test-install-zun.yml as a sample...09:50
noonedeadpunkand it's smth that you either may offer for upstream, or we can do it ourselves if you don't have opportinity09:52
ChipOManiacnoonedeadpunk: Wouldn't have a problem with that. :)10:01
ChipOManiacWe're trying to set it up at our shop.10:02
ChipOManiacJust don't know where to start.10:02
jrosserChipOManiac: take one of the existing playbooks for another sevice as a starting point, the code is really quite modular these days so the changes needed should be fairly minimal10:03
jrosserand spin up an all-in-one to bash at it a bit10:03
openstackgerritDmitriy Rabotyagov (noonedeadpunk) proposed openstack/openstack-ansible-os_zun master: Fix docs linking and naming  https://review.opendev.org/67224610:04
*** nurdie has joined #openstack-ansible10:07
*** kopecmartin|off is now known as kopecmartin10:12
*** nurdie has quit IRC10:12
ChipOManiacjrosser: I see. But the playbook for nova seemed a little daunting, and threw me off actually.10:17
ChipOManiacBTW thanks noonedeadpunk and jrosser.10:17
noonedeadpunkYou may probably look at masakari (since it is also devided for compute and api)10:19
ChipOManiacI'll take a look then. Thanks :)10:20
jrossernoonedeadpunk: i just saw that the placement playbook doesnt do any management of haproxy like some of the others do - does that look wrong?10:23
*** ansmith has joined #openstack-ansible10:26
noonedeadpunkjrosser: it's ok if we don't mind service outage... But for placement I'd say it's better to do it serial10:26
noonedeadpunkbtw, masakari s missing serial:(10:26
noonedeadpunkseems, like we need some cleanup and unification for playbooks as well...10:27
jrosseryes, QA time everwhere :)10:27
jrosserbut thats good10:27
openstackgerritJonathan Rosser proposed openstack/openstack-ansible-tests master: Update ansible to 2.8.2  https://review.opendev.org/65965810:32
noonedeadpunkjrosser mnaser do you know where/how journalctl logs get colected and compressed in our CI?10:46
*** luksky11 has joined #openstack-ansible10:47
jrossernoonedeadpunk: https://github.com/openstack/openstack-ansible/blob/master/scripts/log-collect.sh#L113-L13710:48
*** luksky123 has joined #openstack-ansible10:48
*** nurdie has joined #openstack-ansible10:48
noonedeadpunkthanks!10:49
*** luksky11 has quit IRC10:52
*** nurdie has quit IRC10:53
*** namrata has quit IRC10:55
openstackgerritDmitriy Rabotyagov (noonedeadpunk) proposed openstack/openstack-ansible-galera_server master: Use systemd-journald instead of log files  https://review.opendev.org/67205911:02
evrardjphello11:02
noonedeadpunkhi there:) how are you doing?:)11:03
*** nurdie has joined #openstack-ansible11:09
*** nurdie has quit IRC11:14
*** kplant has joined #openstack-ansible11:16
*** spatel has joined #openstack-ansible11:20
*** spatel has quit IRC11:25
openstackgerritDmitriy Rabotyagov (noonedeadpunk) proposed openstack/openstack-ansible master: [WIP] Drop creation of log directories  https://review.opendev.org/67178311:27
*** ChipOManiac has quit IRC11:28
*** nurdie has joined #openstack-ansible11:30
*** nurdie has quit IRC11:35
*** vnogin has quit IRC11:38
*** ansmith has quit IRC11:41
*** nurdie has joined #openstack-ansible11:51
*** nurdie has quit IRC11:56
*** markvoelker has quit IRC11:58
*** namrata has joined #openstack-ansible11:59
*** udesale has quit IRC12:04
*** strobelight has quit IRC12:04
*** udesale has joined #openstack-ansible12:04
*** nurdie has joined #openstack-ansible12:11
Blinkizopenstack-ansible setup-openstack.yml fails at [os_keystone : Add service project] with "keystoneauth1.exceptions.http.Unauthorized: The request you have made requires authentication. (HTTP 401)". https://paste.ubuntu.com/p/VJD2kN8c5w/12:14
BlinkizHow can I troubleshoot this?12:14
*** markvoelker has joined #openstack-ansible12:16
*** nurdie has quit IRC12:16
*** namrata has quit IRC12:24
*** goldyfruit has quit IRC12:26
*** nurdie has joined #openstack-ansible12:32
*** electrofelix has joined #openstack-ansible12:36
*** nurdie has quit IRC12:37
*** ansmith has joined #openstack-ansible12:37
*** namrata has joined #openstack-ansible12:38
*** luksky123 has quit IRC12:39
*** siqbal has joined #openstack-ansible12:48
*** nurdie has joined #openstack-ansible12:53
*** nurdie has quit IRC12:57
*** strattao has joined #openstack-ansible12:58
*** strobelight has joined #openstack-ansible13:06
*** nurdie has joined #openstack-ansible13:13
*** nurdie has quit IRC13:18
*** strattao has quit IRC13:20
*** openstackstatus has joined #openstack-ansible13:20
*** ChanServ sets mode: +v openstackstatus13:20
*** cshen has quit IRC13:22
*** nurdie has joined #openstack-ansible13:25
*** goldyfruit has joined #openstack-ansible13:35
*** tosky_ has joined #openstack-ansible13:40
*** tosky has quit IRC13:42
*** BlackDex has joined #openstack-ansible13:53
BlackDexhello there. With the openstack dynamic inventory, is there a way to force a specific IP address as the accessIP(v4) ???13:54
BlackDexnow it seems to just pick the first one in the line (seems to be sorted by network id)13:55
*** rpittau is now known as rpittau|afk14:03
*** tosky_ is now known as tosky14:08
*** nurdie_ has joined #openstack-ansible14:14
*** nurdie has quit IRC14:16
*** nurdie_ has quit IRC14:19
mnaserBlackDex: you might wanna look/ask in #openstack-sdks14:20
BlackDexmnaser: oke, i will try it over there :) Thx for the pointer14:22
*** gyee has joined #openstack-ansible14:23
*** vnogin has joined #openstack-ansible14:28
openstackgerritKevin Carter (cloudnull) proposed openstack/ansible-config_template master: Enhance the config_template comment parser  https://review.opendev.org/67217014:33
*** TxGirlGeek has joined #openstack-ansible14:52
*** nurdie has joined #openstack-ansible14:58
*** miloa has quit IRC14:58
*** nurdie has quit IRC15:05
*** nurdie has joined #openstack-ansible15:06
*** vnogin has quit IRC15:10
*** trident has quit IRC15:18
*** namrata has quit IRC15:19
*** namrata has joined #openstack-ansible15:20
*** trident has joined #openstack-ansible15:20
*** vnogin has joined #openstack-ansible15:38
*** strattao has joined #openstack-ansible15:38
*** trident has quit IRC15:52
openstackgerritMerged openstack/openstack-ansible-lxc_hosts stable/stein: Fix copying apt keys from host to containers  https://review.opendev.org/67012615:55
*** trident has joined #openstack-ansible15:55
mnaser#startmeeting openstack_ansible_meeting16:01
openstackMeeting started Tue Jul 23 16:01:46 2019 UTC and is due to finish in 60 minutes.  The chair is mnaser. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: openstack_ansible_meeting)"16:01
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:01
mnaser#topic rollcall16:01
*** openstack changes topic to "rollcall (Meeting topic: openstack_ansible_meeting)"16:01
mnasero/16:01
noonedeadpunko/16:01
namratao/16:01
guilhermespo/16:02
mnaserhows everyone?!16:02
jrossero/16:02
* guilhermesp fixes deployments 16:02
mnaserfun :)16:02
mnaser#topic office hours16:03
*** openstack changes topic to "office hours (Meeting topic: openstack_ansible_meeting)"16:03
mnaserpersonally16:03
mnaserhttps://review.opendev.org/#/c/671783/16:03
mnaseri love the -392 part :D16:04
guilhermespit is  lot :P16:04
noonedeadpunkSo I was thinking about dropping os-log-dir-setup.yml and rsyslog client in terms of this16:04
guilhermespseems that we started the work of cleaning up  things16:04
mnaseryeah i think at this point rsyslog_client wont really do much if we never run it16:05
mnaseri would even retire rsyslog_server unless omeone wants to maintain it16:05
noonedeadpunkbut since it's still used by ceph, unbound and things like tempest, rally and utility container...16:05
mnaserutility needs rsyslog? o_O16:05
*** Blinkiz has quit IRC16:05
noonedeadpunknot rsyslog but os-log-dir-setup.yml16:06
mnaserahhh ok16:06
mnaserthis is the thing that does bind mounts right?16:06
noonedeadpunkI mixed up things a bit:(16:06
noonedeadpunkyep16:06
mnaseri was always wondering why we just didn't log things inside the container and kills all those complicated bind mounts16:06
jrosserit probably historical so you can just collect up whatever is in /openstack/logs/* and not worry about which containers you have16:08
noonedeadpunkprobably for compressing without entering container16:08
spotzI thought it was so we could find everything in one place?16:08
noonedeadpunkbut since integrated test, which are actually metal ones, everything is already in one place16:09
evrardjpo/16:10
spotzevrardjp!!!!16:10
evrardjpspotz: ! :)16:10
evrardjpmnaser: love the - in -39216:11
*** vnogin has quit IRC16:11
cjloadero/16:12
evrardjpmnaser: yes, historical. I would prefer removing all the complex bind mounts too, as this was a pain to deal with. Cleaning this up would also simplify the code further16:12
*** Pilou has quit IRC16:13
jrosserthere is something that collects container journals on the host anyway isnt there?16:13
noonedeadpunkso, the thing is that we don't need that almost anywhere, ecept 3 playbooks16:13
jrosserso moving to all journals this is now of little point to keep the bind mounts16:14
mnaseryeah i agree with all of this so maybe it would be a good clean up16:14
mnaserbtw also knock on wood our CI has been relatively stable recently16:14
mnaserim pretty happy on where it is16:14
mnaserthe upgrade jobs need work unfortunately16:15
evrardjpyeah.16:15
evrardjpwe've decreased coverage though :(16:15
evrardjpif ppl want to help on increasing coverage, I have plenty of ideas, so little time.16:16
jrosserevrardjp: ^ can you define what you mean by that, as there several different things16:16
*** vnogin has joined #openstack-ansible16:17
evrardjpwell I think the first thing to do is to match what we removed -- so define new "specific" jobs having a pre-run play configuring the o_u_c or user_variables, to get feature parity back16:18
evrardjpthen I guess the idea would be to implement multi-node jobs in periodics16:18
noonedeadpunkYeah, since we might be missing system packages in roles16:20
noonedeadpunkwe won't catch this if they are already installed by previous role16:20
mnaserwould we get coverage again if we run both container and metal on every change?16:21
mnaseri mean im not opposed to it but we need to figure out why centos takes stupid long with lxc16:21
mnaserits like 2h20 to run aio16:21
jrosseri would like to see haproxy back in some form16:21
mnaseryes with the bind-to-mgmt stuff you're doing16:22
mnaserit'll be running fine16:22
jrosserthe curent metal jobs are fast but they are not sufficiently real life16:22
jrosseri'm a bit stuck on the galera stuff there16:22
mnaserjrosser: its odd that it just works for us, i can try to help with looking that the fails16:25
mnaserdid you end up doig the my.cnf adjustments?16:25
jrosseri did, and it's inconsistent16:25
jrosserheres the change for the client my.cnf https://review.opendev.org/#/c/672101/16:26
mnaserjrosser: lol16:26
mnaseryou're gonna hhate me16:26
mnaserjrosser: check the review :p16:26
jrosseri figured i may have messed it up16:26
noonedeadpunkyeah16:27
jrosseraaaaaahhhhhh crap :)16:27
jrosserthankyou :)16:27
* jrosser fixes16:27
openstackgerritJonathan Rosser proposed openstack/openstack-ansible-galera_client master: Default to connecting clients via ip rather than local socket  https://review.opendev.org/67210116:28
mnaserso that should hopefully help16:28
evrardjpmnaser: it won't be enough, and I didn't intent to run centos+lxc :)16:28
mnaserevrardjp: well i figured we'd run all the oeprating systems we cover16:29
evrardjpI just wanted to have like mariadb cluster testing + keystone and stop there16:29
mnaserthat probably can be wired up in logic16:30
evrardjpwe already have all we need16:30
mnaserye sbut writing the 'dependency' system16:30
evrardjpjust change affinity16:30
evrardjpwhat do you mean?16:30
mnaserwhen testing os_keystone then grab what services need os_keystone (i.e. galera memcache etc)16:31
evrardjpthe idea to not run centos+lxc was just to have scenarios (ubuntu +lxc is the most frequent one)16:31
mnaserwhen testing os_nova then grab its dependnecies which are os_neutron,os_keystone,os_glance16:31
mnaserwhos dependencies are.. etc16:31
mnaserto reduce our run times16:31
evrardjpthat's kinda what's done in tests/role/bootstrap16:31
evrardjpbut I understand it would be smarter if we do it that way16:32
evrardjpI thought this could be done using a CLI :)16:32
mnasermhmm16:32
mnaseri think we should have full coverage, if we do aio_lxc, we do it for all supproted systems16:32
evrardjpjust encapsulate the logic there, instead of relying on so many conditionals in ansible16:32
mnaserimho we either do it or drop it16:32
mnaseror otherwise we'll get a change that breaks ar ole for centos that wont be caught there16:32
mnaserand then itll be broken in integrated16:33
evrardjpI meant to keep centos for baremetal, so it would still be tested. Just keeping the most common use cases16:33
*** vnogin has quit IRC16:33
evrardjpbut I understand your point16:33
*** vnogin has joined #openstack-ansible16:34
mnaseri feel like with a little bit more efort we'd understand the fundamnetal reason of why centos is sooooo slow16:34
mnaseri think we've regressed something16:34
mnaserit never took this long before16:34
jrosserthe data is all there in the ARA reports / db16:35
jrosserto decide if its specific things that are slow, or it's just across the board16:35
mnaseracross the board16:35
mnaserevery operation is slower16:35
*** vnogin has quit IRC16:35
mnaserlike 3-4x slower16:35
mnasereven simple things16:35
jrosserdoes that still stand outside CI?16:36
noonedeadpunkOur connection module affects?16:36
*** jamesdenton has quit IRC16:36
mnaseri havent tried outside CI, i thougth about our connection moduel but figured it would regress in both OSes?16:36
*** jamesdenton has joined #openstack-ansible16:36
jamesdentono/16:36
mnaserbonjour16:36
jamesdentoni've been talking on IRC for like, at least a week, and just realized nothing was going thru16:37
mnaserlolol16:37
jamesdentonmy feelings were hurt for a bit16:37
jamesdentonlol16:37
mnaseryeah i dont know16:38
mnaserfor the centos stuff16:38
mnaserit deffo needs some profiling16:38
mnaserit'd be nice to get to nspawn and not have to deal with that but16:39
jrosserwe bit too much off there in one go16:39
mnaseryea macvlan+nspawn together is a lot16:39
jrossernspawn + macvlan is too much16:39
jrosseryes16:39
mnaserbridge+nspawn is easier to cosnume but i dunno if i have the current cycles to help with it16:40
*** vnogin has joined #openstack-ansible16:40
jrosseri think there may be (was?) a limitation with nspawn and the number of interfaces you could create16:40
jrosserevrardjp: did you do some work on ansible profiling?16:41
evrardjplong ago16:41
evrardjpdw is better :D16:41
jrosseri was just looking for dw but he's not in #mitogen16:41
jrosserdon't want to waste a bunch of time learning 10 wrong tools when someon can just say "do this"16:42
evrardjpthat reminds me I need to connect on that channel since I reconfigured my bouncer16:42
evrardjpjrosser: totally16:42
evrardjpjust wait for him, last time he was super helpful to me16:42
evrardjpmaybe ping him on twitter?16:42
jrosserdone16:45
chandankumarcloudnull: jrosser needs +w on this https://review.opendev.org/#/c/672225/16:46
mnaserso we'll keep improving and cleaning up things, journald seems to be cleaning up well16:46
cloudnullchandankumar done16:47
chandankumarcloudnull: thanks :-)16:47
mnaserOH16:47
mnaseralso16:48
mnaserdid y'all see my email to the ML16:48
mnaserabout openstack-ansible-collab16:48
guilhermesphectic days, just saw an email around, but I will take a look16:48
jamesdentonJust a heads up, but the unicast flood issue that was brought up last week is related to change in os-vif introduced in Stein. See: https://bugs.launchpad.net/os-vif/+bug/1837252.16:50
openstackLaunchpad bug 1837252 in neutron "IFLA_BR_AGEING_TIME of 0 causes flooding across bridges" [Undecided,Incomplete]16:50
jrosserchandankumar: did you find a solution with your tempest undefined var?16:50
mnaserjamesdenton: affecting lxb only?16:51
chandankumarjrosser: above changes worked https://review.opendev.org/#/c/672231/ here, But I need to come up with a better solution16:51
jamesdentonit affects the qbr bridges, too, with OVS. Just not sure what the overall effect is there16:51
chandankumarit might happening due to mixing of venv and distro stuff16:51
chandankumarjrosser: sorry wrong review16:52
chandankumarjrosser: https://review.opendev.org/#/c/667219/16:52
jrosserevrardjp: word according to dw "'perf record -g ansible-playbook ...' of the ansible run  /and/ separately on the host using simply 'perf record'   followed by 'perf report' might show something obvious"16:57
*** vnogin has quit IRC16:57
*** siqbal90 has joined #openstack-ansible16:57
jrossernamrata: did you want to ask about upgrades?16:57
namratayeah I was waiting for open discussion16:58
evrardjpjrosser: oh yeah that rings me a bell :)16:58
namrata Hi would like to contribute to openstack ansible and I can start with the issue which I faced while upgrading R->S i.e upgrading WSREP SST method from xtrabackup-v2 to mariabackup.16:58
jrossernamrata: just ask :)16:58
*** siqbal has quit IRC16:58
evrardjpjrosser: could it be the fact we just added all those plays, and maybe there is cruft in the inventory?16:59
evrardjpI haven't checked tbh16:59
namratajrosser suggested to take this up in the meeting so we can discuss how to handle it16:59
jrossermnaser: ^ so for fixing up the R-S upgrade for galera, do we make patches to master? i wasnt totally clear where we do that16:59
jrosserevrardjp: ^ maybe you can advise too16:59
evrardjpwell, is S-master broken too?17:00
jrosserif you start on S you are already on the new replication method17:00
evrardjpok17:00
evrardjpso it's S upgrade only, so it's only implementable in stein17:00
evrardjpyou got your answer ? :p17:01
jrosseri guess it's made more complicated by not having a working R-S upgrade CI job :/17:01
jrosserwell, unless we do, of course17:01
*** siqbal90 has quit IRC17:02
mnaseryeah stable only patch17:02
namrataokay so I should push to stable/stein then17:02
jrossernamrata: ok so that sounds like your answer, write something that goes onto stable/stein17:02
namratajrosser thanks17:03
jrosserand thanks for taking the time to fix it up :)17:03
namrata:]17:03
*** udesale has quit IRC17:03
*** trident has quit IRC17:07
*** chandankumar is now known as raukadah17:08
*** trident has joined #openstack-ansible17:10
*** cshen has joined #openstack-ansible17:12
mnaser#endmeeting17:15
*** openstack changes topic to "Launchpad: https://launchpad.net/openstack-ansible || Weekly Meetings: https://wiki.openstack.org/wiki/Meetings/openstack-ansible || Review Dashboard: http://bit.ly/2xA1eZC"17:15
openstackMeeting ended Tue Jul 23 17:15:41 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:15
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2019/openstack_ansible_meeting.2019-07-23-16.01.html17:15
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2019/openstack_ansible_meeting.2019-07-23-16.01.txt17:15
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2019/openstack_ansible_meeting.2019-07-23-16.01.log.html17:15
strattaoHope all is well with you guys!17:16
*** cshen has quit IRC17:16
strattaoWe’re having some issues with one of our deployment regions. Rabbit seems to be handling the nova queues just fine, but is stumbling over the neutron queues and we’re getting network timeouts, etc.17:17
openstackgerritSorin Sbarnea proposed openstack/openstack-ansible-os_tempest master: POC: running openstack-tox-molecule  https://review.opendev.org/67233317:19
openstackgerritSorin Sbarnea proposed openstack/openstack-ansible-os_tempest master: POC: running openstack-tox-molecule  https://review.opendev.org/67233317:19
strattaoI was wondering if anyone has a writeup with some best practices for large-scale deployments, worker tunings, etc.? We are looking at adding additional neutron nodes to handle the load. Any recommendations or experiences to share? maybe jrosser or jamesdenton got some insights?17:20
jrosserstrattao: one of my team went to this https://indico.cern.ch/event/776411/timetable/#2019052717:23
jrosserand said that some of the talks were about larger scales and what you need to do to achieve that17:24
jrosserthe pdf are all there to look through17:29
strattaoyeah, some guy named mnasser even has a walkthrough with examples - I wish all talks had that level of detail!17:30
strattaomnaser*17:30
strattaoso, our general approach of just more api workers & more network nodes until the workload is handled, is that the process when you start working at scale?17:32
jrosserwell scale means different things in different contexts, i don't have particularly many nodes but have lots of throughput network wise17:34
strattaodo you have standalone network nodes? what about standalone rabbit?17:36
jrosserso I split the network nodes out from day 117:36
strattaoOur infrastructure looks just like this right now: https://docs.openstack.org/project-deploy-guide/openstack-ansible/pike/app-config-prod.html17:36
jrosserthe one i build next will have 4 on day one rather than 2, and 20 cores in each17:36
strattaobut we are using ovs+dvr17:37
strattaohow many api workers? rabbit pool connections?17:38
jrosserjust the OSA defaults, like i say i expect we are running into different limits first17:38
mnaseri have a walkthrough? :p17:38
strattaoyeah, look at this beautiful presentation! https://indico.cern.ch/event/776411/contributions/3345183/attachments/1851624/3039917/02_-_vGPUs_with_OpenStack_-_Accelerating_Science.pdf17:39
strattaovGPUs are in our future and this is super helpful!17:39
mnaser:D17:40
jrosserstrattao: in very general terms if you have a lot of CPU load from "network stuff" it makes sense to run the neutron agents on dedicated hardware at some point so your users don't DOS your control plane17:40
jrosserand similarly rabbit sits at the other end of the scale, Sanger Institute recommended dedicated hardware for that as its so critical/potentially fragile17:41
jrosserso you have to take a judgment based on how stuff is working out under your workload17:42
jrossermnaser: you need licences for nvidia vgpu?17:46
mnaseryep17:46
mnasernvidia grid17:46
jrosserhmm bummer17:47
jrosserthey make it expensive17:47
openstackgerritKevin Carter (cloudnull) proposed openstack/ansible-config_template master: Enhance the config_template comment parser  https://review.opendev.org/67217017:49
*** namrata has quit IRC17:51
*** nurdie has quit IRC18:03
openstackgerritMerged openstack/openstack-ansible-os_octavia stable/stein: Ensure that admin endpoint is used to configure octavia quota  https://review.opendev.org/66836918:04
*** nurdie has joined #openstack-ansible18:05
*** poopcat has joined #openstack-ansible18:08
*** vnogin has joined #openstack-ansible18:16
*** nurdie has quit IRC18:18
cloudnull^ if folks have a minute to give https://review.opendev.org/672170 a review I'd greatly appreciate it -cc jrosser18:21
*** strattao has quit IRC18:26
*** strattao has joined #openstack-ansible18:46
*** strattao has quit IRC18:47
grabesjamesdenton: Thanks for your work on this: https://bugs.launchpad.net/os-vif/+bug/183725218:56
openstackLaunchpad bug 1837252 in os-vif "IFLA_BR_AGEING_TIME of 0 causes flooding across bridges" [High,Confirmed] - Assigned to sean mooney (sean-k-mooney)18:56
*** strattao has joined #openstack-ansible18:57
jamesdentonhappy to help19:01
*** goldyfruit has quit IRC19:02
*** goldyfruit has joined #openstack-ansible19:06
openstackgerritVadim Kuznetsov proposed openstack/openstack-ansible-os_octavia master: Updated certificate distribution task  https://review.opendev.org/65766219:06
*** kopecmartin is now known as kopecmartin|off19:16
*** vnogin has quit IRC19:18
*** cshen has joined #openstack-ansible19:21
*** vnogin has joined #openstack-ansible19:26
*** cshen has quit IRC19:33
openstackgerritVadim Kuznetsov proposed openstack/openstack-ansible-os_octavia master: Fixed octavia-health-manager group name  https://review.opendev.org/67234719:42
*** tosky has quit IRC19:47
*** kplant has quit IRC19:54
*** allanb has joined #openstack-ansible19:54
*** jsquare has quit IRC20:03
*** jsquare has joined #openstack-ansible20:05
*** vnogin has quit IRC20:11
*** ansmith has quit IRC20:42
*** pcaruana has quit IRC20:50
*** vnogin has joined #openstack-ansible21:16
*** irclogbot_2 has quit IRC21:32
*** altlogbot_0 has quit IRC21:33
*** altlogbot_1 has joined #openstack-ansible21:33
*** irclogbot_2 has joined #openstack-ansible21:33
*** vnogin has quit IRC21:39
*** strattao has quit IRC21:45
*** strobelight has quit IRC21:47
*** irclogbot_2 has quit IRC21:59
*** altlogbot_1 has quit IRC22:01
openstackgerritVadim Kuznetsov proposed openstack/openstack-ansible-os_octavia master: Updated certificate distribution task  https://review.opendev.org/65766222:04
*** ansmith has joined #openstack-ansible22:18
*** altlogbot_1 has joined #openstack-ansible22:21
*** gyee has quit IRC22:23
*** TxGirlGeek has quit IRC22:25
*** altlogbot_1 has quit IRC22:27
*** goldyfruit has quit IRC22:30
*** goldyfruit has joined #openstack-ansible22:30
*** goldyfruit has quit IRC22:38
*** gyee has joined #openstack-ansible23:10
*** altlogbot_0 has joined #openstack-ansible23:13
*** altlogbot_0 has quit IRC23:19
*** altlogbot_0 has joined #openstack-ansible23:27
*** irclogbot_3 has joined #openstack-ansible23:31

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