So there is not much to update on the GCE image. I wrote the GCE data
source support for cloud-init and Canonical accepted it upstream, so if
Fedora decides to use cloud-init, the support for Google Compute Engine is
Other than that, Fedora 20 images I built are working extremely well on
GCE. I am running it in production serving real traffic! :-)
It would be very nice to have Google Cloud tools packaged natively for
Fedora, those are gcutil, gcloud and gsutil. Do you know if anyone wants to
work on that or do you think GCE tools aren't necessary?
I am happy to start the work needed to unbundle those tools and start
On 3 February 2014 11:45, Vaidas Jablonskis <jablonskis(a)gmail.com> wrote:
Submitted to Canonical, will update on the progress.
On 1 February 2014 11:28, Matthew Miller <mattdm(a)fedoraproject.org> wrote:
> On Thu, Jan 30, 2014 at 10:11:41AM +0000, Vaidas Jablonskis wrote:
> > Since everybody voted up for cloud-init for initial GCE instance setup,
> > wrote cloud-init data source for GCE metadata. The only thing it does
> That is awesome! Thanks for doing this.
> > Should I assume that people will create a GCE metadata attribute called
> > 'user-data' if they want to get cloud-init to setup their instance
> > initially?
> I think this is probably a good discussion for cloud-init upstream. I
> the important thing will be consistent.
> > Which brings me to another question - should we have a specific
> > snippet for GCE and potentially for other clouds which just changes
> > cloud-init config (enables/disables cloud-init data sources) based on
> > kind of cloud image that is?
> So far, we've tried to keep the images identical no matter the target
> That has some value if we can keep it up, we can also look at targetting
> specific environments separately too if it gains us something greater than
> that value.
> Matthew Miller -- Fedora Project -- <mattdm(a)fedoraproject.org>
> cloud mailing list
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct