nice, finally tower is open source.
but I’d like to do an old school installation, any chance to see this within the next weeks?
bye
We have no current plans to implement a different install target in the open source AWX repository.
Are you opposed to, as Stefan said, and “old school” installation, or just not planning on it yourself? Would you consider a PR if someone implemented it?
In a way I am a bit opposed to it, even from a PR. Having an alternate bare-metal/VM based install opens us up to maintaining and supporting that. On the Tower side we already have experience with that and it’s nearly a full time job as it is. I’m not opposed to someone else owning it, but that person absolutely has to be the one to own it.
Matt, is the code that does that build still proprietary? If it is, as you say, nearly a full time job to support this, wouldn’t it benefit you to release that code to allow the community to help with it?
And isn’t it more work to deal with three build processes (docker, kubernetes, bare metal), than one or two? I don’t quite understand why, when Tower is built one way, you would take the time to use docker to build it a different way.
Thanks,
Paul
Matt, is the code that does that build still proprietary? If it is, as you
say, nearly a full time job to support this, wouldn't it benefit you to
release that code to allow the community to help with it?
And isn't it more work to deal with three build processes (docker,
kubernetes, bare metal), than one or two? I don't quite understand why, when
Tower is built one way, you would take the time to use docker to build it a
different way.
The docker build is much simpler by design. It's a great way to
constrain weird variables, and for small deployments, it makes sense
to constrain as much as possible to limit weird failure cases.
Ensuring supportability of complex deployments is an enterprise
feature, and for good reason. That's something that's generally needed
by large organizations, and it's something they can and should pay
for. That's our business model.
As Matt said before, others are free (and encouraged!) to build and
support their own deployment mechanisms.
--g