From nobody Thu Feb 29 18:29:44 2024 X-Original-To: freebsd-enterprisewg@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 4Tm0BZ5Sf4z5CgT9 for ; Thu, 29 Feb 2024 18:29:58 +0000 (UTC) (envelope-from greg@freebsdfoundation.org) Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Tm0BZ41stz4NGg for ; Thu, 29 Feb 2024 18:29:58 +0000 (UTC) (envelope-from greg@freebsdfoundation.org) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x532.google.com with SMTP id 41be03b00d2f7-5d8b70b39efso1167000a12.0 for ; Thu, 29 Feb 2024 10:29:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsdfoundation.org; s=gfnp-20170908; t=1709231396; x=1709836196; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=TgbegsvzLL8qdWqscs5qMfJh7owMMxNcWubM4lMdb8U=; b=UCUmsDhc06h7w4U3XPN68hZ0KIUHj5twopOoKtaXo8yDxAM7slszz+yOBgKCCSJP0D +F2JlYIounUogcDJ4LyazhTrDKkQqcT5QM8pj7MhvkqPX5z0bhLBU9OcHnllnGTm0M4o KwJ4tXJ46lCpzLw+ju2dqizRSxNt7s4PiaY9CcK7Z92TLheJXebE1+37YR2NrQR2F+mD sQ/q24ut+gnRZE8dHV/CiYzp5A1JhPyK9L3LJ7VkYdJkNfSMrPpzJDH9cW01lllvfRjs LN0MiPuJ0suqpn6cG00Ra37mOJ/GvpUN5O0VZmQDi9PNFMclVTK75n3nSd6p+xsqLFCq 8Tdg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709231396; x=1709836196; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=TgbegsvzLL8qdWqscs5qMfJh7owMMxNcWubM4lMdb8U=; b=eDv3drte0P6WecnzclN+ex5dht+k7S/ZCw4R51wpFLSspjLvSRhElFQ3dP/fTc3AL9 qqXOc6MIVM0qh7CcxSRlHy0k/VNgNc3m7R4tgM4icUGwFnmb5UVWCk4j8nNb/b3j/mRw jEbNt6K4WeLT7qAPMe2mUgqaYz0nPoV193pnV2re1FL4ivfPbvMJnSIGe9ZcOkkjyXeN E+toMO8C1xonjTzXo5ubwnNhOxJ1tAlXWuCttkNfOcz2hLImFPjFeT887+8db62oytCQ /+5WwOknNbK5A8ZWHfQRppSf8mhqRPtdpTmVRHUHuyxpMWgtVOGyfaWnhRe7Cjwgy6GG Oyog== X-Gm-Message-State: AOJu0Yz0cQUUGrwGFHXOb90ITNVDsNbQlpc/MnjCRLvcolz2VCRgHu75 OkkJFaVTlQRbTFwALkHiORFqbFYNZvpalxJwg/SOb6hTm3T34KN3n7GkAZ5pFjAMQl9BT8nrHa3 OdBekedanFfeClpoqv/C0czSaURMT+PYU6Q6v88yayV0RxDgTJO8= X-Google-Smtp-Source: AGHT+IEaJ7MmNBjw3lYwQB0V7l8+oWtkhIf9/rI7f1WLtc1aVyApGJ4LF9BjR185OsF8jD52aS/kA1G5S0pT0dkQ0b8= X-Received: by 2002:a17:90a:a893:b0:29a:f991:dcc1 with SMTP id h19-20020a17090aa89300b0029af991dcc1mr2942716pjq.1.1709231395711; Thu, 29 Feb 2024 10:29:55 -0800 (PST) List-Id: FreeBSD as a general-purpose enterprise server List-Archive: https://lists.freebsd.org/archives/freebsd-enterprisewg List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-enterprisewg@freebsd.org X-BeenThere: freebsd-enterprisewg@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Greg Wallace Date: Thu, 29 Feb 2024 13:29:44 -0500 Message-ID: Subject: Re: Quick update To: Christian Moerz Cc: "freebsd-enterprisewg@FreeBSD.org" Content-Type: multipart/alternative; boundary="0000000000002e53d406128972e4" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4Tm0BZ41stz4NGg --0000000000002e53d406128972e4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thank you for forwarding this, Chris. Sorry everyone for the misfire! On Thu, Feb 29, 2024, 12:58 PM Christian Moerz wrote: > For anyone who has not gotten this because this went to the @ > freebsdfoundation.org mailing list domain=E2=80=A6 > > Below is an update from Greg and me. > > > > Chris > > > > *From: *Greg Wallace > *Date: *Wednesday, 28. February 2024 at 19:09 > *To: *Enterprise WG > *Subject: *Quick update > > Hi Everyone, > > > > I know it's been a couple months since my last update. > > > > The year has started off with a bang and I have also been waiting to have > some more concrete updates to share. > > > > February update > > > > Here's where a few of the major efforts stand: > > - OCI runtime extension > > > - The Working Group has been approved and Doug has been making > progress. He added use cases to the Requirements page > . > He has also been joining the weekly Jails calls and you can find mo= re > detailed updates there. > - I am presently trying to find a good day and time for the WG to > hold bi-weekly meetings and once set, I will be updating this page = with > meeting links and note: > https://github.com/opencontainers/wg-freebsd-runtime > > > - bhyve manageability (thanks to Chris M. for providing these bullets) > > > - We have identified some core elements that we are missing around > bhyve manageability - generally speaking, it would be nice to have = tooling > and configurability for bhyve like for jails (i.e jls, jexec, =E2= =80=A6) > - we are looking at new developments (sysutils/vmstated) as well as > existing ones (sysutils/bmd) to contrast available options on how t= o > develop and work towards this. Both address =E2=80=9Cstate manageme= nt=E2=80=9D for bhyve > virtual machines. > - for now, the consensus on network management is to not combine it > with the management tooling for bhyve and leave that as separate = =E2=80=9Cwork > bench=E2=80=9D with rc scripting and existing utilities. > - We plan to further improve the base utility vmrun.sh to also > address setting up Windows guests. > - We updated the FreeBSD handbook=E2=80=99s virtualization chapter = with a > first improvement iteration A second iteration and expansion is alr= eady > under review with > > > - setting up Windows guests > - snapshot and restore experimental feature > - jailing bhyve with vnet > > > - We also updated the bhyve man page with a first improvement > iteration, which is actively under review. > > > - .NET support > > > - You may recall that this primarily came to light in the Enterprise > WG because the lack of .NET support for FreeBSD prevents projects h= osted on > GitHub and using GitHub Actions from accepting patches from FreeBSD > developers (Samba came up initially, and there are many others). > - Thanks to some heroic work from the FreeBSD community, FreeBSD is > now a Community Supported Platform in .NET (at least for version 8) > > > - see: https://github.com/dotnet/runtime/issues/14537 > - you can now run run $ pkg install dotnet and it will work > - This means your .NET apps will run on FreeBSD and with a few > tweaks you can also use Azure Pipelines (see: > https://github.com/dotnet/runtime/issues/14537#issuecomment-1958= 830867 > ) > > > - Still to do are getting full support in GHA, and what I am trying to > make happen is to get FreeBSD added as an officially supported plat= form by > the .NET team. There are also a few other smaller things related to > powershell and finishing up Azure Pipelines > > This table summarizes the .NET bring up situation: > > Component > > Link > > Description > > Status > > Work to date by > > dotnet > > Issue 1139 > > Building the .NET Core SDK on FreeBSD > > Closed > > FreeBSD Community > > dotnet > > Issue 14537 > > Support for FreeBSD > > Open > > FreeBSD Community > > libunwind > > PR276346 > > devel/libunwind: Update to 1.8.0 > > Closed > > FreeBSD Community > > installer > > Issue 248 > > Re-enable FreeBSD builds once core-setup is building for FreeBSD again > > Closed > > FreeBSD Community > > dotnet > > Issue 71338 > > Support for FreeBSD-arm64 - Ampere partnership opportunity? > > FreeBSD Community > > PowerShell > > Pull 20041 > > WIP: Add platform support for FreeBSD > > FreeBSD Community > > > > PowerShell/PowerShell-Native > > Pull 92 > > Fix FreeBSD build failures. Update tests for FreeBSD > > Waiting on repo owner MS > > FreeBSD Community > > .NET Virtual Monolithic Repository (VMR) > > https://github.com/dotnet/dotnet > > Need scoping in FreeBSD community > > FreeBSD Community > > > > actions/runner > > Issue 385 > > FreeBSD support > > Need feedback from MS > > > > microsoft/azure-pipelines-agent > > Pull 3266 > > Adjustments for FreeBSD Beckhoff needs > > Waiting on repo owner MS > > Azure Pipelines Task SDK > > Pull 799 > > Add FreeBSD support for Azure Pipelines Task SDK > > Waiting on repo owner MS > > - Kerberos > > > - Decision to switch to MIT from Heimdal. This will help out a lot in > the long term. In the short term, lots of work has gone into patchi= ng > Heimdal. > > > - AD / DNS integration > > > - I don't have an update here. If others on list do, please chime in > > > - smbfs driver update in kernel > > > - no update from previous > > > - OpenJDK > > > - Foundation is still looking for a contractor > > > - Better support for FreeBSD in AI, in particular CUDA > > > - No update > > > - OTHER > > > - The engineer working on the FreeBSD CIS Benchmark is making > excellent progress. On track to have all section complete and out f= or > review in Q2 > > > > Look forward to hearing from others on things you have in motion and any > ideas on how to make progress in areas like AI. > > > > Thanks! > > > > -- > > Greg Wallace > > Director of Partnerships & Research > > [image: Image removed by sender.] > > M +1 919-247-3165 > > Schedule a meeting > > Get your FreeBSD Gear > > -- > Discussion on this list is governed by the FreeBSD Code of Conduct. Pleas= e > familiarize yourself with it here: > https://www.freebsd.org/internal/code-of-conduct/ > --- > You received this message because you are subscribed to the Google Groups > "Enterprise WG" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to enterprise-wg+unsubscribe@freebsdfoundation.org. > To view this discussion on the web visit > https://groups.google.com/a/freebsdfoundation.org/d/msgid/enterprise-wg/C= AP%3Ds-_g7g_SWshi_h9ZDxbjrym4TugSKbsYi%3DUQCn2g6Pc%3DqsQ%40mail.gmail.com > > --0000000000002e53d406128972e4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thank you for forwarding this, Chris. Sorry everyone for = the misfire!

On Thu, Feb 29, 2024, 12:58 PM Christian Moerz <freebsd@ny-central.org> wrote:

For anyone who has = not gotten this because this went to the @freebsdfoundation.org mail= ing list domain=E2=80=A6

Below is an update = from Greg and me.

=C2=A0

Chris=

=C2=A0

From: Greg Wallace <greg@freebs= dfoundation.org>
Date: Wednesday, 28. February 2024 at 19:09
To: Enterprise WG <enterprise-wg@freebsdfoundati= on.org>
Subject: Quick update

Hi Everyone,

=C2=A0

I know it's been a couple months since my last update.=C2=A0

=C2=A0

The year=C2=A0has started off with a bang and I have also been waiting= to have some more concrete updates to share.

=C2=A0

February update

=C2=A0

Here's where a few of the major efforts stand:=

  • OCI runtime extens= ion
    • The Working Group = has been approved and Doug has been making progress. He added use cases to = the Requirements page. He has also been joining the weekly Jails cal= ls and you can find more detailed updates there.
      • <= li style=3D"color:black;margin-top:0cm;margin-bottom:0cm;vertical-align:bas= eline;font-variant-numeric:normal;font-variant-east-asian:normal;font-varia= nt-alternates:normal"> I am presently try= ing to find a good day and time for the WG to hold bi-weekly meetings and o= nce set, I will be updating this page with meeting links and note: https://github.com/opencontainers/wg-freebsd-run= time
  • bhyve manageabilit= y (thanks to Chris M. for providing these bullets)
    • We have identified= some core elements that we are missing around bhyve manageability - genera= lly speaking, it would be nice to have tooling and configurability for bhyv= e like for jails (i.e jls, jexec, =E2=80=A6)
    • we are looking at = new developments (sysutils/vmstated) as well as existing ones (sysutils/bmd= ) to contrast available options on how to develop and work towards this. Bo= th address =E2=80=9Cstate management=E2=80=9D for bhyve virtual machines.
    • for now, the conse= nsus on network management is to not combine it with the management tooling= for bhyve and leave that as separate =E2=80=9Cwork bench=E2=80=9D with rc = scripting and existing utilities.
    • We plan to further= improve the base utility vmrun.sh to also address setting up Windows guest= s.
    • We updated the Fre= eBSD handbook=E2=80=99s virtualization chapter with a first improvement ite= ration A second iteration and expansion is already under review with=
      • setting up Windows= guests
      • snapshot and resto= re experimental feature
      • jailing bhyve with= vnet
    • We also updated th= e bhyve man page with a first improvement iteration, which is actively unde= r review.
  • .NET support
    • You may recall tha= t this primarily came to light in the Enterprise WG because the lack of .NE= T support for FreeBSD prevents projects hosted on GitHub and using GitHub A= ctions from accepting patches from FreeBSD developers (Samba came up initially, and there are many others).=
    • Thanks to some her= oic work from the FreeBSD community, FreeBSD is now a Community Supported P= latform in .NET (at least for version 8)
    • Still to do are ge= tting full support in GHA, and what I am trying to make happen is to get Fr= eeBSD added as an officially supported platform by the .NET team. There are= also a few other smaller things related to powershell and finishing up Azure Pipelines

This t= able summarizes the .NET bring up situation:

Component=C2=A0

Link

Description

Status

Work to date by

dotnet=

Issue 1139

Building the .NET Core = SDK on FreeBSD

Closed=

FreeBSD Community

dotnet=

Issue 14537<= /p>

Support for FreeBSD

Open=

FreeBSD Community

libunwind=

PR276346

devel/libunwind: Update= to 1.8.0

Closed=

FreeBSD Community

installer=

Issue 248

Re-enable FreeBSD build= s once core-setup is building for FreeBSD again

Closed=

FreeBSD Community

dotnet=

Issue 71338<= /p>

Support for FreeBSD-arm= 64 - Ampere partnership opportunity?

FreeBSD Community

PowerShell

Pull 20041<= /u>

WIP: Add platform suppo= rt for FreeBSD

FreeBSD Community

=C2=A0

PowerShell/PowerShell-N= ative

Pull 92=

Fix FreeBSD build failu= res. Update tests for FreeBSD

Waiting on repo owner M= S

FreeBSD Community

.NET Virtual Monolithic= Repository (VMR)

https://github.com/dotnet/dotnet<= u>

Need scoping in FreeBSD= community

FreeBSD Community

=C2=A0

actions/runner

Issue 385

FreeBSD support<= u>

Need feedback from MS

=C2=A0

microsoft/azure-pipelin= es-agent

Pull 3266=

Adjustments for FreeBSD= Beckhoff needs

Waiting on repo owner M= S

Azure Pipelines Task SD= K

Pull 799

Add FreeBSD support for= Azure Pipelines Task SDK=C2=A0

Waiting on repo owner M= S
  • Kerberos=
    • Decision to switch= to MIT from Heimdal. This will help out a lot in the long term. In the sho= rt term, lots of work has gone into patching Heimdal.<= /li>
  • AD / DNS integrati= on
    • I don't have a= n update here. If others on list do, please chime in
  • smbfs driver updat= e in kernel
    • no update from pre= vious
  • OpenJDK<= /u>
    • Foundation is stil= l looking for a contractor
  • Better support for= FreeBSD in AI, in particular CUDA
    • No update
  • OTHER<= /span>
    • The en= gineer working on the FreeBSD CIS Benchmark is making excellent progress. O= n track to have all section complete and out for review in Q2

=C2=A0

Look forward to hearing from others on things you ha= ve in motion and any ideas on how to make progress in areas like AI.=

=C2=A0

Thanks!

=C2=A0

--

Greg Wallace

Director of Partnerships & Research

3D"Image

M +1 919-247-3165

--
Discussion on this list is governed by the FreeBSD Code of Conduct. Please = familiarize yourself with it here: https://www.freebsd.org/internal/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups &= quot;Enterprise WG" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to enterprise-wg+unsubscribe@freebsdfoundation.= org.
To view this discussion on the web visit https://groups.google.com/a/freebsdfoundation.org/d/msgid/enterprise-wg/CAP= %3Ds-_g7g_SWshi_h9ZDxbjrym4TugSKbsYi%3DUQCn2g6Pc%3DqsQ%40mail.gmail.com=

--0000000000002e53d406128972e4--