Long term we want to have a pattern when the bundle is a directory with local charms in a directory next to the bundles.yaml file. We could not do this cleanly before the multi-series charms that are just getting out the door. I think that bundles with local charms will be suboptimal until we can get those bits to line up.
I don't think we want to be doing the file based urls, but to build a pattern that's reusable and makes sense across systems. Creating a standard pattern I think is the best path forward. On Tue, Mar 8, 2016 at 12:26 PM Martin Packman <[email protected]> wrote: > On 05/03/2016, Ian Booth <[email protected]> wrote: > >> > >> How will bundles work which reference local charms? Will this work as > >> expected where nova-compute is a directory at the same level as a bundle > >> file? > >> > >> ``` > >> series: trusty > >> services: > >> nova-compute: > >> charm: ./nova-compute > >> num_units: 2 > >> ``` > >> > > > > The above will work but not until a tweak is made to bundle deployment to > > interpret a path on disk rather than a url. It's a small change. This > would > > be done as part of the work to remove the local repo support. > > Can we keep interpreting the the reference in the bundle as a url, but > start supporting file urls? That seems neater than treating the cs: > prefix as magic not-a-filename. > > The catch is that there's no sane way of referencing locations outside > a base url. > > charm: file:nova-compute > > Works as a reference to a dir inside the base location, but: > > charm: file:../nova-compute > > Will not work as a reference to a sibling directory. And absolute file > paths are pretty useless across machines. > > Martin > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
