Quick update

Reply: Greg Wallace : "Re: Quick update"
Go to: [ bottom of page ] [ top of archives ] [ this month ]
From: Christian Moerz <freebsd_at_ny-central.org>
Date: Thu, 29 Feb 2024 17:58:16 UTC
For anyone who has not gotten this because this went to the @freebsdfoundation.org mailing list domain…
Below is an update from Greg and me.

Chris

From: Greg Wallace <greg@freebsdfoundation.org>
Date: Wednesday, 28. February 2024 at 19:09
To: Enterprise WG <enterprise-wg@freebsdfoundation.org>
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<https://github.com/opencontainers/wg-freebsd-runtime/blob/main/docs/REQUIREMENTS.md>. He has also been joining the weekly Jails calls and you can find more 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, …)
     *   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. Both address “state management” 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 “work bench” 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’s virtualization chapter with a first improvement iteration. A second iteration and expansion is already 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 hosted 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-1958830867)

     *   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 platform 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<https://github.com/dotnet/source-build/issues/1139>

Building the .NET Core SDK on FreeBSD

Closed

FreeBSD Community

dotnet

Issue 14537<https://github.com/dotnet/runtime/issues/14537>

Support for FreeBSD

Open

FreeBSD Community

libunwind

PR276346<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276346>

devel/libunwind: Update to 1.8.0

Closed

FreeBSD Community

installer

Issue 248<https://github.com/dotnet/installer/issues/248>

Re-enable FreeBSD builds once core-setup is building for FreeBSD again

Closed

FreeBSD Community

dotnet

Issue 71338<https://github.com/dotnet/runtime/issues/71338>

Support for FreeBSD-arm64 - Ampere partnership opportunity?

FreeBSD Community

PowerShell

Pull 20041<https://github.com/PowerShell/PowerShell/pull/20041>

WIP: Add platform support for FreeBSD

FreeBSD Community


PowerShell/PowerShell-Native

Pull 92<https://github.com/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<https://github.com/actions/runner/issues/385>

FreeBSD support

Need feedback from MS


microsoft/azure-pipelines-agent

Pull 3266<https://github.com/microsoft/azure-pipelines-agent/pull/3266>

Adjustments for FreeBSD. Beckhoff needs

Waiting on repo owner MS

Azure Pipelines Task SDK

Pull 799<https://github.com/microsoft/azure-pipelines-task-lib/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 patching 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 for 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 removed by sender.]
M +1 919-247-3165
Schedule a meeting<https://calendly.com/greg-freebsdfound/30min>
Get your FreeBSD Gear<https://freebsd-foundation.myshopify.com/>
--
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 "Enterprise WG" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enterprise-wg+unsubscribe@freebsdfoundation.org<mailto: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<https://groups.google.com/a/freebsdfoundation.org/d/msgid/enterprise-wg/CAP%3Ds-_g7g_SWshi_h9ZDxbjrym4TugSKbsYi%3DUQCn2g6Pc%3DqsQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.