On Mon, Jun 24, 2019 at 10:59:44AM +0200, David Sastre wrote:
I would not consider ansible as the right tool to provision a system
from scratch (as in PXE booting, etc...).
Ansible is better used on a system you can connect to using SSH and
perform actions as required, with or without doas, as
On Mon, Jun 24, 2019 at 11:43:36AM +0300, Gregory Edigarov wrote:
I don't want to re-open the hostilities, but installing OpenBSD via
Ansible is very relevant to my interests. Previously discussed on
this list was a very roundabout approach using Qemu -- is there a
better way now?
it's all
On Fri, Jun 21, 2019 at 11:50 PM Frank Beuth wrote:
>
> On Fri, Jun 21, 2019 at 12:36:22PM -0700, Misc User wrote:
> >I use PXE + install.conf + siteXX.tgz + siteXX-%hostname%.tgz for my
> >installs. I also have an rc.firsttime to download and install the
> >required packages.
>
> Thanks, but
On 21.06.19 21:02, Frank Beuth wrote:
On Wed, Jun 19, 2019 at 11:29:32PM +0200, Maxim Bourmistrov wrote:
Installing via NOT RECOMMENDED WAY(following upgrade65.html) -
scripting on
steroides (ansible).
I don't want to re-open the hostilities, but installing OpenBSD via
Ansible is very
On Sun, Jun 23, 2019 at 10:49:22AM +0300, cho...@jtan.com wrote:
Frank Beuth writes:
You go ahead and continue to trust your VPS without taking any care to
consider where your software comes from.
It's choices like that which make "hardening" even be a thing. Have you
considered _not_
Frank Beuth writes:
>
You go ahead and continue to trust your VPS without taking any care to
consider where your software comes from.
It's choices like that which make "hardening" even be a thing. Have you
considered _not_ building a system on a foundation made of cheese?
Have fun with that.
[Please ignore the previous message I sent on this topic. I
accidentally pressed 'Send' before my message was complete.]
On 22/06/2019 19:52, cho...@jtan.com wrote:
> Lyndon Nerenberg writes:
>> We are looking forward to that. *However*, there is a lot to be
>> said for regularly re-installing
On 22/06/2019 19:52, cho...@jtan.com wrote:
> Lyndon Nerenberg writes:
>> We are looking forward to that. *However*, there is a lot to be
>> said for regularly re-installing your hosts from scratch. This
>> ensures your installer scripts don't rot as host system "features"
>> accrete over time.
Using Ansible to reinstall the operating system is like trying to turn a four
door sedan into a monster truck with a hammer.
Wrong tool for the job.
> On Jun 22, 2019, at 6:46 PM, Frank Beuth wrote:
>
>> On Sat, Jun 22, 2019 at 03:06:30AM +0100, Andrew Luke Nesbit wrote:
>>> On 21/06/2019
On Sat, Jun 22, 2019 at 03:06:30AM +0100, Andrew Luke Nesbit wrote:
On 21/06/2019 19:02, Frank Beuth wrote:
I don't want to re-open the hostilities, but installing OpenBSD via
Ansible is very relevant to my interests.
I feel exactly the same way and am surprised that Ansible caused
Frank Beuth writes:
> That's the interesting thing in my case (at least)... the system *IS* already
> extant!
And how have you introduced it to your command-and-control system? That
is, ultimately, the key.
> It has a nice shiny new Ubuntu/Debian/Fedora/centOS install that has just
> been
>
On Sat, Jun 22, 2019 at 10:29:22PM +0300, cho...@jtan.com wrote:
Ansible is not the correct tool for this job; it can only configure and
maintain an _extant_ system.
None of the recent plethora of configuration management tools have
considered the scenario *before* an operating system has been
On 21/06/2019 19:02, Frank Beuth wrote:
> I don't want to re-open the hostilities, but installing OpenBSD via
> Ansible is very relevant to my interests.
I feel exactly the same way and am surprised that Ansible caused
hostilities. Can you send me a link to the thread where this happened
please?
Frank Beuth writes:
> Yes, and being able to Ansible-manage even the re-installation would make the
> whole process that much nicer :)
Ansible is not the correct tool for this job; it can only configure and
maintain an _extant_ system.
None of the recent plethora of configuration management
Frank Beuth writes:
> Yes, and being able to Ansible-manage even the re-installation would make the
> whole process that much nicer :)
I started writing a rebuttal to this, but it quickly turned into writing
our design document for how we handle this internally across he data-
centre. That's
Lyndon Nerenberg writes:
> We are looking forward to that. *However*, there is a lot to be
> said for regularly re-installing your hosts from scratch. This
> ensures your installer scripts don't rot as host system "features"
> accrete over time. This is prone to happen when you Ansible- or
Or
On Sat, Jun 22, 2019 at 10:28:53AM -0700, Lyndon Nerenberg wrote:
We are looking forward to that. *However*, there is a lot to be
said for regularly re-installing your hosts from scratch. This
ensures your installer scripts don't rot as host system "features"
accrete over time. This is prone
Daniel Jakots writes:
> You can automate installation with autoinstall(8). You can also
> automate upgrades with autoinstall(8)
This works like a charm. On our load balancers we PXE install
with a local rc.firsttime that installs python. After that we
do all the system, haproxy, nginx,
On 6/22/19 7:23 AM, Frank Beuth wrote:
> I wonder if there is a way to have Ansible build a custom
> autoinstall.conf (using templates) and insert it into bsd.rd immediately
> prior to uploading.
I use elfrdsetroot from upobsd to do something along these lines
$ pkg_info upobsd
Information for
On Sat, Jun 22, 2019 at 04:41:47AM +0100, Andrew Luke Nesbit wrote:
On 21/06/2019 19:02, Frank Beuth wrote:
I don't want to re-open the hostilities, but installing OpenBSD via
Ansible is very relevant to my interests.
I feel exactly the same way and am surprised that Ansible caused
On Fri, Jun 21, 2019 at 01:20:44PM -0700, Misc User wrote:
You could stick bsd.rd onto a bootable partition then point grub to it.
You could also disable password login for root and just use a key pair.
That way you wouldn't be sending the password encrypted (or at most only
giving it a
On Fri, Jun 21, 2019 at 12:36:22PM -0700, Misc User wrote:
I use PXE + install.conf + siteXX.tgz + siteXX-%hostname%.tgz for my
installs. I also have an rc.firsttime to download and install the
required packages.
Thanks, but neither this nor the autoinstall suggestion seem applicable for my
On 6/21/2019 1:08 PM, Frank Beuth wrote:
On Fri, Jun 21, 2019 at 12:36:22PM -0700, Misc User wrote:
I use PXE + install.conf + siteXX.tgz + siteXX-%hostname%.tgz for my
installs. I also have an rc.firsttime to download and install the
required packages.
Thanks, but neither this nor the
On 6/21/2019 11:02 AM, Frank Beuth wrote:
On Wed, Jun 19, 2019 at 11:29:32PM +0200, Maxim Bourmistrov wrote:
Installing via NOT RECOMMENDED WAY(following upgrade65.html) -
scripting on
steroides (ansible).
I don't want to re-open the hostilities, but installing OpenBSD via
Ansible is very
On Fri, 21 Jun 2019 20:02:48 +0200, Frank Beuth
wrote:
> On Wed, Jun 19, 2019 at 11:29:32PM +0200, Maxim Bourmistrov wrote:
> >Installing via NOT RECOMMENDED WAY(following upgrade65.html) -
> >scripting on steroides (ansible).
>
> I don't want to re-open the hostilities, but installing
On Wed, Jun 19, 2019 at 11:29:32PM +0200, Maxim Bourmistrov wrote:
Installing via NOT RECOMMENDED WAY(following upgrade65.html) - scripting on
steroides (ansible).
I don't want to re-open the hostilities, but installing OpenBSD via Ansible is
very relevant to my interests. Previously
26 matches
Mail list logo
