Comment 1 for bug 1478188

Hi Anoop,

In doing our GAP analysis, we found that the Ubuntu images _almost_ just
work.

Issues:
1. The meta-data source for OPC is not fully EC2 compliant when it comes
to SSH keys. If you could add "0=opc" (or something like it) as a leaf
at http://169.254.169.254/latest/meta-data/public-keys, (i.e
http://169.254.169.254/latest/meta-data/public-keys/0=ocp), then
Cloud-init will just work.

2. The meta-data version that Cloud-init uses by default is
"2009-04-04". For compatibility's sake, if you were able to add this a
meta-data version, then Cloud-init would be 99% capable sans the first
issue.

Canonical can easily make the changes to support Cloud-init on OPC.
However, I want to highlight that given the wide adoption of Cloud-init
on other distros, if Oracle can make theses changes then not only will
you get Ubuntu, but Debian, SuSE, Gentoo, Arch, Centos, etc, etc for
free. And in terms of building out your Marketplace, it would make
working with other third-parties (like Bitnami) easier. In our
experience of working with many other clouds once Cloud-init support
lands, our cloud partners report immediate uptake and usage. .

The other big reason why making these changes to your meta-data source
would be beneficial is that it would be a migration path for users.
Users who do dev/test in house and deploy to your cloud, or users who
are on competing clouds would be able to migrate their instances into
your cloud with out modification. I can't underscore the immediate value.

Can you indicate whether these two minor changes are feasible and if so,
when might they be done?

I might add that I normally don't ask the clouds that we engage with to
change their meta-data dictionaries. In this case, I think that there is
immense value to making these minor changes.

Thanks,
Ben