I've already used conjure-up for canonical-kubernetes and it DID install
everything without the errors of the non conjure-up method.

thanks Adam.... btw  Happy New Year !

brian


On Sun, Jan 1, 2017 at 2:32 PM, Adam Stokes <adam.sto...@canonical.com>
wrote:

> Hey Brian
>
> You'll want to use conjure-up for the localhost (LXD) as we provide some
> alterations to the lxc profile that houses those charms.
>
> On Sun, Jan 1, 2017, 2:26 PM brian mullan <bmullan.m...@gmail.com> wrote:
>
>> Environment:
>>
>> ubuntu 16.04 server VM (in kvm)
>>
>> 50GB disk
>> 8 GB ram
>> 4 cpu core
>>
>> I followed the instructions at:  https://jujucharms.com/
>> canonical-kubernetes/
>> but I will retry with the conjure-up kubernetes method as well...
>>
>> which resulted in the following "juju status (note errors w/Flannel):
>>
>> Model    Controller  Cloud/Region         Version
>> default  lxd-test    localhost/localhost  2.0.2
>>
>> App                    Version  Status   Scale  Charm
>> Store       Rev  OS      Notes
>> easyrsa                3.0.1    active       1  easyrsa
>> jujucharms    5  ubuntu
>> etcd                   2.2.5    active       3  etcd
>> jujucharms   21  ubuntu
>> *flannel                0.6.1    error  *      4  flannel
>> jujucharms    7  ubuntu
>> kubeapi-load-balancer  1.10.0   active       1  kubeapi-load-balancer
>> jujucharms    5  ubuntu  exposed
>> kubernetes-master      1.5.1    active       1  kubernetes-master
>> jujucharms   10  ubuntu
>> kubernetes-worker      1.5.1    waiting      3  kubernetes-worker
>> jujucharms   12  ubuntu  exposed
>>
>> Unit                      Workload  Agent  Machine  Public address
>> Ports     Message
>> easyrsa/0*                active    idle   0
>> 10.158.189.254            Certificate Authority connected.
>> etcd/0*                   active    idle   1        10.158.189.107
>> 2379/tcp  Healthy with 3 known peers.
>> etcd/1                    active    idle   2        10.158.189.42
>> 2379/tcp  Healthy with 3 known peers.
>> etcd/2                    active    idle   3        10.158.189.223
>> 2379/tcp  Healthy with 3 known peers.
>> kubeapi-load-balancer/0*  active    idle   4        10.158.189.99
>> 443/tcp   Loadbalancer ready.
>> kubernetes-master/0*      active    idle   5        10.158.189.105
>> 6443/tcp  Kubernetes master services ready.
>>  * flannel/0*              error     idle
>> 10.158.189.105            hook failed: "cni-relation-changed" for
>> flannel:cni*
>> kubernetes-worker/0       waiting   idle   6
>> 10.158.189.132            Waiting for kubelet to start.
>>  * flannel/2               error     idle
>> 10.158.189.132            hook failed: "etcd-relation-joined" for
>> flannel:etcd*
>> kubernetes-worker/1*      waiting   idle   7
>> 10.158.189.37             Waiting for kubelet to start.
>>  * flannel/1               error     idle
>> 10.158.189.37             hook failed: "etcd-relation-joined" for
>> flannel:etcd*
>> kubernetes-worker/2       waiting   idle   8
>> 10.158.189.176            Waiting for kubelet to start.
>>  * flannel/3               error     idle
>> 10.158.189.176            hook failed: "cni-relation-changed" for
>> flannel:cni*
>>
>>
>>
>> --
>> 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

Reply via email to