It does and I have been digging through it. And thanks for the IP explanation
.. thought I was going crazy .. well more crazy ☺
What I was looking for was like I was using in RDO Openstack using Packstack
where I could export the settings to a file then adjust the file as needed and
To give an update on this, and it can be helpful to someone interested in:
Verified.
1. create a vanilla `trusty` LXD container named `gold`
2. ssh into `gold` container, `apt install python python-dev...`
3. in terminal, `$ lxc snapshot gold`, this created a snapshot, can be
viewed from `$
On Tue, Sep 5, 2017 at 1:03 PM Raghurama Bhat wrote:
> Hi Rick,
>
>
>
> My question was more generic in the sense, How do I build self healing to
> the system where I can replace broken machines. In the scenario that you
> describe below, will the remaining workers be
Hi Micheal,
1. The topology of the cluster is encoded as yaml in the bundle itself,
e.g.
https://api.jujucharms.com/charmstore/v5/~containers/bundle/canonical-kubernetes/archive/bundle.yaml
2. The yaml for the objects deployed in your cluster are typically kept in
your own source control repo.
3.
Hi Micheal,
You don't get the external IP automatically because the k8s cloud-provider
flag is not automatically set to vsphere for you (yet).
When you deploy to AWS with conjure-up, we set the k8s cloud-provider for
you so that you can use AWS features like ELBs and EBS. We intend to add
this