Ok great! I looked up the source and I think it can be achieved by updating the juju/juju and the juju/utils repo. For some reason I only got the juju-local binary by installing the Go code though (I also spoofed my OS by pointing juju to a copy of the /etc/os-release from Ubuntu). However, I would only need this to make the juju client run on my primary linux OS which is currently openSUSE and I'm not sure if that is important enough to change the source code. I'm perfectly ok with using Ubuntu for the actual cluster although SLES compatibility might be interesting for other people.
Op zo 20 sep. 2015 om 12:59 schreef Mark Shuttleworth <m...@ubuntu.com>: > On 20/09/15 02:23, Andrew Wilkins wrote: > > The OS-detection code exists primarily to decide how the Juju > > servers/agents should be installed, configured, and how they should > behave > > at runtime. We should stop being so pedantic on the client side. > > Definitely, and we must already have a way around that because IIRC we > build the code for Windows and MacOS, and the server hasn't (yet :)) > been ported to those. So I would look to figure out how to instruct the > build so as to build the client only on OpenSUSE as a starting point. > Then of course patches for the server/controller (should be easy enough) > and for agents (to enable SLES charms :)) would be next. > > Mark >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju