[Openstack-operators] Sharing resources across OpenStack instances
richard at raseley.com
Thu Apr 23 23:08:55 UTC 2015
Fox, Kevin M wrote:
> I haven’t tried it,
> but https://www.openstack.org/summit/openstack-paris-summit-2014/session-videos/presentation/glance-artifacts-it-and-39-s-not-just-for-images-anymore
> claims heat artifacts are working in juno. So maybe specifically heat
> resource transfer isn't needed if glance has it covered.
Very interesting, thank you for sharing. That is very much in-line with
what I had hoped for Glance.
>>> * Manilla - Users want to transfer files or folder hierarchies.
> Hmm.... So is rsync out of the question, or are you more interested
> in scheduling/managing transfers via the cloud?
I don't think rsync is out of the question in terms of the underlying
replication mechanism - it was more about the ability to schedule / manage.
>>> I think you're touching on a lot of important (and really good)
>>> ideas here, it seems like there are various plausible ways one
>>> could go about
>>> You've also touched on something that I've never really
>>> understood, which is why does Murano exist at all?
> This was brought up precisely when Murano tried to incubate. And its
> one of the reasons a lot of functionality got pushed over into Glance
> I think. I'm not really sure where Murano fits long term in the
> picture either, but I do know for sure that the app catalog system
> needs some kind of UI, and if all the rest of the Murano bits get
> pushed into the other OpenStack projects, I'm guessing that will
> still be needed. Whether the result is still called Murano, or it
> ends up just being folded into Horizon's project, that may not
> matter. The important thing is there's an app catalog.
Thank you for that additional context. I absolutely agree that the
general idea of the app catalog is an important one.
More information about the OpenStack-operators