On Wed, Jul 19, 2017 at 06:53:44PM +0200, Jan Pokorný wrote:
> I don't think that alone would suffice, I'd expect at least (port,transport)
> pair to be reasonably unique as long as you can remap TCP/UDP independently
> (I am not sure, but would be no surprise) -- but hey, we have just hit
>
On Tue, Aug 01, 2017 at 11:07:24PM +0200, Jan Pokorný wrote:
> https://bugzilla.redhat.com/1477354
Thanks for the info. We are seeing similar problems with the
pacemaker build on Debian now:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869986
Guess we'll need to fix pacemaker libs to
Hello devs,
Following the bundle release in 1.1.17, I've been working on a
similar implementation for rkt. Resource agent based on docker
is here:
https://github.com/vvidic/resource-agents/blob/rkt/heartbeat/rkt
That part should be fairly functional, but I'm having a bit more
problems with
On Tue, Jul 18, 2017 at 09:02:34AM +0200, Oyvind Albrigtsen wrote:
> mount_points might be good to have for rkt as well, as it creates
> directories on the host server that the container will mount:
> https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/docker#L109
Right, I was
On Mon, Jul 17, 2017 at 03:43:22PM -0500, Ken Gaillot wrote:
> See the xml/Readme.md file -- I won't say all our documentation is
> helpful, but that one is pretty good. ;-) Basically, you create a
> resources-2.10.rng and leave everything else alone, and the makefile
> will take it from there.
>
On Mon, Jul 17, 2017 at 09:44:13PM +0200, Valentin Vidic wrote:
> The first question I have is if the xml changes are ok for the
> new container type? Do I need to modify both resources-2.8.rng
> and resources-2.9.rng or perhaps create a new version?
Seems there is a problem with the
Trying out the cluster init functionality I can't get SBD to work:
1. The config file is updated with SBD_DEVICE and SBD_WATCHDOG,
but the systemd service only takes $SBD_OPTS:
ExecStart=/usr/sbin/sbd $SBD_OPTS -p /var/run/sbd.pid watch
Maybe a different service file is expected or this only
On Fri, Jul 21, 2017 at 11:20:46AM +0200, Kristoffer Grönlund wrote:
> I would also like to take the opportinity to introduce a new core
> developer for crmsh, Xin Liang! For this release he has contributed
> some of the bug fixes discovered, but he has also contributed a
> rewrite of hb_report
I'm seeing this state when trying to stop the docker bundle
with pacemaker 1.1.17:
15738 ?Ssl7:23 /usr/sbin/dockerd -H fd://
15742 ?Ssl5:31 \_ containerd -l
unix:///var/run/docker/libcontainerd/containerd.sock --metrics-interval=0
--start-timeout 2m --state-dir
On Mon, Jul 24, 2017 at 09:57:01AM -0500, Ken Gaillot wrote:
> Are you sure you have pacemaker 1.1.17 inside the container as well? The
> pid-1 reaping stuff was added then.
Yep, the docker container from the bundle example got an older
version installed, so mystery solved :)
Another issue with the rkt containers is the port-mapping. Each container
defines exposed ports:
"ports": [
{
"name": "http",
"protocol": "tcp",
"port": 80,
"count": 1,
On Mon, Jul 24, 2017 at 10:26:52AM +0200, Kristoffer Grönlund wrote:
> Apologies for being unclear in the announcement: No, the hb_report
> rewrite is not included in 3.0.1, but will be ready soon I hope.
No problem, just wanted to check if I missed something on the Debian side.
--
Valentin
On Mon, Jul 24, 2017 at 12:19:20PM +0200, Klaus Wenninger wrote:
> Wasn't aware of the different behavior of pacemaker_remoted as pidone.
> If it is really spawned as pidone - which might be worth verifying -
> it should indeed create a zombie catcher pid1.
You are right about PID 1, it looks
On Mon, Jul 24, 2017 at 10:30:08AM +0200, Kristoffer Grönlund wrote:
> This may be an unintentional SUSE-ism that has snuck in... please create
> an issue on github and attach your service file for sbd, and I'll take a
> look!
Thanks, will open both issues so you can verify on your side.
--
On Mon, Jul 24, 2017 at 01:04:06PM +0200, Klaus Wenninger wrote:
> Interesting... Looking at the code I would expect 2 processes. Some
> 'pcmk-init' with pidone and
> 'pacemaker_remoted' that is spawned out as child.
> So looks as if the spawning thing isn't working. Strange thing is that
> the
On Sat, Jun 16, 2018 at 09:50:54AM +0300, pierre-philipp braun wrote:
> Should I report a bug or can you help me right now? Should I provide
> some additional information?
I think this was fixed in git but not yet released as 1.0.13.
--
Valentin
___
On Wed, Oct 24, 2018 at 01:25:54PM +0100, Adam Spiers wrote:
> No doubt I've missed some pros and cons here. At this point
> personally I'm slightly leaning towards keeping them in the
> openstack-resource-agents - but that's assuming I can either hand off
> maintainership to someone with more
On Wed, Oct 24, 2018 at 04:22:52PM +0200, Kristoffer Grönlund wrote:
> Do you mean additional python module dependencies, or that the
> dependency on python itself seems like added weight? Because since
> python is a dependency of pacemaker as well as both crmsh, pcs and
> fence-agents already, it
On Wed, Oct 17, 2018 at 12:03:18PM +0200, Oyvind Albrigtsen wrote:
> - apache: retry PID check.
I noticed that the ocft test started failing for apache in this
version. Not sure if the test is broken or the agent. Can you
check if the test still works for you? Restoring the previous
version of
On Fri, Oct 19, 2018 at 11:09:34AM +0200, Kristoffer Grönlund wrote:
> I wonder if perhaps there was a configuration change as well, since the
> return code seems to be configuration related. Maybe something changed
> in the build scripts that moved something around? Wild guess, but...
Seems to
On Thu, Nov 29, 2018 at 07:46:12AM +0100, Ivan Devát wrote:
> unfortunately, pcs web UI does not work with jquery 3.2.1 and it seems that
> it is not easy to fix it now.
No problem, thanks for checking. If you can say what are the main
problems, so we can give it a try at some later point?
--
On Wed, Apr 10, 2019 at 05:44:45PM -0500, Ken Gaillot wrote:
> Florian Haas and Kristoffer Grönlund noticed that the ClusterLabs
> organization on github currently carries over any app access that
> members have given to their own accounts.
Related to github setup, I just noticed that some
On Mon, Apr 29, 2019 at 04:31:16PM +0200, Kristoffer Grönlund wrote:
> Yes, this would be OK to me at least (as the creator of the logo)!
I've also used it for the Debian HA packaging repo:
https://salsa.debian.org/ha-team
--
Valentin
___
Manage
23 matches
Mail list logo
