Tuesday, 2014-12-09

*** barclaac has quit IRC00:01
openstackgerritDoug Wiegley proposed openstack/neutron-lbaas: Post-split, get jenkins tests passing  https://review.openstack.org/14018200:19
*** sbfox has quit IRC00:27
*** crc32 has quit IRC00:58
*** SumitNaiksatam has quit IRC01:15
*** mestery has quit IRC01:18
*** mestery has joined #openstack-lbaas01:20
*** xgerman has quit IRC01:21
*** mestery has quit IRC01:23
openstackgerritDoug Wiegley proposed openstack/neutron-lbaas: Post-split, get jenkins tests passing  https://review.openstack.org/14018201:24
*** mlavalle has quit IRC01:27
*** SumitNaiksatam has joined #openstack-lbaas01:29
openstackgerritDoug Wiegley proposed openstack/neutron-lbaas: Post-split, get jenkins tests passing  https://review.openstack.org/14018201:57
openstackgerritDoug Wiegley proposed openstack/neutron-lbaas: Post-split, get jenkins tests passing  https://review.openstack.org/14018202:02
*** barclaac|2 has quit IRC02:21
*** fnaval has quit IRC02:30
*** SumitNaiksatam has quit IRC02:39
*** ptoohill_ has joined #openstack-lbaas02:45
*** ptoohill_ has quit IRC02:46
*** fnaval has joined #openstack-lbaas02:46
*** ptoohill_ has joined #openstack-lbaas02:46
*** mestery has joined #openstack-lbaas02:57
*** SumitNaiksatam has joined #openstack-lbaas03:14
*** sbalukoff has quit IRC03:21
*** mestery has quit IRC04:00
*** mestery has joined #openstack-lbaas04:22
dougwigyes, yes, we are guinea pigs.04:34
*** sbfox has joined #openstack-lbaas04:42
openstackgerritDoug Wiegley proposed openstack/neutron-lbaas: Post-split, get jenkins tests passing  https://review.openstack.org/14018204:46
*** sbfox has quit IRC05:20
openstackgerritDoug Wiegley proposed openstack/neutron-lbaas: Post-split, get jenkins tests passing  https://review.openstack.org/14018205:32
dougwigaha, 2 out of 3 passing now.  stupid environment differences.05:37
*** sbfox has joined #openstack-lbaas05:38
openstackgerritDoug Wiegley proposed openstack/neutron-lbaas: Post-split, get jenkins tests passing  https://review.openstack.org/14018205:45
openstackgerritDoug Wiegley proposed openstack/neutron-lbaas: Post-split, get jenkins tests passing  https://review.openstack.org/14018205:52
*** jschwarz has joined #openstack-lbaas05:54
*** fnaval has quit IRC05:55
*** fnaval has joined #openstack-lbaas05:56
*** mestery has quit IRC05:57
*** fnaval has quit IRC06:00
dougwigwoohoo, passing.06:02
*** ptoohill_ has quit IRC07:04
*** sbalukoff has joined #openstack-lbaas07:36
*** kobis has joined #openstack-lbaas08:06
*** barclaac has joined #openstack-lbaas08:18
*** kobis has left #openstack-lbaas08:19
*** barclaac has quit IRC08:22
*** sbfox has quit IRC09:39
*** woodster_ has quit IRC10:30
*** SumitNaiksatam has quit IRC11:22
*** jschwarz has quit IRC11:24
*** SumitNaiksatam has joined #openstack-lbaas11:26
*** enikanorov__ has joined #openstack-lbaas13:18
*** enikanorov_ has quit IRC13:18
*** woodster_ has joined #openstack-lbaas13:48
*** mestery has joined #openstack-lbaas13:59
*** mestery has quit IRC14:29
*** kobis has joined #openstack-lbaas14:45
*** fnaval has joined #openstack-lbaas14:51
openstackgerritMerged openstack/neutron-lbaas: Post-split, get jenkins tests passing  https://review.openstack.org/14018215:37
*** ptoohill_ has joined #openstack-lbaas15:37
*** ptoohill_ has quit IRC15:37
*** ptoohill_ has joined #openstack-lbaas15:38
*** fnaval has quit IRC15:48
*** fnaval has joined #openstack-lbaas15:48
rm_work8m to meeting, woo15:52
*** fnaval has quit IRC15:53
*** mestery has joined #openstack-lbaas15:55
*** vjay7 has joined #openstack-lbaas15:57
*** xgerman has joined #openstack-lbaas16:00
*** jorgem has joined #openstack-lbaas16:01
*** mlavalle has joined #openstack-lbaas16:17
*** fnaval has joined #openstack-lbaas16:18
blogandougwig: if no one wants to do teh alembic i will16:18
bloganbut if someone has a lot of knowledge in it then i think it would be best if they did it16:19
bloganthough i don't foresee it being too difficult16:19
dougwigblogan: hit it.  bob chukka said that the group policy stackforge already set up its own alembic chain for neutron, so there is an example.16:19
dougwigyou will be putting yourself on the critical path, though.  :)16:19
xgermanblogan I think you know the most16:19
sballeblogan: I agree16:20
xgermanlet me know if we need to get you an HP Cloud instance16:20
xgermanblogan --16:20
rm_workT_T16:20
dougwigfyi, it is safe to clone the new repos now.16:21
dougwigi've started adding 'standalone' tasks in the split etherpad, if you're looking for something to do: https://etherpad.openstack.org/p/services_split16:26
*** SumitNaiksatam has quit IRC16:28
*** vjay7 has quit IRC16:29
*** enikanorov has quit IRC16:30
*** enikanorov has joined #openstack-lbaas16:30
*** vjay7 has joined #openstack-lbaas16:32
blogandougwig: essentially we just need all tables for v1 for the initial alembic right?16:39
*** vjay7 has quit IRC16:40
dougwighow about the upgrade case from icehouse?  :)   it might need an initial state, which it only runs on fresh install.  or it might need to leave those tables to neutron's chains and just start diverging somehow.16:41
bloganyou mean if somehow upgrades from icehouse to kilo, they may have data in the tables that exist in neutron, so we need to migrate that data over as well?16:43
blogans/somehow/someone16:43
*** vjay7 has joined #openstack-lbaas16:44
dougwigit's all one db, we're just taking over the tables.  so how do we handle new installs vs upgrades?16:47
bloganoh god i forgot we decided on that16:47
bloganisn't just as simple as checking if the table exists, and if it doesn't we create it?16:49
bloganare we removing foreign keys?16:49
bloganok so if someone upgrades from icehouse, they also need to get hte juno chagnes16:50
bloganif any16:50
bloganand kilo changes if any16:51
bloganand if they install fresh they should just get fresh tables from kilo state16:51
bloganjuno migrations for lbaas remain in neutron, so i think its just a matter of getting the sequence right16:52
blogandougwig: thinking out loud here so tell me if i've got it wrong16:52
*** SumitNaiksatam has joined #openstack-lbaas16:52
dougwigi think that sounds sane.  no reason to rework the big neutron change unless there's a strong reason.16:53
bloganand then of course downgrading will be a pain16:53
blogannot sure how I will be able to tell if a person is downgrading from a fresh install versus an upgrade16:53
xgermanblogan, downgrading is something only jorgem likes :-)16:58
dougwigdoes alembic have a table for migration state?  can you put a flag in it?16:58
bloganxgerman: bc making mistakes is acceptable to him, not for me16:58
xgermanlol16:59
blogandougwig: yeah ill need to look into that16:59
dougwigbe prepared to stamp this out for vpn and fw when you're done, or find some minions to do those two, please.16:59
jorgemxgerman: he yo!17:01
blogandougwig: that'll be fine, ocne i figure it out here ill have it figured out for all17:01
bloganthough will need someone knowledgeable people with those17:01
dougwigpaul and sumit are standing by to help.17:02
*** barclaac|2 has joined #openstack-lbaas17:26
xgermanok, cloned the repos now...17:30
kobisany news about the lbaas mid-cycle meetup?17:31
dougwiglast i heard was week of feb 2nd.17:35
xgermanblogan I know this is embarassing but I loast the link to the LBaaS V2 API docs Min created17:38
xgermanI am wondering if you still have that17:38
sballedougwig: Do you have the install steps for the new LBaaS handy?17:43
dougwigsballe: https://wiki.openstack.org/wiki/Neutron/LBaaS/DeployWithDevstack17:45
sballethx17:45
*** vivek-ebay has joined #openstack-lbaas17:46
*** sbfox has joined #openstack-lbaas17:52
bloganxgerman: one sec18:20
bloganxgerman: https://review.openstack.org/#/c/110824/18:20
bloganxgerman: and https://review.openstack.org/#/c/106434/18:20
blogannot sure which is which18:21
xgermanok, thanks - also Min came in and gace it to me18:21
bloganah18:21
xgermando we want to revive it :-)18:21
bloganat some point, but its not immediately needed18:21
xgermancool18:21
*** rohara2 has quit IRC18:22
*** rohara has joined #openstack-lbaas18:23
*** barclaac|3 has joined #openstack-lbaas18:28
sballedougwig: Do we want to continue to use lbaaS v1 in devstack or are we moving it to V2? I am assumign Ve but just wanted to check.18:30
sballes/Ve/V218:30
dougwigfor the split, v1.18:30
sballeok so we leave it the way it is18:30
xgermanwe want v2 :-)18:30
dougwigsoon, german, soon.18:31
sballe:-)18:31
*** barclaac|2 has quit IRC18:31
blogandougwig: will the providerresourceassociations table continue to be owned by neutron?18:32
bloganat least for teh split18:32
bloganby own, i mean neutron does the manages the migration chain18:32
blogansince this table is used by all advanced services, at least that is the structure18:33
*** kobis has quit IRC18:38
*** sbfox has quit IRC18:45
*** sbfox has joined #openstack-lbaas18:55
*** jorgem has quit IRC19:00
openstackgerritGerman Eichberger proposed openstack/neutron-lbaas: WIP - service insertion  https://review.openstack.org/14043819:12
*** jorgem has joined #openstack-lbaas19:23
dougwigblogan: yes, neutron19:25
blogandougwig: someone who installs kilo fresh will still need to run through all the neutron migrations right?19:26
dougwigyes19:26
blogandougwig: and we're not moving any migrations for lbaas out of the icehouse and juno chain19:26
dougwigthat seems reasonable to me, assuming we can do future mods to those tables from our alembic chain?19:27
bloganso wouldn't the fresh installs also run through that same migration?, we just need to make sure everything thats been done in kilo gets moved over19:27
dougwigit's an issue of which alembic chain owns the table, which if alembic doesn't track, i'm not concerned about.19:27
dougwigif that made any sense.19:27
bloganif they're using the same database then it shouldn't matter19:30
bloganonce we split out into different dbs i see this being more effort19:30
*** cipcosma has joined #openstack-lbaas19:32
dougwigyou're *sure* that alembic doesn't track which chain owns which table?19:32
bloganim going to be 100% certain before i commit to my answer, i know you will remember for eternity if im wrong19:34
*** barclaac|3 has quit IRC19:35
*** barclaac|2 has joined #openstack-lbaas19:40
blogandougwig: so im probably wrong, alembic won't work if the alembic_version table has a migration name it can't find19:42
dougwigwhich means for us?19:43
blogandougwig: looking for a workaround, i have none in mind right now, unless alembic has a mechanism to search for migrations in many locations19:44
dougwigdid you check out the group based policy example?19:44
bloganyep nothing stood out19:45
bloganthough im sure i missed something19:45
dougwighang on, i know we can do separate chains, handling them independently.  are you saying we can't?  or something else?19:57
*** jorgem has quit IRC19:59
dougwigblogan: ^^19:59
blogandougwig: im saying we can do separate chains, but if we're doing a fork which is what this is, then i dont know if we can, im looking, gbp should hve had the same issue20:00
blogandougwig: ivar lazzaro wouldn't happen to be there would he?20:01
dougwigno20:02
dougwigok, what do you recommend?20:03
bloganreading about alembic branches20:03
blogandougwig: branches require the parent to be in the same directory, so it goes back again to telling alembic to look in multiple locations for migrations20:05
dougwighmm, neutron-db-manage could copy them all into a tmp directory.  (gross)20:05
*** mwang2 has joined #openstack-lbaas20:05
blogandougwig: yeah, but gbp had to have had this same problem20:05
bloganI've already asked SumitNaiksatam but he's afk20:05
dougwigping rkukura20:05
dougwighe's sitting next to me if he doesn't reply20:06
bloganhe worked on gbp?20:08
*** vjay7 has quit IRC20:09
dougwigyes.  and he's the one that brought up their alembic implementation to me.20:12
blogandougwig: okay think i got it now, one sec20:16
dougwigk20:17
blogandougwig: we want neutron-db-manage to use this correct?20:22
blogannot have our own client20:22
*** BB_ has joined #openstack-lbaas20:22
blogani mean all services uses neutron-db-manage20:22
dougwigi think that'd be cleaner, but if separate scripts makes life easier, i'm sure we can doc it.20:22
dougwigclenaer for the user, not cleaner for us.20:22
BB_hello. I configured LBAAS according to link http://docs.openstack.org/admin-guide-cloud/content/install_neutron-lbaas-agent.html20:23
bloganyeah, its cleaner for the user20:23
BB_i would like to configure them, like VM-A talks to VM-B using LB.20:23
BB_Is there a link explaining that configuration ?20:23
BB_Folks, any help on configurtion ?20:33
dougwigBB_: sorry, we're in the midst of splitting repos from neutron, so are all a bit distracted just now.20:39
dougwigare you around later?20:39
openstackgerritBrandon Logan proposed openstack/neutron-lbaas: Initializing alembic for separate chain  https://review.openstack.org/14047220:41
blogandougwig: ^^ won't work without neutron-db-manage fix which I will do after an appointment i have to make20:41
bloganso I'll have it done by tonight20:41
blogandougwig: however you can test with the cli.py file in that review20:42
bloganwhoops didn't mean to keep one of those files20:42
*** crc32 has joined #openstack-lbaas20:42
openstackgerritBrandon Logan proposed openstack/neutron-lbaas: Initializing alembic for separate chain  https://review.openstack.org/14047220:43
openstackgerritBrandon Logan proposed openstack/neutron-lbaas: Initializing alembic for separate chain  https://review.openstack.org/14047220:44
johnsomdougwig: For the devstack task, I am guessing we want vpn/fw/lbaas to become "extras", in extras.d?20:47
dougwigi've never modified devstack, so your guess is as good as mine.20:47
johnsomGrin.  I see that opendaylight is setup that way.  Does anyone else in the room have an opinion?20:48
dougwigmy only opinion is that all the existing conf files that specific q-lbaas or whatnot work before and after, just with an extra package installed.20:49
sballejohnsom: I looked at this too. Why wouldn't you just add it to the lib/neutron? and  stackrc?20:51
sballeThey are core services and not plugins like opendaylight20:51
johnsomOk.  That was what I was trying to figure out.  That is a lot easier too.  Thanks sballe20:52
sballejohnsom: that was just my gut feeling when I looked at it20:52
*** sbfox has quit IRC20:59
xgermandougwig, so for the tests we are pulling in the config from neutron -- is this ok or do we want our own config?21:25
xgermanneutron-lbaas/.venv/src/neutron/neutron/tests/etc/neutron.conf.test21:26
*** vivek-ebay has quit IRC21:31
*** mestery_ has joined #openstack-lbaas21:37
*** mestery has quit IRC21:38
*** mlavalle has quit IRC21:39
BB_dougwig: okay. let me know when you guys are fre21:44
*** mestery_ is now known as mestery21:51
*** cipcosma has quit IRC21:51
dougwigxgerman: fine to pull in neutron config21:52
*** mlavalle has joined #openstack-lbaas21:53
*** xgerman_ has joined #openstack-lbaas21:58
SumitNaiksatamdougwig: blogan: for gbp we have an independent migration script, if that was the question22:23
*** vivek-ebay has joined #openstack-lbaas22:25
dougwigblogan found ivar.  review is linked above.22:25
blogandougwig, SumitNaiksatam: i have a feeling that if we want neutron-db-manage to manage all services, we're going to have to modify neutron's env.py, but im about to start working on that closely22:29
SumitNaiksatamblogan: okay22:30
dougwigneutron changes are relatively easy today and tomorrow.  :)22:30
bloganyes i know, which is hwy i want to get this done quickly22:31
bloganas im sure you do too22:31
bloganas well as everyone22:31
*** blogan_ has joined #openstack-lbaas22:32
*** SumitNaiksatam has quit IRC22:37
*** sballe is now known as sballe_mobile22:38
*** sballe_mobile is now known as sballe22:38
*** SumitNaiksatam has joined #openstack-lbaas22:48
dougwigplugin shims - https://review.openstack.org/#/c/140515/22:59
*** mikedillion has joined #openstack-lbaas23:16
blogan_sweet, dont have to make changes to neutron migration's env.py23:17
blogan_dougwig: which do you prefer neutron-db-manage -service lbaas,fwaas,vpnaas runs migrations for all 3 advanced services, but not neutron, or runs for all 3 AND neutron23:18
blogan_--service23:18
blogan_first option may as well just be its own client, while the second one seems more in line with a unified client23:20
*** mikedillion has quit IRC23:23
dougwigi don't have a strong opinion.23:23
*** mikedillion has joined #openstack-lbaas23:24
blogan_im going to do the second option23:29
*** sbfox has joined #openstack-lbaas23:36
*** ajmiller has quit IRC23:36
dougwigok23:37
dougwigthe neutron mass delete is in the merge queue!23:37
dougwig+36, -2498223:37
blogan_yowzers23:39
blogan_gut that pig23:39
blogan_well im dumb for not thinking of this23:40
blogan_if someone does a neutron-db-manage upgrade <migration_name> it will only work for one of the four23:41
*** mestery has quit IRC23:50
*** ptoohill_ has quit IRC23:52
blogan_im just going to do one at a time23:53
dougwigok23:56
dougwigat some point, they'll have to do the flows separately.  and the packager can script doing four as easily as one.23:57
*** ptoohill_ has joined #openstack-lbaas23:57
blogan_yeah we'll have our own client at some point, and it won't be hard23:57
blogan_then again this is going to require almost the same amoutn of work as if we had our own client23:58
blogan_as in now devstack is going to have to run neutron-db-manage with the --service for each service, and without the --service for neutron23:59
blogan_ill get it up in review though, and people can comment on it23:59
*** crc32 has quit IRC23:59
*** mestery has joined #openstack-lbaas23:59
dougwigok23:59

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