Skip to main content

Sorry for lack of updates, lots of stuff

Have been in Geneva for the last 3 weeks now. Been busy over here getting things in order and making sure we are ready for a major product launch over here. I am also working on some staffing and support issues for here in Europe.

Our CEO was just on CNBC, and he did an awesome job, yay Mitch!
http://www.cnbc.com/id/15840232?video=1169688483&play=1

Upgraded our Vcenter servers up to Vsphere 4. The upgrade of the servers themselves went well, but I tried to do a hypervisor upgrade, which failed. I have a case open with Vmware on the upgrade. I'm also have some strange connectivity issue on one of my physical systems. The new product is very cool, the new alarming system is a much needed improvement. Overall very happy with it so far. I am looking forward to testing the performance with the new hypervisor.

Some cool stuff my team has done. Integrated all of our linux boxes with winbind to AD. Its much easier to admin them and control access now, very good stuff. We can give developers granular access to QA and Dev systems now.

We are also building a syslog infrastructure which is similar to the one I built in my previous company. Essentially its a syslog-ng frontend to splunk, where we can forward and log streams as needed. The cool thing is that my sharp engineers at work are figuring it out on their own and learning new stuff in the process. This is the kind of thing that makes doing infrastructure and systems cool.

Working with Microsoft on a spooler issue thats been annoying, printers are so fussy.

We closed a deal with HP to get a bunch of new software. My team will be working on implementing some new technologies to add onto our existing HP investments. We currently use HP Performance Center, HP Quality Center, and HP Quicktest Pro. We added more users into Performance Center. We also puchased HP Real User Monitor (RUM, which requires BAC... I thought I got away from BAC at my last gig). We also will be implementing HP Diagnostics for Java, which should be a very useful tool for us leading up to our new product release.

That should do it for now :)

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…

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, maybe 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 components or …