Skip to main content

DST?

Its funny how many of my house appliances and cars and such just have the Daylight Savings Time hardcoded. It's going to be a pain, because not only will they not change this weekend, but they will change in a month or two. I've heard a little press about the change, but it will cause outages and issues. It will not be the non-issue that year 2000 was when it happened.

As for my company, it has been in planning at our company since August 2006, but it wasn't seriously engaged until January 2007. We've been frantic trying to get things fixed in time. We have done as much as we can, so we'll see how it affects us.

If we had better auditing, and deployment tools this would have been a lot easier to manage. I am hoping that this gives me and ammunition that I need to convince people to start taking this more seriously. We will start a larger Opsware SAS pilot once DST has passed, and we've fixed those issues which popped up.

Comments

Popular posts from this blog

Misunderstanding "Open Tracing" for the Enterprise

When first hearing of the OpenTracing project in 2016 there was excitement, finally an open standard for tracing. First, what is a trace? A trace is following a transaction from different services to build an end to end picture. The latency of each transaction segment is captured to determine which is slow, or causing performance issues. The trace may also include metadata such as metrics and logs, more on that later.
Great, so if this is open this will solve all interoperability issues we have, and allow me to use multiple APM and tracing tools at once? It will help avoid vendor or project lock-in, unlock cloud services which are opaque or invisible? Nope! Why not?
Today there are so many different implementations of tracing providing end to end transaction monitoring, and the reason why is that each project or vendor has different capabilities and use cases for the traces. Most tool users don't need to know the implementation details, but when manually instrumenting with an API, t…

F5 Persistence and my 6 week battle with support

We've been having issues with persistence on our F5's since we launched our new product. We have tried many different ways of trying to get our clients to stick on a server. Of course the first step was using a standard cookie persistence which the F5 was injecting. All of our products which use SSL is being terminated on the F5, which makes cookie work fine even for SSL traffic. After we started seeing clients going to many servers, we figured it would be safe to use a JSESSIONID cookie which is a standard Java application server cookie that is always unique per session. We implemented the following Irule (slightly modified in order to get more logging):
http://devcentral.f5.com/Default.aspx?tabid=53&view=topic&postid=1171255 (registration is free)
when HTTP_REQUEST {
# Check if there is a JSESSIONID cookie
if {[HTTP::cookie "JSESSIONID"] ne ""}{
# Persist off of the cookie value with a timeout of 2 hours (7200 seconds)
persist…

Ipmonitor, spiceworks, and vendor maintenance

I'm happy that solarwinds has released a major upgrade to ipmonitor. Too bad they didn't notify me my maintenance expired about a month ago. I'm renewing it now, and looking forward to v10. This product is excellent, cheap, and does a great job with agentless monitoring. You can also tweak it to monitor pretty much anything as needed. Such a good deal for a great all around product.
Speaking of maintenance, I also just investigated and found out that our F5 Big-IP maintenance expired in April. Glad we have a HA pair in case of issues in the next little while, but I don't understand why vendors and resellers don't keep on top of customers. It's essentially free money they aren't going to get if they don't chase folks about it.
Vendors who do a good job with maintenance:
IBM
Oracle
Sybase
HP Software
Cisco
Vendors who are horrible with maintenance in my experience:
HP hardware
Dell
F5
What cisco does that's really cool is they integrate maintenance into …