Tuesday, 2015-08-11

mgagnemdorman: oh, I didn't get a notice. I was wondering if you were running the l3 agent or not.00:08
mgagnemdorman: I settled to write my own L3 agent and I now wonder how the hell people develop against Neutron when extending or writing their own plugins. Class interfaces aren't well defined and you have to reverse engineer the whole thing to understand what's going on...00:10
*** mahito has joined #openstack-operators00:11
*** SimonChung has quit IRC00:20
*** geoffarnold has quit IRC00:23
mgagnemdorman: and it would be great if L3NATAgent was decomposed a bit more, there is a lot of common code in there which could be useful for a developper without having L3NATAgent polluted by ha.AgentMixin or dvr.AgentMixin :-/00:27
mdormanhave ot check with klindgren__ to be sure, but i am pretty sure we are not running the l3 agent00:27
mdormanwe might have a ‘dummy’ one or something that doesn’t actually exist other than in the db, but i am not 100% sure on that00:28
mdormannot real surprised to hear that re: neutron code00:28
mdormanso did you work it out to come to the meetup next week?00:28
mgagnestill no news from my boss :-/00:28
mgagneI really wish to make it00:29
mgagnemdorman: yea... I started with the router service_plugin itself and found that all the code in there assumes there is an agent. And coding stuff in the plugin would mean calls will be sync with my customer network manager/service, at the risk of blocking neutron-server itself completely.00:29
mgagnemdorman: so I moved my interest to neutron-l3-agent (L3NATAgent) and found that creating my own is more or less useful work since all the hard work (I'm interested in) is done in the router_info class so I only need to write my own router class. but l3-agent still has some assumptions about namespace and interface_driver usage hard-coded in there which I doesn't care about. :-/00:32
mdormanyeah sounds fun :)00:41
mgagneyea, I'm screaming in my head atm00:42
WormManI'm only cursing at cinder's netapp driver right now :)00:43
mgagnehaha00:44
mgagneif only some part of the initialization process was moved to a method, I could redefine them and ignore them :D00:45
mgagneI however don't understand why it's still named "L3NATAgent" when there is no NAT in the agent implementation.00:46
WormMansigh, it appears openstack's preferred_target on netapp iscsi is the first one, needless to say that causes problems when we're on a different firewall than that address00:49
*** gyee has quit IRC00:53
*** mdorman has quit IRC00:53
*** radez is now known as radez_g0n300:59
*** radez_g0n3 is now known as radez01:03
*** SimonChung has joined #openstack-operators02:03
*** SimonChung1 has joined #openstack-operators02:04
*** SimonChung has quit IRC02:07
*** hakimo_ has joined #openstack-operators02:52
*** hakimo has quit IRC02:54
*** david-lyle has quit IRC03:21
*** fawadkhaliq has joined #openstack-operators03:29
*** britthouser has quit IRC03:38
*** logan2 has quit IRC03:47
*** jkraj has joined #openstack-operators03:54
*** logan2 has joined #openstack-operators03:55
*** SimonChung has joined #openstack-operators04:03
*** SimonChung1 has quit IRC04:05
*** jasondotstar has quit IRC04:06
*** fawadkhaliq has quit IRC04:21
*** michchap has quit IRC04:30
*** jkraj has quit IRC04:38
*** david-lyle has joined #openstack-operators04:40
*** britthouser has joined #openstack-operators04:41
*** michchap has joined #openstack-operators04:50
*** Marga_ has quit IRC05:03
*** Marga_ has joined #openstack-operators05:04
*** SimonChung has quit IRC05:06
*** jkraj has joined #openstack-operators05:07
*** fawadkhaliq has joined #openstack-operators05:22
*** fawadk has joined #openstack-operators05:31
*** fawadkhaliq has quit IRC05:31
*** SimonChung has joined #openstack-operators05:34
*** belmoreira has joined #openstack-operators05:43
*** SimonChung has quit IRC06:05
*** SimonChung has joined #openstack-operators06:05
*** SimonChung has quit IRC06:08
*** SimonChung has joined #openstack-operators06:08
*** SimonChung has quit IRC06:14
*** jkraj has quit IRC06:36
*** matrohon has joined #openstack-operators06:52
beddarimfisch: so no TripleO but rather using Docker and its related toolchains? Was there much discussion around that? :)07:10
*** arcimboldo has joined #openstack-operators07:10
beddarimfisch: I think it is wise and would want the same sometime in the (not too distant) future07:11
*** jkraj has joined #openstack-operators07:22
*** bvandenh has joined #openstack-operators07:35
*** jasondotstar has joined #openstack-operators07:44
*** jasondotstar has quit IRC07:48
*** fawadk has quit IRC08:25
*** fawadkhaliq has joined #openstack-operators08:26
*** mahito has quit IRC08:34
*** jasondotstar has joined #openstack-operators08:57
*** bvandenh has quit IRC09:03
*** ToMiles has quit IRC09:04
*** Miouge has quit IRC09:05
*** Miouge has joined #openstack-operators09:08
*** Miouge has quit IRC09:10
*** bvandenh has joined #openstack-operators09:29
*** bvandenh has quit IRC09:38
*** arcimboldo has quit IRC09:41
*** fawadkhaliq has quit IRC10:22
*** fawadkhaliq has joined #openstack-operators10:22
*** arcimboldo has joined #openstack-operators10:37
*** arcimboldo has quit IRC10:37
*** arcimboldo has joined #openstack-operators10:37
*** bvandenh has joined #openstack-operators10:57
arcimboldois there anyone running openstack with ceph and having troubles when more than one volume is attached to the VM?11:15
*** saneax has joined #openstack-operators11:23
*** belmoreira has quit IRC11:35
*** ggillies has quit IRC11:47
*** ggillies has joined #openstack-operators11:48
*** bvandenh has quit IRC12:03
*** saneax has quit IRC12:17
*** pontusf1 has quit IRC12:18
*** saneax has joined #openstack-operators12:18
*** bvandenh has joined #openstack-operators12:28
*** saneax has quit IRC12:30
*** saneax has joined #openstack-operators12:34
*** bvandenh has quit IRC12:36
*** jaypipes has joined #openstack-operators12:44
*** Piet has quit IRC12:47
*** radez is now known as radez_g0n313:01
*** pontusf has joined #openstack-operators13:10
mfischbeddari: yep no triple o13:14
*** ferest has joined #openstack-operators13:18
*** fawadkhaliq has quit IRC13:20
*** ferest has quit IRC13:22
*** VW_ has joined #openstack-operators13:30
*** ruagair has quit IRC13:30
*** ruagair has joined #openstack-operators13:32
*** david-lyle has quit IRC13:36
*** SimonChung has joined #openstack-operators13:36
*** bhunter71 has quit IRC13:40
*** esker has quit IRC13:59
*** dminer has joined #openstack-operators14:00
*** saneax has quit IRC14:00
*** fawadkhaliq has joined #openstack-operators14:01
*** Piet has joined #openstack-operators14:01
*** Piet has quit IRC14:05
*** Piet has joined #openstack-operators14:05
*** radez_g0n3 is now known as radez14:13
klindgren__mgagne, we don't run the l3agent14:46
*** mdorman has joined #openstack-operators14:51
*** bhunter71 has joined #openstack-operators14:54
*** gfa is now known as gfa_15:03
*** gfa_ is now known as gfa15:05
mgagneklindgren__: thanks for the info. I will try to go down the path of writing my own agent =)15:09
mgagneklindgren__: looks like you need to run a mechanism agent on the l3 agent or ports will fail to "bind"15:10
*** david-lyle has joined #openstack-operators15:15
*** SimonChung has quit IRC15:16
*** saneax has joined #openstack-operators15:18
klindgren__yea - so all of our floating ip's actually show up as status down - because of that15:29
mgagneworking on the mech part now15:39
klindgren__are you going to be doing bgp advertisements in the agent- or actually making something that logs in to a router and applied the appropriate config?15:40
*** radez is now known as radez_g0n315:41
*** geoffarnold has joined #openstack-operators15:49
*** geoffarnold has quit IRC15:51
*** geoffarnold has joined #openstack-operators15:51
*** arcimboldo has quit IRC15:53
mgagneklindgren__: we have a network management system already. we will just proxy the calls to it15:56
mgagneklindgren__: we are looking for floatingips support first. we might implement more later15:56
klindgren__ah kk15:56
mgagneyea15:57
klindgren__we proxy the calls into our system as well15:57
mgagnehehe15:57
klindgren__we jsut did it on the api side vs's the agent side15:57
klindgren__since it was much easier to add in15:57
klindgren__but it does have the downside of making your system inline to the response time of the requests15:57
klindgren__we might refactor that bit later on15:58
mgagneyea. I however fear this might block the API if the network manager doesn't respond in a timely fashion15:58
mgagneyea15:58
*** jasondotstar has quit IRC16:00
*** gyee has joined #openstack-operators16:03
*** SimonChung has joined #openstack-operators16:06
*** j05hk has joined #openstack-operators16:09
mgagneand now, why can't I merge both l3-agent and mech agent :D16:10
*** geoffarnold has quit IRC16:10
*** geoffarnold has joined #openstack-operators16:11
mgagnebetter not :-/16:16
claytonanyone else run into issues with scheduler_tracks_instance_changes defaulting to true on kilo?16:17
*** ig0r_ has joined #openstack-operators16:20
claytonwe did a prod kilo upgrade last night and having that on (and it defaults to on) lead to nova-scheduler chewing up a whole core and it being so busy it couldn't reply to rabbit heart beats in a timely fashion16:20
*** arcimboldo has joined #openstack-operators16:22
mgagneI can't see how this could end up well with lot of instances... :-/16:25
claytonyeah, and this actually is even worse - https://github.com/openstack/nova/commit/82cc056fb7e1b081a733797ed27550343cbaf44c16:25
claytonthere is a docimpact tag, but nothing ever showed up in the docs or in the release notes that I can see16:25
*** SimonChung has quit IRC16:27
*** SimonChung1 has joined #openstack-operators16:27
mgagneI think they didn't catch it because heartbeat is disabled by default now16:27
claytonwell, it's bad even without heartbeat16:28
claytoneven after we turned off heartbeat it was so busy it failed to schedule instances.16:29
mgagne:-/16:30
mgagnethanks for the heads up...16:30
mgagneI might just end up updating the port bindings from the l3-agent ^^'16:32
claytonfwiw, we're using heartbeats with rabbit behind a load balancer in prod now and I hate to curse myself, but no issues so far.16:38
claytonklindgren__: ^^^16:38
klindgren__what version of oslo_messaging? 1.8.3?16:40
clayton1.8.3-0ubuntu0.15.04.1~cloud016:41
klindgren__kk16:41
klindgren__we are running 1.8.3 as well - we were running 1.8.1 iirc under juno16:42
klindgren__I will say that with 1.8.3 I have seen some rabbitmq stuff16:42
klindgren__but this was related to cells16:42
*** radez_g0n3 is now known as radez16:43
*** ig0r_ has quit IRC16:48
*** arcimboldo has quit IRC16:51
*** arcimboldo has joined #openstack-operators16:51
*** j05hk has quit IRC16:54
*** matrohon has quit IRC16:55
*** arcimboldo has quit IRC16:58
mgagnealright, update on my adventure: you don't need an agent like I thought. you can write a mechanism driver and just load it with the others in ml2_conf.ini (mechanism_drivers) on the node running neutron-server. There is a very well documented ABC class (MechanismDriver) which explains how to write your own mechanism. this is were you can bind the port.17:03
*** jasondotstar has joined #openstack-operators17:03
*** j05hk has joined #openstack-operators17:06
*** SimonChung1 has quit IRC17:07
*** SimonChung has joined #openstack-operators17:07
*** ggillies has quit IRC17:20
*** VW_ has quit IRC17:21
WormMansigh, cinder netapp iscsi volume broken in my environment...17:21
*** VW_ has joined #openstack-operators17:22
WormManso, do I try nfs or fix iscsi17:22
*** ggillies has joined #openstack-operators17:22
*** VW_ has quit IRC17:26
*** arcimboldo has joined #openstack-operators17:31
*** arcimboldo has quit IRC17:35
*** VW_ has joined #openstack-operators17:40
*** SimonChung1 has joined #openstack-operators17:49
*** SimonChung has quit IRC17:49
*** harlowja has quit IRC17:51
*** harlowja has joined #openstack-operators17:54
*** derekh has joined #openstack-operators17:56
klindgren__welcome back17:59
*** klindgren__ is now known as klindgren17:59
*** derekh has quit IRC18:06
*** j05hk has quit IRC18:14
*** j05hk has joined #openstack-operators18:17
*** SimonChung has joined #openstack-operators18:17
*** ig0r_ has joined #openstack-operators18:17
*** SimonChung has quit IRC18:17
*** SimonChung2 has joined #openstack-operators18:17
*** SimonChung1 has quit IRC18:18
*** ig0r_ has quit IRC18:18
*** geoffarnold has quit IRC18:22
*** ig0r_ has joined #openstack-operators18:28
*** geoffarnold has joined #openstack-operators18:37
*** geoffarnold is now known as geoffarnoldX18:38
*** geoffarnoldX is now known as geoffarnold18:44
*** SimonChung has joined #openstack-operators18:45
*** SimonChung2 has quit IRC18:45
*** VW_ has quit IRC18:53
*** VW_ has joined #openstack-operators18:54
*** geoffarnold has quit IRC18:54
*** geoffarnold has joined #openstack-operators18:55
*** VW_ has quit IRC18:58
*** ig0r_ has quit IRC18:59
*** geoffarnold has quit IRC19:02
*** geoffarnold has joined #openstack-operators19:03
*** ig0r_ has joined #openstack-operators19:04
*** geoffarnold has quit IRC19:14
*** VW_ has joined #openstack-operators19:18
*** j05hk has quit IRC19:22
*** alejandrito has joined #openstack-operators19:24
*** j05hk has joined #openstack-operators19:28
*** geoffarnold has joined #openstack-operators19:28
*** gyee has quit IRC19:31
*** jkraj has quit IRC19:43
*** ig0r_ has quit IRC19:58
*** Dyon has quit IRC20:00
*** ig0r_ has joined #openstack-operators20:08
*** fawadkhaliq has quit IRC20:10
*** geoffarnold has quit IRC20:15
*** morgan_503 is now known as morgan_40420:23
*** VW_ has quit IRC20:27
*** VW_ has joined #openstack-operators20:28
*** VW_ has quit IRC20:30
*** VW_ has joined #openstack-operators20:31
*** VW_ has quit IRC20:49
*** VW_ has joined #openstack-operators20:50
*** VW_ has quit IRC20:50
*** VW_ has joined #openstack-operators20:51
*** ig0r_ has quit IRC20:58
*** morgan_404 is now known as morgan_41021:04
*** morgan_410 is now known as morgan_40421:05
*** saneax has quit IRC21:07
*** Piet has quit IRC21:18
*** Piet has joined #openstack-operators21:22
*** j05hk has quit IRC21:38
*** alejandrito has quit IRC21:41
*** j05hk has joined #openstack-operators21:44
*** j05hk1 has joined #openstack-operators21:45
*** ruagair has quit IRC21:48
*** j05hk has quit IRC21:49
mgagnemdorman: so I got my custom router and mechanism driver in place. Router is created, ports are bound correctly and floatingips are now active when associated to instances :D21:59
*** SimonChung has quit IRC22:03
*** SimonChung1 has joined #openstack-operators22:03
*** SimonChung1 has quit IRC22:03
*** SimonChung has joined #openstack-operators22:03
*** SimonChung1 has joined #openstack-operators22:04
*** SimonChung has quit IRC22:04
*** VW_ has quit IRC22:12
*** VW_ has joined #openstack-operators22:13
*** VW_ has quit IRC22:17
*** dminer has quit IRC22:27
*** bhunter71 has quit IRC22:32
mdormanawesome22:35
mdormani wish we were as fast as you :)22:35
*** VW_ has joined #openstack-operators22:43
*** jaypipes has quit IRC22:50
*** saneax has joined #openstack-operators22:53
*** SimonChung1 has quit IRC22:54
*** SimonChung has joined #openstack-operators22:54
mgagneI have yet to wire with our network manager :-/22:57
mgagneit's only configuring the floating ip in syslog for now :P22:57
mgagnemdorman: my mechanism driver is similar to this one: https://gist.github.com/mgagne/f38bfb96f4340e92f93b23:02
*** ruagair has joined #openstack-operators23:15
*** morgan_404 has quit IRC23:29
*** VW_ has quit IRC23:29
*** VW_ has joined #openstack-operators23:30
*** morganfainberg has joined #openstack-operators23:31
*** morganfainberg is now known as morgan_40423:32
*** VW_ has quit IRC23:34
*** VW_ has joined #openstack-operators23:52
*** alop_ has joined #openstack-operators23:56
*** alop has quit IRC23:56
*** alop_ is now known as alop23:56
*** alejandrito has joined #openstack-operators23:57
*** david-lyle has quit IRC23:58
*** alop has quit IRC23:58
*** david-lyle has joined #openstack-operators23:58

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