<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 22, 2015 at 9:05 AM, Scott McBrien <span dir="ltr"><<a href="mailto:smcbrien@gmail.com" target="_blank">smcbrien@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Look, a satellite subscription, like RHEL, is for any version. You could install Satellite 5 and have a much smoother install experience, user experience, and copious, well written and updated documentation. In fact, Red Hat just released another dot update to satellite 5. However, you chose the new hotness, and with that choice comes all the stuff you're complaining about.</div></blockquote><div><br></div><div>My in production version _is_ 5.x. And you're right, the license is for any version of the product. But it's not for infinite instances. There is a 1-year transition license, and it's a helluva lot easier to start such a thing at the beginning of the year instead of the middle (i.e. I know I need to be transitioned by January of next year without having to consult a calendar). </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div></div><div>Red Hat is not alone in this. The more people you put your stuff in front of, the more flaws are exposed in the product. That's how the software industry functions. The days of developers locking themselves in a room and coming out years later with a super polished product with lovely documentation are over. Release early, release often is a mantra I hear all the time, and it means that if you want the bleeding edge, often you're the one doing the bleeding.</div></blockquote><div><br></div><div>We seem to have a fundamental disagreement on what the expected quality of _paid for_, *release ready*, software should be. If I were installing all of the upstream components to cobble together a "free" version of Satellite, then I'd expect the issues I'm running into. But when I'm using the non-free version I expect _very_ different experience. That's what is being paid for -- Red Hat to make all the stuff work via their installer and documentation.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br></div><div>I hate to say it, but if you expect a great experience from a new (marketing speak for immature) product, you're going to live a life of constant frustration and disappointment.</div></blockquote><div><br></div><div>Given what I wrote above, I'm not going to accept this lame shirk of responsibility.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br></div><div>.1 will be a significant improvement and .2 will look a lot more like your expectations.</div></blockquote><div><br></div><div>Good. I look forward to it. But that doesn't change the fact that I think the current "release" version wasn't ready to begin with.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br></div><div>As for docs, I don't know what's going on over there. Hell, if you look at the admin guide for RHEL 7, the flagship product, the section on iscsi still talks about configuring tgtd, which doesn't ship with RHEL 7...</div><span class="HOEnZb"><font color="#888888"><br></font></span></blockquote><div><br></div><div>At least we agree on something. Try finding the documentation for persistent IP address aliasing in the RHEL 7 docs. </div></div><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>James Sumners<br><a href="http://james.sumners.info/" target="_blank">http://james.sumners.info/</a> (technical profile)</div><div><a href="http://jrfom.com/" target="_blank">http://jrfom.com/</a> (personal site)</div><div><a href="http://haplo.bandcamp.com/" target="_blank">http://haplo.bandcamp.com/</a> (band page)</div></div></div></div></div>
</div></div>