Tuesday, 2018-01-09

*** ashak has joined #openstack-ansible00:15
*** woodard has joined #openstack-ansible00:16
*** esberglu has quit IRC00:37
*** chyka_ has quit IRC00:38
*** TxGirlGeek has quit IRC01:01
*** TxGirlGeek has joined #openstack-ansible01:11
*** TxGirlGeek has quit IRC01:12
*** pbandark has quit IRC01:17
*** markvoelker has joined #openstack-ansible01:17
*** ashak has quit IRC01:20
*** ashak has joined #openstack-ansible01:21
*** pradiprwt has quit IRC01:22
*** woodard_ has joined #openstack-ansible01:36
*** woodard has quit IRC01:36
*** savvas` has joined #openstack-ansible02:25
*** savvas` has quit IRC02:27
*** savvas` has joined #openstack-ansible02:28
*** armaan has quit IRC02:33
yifeiHi all. I have question that when play "lxc_container_config.yml", if any container creation failed, the tasks after flush_handlers will not be run. Then the rest configuration tasks for all of the containers would not be run either.02:33
yifeiany one know about this?02:34
yifeiashak: I have met the same problem. It seems that it has been fixed in the lastest stable/pike02:37
yifeiashak: but after deployment, my galera will be crush and cannot be started after running sometime. I have had a lot problems while deploying pike on centos. Made me crazy.....02:41
*** udesale has joined #openstack-ansible02:46
*** markvoelker has quit IRC03:06
*** adreznec has quit IRC03:07
*** adreznec has joined #openstack-ansible03:08
*** adreznec has quit IRC03:16
*** adreznec has joined #openstack-ansible03:21
*** ANKITA has quit IRC03:28
masbergood afternoon all, shall I run the playbooks as root in order to install openstack through OSA?03:44
masberthe reason I am asking is because OSA recommends ubuntu for installation but root user can't ssh by default so I am not sure whether I should enable ssh for root user on all hosts and run ansible as root or just change the permissions for /etc/openstack-ansible folder?03:46
*** savvas` has quit IRC03:58
*** gfa has quit IRC03:59
*** esberglu has joined #openstack-ansible04:16
*** esberglu has quit IRC04:17
*** nshetty has joined #openstack-ansible04:26
*** chhavi has joined #openstack-ansible04:37
*** pmannidi has quit IRC04:44
*** mpranjic has joined #openstack-ansible04:46
*** hybridpollo has quit IRC04:54
*** markvoelker has joined #openstack-ansible04:56
*** bhujay has joined #openstack-ansible04:58
masberhi, I am getting this error while running "sudo openstack-ansible -vvv setup-hosts.yml" --> https://bpaste.net/show/9eb98e0f18d005:01
masberit looks like br-mgmt does not exist?05:05
*** poopcat1 has quit IRC05:09
*** nshetty has quit IRC05:44
*** nshetty has joined #openstack-ansible05:45
*** smatzek has joined #openstack-ansible05:53
*** smatzek has quit IRC05:57
masberok, I think I have to create the bridges myself05:59
*** pmannidi has joined #openstack-ansible06:18
*** ANKITA has joined #openstack-ansible06:35
*** taseer1 is now known as Taseer06:37
*** gkadam has quit IRC06:43
*** taseer1 has joined #openstack-ansible06:44
*** taseer2 has joined #openstack-ansible06:44
*** Taseer has quit IRC06:45
*** taseer3 has joined #openstack-ansible06:48
*** taseer2 has quit IRC06:48
*** taseer4 has joined #openstack-ansible06:48
*** taseer1 has quit IRC06:48
*** taseer3 has quit IRC06:53
*** pcaruana has joined #openstack-ansible06:56
*** armaan has joined #openstack-ansible07:10
*** SmearedBeard has joined #openstack-ansible07:25
evrardjpcores, could we wait before introducing new features? We have so many bugs to fix now, I'd rather we fix/stabilize things this week.07:27
evrardjpbefore merging* new features07:27
evrardjpmasber: you have to create bridges yourself. It's written in our deploy guide documentation07:31
ThomasSch_hi07:32
evrardjphello ThomasSch_07:33
ThomasSch_i wanted to enable ceph for backup and followed the guide07:33
ThomasSch_i get an error in retrieving ceph keyring for openstack clients07:33
ThomasSch_the cinder backup is working fine07:33
evrardjpdid you deploy ceph with osa, or you have a standalone ceph cluster?07:33
ThomasSch_is this known?07:33
ThomasSch_yes07:33
ThomasSch_followed the ceph guide07:33
*** pmannidi has quit IRC07:34
evrardjpWhich guide?07:34
evrardjp:)07:34
ThomasSch_https://docs.openstack.org/project-deploy-guide/openstack-ansible/pike/app-config-prod-ceph.html07:34
evrardjpok07:34
ThomasSch_was getting the link :-)07:34
evrardjpyour yes was good in its logic, it just didn't help me :p07:35
evrardjpyou're following the right docs07:35
ThomasSch_yes sorry :-)07:35
ThomasSch_so ceph with osa07:36
evrardjpno it's my fault, ambiguous quesiton!07:36
evrardjpso you mean cinder backup is working, but not with a ceph backend?07:36
ThomasSch_no cinder backup is not working but the normal backend07:36
ThomasSch_ Retrieve keyrings for openstack clients from ceph cluster]07:36
ThomasSch_fatal: [infra1]: FAILED! => {"failed": true, "msg": "'ceph_mon_host' is undefined"}07:37
ThomasSch_i was running os-cinder playbook with tag cinder-config07:37
evrardjpceph_mon_host must be defined07:37
evrardjpif you followed the docs07:37
evrardjpin the docs it's in /etc/openstack_deploy/openstack_user_config.yml07:37
evrardjpbut you could define it in conf.d/ too07:38
evrardjpThomasSch_: you should run without the tags at first07:38
ThomasSch_it is defined07:38
ThomasSch_ceph-mon_hosts: *infrastructure_host07:38
ThomasSch_ok07:38
ThomasSch_i will give it a try07:39
*** SmearedBeard has quit IRC07:41
evrardjpmmm07:45
evrardjp*infrastructure_hosts ?07:46
*** udesale has quit IRC07:46
evrardjpand do you have _infrastructure_hosts: &infrastructure_hosts ?07:46
evrardjpmaybe better if you share your openstack_user_config07:47
*** epalper has joined #openstack-ansible07:49
ThomasSch_one second07:54
ThomasSch_os cinde rinstall worked without any error07:55
ThomasSch_still only 4 pools in ceph07:55
ThomasSch_no backup pool07:55
openstackgerritlei zhang proposed openstack/monitorstack master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53204907:56
ThomasSch_here is the config07:56
ThomasSch_https://pastebin.com/mZzuP6U807:56
*** mbuil has joined #openstack-ansible07:57
*** gkadam has joined #openstack-ansible08:13
*** pradiprwt has joined #openstack-ansible08:22
*** SmearedBeard has joined #openstack-ansible08:29
openstackgerritJean-Philippe Evrard proposed openstack/openstack-ansible-os_keystone master: Fix undefined handler Manage LB  https://review.openstack.org/53206908:29
*** chhavi__ has joined #openstack-ansible08:29
jafeha__good morning08:29
*** chhavi has quit IRC08:29
*** jafeha__ is now known as jafeha08:29
evrardjpThomasSch_: are they supposed to be different pools? I don't know08:30
evrardjpjafeha: good morning08:30
jafehagood morning evrardjp08:30
evrardjpThomasSch_: maybe we have to add verification checks in our docs08:30
evrardjplet's wait for logan- or andymccr , they worked on ceph, so they know what to expect08:31
evrardjpjafeha: I have to finish up another bug that prevented me fixing the first bug, then I am all scenarios!08:32
jafeha:D08:32
jafehai only having half an eye, but whats wrong with ceph?08:32
evrardjp(Unless someone merges something that breaks further things, which usually happens to me, thanks to my luck)08:32
evrardjpjafeha: are there supposed to be two different pools for cinder and cinder backups?08:32
jafehaafair yes08:33
jafehawe have separate pools at least08:33
evrardjpThomasSch_: you got your answer there :)08:33
jafehanever tested that functionality though08:33
andymccrThomasSch_: in general check out https://github.com/ceph/ceph-ansible docs - it will have docs on how to setup pools etc.08:33
evrardjpandymccr: thanks!08:33
andymccrOSA literally just implements that, so none of the ceph bits are really special, aside from some glue bits08:33
*** SmearedBeard has quit IRC08:34
jafehaandymccr, talking about ceph, do you know if there are any plans for implementing rados as opt in as swift backend?08:34
andymccrjafeha: there are! let me find the PR08:35
andymccri'm hoping to talk to logan- about it at the PTG and get that finalised08:35
andymccrhttps://review.openstack.org/#/c/517856/08:35
jafehawohoo :D08:35
andymccrhe's most of the way there already, but it just needs a bit of TLC and we can get that going08:35
jafehathat makes my mood even better today :D08:35
jrosserandymccr: nice to see that radosgw stuff in progress - whats still to do?08:39
evrardjpandymccr: how does this work?08:41
evrardjpdoes the radosgw speak a swift compatible api?08:42
evrardjpor is there some kind of middleware wiring to do between swift and the radosgw?08:42
*** wspthr has quit IRC08:47
openstackgerritlei zhang proposed openstack/openstack-ansible-apt_package_pinning master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53208208:47
andymccrevrardjp: yeah radosgw does swift and s3 apis08:49
andymccrbut it just requires integration with keystone etc.08:49
andymccrjrosser: honestly not too much, ive manually set it up a few times, and it basically does what logan- already has setup, so i think it really just needs a bit of a look over. i've got that on my to-do list. the actual setup is pretty simple though.08:50
andymccrevrardjp: so you just create the swift endpoint but point it to the radosgw vip endpoint. and then it works, obviously swift middleware and other stuff that is swift specific wont work ever08:51
*** gameon has joined #openstack-ansible08:51
openstackgerritlei zhang proposed openstack/openstack-ansible-ceph_client master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53208608:51
jrosserandymccr: thats great - have you ever needed/wanted a seperate LB for radosgw to scale it independantly of all the API endpoints?08:53
andymccrjrosser: personally ive not set that up, but i think it would be reasonably ok to setup with how it is now08:54
openstackgerritlei zhang proposed openstack/openstack-ansible-galera_client master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53208808:56
openstackgerritlei zhang proposed openstack/openstack-ansible-galera_server master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53209108:59
*** SmearedBeard has joined #openstack-ansible09:00
ashakyifei: thanks for sharing that. Hopefully that means it's not me doing something totally crazy09:01
openstackgerritlei zhang proposed openstack/openstack-ansible-haproxy_server master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53209409:03
openstackgerritlei zhang proposed openstack/openstack-ansible-lxc_container_create master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53209609:04
jafehaandymccr, jrosser evrardjp we had set the radosgw as our swift endpoint, but i never got the glue for keystone working. i'm glad this goes ahead though.09:13
jafehai'm not sure about the integration within ceph-ansible, but i think for serving one endpoint we'd need to deploy haproxy on those ceph nodes.09:14
*** sxc731 has joined #openstack-ansible09:15
jrosserjafeha: it's notes as a todo here https://review.openstack.org/#/c/517856/ see the comment in patch set 609:15
jafehajrosser, thanks :D09:17
andymccr^ should work. ive done it manually a few times09:17
andymccrto integrate OSA with a separate ceph-ansible deploy at least09:17
jafehathats the easy way to go, i had built it with a separate haproxy deployment on the storage nodes because our infra hosts are painfully slow / low bandwidth09:19
*** bhujay has quit IRC09:21
*** SmearedBeard has quit IRC09:21
*** bhujay has joined #openstack-ansible09:27
openstackgerritlei zhang proposed openstack/openstack-ansible-lxc_hosts master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53212209:28
openstackgerritlei zhang proposed openstack/openstack-ansible-memcached_server master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53212509:31
openstackgerritlei zhang proposed openstack/openstack-ansible-openstack_hosts master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53212709:35
openstackgerritlei zhang proposed openstack/openstack-ansible-openstack_openrc master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53212909:39
openstackgerritlei zhang proposed openstack/openstack-ansible-ops master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53213009:41
openstackgerritlei zhang proposed openstack/openstack-ansible-os_almanach master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53213109:45
*** armaan has quit IRC09:46
*** armaan has joined #openstack-ansible09:47
*** chhavi__ has quit IRC09:48
openstackgerritlei zhang proposed openstack/openstack-ansible-os_aodh master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53213309:48
*** chhavi__ has joined #openstack-ansible09:49
openstackgerritGaudenz Steinlin proposed openstack/openstack-ansible master: Stable keepalived priorities  https://review.openstack.org/53213509:52
openstackgerritlei zhang proposed openstack/openstack-ansible-os_barbican master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53213709:53
*** mardim has quit IRC09:54
openstackgerritlei zhang proposed openstack/openstack-ansible-os_ceilometer master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53213909:57
*** udesale has joined #openstack-ansible09:59
*** mardim has joined #openstack-ansible10:01
*** pbandark has joined #openstack-ansible10:01
openstackgerritlei zhang proposed openstack/openstack-ansible-os_cinder master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53214010:01
openstackgerritlei zhang proposed openstack/openstack-ansible-os_cloudkitty master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53214310:05
openstackgerritlei zhang proposed openstack/openstack-ansible-os_designate master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53214410:07
*** wspthr has joined #openstack-ansible10:07
*** armaan has quit IRC10:07
*** armaan has joined #openstack-ansible10:07
openstackgerritlei zhang proposed openstack/openstack-ansible-os_glance master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53214510:10
openstackgerritlei zhang proposed openstack/openstack-ansible-os_gnocchi master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53214810:15
openstackgerritlei zhang proposed openstack/openstack-ansible-os_heat master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53215010:19
openstackgerritlei zhang proposed openstack/openstack-ansible-os_horizon master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53215110:23
openstackgerritlei zhang proposed openstack/openstack-ansible-os_ironic master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53215210:26
openstackgerritlei zhang proposed openstack/openstack-ansible-os_keystone master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53215310:29
*** mpranjic has quit IRC10:31
openstackgerritlei zhang proposed openstack/openstack-ansible-os_magnum master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53215410:32
*** taseer4 is now known as Taseer10:33
openstackgerritGaudenz Steinlin proposed openstack/openstack-ansible master: Stable keepalived priorities  https://review.openstack.org/53213510:35
openstackgerritlei zhang proposed openstack/openstack-ansible-os_molteniron master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53215510:36
openstackgerritlei zhang proposed openstack/openstack-ansible-os_monasca-agent master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53215610:41
openstackgerritlei zhang proposed openstack/openstack-ansible-os_monasca-ui master: Fix the incorrect git.openstack.org source URL  https://review.openstack.org/53215710:43
evrardjpcloudnull mhayden andymccr odyssey4me mgariepy hwoarang spotz Could you please not merge new features into master this week, until the most critical bugs are resolved? Thank you!10:44
hwoarangevrardjp: sure thing. Do you have a list for us during the meeting?10:46
evrardjphwoarang: yes, we'll go through them, and I will discuss the context during the meeting too.10:46
evrardjpThanks for your regular presence, it's a pleasure to see you there :)10:47
evrardjpI am not sure everyone realizes how much I like to see people attending the meetings, and be active :D10:48
hwoarangah good. Looking forward to the meeting then10:48
hwoarangwould be nice for gerrit to provide a way to block new checkins though :)10:49
hwoarangfeature request!10:49
*** chyka has joined #openstack-ansible10:51
*** chyka has quit IRC10:55
evrardjpI am fine with people adding new features and testing them, as long as they are not +W10:56
*** chhavi__ has quit IRC10:57
*** tacco has joined #openstack-ansible11:03
*** stuartgr has joined #openstack-ansible11:15
*** udesale has quit IRC11:24
*** pbandark1 has joined #openstack-ansible11:34
jafehahey everybody. i'm currently debugging some issues relating the unbound configuration. there seem to be two different regional zones to being set. the unbound role sets the unbound_regional_zone (defaults to RegionOne.openstack) and the openstack_domain (defaults to openstack.local) from the osa main repository. can anyone explain me the difference of those two?11:35
*** pbandark has quit IRC11:35
*** pbandark1 is now known as pbandark11:35
*** udesale has joined #openstack-ansible11:36
jafehaand also: the unbound client role seems not to set any search domain, which breaks fqdn resoution for my compute nodes.11:37
*** udesale has quit IRC11:39
*** udesale has joined #openstack-ansible11:39
odyssey4mejafeha we may need to consult with logan- on that, but it sounds like there's an extra bit of default wiring we might need to do there11:40
odyssey4meevrardjp I'd suggest using an administrative -2 on any patches you see are doing so. I, personally, am not going to have time for new features anyway in the next week or two.11:41
jafehaodyssey4me, seems to me like we're having some issues with our metal, not the containers.11:41
jafehathe vars could imho be consolidated though.11:42
odyssey4mejafeha perhaps, if they're intended to be the same by default - but logan- would need to confirm as he's the developer of the unbound 'feature'11:42
jafehasure, i might miss something here11:43
odyssey4methe openstack_domain is meat as the default domain for instances, whereas the unbound domain is for the back-end IIRC11:43
odyssey4me*meant11:43
jafehaodyssey4me, thats what i thought before, but then the vars and their settings keep confusing me: openstack_domain: openstack.local and lxc_container_domain: "{{ openstack_domain }}" and unbound_regional_zone: "{{ service_region }}.{{ unbound_root_zone }}"11:47
odyssey4mejafeha yep, which is why I think logan- needs to provide insight11:48
jafehabut i'll consult with logan- mbe he can light things up for me11:48
evrardjpodyssey4me: you're good then :) I am trying communication, see how it goes.11:48
*** SmearedBeard has joined #openstack-ansible11:50
bhujayodyssey4me: Trying hard to  integrate horizon with cloudkitty , I followed gokhan's stable/pike role https://github.com/b3lab/openstack-ansible-os_cloudkitty/tree/stable/pike , So far the steps I have taken is including cloudkitty-dashboard git source in openstack_services.yml and running the symbolic link creation through  horizon_post_install.yml . From CLI cloudkiity seems to be working fine .However ,  from dashboard admin cloudkitty11:57
bhujayservice mapping is failing with the following errors https://gist.github.com/anonymous/bfa44ee54afefe929241beeea8f1c5aa , any hint ?11:57
odyssey4mebhujay it looks like the dashboard itself might have a bug - not sure how well it's maintained by the cloudkitty project, or if the cloudkitty project itself is well maintained11:58
odyssey4meit might also just be a missing bit of horizon config that's needed for cloudkitty - I don't know11:59
odyssey4megiven that errr put it together, perhaps he can help when he comes online11:59
evrardjpbhujay: probably worth asking huats11:59
evrardjpiirc11:59
bhujayevrardjp:Yes I was there in cloudkitty iirc , given the error , actually asking for a correct SHA that I can include in openstack_service.yml12:01
bhujayodyssey4me:As always sir , your hint is helpful . I will at least plan  few experiments with  some older commits12:03
odyssey4mebhujay not sure if older will help, horizon's changed quite a bit and I'm not sure if the cloudkitty dashboard has caught up to those changes12:03
odyssey4mebut sure, I'd be looking at the differences - the last cloudkitty dashboard commit vs major changes in horizon and cloudkitty12:04
bhujayodyssey4me and evrardjp , just wanted to update that my month long effort on gnocchi and aodh finally given result . Was able to test sucessfully heat autoscalling , it worked like a charm ! now  the last is billing part  and I am planning to test open for my organization12:09
evrardjpbhujay: wow, that's great to hear. We need to make this work in a scenario12:10
bhujaysure , need to learn heat more . For that I have formed a small team  who will focus on different use cases for our current applications12:11
odyssey4mebhujay awesome, any change you can share how you put it all together in some way - blog or etherpad?12:11
odyssey4meor gist12:11
odyssey4me*chance12:11
odyssey4meevrardjp happy to approve https://review.openstack.org/529424 ?12:12
evrardjpodyssey4me: why not, I trust you.12:12
evrardjp:D12:12
evrardjpfuture will tell me if I should have or not :p12:13
odyssey4meevrardjp also, does your -2 still stand here? it seems old: https://review.openstack.org/#/c/510551/12:13
evrardjpremoved.12:13
odyssey4methx12:13
jafehaevrardjp, talking about scenarios, i'm currently giving my ovs aio tests another run, do your patching, i'll get back to you as soon as i've completed a successful run12:15
*** eumel8 has joined #openstack-ansible12:16
bhujayas of now i used only  the learning template provided by heat , heat irc was great help . There  aodh listener listenes for a gnocchi cpu utilization threshold and once reached  aodh notifier triggers an autoscale group . This worked so smooth that I am confident we will apply it for our real applications soon and update you12:16
bhujayjafeha: is it ovs bridge ? does it mean we will have option to choose linuxbridge or ovs  for osa deployment ? I was browsing if there is osa integration possible for opendaylight but understood it depneds on ovs , it will  be great if osa covers these stuffs12:20
*** sxc731 has quit IRC12:20
jafehabhujay, osa already covers the deployment of ovs, there is also some work being done to deploy opendaylight in future releases (dunno, mbe queens).12:21
odyssey4meyep, queens12:22
jafehai'm currently working on an ovs aio scenario for ovs, as the aio only supports linuxbridges so far12:22
hwoarangjafeha: that's interesting. epalper is also looking into aio+ovs. maybe you can exchange notes :)12:23
jafehathis scenario is also needed for gate checks as far as i understood evrardjp12:23
jafehahwoarang, nice to know :D12:23
jafehai'm currently testing with the queens beta, mbe i should better test it with pike to prevent running into completely unrelated issues ;)12:25
gokhan_bhujay, ı didn't test cloudkitty dashboard, because we won't use it. we also developed a billing service and for it we developed a new dahboard. our billing service is not yet opensource. Our billing service benefits from cloudkitty. For your error I think there is a problem on cloudkittydasboard itself. it is not related OSA.12:27
eumel8evrardjp: We have the approval for project doc translation from the TC. So we can start whenever we want ;)12:28
evrardjpeumel8: that is good, everything is set into place :)12:30
evrardjpI will work with the appropriate people12:31
bhujaygokhan_: thanks gokhan,  I will check if it is possible to debug , billing/ sowing the price information  is a important factor for my project. IS there any other alternative  opensource or some low cost solutions ?12:31
evrardjpthat would probably means AJaeger, odyssey4me, and you.12:31
eumel8evrardjp: just to find out how jobs will be implemented, maybe copy things from other repos12:33
evrardjpexactly12:33
gokhan_bhujay, I don't now. if our boss decides to make it opensource our dashboard, I will inform you.12:33
evrardjpwe have a simpler case because we don't have (currently) the same depths of jobs12:33
bhujayjafeha: That was a helpful update . I got  few ref now on osa ovs . thanks12:34
eumel8evrardjp: problems are always in the details ;)12:36
jafehabhujay, you're welcome. i'm just trying to help a little here, nothing compared to the cores12:37
gokhan_hi evrardjp I wrote openstack  panko(openstack event service)  role and now testing it. if it passes my test, I want to share it.12:39
evrardjpgokhan_: a lot of precedents already exists :)  Want to include it in the openstack-ansible repos and be maintainer of it, or just want to point documentation about how integration of your role should be done?12:45
evrardjpbeing in the openstack-ansible-.* repos will have the advantage of more eyes, and be part of our processes (role maturity, bot updates...)12:46
evrardjpbut we expect you'd help us maintain it12:47
eumel8how to acquire new cores... ;)12:49
evrardjp:D12:51
gokhan_evrardjp, after testing it,  I wanna include it in  openstack-ansible repos. For telemetry stack it could be good.12:51
evrardjpeumel8: If you have additional advise there, I'm all ears! :D12:51
evrardjpgokhan_: I fully agree.12:52
evrardjpOn top of that, we can make it work as a part of an autoscaling scenario, which would ensure autoscaling work as expected for you12:52
*** savvas` has joined #openstack-ansible12:53
*** savvas` has joined #openstack-ansible12:53
epalperjafeha: Thanks for looking into aio+ovs. I was trying to bringup aio+ovs with osa, but it failed. I thought this support is already exists in osa12:53
epalperjafeha: you could find the details in an email with subject "[openstack-ansible] problems with bringing up openstack in AIO flavor with OVS"12:55
*** savvas` has quit IRC12:55
*** savvas` has joined #openstack-ansible12:55
*** smatzek has joined #openstack-ansible12:56
epalperjafeha: if you send me link to code patches, i could try on my setup12:56
*** savvas` has quit IRC12:57
*** savvas` has joined #openstack-ansible12:57
jafehaepalper, i'm having a really, really raw patchset yet, which did not deploy a single time so far.12:57
epalperjafeha: okay, please let me know once it's ready for testing12:59
gokhan_evrardjp yep on telemetry stack we can work on autoscaling scenario. after testing panko, I will struggle to work on autoscaling scenario with telemetry services and heat.12:59
gameonHello all - I have deployed Ceph on my compute nodes, in a hyperconverged fashion. My local storage on each Hypervisor is now reported at 20+TB per hypervisor, Horizon doesn't account for the fact it's shared. Is there a way to tweak this behavior? Thank you13:04
*** udesale has quit IRC13:06
evrardjpgameon: that's probably more a horizon or a nova thing, we are merely deployers.13:06
jafehagameon, afair there is a long standing bug for wrongly storage calculations in horizon. so that might be even unrelated to your setup. we have a triple replica ceph cluster, which is summed to crazy amounts of storage13:06
evrardjpandymccr: are you there?13:06
evrardjpdoes this ring you a bell: https://bugs.launchpad.net/openstack-ansible/+bug/1741471/comments/4 ?13:07
openstackLaunchpad bug 1741471 in openstack-ansible "keystone upgrade to Queens failure due to new handler" [Undecided,New] - Assigned to Jean-Philippe Evrard (jean-philippe-evrard)13:07
*** udesale has joined #openstack-ansible13:08
gameonevrardjp : Indeed, I had wondered if anyone had seen it, thank you :)13:08
gameonjafeha: That's interesting, I will have a look into if I can solve it but it sounds like it may be something I have to live with13:08
gameonThanks both evrardjp jafeha13:08
jafehagameon, i saw the issue and accepted that storage calculations across multiple supported types of distributed and non-distributed storages are a hard problem to solve13:14
*** dave-mccowan has joined #openstack-ansible13:15
*** woodard_ has quit IRC13:18
*** dave-mccowan has quit IRC13:21
*** dave-mccowan has joined #openstack-ansible13:26
*** sxc731 has joined #openstack-ansible13:28
*** bhujay has quit IRC13:33
masberevrardjp, yes, I am following the docs to create the bridges now. Why the IPs is assigned to the mgmt-bridge?13:34
masberevrardjp, if I follow this example https://docs.openstack.org/project-deploy-guide/openstack-ansible/pike/app-config-test.html it doesn't assign IP to eth0, how is the server going to communicate to the rest of the network?13:35
*** woodard has joined #openstack-ansible13:35
Bico_Finomorning!13:38
*** Smeared_Beard has joined #openstack-ansible13:47
*** esberglu has joined #openstack-ansible13:48
*** SmearedBeard has quit IRC13:48
masberhi, I am trying to setup my first OSA installation and need some help with the networking13:51
masberI am following this document https://docs.openstack.org/project-deploy-guide/openstack-ansible/pike/app-config-test.html13:52
masberand I can see that the physical interface eth0 does not have an IP, is it because it will take the IP assigned from br-mgmt?13:53
jrosserin that example eth0 (the physical interface) is a trunk13:53
jrosseryou then see the vlans broken out onto eth0.10/20/3013:54
jrossersee the table "Network CIDR/VLAN assignments" this is how the example assumes the connectivity to the hosts is arranged13:55
masberjrosser, but is this assuming that I need to setup a vlan in the physical switch?13:57
masber*the vlans13:57
*** sxc731 has quit IRC13:58
jrossermasber: yes that is the assumption. you are of course free to redo it however you wish, to achieve those three seperate networks13:58
*** chhavi__ has joined #openstack-ansible13:58
jrosserOSA assumes that you've got this all sorted out before starting the deploy, and picks up from br-<thing> onward13:59
*** tacco has quit IRC13:59
*** tacco has joined #openstack-ansible14:01
masberjrosser, ok, I don't have access to the physical switch... is there a possibility that I can do something like bridge_ports eth0 (as a flat network)?14:02
*** shardy_afk has quit IRC14:17
*** afred312 has quit IRC14:20
*** afred312 has joined #openstack-ansible14:20
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible master: Fix sources-branch-updater and add docs  https://review.openstack.org/52937714:20
*** sxc731 has joined #openstack-ansible14:22
*** tacco has quit IRC14:25
*** smatzek has quit IRC14:28
*** yifei1 has joined #openstack-ansible14:28
*** smatzek has joined #openstack-ansible14:28
*** smatzek has quit IRC14:28
*** yifei1 has left #openstack-ansible14:30
*** tacco has joined #openstack-ansible14:33
evrardjpdear cloudnull, DimGR, andymccr, d34dh0r53, hughsaunders, b3rnard0, palendae, odyssey4me, serverascode, rromans, erikmwilson, mancdaz, _shaps_, BjoernT, claco, echiu, dstanek, jwagner, ayoung, prometheanfire, evrardjp, arbrandes, mhayden, scarlisle, luckyinva, ntt, javeriak, spotz, vdo, jmccrory, alextricity25, jasondotstar, admin0, michaelgugino, ametts, v1k0d3n, severion, bgmccollum, darrenc,14:38
evrardjpJRobinson__, asettle, colinmcnamara, thorst, adreznec, eil397, qwang,nishpatwa_, cathrichardson, drifterza, hwoarang, cshen, ullbeking:14:38
evrardjpthe osa bug triage will start in 1h30’. Please have a look at the bug list before starting: https://etherpad.openstack.org/p/osa-bugtriage14:38
evrardjp1h20, my bad.14:38
hwoarangtime flies14:38
mhaydenohai14:39
hwoarango/14:39
*** markvoelker has quit IRC14:40
openstackgerritMajor Hayden proposed openstack/openstack-ansible-lxc_hosts stable/pike: Allow NetworkManager to work (if present)  https://review.openstack.org/53220114:43
admin0\o14:43
admin0long time no see :)14:43
*** jwitko_ has joined #openstack-ansible14:50
*** smatzek has joined #openstack-ansible15:11
*** smatzek has quit IRC15:11
*** smatzek has joined #openstack-ansible15:11
*** markvoelker has joined #openstack-ansible15:13
*** markvoelker has quit IRC15:16
openstackgerritTaseer Ahmed proposed openstack/openstack-ansible-os_congress master: Introduce os_congress role in gerrit  https://review.openstack.org/52249115:23
*** bhujay has joined #openstack-ansible15:23
*** markvoelker has joined #openstack-ansible15:25
cloudnullmornings15:29
spotzhey15:30
cloudnulljrosser: re - multiple container store: yes that is in pike.15:31
jrossercloudnull: oooh ok thats great, missed that getting backported15:31
cloudnullhttps://github.com/openstack/openstack-ansible-lxc_container_create/blob/stable/pike/defaults/main.yml#L79-L8415:32
cloudnulli'm not sure what tag that got into15:32
cloudnullbut it is in the stable branch15:32
evrardjpcloudnull I am gonna do a tag soon anyway15:33
cloudnullwoot!15:33
evrardjpso, we will be good15:33
mgariepycloudnull, https://github.com/openstack/openstack-ansible-lxc_container_create/commit/270743d0423846a209c0f92053d8505796c9f8f515:33
mgariepyyou can see the branches in the commit.15:33
mgariepy:D15:33
*** bhujay has quit IRC15:34
cloudnullorly!15:34
mgariepythanks to evrardjp that pointed it to me last year :)15:34
cloudnullthat's a super handy feature15:34
mgariepyyep indeed.15:34
evrardjpyw :)15:35
evrardjpIt's also on gerrit iirc15:35
evrardjpgithub is just very fast in my workflow15:36
evrardjp(see included in, on the top right in gerrit)15:36
*** sxc731 has quit IRC15:37
*** sar has joined #openstack-ansible15:42
ashakyifei: so I just ended up at the same place as you. My galera servers ar eno longer in the load balancer. It seems that haproxy is trying to do healthchecks on port 9200 of the galera clusters. There's nothing listening on that port on them. release notes here: https://docs.openstack.org/releasenotes/openstack-ansible/unreleased.html talk about this being a new feature in tag 17.0.0.0b215:54
*** SerenaFeng has joined #openstack-ansible15:59
evrardjpBug triage cloudnull, DimGR, andymccr, d34dh0r53, hughsaunders, b3rnard0, palendae, odyssey4me, serverascode, rromans, erikmwilson, mancdaz, _shaps_, BjoernT, claco, echiu, dstanek, jwagner, ayoung, prometheanfire, evrardjp, arbrandes, mhayden, scarlisle, luckyinva, ntt, javeriak, spotz, vdo, jmccrory, alextricity25, jasondotstar, admin0, michaelgugino, ametts, v1k0d3n, severion, bgmccollum,15:59
evrardjpdarrenc, JRobinson__, asettle, colinmcnamara, thorst, adreznec, eil397, qwang,nishpatwa_, cathrichardson, drifterza, hwoarang, cshen15:59
evrardjpHere is our bug list for today https://etherpad.openstack.org/p/osa-bugtriage15:59
evrardjp#startmeeting openstack_ansible_meeting15:59
openstackMeeting started Tue Jan  9 15:59:42 2018 UTC and is due to finish in 60 minutes.  The chair is evrardjp. Information about MeetBot at http://wiki.debian.org/MeetBot.15:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:59
*** openstack changes topic to " (Meeting topic: openstack_ansible_meeting)"15:59
openstackThe meeting name has been set to 'openstack_ansible_meeting'15:59
evrardjp#topic rollcall15:59
*** openstack changes topic to "rollcall (Meeting topic: openstack_ansible_meeting)"15:59
evrardjpwaiting for a couple of minutes before starting15:59
cloudnullo/16:00
d34dh0r53o/16:00
mgariepyhalf-o/16:00
evrardjpwow d34dh0r53 is in the place! Glad to see you :)16:01
evrardjp#topic new year16:01
*** openstack changes topic to "new year (Meeting topic: openstack_ansible_meeting)"16:01
evrardjpPlease allow me to start the first meeting of 2018 by wishing you all an happy new year.16:01
d34dh0r53:) good to be here16:01
evrardjpI hope you had nice winter holidays.16:01
evrardjp:)16:01
d34dh0r53Likewise16:01
evrardjp#topic this week's focus introduction16:02
*** openstack changes topic to "this week's focus introduction (Meeting topic: openstack_ansible_meeting)"16:02
prometheanfirehi16:02
evrardjpA new topic/section on our weekly meeting!16:02
evrardjpA little backstory first.16:02
evrardjpWe faced a few challenges at the beginning of this cycle.16:02
evrardjpWhile these challenges came mostly from external factors, I think we sometimes failed to work together in their resolution.16:02
evrardjpAfter analysis, I've noticed that it mostly came from different people working on different things, and then those different things would land together, making it harder to fix compared to a more coordinated approach.16:02
*** sxc731 has joined #openstack-ansible16:03
evrardjpAfter discussing with a few of you, I realized reducing the amount of community meetings also reduced our communication abilities, which led to less coordination.16:03
evrardjpI think we should therefore have a "week's focus".16:03
openstackgerritMerged openstack/openstack-ansible master: Stable keepalived priorities  https://review.openstack.org/53213516:03
evrardjpThis "focus" thing will allow us to be in sync with what we do together, avoid misunderstandings.16:03
evrardjpAt each community meeting (currently happening at the last Tuesday of the month), I'll propose next month focuses, and we'll adapt the planning together.16:03
evrardjpWhat's your opininon? Is there anyone opposed to this idea?16:03
spotz\o/ I'm late catching up16:04
spotzIf we're having focuses we also need to allow for emergencies16:05
evrardjpyeah I think we need ofc space for modifications of the planning16:05
evrardjpbut they should be relatively minimum, and only about fixing something we should triage as critical16:06
evrardjp(which means blocking people because of broken gates)16:06
spotzWell a bug could be critical as well. Maybe a list of what constitutes critical16:07
evrardjpthat's what I meant16:07
evrardjpmodifications of the planning should be minimal, the modification should only happen in case of a critical bug appearing.16:08
evrardjpalso I think this should be a FOCUS not a hinderance16:08
evrardjppeople should still be able to do their usual work, but remember what the focus is16:09
*** markvoelker has quit IRC16:09
evrardjpto avoid stepping on each other toes16:09
odyssey4meo/ not sure how this would play out - could you give an example of what a focus would be, and what that would mean in real terms?16:10
openstackgerritMerged openstack/openstack-ansible master: Avoid retrieving IP from a missing bridge  https://review.openstack.org/52473816:11
evrardjpodyssey4me: I thought of different focuses, depending on where we are in the cycle16:11
evrardjphandling deprecations would be one16:11
evrardjpso if during that week's focus we are cleaning the old things, we know the next week we could have things linked to the removal appearing.16:12
openstackgerritGaudenz Steinlin proposed openstack/openstack-ansible stable/pike: Stable keepalived priorities  https://review.openstack.org/53223016:13
evrardjpfor this week I thought the focus could be on fixing the upgrade from P-Q. let me explain that:16:13
odyssey4meok, that works for short term things - but what about long term things like implementing the nspawn usage or changing up the inventory or changing up how the software installs are done16:13
evrardjpThis could still integrate.16:13
evrardjpA cycle is 6 months16:14
evrardjpif we plan the focus month per month, it would allow us to have a big picture and a more organized planning, together, of what happens in the cycle16:14
odyssey4mewell, I'd suggest that you give your suggestion a try - but bear in mind that some things are long term an dwon't fit well with that... what you're suggesting sounds like a good thing for people who are looking to help, but don't know where to start16:15
evrardjpWe have a lot of challenges for the last part of the Queens cycle. I know we have many new features to introduce,16:15
evrardjpbut I'd like to first fix the , in order to be able to upgrade from P-Q, whether they are roles or the AIO.16:15
evrardjpIf we don't merge new things like nspawn this week, it would help on getting there16:15
odyssey4mehaving a sort-of breakdown for the cycle where there is some sort of focus for a period for the general community to chip in is a great idea IMO16:16
evrardjpthanks for your support16:16
odyssey4methat allows bugs to be arranged into the schedule too, which might be a nice way of smashing more of them16:16
evrardjpLike I said it should be a focus, not a hinderance. So people should still be able to do their work16:16
openstackgerritGaudenz Steinlin proposed openstack/openstack-ansible stable/ocata: Stable keepalived priorities  https://review.openstack.org/53223216:17
evrardjpthey should just remember that if there is a bug smash for example, introducing a large feature would be counter productive16:17
evrardjpor at the opposite, if there is a large feature that we expect to require a bug smash, we can have the "focus" done that way16:17
evrardjpanyone other opinion?16:18
evrardjpif not let's move to try it, and see how it goes, start the bug triage for today.16:18
evrardjp#topic this week's bugs.16:19
*** openstack changes topic to "this week's bugs. (Meeting topic: openstack_ansible_meeting)"16:19
evrardjpwe have some nasty bugs this week, and a whole series of bugs too.16:19
*** RandomTech has joined #openstack-ansible16:19
evrardjp#link https://bugs.launchpad.net/openstack-ansible/+bug/174199016:20
openstackLaunchpad bug 1741990 in openstack-ansible "os_cinder Associating QoS types to volume types fails" [Undecided,New]16:20
*** udesale has quit IRC16:20
RandomTechIs it normal for the rabbgitMQ check to fail the first time you run setup-infrastructure but work the second time?16:20
odyssey4memy might want to switch to using storyboard - not sure exactly how it works, but my impression is that was designed with this work method in mind16:20
evrardjpodyssey4me: interesting. I will have a look at that.16:21
odyssey4meawesome16:22
spotzodyssey4me: We've played with storybooard a little during Upstream Institute, it's definitely good for grouping like topics and smaller pieces of an issue. It does take some getting used to16:22
evrardjpthe whole point of this previous topic was to get attention on the collaborative part. I think it would be helpful to avoid clashes.16:22
openstackgerritGaudenz Steinlin proposed openstack/openstack-ansible stable/newton: Stable keepalived priorities  https://review.openstack.org/53223316:23
odyssey4meyeah, it may help reduce the amount of unplanned work coming into play16:23
evrardjpto get back to the bug triage now, I think that this issue looks valid16:23
evrardjpwhat about marking it as confirmed and high?16:23
*** SerenaFeng has quit IRC16:24
evrardjpok I will continue the bug triage road.16:25
cloudnullon the road again16:25
evrardjphaha16:25
evrardjpthat's a good song, and a good radio broadcast.16:25
evrardjpcloudnull: do you happen to agree on the bug classification?16:25
cloudnullfor keepalived ?16:26
cloudnull53223316:26
evrardjpfor https://bugs.launchpad.net/openstack-ansible/+bug/174199016:26
openstackLaunchpad bug 1741990 in openstack-ansible "os_cinder Associating QoS types to volume types fails" [Undecided,New]16:26
cloudnullhahaha .16:26
evrardjpconfirmed? high?16:26
* cloudnull looking at the wrong link :)16:26
odyssey4meyeah, looks valid16:26
odyssey4meagreed16:26
evrardjpok thanks.16:27
*** pbandark1 has joined #openstack-ansible16:27
cloudnull++16:27
evrardjpnext one is fun16:27
*** pbandark has quit IRC16:27
*** pbandark1 is now known as pbandark16:27
evrardjp#link https://bugs.launchpad.net/openstack-ansible/+bug/174163416:27
openstackLaunchpad bug 1741634 in openstack-ansible "virtualenv-tools is unreliable for changing path in venvs" [Critical,New] - Assigned to Jean-Philippe Evrard (jean-philippe-evrard)16:27
cloudnulli might set that to high16:27
evrardjpcloudnull: we agree then :)16:27
odyssey4mevalid, high/confirmed16:27
evrardjpfor https://bugs.launchpad.net/openstack-ansible/+bug/1741634 I think we should mark it as critical16:27
odyssey4meactually, yeah - critical makes sense16:28
evrardjpbecause it will break gates and expectations16:28
evrardjpquestion16:28
cloudnullis it failing for us these days16:28
cloudnullor is that just due to the project being unmaintaine d?16:28
evrardjpthe project is unmaintained16:28
evrardjpand won't accept a simple change to change the shebang16:28
evrardjpso we are kinda stuck16:29
evrardjpso that was my question16:29
evrardjpvendor in, or use another thing16:29
cloudnullcan we just fork and fix16:29
cloudnulland then look for an alternitive later?16:29
evrardjpI've checked what it would need to do for an alternative16:29
evrardjpthat's very simple16:29
* hwoarang was dragged to some internal talks and is catching up now16:29
evrardjphttps://review.openstack.org/#/c/531731/16:29
evrardjpwas just wondering if you agreed on the approach, because we're gonna have to backport that back down.16:30
evrardjpvery low.16:30
evrardjpI guess we can discuss in the review now16:30
evrardjplet's move to next bug16:30
cloudnullI'd probably fork and fix the unmaintained project16:30
cloudnullthen spec out an actual replacement16:31
evrardjpok that's really possible too.16:31
odyssey4mecloudnull could, but then how do we publish the updated version to pypi?16:31
evrardjpIt would be quite easy and less risky16:31
evrardjpsomeone could take the responsibility for it I guess16:31
cloudnullodyssey4me: yes. if the maintainer is not wanting to deal with it we cloud take it over on pypi if they're willing16:31
evrardjpodyssey4me: the fork approach is less risky but logistically more complex16:31
hwoarangsed is simple enough imho16:32
odyssey4methe tool doesn't seem to do much else IIRC16:32
evrardjpyeah I think sed _should_ cover us enough.16:32
evrardjpbut that's the thing, it's only a _should_ , according to what I have seen.16:32
cloudnullif it works +116:33
evrardjpok16:33
evrardjplet's discuss next bug then16:33
evrardjpit blocks this patch :p16:33
evrardjp#link https://bugs.launchpad.net/openstack-ansible/+bug/174147116:33
openstackLaunchpad bug 1741471 in openstack-ansible "keystone upgrade to Queens failure due to new handler" [Undecided,New] - Assigned to Jean-Philippe Evrard (jean-philippe-evrard)16:33
evrardjpthis one is fun too, and is not our fault.16:33
evrardjpRight now I don't know how to fix it, and I will dig deeper (except if someone knows how to fix this)16:35
odyssey4memaybe logan- can help with that as he worked on the LB thingy16:35
logan-o/16:36
evrardjpthe alternative would be to install ansible==2.3 just before running the os_previous_* role, and then do the upgrade after an update of ansible.16:36
logan-issue there is upgrades right?16:36
evrardjpodyssey4me: it's a pure ansible failure16:36
evrardjpbut yeah :)16:36
odyssey4meah yes, this is actually an issue with the way our role tests upgrades16:36
evrardjplogan-: yes16:36
evrardjplogan-: odyssey4me have a look at my last comment16:36
odyssey4mewe use the newer ansible to test the older role code16:36
evrardjpyes16:36
logan-https://github.com/openstack/openstack-ansible-os_keystone/blob/a48a73089286a370312a35fc7df54a6a3a513fa2/handlers/main.yml#L107-L10916:37
evrardjpwe could technically change the older role by adding {{ role_dir }} iirc16:37
logan-could we just drop that in the previous branch16:37
*** markvoelker has joined #openstack-ansible16:37
odyssey4meso yes, we should either change how the upgrade test runs in the roles - or work out a workaround16:37
evrardjplogan-: that sounds a bad idea16:37
odyssey4melogan- dropping it in the older branch creates turtles16:37
evrardjpwe could define that handler in the playbook without needing that16:37
odyssey4medrop into pike, breaks the pike upgrade test - drop into ocata doesn't support the listen thing in the handler16:38
evrardjpbut that's just the start of all our failures16:38
evrardjpwe are NOT testing pike in reality.16:38
logan-gotcha odyssey4me16:38
evrardjpodyssey4me: in this case that would stop at Pike, but yes, it could technically.16:38
evrardjp(ansible 2.3 and 2.2 having the same behavior)16:38
odyssey4mebest longer term strategy is to make the upgrade test use the right ansible for the initial deploy... but then it also needs to implement the older roles for everything... so the whole upgrade jobs needs to change quite dramatically16:39
evrardjpmy concern is that we aren't testing pike to queens16:39
openstackgerritGaudenz Steinlin proposed openstack/openstack-ansible stable/pike: Avoid retrieving IP from a missing bridge  https://review.openstack.org/53224316:39
evrardjpodyssey4me: yeah that's my concern.16:39
openstackgerritGaudenz Steinlin proposed openstack/openstack-ansible stable/ocata: Avoid retrieving IP from a missing bridge  https://review.openstack.org/53224416:39
evrardjpthat's too big of a change.16:39
odyssey4meit might be better to just make the role tests use the integrated build, but with a more limited inventory16:39
openstackgerritGaudenz Steinlin proposed openstack/openstack-ansible stable/newton: Avoid retrieving IP from a missing bridge  https://review.openstack.org/53224516:39
odyssey4meagain, that's a significant body of work16:40
evrardjpI thought the change of ansible version just before and after sounded better, but I don't think it's a solution, merely a workaround16:40
evrardjpodyssey4me: I agree.16:40
evrardjpwhich could be a focus in the future ! :D16:40
*** sar has quit IRC16:40
evrardjp(I am trying to sell this one very hard!)16:40
evrardjpanyway16:40
odyssey4mecurrently it deploys the current branch for all things except the role being tested, it then deploys the previous branch role, then deploys the current branch role16:41
evrardjpI think we are safe to mark this as confirmed.16:41
evrardjpodyssey4me: yes16:41
evrardjpand under ansible 2.4 it doesn't do previous for all tasks16:41
odyssey4meso it's not as simple as just switching the ansible version, because that may not work with the new roles for all the infra16:41
evrardjpit does for the main.yml includes, but not their includes.16:41
evrardjpno I meant just before the os_previous_role16:42
evrardjpthe rest being still the current version16:42
odyssey4meoh bother - I've seen a pretty nasty pattern to do the different types of includes based on ansible version, but it's almost unreadable16:42
evrardjpno that's not what I meant16:42
evrardjpwe do have many playbooks16:42
evrardjpthe last ones are doing the previous branch role execution, then the current branch role execution and the functional testing16:43
evrardjpI'd insert a ansible downgrade based on tests/common/previous before the previous branch execution, and an ansible upgrade based on tests/common16:44
evrardjpbut that's all a mess IMO16:44
odyssey4meif we can finalise getting the integrated build to using a static inventory then we can switch the roles to using it instead of something else16:44
odyssey4mehmm, that could work - messy as you say, but workable16:44
odyssey4meanother option could just be to be rid of tox and to use two venvs16:44
odyssey4meone for current, one for previous16:45
evrardjpthat sounds nice16:45
odyssey4meinstead of using tox to build the venv, do it ourself16:45
evrardjpso we'd have to run x shell tasks, one to do the infra, one to do the old role with previous venv, the rest?16:45
evrardjpand one with the rest*16:46
evrardjpthat sounds cleaner in the meantime we reform stuff.16:46
odyssey4mewell, tox is just running scripts anyway - so we just switch to zuul executing the scripts and make the scripts facilitate everything16:46
odyssey4meI did hope to get to doing that this cycle, but time has not been kind.16:47
evrardjpthat is interesting. But just to make sure we are in sync, we'll not change the stable/pike code to make the code work under ansible 2.3 and ansible 2.416:47
evrardjpbecause that was also an option16:47
evrardjp(not the handlers part, but at least adapting the includes)16:47
odyssey4meI'd rather avoid changing the previous branch to cater for the current dev head.16:47
odyssey4meThe only reason to port stuff back is to make it easier to keep the test implementations more maintainable.16:48
evrardjpIt makes sense to me.16:48
odyssey4meBut that would be the test implementations only, not the main body of role code.16:48
evrardjpyeah here it would change the body of the code to change the include from include: includefile.yml to include: "{{ roledir }}/includefile.yml"16:49
evrardjpI saw there is another config thing that could alter that loading, so i will double check if that's not something we could do16:50
evrardjpok let's mark this as confirmed and critical because it blocks gates, but we'll discuss implementation details later16:51
odyssey4mesure16:52
evrardjpnext16:52
evrardjp#link https://bugs.launchpad.net/openstack-ansible/+bug/174146216:52
openstackLaunchpad bug 1741462 in openstack-ansible "P-Q upgrade fails due to change in inventory" [Undecided,New]16:52
*** chyka has joined #openstack-ansible16:52
evrardjpanother one I'd consider critical16:52
odyssey4meconfirmed, crit16:52
evrardjpnot possible to upgrade right now16:52
evrardjp#link https://bugs.launchpad.net/openstack-ansible/+bug/174124716:53
openstackLaunchpad bug 1741247 in openstack-ansible "Upgrade from Ocata fails with timeout" [Undecided,New]16:53
odyssey4meit's breaking upgrades, and we're nearing the end of the cycle16:53
odyssey4meour timeout is already too long - infra doesn't like longer than 3 hrs and we have 4 IIRC16:53
evrardjpthat's bad news.16:54
odyssey4methat said, it's old code - not much we can do16:54
evrardjpany idea of what we can do for that then?16:54
evrardjpManual testing and removing the periodics?16:54
evrardjpthat doesn't sound better.16:54
odyssey4meonly option might be to use 100% serial values for the initial deploy to try and cut time - or to cut the number of containers down like we have for master16:54
evrardjpmaster has seen lots of performance improvements16:55
evrardjpmaybe the 100% serial would be a good temp fix16:55
evrardjplet's mark this as confirmed and critical too?16:55
odyssey4meyup16:55
*** smatzek has quit IRC16:56
evrardjpnext16:56
evrardjp#link https://bugs.launchpad.net/openstack-ansible/+bug/174123516:56
openstackLaunchpad bug 1741235 in openstack-ansible "Shallow cloning doesn't work during repo-build" [Undecided,New]16:56
evrardjpI'd say this is a whishlist16:56
odyssey4meyes16:57
*** smatzek has joined #openstack-ansible16:57
evrardjpwe can consider this as opinion too16:57
odyssey4meit doesn't matter too much - and is part of the longer term plan for the python deploy bits anyway16:57
evrardjpopinion -> "doesn't fit the project plan"16:58
evrardjpok let's mark it as wishlist then16:58
evrardjplast for today16:58
evrardjp#link https://bugs.launchpad.net/openstack-ansible/+bug/174122516:58
openstackLaunchpad bug 1741225 in openstack-ansible "Check for NOPASSWD in sudo configuration can't be disabled" [Undecided,New]16:58
odyssey4mereality is that infra is planning to publish all services to pypi some time in the future so we won't *have* to use SHA's - we'll be able to just use pypi with appropriate pins16:58
*** smatzek_ has joined #openstack-ansible16:59
evrardjpodyssey4me: that is good when we think about it.16:59
evrardjpfor last bug, mhayden are you there?16:59
odyssey4melooks like mhayden has confirmed16:59
odyssey4memaybe low/med16:59
*** smatzek_ has quit IRC17:00
evrardjpok let's mark this as confirmed and med17:00
evrardjpthanks everyone!17:00
*** smatzek_ has joined #openstack-ansible17:00
*** ThomasSch_ has quit IRC17:00
evrardjpnext week's gonna be though too :(17:00
evrardjpwe have many big ones remaining in the list17:00
evrardjpanyway, thanks for your time all!17:00
evrardjp#endmeeting17:00
*** openstack changes topic to "Launchpad: https://launchpad.net/openstack-ansible || Weekly Meetings: https://wiki.openstack.org/wiki/Meetings/openstack-ansible || Review Dashboard: https://goo.gl/tTmdgs"17:00
openstackMeeting ended Tue Jan  9 17:00:41 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2018/openstack_ansible_meeting.2018-01-09-15.59.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2018/openstack_ansible_meeting.2018-01-09-15.59.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2018/openstack_ansible_meeting.2018-01-09-15.59.log.html17:00
odyssey4methx evrardjp17:00
*** smatzek has quit IRC17:02
hwoarangthank you17:03
cloudnull++ thanks evrardjp17:04
ashaki'm still having issues on centos, where during running os-cinder-install.yml, the task 'galera_client : Install galera distro packages' wants to install packages on one of my infra nodes and is failing with messages like: file /etc/my.cnf from install of MariaDB-common-10.1.30-1.el7.centos.x86_64 conflicts with file from package mariadb-config-3:10.1.20-2.el7.x86_6417:05
*** sar has joined #openstack-ansible17:07
RandomTechhey a have two questions17:09
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/openstack-ansible master: Fix sources-branch-updater and add docs  https://review.openstack.org/52937717:10
hwoarangashak: would it be possible to file a bug so we can track it?17:10
hwoarangsounds like a simple solution would be to remove mariadb-config before installing packages but it's easier to track it in a bug17:11
spotzodyssey4me: I'm gonna grammar police your rst for that patch if that's ok. I'll put a -1 on it so folks know I'll be doing it as I might not get to it until later17:12
ashakhwoarang: sure. where does one file bugs?17:12
hwoarangashak: https://bugs.launchpad.net/openstack-ansible17:13
ashakoh yeah, silly me :)17:13
*** chhavi__ has quit IRC17:14
*** smatzek_ has quit IRC17:15
*** smatzek has joined #openstack-ansible17:15
*** epalper has quit IRC17:15
odyssey4mespotz go ahead - I won't be doing any more mods until tomorrow, so feel free to fix up my terrible grammar through your day17:19
spotzodyssey4me: Aww it's not so bad just some nits:)17:20
*** smatzek has quit IRC17:21
*** smatzek has joined #openstack-ansible17:29
*** smatzek has quit IRC17:30
*** smatzek has joined #openstack-ansible17:30
*** smatzek has quit IRC17:31
*** smatzek has joined #openstack-ansible17:32
*** nshetty has quit IRC17:35
*** smatzek has quit IRC17:36
*** smatzek has joined #openstack-ansible17:37
*** smatzek has quit IRC17:39
*** smatzek has joined #openstack-ansible17:40
RandomTechhey i noticed something about the documentation that may need updated17:42
*** smatzek has quit IRC17:44
*** mbuil has quit IRC17:45
*** smatzek has joined #openstack-ansible17:46
*** markvoelker has quit IRC17:47
*** sxc731 has quit IRC17:48
*** gkadam has quit IRC17:49
*** smatzek has quit IRC17:50
*** smatzek has joined #openstack-ansible17:51
*** smatzek has quit IRC17:56
*** eumel8 has quit IRC17:58
*** smatzek has joined #openstack-ansible17:58
*** smatzek has quit IRC18:03
*** smatzek has joined #openstack-ansible18:03
RandomTechandymccr: are you avaible for a minute?18:04
*** rmcall has joined #openstack-ansible18:05
*** hamza21 has joined #openstack-ansible18:10
*** hamza21 has quit IRC18:17
*** MikeW has quit IRC18:22
*** esberglu has quit IRC18:31
*** esberglu has joined #openstack-ansible18:31
*** lihi has quit IRC18:47
*** oanson has quit IRC18:48
*** gkadam has joined #openstack-ansible18:57
*** poopcat has joined #openstack-ansible19:09
*** markvoelker has joined #openstack-ansible19:13
*** markvoelker has quit IRC19:13
*** poopcat1 has joined #openstack-ansible19:14
RandomTechhey cloudnull got a sec?19:16
*** poopcat has quit IRC19:16
cloudnullsure19:17
cloudnullwhats up ?19:17
RandomTechis it okay if setup-hosts fails on get modern pip but sucsedes on Get Modern PIP using fallback URL19:19
RandomTechi noticed our playbook did that19:21
*** markvoelker has joined #openstack-ansible19:23
RandomTechthe rest of the playbook seems to have ran fine however19:23
*** madorn has quit IRC19:25
*** madorn has joined #openstack-ansible19:27
*** stuartgr has quit IRC19:28
*** gkadam has quit IRC19:32
*** savvas`_ has joined #openstack-ansible19:34
*** savvas` has quit IRC19:35
*** savvas`_ has quit IRC19:35
*** savvas` has joined #openstack-ansible19:35
*** savvas` has quit IRC19:37
RandomTechany idea cloudnull ?19:42
*** markvoelker has quit IRC19:42
*** markvoelker has joined #openstack-ansible19:43
*** woodard has quit IRC19:43
*** markvoelker has quit IRC19:48
*** woodard has joined #openstack-ansible19:49
cloudnullRandomTech: sorry. walked away a min20:01
cloudnullback now20:01
cloudnullyes that should be fine20:01
cloudnullif it succeeds using the fall back url everything should be ok20:01
cloudnullRandomTech: https://review.openstack.org/#/c/530959/20:02
RandomTechSounds good, going to run the second playbook now20:02
cloudnullI implemented that change, which I think would be good to backport.20:02
RandomTechi do have 1 comment on the documentation however20:02
cloudnullthat PR will tell you if there was an actual failure20:03
cloudnullwhat's up with the docs?20:03
cloudnullif any cores are around that could give pr 530959 a push it'd be appreciated.20:03
RandomTechthe documentation is marked 16.0.6 however it has you clone version 16.0.5 here: https://docs.openstack.org/project-deploy-guide/openstack-ansible/pike/deploymenthost.html20:04
RandomTechin the install source and dependencies task20:05
RandomTechbetter link: https://docs.openstack.org/project-deploy-guide/openstack-ansible/pike/deploymenthost.html#install-the-source-and-dependencies20:05
cloudnullah.20:09
cloudnullsorry was looking at this a bit cross eyed.20:09
cloudnullI think the online documentation only ever points to the current stable branch20:10
cloudnullwhen the tag is cut for 16.0.6 that tag version will be updated.20:10
* cloudnull if i'm not mistaken20:11
*** armaan has quit IRC20:22
*** armaan has joined #openstack-ansible20:23
*** Smeared_Beard has quit IRC20:27
RandomTechlogan-: you availible for a moment?20:31
logan-yep, what's up20:31
RandomTechwere getting this error when running setup-infrastructure: please provide devices to your osd scenario20:33
*** markvoelker has joined #openstack-ansible20:33
RandomTechits under: ceph-osd : verify devices have been provided20:33
RandomTechcant tell where we provide them in the configs however20:33
*** SmearedBeard has joined #openstack-ansible20:33
logan-if all of the osd systems are using the same disk layout you could drop it in user_variables20:34
logan-let me find the ceph-ansible docs on how to define that20:34
logan-https://github.com/ceph/ceph-ansible/blob/master/group_vars/osds.yml.sample20:35
logan-best to read thru this whole file20:35
logan-any of the variables in there that you'd like to set can be done in OSA's user_variables.yml20:36
RandomTechthats what ive been doing20:37
RandomTechnot seeing where that would be, may see is ceph ansible is active20:37
RandomTechthers only 1 guy there i must have the wrong one20:38
logan-are you confused on where to set the variables? which variables you need to set? or what to put in them?20:39
*** sar has quit IRC20:39
RandomTechwhat to set20:40
RandomTechhow to define what osd to use20:40
logan-https://github.com/ceph/ceph-ansible/blob/97f520bc7488b8e09d4057783049c8975fbc336e/group_vars/osds.yml.sample#L72-L81 example there20:41
logan-if you are splitting the journal from the data disk, you'll also need to define dedicated_devices: https://github.com/ceph/ceph-ansible/blob/97f520bc7488b8e09d4057783049c8975fbc336e/group_vars/osds.yml.sample#L137-L15520:42
*** armaan has quit IRC20:44
RandomTechdo you know if splitting data and journal is needed?20:47
logan-it is not needed if you choose the collocated scenario20:48
*** SmearedBeard has quit IRC20:52
RandomTechwould i put this under cinder backends?20:52
openstackgerritDavid Moreau Simard proposed openstack/openstack-ansible master: DNM: Get ara database  https://review.openstack.org/53230920:57
*** SmearedBeard has joined #openstack-ansible20:58
openstackgerritKevin Carter (cloudnull) proposed openstack/openstack-ansible master: Add scaffolding for multiple container techs  https://review.openstack.org/52774921:02
RandomTechanyone have an example of a osa ceph deploy where they defined devices21:02
logan-RandomTech: no, it'll need to be available under the OSD hosts.. so either place it in container_vars like you would cinder_backends, except under your osd hosts21:03
logan-or define these vars in user_variables.yml where they'll be available on all of the hosts21:03
RandomTechya im trying to figure out exactly where to define them in user_variable.yml and what format21:04
RandomTechalso sorry logan- im fairly new to this21:05
*** markvoelker has quit IRC21:13
*** markvoelker has joined #openstack-ansible21:13
*** markvoelker has quit IRC21:17
*** RandomTech has quit IRC21:19
*** strgout has joined #openstack-ansible21:19
*** smatzek has quit IRC21:24
*** smatzek has joined #openstack-ansible21:24
*** smatzek has quit IRC21:24
*** smatzek has joined #openstack-ansible21:24
*** smatzek has quit IRC21:24
*** smatzek has joined #openstack-ansible21:25
*** smatzek has quit IRC21:30
*** pcaruana has quit IRC21:38
*** dave-mccowan has quit IRC21:40
*** threestrands has joined #openstack-ansible21:44
*** threestrands has quit IRC21:44
*** threestrands has joined #openstack-ansible21:44
*** rmcall has quit IRC21:52
openstackgerritAmy Marrich (spotz) proposed openstack/openstack-ansible master: Fix sources-branch-updater and add docs  https://review.openstack.org/52937721:56
*** markvoelker has joined #openstack-ansible22:29
*** markvoelker has quit IRC22:30
*** zerick_ has quit IRC22:33
*** zerick has joined #openstack-ansible22:34
*** afred312 has quit IRC22:36
*** zerick has quit IRC22:49
*** afred312 has joined #openstack-ansible23:06
*** chhavi__ has joined #openstack-ansible23:11
*** markvoelker has joined #openstack-ansible23:11
*** markvoelker has quit IRC23:11
*** afred312 has quit IRC23:11
*** chhavi__ has quit IRC23:15
*** afred312 has joined #openstack-ansible23:20
*** pmannidi has joined #openstack-ansible23:24
*** markvoelker has joined #openstack-ansible23:43
*** markvoelker has quit IRC23:43
*** ianw has quit IRC23:50
*** ianw has joined #openstack-ansible23:51

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