Skip to main content

Released new CMS, Wireless

A couple weeks late, but we finally launched the new CMS for our corporate site. Its good marketing is in control of the site now, but the CMS has some major issues. I’m not going to get into the details, but it doesn’t seem like the right technology for most people who want to implement a CMS. We changed our main domain, and further split the marketing site from the application, which makes my team’s lives much easier in operations. Glad to have Coradiant in place, its very handy for these kinds of moves. Also happy that we put in Omniture with this new CMS release. I would like to test Coradiant Edge and the Omniture integration at some point.

We have been putting in sonicpoints to replace the hackjob dd-wrt I tried to put into place. I really like that product, and its very nice for my home use, but its got some issues with the N radios I guess, not too sure. Anyways the sonicpoints allow us to control them from our NSA appliances from Sonicwall. Makes security and implementation easier and faster. They are also very cheap, so that’s another positive. Trying to get them rolled out fully this week. Bought some for our Geneva office too, I’m headed there in a couple weeks.

I also implemented some new Netapp monitoring and such which is also pretty cool.

I’m headed to London on Tuesday night for some vacation and to spend time with my brother and his fiancĂ©. Will be back a week from tomorrow (Monday), so you probably will not get another post for at least 10 days.
Have a good week.


Anonymous said…
Have fun in England! I love fish in a newspaper. Sustenance for the mind and body all in one neat package.

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 wi

NPM is Broken

As someone who bought and implemented NPM solutions, covered them as an analyst, and now watches the industry, one cannot help but notice that NPM(D) is broken. According to Gartner themselves, the data center is rapidly changing, the data center is going away, m aybe not as quickly as Capp states, but it’s happening. This is apparent by the massive public cloud growth posted by Amazon, Microsoft, and Google in their infrastructure businesses. This means that traditional appliance-based NPMD offerings will not work, nor will traditional ways of collecting packet data. Many of the flow offerings do not handle the new types of flows which these services generate, but most importantly they do not understand the internet, which is the most important part of assuring services in cloud hosted environments. The network itself is not just moving to overlay a-la NSX and ACI, it's moving inside of orchestrated containers, and new proxy/load balancing systems typically built off component

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): (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) p