for questions like these, submit a github issue on the project itself, since
it's not cloudstack code.
On Feb 13, 2015, at 4:23 AM, Osay Osman Yuuni <oyu...@gmail.com> wrote:
> Never mind @sebgoa. Works like snake oil
>
> On 13 February 2015 at 10:21, Osay Osman Yuuni <oyu...@gmail.com> wrote:
> Hi @sebgoa,
> Thanks for putting up the ansible-kubernetes. I'm trying it out and have hit
> an issue. I've edited k8s.yml and replaced the template with the name of my
> own template. When I try to run the playbook I get this error
>
> failed: [localhost] => {"failed": true, "parsed": false}
> /bin/sh: 1:
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python: not
> found
>
> I'm running this off an Ubuntu 14.04 VM. The template I specified is a
> coreOS (stable) template for cloudstack. Are there any prerequisites I might
> have missed?
>
> Cheers
> Osay
>
> On 12 February 2015 at 17:00, Sebastien Goasguen <run...@gmail.com> wrote:
>
> On Feb 5, 2015, at 6:07 PM, Phillip Kent <phillip.k...@xmlsoup.com> wrote:
>
> > Thanks all for this useful thread.
> >
> > I can confirm that a CoreOS template runs fine on an ESXi hypervisor
> > in CloudStack 4.3.1. The type is set to "Other (64-bit)". I didn't set
> > up the template so I don't know about relative performance with other
> > type settings.
> >
> > Regarding CoreOS, does anyone know what port(s) are required for
> > CoreOS to do auto-updating?
>
> good question. CoreOS uses the Omaha protocol for updates.
> But I am not sure what ports are being used. Might be worth asking in the
> coreOS irc channel
>
> >
> > Obviously I can set an egress rule to allow all ports but I might want
> > to be more restrictive.
> >
> > -Phillip
>
>
>
