Friday, 2017-07-21

*** masber has quit IRC00:33
*** masber has joined #openstack-ha00:33
*** aasmith has joined #openstack-ha00:58
*** masahito has joined #openstack-ha01:11
*** masahito has quit IRC01:13
*** masahito has joined #openstack-ha01:14
*** kgaillot has quit IRC01:24
*** jmlowe has quit IRC01:49
*** masahito has quit IRC01:53
*** masahito has joined #openstack-ha01:53
*** masahito has quit IRC01:59
*** masahito has joined #openstack-ha02:00
*** markvoelker has quit IRC02:09
*** markvoelker has joined #openstack-ha02:09
*** markvoelker has quit IRC02:14
*** yangyapeng has joined #openstack-ha02:31
*** masahito has quit IRC02:43
*** masahito has joined #openstack-ha02:49
*** masahito has quit IRC03:04
*** masahito has joined #openstack-ha04:02
*** masahito_ has joined #openstack-ha04:03
*** masahito_ has quit IRC04:07
*** masahito has quit IRC04:07
*** markvoelker has joined #openstack-ha04:10
*** hoonetorg has joined #openstack-ha04:32
*** masahito has joined #openstack-ha04:35
*** masahito_ has joined #openstack-ha04:37
*** masahito has quit IRC04:40
*** masahito_ has quit IRC04:44
*** markvoelker has quit IRC04:45
*** masahito has joined #openstack-ha04:51
*** masahito_ has joined #openstack-ha04:52
*** masahito has quit IRC04:55
*** masahito_ has quit IRC05:05
*** masahito has joined #openstack-ha05:05
*** masahito has quit IRC05:32
*** radeks has joined #openstack-ha05:34
*** masahito has joined #openstack-ha05:39
*** masahito_ has joined #openstack-ha05:40
*** markvoelker has joined #openstack-ha05:42
*** masahito has quit IRC05:44
*** masahito_ has quit IRC05:45
*** masahito has joined #openstack-ha05:45
*** yangyapeng has quit IRC05:46
*** yangyapeng has joined #openstack-ha05:47
*** masahito has quit IRC05:47
*** masahito has joined #openstack-ha05:47
*** masahito has quit IRC05:49
*** masahito has joined #openstack-ha05:49
*** radeks has quit IRC05:51
*** masahito has quit IRC05:54
*** masahito has joined #openstack-ha05:55
*** masahito has quit IRC06:02
*** masahito has joined #openstack-ha06:02
*** masahito_ has joined #openstack-ha06:07
*** masahito_ has quit IRC06:08
*** masahito has quit IRC06:08
*** masahito has joined #openstack-ha06:08
*** masahito_ has joined #openstack-ha06:10
*** masahito has quit IRC06:12
*** markvoelker has quit IRC06:14
*** masahito_ has quit IRC06:23
*** masahito has joined #openstack-ha06:48
*** radeks has joined #openstack-ha07:02
*** markvoelker has joined #openstack-ha07:11
*** dgurtner has joined #openstack-ha07:24
*** tnarg has quit IRC07:36
*** masahito has quit IRC07:38
*** markvoelker has quit IRC07:45
*** rmart04 has joined #openstack-ha08:04
*** masahito has joined #openstack-ha08:10
*** masahito_ has joined #openstack-ha08:19
*** egonzalez has joined #openstack-ha08:21
*** masahito has quit IRC08:22
*** masahito_ has quit IRC08:25
*** masahito has joined #openstack-ha08:25
*** markvoelker has joined #openstack-ha08:42
*** MatthewLi has quit IRC08:48
*** MatthewLi has joined #openstack-ha08:49
*** MatthewLi has quit IRC08:49
*** masahito has quit IRC08:50
*** MatthewLi has joined #openstack-ha08:51
*** masahito has joined #openstack-ha09:01
*** masahito_ has joined #openstack-ha09:03
*** masahito has quit IRC09:05
*** masahito_ has quit IRC09:12
*** masahito has joined #openstack-ha09:12
*** masahito has quit IRC09:13
*** masahito has joined #openstack-ha09:13
*** masahito has quit IRC09:15
*** masahito has joined #openstack-ha09:16
*** markvoelker has quit IRC09:16
*** MatthewLi has quit IRC09:34
*** masahito has quit IRC09:39
*** markvoelker has joined #openstack-ha10:12
*** yangyapeng has quit IRC10:43
*** markvoelker has quit IRC10:45
*** markvoelker has joined #openstack-ha11:43
*** rossella__ has quit IRC11:50
*** rossella__ has joined #openstack-ha11:53
*** rossella__ has quit IRC11:59
*** rossella__ has joined #openstack-ha12:02
*** markvoelker has quit IRC12:16
*** markvoelker has joined #openstack-ha12:26
*** jmlowe has joined #openstack-ha12:39
*** jmlowe has quit IRC12:40
*** MatthewLi has joined #openstack-ha13:01
*** yangyapeng has joined #openstack-ha13:10
*** catintheroof has joined #openstack-ha13:25
*** catinthe_ has joined #openstack-ha13:26
*** jmlowe has joined #openstack-ha13:30
*** catintheroof has quit IRC13:30
*** Qiming has quit IRC13:46
*** Qiming has joined #openstack-ha13:50
*** rossella__ has quit IRC13:52
*** rossella__ has joined #openstack-ha13:54
*** radeks has quit IRC14:13
*** jmlowe has quit IRC14:15
*** kgaillot has joined #openstack-ha14:24
*** jmlowe has joined #openstack-ha14:28
*** zzhou_ has quit IRC14:33
*** rossella__ has quit IRC14:41
*** rossella__ has joined #openstack-ha14:43
*** rmart04 has quit IRC14:59
tbarroni'm looking for a pcs fencing agent for openstack/nova where the target of the15:02
tbarronstonith operation is not an OpenStack compute node but rather a guest VM15:02
tbarronso as I (mis?) understand the matter, not fence_compute15:02
tbarronAnyone know of such a thing?15:02
tbarronbasically, I want to interface with a fence_openstack_guest_vm device like15:03
*** zzhou has joined #openstack-ha15:03
tbarroninterfacing with a fencing agent for ilmi or idrac but have it issue openstack nova15:03
tbarroncommands to control the life-cycle of some "service" VMs for manila15:04
tbarronthese service VMs provide NFS service to backend storage and currently15:04
tbarronhave no HA and are therefore not suitable for enterprise production OpenStack15:05
tbarrondistributions15:05
*** hoonetorg has quit IRC15:05
tbarronthe idea is to run pairs of these SVMs active/hot-standby15:05
tbarronrather than just resurrecting a single SVM as boot up time will take significantly15:06
tbarronlonger than failover to a hot-standby15:06
*** MatthewLi has quit IRC15:06
aspierstbarron: it sounds like you are trying to reinvent part of masakari or senlin15:27
aspiersfencing is not required for managing individual VMs, because you can simply control them via nova15:29
aspierstbarron: I'd be more than happy to discuss this problem with you further. It's firmly in the compute HA space which I've been working on the last couple of years15:30
tbarronaspiers: I've recently watched you-tubes of your summit presos15:31
aspierstbarron: oh ok cool, I was about to send you links ;-)15:31
aspiersso one option is just to use masakari's vmmonitor15:31
tbarronaspiers: my thinking, correct or wrong, is that since these are "service" VMs, that is15:31
tbarronimages running known, specialized software, the problem space is simpler than15:32
tbarronwhat masakari solves15:32
aspiersI'm not sure but I *think* I persuaded your colleague Andrew Beekhof that masakari is worth pursuing15:32
tbarronthat is, i can run pcs/corosync in the service VMs themselves w/o any need of remote agents, etc.15:32
aspiersyes, masakari solves a lot more than this, but it's nicely modular so you don't have to bring in all the components if you don't want to15:32
tbarronaspiers: good tip on Beekhof, I will check with him for sure15:33
aspierswell you *could* place Pacemaker inside the VMs, but personally I'm not convinced that's the best approach15:33
tbarronb/c as you know we aren't using masakari currently15:33
aspiersright15:33
aspiersPacemaker has a mostly in-band approach to management, with the fencing devices being the out-of-band exception15:34
aspiersbut in this case you already have nova for out-of-band management15:34
tbarroni'm not sure it's the best approach either, but I want to understand how to do it15:34
aspierswell, you'd have to write your own fencing device15:34
tbarronwithout putting a nova client and keystone client inside the service VMs15:34
aspiershttps://github.com/ClusterLabs/fence-agents15:34
tbarronaspiers: yeah, I'll study that15:35
aspiersif you don't put those clients inside, then you'd need some service on the outside for them to talk to15:35
tbarronaspiers: personally I think the masakari stuff looks really cool and there is clearly a need15:35
aspierswhich sounds even uglier15:35
tbarronfor general purpose "pet" VM management15:35
aspiersright15:35
aspiersbut actually this particular use case (i.e. service VMs) is a very interesting one which I hadn't thought of before15:36
aspiersand it definitely ties into the architectural thoughts I have been having recently15:36
tbarronwell, the "ugly" thing I was thinking about was an external fencing agent15:36
aspiersah no, the fencing agent needs to live inside the Pacemaker cluster15:36
tbarronexternal virtual power cycler I should have said15:36
aspierslike I said, if you want the heavy lifting to be done outside, then the fencing agent would become a proxy for the outside mechanism15:37
aspiersbut when Pacemaker wants to fence something, initially it has to invoke something inside the cluster15:37
tbarronthat one could access via ssh key instead of keystone credentials, after somebody with the15:37
tbarronright keystone credentials configured it for *this* nova VM15:37
aspiersand to me introducing a proxy sounds like a fundamentally flawed architecture, because if the connection between the inside and outside is lost, you're totally hosed15:37
* tbarron will reflect on that point15:38
aspierstbarron: if it's easier, we could talk on Red Hat's fancy video conferencing thingy (I forget the name) or Google Hangouts or whatever15:39
tbarronaspiers: that would be great (bluejeans) or hangouts - I will email you and check availability15:39
aspierspresumably SUSE will have just as strong a need for HA service VMs as you guys, so it's not an entirely selfless offer ;-)15:40
aspiersyeah bluejeans, that's the one15:40
tbarronaspiers: yeah, say hi to toabctl for me :D15:40
aspiershaha OK :)15:40
aspiersof course ... the manila connection15:40
aspiersnot sure if you saw my most recent talk from Israel? this one is the most accurate in terms of architecture https://youtu.be/uMCMDF9VkYk15:41
aspiersin the previous ones I think I slightly messed up the diagrams15:41
aspiershttps://aspiers.github.io/openstack-day-israel-2017-compute-ha/#/nova-host-alerter15:42
aspierstbarron: also, I don't know too much about Senlin, but this use case does potentially sound like a good match for it https://wiki.openstack.org/wiki/Senlin15:44
aspierstbarron: Qiming could probably comment on whether I'm right15:44
aspiersin fact for this particular use case, Senlin might be a better choice than masakari's vmmonitor15:45
tbarronaspiers: I hadn't seen the Israel talk, will view it in a a little bit, thanks!15:49
aspiers:)15:49
tbarronQiming: aspiers I don't know much about Senlin, will do some homework15:50
tbarronaspiers: we had dinner together in Atlanta but this issue wasn't really on my radar at the time ...15:52
aspiersah ok15:53
aspierstbarron: I'm intending to propose a new Working Group for covering these kinds of architectural topics15:54
tbarronaspiers: makes sense15:57
aspiersactually we have a talk submitted for Sydney trying to tie all these projects together to some extent15:57
tbarroni'm on a manila topic proposed but don't know whether I'll be going to Sydney at this point.  Might rely on you tube again :D15:59
aspiersyeah I don't know whether I'll make it either15:59
*** egonzalez has quit IRC16:16
*** dougs1 has quit IRC16:49
-openstackstatus- NOTICE: Restarting Gerrit for our weekly memory leak cleanup.17:05
-openstackstatus- NOTICE: docs.o.o is currently broken, we're investigating18:38
*** dgurtner has quit IRC18:51
*** catinthe_ has quit IRC19:58
*** jmlowe has quit IRC20:32
*** v12aml has quit IRC21:30
*** markvoelker has quit IRC23:39
*** catintheroof has joined #openstack-ha23:58

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