Tuesday, 2015-03-31

palendaejaveriak: Oops00:01
palendaejaveriak: I'm honestly not sure - can always move it00:01
javeriakso I should go ahead and just push to kilo ?00:02
javeriakis that appropiate?00:02
palendaejaveriak: Is it the plumgrid stuff?00:03
javeriakyes its is00:03
*** mahito has quit IRC00:03
palendaeI would say put it in kilo for now, and we can discuss on the Thursday meeting at worst00:03
javeriakI decided it was better to do this in two steps, introduce the modularizing stuff in one spec/commit and the add the plumgrid plugin in the next00:03
palendaeI don't know that it would make it in for our first kilo release (which will be 11.0.0), but better to have it in the specs repo than not00:04
palendaeI'd agree with that00:04
javeriakwhat's the code freeze date for 11.0.0?00:05
palendaeIt'll be after kilo is officially released upstream; we're working on the kilo package support now00:06
javeriakok, right00:09
*** sigmavirus24 is now known as sigmavirus24_awa00:09
*** mahito has joined #openstack-ansible00:11
palendaejaveriak: This patch will be the starting point https://review.openstack.org/#/c/166986/00:11
palendaejaveriak: Hopefully that'll be accepted by Wednesday at the latest00:11
javeriakand if we were interested in 10.1.1, backporting would be possible after the original commits merged on master correct?00:13
palendaeThe 10.x version would likely be 10.2, but yes - if you're interested, backporting could be possible. It's worth noting that 10.x is considered Rackspace technical debt; 11.0.0 and on are to be the community driven ones00:18
palendaeWhat that means in technical terms is the playbooks and variables are in different locations00:19
*** vmtrooper has joined #openstack-ansible00:19
javeriakSo 11.0.0 seems to be bringing in major changes. We would generallly be interesed in 10.x at the moment.00:22
javeriakAre 11.0.0 and 10.2 going to be tagged at the same time?00:23
palendaeThat I don't know00:24
palendae11.0.0 will be cut from master00:24
palendaeMaster has the 'galaxified' roles00:24
*** vmtrooper has quit IRC00:24
palendaeWhich were pulled out of the rpc_deployment directoy00:24
palendaeWe're not abandoning 10.x though00:24
javeriak10.1.3 doesnt seem to have come out yet either?00:25
javeriakSince I've been working off of the 10.x branch, I take it I should commit from the same rather than master?00:26
palendaeThat'll probably be easiest. the numbered ones are tags, the icehouse, juno, and master ones are the branches00:30
javeriakyep right thats what I meant, ok cool thanks, for now I will just push in my specs to the kilo directory00:36
palendaeCool00:40
stevellepalendae: if you have any clues about my gating joy, I'd be happy for deets00:42
palendaestevelle: the command vs shell?00:43
stevellepalendae: no, the lxc patch00:43
stevellejust lots of tempest failures00:44
stevelleroot cause escaping me00:44
palendaeLooking00:45
palendae500s >.<00:45
palendaestevelle: I haven't seen these in my testing so far00:48
stevelleyeah, it has to be a problem in the code00:48
stevelleguessing it's "ip link add name ${LXC_BRIDGE} type bridge"00:49
palendaeIt's failing on neutron too...00:50
palendaeI don't see anything in the console with 'LXC container', which is what the script is outputting00:53
stevellepalendae: https://review.openstack.org/#/c/169069/5/playbooks/roles/lxc_hosts/templates/lxc-system-manage.j2,unified line 206 I think the condition is inverted.  needs a !00:53
stevellenot confident of that00:54
palendaeThat reads to me like the conditional is attempting to actually create it00:55
palendaeSo if it successfully works, configure it00:55
palendaeInteresting that we use ip link in one part and brctl add in another00:56
stevellethat was done specifically so we could avoid screen scraping existence of the bridge with "brctl show"00:59
stevellealternative would be like if [ $(brctl show | grep ${LXC_BRIDGE} | wc -l) ]01:00
*** javeriak has quit IRC01:03
*** javeriak has joined #openstack-ansible01:15
palendaeAh, right01:20
*** javeria has joined #openstack-ansible01:26
*** javeria has quit IRC01:28
*** javeriak_ has joined #openstack-ansible01:30
*** javeriak has quit IRC01:31
*** javeriak_ has quit IRC01:31
*** javeriak has joined #openstack-ansible01:32
*** stevemar has joined #openstack-ansible01:39
cloudnullstevelle the latest set of failures (500 errors) loot to be neutron specific I've gone ahead and fired off a retry. we'll see if it still dies.02:04
palendaecloudnull: Did you see javeriak's questions? Do we have a way to communicate estimated release dates on launchpad targets?02:05
palendaeI assume we could edit at https://launchpad.net/openstack-ansible/+milestones ?02:05
cloudnullwithin launchpad we can set release dates.02:06
cloudnull11.x, per launchpad, has no expected release date.02:06
palendaeWould be good to relay some of those timelines to the community02:06
palendaeRight02:06
palendaeNor does 9.0.5 :)02:06
cloudnull10.1.3 is past due, due to a few issues being worked through.02:07
cloudnullbut 10/9 are rax technical debt at this point.02:08
palendaeYeah, though aren't we supporting the past 2 series?02:08
*** vmtrooper has joined #openstack-ansible02:08
palendaeWell, current and current-102:08
cloudnullwe are.02:08
palendae(also, I dunno if that's written down for os-a-d)02:09
*** vmtrooper has quit IRC02:13
openstackgerritSteve Lewis proposed stackforge/os-ansible-deployment: Updated repository for minimum viable kilo install  https://review.openstack.org/16698602:40
*** javeriak has quit IRC02:43
*** javeriak has joined #openstack-ansible02:45
*** javeriak has quit IRC03:03
*** alextricity has quit IRC03:16
*** mahito has quit IRC03:41
*** vmtrooper has joined #openstack-ansible03:57
*** vmtrooper has quit IRC04:02
*** raminoid has joined #openstack-ansible05:32
*** javeriak has joined #openstack-ansible05:33
raminoidHi, I am new to OpenStack and I am tasked with bringing up a complete infrastructure on a sandbox account. This includes VMs, Floating IPs, Load Balancers, Security Groups, Puppet Master and Package server. I was told Ansible can help me here. I could use any guidance you have05:33
palendaeraminoid: It's late for me, but this channel's largely about this project: http://git.openstack.org/cgit/stackforge/os-ansible-deployment05:37
palendaeIt will set up an openstack environment for you, and can do what we call an 'all-in-one' to test it out on a single machine05:38
palendaeHowever, for multi-nodes, it does not try to do network configuration, nor does it try to do load balancing for production. There's an ansible role for HAProxy, but that's really only for development and testing05:39
raminoidthanks for the clarification05:44
palendaeraminoid: Sure thing. If you do check out the code and run it, the scripts/gate-check-commit.sh script will set up an AIO and try the tests05:45
*** vmtrooper has joined #openstack-ansible05:46
palendaeOr you can manually run scripts/bootstrap-aio.sh, then openstack-ansible (a wrapper script that source ansible variable files for you) setup-hosts, setup-infrastructre, and setup-openstack05:46
*** markvoelker has quit IRC05:48
*** vmtrooper has quit IRC05:51
*** markvoelker has joined #openstack-ansible06:19
*** markvoelker has quit IRC06:26
openstackgerritJaveria Khan proposed stackforge/os-ansible-deployment-specs: Add modularize-neutron-plays specification  https://review.openstack.org/16918906:44
openstackgerritJaveria Khan proposed stackforge/os-ansible-deployment-specs: Add modularize-neutron-plays specification  https://review.openstack.org/16918906:50
*** bilal has joined #openstack-ansible06:52
*** sdake has quit IRC06:56
*** stevemar has quit IRC07:16
*** markvoelker has joined #openstack-ansible07:22
*** markvoelker has quit IRC07:27
*** mahito has joined #openstack-ansible07:27
*** vmtrooper has joined #openstack-ansible07:35
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: [WIP] Heat config changes for kilo  https://review.openstack.org/16794707:38
odyssey4memorning07:38
*** vmtrooper has quit IRC07:40
odyssey4meany thoughts on why we're effectively setting up the container bridge twice in https://review.openstack.org/169069 ?07:44
*** raminoid has left #openstack-ansible07:45
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: [WIP] Heat config changes for kilo  https://review.openstack.org/16794707:56
*** javeriak has quit IRC08:05
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Updated nova logic to correct issues with addon devices  https://review.openstack.org/16657808:21
*** markvoelker has joined #openstack-ansible08:23
*** markvoelker has quit IRC08:27
odyssey4methe python wheels aren't building today, thanks to https://bugs.launchpad.net/horizon/+bug/143854309:01
openstackLaunchpad bug 1438543 in OpenStack Dashboard (Horizon) "wrong package name 'XStatic-Angular-Irdragndrop' in horizon/requirements.txt" [Undecided,New]09:01
matttopenstack: bah09:11
matttodyssey4me: rather!09:12
mattti was wondering what the heck that failure was09:12
odyssey4methe repo happens to be in stackforge and no-one's done a review yet, so I think I'll do it quickly09:12
odyssey4mehttps://github.com/stackforge/xstatic-angular-lrdragndrop09:12
odyssey4meonce that's done, then horizon has to be fixed :/09:13
odyssey4memattt seeing as horizon needs a patch to fix it now anyway, perhaps you can get on that?09:14
git-harryodyssey4me: that project is a bit confusing09:22
git-harrythey use i and l interchangably09:23
git-harry*interchangeably09:23
odyssey4megit-harry yeah, it seems that someone did the pypi packaging configuration in stackforge... but the real stuff is elsewhere09:23
odyssey4methe packaging setup was broken09:23
*** markvoelker has joined #openstack-ansible09:23
odyssey4mesomehow it's been fixed, but not in stackforge09:23
*** vmtrooper has joined #openstack-ansible09:24
odyssey4meso pypi is serving the right stuff now, but horizon's trying to use the old naming09:24
git-harryodyssey4me: the readme on the project uses i which would suggest the pypi package is wrong09:26
odyssey4methe readme on the source project? https://github.com/lorenzofox3/lrDragNDrop09:27
odyssey4meit uses lowercase l09:27
matttodyssey4me: you want me to do what?09:28
matttsorry, i was looking at something else09:28
*** markvoelker has quit IRC09:28
git-harryOh I'm I looking at completely the wrong thing - https://github.com/stackforge/xstatic-angular-lrdragndrop09:28
*** vmtrooper has quit IRC09:28
odyssey4memattt my suggestion was to fix this patch to use lowercase (e)l and not uppercase (eye)I09:29
odyssey4mehttps://github.com/openstack/horizon/commit/55df9369b6461275248bd1440570f3ad6eabe49e#diff-b4ef698db8ca845e5845c4618278f29a09:29
matttwhy is this breaking now tho, no recent commit has gone into requirements.txt09:29
odyssey4mehmm, someone's already on it https://review.openstack.org/#/c/169132/09:30
git-harrymattt: look at the date of the package on pypi09:30
git-harryI suspect it's been updated and the old one removed09:30
odyssey4meyup, looks like it to me09:30
git-harryand they've uses the different spelling09:30
matttwho does that09:30
odyssey4mewell, the package was probably just renamed - if that's possible09:30
odyssey4meThai Tran does that, apparently09:31
matttso like09:33
matttgreat if that merges into master, but shame we're not using master :P09:34
odyssey4mehorizon patch in flight too: https://review.openstack.org/#/c/16913309:34
odyssey4mewe will have to do something to work around this, not sure what exactly09:34
mattthe has to rename it back09:36
matttotherwise splosion everywhere09:36
mattt(or she)09:36
odyssey4meor we need to move horizon to a sha in our test builds, and need to sticky-tape the requirements.txt somehow?09:37
matttprobably best to sit on it for a few mins and see what happens upstream09:38
matttbefore we get out the duct tape09:38
odyssey4meah, easy enough - we already pin global requirements to a sha... so we just update that, and update horizon's pin to a sha too09:41
odyssey4methis is what we get for working with pre-release software :)09:41
matttthis affects everything tho09:42
matttactually no it doesn't09:43
matttguess this was introduced in kilo09:43
git-harryodyssey4me: I don't think it's because we're using pre-release. It's because the package was removed from pypi09:44
svgGood 'morning' fellows of the stack09:44
svgThe reason that haproxy is not meant for production, is that because that setup is not HA by itself, or are there other reason?09:44
odyssey4mesvg we've put no effort into making the configuration 'production ready' or highly available as we recommend that physical load balancers are used instead and have only  tooled it up for development purposes09:46
odyssey4meif anyone else wishes to submit patches and use it in their reference architecture, that's fine and dandy09:46
svgok, so that's a yes, thx09:47
odyssey4mehmm, why are projects putting requirements into both their own requirements.txt and the global requirements.txt ?09:55
*** mahito has quit IRC10:04
openstackgerritHugh Saunders proposed stackforge/os-ansible-deployment: Update cinder services to kilo  https://review.openstack.org/16806610:05
*** markvoelker has joined #openstack-ansible10:24
*** markvoelker has quit IRC10:29
*** bilal has quit IRC10:41
*** vmtrooper has joined #openstack-ansible10:59
*** markvoelker has joined #openstack-ansible11:25
*** markvoelker has quit IRC11:29
openstackgerritMerged stackforge/os-ansible-deployment: Updated nova logic to correct issues with addon devices  https://review.openstack.org/16657811:34
*** galstrom_zzz is now known as galstrom11:46
*** britthouser has quit IRC11:54
*** vmtrooper has quit IRC11:55
*** britthouser has joined #openstack-ansible11:55
svgI'm at the 'name: Ensure Keystone Service' playing on 'hosts: glance_api[0]'; this task keeps running, seems the command hangs on connecting to the lb internal ip on 3535712:03
svgI can ping the lb internal ip, I can't make a tcp connection to it12:04
matttsvg: did you run the haproxy playbook?12:06
svgyes12:06
svgI can curl that endpoint fine from other hosts, also from the infra hosts where that container is located12:06
svgI planned to use f5, but when wiating for the network colleague to set that up, I tried haproxy for now; I did use the ip from that infra hosts where haproxy is running, not e separate dedicated one12:07
svgouch, another pebkac, bad network mask :(12:12
matttsvg: good12:12
matttbecause i didn't have a clue what it could be :)12:13
Sam-I-Ami was suspecting a network issue12:13
matttSam-I-Am: speak up next time!12:13
cloudnullMorning.12:13
Sam-I-Amevening12:13
matttmorning cloudnull12:14
cloudnullHow's it mattt12:14
matttcloudnull: purdy good thank you12:14
*** markvoelker has joined #openstack-ansible12:17
cloudnullWhat's new and exciting in openstack land?12:18
Sam-I-Amkilo12:20
Sam-I-Amof course12:20
cloudnullOdyssey4me did we resolve the python requirements issue already ?12:25
matttcloudnull: it didn't fail for me the last time i tried, so perhaps it was resolved upstream12:31
matttyeah looks like XStatic-Angular-IrDragNDrop is available again12:32
openstackgerritgit-harry proposed stackforge/os-ansible-deployment: Update cinder services to kilo  https://review.openstack.org/16806612:35
cloudnullMattt so we've not rebuilt our own mirror in some time. Once the min kilo stuff merges we can rebuild the tax mirror with some of the new packages which will mitigate this for some this.12:43
cloudnullWhich would've helped because we would have a built wheel in our mirror.12:45
matttcloudnull: yeah true!12:48
svgAnyone up for a swordfight?12:51
cloudnullHow's it svg12:52
svgI'm slacking off, it's deploying the openstack stuff now12:52
svgworking on nova atm12:52
cloudnullNice.12:53
matttwe should build on top of gentoo12:53
cloudnullIts "compiling"...12:53
mattt5 hours later ..........12:53
cloudnullCrap the kernel is missing some module ....12:54
mattthehe12:54
Sam-I-Amcloudnull: compile it all again12:55
Sam-I-Amgrab a beer12:55
mattta beer?  you're a slow drinker.12:55
svgcloudnull: that would become 'crap systemd is missing python'12:55
cloudnullOr just crap systemd...12:55
svgack12:55
svgah, next uop, neutron12:55
* svg goes for a walk12:56
matttsvg: it shouldn't take that long :)12:56
cloudnullSam-i-am loves neutron ;)12:56
Sam-I-Ammattt: i call it 'inexperienced'12:56
matttSam-I-Am: i may actually need your help w/ neutron today12:57
mattti have no idea what i'm doing wrong, but it aint working :)12:57
Sam-I-Amfirst guess - you're using it.12:57
mattthehe12:58
*** galstrom is now known as galstrom_zzz13:02
Sam-I-Amlulz @ nova gate still using sql_connection13:03
*** subscope has joined #openstack-ansible13:07
svgwoohoo, can login to horizon :)13:12
svgcolleagues that are testing mirantis/fuel and started at the same time as me, are still stuck with setting up pxe stuff for their hardware13:13
hughsaunderssvg: woot :)13:15
*** logan2 has quit IRC13:16
*** logan2 has joined #openstack-ansible13:19
cloudnullWinning all around ;)13:20
matttsvg: YOU WIN13:27
*** jaypipes has quit IRC13:29
*** Bjoern__ has joined #openstack-ansible13:32
openstackgerritMerged stackforge/os-ansible-deployment: Add support for passing api version to glance module  https://review.openstack.org/16795913:41
*** jaypipes has joined #openstack-ansible13:42
matttSam-I-Am: ok i tracked down my problem (as in, what is happening), still have no idea what's causing it13:44
matttSam-I-Am: when i boot an instance w/ a private IP, the instance doesn't get an IP via dhcp13:45
matttSam-I-Am: looks like entries aren't getting added to bridge fdb13:45
matttSam-I-Am: when i manually add and reboot the instance it comes up w/ an IP13:45
Sam-I-Ammanually add what, an ip?13:46
Sam-I-Amor manually add the entries to the fdb13:46
matttSam-I-Am: yes manually add entries to fdb13:46
matttSam-I-Am: on both the neutron agents controller and hypervisor13:47
Sam-I-Amhmm13:47
Sam-I-Amjuno?13:47
matttSam-I-Am: this is kilo13:48
Sam-I-Amdoes this have anything to do with what Apsu is working on with things saying they happened but not really happening?13:48
matttSam-I-Am: the same AIO build on juno "just works"13:48
matttSam-I-Am: it's possible, but i've turned on debugging and i don't see neutron adding these entries13:48
Sam-I-Amthats odd13:49
mattt(i do see it trying to remove them if you tear down the network tho)13:49
Sam-I-Amdoes this happen consistently, or only in tempest?13:49
matttSam-I-Am: consistently13:51
mattt(for me at least)13:51
mattti'm spinning up instances manually here13:51
*** logan2 has quit IRC13:53
*** logan2 has joined #openstack-ansible13:56
*** sigmavirus24_awa is now known as sigmavirus2413:59
Sam-I-Ammattt: i dont have a working kilo install to play with yet14:00
matttSam-I-Am: ok think i found it14:04
Sam-I-Ammattt: what?14:05
matttneutron14:05
matttflipped to nova-network and solved.14:05
Sam-I-Amoh, right. that works.14:06
matttnah, i think we're dropping a bad config in our kilo minor patch14:06
matttjust validating now14:06
Sam-I-Ammattt: if its always the case, then probably.14:06
Sam-I-Amdid much change for kilo?14:07
*** alextricity has joined #openstack-ansible14:09
*** Mudpuppy has joined #openstack-ansible14:20
*** Bjoern__ is now known as BjoernT14:21
*** sdake has joined #openstack-ansible14:29
*** galstrom_zzz is now known as galstrom14:40
sigmavirus24odyssey4me: I'm confused, do you want me to remove the reference to the keystone-kilofication blueprint?14:42
odyssey4mesigmavirus24 I would guess that the appropriate action is to mark the blueprint in launchpad as superceded, and to reference the blueprint in the commit message... although the approach you took with referencing both was the least offensive. :p14:44
*** hj-hp has joined #openstack-ansible14:51
*** jaypipes has quit IRC14:53
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Updated for 9.0.7 tag  https://review.openstack.org/16935514:59
rackertomo/15:01
sigmavirus24\o15:02
openstackgerritJesse Pretorius proposed stackforge/os-ansible-deployment: Update to readme to reference doc source more generally  https://review.openstack.org/16935815:03
d34dh0r53meetings?15:05
palendaed34dh0r53: Off by an hour15:06
palendaed34dh0r53: It's not 1600 UTC15:06
sigmavirus24hm15:06
sigmavirus24oh damnit15:06
Sam-I-Amthe calendar invite has been b3rnard0'd15:07
b3rnard0hey!15:07
b3rnard0let me check it15:08
matttmy calendar said 160015:08
matttit is now 160015:08
BjoernTaccording outlook it is now 1600 utc15:08
BjoernTbut google says 150015:08
matttbut that's not true :)15:08
matttit is 1500 UTC15:08
BjoernTi trust google15:09
matttsaid no one ever15:09
palendaeBjoernT, mattt: I bet you're seeing the invite that was made based on CST15:09
b3rnard0well something happened as it was right last week15:09
matttb3rnard0: we flipped to summer time on sunday15:10
sigmavirus24palendae: it /is/ based on UTC15:10
palendaeAh15:10
BjoernTFun fact is I re did my invite in the UTC time zone and outlook is wrong15:10
sigmavirus24BjoernT: yep15:10
b3rnard0i see sigmavirus24 thursday invite at 10am CST15:10
palendaelaffo15:10
b3rnard0oh outlook15:10
Sam-I-Amoutlook does gmt with daylight savings15:11
BjoernTMicrosoft and Apple usually have time zone issues, lol15:11
Sam-I-Amits special15:11
cloudnullhttps://review.openstack.org/#/c/169355/ <- icehouse 9.0.7 review, Cores please give it a look when you can.15:11
palendae" Coordinated Universal Time (UTC) " Wouldn't that be CUT? Everything about this is wrong!15:12
palendaemattt: So your clocks are at 1600?15:12
sigmavirus24palendae: do you know what CERN stands for?15:13
palendaeSomething goofy in swiss?15:13
matttpalendae: yeah we're currently GMT+115:13
sigmavirus24CERN = European Organization for Nuclear Research15:13
palendae derived from the name "Conseil Européen pour la Recherche Nucléaire"15:14
openstackgerritMatt Thompson proposed stackforge/os-ansible-deployment: [WIP] Heat config changes for kilo  https://review.openstack.org/16794715:14
sigmavirus24palendae: "SI" is  International System of Units15:14
palendaeGuess they just didn't want to update the logo15:14
Sam-I-Amsigmavirus24: "si" means "yes" to b3rnard015:14
sigmavirus24palendae: not everything is made or altered for arrogant self-important americans ;)15:15
palendaesigmavirus24: I meant CERN15:15
palendaeThey had a working acronym in French15:15
palendaeAnd left it15:15
b3rnard0Sam-I-Am: que?15:15
palendaeEven though they change the english15:15
Sam-I-Amb3rnard0: what am i queuing?15:16
sigmavirus24b3rnard0: isn't it qué?15:16
Sam-I-Amb3rnard0: like rabbitmq?15:16
b3rnard0si15:17
sigmavirus24b3rnard0: isn't it sí?15:17
b3rnard0wat?15:17
Sam-I-AmLe Système International d'Unités ?15:18
*** KLevenstein has joined #openstack-ansible15:19
*** KLevenstein is now known as KLev-afk15:20
odyssey4meI'm confused. When is the meeting?15:20
palendaeodyssey4me: In 40 minutes15:20
odyssey4meI'm at GMT+2 now.15:20
odyssey4meRight, so the calendar invites for Rackers are broken. b3rnard0 make the fix when you learn how to outlook :p15:21
d34dh0r53b3rnard0: what were you saying about logging?15:26
sigmavirus24d34dh0r53: there was a log-rotate LP bug reported last night by paul15:26
sigmavirus24d34dh0r53: https://bugs.launchpad.net/openstack-ansible/+bug/143841715:27
openstackLaunchpad bug 1438417 in openstack-ansible "No logrotate config in containers" [Undecided,New]15:27
sigmavirus24I'm not sure if that's what b3rnard0 was talking about15:27
sigmavirus24But you reminded me that I saw it15:27
odyssey4mesigmavirus24 d34dh0r53 good call on that bug, that's pretty nasty15:28
odyssey4meassuming it's true ;)15:28
d34dh0r53b3rnard0 is suspiciously quiet15:28
d34dh0r53odyssey4me: I think it is in juno/icehouse15:28
Sam-I-Amd34dh0r53: he's busy piecing together the outhouse invite15:29
Sam-I-Ammattt: neutron stuffs?15:29
*** stevemar has joined #openstack-ansible15:29
matttSam-I-Am: what's that?15:33
Sam-I-Amthe problem you were having15:33
Sam-I-Amthis is an aio, right?15:33
matttSam-I-Am: i've not been successful getting networking going on AIO or multi node build (all on cloud servers)15:34
MudpuppyNeed duct tape around my head today heheh15:34
Sam-I-Ammattt: whats your ml2 conf look like?15:35
stevelleodyssey4me: sigmavirus24 pretty sure we put log rotation in master with rework to rsyslog.  needed in juno though15:36
stevelled34dh0r53: ^15:36
sigmavirus24stevelle: that's what d34dh0r53 said ;)15:36
stevelleall agreement15:36
matttSam-I-Am: http://paste.openstack.org/show/197714/15:36
sigmavirus24<d34dh0r53> odyssey4me: I think it is in juno/icehouse [10:29:04|31-03-2015]15:36
*** daneyon_ has joined #openstack-ansible15:36
Sam-I-Ammattt: vxlan tenant network?15:37
matttSam-I-Am: yepper15:39
*** daneyon has quit IRC15:39
Sam-I-Amhmm, file looks ok15:40
Sam-I-Ammattt: nothing in any of the debug? neutron just doesnt Do The Thing?15:44
sigmavirus24Sam-I-Am: mattt related to https://bugs.launchpad.net/openstack-ansible/+bug/1436916 perhaps?15:45
openstackLaunchpad bug 1436916 in openstack-ansible "num_sync_threads set to 0 when api_workers set to 0" [Undecided,New]15:45
Apsumattt: In the agents container, what's the output of "ip -o l | grep tap | grep -v master"?15:45
matttApsu: http://paste.openstack.org/show/197718/15:48
matttApsu: not sure if you saw what i wrote earlier15:49
matttApsu: so i compared a kilo install to juno, and i noticed when i booted an instance on kilo i didn't have the same bridge fdb entries15:49
matttApsu: once i manually created them and rebooted the instance it was able to get an ip from dhcp15:49
matttsigmavirus24: hehe nah15:49
matttsigmavirus24: got burned by that one already, 100% sure it's not that15:49
Apsumattt: I saw, yeah. I find that odd, but the fdb entries are an L2pop thing, and aren't explicitly required for operation. What is required, however, is that the taps are in the bridges15:50
sigmavirus24mattt: just making sure =P15:50
ApsuAnd that tap you just pasted isn't in a bridge :)15:50
matttApsu: this is the issue you were wrestling before right?15:50
ApsuYep15:51
ApsuI wrote a fuzzing script to attempt to figure out what's going on, and I discovered some fun facts15:51
palendaeYou discovered a den of lies15:51
Apsu^15:52
ApsuApparently when you tell the kernel "do this network thing", and it returns from the syscall15:52
*** jwagner_away is now known as jwagner15:53
ApsuIt doesn't immediately do the thing you told it to do15:55
ApsuSo... creating an interface then immediately checking for it can fail if you do enough of them fast enough.15:55
matttApsu: wait, regarding my env15:55
ApsuLikewise bringing it up/down, adding/removing from bridge15:55
matttApsu: ip -o l | grep tap | grep master |wc -l => 415:55
matttApsu: so i do have some tap devices in bridges15:56
ApsuYes.15:56
ApsuMost of them go in, sometimes one or two go in then back out.15:56
ApsuThat specific scenario is what I'm trying to nail down now15:56
Sam-I-AmApsu: is this issue only with kilo?15:56
palendaeSam-I-Am: no15:57
matttApsu: i don't even know what that problematic tap device is tho15:57
palendaeSam-I-Am: It's a kernel-level thing15:57
matttApsu: the ones i'm concerned with are all in bridges15:57
ApsuSam-I-Am: No.15:57
ApsuUnrelated to neutron.15:57
Sam-I-Amwell, yeah... i'm just wondering if something changed in neutron code that makes it more evident15:57
Apsumattt: My guess is that's not true. Do you have debug on for your neutron LB agent?15:58
matttApsu: it must be, because if i manually add the fdb entries network flows15:58
matttif one of hte necessary taps weren't in the bridge surely that wouldn't happen15:58
palendaeSam-I-Am: What first made it apparent to us was enabling the neutron tempest tests on Juno15:58
Sam-I-Amahh ok15:58
*** galstrom is now known as galstrom_zzz15:58
Apsumattt: hrm. That just doesn't make sense to me.15:58
matttApsu: ok let me try to document this quickly (need to leave office)15:59
Apsumattt: No problem. Not that I don't believe what you're seeing, I'm just trying to understand how it could make sense.15:59
Sam-I-Amthis16:00
cloudnullbug triage meetings: cloudnull, mattt, andymccr, d34dh0r53, hughsaunders, b3rnard0, palendae, Sam-I-Am, odyssey4me, serverascode, rromans, mancdaz, dolphm, _shaps_, BjoernT, claco, echiu, dstanek16:00
ApsuThe FDB (Forwarding DataBase) is part of every linux bridge. It's filled in automatically with MAC addresses during the normal course of switch learning operation16:00
dstaneko/16:00
b3rnard0hello. here's the link to the bug notes: https://etherpad.openstack.org/p/openstack_ansible_bug_triage.2015-03-31-16.0016:00
hughsaunderslo16:00
ApsuThe ML2 L2pop feature tries to add MAC addresses to the FDB that it already knows about, since Neutron built the network topology16:00
ApsuThat way it saves on broadcast/flood behavior16:01
ApsuBut that doesn't mean it Requires preloading the FDB. It should always work with/without it.16:01
Sam-I-Am"tries"16:01
d34dh0r53\0/16:01
*** javeriak has joined #openstack-ansible16:02
cloudnullhelo .16:02
cloudnullfirst up: https://bugs.launchpad.net/openstack-ansible/+bug/143849816:02
openstackLaunchpad bug 1438498 in openstack-ansible "Memcache connection limit too low" [Undecided,New]16:02
*** tbyrom138 has joined #openstack-ansible16:03
cloudnullits set to 1024. do we want to parameterize that?16:03
cloudnullseems like an easy fix in master/juno but is it important to us?16:03
odyssey4meis that hard set in our defaults, in a template or in a file (like an upstart file) ?16:04
d34dh0r53I'm a big fan of parameterize all of the things16:05
*** galstrom_zzz is now known as galstrom16:05
d34dh0r53less chance for snowflakes that way16:06
odyssey4med34dh0r53 rumour has it that snowflakes are trendy :p16:06
cloudnullodyssey4me its an unset variable.16:06
d34dh0r53odyssey4me: :) what all the cool kids are doing?16:06
cloudnull-c #N16:06
cloudnull-c <num>      max simultaneous connections (default: 1024)16:06
cloudnullthe template https://github.com/stackforge/os-ansible-deployment/blob/master/playbooks/roles/memcached_server/templates/memcached.conf16:07
odyssey4meah, so something we haven't needed to set before now - in that case we may as well parameterise and add as a best practise16:07
cloudnullwould need to be changed.16:07
dstanekdo you also need to up the ulimit if you go higher than the 1024?16:08
ApsuProbabl16:09
Apsuy16:09
odyssey4megood point - sounds like some triage is required16:09
cloudnulldstanek i don't believe so. nothing in man page indicates that you would have to.16:10
dstanekcloudnull: i thought the default was 1024 fds16:10
Apsudstanek: It is.16:10
Apsuhttp://stackoverflow.com/questions/2054212/is-ulimit-needed-launching-memcached-with-c minor verification16:11
ApsuBut it does make sense.16:11
sigmavirus24lol memcached16:12
cloudnullso we'd need to update the limits.conf where memcached is installed such that the limit is set to the same value of the user defined connections when greater then 1024.16:13
d34dh0r53that's how I read it16:13
Apsuyar16:13
odyssey4mesounds like a worthy bug note, with a ref to the url from Apsu16:14
cloudnullmoving on16:15
cloudnullfor juno/icehouse: https://bugs.launchpad.net/openstack-ansible/+bug/143841716:15
openstackLaunchpad bug 1438417 in openstack-ansible "No logrotate config in containers" [Undecided,New]16:15
dstanekcloudnull: yep, exactly. although making it a little higher may not sure - i don't know how many fds it uses for other things although i suspect not many16:15
* cloudnull dstanek thats a good point. if we set it high than 1024 we may want to add some percentage over the defined value. 16:17
cloudnullandymccr, odyssey4me, d34dh0r53: https://bugs.launchpad.net/openstack-ansible/+bug/1438417 <- what say you?16:17
openstackLaunchpad bug 1438417 in openstack-ansible "No logrotate config in containers" [Undecided,New]16:17
d34dh0r53dstanek: cloudnull we could add 1024 to it so that the OS still has it's old default, up to a point of course16:18
d34dh0r53cloudnull: andymccr odyssey4me confirmed, high16:18
andymccrsounds high to me :D16:18
odyssey4mecloudnull target at icehouse/juno with invalid at master - priority sounds high (as per the others)16:19
cloudnullone.16:19
cloudnull*done16:19
cloudnullwhat will it take to get that in?16:19
odyssey4mealthough icehouse is in maintenance - not sure if it'll every get a new tag, or are we still on the path to the last tag?16:20
palendaeodyssey4me: A review was cut for 9.0.7 today16:20
cloudnullits on the path to a last tag, until we make another one :)16:20
*** daneyon has joined #openstack-ansible16:20
odyssey4meI suppose we can merge a fix and do a new tag if someone decides it's important enough16:21
d34dh0r53perhaps a known issues for icehouse?16:21
odyssey4mework involved is probably not too bad16:21
d34dh0r53fixed in docs :)16:21
odyssey4meif this is done in master, it could be back ported or written in - I would expect a juno backport to be relatively simple16:21
cloudnullok , so being that this is a hot issue, who wants it?16:22
odyssey4meicehouse, well, that's often complicated - so yeah I agree with d34dh0r53  that perhaps a docs entry is best16:22
d34dh0r53I think the Juno patch will need to be written from scratch as the logging arch changed somewhat.  Porting from Juno to Icehouse *shouldn't* be that hard, but I don't think this is worthy of a dot release for icehouse by itself16:23
*** daneyon_ has quit IRC16:24
odyssey4med34dh0r53 agreed, sounds like you're volunteering?16:25
*** tbyrom138 has quit IRC16:26
* d34dh0r53 hides behind something16:26
d34dh0r53yeah, I can take it16:27
BjoernTand don't forget all the nice logs like neutron-agent* lol, those are filling up pretty fast16:27
cloudnullso d34dh0r53 voluntold.16:27
cloudnullnext: https://bugs.launchpad.net/openstack-ansible/+bug/143811816:28
openstackLaunchpad bug 1438118 in openstack-ansible "some v10 Juno playbooks containing a wrong host pattern" [Undecided,New]16:28
odyssey4menetron logs are awesome DDoS tools16:28
BjoernTlol, /dev/urandom is too16:29
cloudnullthis is a host pattern problem in juno.16:29
cloudnullwe should fix that for 10.1.316:29
cloudnullmo16:29
cloudnull*imo16:29
Apsuodyssey4me: debug=True, enjoy your iowait!16:30
odyssey4mewhoops cloudnull yeah that's a bad lysdexic typos16:30
cloudnullit effects icehouse too16:30
* odyssey4me nods16:31
Sam-I-Amwhoops16:31
BjoernTyeah it's an openstack problem in general. No debug on, does not give you any detail to fix issues and debug on is too much...16:31
odyssey4mecloudnull I would guess that this doesn't have too much effect functionally, so this is a low/medium priority.16:33
*** galstrom is now known as galstrom_zzz16:34
odyssey4meI would also venture to say that an icehouse fix is not essential.16:34
cloudnulli agree low16:34
cloudnullbut it is something that we should resolve.16:34
odyssey4methe fix is fairly trivial16:34
cloudnullit is16:34
odyssey4meany volunteers16:34
cloudnulllow hanging fruit here folks :)16:35
odyssey4mesvg perhaps you'd like to submit a fix seeing as you found it?16:35
odyssey4meotherwise, if no volunteers then I'm happy to put one together16:36
palendaeI could do it, too16:36
odyssey4mesold, to the palendae :)16:36
cloudnullpalendae in the house !16:37
Sam-I-Ampalendae: earn your curs^H^H^Hore16:37
cloudnullnext : https://bugs.launchpad.net/openstack-ansible/+bug/143797816:37
openstackLaunchpad bug 1437978 in openstack-ansible "RabbitMQ restarts without condition in juno/icehouse" [Undecided,New]16:37
cloudnullessentially anytime you run the rabbitmq plays, it restarts in icehouse/juno .16:37
odyssey4meyeah, that sucks16:38
cloudnullwe can potentially backport the logic from master.16:38
odyssey4mefor production that can create a mess16:38
odyssey4meI'd vote for medium priority.16:39
odyssey4meMaybe low.16:39
cloudnullyup triaged medium16:39
cloudnullimo its a medium, its not idempotent and could cause production issues.16:39
openstackgerritMiguel Alejandro Cantu proposed stackforge/os-ansible-deployment-specs: Add spec for BP implement-ceilometer  https://review.openstack.org/16941716:40
Apsuquiet openstackgerrit, we're busy16:40
cloudnullnext: https://bugs.launchpad.net/openstack-ansible/+bug/143699916:40
openstackLaunchpad bug 1436999 in openstack-ansible "LVM/DM/UDEV out of sync inside cinder-volumes container" [Undecided,New]16:40
cloudnullBjoernT around ?16:40
Apsucloudnull: Saw that one, and I agree with BjoernT. In fact, I think it's surprising we haven't had more issues with udev being off in containers in fact lol16:42
BjoernTyes16:42
* cloudnull hands mic to BjoernT 16:42
*** KLev-afk is now known as KLevenstien16:43
*** KLevenstien is now known as KLevenstein16:43
BjoernTso I will update the issue. I did some testing and was not able to reproduce it, in either configuration16:43
cloudnullso we'll need to do more work to confirm that issue.16:44
BjoernTI'm  pretty sure that a static /dev, like we have right now is causing issues.  Since the /dev/mapper tree is persistent across reboots16:44
BjoernT"/dev" is not managed by udev inside the container unless you set a parameter16:44
BjoernTobtain_device_list_from_udev rendered lvm useless16:45
BjoernTso I't a mystery how this can happen but we have a big issue here imho16:45
cloudnullso can we get some folks to go dive into this and track down what the root cause is ?16:46
ApsuWhat was the original issue causing us to disable udev? I mean, did we see an actual critical issue occurring, or just were trying to avoid something we'd heard about?16:46
ApsuSorry, that's out of scope. I'll followup elsewhere16:46
BjoernTcpu load cause by udevd on each container16:46
BjoernTespecially on infra nodes16:46
cloudnullApsu triggering udev in the container causes it to trigger on the host.16:46
cloudnullx32+ containers makes the load hard to manage.16:47
BjoernTso to make it short, some dev help would be appreciated to reproduce it16:47
*** bilal has joined #openstack-ansible16:47
cloudnullalso with all of udev enabled lvm becomes unavailable within the container.16:47
*** jaypipes has joined #openstack-ansible16:48
odyssey4meSounds to me like Apsu and BjoernT could perhaps collaborate on this - although it does seem like an edge case.16:48
cloudnullyea Apsu BjoernT can you guys sync up and bang on it a bit ?16:49
odyssey4mePure conjecture here, so correct me with pleasure.16:49
Apsucloudnull: According to Ubuntu devs, their apparmor policy prevents udev trigger cascades, and they run udev in all their lxc containers. So... yeah. I'll follow up with BjoernT and look at it16:49
BjoernTnice16:49
cloudnullnext: https://bugs.launchpad.net/openstack-ansible/+bug/143691616:50
openstackLaunchpad bug 1436916 in openstack-ansible "num_sync_threads set to 0 when api_workers set to 0" [Undecided,New]16:50
cloudnullmattt ^16:50
odyssey4mepatch in already: https://review.openstack.org/16828716:51
odyssey4methe whole api threads = 1 if it's 0 isunnecessary as it's already done at the top of that template16:53
cloudnullsounds good.16:54
cloudnullso last one: https://bugs.launchpad.net/openstack-ansible/+bug/143664716:55
openstackLaunchpad bug 1436647 in openstack-ansible "Make chunk size configurable for swift-backed glance" [Undecided,New]16:55
andymccrassign that to me16:57
andymccrits super quick16:57
andymccrprobably medium prio16:57
odyssey4meodd, why're we differing from the default swift which AFAIK is 5G, just like cloudfiles?16:58
andymccrodyssey4me: its a glance thing16:58
cloudnullandymccr done.16:58
cloudnullso we're done here.16:58
andymccrboom!16:58
cloudnullthanks everyone.16:58
odyssey4meah, glance, how do I love thee... let me count the ways...16:58
Sam-I-Amwoohoo16:58
d34dh0r53notes -> https://etherpad.openstack.org/p/openstack_ansible_bug_triage.2015-03-31-16.0016:58
andymccrodyssey4me: dont count the ways you will not be done before 2020!16:58
cloudnulljust as a side note, we have a couple of specs that have been submitted, if we can get some reviews on them sometime soonish it would be great.16:59
d34dh0r53minor grievance time?16:59
d34dh0r53Based on this: https://wiki.openstack.org/wiki/Bugs I don't believe that we're using the Triaged tag appropriately17:00
d34dh0r53s/tag/status/17:00
sigmavirus24huh17:00
openstackgerritMiguel Grinberg proposed stackforge/os-ansible-deployment: WIP Horizon config changes for kilo  https://review.openstack.org/16746017:01
odyssey4med34dh0r53 that's possible, but can you be more specific?17:02
d34dh0r53We don't have specific analysis or fixes for the problem in most of our Triaged bugs17:03
sigmavirus24odyssey4me: we're using triaged to mean that "The Bug team has seen this, confirmed it, and given it a priority"17:03
odyssey4meperhaps an item for thu's agenda should be whether we're adopting that as a set of definitions17:03
sigmavirus24odyssey4me: that classification says it should be used if there's some kind of fix ready for it17:03
odyssey4methen we can happily allow bugs to be changed according to the appropriate status17:04
* sigmavirus24 likes our definition better personally =P17:04
odyssey4meI see there's been a similar debate on openstack-dev somewhere17:04
d34dh0r53yeah, I agree this should be discussed in the Thu meeting17:04
sigmavirus24d34dh0r53: add it to the agenda?17:04
odyssey4mesigmavirus24 I prefer confirmed for that status, but even then it's a stretch17:05
odyssey4memaybe incomplete should be set if it needs investigation17:05
sigmavirus24odyssey4me: except that literally anyone can mark a bug as "confirmed"17:05
odyssey4mewhich many of our reported bugs do need17:05
d34dh0r53sigmavirus24: do you have the link for the meeting wiki?17:05
sigmavirus24d34dh0r53: it's in the topic?17:06
odyssey4med34dh0r53 https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting17:06
d34dh0r53facepalm17:06
odyssey4mehahaha17:06
svgodyssey4me: sure, that's a no brainer, and it'll let me get acquainted with the contribution process17:09
d34dh0r53:) AFK Lunch17:09
svgIf I understood correctltly, I should patch it in master, and tag it for juno?17:09
odyssey4mesvg that looks like it's an issue for juno/icehouse only, so patch to the juno branch and cherry-pick ti icehouse... palendae can advise as he's volunteered, but it'd be great if you could take it on as we'd welcome more contributors17:11
odyssey4meif you do find similar patterns in master, then patch for them too17:12
palendaesvg, odyssey4me I haven't started and am going to lunch shortly, so feel free :)17:12
svgAh ok, I see the new info on the bug report.17:12
odyssey4mesvg, feel free to reassign to yourself - many people in this channel can help you get through the hurdles of your first submission :)17:13
svgI'll try to get my act together this evening, as I didn't do anything on opentack contributions yet.17:13
svgwill do, thx17:13
svgnice, welcoming community btw :_)17:13
sigmavirus24svg: I'm willing to help with OpenStack/OSS contributions in general so feel free to ping me when you have time and we can figure something out17:14
* sigmavirus24 regularly helps people get their first contributions into OSS projects17:14
svgbtw, anybody here that can get me in touch with sales/support for Europe? Part of the evaluation I'm doing, is getting fallback support, as we have as good as no openstack knowledge inhouse17:14
svg$boss sounded like 'mirantis will probably give better support'17:15
svg(he contacted rackspace via a web form, but didn't get any reply yet)17:15
Sam-I-Amsvg: trying to figure it out17:18
svgthx Sam-I-Am17:19
odyssey4meheh svg us devs don't get involved in the sales process much :p - we'll need to find the right stuff to point you at17:19
svgI hope for you you don't :)17:20
Sam-I-Amhaha17:20
svgbut anything that gets us somewhere fater than a 'webform'17:20
svgfaster17:20
odyssey4meI am surprised that http://www.rackspace.co.uk/cloud/private (number at the bottom, live web chat option at the top) hasn't got $boss far?17:21
javeriakhey guys, i got reviews back for my spec adding modular neutron plays https://review.openstack.org/#/c/169189/2 , so I've assigned juno as the series goal to the bp17:23
svgodyssey4me: he emailed17:23
javeriakand from the latest comment i take it, this can still go in for 10.x ?17:25
javeriakand I can file it again for master17:25
svgodyssey4me: I'm doing a webchat now, hopefully I can get him th einfo he wants, thx17:27
odyssey4mejaveriak the general idea is usually to focus initial attempts at new ways of doing things in master, then to look at back-porting17:28
odyssey4mehowever, it's not exclusive and if you're prepared to forward-port then it may be entertained17:29
javeriakyep my current focus is supporting these changes for 10.x, and I would ofcourse also like to add them to master in parallel, would this require opening a seperate bp to track the master effort?17:35
*** sdake_ has joined #openstack-ansible17:37
odyssey4mejaveriak to be honest this is new territory, perhaps cloudnull can advise or perhaps it's best discussed at the next community meeting17:39
odyssey4mefor now I'd suggest that the blueprint cover the intention clearly17:39
stevelleseems to me a single blueprint should be sufficient unless it turns out that the implementation is fundamentally different and requires a different strategy17:41
*** sdake has quit IRC17:41
odyssey4mestevelle I would agree personally.17:42
*** sdake has joined #openstack-ansible17:48
*** sdake_ has quit IRC17:52
*** javeriak has quit IRC18:06
*** bilal has quit IRC18:11
sigmavirus24odyssey4me: stevelle blueprints are almost always exclusively targetted towards master18:14
sigmavirus24stable/maintenance branches usually don't receive features/additions18:14
cloudnullsigmavirus24 i'd agree however we removed stable from the name of the branches because we were attempting to provide a mechanism to allow features to be added into a branch that may have already been released.18:18
sigmavirus24blueprints are also designed to only target one series of development18:19
sigmavirus24We can use it to track two, but it'll probably confuse people later down the road if we do that18:20
cloudnullie in future majors we'd want to provide "x" post the initial release. the issue is that 10/9.x are rax technical debt so as a rax product do we want to have it included and when?18:20
sigmavirus24(to be clear, I'm not arguing to not back/forward port something because of LaunchPad, just that if we want to track the work in a less confusing way, we should probably not use one)18:21
palendaecloudnull: For javeriak's first BP, the modular networking support, I think would be useful. However, my personal opinion is that it should be current forward18:21
palendaeThough it appears he has use for it in 10.18:21
palendaex18:22
sigmavirus24Also note that while we all acknowledge 9.x and 10.x as technical debt, no one is aiming to refactor them so that they aren't18:23
cloudnullas i read the bp i think he is developing/has developed the functionality for "10.x" so we might want to see if we can team up with him and get the functionality into master.18:23
cloudnullsigmavirus24 right no refactoring the stable branches.18:25
cloudnullwe've already been down that road =)18:25
cloudnullthere be dragons.18:25
sigmavirus24Right18:25
* palendae aims to refactor18:26
sigmavirus24palendae: dont' make me shoot you with a blue shell18:26
palendaeYou mean a gold shell?18:27
BjoernTi take that too18:27
*** javeriak has joined #openstack-ansible18:44
palendaeIf some others could look at https://review.openstack.org/#/c/169069/ and comment/review, I'd appreciate it18:45
Sam-I-Ampalendae: ha, you almost got me.18:49
palendaeSam-I-Am: ?18:49
*** prometheanfire has joined #openstack-ansible18:50
Sam-I-Ampalendae: conflict, sir.18:51
prometheanfireis there a list of software that's needed by os-ansible?  lxc and the like? (not the stuff from requirements.txt)18:51
palendaeSam-I-Am: You're a conflict18:51
prometheanfiretrying to see how to package this (if that's even applicable)18:51
Sam-I-Amprometheanfire: the docs contain a list of packages needed on the hosts18:51
Sam-I-Amthen the ansible stuff grabs packages for each service18:51
Sam-I-Ampalendae: thanks for the compliment18:52
prometheanfireah, guess it assumes a specific distro then18:52
palendaeprometheanfire: There's http://git.openstack.org/cgit/stackforge/os-ansible-deployment/tree/scripts/bootstrap-aio.sh#n8718:52
Sam-I-Amit runs on ubuntu18:52
prometheanfireright, forgot about that18:52
Sam-I-Amyou could probably make it work on another distro18:52
palendaehttp://docs.rackspace.com/rpc/api/v9/bk-rpc-installation/content/sec_overview_requirements.html18:52
prometheanfireya, I'm sure I can18:53
prometheanfireyou need to define the container image location I'm guessing18:53
prometheanfireor is that run from the host?18:53
*** stevemar has quit IRC18:54
Sam-I-Amprometheanfire: containers are built on the fly18:54
prometheanfireusing what as the source?18:55
prometheanfirethat's my question?18:55
prometheanfirecan I run this on gentoo? :P18:55
palendaehttp://git.openstack.org/cgit/stackforge/os-ansible-deployment/tree/playbooks/roles/lxc_container_create/tasks/container_create.yml#n5718:55
Sam-I-Amopenstack and python deps are python rolled into wheels packages18:56
Sam-I-Amthe system deps are dpkg18:56
palendaeYou can run it, I don't know that it'll succeed :)18:56
* prometheanfire is considering using this as the 'official' deployment way for gentoo18:56
palendaeBecause of what he said18:56
palendaeLots of references to deb and dpkg hard coded18:56
prometheanfireis dpkg run in the container, that's my question18:56
Sam-I-Ammaybe there's a package-ish module for ansible18:56
prometheanfireif so, no problem18:56
Sam-I-Amapt is, yes18:56
Sam-I-Amssh into container, do things.18:57
prometheanfireso the host only need lxc things18:57
palendaeprometheanfire: Yes, see http://git.openstack.org/cgit/stackforge/os-ansible-deployment/tree/playbooks/roles/lxc_container_create/tasks/container_create.yml#n6418:57
palendaeThough that actually just sets up apt sources18:57
sigmavirus24prometheanfire: the lxc template is ubuntu which I'm not sure gentoo will like18:58
prometheanfireif it's in the container that's fine18:58
prometheanfirelxc template can be whatever it wants though, distro should not mater18:58
palendaeYeah18:58
palendaeI see what you're getting at18:58
palendaeGentoo hosts with ubuntu containers?18:58
prometheanfirebasically18:58
sigmavirus24Gentoo deployers will love that /s18:59
prometheanfireI can work on submitting review to abstract other things :P18:59
* prometheanfire waves at sigmavirus24 18:59
sigmavirus24Well as long as you don't try to use the downstream packages. Those are almost always broken18:59
palendaehttp://git.openstack.org/cgit/stackforge/os-ansible-deployment/tree/playbooks/roles/openstack_hosts/tasks/openstack_host_packages.yml runs apt on a loop18:59
sigmavirus24=P18:59
prometheanfiremy packages are good :P18:59
sigmavirus24That's what they all say19:00
prometheanfirethen again, I basically just package straight from pip19:00
prometheanfirethe deps stay the same, etc19:00
sigmavirus24prometheanfire: I'm mostly ribbing you19:00
prometheanfireI know19:00
* sigmavirus24 hasn't tried out teh gentoo packages19:00
prometheanfireI want to stop packaging openstack, more or less :P19:00
sigmavirus24On the bright side, I never see bug reports from users of them19:00
palendaeSo setup-hosts.yml calls openstack-hosts-setup.yml, which calls the openstack_hosts role, with has a call to apt19:00
sigmavirus24prometheanfire: that's a healthy life decision19:00
palendaeThat's the extent of what I see, though I haven't actually grepped19:01
* sigmavirus24 is pretty sure the debian maintainer is going to not live very long at this rate19:01
prometheanfireI'll still package the clients, but the way to run openstack servers on gentoo would be containers19:01
prometheanfireanyway, time for a meeting19:01
prometheanfirepalendae: I'll have to check if ansible has that package resource, need to get more familiar with it anyway19:02
prometheanfirebrb in an hour :(19:02
*** stevemar has joined #openstack-ansible19:04
*** stevemar has quit IRC19:08
*** stevemar has joined #openstack-ansible19:08
*** hj-hp has quit IRC19:24
*** hj-hp has joined #openstack-ansible19:24
*** sdake_ has joined #openstack-ansible19:31
*** sdake__ has joined #openstack-ansible19:35
*** sdake has quit IRC19:35
d34dh0r53cloudnull: we good to merge 9.0.7?19:37
*** sdake_ has quit IRC19:38
cloudnullmake it go19:39
cloudnullif there are at least 2 +2's19:39
palendaeplussed a 219:39
d34dh0r53gone, no refunds19:40
*** Mudpuppy_ has joined #openstack-ansible19:47
*** galstrom_zzz is now known as galstrom19:47
*** Mudpuppy has quit IRC19:50
*** hj-hp has quit IRC19:50
openstackgerritJaveria Khan proposed stackforge/os-ansible-deployment-specs: Add modularize-neutron-plays specification  https://review.openstack.org/16918919:53
*** jwagner is now known as jwagner_away19:54
*** Mudpuppy_ has quit IRC19:56
*** Mudpuppy has joined #openstack-ansible19:56
bgmccollumshould this even be in the icehouse branch? https://github.com/stackforge/os-ansible-deployment/blob/icehouse/etc/rpc_deploy/conf.d/swift.yml.example20:00
*** hj-hp has joined #openstack-ansible20:01
cloudnullbgmccollum nope.20:03
bgmccollum;(20:03
*** daneyon_ has joined #openstack-ansible20:07
*** Mudpuppy has quit IRC20:08
sigmavirus24bgmccollum: nice catch20:08
bgmccollumthis too - https://github.com/stackforge/os-ansible-deployment/blob/icehouse/etc/rpc_deploy/rpc_user_config.yml#L6320:08
openstackgerritJaveria Khan proposed stackforge/os-ansible-deployment-specs: Add modularize-neutron-plays specification  https://review.openstack.org/16918920:10
*** daneyon has quit IRC20:11
stevellejaveriak: FYI there is one extra space on line 39 and 40 preceding the hyphen, over indenting the list items. Contrast with 43 and 44 and they don't line up.20:13
*** Mudpuppy has joined #openstack-ansible20:14
javeriakstevelle , thanks for the catch, still trying to get used to the sphinx syntax :)20:16
*** jwagner_away is now known as jwagner20:16
svg[preparing first contribution] making a patch for a registered bugm  on say the juno branch, which needs a similar/related patch on the icehouse branch; do I need to do sth specific to have a relation with  both patches ? or is mentioning the same `Closes-Bug:' in both commits enough?20:17
openstackgerritJaveria Khan proposed stackforge/os-ansible-deployment-specs: Add modularize-neutron-plays specification  https://review.openstack.org/16918920:17
stevellejaveriak: it looks like you can use tox -e docs for a local test20:17
javeriakI've been basically using this http://rst.ninjs.org to test out the formatting20:19
cloudnullsvg: `Closes-Bug:` in both patches should be enough. it the bug will require multiple patches to close for a single release branch you can use `Partial-Bug:`20:19
svgok, thx; Partial-Bug then20:20
cloudnulljaveriak if you just run "tox" it will test and do all the building. the tox.ini has been setup to do all of the build job for you.20:21
javeriakcloudnull, cool, just gave it a try, much easier20:22
cloudnullyea less steps :)20:23
palendaecloudnull: Would you be able to answer some of the questions on https://review.openstack.org/#/c/169069/ ?20:23
cloudnullinline comments ?20:24
palendaeyeah20:24
cloudnulllet e go look20:24
svgIs `git review' always that slow?20:26
cloudnullpalendae stevelle we can get rid of that top brctl call/configure_bridge call the check in sysfs for the bridge should be enough for us to skip the container build process.20:26
palendaeSo lines 190-197 could be removed?20:27
cloudnull191 - 19620:28
svgHey, git review fails on my stating I need to fill in my contct details, which I tried several times alreaady, but that always gets me Server Error - Cannot store contact information20:28
palendaeAh, yes20:28
*** jwagner is now known as jwagner_away20:29
cloudnullsvg sorry for the reference doc but have you gone through - https://wiki.openstack.org/wiki/Documentation/HowTo/FirstTimers#Set_up_git_and_git_review20:29
openstackgerritMerged stackforge/os-ansible-deployment: Updated for 9.0.7 tag  https://review.openstack.org/16935520:30
svgcloudnull: Yes, I have. The issue is me not being able to fille in my contact details on https://review.openstack.org/#/settings/contact20:31
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Updated for 9.0.7 tag  https://review.openstack.org/16950521:01
*** daneyon_ has quit IRC21:02
openstackgerritSerge van Ginderachter proposed stackforge/os-ansible-deployment: Correct a syntax error in some hosts: patterns  https://review.openstack.org/16950621:02
*** daneyon has joined #openstack-ansible21:02
openstackgerritSerge van Ginderachter proposed stackforge/os-ansible-deployment: Correct a syntax error in some hosts: patterns  https://review.openstack.org/16950721:04
openstackgerritKevin Carter proposed stackforge/os-ansible-deployment: Repo Updated for 9.0.7 tag  https://review.openstack.org/16950521:09
cloudnull^ this review is going to fail for icehouse until it gets replicated out to mirror.rax21:10
*** hj-hp has quit IRC21:13
prometheanfirecloudnull: chicken meet egg?21:17
cloudnullits a race !21:17
prometheanfirecloudnull: you know if there's a package resource like puppets (where you can override name per distro)21:17
prometheanfirein ansible21:18
cloudnullexample?21:18
prometheanfirepackge 'apache' {21:18
prometheanfire  rhel? name=httpd21:19
*** BjoernT has left #openstack-ansible21:19
prometheanfire  debian? name=apache221:19
prometheanfire}21:19
prometheanfirepeudo-y code21:19
cloudnullin our bits, thats in the apt_packages list21:19
prometheanfireright, I want that to be generic :P21:19
cloudnullIE https://github.com/stackforge/os-ansible-deployment/blob/master/playbooks/roles/os_cinder/defaults/main.yml#L143-L15421:20
cloudnullso you'd have to add a new list. and tasks to support the new package lists.21:20
prometheanfireI get that21:20
prometheanfireit would probably be seperated out to lists per distro21:20
prometheanfirethen load the correct list21:21
prometheanfirecinder_gentoo_packaged: or something21:21
cloudnullyup.21:21
prometheanfirethe test pipeline would need gentoo hosts for this wouldn't it21:22
cloudnullyup21:22
prometheanfirelol21:22
prometheanfireguess that gives me more preasure to build official gentoo(hardened) images for OS21:23
cloudnulljust adapt the AIO scripts and get it on an external CI within your own gentoo based deployment cluster.21:23
cloudnullBOOM!21:23
prometheanfireneed an image first21:23
cloudnullopenstack, in openstack, on gentoo.21:23
cloudnullit would be OO'G21:23
prometheanfiregoog21:23
prometheanfiregentoo on openstack on openstack on gentoo21:24
prometheanfireneed to add an le to the end21:24
d34dh0r53LMAO21:24
d34dh0r53OO'G21:24
* cloudnull nobody gets my jokes....21:24
mattthaha, gentoo21:32
*** hj-hp has joined #openstack-ansible21:32
matttwith a lot of work i'm sure you could build a pretty nice platform21:32
cloudnullpalendae whats the sate with https://bugs.launchpad.net/openstack-ansible/+bug/143093721:33
openstackLaunchpad bug 1430937 in openstack-ansible juno "Enable NetworkBasicOps test in tempest commit checks" [Medium,New]21:33
cloudnull^ isn't that in juno ?21:33
cloudnullApsu: whats the state of https://bugs.launchpad.net/openstack-ansible/juno/+bug/142378321:34
openstackLaunchpad bug 1423783 in openstack-ansible juno "Horizon is not generating CSS correctly" [Undecided,New]21:34
cloudnullApsu palendae: whats the state of https://bugs.launchpad.net/openstack-ansible/+bug/1430937 https://bugs.launchpad.net/openstack-ansible/+bug/142525521:35
openstackLaunchpad bug 1430937 in openstack-ansible juno "Enable NetworkBasicOps test in tempest commit checks" [Medium,New]21:35
openstackLaunchpad bug 1425255 in openstack-ansible juno "Tempest NetworkBasicOps tests cannot ping from within instances" [Critical,New] - Assigned to Nolan Brubaker (nolan-brubaker)21:35
Apsucloudnull: sec21:36
ApsuI did the master commit on the CSS one. Guess it got tagged for backport.21:36
ApsuAs for the networkops tempest stuff, that's what I'm working on trying to find a workaround for with the kernel interface behavior21:37
*** sdake has joined #openstack-ansible21:38
*** sdake__ has quit IRC21:42
*** Mudpuppy_ has joined #openstack-ansible21:44
*** KLevenstein has quit IRC21:44
*** Mudpuppy has quit IRC21:47
*** Mudpuppy_ has quit IRC21:48
*** KLevenstein has joined #openstack-ansible21:50
*** stevemar has quit IRC21:51
*** sdake_ has joined #openstack-ansible21:59
*** sdake has quit IRC22:03
*** javeriak has quit IRC22:04
*** javeriak has joined #openstack-ansible22:12
*** hj-hp has quit IRC22:18
*** KLevenstein has quit IRC22:23
*** hj-hp has joined #openstack-ansible22:26
*** sigmavirus24 is now known as sigmavirus24_awa22:42
*** devlaps has joined #openstack-ansible22:50
*** devlaps has quit IRC22:54
*** darrenc is now known as darrenc_afk22:59
*** galstrom is now known as galstrom_zzz23:02
*** jaypipes has quit IRC23:09
*** hj-hp has quit IRC23:15
*** hj-hp has joined #openstack-ansible23:16
*** hj-hp has quit IRC23:20
*** darrenc_afk is now known as darrenc23:22
*** jaypipes has joined #openstack-ansible23:23
*** javeriak has quit IRC23:32
*** javeriak has joined #openstack-ansible23:36
*** javeriak has quit IRC23:43

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