Skip to main content

Datacenter Automation Decisions - Rev2

As referenced by my last post, you can see this is high priority for everyone at my company. We have decided that Bladelogic can fit one area very well, but the vision, strategy, and direction of the company is not in line with our needs. Bladelogic had a stronger POC team, and better talent as well. If Opsware can do what we need for the application configuration management and deployment, then it would be the best choice for the following reasons:

  • Dependency mapping and use of the agents to do that.
    • The EMC/nlayers solution is better but not feasible for our network
    • Opsware has an excellent visual application manager which can help us troubleshoot problems and changes quickly.
  • End to end view of Network and soon Storage assets.
    • We have started a POC with the NAS product, and it can deliver very good network data to the server tool.
    • Alterpoint is next week, who Bladelogic partners with for network info in the tool. The integration is not as tight, which is understandable.
  • Scalability and resiliency.
    • Bladelogic has a lack of built in replication and agent failover. The agent and replication can be adapted using 3rd party tools.
    • Our ultimate scope is over 20,000 systems with varying uses of the tool.

We are going to deploy Opsware before a general decision is made for the company, and if the product cannot do what we need we will go with Bladelogic. Either way with our lack of centralized authentication, the major issue is going to be getting some kind of agent to deploy software on the systems. We will see how this pans out.

Needless to say Bladelogic is not happy about this decision, and rightly so. I have explained to them that this is not a final decision, but it’s a better direction due to strategy and needs of our business. Software is a mix of capabilities, direction, and the suite of offerings a single entity can offer us.

Comments

Post a Comment

Popular posts from this blog

Industry Insights: The Challenges Behind New User Interfaces

The future of computing will be bifurcated. On one hand, there will be entirely new models for computing such as voice, autonomous agents, and bots, with no traditional user interfaces. On the extreme opposite hand, there will be new user interfaces augmented with our ‘real’ worlds, such as the innovation done by Microsoft holographic computing technologies, along with virtual reality platforms coming to market from Google and Facebook. Bringing these trends to fruition, though, will require some key enabling technological limitations to be overcome. Voice It’s been slowly happening for a while now: Voice recognition will change one of the key interfaces with today’s computing and applications. Apple’s Siri, Google Now, Microsoft Cortana, and the super-hot Amazon Echo, along with their smart agents, are the practical embodiments of a growing trend toward the application of machine learning to voice and data. Andrew Ng, chief scientists at Baidu, says that 99 percent accuracy is th...
Post a Comment
Read more

Dynatrace Growth Misinformation

For my valued readers: I wanted to point out some issues I’ve recently seen in the public domain. As a Gartner analyst, I heard many claims about 200% growth, and all kind of data points which have little basis in fact. When those vendors are asked what actual numbers they are basing those growth claims on, often the questions are dodged. Dynatrace, recently used the Gartner name and brand in a press release. In Its First Year as an Independent Company, Gartner Ranks Dynatrace #1 in APM Market http://www.prweb.com/releases/2015/06/prweb12773790.htm I want to clarify the issues in their statements based on the actual Gartner facts published by Gartner in its Market Share data: Dynatrace says in their press release: “expand globally with more than three times the revenue of other new generation APM vendors” First, let’s look at how new the various technologies are: Dynatrace Data Center RUM (DCRUM) is based on the Adlex technology acquired in 2005, but was cr...
10 comments
Read more

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...
2 comments
Read more