Hi folks,
Our next team meeting is re-re-scheduled for Thu, Apr 18 @ 20:00 UTC.
Apologies for the shuffling - I missed some details the last time
around. We'll meet on jitsi as usual:
https://jitsi.debian.social/DebianCloudMeeting20240418
Thanks,
Ross
On Mon, Apr 08, 2024 at 04:11:10PM -0700, Noah Meyerhans wrote:
> On Thu, Apr 04, 2024 at 09:36:08PM -0700, Ross Vandegrift wrote:
> > Our next team meeting is re-scheduled for next Thu, Apr 11 @ 20:00 UTC.
> > Note
> > the different day! We'll meet on jitsi at:
> >
Hi folks,
Our next team meeting is re-scheduled for next Thu, Apr 11 @ 20:00 UTC. Note
the different day! We'll meet on jitsi at:
https://jitsi.debian.social/DebianCloudMeeting20240411
Thanks,
Ross
On Wed, Apr 03, 2024 at 10:04:26PM -0700, Noah Meyerhans wrote:
> On Wed, Apr 03, 2024 at 09:14:31PM -0700, Ross Vandegrift wrote:
> > > > Our next team meeting is scheduled for next Wed, Apr 10 @ 20:00 UTC. As
> > > > usual we will chat at:
> >
On Wed, Apr 03, 2024 at 02:29:18PM -0700, Noah Meyerhans wrote:
> On Wed, Apr 03, 2024 at 01:58:41PM -0700, Ross Vandegrift wrote:
> > Our next team meeting is scheduled for next Wed, Apr 10 @ 20:00 UTC. As
> > usual we will chat at:
> > https://jitsi.debian.social/Debia
Hello,
Our next team meeting is scheduled for next Wed, Apr 10 @ 20:00 UTC. As
usual we will chat at:
https://jitsi.debian.social/DebianCloudMeeting20240410
Thanks,
Ross
Package: cloud.debian.org
Severity: important
X-Debbugs-Cc: rvandegr...@debian.org
Hi team,
We should probably pull the daily sid and trixie images built with the
compromised xz-utils. Looking at the json manifests, this would be:
sid: all images since 2024-02-27
trixie: 2024-03-05
On Sun, Mar 17, 2024 at 09:39:25AM -0700, Noah Meyerhans wrote:
> On Wed, Mar 13, 2024 at 09:23:35PM -0700, Ross Vandegrift wrote:
> > Noah raised an issue related to a bug in systemd-resolved, and we agreed
> > that
> > it should be disabled for now. Upstream bu
On Fri, Mar 22, 2024 at 04:12:57PM +0100, Stephan Müller wrote:
> Oh, interesting! Thanks for the quick answer. Do you know if and how I can
> control this behavior?
cloud-init is trying to figure out if it's running on GCE by checking
for the local metadata service. It should fail and move on.
Hello everyone,
Here are my notes from today's team meeting.
cloud-init updates
--
cloud-init has been updated to 24.1.1 in unstable. For the full details on
what's new, please refer to the upstream changelog at:
https://github.com/canonical/cloud-init/blob/24.1.1/ChangeLog
Hello,
Our next team meeting is scheduled for Wed Mar 13, 2024 @ 20:00 UTC. It looks
like jitsi.debian.social is back - so we'll be online at:
https://jitsi.debian.social/DebianCloudMeeting20240313
Thanks,
Ross
Control: tags -1 pending
On Mon, Feb 19, 2024 at 01:47:24PM -0800, Ross Vandegrift wrote:
> On Tue, Dec 05, 2023 at 11:04:12PM +0100, Santiago Vila wrote:
> > During a rebuild of all packages in unstable, your package failed to build:
>
> I started updating to the latest upstream
On Tue, Dec 05, 2023 at 11:04:12PM +0100, Santiago Vila wrote:
> During a rebuild of all packages in unstable, your package failed to build:
I started updating to the latest upstream release, which fixes this FTBFS. But
I'm reluctant to push to the team repo, due to an issue with the network
Control: severity -1 normal
Hello,
On Sun, Feb 18, 2024 at 01:09:56PM -0800, Flavio Veloso Soares wrote:
> So I just want to clarify what's the current status quo regarding
> systemd-resolved/-networkd in cloud images so I can file bug reports
> properly.
Not a bug - it was done in [1].
Hi folks,
On Fri, Feb 09, 2024 at 08:56:19AM -0800, Ross Vandegrift wrote:
> Our next team meeting is scheduled for 2024-02-14 @ 20:00UTC. We'll be
> on jitsi at: https://jitsi.debian.social/DebianCloudMeeting20240214
Looks like that prediction was incorrect - I guess jitsi.debian.soci
Hi folks-
Our next team meeting is scheduled for 2024-02-14 @ 20:00UTC. We'll be
on jitsi at: https://jitsi.debian.social/DebianCloudMeeting20240214
Thanks,
Ross
On Tue, Feb 06, 2024 at 11:26:47AM +0100, Renzo Davoli wrote:
> Thank you Noah,
> On Wed, Jan 31, 2024 at 07:52:08AM -0800, Noah Meyerhans wrote:
> > On Wed, Jan 31, 2024 at 03:26:05PM +0100, Renzo Davoli wrote:
> > >no new sid cloud images have been created in
> > >
Hi Jonathan,
On Mon, Feb 05, 2024 at 08:59:56PM +0200, Jonathan Carter wrote:
> Hey Ross!
>
> On 2023/12/15 07:14, Ross Vandegrift wrote:
> > We prefer the previous text here: the contract work with SPI covers more
> > than
> > just the cloud images.
> >
&
Hi everyone,
The team met this week, but didn't have any significant items come up. With
the holidays, none of us had significant time to put into cloud team business.
Noah mentioned that a few of our packages are ready for new upstream versions,
including cloud-init and awscli. See the recent
Hello and happy new year,
Our next team meeting is scheduled for 2024-01-10 @ 20:00UTC. We'll be
on jitsi at: https://jitsi.debian.social/DebianCloudMeeting20240110
Thanks,
Ross
On Sun, Dec 10, 2023 at 08:54:41PM +, bittn...@gmail.com wrote:
> Hello... I had a few questions about running Debian Bookworm versions
> (generic, genericcloud) on hypervisors like qemu or kvm.
> My first problem is user and password... I tried to use cloud-init according
> to the
On Sat, Dec 16, 2023 at 06:32:03PM +0100, Bastian Blank wrote:
> On Sat, Dec 16, 2023 at 06:15:43PM +0100, Thomas Lange wrote:
> > Is it worth to switch?
I think it's a good idea.
> What is the minimum qemu version for using those files?
5.1, I think: qemu seems to have a single block
Hi Jonathan,
Digging up an old thread from last July regarding an update to the cloud team
delegates and delegation text. If you have some time, it'd be great to finish
this up.
On Sat, Jul 02, 2022 at 10:40:08AM +0200, Bastian Blank wrote:
> On Fri, Jul 01, 2022 at 10:21:51PM -0700, R
Hello,
Here are some notes on this week's discusison.
Extension support in Azure
==
Microsoft has reversed course on the issue described in [1], the VM extensions
are now opt-in. Bastian Blank is working on a change to re-enable extension
support in the waagent config
On Fri, Jul 28, 2023 at 02:44:43PM -0700, Ross Vandegrift wrote:
> Until recently, extensions required user consent to install. But a
> recent patch [3] to the Azure CLI has changed this. Azure CLI's future
> defaults will automatically install the Guest Attestation Extension,
>
Hi Andrew,
On Wed, Nov 29, 2023 at 08:22:35PM +1300, Andrew Ruthven wrote:
>
> I've spotted a few issues with the netplan config in the Bookworm image, as
> listed below.
>
> I think (1) is probably with netplan and (2) and (3) are with cloud-init.
>
> Are others seeing these? In my case, this
On Mon, Nov 13, 2023 at 01:48:09PM +0900, Osamu Aoki wrote:
> But not for LXD since it uses different images. Image normally downloaded and
> used by `lxc launch ...` becomes buggy once its instance is started because
> then
> cloud-init starts system initialization with its default setting.
Oh
Hi folks,
Our next team meeting is scheduled for 2023-12-13 @ 20:00UTC. We'll be
on jitsi at: https://jitsi.debian.social/DebianCloudMeeting20231213
Thanks,
Ross
Hello,
On Tue, Dec 05, 2023 at 10:32:18PM +0100, Dick Visser wrote:
> I used just that very URL
> http://ftp.debian.org/debian/dists/bookworm/main/installer-amd64/current/images/netboot/
The cloud team maintains the pre-installed images at:
https://cloud.debian.org/images/cloud/ - the debian
On Sat, Nov 11, 2023 at 09:46:51PM +0900, Osamu Aoki wrote:
> Package: cloud-init
> Version: 22.4.2-1
> Severity: normal
>
> ## Background:
>
> The problem and possible root cause fix are reported on upstream github
> issue: https://github.com/canonical/cloud-init/issues/4603
>
> ## Issue:
> I
Hi Amy,
On Mon, Oct 16, 2023 at 11:22:12AM -0700, Amy Crate wrote:
> We have some teams in GCP that would like to make use of the
> linux-headers-cloud-amd64 package. Sometimes they are using an image for
> longer than the default kernel on that image has a linux-headers package in
> the
Hi everyone,
Here are my notes from this week's cloud team meeting.
CI job `test python latest` requires adjustment
===
One of the CI jobs tests our python source against the latest python release.
It's failing after the 3.12 release. I started
Hello,
Our next team meeting is scheduled for 2023-10-11 20:00 UTC. We'll be
on jitsi: https://jitsi.debian.social/DebianCloudMeeting20231011.
Ross
Control: tags -1 moreinfo
Hi Tom,
> I created an EC2 instance in us-east-1 using the command line below. The
> instance does not have a public IP, although I requested one. It is not
> possible to add a public IP after creation time, except for elastic IPs,
> which carry additional cost.
I
Hello,
Our next team meeting is scheduled for 2023-09-13 20:00 UTC. We'll be
on jitsi: https://jitsi.debian.social/DebianCloudMeeting20230913.
Ross
ns wrote:
>
> > On Wed, Aug 02, 2023 at 09:58:01PM -0700, Ross Vandegrift wrote:
> > > Our next team meeting is scheduled for 2023-08-09 20:00 UTC. We'll be
> > > on jitsi: https://jitsi.debian.social/DebianCloudMeeting20230809.
> >
> > I'll be attending the cloud-ini
Hi Lucas,
On Wed, Aug 02, 2023 at 10:38:24PM -0700, Ross Vandegrift wrote:
> The system tests need some easy fixes. The end to end test tries to boot the
> image on the native arch. It probably needs a feature to check if qemu is
> needed. Time permitting, I plan to look at these in
Hi Lucas,
On Wed, Jul 26, 2023 at 08:53:29PM +0200, Lucas Nussbaum wrote:
> On 24/07/23 at 22:00 -0700, Ross Vandegrift wrote:
> > I've been in touch with folks from the kdevops project [1]. They are
> > looking
> > for more vagrant images for arm64. Would it b
Hello,
Our next team meeting is scheduled for 2023-08-09 20:00 UTC. We'll be
on jitsi: https://jitsi.debian.social/DebianCloudMeeting20230809.
Thanks,
Ross
Hello,
On Wed, Aug 02, 2023 at 10:21:46AM +0530, T K Sourabh wrote:
> During our testing, we found that bookworm debian-cloud image uses
> chronyd instead of the new debian default systemd-timesyncd[1].
>
> We wanted to understand the reasoning for this and why is chronyd is
> kept as default
If you use the Azure CLI's future defaults to launch a VM, the VM may be
modified without notifying you. This is not specific to Debian, and is due to
an Azure change. This message will explain the situation, our response, and
the user impact.
Background
==
Azure VM extensions are
Package: cloud.debian.org
Severity: wishlist
User: cloud.debian@packages.debian.org
Usertags: vagrant image
X-Debbugs-Cc: rvandegr...@debian.org
Hello,
I've been in touch with folks from the kdevops project [1]. They are looking
for more vagrant images for arm64. Would it be possible to
On Thu, Jul 20, 2023 at 02:23:38PM +, Shawn Weeks wrote:
> I’m not exactly sure where this issue should go in GitLab but it looks like
> the generic cloud images are creating the netdev group with a GID > 999 which
> causes anything that installs network-manager to fail since it expects
On Thu, Jul 13, 2023 at 12:17:38PM -0700, Noah Meyerhans wrote:
> On 7/13/23 12:08, Emanuele Rocca wrote:
> > Hi,
> >
> > https://lwn.net/Articles/937830/ mentions that a kernel developer could
> > not find arm64 virtualisation images for any distro except for openSUSE:
> >
> > > There are no
Hi Lukas,
On Thu, Jul 06, 2023 at 01:03:12PM +0200, Lukas Märdian wrote:
> I'd like to congratulate on a solid Bookworm release!
> With delight I followed your process of switching to the new system-networkd +
> Netplan stack [0,1,2,3] and as the maintainer of netplan.io in Debian I did my
> very
Hello,
I didn't send out notes from last month's meeting - it was right after the
release, and the team didn't really have much business. But this month, we
have a cavalcade of administrative issues.
GCP billing migrations
==
Andrew Jorgensen from Google has reminded us
Hi folks,
Our next team meeting is scheduled for 2023-07-12 20:00 UTC. We'll be
on jitsi: https://jitsi.debian.social/DebianCloudMeeting20230712.
Thanks,
Ross
Hello,
Our next team meeting is scheduled for 2023-06-14 20:00 UTC. We'll be
on jitsi: https://jitsi.debian.social/DebianCloudMeeting20230614.
Thanks folks,
Ross
Hi Nick,
On Thu, May 25, 2023 at 01:51:51PM +, Nick Armstrong wrote:
> Hi there, what would it look like to get an Oracle Cloud-optimized
> build of Debian published to our Marketplace? We’re interested in
> doing something like this, and wondering where to start, who to talk
> with, etc.
Hi folks,
On Tue, May 09, 2023 at 05:27:10PM +0200, Bastian Blank wrote:
> Our next team meeting is scheduled for 2023-05-10 20:00 UTC. We'll be
> on jitsi: https://jitsi.debian.social/DebianCloudMeeting20230510.
I've been traveling and this slipped my mind - thanks Bastian for
sending this
Hi folks,
We had a short meeting today, seems that things will be quiet leading up to the
bookworm release.
EC2 AMI changes for bookworm
There's two tweaks we'd like to make to the EC2 images prior to the bookworm
release:
- prefer uefi boot
- switch to gp3 storage
On Fri, Apr 07, 2023 at 01:26:48AM +, Winnie Yue wrote:
> Could you please upgrade cloud-init to the latest release 23.1.1? Your
> help will be greatly appreciated. Thanks.
We are currently in the freeze period for the bookworm release, so this
won't happen until after the release is
Hi everyone,
Our next team meeting is scheduled for 2023-04-12 20:00 UTC. We'll be
on jitsi: https://jitsi.debian.social/DebianCloudMeeting20230412
Talk to you soon,
Ross
On Mon, Mar 06, 2023 at 10:51:47AM -0800, Ross Vandegrift wrote:
> Our next team meeting is scheduled for 2023-03-08 20:00 UTC. We'll be
> on jitsi: https://jitsi.debian.social/DebianCloudMeeting20230308
There's a good chance I'll miss the meeting - my son's home sick, and
it'll be m
Hi everyone,
Our next team meeting is scheduled for 2023-03-08 20:00 UTC. We'll be
on jitsi: https://jitsi.debian.social/DebianCloudMeeting20230308
Talk to you soon,
Ross
On Fri, Feb 17, 2023 at 09:54:08PM +0100, Santiago Vila wrote:
> After applying the suggested patch, the reported error
> does not show anymore.
>
> Instead, I get this:
>
> /scripts/local-bottom/growroot: line 97: wait-for-root: not found
>
> Where does this "wait-for-root" come from?
> I
On Thu, Feb 09, 2023 at 08:27:34AM +0100, Bastian Blank wrote:
> On Wed, Feb 08, 2023 at 09:26:55PM -0800, Ross Vandegrift wrote:
> > - 8 cpu arm64, 16G of RAM (in AWS-speak: c6g.2xlarge)
>
> My thought was on m6g.2xlarge. With a more useful amount of ram (32
> GB). While rsyn
Hello,
Here are my notes from today's discussion.
Future of cloud boot
The team discussed some possible future plans for moving away from grub
during the next release cycle. systemd-boot is attractive, but there
are two outstanding issues:
1) currently, it isn't signed for
Hi Julien,
On Mon, Jan 23, 2023 at 05:24:51PM +0100, Julien Cristau wrote:
> On Tue, Jan 17, 2023 at 22:22:59 -0800, Ross Vandegrift wrote:
> > It probably makes sense for the cloud team to own the cloud
> > infrastructure, and DSA to own the OS config and ongoing operations. I
Hi everyone,
Our next team meeting is scheduled for 2023-02-08 20:00 UTC. We'll be
on jitsi: https://jitsi.debian.social/DebianCloudMeeting20230208
Talk to you soon,
Ross
On Fri, Dec 16, 2022 at 03:48:00PM -0800, Ross Vandegrift wrote:
> At a high level the issue is: firewalld.service forces network-pre.target
> after
> sysinit.target, but cloud-init.service forces the other way around. In
> detail,
> using < to represent Before, the imposed o
Hi Julien,
Digging up this thread after our last cloud team meeting, hoping to
shake out the next steps. Summarizing things so far:
1. you've provded some technical requirements for the hosts, all of
which sound easily do-able to me.
2. Amazon has given us the go-ahead to use their sponsored
Hi everone,
We had a short team meeting last Wed, here are my notes - apologies for
the delay!
mirror improvements
---
Our DNS delegation for debian.cloud is in place, which finally wraps up
the DNS config blockers for the mirror improvements. Thanks to DSA,
SPI, and DPL for
Hi everyone,
Our next team meeting is scheduled for 2023-01-11 20:00 UTC. We'll be
on jitsi: https://jitsi.debian.social/DebianCloudMeeting20230111
Talk to you soon,
Ross
Hello,
Here are my notes from this past Wednesday's meeting.
awscli updates
--
All of the relevant python aws packages were recently updated to the latest
versions. And aws-crt-python is waiting in NEW. This will enable awscli v2.
gitlab pipeline issues
--
On Mon, Dec 12, 2022 at 05:41:46PM -0800, Noah Meyerhans wrote:
> On 12/12/2022 6:44 AM, Sam Hartman wrote:
> > >> From my quick read: Michael Biebl proposes dropping
> > >> network-pre.target
> > Ross> from cloud-init's After=, and replacing it with each of the
> > Ross>
Control: forwarded -1
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1956629
Hi Guillaume,
On Tue, Dec 06, 2022 at 06:26:26PM +0100, Guillaume Knispel wrote:
> firewalld and cloud-init have ordering cycles between their systemd unit
> files, leading to more or less broken boot
Hi everyone,
Our next team meeting is scheduled for 2022-12-14 20:00 UTC. We'll be
on jitsi: https://jitsi.debian.social/DebianCloudMeeting20221214
Talk to you soon,
Ross
On Mon, Nov 28, 2022 at 09:02:01AM -0800, Noah Meyerhans wrote:
> On Sun, Nov 13, 2022 at 09:51:52PM -0800, Ross Vandegrift wrote:
> > Noah Meyerhans has continued the work packaging awscli v2. We discussed the
> > issues surrounding the current dependencies of aws-crt-py
Here are my notes from the recent meeting:
Progress on awscli v2
-
Noah Meyerhans has continued the work packaging awscli v2. We discussed the
issues surrounding the current dependencies of aws-crt-python - upstream
sometimes breaks api & abi compatibility without changing
Hello folks,
Our next team meeting is scheduled for 2022-11-09 20:00 UTC. We'll be
on jitsi: https://jitsi.debian.social/DebianCloudMeeting20221109
Regards,
Ross
On Fri, Nov 04, 2022 at 02:56:45PM -0700, Noah Meyerhans wrote:
> Given the number of packages involved, though, I expect it'll take a
> while for everything to have a properly managed SONAME. Given that, I
> see a few alternatives:
>
> 1. We package aws-crt-python with all the aws-c-* packages
On Wed, Nov 02, 2022 at 10:26:50PM -0700, Noah Meyerhans wrote:
> Honestly, filing some of the ITPs would be quite helpful at this point.
> We'll need to get the following projects packaged:
>
> aws-c-auth
> aws-c-cal
> aws-c-compression
> aws-c-event-stream
> aws-c-http
I got this far, and
Hi Noah,
On Mon, Oct 31, 2022 at 10:50:19PM -0700, Noah Meyerhans wrote:
> On Tue, Oct 05, 2021 at 11:10:43PM -0600, Ross Vandegrift wrote:
> > > awscli v2 remains quite difficult to package, but it seems that upstream
> > > is looking to address this. See
> > >
(moving to debian-cloud@lists.d.o)
On Wed, Oct 26, 2022 at 09:26:02AM -0700, Eric Stone wrote:
> I have a problem on AWS, where I have about 20 servers that I cannot access
> because I cannot re-subscribe to the AMI.
I don't quite follow - once a VM is launched, access to the VM should be
Hello,
Here are my notes from today's meeting.
systemd-tmpfiles for /var
=
We discussed Bastian's proposal [1], to use systemd-tmpfiles to manage /var.
The eventual goal is to support trusted systems, where installed packages can
be meanigfully authenticated before
Hello folks,
Our next team meeting is scheduled for 2022-10-12 20:00 UTC. We'll be
on jitsi: https://jitsi.debian.social/DebianCloudMeeting20221012
Regards,
Ross
On Wed, Sep 21, 2022 at 03:11:53PM -0700, Viktor Bogdanov wrote:
> Could you please clarify why Debian AWS AMIs use "init" as process 1 while
> "regular" Debian uses "systemd"?
You might be thrown by the cmdline for pid 1 - the binary is named
/sbin/init, but it comes from systemd. For instance,
On Wed, Aug 24, 2022 at 09:12:23PM +0100, Marcin Kulisz wrote:
> On 2022-08-23 22:55:27, Ross Vandegrift wrote:
> > On Fri, Aug 12, 2022 at 05:37:33PM +0100, Marcin Kulisz wrote:
>
> snip
>
> > > My take on the latter would be that one of the delegates if we'd have
On Wed, Aug 24, 2022 at 09:51:40PM +0200, Bastian Blank wrote:
> On Tue, Aug 23, 2022 at 10:55:27PM -0700, Ross Vandegrift wrote:
> > On Fri, Aug 12, 2022 at 05:37:33PM +0100, Marcin Kulisz wrote:
> > > My take on the latter would be that one of the delegates if we'd h
On Fri, Aug 12, 2022 at 05:37:33PM +0100, Marcin Kulisz wrote:
> I have managed to talk to Jeb and he is very receptive for the idea of handing
> over root access to the account.
> We just need to provide him with the group email address which he is going to
> put on the account and he will remove
On Mon, Aug 22, 2022 at 09:07:29AM +0200, Bastian Blank wrote:
> On Sun, Aug 21, 2022 at 10:35:38PM -0700, Ross Vandegrift wrote:
> > According to apt-transport-mirror(1), apt can do this on the client side.
> > Once
> > the MR for mirror+file apt sources is merged, w
Hi Bastian,
Thanks for putting this together, it looks pretty good.
On Sun, Aug 21, 2022 at 09:22:17PM +0200, Bastian Blank wrote:
> We need to look how we can use deb.debian.org as last resort fallback.
> Fastly requires explicit config of the domains, which is quite possible,
> as they support
On Wed, Aug 17, 2022 at 07:40:04PM -0700, Noah Meyerhans wrote:
> Adding some tracing to the dhclient-script, I can see that
> /etc/dhcp/dhclient-exit-hooks.d/rfc3442-classless-routes is trying to add
> the routes with calls like:
>
> ip -4 route add 169.254.169.254/32 via 169.254.0.1 dev ens5
>
Hi everyone,
Here are my notes from this week's meeting.
debian.cloud
The registration process for debian.cloud is complete. We're starting to plan
nameservers. Our goal is to provide Debian-controlled hostnames for archive
mirrors hosted in the various cloud providers. Stay
On Tue, Aug 09, 2022 at 03:40:52PM +, Jeremy Stanley wrote:
> On 2022-08-09 08:19:06 -0700 (-0700), Ross Vandegrift wrote:
> > On Tue, Aug 09, 2022 at 06:26:55AM +, Ethan wrote:
> > > I cannot find GPG-signed SHA512SUMS files for the Debian Cloud images.
> > > Wh
On Tue, Aug 09, 2022 at 06:26:55AM +, Ethan wrote:
> I cannot find GPG-signed SHA512SUMS files for the Debian Cloud images.
> Where are the SHA512SUMS.sign files for verification?
Sorry, there aren't currently signatures for those checksums.
Ross
Hi team,
Our next meeting is scheduled for next Wed, Aug 10 @ 20:00UTC. We'll be
on jitsi: https://jitsi.debian.social/DebianCloudMeeting20220810
See ya then,
Ross
Hi Luis,
On Tue, Jul 12, 2022 at 12:21:51PM -0700, Luis Chamberlain wrote:
> On Thu, Jul 07, 2022 at 07:54:38AM +0200, Lucas Nussbaum wrote:
> > On 06/07/22 at 18:10 -0700, Luis Chamberlain wrote:
> > > Curious, is any of this also useful to build the other cloud images?
> > > Or is that a
Hello,
We'd normally have a team meeting scheduled this Wednesday. But since DebCamp
is underway and DebConf is next week, it seems good to postpone. I won't
be there, but hope everyone attending has a great time.
If there are any pressing items, please shoot out an email.
Until next month,
Hi Jonathan,
On Fri, Jun 24, 2022 at 04:47:23PM +0200, Jonathan Carter wrote:
> Hi Ross and cloud team
>
> On 2022/06/19 07:35, Ross Vandegrift wrote:
> > Okay great. We've never written anything down, but I've been meaning to do
> > it
> > for a while. This
On Mon, Jun 13, 2022 at 11:42:19AM +0200, Jonathan Carter wrote:
> On 2022/06/09 06:50, Ross Vandegrift wrote:
> > We discussed this issue at our meeting today. Everyone in attendance agreed
> > that the provision isn't necessary, and should be removed from the
> > delega
Here are my notes from today's meeting:
Updating the team delegation
We discussed the proposed updates to the team's delegation. No one raised any
concerns regarding removing the conflict of interest prohibitions, either on
the call or on the mailing list. See the
Package: cloud.debian.org
Severity: normal
Hi Olaf,
On Fri, Jun 03, 2022 at 10:03:35AM +0200, Olaf Seibert wrote:
> The PGP signature files, such as SHA512SUMS.sign, are missing from the pages
> https://cdimage.debian.org/images/cloud/bullseye/latest/ and
>
Hi Jonathan,
On Wed, Jun 01, 2022 at 10:28:47AM +0200, Jonathan Carter wrote:
> IMHO some people in Debian have been overly concerned about conflicts of
> interest. It's true that we should be mindful of them, and that people
> should declare when they do arrive at a situation where there's a
Hi team,
Our next meeting is scheduled for Wed Jun 8 @ 20:00UTC. As usual, we'll be on
jitsi in: https://jitsi.debian.social/DebianCloudMeeting20220608
We'll discuss the recent proposal to loosen the requirements that prohibit
cloud provider employees from being team delegates. For context:
-
On Wed, Jun 01, 2022 at 09:17:32AM +0200, Thomas Goirand wrote:
> Agreed. Ross, can you reconsider? Johnathan, your thoughts?
Sure - if we adopt a policy that permits it (and so far it sounds like we
will), I'd be happy to continue.
Ross
On Wed, Jun 01, 2022 at 10:28:47AM +0200, Jonathan Carter wrote:
> That said, I wouldn't want the whole cloud team to work for a single vendor.
> Would it be enough to limit membership in the cloud team, say, at most one
> person in the cloud team who works for any vendor/cloud provider/etc?
>
>
Hi team,
Effective today, I'm resigning as cloud team delegate. I started a new job,
and am no longer eligible due to our conflict of interest prohibition. Since
very little of my cloud team work required delegation, I don't plan on changing
my involvement. I've had less time for Debian in
On Thu, May 05, 2022 at 03:09:23PM -0600, Sam Hartman wrote:
> > "Paul" == Paul Gevers writes:
>
> Paul> I fear my legal language is just not good enough. What are you
> Paul> afraid of? And are you already afraid of that in the current
> Paul> situation where we are already
1 - 100 of 237 matches
Mail list logo
