Comment 10 for bug 1495978

To be able to move from local dev. environment (using LXD containers) to private cloud (e.g. for staging) to finally be able to deploy to a public cloud ( e.g. production) is one of the key benefits of using Juju for operations. What sets Juju apart from existing solutions is that you can do this in a very streamlined operation with blazing fast response and almost no extra effort from user.

Given that the majority of enterprise world uses RHEL based OS for their workloads, the current limited support of Juju with RHEL-based OSes (no LXD support, support for private cloud, support with AWS with custom simplestreams repo) creates a discontinuity in the above use-case. I find this feature/bug currently one of the most important to gain traction in enterprise without having to spend a lot of effort to port legacy applications from RHEL to Ubuntu just so that you can have a PoC with Juju.

Nevertheless, I'm pen to any suggestions/hacks from community on how to use Juju with CentOS LXD locally so I can finally demo my cloud workload (7+ different VM types, 20+ microservices) on Juju.