On 4/4/20 5:42 PM, Noah Meyerhans wrote:
>> So, when I'm being asked about it, my answer from an OpenStack operator
>> point of view, is always a big "NO !". I want to be able to service my
>> compute nodes. This means being able to live-migrate the workload away,
>> otherwise, customers may notice
Just for finding the relevant sources easier. Here's the link to the
MR and the discussion during the sprint:
https://salsa.debian.org/cloud-team/debian-cloud-images/-/merge_requests/197
https://gobby.debian.org/export/Sprints/CloudSprint2019/2-%20Building%20images
--
regards Thomas
On Sat, Apr 04, 2020 at 10:17:20AM +0200, Thomas Goirand wrote:
> > The first two bugs are about nested virtualization. I like the idea of
> > deciding to support that or not. I don't know much about nested virt,
> > so I don't have a strong opinion. It seems pretty widely supported on
> > our p
Package: cloud-init
Version: 18.3-6
I am launching a Buster 10.3 EC2 instance with the following user data
to initialise and set the default locale:
#cloud-config
hostname: argon
locale: en_GB.UTF-8
timezone: Europe/London
This fails to set the locale, and "systemctl status cloud
On Fri, Apr 03, 2020 at 11:04:06PM +0200, Thomas Goirand wrote:
> Hi,
>
> Today, Bastian just closed my merge request with the below message:
>
> Bastian Blank wrote:
> > We talked about this before I believe. But I was not able to find what
> > consensus we got out of it about application-specif
On 4/4/20 1:34 AM, Noah Meyerhans wrote:
> On Wed, Apr 01, 2020 at 03:15:37PM -0400, Noah Meyerhans wrote:
>> There are open bugs against the cloud kernel requesting that
>> configuration options be turned on there. [1][2][3]
>
>
>
>> 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952108
>
On 4/2/20 7:55 PM, Ross Vandegrift wrote:
> On Wed, Apr 01, 2020 at 03:15:37PM -0400, Noah Meyerhans wrote:
>> Should we simply say "yes" to any request to add functionality to the
>> cloud kernel? None of the drivers will add *that* much to the size of
>> the image, and if people are asking for t
On Fri, 3 Apr 2020, at 22:56, Noah Meyerhans wrote:
> On Fri, Apr 03, 2020 at 06:16:33PM +0200, Jonathan Ballet wrote:
> > In its own Linux image, AWS apparently ships a set of udev rules + a
> > script to get these device names out of the information exposed by the
> > NVMe devices, which create a
