[Container-tools] Recommendations for bootstrapping a local k8s cluster?

[Nick Coghlan]

On 26 May 2015 at 11:37, Nick Coghlan <ncoghlan at gmail.com> wrote:
> On 26 May 2015 at 02:13, James Shubin <purpleidea at redhat.com> wrote:
>> The biggest issue the project faces, is that the Fedora packages for
>> vagrant+vagrant-libvirt don't work perfectly, so it's hard to get those
>> up and going, and they're a pre-req for OMV. One such bug:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1221006
>
> Thanks for the heads up - I don't think that's the problem I'm seeing,
> but it's definitely one to keep in mind.

I decided to continue with debugging the OMV based version, and I've
changed my mind on whether or not I'm hitting that bug.

Using the example template at
https://github.com/purpleidea/oh-my-vagrant/blob/master/examples/kubernetes-ansible.yaml,
I'm seeing the following in /etc/hosts on the created VMs:

$ cat /etc/hosts
127.0.0.1   master1 localhost localhost.localdomain localhost4
localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

## vagrant-hostmanager-start
192.168.123.100 master1
192.168.123.101 minion1
192.168.123.102 minion2
## vagrant-hostmanager-end

But on the machines themselves, eth0 is the interface the host
connects to via vagrant ssh, while eth1 doesn't have an IPv4 address
assigned at all, even though the network management scripts indicate
it should:

$ cat /etc/sysconfig/network-scripts/ifcfg-eth1
#VAGRANT-BEGIN
# The contents below are automatically generated by Vagrant. Do not modify.
NM_CONTROLLED=no
BOOTPROTO=none
ONBOOT=yes
IPADDR=192.168.123.100
NETMASK=255.255.255.0
DEVICE=eth1
PEERDNS=no
#VAGRANT-END

More details at https://bugzilla.redhat.com/show_bug.cgi?id=1221006#c13

So time to try using ansible to create the VMs as well, and seeing if
that has more success, or if it hits similar issues with the network
configuration layer.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia