Monday, 2014-07-21

*** woodster__ has quit IRC01:15
*** fnaval has quit IRC01:28
*** fnaval has joined #openstack-lbaas01:29
*** fnaval has quit IRC01:33
*** mestery has joined #openstack-lbaas01:42
*** mlavalle has quit IRC02:43
*** woodster__ has joined #openstack-lbaas02:52
ctraceydougwig: you saying that session_persistence is wrong in client or API?04:09
dougwigblogan didn't use any underscores.   and I didn't pass it at all.04:10
ctraceyit does use underscores unless that has recently changed04:13
ctraceydougwig: https://github.com/oslbaas/neutron/blob/bp/lbaas-api-and-objmodel-improvement-haproxy-driver/neutron/extensions/loadbalancerv2.py#L22704:15
ctraceybut i am confused as to why it is not sticking on the backend04:15
ctraceyeven when I pass it04:15
bloganhello05:18
dougwigheya05:19
dougwigctracey: sec, looking into it on my end.05:20
blogandougwig: what are saying about the plugin holding off telling the drivers about the listeners?05:21
dougwigjust that it looks like when the "parent" gets created, the downhill notification is auto-magic because of how the foreign keys are setup.05:22
dougwigassuming any model change triggers a driver call, that is.05:22
dougwighaven't gotten things running end-to-end enough to test it.05:22
bloganwell the plugin still does a check on all non loadbalancer CUD calls to see if it is linked to a loadbalancer, and if it is it sends it to the driver05:23
bloganis that what you mean?05:25
dougwigsort of; but it's a second order issue for me right now.  still trying to get things up enough to pass to the drivers at all.05:26
dougwigthis should go on the todo list somewhere:05:26
dougwig blogan: for 105610, can you swap LOADBALANCERV2 for LOADBALANCER, for the noop driver, in etc/neutron.conf?05:27
bloganyeah i can do htat, i got another change going into the one before that, but im holding off until tomorrow05:27
bloganill update both in the same chain rebase05:28
bloganyou get over that migration issue about lbaas_listeners being missing?05:28
bloganoh yeah step in devstack05:28
dougwigyes, i somehow had stale crap in my neutron db, which is odd, considering it was a fresh devstack.05:28
bloganshould checkout the review first, then run devstack05:28
dougwigi edited the wiki with all the tweaks i had to make.05:29
blogandid you put in that you should check hte review out first then run devstack?05:29
bloganof cours ethat would assume neutron was there first05:30
bloganoh yeah ctracey: api is session_persistence05:32
dougwigblogan: i got it working the other way around, actually.  well, "working".05:33
bloganneutron-db-manage?05:33
dougwigthe db is correct, neutron server is running the new bits and the drivers are initializing.05:33
dougwigfirst drop tables, then db-manage, yes.05:33
dougwigi just had the cli problems above, and hadn't done anything straight to the api yet.05:34
bloganhmm05:38
*** blogan_ has joined #openstack-lbaas05:49
blogan_can't recreate what the pastebin showed the cli was returning06:01
blogan_im hitting the sack, see ya tomorrow06:07
*** blogan_ has quit IRC06:07
*** woodster__ has quit IRC07:35
*** enikanorov__ has quit IRC09:52
*** evgenyf has joined #openstack-lbaas10:45
*** HenryG_afk is now known as HenryG12:12
*** woodster__ has joined #openstack-lbaas12:52
*** samuelbercovici has joined #openstack-lbaas12:58
*** fnaval has joined #openstack-lbaas13:06
*** sballe has joined #openstack-lbaas13:54
*** samuelbercovici1 has joined #openstack-lbaas13:58
*** samuelbercovici has quit IRC14:01
*** samuelbercovici1 is now known as samuelbercovici14:01
*** fnaval has quit IRC14:10
*** rolledback has joined #openstack-lbaas14:13
*** samuelbercovici1 has joined #openstack-lbaas14:16
*** samuelbercovici has quit IRC14:19
*** samuelbercovici1 is now known as samuelbercovici14:19
*** fnaval has joined #openstack-lbaas14:36
sballeMorning15:02
*** openstackgerrit has joined #openstack-lbaas15:02
*** sbfox has joined #openstack-lbaas15:06
*** sbalukoff has quit IRC15:07
*** xgerman has joined #openstack-lbaas15:12
*** jorgem has joined #openstack-lbaas15:40
*** sbfox has quit IRC15:44
*** TrevorV_ has joined #openstack-lbaas15:45
*** TrevorV_ has quit IRC15:46
bloganhello15:53
bloganall15:53
*** mestery has quit IRC15:55
TrevorVhi16:03
TrevorVblogan16:03
TrevorVhow16:03
TrevorVgoes16:03
TrevorVit16:03
bloganhi TrevorV16:03
bloganwho are you?16:03
*** evgenyf has quit IRC16:05
*** markmcclain has joined #openstack-lbaas16:17
bloganmarkmcclain: do you know if mestery will be on today?16:22
markmcclainblogan: he should be back today16:23
bloganmarkmcclain: or if you can shed some light on a question, we have two specs that need to be accepted into juno-3, but they haven't yet, they're the tls and l7 specs.  I think mestery will be up to accepting them today if we can get it in today.16:24
bloganmarkmcclain: would you agree?16:24
markmcclainblogan: let me check the list16:25
markmcclainl7 should get an approval16:26
*** mlavalle has joined #openstack-lbaas16:26
bloganmarkmcclain: that woudl be great, but I think tls is probably just as, if not more, important16:26
markmcclaintls is tied to barbican16:27
markmcclainso that's causing a bit of project sync issue which is why it's on the fence16:27
samuelbercovicihi all16:28
samuelbercovicimarkmcclain: what is the "project sync" issue at hand?16:29
blogansameulbercovici: i'm assuming its because what our tls spec requires from barbican ismerged in yet iether16:31
markmcclainit's more bureaucratic that barbican is on track for graduation16:31
samuelbercovicimarkmcclain: the bp can be approved with the pre-condition that if barbican will not be graduated, this will be delayed16:32
samuelbercoviciright?16:32
markmcclainyeah it's more finding space for it… concerned that the v2+L7 is a huge backlog to clear16:34
markmcclainI think the promise to delay seems acceptable16:34
markmcclainif the other work gets backed up16:35
samuelbercovicisore.16:35
samuelbercovicisure16:35
samuelbercoviciapproving the BP just gives us the green light to work on this.16:36
samuelbercoviciwith the hope that we can make it to the release16:36
blogan+1 sam16:36
jorgemAdam told me that the Barbican work was implemented and pending review.16:37
markmcclainjorgem: go to know16:37
jorgemHe's out today but I'm trying to get more details from him16:37
*** markmcclain has quit IRC16:38
jorgemI scared mark away :(16:38
jorgemlol16:39
bloganway to go jorge16:39
samuelbercoviciLOL16:39
jorgemHere is the work Adam completed ==> https://review.openstack.org/#/c/107845/16:40
samuelbercovicithis is nice work. it is not even mandatory thought.16:41
jorgemWhich item is mandatory?16:42
*** markmcclain has joined #openstack-lbaas16:42
jorgemI don't think any of them are from what Adam & Carlos told me. Thus TLS is not blocked.16:42
jorgemThere work was meant to make it easier.16:42
samuelbercovici+116:43
samuelbercovicithe only work which may be needed, not sure where it will reside is the libraries carlos is doing16:44
samuelbercovicihi mark16:45
*** evgenyf has joined #openstack-lbaas16:56
dougwigblogan: you're not seeing the two errors i hit?  (not the non-default stuff; i can work around that.)16:58
blogandougwig: which two errors?16:59
blogansession_persistence?16:59
bloganbrb16:59
dougwigthese two:16:59
dougwighttps://www.irccloud.com/pastebin/FP493i5F17:00
dougwighey folks, last chance to give +1's to blueprints you really want: https://etherpad.openstack.org/p/lbaas_reviews17:02
dougwig(possibly past last chance, but hey.)17:02
*** rolledback has quit IRC17:10
*** samuelbercovici has quit IRC17:21
*** evgenyf has quit IRC17:22
dougwigblogan, i assume you renamed something?17:23
dougwig./neutron/tests/unit/services/loadbalancer/drivers/a10networks/test_thunder_driver.py:19:1: H302  import only modules.'from neutron.tests.unit.db.loadbalancer import test_db_loadbalancerv2' does not import a module17:23
dougwignope, looks like my rebased repo is messed up.17:24
*** barclaac|2 has quit IRC17:29
*** mestery has joined #openstack-lbaas17:33
*** mestery has quit IRC17:33
*** mestery has joined #openstack-lbaas17:34
bloganah taht session_persistence is probably broken in the haproxy driver17:42
bloganmestery: can we get these 3 specs approved today: https://review.openstack.org/#/c/98640/ https://review.openstack.org/#/c/99709/  https://review.openstack.org/#/c/100931/17:45
mesteryblogan: I'll see what I can do. Given these are all LBaaS specific, I'm inclined to approve them post-SAD (today), and if they land, they land.17:47
mesteryblogan: Makes sense?17:47
bloganyou mean if the code is completed and reviewed in time then it would be able to land?17:47
bloganmestery: ^^17:48
mesteryblogan: Correct17:49
*** sbfox has joined #openstack-lbaas17:49
bloganmestery: are there major issues with approving the spec but, in the case of tls, if barbican is not ready then don't merge the code in?17:50
bloganmestery: or is it just more the volume of changes that lbaas is getting that you'd rather just take the wait and see approach?17:51
mesteryblogan: I think a little of both to be honest17:51
bloganmestery: ok understood, would you mind if i sent out an email to the lbaas group quoting you on if the code is fully implemented and fully reviewed then it can go into Juno?17:53
bloganmainly beacuse people may freak out if they see it didnt get accepted in time17:53
bloganthe specs that is17:53
mesteryblogan: Yes, though for TLC, the barbican question is slightly open still17:54
dougwigfor tls & l7, we also need to get the driver changes/object change info out to the vendor driver authors before the last possible second, or those two items will *only* be in the ref driver.17:54
bloganmestery: ok i'll make a point to mention that, is it because of the uncertainty that barbican will have everything needed for tls? or some other issues we are unaware of?17:54
mesteryblogan: The main uncertaintiy is around if barbican will graduate or not, I think that's it.17:55
bloganmestery: ah okay thanks, ill mention that.  appreciate your patience17:55
dougwigblogan: one sec on that email.17:57
blogandougwig: im starting to think we may not have enough time to the older drivers updated with tls and l7, that woudl be the shim that woudl do that right?17:57
blogandougwig: okay17:57
dougwigmestery: what's the last day for code submissions for juno-3?17:57
mesteryblogan: https://wiki.openstack.org/wiki/Juno_Release_Schedule17:57
mesteryblogan: Sept 4 if code is already submitted17:58
*** fnaval has quit IRC17:58
dougwigaug 21 is code not submitted?17:58
*** sbalukoff has joined #openstack-lbaas17:59
dougwigif17:59
bloganmestery: i'm kind of reiterating jorge's question here, but july 20 was the last day for the specs to be accepted, where is that date specified?17:59
mesteryblogan: That was in an email which I sent, I can dig it out.18:00
dougwigblogan: i think we need like an august 14th deadline or something for the tls/l7 ref changes submitted, then.  we've got 3 vendors at present writing new drivers, that will need at least a little time to respond in kind.18:00
mesteryblogan: I think it was 2-3 weeks ago.18:01
mesteryblogan: SPD/SAD is something which nova and neutron took part in.18:01
mesteryTo try and control the spec rush near the end.18:01
dougwigit was mentioned at every neutron and lbaas irc meeting for the last several weeks.18:01
bloganmestery: no dont dig it out I was just wondering if it was wikified18:01
blogandougwig: obviously im just ignorant18:02
bloganbeen hard to keep up with everything18:02
dougwigha, just saying that i haven't seen it on any official release wikis.  i just heard about it at meetings.18:02
blogani shall get better though!18:02
bloganonce the rush dies down18:02
bloganone does SPD and SAD stand for?18:03
blogannvm found it18:04
bloganspec proposal deadline, spec approval deadlilne18:04
dougwigopenstack does like its acronyms.18:05
blogandougwig: still hold of on sending that email?18:07
dougwigsorry, i sent this as food for thought on deadlines for the email: "blogan: i think we need like an august 14th deadline or something for the tls/l7 ref changes submitted, then.  we've got 3 vendors at present writing new drivers, that will need at least a little time to respond in kind."18:07
dougwigor we need to somehow communicate the object changes before the ref driver is submitted.18:08
blogandougwig: are they writing new drivers only, or are they also going to implement tls adn l7?18:08
dougwigis there a difference?18:09
dougwigas in, i don't know, but we should give them a fighting chance.18:09
bloganwell there is because they will probably want to base their cdoe off a review that hast he tls adn l7 object model changes vs only the v2 lbaas18:10
*** rolledback has joined #openstack-lbaas18:11
dougwigpersonally, i expect to submit two reviews in the juno-3 timeframe; the first based off of v2, the second with additions based on l7/tls.  i'm not sure it's wise for anyone to wait until the latter review is ready.18:11
bloganwhat im getting as is i want to be clear about what exactly needs to go in by august 14th: just new driver interface implementation of their drivers, or that and tls and l718:11
*** rolledback has quit IRC18:11
dougwigi think we just need to let them know what the interface will be; i don't care if it's pre-release, or WIP, or a google doc.18:11
*** rolledback has joined #openstack-lbaas18:12
bloganokay well im pretty sure we have a consensus on the L7 and tls stuff so that can easily be derived18:12
dougwigi agree, just want to make sure we prioritize the interface changes, because several people have to serialize around that point.18:12
bloganokay so is it agreed that vendors can't just implement l7 and tls in their old drivers and expect the shim to do some kind of translation so their old drivers can still do tls/l7, which I'm pretty sure wouldn't even be possible so its probably a moot comment18:13
bloganor question18:13
bloganjust thinking about how todo that hurts my brain18:14
dougwigoh hell no.18:18
dougwig:)18:18
dougwigi hadn't even ever considered it.18:18
dougwigdamnit, i think i screwed up your gerrit commits.  and i'm not even sure how, except that a git rebase on a gerrit review branch must've auto-propagated (and seemingly not in the way that it looks in my tree.)18:19
dougwigcan you look?18:19
*** sbfox has quit IRC18:20
xgermandougwig it seems your last review pulled some constant changes18:20
dougwigif you look here: https://review.openstack.org/#/c/105331/13/neutron/plugins/common/constants.py,unified18:20
dougwigi definitely undid some constants changes.  in a way that's opposite to how the merge looks locally.18:21
xgermanthanks,18:21
xgermanMichael was asking...18:22
bloganlol dougwig what did you do18:22
dougwigpull brandon's n-1 changesets.18:22
*** johnsom has joined #openstack-lbaas18:22
dougwigblogan: i don't even know!18:22
bloganwhat did you intend on pushing up?18:22
dougwigi added a line to neutron.conf, ran 'git review', it said some things about auto-rebasing dependencies, magic happened.18:23
dougwigbad, bad magic.18:23
bloganlol18:23
blogani was going to add that in the other one i thought18:24
dougwigthis was avendor specific one.18:24
dougwiga vendor18:24
bloganah okay18:24
dougwigok, what's the best way to rollback?18:24
blogani can do it18:25
dougwigok, thanks.18:25
bloganwell if you want to go ahead18:25
bloganbut i can do it quickly, and add your change if you want18:26
dougwigplease, go for it.  i think i'd have to setup your four branches and submit each separately, so it'd take me a bit.  i managed to screw up five changesets with one branch.18:26
bloganlol18:26
bloganwell i was planning on pushing code up to this one anyway18:27
bloganso it would have caused the chain reaction18:27
bloganwhat change did you need to make though?18:27
TrevorVIs anyone else having issues using dev-stack right now?  My neutron is failing with a DB issue.18:28
dougwigif you pulled in the last 20 minutes, it's broken. standby.18:29
dougwigif not, please paste the error.18:29
TrevorVI pulled before I went to lunch.  Like, over an hour ago18:29
dougwigis the error by chance about a missing lbaas.listeners table?18:30
TrevorVDetected added foreign key for column 'id' on table u'ml2_brocadeports'18:30
TrevorVthat's what mine was18:30
TrevorVorrr... maybe that's just an INFO and not the actual failure18:31
TrevorVHold on18:31
TrevorVdougwig, blogan says to give him a minute and I'll pull and see if I still have a problem18:33
bloganxgerman: do you know what michael johnson ws referencing with his comment : "Looks good. One note about including a gerrit comment in the code."?18:38
johnsomblogan: Hi.  I think Gerrit ate my comment18:40
bloganlol i was looking for mjohnson in the userlist, i forgot you were johnsom18:41
blogangerrit does like to eat comments18:41
xgermanhungry gerrit? especially around lunch time?18:42
bloganlol dougwig you managed to change the topic as well18:43
dougwigfuck me.18:43
blogangerrit already did that18:43
johnsomThere was a discussion about the exceptions and the extension loading magic.18:44
ptoohilllol18:44
johnsomIts the extension loading magic that happens with neutron. Even though they are separate REST urls, the extension loading stores the resources in a dictionary with the keys being the resource names. So with two resources named 'pools', it does a dictionary.update() if the resource already exists. Tough for me to explain but the code is here:18:44
johnsomto quote18:44
*** evgenyf has joined #openstack-lbaas18:45
bloganah yeah i remember typing that up, but i still dont understand what you mean gerrit comment though?18:45
bloganyou mean my code comments that mention to remove it once the v1 is totally gone?18:45
*** TrevorV_ has joined #openstack-lbaas18:46
johnsomI didn't see those comments in the code.  I just thought it would be a good idea to include the reason in code comments as it could come up later.18:48
bloganjohnsom: ahh, i didn't put comments on that particular exception that oleg was commenting about but I did later in the extension definition where I made the extension define the attributes that were nto required and also in the plugin code where it raises that particular exceptions18:50
*** mestery has quit IRC18:51
johnsomAh, ok18:52
*** mestery_ has joined #openstack-lbaas18:56
*** mestery_ has quit IRC18:57
*** mestery has joined #openstack-lbaas18:57
*** sbfox has joined #openstack-lbaas18:58
*** sbfox has quit IRC19:15
*** enikanorov_ has joined #openstack-lbaas19:16
mesteryblogan: I just went +2 on all 3 BPs, waiting for markmcclain to also +2 and then he or I can +A them.19:21
mesteryblogan: Thanks for your and all the LBaaS team members work in this area!19:21
bloganmestery: the specs?19:23
mesteryblogan: Correct, the specs19:23
bloganmestery: awesome, thanks a bunch on that!19:24
mesteryblogan: no problem sir!19:25
dougwigmestery: thank you!19:25
mesterydougwig: sure!19:26
*** sbfox has joined #openstack-lbaas19:34
dougwigok, git is happy again.  many thanks, blogan19:35
*** evgenyf has quit IRC19:38
*** fnaval has joined #openstack-lbaas19:42
blogandougwig: lets wait to see if gerrit is happy19:43
*** evgenyf has joined #openstack-lbaas19:44
sbalukoffmestery: That's great! Thanks!20:05
*** Youcef has joined #openstack-lbaas20:06
*** rolledback has quit IRC20:15
*** evgenyf has quit IRC20:15
*** rolledback has joined #openstack-lbaas20:19
*** sbfox has quit IRC20:28
*** sbfox has joined #openstack-lbaas20:34
*** rolledback has quit IRC20:43
*** jorgem has quit IRC21:01
*** fnaval has quit IRC21:12
*** fnaval has joined #openstack-lbaas21:22
*** TrevorV_ has quit IRC21:29
*** mestery has quit IRC21:33
*** dlundquist has joined #openstack-lbaas21:35
sbalukoffmarkmcclain: Will you have time today to look at the specs that Kyle has +2'ed to see whether y'all are comfortable merging these?22:00
*** fnaval_ has joined #openstack-lbaas22:00
*** fnaval has quit IRC22:01
*** fnaval_ has quit IRC22:05
*** fnaval has joined #openstack-lbaas22:06
markmcclainsbalukoff:22:11
markmcclainsbalukoff: yes22:11
mlavalleblogan: when re-starting the neutron server (q-svc) I get the folowwing: 2014-07-21 22:13:56.898 15583 TRACE neutron     dirs = self._retrieve_deployed_instance_dirs()22:15
mlavalle2014-07-21 22:13:56.898 15583 TRACE neutron   File "/opt/stack/neutron/neutron/services/loadbalancer/drivers/haproxy/nonagent_namespace_driver.py", line 144, in _retrieve_deployed_instance_dirs22:15
mlavalle2014-07-21 22:13:56.898 15583 TRACE neutron     return [dir for dir in os.listdir(self.state_path)22:15
mlavalle2014-07-21 22:13:56.898 15583 TRACE neutron OSError: [Errno 2] No such file or directory: '/opt/stack/data/neutron/lbaas/v2'22:15
bloganmlavalle: ahh fresh system bug catch22:16
mlavalleblogan: I am glad I caught my first lbaas v2 bug :-)22:16
bloganmlavalle: ha first of many i'm sure22:16
bloganmlavalle: to be fair this is a WIP review22:17
bloganmlavalle: to get around this you can either create that directory on your system or use the loggingnoop driver22:17
mlavalleblogan: just create the directory empty?22:18
bloganmlavalle: yep22:18
*** dlundquist has quit IRC22:18
mlavalleblogan: ok…. one other thing…. in the instrctions in the wiki, you indicate to stop the neutron service in the screen utility…. It would be clearer if you state that the screen name is q-svc22:19
mlavalleblogan: actually, if you are ok with it, I can fix it22:20
bloganmlavalle: sure you can fix it, dougwig added that so I will blame him again22:20
bloganfeels great shifting blame to other people, i'd be a good politician22:20
mlavalleblogan: ok, I blame dougwig as well, so it's official22:21
* dougwig is soaking in in the blame.22:21
dougwigi'm not sure i edited the part in question, but i'll take the blame anyway.22:22
bloganlol22:22
*** fnaval_ has joined #openstack-lbaas22:22
*** fnaval has quit IRC22:25
mlavalleblogan: the v2 in /opt/stack/data/neutron/lbaas/v2 is also a directory?22:25
bloganmlavalle: that is correct22:25
*** dlundquist has joined #openstack-lbaas22:26
sbalukoffmarkmcclain: Thanks!22:26
xgermansbalukoff here is another doc review for you https://review.openstack.org/#/c/108517/22:26
bloganxgerman: is that the official api docs for the v2 lbaas api?22:27
xgermansbalukoff +122:27
xgermanblogan, yes. Min is creating them22:27
bloganxgerman: is she just using libra as a central place to store it or is this part of libra?22:28
sbalukoffxgerman: I'll have a look, eh!22:28
xgermansorry, I got confused22:28
xgermanthat might be the one libfra change I asked her to look at22:29
xgermantoo many parallel conversations22:29
bloganxgerman: still hung over from germany's world cup win?22:29
mlavalleblogan: next problem: 2014-07-21 22:26:27.070 18958 TRACE neutron ProgrammingError: (ProgrammingError) (1146, "Table 'neutron_ml2.lbaas_loadbalancers' doesn't exist") 'SELECT lbaas_loadbalancers.tenant_id AS lbaas_loadbalancers_tenant_id, lbaas_loadbalancers.id AS lbaas_loadbalancers_id, lbaas_loadbalancers.name AS lbaas_loadbalancers_name, lbaas_loadbalancers.description AS lbaas_loadbalancers_description,22:29
mlavallelbaas_loadbalancers.vip_subnet_id AS lbaas_loadbalancers_vip_subnet_id, lbaas_loadbalancers.vip_port_id AS lbaas_loadbalancers_vip_port_id, lbaas_loadbalancers.vip_address AS lbaas_loadbalancers_vip_address, lbaas_loadbalancers.status AS lbaas_loadbalancers_status, lbaas_loadbalancers.admin_state_up AS lbaas_loadbalancers_admin_state_up, providerresourceassociations_1.provider_name AS providerresourceassociations_1_provider_name22:29
mlavalleproviderresourceassociations_1.resource_id AS providerresourceassociations_1_resource_id \nFROM lbaas_loadbalancers LEFT OUTER JOIN providerresourceassociations AS providerresourceassociations_1 ON lbaas_loadbalancers.id = providerresourceassociations_1.resource_id' ()22:29
bloganmlavalle: i knew that would happen22:30
bloganmlavalle: restack22:30
xgermanbloga, yep. I asked my kids every day "Who is world champion?" :-)22:30
bloganmlavalle: or there is a neutron-db-manage command22:30
mlavalleblogan: just type "neutron-db-manage"22:31
dougwigmlavalle: it'll be: "neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head"22:33
blogandougwig: i believe that is correct22:33
bloganshould add taht in the wiki too22:33
blogani didn't test the wiki out step-by-step, my bad!!22:34
mlavalledougwig: and after that restart neutron-server, right?22:34
dougwigyes.22:35
bloganyes22:35
* mlavalle trying22:35
dougwig(ideally neutron-server isn't running during the migration.)22:35
mlavalledougwig: yeah…. neutron server is down at this moment22:35
mlavalledougwig, blogan: from neutron-db-manage sqlalchemy.exc.OperationalError: (OperationalError) (1050, "Table 'lbaas_healthmonitors' already exists") "\nCREATE TABLE lbaas_healthmonitors (\n\ttenant_id VARCHAR(255), \n\tid VARCHAR(36) NOT NULL, \n\ttype ENUM('PING','TCP','HTTP','HTTPS') NOT NULL, \n\tdelay INTEGER NOT NULL, \n\ttimeout INTEGER NOT NULL, \n\tmax_retries INTEGER NOT NULL, \n\thttp_method VARCHAR(16), \n\turl_path22:37
mlavalleVARCHAR(255), \n\texpected_codes VARCHAR(64), \n\tstatus VARCHAR(16) NOT NULL, \n\tadmin_state_up BOOL NOT NULL, \n\tPRIMARY KEY (id), \n\tCHECK (admin_state_up IN (0, 1))\n)\n\n" ()22:37
markmcclainI've +2'd the TLS specs22:37
markmcclainhad comments on the L7 spec… I like blogan's suggestion of nested relationship22:38
bloganmarkmcclain: yeah! though I don't think it will be easy with the extension resource loader22:39
dougwigmlavalle: stale db; open with mysql (mysql -u root neutron_ml2), and drop all the existing lbaas tables.  then re-migrate.22:41
* mlavalle trying22:42
bloganmlavalle: yeah migrations won't handle that gracefully22:43
blogani debated using drop if exists but no one else did in previous migrations so I didn't, just so the down migration would work22:43
sbalukoffmarkmcclain and blogan: If holding off for a nested relationship model means we don't get L7 switching until Kilo, then I would advocate going for the relatively simple L7 policy / rule structure outlined in the spec.22:45
sbalukoffAlso, the spec essentially lays out what we'd talked about on the mailing list for several months. It's a little frustrating to get told we need nested relationships now. :P22:46
blogansbalukoff: blame me, I was too focused on other things to really focus on those specs22:46
sbalukoffAlso, in my experience, it's extremely rare to need advanced logic in an L7 rule. :P Something like 95% of the policies we see in production consist of 1 rule looking for a hostname or URL path.22:47
sbalukoffMost application developers perfer to do advanced application logic in the application layer, not the load balancer.22:48
bloganso you're saying no need for L7? great!22:49
blogankidding22:49
sbalukoffblogan: Haha! I'mma come break your knees.22:49
dougwigsbalukoff: i have a pile of counter-examples, but i expect you're correct for the consumer level stuff.22:49
sbalukoffLook, if y'all think we can get nested relationships in time for Juno (and by that, I mean, convince the people representing vendors whose products probably won't support this anyway), then that's great...  but I'd really rather not delay until Kilo for layer 7 switching.22:51
sbalukoffWould it be a terrible liability to support L7 switching as suggested in the spec?22:51
sbalukoff(Would this prevent us from using nested relationships in a version 2 of this design?)22:51
bloganisn't this a version 2 already though?22:52
bloganand changing teh API contract is a huge deal22:52
sbalukoffblogan: Are you anticipating zero API changes between Juno and Kilo?22:52
sbalukoffI'm not...22:52
bloganmore like API additions, not deprecations22:52
bloganadding thigns to an API is not breaking contract22:53
sbalukoffOh! So, do you think this would entail a depreciation?22:53
blogani assumed you meant add the nested relationship in K and deprecate the root l7policy and l7rules22:53
sbalukoffWould nested relationships do away with rool l7policy and l7rules?22:54
sbalukoffReally, I'm not sure how you envision nested relationships working.22:54
bloganhonestly I would hope so, i wouldn't want two ways to do it22:54
bloganlol well i guess im not sure how you are envisioning it either22:55
mlavalleblogan, dougwig: I got the eutron server running. I have to go now, but I will run the tempest test tomorrow22:55
bloganmlavalle: okay cool, you will probably run into erros that happen in the driver so sorry, if that happens often enough try out the LoggingNoop driver22:56
*** sbfox has quit IRC22:56
mlavalleblogan: thanks, will do22:56
*** fnaval_ has quit IRC22:56
sbalukoffOh wait!22:56
sbalukoffblogan: Are you talking about the URL path?22:57
bloganyes22:57
bloganwhat the hell are you talking about?22:57
*** fnaval has joined #openstack-lbaas22:57
sbalukoffSorry... total brainfart.22:57
sbalukoffI thought this had to do with earlier comments about advanced logic.22:57
sbalukoffAND and OR rules, etc.22:58
sbalukoffDerp.22:58
bloganha lol i was wondering why you were bringing that up22:58
sbalukoffYeah... Ok, so what you're suggesting should be a "minor" change to the spec as is.22:58
sbalukoffAnd yes, I'm in favor of it. :)22:58
bloganoh look whos changed his tune!22:58
sbalukoffI'm as wiggly as a worm, eh.22:58
sbalukoffAnd yes-- I will totally change my tune if you show me how I'm being stupid.22:59
*** fnaval_ has joined #openstack-lbaas22:59
bloganthere will still be a challenge in getting the neutron extension loading working with 3rd level resources22:59
sbalukoff(Which isn't that hard, most times.)22:59
blogani bet i can work on that and get it working22:59
sbalukoffIf we have to resort to a fall-back way of doing this which doesn't exactly match the spec, is that a show-stopper?22:59
xgermanI bet - you are the miracle worker here22:59
sbalukoffYes, indeed!23:00
bloganwell the fall-back way is having them as root level objects23:00
bloganorrrr23:00
sbalukoffOr l7rule being a child of l7policy23:00
sbalukoffWhich isn't a bad way to go about it.23:00
*** mlavalle has quit IRC23:00
xgerman+123:01
sbalukoffWell, crapsticks, then! What do we need to change about this spec to get that approved?23:01
blogansince 2nd level subresources work, keep l7policy as a subresource of listener, but then have the l7rules bet be an attribute of l7policy, still store it in its own table but dont represent it in the url23:01
*** fnaval has quit IRC23:01
sbalukoffblogan: And since all the rules are ANDed together, order doesn't matter...  yeah, that could work.23:02
xgermanwell, mestery is busy: https://twitter.com/mestery/status/491353727463194625/photo/123:02
sbalukoffDoing a beta-test of that UDP load balancing session, eh?23:02
xgermanyep, 4 years OpenStack in MN23:03
sbalukoffHeh! The Seattle celebration is this Thursday.23:03
sbalukoffI won't be there, because friends got me tickets to Book of Mormon... but it ought to be fun for those who do go.23:03
bloganah man i missed that when it was here in san antonio!23:04
xgermanyep, I am in San Diego and we don't have much OpenStack23:04
blogani was talking abotu book or mormon23:04
bloganof23:04
blogansbalukoff: even if the L7 spec doesn't get accepted today, it'll probably get accepted soon.  Plus mestery told me that even al 3 of those didn't get accepted and the code landed in gerrit and was fully approved he'd still accept it in Juno23:06
*** markmcclain has quit IRC23:06
sbalukoffOh, heck yes.23:06
blogansbalukoff: so don't worry23:07
bloganabout that at least23:07
bloganI am worried about the shear amount of volume we have to do23:07
sbalukoffYes, looking at this spec, there are other problems, too-- like the all caps constants suggestion you made in revision 17.23:07
xgermanyeah, you got a good bragian23:07
sbalukoffDamn! I'm late for a meeting. BBIAB.23:07
xgermanwell, i would go soft23:07
xgermanon the all caps23:07
xgermanbut yeah, if they need to change by all means23:08
sbalukoffNOT ME, DAMMIT! ;)23:08
bloganalright im headed home23:08
blogantake it easy!23:08
xgermansee ya23:09
*** dlundquist has quit IRC23:12
*** dlundquist has joined #openstack-lbaas23:26
*** fnaval_ has quit IRC23:51

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