Date: Mon, 25 May 2020 17:03:41 +1000 From: Chris Knight <stryqx@gmail.com> To: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: freebsd 12.0 azure and azure-agent (waagent) Message-ID: <CAHgj5TQ2FErLh1sGhi43eu5NW0mdVGaat1CqrvX4Lq5-dr%2BU9A@mail.gmail.com> In-Reply-To: <20200524120339.GB84757@bastion.zyxst.net> References: <20200524120339.GB84757@bastion.zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Howdy, azure-agent (waagent) functionality on FreeBSD can be found here: https://docs.microsoft.com/en-us/azure/virtual-machines/linux/freebsd-intro-on-azure The full list of functionality for azure-agent can be found on the GitHub page (https://github.com/Azure/WALinuxAgent). If you upgrade to FreeBSD 12.1, make sure you upgrade the pre-installed package using sysutils/azure-agent in the Ports Tree. You could do this before the upgrade as well as after the upgrade. So long as you don't try any of the Azure provisioning mechanisms during the upgrade (e.g. IP address change) you should be right. On Sun, 24 May 2020 at 22:04, tech-lists <tech-lists@zyxst.net> wrote: > Hello, > > I'm considering upgrading a freebsd instance originally installed onto > azure > via their marketplace. It's freebsd-12.0 and I'd like to bring it to 12.1 > via > freebsd-update. > > I notice that when it was provisioned, it seems azure-agent (waagent) was > installed manually, presumably by azure themselves. It was not installed > via > the pkg install method. It's dependent on python27 which is now obsolete. > Apart from that, it looks just like a standard basic vm. > > What I'd like to know: > > is waagent required for the VM to function? If I upgrade, and something > goes wrong with waagent, will the vm come back up? Or will it be stopped if > waagent is non-functional? > > As 12.0 -> 12.1 involves default python going 27 -> 3[6-7] what do I need > to > look out for regarding waagent? I presume I'm going to have to install > azure-agent (python37) over the top. > > All this is an issue because there's no ILO functionality exposed to the > customer in Azure. > > thanks, > -- > J. > -- Regards, Chris Knight
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHgj5TQ2FErLh1sGhi43eu5NW0mdVGaat1CqrvX4Lq5-dr%2BU9A>