Thursday, 2015-07-23

*** mahito has joined #openstack-operators00:04
*** alop has quit IRC00:27
*** gyee has quit IRC00:33
*** `mjr_ has quit IRC00:44
*** chlong has quit IRC00:52
*** klindgren has joined #openstack-operators01:27
*** chlong has joined #openstack-operators02:11
*** robksawyer has joined #openstack-operators02:18
*** hakimo_ has joined #openstack-operators02:52
*** hakimo has quit IRC02:55
*** bradjones has quit IRC03:03
*** bradjones has joined #openstack-operators03:04
*** bradjones has quit IRC03:04
*** bradjones has joined #openstack-operators03:04
*** Marga_ has quit IRC03:13
*** robksawyer has quit IRC03:25
*** cpschult has joined #openstack-operators03:42
*** mahito has quit IRC03:59
*** HenryG has quit IRC04:09
*** HenryG has joined #openstack-operators04:12
*** cpschult has quit IRC04:28
*** robksawyer has joined #openstack-operators04:31
*** mahito has joined #openstack-operators04:40
*** maishsk has quit IRC04:51
*** mahito has quit IRC05:04
*** mahito has joined #openstack-operators05:05
*** mahito_ has joined #openstack-operators05:08
*** mahito has quit IRC05:09
*** bvandenh has joined #openstack-operators05:39
*** bhunter71 has quit IRC05:42
*** mmorais has quit IRC05:58
*** robksawyer has quit IRC06:07
*** robksawyer has joined #openstack-operators06:08
*** Miouge has joined #openstack-operators06:15
*** maishsk has joined #openstack-operators06:16
*** maishsk has quit IRC06:26
*** maishsk has joined #openstack-operators06:28
*** chlong has quit IRC06:49
*** ruagair has quit IRC06:54
*** maishsk has quit IRC06:59
*** maishsk has joined #openstack-operators07:00
*** bvandenh has quit IRC07:00
*** Marga_ has joined #openstack-operators07:27
*** vinsh_ has joined #openstack-operators07:29
*** vinsh has quit IRC07:31
*** vinsh has joined #openstack-operators07:36
*** vinsh_ has quit IRC07:36
*** subscope has quit IRC07:41
*** subscope has joined #openstack-operators07:55
*** vinsh_ has joined #openstack-operators07:58
*** vinsh has quit IRC07:59
*** vinsh has joined #openstack-operators07:59
*** vinsh_ has quit IRC08:03
*** subscope has quit IRC08:09
*** derekh has joined #openstack-operators08:25
*** subscope has joined #openstack-operators08:25
*** maishsk has quit IRC08:30
*** maishsk has joined #openstack-operators08:31
*** bvandenh has joined #openstack-operators08:45
*** robksawyer has quit IRC08:47
*** robksawyer has joined #openstack-operators08:47
*** saneax has quit IRC09:01
*** mahito_ has quit IRC09:06
*** mahito has joined #openstack-operators09:07
*** mahito has quit IRC09:11
*** bvandenh has quit IRC09:28
*** maishsk has quit IRC09:34
*** bvandenh has joined #openstack-operators09:42
*** saneax has joined #openstack-operators10:19
*** maishsk has joined #openstack-operators10:44
*** chlong has joined #openstack-operators11:08
*** maishsk has quit IRC12:14
*** maishsk has joined #openstack-operators12:19
*** cpschult has joined #openstack-operators12:24
*** j05hk has joined #openstack-operators12:26
*** cpschult has quit IRC12:32
*** VW_ has joined #openstack-operators12:35
*** ferest has joined #openstack-operators12:50
*** bvandenh has quit IRC12:57
*** ferest has quit IRC12:57
*** bvandenh has joined #openstack-operators12:59
*** j05hk has quit IRC13:38
*** j05hk has joined #openstack-operators13:38
*** bvandenh has quit IRC13:42
*** dminer has joined #openstack-operators13:48
*** belmoreira has joined #openstack-operators14:07
*** VW_ has quit IRC14:08
*** VW_ has joined #openstack-operators14:09
*** VW_ has quit IRC14:13
*** zul has quit IRC14:14
*** VW_ has joined #openstack-operators14:18
*** belmoreira has quit IRC14:19
*** rbrooker has joined #openstack-operators14:20
*** zul has joined #openstack-operators14:27
*** jeh has joined #openstack-operators14:40
*** mdamkot_sfdc has joined #openstack-operators14:42
*** maishsk has quit IRC14:59
*** saneax has quit IRC14:59
*** mdorman has joined #openstack-operators15:02
*** bhunter71 has joined #openstack-operators15:07
*** fawadkhaliq has joined #openstack-operators15:07
*** david-lyle has joined #openstack-operators15:17
*** rbrooker has quit IRC15:30
*** SimonChung1 has quit IRC15:36
*** saneax has joined #openstack-operators15:37
*** rbrooker has joined #openstack-operators15:38
*** mdamkot_sfdc has quit IRC15:49
*** kitch_ has joined #openstack-operators16:03
kitch_Anyone with experience taking a deployment with one network node and splitting it into two?16:03
klindgrenI assume that would just be  moving a router to the new node?16:08
klindgrenLike neutron l3-agent-router-remove <l3 agent uuid> <router uuid>16:08
klindgrenneutron l3-agent-router-add <new l3 agent uuid> <router uuid>16:09
*** signed8bit has joined #openstack-operators16:09
klindgrenwe (godaddy) don't use routers/l3 agents in our neutron deployment.  I know that TWC does, I believe they talked about moving routers/agents around.16:10
klindgrenmfisch, clayton, med_ ^^16:10
med_yep16:10
med_one network node: like a single neutron controller and making it several?16:11
med_(for HA)16:11
med_or for segmenting the network kitch_ ?16:11
med_thanks Kris.16:11
klindgrenI assumed splitting for load16:11
mfischwe move routers all teh time16:11
*** rbrooker has quit IRC16:12
med_kitch_, we do this with Neutron with VXLAN and OVS16:12
kitch_med_: for scale out, we have singleton, and things are not going well, time to split the work. i can take an outage, but im not sure what hte process would be16:12
med_we (today) have 3 neutron api endpoints and we'll be scaling that up to 5 or more (RSN)16:12
med_not sure you'll need an outage even16:12
mfischkitch_: bring up a new node, move routers over16:13
kitch_so the trick is, i need to move existing networks to that new node, not just take new ones16:13
med_just bring up (hopefully using some sort of config mgmt tool like Puppet &c) another neutron api endpoint16:13
med_and then do a router delete, router add to the new endpoint16:13
mfischmoving routers is simple16:13
mfischlet me find our tool16:13
* med_ works directly with mfisch on this16:13
mfischneutron l3-agent-router-remove ${SRC_AGENT_UUID} ${ROUTER_UUID}16:13
mfischneutron l3-agent-router-add    ${DST_AGENT_UUID} ${ROUTER_UUID}16:13
mfischin a nutshell16:13
med_^ yep16:14
*** serverascode has quit IRC16:14
kitch_ok, so when new routers are created, it just gets load balanced by virtue of the haproxy in front of the neutron servers?16:14
mfisch you should always have >1 node for this anyway, if it dies, you'd be in trouble16:15
mfischkitch_: no16:15
*** serverascode has joined #openstack-operators16:15
mfischkitch_: that code is explicitly moving it to a node, hence the SRC and DST agent uuids16:15
kitch_right, im saying after i move existing over16:15
kitch_what happens to future routers?16:16
*** SimonChung has joined #openstack-operators16:16
mfischdisable the agent on the old node if you want to16:16
mfischto prevent stuff from coming back16:16
mfischor otherwise neutrons scheduler figures it out for you16:16
mfischnot haproxy afaik16:17
kitch_ah, ok16:17
kitch_that was the part i was missing16:17
kitch_can i split JUST the l3 agent?16:17
kitch_we’re building a new architecture for scale from teh start, but i need a band aid with minimal effort to keep folks happy in the interim16:17
mfischI assume you can run a node with just the l3 agent but I'm not sure16:18
mfischwhy dont you setup this in a VM and try it there first?16:18
klindgrenkitch_, yes - re: new routers the scheduler should split the placement between the l3 agents - I dunno if htat tunable or not16:18
kitch_fair enough, i think ill spin up a test with just another l3 agent, and see if i can remove and add them16:18
kitch_now, question is this, there are active users on those existing routers, i dont believe neutron is going to let me remove the router if its in use, no?16:19
kitch_ohh16:19
kitch_sorry16:19
kitch_im removing the l3-agent-router16:19
kitch_no the router itself16:19
klindgrenso you currently have mutliple services on a node and want to move that stuff to just a new node16:20
klindgren?16:20
kitch_yep16:20
klindgrens/that stuff/l3-agent16:20
klindgrenI would make a new l3-agent node16:21
kitch_well, i want to split the one l3 agent on my current node, out to two l3 agents on other nodes16:21
klindgrenmove the routers to the new node16:21
klindgrenremove the l3 agent from the old node16:21
kitch_yeah, i think im getting it now16:21
*** Guest100_ has joined #openstack-operators16:28
med_and there may be a nominal "blip" for the users16:30
med_and how nominal is relative to the number of routers/etc.16:31
*** signed8bit has quit IRC16:31
*** Guest100_ has quit IRC16:32
*** bvandenh has joined #openstack-operators16:33
*** simonmcc has quit IRC16:38
*** simonmcc has joined #openstack-operators16:38
*** derekh has quit IRC16:46
kitch_sure16:48
kitch_Thanks folks for the thoughts and info, ill report back with whatever we end up doing :)16:49
*** jraim has quit IRC17:07
*** jraim has joined #openstack-operators17:08
*** alop has joined #openstack-operators17:09
*** Guest100_ has joined #openstack-operators17:11
*** fawadkhaliq has quit IRC17:11
*** fawadkhaliq has joined #openstack-operators17:11
kitch_Just curious, if one were to create a node with only the l3 agent on it, can i really get away with it beign the only openstack service there?17:24
*** Guest100_ has quit IRC17:30
klindgrenkitch_, outside of running whatever L2 agent - I dont see why you would need to run anything else on that node - unless you are doing fwaas or  something similar.  DHCP does not need to be on the same network node as the router.17:32
*** signed8bit has joined #openstack-operators17:33
*** signed8bit is now known as signed8bit_ZZZzz17:46
*** signed8bit_ZZZzz is now known as signed8bit17:48
*** bvandenh has quit IRC17:53
kitch_klindgren: ok, so drag along our ml2 and ovs with l3 and we should be set17:57
*** slaweq has joined #openstack-operators18:00
klindgrenkitch_, right18:11
kitch_Wish us luck. I’ll be quite happy to get off of rhel 6.5 and on to multi-ubuntu nodes18:13
klindgrenso we run dhcp on as a standalone service on a set of nodes - it needs the L2 stuff (for us openvswitch-agent) to configure it to talk on the correct network, then we only have the dhcp agent running on that node.18:13
klindgrenwe use Cent 6 and Cent7 - we haven't had any issues18:13
klindgrenoutside of the python 2.6 stuff.  But I have a work aroudn for that so *shrug*18:14
*** signed8bit is now known as signed8bit_ZZZzz18:33
*** signed8bit_ZZZzz is now known as signed8bit18:35
*** Miouge has quit IRC18:36
kitch_so no performance issues with things like namespaces on cent6? klindgren18:39
klindgrenkitch_, we only run dhcp-agent18:39
klindgrenso not that we have seen18:39
klindgrenthough we are movign those servers to cent718:40
klindgrenactually we are mostly moved to cent718:40
klindgrenwe also have all of our instances configured to do config-drive for statically configuring their network stuff as well18:40
kitch_ok :) I was seeing 2-3x performance on modern kernel vs 2.6.x of 618:40
klindgrenbecause it sucks if your instances stop trying to querry for a lease18:41
*** Miouge has joined #openstack-operators18:41
klindgrenI assume you were mainly seeing that around the l3-agent stuff?18:41
klindgrenIE iptables inside a netns18:42
*** bvandenh has joined #openstack-operators18:43
kitch_  yeah18:53
*** bitblt has joined #openstack-operators18:55
*** bitblt has quit IRC18:58
*** VW_ has quit IRC18:58
*** Miouge has quit IRC18:58
*** VW_ has joined #openstack-operators18:59
*** VW_ has quit IRC18:59
*** VW_ has joined #openstack-operators18:59
*** bvandenh has quit IRC19:02
klindgrenkitch_, we run all of our VM's on shared provider networks - so no routers for us19:05
*** yuriy has joined #openstack-operators19:12
kitch_klindgren: lucky you :D19:19
mnasersame ^19:22
mnaserwe do offer the ability for users to create their own networks if they want19:22
mnaserso it gives them the best level of performance while giving them the ability to still have the whole my-own-network-with-nat-routers stuff19:23
klindgrenyea - we made modification to neutron to allow us to inject routes for floating ip's into the network19:27
klindgrenso that vm's can have floating ip's19:27
klindgrenand actually have those IP's show up in the vm and be used "normally"19:27
klindgrenwe specifically prevent people from creating routers - 99% of our end users don't care about that stuff anyway19:28
klindgrenthose that do care about that stuff really want L2 adjacency - which we don't support in our model.  As a company as a whole we are actively moving away from depending on L219:29
*** bvandenh has joined #openstack-operators19:30
klindgrenso they want us to build overlays to solve their problems - which I am not keen on doing - since overlays in my experience are problematic.  Plus it gets you to a point where you are always trying to figure out how to scale a router to deal with the load that vm's behind that router serv's19:31
klindgrenIE I can put 10 large vm's behind a singe router and the through put of those vm's is directly related to the ability of that single router to process packets19:32
*** bvandenh has quit IRC19:37
*** Miouge has joined #openstack-operators19:37
*** yuriy has quit IRC19:43
*** Miouge has quit IRC19:47
*** Miouge has joined #openstack-operators20:01
*** Miouge has quit IRC20:02
*** bvandenh has joined #openstack-operators20:19
*** bhunter71 has quit IRC20:20
*** kitch_ has quit IRC20:40
*** signed8bit has quit IRC20:42
*** markvoelker has quit IRC20:42
klindgrenwhen is the LDT meeting  today? - VW_21:11
klindgren9PM mountain - I can timezone...21:13
*** VW_ has quit IRC21:32
*** VW_ has joined #openstack-operators21:33
*** hakimo has joined #openstack-operators21:36
*** hakimo_ has quit IRC21:36
*** VW_ has quit IRC21:37
*** VW_ has joined #openstack-operators21:40
VW_yep klindgren that is correct21:40
VW_:)21:40
klindgrenhrm - mightn ot be able to make it today :-/21:41
jlkhrm?21:42
jlkstrange21:42
*** fawadk has joined #openstack-operators21:47
*** fawadkhaliq has quit IRC21:48
jlkso gmail is pretty bad when the time says 03:00UTC  but clicking 22:00 CDT showed the right time.21:48
*** slaweq has quit IRC21:49
*** bhunter71 has joined #openstack-operators21:50
*** SimonChung has quit IRC21:52
*** dminer has quit IRC21:56
*** SimonChung has joined #openstack-operators21:59
*** jeh has quit IRC22:05
*** hakimo has quit IRC22:12
*** hakimo has joined #openstack-operators22:13
*** fawadk has quit IRC22:31
*** kitch has joined #openstack-operators22:32
*** signed8bit has joined #openstack-operators22:34
*** bvandenh has quit IRC22:37
*** signed8bit has quit IRC22:37
*** signed8bit has joined #openstack-operators22:38
WormManahh, vif_type=binding_failed... the most useless error ever22:42
jlk"Error scheduling instance"22:43
*** signed8b_ has joined #openstack-operators22:45
*** signed8bit has quit IRC22:46
*** chlong has quit IRC22:52
klindgrenjlk guessing that should be 15:00UTC22:56
jlkwell, it's 22:57 UTC right now22:57
jlkso 3:00 UTC seems right22:57
klindgrenah - I htin the issue its it would 3:00UTC tommorrow22:57
klindgrennot today22:57
klindgrenthink*22:57
klindgrenWormMan, and JLK +1 to both of those22:58
klindgrenor "No Valid Host"22:58
jlkgmail is trying to say that 0300 UTC is 8am for me, when in reality it's 8pm for me22:59
*** david-lyle has quit IRC23:02
*** VW_ has quit IRC23:12
*** VW_ has joined #openstack-operators23:13
*** signed8b_ is now known as signed8bit_ZZZzz23:15
*** signed8bit_ZZZzz is now known as signed8b_23:15
*** VW_ has quit IRC23:17
*** SimonChung has quit IRC23:21
*** VW_ has joined #openstack-operators23:27
*** signed8b_ is now known as signed8bit_ZZZzz23:28
WormManwoo, progress...23:31
WormManFailed to start vnc server on my_ip:023:31
WormManyea, that's not gonna work :)23:31
WormManbut I'm closer to having a cloud23:31
*** signed8bit_ZZZzz is now known as signed8b_23:32
*** david-lyle has joined #openstack-operators23:36
*** mahito has joined #openstack-operators23:55

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