Wednesday, 2017-04-26

*** rebase has quit IRC00:21
*** rebase has joined #openstack-operators00:22
*** sticker has joined #openstack-operators00:32
*** vinsh has quit IRC00:34
*** vinsh has joined #openstack-operators00:35
*** arif-ali has quit IRC00:45
*** dalees has quit IRC00:45
*** dalees has joined #openstack-operators00:46
*** arif-ali has joined #openstack-operators00:46
*** Apoorva_ has joined #openstack-operators00:49
*** Apoorva_ has quit IRC00:49
*** Apoorva_ has joined #openstack-operators00:50
*** Apoorva_ has quit IRC00:52
*** Apoorva has quit IRC00:52
*** zerick has quit IRC00:55
*** zerick has joined #openstack-operators00:57
*** haukebruno has quit IRC01:00
*** keekz has quit IRC01:00
*** keekz has joined #openstack-operators01:00
*** haukebruno has joined #openstack-operators01:01
*** tdasilva has quit IRC01:21
*** tdasilva has joined #openstack-operators01:25
*** mriedem has quit IRC01:28
*** haukebruno has quit IRC01:29
*** haukebruno has joined #openstack-operators01:34
*** fragatin_ has quit IRC01:57
*** fragatina has joined #openstack-operators01:58
*** dtrainor has quit IRC02:16
*** rebase has quit IRC02:21
*** rebase has joined #openstack-operators02:22
*** B_Smith has quit IRC02:23
*** rebase has quit IRC02:28
*** cemason has joined #openstack-operators03:06
*** rebase has joined #openstack-operators03:28
*** rebase has quit IRC03:33
*** liverpooler has quit IRC03:43
*** dtrainor has joined #openstack-operators03:51
*** jamemcc has quit IRC04:09
*** JillS has quit IRC04:10
*** arnewiebalck_ has joined #openstack-operators04:13
*** fragatin_ has joined #openstack-operators04:22
*** zenirc369 has joined #openstack-operators04:22
*** fragatina has quit IRC04:26
*** fragatin_ has quit IRC04:27
*** fragatina has joined #openstack-operators04:45
*** fragatina has quit IRC04:45
*** fragatina has joined #openstack-operators04:46
*** JillS has joined #openstack-operators04:56
*** yprokule has joined #openstack-operators04:57
*** jamemcc has joined #openstack-operators04:57
*** slaweq has joined #openstack-operators05:01
*** slaweq has quit IRC05:02
*** arnewiebalck_ has quit IRC05:20
*** sticker_ has joined #openstack-operators05:25
*** slaweq has joined #openstack-operators05:26
*** darrenc has quit IRC05:28
*** darrenc has joined #openstack-operators05:28
*** slaweq has quit IRC05:28
*** sticker has quit IRC05:29
*** rebase has joined #openstack-operators06:10
*** Oku_OS-away is now known as Oku_OS06:11
*** zenirc369 has quit IRC06:16
*** racedo has joined #openstack-operators06:26
*** d0ugal has quit IRC06:39
*** d0ugal has joined #openstack-operators06:41
*** makowals has quit IRC06:44
*** makowals has joined #openstack-operators06:45
*** manheim has joined #openstack-operators07:00
*** racedo has quit IRC07:02
*** tesseract has joined #openstack-operators07:04
*** manheim has quit IRC07:04
*** manheim has joined #openstack-operators07:04
*** pcaruana has joined #openstack-operators07:19
*** robksawyer has joined #openstack-operators07:29
*** robksawyer has quit IRC07:33
*** electrofelix has joined #openstack-operators07:34
*** robksawyer has joined #openstack-operators07:42
*** arnewiebalck_ has joined #openstack-operators07:45
*** robksawyer has quit IRC07:46
*** dbecker has joined #openstack-operators08:00
*** rebase has quit IRC08:04
*** rebase has joined #openstack-operators08:06
*** arnewiebalck_ has quit IRC08:10
*** yprokule has quit IRC08:17
*** racedo has joined #openstack-operators08:30
*** sticker_ is now known as sticker08:33
*** derekh has joined #openstack-operators08:36
*** rebase has quit IRC08:53
*** aojea has joined #openstack-operators08:55
*** aojea_ has joined #openstack-operators09:19
*** aojea has quit IRC09:23
*** haplo37 has quit IRC09:47
*** haplo37 has joined #openstack-operators09:56
*** paramite has joined #openstack-operators10:05
*** B_Smith has joined #openstack-operators10:09
*** slaweq has joined #openstack-operators10:29
*** slaweq has quit IRC10:34
*** JillS has quit IRC10:37
*** jamemcc has quit IRC10:38
*** yprokule has joined #openstack-operators10:57
*** Miouge has joined #openstack-operators11:06
*** JillS has joined #openstack-operators11:16
*** jamemcc has joined #openstack-operators11:16
*** vijaykc4 has joined #openstack-operators12:30
*** vijaykc4 has quit IRC12:32
*** vijaykc4 has joined #openstack-operators12:33
*** liverpooler has joined #openstack-operators12:54
*** mriedem has joined #openstack-operators13:03
*** VW has joined #openstack-operators13:04
*** jamesdenton has joined #openstack-operators13:16
*** tongli has joined #openstack-operators13:20
*** vijaykc4 has quit IRC13:21
*** Miouge has quit IRC13:21
*** fragatina has quit IRC13:40
*** fragatina has joined #openstack-operators13:41
*** catintheroof has joined #openstack-operators13:56
*** chlong has joined #openstack-operators13:58
*** cnf has quit IRC14:04
*** Miouge has joined #openstack-operators14:14
*** slaweq has joined #openstack-operators14:30
*** slaweq has quit IRC14:34
*** manheim has quit IRC14:35
*** manheim has joined #openstack-operators14:40
*** manheim has quit IRC14:46
*** marst has quit IRC14:47
*** manheim has joined #openstack-operators14:48
wasmummoving from kilo to mitaka some quick questions:  We are using network nodes on kilo with vrrp14:48
wasmumhow does this look in mitaka going to linux bridging?  Do you still need your network node, I assume yes.  How does this effect the controller build, does it just get the neutron server service api installed and you build your network nodes as you would build a controller node (acccording to the docs) without the neutron server service?14:50
*** manheim has quit IRC14:53
*** marst has joined #openstack-operators14:54
*** manheim has joined #openstack-operators14:55
*** marst_ has joined #openstack-operators14:55
*** marst has quit IRC14:55
*** manheim has quit IRC14:57
*** tongli has quit IRC15:00
*** cemason has quit IRC15:07
*** cemason has joined #openstack-operators15:09
*** DaSchab has joined #openstack-operators15:09
*** catintheroof has quit IRC15:10
*** catintheroof has joined #openstack-operators15:11
*** DaSchab has quit IRC15:11
*** catintheroof has quit IRC15:11
*** Miouge has quit IRC15:12
*** aojea_ has quit IRC15:29
*** fandi has joined #openstack-operators15:30
*** slaweq has joined #openstack-operators15:32
*** rmart04 has joined #openstack-operators15:37
*** chyka has joined #openstack-operators15:39
*** yprokule has quit IRC15:43
*** Rockyg has joined #openstack-operators15:45
erhudymoving from nova-network to neutron?15:53
*** Caterpillar has joined #openstack-operators15:56
*** jlk has quit IRC16:01
*** jlk has joined #openstack-operators16:02
*** jlk has quit IRC16:02
*** jlk has joined #openstack-operators16:02
*** slaweq has quit IRC16:04
*** rebase has joined #openstack-operators16:18
*** shasha___ has joined #openstack-operators16:21
*** Apoorva has joined #openstack-operators16:22
wasmumerhudy: moving from kilo to mitaka neutron networking in kilo with vrrp an gre overlay and going to mitaka linux bridging with a vxlan overlay and vrrp16:26
*** fragatina has quit IRC16:38
erhudyah, godspeed you, the godaddy people in here have mentioned repeatedly that they want to jettison their OVS stuff in favor of linuxbridge so maybe one of them would have some Top Tips if they've begun moving down that path16:39
*** rebase has quit IRC16:42
*** rebase has joined #openstack-operators16:42
mdormanerhudy: wasmum  yeah don’t really have any practical advice at this point.  that’s still a “it would be nice to do” project on our end.  The biggest challenge for us would be figuring out how to migrate from OVS to linux bridge with minimal impacts to VM connectivity16:45
wasmummdorman: can you disclose how many workloads you average (instance count)?16:46
*** derekh has quit IRC16:46
wasmumat this point were under 200 instances so the impact exists but can be mitigated through politics16:47
mdormanlike VMs per hypervisor?16:47
mdormanwe have on the order of 10s of thousands of instances total16:47
wasmumso moving from ovs to linux bridging is something we need to either commit to now or never.16:47
mdormanyeah now would be the time to do it for sure :)16:47
erhudy<requisite shilling for calico goes here>16:47
wasmumyeah the impact you face would be a resume generating event16:48
mdormanhaha16:48
*** usertm has joined #openstack-operators16:48
mdormantaht’s why we’d have to figure out how to do it in a non impactful way, or with a blip of just seconds16:48
erhudymoving baseline network technologies without user impact seems like a sisyphean task16:49
mdormanagreed.  i am not sure it will ever happen to be honest16:49
wasmumsounds like an awesome challenge.  not sure the grey mass in my head would be able to comprehend how to accomplish that16:49
erhudyi spent about a year researching whether we could jump from nova-network to anything neutron in place before concluding "not without making everyone really mad"16:50
wasmumman how I long for an LTS supported version of openstack16:50
erhudyyou and every other operator16:50
*** tesseract has quit IRC16:51
wasmumyeah, how come that falls silent in the foundation meetings?16:51
*** marst_ has quit IRC16:52
erhudy¯\_(ツ)_/¯16:52
wasmumupgrades and architectural changes are the main obstacles we face presenting a long term solution in an enterprise16:52
erhudyit's why we were on kilo for a long time after EOL, moved to liberty after it was EOL, and will be moving our existing clusters to mitaka even though it's EOL16:53
erhudymost operators in here probably have similar stories16:53
erhudyif you're willing to pay for canonical support, mitaka was part of the xenial LTS release so in a certain sense mitaka is LTS, but supported by canonical16:55
RockygI think the problem with LTS is that the vendors aren't willing to agree on it and make it a priority for their community developers.17:02
RockygLearning how to steer community developers is really hard, I think.17:04
erhudythe lack of an official upstream LTS combined with a 6-month dev cycle means the changes arrive at a bewildering pace17:04
*** fragatina has joined #openstack-operators17:05
RockygVery few devs have ever experienced trying to run/mange a cloud17:05
RockygThey don't feel that pain.17:05
erhudywell, there are a number of devs in here now and i don't want to craptalk them17:06
RockygA number of senior community devs still don't understand why ops don't do continuous deployment17:06
erhudythat particular thought has come to mind, but having been on both sides, as a dev you think about different concerns17:07
RockygIt's not that they're bad.  It's just how do you get them to understand where the code issues intersect the ops pain points.17:07
RockygThey hear the pain, but they need to be aqble to drill down to specific lines of code.17:08
RockygAnd ops don't drill to the code level.17:08
erhudydevstack is now outlawed, every dev has to build their code on a 200-node cluster that will disintegrate under the volume of RPC messages and DB connections17:08
RockygIt's the different fram of references and finding the intersectiing places isn't easy.17:09
RockygUh, erhudy  is that so they solve your problem first ;-)17:09
erhudyidk, i think that handwaves over the capabilities of ops people, the old stereotype of being a "sysop" who has a pile of tribal knowledge shell scripts doesn't really apply these days17:09
RockygNo, the ops guys know, the dev guys know, but they work on totally different types of systems17:10
erhudyas somebody with an ops background, i do think that devs need to walk that walk at least once17:11
erhudyin order to understand why your ops guys are telling you what they are, instead of assuming they're stonewalling because lazy/antagonistic17:12
RockygAnd maybe devops has so much code themselves that devs aren't aware of, it would take some time for a dev to review the ops code base to understand the interoperations between the two code bases.17:12
*** paramite has quit IRC17:12
RockygNah.  The devs don't think ops are lazy.  It's just two different languages with the same words17:12
erhudywe'll have the chance to have our own west side story week after next17:13
erhudydevs are jets, operators are sharks17:13
erhudybrawl in the convention center, total madness17:14
Rockyglol17:14
RockygI've been promoting a take a dev to work day to the ops folks I know, but it hasn't gained much steam.17:15
RockygThe OSIC guys actually have a setup where the devs get a week of ops tasks to learn and do before they start contributing to openstack code17:16
*** cnf has joined #openstack-operators17:18
Rockygalso, with the novanet to neutron move, there were plans and work on smooth migration, but it took so long to actually get the code there that lots of that energy and direction got left on the roadside17:18
erhudyre: that, our specific problem was that we use nova-network in multi-host mode, so our clusters never had network nodes17:19
erhudyand DVR wasn't in the right place at the time, and you still need network nodes to do routing for instances without provider network IPs anyway17:19
RockygOh.  that.17:19
erhudycalico is what we ended up settling on since it's a private cloud17:20
*** aojea has joined #openstack-operators17:20
RockygUh, yeah.  Devs can't code to architectures they don't know about/expect.17:20
erhudyit's not like we hacked multi-host mode into nova-network, it was a flag in nova.conf17:21
RockygI bet you could get Neil Gerram of calico to work through some upgrade scenarios with you at the summit.17:21
RockygJerram17:21
erhudywe already decided our existing nova-network clusters will get upgraded to mitaka and then they can live out the rest of their lives in peace17:22
RockygGrab him if he's there and and do some brainstorming.  He'd be good at that and would even enjoy it.17:22
*** Rockyg has quit IRC17:26
*** Apoorva_ has joined #openstack-operators17:30
*** rebase has quit IRC17:31
*** rebase has joined #openstack-operators17:32
*** makowals_ has joined #openstack-operators17:33
*** Apoorva has quit IRC17:33
*** makowals has quit IRC17:34
*** slaweq has joined #openstack-operators17:37
*** slaweq has quit IRC17:40
*** pcaruana has quit IRC17:40
*** electrofelix has quit IRC18:01
*** aojea has quit IRC18:01
*** aojea has joined #openstack-operators18:04
*** dminer has joined #openstack-operators18:08
*** slaweq has joined #openstack-operators18:11
*** slaweq has quit IRC18:17
*** slaweq has joined #openstack-operators18:18
*** slaweq has quit IRC18:22
*** aojea has quit IRC18:24
*** aojea has joined #openstack-operators18:25
yankcrimelol @ erhudy18:25
yankcrimethat's basically us right now18:26
*** gyee has joined #openstack-operators18:26
yankcrimemoving from one super EOL release to only a vaguely EOL release18:26
yankcrimewith a short-term goal to get to mitaka, which is just about to go EOL18:26
yankcrimefml basically18:26
erhudyliberty's been fine for us, we'll jump them up to mitaka and they'll stick around for a few more years18:27
*** aojea has quit IRC18:29
yankcrimeyeah, it's a desire to layer on some of the newer features such as magnum that's prompted us to get a bit more aggressive with upgrades18:30
yankcrimesticking stuff in containers has really helped18:30
*** Apoorva_ has quit IRC18:37
*** Apoorva has joined #openstack-operators18:38
*** fragatina has quit IRC18:46
*** fragatina has joined #openstack-operators18:46
*** marst_ has joined #openstack-operators18:49
*** shasha___ has quit IRC18:49
klindgren_thats what we are going through right now18:52
*** usertm has quit IRC18:52
klindgren_moving our liberty install into containers18:52
klindgren_we also have a number of patches around cellsv1 that makes upgrading "interesting"18:52
klindgren_especially since nova started moving everything to objects and breaking cells v1 code all over the place18:53
*** VW_ has joined #openstack-operators18:57
*** aojea has joined #openstack-operators18:58
*** VW_ has quit IRC18:59
*** VW_ has joined #openstack-operators18:59
*** VW has quit IRC19:01
*** VW_ has quit IRC19:03
*** VW has joined #openstack-operators19:03
*** fragatina has quit IRC19:04
*** fragatina has joined #openstack-operators19:04
*** racedo has quit IRC19:18
*** racedo has joined #openstack-operators19:20
*** marst_ has quit IRC19:22
*** slaweq has joined #openstack-operators19:23
*** robksawyer has joined #openstack-operators19:23
*** slaweq has quit IRC19:28
*** racedo has quit IRC19:29
*** manheim has joined #openstack-operators19:29
*** robksawyer has quit IRC19:29
*** arnewiebalck_ has joined #openstack-operators19:30
*** arnewiebalck_ has quit IRC19:30
*** rebase has quit IRC19:31
*** arnewiebalck_ has joined #openstack-operators19:32
*** rebase has joined #openstack-operators19:32
*** rmart04 has quit IRC19:33
*** shewless_ has joined #openstack-operators19:55
shewless_Hello. Does anyone have any good reference material for integrating ceph with openstack.  Specifically for using ceph for ephemeral storage (what kind of iops is required)19:56
*** Apoorva has quit IRC19:59
*** dminer has quit IRC20:00
*** fandi has quit IRC20:04
*** aojea has quit IRC20:08
*** rockyg has joined #openstack-operators20:16
*** aojea has joined #openstack-operators20:17
*** Apoorva has joined #openstack-operators20:17
*** VW has quit IRC20:20
*** VW has joined #openstack-operators20:21
*** dminer has joined #openstack-operators20:23
*** dbecker has quit IRC20:25
shewless_I'm not looking for "how" to integrate ceph with openstack.  I'm moreso looking for the performance requirements of the ceph cluster20:28
*** rockyg has quit IRC20:32
zerickshewless_: I guess Red Hat docs would point on that direction20:38
*** rockyg has joined #openstack-operators20:38
shewless_zerick: thanks.. I'm not seeing anything on that subject20:39
*** arnewiebalck_ has quit IRC20:41
*** manheim has quit IRC20:48
*** Fin1te has joined #openstack-operators21:08
*** haplo37 has quit IRC21:09
*** slaweq has joined #openstack-operators21:16
*** Caterpillar has quit IRC21:16
*** haplo37 has joined #openstack-operators21:18
*** dminer has quit IRC21:22
*** slaweq has quit IRC21:30
*** Apoorva_ has joined #openstack-operators21:34
*** Apoorva_ has quit IRC21:36
*** Apoorva_ has joined #openstack-operators21:36
*** Apoorva has quit IRC21:36
zerickshewless_: maybe this? http://www3.intel.com/content/dam/www/public/us/en/documents/reference-architectures/redhat-cloud-blocks-solution-brief.pdf21:43
zerickand this https://access.redhat.com/sites/default/files/attachments/osp10-rhcs2-v1.pdf21:43
*** rockyg has quit IRC21:47
*** chlong has quit IRC21:48
*** Fin1te has quit IRC21:57
*** manheim has joined #openstack-operators21:59
*** Apoorva_ has quit IRC22:02
*** manheim has quit IRC22:03
*** Apoorva has joined #openstack-operators22:03
*** shasha___ has joined #openstack-operators22:09
*** aojea has quit IRC22:10
*** jamesdenton has quit IRC22:12
*** manheim has joined #openstack-operators22:25
*** slaweq has joined #openstack-operators22:31
*** VW_ has joined #openstack-operators22:32
*** slaweq has quit IRC22:35
*** VW has quit IRC22:36
*** VW_ has quit IRC22:36
*** shasha___ has quit IRC22:47
*** Apoorva_ has joined #openstack-operators23:10
*** Apoorva_ has quit IRC23:11
*** Apoorva has quit IRC23:11
*** Apoorva has joined #openstack-operators23:11
*** manheim has quit IRC23:21
*** shasha___ has joined #openstack-operators23:22
*** shasha___ has quit IRC23:27
*** chyka has quit IRC23:32
*** shasha___ has joined #openstack-operators23:36
*** shasha___ has quit IRC23:43

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