[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Building GCE images with bootstrap-vz

2014-02-19 21:55 GMT+01:00 Tomasz Rybak <tomasz.rybak@post.pl>:
Sorry everyone - I'll resume  working on bootstrap-vz
and provide some details on work on GCE next week.
Now I need to fix my packages and try to catch up
with non-computer-related world ;-)

Hi Tomasz,
I had a look at the code and have a few remarks:

You update some fs partition file, adding:


I just wonder about the reason of such a sleep.

In the gce manifest, you add some packages:

"google-compute-daemon, google-startup-scripts, python-gcimagebundle..."

Specific gce required packages could be added  in gce provider tasks instead of asking user to add those in manifest. As those packages are required, it would be best to automatically add them within the provider.

Example: providers/kvm/tasks/packages.py, in DefaultPackages task: 

Could do the same for gce required packages.
Best, of course, would be to get those packages directly in Debian instead of using Google mirror.

Regarding NTP setup, it would be fine to use a plugin that sets NTP instead of specific code (could be useful for different providers I think).

This task downloads files from a remote location (at Google). Should not the gsutil code source provided within bootstrap-vz waiting for an official Debian package ?
With a download at each image creation, we do not know the version of gsutil downloaded files nor, in case of remote modifications, if image remains "stable" across builds.


Best regards.

Tomasz Rybak  GPG/PGP key ID: 2AD5 9860
Fingerprint A481 824E 7DD3 9C0E C40A  488E C654 FB33 2AD5 9860

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438  

Reply to: