19:05:12 #startmeeting Weekly OVSDB meeting 19:05:12 Meeting started Tue May 20 19:05:12 2014 UTC. The chair is Madhu. Information about MeetBot at http://ci.openstack.org/meetbot.html. 19:05:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:05:12 The meeting name has been set to 'weekly_ovsdb_meeting' 19:05:28 #info networkstatic needs a new headset 19:05:37 #info webex needs to work 19:06:12 #vote Hangout +1 0 -1 19:06:33 +1 19:06:33 still learning ;) 19:06:41 #vote +1 19:06:45 #startvote Hangout +1,0,-1 19:06:45 Unable to parse vote topic and options. 19:07:06 Needs the question mark 19:07:13 Like this: 19:07:19 Hangout? +1,0,-1 19:07:25 #startvote hangout ? +1,0,-1 19:07:25 Begin voting on: hangout ? Valid vote options are +1, 0, -1. 19:07:25 Vote using '#vote OPTION'. Only your last vote counts. 19:07:30 #vote +1 19:07:30 #vote +1 19:09:14 #endvote 19:09:14 Voted on "hangout ?" Results are 19:09:14 +1 (2): tbachman, Madhu 19:09:26 #info Brent is raging ;) 19:10:26 Im a QA guy 19:22:45 #link Floating IP Client Commands http://docs.openstack.org/user-guide/content/floating_ip_allocate.html 19:23:13 did that work? 19:24:06 #info Floating IP Client Commands http://docs.openstack.org/user-guide/content/floating_ip_allocate.html 19:57:46 has anyone seen this errer: 19:57:46 io.netty.handler.codec.TooLongFrameException: frame length exceeds 100000: 100154 - discarded 19:58:01 it's coming from ovsdb 19:58:15 at org.opendaylight.ovsdb.lib.jsonrpc.JsonRpcDecoder.fail(JsonRpcDecoder.java:159) [bundlefile:na] 20:27:06 GiovanniMeo is bamf 21:05:22 brb 22:26:25 when trying to run the mininet with ovsdb we are seeing netty exceptions is OpenDaylight controller 22:26:30 WARN i.n.channel.DefaultChannelPipeline - An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. io.netty.handler.codec.TooLongFrameException: frame length exceeds 100000: 100000 - discarded 22:26:36 has anyone seen this 22:56:48 Hsin-Yi Shen proposed a change to ovsdb: BUG-1056 brocastflow is not proper modified after deleting interface https://git.opendaylight.org/gerrit/7270 23:32:59 Madhu Venugopal proposed a change to ovsdb: Adjusting the ovsdb stable/hydrogen dependencies to appropriate Controller, Yangtools dependencies. https://git.opendaylight.org/gerrit/7273 00:07:18 Madhu Venugopal proposed a change to ovsdb: Fixed typo in PortHandler.java. https://git.opendaylight.org/gerrit/7280 00:09:06 Madhu Venugopal proposed a change to ovsdb: Removed convertNeutronIDToKey(String) calls. https://git.opendaylight.org/gerrit/7281 00:11:00 Madhu Venugopal proposed a change to ovsdb: BUG-954: Add support for Neutron port/network delete events for OF1.3 https://git.opendaylight.org/gerrit/7282 00:59:16 A change was merged to ovsdb: Adjusting the ovsdb stable/hydrogen dependencies to appropriate Controller, Yangtools dependencies. https://git.opendaylight.org/gerrit/7273 01:04:20 A change was merged to ovsdb: Fixed typo in PortHandler.java. https://git.opendaylight.org/gerrit/7280 01:06:54 A change was merged to ovsdb: gitreview: add .gitreivew for stable/hydrogen branch https://git.opendaylight.org/gerrit/7262 01:08:47 A change was merged to ovsdb: Removed convertNeutronIDToKey(String) calls. https://git.opendaylight.org/gerrit/7281 01:11:40 A change was merged to ovsdb: BUG-954: Add support for Neutron port/network delete events for OF1.3 https://git.opendaylight.org/gerrit/7282 01:16:44 networkstatic: thanks boss. 01:16:54 course sir 01:17:11 networkstatic: do u think we shud also cherry pick the IPFIX gerrits ? 01:17:26 we have a couple of them ... if u want we can take them over to stable/hydrogen 01:17:48 i think onlu jimoo was using, whatever u think buddy. 01:18:27 getting my manual QA on now, :) 01:18:54 oh dude. pls don't waste time in doing QA sir :) 01:19:01 lets put effort on IT 01:19:07 and let the Scripts handle it for us 01:19:40 lol, i need a working build to verify stuffs tonight, its good, have ones already. 01:19:56 hey guys how was today's meeting? Hated to miss but I was in my session 01:19:57 btw, u needs to DL Veep 01:20:00 sooo good 01:21:28 networkstatic: of course sir. ur review comments are important. both in gerrit and TV shows ;) 01:21:38 haha 01:21:48 Mierdin: it was a good call. Status updates and my UT/IT talk :) 01:22:00 yes, need a little bit of pleasure in our world of living on laptop 01:22:03 u didn't miss that talk much as I bored u the other day :) 01:22:23 one of us need to blog on the diff of UT/IT/SI 01:22:54 do u watch the shows in ur laptop sir ? 01:22:56 might throw into slides real quick while fresh 01:23:02 nah airplay to tv 01:23:02 I have a kick-ass HTPC at home ;) 01:23:12 ah... fancy 01:23:15 man, i stopped the htpc w/ airplay 01:23:19 no maintenance 01:23:43 mainly cause faster to drag to Beamer 01:23:50 i share app :) 01:23:57 AA :) 01:24:07 u have JB ATV2? 01:24:10 or 3 01:24:34 or even better, mac mini 01:24:40 those are awesome 01:24:47 u know my setup :) 01:24:53 i forgot! lol 01:24:54 i cannot afford to use mac-mini 01:24:56 haha 01:25:02 laptop stuffed behind tv 01:25:03 lol 01:25:12 nahh... 01:25:16 too cheap for mini :) 01:25:19 i know i am 01:25:25 mine need PCIE slots 01:25:30 oh ya. that too ;) 01:25:31 those things hold value on ebay like a champ 01:26:27 ooh new intellij update out 01:27:02 am an eclipse guy :) tried intellij but... somehow it is not clicking 01:27:09 maybe i have to put more time into it 01:28:03 networkstatic: btw.. hope u r following on the email thread on the broadcast multiple output port issue 01:28:13 it is an issue on modify flow operation 01:28:20 and is currently being fixed 01:28:30 pls keep in mind during your manual QA :) 01:28:41 DHCP won't resolve until this issue is merged 01:28:55 networkstatic: fyi : https://git.opendaylight.org/gerrit/#/c/7099/ 01:28:57 i am buddy, i saw that earlier, only thing still broken here 01:29:50 im burned out. going back in the cave for a couple days. sure im wearing out my welcome of asking questions 01:30:07 http://monolingual.sourceforge.net just deleted 3Gb of language packs off mac 01:30:20 more room for VMs 01:33:08 networkstatic: take off sir. we need the crazy networkstatic not the sad one :) 01:34:13 sad faces bad :) 01:42:55 madhu it is not possible for you to bore me 01:43:49 oh and btw just ran into edwarnicke at clus 01:43:55 had a baller chat about helium 01:44:06 introduced me as well 01:44:08 I feel important now 01:44:10 ish 01:44:12 not really... 01:49:58 * edwarnicke waves :) 07:29:11 Hi 13:07:55 Madhu Venugopal proposed a change to ovsdb: Commit operation as per Section 5.2.7 of RFC 7047 https://git.opendaylight.org/gerrit/7297 13:07:56 Madhu Venugopal proposed a change to ovsdb: Fixed a bug in where condition usage in Update & Delete operations. Also moved Delete operation to a seperate transaction in the Test code to test multiple transactions. https://git.opendaylight.org/gerrit/7298 13:18:13 MierdinMobile: hello sir. guess u r busy with #CLUS. Need some help with Mutate. 13:18:19 dave_tucker: hey buddy. 13:18:28 hey Madhu! 13:19:27 the IT that we are writing for operations Insert, delete, etc. will not work until we have Mutate 13:19:39 once Mutate is in place, we will need better Asserts :) 13:20:07 regarding Mutate, I am waiting on Matt to address the comments 13:20:56 Madhu: cool 13:20:57 dave_tucker: just fyi. 13:21:14 also, you need to retrigger the job for 7298 in jenkins 13:22:25 code review now done ;) 13:24:09 also we need to fix this IT - https://jenkins.opendaylight.org/ovsdb/job/ovsdb-verify/org.opendaylight.ovsdb$ovsdb_library/412/testReport/org.opendaylight.ovsdb.lib.jsonrpc/TestClient/testBasicFlow/ 13:24:25 as it's a pain in the ass that builds are being marked unstable because of this 13:25:22 oh and I retriggered the build in jenkins for you while I was there 13:25:38 Madhu Venugopal proposed a change to ovsdb: Abort operation as per Section 5.2.8 of RFC 7047 https://git.opendaylight.org/gerrit/7300 13:25:59 thanks sir 13:26:09 your +1s are useful :) 13:26:17 will ask Brent/Ashwin to merge it 13:26:36 i don't want to +2 my own commits :) 13:27:18 dave_tucker: sure. i will take a look @ the basic flow error 13:27:37 brb sir 13:27:38 just need to catch the exception and use a different port 13:27:40 ;) 13:27:52 lets use a different port for this IT period :) 13:28:10 lol. issue is only present when 2 jobs are building at the same time 13:29:00 ya. i mean pick ports randomly between 6640 - 6740 ;) 13:29:11 but then we might have a coliision 13:29:18 so still need logic to handle that ;) 13:29:19 brb sir. 13:29:21 k 13:36:22 when you are back we should chat about my commit you have -1'd :p 13:36:49 am back. :) but before chatting about that, i want to quickly get your opinion on Mutate 13:37:01 we both commented on Matt's Mutate diffs 13:37:23 but since we need that to do proper IT, I am inclined on merging them first and then I will update the tests with mutate operation in place. 13:37:35 Madhu: that works for me 13:37:37 I don't want to get blocked by the absence of Mutate. 13:37:41 okay. lemme merge them now. 13:37:57 waiting for maven before I add the IT for select fyi 13:37:58 now... lets talk about the static table name issue. 13:38:02 yeah :p 13:38:25 so my point is, it doesn't matter.... the constants are a convenience function and you can use them, or not 13:38:38 my point is 13:38:46 but based on the fact that everybody will be defining the same basic set of constants, makes sense to have them in library 13:38:49 the moment you declare it.. it gets first class citizen 13:39:13 I don't want the Table names to get that privilege in the library 13:39:44 We had this extensive discussion and intact am opposed to even having the database name OpenVSwitch given that first class citizen role in the library 13:39:59 well I think we should add the VTEP stuff too 13:40:03 and i also changed that code (will get it out of my stash and push it) 13:40:20 even if it's just to a class full of constants in utils 13:40:24 or something ;) 13:40:35 not in library :) 13:40:40 lemme put it this way 13:40:41 the library itself doesn't care - it just wants a string 13:40:51 if u c it in RFC7047, it gets into library :) 13:41:17 if u don't see it in the RFC, library should not give it a preference. 13:41:30 ashw7n: my man. :) 13:41:35 lol 13:41:47 we are stalkers ;) 13:41:53 dave_tucker: back to the topic 13:42:08 we made the mistake during the Hydrogen release by mixing library and plugin 13:42:13 appreciate your view Madhu. but as a developer, I like convenience.... and it makes it hard to use the library if I have to read the OVSDB schema to get the table names ;) 13:42:35 dave_tucker: that problem will be solved :) once we have plugin operating on Library 13:42:43 + DRY principle. we will have multiple defintions of the same constants 13:42:57 no. we will not :) 13:43:01 ok cool 13:43:06 lemme explain it other way 13:43:12 then in that case I'll abandon and we move this to the plugin 13:43:28 the tests that we are adding to the library now are "temporary" 13:43:31 once plugin is in place 13:43:44 lets get crazy there :) and use these constants and intact I would recommend static typing there 13:43:56 lets also introduce first class tables as classes on the plugin layer 13:44:00 Madhu: I'm not keen on static typing ;) 13:44:01 and add all the nice test-cases there 13:44:17 but we should DEFINATELY have IT/UT in the library 13:44:18 library should be kept clean. IMHO 13:44:39 and that should include the tests we have today (but with more assertions) 13:44:40 ;) 13:44:42 the UT/IT in library should be completely RFC7047 dependent :) 13:45:00 dave_tucker: +10000 on assertions 13:45:02 Madhu: yessir, but you have to test against an implementation 13:45:25 dave_tucker: can u imagine the world am trying to try in the library ? :) 13:45:35 we can use list_dbs :) to get all the databases supported 13:45:48 Madhu: ok yeah that makes sense 13:45:50 and then we can do getSchema to get all the tables and columns in that 13:45:54 with these 2 info 13:46:05 we can test all the tables and individual columns from library 13:46:19 without needing to have a string like "bridge" or "Interface" defined in the Test classes :) 13:46:21 but to do CRUD, we need to understand the schema though 13:46:27 i think 13:46:36 yep. CRUD needs it. but that is in the Northbound layer 13:46:58 well, ok I mean Select + Insert + Update + Delete 13:47:00 but even there :) if we expose the getSchema and list_dbs (which we will) 13:47:13 even Select +insert + update + delete 13:47:20 can be done entirely schema independent 13:47:33 just by getting the info using list_dbs and getSchema :) 13:47:42 because everything u need to know is in there 13:47:46 yeah I guess we just need some test data that matches the expected types as per the RFC 13:47:50 tableName, Column Name, Column Type. etc... 13:48:23 so IMO, library tests should not even have the string "bridge" represented there 13:48:32 Madhu: fair enough sir 13:48:33 we are adding such tests now just to make progress. 13:48:46 once we are in stable grounds all these tests should move to plugin 13:48:51 yeah I know... your reasoning is correct, as always :p 13:48:55 and we will live in a pure Library world :) 13:49:00 lol 13:49:14 where everything is abstract 13:49:21 since Ben & Justin are happy to have this library as ref impl in OVS 13:49:30 its better to be abstract and scalable to any schema 13:49:37 and folks just pick it up and use it :) 13:50:01 dave_tucker: sorry for being religious on this topic. 13:50:10 just trying to avoid the same mistakes that we did for Hydrogen 13:50:40 whenever i see these static values (even in tests), i don't feel comfortable 13:50:42 Madhu: it's fine sir. I was looking at use of the library forgetting that we needed to support multiple schemas. totally makes sense now we've spoken about it 13:50:51 but being practical, am just trying to make sure we make progress too 13:51:00 excellent buddy. 13:51:37 intact once all the operations are done, my plan is to write the abstract and generic test-case 13:51:49 which will ram through all the tables/columns and operations 13:52:07 without the need to have any static typing or strings :) 13:52:11 but that is a lot of work 13:52:40 Dave Tucker proposed a change to ovsdb: Add OVSDB Select Operation https://git.opendaylight.org/gerrit/6861 13:52:53 thanks odp-gerritbot 13:53:02 included your fix for the where's too Madhu 13:53:09 as well as the IT 13:53:15 thanks sir. 13:57:32 Dave Tucker proposed a change to ovsdb: Unit Test Coverage for OvsdbClientImpl https://git.opendaylight.org/gerrit/7122 13:57:45 and that one was rebased and addressed sam's comments 13:58:33 omg networkstatic_ finally cloned himself - networkstatic_zZ 13:58:49 that's too much awesome for one channel 14:01:04 lol 14:01:07 networkstatic_: u there sir ? 14:04:11 Dave Tucker proposed a change to ovsdb: Update .gitreview to use topic/schema branch https://git.opendaylight.org/gerrit/7303 14:04:12 networkstatic: hey buddy 14:16:07 Madhu: ref https://git.opendaylight.org/gerrit/7122 - do u know if we could s/Integration/IT/g with the name of the base class without confusing Maven? 14:18:11 also Madhu we can't merge that until https://git.opendaylight.org/gerrit/#/c/7121/ merges 14:18:47 when writing the UT I noticed that isReady is always true... the timeout in the todo is therefore pointless 14:21:26 "return null != schema;" is always true. Because we init schema when the class is instantiated. 14:21:48 a better check is to see if the list of schemas > 0, which is what was added in 7121 14:30:25 Madhu: if you are still there sir... re-read your comments... would you be happy with this https://gist.github.com/878b3de25df043afbc38 for the timeout 14:36:35 now using isEmpty instead of size - https://gist.github.com/f2beecf462f15eaff1fb 14:41:35 Dave Tucker proposed a change to ovsdb: Stop isReady method always returning true https://git.opendaylight.org/gerrit/7121 14:47:36 Dave Tucker proposed a change to ovsdb: Stop isReady method always returning true https://git.opendaylight.org/gerrit/7121 14:49:03 dave_tucker: hey buddy. 7am+ is challenging :) 14:49:18 be back online in 1 hr. will continue reviewing / merge the code sir 14:52:56 oops. sorry bro forgot it was 7am 16:03:54 Hey Madhu 16:03:59 read some of the chat on my phone 16:04:02 saw you guys were asking about Mutate 16:04:10 Mierdin: hi buddy 16:04:23 I'm not holding you guys up on anything, right? I can take a break from this and make a change if you're waiting on something 16:04:26 yes sir. Mutate is an important operation for us to write proper IT 16:04:43 agreed 16:04:50 it would be awesome if you can get the Mutate pushed 16:05:20 I was inclined to merge the code as is 16:05:34 but I have a few comments and wanted to talk to u first. 16:06:20 I noticed you commented on the commit I assume that's what you'd like me to fix 16:06:39 there is 1 more thing 16:07:23 Mierdin: i was reviewing the value() method : count = (Integer) value; //TODO: Verify this is the right thing to do. Fairly sure from re- 16:07:23 reading RFC but want to make sure. 16:07:57 the "count" member belongs to the result object. 16:08:28 also. a value() method doesn't apply for mutate operation 16:09:12 As we discussed, it is similar to update() but carries specific mutations 16:10:16 ehi guys, 16:10:22 i need some help with ovsdb 16:10:30 gotcha. So not needed? I assumed it needed to be there since the RFC says it returns a "count" object just like Update 16:10:41 i'm trying to rune the autorelease to release ovsdb project 16:10:43 GiovanniMeo: sure 16:10:45 but i noticed 16:10:46 Madhu: And it's good to hear that you'd prefer me to bind the Operations changes with the Mutate changes. I wasn't sure if that was the right way to do it but makes sense now that they should be together, given their relationship 16:10:49 this dependency 16:10:52 org.opendaylight.integration:distributions-virtualization:zip:osgipackage:0.1.2-SNAPSHOT:provided 16:11:11 so this is causing a circular dependency in the release 16:11:21 because ovsdb need the integration 16:11:26 and the integration needs ovsdb 16:11:32 Mierdin: right. typically i prefer smaller commits. but this specific one 16:11:52 Mierdin is hard to catch the issue unless it is in the package of the 3 things (which includes the Test coverage) :) 16:12:09 GiovanniMeo: correct :) 16:12:13 so ? 16:12:14 so i wonder 16:12:34 what you need the distribution for 16:12:36 in here 16:12:37 Madhu: :) test coverage was the next change that I was working on. 16:12:53 so we can see if we can break the circle 16:12:55 somehow 16:13:18 Mierdin: perfect. i don't want to act like an ass... but we are trying to be more organized this time around :) 16:13:38 GiovanniMeo: distribution here is like the same reason all other project has 16:13:49 Madhu: no, not at all! It's like I said, I want to make sure that my contributions are done the right way 16:13:53 for testing OVSDB with their dependent bundles 16:14:20 Mierdin: there is nothing wrong in not adding the tests in the commit (for the master branch and Hydrogen release) :) 16:14:37 GiovanniMeo: this issue is NOT specific to ovsdb I believe 16:14:55 all the other depends on the controller distro 16:14:59 GiovanniMeo: all other projects does the same... they have a distribution which pulls in the dependencies and then builds on their own 16:15:04 not on one from integration 16:15:07 GiovanniMeo: fair enough :) 16:15:18 Madhu: okay so I need to head over to Moscone, but can make the changes. In summary, I need to remove that method entirely, and also merge the change to Operations.java with the addition of Mutate.java. Correct? 16:15:24 I was lazy because we depend on controller and open flow plugin projects 16:15:27 Madhu: I can follow up once out of here with proper UT/IT 16:15:31 so if we build the distro in here 16:15:37 starting from controller base 16:15:43 would you see any issue with that? 16:15:45 Mierdin: thanks 16:16:06 or if we create a distro 16:16:08 GiovanniMeo: not a problem. But we also need the openflowplugin and openflowjava pulled in as well 16:16:29 the trouble we are facing is the version compatibility :( 16:16:39 sure that means ovsdb will be released after openflowplugin and openflowjava 16:16:50 as u know it is all interlinked and that is the reason i made it simple by pulling in the virt edition from integration branch 16:16:51 just looking to break the circular dependency 16:16:55 i will propose a patch 16:17:02 based on this 16:17:04 thx Madhu 16:17:50 sure GiovanniMeo . thanks. 17:16:11 Hsin-Yi Shen proposed a change to ovsdb: BUG-1056 brocastflow is not proper modified after deleting interface https://git.opendaylight.org/gerrit/7270 17:40:14 hello! can someone give me some lights finding how to disable the module that enables reactive forwarding in opendaylight? I've been using the ovsdb nb api to set up some flows, but some of them are overridden by reactive flows 17:42:38 I think it's simple forwarding 17:44:04 A change was merged to ovsdb: Cleaned up Integration Test setup https://git.opendaylight.org/gerrit/7233 17:44:20 CASP3R: thank you. I'll try it out. By that the way, is there any way for disabling a bundle automatically in odl? 17:44:44 Not off the top of my head 17:45:17 ss simple 17:45:35 you can just delete the simpleforwarding jar buddy 17:45:51 from the /plugins directory 17:46:02 yea i know we do that when doing performance testing but didn't know if there a "better' way to do it 17:46:39 ah roger, proper! 17:46:52 it shouldnt be bundled in the next integration releases 17:47:05 enough complained when it was in hydriogen 17:47:24 networkstatic: so right now I could just just remove it from there and put it back in case I need it 17:50:39 A change was merged to ovsdb: Fixed a bug in where condition usage in Update & Delete operations. Also moved Delete operation to a seperate transaction in the Test code to test multiple transactions. https://git.opendaylight.org/gerrit/7298 17:50:40 A change was merged to ovsdb: Commit operation as per Section 5.2.7 of RFC 7047 https://git.opendaylight.org/gerrit/7297 17:52:55 A change was merged to ovsdb: Abort operation as per Section 5.2.8 of RFC 7047 https://git.opendaylight.org/gerrit/7300 17:53:28 yessir rrsantos 17:53:35 ss gives you all of the running modeuls 17:53:37 modules 17:53:46 from the OSGI cli 17:54:22 then u can stop and start based on the PID 17:54:33 number of the module process in the output 17:54:38 stop or start etc 17:54:44 with the number 17:55:34 networkstatic: yes, it is working now. by the way, should I need to set up a rule for sending arp requests to the controller after I disable the simple forwarding? 17:55:55 ah ARP lol, thats a toughy 17:56:26 I need to look at what if anything has been done with arp tracker 17:56:26 hosttracker 17:56:36 doesn;t the ARPhandler do that? 17:56:38 darn, evan isnt on 17:56:50 roger, simple forwarding loads that 17:57:16 i know evan had been working on L2switch 17:57:22 i am just not sure 17:57:33 we use openstak/ovsdb for ARP 17:57:41 or to not need arp :) 17:57:58 the beauty of openstack for networking 17:58:26 much harder problem discovering w/o orchestration 17:59:14 rrsantos: soon as colin dixon or evan are on we can sync u up 18:00:27 networkstatic: thank you :) so a possible solution for handling arp requests after disabling simpleforwarding would be using openstack? 18:01:46 if u want to give openstack a run here are instructions buddy http://networkstatic.net/updated-devstack-opendaylight-vm-image-for-openstack-icehouse/ 18:01:55 and a nwe image 18:04:34 I should give it a try 18:05:03 I've been reading so much things about openstack but never tried it though 18:10:30 odp-gerritbot: wakeup... 18:10:37 ha 18:10:42 dont u snap at odl_meetbot 18:10:48 he will cut you 18:11:08 fiesty little bugger 18:11:45 he is partying too much. 18:11:50 rofl 18:12:44 Dave Tucker proposed a change to ovsdb: Update .gitreview to use topic/schema branch https://git.opendaylight.org/gerrit/7303 18:13:32 Dave Tucker proposed a change to ovsdb: Stop isReady method always returning true https://git.opendaylight.org/gerrit/7121 18:25:36 Madhu: how do you suggest I merge the two commits? 18:27:12 Mierdin: copy/paste and abandon the other? 18:27:30 you could dance with cherry-pick and rebase but it might get confusing quickly 18:30:46 yeah I've done rebase before and know it's not my first choice :) 18:31:18 evanz_: hey bud, you guys done anything significant with the L2Switch yet? If so can u dump usage for rrsantos ? 18:34:05 networkstatic: not as far as I am aware 18:34:32 rogr 18:34:35 the cisco guys are doing cisco live this week, should get more active after that 18:34:57 rrsantos: looks like simpleforwarding is the out of the box for now buddy 18:35:17 aye 18:35:19 it basically proxies ARP and does an L3 rewrite 18:35:39 kinda expensive but does scale beyond L2 segments 18:37:47 dave_tucker: so the changes are already committed locally 18:37:54 this is gonna sound stupid 18:37:55 but... 18:38:14 Mierdin: there are no stupid questions...unless its from you. 18:38:21 i can say something dumber if it makes u feel better 18:38:24 I can maybe undo the Operations changes, commit, then recreate them with a new commit that appends to the commit containing the new Mutate file? 18:38:32 bigmstone: ass 18:38:38 If it's in the same branch.... 18:38:48 you can git reset to the change id of your first commit 18:38:54 networkstatic: that's because we can put a southern draw on it. 18:38:58 then git add, git commit --amend 18:39:02 oh yeah, bigtime 18:39:19 For reference, I'm sitting next to Mierdin right now. So I'm giving him a hard time. 18:39:20 maybe some gravy on it too 18:39:32 Had biscuits and gravy this morning. 18:39:43 From SF...so it wasn't near as good as it could be. 18:42:08 networkstatic: I see, thank you. Well in that case is there a way of overriding simpleforwarding flows? Because right now I'm setting up flows with my needs but when some traffic appears a new flow is created by simpleforwarding with the same priority as the previous one 18:42:50 roger, stopping simpleforwarding and then handcrafting the flows would be the route to go 18:43:25 look at simpleforwarfing and see how the arp is handled 18:43:44 u can craft a reply or stitch the broadcast domain out 18:44:03 or use overlays and not worry about end to end hops in our case 18:44:24 doesnt apply to physical network yet unfortunately 18:44:39 but could if u nail up tunnels on ur kit 18:45:14 u can plumb the ARP request/response flows manually ofcourse 18:45:24 allow all arp etc 18:45:33 like a big toughy ACL 18:48:35 well right now I'm not developing a controller application, so I'm not messing with the ODL code yet. I'm just using the REST API for creating new flows. so the best solution would be to install additional flows allowing all the arp traffic? 18:53:10 rpger rrsantos that would make sense, also pinging the controller listserv for feedback would be good 18:53:28 asking for plans on arp handling 18:53:50 always good to hear needs 18:54:40 I'm sorry, but what do you mean with pinging the controller listserv? 18:58:18 sorry, sending an email to controller-users https://lists.opendaylight.org/pipermail/ 18:58:45 for any dynamic way to handle arp other then simpleforwarding 18:58:51 or plans in the future 18:59:08 or hit the main channel, i jsut havent seen anything new on that front 19:06:05 Dave Tucker proposed a change to ovsdb: Unit Test Coverage for OvsdbClientImpl https://git.opendaylight.org/gerrit/7122 19:08:31 ahhhh got it networkstatic, I'll send a mail to it soon. thank you for all the help! 19:08:46 great buddy 19:08:48 u got it 19:13:18 dave_tucker: here's my mod to OvsDBClientTestIT 19:13:19 http://pastebin.com/BqbMHfWe 19:13:35 following Madhu's advice, no need for the set method 19:13:46 and had to add the Where reference to Mutate.java 19:13:47 Mierdin: lgtm 19:14:12 cool. I'm going to test using your ovs vagrant stuff first and then commit 19:14:20 which….by the way….is bad ass 19:26:20 dave_tucker: hmmm doesn't look like docker is installed on the centos VM pulled down by vagrant 19:26:34 for which repo sir? 19:26:51 docker-ovs? 19:28:07 yup 19:28:35 sudo docker pull dave-tucker/docker-ovs:2.1.2 19:28:40 docker: command not found 19:29:12 weird cuz I see on your screenshot immediately after vagrant up/reload/ssh 19:29:51 oops, there was an error with setting up epel repo that scrolled by and I missed it 19:29:56 looks like a 404 19:29:58 let me try to rebuild 19:33:54 dave_tucker: while I'm waiting for that, I'm missing where to specify IP address in OvsDBClientTestIT 19:34:07 how do you point that test case to the OVS instance set up in docker? 19:34:30 yessir. your docker vm will be 192.168.50.4 iirc 19:35:17 Madhu_offline's changed merged today on integration test properties 19:35:21 let me find the gerrit 19:36:15 https://git.opendaylight.org/gerrit/#/c/7233/ 19:37:15 Mierdin: so mvn -Dovsdbserver.ipaddress=192.168.50.4 -Dovsdbserver.port=6640 -Pintegrationtest verify 19:38:23 oh right gotcha I remember that now 19:38:26 will give that a try 19:38:37 good work with this vagrant stuff man, it's pretty hands-free 19:38:50 Mierdin: look at GV. 19:41:42 Dave Tucker proposed a change to ovsdb: Fix TestClient test Case https://git.opendaylight.org/gerrit/7320 20:01:05 Matt Oswalt proposed a change to ovsdb: Create Mutate Operation https://git.opendaylight.org/gerrit/7321 20:01:18 * Mierdin hugs odp-gerritbot 20:01:56 I have to run to a session real quick. Hoping to test the addition today but wanted to push this so it wasn't in your way anymore 20:07:42 bah - still broke. Abandoned for now but the stuff I needed to do should be mostly there 20:08:00 just too busy right now and can't concentrate. I'll get back on later today and make sure this gets done right 20:08:22 I'll be on MierdinMobile for rest of day 21:29:01 networkstatic: hey buddy 21:29:12 yoos 21:29:43 Mierdin: hi. sorry i just came back. will read through the messages. I will also send a proposal on your way. 21:29:52 proposal to fix the Mutate issue :) 21:40:22 Madhu:that was a long lunch :p I managed to rebase my commits sir so you are all good to review 21:40:38 will be watching odp-gerritbot for anything incoming from you ;) 21:43:51 Madhu: and can you also update the trello when you get a sec sir? sure you'd like to check Abort + Commit off! 21:43:57 dave_tucker: lol. ofcourse sir 21:44:14 Madhu :p 21:44:21 dave_tucker: did u get a chance to review the RFC7047 ? 21:44:36 yessir. we have all the rpc and operations covered 21:44:48 in the trello at least 21:45:03 sure. I think we have to address the notifications next 21:45:08 checking for any errata or updates 7047 as we speek 21:45:11 today we handle hello, update 21:45:34 we have few notifications not addressed 21:46:19 dave_tucker: once we have the notifications covered, we are in good shape with library. 21:46:32 reasonable shape :) 21:46:52 Madhu: I don't see any mention of hello in the rfc 21:47:18 sorry. Echo :) 21:47:27 lol. ok with you now :) 21:48:15 yeah those are going to be fun :) 21:48:59 fixed our issue with the IT sir (port conflict), that's in review... also renamed the class IT as it's most definately an IT not a UT. 21:49:11 * dave_tucker hope's thats ok 21:52:30 dave_tucker: lemme take a look. 21:53:02 only if it doesn't interfere with your other commits boss ;) 21:53:11 you need a break from code review sometimes 21:56:34 dave_tucker: i know :) at this point, am not even reviewing any code. 21:56:48 am looking at Matt's fix and help massage it a bit. 21:56:58 :D 21:57:01 then an important email reply .. followed by code-review ;) 21:58:44 you've got it all planned out bro 21:59:03 i'm working on converting ABNF -> ANTLR -> Java Classes for Yang support in InteliJ 21:59:07 fun times 22:08:37 shague_: networkstatic just replied to an email regarding LBaaS proposal from Chris, uw.edu 22:08:56 Madhu: what lb ? 22:09:04 since shague_ is looking into it as well, i extended the invite to Chris to participate in the work 22:09:17 ekarlso: u always jump out of the bush and ask questions ;) 22:09:25 https://docs.google.com/document/d/169sTVsXHT7Gdi3F8XRktx1093p5ai2Tl_mQRUfLy24c/edit# 22:09:25 Madhu: aint I allowed ? 22:09:27 :p 22:09:28 that lb :) 22:09:29 excellent, oh yeah, been friends with him for a while 22:09:36 ekarlso: of course no sir :) u r always welcome 22:09:42 smart dude 22:09:47 chsmall in here too 22:09:54 ekarlso : u first message starts with a ? always ;) 22:10:09 chsmall: ah. he is here. sorry didn't realize it 22:10:10 LOL 22:10:12 hahaha 22:10:17 first question 22:10:18 lol 22:10:24 hi 22:10:35 heya bro 22:10:40 chsmall: didn't realize u r part of this already :) 22:10:49 wouldn't have been formal in replying to the email ;) 22:11:42 chsmall: so glad you sent out that proposal. we were talking about it for a few weeks now and shague_ has picked up to work on it. 22:12:28 ekarlso: if u have any questions... chsmall is here to answer ;) 22:12:35 hehe 22:12:41 well played Madhu 22:13:15 * Madhu still not able to shake myself off that stupid email i just sent out without realizing chris is already here in this channel 22:13:26 I chatted with shague_ a bit last week but wanted to put something out there to start the discussion 22:13:41 chsmall: excellent. 22:13:45 sorry didn't realize all these 22:15:09 Madhu im sorry bro :( my fault, i shoulda made the connetction sooner 22:15:15 but damn u r so polite 22:15:25 wtf. why polite ? :) 22:15:27 it will be a reference for future people coming to the project 22:15:31 am glad that someone is doing it 22:15:45 u r friendly 22:15:54 we are friendly project 22:16:24 except for ekarlso 22:16:35 lol. man. 22:16:40 hehe 22:16:53 he rates every bit of harrasment he gets :) 22:17:22 he is a lone warrior now sir in this channel 22:17:28 chsmall i havent had a chance to dig in, soon as i get a stupid service registered and put up for review im digging in! 22:17:33 haha 22:17:39 we have converted all other ex-colleaques of his to sanity ;) 22:17:55 lol 22:18:06 dave_tucker: u got the drift ? ;) lol 22:18:26 no the dave_tucker at HP is a right jackass. he rights buggy code 22:18:32 have no idea who he is 22:18:45 Just catching up on the e-mail. I think it makes sense to LBaaS in ovsdb since 1) it will be mostly done inside ovs 2) Not sure if I want to spinup a whole project to start with 22:19:41 chsmall: good call. 22:20:09 and openstack services are the only real thing in SDN today 22:20:11 oops 22:20:24 i tried to find a good lone wolf picture for endre 22:20:28 best i came up with is 22:20:29 https://www.dropbox.com/s/51dmgdfpytegk8h/Screenshot%202014-05-21%2018.19.30.png 22:20:32 what u want with me :p 22:20:41 ROFL 22:20:49 lol 22:20:59 However how LBaaS is done may effect other OpenStack advanced network services so I am hoping to get as much input as I can. 22:21:41 does the Neutron API differentiate between LBaaS and Port load balancing? 22:21:51 well, nm, 22:22:00 chsmall: agreed. will review the proposal 22:22:03 and give feedback. 22:22:21 only thing we care on overall is fulfilling V2 api requests 22:22:22 and also, i heard a lot of interest on LBaaS from EBay folks who attended the OVS hackathon 22:22:30 lets get some inputs form ashw7n as well. 22:22:32 rest is whatever implementation we want bro 22:22:36 good call 22:23:00 chris have u looked at NXMs buddy? 22:23:16 tcp_flags may be handy for you also 22:23:43 to avoid a punt fest 22:26:10 There is a proposal about LBaaS from someone at Blue Box. He was working with Ebay/Rackspace who are very interested looking at how to enhance OpenStack LBaaS 22:26:24 nice 22:26:36 will check the blueprint 22:27:00 andyhky is a Racker if u need details 22:27:06 and a hell of a guy 22:27:14 who randomly lives 20 minuutes from me 22:29:27 Only mentioned extensions in passing in the strawman. Very useful but they are extensions and you have to be careful about relying too much on them. 22:32:23 Would like to have some level of graceful fallback to lowest denominator to standards but add more functionality/performance if you have the correct resources 22:33:19 rogr boss, for sure 22:33:24 we used to be that way 22:33:46 until we realized we couldn be as useful 22:33:50 now we are arms dealers 22:34:15 gimme onePk, JunOSSDK, EOS, whatever it takes 22:34:20 hehe, j/k 22:34:38 ONF being reluctant to have a SW spec is frustrating 22:35:03 maybe u can push :) ur a researcher n ONF arent u? 22:40:11 You definetly need to use extensions or reach-arounds (as IU has coined the term) to do useful things. I having been pushing for more useful info in 22:40:53 capabilities since somewhere around OF 0.8.9 22:42:21 chsmall: agreed. 22:42:23 If you knew exactly what the switch was capable of you could build a strategy to implement the task. 22:43:03 when it comes to OVS at least :) depending on NXM seems reasonable 22:43:36 and as networkstatic said, we were originally an OXM only shop to realize that we cannot do everything that we want to 22:43:56 also from the history, we can see that NXMs get into OXM and OF spec but a bit delayed 22:44:21 so tru, TLVs in OVS are implemented the same 22:44:27 only diff is the constant sent 22:44:44 also, if we have to over-simply or grossly-incorrect :) we can see OVSDB as an extension as well :) 22:45:03 and Im a hack 22:45:08 it extends the Flow functionality to configuration and both work hand in hand very well 22:45:11 not even an extension 22:45:53 of course all these are true for OVS :) 00:04:05 hell 00:04:27 random 00:25:25 networkstatic: is it madhu's birthday? I got a g+ notif 00:26:07 Madhu_offline: Happy b-day man! 00:26:18 woo! 00:42:38 sorry for the condition I left my stuff in. Crazy out here. Just trying to keep stuff moving 00:43:29 The vagrant stuff is wicked cool though I will get back to it ASAP 03:10:24 evanz: tbachman thanks guys. yes 03:10:46 its like a biological clock for me. tic toc tic toc ;) 03:12:07 :) 04:01:21 ashw7n: 04:01:28 yes boss 04:01:53 few questions sir 04:02:19 sure.. 04:03:27 we are working on the schema branch as u might have noticed 04:03:58 a lot of questions actually :) but i will restrict to a few 04:04:23 in the master we used the OvsDBMap and OvsDBSet 04:04:39 yes 04:04:55 which does the nasty ovsdb json stuff such as including "set" and "map" for the multi-dimensional array 04:05:41 in the current monitor code 04:06:16 am looking at the response handling portion especially 04:06:22 MonitorHandle monitor = ovs.monitor(dbSchema, monitorRequests, new MonitorCallBack() { 04:06:31 in OvsDBClientTest 04:06:57 the MonitorCallback seems to use the TableUpdates from the past 04:06:58 checking... 04:07:10 yes, we need to get to the bottom :) 04:07:26 what we need is a simple approach just like what we have for the schema 04:08:48 am still confused sir :) 04:09:13 how are the ovsdb json "set" and "map" translated now to a Java Set and a Java Map ? 04:09:27 since we are not explicitely using ovsdbmap and ovsdbset 04:10:04 public static DatabaseSchema fromJson(String dbName, JsonNode json) { 04:10:10 in DatabaseSchema 04:10:56 wait, i didnt get the part of ovsdb set thing, we havent done that yet 04:11:31 we need to change the mapping either manually, just like the DatabaseSchema, or use a generic translation like we have on the existing code 04:12:09 if u look at our master 04:12:28 okay 04:12:36 tables like Bridge, etc.. are all defined with OvsSet and OvsMap 04:13:46 this helps in ser and deser back and forth between the java world and the "set", "map" ovsdb json world 04:14:33 am just trying to see how we will be addressing it in the new schema driven world 04:14:50 i hope we will expose it as a simple Set or Map in Java 04:15:00 without the need to expose OvsSet and OvsMap 04:15:01 yes, it needs to be a simple Set and Map in java 04:15:25 and our serialization logic would have to deal with it, based on the Schema definition 04:15:38 got it. 04:15:40 or the spec 04:15:54 but the good part is that we have a schema which has all the details and types 04:15:59 so we shoudl be able to do it 04:16:01 yes. 04:16:08 actually we have to cleanup the schema branch 04:16:13 and remove all the old references sir 04:16:18 i will work on one example tomorrow 04:16:20 it is getting damn confusing seeing all here 04:16:22 yes we should 04:16:32 maybe we can spent some time tomorrow together 04:16:40 yes sir. 04:16:55 few of us are filling in the missing operations 04:17:10 adding tests gets challenging because we don't have these coveree 04:17:29 because without the ovsdbset and ovsdbmap covered 04:17:36 we cannot even handle monitor 04:17:41 without monitor we cannot do mutate 04:17:49 and the chain continues :( 04:19:03 ohh, okay, so can you tell me one operation which is using set and map and i'll work on it 04:19:22 oh. 04:19:27 monitor as an example sir 04:19:49 once we set Monitor. the monitor response (and the update) will return data with this stupid json format 04:20:01 that is the most important of it all. 04:20:23 the other is the insert, update, mutate operations. 04:20:29 since insert is already implemented. 04:20:38 we have to make Insert work for all the set/map cases as well 04:21:09 okay, so what is the TableUpdate returning now, sorry its been couple weeks :D 04:21:30 i will give u an example sir 04:21:58 https://gist.github.com/5c194ad56fa4a038a69e 04:22:25 this is an example where a monitor is done on Bridge table for columns name, fail_mode and protocols 04:22:31 name, fail_mode are both simple strings. 04:22:38 but protocols is a set 04:22:43 ok 04:23:24 the return as u can see has the ----- protocols":["set",["OpenFlow10","OpenFlow13"]] 04:23:40 this was originally mapped to OvsDBSet 04:23:51 and mapped statically to the protocols object in the Bridge Class 04:24:01 lol, I know this, but what i was asking is about the current method we have for getUpdate 04:24:15 there is a test case in OvsDbClietnTestIT 04:24:20 for monitor 04:24:25 isnt it returning 04:24:25 ? 04:24:41 I thought it was working before I checked in 04:24:50 testMonitorRequest 04:24:55 ya i saw that :) but the TableUpdates didn't have toString() :) 04:25:03 and hence the output is this : result = org.opendaylight.ovsdb.lib.message.TableUpdates@2f2b69ef 04:25:05 lol 04:25:17 am adding the toString now to check what the result is parsed out as 04:25:30 but as u can see, the result will be parsed out properly because 04:25:56 TableUpdates is statically typed class for the static Tables (from the existing code) 04:26:03 so we have to stop using this :) 04:26:28 okay, i think it will be much better if we can spent some time tomorrow 04:26:45 and we can hack it out 04:28:26 ok sir 04:30:00 ashw7n: shall we do hangout tomorrow to begin with and then I can even drive in to your office 04:30:58 okay 04:31:29 ok sir. thanks. 04:31:47 the old code and new code in the same folder causes a lot of confusion 04:32:00 am planning to create a new package called old and move the old classes into it 04:32:18 (to avoid compilation issues on the application layer (plugin and neutron) 04:36:04 i left the old ones in there so taht we dont break everything 04:36:10 i told you this was a big change :D 04:36:37 of course sir. 04:37:02 we are on path for helium release now :) and this is getting HOT 04:46:09 ashw7n: just trying my luck :) do u have sometime tonight ? 04:46:23 for a hangout in 30 mins ? 04:46:34 sure, in 10 minutes? 04:46:56 15 :) my kid shud be asleep by then. 05:00:03 okay 05:00:05 ping me please 05:05:20 ashw7n: am ready sir. will ping u in hangout 12:02:09 dave_tucker: minor nit on select fix 12:03:01 Madhu: hey buddy 12:03:24 Madhu: this one is rebased now sir https://git.opendaylight.org/gerrit/#/c/6861/ 12:04:04 yes. 12:04:16 the method name "value" in the Select class may not be appropriate 12:04:42 ok. I'm playing follow the leader here - as I said, copy/paste ninja 12:07:14 dave_tucker: trying to find a more appropriate method name from the existing example 12:07:53 dave_tucker: the closest i could find is the addColumn method of Monitor 12:09:56 Madhu: would "row" be better than "value"? 12:10:49 or rows rather... or even just select ;) 12:11:08 From the RFC... The operation searches "table" for rows that match all the conditions 12:11:08 specified in "where". 12:11:23 yes. 12:11:30 but rows is not the right one here 12:11:33 it is the "result" object 12:11:45 i think addColumn is the most appropriate 12:11:54 and it should be similar to monitorrequest.java 12:11:57 but wouldn't it be addRows 12:12:03 or addRow 12:12:09 nope. 12:12:11 rather.... as the result of a select is Rows 12:12:16 Select is not adding a row 12:12:19 * dave_tucker is missing something 12:12:46 it is searching for data in a Table given a where condition and columns of data to Select from 12:12:52 and the result object is the row. 12:12:59 rather rows 12:13:18 so the "value" method is not appropriate. and must be replaced with addColumn 12:13:36 and the test case must include that. (now it is ignored and uses just the where clause) 12:15:09 we have a setColumns method that adds columns to the list... how does addColumns differ? 12:15:22 not trying to be awkward... just struggling to understand 12:17:03 of course sir :) 12:17:12 setColumns is the typical getter setter. 12:17:37 addColumn() is a usage aspect of the API 12:18:28 ok.. so other than the name is the method signature ok? 12:18:29 we are providing a choice to the user to choose to write addColumn() one after another instead of a precooked list. 12:18:34 generics confuse the hell out of me 12:18:36 :S 12:18:57 actually the method signature is also not appropriate :( 12:19:09 because. there is no "value" per-se 12:19:22 and adding it to the rows is also not correct 12:19:27 it should be adding to the columns 12:19:42 because rows is the return value of select operation 12:19:48 not something set by the user 12:19:49 public > Select addColumns(ColumnSchema columnSchema) 12:20:03 then columns.put(columnSchema) 12:20:19 and remove private Map rows as it's the return value 12:20:21 ? 12:21:10 please refer to MonitorRequest.java 12:21:16 it does exactly the same that we are looking for 12:21:23 https://gist.github.com/a89bcd35f250158690e6 12:21:35 I have that class open too Madhu :) 12:23:01 * dave_tucker changes gistify to gist in java 12:24:23 Madhu: highlighting in java https://gist.github.com/anonymous/b78271c0967dc3d192ad 12:25:01 s/addColumns/addColumn/ 12:25:07 oops! 12:26:12 done. grabbing coffee brb 12:32:39 ok back in the room 12:34:37 Madhu: would it make sense to just call the method "column" 12:35:11 .add(op.select(bridge).column(name) 12:35:14 dave_tucker: was actually thinking about that 12:35:15 but 12:35:23 method() is an action 12:35:28 and column is a noun :) 12:35:31 not a verb 12:35:41 thats y addColumn makes more sense 12:36:01 well where is an adverb 12:36:06 :p 12:36:07 lol. 12:36:37 but from a usage standpoint, you are saying "select" "column" not "select" "addColumn" 12:36:39 for other places such as set(), mutate(), abort() 12:37:11 these are all actions and hence update has a set(), etc... 12:37:25 ya. select is the verb there :) 12:37:39 and column is the data / noun that goes in as parameter 12:38:02 what about "from" 12:38:04 like sql 12:38:11 select * form 12:38:15 s/form/from 12:38:20 actually no :) 12:38:27 we are selecting the columns 12:38:39 from is for the table to select from 12:38:46 the * is what is being discussed here 12:39:25 crap! 12:39:29 as per the RFC. the Select Column is exactly the same as Monitor Column 12:39:36 thats y i chose that example 12:39:58 Select : "columns": [*] optional 12:40:15 Monitor-request : "columns": [*] optional 12:40:20 I know... I know... but I like the notation we have 12:40:25 .column is pretty 12:40:32 .addColumn is not 12:40:36 :p 12:40:49 if u can verbify column() then am with u there ;) 12:41:16 I'm going to column get you Madhu 12:41:18 there done 12:41:21 lol 12:41:32 lol. nice try 12:42:38 but if u feel column() is more usable and intuitive 12:42:46 its okay. am not trying to be a poet here ;) 12:42:49 rofl 12:43:03 lets put it to the vote... otherwise its just my say vs yours 12:43:16 we need a mediator lol 12:43:33 where's odl_meetbot 12:44:31 .add(op.select(bridge).column(colA).column(colB).where(colA.x = "y") 12:44:33 vs 12:44:41 .add(op.select(bridge).addColumn(colA).addColumn(colB).where(colA.x = "y") 12:44:59 of course #1 is more intuitive :) 12:45:22 right I'm rolling with #1 before you change your mind lol! 12:45:24 because it sounds just like english here 12:45:48 yeah, tbh I think we can excuse it not being a verb because it's being used to construct an operation 12:45:50 select from bridge column colA, colB where colA.x=y 12:46:03 #agreed ;) 12:46:24 lol 12:46:28 okay sir. lets do it. 12:46:38 same for MonitorSelect 12:46:40 * dave_tucker ducks 12:47:33 well... there i have some problem :) 12:47:44 because it is a "Builder" 12:47:54 Dave Tucker proposed a change to ovsdb: Add OVSDB Select Operation https://git.opendaylight.org/gerrit/6861 12:47:55 not sure why we have 2 different patterns here though 12:47:59 qq — this all makes sense b/c the context here is add 12:48:02 Ashwin can help answer it for us 12:48:10 Will this ever be used w/o the add, or other verb operation? 12:48:18 B/c then the column may not make sense? 12:48:21 * tbachman ducks 12:48:34 tbachman: good question. 12:48:38 tbachman: I don't think so 12:48:46 but in this. it is used only for add 12:48:48 there are normal getter/setters for use outside 12:48:50 I think 12:49:03 so, that seems reasonable :) 12:49:06 because RFC doesn't indicate anything like exclude :) 12:49:39 if there is an exclude option in select column 12:49:50 then i agree.. we are in trouble with the simplicity of column() :) 12:50:52 but it looks so cool! it's like it's own DSL 12:52:48 they say programming is an art :) 12:52:57 and with today's poetic discussion, we proved it. lol. 12:53:51 Madhu: question for you on OVSDB 12:54:03 oops. am in trouble now 12:54:10 LOL 12:54:22 no — I *should* actually know the answer, but don’t 12:54:36 You created some extra code for “bi-directional” JSON RPC 12:54:38 * dave_tucker lines up the next question for Madhu 12:54:45 (heard you mention that a few times) 12:54:54 Were there no libs out there to do this? 12:55:02 Or just none that provided what u needed? 12:55:11 #2. 12:55:16 none that provided what we need 12:55:20 * tbachman steps aside to let dave_tucker ask his q 12:55:24 Madhu: got it. 12:55:42 Reason I’m asking — will likely be doing the SB plugin 4 ur fave prototocol ;) 12:55:44 * Madhu thinks tbachman is ready to reuse some of it for his "project" 12:55:52 lol 12:55:55 read my mind 12:56:03 and thats y i hate that. 12:56:09 yeah 12:56:17 Madhu: you never answered my question about ServiceHelper. why we use that vs just using OSGi to inject services to the classes that need them :D 12:56:18 because it is going to be a r.i.p.o.f.f ;) 12:56:27 Madhu: tbachman: lol 12:56:29 lol 12:56:30 ah. right dave_tucker 12:56:43 Madhu: would you expect anything less from me ;)? 12:56:49 service helper is useful for those bundles who don't have any Activator 12:56:58 tbachman: u as a friend no problem :) 12:56:58 tbachman: Ctrl + C, Ctrl + V 12:57:10 dave_tucker: lol! 12:57:14 that’s what I do best :) 12:57:30 Madhu: cool, but if we *have* an activator, we should use it right ;) 12:57:40 tbachman: heard another great addition to ur team ;) 12:57:48 ? 12:57:49 * dave_tucker refers to copious usage of ServiceHelper in ovsdb.neutron 12:57:51 dave_tucker: well it depends actually 13:01:01 Dave Tucker proposed a change to ovsdb: Add OVSDB Select Operation https://git.opendaylight.org/gerrit/6861 13:08:15 6861 is ready for merging now Madhu ;) before you change your mind about columns ;) 13:09:27 lol. 13:09:44 but. it is certainly way better than value() and updating rows. do u agree dave_tucker ;) 13:09:58 Madhu: yessir 13:10:09 that's what code review is for 13:10:31 certainly sir. glad we are doing it 13:10:33 and it forced me to understand what I was doing better, so thanks Madhu :) 13:17:34 A change was merged to ovsdb: Add OVSDB Select Operation https://git.opendaylight.org/gerrit/6861 13:18:13 dave_tucker: now to the isReady() debate ;) 13:18:24 Madhu: lol 13:20:12 omg lol 13:20:42 lets do https://git.opendaylight.org/gerrit/#/c/7320/ first 13:22:11 dave_tucker: okay :) 13:22:20 am torn between UT vs IT here :) 13:22:31 yes. it is IT :) 13:22:46 but it is a clear UT by not mocking the server portions 13:23:05 if we see Netty library as something that just works like a Java system library 13:23:24 then it is a mocked form of server. won't u agree ? 13:25:59 Madhu: I'm torn too 13:26:23 but UT should focus on testing logic in a single class 13:26:42 this seems to test multiple classes (like an IT) and also uses data that looks real iirc 13:27:43 well yes. thats y am trying to duck with the fact that if we assume Netty as something solid 13:27:49 and the data is not real :) 13:27:57 it is of course faked from a file 13:28:25 does this sound real to u dave_tucker : "planet of apes" ? ;) 13:29:01 Madhu: yessir. it's in the SciFi schema in RFC1999 13:29:10 j/k 13:29:12 lol 13:29:26 as u can see 13:29:45 this UT was written to test JsonRPCDecoder class 13:29:57 of course with the help of Netty 13:30:18 dave_tucker: it doesn't test anything else. 13:30:45 Then it should be JsonRPCDecoderTest ;) and we should be testing those methods 13:31:04 that I agree. 13:31:18 starting up servers etc... is normally done in an IT 13:31:19 calling this an IT is a stretch 13:31:26 i agree there too 13:31:35 just that it is an intelligent mocking :) 13:31:36 the "right" way to do a UT would be to inject that data directly in to the method being tested 13:31:51 Madhu: too much intelligence there ;) 13:33:41 * dave_tucker wonders if there is a mocking framework for netty 13:33:51 the netty dependency makes this an IT imo 13:33:59 dave_tucker: i will keep this open for Ashwin to comment 13:34:11 and I spoke to him yesterday 13:34:16 and we are going to fix some issues today. 13:34:19 COOL! :D 13:34:24 i identified a few for his taste :) 13:34:39 ok the are you ready for isReady :D 13:34:52 i gave my comment already. u decide sir 13:35:54 Madhu: java q. does the while break as soon as the condition is met? or does it finish the loop an re-evaluate the condifion before next run? 13:36:32 and if I add a "break" inside the if, will that break out of the "if" or the "while" or both ;) 13:36:54 breaks the loop :) 13:37:27 ok Madhu... will add a break and call it quits. as I said, I like to return only at the end of a method as I find it easier to read 13:37:31 dave_tucker: http://stackoverflow.com/questions/4154553/the-command-break-in-java-what-if ;) 13:37:48 Madhu: thanks sir! 13:38:08 dave_tucker: if u break, then u have to use that stupid variable ;) to know what is the return value 13:38:37 lol. hey don't go calling "boolean ready" stupid - he's my friend 13:39:05 ah. i had just 1 freedom to call someone stupid.. now even that is gone. 13:39:45 Madhu: you have no freedoms sir. you must suffer my code reviews all day long! 13:40:18 lol. ok buddy 13:40:34 u decide on the usage of boolean vs returning from within ;) 13:41:41 Madhu: ha I win! I will wear you down with my amateur java lol 13:42:37 Dave Tucker proposed a change to ovsdb: Stop isReady method always returning true https://git.opendaylight.org/gerrit/7121 13:42:55 Madhu: I went with your method though 13:43:24 have a feeling that my hatred of returning values mid-method is as irrational as my hatred of Hugh Grant and Colin Firth 13:44:36 ah. that is universal then. i thought it was just me ;) 13:44:46 :) 13:44:48 i mean the actor hatred part 13:44:52 I got that 13:48:23 A change was merged to ovsdb: Stop isReady method always returning true https://git.opendaylight.org/gerrit/7121 13:50:43 do we need to get a fund together so networkstatic can have an IRC bouncer? 13:51:35 Giovanni Meo proposed a change to ovsdb: ovsdb has a dependency on artifacts from integration project, that shall be removed https://git.opendaylight.org/gerrit/7334 13:52:01 Dave Tucker proposed a change to ovsdb: Unit Test Coverage for OvsdbClientImpl https://git.opendaylight.org/gerrit/7122 13:52:06 andyhky: lol. 13:53:46 andyhky: earthfirewindwaterheartbyyourpowerscombinediamcaptainpla.net thats something. 13:54:12 I try :) 13:54:32 pla.net.... u nailed it 13:56:58 Madhu: after GiovanniMeo's changes have merged do you think we can attempt a merge of master to topic/schema... so we get distribution + vagrant + other fixes in our topic branch 13:57:15 dave_tucker: good idea 13:57:26 we need to pick up all the changes going into neutron layer as well 13:57:54 dave_tucker: would u like to give GiovanniMeo's fix a try ? 13:58:00 d/ling it now ;) 13:58:06 tx bro 14:00:12 thx guys, i have done basic validation on it 14:00:16 as basic as making sure 14:00:21 the bundles all startup 14:00:26 and the ovsdb is running 14:00:34 but nothing more than that 14:00:54 so any real run is very much appreciated 14:01:17 also any suggestions on how to avoid caching run.base.sh 14:01:19 is welcome 14:01:53 GiovanniMeo: assume this is not your fault, but get this when starting the controller. https://gist.github.com/45f60f6a63a9953159ec 14:02:28 i didn't see it in my run 14:02:35 but i suspect 14:02:36 ovsdb bundles start fine 14:02:41 it's a race condition 14:02:58 simply thee remoterpc 14:03:12 should be waiting till the mandatory dependency 14:03:18 on routing table 14:03:24 is satisfied 14:03:27 or should run 14:03:32 assuming that could be null 14:03:43 the usual problem of dependency management 14:03:51 we have seen spread around mdsal :( 14:04:08 GiovanniMeo: yeah :) will raise a bug :) but will +1 your change as it lgtm 14:04:41 GiovanniMeo: sorry didn't try the change yet 14:04:45 but easy to ask the question 14:04:46 :) 14:05:09 so we still have the option to use -of13 and choose between ad-sal OF plugin and MD-SAL OF plugin ? 14:08:26 i just copied 14:08:31 run.base.sh 14:08:35 as it's 14:08:41 so the flag is in there 14:08:50 didn't tested though 14:11:28 Madhu: tested. it works 14:12:07 thanks guys. 14:12:27 Madhu: proof - https://gist.github.com/anonymous/a3ba57675ce8c4035fe9 ;) 14:12:44 excellent :) 14:13:00 okay, 7am is here. and time to exit for 90 mins 14:13:36 bye Madhu 14:14:02 dave_tucker: before I leave, will push a test code for ur review :) 14:14:14 Madhu: ofc, I owe you a review or 100 14:18:29 Madhu Venugopal proposed a change to ovsdb: Added a test-case to include non-atomic column to test the ser/de-ser pipeline in the new schema base code. https://git.opendaylight.org/gerrit/7335 14:18:49 dave_tucker: all yours sir. bfn 14:19:34 dave_tucker: pls look out for the ---- "row":{"flood_vlans":["set",[100,200]] in the message sent to the OVS 14:19:46 the ugliness of "set" usage is being tested here. 14:19:49 ok boss will do ;) 14:20:03 pls look for definition in the RFC and u will understand what am talking about :) 14:20:04 bye 14:33:49 thx dave_tucker for the test 14:33:54 much appreciated it! 14:34:05 GiovanniMeo: any time! 14:36:03 Guys... what is the current version of ovsdb for stable/hydrogen ? 14:36:36 (I ask because I happen to be updating the integration stable/hydrogen pom files versions for openflowplugin and noticed ovsdb also appears to be out of date) 14:37:06 guys... although having ping between VM's, why am I seeing red ports in opendaylight? 14:37:33 I am trying to understand how the integration between opendaylight and openstack works in fedora 20 14:38:52 for instance the qg interfaces of br-ex of the openstack control node appears in red 14:39:01 in opendaylight 14:43:55 after stacking, googling and praying, my concerns come because I do not know what do I have to see in the opendaylight GUI 14:44:00 arrgghhhh :S 14:44:46 does anybody know what do we have to see in the opendaylight GUI? 15:45:48 jordi_cttc: hi 15:47:19 jordi_cttc: the open daylight GUI displays what is learnt on the backend 15:47:42 when you say node appears in red ... do u mean the ports attached to the switch appears in red ? 15:48:04 that typically means that the port is down 16:39:03 edwarnicke: did u send any email about ovsdb stable/hydrogen version issue in integration branch ? 16:39:11 i remember seeing it. but now I don't :( 16:39:16 can u pls resend it if u don't mind 18:16:00 networkstatic: i know you missed this. 18:16:02 [09:50:43] do we need to get a fund together so networkstatic can have an IRC bouncer? 18:16:11 haha 18:16:21 whatup buddy 18:16:31 u have a good time last week? 18:33:45 of course! 18:33:48 you? 18:39:23 Madhu: or networkstatic: question about Trello. Trying to add this for Openflowplugin. I see you have on the top level ovsdb (https://trello.com/ovsdb) and under that you have the boards Helium, Hydrogen, etc. So is this top level ovsdb an organization? 18:39:49 roger, buddy 18:39:56 we had it RO 18:40:02 but i think its RW now 18:40:21 abhijitkumbhare: yes. 18:40:23 inside Helium is the current cadence we are on 18:40:30 OK - I just created first OpenFlow plugin as a board - will delete and create it as an org 18:40:41 got it 18:40:45 abhijitkumbhare: yes. 18:40:51 create an org 18:40:55 and have control over the org 18:41:04 and create boards and share it with others 18:41:05 sounds good 18:41:07 awesome, link us when u get done if you dont mind, would be great 18:41:12 sure 18:41:24 thanks buddy, 18:42:56 i like trello over bugzilla for roadmap projects 18:43:16 i really hate searching in bugzilla 18:43:46 if u r an agile focused project, we also use agilefant :) 18:43:52 searching in Evernote is worse 18:44:02 pretty good free agile sprint tracking tool 18:44:13 i loved what akim did with toolkit 18:44:16 so sexy 18:44:31 not akim but akim's agilefant 18:44:38 not that he isnt pretty 18:44:42 what? 18:44:42 lol 18:44:44 lol 19:08:08 To jump in a little late, I've been using GitHub's issues for a large robotics project for quite some time. Quite a fan. Very powerful, love being able to link to commits/files/branches/LoC, good syntax highlighting of code chunks, @tagging for devs and teams, milestones for sprints...I could go on and on lol 19:19:02 heya dfarrell07 i just realized that u r Daniel! 19:19:04 lol 19:19:13 robotics tipped me off 19:23:42 networkstat: Yeah lol, dfarrell07 -> Daniel Farrell, SDN intern at Red Hat 19:24:58 I know networkstat -> Brent from all the helpful blogs, lol 20:14:47 Wow - this Trello stuff is real cool 20:15:27 I have added Madhu and networkstatic to the members of OpenFlow plugin Helium release 20:15:41 abhijitkumbhare: thanks. 20:15:42 Not assigned any tasks :-) 20:15:56 I mean to you guys :-) 20:16:00 lol 20:16:11 don't worry we are crazy enough to pick some ;) 20:16:18 sure :-) 21:34:23 * Mierdin finally grabs some time to fix my screw-up from yesterday 21:59:01 Mierdin: hi. 21:59:17 hey Madhu 21:59:19 lemme know if u need any help sir 21:59:26 fixed my dumb checkstyle errors 21:59:28 sorry about that 21:59:30 was dumb 21:59:37 got vagrant VM up and running now, working through IT 21:59:57 ok. 22:00:29 if u want, we can do hangout and I will show u exactly how I run these tests and code these as well. 22:01:29 I may need that 22:01:38 today will be hard, last day of CLUS 22:01:44 but taking a stab now 22:01:48 trying to learn :) 22:02:09 sure np. 22:06:03 getting some errors in the test logs 22:06:06 io.netty.channel.ConnectTimeoutException: connection timed out: /192.168.111.135:5000 22:06:12 don't recognize that address 22:06:28 here's my build string mvn -Dovsdbserver.ipaddress=192.168.50.4 -Dovsdbserver.port=6640 -Pintegrationtest verify 22:07:36 Mierdin: back. 22:07:45 hmm. lemme check. 22:08:26 btw I verified 50.4 is the actual address, can ping it from my laptop, etc 22:08:35 oh, and here's how I started docker 22:08:38 sudo docker run -p 6640:6640 -p 6633:6633 -p 6644:6644 --privileged=true -d -i -t davetucker/docker-ovs:2.1.2 /bin/bash 22:08:56 hmm. the error comes from integration-test.properties file 22:09:08 but i have deleted those files :) 22:09:30 maybe u need a rebase. 22:12:30 crap 22:12:50 but u shud not be picking up that file anyways. 22:13:11 sorry to ask. u r in topic/schema branch correct :) 22:16:34 lol yesss :) 22:18:32 gotta boot for now, will sign on my phone real quick 22:32:53 signing in from phone to irc is exceptionally nerdy, i like 22:45:21 networkstatic: feeling naughty ? :p 23:19:06 ekarlso: what r u doing up? 23:25:03 tbachman: :P 23:25:08 working on some stuff ;) 23:25:13 crazy man 01:38:52 Ashwin Raveendran proposed a change to ovsdb: renamed old package to temp and fixes for min/max https://git.opendaylight.org/gerrit/7352 03:38:05 Hey Madhu 03:38:19 hi Mierdin 03:38:27 guess u r having fun @ clues 03:38:29 clus 03:38:33 saw the pics. 03:38:36 ;) 03:38:51 Yeah I have a nice bunch of followers lol 03:39:03 they really like to exploit my embarrasment :) 03:39:57 lol. 03:40:07 anywho 03:40:12 yes sir. 03:40:16 I'm really not looking forward to a rebase 03:41:08 :) 03:41:11 He had a great time. 03:41:38 Mierdin: easiest would be to pull a new repo and apply ur patch 03:41:50 honestly yeah I was going to suggest 03:41:55 it's not like it's that much code 03:42:04 yet you wouldn't know it based on how long it's taking me to get this to work :) 03:42:10 I can do that 03:43:36 Mierdin: IMHO i think this is the best way to learn :) 03:44:08 pro-git is your friend. if you had not reviewed it, would highly recommend it 03:44:15 as long as I don't annoy you pros too much LOL 03:44:27 small book. but some good info in there 03:44:31 oh god no. 03:45:00 once u have the commit merged in u will be unstoppable :) 03:48:15 I need to do more practice with things like rebase on a dummy repo 03:48:22 I have the basics down but the advanced stuff still scares me 03:48:27 I've rebased before but still....scary 03:49:57 yep, 03:50:05 i have a playground/ directory 03:50:10 specially for git :) 03:50:24 and will recreate scenarios there before monkeying with working code. 03:52:48 that's a really good practice 03:53:18 well I am home next week (and over the weekend obviously) and will be working hard to finish this 03:59:31 ok Mierdin don't worry about it. we have many other things to do anyways 03:59:35 and we will concentrate on those 07:14:19 favorite alias of the day 07:14:40 alias of13="gsed -i 's/# ovsdb.of.version=1.3/ovsdb.of.version=1.3/g' configuration/config.ini" 07:14:52 i need a life 07:23:36 networkstatic, lol 07:24:26 networkstatic, that's just...sad. and funny. 09:40:16 hi, does somebody know how to awake an interface which is down in opendaylight? 09:46:05 networkstatic: i think you should push your aliases to the resources folder :) 09:46:25 i think it will solve world hunger too . lol 09:47:01 jordi_cttc: hi. is this in relation to the port DOWN after stacking ? 09:47:27 yes 09:47:39 madhu: yes 09:47:40 one of the most typical case of port/interface Down is the failure to obtain the Openflow port number. 09:48:00 ODL doesn't influence that at all. that is entirely on the OVS side. 09:48:35 madhu: ok, I imagine ODL is like a transparent stuff between openstack and ovs 09:48:40 jordi_cttc: curious to know your setup that results in a null OF port for theres interfaces 09:49:16 jordi_cttc: kind of. But not so transparent when it comes to Overlay Tunnel management 09:49:29 madhu: I am using the fedora20 VM that Kyle uses in the last presentation 09:49:42 it just doesn't mess up with the libvirt's work on handling the tap ports and addition to br-int 09:49:50 jordi_cttc: okay. 09:49:55 madhu: I made a clon and I am working on with two machines 09:50:14 can u check the ovs logs 09:50:29 under /var/log/openvswitch/ovs-vswitchd.log 09:50:37 madhu: in fact, if you visit http://pastebin.com/7z9J8G8C, you will see what happens after each step I do 09:50:50 madhu: ok, I am going to check the logs 09:50:55 madhu: thanks 09:51:03 sure. this paste bin covers the ODL log. 09:51:09 which is very useful of course :) 09:51:16 but this issue seems to be on the OVS side 09:52:05 madhu: in which computer? controller or compute 09:52:23 madhu: I have them separated and I only count with one compute node 09:52:48 jordi_cttc: it depends on where the problem is seen. 09:52:54 if u look @ this pastebin 09:52:59 tapbd5b518e-31 seems to have a problem 09:53:10 "ERROR o.o.o.n.provider.OF13ProviderManager - Could NOT Identify OF value for port tapbd5b518e-31 on OVS|192.168.56.101:48886" 09:53:27 56.101 .. which node is that ? 09:53:58 yeah, this is the compute 09:54:35 madhu: I have to mention that sometimes I have the error on the control side and other times in the compute :S 09:55:30 okay. 09:55:49 jordi_cttc: i would just check in both the nodes 09:55:55 and try to spot errors 09:56:30 on both side there are errors 09:56:48 @ the compute: 2014-05-19T09:07:15.164Z|00158|connmgr|INFO|br-int<->tcp:192.168.56.135:6633: sending OFPBRC_BAD_TYPE error reply to OFPST_GROUP request message 09:57:19 @ the controller: 2014-05-19T09:49:41.348Z|00785|connmgr|INFO|Dropped 4 log messages in last 15 seconds (most recently, 15 seconds ago) due to excessive rate 2014-05-19T09:49:41.348Z|00786|connmgr|INFO|br-tun<->tcp:192.168.56.135:6633: sending OFPBRC_BAD_TYPE error reply to OFPST_GROUP request message 09:58:44 right now, the br-int interface (tapXX) of the controller is down 09:59:01 jordi_cttc: can u pls make sure ovs-vswitchd is running ? 09:59:06 ps -aef | grep ovs-vswitch 09:59:24 but sometimes the br-int interface which is down is at the compute node 09:59:58 ps -aef | grep ovs-vswitch root 4852 1 0 08:44 ? 00:00:03 ovs-vswitchd: monitoring pid 4853 (healthy) root 4853 4852 0 08:44 ? 00:00:14 ovs-vswitchd unix:/var/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info --mlockall --no-chdir --log-file=/var/log/openvswitch/ovs-vswitchd.log --pidfile=/var/run/openvswitch/ovs-vswitchd.pid --detach --monitor odl 8389 988 0 09:59 pt 10:00:04 is working 10:00:11 hmm okay 10:00:30 the tap interface being down has nothing to do with the above error. 10:01:07 I do not why but at the time to make stack.. it start to appear ports at odl and some of them are red 10:01:19 then looking at the odl messages, I saw the error 10:01:35 it is like the openflow staff cannot communicate with the br-X interfaces 10:01:39 can u do "ovs-vsctl list bridge" 10:01:58 also "ovs-vsctl list interface" 10:03:01 the bridge instruction reflects that there are 3 br at the control and 1 at the compute node using all of them OpenFlow13 10:03:32 can u pls paste bin the outputs ? 10:03:43 yes sure 10:04:01 thank you very much madhu, I've been googling the errors but I do not find relevant info 10:06:28 madhu: http://pastebin.com/x69Cceyu 10:06:31 at the controller node 10:06:38 I pass you the link to the compute 10:08:01 jordi_cttc: i do see the gre tunnel created here :) 10:08:17 also the ofport is proper 10:08:37 btw. the error message on the ODL controller doesn't mean it is a persistent error. 10:08:46 ahh okk! 10:08:57 the OVS can throw events in a not so consistent order 10:09:09 regarding the ODL message I though that once was appeared, there was connectivity problems 10:09:14 so ODL might throw an error stating hey i cannot find a corresponding OF port number 10:09:32 but later OVS can allocate it and attach to the Interface 10:09:39 and then ODL will converge and act on them 10:09:44 The log of the compute node: http://pastebin.com/viXQWVvP. I have launched two VM machines and I can ping between them 10:10:18 ahh, ok! so I was looking half the movie ;) 10:10:35 ya the logs look good 10:11:17 madhu: so I am afraid... that I am expecting to see something that already is not integrated ;) 10:11:36 madhu: let me explain what I was planning to test with this setup 10:12:02 both VM's pinging between each other, seems logic to me as they reside in the same compute node. 10:12:30 so what I was planning to do whas to creat another private network, and create another router 10:12:51 L3 is not supported yet 10:12:56 then instante vm's on both private networks and communicate between them 10:13:41 but i have to check if it will work with the existing L3 agent. 10:14:01 jordi_cttc: that is targeted for the Helium release 10:14:02 fyi 10:14:26 by the way, creating a third interface in the default router, I have connectivity between VM's machines placed in different machine 10:14:59 madhu: okkk :), so being a starter, I am trying to run very fast ;) 10:15:16 the Helium release of Openstack? 10:15:24 or odl? 10:16:03 odl 10:16:25 finally, could I ping the VMs from outside? 10:16:32 I mean from the controller? 10:18:00 if I do "route" at the controller, I saw the route to the private network 10.0.0.0 by means of the default router (172.24.4.2) 10:18:25 but when I try, the 172.24.4.1 says that it is a unreachable host 10:18:58 i have ping to 172.24.4.1 10:19:08 maybe the down interface is producing that 10:19:26 u have to use floating ip i think 10:20:04 mmm, if I do that, the stack do not work :s at the controller 10:20:36 with tbachman, we fix local.conf and commenting the floating ip was one point to make stack working 10:20:54 * tbachman wakes up...... 10:21:00 scrolling back now..... 10:21:34 tbachman: is the right person for floating-ip. glad he is up ;) 10:21:43 lol 10:21:44 madhu: jeje 10:21:52 tbachman: hi 10:21:55 We need to test — I can do that now 10:21:58 jordi_cttc: hi! 10:22:17 Madhu: this has been there since the beginning, right? 10:22:23 (i.e. not a recent checkin) 10:22:51 (b/c jordi_cttc is running Fed20, which uses the Hydrogen virtualization release) 10:23:04 tbachman: which recent checkin sir ? 10:23:17 we haven't done anything special for floating. it shud just work :) 10:23:19 Just saying that floating IP support has been there. 10:23:21 Right 10:23:21 k 10:23:42 tbachman: if u remember the trello card (which u volunteered for ;) ) 10:23:53 the floating-ip support is to validate that 10:23:59 Yes — hadn’t caught up with alagalah yet on that, but will just do it now :) 10:26:21 so, why I can ping 172.24.4.1 and not 172.24.4.2? 10:26:26 from the controller node? 10:27:25 jordi_cttc: those are the IPs of your instances? 10:27:30 Or is .1 the router? 10:27:37 (that’s the router…. nm) 10:27:44 jordi_cttc: how are you pinging? 10:27:46 .2 is the router that appears in horizon 10:28:01 ping 172.24.24.2 10:28:06 ah 10:28:26 the vm instances are on the range 10.0.0.0 10:28:43 if I do route at my controller I see: 10.0.0.0 172.24.4.2 255.255.255.0 UG 0 0 0 br-ex 10:29:00 stack creates the route at the controller node 10:29:17 but then I can ping 172.24.4.1 but not 172.24.4.2 10:31:08 jordi_cttc: btw — meant to ask… where are you located? 10:31:11 (time zone) 10:31:16 (if I may ask :) ) 10:32:15 yeah sure, no problem UTC+01:00, Barcelone 10:32:26 Ah, nice! 10:32:35 never been…. but would like to some day :) 10:33:11 really nice place! I recommend you, I can provide you some insights ;) 10:33:18 :) 10:33:20 where are you? if I may ask? 10:33:27 I’m in the U.S., in Maryland 10:33:33 Near the city of Baltimore 10:34:06 uooo, this is what I was thinking, ... so maybe I am disturbing you because it is late at night 10:34:13 lol 10:34:16 no way :) 10:34:18 6:30 10:34:24 am a morning guy :) 10:34:36 besides… I think if someone is on IRC, they are fair game 10:34:41 people here have odd hours 10:34:46 especially folks like Madhu :) 10:34:52 (3:30 a.m. for him!) 10:35:27 jeje, wow Madhu!! soo then ... again thank you very much!!! 10:36:09 jordi_cttc: the OVSDB channel in particular seems to attract people who don’t sleep ;) 10:36:13 this is the time of the day i can excuse my stupidity ;) 10:36:30 jordi_cttc: Madhu is the ODL rock star 10:36:32 tbachman: its a strategy 10:36:34 don’t listen to him 10:36:47 (on the stupidity part) 10:37:21 lol. i can even claim ignorance :) "did i really say that". i must have been sleep-walking/talking 10:37:31 .. /chatting 10:38:34 lol 10:38:56 I like, you seem crazy ;) 10:41:55 returning to the mestery ;) 10:42:22 why I cannot ping 172.24.4.2 from the controller node 10:42:32 ? 10:44:29 br-ex at the controller node has to have a gre tunnel? .... I think I am starting to get addicted to this ;) 10:54:51 tbachman: maybe I have not created the link point to the exterior 10:55:12 jordi_cttc: sorry — was preoccupied with configuring devstack 10:55:13 tbachman: ovs-vsctl add-port br-ex eth1 10:55:20 so - what is 172.24.4.1? 10:55:23 ooohhh sorry, excuse 10:55:45 I think this is the gateway, which I can ping from the controller node 10:55:52 and 172.24.4.2? 10:56:00 172.24.4.2 is the IP of the router that appears in horizon 10:56:13 So - the router isnt’ your GW? 10:56:21 it seems so... 10:57:24 in order to do that I was googling and maybe I have missed to configure open-vswitch 10:57:29 tbachman: ovs-vsctl add-port br-ex eth1 10:57:32 with that 10:59:02 jordi_cttc: did you set up the FLOATING_RANGE in local.conf 10:59:03 ? 10:59:09 nooo 10:59:13 ah, k 10:59:14 we removed it 10:59:20 so, it’s the same as where we left it :) 10:59:42 somehow yes 11:00:01 k 11:00:12 according to madhu, the problems I saw at the odl console were not so dramatic... as openvswitch can fix them 11:00:21 let me stack with that — I want to understand just how DS sets up the networking 11:00:35 jordi_cttc: just to make sure I understand — what is it ur trying to do? 11:00:45 Just trying to understand the setup once stacked? 11:01:04 tbachman: I want to test the intregration odl+ostack 11:01:32 So — you are able to stack successfully, and spin up VMs? 11:01:48 tbachman: yes 11:01:57 jordi_cttc: what more do you want to test :) ? 11:02:00 lol 11:02:33 tbachman: jeje, this is what I was trying to check, I thing I am going further that it is already done 11:02:57 not sure — there are other things you can probably play with 11:02:59 tbachman: as both VM's are in the same compute node.. I though it was easy to ping the machines 11:03:08 Oh, wait 11:03:22 you’re trying to ping the VMs from the shell that you ran stack.sh from? 11:03:35 yes, from the controller node 11:03:37 ah 11:03:42 so, there’s another way to do that 11:03:54 you can ping it from the router that’s on their subnet 11:03:59 using “ip netns” commands 11:04:10 jordi_cttc: do you still have the link to that gerrit that I showed you? 11:04:15 the one with the dsconf.sh util? 11:04:21 let me check 11:04:23 If so — there’s another utility in there called pingvm.sh 11:04:27 that will do this for you 11:04:38 tbachman: plenty of utilities, it is like a gold mine 11:04:41 ;) 11:04:44 lol 11:05:04 the shell script isn’t big, so you can peek in to it to see how we’re doing the ping 11:05:15 ok 11:05:21 (credit goes to networkstatic and Madhu for figuring these out — I’m just a packager on this one ;) ) 11:07:27 jeje 11:07:47 tbachman: let me continue explaining my idea... 11:08:51 tbachman: I want to create a second private network and another router to communicate machines in both private networks.. but ... madhu told me that L3 agent is not integrated in odl 11:08:58 so I could not do it 11:09:21 jordi_cttc: I see. I would believe what Madhu says there :) 11:10:51 jeje, me too 11:12:19 oops. lemme explain myself here :) 11:12:27 we haven't tested L3-agent 11:12:37 since we are flooding ARP today 11:12:57 and not removing the L3-agent from the devstack 11:13:18 it could work (as ARP resolution happens behind us) 11:13:43 but.. i have to still check the emac of rule programming for L3-agent 11:14:25 again... l3-agent is something that is flaviof_zzz interest 11:14:36 he is zzz now... but am bet he is interested ;) 11:15:31 jejeje 11:16:34 my computer is close to dye ... too much mambo 11:18:06 lol 11:18:16 jordi_cttc: I’ll see if I can test this out 11:18:22 I still owe Madhu floating IPs :) 11:19:03 tbachman: u r just carrying the sin of others 11:19:06 :) 11:19:11 lol 11:36:50 jordi_cttc: will ping you when I get this resolved 11:37:00 (not sure if it will be today, but hopefully) 12:19:03 tbachman: do not worry tbachman, I will fight it! If we can speak afterwards better! Thanks 16:31:07 . 16:31:30 FlorianOtel: that has a ring of finality to it ;) 16:37:05 dave_tucker: hey buddy 16:37:27 hey Madhu 16:37:47 dave_tucker: i think we shud just leave the UT as UT :-) 16:38:01 just saw Ashwin's comments and I agree with him on that (as u know already) 16:38:06 Madhu: it's not a UT :) but point taken 16:38:13 lol. yes it is not 16:38:16 but it is not IT as well 16:38:19 but anyways. 16:38:26 regarding the failure retry 16:38:38 though the retry will work in this case. 16:38:55 how about the IT with docker instances contending for the same port on the host machine ? 16:39:00 won't that cause problems too > 16:39:22 no sir... as there is only a single slot open on that jenkins node 16:39:34 or at least there should be only one ;) 16:40:08 hmm. 16:40:09 then how come the UT fails ? 16:40:15 because we cannot have multiple parallel jobs. isn't it 16:40:46 correction. ovs-verify has one slot on the jenkins slave. the normal verify job has 2 slots 16:41:08 maybe we shud just change the normal verify to 1 slot as well 16:41:12 problem solved ;) 16:41:20 anyways we have to do that for IT 16:44:03 Madhu: lol. but then we have longer build queues 16:44:20 dave_tucker: thats okay. because we have this problem in IT anyways 16:44:46 and we have to enable IT to the regular Verify and merge jobs 16:45:01 don't want to change the code because of setup environment issues :) 16:46:08 up to you Madhu... as long as we have tests and they run I don't mind 16:46:18 but would prefer that we could fix the IT's to run in parallel 16:46:53 dave_tucker: its a valid point on the longer queues 16:47:17 Madhu: my worry is when we move to dyanamic slaves, that we could have conflicts with other projects 16:47:20 maybe we can first get the IT environment fixed to have it a capability to run in parallel 16:47:38 that won't happen :) 16:47:49 tykeal is awesome in giving us dedicated setup 16:48:12 Madhu: we should catch up with tykeal when he's back 16:48:18 yep. 16:48:36 dave_tucker: for the moment, lets freeze that gerrit and come back to it with a plan 16:48:38 iirc he was against us having special treatment 16:48:45 not us :) 16:48:54 it is for most of the integration tests today 16:49:01 and I don't see any other way actually 16:49:17 ok Madhu: we just need to note that jenkins builds marked unstable may not actually be unstable for now 16:49:18 well. theoretically yes. but practicaly it is a nightmare to share resources that way 16:49:40 shall we make the verify job for 1 slot ? 16:50:09 and am inclined to enable the ova-verify job for the schema branch triggers. 16:50:14 what do u think ? 16:50:18 Madhu: YES! 16:50:40 I was going to do that, but we still have a bug that is causing intermittent IT failure 16:50:41 cool. 16:50:47 btw. mutate works 16:50:54 :) 16:51:13 and i will send the patch to Matt to take a look 16:52:20 Madhu: re jenkins, we could uncheck "Execute concurrent builds if necessary" 16:52:32 but we'll have to do this for both ovsdb-merge and ovsdb-verify 16:52:34 yep. 16:52:40 np. lets do it 16:52:45 ours is not high volume anyways 16:52:46 ok sir. I'm logged in 16:52:49 i'll do it now 16:52:50 thanks buddy 16:53:20 Madhu: actually sir it won't work 16:53:27 :( 16:53:35 merge and verify could be run in parallel 16:53:51 hmm... 16:53:56 need to open a helpdesk ticket for the jenkins master to only have one open build slot 16:54:13 that would be best I think 16:54:21 yes. sir. good point 16:57:41 hello all! does any of you tried to set up openflow rules in a multihomed node with openvswitch, but at the same time, as an endpoint (receiving and sending application traffic)? 16:58:27 Madhu: can you take a look at this one today? would like to get this merged ;) https://git.opendaylight.org/gerrit/#/c/7122/ 16:58:51 yes dave_tucker certainly 16:59:29 thanks Madhu. have abandoned the UT/IT change but have take a todo to refactor that test to look more like a conventional UT 16:59:36 will make my code OCD happy :) 17:00:24 gtg put myles to bed. ttfn 17:13:26 rrsantos: hi 17:13:42 Madhu: hello 17:13:54 i have done something like that 17:14:03 is there a question on that rrsantos ? 17:14:48 well yes, how did you made it? I was considering multiple tap interfaces 17:31:12 Madhu: I was considering something like this http://i.imgur.com/XQgpHnk.png 17:34:14 rrsantos: yes. I did this exactly 17:34:32 and infact our devstack setup has something like this already 17:34:41 all the VMs launched by Nova are Tap interfaces 17:35:01 and the middle layer of OVS are hosted on another node. 17:36:27 ahhh that's great, at least I already have that thing figured out. I think my current issue right now is about routing 17:36:37 and setting up matching flows 17:37:09 I'll have to go now, but meanwhile I'll dig up a bit more on that subject. Thank you Madhu :) 17:39:30 ugh, been so heads down there has been an infomercial in the background for the past 12 hours on repeat 17:39:53 i got good tip on aging secrets now 17:40:34 LOL 17:40:46 hehe hey mlemay 17:41:39 hey Brent.. so got the flow stuff working? 17:42:30 good man, done today 17:42:51 far too many projects on this one 17:43:01 like 6 or something 17:43:42 we here in ovsdb like to turtore ourselves using as many OSS projects as possible 17:44:02 like a mini interop project 18:40:49 Brent Salisbury proposed a change to ovsdb: Adding neutron api v2.0 security group/rules handlers to the Neutron integration in OVSDB plugin. Depends on pending neutron security apis being reviewed. https://git.opendaylight.org/gerrit/7364 18:59:25 Brent Salisbury proposed a change to ovsdb: Adding neutron api v2.0 security group/rules handlers to the Neutron integration in OVSDB plugin. Depends on pending neutron security apis being reviewed. https://git.opendaylight.org/gerrit/7366 19:00:41 . 20:45:46 dfarrell07: hi. can u share the shared calendar ? 20:47:33 Madhu: Yeah, one sec, digging up the link 20:48:00 http://goo.gl/mxwjTb 20:48:18 You can use the button at the bottom right to subscribe to the cal 20:56:08 Madhu: You ment share it here, right? Or more widly? 20:56:17 dfarrell07: thanks sir 20:56:53 Madhu: np :) 21:00:08 thx dfarrell07 that calendar is handy 21:00:17 official? 21:00:42 Mierdin: Thanks! No, the wiki should be considered the offical source. 21:00:52 It does contain all the data from all the wikis though 21:01:34 So unoffically, it's equivalently offical ;) 21:02:03 Mierdin: https://wiki.opendaylight.org/view/Meetings 21:03:55 dfarrell07: rock on! 22:07:00 the miniature keyboard vacuum never really took off did it 22:09:14 I am looking for REST API equivalent of "addTunnel " to automate my testing 22:09:34 standby padma_ will get u the link 22:09:51 thank you 22:10:19 one more help; which module has implementation of this command in ovsdb? 22:11:45 here you go buddy 22:11:46 https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=blob;f=resources/commons/OVSDB_Northbound_APIs.json.postman_collection;h=97a09e4390ce468e3a27eae46873e125a1d2cf16;hb=HEAD 22:12:31 ovsdb/northbound/ovsdb bundle and ConfigurationService in ovsdb/ovsdb 22:13:30 apologies calling you buddy btw in case ur a female. the name didnt register with me 22:13:50 the postman collection i didn't see POST for addTunnel. I saw bridge, port interface add 22:13:54 ah 22:14:18 padma: the postman collection has all the generic info 22:14:26 lemme see if i have an example in my local collection 22:14:27 and you have to construct it for whatever u need. 22:14:32 including the addTunnel 22:14:45 good point could be handy 22:16:21 madhu that's exactly what I am looking for 22:18:19 padma_: http://openvswitch.org/ovs-vswitchd.conf.db.5.pdf is the actual schema that has all the fields exposed by ovsdb 22:18:37 and please use the create Port and create Interface REST-API from that post-man collection 22:18:56 and fill in any data that you want that helps with creating the tunnel base on the schema above 22:19:21 padma_: we can create a specific example of creating a tunnel in post-man 22:19:46 yes that would be helpful 22:19:48 but it would be a good exercise for you to use the above schema and Postman collections and will help you manage the entire switch 22:20:10 thanks madhu, tty everyone in a bit, if i dont have a great weekend. 22:21:50 padma_ I am middle of something now. pls drop me an email and I will give u the exact postman script that takes care of this. 22:21:56 mavenugo@gmail.com 22:22:42 thanks Madhu 21:59:58 networkstatic: you about sir? 22:02:56 ping me if you want help with the neutron stuff bro... can help get the services registered in osgi ;) 22:07:56 cool thanks, was bouncing the APIs off madhu on updates then will put up the patches for review. 22:08:33 the ovsdb part wont build currently as it doesnt have the services to subscribe from in controller yet 22:09:33 just put the patch up as thats the NB ovsdb knowing it would fail build until dependancies get up there 22:10:03 dave_tucker_zzz ah u slept 20:36:27 gawd, i just slept 9 hours 20:36:35 networkstatic: nice! 20:36:44 when’s the last time *that* happened? 20:36:47 wtf, im like a vampire now 20:36:51 lol 20:37:01 i need to start wearing mascarra 20:37:08 goth 20:37:08 get weird with it 20:37:13 own it 20:37:16 yes 20:37:33 so we are off tomorrow 20:37:35 were u running an all-nighter before? 20:37:41 networkstatic: we’re supposedly off now 20:37:46 every night :) 20:37:50 seems like we’re not so good with these things 20:37:51 lol 20:37:55 no not at all 20:38:16 i dont think ive taken a "day off" since ODL became real 20:38:22 wtf would i do? 20:38:24 lol 20:38:25 go play golf? 20:38:29 save kitties 20:38:41 do that on laptop breaks already 20:38:42 lol 20:38:43 build the NSA roomba 20:38:50 see now that 20:38:56 is what we should be doing 20:39:10 Danial is on the robot team or some shit 20:39:14 our intern 20:39:24 we should have him sweat shop it out 20:39:29 folks think that the innocent, cute robot on the floor is just cleaning it up 20:39:32 make money on his labor 20:39:38 really a networked set of super-sensors 20:39:43 for gvmt 20:39:45 child labor 20:39:47 lol 20:39:51 yes 20:40:41 FlorianOtel 20:40:45 networkstatic: no TWS on Monday, right? 20:40:55 ah u r the best 20:40:58 thank u 20:41:01 i send an email now 20:42:51 man, what a team 07:54:43 . 13:28:18 hi guys 15:47:06 padma: just replied to ur email 09:36:55 hi guys 09:37:24 has someone connected a vm to the internet with the integration odl+openstack (fedora20)? 13:27:46 A change was merged to ovsdb: Sample OpenStack/Neutron v2.0 Postman API Collection https://git.opendaylight.org/gerrit/7409 15:49:44 A change was merged to ovsdb: Adding neutron api v2.0 security group/rules handlers https://git.opendaylight.org/gerrit/7366 18:07:01 networkstatic: A week or two ago you were irritated with the openflow folks because they were breaking things in the code. I'm thinking about updating to the latest builds. Have things stabilized? 18:42:54 Mierdin: hi 18:42:57 networkstatic: hey buddy. 18:50:47 Madhu: are we doing WebEx or hangout today? 18:51:01 webex i think :) 18:51:05 k 19:07:27 hi LuisGomez r u joining us ? 19:13:30 https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Test_Provider 19:13:35 is that the link? 19:54:18 Mierdin: hi u r up next on the call sir :) 21:03:29 Madhu, networkstatic: You guys are cool with having the *_integration jobs Ed mentioned, right? I'd gladly take them on. Just didn't hear a clear "ACK, yeah that's a thing we want, someone work on it" 21:04:16 dfarrell07: let me check out the Integration projects and check what is being done there 21:04:27 Madhu: kk 21:04:33 and i would prefer dave_tucker_zzz around to make that call as well. 21:04:41 Sure, makes sense 21:04:48 adding an integration job with a trigger is not a big deal. 21:05:00 just that I want to make sure it all falls in line with the work that we are already taking up 21:05:09 Right, I just took a look and I think I already see clearly how to do it 21:05:15 kk 02:11:38 Mierdin: hi matt 02:11:51 got your email and yes. -p indicates the port forwarding. 02:12:02 the port forwarding instructions are incorrect 02:28:38 Mierdin: use just -p 6641:6640 02:45:27 Mierdin1: just replied to ur email 09:08:20 a stupid question about openflow 09:08:38 two rules identical, one has a field more in the matching 09:09:11 will it be taken the most specific one or one will overwrite the other? 09:23:08 highest priority wins 09:24:07 sorting based on priority, so top to bottom , first match is the end of the table 09:24:45 one field at p=50000 would be elected over a 12-tuple at p=49000 09:24:59 that make sense? 09:42:26 and if they have the same priority? 09:43:01 but one has a field more, for example one has an ingress port specified 09:43:16 on a switch with 3 ports 09:43:25 if a flow comes from port 1 09:43:48 would it be taken the flow rule specifing ingress port=1 over the one which doesn't specify an ingress port at all? 10:06:06 phate06: if the priority is not the same, the result is not very deterministic 10:06:37 phate06: AFAIK, the first rule will be used for the match 10:07:09 phate06: what I'm sure about is that the number and type of match fields does not matter 10:07:22 phate06: no such thing as a more specific match 10:51:52 ok too bad... thanks for the answer:) 20:10:34 anyone know how to disable IPv6 in local.conf on the compute node? 20:15:13 networkstatic: for SHAME 20:15:23 lolz 20:15:34 dont u dare tell ed 20:15:36 :) 20:17:01 how much is my silence worth to you? :) 20:32:11 Madhu: would love to formally document the vagrant stuff for you guys if that's cool 20:32:21 there's a brief mention on the main page but would love a full walkthrough 20:32:26 Mierdin1: pls do sir :) 20:32:35 how do I go about getting perms to do so? 20:32:41 Mierdin1: we can't have enough documentation 20:32:53 perms are all open for all in the wiki :) 20:33:08 you can go ahead and add a page under ovsdb and start docing:) 20:34:57 +Cats 20:35:09 im tired of +1s, too impersonal 20:35:16 im not a machine 20:36:15 networkstatic: purr purr 20:36:18 tired of LOLs ;) 20:36:28 LOL 20:36:31 PURRR 20:36:48 IM TIRED OF LOWER CASE LETTERS TOO 20:36:54 FROM HERE ON OUT 20:36:57 IM SHOUTING 20:37:15 your PURRR is like ROAR 20:37:18 * Madhu scared 20:37:18 hahaha 20:37:56 and this will be tweeted soon : "networkstatic: anyone know how to disable IPv6 in local.conf on the compute node?" 20:38:01 Time to get serious https://www.dropbox.com/s/i4qs9uy3xt11yw8/Screenshot%202014-05-28%2016.37.58.png 20:38:02 maybe cc Ed 20:38:04 NOOOOOOO 20:38:12 lol 20:38:22 :) 20:38:33 serious business. love it. 20:38:34 the v6 harrasment is like a dose of my SDN twitter trolling 20:38:53 i dont remember anything about v6 20:38:59 other then it looks like a mac address 21:10:44 networkstatic: in fedora, you can do it by changing grub: http://www.server-world.info/en/note?os=Fedora_19&p=initial_conf&f=3 21:11:10 networkstatic: https://www.dropbox.com/s/gwtxyp5q81v1abx/Screenshot%202014-05-28%2017.11.07.png 21:11:46 networkstatic: I like the "serious" pic :) 21:21:24 ah nice thanks flaviof didnt think about just disabling :) 21:46:28 I'm trying to read the observation ID from the IPFIX object. It's defined to return OvsDBSet but seems to be actually retirning OvsDBSet 21:57:23 jimooo99: i don't know of anyone testing ipfix table :) other than you. 21:57:33 so please file a bug whenever u find 1 21:57:42 and 1 of us (including you :) ) can fix that 22:04:41 the latest builds seem really broken. Can't run on windows at all and now it just connects and disconnects repeatedly in linux. So many exceptions that my own logging gets lost. 01:33:41 I presume everyone's planning on attending this? http://events.linuxfoundation.org/events/opendaylight-developer-design-forum 01:33:49 About to request invite before I forget 02:37:31 Mierdin roger buddy 02:37:38 thats the next big one 03:29:16 networkstatic: cool, sent 04:33:07 Mierdin excellent 01:56:39 Hi folks 01:57:04 Anyone willing to help a guy out trying to get opendaylight+openstack to work? 01:58:16 @Mierdin, I cannot think of a reason why you could not have a compute node in diff DC assuming your network plugin worked. 01:59:01 The local and vlan neutron plugins assume you are plugged into the same switch 02:17:07 I've got a 3 compute nodes and what I call my control/network node plus opendaylight 02:17:35 Got ML2 configured with opendaylight driver, all my ovs instances pointed to opendaylight 02:17:58 looks like opendaylight sets up VXLan tunnels between all the OVS instances 02:18:22 When I try to boot a VM, I get: {u'message': u'Unexpected vif_type=binding_failed', u'code': 500, u'details': u' File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 258, in decorated_function 10:46:13 hello world 19:19:29 #endmeeting