Re: Releasing Buster for AWS

[Stephen Gelman]

On Sep 18, 2019, at 10:25 PM, Noah Meyerhans  wrote:
> 
> 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 happen.  What are the current blockers for getting an AMI 
>> released?  Anything I can do to help?
>> 
> 
> It was released several days ago.
> https://wiki.debian.org/Cloud/AmazonEC2Image/Buster 
> 

Oh wow!  I looked and didn’t see it… This should probably be updated:

https://wiki.debian.org/Cloud/AmazonEC2Image 


Thanks so much for pointing me in the right direction!

Stephen

Re: Releasing Buster for AWS

[Noah Meyerhans]

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 happen.  What are the current blockers for getting an AMI 
> released?  Anything I can do to help?
> 

It was released several days ago.
https://wiki.debian.org/Cloud/AmazonEC2Image/Buster

Re: Releasing Buster for AWS

[Stephen Gelman]

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 happen.  What are the current blockers for getting an AMI 
released?  Anything I can do to help?

Stephen

Bug#940587: cloud.debian.org: additional Vagrant boxes with puppet/ansible pre-installed?

[Geert Stappers]

On Wed, Sep 18:
> On 2019-09-18 1:36 a.m., Geert Stappers wrote:
> > On Tue, Sep 17, 2019 at 10:52:54AM -0400, Gabriel Filion wrote:
> >> vagrant boxes images that would have puppet/ansible pre-installed
> > There is https://cloudinit.readthedocs.io/en/latest/
> > But it lacks what it makes it tick.
> > 
> > Nowhere is documented
> > * how it starts (what triggers the start)
> > * how "client" finds "server"
> > * why "client" trusts "server"
> 
} I don't quite understand how this is related to building Vagrant boxes.

It isn't indeed.  Now the uncensored version:

|It feels wrong to put specific orchestartion components in all images
|when one knowns there is a generic component (cloudinit) that solves
|the problem. Sadly is cloudinit poorly documented.
|So now to choose from two problems.
|My choice would be going for understanding "cloudinit"


Good luck with your approach.


Regards
Geert Stappers


signature.asc
Description: PGP signature

Bug#940587: cloud.debian.org: additional Vagrant boxes with puppet/ansible pre-installed?

[Gabriel Filion]

Hi,

On 2019-09-18 1:36 a.m., Geert Stappers wrote:
> On Tue, Sep 17, 2019 at 10:52:54AM -0400, Gabriel Filion wrote:
>> I was wondering if folks maintaining the vagrant boxes would be willing to
>> publish additional images that would have puppet/ansible pre-installed with
>> the debian packages from each release's package repository?
> 
> I also don't understand how cloudinit works.
> 
> There is https://cloudinit.readthedocs.io/en/latest/
> But it lacks what it makes it tick.
> 
> Nowhere is documented
> * how it starts (what triggers the start)
> * how "client" finds "server"
> * why "client" trusts "server"

I don't quite understand how this question is related to building
Vagrant boxes.

According to the documentation[0] the boxes are generated using a Packer
template, and cloudinit is mentioned nowhere on that wiki page.

[0]: https://wiki.debian.org/Teams/Cloud/VagrantBaseBoxes#Build_process



signature.asc
Description: OpenPGP digital signature