we're trying to make providers easier to right, currently we use provider object-storage, but a number of low cost providers don't have it and it complicates writing a provider (ie. no all openstack installs have object storage either), obviating the need by making juju handle its own very limited need object storage needs makes things a bit simpler. most charms are fairly small minus those that bundle binaries.
-k On Mon, Oct 20, 2014 at 4:53 PM, Vasiliy Tolstov <v.tols...@selfip.ru> wrote: > 2014-10-20 21:16 GMT+04:00 Kapil Thangavelu < > kapil.thangav...@canonical.com>: > > That should be fine, the dictates here are from mongodb default > semantics, > > we've tweaked them minorly but for the most part there per upstream > > recommends. The amount of data juju uses is miniscule (1-2mb).. till juju > > 1.21 where we store charms in mongodb. > > > Hmm, why you need to store charms in mongodb =( ? > > -- > Vasiliy Tolstov, > e-mail: v.tols...@selfip.ru > jabber: v...@selfip.ru >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
