X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mx1.tetrasec.net (mx1.tetrasec.net [74.117.190.25]) by lists.alpinelinux.org (Postfix) with ESMTP id 52FACF84D8B for ; Thu, 14 Mar 2019 14:43:34 +0000 (UTC) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 230189E1D4F; Thu, 14 Mar 2019 14:43:34 +0000 (UTC) Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id 4064C9E00FA; Thu, 14 Mar 2019 14:43:32 +0000 (UTC) Date: Thu, 14 Mar 2019 15:43:25 +0100 From: Natanael Copa To: Tuan Hoang Cc: alpine-devel@lists.alpinelinux.org Subject: Re: [alpine-devel] unattended installs (WAS: Should `setup-apkrepos -f` if fails.) Message-ID: <20190314154325.70bb543b@ncopa-desktop.copa.dup.pw> In-Reply-To: References: <4794e0ed-092a-c051-d850-bef86b8bb475@linux.ibm.com> <20190308155207.GA7260@homura.localdomain> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-alpine-linux-musl) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Fri, 8 Mar 2019 17:00:47 +0100 Tuan Hoang wrote: > I would love to hear opinions from Alpine dev team on this matter. > > What's in my mind is something like established method like kickstart > (and preseed too?). > > Something like, you have an init service that watches for kernel parm > 'auto_inst'. If there is, it starts the automated installer for you (and > somehow can reuse our setup-* scripts), with a provided configuration > file. Could be like 'auto_inst=https://yoursite.com/auto_inst.conf'. I > think this would be a nice fit for Alpine. We currently have support for "answer" files. This was added as a hack, and I would like to replace it. I think it would be cool if you could provide alpine with an coud-init yaml file and it would install it based on that. I don't know if cloud-init format is the best or if there are any other alternatives to consider. I just think we should not invent our own format for this. -nc --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---