Tuesday, 2015-08-04

*** yaya has quit IRC00:08
*** darrenc_afk is now known as darrenc00:11
*** jaypipes has quit IRC00:18
*** alop has quit IRC00:55
*** tlian has quit IRC01:06
*** sdake_ has quit IRC01:15
*** sdake has joined #openstack-ansible01:16
*** pellaeon has quit IRC01:35
*** pellaeon has joined #openstack-ansible01:35
*** JRobinson__ has joined #openstack-ansible01:36
*** galstrom_zzz is now known as galstrom01:42
openstackgerritDavid Stanek proposed stackforge/os-ansible-deployment: Uses tox for automating documentation builds  https://review.openstack.org/20757701:52
*** galstrom is now known as galstrom_zzz02:35
*** sdake has quit IRC02:48
*** sdake has joined #openstack-ansible03:16
*** sdake_ has joined #openstack-ansible03:38
*** sdake has quit IRC03:41
*** JRobinson__ is now known as JRobinson__afk03:51
*** galstrom_zzz is now known as galstrom04:11
*** daneyon has quit IRC04:17
*** daneyon has joined #openstack-ansible04:17
*** galstrom is now known as galstrom_zzz04:52
*** JRobinson__afk is now known as JRobinson__05:06
*** fawadkhaliq has joined #openstack-ansible05:14
*** fawadk has joined #openstack-ansible05:15
*** fawadkhaliq has quit IRC05:18
openstackgerritSteve Lewis proposed stackforge/os-ansible-deployment:  Updated master to the latest SHAs - 03.Aug.2015  https://review.openstack.org/20880105:22
*** javeriak has joined #openstack-ansible06:04
*** JRobinson__ has quit IRC06:07
openstackgerritSteve Lewis proposed stackforge/os-ansible-deployment: Add support for swift proxy config: sorting_method  https://review.openstack.org/20881706:16
*** daneyon has quit IRC06:30
*** javeriak has quit IRC06:38
*** javeriak has joined #openstack-ansible06:38
svgGood morning all o/06:53
stevelleo/07:02
*** gparaskevas has joined #openstack-ansible07:07
*** fawadkhaliq has joined #openstack-ansible07:12
*** javeriak_ has joined #openstack-ansible07:14
*** javeriak has quit IRC07:14
*** fawadk has quit IRC07:14
*** fawadk has joined #openstack-ansible07:15
*** javeriak has joined #openstack-ansible07:17
*** fawadkhaliq has quit IRC07:18
*** javeriak_ has quit IRC07:20
*** javeriak has quit IRC07:24
*** javeriak has joined #openstack-ansible07:24
*** javeriak_ has joined #openstack-ansible07:27
*** javeriak has quit IRC07:28
odyssey4meo/ svg07:35
odyssey4mestevelle you still awake?07:35
*** fawadk has quit IRC07:45
svgto make a temporary test kilo versionm right now, with the ceph patch in, should I use kilo HEAD or 11.0.4? I'm inclined to take head, unless someone has better advice?07:52
*** fawadkhaliq has joined #openstack-ansible07:57
matttsvg: assuming you're using this for testing i'd go head, it may not apply cleanly to 11.0.407:58
svgthx07:59
matttyou're welcome, and good morning to you!07:59
svgsame, same07:59
* svg has a hard time waking up todat07:59
evrardjphello08:01
evrardjpsvg, I'm going to do the same this afternoon08:02
evrardjpquick question: for kilo branch we are following upstream kilo stable branch right?08:03
evrardjpso there should be a merge soon with the new kilo release, right?08:03
*** fawadkhaliq has quit IRC08:06
odyssey4meevrardjp yes, and yes - once we tag 11.1.0 there'll be a follow-on merge to update the sha's from stable/kilo08:10
odyssey4mewe'll then continue to tag a hotfix version every two weeks, after which we update the sha's every time08:11
matttshas were last bumped 23/07, so quite recent08:12
odyssey4mebgmccollum blast, that explains the behaviour cc gparaskevas08:20
*** javeriak_ has quit IRC08:25
*** javeriak has joined #openstack-ansible08:26
*** javeriak has quit IRC08:26
*** javeriak has joined #openstack-ansible08:34
*** jwitko has quit IRC08:35
*** jwitko has joined #openstack-ansible08:37
*** javeriak_ has joined #openstack-ansible08:38
*** javeriak has quit IRC08:38
gparaskevasodyssey4me: Hey goodmmorning08:43
gparaskevasodyssey4me: what happend?08:43
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Updated master for new dev work - 27.07.2015  https://review.openstack.org/19912608:54
odyssey4megparaskevas bgmccollum provided f3eedback that using git review with HTTP passwords requires git-review 1.25 or newer09:03
gparaskevasodyssey4me: ok but what about using ssh?09:03
odyssey4megparaskevas using ssh is built-in, but you need to find a way to get through your firewall on the required port09:03
odyssey4meuse an ssh tunnel or something09:03
*** javeriak has joined #openstack-ansible09:19
gparaskevasodyssey4me: i Have a quick question regarding python beaver09:19
odyssey4megparaskevas best is usually to ask, not ask to ask :)09:20
gparaskevasodyssey4me: i have tried to evaluate rpc-openstack but unfortunalty all many pip installs cannot be completed inclding pthon-beaver it self09:20
gparaskevasodyssey4me: i can see that pip is redirected to local repository which does not have all the packages.09:21
*** javeriak_ has quit IRC09:22
gparaskevasodyssey4me: why is that happening and how cna i overcome?09:22
*** javeriak has quit IRC09:29
*** javeriak has joined #openstack-ansible09:29
odyssey4megparaskevas note that the version of rpc you're trying to evaluate has not yet released any documentation to describe how to install it yet - that's because RPC11 is not yet released09:31
*** fawadkhaliq has joined #openstack-ansible09:31
gparaskevasodyssey4me: i am using this: https://github.com/rcbops/rpc-openstack/tree/kilo BTW anyway I have created my own playbooks for ELK and Nagios that extend OSAD but i was using syslog and not beaver. Now i want use beaver and i cannot install it because of pip configuration09:33
gparaskevasodyssey4me: is there a way to overcome this?09:33
odyssey4megparaskevas you have to rebuild the repo, but set the base that it searches from to be a base that includes both the rpc and osad playbooks09:34
gparaskevasodyssey4me: ok how can i do that i am not very famailiar with pip :/09:34
odyssey4meyou'll notice that rpc-openstack has this play to build the repo for the rpc packages: https://github.com/rcbops/rpc-openstack/blob/master/rpcd/playbooks/repo-build.yml09:34
gparaskevasyes09:35
odyssey4meyou just need to cd to the rpc-openstack playbooks directory, then execute: openstack-ansible repo-build.yml09:35
odyssey4meonce you've done that, then execute the beaver.yml playbook09:36
gparaskevasok i have seen that le me try. thanks again!09:36
odyssey4meoh, sorry - after the repo-build you need to add the rpc package repo to the hosts and containers, so you have to execute the repo-pip-setup.yml playbook09:36
odyssey4me(it's been a while since I worked on it - sorry about the mixup)09:37
gparaskevasok so both?09:37
odyssey4merepo-build, then repo-pip-setup, then beaver09:37
gparaskevasok is there any interest in nagios for OSAD? I can see that you try to keep it clean and OS specific but since i like to contribute i cannot force my self not to ask09:38
matttgparaskevas: sec, i saw a blog post on this09:43
gparaskevasmattt: this one? https://developer.rackspace.com/blog/openstack-osad-and-nagios-against-the-world/09:44
matttyep :)09:44
gparaskevasmattt: :P09:44
mattti love nagios, so i'm all for this09:44
matttbut not had time to try it tbh :(09:44
gparaskevasmattt: haha i have seen it but i have not tried it i have created my own. i can share if you like09:44
*** javeriak has quit IRC09:45
matttgparaskevas: yeah would love to see what yoiu have09:48
gparaskevasmattt: ok09:48
odyssey4megparaskevas so the starting point would be to submit a spec to the project, proposing how you would integrate it and how it would affect the playbooks, roles, etc09:49
gparaskevasodyssey4me: ok let me see how to submit a spec09:49
mattti'm not sure nagios config shoudl live in os-a-d personally09:52
mattti thought you had a separate git repo :)09:53
*** openstackgerrit_ has joined #openstack-ansible09:53
*** javeriak has joined #openstack-ansible09:54
mattt^^^ gparaskevas09:54
gparaskevasi have a separate repository like rpc-openstack09:54
gparaskevasso i guess there is no problem09:55
matttgparaskevas: it'd be interesting to hear what the community thinks, if they want a reference monitoring implementation inside osad then why not09:55
matttbut my gut feeling would be that most people would want it kept separate09:55
gparaskevasmattt: yes this is what i feel also. i any case they can be stored and maintained seperatly but they can see eachother in every installation :P09:56
matttcool that sounds ideal to me :)09:57
evrardjpmattt: FYI, I don't want monitoring in my OSAD, but I don't mind having some monitoring practices in the doc...10:18
evrardjpmonitoring is really a specific job, done differently in each enterprise10:19
git-harryYeah, this project needs to be careful of feature creep10:20
matttnagios does seem to be a popular choice tho, it would be good to have an external repo that plugs everything together as far as nagios is concerned that the community can hack on10:22
evrardjpusing scripts for checking health is a kinda standard way of doing it10:24
evrardjpso I agree, nagios in an external repo would be a good idea...10:25
evrardjpZabbix is also quite popular10:25
matttcan zabbix use nagios lugins?10:26
mattt*plugins10:26
evrardjpnot really, but nagios can start commands and return response codes for giving status... Zabbix can do the same10:32
evrardjpso one script for status checking can be used for both10:32
*** fawadk has joined #openstack-ansible10:35
odyssey4memattt yes, through a wrapper10:36
odyssey4mebut yeah, as we grow I think the strategy of being more modular is going to become more important over time10:37
*** fawadkhaliq has quit IRC10:37
odyssey4meso it's going to be more and more important to have the roles be independant (able to run on their own to achieve the goal of installing/configuring the service), and the playbooks be more opinionated10:38
*** fawadkhaliq has joined #openstack-ansible10:38
odyssey4megparaskevas a few principles would be useful to bear in mind when preparing your blueprint10:39
odyssey4me1 - don't expect the role to be imported into the os-ansible-deployment repository... expect instead to make use of the facility in bootstrap-ansible to import any external roles you need and perhaps only expect to include some playbooks in-repo, or perhaps some docs describing how to make use of the external roles.10:40
odyssey4meheh, I shoved it all in one principle :p10:40
gparaskevasodyssey4me: yes ofcource. If the playbooks doesnt need to be merged with OSAD which is clear that is shouldnt then blueprint isnt still nessesery. I will submit my repository which works on a modular type like rpc-openstack if i may10:41
*** fawadk has quit IRC10:43
odyssey4megparaskevas sure - what you may consider doing is adding some docs to osad to reference what you've done so that others can learn from it10:46
stevelleodyssey4me: awake for a bit, whats news?11:02
evrardjpstevelle: how many hours do you sleep a day/a week? It's like I've seen you a few hours before...11:03
stevelleevrardjp: I feel like not as many as I would like :)11:04
stevellealso realizing it's lunch hour in western europe right now so might not get an answer11:06
odyssey4mestevelle I'm working a two-pronged attack for the sha updates11:10
odyssey4meone test is working to get updated to at least liberty-2, the other to the latest sha's11:10
*** javeriak has quit IRC11:11
stevelleI did latest shas last night and had two successful runs before I submitted a patch... which has failed twice now11:11
odyssey4methe issue on the latest sha's appears to be in keystone one of the oslo_messaging imports fails11:11
stevelleI know at least one of my successful runs had a different sha for heat, but I thought keystone was the same.11:12
odyssey4mestevelle http://paste.openstack.org/show/u3mIrPjsUWANe8ZJ0ksy/11:12
odyssey4mestevelle also note that in the previous sha update attempt on master, cloudnull_afk had some extra bits: https://review.openstack.org/#/c/199126/11:13
stevellewell I am no longer even remotely hopeful for my patch11:15
odyssey4mestevelle no worries, we'll work through it :) you should try to get some more rest11:16
stevelleodyssey4me: I look forward to checking back in a few hours to see where things are11:19
*** openstackgerrit has quit IRC11:31
*** openstackgerrit_ is now known as openstackgerrit11:31
*** openstackgerrit has quit IRC11:32
*** openstackgerrit_ has joined #openstack-ansible11:32
*** openstackgerrit_ is now known as openstackgerrit11:32
*** openstackgerrit_ has joined #openstack-ansible11:33
*** sdake_ has quit IRC11:47
*** fawadkhaliq has quit IRC11:48
*** jaypipes has joined #openstack-ansible11:59
*** woodard has joined #openstack-ansible12:05
*** openstackgerrit has quit IRC12:16
*** openstackgerrit has joined #openstack-ansible12:17
*** fawadkhaliq has joined #openstack-ansible12:23
*** bapalm_ has joined #openstack-ansible12:34
*** sdake has joined #openstack-ansible12:36
*** pilgrimstack has joined #openstack-ansible12:41
*** pilgrimstack1 has quit IRC12:42
mattthow do you rebootstrap your galera cluster again?12:54
*** tlian has joined #openstack-ansible12:54
matttn/m says in the error :P12:54
git-harryyou're welcome12:55
matttgit-harry: this is why they pay you the big bucks12:55
gparaskevasi ould love to here that :P12:55
gparaskevaswould*12:55
gparaskevasi am having issues my self with galera12:56
gparaskevasi usualy do that: mysqld --tc-heuristic-recover=ROLLBACK if nodes cannot come up...12:56
*** jaypipes has quit IRC12:57
matttgparaskevas: openstack-ansible -e galera_ignore_cluster_state=true galera-install.yml12:58
matttcannot confirm or deny that it's working tho :)12:58
*** jaypipes has joined #openstack-ansible13:00
*** gparaskevas has quit IRC13:01
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Improve Keystone Apache configuration  https://review.openstack.org/20904713:02
odyssey4mestevelle so https://review.openstack.org/209047 fixes the keystone import errors, now to move onto the next issue :)13:02
evrardjpI'd like to have multiple backend drivers for my storage (NetApp, LVM and I'd like to test the ceph integration)... Is it possible to have multiple backends under cinder_backends, or should I create a cinder_backend per container, and multiply the number of containers on the same host?13:12
*** TheIntern has joined #openstack-ansible13:14
odyssey4meevrardjp it's already built-in: http://osad.readthedocs.org/en/latest/install-guide/configure-cinder.html13:18
evrardjpit's not what I meant13:19
evrardjpbut I'll use this page to be understable13:20
evrardjpOn the point 9) on that documentation13:20
evrardjpthere is netapp: and then the netapp directives13:20
evrardjpis it possible to put, on the same level as netapp, lvm: ?13:21
evrardjpat the same time13:21
*** KLevenstein has joined #openstack-ansible13:21
*** KLevenstein is now known as KLev-away13:21
evrardjpI think everything will be confused, right?13:21
matttevrardjp: you can use both13:22
matttevrardjp: i've just done that on an API so i can use lvm and ceph13:22
evrardjpin the same container?13:22
evrardjpso they are gonna be in the same avaiability zone I guess13:22
evrardjpI'll try and see how it's gonna play out13:23
mattti had a single cinder-volume running on the aio instance itself13:23
mattti'm not sure from a cinder perspective what is ideal but the playbooks seem to support this at least13:24
odyssey4meevrardjp exactly :)13:24
odyssey4meevrardjp I'm not sure about the AZ, I'd have to dig into the template/playbook to verify that13:24
evrardjpodyssey4me: the exactly is for "let's try and see" I guess, not the availability zone?13:25
evrardjpright.13:25
evrardjp:D13:25
evrardjpI'll look later don't worry about that13:25
odyssey4meevrardjp exactly is for the nfs being at the same level as netapp13:26
evrardjpso it's definitely possible to have multiple backends on the same container...13:27
evrardjpthanks for the info13:27
odyssey4meevrardjp yup13:27
odyssey4meevrardjp lvm is the only special case which requires the volume service to be on the same server as the storage13:28
odyssey4meall other cinder backends can share a volume service (and therefore the same volume service container)13:29
evrardjpthat makes sense odyssey4me13:29
Sam-I-Amwhats with reviews taking so long?13:35
Sam-I-Amhttps://review.openstack.org/#/c/204597/13:35
Sam-I-Amstill waiting13:35
matttSam-I-Am: a good # of cores are out at the moment13:38
*** Mudpuppy has joined #openstack-ansible13:39
Sam-I-Ammattt: this is a problem13:39
matttSam-I-Am: why?13:40
*** Mudpuppy has quit IRC13:40
Sam-I-Ambecause we cant get stuff done?13:40
matttsure we can13:40
mattturgent stuff will go through as normal13:40
*** Mudpuppy has joined #openstack-ansible13:41
matttSam-I-Am: is that review blocking anything at the minute?13:41
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Re-order setup-openstack play to match the gate check order  https://review.openstack.org/20907113:44
Sam-I-Amits not blocking anything13:44
Sam-I-Amthings just tend to get stale though13:44
odyssey4meSam-I-Am it's a pretty big change into something most of the team are not good at (neutron), and most of the cores are away13:45
odyssey4meif you could get some hardware tests done by the guys who know neutron well then there'd be more confidence in core votes13:45
odyssey4mealso note that the bug is only targeted for 11.1.1, so there's no rush - the attention is elsewhere at the moment13:45
Sam-I-Amodyssey4me: how does one go about getting hardware tests done? the multi-node gate has been hosed for a while.13:46
odyssey4meSam-I-Am have a chat to Apsu and rackertom to see if they can spend some cycles on it - also d34dh0r53 regularly works in the hardware labs13:47
*** javeriak has joined #openstack-ansible13:47
odyssey4meI'm not sure if svg or evrardjp have some sort of test infrastructure and are willing to test it out too. I like the patch as it cleans things up - I just have no idea whether it causes any issues.13:48
evrardjpwhat should I test?13:48
Sam-I-Amevrardjp: https://review.openstack.org/#/c/204597/13:49
Sam-I-AmApsu rackertom d34dh0r53 y'all around?13:49
evrardjpI have a test infrastructure, but the resource missing is not hardware, it's time ;)13:49
odyssey4meevrardjp yep, we all suffer from the lack of that resource :)13:50
evrardjpI know :)13:50
Sam-I-Amsleep is optional13:50
Sam-I-Amyou can donate the hardware to me :)13:50
evrardjpI'll cherry pick into kilo Sam-I-Am and restart my playbooks soon13:50
odyssey4methanks evrardjp :)13:51
evrardjpput the words in a different order and you get what I meant :p13:51
evrardjpjust finishing multiple backends testing first13:51
rackertomSam-I-Am: m'yes13:53
Sam-I-Amevrardjp: thx13:56
Sam-I-Amrackertom: whatchoo think of the neutron patch?13:56
*** sigmavirus24_awa is now known as sigmavirus2414:00
rackertomSam-I-Am: I thought I +1 it already. Saw a new patch was added, so re-+1.14:00
Sam-I-Amrackertom: aight thanks. thats sort of the fun of rebasing :/14:01
rackertomI really liked the grouping, and obviously conditionally including options that only need to be on a server is good stuff.14:02
rackertomMakes the rendered templates look more like what someone would expect if following the docs.14:03
odyssey4merackertom the concern I have is whether we're introducing any regressions with it, or perhaps new bugs... so ideally I'd like to see someone provide feedback of more thorough testing14:04
Sam-I-Amits neutron, there's always new bugs :)14:05
Sam-I-Ami've tested the neutron bits on my own multi-node labs14:05
Sam-I-Amjust not embededed in ansible14:05
Sam-I-Amhowever, the configs look the same14:05
rackertomodyssey4me: I absolutely agree. Though, again, client nodes should just be ignoring server only options, and moving options within a file wouldn't matter either, I totally think having a good lab setup for this would be a great help.14:06
rackertomEvery bit of my attempts at lab work has ended in smouldering piles of rubble, so maybe when I get this sha thing sorted, I could try to find hosts to test this on.14:08
*** TheIntern has quit IRC14:08
evrardjpodyssey4me: I'm sorry but at the end I won't test the multiple backends directly... I want to test multiple availability zones so... one container per AZ it is...14:10
*** spotz_zzz is now known as spotz14:11
*** javeriak has quit IRC14:12
Sam-I-Amrackertom: whats up with your lab?14:12
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Updated master to the latest SHAs - 03.Aug.2015  https://review.openstack.org/20880114:13
ApsuMorning.14:18
Sam-I-Ammoo14:18
Apsuodyssey4me: Sam-I-Am: Sup?14:18
rackertomSam-I-Am: my physical labs never fully work.14:19
*** phalmos has joined #openstack-ansible14:20
Sam-I-AmApsu: looks for love on https://review.openstack.org/#/c/204597/14:20
Sam-I-Amer, looking14:20
Sam-I-Amideally, somewhere to multi-node test it14:20
ApsuSam-I-Am: Ok, so why haven't you run it through our jenkins lab?14:21
Sam-I-AmApsu: no acces14:22
Sam-I-Amremember, i'm in docs :)14:22
ApsuI remember that's what you tell everyone14:22
* Apsu stares at review you Just linked14:23
*** TheIntern has joined #openstack-ansible14:24
ApsuSam-I-Am: Also, I thought those jenkins multi-node jobs were nightly and such14:25
Sam-I-Ami dont know what happened to the 'wherenow' ci bits14:25
ApsuHas the beautiful Jenkins I built been asploded?!14:25
Sam-I-Ami think you were part of that business14:25
Sam-I-Ami havent seen a wherenow appendage on reviews in a while14:25
Sam-I-Ammaybe the hardware flooded or caught fire?14:25
ApsuBoth/and.14:26
palendaeApsu: You'd have to ask hughsaunders, but I'm pretty sure the multi-node jobs were removed from per-commit checking14:26
palendaeBecause they weren't voting and were failing a lot14:26
Apsulol14:26
ApsuSuper useful, then. k14:26
palendaeYep14:27
odyssey4meApsu the multi-node labs are dead at this time, and have been for a few months14:27
odyssey4mehughsaunders did a rage quit on jenkins :p14:27
odyssey4mewell, actually at stupid hardware issues14:28
matttdammit hughsaunders14:28
ApsuThat's a paddlin'14:29
Sam-I-AmApsu: sounds like you should fix it :)14:29
*** phalmos has quit IRC14:30
Sam-I-Amhow did this become invalid?14:31
Sam-I-Amhttps://bugs.launchpad.net/openstack-ansible/+bug/147543614:31
openstackLaunchpad bug 1475436 in openstack-ansible juno "VLAN range issue in ml2_conf.ini" [Wishlist,Triaged]14:31
Sam-I-Amseems like it needs more discussion14:31
Sam-I-Amparticularly along the lines of 'is this workaround hackish, or do we need to document this?'14:31
*** TheIntern has quit IRC14:32
ApsuSam-I-Am: It's invalid for Kilo+ because the mechanism for parsing the OSAD config and generating ml2_conf.ini has changed, and the bug doesn't apply there anymore.14:35
ApsuIt's still valid for Juno, and there's a workaround that should probably be documented.14:36
*** TheIntern has joined #openstack-ansible14:37
Sam-I-AmApsu: so is what approd0 says... the way?14:40
*** phalmos has joined #openstack-ansible14:40
ApsuIt should work, because the Juno template doesn't loop over the ranges variable to split it by commas14:40
ApsuMeaning we're basically doing an injection vulnerability on our config14:41
Sam-I-Amthats why i thought it seemed hackish14:41
ApsuSo pretty much whatever's in there will get added as-is, so if you make sure it has the right name for each range pair, you can add as many as you want14:41
evrardjpsvg mattt you there? I'd like to configure ceph, cherry-picked from master into kilo... for the user_secrets I've added cinder_ceph_client uuid... should I put the token I receive after client creation with the == ?14:47
evrardjpand for the user should I put "client." before my client name, like it's shown in ceph auth list?14:47
Sam-I-AmApsu: i sort of think we should make this a little more... bettah14:49
svgevrardjp: the uuid will be generated randomly just like other secrets14:49
Sam-I-Amrather than documenting a hack that happens to work14:49
Sam-I-Amalso, injection14:49
Sam-I-Amalthough i guess we dont validate a bunch of values for things14:49
ApsuSam-I-Am: Me too. But I was told "this won't be getting backported as a fix". Or something similar that sounded like "no".14:50
ApsuThe fix is pretty easy.14:50
svgand just give a user name, no client. prefix14:50
ApsuJust add a loop in the template14:50
Sam-I-Ammaybe not backported, but for master14:50
evrardjpsvg: I am not using the token generation14:50
Sam-I-Amwho closed this bug?14:50
ApsuSam-I-Am: Master/Kilo aren't affected, that's what I was saying14:50
svgAlso evrardjp I found a small bug in user_variables #comments abou ceph_conf14:50
ApsuWe switched from a Jinja template to a Python module14:50
svgevrardjp: what tokens are you talking about?14:51
*** galstrom_zzz is now known as galstrom14:51
evrardjpok I get the issue, we are not speaking about the same stuff14:51
svgyou were talking about ceph client uuid?14:51
Sam-I-AmApsu: yeah... but does approd0's workaround apply to juno or newer versions?14:51
ApsuJuno.14:51
Sam-I-AmApsu: in other words, we really dont document how to 'officially' accomplish multiple vlan ranges in any version14:52
svgthe only ceph uuid is nova_ceph_client_uuid14:52
evrardjpsvg: Yes, but I realize that cinder_ceph_client_uuid is an openstack uuid, nothing really interesting for ceph right?14:52
evrardjpjust to summarize14:52
evrardjpI currently have my ceph cluster, with a pool for cinder14:52
svgno it's a uuid for libvirt config14:52
evrardjpI've created a user for it14:53
evrardjpit's mentionned as client.openstack in ceph auth list14:53
evrardjpso to use ceph in openstack I edited the openstack_user_config.yml14:53
ApsuSam-I-Am: Hm, apparently we don't. I thought it was present in comment form in the example user_config.14:53
Sam-I-AmApsu: no, its not... and its not obvious either.14:54
ApsuSam-I-Am: The 'right' way is a:b,c:d[,...]14:54
evrardjpsvg: in that file I have to write down a rbd_user and rbd_secret_uuid14:54
ApsuSam-I-Am: The example Does say it corresponds to the ml2_conf.ini plugin options, which uses comma separation. But that's not super clear14:55
evrardjpin the openstack_user_config.yml.example, the default value for rbd_secret_uuid is "cinder_ceph_client_uuid"14:55
Sam-I-AmApsu: yeah, i see that14:55
evrardjpso I thought this was the token used for auth14:55
evrardjpsvg: but it isn't right?14:55
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: Bump tempest sha  https://review.openstack.org/20910414:56
svgno14:56
Sam-I-AmApsu: debating re-opening that bug as a docs thing or just creating a new bug14:56
svgthe _uuid var needs to go in user_secrets and will be generated by the inventory14:57
ApsuSam-I-Am: Go for it, imo14:57
svgby that script14:57
evrardjpok14:57
Sam-I-AmApsu: option A or B ?14:57
evrardjpsvg: so I have to get the token at another time I guess14:57
evrardjpok14:57
ApsuSam-I-Am: Both/and. Close your eyes and point. Or, re-open as a docs thing. Since it will have appropriate context already.14:58
Sam-I-Amright14:58
svgevrardjp: I don't follow14:58
svgwhat token are you talking about?14:59
svgtoke != uuid14:59
*** javeriak has joined #openstack-ansible14:59
svgcinder_ceph_client_uuid: => user_secrets.yml14:59
svgand the name is default set:  inventory/group_vars/hosts.yml:cinder_ceph_client: cinder15:00
svgonly overrule if you need another name15:00
evrardjpsvg: I got that the uuid is for libvirt15:03
evrardjpfor the ceph auth you need a valid token for your client15:03
evrardjpyou get it from ceph auth get-or-create, IIRC15:03
svgyou mean a client 'secret'15:04
*** yaya has joined #openstack-ansible15:04
svgthe ansible scripts will manage that15:04
svgyou just need to mke sure you have ssh root access to your monitor hosts15:04
evrardjpyes, token - key - secret, whatever it's called15:04
evrardjpthat's an issue15:05
svgWell, given those terms are oveabused in openstack all the place, it gets confusing :)15:05
evrardjpyeah sorry15:05
evrardjp:)15:05
evrardjpso I don't really have to care about that15:05
svgno15:05
evrardjpthat token*15:05
evrardjpthat whatever*15:06
svgsee roles/ceph_client/tasks/ceph_auth.yml15:06
*** javeriak has quit IRC15:06
*** javeriak has joined #openstack-ansible15:06
evrardjpyeah I remember that15:06
evrardjpbut I was afraid that rbd_secret_uuid in openstack_*15:07
evrardjpwas used for auth15:07
evrardjpit's just for libvirt I guess15:07
svgyes15:07
svgAnyone around here that understands the inventory/dynamic_inventory.py sccript?15:07
matttdefine understand15:08
matttsvg: i've made a small change to it, but i've never looked at it in detail15:09
matttgot a specific question?15:09
svgWell, it barfs at me from a fresh config :)15:11
svg  File "inventory/dynamic_inventory.py", line 596, in _add_additional_networks15:11
svg    container['ansible_ssh_host'] = networks[old_address]['address']15:11
svgKeyError: 'address'15:11
svgtrying to understand what that old_address stuff might be15:11
odyssey4mesigmavirus24 so https://review.openstack.org/209047 failed to build, and https://review.openstack.org/208801 will likely also fail without that config - should I merge the patches or do you think it's worth trying to keep them seperate and just to figure out why it's failing and see if that can be resolved first?15:11
svggiven it's a fres config and not an upgrade, I could see how there wouldnt be old addresses15:11
sigmavirus24odyssey4me: IMO merge them so they'll pass15:12
*** daneyon has joined #openstack-ansible15:12
odyssey4meit looks like it's a dep failure: stderr: Could not find a version that satisfies the requirement pbr<2.0,>=1.3 (from oslo.middleware) (from versions: 0.11.0)\nNo matching distribution found for pbr<2.0,>=1.3 (from oslo.middleware)\n', u'failed': True, 'attempts': 1, u'cmd': u'/usr/local/bin/pip install oslo.middleware'}15:12
sigmavirus24odyssey4me: it seems reasonable to me that with a SHA bump (on master (aka unstable)) we might need to update configuration etc.15:12
*** daneyon has quit IRC15:13
odyssey4mesigmavirus24 yeah, quite possible - I'm going to do a quick rebuild of a test AIO to see if it's something that can work without merging15:14
*** phalmos has quit IRC15:14
odyssey4methat dep failure is odd15:14
matttsvg: having a look, nothing jumps out of me immediately tho15:16
*** javeriak_ has joined #openstack-ansible15:16
sigmavirus24odyssey4me: so that's because we're pulling in an old version of requirements.txt15:17
sigmavirus24And I think we use the lower bound on things when building now15:17
sigmavirus24maybe15:17
sigmavirus24because the old lower bound in requirements.txt was >=0.1115:17
*** javeriak has quit IRC15:17
sigmavirus24and the oslo.middleware that we're pulling in isn't pinned as far as I can tell15:17
sigmavirus24so that has a different set of requirements from global-requirements and that is causing the conflict15:18
sigmavirus24Also  odyssey4me requirements synchronize across projects via reviews15:18
svgon a side node mattt, I found a small mistake in the ceph patch in etc/openstack_deploy/user_variables.yml: it doesnt document the new way of doing the ceph.conf config15:18
svgthis should fix it: http://sprunge.us/OYVd15:18
sigmavirus24so if that >=0.11,<2.0 requirement didn't sync to every project that's prior to the SHAs currently on master, yaprt might be packaging 0.11 because that's the only version that matches everything15:18
sigmavirus24because it might be >=0.11,<1.0 on some package and 0.11.0 is the only version that matches of pbr15:19
*** daneyon has joined #openstack-ansible15:19
matttsvg: derp, i forgot to update that15:20
matttsvg: are you going to review that or shall i?15:20
svgI got it ready, was just wondering if I need to do more than just a review (need to file a bug?)15:20
evrardjpsvg: your link was PRECISELY what I was asking now15:21
evrardjp:p15:21
evrardjpwhat I was planning to ask*15:22
*** phalmos has joined #openstack-ansible15:22
matttevrardjp: i herped the derp :(15:22
svgevrardjp: I mentioned it earlier to you :)15:22
evrardjpindeed, but with the pastebin it's easier :D15:22
matttsvg: wonder if you can target it at the existing bug15:23
evrardjpI grepped so I found the ceph_mons thing15:23
evrardjpbut still it's better in the doc15:23
*** javeriak_ has quit IRC15:23
evrardjpceph_mons should be written like the old mon_hosts? or within brackets?15:25
matttsvg: i don't think a bug is necessary for that due to it changing a commented out section in user vars, however others may disagree15:25
mattts/changing/removing/15:25
evrardjp['ip1','ip2','ip3'] ?15:25
matttevrardjp: ceph_mons is a list15:25
odyssey4mesigmavirus24 odd, we have an issue here - with the updates sha's the pbr version fail is still there15:25
odyssey4meNo matching distribution found for pbr<1.0,>=0.5.21 (from python-seamicroclient)15:26
evrardjpif the doc is incorrect, it's a bug, cause we consider the documentation as code :p15:26
matttevrardjp: https://github.com/mattt416/rpc-openstack/blob/ceph_local/rpcd/etc/openstack_deploy/user_variables.yml#L38-L4515:26
* mattt goes and sprays himself down with bleach15:26
odyssey4mesigmavirus24 the repo server has pbr 1.4.015:26
d34dh0r53evrardjp: svg: something I put together yesterday https://gist.github.com/d34dh0r53/015a00d2100089fd4a0e, comments are welcome :)15:27
odyssey4meso I move to remove python-seamicroclient from the requirements15:27
odyssey4melet me test if that works15:27
sigmavirus24odyssey4me: so uh15:27
sigmavirus24There should be a way to tell tempest things to bugger off15:28
matttevrardjp: i like to create bugs for everything, but i'm a bit pedantic and others disagree on the need15:28
openstackgerritSerge van Ginderachter proposed stackforge/os-ansible-deployment: Update the documented ceph user variables  https://review.openstack.org/20913015:28
sigmavirus24mattt: bugs for everything works for me because it usually describes why a patch is being worked on15:28
sigmavirus24that way if someone else has to pick it up they have context15:29
sigmavirus24/cc evrardjp15:29
odyssey4mesigmavirus24 this is the issue with the repo trying to satisfy all requirements and only have one version of all the requirements in it - we end up getting stuck in this nastiness15:29
evrardjpmattt: :D I agree, bugs are cool stuff. but you know I'm a hipster, I'm working with openstack and all...15:29
evrardjp:p15:29
evrardjpd34dh0r53: I guess the gist is already outdated15:30
evrardjpbecause the user_variables has changed15:30
evrardjp (the ceph.conf part)15:31
svgyes15:31
d34dh0r53lol, when?15:31
matttlolz15:31
d34dh0r53I made this yesterday :/15:31
matttodyssey4me: *silence*15:31
svgd34dh0r53: nova_ceph_client_uuid: missing is a bug?15:32
d34dh0r53svg: I'm not sure, possibly an illustration of my unfamiliarity with ceph15:32
evrardjpit proves one thing: ceph brings a lot of interest.15:33
svgthe default is to use the cinder value15:33
svgnova_ceph_client_uuid: '{{ cinder_ceph_client_uuid | default() }}'15:33
svgas nova needs access to both cinder and nova ceph backends15:33
svgone user to rule them both15:33
d34dh0r53so when I do that the virsh secret-define fails with a duplicate key15:34
d34dh0r53ahh15:34
d34dh0r53makes sense15:34
*** yaya has quit IRC15:34
matttd34dh0r53: yeah if you set the uuid in your secrets file you won't see that15:34
evrardjpsvg: for the ceph_mons I can use an itemized list, right? I didn't get the "it's a list" remark from mattt, as list have numerous ways to be written :p15:36
*** javeriak has joined #openstack-ansible15:37
svgwell, both [1, 2, 3] and - 1\n- 2\m- 3 are valid yaml :)15:37
evrardjpif it's an inline list it's ['1','2','3'] i guess15:37
matttevrardjp: i thought they were the same thing15:37
evrardjpok that's what I thought15:37
d34dh0r53I used  - ip.ad.dr.ess\n in mine and it worked fine (needs to be indented under ceph_mons:)15:38
evrardjpmattt I'm just taking cautious steps here.... Don't want to really redo all that stuff because of a typo15:38
evrardjpsorry for being overly verbose15:38
evrardjpd34dh0r53: that is what I thought15:39
matttevrardjp: :thumbsup:15:39
svgevrardjp: mattt integers vs strings if you quote them15:39
evrardjpsvg: true15:40
*** yaya has joined #openstack-ansible15:40
*** javeriak_ has joined #openstack-ansible15:42
*** KLev-away is now known as KLevenstein15:42
evrardjpit's really different to have deployed host to connect on the ceph storage and the deploying host connecting to the ceph storage on my side... so it changes the model and also how the ceph.conf is fetched...15:43
*** javeriak has quit IRC15:44
d34dh0r53reviews plz https://review.openstack.org/#/c/209130/15:45
odyssey4mesigmavirus24 as I dig down the rabbit hole it seems that the dearth of clients we insist on including in the utility container is the culprit15:48
odyssey4meI'm starting to think that a cull is in order15:48
evrardjpd34dh0r53: done15:48
d34dh0r53tys15:48
odyssey4mewhy should we include clients for projects which we aren't setting up the back-ends for15:48
sigmavirus24odyssey4me: I thought tempest was put into virtualenvs15:48
*** alop has joined #openstack-ansible15:48
sigmavirus24why isn't that in the virtualenv with the rest of tempest?15:48
odyssey4mesigmavirus24 it's not tempest, it's the utility container's pip packages15:49
sigmavirus24Oh15:49
sigmavirus24Why is that client in there then?15:49
* sigmavirus24 is lost =P15:49
sigmavirus24Sam-I-Am: can you look at 209130?15:49
odyssey4meyeah, exactly15:49
Sam-I-Amsigmavirus24: not sme, but ok from a docs thing15:50
Sam-I-Aman example would be useful15:51
odyssey4meyeah, I think that perhaps it'd be good to put together a doc to add to the repo and attached to the install guide15:52
odyssey4merather than trying to be too complete in user_variables15:52
palendaeodyssey4me: That makes sense... sigmavirus24 and I talked about making a schema validator for user_variables and/or user_config, and generating the example files from that15:53
palendaeIn that scenario, we couldn't have docs in the example file15:53
sigmavirus24palendae: so we could generate docs in the example file with that15:54
sigmavirus24If we have documentation in the schema15:54
sigmavirus24but yeah15:54
sigmavirus24I have N things to work on right now15:54
*** phalmos has quit IRC15:54
Sam-I-Amconfig file generation is a Good Thing15:54
sigmavirus24And K conversations happening in different channels15:54
Sam-I-Amdont do a neutron :)15:54
odyssey4mepalendae sigmavirus24 I love that idea - rather have docstrings or something in the code and generate example configs (and docs) from them15:54
palendaesigmavirus24: Oh, no, it's just a mention of, "We have this idea"15:55
*** yaya has quit IRC15:55
palendaeNot to work on now15:55
palendae*Maybe* at the work hackathon in a few weeks15:55
evrardjpSam-I-Am: for the patch you asked me to test, does it involve a change of neutron config for better testing?15:55
odyssey4mepalendae I think for dev documentation that'd be perfect15:56
evrardjpI've cherry-picked it, and I was planning to test directly15:56
palendaeodyssey4me: There's also the problem of people generating invalid configs and filing bugs15:56
palendaeBecause they forgot a variable15:56
palendaeSo I'd like to help remedy that15:56
sigmavirus24yep15:56
odyssey4mefor more long-hand documentation made for first-timers we can then narrow down the docs we carry to only cover the simple and common use-cases15:56
sigmavirus24That's why i wrote the project in the first place15:56
palendaesigmavirus24: Right15:56
sigmavirus24"I forgot a thing and forgot its format"15:57
palendaeBut reducing the number of places we have to add a new option would be good15:57
odyssey4mesigmavirus24 palendae yep, and then there're the format and name changes between versions too :/15:57
palendaeNot sure if we'd handle that15:57
Sam-I-Amevrardjp: it doesnt change how neutron works15:57
palendaeminimum viable product :)15:57
Sam-I-Amevrardjp: it just removes unnecessary config items from certain places, and clarifies some others15:58
palendaeAnd things like infra-repo_hosts vs openstack_repo_url being defined in 2 different files would need to be taken into account15:58
odyssey4meevrardjp it should work with your existing config15:58
*** woodard has quit IRC15:58
palendaeYou need one or the other15:58
sigmavirus24palendae: we can graft that on later15:58
odyssey4meif it doesn't, then the patch needs to be fixed :)15:58
palendaeSure15:58
sigmavirus24like "This variable name has been renamed to blah"15:58
*** woodard has joined #openstack-ansible15:58
palendaeas long as we don't use oslo.config's deprecation methodology15:58
openstackgerritSerge van Ginderachter proposed stackforge/os-ansible-deployment: Update the documented ceph user variables  https://review.openstack.org/20913015:58
palendaeCause that was impenetrable15:58
sigmavirus24palendae: we won't be able to15:58
palendaeGood15:59
odyssey4meoh and sigmavirus24 you were right - it was all the tempest clients, but I think they still get taken into account for all the requirements.... anyway, testing another try and making this work15:59
evrardjpok relaunching all my playbooks now15:59
Sam-I-Ambug triage meeting?16:01
Sam-I-Amor something16:01
*** phalmos has joined #openstack-ansible16:02
woodardbug meeting?16:02
odyssey4mealrighty everyone - we have a bug triage meeting now16:02
Sam-I-Amyes, we do16:03
odyssey4mecloudnull, mattt, andymccr, d34dh0r53, hughsaunders, b3rnard0, palendae, Sam-I-Am, odyssey4me, serverascode, rromans, mancdaz, dolphm, _shaps_, BjoernT, claco, echiu, dstanek, jwagner, ayoung bug triage meeting in this channel :)16:03
odyssey4melet's start from the top: https://bugs.launchpad.net/openstack-ansible/+bug/147948416:03
openstackLaunchpad bug 1479484 in openstack-ansible trunk "server_id missing in my.cnf" [Medium,New]16:03
odyssey4mephalmos you around?16:04
*** yaya has joined #openstack-ansible16:04
phalmosYes sir16:04
odyssey4meok, we discussed this briefly on thu and left it as 'new' to ensure we could spend a little more time on it today16:04
odyssey4methis should be a pretty simple template change in the galera_server role - I guess the only complexity is to ensure the numbers are unique for each node16:05
evrardjpsvg: isn't there a space missing in your new example? ;)16:05
svgWhere?16:05
evrardjpend of day I didn't see if there was one space or two...16:05
evrardjphttps://review.openstack.org/#/c/209130/2/etc/openstack_deploy/user_variables.yml16:06
Sam-I-Amphalmos: what does this change accomplish?16:06
evrardjpceph_mons16:06
odyssey4mephalmos which section/file should the server_id setting be found?16:06
svgyes, though one space is still valid yaml :)16:06
evrardjpoh16:06
phalmosIt allows a directed replication if you need to restore16:06
evrardjpreally ?16:06
svgof course16:06
evrardjpgood to know16:07
Sam-I-Amphalmos: can you add those details to the bug?16:07
odyssey4meevrardjp yes, it just looks better if it's two :p16:07
phalmosyes.16:07
Sam-I-Amand where the option goes, pls16:07
Sam-I-Ammakes it easier on the brain later16:07
odyssey4meSam-I-Am +116:07
Sam-I-Am'why is this what what?' heh16:07
phalmoswill do16:07
openstackgerritSerge van Ginderachter proposed stackforge/os-ansible-deployment: Update the documented ceph user variables  https://review.openstack.org/20913016:07
*** erikmwilson has joined #openstack-ansible16:07
evrardjp:D16:08
odyssey4meonce that's done we can mark it as triaged and we'll hunt down someone to put a patch in for it16:08
Sam-I-Amphalmos: or you can patch it :)16:08
odyssey4methat said, if anyone here wants to pick it up, feel free to do so :)16:08
Sam-I-Amlooks fairly straightforward16:08
odyssey4menext: https://bugs.launchpad.net/openstack-ansible/+bug/139968416:08
openstackLaunchpad bug 1399684 in openstack-ansible "tenant_network_types should be configurable" [Low,New]16:09
Sam-I-Amodyssey4me: i just commented on this bug16:09
odyssey4meI see so.16:09
odyssey4meSam-I-Am does your recent review change this at all?16:09
Sam-I-Amif it actually works that way (and i think it does), do we simply want to say 'order the networks in the order of priority' or actually code up some way to specifically set it16:10
Sam-I-Amno, it doesnt16:10
Sam-I-Amadding an option for default project network type probably isn't difficult, but it needs to validate that the value is also in one of the provider network stanzas16:10
odyssey4meso it's most likely that unless we introduce some sort of ordering flag that this will never be possible to order16:11
Sam-I-Amdont want to have default network = vlan and there's no vlan provider network16:11
Sam-I-Amodyssey4me: right now i think it just uses the order of your provider networks16:11
odyssey4meI like cloudnull_afk's thinking - just allow it to be overridden, then deployers can specify an order if they want16:11
Sam-I-Amso it isnt indeterminate16:11
odyssey4meSam-I-Am yeah, it'll likely be a list return which will be different every time most likely16:12
Sam-I-Amthe only value that really matters is the first value16:12
Sam-I-Amso thats the only one we need to consider16:12
odyssey4meso this needs some extra work to triage16:12
odyssey4mewe can confirm it, and it's already marked as low priority16:12
Sam-I-Amif you create a network as a non-admin project, it uses the first type in the list16:12
Sam-I-Amthe only way to use any of the other types is to either a) be admin or b) allow it in policy16:13
odyssey4menext: https://bugs.launchpad.net/openstack-ansible/+bug/141276216:13
openstackLaunchpad bug 1412762 in openstack-ansible juno "Disable unneeded heat resource-types" [Low,Confirmed]16:13
odyssey4memattt are you around?16:13
odyssey4meSam-I-Am on the previous bug, if you want to spend some time triaging that then go for it16:14
Sam-I-Ammmkay16:14
odyssey4meok, we'll carry this bug until next week16:14
matttodyssey4me: on a call bu tyes16:14
mattt*but yes16:14
svgmattt: or someone else: trying to understand the dynamic inventory script, and why it barfs here: http://paste.ubuntu.com/12001011/16:15
svgbut I'm off heading home, ttyl guys16:15
odyssey4memattt I resurrected the above bug (disable unneeded heat resource types for discussion with regards to whether it needs to be done or whether we should can it16:15
odyssey4memiguelgrinberg is of the opinion that it's not really worth the bother16:15
matttodyssey4me: it's a nice to have for sure16:15
matttodyssey4me: but low prioprity16:16
odyssey4meI am paraphrasing quite a bit there :)16:16
mattt*priority16:16
odyssey4meok mattt I'm going to classify it as a wishlist item then16:16
matttodyssey4me: that sounds fair16:16
miguelgrinbergmattt: maybe it makes sense for rpc-openstack, but not for osad16:16
odyssey4mealright, wishlist - but no target16:17
odyssey4menext: https://bugs.launchpad.net/openstack-ansible/+bug/147947316:17
openstackLaunchpad bug 1479473 in openstack-ansible trunk "Need log_slave_update enabled" [Wishlist,New]16:17
odyssey4mephalmos as with the other one, if you're able to add examples of what you're looking for into the bug then we should easily get a patch in pretty quickly16:18
odyssey4methis is a low hanging fruit wishlist item which helps with data restores when they're needed16:18
phalmosyup16:18
odyssey4menext: https://bugs.launchpad.net/openstack-ansible/+bug/147543616:19
openstackLaunchpad bug 1475436 in openstack-ansible juno "VLAN range issue in ml2_conf.ini" [Wishlist,Triaged]16:19
Sam-I-Amyeah16:19
ApsuFun one16:19
Sam-I-Ami re-opened this16:19
*** woodard has quit IRC16:19
Sam-I-Ammostly because we dont document how to accomplish this16:19
Sam-I-Amprobably needs a patch for juno, and another patch for master for backport to kilo16:20
odyssey4meSam-I-Am a doc patch then?16:20
*** woodard has joined #openstack-ansible16:20
Sam-I-Amodyssey4me: yeah, i think this is all docs... perhaps some testing.16:20
ApsuYep16:21
Sam-I-Amseems like appprod0 posted the workaround for juno16:21
Apsus/workaround/injection attack/16:21
Sam-I-Amhaha16:21
ApsuIt's a smart workaround, makes me laugh.16:21
Sam-I-Amone of these days we need to validate stuff a bit better :)16:21
Sam-I-Ambut thats a side project16:21
ApsuValidation is for sissies. Be liberal in what you accept!16:21
Sam-I-Amwasnt most of this written in texas?16:22
Sam-I-Amthere aint no liberal16:22
ApsuSA is a microcosm unto itself.16:22
Sam-I-Ammicromexico?16:23
Apsululz16:23
ApsuOk, odyssey4me can move on now :P16:23
Sam-I-Amyep16:23
Sam-I-AmNEXT!16:23
odyssey4mesorry - had someone come to my desk :p16:23
odyssey4meSam-I-Am is this a doc patch then?16:24
Sam-I-Amodyssey4me: think xo16:24
Sam-I-Amso16:24
odyssey4meok, is this something you will be picking up?16:24
Sam-I-Amyeah16:25
odyssey4meok, I'll assign to you - shall I target it to a milestone or leave it for now?16:25
Sam-I-Amwhatever is best there16:25
Sam-I-Amnot sure what the target would be16:26
odyssey4mehttps://bugs.launchpad.net/openstack-ansible/+bug/147912716:26
openstackLaunchpad bug 1479127 in openstack-ansible "nf_conntrack table fills on swift nodes" [Undecided,New]16:26
*** bapalm_ has quit IRC16:27
Sam-I-Amseems like a valid issue16:27
Sam-I-Ambut !sme16:27
odyssey4meI've definitely seen this in production before16:27
odyssey4meApsu rackertom any comment on this?16:27
ApsuSure, like we've been doing for ~15 years or so, if you know you'll have lots of connection initiation, you set the time-wait reuse sysctl16:28
ApsuJordan linked a related bug that had that exact fix16:28
odyssey4methis is marked as related and has patches for it https://bugs.launchpad.net/openstack-ansible/+bug/144136316:28
openstackLaunchpad bug 1441363 in openstack-ansible trunk "nf_conntrack schould be unloaded on swift object server" [Medium,Fix released] - Assigned to Andy McCrae (andrew-mccrae)16:28
ApsuYep16:29
*** openstackgerrit_ has quit IRC16:29
odyssey4meso do we still have a problem? was the previous patch not good enough?16:29
ApsuRaising the nf_conntrack_max is basically never correct unless you expect to maintain a huge number of active connections16:29
odyssey4meor is this a situation where someone just wasn't running with that patch?16:29
ApsuIf your issue is connection creation speed, you set tw_reuse16:29
odyssey4meit seems to me like we need ot know what version they were running to determine whether this had the tw_reuse option set16:30
odyssey4memarking as incomplete16:30
ApsuWell not only that, but we need to understand why they're running out of conntrack entries.16:31
ApsuAre these TW connections (without that sysctl)? Or are there > nf_conntrack_max active connections16:31
ApsuA simple ss -s to show a summary would be helpful16:31
odyssey4meApsu can you pose some relevant question in the bug please?16:31
ApsuSure16:32
odyssey4methanks Apsu16:33
odyssey4menext: https://bugs.launchpad.net/openstack-ansible/+bug/147936016:33
openstackLaunchpad bug 1479360 in openstack-ansible "MaaS: RabbitMQ's maas_user password not set or used in 10.1.10" [Undecided,New]16:33
odyssey4mepalendae you around?16:33
palendaeYep16:33
palendaeI'd imagine that would be a 10.1.12 thing16:33
odyssey4meis this a bug that's yet to be fixed?16:34
palendaeI think so16:34
odyssey4meok, cool - moving on: https://bugs.launchpad.net/openstack-ansible/+bug/147987016:34
openstackLaunchpad bug 1479870 in openstack-ansible "teardown.sh does not cleanup lvm.conf" [Undecided,New]16:34
palendaed34dh0r53: ^16:35
palendaerackertom: I think you looked at ^^ too16:35
odyssey4meheh, that is plausible - considering that teardown.sh is a dev/test tool I think we can wishlist this and move on?16:36
palendaeI'd say so16:36
odyssey4mehttps://bugs.launchpad.net/openstack-ansible/+bug/148091416:36
openstackLaunchpad bug 1480914 in openstack-ansible " Add Ceph/RBD support to playbooks" [Undecided,New]16:36
palendaeI think that's in progress16:36
odyssey4meah, that's a docimpact bug16:36
palendaeOh16:37
odyssey4meI'll assign to docs and move on16:37
odyssey4menext: https://bugs.launchpad.net/openstack-ansible/+bug/148098716:37
openstackLaunchpad bug 1480987 in openstack-ansible ".my.cnf should not contain LB VIP" [Undecided,New]16:37
phalmosme again16:38
odyssey4mehmm, ok I disagree - except on the galera containers themselves16:38
phalmosYes, in the containers is where things get confusing16:38
phalmoscontainers' client should only hit th elocal instance16:39
phalmosnot the VIP16:39
odyssey4mephalmos is this juno specific, as I recall in kilo/master we already set the host to 127.0.0.1 in the galera containers16:39
phalmosThis was Juno.  I was unaware of the change in kilo/master16:39
odyssey4meok cool - will mark this for juno only16:39
*** yaya has quit IRC16:40
palendaephalmos: Assuming you'd like this for 10.1.12 then?16:40
palendaeI'll get cards made on RAX's side for these so we have visibility16:40
phalmosI guess so16:40
phalmoswe should keep it consistent with Kilo.  That way it isn't that much of a departure16:41
phalmosfor support16:41
palendaeFair16:41
odyssey4mephalmos so in kilo only the galera containers are set to look at 127.0.0.116:41
phalmosok, makes sense16:42
odyssey4mewe have a review in to make sure that everything else points to the vip as it currently also points to 127.0.0.1 which is useless :p16:42
odyssey4mefyi https://review.openstack.org/20793916:42
odyssey4mehttps://bugs.launchpad.net/openstack-ansible/+bug/148138016:43
openstackLaunchpad bug 1481380 in openstack-ansible trunk "Bump tempest sha" [Undecided,New]16:43
odyssey4memattt this is likely to be covered by https://review.openstack.org/208801 but it's fine that you have an independant review in which may be useful for backporting to kilo16:43
odyssey4meall done, thanks all - are there any other bugs that anyone wants to raise for discussion?16:45
Sam-I-Amnot here16:46
*** TheIntern has quit IRC16:48
odyssey4mealright, then I guess that about covers it :)16:50
odyssey4methank you all for your time16:51
*** fawadkhaliq has quit IRC16:52
rackertompalendae: Sorry, went to lunch. Yes, I looked at that problem once upon a time. There wa a .bak file being created and if you ran the setup too many times the .bak became the modified version.16:52
rackertomSo, a simple way would be if *.bak does not exist, copy *.conf to *.orig.16:53
rackertomSorta like dpkg does16:53
evrardjpSam-I-Am: I'm off for today, and I'm not available tomorrow... So for your testing... it's following its course, but at the moment only the setup-infrastructure is re-running .... It's gonna take a while before you get your results. Sorry for that16:57
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Improve Keystone Apache configuration  https://review.openstack.org/20904717:00
*** yaya has joined #openstack-ansible17:00
odyssey4mesigmavirus24 stevelle rackertom ^ might do the trick - busy running two tests to find out17:00
*** phalmos has quit IRC17:01
rackertomodyssey4me: I totally agree with Apsu comment on there. Having 300k connections actively tracked by swift seems insane to me.17:01
odyssey4menot sure if tempest actually needs those for some reason17:01
Sam-I-Amevrardjp: np, thanks for testing it17:01
sigmavirus24I was about to dart out for a ride over lunch17:01
Sam-I-Amsigmavirus24: so ride?17:01
Apsurackertom: nod17:01
sigmavirus24I'll test it when I get back dolphm17:01
sigmavirus24er odyssey4me17:01
Apsurackertom: Something's screwy. Most likely it's just a bunch of TIME-WAIT NAT entries17:02
ApsuThe sockstat summary should tell us immediately17:02
* dolphm got excited17:02
* dolphm is dissapoint17:02
rackertomYeah, my guess is the monitoring tool is behaving badly and opening/closing connections quickly whereas maybe a persistent connection might be better.17:03
*** yaya has quit IRC17:03
ApsuYep. Or at least reusing TWs, which is 99.9999% safe these days17:04
ApsuRecycling is still iffy. I always get nervous when folks are like "just set this sysctl!".17:04
ApsuBut I get more nervous when they start upping sysctl maxes.17:04
Sam-I-Amheh17:04
ApsuBecause that's prooooobably not the solution to the actual issue17:04
Sam-I-AmApsu: why do we want real solutions?17:04
Sam-I-Amjust throw more X as it17:05
ApsuOh good point, I forgot we weren't talking about real engineering.17:05
ApsuMore is better.17:05
*** daneyon has quit IRC17:05
*** daneyon has joined #openstack-ansible17:05
*** abitha has joined #openstack-ansible17:06
*** javeriak has joined #openstack-ansible17:06
*** daneyon has quit IRC17:07
*** daneyon has joined #openstack-ansible17:07
*** javeriak_ has quit IRC17:08
d34dh0r53core reviews please https://review.openstack.org/#/c/209130/17:11
rromanshttp://docs-internal.rackspace.com/rpc/api/v11/bk-rpc-swift/content/ch-object-storage-overview.html17:21
rromanssorry, wrong window17:22
*** daneyon_ has joined #openstack-ansible17:27
*** daneyon has quit IRC17:30
*** javeriak has quit IRC17:36
*** erikmwilson has left #openstack-ansible17:45
*** javeriak has joined #openstack-ansible17:58
*** javeriak has quit IRC18:03
*** javeriak has joined #openstack-ansible18:04
*** TheIntern has joined #openstack-ansible18:05
Sam-I-Amstupid gate failures18:10
*** phalmos has joined #openstack-ansible18:13
sigmavirus24Sam-I-Am: are they stupid?18:13
Sam-I-Amsigmavirus24: failing for no useful reason, sure18:14
sigmavirus24that's not stupid, that's predictable18:14
Sam-I-Amlulz18:16
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Improve Keystone Apache configuration  https://review.openstack.org/20904718:19
odyssey4mesigmavirus24 it looks like openstack-ci is under pressure again and that our gating on master won't be functional until tomorrow (if then)18:21
odyssey4mewe'll need to keep testing manually until we get a pass on a patch18:21
odyssey4methe above patch is still an attempt to keep the unblock relatively clean, but we're starting to need multi-purpose patches to unblock anyway18:22
odyssey4meI don't want to merge them until I get a clean build with them both added, but a fail with just one18:22
odyssey4meso far I have a clean build, but not a successful tempest test18:23
sigmavirus24interesting18:27
*** bapalm_ has joined #openstack-ansible18:41
odyssey4melbragstad great feedback - did those calculations come from some sort of background tests or something?18:42
lbragstadodyssey4me: those are from when dolphm and I poked at keystone during performance tests, not sure if the *actual* values of those calculations are what you need but that's how we went about the math18:43
lbragstadthose numbers are what seemed to give us the best results18:44
*** phalmos has quit IRC18:50
*** jasondotstar has joined #openstack-ansible19:01
odyssey4melbragstad excellent, I'll update the defaults19:02
*** phalmos has joined #openstack-ansible19:05
*** alextricity has quit IRC19:17
*** TheIntern has quit IRC19:18
*** TheIntern has joined #openstack-ansible19:20
*** phalmos has quit IRC19:24
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Improve Keystone Apache configuration  https://review.openstack.org/20904719:32
*** phalmos has joined #openstack-ansible19:32
odyssey4mesigmavirus24 are you around?19:38
*** britthouser has joined #openstack-ansible19:39
*** jasondotstar is now known as jasondotstar|afk19:39
*** britthou_ has joined #openstack-ansible19:40
sigmavirus24yep19:42
sigmavirus24odyssey4me:19:43
*** britthouser has quit IRC19:43
odyssey4mesigmavirus24 so I've narrowed down the tempest test failures (at least some) to swift rejecting auth19:43
sigmavirus24hm19:43
odyssey4meI've also confirmed this using the openstack client to simply try to create a container in swift from the utility lxc container19:44
sigmavirus24any explanation in swift logs?19:44
odyssey4mesigmavirus24 just the usual stfu: proxy-server: Invalid user token - deferring reject downstream19:44
sigmavirus24odd19:45
sigmavirus24I'm still building that patch but I guess I'll have to restart =/19:46
odyssey4mewhich patch?19:47
sigmavirus24yours19:47
sigmavirus24the keystone apache config one19:47
sigmavirus2420904719:47
odyssey4meI've done the sequence of that + the sha updates, and am using the previous patch set of the keystone/apache one.19:48
odyssey4meinteresting, it looks like keystone approves the token, but swift denies it19:48
odyssey4meodd19:48
sigmavirus24could it be an issue with roles?19:50
sigmavirus24as in yes this token is valid comes from keystone and then swift's default policy is different in the new SHA so the tempest user isn't authorized to do whatever?19:50
odyssey4methat's a possibility19:51
odyssey4mealthough I'm using the admin user for the testing right now19:52
odyssey4mesigmavirus24 here's the client debug log: http://paste.openstack.org/show/tQSr8mOjePbwpH3OlD8J/19:54
sigmavirus24odyssey4me: those are some mighty odd logs19:58
odyssey4mesigmavirus24 welcome to the openstack client logs :)19:58
sigmavirus24It looks as though openstackclient tries twice before failing19:58
odyssey4mewell, if it's ok I'll hand this over to you - see what you can do to dig up the next issue and hopefully resolve it19:59
odyssey4meotherwise I'll pick it up in the morning19:59
*** javeriak_ has joined #openstack-ansible19:59
sigmavirus24yeah I'll try to dual wield tasks20:01
*** javeriak has quit IRC20:02
odyssey4mesigmavirus24 you know the priorities, so don't kill yourself over it20:03
sigmavirus24yeah20:04
sigmavirus24but killing myself is half the fun20:04
odyssey4mestevelle you around? if you have a gap to dig into it, the patches I've submitted get us to a successful build but swift appears to be rejecting auth and it needs digging into20:04
odyssey4mesigmavirus24 stevelle was looking into this last night, and it's blocking his work, so if he has cycles then he can take over :)20:05
odyssey4meyou can just shake pom poms from the sidelines :p20:05
stevelleIf I get a gap I'll repro odyssey4me20:06
sigmavirus24erry day I'm building AIOs20:06
*** yaya has joined #openstack-ansible20:06
odyssey4mealright, have a good day - I'll pick up in the morning20:07
odyssey4mepop me an email if you find something more, or update the review with comments or whatever20:07
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Reduce neutron configuration  https://review.openstack.org/20459720:10
*** yaya has quit IRC20:16
*** javeriak_ has quit IRC20:27
*** woodard has quit IRC20:50
*** yaya has joined #openstack-ansible20:51
*** jmckind has joined #openstack-ansible20:56
matttodyssey4me: oops, didn't see that review ... i can close mine off if the end-to-end bump will go through relatively quickly21:04
mattt(i'll review it tomorrow to help that along)21:04
*** bapalm_ has quit IRC21:07
*** jasondotstar|afk is now known as jasondotstar21:07
*** abitha has quit IRC21:10
*** abitha has joined #openstack-ansible21:11
matttsvg: sorry, had to run off to airport earlier, can you check if your openstack_user_config.yml has ip_from_q names under the networks in provider_networks match the names in cidr_networks?21:16
*** dmsimard has quit IRC21:21
*** spotz is now known as spotz_zzz21:24
*** jmckind has quit IRC21:24
*** jmckind has joined #openstack-ansible21:26
*** dmsimard has joined #openstack-ansible21:40
*** yaya has quit IRC21:43
*** yaya has joined #openstack-ansible21:43
*** phalmos has quit IRC21:51
*** yaya has quit IRC21:53
*** JRobinson__ has joined #openstack-ansible22:00
*** jmckind has quit IRC22:02
*** TheIntern has quit IRC22:05
*** sigmavirus24 is now known as sigmavirus24_awa22:25
*** KLevenstein has quit IRC22:30
*** jaypipes has quit IRC22:35
*** jasondotstar has quit IRC22:36
*** galstrom is now known as galstrom_zzz22:40
*** sdake has quit IRC23:00
*** jasondotstar has joined #openstack-ansible23:20
*** jmckind has joined #openstack-ansible23:22
*** jmckind has quit IRC23:23
*** jmckind has joined #openstack-ansible23:24
*** sdake has joined #openstack-ansible23:45
*** sdake_ has joined #openstack-ansible23:48
*** sdake has quit IRC23:52
*** galstrom_zzz is now known as galstrom23:55

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