What would you like to see in the virtual Charm School hangouts?

[Adam Gandelman]

On 05/26/2013 08:02 AM, Mark Canonical Ramm-Christensen wrote:
> There are multiple inter-related issues that are being discussed here:
>
> * making it easier to write charms in Ruby or PHP when those languages
> are not available in the cloud image by default.
>
> * making it easier to support charms on private clouds that block
> outgoing network access (egress filtering)
>

Just curious.. Why hasn't cloud-init been leveraged to address these two
points?  Seems it would be easy to expand potential charm metadata
(additional packages, pre-install requirements, etc) or environment
config (apt_proxy) into additional cloud-config that gets appended to
what juju already generates.  Or has it been a design decision to avoid
making support for cloud-init and metadata a provider requirement? Looks
like all but the local provider use cloud-init (though it could)

Adam