Hi Matt and Michael,
That was the 'problem'. I now can deploy my test ownCloud unit, with (alpha)
Ceph support.
My additions for Ceph is quite basic and needs some additional testing before I
commit a new 'build'
I hope to do so coming week
Xander
Sent from my iPhone
On 16 mei 2014, at 17:18, Matt Bruzek matthew.bru...@canonical.com wrote:
Xander,
Michael is correct the charm name is based on the name in the metadata.yaml
file not the directory. So watch out for that.
Are you working on adding support for ceph in the current owncloud charm? If
so please work with José Antonio Rey j...@ubuntu.com
I am reviewing the owncloud charm right now:
https://code.launchpad.net/~jose/charms/precise/owncloud/port-change+repo+ssl-support/+merge/215527
Thank you,
- Matt Bruzek matthew.bru...@canonical.com
On Fri, May 16, 2014 at 4:24 AM, Michael Nelson
michael.nel...@canonical.com wrote:
On Fri, May 16, 2014 at 11:15 AM, Xander Maas xjm...@gmail.com wrote:
Hi all,
I am trying to create an ownCloud charm with Ceph support. (I already had
a more or less working dev version)
When I try to deploy my latest revision, juju doesn’t seem to get the
latest (local) revision. I noticed this, as I had a typo in my config.yaml
It may not be the same reason, but I have seen this when I've got
multiple copies of the same charm in my local JUJU_REPOSITORY, ie.
something like:
~/myrepo/precise/my-charm
and
~/myrepo/precise/an-older-charm-version
juju uses the first charm which matches name in the metadata, so you
want to move any old charm versions out of your juju repo.
Another reason can be that the version of the charm that your
bootstrap node has cached is greater than the one you're deploying,
but you shouldn't normally get into that situation.
-Michael
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
