Re: my progress

2016-11-04 Thread Thomas Lange
Hi Sam, today we've managed to produced an GCE image which was also tested with success. It boots, and we can log into this machine. We had to do some changes in the config space. Everything is now available in the examples of FAI on github. I plan to make a new FAI release in the middle of next

my progress

2016-11-04 Thread Sam Hartman
I pushed to git://git.debian.org/cloud/fai-cloud-images.git. You can use the configuration space like fai-diskimage -c DEBIAN,CLOUD,AMD64,GRUB_PC -S image_zieimage_name It's very minimal, but does appear to produce an image. The GCE class is present but I haven't tested it. Next nweek I'll base

Bug#843209: Please permit class directory-like feature for fai-diskimage

2016-11-04 Thread Sam Hartman
package: fai version: 5.2 severity: wishlist. FAI has a great feature in the class directory that allows a configuration space to infer classes from things such as the installed hardware. This is not currently available from fai-diskimage. I'd really like to have a feature like that for

Re: Hash sum mismatches

2016-11-04 Thread James Bromberger
Hm. Closest I had got was setting the Cache Control headers really low - so it was supposed to be rare. Perhaps 5 minutes on "sid" as a default is too long? The timeouts we have are: ExpiresDefault "access plus 30 minutes"

Re: FAI image creation

2016-11-04 Thread Sam Hartman
fai-cloud-images perhaps integrating Thomas's comments. I think we will have wrapper scripts, and I want the scripts and config space in one repo. I think starting from scratch is probably a good idea.

Hash sum mismatches

2016-11-04 Thread Noah Meyerhans
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

Processed: raising severity

2016-11-04 Thread Debian Bug Tracking System
Processing control commands: > severity 693945 important Bug #693945 [cloud.debian.org] Reportbug support for cloud.debian.org Ignoring request to change severity of Bug 693945 to the same value. > severity 831848 important Bug #831848 [reportbug] Reportbug support for cloud.debian.org pseudo

Processed: raising severity

2016-11-04 Thread Debian Bug Tracking System
Processing control commands: > severity 693945 important Bug #693945 [cloud.debian.org] Reportbug support for cloud.debian.org Severity set to 'important' from 'wishlist' > severity 831848 important Bug #831848 [reportbug] Reportbug support for cloud.debian.org pseudo package Severity set to

Bug#693945: raising severity

2016-11-04 Thread Noah Meyerhans
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

Processed: closing 697490

2016-11-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 697490 Bug #697490 [cloud.debian.org] cloud.debian.org: use /etc/sudoers.d. Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 697490: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697490

Bug#831302: marked as done (Vagrant box allows root login with insecure default key)

2016-11-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Nov 2016 19:13:50 +0100 with message-id <581ccfde.7020...@libera.cc> and subject line has caused the Debian Bug report #831302, regarding Vagrant box allows root login with insecure default key to be marked as done. This means that you claim that the problem has been

Processed: closing 813493

2016-11-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 813493 Bug #813493 [cloud.debian.org] cloud.debian.org: [AWS] Debian Jessie 8.1 images lack root partition grow Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 813493:

Re: Ec2: Boot time delays

2016-11-04 Thread Tim Sattarov
On 04/11/16 12:19 PM, James Bromberger wrote: > On 4/11/2016 10:28 PM, Tim Sattarov wrote: >> Just checked on one of the instances: >> dmidecode shows >> >> BIOS Information >> Vendor: Xen >> Version: 4.2.amazon >> Release Date: 05/12/2016 >> >> >> and dmesg >> [

Re: Ec2: Boot time delays

2016-11-04 Thread James Bromberger
On 4/11/2016 10:28 PM, Tim Sattarov wrote: > Just checked on one of the instances: > dmidecode shows > > BIOS Information > Vendor: Xen > Version: 4.2.amazon > Release Date: 05/12/2016 > > > and dmesg > [6.352070] xenbus_probe_frontend: Waiting for devices to

Re: Ec2: Boot time delays

2016-11-04 Thread Tim Sattarov
On 04/11/16 10:12 AM, Tim Sattarov wrote: > On 04/11/16 01:26 AM, James Bromberger wrote: >> Hello all, >> >> Some of you may recall a 30 second delay for xen_fb_frontend when >> booting Debian in EC2[1]. It appears that this is now starting to >> resolve - if you launch (or stop/start) an

Give FAI a try

2016-11-04 Thread Thomas Lange
Hi folks, if want to give FAI a try, here are some hints: - read the man page fai-diskimage(8) - create a config space for FAI by using the examples from the fai-doc package - mkdir -p /srv/fai/config - cp -a /usr/share/doc/fai-doc/examples/simple /srv/fai/config - either download a Jessie 64bit