Friday, 2015-06-26

*** Rockyg has joined #openstack-relmgr-office00:12
*** Rockyg has quit IRC00:52
*** david-ly_ has joined #openstack-relmgr-office01:06
*** david-lyle has quit IRC01:09
*** dims has joined #openstack-relmgr-office02:14
*** dims_ has quit IRC02:15
*** dims has quit IRC02:20
*** dims has joined #openstack-relmgr-office02:22
*** dims has quit IRC03:01
*** AzherKhan has joined #openstack-relmgr-office03:01
*** AzherKhan has quit IRC03:10
*** mestery has joined #openstack-relmgr-office03:23
*** david-ly_ is now known as david-lyle03:51
*** mestery has quit IRC06:08
*** dims has joined #openstack-relmgr-office09:59
*** dims has quit IRC10:18
*** dims has joined #openstack-relmgr-office10:59
ttxdhellmann: draft of the server versioning blogpost: http://paste.ubuntu.com/11778123/ -- let me know if you see anything missing11:38
*** dims is now known as dimsum__12:09
*** dims_ has joined #openstack-relmgr-office12:13
*** dimsum__ has quit IRC12:16
*** mestery has joined #openstack-relmgr-office12:52
*** mestery has quit IRC12:57
*** dimsum__ has joined #openstack-relmgr-office13:07
*** dims_ has quit IRC13:10
dhellmannttx: reading13:36
dhellmannttx: two typos fixed in https://etherpad.openstack.org/p/BJXtVdm37N13:40
dhellmannttx: do you want to mention the reason for not going with 12 for everyone?13:42
ttxthe slow drift reason ? yeah, let me try to add that13:45
dhellmannyeah, I can see that being asked a bunch13:46
dimsum__dhellmann: should mention big tent somewhere in there? Allow new projects to rapidly iterate?13:46
ttxdhellmann: what were the two typos ? copypasting from etherpad adds unwanted whitespace13:47
dhellmannttx: conundrum on line 44 and got on line 37 of the etherpad13:47
ttxack, thx13:47
dhellmanndimsum__: at this point we still want most projects to only release on the cycle boundaries, so I'm not sure that applies (yet)13:48
*** dansmith is now known as superdan13:49
dimsum__dhellmann: right, this versioning scheme does give them a choice13:50
dhellmannyeah, but I don't think we're ready to advertise that too much, yet13:50
dimsum__fair point :)13:50
ttxdhellmann: see etherpad13:57
dhellmannI'm not sure I would classify the range of versions we have as "radically-different" but I think I get what you're saying :-)13:58
ttxsufficnely-different ?13:58
dhellmannyeah, I like that better. Or purposefully distinct13:59
dhellmannttx: ship it!13:59
ttxI'll go with purposefully distinct13:59
* dhellmann heads offline for a bit14:00
ttxhttp://ttx.re/new-versioning.html14:01
dimsum__looks good ttx14:03
ttxdhellmann, dimsum__ thanks!14:04
*** gordc has joined #openstack-relmgr-office15:04
*** mestery has joined #openstack-relmgr-office15:06
gordchi, had a release question regarding liberty-1 and reverting migrations15:07
gordcwe merged this in liberty-1 to lower ids in our sql backend: https://review.openstack.org/#/c/183531/15:08
gordcthis apparently breaks heat (and maybe others) since heat generates ids beyond 128char15:08
gordcif i need to revert that migration, is it all good to just hit revert? or do i need to ensure some backward compatibility between liberty-1 and otherstuff15:09
* gordc does not have a way to ensure this, that said, migration will not pass if you have data beyond 128char15:10
gordcdhellmann: ^ in case you have feedback15:12
*** dimsum__ has quit IRC15:13
*** mestery has quit IRC15:17
gordcttx: ^15:25
ttxgordc: o/15:54
ttxgordc: it's fine to break liberty-115:54
ttxI mean, it's not fine to break master generally, but it's not worse to break liberty-115:54
ttxtechnically it's not more "released" than any other commit in master15:55
ttxgot to run15:56
gordcttx: cool cool. thanks for confirmation :)15:57
*** dimsum__ has joined #openstack-relmgr-office16:53
dhellmanngordc: I think rather than just reverting that patch, you probably want a migration to change the size back, for anyone deploying from master17:18
*** nikhil_k is now known as nikhil_k-eto17:33
*** nikhil_k-eto is now known as nikhil_k-away17:33
gordcdhellmann: so the one issue is that if you have big ids, the migration will never pass. if you have 'small' ids it will... but i don't really have a consistent way to handle both cases.18:14
dhellmanngordc: in the follow up, introspect the column size and only change it back if it is small18:15
gordcdhellmann: but if i leave the original script in there, it will break. and you will never be able to get to followup script18:17
dhellmanngordc: update that one to skip? or replace its body with the logic to resize back up?18:17
gordcdhellmann: update the existing script to skip on error?18:18
dhellmanngordc: no, to not do anything -- are you using alembic or sqlalchemy-migrate?18:22
dhellmanngordc: either way, i think you'll confuse the migration tracking for any deployment that has successfully run that migration if you just delete it18:22
gordcsqlalchemy-migrate18:23
dhellmanngordc: with a database migration you have to assume that if it lands in master it has landed in production. You can't delete it, but you can make a new migration that undoes the change.18:23
gordcdhellmann: :(18:24
dhellmanngordc: yeah18:24
gordcdhellmann: i'll try to catch the error in existing script and add new script i guess.18:24
dhellmanngordc: that works. You could also delete its body to make it a noop. As long as the script still exists it will not break the tracking18:25
gordcdhellmann: yeah that works too. i'll give that a try.18:25
gordcdhellmann: thanks18:26
*** mestery has joined #openstack-relmgr-office19:54
*** gordc has left #openstack-relmgr-office20:05
*** mestery has quit IRC20:57
*** openstack has joined #openstack-relmgr-office21:26

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