Deployment Oversight
Merlijn Sebrechts
merlijn.sebrechts at gmail.com
Sun Nov 27 00:45:03 UTC 2016
I feel you, James
We've been battling with weird issues / compatibility problems with the
manual provider on private infra for the past year. Just finding out where
the problem is requires diving deep into the internals of Juju and the
Charms. In the end, we patched our own servers heavily and had to patch
~30% of the Charms we tried. This slowed us down so much that we just gave
up and moved to MAAS. We're having a lot less problems now..
2016-11-27 0:03 GMT+01:00 James Beedy <jamesbeedy at gmail.com>:
> Was a bit flustered earlier when I sent off this email, I've looked a bit
> closer at each of the individual problems, thought I would report back with
> my findings.
>
> 1. Job for systemd-sysctl.service failed because the control process
> exited
> - This is an error I'm seeing when installing juju (not sure if this
> is adding to any other issues or not), didn't look into it much, but filed
> a bug here -> https://bugs.launchpad.net/juju/+bug/1645025
>
> 2. ERROR juju.state database.go:231 using unknown collection
> "remoteApplications"
> - This seems to only exist in 2.0.1, installed from juju/stable ppa,
> when I reverted back to 2.0.0, this went away.
>
> Charm/Layer Issues
>
> 3. Problem with Ruby: ["env: './configure': Permission denied"]
> - Both of my charms were utilizing layer-ruby. When deployed to lxd,
> and EC2, I don't seem to get this error, but deploying on this
> private/dedicated infra doesn't like python running `./configure` I feel
> (could also be permissions on /tmp, but I tried moving the upacking and
> configuring to another dir, and still got this error).
> - Filed bug here -> https://github.com/battlemidget/juju-layer-ruby/
> issues/12
> - Removing layer-ruby was my fix here, this allowed my charms to
> deploy w/o error.
>
> 4. Elasticsearch
> - Seems the es charm can't find the yaml module (possibly a python3.5
> thing)???
> - Filed bug here -> https://bugs.launchpad.net/
> charms/+source/elasticsearch/+bug/1645043
> - My workaround here, just to get the app deployed, was to deploy
> elasticsearch to a lxd container on one of my hosts. Of course this isn't
> an answer for anything more then POC, but worked to allow me to
> deploy/troubleshoot the rest of my bundle.
>
>
> Aside from the remaining elasticsearch issue, I was able to get my stack
> deployed -> http://paste.ubuntu.com/23540146/
>
> My earlier baffled and confused cry for help seems now just revolve around
> getting es to deploy.
>
> My apologies for reaching out in such a way earlier before diving into
> what was going on, hopefully we can work out whats going on with my infra
> <-> ES.
>
> Thanks
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20161127/d8d7e217/attachment.html>
More information about the Juju
mailing list