On 2018-07-31 07:24:58, Noah Meyerhans wrote:
> Thanks, Tomasz, for putting together the summary. Sorry I couldn't be
> there.
>
> On Tue, Jul 31, 2018 at 12:37:51PM +0200, Tomasz Rybak wrote:
> > There was intensive discussion related to automated/unattended
> > upgrades of our images: whether
On Tue, Jul 31, 2018 at 12:37:51PM +0200, Tomasz Rybak wrote:
>We had we had Cloud Team BoF during DebConf 18 in Taiwan, on 2018-07-30.
Video of the session is online too:
http://meetings-archive.debian.net/pub/debian-meetings/2018/DebConf18/2018-07-30/debian-cloud-team-bof.webm
--
Steve
On Tue, Jul 31, 2018 at 07:24:58AM -0700, Noah Meyerhans wrote:
:On a well-maintained system, u-u is trivial to disable if that's the
:admin's desire. On a non well-maintained system, u-u is essential for
:the safety of the user, the cloud provider, and the internet at large.
Stongly agree. If a
Thanks, Tomasz, for putting together the summary. Sorry I couldn't be
there.
On Tue, Jul 31, 2018 at 12:37:51PM +0200, Tomasz Rybak wrote:
> There was intensive discussion related to automated/unattended
> upgrades of our images: whether we should do it at all (there may be
> run in environment
We had we had Cloud Team BoF during DebConf 18 in Taiwan, on 2018-07-30.
We started with short summary of what happened since last year: sprint
in October 2017 in Seattle, hosted by Microsoft Azure team. We still work
on moving all our build processes to use FAI - but for GCE, AWS, and Azure