Date: Tue, 05 Dec 2017 15:40:44 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 224100] net-mgmt/crmsh: This package was not properly ported for FreeBSD Message-ID: <bug-224100-13-gdiuHBZbZ2@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224100-13@https.bugs.freebsd.org/bugzilla/> References: <bug-224100-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224100 --- Comment #1 from David Shane Holden <dpejesh@yahoo.com> --- I think the problem you're having is not with crmsh but with the resource agents which you're trying to use. That's where the Linuxisms are located since they're glorified rc scripts. When I created the net-mgmt/resource-agents port it was because I wanted the zabbixserver RA w= hich I've been using successfully for a couple of years now. As far as the other 100 or so RAs are concerned nearly all of them will need testing, patching,= or alternates created specifically for FreeBSD. Depending on which ones you're trying to use the changes to support FreeBSD might be trivial. The reason they're all installed and not just the ones I know to work on FreeBSD is because there's ~100 of them (of which I only use a couple) and some are ve= ry specific to software I've never used, so for all I know they could work just fine. I agree that the cluster suite could use more testing, but the sad t= ruth is there's not many people who venture into using corosync/pacemaker and far fewer who try to do it on FreeBSD. You're quite possibly only the second person to actually try to use these ports besides me in the 1.5+ years sinc= e I submitted the patches to get them added to the ports tree. If you decide to delve further into tracking down bugs and submitting patches I'd be more th= an willing to assist and I've had good experiences upstreaming patches for Fre= eBSD support to the libqb/corosync/pacemaker repositories. The claim that crmsh is completely broken isn't true though. Some of the subcommands might not work for one reason or another and those should definitely be reported as bugs but the tool itself is in a working state. Here's an example of my 2-node zabbix server cluster. # crm status Stack: corosync Current DC: col1002.mon.corp.fl1 (version 1.1.18-2b07d5c5a9) - partition wi= th quorum Last updated: Tue Dec 5 14:17:05 2017 Last change: Tue Dec 5 14:16:01 2017 by hacluster via crmd on col1002.mon.corp.fl1 2 nodes configured 3 resources configured Online: [ col1001.mon.corp.fl1 col1002.mon.corp.fl1 ] Full list of resources: zabbixserver (ocf::heartbeat:zabbixserver): Started col1001.mon.corp.fl1 Clone Set: cloneSysinfo [sysinfo] Started: [ col1001.mon.corp.fl1 col1002.mon.corp.fl1 ] # crm configure show node 1: col1001.mon.corp.fl1 node 2: col1002.mon.corp.fl1 primitive sysinfo ocf:pacemaker:SysInfo \ op monitor interval=3D20s primitive zabbixserver zabbixserver \ params binary=3D"/usr/local/sbin/zabbix_server" pid=3D"/var/run/zabbix/zabbix_server.pid" config=3D"/usr/local/etc/zabbix32/zabbix_server.conf" \ op monitor interval=3D60s timeout=3D45s \ op start interval=3D0 timeout=3D60s \ op stop interval=3D0 timeout=3D300s \ meta target-role=3DStarted clone cloneSysinfo sysinfo \ meta target-role=3DStarted location cli-prefer-zabbixserver zabbixserver role=3DStarted inf: col1001.mon.corp.fl1 property cib-bootstrap-options: \ have-watchdog=3Dfalse \ dc-version=3D1.1.18-2b07d5c5a9 \ cluster-infrastructure=3Dcorosync \ stonith-enabled=3Dfalse \ last-lrm-refresh=3D1512483361 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224100-13-gdiuHBZbZ2>