Filed under DevOps …

Jun 06 2012
DevOps

IBM embraces the DevOps counterculture

When The Man embraces a counterculture movement like DevOps, does that mean it no longer counts as counterculture? We’re about to see because IBM is serious about DevOps, and not as some cheap way to co-opt a hippie-tech buzzword and make itself cool.  Yes, IBM, that enterprise technology vendor that in many ways epitomizes everything that the DevOps movement was set up to escape.

Until this week, I hadn’t realized just how serious IBM was about DevOps.  But on Tuesday I was fortunate to spend some time talking with IBM’s Bill Higgins.  As we talked, I started searching the web for more information on IBM’s involvement, and found it…everywhere.  Yes, there were the obligatory conference talks, but there was also smart discussion about how to pull off DevOps within traditional enterprise IT.

And a whole IBM blog devoted to the topic of DevOps.  Imagine that!

Yes, it just started.  But it’s great to see such a trusted enterprise brand do more than merely slap the DevOps label on a tired, old product line, hoping that customers won’t notice.  I’m sure IBM is doing that, too, but not Higgins and his team.  It sounds like there’s a very real, concerted effort to embrace DevOps within IBM and within its customer base.

I don’t know where this leaves the counterculture.  But I think it means DevOps is more than some passing fad.  And that maybe, just maybe, IBM is shrewdly embracing the counterculture again, just as it did with Linux and open source years ago.  That bet paid off big time for Big Blue.  I imagine its bet on DevOps will do the same.

UPDATE: Donnie Berkholz, part of Redmonk’s awesome analyst team, attended IBM’s Pulse conference earlier this year, and praised IBM for being out in front of its stodgy peers in terms of DevOps and other important trends:

IBM’s people really get it. They understand trends that are happening at the frontlines of tech today in startups and in open-source development. IBM is way out in front on enabling DevOps in big enterprises, and the teams working on DevOps inside Tivoli as well as Rational (which builds tools for developers) are outstanding. A lot of my experience with enterprises is that they’re slow-moving and often lagging trends by years, to the point where it’s nearly laughable, but in this case IBM is definitely a front-runner.

Tagged ,
May 24 2012
Big Data, Cloud, DevOps

Survey: CIOs are confused on prioritizing IT projects, and especially on how to pay for them

CIOs are an optimistic lot these days.  According to recent survey data from InformationWeek, 61 percent of those IT executives surveyed indicate that their IT budgets will remain the same or shrink.  Yet the vast majority claim that important new projects for cloud, Big Data, security, and more will come from “new money” rather than “savings.”

How does that math work?

It’s not as if the proposed projects are useful.  As shown below, CIO’s seem to have a good handle on where money should be spent:

What they lack, of course, is a grasp on reality in terms of funding all these projects, as shown here:

And while we at Nodeable don’t have the be-all, end-all answer for how to fund these projects, we can suggest one: optimize efficiency of existing resources.  This actually fits IT priorities, generally.  After all, four of the top-five projects identified are “block-and-tackle” projects that improve existing systems rather than introducing a gee-whiz new line of business system.


The difference, of course, is that one can introduce a system like Nodeable and not only bring down costs (by tuning cloud systems based on our trending data, anomalies we flag in how resources are being used, etc.), but also drive one’s business by analyzing how resources are being used at a macro level.

I can see, for example, who is most active in handling JIRA tickets.  I can see which of my developers show up most often in the GitHub activity stream.  And while I can of course track waste in my use of AWS, I can also benchmark how my company manages its storage and compute resources against how others do.

Ultimately, what needs to be done is bring IT in better alignment with business goals.  The DevOps trend does this by reducing bureaucracy, allowing developers to get work done with a minimum of overhead.  This is the crowd Nodeable hopes to enable.

Otherwise, we end up with a mismatch of resources with goals, as InformationWeek points out:

What about hybrid clouds and cloud bursting, an activity that promises to dramatically change the face of IT spending and human resourcing as we know it? Marquee names like Zynga and DreamWorks are just two pioneers that have managed to optimize their internal infrastructure spend by balancing private and public cloud. Yet only 10% of our survey respondents identify private cloud as a top priority.

Worse, the project that came in at No.12 of 12, with a whopping 2%—launching or upgrading an enterprise social networking platform—is one that has the attention of non-IT partners….We guarantee you that if we had surveyed CMOs and their direct reports instead of CIOs and their reports, social would have been near the top.

Enterprises need to figure out how to do more with less, and that “less” means getting to more productivity with “less money,” which often will necessitate less cumbersome and costly bureaucracy.  Nodeable offers one way to accomplish this, and no doubt you can think of others.  It’s only as IT becomes more agile and joined-at-the-hip with business requirements that it’s going to be a hero in 2012.

Tagged , , , , ,
May 16 2012
Cloud, DevOps

Even developers like simplicity

How is it that we can manage to follow an average of 245 friends on Facebook and 350 people on Twitter, yet we struggle to effectively manage a handful of cloud resources?  Some will argue that it’s because social information is less important and hence requires less vigilance.  We can manage more because we actually manage less.  After all, we’re unlikely to be fired if we miss our uncle’s post about how many miles he ran today, but we could if we allow the website to crash and burn.  But the problem may also derive from the user experience.

Systems management tools get a bad rap, and for good reason.  The user experience can be less than appealing.

There’s a belief – a false one, in my experience – that technical IT folks must necessarily love complex ways in which to manage their systems.  I’m sure there are über-geeks for whom complexity is an end in itself.  But they’re the exception, not the rule.

In a conversation with an IT team at a Fortune 100 company earlier this year, one of the system administrators said that he’d buy a tool that “did whatever John would do.”  John was their Nagios expert, a system that no one else on the team could decipher.  As the sysadmin lamented, however, John sometimes goes on vacation or is unavailable while he (gasp!) spends time with family, etc.  So he wanted to receive alerts on his phone when things went awry, with one button: “Do what John would do.”

He’d click that button early and often.

Nodeable isn’t yet at the point where we learn John’s behavior in given situations and make it easily replicable by others in his absence, but as an industry I suspect we’re not terribly far off from being able to approximate this.  What we can do is simplify IT management by surfacing trending issues/anomalies/etc. so that the heavy lifting of managing cloud systems is done by Nodeable, not the developer or her operations team.  It’s not exactly “what would John do?” management, but it’s a headstart on seriously reducing complexity so that IT can focus on tailoring systems to improve business, rather than performing root cause analysis.

And, no, it’s not necessarily an easier in the cloud, even though the magic of the cloud can be the hiding of infrastructure complexity.  But the real complexity is in deciphering what’s happening in real time as apps are updated, systems are tweaked, etc.  Any changes are made on a granular level, not on a “system” level, as Enstratus James Urquhart argues,

If something goes wrong with an application, developers are on the hook to fix it, change it or kill it….However, developers and engineers can only make those changes one, or a few, components at a time. Nobody can configure the “system” to work an expected way. All you can do is constantly monitor the success and effectiveness of the technologies you deploy into the cloud, and constantly tweak them to make them as useful as they can be in that environment.

For developers to be most effective, they need to spend most of their time writing and optimizing their applications, not deciphering archaic error messages, constructing search queries in Splunk to search out root problems, or other traditional IT tasks.  A good system will surface insights into trending issues in real-time, based on continuous tracking of machine data that gives clues as to whether the changes to the system are helping or hurting.

In sum, a system is powerful not only in the various features it claims to have, but also in how well it obscures the complexity behind-the-scenes to let developers focus on writing apps.  It’s not yet “what John would do,” but it’s getting close.

Tagged , , , , ,
Mar 22 2012
Cloud, DevOps

Netflix fires Operations, lets developers run the asylum – and it works

If one assumes, as Tim O’Reilly does, that the future is already here, but is unevenly distributed to the alpha geeks, then we should assume the future looks a lot more like Netflix than it does Blockbuster Video.  While I don’t think the operations role is going to go away anytime soon, at Netflix it already has.

Is this the future of IT?

In a fascinating interview with Netflix’s cloud architect, Adrian Cockcroft, it seems the answer may well be “yes.”  Netflix actually trashed the operations role, turning it back onto the developers who write its code.  The result, says Cockcroft, is much more responsible developers writing much better code:

[W]e’ve built a decoupled system where every service is capable of withstanding the failure of every service it depends on. The typical environment you have for developers is this image that they can write code that works on a perfect machine that will always work, and operations will figure out how to create this perfect machine for them. That’s the traditional dev-ops, developer versus operations contract. But then of course machines aren’t perfect and code isn’t perfect, so everything breaks and everyone complains to each other.

So we got rid of the operations piece of that and just have the developers, so you can’t depend on everybody and you have to assume that all the other developers are writing broken code that isn’t properly deployed. And when you write a REST call to them, you might get nothing back or broken code and you just have to deal with that.

By making everyone responsible for the robustness of their code, we’ve ended up training a whole building full of developers to build their code very robustly, and I think it’s because we took the crutch of having operations to fix it up for you away from them.

Most companies aren’t ready for this kind of an IT revolution.  Or so they say.  The truth is, however, that there’s a lot of “No Ops” going on at even the stodgiest of enterprises.

Indeed, in a recent Forrester survey 58 percent of the IT executives surveyed say they’re running mission-critical workloads in unmanaged public clouds, and only 36 percent of these organizations have any sort of policy in place about use of public cloud resources.  This may not be the same thing as what Netflix is doing, but the effect is somewhat the same: developers are having to manage more of their operational infrastructure.

None of which is to suggest this is Right or Good.  But it’s happening, and I suspect the net result will be enterprise IT coming to look a lot more like Netflix over the years, and less like the good ol’ days of buying from and golfing with IBM.

Tagged , , , ,
Mar 12 2012
Cloud, DevOps, Monitoring

Even in Dell’s cloud, SMBs aren’t ready for an IT-free future

One of the major premises of cloud computing is that it effectively enables the IT professional to worry more about her application, and less about the underlying infrastructure.  This is true, but it’s unfortunately the theory is better than the reality.  In fact, IT jobs aren’t being eliminated by the cloud, but instead are being changed by them.  This is as true for the SMB market as it is within the Enterprise market.

Hence, while software vendors may hope to deliver a suite of applications to prospective SMB buyers, they can’t overlook the need to continue to provide insight into infrastructure.

Dell, long the bastion of cheap hardware, is spinning up a new story around SaaS applications: integrate a suite of winning applications and sell them in an Apple App Store-like model.  It’s a compelling vision, especially in light of SMBs persistent frustration over the hassle of installing and managing software.  It turns out that this same frustration haunts SMBs in the cloud, where 49 percent complain about the bother of rolling out new applications and another 41 percent feel that integration between cloud applications is less than ideal, according to a Dell-commissioned survey of 400 SMBs.

Dell not only plans to integrate a variety of SaaS applications, including Salesforce.com, but it also plans to take care of all the cloud infrastructure for its SMB customers, both hardware and software.  This is a good move, but Dell is kidding itself if it thinks that SMBs are going to lose all interest in the underlying infrastructure of their applications.  Microsoft’s Azure was initially a fully-baked PaaS offering…only to discover that its target customers weren’t yet ready to fully embrace PaaS.  Azure morphed into IaaS and has had a more welcoming audience ever since.

In other words, the world wants technology magic, but not too much magic.

We’ve seen this at Nodeable.  Nodeable is a real-time information network for cloud systems and services.  We help users understand and improve their cloud systems and services.   Nodeable collects and analyzes the data from users’ connected systems to find the trends, correlations and causality of events that have impact on your business, and we surface those findings in an easy-to-read dashboard.

Initially we also were targeting the ability to automate fixes to problems we found, but the feedback from our beta users was overwhelming: give us insight into what our systems are doing, but don’t fix the problems.  Instead, users wanted to be able to fix problems in their chosen way, using their preferred tools.  Magic, but not too much.

Bill Odell, Dell’s senior director of SMB cloud solutions, says that “Dell is currently cooking up its own cloud-based analytics applications – something to ‘replace all those Excel sheets and macros’ that SMBs used to run themselves .”  This sounds really cool, but shouldn’t be done in isolation of the infrastructure.  Dell’s seeming attempt to focus its customers’ attention on the application is a noble one, but it should also apply its analytics to the underlying infrastructure, such that users can keep tabs on what’s happening in the systems associated with their applications, and make changes to improve inefficiencies or breakage points.

The future is cloud, but we’re not yet at a point where we trust the infrastructure to run itself (or have some third-party run it for us).  We want to stay involved with our IT, including SMBs.  The vendor that can deliver to SMBs a seamless, integrated cloud experience without the customer feeling like she has completely ceded control over her application or her infrastructure will win.

Tagged , , , , ,
Feb 28 2012
Cloud, DevOps

IT: Increasingly a matter of dollars and cents, not ones and zeroes?

Not content to juggle spreadsheets, CFOs apparently want to manage the IT department, as well.  In a new survey of over 200 UK CFOs and finance directors, 43 percent believe the CIOs role is destined to become part of their companies’ financial functions.  And while it’s not surprising that an executive might believe she can do a better job than her peers, even outside her core skillset, it’s telling that business executives increasingly see technology as part of their job.

Blame the cloud.

After all, it’s the cloud that makes IT more a matter of “Information” and less a matter of “Technology.”  A system like Zendesk is heavy on technology, of course, but its users don’t need to worry about that.  The technology is ‘hidden’ under the covers.  The same is true of Salesforce.com and a range of other systems.  Even Nodeable, a real-time information network used to monitor geeky infrastructure like AWS instances, GitHub, and JIRA, can be and increasingly is used by business-level users.

The cloud has minimized the need to futz with installing and configuring complex infrastructure, even as IT consumerization has made hitherto obscure technology easy to use.

None of which is to suggest that CFOs are well-equipped to take on the role of CIO.  Some probably are.  Many likely aren’t.  As Ewan Leith noted to me on Twitter:

But the point is that the cloud makes the CFO’s interest in running IT a plausible possibility.  And centralizing some of the IT functions within finance actually makes sense, given that the cloud makes some formerly technical solutions a matter of dollars and cents rather than ones and zeroes.

In sum, the IT landscape is changing significantly, even dramatically.  Server huggers of the enterprise world had best beware.  The CFO may not have a valid claim to your job, but the rise of DevOps suggests that there’s a class of technical user that may not care to report up to a CIO, preferring to take this burden of managing all aspects of her application.

The cloud makes it possible.

Tagged , , ,
Feb 03 2012
1 Comment
DevOps, Social

Systems made social

There’s one frustrating thing in common with most of the Business Intelligence and Operational Intelligence companies today: they’re very much BYOI.  That is, Bring Your Own Intelligence.  Tools like Tivoli or Splunk do an incredible job of indexing one’s data and making it searchable, but they don’t do much to make all of that big data small.  You still need a highly competent business analyst or developer that has mastered these programs’ arcane search queries to pull insights out of the data, and in today’s incredibly fast-paced world that’s not good enough.  It’s too slow.

It’s not their fault, however.  Such programs were born in an era when data warehousing was all the rage; when it was enough to collect, sort, and search data.  In today’s world, social is the new mantra, and “social” matters as much for machines as it does for people.  APIs can make systems social, and social systems can tell you a lot more about what’s going on in a system, and what should be happening, than brute force searching of voluminous log files ever could.

Back to the BYOI concept.  Splunk is the gold standard in systems management these days, and rightly so.  It’s a powerful product that helps users perform root cause analysis for system failures, among other things.  But to get the most from the tool, you have to be prepared to get your hands dirty.  Really dirty, as TechWorld laments:

If you want to make Splunk work, you’ve got to be ready to abandon the slick GUI and dive deep into difficult technical configuration, editing configuration files, writing regular expressions, and taking the time to understand where your data are coming from and how Splunk will see them….Overall, getting data into Splunk is much more of your typical open source experience, with a confusing maze of pointers, wikis, product tech notes and documentation, but backed up by Splunk’s technical support staff. Plan on spending more than a few moments getting started.

It’s a great tool provided you know what you’re looking for, and how to structure the query to find it.

Let’s call this the old Unix world.  Powerful so long as you’re geeky enough to master it.  Just as in servers, however, we’re seeing an emerging “Insight as a Service” market that goes beyond providing raw tools for searching huge quantities of data, and instead serves up insight based on that data.  Insight as a Service is letting hosted software take on the burden of crunching the data for you, making Big Data a game that everyone can play, and not just data scientists.

In other words, the data still needs to be parsed, but who parses it shifts from the buyer to a third-party vendor.  In the cloud world, that vendor is not only going to be able to analyze your data to look for trends within your enterprise, but can also compare it to a broader database of user data, benchmarking you against competitors and peers.

Now that is real business intelligence.  Social intelligence based on machine data.

And it becomes even more useful if the “insight tool” spans different systems.  It’s fine to have a system that tracks my AWS instances, my Puppet deployment, or whatever, but it’s even better if these disparate views can be normalized and visualized in one place, as Redmonk analyst Stephen O’Grady posits will start to happen in 2012:

The challenges of service intregration will create commercial opportunities for aggregating services which consume individual performance streams, normalize it and present customers with a consolidated single picture of their network performance.

Even in this singular view, care needs to be taken not to overwhelm the user.  In the consumer world, Facebook, more than anyone else, has been focused on this with its Highlighted Stories, moving the full news feed to the top-right corner of the screen.  Users set filters on what content they want to see, and from whom, but Facebook also analyzes data on how users interact with content and each other, and surfaces stories based on the combination of the two.

Well, the same thing can be applied to systems, highlighting the “big stories” that are happening right now in your cloud systems, whether AWS or Salesforce.com or GitHub or some custom application you wrote.

That’s what we’re doing at Nodeable.  Nodeable brings the best features of social networking and data analysis to the cloud by aggregating, normalizing and analyzing the data from systems and services.  As an initial step, Nodeable offers real-time visibility into the cloud software development lifecycle to help identify and react to system-driven trends and patterns in real-time.  Forsaking the BYOI model, Nodeable also adds intelligence to systems data, so that what you see in the data stream directly improves application development and deployment.

Nodeable is a real-time information network for cloud-based systems and services.  We make systems social.  And social is good.

Tagged , , , ,
Jan 04 2012
1 Comment
DevOps

Governing the cloud, developer-style

Governance is supposed to be The Next Big Thing for the cloud in 2012, as enterprises get serious about managing the cloud sprawl that has mushroomed as developers and others have sought to get work done by sidestepping bureaucracy.  Enterprises are trying to get out in front of the cloud train, often to no avail, because the very premise behind adoption of cloud computing cuts against enterprise efforts to control it.

That’s the whole reason DevOps has become a real phenomenon.  The cloud has given developers the ability to build and manage their own applications, without a heavy Operations infrastructure.  Or has it?  In the shift to DevOps, a developer wants to spend the majority of her time on development, not operations.  Yet the “Ops” remains a critical function.  Call it governance.  Call it whatever you want.  But whether in a free-flowing enterprise or a stodgy old-school enterprise, there still needs to be a level of operational oversight.

Adam Strichman, president of Sanda Partners, suggests that 2012 will be the year “Companies will begin to publish firm policies on what can be cloud, who has to review cloud services, what data can go into a cloud service, and who has to be involved in [cloud] decisions.”  He’s probably right.  But in this rush to govern the cloud, enterprises may well end up crushing the very thing the cloud affords them: developer flexibility and (often) predictable, lower costs.

So how to achieve both?  How to give developers flexibility without letting their cloud systems become unwieldy?

One way is to give them management and monitoring tools that fit their existing mindset and workflow.  Something like Twitter, which has proven so adept at managing one-to-many relationships.  Traditional IT management tools are not very good with this, because they don’t know how to visualize this one-to-many sort of relationship.  Nodeable is an example of a company that has built a DevOps-friendly monitoring and management service that allows developers to focus on development while delivering operations management for disparate cloud services in one, easy-to-follow Twitter-like UI.

Even as the enterprise seeks a “standard set of management APIs for SaaS, PaaS and Iaas,” developers deploying to AWS or other cloud infrastructure also need a common way to manage disparate services in one place.  Bonus points will be given for tools that learn from the “data exhaust” these systems create, and coach the developer on how to fix an issue, based on what has worked for others in similar circumstances.

Systems management in the cloud, in other words, is a Big Data problem, and one that needs to be simple and intuitive for a developer to use, so that she can focus on her application, and not all the operational complexity that goes with it.

This is what we’re doing at Nodeable.  You should sign up for our private beta and tell us how we’re doing.

Tagged ,
Dec 20 2011
DevOps

The Stars Align for Cloud Intelligence

It’s not surprising that cloud computing is grabbing money out of budgets formerly allocated to hardware and virtualization. After all, at a certain point, it becomes more cost effective to let someone else build efficient data centers. Few can out-datacenter Amazon.

But what is perhaps surprising is where the cloud dollars will go in 2012: mobility and infrastructure support, according to a new survey of medium-size and large enterprise CIOs published by CIO Insight.

Not that hardware vendors are going out of business in 2012. Thanks to heavy spending by the cloud vendors, as detailed by Morgan Stanley Research (warning: PDF), server vendors will continue to make money, albeit on a much more modest growth curve. Red Hat, too, as the arms dealer to many of these cloud vendors, will also continue to thrive. At any rate, as with government expenditures, few ever really cut spending. They simply grow it more slowly, allocating budget savings in one area to another, increasing spending all the while, year-over-year.

Mobility is a no-brainer. App development is CIO Insight‘s fastest growing budget area, as enterprises seek to embrace the consumer smartphone trend to deliver functionality in app-like form.

IT infrastructure operations software, however, is perhaps less obvious, because it’s less visible. But in a world where enterprises risk losing control of their IT as it’s distributed across public and private clouds, as well as internal and external data centers, it’s perhaps even more critical to business success. The cloud, after all, is collecting data from, crunching data for, and serving data to mobile devices.

Which is why business intelligence remains a hugely important budget item, as the report points out:

{B]usiness intelligence…has become one of the most popular areas of IT investment. Nearly nine in 10 organizations are budgeting BI for 2012. The rise in investment should astound anyone: More organizations will spend on BI in 2012 than on any other kind of application. By comparison, 84 percent are budgeting for traditional desktop productivity applications, 83 percent for project management and an equal number for collaboration solutions, and 82 percent for human resources apps. Across all 75 budget areas, BI will be the seventh most common in 2012.

As the cloud becomes more important to delivering business value, I suspect we’ll see a similar rise in what we at Nodeable call “systems intelligence.” Think of it as business intelligence for your cloud systems, be they Amazon Web Services (AWS), GitHub, JIRA, or even Nagios, Puppet, or…you name it. If it has an API, it can be monitored and managed, and increasingly will, whether or not one would normally term it a “cloud” system.

And the reason for systems intelligence is roughly the same as business intelligence: BI exists to make sense of all the disparate business data that can help a CEO streamline her business.  Systems intelligence exists to make sense of all the disparate systems data that can help a CTO/CIO streamline her IT operations.

If the CIO’s paramount job responsibility in 2012 is delivering operational efficiency, then it follows we must become much more adept at tracking and influencing the systems that have the potential to deliver such efficiency. My app is down: is it AWS’ fault? Bad code committed to GitHub? Some combination of the two? Which of my developers is the most productive? Who on my DevOps team is closing the most JIRA tickets? Etc.

All of these questions are easily answered by our systems, if we know how to ask. And how they interact with each other is also easy to find out…if you’ve put a heck of a lot of effort into getting the right data from the APIs, as Nodeable does.

CIOs are investing heavily in the cloud to get to greater levels of operational efficiency, but they’ll never get there without also investing in systems intelligence tools that understand the cloud. Tools like Boundary, or Nodeable, or other new-school systems management tools.

Tagged , ,
Dec 16 2011
DevOps

A SETI for cloud systems data

Rackspace just put its Cloudkick investment to good use, announcing its cloud monitoring private beta.  We’re big fans of Rackspace, and have long liked the Cloudkick monitoring tools.  Heck, I’m even quoted on the Cloudkick webpage for saying it “democratizes the cloud.”  The problem, however, is that such tools don’t go nearly far enough.  In an API-driven world, monitoring silo’d systems is just a baseline.  It’s table stakes.

Systems increasingly talk to each other, or can.  But traditional monitoring tools, along with the broader category of systems management, have a hard time making sense of the intersection of systems through APIs, not to mention simply making intelligent inferences from single-system data.  Did my app break because of my GitHub commit or is something awry with Amazon?  Or perhaps both?

More pertinently to Rackspace’s new monitoring tools, from the documentation it seems the developer must still program the monitoring tool to get it to send you alerts. This places all the burden on the user to input all of the logic, rather than allowing the system to analyze the systems’ data streams and move beyond mere monitoring to systems intelligence (sort of like business intelligence, but for cloud infrastructure).

Monitoring and management is a big data problem to solve.  But as much as Hadoop and other big data tools are being put to use in other areas, no one seems to be using them within the systems management context.  This is a problem.

The DevOps professional shouldn’t have to spend time setting up their tools.  The tools should enable them to spend the vast majority of their time doing their real job: developing their applications.

None of which is intended to disparage Rackspace or the many systems management companies out there that can’t do this.  Even the most impressive of the new breed of management tools, like Splunk, leave users in silos and fail to connect the dots between the different servers or systems being managed.  Such systems leave the heavy lifting to the users, which is why entire teams of Operations professionals are required to make sense of logs and such.

But in a DevOps world fixated on getting things done — right now — this won’t do.  Better tooling is required.  This is why Nodeable was born, and why we’re upending the traditional systems management market.  If you’d like to get a taste for yourself, please sign up for our private beta.  We have some big names trying the system now.  We’d love to add you, too.

Tagged
← Older posts
Follow

Get every new post delivered to your Inbox.

Join 52 other followers

%d bloggers like this: