Monday, 2016-05-23

*** krotscheck_dcm is now known as krotscheck00:39
*** hieulq has joined #openstack-sprint01:16
*** baoli has quit IRC01:57
*** baoli has joined #openstack-sprint02:04
*** baoli has quit IRC02:26
*** yuikotakada has joined #openstack-sprint05:55
*** yuikotakada is now known as yuikotakadamori05:55
*** yuikotakadamori has quit IRC07:23
*** yuikotakadamori has joined #openstack-sprint08:20
*** baoli has joined #openstack-sprint09:05
*** baoli has quit IRC09:09
*** cdelatte has joined #openstack-sprint11:05
*** rfolco has joined #openstack-sprint12:00
*** baoli has joined #openstack-sprint12:02
*** anteaya has joined #openstack-sprint13:14
*** ChanServ changes topic to "Taking Infra servers running Precise and upgrading them to Trusty | https://wiki.openstack.org/wiki/VirtualSprints#Infra_Trusty_Upgrade"14:13
fungii've claimed the storyboard.o.o upgrade for myself. guess i'll try to kick the week off with that14:14
funginote that, contrary to what you might expect, there is a fair amount of change/review work which people without infra-root access can help with on this sprint14:15
anteayagreat14:15
anteayaI'm fine to help with the change/review work14:15
anteayamostly I need to learn what to do there14:16
fungipick an entry in openstack-infra/system-config manifests/site.pp which only has precise in the the comment and add a second line for trusty (like what you see for storyboard.openstack.org already)14:16
anteayaso I'll watch/observe/learn from the first one?14:16
fungithen see if it passes tests, and if not, try to figure out what needs fixing first14:16
fungionce an infra-root admin gets to the point of launching a replacement for that entry, they will quite probably find other things which need tweaking in various puppet modules as well, which will need reviewing14:17
fungialso, even if not infra-root, you can try to launch your own versions of some of these on a trusty vm under your control and figure out if anything needs improving to work there14:18
anteayaawesome thank you14:18
anteayado we want a separate URL in the topic for the etherpad: https://etherpad.openstack.org/p/newton-infra-distro-upgrade-plans14:31
anteayaor is the link to the virtual sprint page sufficient?14:31
ZaraooooOoooOOoo (I'm just lurking for now, feel free to ping me for reviews)14:36
anteayaZara: or you can help following the instructions fungi gave above14:37
Zaraanteaya: yeah, sorry, I meant because I'm behind with other things today, so unlikely to get to it until tomorrow14:38
anteayaZara: ah okay14:38
anteayatomorrow is great too14:39
fungiyeah, i got sidetracked by someone asking me a ton of zuul questions in a private /msg14:39
anteayahappy to have your help when you have the time14:39
anteayafungi: :(14:39
fungiplanning to hit up #storyboard to coordinate the server upgrade shortly14:39
anteayafungi: was that this person? http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2016-05-23.log.html#t2016-05-23T08:50:0114:39
Zarayay :) (in fairness I err on the side of under-committing myself so that I'm able to respond to messages.)14:40
anteayaZara: good plan14:40
anteayashould we have a common gerrit topic for this work?14:45
anteayatrusty-upgrade as a suggestion14:45
fungiwfm14:46
anteayathanks, I'll add it to the etherpad14:47
fungiappreciated https://review.openstack.org/#/q/topic:trusty-upgrade+status:open14:47
fungior you can add it to our sprint section on the wiki14:47
fungii wasn't sure what was best to link in the /topic here and still keep it short14:48
anteayasure14:48
anteayathe sprint wiki section has the etherpad link14:48
anteayawhat is apps.openstack.org?14:49
anteayaam I safe to take that one?14:49
anteayaI'll take that one14:49
fungithat's the openstack app catalog. i believe it's entirely self-contained at this point (no trove, no cinder) though it may have local data which needs copying to a replacement. docaedo will know14:50
fungihowever, a patch to start testing it against trusty will be the first step regardless14:51
anteayaI will take it14:51
anteayathanks14:51
fungiin spite of being completely distracted by all manner of other things, i have now gotten far enough to lower the ttl on our a/aaaa dns entries for storyboard.openstack.org to 5 minutes (previously 60, so i shouldn't change dns until ~15:50 utc)14:52
anteayafungi: yay14:57
anteayafungi: I have added an "how can I help?" section on the etherpad15:00
anteayafungi: can you check my instructions for create a patch to ensure I am conveying accurate information should we get a newcomer15:00
fungianteaya: looks great--thanks!15:02
anteayafungi: thank you15:02
clarkbapache differences likely to be the common issue we hit15:12
anteayamorning clarkb15:12
fungispeaking of which, my attempt to deploy a storyboard.o.o replacement failed. i reran with --keep and am digging in syslog on it now to see what happened15:14
fungigotta be something which wasn't exercised when i deployed the storyboard-dev instance last week15:14
Zaraoh no! thank you for looking into it.15:15
fungioh, looks like maybe-racy resource ordering15:15
fungiMay 23 15:08:34 storyboard puppet-user[19383]: (/Stage[main]/Storyboard::Cert/File[/etc/ssl/certs/storyboard.openstack.org.pem]/ensure) change from absent to file failed: Could not set 'file' on ensure: Could not find group ssl-cert at 41:/etc/puppet/modules/storyboard/manifests/cert.pp15:15
fungithat group should be created by the ssl-certs package15:16
Zarassl certssssssssss15:16
Zaramaybe if I hiss at them, things will work15:16
fungier, ssl-cert package15:17
clarkblogstash-worker* can just be replaced in batches. remember to bounce iptables on elasticsearch nodes once dns is updated. I will likely start there when I have a good chunk of time today15:17
fungiby the time the puppet manifest is done being applied, that package has been installed and the group it wants exists, just not soon enough to satisfy the dependency15:18
fungii have a feeling we're going to end up with a circular dependency issue here if i try to install that package to break the dependency cycle15:19
anteaya:(15:19
clarkbis there no dep on the package?15:19
fungii believe the apache puppet module is pulling it in15:20
fungibut we need those files in place before we start apache15:20
fungiso we make the apache class depend on those files15:20
fungiwhich need permissions set to a group which is added by a dependency of the class we're trying to prepare for15:20
nibalizergood morning15:27
funginibalizer: ^ ideas on that circular logic problem?15:27
nibalizerstill reading15:28
fungii suppose i could add a resource for the ssl-cert group so that puppet creates it explicitly and break the cycle that way15:28
anteayanibalizer: morning15:28
nibalizerfungi: yea that is one way15:28
fungithough... for users of the module relying on its snakeoil cert support, that cert/key is also created by the ssl-cert package i think?15:29
nibalizerso we xant drop the cert after the package?15:29
fungiso that's probably not sufficient15:29
funginibalizer: ideally we get it to install the ssl-cert package, then create the certs used by our vhost configs, then install apache (which will get automatically started by its packaging)15:29
fungibut i think the apache puppet module is also separately depending on that package. still digging to see whether that's the case15:30
fungione of those order-of-operations situations puppet is lousy with15:31
anteaya<-- food15:32
clarkbjust set that file to root:root15:32
fungiclarkb: you're genius. there are no members of that group on the production storyboard.o.o15:34
fungisometimes the simple solutions are the hardest to arrive at15:34
nibalizerheh15:39
fungiadded as https://review.openstack.org/32000815:39
fungithough i'm half expecting the next attempt to launch it will point out that we also don't have the parent directories for these files as they're probably also created by the ssl-cert package15:40
nibalizerfungi: looking great15:40
anteayaso apparently apps.o.o is already on trusty: http://git.openstack.org/cgit/openstack-infra/system-config/tree/manifests/site.pp#n125615:43
anteayacan anyone confirm?15:44
nibalizeranteaya: nope15:45
nibalizernibz@apps:~$ cat /etc/issue15:45
nibalizerUbuntu 12.04.5 LTS \n \l15:45
nibalizerhttp://puppetboard.openstack.org/node/apps.openstack.org is another easy way to check15:46
anteayanibalizer: thanks15:46
anteayahmmm, what would be happening that site.pp has trusty but the node is precise?15:48
nibalizeranteaya: someone goofed i'd guess15:50
anteayaokay what if anything should I do now?15:50
fungiprobably need to coordinate with docaedo to find out what data should be copied to a new server and when a good time for a cutover would be15:56
anteayaokey dokey15:58
*** kcalman_ has joined #openstack-sprint16:00
pleia2o/16:03
anteayamorning pleia216:03
anteayathe etherpad is here: https://etherpad.openstack.org/p/newton-infra-distro-upgrade-plans16:03
fungiit's also linked from the wiki page mentioned in the /topic16:04
*** jeblair has joined #openstack-sprint16:04
jeblairhowdy!16:04
fungiwe're still sort of spinning up here i think16:07
jeblairwhew, didn't miss much then16:07
fungii'm poking at trying to upgrade storyboard.o.o, anteaya is trying to coordinate details for the apps.o.o upgrade16:08
jeblairwhy don't i go do cacti16:08
fungithat sounds swell16:08
fungithanks!16:08
clarkbcacti will require firewall update and iptables bounce everywhere16:09
jeblairwhee! :)16:09
fungioh, right, because snmp16:10
clarkbI have furnace person coming over this morning to tell me what it will cost to make home habitablr16:10
clarkbafterwards will start on logstash workers16:10
anteayaclarkb: is this part of the inspection still16:11
anteayaclarkb: or are you a proud homeowner?16:11
clarkbI am a proud homeowner16:11
anteayayay!16:11
anteaya\o/16:11
anteayacongratulations16:11
anteayawhen do you move in?16:11
clarkbdepends on ehat furnace person says :) probably mid next month16:12
jeblairclarkb: congrats!  (i also had to replace furnace first thing -- what's with that?)16:12
anteayaclarkb: yay16:12
clarkbthis one is 27 years old was not working during inspectio  so we knew it upfront16:12
clarkbthe fridge on the other hand was foa16:13
clarkber doa16:13
anteaya:(16:13
jeblairyeah, i guess "furnace broke -- time to sell the house" is a thing16:13
anteayaha ha ha16:13
pleia2fwiw, everything breaks when you first move in16:13
pleia2it's a thing16:13
pleia2it gets better :)16:13
anteaya:)16:13
jeblairclarkb, pleia2: my surprise doa appliance was the dishwasher16:13
pleia2garbage disposal16:14
jeblair(oh, yeah, replacing this is what i want to be doing right now)16:14
jeblairpleia2: we *thought* the disposal was bad, but then we found the thing that was stuck in it. ew.16:14
clarkbwe spent the weekend cleaning. previous occupant had a dog which means fur everywhere and dirty walls16:14
clarkbwhich after cleaning will hopefully get new paint16:14
anteayayay new paint!16:15
anteayaif you get a pet yourself your pet will go anywhere the prior pet went if it went in the house16:15
anteayaso cleaning, steaming or replacing carpet is not a bad idea if you on on the fence on flooring16:16
clarkbChloe has already enjoyed licking things I assume the dog licked16:16
anteayaha ha ha16:16
anteayaokay then, looks like you have addressed that concern16:16
jeblairi lowered cacti's ttl16:22
jeblairapparently it does not have an aaaa address16:22
jeblairi'm certain we want to move the filesystem to cinder; do we also want to move mysql to trove?16:23
fungithat's a good question... i know mordred was looking into trove's replication options to possibly mitigate our need to stop using it16:24
jeblairi'm leaning toward trove for now.... it'll be in the same boat as most other services16:25
fungiand even if we take trove as a short-term proxy for "remote mysql server we operate" it's a good next step16:25
jeblairya16:25
fungiso i'm inclined to agree16:26
jeblaircacti uses a whole 711M of disk for rrd16:26
jeblairmin volume size is 100G?16:26
jeblair(for sata)16:26
jeblair7516:27
jeblairi guess i will give it a 75G volume16:27
fungiheh16:29
fungithat's hilarious16:29
pleia2fungi: might want to use trusty-upgrades (with an 's') for the topic since that's what pabelanger has been using16:30
fungiahh, good idea. i just went with whatever anteaya suggested, but we can adjust it16:32
anteayapleia2: do you want to change that on the etherpad?16:32
pleia2anteaya: I added the other link16:32
anteayaI didn't know there was an existing topic16:32
pleia2already16:32
anteayawe can change it, just fungi and I have patches up using today's topic16:32
anteayadone16:33
anteayatrusty-upgrades it is16:33
fungii just adjusted the topic on my patch too16:33
pleia2thanks16:33
fungithough it looks like crinkle already approved it. thanks!16:33
anteayathank you16:33
crinkleo/16:34
anteayaah dueling topic upgrades16:34
*** sivaramakrishna has joined #openstack-sprint16:34
anteayafungi: who won?16:34
pleia2so I'm gathering we're preferring to replace nodes rather than in-place upgrades16:34
pleia2need to add some details to the etherpad, re: lower dns ttl etc16:35
anteayalooks like you did, guess it only accepts one update16:35
anteayapleia2: good idea16:35
pleia2going to drop planet.o.o ttl16:40
fungii'm 99% sure it's entirely stateless (or rather, will rebuild its state from scratch)16:41
pleia2done for a and aaaa16:41
pleia2fungi: 99%, it does store some information just in case a blog disappears during a run so the blog remains in the planet feed16:41
pleia2but I think we don't care about that so much16:41
pleia2it updates often enough, nbd16:42
pleia2anyway, a/aaaa records at 5min now16:42
anteayapleia2: can you do paste.o.o while you are there?16:43
pleia2anteaya: sure16:44
anteayathanks16:44
pleia2anteaya: done16:44
anteayathank you16:44
jeblaircacti could use some more puppeting (its database configuration is not in puppet)16:51
anteayajeblair: should that become a story so it doesn't get lost?16:56
jeblairanteaya: probably so16:56
jeblairon puppet-cacti16:56
anteayajeblair: do you want to do it or shall I?16:56
jeblairwait, we don't have a puppet-cacti16:56
jeblairmaybe we need one :)16:56
anteayaif I do it it will just be a copy paste of your words16:56
anteayaah ha16:56
anteayaI agree16:56
jeblairanteaya: if you could, that would be great; i don't have any more words to add16:57
anteayaI will16:57
jeblairanteaya: it's LHF16:57
anteayaI will tag it appropriately16:57
anteayaI think we need to grow a puppet-cacti repo, I can't find one16:59
anteayathen our puppet cacti repo should have database configuration17:00
anteayaI had thought you had said we just didn't have one in storyboard17:00
anteayawe don't have the repo at all17:00
anteayaI'll mix up a repo17:00
anteayahave we anything to import into it when it is created?17:00
jeblairanteaya: there is no cacti module right now, it's managed out of system-config.17:01
anteayaI'll create a new empty repo called openstack-infra/puppet-cacti17:02
anteayathen we can go from there17:02
jeblairanteaya: well, don't do that unless you intend to put something in it :)17:02
anteayaoh sorry17:02
anteayaI had thought that was what you wanted17:02
jeblairanteaya: i would love for someone to do that.  i do not plan on doing it.17:03
anteayayou want a bug filed against system-config for now? to puppet more of puppet-cacti17:03
anteaya's database?17:03
jeblairanteaya: that's probably best17:03
anteayaokay I'll create the story, sorry I was confused17:03
anteayahttps://storyboard.openstack.org/#!/story/200060117:07
*** sivaramakrishna has quit IRC17:07
*** sivaramakrishna has joined #openstack-sprint17:08
*** sivaramakrishna has quit IRC17:09
jeblairfungi: apache on the new cacti server is continuously segfaulting17:12
fungijeblair: ouch17:13
fungicontinuously as in as soon as it gets browsed, or with no activity at all? when just trying to start or after it's running?17:13
jeblairfungi: as soon as it receives a request.  it worked with the ubuntu/debian start page, but once i removed that so that it hit the cacti endpoint (php), it started segfaulting on every request17:14
fungioh17:15
fungiso segfault in mod_php17:15
jeblairmaybe.  i will get dumps.17:15
fungilikely means there is some php in there which is unhappy under/incompatible with the php version on trusty17:16
fungiat least that's the most likely culprit17:16
fungior we have some php configuration there which is no longer valid under newer php releases17:17
fungijeblair: anteaya: yep, whoever picks up the task to puppet db setup for our cacti class could optionally extend the scope of work there to doing it in a new puppet module17:20
fungi(and subtree-split or filter-branch the existing class in the process to preserve history on what's being copied in)17:21
anteayashould I append anything to the story? https://storyboard.openstack.org/#!/story/200060117:21
fungii can17:23
*** bkero has joined #openstack-sprint17:24
anteayafungi: thanks17:24
jeblairfungi: http://paste.openstack.org/show/498224/17:29
jeblairfungi: that appears to infinitely recurse17:29
funginow that's fancy17:30
fungimod_php, as expected17:30
fungithough looks like an actual php bug?17:31
fungiat least i don't see it calling out to anything17:31
jeblairfungi: browsing bug histories, i've seen those described as 'userland error' by php devs17:31
fungimmm17:32
jeblairit *might* be the unconfigured database17:32
bkeroI'd be scared of any PHP error that happened in kernel land.17:33
jeblairi'll copy that over now17:33
jeblairbkero: i believe it's in userspace17:33
jeblairbkero: (i think php provides dtrace hooks, which is why dtrace shows up in function names in the call stack)17:35
bkeroOdd that they wouldn't macro that out17:36
jeblairuh yep.  apparently that *particular* segfault meant "database not found"17:39
* jeblair cleans up host17:40
nibalizerhah17:40
pleia2yeesh17:42
jeblairhttp://104.239.135.208 looks okay17:43
jeblairi'm going to replace the hostname in dns now17:43
fungiwow, heh17:43
jeblairiptables configs are by hostname, so once i do that, i can rehup iptables everywhere17:43
fungimissing database? raise exception in php, segfault apache17:44
fungisounds like sane error handling to me17:44
jeblair(i mean, we could add the new and old ips to iptables globally, then remove them later; but i think we'll be okay with a small gap in cacti data)17:44
nibalizerfungi: exactly17:44
fungijeblair: yeah, seems fine. when we see gaps in the graphs, we'll know the reason17:45
fungimaybe #status log it for posterity17:45
jeblair#status log changed cacti.openstack.org IP address (for upgrade to trusty); gap in data around this time while iptables updates everywhere to allow snmp17:46
openstackstatusjeblair: finished logging17:46
jeblairalso, i just used "python dns.py 2fb22df0-c176-4885-9a66-5735519c719b" to output the dns commands17:47
fungiglad that still works17:47
jeblairthat is necessary because dns.py <hostname> doesn't work when there are 2 hosts, but supplying the uuid does work17:47
jeblairso yay!17:48
fungiclarkb: nibalizer: crinkle: hey! the ssl-cert to root group name adjustment worked! i just successfully launched a trusty-based storyboard.o.o to completion from scratch17:48
pleia2\o/17:49
anteayafungi: yay!17:49
crinkle\o/17:49
nibalizernice!17:49
nibalizerin clarkb we trust17:49
anteayaha ha ha17:50
anteayaI want a coin with that stamped on it17:50
bkeroOn infrabucks17:50
jeblairoh, weird17:51
jeblairso *most* of our iptables is by hostname17:51
jeblairbut cacti snmp is not17:51
jeblairand the reason i did not find this out by searching for the ip address in system-config is that it is in puppet-iptables17:51
nibalizeryep17:51
* nibalizer really wants to make that whole system better17:51
jeblairnibalizer, fungi: can you instapprove remote:   https://review.openstack.org/320085 Change cacti IP address17:53
jeblair(i also removed the previous previous cacti address)17:53
nibalizero717:54
fungijeblair: awesome17:54
fungijeblair: what about its ipv6 address? i wonder if it's likely to start using that from the new server or not17:54
jeblairfungi: i think it had an ipv6 interface+address on host before, just wasn't in dns.  but yeah, we should add that...17:55
jeblairoh hey17:55
jeblairwe had the v6 address too17:56
jeblairfungi, nibalizer: remote:   https://review.openstack.org/320089 Change cacti IPv6 address17:58
jeblairi'm enqueing those into gate to reduce the window we are without data collection18:01
fungianybody happen to know what causes launch-node.py to do this? http://paste.openstack.org/show/498236/18:03
fungiit seems to be benign, but i get pages and pages of it after the script completes18:04
nibalizerfungi: no idea18:05
nibalizerdo you have openstack related envvars sourced when you run it?18:05
anteayabkero: are you going to be testing paste.o.o on trusty on a local vm?18:05
funginibalizer: yes, i do (following the README from the same directory to the letter)18:06
anteayabkero: I was just about to do that but won't bother if you are18:06
bkeroanteaya: I did during the summit. Paul was there. I tested using a trusty host against the a db made with precise18:06
bkeroworks fine without modification :)18:06
anteayabkero: great do you want to update the etherpad for the paste.o.o entry?18:06
anteayaso we all can track your progress18:07
jeblairfungi: i did not see that with the host i just launched18:07
bkeroanteaya: sure, although I'm not a rooter and can't provision the boxes or do dns myself18:07
anteayaright, but you can claim the server with your work18:07
anteayaso I can stop dublicating what you have already done18:07
* bkero nods18:07
fungijeblair: are you using an interactive root shell on the puppetmaser to run it? just wondering what i might be doing to cause different behavior18:07
fungibkero: yep, i moved our lodgeit db back into trove recently, so if the manifest is working fine on trusty then it should be an easy one for us to swap out. i'm happy to tackle it next after i get the storyboard swapout done18:09
bkerofungi: ok, the review has us creating a new paste01 host, so I think that's going to need to be provisioned, then tested, and if works well we can update DNS.18:10
bkeroThanks for the assist!18:10
anteayabkero: why are you creating a new domain name? https://review.openstack.org/#/c/311235/2/manifests/site.pp18:10
bkeroanteaya: see the -1 comment from paul18:11
bkeroHe advised that's the new naming strategy, and I didn't have the context to refute that. So I shrugged and updated the patch to match.18:11
anteayabkero: I think it was decided, did he say who decided or where?18:11
nibalizeri'm working on puppetdb01.openstack.org so that fits18:11
anteayaokay well that is news to me18:12
nibalizerwe had a discussion in one of the workrooms at the summit18:12
bkeroanteaya: Not that I can recall18:12
fungioh, should i rebuild the storyboard.o.o replacement as storyboard01?18:12
anteayaand doesn't match what the top of the etherpad says for how to proceed today18:12
anteayaI don't care18:12
anteayabut I would like some agreement18:12
nibalizeryah i wouldn't go so far as to say we decided, but we disucssed it a bunch18:12
anteayanibalizer: who?18:12
fungithat's mostly because i forgot we'd decided that18:12
nibalizerit helps us prevent us having two hosts with the same name18:12
nibalizerwhich makes our automation more predictable and less buggy (and stretches my brain less)18:13
anteayaI obviously missed this dicussion and would like to read up on it18:13
jeblairfungi: no, sudo from corvus18:13
anteayaif anyone has any links to the discussion18:13
jeblairfungi: i also literally followed the instructions18:13
bkeronibalizer: it does allow us to use node regexes, which should make the manifests smaller18:13
funginibalizer: what was the reason again? because tracking multiple hosts with the same fqdn is hard to make work correctly in our ansible inventory?18:13
jeblairfungi: i have export OS_CLIENT_CONFIG_FILE=/etc/openstack/all-clouds.yaml18:13
jeblairfungi: in my .profile18:14
fungijeblair: those envvars get preserved by sudo?18:14
bkerosudo -E preserves environment18:14
jeblairbkero, nibalizer, fungi: i think if we decided on a new naming strategy, we should document it18:14
nibalizerjeblair: yah18:15
bkerojeblair: I agree. I think that's what this page is for. https://etherpad.openstack.org/p/infra-operating-system-upgrades18:15
bkeroCan we get quorum in here right now though?18:15
fungiwell, etherpads aren't documentation18:15
jeblairfungi: oh, wait, i did not use sudo18:15
*** ig0r_ has joined #openstack-sprint18:15
fungijeblair: oh, so it's working with our normal accounts again now? i didn't think to try that18:16
nibalizeri had decided to try out the foo01.o.o syntax with the puppetdb upgrade18:16
bkeroSpeaking of etherpads aren't documentation, does anyoen remember which workmeeting the decision was part of, so we can go through the summit pads and validate?18:16
jeblairyeah, the documentation would go in http://docs.openstack.org/infra/system-config/sysadmin.html#launching-new-servers or https://git.openstack.org/cgit/openstack-infra/system-config/tree/launch/README18:16
nibalizerstill in progress because puppetdb is annoying18:16
fungijeblair: for a while it was broken because of lack of filesystem access to reset the inventory cache18:16
jeblairi would particularly like it to be documented because i don't recall whether we did 01 or date18:16
nibalizerjeblair: want me to take a crack at a system-config patch?18:16
nibalizercan whip that up pretty easily18:17
jeblairand i'd really like it to go through a written discussion process because then i would know where to find the answer to "what does paste01 mean compared to jenkins01"?18:17
nibalizeroh thats a good point i had not considered18:18
nibalizerwell I could start an ML thread that we can kick around for a while18:18
fungi(git01, logstash-worker01, et cetera)18:18
nibalizerand we could just upgrades in the standard way today?18:18
bkeroSend it to the committee!18:18
bkero(heh, don't do that)18:18
jeblairlike, my recollection is that we *decided* we should change our naming scheme to something that supports more hosts.  i don't remember deciding exactly what that scheme would be.  i think we're at the point where we should kick around proposals)18:18
jeblairnibalizer: ++18:19
nibalizercool18:19
fungii suppose one answer there is that we just keep burning hostnames (so when you replace git01, do so with git09 and delete git01 later)18:19
bkerohttps://etherpad.openstack.org/p/newton-infra-launch-node-ansible-and-puppet18:20
nibalizeror use a - or something eg paste-01.o.o and git01-01.openstack.org18:20
jeblairfungi: yeah, that would probably be fine18:20
bkeroThis seems like where the discussion took place18:20
nibalizerbkero: thanks for digging that up18:20
nibalizerbtw the spec i promised in that got written and is up against the specs repo18:21
fungiwe've already followed this pattern at least once, which is why our 6 elasticsearch nodes are numbered 02-0718:21
jeblairfungi: i assume we'll have an es01 again someday18:21
fungithere's certainly nothing to stop us18:21
jeblair(i'd expect 'lowest available number') to be the algorithm18:22
nibalizerso most of the time it cycles between 01 and 02 ?18:22
jeblairi'd imagine so18:22
bkeroIn theory a piece of clustering software that was sufficiently braindead could see a replaced 'old' node and if that were the leader it would either split-brain or ruin state.18:23
fungior 00 and 01 (cardinals or ordinals?!?)18:23
bkeroBut I don't think any of the clustering software we use is that dumb18:23
* fungi finds ways to paint the bikeshed18:23
fungibkero: if it is, we should fix it18:24
bkeroDefinitely, we just need to know that software matching that description exists first. Ideally without getting burned.18:28
anteayacan someone who understands what the decision is update the etherpad please? https://etherpad.openstack.org/p/newton-infra-distro-upgrade-plans18:28
anteayathen we at least have a chance of following the same workflow18:29
*** kcalman_ has quit IRC18:36
anteayaI'm going for a walk I'll be back in about an hour18:38
*** baoli has quit IRC19:01
bkeroSo, uh, I don't feel I have the authority to put that up at the top, but maybe someone else in here does?19:24
bkeroSo we can move on with $THINGS.19:25
fungidid nibalizer's spec cover it?19:32
* fungi checks19:32
funginibalizer: nice futurama reference there19:33
fungii'll propose a straw man of what i think we arrived at as a documentation patch. just a sec19:35
nibalizeri jeblair was saying he wanted to hash it out on the ML19:42
fungithat's fine, the ml discussion can be "here's a proposed patch"19:42
nibalizerawesome19:44
nibalizerthanks fungi19:44
fungihttps://review.openstack.org/32011519:46
fungiwas someone writing the ml thread starter already, or shall i?19:46
anteayaI just returned from my walk19:48
anteayaI was not writing anything19:48
fungii was taking a longish break for lunch, so only just picked this back up myself19:48
anteayaI do not object to fungi writing a ml thread starter19:48
anteayanice, I hope you had a nice lunch19:49
anteayagorgeous day here19:49
anteayasunny and quiet19:49
pleia2planet looks fine, but I haven't run launch-node.py in months, anything I should know once this system-config patch is in place?19:49
anteayalike it used to be all summer long19:49
fungiother than the fact that one replacement server may have already gone into production today without a numbered suffix, i didn't hear any particular objection to sticking with that pattern19:49
anteayapleia2: nice work on planet19:49
fungipleia2: which system-config patch?19:50
pleia2fungi: just https://review.openstack.org/#/c/320047/ for planet trusty node19:50
*** baoli has joined #openstack-sprint19:56
*** baoli has quit IRC19:57
*** baoli has joined #openstack-sprint19:57
*** ig0r_ has quit IRC19:59
fungipleia2: just cut-n-paste what's in launch/README in system-config20:01
pleia2fungi: alright good, no surprises then :)20:09
*** baoli_ has joined #openstack-sprint20:19
*** baoli_ has quit IRC20:20
*** baoli_ has joined #openstack-sprint20:20
pleia2ooh, my local test was not a great one for planet, there are python errors I missed that I don't see in prod, and it's causing a much shorter list of blogs during processing20:21
* pleia2 digs20:21
*** baoli has quit IRC20:21
pleia2so it's this https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747381 which brings me to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=73583720:25
openstackDebian bug 747381 in planet-venus "planet-venus: please move experimental version to unstable" [Important,Fixed]20:25
openstackDebian bug 735837 in python-html5lib "python-html5lib 0.999-2 breaks planet-venus" [Important,Open]20:25
pleia214.04 has the buggy 0~bzr116-1 version, not the "new" unstable one20:26
jeblairdo we have any hosts without public ipv6 addresses?20:29
jeblairoh, mirror servers...20:29
jeblairi suspect that trusty's cacti+php do not play well with servers with aaaa records20:30
pleia2that's depressing20:30
fungiwow20:31
jeblairi think php's snmp module is misinterpreting the ":161" (port) that is appended to each hostname in the @snmp2_get calls20:31
pleia2x_x20:31
pleia2php!20:31
pleia2lunchtime20:32
*** baoli_ has quit IRC20:35
jeblairor... maybe it's actually trying to use ipv6...20:38
fungithread on new naming pattern http://lists.openstack.org/pipermail/openstack-infra/2016-May/004323.html20:39
jeblairokay, i think the error is entirely in our snmpd config... patch incoming20:48
jeblair(and i guess we should cheer that php/cacti have started trying ipv6 by default which has uncovered this?)20:48
fungiyay progress!20:50
jeblairfungi, pleia2, nibalizer: remote:   https://review.openstack.org/320135 Listen on IPv620:50
jeblairoh there is no subscribe there...20:51
jeblairi wonder if we should set that up first20:51
*** baoli has joined #openstack-sprint20:52
fungino subscribe for what?20:53
jeblairfungi: to restart snmpd when the file is updated20:53
fungiahh20:53
fungiin puppet, got it20:53
fungii was low on context20:53
jeblairfungi: and i was stingy with it :)20:53
jeblairremote:   https://review.openstack.org/320137 Subscribe the snmp service to config file updates20:54
fungialso for some reason i didn't realize you needed v6-specific snmp communities20:54
jeblairfungi: i didn't either, but beat my head against it for several minutes before google told me about it20:54
jeblairi restacked it so the subscribe is first, then the v6 update20:54
fungiyeah, i just found similar documentation when i reviewed that. amusing20:55
jeblairnibalizer, pleia2: if you can review 320137 and 320135 soon, that would help us get our cacti monitoring back21:02
pleia2I'll +A in a few minutes if nibalizer isn't around to look21:10
fungiso back on the topic of server names as pertains to this week's exercise... should we proceed under the assumption that our server replacements need to be whatever01 now, or should we hold off doing that and stick with the old method of naming them the same thing as what they're replacing until we gain broader consensus on the ml/doc review?21:16
fungii'm fine going either direction, but am likely to default to $old_way if we're still trying to build consensus on $new_way21:17
jeblairi just did cacti.o.o without a number, and don't really feel like redoing it, but i think if we figure we have consensus, i don't object to remaining hosts being numbered21:17
jeblair(and am similarly ambivalent)21:17
nibalizer;[ya dont redo cacti22:03
* bkero would vote for numbering under the assumption that it or something like it would be used in the future.22:21
jeblaircacti has data again22:30
jeblairi'll delete the old host tomorrow22:30
anteayayay cacti22:41
*** jhesketh_ has joined #openstack-sprint22:49
*** craige_ has joined #openstack-sprint22:51
*** natorious_ has joined #openstack-sprint22:52
*** sbadia_ has joined #openstack-sprint22:53
*** rfolco has quit IRC22:53
*** bkero has quit IRC22:53
*** zhenguo_ has quit IRC22:53
*** sbadia has quit IRC22:53
*** jhesketh has quit IRC22:53
*** mmedvede has quit IRC22:53
*** craige has quit IRC22:53
*** natorious has quit IRC22:53
*** sbadia_ is now known as sbadia22:53
*** craige_ is now known as craige22:53
*** natorious_ is now known as natorious22:53
*** mmedvede has joined #openstack-sprint23:03
*** yujunz has joined #openstack-sprint23:09
*** yujunz has quit IRC23:15
fungii mostly don't want to create a weird storyboard01 and put it into production only to find later there's consensus on not doing that23:15
fungibut if the majority seems to be leaning there, i may just do it anyway and move on with my life23:16
fungii made some very excellent pizza tonight, so i'm in much more of a go-with-the-flow sort of mood23:17
nibalizermmm23:21
anteayapizza23:30
anteayaif you create a storyboard01 server would users navigate to storyboard01.openstack.org?23:31
anteayaor would it just show up in cacti and system-config (and puppetboard) as storyboard01?23:31
*** rfolco has joined #openstack-sprint23:38
*** zhenguo_ has joined #openstack-sprint23:39
pleia2anteaya: as I understand it, the name in nova would be storyboard01, and so would the hostname (for ansible) but otherwise it would show up/be referred to as storyboard.o.o23:46
pleia2so I think we'd continue to use storyboard.o.o in cacti and system-config23:47
anteayaah okay thank you23:47
anteayawas wondering how far the enumerated name went23:47
pleia2I'm kind of guessing too :)23:48

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