Skip to main content

Datacenter automation status

Over the last week, I have been testing the CA Server management and CMDB product, as well as Bladelogic. Both products are good, but have their downsides. I am evaluating 4 products, and narrowing it down to 2 in order to deploy on a real QA/staging environment. The criteria we are testing on are as follows, each has a weight as well. More later:

Requirement Sub-Feature
Network Option
Track network device configuration
Create policy for configuration standards
CMDB
Visualize relationships between servers
Visualize relationships between server and network
Track dependencies of servers and websites
Software Deployment
Support for MSI, RPM, and Sun Packages
GUI for creating Packages
Search and replace
Reverse engineer files into packages
Rollback
Notifications via SNMP and SMTP
Download patches, deploy, and rollback patches
Create a policy of patches
Hardware asset collection
Collect data via DMI
Collect detailed information
Software asset collection
Collect software revision and install details
Collect how often and for how long software is used
Reporting capability
Export to PDF,XLS
Report on compliance, changes, and activity
Open database with views that make it easy to query
Multiple Datacenter capability
Ability to have proxies in datacenters/envs
Ability to have decentralized control over envs
PXE deployment
Provision OS and policy in one job
Monitor and track configuration/policy
Create policy off Live including patches and settings
Track compliance to the policy
Enforce the policy
Track changes made outside the product
Prevent the execution of a specific exe or file
Manage users and services
Manage local users across servers
Replicate credentials to other servers
Manage services in real-time
Verify status of services in real-time across servers
Verify services port usage
Usability
How easy is the product to administrate
How easy is the product to use
How easy is the product to configure and setup

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 …