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

Nick Coghlan ncoghlan at gmail.com
Thu May 28 08:53:54 UTC 2015


On 27 May 2015 at 16:37, James Shubin <purpleidea at redhat.com> wrote:
> On Wed, 2015-05-27 at 13:43 +1000, Nick Coghlan wrote:
>> More details at
>> https://bugzilla.redhat.com/show_bug.cgi?id=1221006#c13
>
> Right, so unfortunately, OMV requires a working vagrant+vagrant-libvirt.
> As a result, OMV works *perfectly* for me, but I'm not using the Fedora
> provided packages. When I do, I get networking issues in the above bug
> you mentioned. Once those networking issues are resolved, then the new
> user experience should be awesome!

When I switched to the official Vagrant boxes for F22, the networking
issues I was seeing went away, so it looks like the problem may be
specifically in the interactions between Fedora's vagrant-libvirt and
your custom Vagrant boxes, rather than being Fedora's vagrant-libvirt
being fundamentally broken.

With that apparently resolved, I was able to move back on to the
debugging the Ansible part of the story, and there I hit a shiny new
bug with the transition to DNF, which is that Ansible can't currently
install packages on F22 unless yum-utils is installed first:
https://bugzilla.redhat.com/show_bug.cgi?id=1225762

Toshio at least worked around the upstream bug in the Ansible dnf
module (https://github.com/ansible/ansible-modules-extras/issues/471)
but that doesn't appear to have made its way into the Fedora Ansible
RPMs yet.

>From an OMV perspective, there doesn't seem to be an easy supported
way to reference *local* ansible modules in the same repo. The best
I've found is to simply check out the relevant git subtree under the
"ansible/modules" subdirectory, which works, but results in a warning
suggesting I "rm -rf" that directory.

I haven't filed a bug or RFE for this yet though, as without the
reference documentation for the YAML file format filled in, I'm not
entirely clear on what's intended behaviour and what's a bug. I was
able to muddle through by looking at the Ruby code in the Vagrantfile,
but the lack of documentation is definitely a big barrier to entry for
creating custom OMV configurations rather than just reusing one the
examples you provide.

Cheers,
Nick.

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




More information about the Container-tools mailing list