From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-0301.mail-europe.com (mail-0301.mail-europe.com [188.165.51.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C6C7E2356D7 for ; Wed, 2 Apr 2025 10:25:00 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=188.165.51.139 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1743589505; cv=none; b=FgaVJ1YlhrOx70zKjwKwtU40X1UKJeuNz2Ys1Mgj0eZkyn6yoBVpjQ3DyiEbXZvPe9pVChMIRvxijcRlvW0t8o3AZlklE0WlJHmGIPwIEtqS73PTyNogiudL5NWWBULszwNkTQ5p+gUEEsgcXymSIkOHG1zM932RbcoFNSYcI+Y= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1743589505; c=relaxed/simple; bh=Ep2Sj0NuRDNNKjwwa97DLXAJ6uVhI21HVUrkvL33Z/E=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=RQFhogy9kIbFyGydzi5wIct6zYC0/jNbmLYY27zZzQTKNz5FSKnB8vJDo+txRFVj/quFS3oNEXtD9PEZpjBfaihjK08SEjkuJ/aCzmPb1Xrebofey6CrY1+/LWH82zzy1zxMXxHRPgcBrRRbv7TCT31e8x8JEiGq+uXWzdqDgqg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=metaspace.dk; spf=pass smtp.mailfrom=metaspace.dk; dkim=pass (2048-bit key) header.d=metaspace.dk header.i=@metaspace.dk header.b=u2q6cmlF; arc=none smtp.client-ip=188.165.51.139 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=metaspace.dk Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=metaspace.dk Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=metaspace.dk header.i=@metaspace.dk header.b="u2q6cmlF" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metaspace.dk; s=protonmail2; t=1743589490; x=1743848690; bh=63jF0pcy0GO8+/MrMVxpz1eIuPquikz3EUPWxZS/40I=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=u2q6cmlFJjRsE5QQh3NyZWx90Zn80K1UdKfMR95Q20cDLwkzN/xeoWVID7NAPrisn 3jourlcYN/zYr5M2q8zVew8zdWzpGkaNCcDkcItDphSWL5OXZvzLv8j1PlIbPME3W+ HRQ8ntRmgg5oIb0qnenAHE1+NZtA99W16VAykd3UeKwwM+bF+4pAH4AIs4mjkSvkKj tNmyQkZq0vQ2vOf+pbDkaWgShGOXPZbM/l4nk5sEzy/auzmmKBhXNfAEbCKD2oVNC/ DKL0XdBbnlungVVV+6UCMKhAQ4e6QC/BS40bO7msieoUNOSjl8HgjulQDEFuJnqF8/ WFo7O91NBD1Jw== Date: Wed, 02 Apr 2025 10:24:45 +0000 To: Luis Chamberlain From: Andreas Hindborg Cc: Daniel Gomez , kdevops@lists.linux.dev, Joel Granados Subject: Re: [RFC] bringup: add semantics to start NixOS support Message-ID: <87y0wic19z.fsf@metaspace.dk> In-Reply-To: References: <20250331100928.5284-1-mcgrof@kernel.org> Feedback-ID: 113830118:user:proton X-Pm-Message-ID: f6e3f10a0177ff4676e9fc8ad146b22f99be2945 Precedence: bulk X-Mailing-List: kdevops@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable "Luis Chamberlain" writes: > On Tue, Apr 01, 2025 at 01:30:30PM +0200, Daniel Gomez wrote: >> On Mon, Mar 31, 2025 at 03:09:28AM +0100, Luis Chamberlain wrote: >> > Tons still left to do... but hey, at least we get to trim clutter out >> > and can aim for a simple setup. TODO: >> > >> > - playbooks/bringup_nixos.yml >> > - playbooks/update_ssh_config_nixos.yml >> > >> > We can probably just trim nixos.nix.j2 so to at least bring up >> > a libvirt guest first, and then the second step is to use process >> > a set of target nodes under a simple workflow. >> > >> > So the only thing here this does is show how we need to first >> > add tons of "support" bools and make terraform and guestfs to select >> > them. That should probably just be its own patch before all this. >> > >> > Then the makefile shows the bare bones bringup we need. But we can >> > probably simplify that more. >> > >> > Signed-off-by: Luis Chamberlain >> >> I have a WIP branch with some cleanup needed for this: >> >> https://github.com/dkruces/kdevops/commits/nixos/ > > OK that and this patch can likely get us going somewhere fast. > >> * kdevops: add nixos support >> This simply makes kdevops runnable in NixOS by >> chaning all the shebangs in scripts/. >> >> * Makefile.kdevops: drop ansible_python_intepreter >> Once ansible cfg series are merged, I think we an get rid of the python >> interperter in the ansible calls and configure that in Kconfig -> ansibl= e.cfg. >> >> * shell.nix >> Just to launch a Nix shell with all kdevops dependencies. Would be cool if that was a flake with a devshell. >> >> * libvirt_user: add nixos support >> Generates a kdevops/ in your Nix configuration/ folder. Output: >> https://github.com/dkruces/nixos-config/tree/main/kdevops >> >> My initial idea was to generate NixOS configuration with Ansible [1]. > > If folks don't want to use libvirt they can just a config yaml entry > describing their qemu junk, and Kconfig should be able then to read that > in and populate pool crap and all that. Do nixos users with > virtualization who are on debian use session URI or system URI? I ask > as system URI crap requires privileges, which is why we do tons of > hoops with sudo for system URI. > > Fedora based distros use session URI by default > Debian based distros use system URI by default > > What do we want to assume for nix os users? > >> But Joel >> tried something different with flakes I think. Adding him to get more fe= eback >> on it. >> >> One thing he found was the need of a hack to be able to launch virt-buil= der [2]: > > Hrm, so the use case was to use virt-builder with nix? Is that the nixy > way to deal with things? I would suggest just spawning qemu directly with user mode networking. No need for root for any of this. Specifically, no need for virsh for just piecing together a few command line arguments. Best regards, Andreas Hindborg