On Thu, Apr 04, 2019 at 05:39:53PM -0400, Jimmy Kaplowitz wrote:
> Since Amazon wants the email address to correspond to SPI rather than
> Debian (i.e. if Debian were to leave SPI a new account would be needed),
Urgs, but okay.
> I was thinking of something like:
>
Package: cloud-init
Version: 18.3
Severity: wishlist
Tags: patch
Dear Maintainer,
The cloud-init system logs to the follow files:
- /var/log/cloud-init-output.log
- /var/log/cloud-init.log
There is nothing shipped which rotates these log files, which is a shame
as they'll grow everytime an
On Thu, Apr 04, 2019 at 07:51:22PM +0100, Marcin Kulisz wrote:
> On 2019-04-04 18:08:27, Bastian Blank wrote:
> > Hi Jimmy
> >
> > On Wed, Mar 20, 2019 at 02:52:23AM -0400, Jimmy Kaplowitz wrote:
> > > On Fri, Mar 15, 2019 at 05:43:59PM -0400, Chris Lamb wrote:
> > > > Let me know if this stalls;
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 2019-04-04 18:08:27, Bastian Blank wrote:
> Hi Jimmy
>
> On Wed, Mar 20, 2019 at 02:52:23AM -0400, Jimmy Kaplowitz wrote:
> > On Fri, Mar 15, 2019 at 05:43:59PM -0400, Chris Lamb wrote:
> > > Let me know if this stalls; I can put you in touch with someone on
> > > the Azure team.
>
> The
Hi Jimmy
On Wed, Mar 20, 2019 at 02:52:23AM -0400, Jimmy Kaplowitz wrote:
> On Fri, Mar 15, 2019 at 05:43:59PM -0400, Chris Lamb 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
On 4/3/19 6:42 PM, Paul Graydon wrote:
> On 4/3/19 08:29, Thomas Goirand wrote:
>> On 4/3/19 10:54 AM, Kenn Leth Hansen wrote:
>>> Hi list,
>>>
>>> I've discovered the CloudStack datasource causes cloud-init to wait
>>> for 120 seconds before continuing to the next datasource if no
>>> service is
> On 4/3/19 08:29, Thomas Goirand wrote:
>> On 4/3/19 10:54 AM, Kenn Leth Hansen wrote:
>>> Hi list,
>>>
>>> I've discovered the CloudStack datasource causes cloud-init to wait for 120
>>> seconds before continuing to the next datasource if no service is
>>> responding on port 80 on the DHCP
> > > > 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 with expectations on how the datasources have been
> > > >
