Etcd elasticsearch lxd #6

Closed
wants to merge 3 commits into
from

Conversation

Projects
None yet
3 participants
Contributor

mbruzek commented May 12, 2016

The etctd, elasticsearch charms needed to be updated to the latest revision number.

Also documented the LXD limitation.

README.md
- - Killing the the Kubernetes leader will result in loss of cluster PKI.
- - No easy way to address the pods from the outside world
- - ZFS does not work on trusty (a bug that will be fixed soon) yet.
+ - This bundle is not supported on LXD because Juju needs to use a LXD profile
@cmars

cmars May 12, 2016

Contributor

Thanks, this looks good.

README.md
+infrastructure (PKI).
+ - No easy way to address the pods from the outside world.
+ - The storage feature with ZFS does not work with trusty at this time because
+the code has to be enhanced to load the zfs module.
@chuckbutler

chuckbutler May 12, 2016

Collaborator

clack clack clack enhance clack clack clack enhance

- constraints: "arch=amd64 cpu-cores=2 mem=4G root-disk=12G"
+ gui-x: '1200'
+ gui-y: '600'
+ constraints: arch=amd64 cpu-cores=2 mem=4G root-disk=12G
@cmars

cmars May 12, 2016

Contributor

I'm not sure about the formatting changes in this file, but if it still works, then it's fine.

@mbruzek

mbruzek May 12, 2016

Contributor

I built a tool to query the charm store to update the revno of the charms. The round trip dumps out different quotes.

@mbruzek

mbruzek May 12, 2016

Contributor

It is valid YAML, whether Juju will work with it remains to be seen.

Collaborator

chuckbutler commented May 12, 2016

+1 LGTM

Contributor

cmars commented May 12, 2016

LGTM

Collaborator

chuckbutler commented May 13, 2016

Not sure how this happened, but the branch has conflicts now 🐙

Contributor

mbruzek commented Jun 1, 2016

This branch has conflicts because of other changes landing before it. I am going to close this pull request and fix the code in another branch.

@mbruzek mbruzek closed this Jun 1, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment