[Python-apps-team] Bug#725384: [PATCH] DataSourceGCE.py an implementation of a cloud-init DataSource for Google Compute Engine

[Brendan Burns]

On Tue, Oct 8, 2013 at 12:17 PM, Brendan Burns <bburns at google.com> wrote:

> On Tue, Oct 8, 2013 at 7:54 AM, Thomas Goirand <zigo at debian.org> wrote:
>
>> On 10/08/2013 04:02 AM, Brendan Burns wrote:
>> > Hey Thomas,
>> > We're currently discussing how this code might be submitted upstream,
>> > the discussions might take a while.
>> >
>> > In the mean time, is there a way we can get this submitted as a Debian
>> > patch so that our users can start to take advantage of it?
>> >
>> > Many thanks!
>> > --brendan
>>
>> Hi Brendan,
>>
>> Please don't top-post:
>> A: Because it messes up the order in which people normally read text.
>> Q: Why is top-posting such a bad thing?
>> A: Top-posting.
>> Q: What is the most annoying thing in e-mail?
>>
>> :)
>>
>> I agree to add your DataSourceGCE.py into the Debian cloud-init package,
>> however, you might know that there's a debconf system to configure which
>> data source to activate. Currently, we can select:
>>
>> NoCloud, AltCloud, CloudStack, ConfigDrive, Ec2, MAAS, OVF, None
>>
>> Which is it going to be for Google Cloud? Will it work to just put that
>> in the /etc/cloud/cloud.cfg.d/90_dpkg.cfg file?
>>
>> Please let me know so I can work it out in the cloud-init package.
>>
>> Cheers,
>>
>> Thomas Goirand (zigo)
>>
>>
> Hey Thomas,
> Sorry for top-posting, that's the gmail default, and I forgot to change
> it...
>
> The appropriate choice should be 'GCE'  (in general is the <Foo> in
> DataSourceFoo.py)
>
> Thanks again for your help!
> --brendan
>
>
>
And yes, it should be sufficient to just put it in the data source list in
the 90_pkg.cfg file.

Thanks again.
--brendan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/python-apps-team/attachments/20131008/150daad7/attachment.html>