Remove Solaris support in ATS

[bryancall]

[postwait]

We run ATS on Illumos (which is the Solaris support).

However, given the leak adoption of this, I'd just -0 this instead of a -1.

If there is positive support for this, I am supportive.

[zwoop]

The problem is that we have no ways to test / build anything on Solaris, at least not right now. If someone is willing to setup a build system for Solaris (and manage it), that the Jenkins CI can "ssh" to, that would help. In addition, we would need someone who's interested / willing to help out if / when we get build issues on the Solaris platform. If we can resolve those two issues, we can revisit.

[bryancall]

@postwait Are you willing to run a build system for Solaris and manage it? Also, fixing any issues that come up?

[postwait]

Manage yes, I don't have the resources to run it. If it's an AWS node I can admin it.

[zwoop]

We currently only have resources on RackSpace, which afaik, has no way of deploying Solaris. At least not last time we looked. That much said, we've already maxed out our spend on the RackSpace donation, and would have to sacrifice other builds (linux / FreeBSD) for dedicated Solaris build systems.

What we would need too is 3x dual core systems at a minimum, same as we allocated for the FreeBSD builds on RackSpace. Anything less than that and the CI falls behind, since we would want this to build on the Github PRs IMO.

Unless we can get such resources somehow (maybe AWS or ASF can donate?), I don't see how we could continue to support this platform.

[postwait]

I completely agree with that assessment.

[bryancall]

We should push this off until ATS 10 and if there hasn't been any progress on setting up CI with Solaris then we should remove the code.

[bryancall]

I have been talking to Leif more about this. I am OK with saying we don't support Solaris for ATS 9, since it is not working anyway and then remove the code for ATS 10.

[postwait]

I am also supportive of this. Drop the baggage.