On Wed, 2008-10-08 at 12:40 -0500, Vanco Backup wrote: > Hmm - I understand your point, but at what time does a degradation of > service become and outage in the eyes of a customer trying to bring a > dozen new servers on-line? To my customer the service was out. It > wasn't a gray area. IMO the user experience should dictate what is or > is not an outage.....
Right, like right now, at this minute, RHN is effectively out for me. Running "up2date -u" or "yum update" on any of my systems mostly just times out. Sometimes it will start and then time out. This happens with a diverse set of systems on two continents using different ISP's so effectively RHN is down. I've never found RHN to be very responsive and always thought it was a little too unreliable, but in recent weeks it's been virtually unusable. While it's not that big of a deal to simply keep my own repository and run my updates from there, I don't think this is an acceptable service level since, just about the only thing I get for my money is RHN (I certainly wouldn't pay money just for the support services as, in my experience, those border on worthless). > So, perhaps the outage list does, in fact, need to be more like the > eBay link, and become a means to let users know that "things aint > right". Certainly this would help, but more critically they need to get this infrastructure fixed. It's been very flaky for several months and just seems to be getting worse and worse. If the service level doesn't improve it's unlikely I will be unable to continue to convince my employer that paying for Redhat is worth the money and we will be forced to look at other options. Later, Tom _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
