On Thu, Feb 02, 2017 at 04:29:11PM +0800, gustavo panizzo wrote:
> I saw your blog post (which I've attached to this email), then the next
> time I needed an EC2 instance I tested the images on a non-IPv6 region
> (SG) and an IPv6 enabled VPC
>
> overall the image looks fine, no extraneous
On Fri, Feb 24, 2017 at 10:19:53AM +0800, gustavo panizzo wrote:
> I found another issue on the image
>
> $ cat /etc/mailname
> ip-10-0-0-64.us-west-2.compute.internal
Nice catch, thank you!
> and this is not a bug, but a diference in opinion
>
> $ grep security /etc/apt/sources.list
> deb
On Tue, Feb 14, 2017 at 12:32:37AM +0100, Laura Arjona Reina wrote:
> >a few days ago Noah blogged about new Stretch AMIs for testing and was
> >wandering how are we going to let people know about changes etc.
>
Control: severity 693945 important
Control: severity 831848 important
Per discussion among the cloud team, I'm raising these bugs to
important. We want to be sure we release stretch with at least basic
support for the cloud.debian.org pseudopackage.
noah
signature.asc
Description: PGP
On Fri, Nov 04, 2016 at 09:03:39PM -0400, Sam Hartman wrote:
> I pushed to git://git.debian.org/cloud/fai-cloud-images.git.
I've got a FAI config targeting jessie on EC2. It seems to work well and
at this point I'm at the point of tweaking the packages lists and
configuration to match JEB's
On Mon, Nov 07, 2016 at 08:23:10AM +, Marcin Kulisz wrote:
> That's true but there is a bit which makes me quite uncomfortable to be
> precise it's that to do all this stuff from within Debian infra we need to
> keep
> AWS IAM keys on it with permissions for spinning up and down instances
James, you said you fixed this! ;P
admin@ip-10-0-0-64:/var/log/fai/cloud3/last$ sudo apt update
Get:1 http://cloudfront.debian.net sid InRelease [219 kB]
Ign http://cloudfront.debian.net jessie InRelease
Get:2 http://cloudfront.debian.net jessie-updates InRelease [145 kB]
Get:3
And I just pushed some changes to introduce basic stretch support via a
STRETCH class. The following commandline resulted in a working image for
EC2:
fai-diskimage -u stretch8g -S8G -cDEBIAN,STRETCH,AMD64,GRUB_PC,DEVEL,CLOUD,EC2
~/disk.raw
I haven't done anything to optimize the configuration
On Fri, Nov 04, 2016 at 09:03:39PM -0400, Sam Hartman wrote:
> I pushed to git://git.debian.org/cloud/fai-cloud-images.git.
It looks like you're the only person with write access to this repo. It
seems like changing group ownership to 'scm_cloud' and granting group
write permission is the right
On Sun, Nov 13, 2016 at 06:17:33AM -0500, Sam Hartman wrote:
> Noah> I've modified the class/DEBIAN.var file such that the default
> Noah> behavior is to generate images for jessie. We can add a
> Noah> STRETCH class in order to generate images for testing. I'd
> Noah> rather use
On Sun, Nov 06, 2016 at 11:38:33AM -0800, Noah Meyerhans wrote:
> > I pushed to git://git.debian.org/cloud/fai-cloud-images.git.
>
> I've got a FAI config targeting jessie on EC2. It seems to work well and
> at this point I'm at the point of tweaking the packages lists and
On Sat, Dec 10, 2016 at 08:57:22PM +0100, Bernhard Schmidt wrote:
> I don't think this will ever be fixed with ifupdown. I think
> systemd-networkd and NetworkManager do the right thing here, but I have
> never had a look at either for maintaining a _server_. So I will not
> propose switching to
On Wed, Dec 14, 2016 at 08:17:28AM +0100, Thomas Lange wrote:
> I wonder why you need to source /usr/lib/fai/subroutines for importing
> the ifclass subroutine. If your scripts are bash scripts, this
> function should be already available.
Hm. I have no idea why I thought that would be necessary.
On Mon, Dec 05, 2016 at 06:02:12PM +0800, gustavo panizzo (gfa) wrote:
> Watching how I can improve the current status of Debian support at $DAYJOB
> I realized that AWS agents are not packaged even if their license
> allows it
>
> I wonder if packaging them, on main, would make Debian supported
On Wed, Mar 29, 2017 at 10:18:36AM -0700, Zach Marano wrote:
>Yeah I guess I'm asking what the official Debian cloud image build process
>is looking like (or if its been started at all).
The current FAI config has at least some support for GCE, but
unfortunately I don't think anybody has
On Thu, Aug 10, 2017 at 08:28:44AM +0100, kuLa wrote:
> I'm recently fiddling a lot with permissions on the Debian AWS account and
> it's
> been pointed to me that it's worth considering updating IAM settings a bit.
>
> Having above in mind and that DDs are already trusted enough :-) I'm
I've updated the stretch AWS AMIs following today's stable point
release.
The AMIs are owned by AWS account ID 379101102735 and are named
debian-stretch-hvm-x86_64-gp2-2017-07-22-75922.
Regional AMI IDs are:
ap-northeast-1: ami-42769724
us-west-2: ami-52c7df2b
eu-west-2: ami-5c4b5a38
us-east-1:
On Mon, Jun 26, 2017 at 09:55:31AM +0200, Xavier Lembo wrote:
> I've tried today to use my jessie working script on the eu-west-1 stretch
> ami (ami-e79f8781)
>
> My custom ami must have a specific size for first partition, so , i use a
> specific block device mapping.
>
> On the Stretch
On Wed, Jun 14, 2017 at 12:09:26AM +0200, Ana Guerrero Lopez wrote:
> > In the current Debian Stretch announcement (still open for editing),
> > we mention only the OpenStack images. I was wondering about the availability
> > of other official images: GCE, AWS, Azure?
> >
> > Please, see the
On Mon, Sep 25, 2017 at 05:25:40PM +0100, Jacob Smith wrote:
> Would it be possible to make the snapshots, used by the AMIs on the
> 379101102735 account, public so that the AMI can be copied?
I've updated the AMI publication tools to mark the backing snapshots
public. I've published stretch 9.2
On Fri, Oct 13, 2017 at 01:48:53PM +0200, Emmanuel Kasper wrote:
> >> > Building
> >> >
> >>
> >> > any further. We will need to look into tools for making new VMs.
> >> I wonder what is meant by "making new VM".
> >> You do mean creating the disk image for the VM or starting
On Sun, Oct 15, 2017 at 11:14:01PM -0600, Ben Howard wrote:
>Thank you for the idea, however, after looking at it, I see FAI as
>technology akin to KickStart, MAAS, AutoYast, etc.
Ben, as you weren't at last year's cloud sprint, you likely missed that
we settled on using FAI as the cloud
On Sat, Aug 26, 2017 at 05:18:45PM +0100, Ben Hutchings wrote:
> > Thomas, can you elaborate why you think this a good idea? Is this about
> > boot time of the kernel image? The thing I really do not want to have is
> > additional kernel source uploads to the archive for just those cloud
> >
On Mon, Aug 28, 2017 at 01:31:31AM +0100, Ben Hutchings wrote:
> > OTOH, the list of required modules may be small enough for us to
> > enumerate the ones we need for booting in /etc/initramfs-tools/modules.
>
> ...and then you could use MODULES=list. initramfs-tools will still
> follow module
On Sun, Aug 27, 2017 at 04:16:50PM +0200, Thomas Goirand wrote:
> Basically, the only thing that I want to see is a specific config for
> that kernel, nothing else. Otherwise, it's going to be too much
> maintenance work. Indeed, it should *not* be a different source upload,
> that's too much work
On Sun, Sep 03, 2017 at 11:34:30PM +0200, Thomas Goirand wrote:
> BTW, how do I generate the @(#*$& image manifest? Uploading an image to
> amazon is such a pain ... :/
The manifest is created by ec2-bundle-vol. However, it sounds like
you're trying to generate what Amazon calls an "instance
On Fri, Dec 15, 2017 at 08:03:51PM +0100, Bastian Blank wrote:
> > > We at credativ are responsible for maintaining the Azure cloud images.
> > > We got asked by Microsoft to explore the possibilities of introducing a
> > > specialised Linux image for this plattform into Debian. The main
> > >
On Sun, Feb 04, 2018 at 02:55:52PM +1100, Michael Schams wrote:
> However, the AWS scan tool rejects the AMI due to the following issue:
>
> (quote) "Vulnerabilities detected - The following vulnerabilities were
> detected and must be addressed: CVE-2017-5754 [3]."
Unfortunately, only the AWS
On Thu, Feb 15, 2018 at 12:02:22PM +0200, Andrei Popenta wrote:
>I want to ask about an issue I noticed with my AWS AMI, that is created
>from the official Debian Jessie AMI.
Have you checked the stretch AMIs for the same issue?
>It seems like after each time I create a new AMI,
On Thu, Dec 28, 2017 at 07:59:59AM +0100, Marcin Kulisz wrote:
> > Now, as salsa is in beta - should we start using it?
>
> I think so, even if 'shit happens' we have copies of the repos locally and the
> team can be recreated, also atm I'm going to push to alioth and salsa at the
> same time.
On Thu, Jun 21, 2018 at 10:03:32PM +0200, Thomas Goirand wrote:
> I have to admit I don't know a lot about proprietary apis. But as for
> OpenStack, APIs are quite stable, and (almost?) always backward
> compatible thanks to API micro-versions and auto-discoverability. In
> fact, I haven't found
Because I don't anticipate being able to make it to the cloud BoF at
Debconf, I'm sending this update here. Please feel free to discuss any
of the issues; just make sure to record the conversation in the
minutes so I can respond.
Current status
==
Stretch
---
Stretch images are
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
On Wed, Aug 08, 2018 at 05:47:06PM -0400, Jimmy Kaplowitz wrote:
> > No, the main reason it isolation. The builds take some global
> > resources, loop devices, and may not return them in case of some errors.
>
> Google builds their official GCE Debian images inside transient GCE
> instances,
On Tue, Feb 27, 2018 at 11:10:48PM -0500, Christopher David Howie wrote:
> * AMI name is "debian-stretch-hvm-x86_64-gp2-2018-02-22-67467"
>
> * it is owned by AWS account ID 379101102735
>
> * For region us-east-1, the AMI ID is ami-0dc82b70
Apologies, this was my fault. The AMIs are generated
On Sun, Oct 14, 2018 at 06:02:23PM +0100, Steve McIntyre wrote:
> One of our (many!) discussion topics at our sprint last week was
> announcing the end of support for our published Jessie (Debian 8.x)
> images. We strongly recommend that all our existing users should move
> forward to Stretch
On Fri, Oct 19, 2018 at 04:14:47PM +0200, Raphael Hertzog wrote:
> > The main thing: concerns were raised by several of the cloud platforms
> > people that LTS security doesn't seem to be working very well. They're
> > not seeing fixes happening for known issues, and so at the moment they
> >
On Sun, Oct 14, 2018 at 10:53:19AM -0700, Noah Meyerhans wrote:
> I've submitted requests to the AWS Marketplace to remove our Jessie
> listings. They haven't yet acted on these requests, but they should do
> so in the coming week.
It sounds like the removal of the jessie listings
On Mon, Oct 22, 2018 at 11:34:14AM -0700, Larry Fletcher wrote:
> So far the security updates for the Jessie kernel have stayed in the 3.16.*
> range, and I doubt if that will change.
Try apt-cache policy linux-image-4.9-amd64
> A few weeks ago I ran a test "dist-upgrade" to Stretch and was
On Mon, Oct 22, 2018 at 07:12:54PM +, Luca Filipozzi wrote:
> Is this true: the goal of the Debian Cloud Team is to make roughly equievalent
> Debian Cloud Images for the various cloud providers so that
> Debian users have a consistent (to the degree possible) experience with
> Debian in each
On Mon, Oct 22, 2018 at 05:52:15PM +, Luca Filipozzi wrote:
> I object because, at the 2018 Debian Cloud Sprint, we collectively
> decided that we were not offering Debian LTS Cloud Images. Are we
> changing our decision? I'd like to see collective decision making, not
> one-offs for each
On Tue, Oct 23, 2018 at 10:04:33AM +0200, Thomas Goirand wrote:
> >> I object because, at the 2018 Debian Cloud Sprint, we collectively
> >> decided that we were not offering Debian LTS Cloud Images. Are we
> >> changing our decision? I'd like to see collective decision making, not
> >> one-offs
On Tue, Oct 23, 2018 at 11:51:26AM +0100, David Osborne wrote:
>Thank you... so the amis themselves should remain indefinitely?
I'd expect "release" AMIs to remain indefinitely, yes. There's strong
precident for this within AWS in general; it's part of the pledge to not
break users. For
On Sat, Nov 03, 2018 at 10:19:25PM -0600, Jim Freeman wrote:
>2018-10-01 stretch AMI (no idea if this is a regression?)
>/var/log/cloud-init.log claims user-data was run, when it fact it was not,
>with tracebacks and log messages (attached) leading me to think that
>failure is
On Tue, Oct 09, 2018 at 11:01:33AM +, Daniel Strong wrote:
> Stderr: gpg: failed to start the dirmngr '/usr/bin/dirmngr': No such file or
> directory
> gpg: connecting dirmngr at '/root/.gnupg/S.dirmngr' failed: No such file
> or directory
> gpg: keyserver receive failed: No dirmngr
On Wed, Dec 26, 2018 at 09:19:56AM -0500, Paul Graydon wrote:
> We are now standardizing on FAI to build our images. If you want the
> Debian Oracle image to become official, it will have to use that.
>
>I took a quick look at FAI a few weeks back, but the dependency on
>DHCP/tftp made
It's on its way. A newer ENA driver is required for working network, so that's
kind of a blocker.
On November 30, 2018 10:17:06 AM PST, Phil Endecott
wrote:
>Package: cloud.debian.org
>Severity: wishlist
>
>Dear Maintainer,
>
>AWS have recently announced new instance types that use the 64-bit
On Thu, Jan 10, 2019 at 11:08:08AM +0100, Bastian Blank wrote:
> > > > Are there any plans to offer Debian AMIs for them?
> > > See
> > > https://salsa.debian.org/cloud-team/debian-cloud-images/merge_requests/46
> > I see that the MR has now been merged. What would be the next step?
>
> SPI
On Thu, Jan 10, 2019 at 07:22:18PM +0100, Lucas Nussbaum wrote:
> Would it make sense to publish an unofficial image and ask for feedback
> from users?
Let's wait until we have candidate stretch kernel packages that fix
#918330 and especially #918188. I believe at least the latter has a fix
on
On Sat, Sep 15, 2018 at 09:54:04PM +0200, Bastian Blank wrote:
> > ### EC2 upload
> >
> > No idea yet. There is a script in our repo to create a single image.
> > But I see nothing that would handle the whole pipeline with replicating
> > and registering AMI in all the regions.
>
> Shouldn't we
On Fri, Jan 25, 2019 at 02:56:53PM +0100, Bastian Blank wrote:
> While installing locales-all is pretty handy and avoids a lot of
> problems, I realized that is comes with a huge drawback: it makes the
> images a lot larger (230MB uncompressed and over 100MB compressed). It
> makes them so much
> > Noah
> > continue maintaining the stretch images for AWS
Still happening. I also did some driver backporting so we'll be able to
support the Amazon EC2 arm64-based instances with the next point
release. Buster will also support these instances.
> > developing buster aws images
Some progress
On Tue, Mar 26, 2019 at 12:25:12PM +0100, Lucas Nussbaum wrote:
> On https://hub.docker.com/_/debian, there's:
>
> > Where to file issues:
> > https://github.com/debuerreotype/docker-debian-artifacts/issues
>
> Are those official images? I'm surprised by official Debian images
> pointing to a
On Thu, Apr 04, 2019 at 09:27:11AM +1300, Andrew Ruthven wrote:
> > > Would it be possible to move the Ec2 datasource up the list like "[
> > > NoCloud, AltCloud, ConfigDrive, OpenStack, Ec2, CloudStack,
> > > ${DIGITAL_OCEAN_SOURCE} MAAS, OVF, GCE, None ]"? This also seems to
> > > be in line
On Thu, Apr 04, 2019 at 07:51:22PM +0100, Marcin Kulisz wrote:
> > > > Let me know if this stalls; I can put you in touch with someone on
> > > > the Azure team.
> >
> > The Azure team asked some time ago for an email address to attach as
> > owner to those accounts. Also we need that to attach
On Fri, Mar 29, 2019 at 03:09:50PM -0300, Lucas Kanashiro wrote:
> I think DebConf is the perfect place to share with the Debian community
> the work we have been doing and collect feedback :)
+1, this is a great idea. There should also be a BoF for people
interested in a more interactive
On Wed, Feb 20, 2019 at 05:17:11PM +0100, Konstantin wrote:
>Seems that Debian Stretch suffers from this
>bug [1]https://bugzilla.redhat.com/show_bug.cgi?id=1430511
>Please check if this patch can be added to cloud-init
>package
>
On Thu, Feb 07, 2019 at 10:17:53AM +0100, Thomas Goirand wrote:
> As a follow-up with the discussion about agent inside VMs, I wonder if
> we should install qemu-guest-agent inside our images. Normally, it
> provides what Ted was talking about: hooks for freezing filesystem,
> mysql, etc.
I don't
On Tue, May 21, 2019 at 11:14:02AM +0300, Eugeny Romanchenko wrote:
>Is it possible for you to add you current Marketplace image to the list of
>supported for t3a/m5a AWS instances?
I've submitted a request to update the AWS Marketplace listing. The new
listing will use the latest stretch
On Mon, May 20, 2019 at 11:26:00AM +0200, Jorge Barata González wrote:
>Vagrant image debian/stretch64 v9.6.0
>/usr/sbin is not included by default in $PATH
>
>```
>vagrant@stretch:~$ service
>-bash: service: command not found
>vagrant@stretch:~$ /usr/sbin/service
>
Control: severity -1 wishlist
> This is a historical convention, going back decades, that only the
> system administrators needs to run the programs in /sbin and
> /usr/sbin. So to avoid users getting confused when they might run
> those programs and get "permission denied", historically normal
On Mon, May 20, 2019 at 03:38:25PM -0300, Arthur Diniz wrote:
>The first thing we did was a [2][1] [3]Low Fidelity Prototype, this was
>just a draft that we based to came up with the [4][2] [5]High Fidelity
>Prototype.
These look great!
>Also we think that is important that if
On Tue, Apr 30, 2019 at 06:25:47PM +0100, nSed rickm wrote:
>Hi my name is Sedrick I recently joined this mailing Iist to get to know
>more about the debian cloud team .I submited a proposal for GSoC with
>debian this year for the cloud image finder .I would like to catch up on
>
Yesterday I published new stretch AMIs for Amazon EC2 for both arm64 and
amd64 architectures. The AMIs refresh all package version to those
included in Debian 9.9 (stretch), per the release announcement at
https://www.debian.org/News/2019/20190427
The AMI details, as usual, are available at
On Thu, Jul 04, 2019 at 11:49:13PM -0700, Noah Meyerhans wrote:
> amd64: ami-0776bf2e6645ef887
> arm64: ami-00781f5d2e3a6d2ab
Correction, the AMI IDs for ap-southeast-2 are:
amd64: ami-069a1bfa76dd19320
arm64: ami-00781f5d2e3a6d2ab
signature.asc
Description: PGP signature
On Wed, Jul 10, 2019 at 05:58:16PM +0300, Mustafa Akdemir wrote:
>When Debian 10 Buster AWS AMI will be created and added to AWS
>Marketplace?
Unfortunately, we have some administrative details to work out regarding
our publication account with AWS. It will be published as soon as we
On Tue, Jul 02, 2019 at 02:12:27PM -0700, Zach Marano wrote:
>I propose we start planning the next Debian Cloud Sprint.
Sounds like a plan. With DebConf coming up, I suspect there might be an
opportunity to do a bit of planning face-to-face, as well as via email
etc.
I've created a wiki
On Sun, Jul 07, 2019 at 11:49:22PM +0200, Thomas Goirand wrote:
> Why must Debian users on Azure see the word "credativ"? To me, it's as
> if I uploaded the OpenStack image to cdimage.debian.org, with filename
> "openstack-debian-image-provided-by-zigo.qcow2". This feels completely
>
On Sun, Aug 18, 2019 at 07:06:27AM +0100, kuLa wrote:
> >New regions on old AWS account: need root account for that.
>
> Above is not fully correct but anyway it's been sorted and Debian
> cloud images thanks to Noah should be now available in the new regions
> as well.
It's been sorted out for
On Thu, Aug 15, 2019 at 03:38:00PM -0400, Jonathan Proulx wrote:
> Accommodation
> -
> there's a lot of choice (and it is all fairly priicey
> unfortunately). As a visitor Noah may actually have better info than I
Last time I was in the neighborhood, I stayed at the Fairfield Inn &
On Sun, Aug 18, 2019 at 10:36:51AM +0100, Marcin Kulisz wrote:
> > I'm very much for sharing a big airbnb with any of you as well. I've
> > searched too, and it's a way cheaper than hotels indeed. I don't mind
> > walking a bit if it's to get the comfort of a private place. So, count
> > me in
On Tue, Aug 27, 2019 at 10:32:41PM -0300, Antonio Terceiro wrote:
> > Do we have a list of stuff that runs on our old AWS account? As we need
> > to migrate all of this to our new engineering account, it would be nice
> > to actually know what runs there. It would be even better if we know
> >
On Tue, Sep 03, 2019 at 10:24:24AM +0100, kuLa wrote:
> > on my side I would have no objections with a removal.
>
> Should we actively ask for removal or wait till normal bugs will become RC and
> removal for all py2 packages is going to be compulsory?
> I personally am ok with both.
In my
On Sun, Sep 01, 2019 at 12:40:50PM +0200, Bastian Blank wrote:
> As mentioned during the last meeting, I would like to move the daily
> builds out of the main debian-cloud-images project. The new project
> reponsible for them would exist in a different group, so we don't longer
> need to guard
On Mon, Sep 02, 2019 at 05:10:55PM +0200, Thomas Goirand wrote:
> State what? That we're supposed to build the cloud images on Casulana?
> As much as I know, that has always been what we were supposed to do. You
> alone decided that the gitlab's CI was the way to go.
Thomas, you seem to be under
On Sun, Sep 08, 2019 at 07:49:45PM +0200, Bastian Blank wrote:
> If no-one shouts I will do the first release of Buster for AWS with both
> amd64 and arm64 tomorrow. Azure needs to be done anyway.
Do it. A lot of users will be happy to have buster AMIs. The remaining
points that were unresolved
On Wed, Sep 18, 2019 at 10:22:17PM -0500, Stephen Gelman wrote:
> On Sun, Sep 08, 2019 at 07:49:45PM +0200, Bastian Blank wrote:
> > > If no-one shouts I will do the first release of Buster for AWS with both
> > > amd64 and arm64 tomorrow. Azure needs to be done anyway.
>
> Seems this didn’t
On Sun, Aug 04, 2019 at 10:15:32PM +0200, Tomasz Rybak wrote:
> > So I'd say Wednesday 7th of Aug at 1900UTC or maybe we could use
> > something like
> > doodle.com to coordinate this?
>
> I propose the same weekday (Wednesday) and hour (19:00 UTC),
> but let's move to next week (so 2019-08-14).
On Mon, Aug 05, 2019 at 05:57:57PM +0100, Marcin Kulisz wrote:
> > 1900 UTC makes it 2100 Geneva time. I'd very much prefer something
> > during work hours if possible. Or is it that the majority of us is doing
> > this away from office hours?
>
> I suggested this time having in mind that quite a
On Thu, Aug 08, 2019 at 05:56:44PM -0700, Tarjei Husøy wrote:
> > The AMIs in the AWS marketplace should be launchable in the new regions.
> > See https://aws.amazon.com/marketplace/pp/B073HW9SP3 and let me know if
> > it'll work for you. The Marketplace AMIs are identical to the ones we
> >
> Amazon recently launched two new regions, Hong Kong (ap-east-1) and
> Bahrain (me-south-1). All new regions after March 20, 2019 come on a
> opt-in basis [1], thus you might not have seen them show up unless you
> saw the news when they were introduced. Would it be possible to have
> stretch
Package: cloud.debian.org
Severity: important
Control: submitter -1 Tarjei Husøy
Hi,
Amazon recently launched two new regions, Hong Kong (ap-east-1) and Bahrain
(me-south-1). All new regions after March 20, 2019 come on a opt-in basis [1],
thus you might not have seen them show up unless you
On Sat, Jul 20, 2019 at 11:26:38PM +0300, Mustafa Akdemir wrote:
>Can i use Debian GNU/Linux 9 (Stretch) AMI by upgrading to Debian
>GNU/Linux 10 (Buster) for Wordpress web site server until Debian GNU/Linux
>10 (Buster) AMI will be published. May it cause any problem by upgrading
>
On Wed, Dec 04, 2019 at 01:16:27PM +1100, paul wrote:
> I'm reworking my old VPN server, and will use the Debian 10 AMI in AWS. I've
> noticed that predictable network interface names are enabled for t3 servers,
> but not t2 - I have test setup on a t2.micro and a t3.micro, and only the t3
> has
On Mon, Dec 09, 2019 at 06:18:15PM +0200, Michael Kanchuker wrote:
>Is there an official image like with Jessie or Stretch?
Yes, details are at https://wiki.debian.org/Cloud/AmazonEC2Image/Buster
It is not yet available on the AWS Marketplace because we are still
blocked on some legal
On Fri, Dec 06, 2019 at 04:42:18PM +0100, Dick Visser wrote:
> I'm struggling to add custom nameservers to /etc/resolv.conf.
> The file gets overwritten on reboot, but I can't find out where this is done.
> Any ideas?
On our cloud images, resolv.conf is managed by dhclient, which is
invoked by
On Tue, Dec 10, 2019 at 08:46:08AM +0100, Tomasz Rybak wrote:
> I remind everyone that our next meeting will take place
> this Wednesday, 2019-12-11, at 19:00 UTC.
I won't be able to make this one because of work committments. Items
I would have wanted to discuss include:
1. Still no word on
On Fri, Oct 18, 2019 at 08:35:34AM -0700, Ross Vandegrift wrote:
> On Fri, Oct 18, 2019 at 07:15:23AM +0200, Geert Stappers wrote:
> > Where to sent patches for `configure-pat.sh`?
>
> I don't know, I'm not familiar with it.
The canonical source for this script is the aws-vpc-nat package for
Hello.
On Fri, Oct 18, 2019 at 12:39:15AM +0200, Dick Visser wrote:
> I'm happily using the new Buster AMI, but I noticed that the image has
> consistent device naming enabled, so my instances have their single
> interface called "ens5".
Can you explain why this causes problems for you? We want
> Looking forward to official Buster image soon. Please let me know if I
> can be of any assistance.
Details about the official buster AMIs can be found at
https://wiki.debian.org/Cloud/AmazonEC2Image/Buster, and these AMIs are
available today.
The Marketplace listings, when they are available,
On Thu, Oct 10, 2019 at 03:02:48PM +0100, Marcin Kulisz wrote:
> > This is only email I got about this, so maybe I'm missing something
> > here. But - is this something we shold talk about during sprint next
> > week?
>
> IMO it makes sense to have a chat about it. If we want Debian to be more
>
On Tue, Oct 08, 2019 at 01:22:20PM -0400, Jonathan D. Proulx wrote:
> Do we have an attendee count for room setup, I've variously hear 13
> and 40...
The currently confirmed roster is at
https://wiki.debian.org/Sprints/2019/DebianCloud2019 and shows about 13
people. I wouldn't expect much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Debian 9.12 (stretch) AMIs for Amazon EC2 are now available. See the 9.12
release announcement at https://www.debian.org/News/2020/2020020802 and
https://wiki.debian.org/Cloud/AmazonEC2Image/Stretch for more details.
The AMIs are owned by AWS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Debian 10.3 (buster) AMIs for Amazon EC2 are now available. See the 10.3
release announcement at https://www.debian.org/News/2020/20200208 and
https://wiki.debian.org/Cloud/AmazonEC2Image/Buster for more details.
The AMIs are owned by AWS accound
Package: src:cloud-utils
Version: 0.31-1
Severity: important
The ec2metadata command queries a well-known link-local endpoint
(169.254.169.254 in Amazon EC2) to obtain information about the instance
on which it runs. Last year, AWS released "IMDSv2" in an effort to
protect customers against some
Please see https://aws.amazon.com/marketplace/pp/B0859NK4HC for details.
Enjoy, and please leave reviews and ratings on the Marketplace.
noah
On Thu, Jan 23, 2020 at 10:15:33PM +0100, Andreas Tille wrote:
> > Currently the machine has 16GB memory 200GB sdd. From current usage
> > the minimum requirement is 8GB memory (16 is certainly better since
> > it is running a UDD clone and teammetrics database) and 80GB sdd.
> >
> > Is there
On Tue, Jan 14, 2020 at 11:56:14PM +0100, Tomasz Rybak wrote:
> Till now we were having meetings on Wednesdays, 19:00UTC.
> It was morning in USA, and evening (but after work) in Europe.
> Should we keep this time, or change it?
I am fairly flexible, at the moment. Any time within about ±3 hours
On Fri, Jan 24, 2020 at 12:39:53PM +, Marcin Kulisz wrote:
> I'd say in the worst case scenario you could host it on one of the old
> accounts
> and then migrate it out to the final one if it's not ready right now.
> Hopefully you've got this automated :-)
The only reason the old account
On Fri, Jun 30, 2017 at 02:14:00PM +, Joonas Kylmälä wrote:
> We need to also take care of asking permission from the authors of
> Debian patches if they can be used under Apache v2 license.
I don't think there's anything copyrightable in any of those
contributions. Note that none of the
1 - 100 of 338 matches
Mail list logo
