From nobody Fri Aug 12 16:21:36 2022 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4M487y6GrYz4Yvrf for ; Fri, 12 Aug 2022 16:21:50 +0000 (UTC) (envelope-from freebsd@gushi.org) Received: from prime.gushi.org (prime.gushi.org [IPv6:2620:137:6000:10::142]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "prime.gushi.org", Issuer "RapidSSL TLS DV RSA Mixed SHA256 2020 CA-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4M487x6mhvz45GL; Fri, 12 Aug 2022 16:21:49 +0000 (UTC) (envelope-from freebsd@gushi.org) Received: from smtpclient.apple (ool-18bb68ab.dyn.optonline.net [24.187.104.171]) (authenticated bits=0) by prime.gushi.org (8.16.1/8.16.1) with ESMTPSA id 27CGLfZ8008367 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 12 Aug 2022 09:21:42 -0700 (PDT) (envelope-from freebsd@gushi.org) DKIM-Filter: OpenDKIM Filter v2.10.3 prime.gushi.org 27CGLfZ8008367 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gushi.org; s=prime2014; t=1660321304; bh=Ua5n801EJYOVlzIUnPQ4WEoKIdajRovohGIZTaETGDo=; h=Subject:From:In-Reply-To:Date:Cc:References:To; z=Subject:=20Re:=20MegaCLI=20port=20is=20ports-only=20--=20how=20wo uld=20you=20deploy=20it?|From:=20Dan=20Mahoney=20|In-Reply-To:=20|Date:=20Fri,=201 2=20Aug=202022=2012:21:36=20-0400|Cc:=20Ruslan=20Makhmatkhanov=20< rm@freebsd.org>,=0D=0A=20"ports@freebsd.org"=20 ,=0D=0A=20"samflanker@gmail.com"=20|Referenc es:=20<1615CF76-EE45-4D11-8102-EA441E845E65@gushi.org>=0D=0A=20<63 5211659622624@mail.yandex.ru>=20=0D =0A=20<493ED6A6-A38F-47B1-B534-9F5CB14DB087@gushi.org>=0D=0A=20|To:=20Doug=20Ambrisko=20; b=rwF/hVRy2+lRhWrs2W/P43tlSVumsbha43z7yw43uAIQGAWdXN/fqS4LLOcwbW953 FCwGBNDAuUreWlmg5+RTRbl08V4seGYtJGkM0fXZtFVylIaPOE62GjMqDgKjyF3Qf5 kNjkB5Xso4kKjLBQpzJjLU+wR5sGHHJKy0qQCok29SOuHCTgdV8X28J/g1U1FXFkm2 KdKHsxjqRPi9Sp1NHcdCUDz4r0sFlq45zfzZ1cxWqVk+QNjtBqYpGxaCN9zqUKvTVL jBwBHvDFTMpy8WOXcT5S7O4u8OLYpBYKjedjoAmrpdduj4weBaQXf8MMhPDSgMD92J UbzwCe5yzQ0fw== X-Authentication-Warning: prime.gushi.org: Host ool-18bb68ab.dyn.optonline.net [24.187.104.171] claimed to be smtpclient.apple Content-Type: text/plain; charset=us-ascii List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\)) Subject: Re: MegaCLI port is ports-only -- how would you deploy it? From: Dan Mahoney In-Reply-To: Date: Fri, 12 Aug 2022 12:21:36 -0400 Cc: Ruslan Makhmatkhanov , "ports@freebsd.org" , "samflanker@gmail.com" Content-Transfer-Encoding: quoted-printable Message-Id: <1578B277-8FB1-4EAB-ACDB-8ACE6E999857@gushi.org> References: <1615CF76-EE45-4D11-8102-EA441E845E65@gushi.org> <635211659622624@mail.yandex.ru> <493ED6A6-A38F-47B1-B534-9F5CB14DB087@gushi.org> To: Doug Ambrisko X-Mailer: Apple Mail (2.3696.120.41.1.1) X-Rspamd-Queue-Id: 4M487x6mhvz45GL X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gushi.org header.s=prime2014 header.b="rwF/hVRy"; dmarc=pass (policy=none) header.from=gushi.org; spf=pass (mx1.freebsd.org: domain of freebsd@gushi.org designates 2620:137:6000:10::142 as permitted sender) smtp.mailfrom=freebsd@gushi.org X-Spamd-Result: default: False [-5.20 / 15.00]; DWL_DNSWL_MED(-2.00)[gushi.org:dkim]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MV_CASE(0.50)[]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; DMARC_POLICY_ALLOW(-0.50)[gushi.org,none]; R_DKIM_ALLOW(-0.20)[gushi.org:s=prime2014]; RCVD_IN_DNSWL_MED(-0.20)[2620:137:6000:10::142:from]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[ports@freebsd.org]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; RCVD_COUNT_TWO(0.00)[2]; TO_DN_EQ_ADDR_SOME(0.00)[]; ASN(0.00)[asn:393507, ipnet:2620:137:6000::/44, country:US]; MID_RHS_MATCH_FROM(0.00)[]; HAS_XAW(0.00)[]; TO_DN_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[gushi.org:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; FREEMAIL_CC(0.00)[freebsd.org,gmail.com] X-ThisMailContainsUnwantedMimeParts: N > On Aug 8, 2022, at 16:45, Doug Ambrisko wrote: >=20 > On Mon, Aug 08, 2022 at 04:10:10PM -0400, Dan Mahoney wrote: > |=20 > |=20 > | > On Aug 8, 2022, at 15:57, Doug Ambrisko = wrote: > | >=20 > | > On Thu, Aug 04, 2022 at 05:22:29PM +0300, Ruslan Makhmatkhanov = wrote: > | > | 03.08.2022, 02:07, "Dan Mahoney" : > | > | Hey there all, > | > | At the dayjob we have a fleet of Dell Poweredge servers = that can use > | > | either mptsas or mrsas -- if you use mptsas, you use = mptutil (in > | > | base) to check the state of the card. > | > | If you use mrsas, you need megacli, which is only in ports, = and the > | > | port hasn't translated to pkg probably because of license > | > | restrictions. ( _LICENSE_RESTRICTED =3D delete-package > | > | delete-distfiles), but the license listed is just = "megacli". > | > | * We want to deploy a cron job to periodically check the = raid status > | > | (we're writing a wrapper, also having it check mfiutil, = zpool, etc). > | > | * We do not want to install and manage a whole ports tree = on every > | > | machine in our fleet, just to install a raid utlity. > | > | Option A: > | > | Make a local package somehow. > | > | The port just downloads a static binary, there's nothing to = build > | > | here, but we want to do this the "right" way. Is there some = way to > | > | have pkg deploy a single local package for this that will, = for > | > | example, report the right package ownership, without moving = every > | > | other package to our poudriere install (we're just using = base > | > | packages, we keep poudriere around for testing in case we = need to > | > | hot-patch something). > | > | For what it's worth, we use puppet for config management, = so pushing > | > | out the static binary is not the worst answer, but it also = feels > | > | "dirty". > | > | Option B: > | > | Figure out how to fix the license. I have no idea what this = would > | > | involve. > | > | Option C: > | > | Also, apparently MegaCLI is no longer maintained (replaced = by > | > | StorCLI), but there's no port for StorCLI, and...there are = multiple > | > | raid-card specific versions? Jeez. > | > | Feels even more dirty. > | > | = [1]https://support.siliconmechanics.com/portal/en/kb/articles/storcl > | > | i-for-freebsd-and-other-operating-systems > | > | Ideas welcome? > | > | -Dan Mahoney > | >=20 > | > Although the path to get to StorCli goes through various cards the > | > latest greatest seem to work on all earlier cards. It works on > | > HBAs and not just RAID cards. At work I did a Linux/FreeBSD > | > POC for FW management and found the FreeBSD version could flash = the HBA > | > and drive FW. I've moved to StorCli from MegaCli. I would = suggest > | > we drop the MegaCli port and move to StorCli. > | >=20 > | > I have code to make mfiutil into mrsasutil and added the MFI ioctl > | > handler to mrsas. I'm not sure how much value that has. I don't > | > deal with supporting FreeBSD and RAID much anymore. If interested > | > I could send patches. > |=20 > | This feels like it should be in base, regardless. Just *something* = to=20 > | query the raid status and health, even if it doesn't ring all the = bells=20 > | of StorCLI. > |=20 > | Right now, you can do this with the older mfi, but not the newer = mrsas,=20 > | which performs better in some cases, which leaves an admin with a=20 > | dilemma: better reliability, or better manageability. > |=20 > | I also feel like this could be added to a minor release (i.e. a=20 > | 12.3 --> 12.4 or a 13.0 --> 13.1), but obviously that decision is = above me. >=20 > This is based of -current. I haven't tested it recently: > = https://people.freebsd.org/~ambrisko/git.mrsas_support_in_mfiutil.patch >=20 > Please give it a try. You will need a new kernel built and booted to > provide the needed ioctl support. It should be close to committable. Doug, I'm trying this out on 12.x and 13.x just for funsies, but given the = release schedule, it's unlikely that there'll be a 12.4 or a 13.2 that = this would make it into. Regardless, I've opened a bug report to get = this added *somewhere* which may cause other people to try it out and = test. -Dan