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 yo
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 ea
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 nei
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 rele
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_ buildi
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.
M
[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 y
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.
oices), leading to further problems, and then people got
> angry.
>
> For details search the misc@ archives for "Reboot and re-link" (the subject
> line), things got spread across multiple threads:
> https://marc.info/?l=openbsd-misc&w=2&r=1&s=Reboot+and+re-link&q=t
>
ding to further problems, and then people got angry.
For details search the misc@ archives for "Reboot and re-link" (the subject
line), things got spread across multiple threads:
https://marc.info/?l=openbsd-misc&w=2&r=1&s=Reboot+and+re-link&q=t
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
> im
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 tool
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 not
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 a
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, &c manag
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 i
aused
hostilities. Can you send me a link to the thread where this happened
please? I want to know why, i.e., pros and cons.
It's the parent thread of this one (look for subject line "Reboot and
re-link").
The issue was not Ansible, just that the original thread poster got very angry
with people.
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 password
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
u
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 autoin
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 re
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 OpenBSD
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 discussed
On 21 June 2019 14:04:50 BST, Florian Obser wrote:
>On Thu, Jun 20, 2019 at 10:47:49PM +0200, mathijs wrote:
>> this makes misc@ so much more amusing
>
>It really doesn't. We are not here to have manure tossed at us for the
>audience's amusement.
Agreed. This kind of abuse happens in any FOSS
On Thu, Jun 20, 2019 at 10:47:49PM +0200, mathijs wrote:
> this makes misc@ so much more amusing
It really doesn't. We are not here to have manure tossed at us for the
audience's amusement.
Everytime something like this happens it takes time away from hacking
on OpenBSD. It doesn't matter that it
mathijs writes:
> this makes misc@ so much more amusing
I didn't join for the soap opera.
Matthew
Dear Maxim,
How are you?
Have you considered taking time away from the computer and doing
something else for a while? Abusing people generally doesn't work well
when you're asking for something to be done, regardless of whether or
not it's paid work.
Why would anybody with any self-respect resp
t 22:51, Theo de Raadt
wrote:
The OpenBSD user community is has too many people like this.
From: Maxim Bourmistrov
Date: Thu, 20 Jun 2019 22:34:54 +0200
Subject: Re: Reboot and re-link
To: Theo de Raadt
Go away?! I'm your user - FIX IT.
On Thu, 20 Jun 2019 at 22:32, Theo d
On 2019-06-20, Maxim Bourmistrov wrote:
> What is seen in 'top' is what compile does to the sys. snmpd just freacks
> out, and the rest as well.
> This is VMWare. Storage below is VSAN.
> bgpd streches 4 arms - to fw1 and 3 remote VPS. No big deal here. Private
> stuff, no massive peering. No peer
On 6/20/19 5:31 PM, Theo de Raadt wrote:
It just doesn't stop.
Maxim Bourmistrov wrote:
I'd say this whole project is your milking cow.(Having a good times biking??)
You really don't move froward much. Except poor guy trying to fix net stack.
You move around vars, back and forward. But real
lled by law.
>
>
> On Thu, 20 Jun 2019 at 22:51, Theo de Raadt
> wrote:
>
> The OpenBSD user community is has too many people like this.
>
> From: Maxim Bourmistrov
> Date: Thu, 20 Jun 2019 22:34:54 +0200
> Subject: Re: Reboot and re-link
> To: Theo
this makes misc@ so much more amusing
On 6/20/19 10:44 PM, Theo de Raadt wrote:
The OpenBSD user community is has too many people like this.
From: Maxim Bourmistrov
Date: Thu, 20 Jun 2019 22:34:54 +0200
Subject: Re: Reboot and re-link
To: Theo de Raadt
Go away?! I'm your user - FIX IT
Why the f I have old kernel?
The ONE taking care of all sh.
On Thu, 20 Jun 2019 at 22:43, Maxim Bourmistrov
wrote:
> btw, after reboot, sys converted to 6.4 kernel. yet again
> I removed all /bsd*
> Do I need to rm /usr/obj* as well
>
> On Thu, 20 Jun 2019 at 22:12, Theo de Raadt wrote:
>
>
> On Thu, 20 Jun 2019 at 22:51, Theo de Raadt wrote:
>
> The OpenBSD user community is has too many people like this.
>
> From: Maxim Bourmistrov
> Date: Thu, 20 Jun 2019 22:34:54 +0200
> Subject: Re: Reboot and re-link
> To: Theo de Raadt
>
> Go away
As just a “user” who has been trying to learn the OpenBSD way (which does take
some effort), I’m very thankful to you and all the devs.
It’s comedically sad to see the transition from “installing via NOT RECOMMENDED
WAY” to “I’m your user - FIX IT.”
Sorry you are catching needless abuse, and
Theo de Raadt wrote:
> I wish he would leave me alone, I don't need his accusations.
>
> This Maxim obviously works for someone. Sometimes I wonder if I
> should make a phone call.
I cannot tell for sure, but maybe it is one of these people.
https://www.verisure.com/about-us
I lead and colla
22:51, Theo de Raadt wrote:
>
> The OpenBSD user community is has too many people like this.
>
> From: Maxim Bourmistrov
> Date: Thu, 20 Jun 2019 22:34:54 +0200
> Subject: Re: Reboot and re-link
> To: Theo de Raadt
>
> Go away?! I'm your user - FIX IT.
>
&
20 June 2019 21:44:16 BST, Theo de Raadt wrote:
>The OpenBSD user community is has too many people like this.
>
>
>From: Maxim Bourmistrov
>Date: Thu, 20 Jun 2019 22:34:54 +0200
>Subject: Re: Reboot and re-link
>To: Theo de Raadt
>
>Go away?! I'm your user - FIX
The OpenBSD user community is has too many people like this.
From: Maxim Bourmistrov
Date: Thu, 20 Jun 2019 22:34:54 +0200
Subject: Re: Reboot and re-link
To: Theo de Raadt
Go away?! I'm your user - FIX IT.
On Thu, 20 Jun 2019 at 22:32, Theo de Raadt wrote:
I take a lot of responsib
Theo de Raadt wrote:
> Maxim Bourmistrov wrote:
>
> > What is seen in 'top' is what compile does to the sys. snmpd just freacks
> > out, and the rest as well.
> > This is VMWare. Storage below is VSAN.
> > bgpd streches 4 arms - to fw1 and 3 remote VPS. No big deal here. Private
> > stuff, no m
Maxim Bourmistrov wrote:
> What is seen in 'top' is what compile does to the sys. snmpd just freacks
> out, and the rest as well.
> This is VMWare. Storage below is VSAN.
> bgpd streches 4 arms - to fw1 and 3 remote VPS. No big deal here. Private
> stuff, no massive peering. No peering at all, ex
k wrote:
> > On Wed, Jun 19, 2019 at 11:29:32PM +0200, Maxim Bourmistrov wrote:
> >
> >> Hey,
> >>
> >> long story short: reboot and re-link is not practical.
> >>
> >> Long story:
> >> Time to upgrade 6.4 to 6.5.
> >> If re
On 2019-06-20, Otto Moerbeek wrote:
> On Wed, Jun 19, 2019 at 11:29:32PM +0200, Maxim Bourmistrov wrote:
>
>> Hey,
>>
>> long story short: reboot and re-link is not practical.
>>
>> Long story:
>> Time to upgrade 6.4 to 6.5.
>> If re-link been act
On Wed, Jun 19, 2019 at 11:29:32PM +0200, Maxim Bourmistrov wrote:
> Hey,
>
> long story short: reboot and re-link is not practical.
>
> Long story:
> Time to upgrade 6.4 to 6.5.
> If re-link been active in 6.4 (don't remember) - I never noticed it.
> Insta
>
> Hit me with stright answers and no "bs wrap-around".
>
>
Upgrade to a snapshot using bsd.rd, and use sysupgrade from now on.
--
chs
Hey,
long story short: reboot and re-link is not practical.
Long story:
Time to upgrade 6.4 to 6.5.
If re-link been active in 6.4 (don't remember) - I never noticed it.
Installing via NOT RECOMMENDED WAY(following upgrade65.html) - scripting on
steroides (ansible).
All down. Reboot.
and
49 matches
Mail list logo
