Category: Features

  • Using AI to Automate Incident Management Sparks Debate

    Using AI to Automate Incident Management Sparks Debate

    When it comes to incident response with an integrated DevOps environment so much depends on the ability of an IT team to respond quickly and consistently to a specific set of events. Because of that requirement, many IT organizations have invested in incident management systems that everyone in IT can consult whenever an issue arises. Now PagerDuty, a provider of incident management software, is taking that concept a step further by applying artificial intelligence (AI) to automate as many incident response tasks as an organization deems appropriate.

    As promising as that may sound, however, Resilient Systems, a unit of IBM that is an arch-rival to PagerDuty, contends most organizations today do not have anywhere near the level of incident management maturity to make investing in AI worth their time and effort yet.

    Eric Sigler, head of DevOps for PagerDuty, says the the latest edition of the company’s namesake incident management platform is designed to augment the capabilities of the local IT administrator by providing:

    Alert Grouping: Rules-based automation and machine learning algorithms automatically group related issues together to make it simpler to identify related issues.

    Similar Incidents: IT administrators and support specialist can see previous related issues and surface information around incident severity, impact and remediation steps.

    Response Automation: A Response Plays capability allows teams to design and execute an automated response pattern to recruiting responders and stakeholders by a single click.

    Dynamic Notifications and Event Routing: IT teams can select notification and assignment behavior and automatically route events to different teams based on event payloads.

    Sigler says PagerDuty has also redesigned the company’s user interface, creating an enhanced live incident details page that makes discovering events simpler.

    Those capabilities, says Sigler, will collectively prove to be critical in an emergency because most of the time the specialist associated with a specific IT discipline is usually not immediately available when needed. First responders to any given event need as much information as possible as their fingertips to resolve issues as quickly as possible.

    But Ted Julien, vice president of product management for Resilient Systems, says most organizations simply don’t have incident response processes in place that would benefit from that level of AI. Machine learning algorithms require access to massive amounts of incident response data to learn what to do, but most organizations don’t collect that data, much less learn from it, he says. That doesn’t mean AI doesn’t have potential. But he believes AI is not nearly as far along when it comes to incident response as anyone would like. In fact, he notes, machine learning algorithms and other forms of IT automation could just as easily wind up doing more harm than good.

    There may come a day when incident response in an IT environment is fully automated. But the distance between where most IT organizations are today and the achievement of that goal is still nothing less than considerable.

    — Mike Vizard

  • LogicMonitor Extends Reach to the Cloud

    LogicMonitor Extends Reach to the Cloud

    LogicMonitor has been making available performance monitoring tools as software-as-a-service (SaaS) applications for several years now. At the Microsoft Ignite conference this week, the company announced it is adding a module through which IT organizations can gain similar insights into public cloud computing services.

    Steve Francis, founder and chief evangelist for LogicMonitor, says LM Cloud is designed to provide real-time visibility into the performance of Amazon Web Services (AWS) and Microsoft Azure clouds, including resource performance monitoring, detailed billing analysis and cloud provider availability.

    Many IT organizations don’t realize just how different managing a public cloud is compared to an on-premises IT infrastructure environment, he says. Not only is too easy to let a workload waste resources, spiraling cloud service costs out of control, but also cloud service providers have policies that limit consumption of resources in a specific region.

    Capabilities provided by LM Cloud include automated discovery of an organization’s entire cloud environment and dashboards that can be employed to troubleshoot issues.

    Francis says that as an extension of the core LogicMonitor service, LM Cloud provides a means for IT organizations to employ one monitoring tool across what have become de facto hybrid cloud computing environments. In fact, using multiple clouds will require IT organizations to rely more on monitoring tools based in the cloud. Otherwise, Francis notes, IT organization would have to correlate data across multiple incompatible tools.

    One of the things that holds IT organizations back from using public clouds is simply that they are more familiar with their on-premises environments. Francis says tools such as LM Cloud will make it much simpler for IT administrators to explore a public cloud environment using a set of capabilities that cloud service providers are not inclined to provide.

    Thanks to the rise of public clouds, DevOps arguably has never been more complicated, with applications distributed across multiple public clouds. But it’s very difficult to manage what can’t be seen, and it’s nearly impossible to compare one public cloud with another—much less an on-premises IT environment—without access to a common baseline of metrics. All too often deciding where to deploy a workload is based on either instinct or corporate fiat rather than detailed analysis.

    While many IT organizations expect to reduce costs by moving workloads to the public cloud, the truth is more nuanced. Long-running applications tend to be less expensive to deploy on-premises. Shorter-run applications lend themselves well to public clouds. Yet, many IT organizations are simply not fast enough when it comes to deploying applications on-premises. Internal IT organizations that have embraced DevOps processes, however, are now more agile. That, coupled with software-defined infrastructure, is narrowing the dexterity gulf that exists between on-premises and cloud computing environments.

    All things may not be equal just yet. But the day when an on-premises IT environment is just another cloud that needs to be managed is that not that far off.

    — Mike Vizard

  • Automation: Where Did My Mind Go? Or, No Need to Remember

    Automation: Where Did My Mind Go? Or, No Need to Remember

    Allow me to share a secret: My handwriting is atrocious. If it were not for the keyboard upon which my fingers are tapping and the laptop that is processing the result of my taps, this article would not be happening.

    I’ve always had poor handwriting. But, it’s gotten worse over time. Other than the occasional grocery list, I don’t write things out by hand anymore. It’s just me and the keyboards on my laptop and phone. Luckily, my mind still works—sort of. The stuff I produce has gotten better. Using a computer allows me to edit faster. But, I don’t retrieve words as quickly as I used to. I find myself using online tools continually during a writing session. I could blame age for the impediment. And that may be the case. But still, a part of me says, “Why remember words when I can just grope around a thesaurus to find what I need?” That I can still spell most words correctly is a bit of miracle. But then again, a computer has been correcting my spelling for the last 25 years.

    I’ll share another secret: I don’t remember phone numbers anymore. At one time, I had all the phone numbers associated with all those close to me committed to memory. I knew the phone numbers of my sister, parents, in-laws, friends, steady customers and even my favorite restaurants. I didn’t have to look anything up online. I just carried the numbers around in my head. Now, the only numbers I have memorized are my own and my wife’s. When I want to talk to my sister, I look up her name in the contact list on my cell phone and hit the “call” button. When I am in my bluetooth-enabled car, I just say, “call sister.” The machines do the rest.

    I can still sum a short list of numbers in my head. Also, I can multiply two numbers together as long as neither number is greater than a thousand. If I want to do multiple operations—say, add some numbers up and then divide by another—I need to use a calculator. I haven’t tried to do this sort of arithmetic on paper in a long time. Maybe I can, maybe I can’t. Dunno. It’s just easier to use a calculator.

    I still read a lot. But I find that I spend more time learning things by watching videos on YouTube. In fact, I just got through brushing up on JMeter by watching a playlist of 20 videos on the topic. It took me about two days. I can’t remember the last time I spent two days completely engaged in reading a technology book. It’s embarrassing to say this, given that I am a technology writer.

    But, there is good news here: I can still make change. I learned how to do this before cash registers reported the change to give back upon purchase. You start with the sale amount and work your way through the cash drawer taking out coins and bills until you reach the amount the customer gave you. Funny that I should remember this small piece of mental acrobatics. But, then again, I haven’t used a cash register in a very long time. Making change has yet to be made simple for me.

    However, the computers I use continually throughout my day make things very simple. They allow me to write out my thoughts clearly. They tell me when to pay my bills. They correct my spelling. They make going to the grocery store a breeze. I just take want I want from the shelves, put my credit card into the card reader at the automated checkout line and pay only what is due—no cash required, no change made.

    Automation has made me really smart in a few areas and helpless in most others. I can design an elegant microservice. I am wicked good at working my way through the ins and outs of Amazon Web Services. I can create the automation code that tests my software so that Jenkins can move everything along the deployment path easily and reliably. Yet, I have no idea how to fix my car when the warning lights go off. I don’t know how to repair my cell phone when it stops working. If my voice-responsive TV no longer delivers video on demand, I’m not even sure who to call. The cable company? Netflix? Linksys? Samsung? Denon? When my microwave breaks down, I throw it out.

    My world is simple on the surface and yet terribly complex underneath.

    At one time, the complexities were more apparent. Information was not at our fingertips. Research meant hours in the library poring over the card catalog. Chemistry was part of professional photography. Acting meant memorizing a script that had to be recited over a period of hours, not minutes. Things were more difficult then. But, we sort of figured it out. We had the ability to negotiate the complexities of life. We had no choice. The machines had yet to be invented.

    Now the machines have been invented. Overall, they have been good to us. Smallpox is gone. Lasik is here. Doors open before us automatically, no pushing required. Delivery is overnight, if not same day. Should I want to run my program on a supercomputer, all I need is an AWS account bound to a credit card. Just 1 percent of the population in the United States feeds the rest of the country. We don’t lack for toilet paper.

    Technology is a wonderful thing.

    But, I can’t help but wonder what becomes of a culture when everything is automated to essential simplicity. What happens over generations when we no longer need to know how to write legibly, remember a phone number or make change? How will our minds work when the stuff that used to make our minds work goes away? I don’t know. I am still trying to figure it out. In the meantime, I’ll leave it up to you to decide.

    — Bob Reselman

  • New Relic Tracing Software Pinpoints Source of IT Issues

    New Relic Tracing Software Pinpoints Source of IT Issues

    At a FutureStack 2017 conference this week, New Relic previewed an implementation of distributed tracing software that has the potential to close the war rooms where IT operations assign blame for application failure.

    New Relic CEO Lew Cirne says a Distributed Tracing capability that New Relic previewed this week will enable developers or IT operations teams to pinpoint the precise source of any given performance issue. Rather than wasting hours on root cause analysis, Cirne says DevOps teams will now be armed with dashboard they can navigate to visually inspect what elements of a distributed computing environment are specifically affecting their applications.

    Based on the open-source Open Tracing software being advanced by the Cloud Native Computing Foundation (CNCF), Cirne says New Relic opted to embrace an open initiative that should lead to more actionable intelligence being derived from the data New Relic collects.

    At this juncture, Cirne contends that deploying an application in production that has not been instrumented borders on the criminal. He concedes, however, the preponderance of applications deployed in production environments today are not instrumented largely because the total cost of instrumenting legacy applications has been cost-prohibitive. But as IT monitoring software becomes less expensive to invoke using agents that communicate back to a software-as-a-service (SaaS) application, most new applications being deployed in the cloud are now being instrumented.

    To help further that goal, New Relic this week also announced support for .Net Core 2.0 framework recently made available on Microsoft Azure and added support for six additional Amazon Web Services (AWS) services. New Relic now supports a total of 25 AWS services.

    At the conference Cirne also showed how IT organizations can now invoke New Relic application programming interfaces (APIs) to spin up a dashboard to track specific events associated with, for example, the rollout of a new application.

    Access to the data New Relic surfaces, notes Cirne, in turn helps fuel adoption of DevOps because organizations gain confidence in their ability to more rapidly build and deploy applications. That confidence will only increase as IT organizations avail themselves of artificial intelligence (AI) software in the form of machine learning and, soon, deep learning algorithms to make more reliable decisions based on patterns in their IT environments. New Relic, he adds, is able to fuel those algorithms because the service collects 1.5 billion metrics and events every minute. That said, humans will still be required to manage the overall IT environment.

    Cirne maintains that the best way to collect all that data is to employ agents, noting New Relic is adopting those agents to make them lightweight enough to even deploy on microservices based on containers.

    New Relic naturally is not the only provider of IT monitoring tools investing heavily in advanced algorithms. In the not-too-distant future, it’s probable that algorithms deployed by different vendors will share insights with one another. In the meantime, IT administrators can take some comfort in the fact that it should soon become easier to manage IT at scale.

    — Mike Vizard

  • CloudBees Applies Analytics to DevOps

    CloudBees Applies Analytics to DevOps

    At the heart of many DevOps initiatives is an automation server based on open-source Jenkins software developed by CloudBees. At the recent Jenkins World 2017 conference, CloudBees showed that Jenkins is now becoming the foundational element through which DevOps teams can now manage a continuous integration/continuous deployment (CI/CD) process end to end.

    New additions to the portfolio include CloudBees DevOptics, an analytics application to aggregate data from software development pipelines as it moves through a Jenkins server. CloudBees CTO Kohsuke Kawaguchi says once organizations are armed with those insights they will be able to, for example, identify potential bottlenecks in their software development processes. CloudBees DevOptics creates a single point of reference on the status of any application delivery project, all the way down to individual commits, says Kawaguchi.

    CloudBees also launched CloudBees Jenkins Advisor, a free plug-in for a Jenkins environment that Kawaguchi says provides another watchful eye capable of continuously analyzing a Jenkins environment using algorithms the company developed. Cloudbess Jenkins Advisor comprises a knowledge base and diagnostic tools that can be employed to detect and resolve issues ranging from simple configuration issues to security and other forms of best practices.

    Finally, the company revamped the user interface provided with CloudBees Jenkins Enterprise, an implementation of Jenkins that comes pre-configured with built-in security and integrations with more than 1,400 DevOps tools. It also announced that a few select managed services providers are now building a practice around Cloudbees Jenkins Enterprise.

    CloudBees reports there are now more than 150,000 active installations of Jenkins worldwide that span a user community of more than a million. Those numbers represent a 50 percent growth rate from January of 2015.

    Most organizations employ DevOps processes to accelerate development of software. But along the way it’s not uncommon for many organizations to lose control over those processes as the amount of software being developed begins to overwhelm their management teams. CloudBees clearly sees providing tools to optimize DevOps processes based on Jenkins as its next big opportunity.

    In general, DevOps is much more of a journey than an event. But rather than being a simple article of faith, analytics can be used to show all the participants in a process that progress is in fact being made. Otherwise, resistance to increasing the number of application development projects being undertaken at the same time starts to mount. Whatever the reason for gathering those metrics, however, that old “Things Measured Are Things Done” maxim continues to apply. Those metrics also help IT organizations justify the return on investment in DevOps to senior managers.

    Of course, managing DevOps processes at scale is as much a cultural challenge as it is a technical issue. When many organizations first embrace DevOps there’s a lot of initial enthusiasm. But the further down the DevOps maturity curve an organization gets, the more they encounter various hurdles. Metrics collected and analyzed by the tools provided by CloudBees help organizations determine to what degree those hurdles are related to simple technical glitches versus organizational issues that are almost always a lot harder to resolve.

    — Mike Vizard

  • DevOps, Security, AI Convergence on Horizon

    DevOps, Security, AI Convergence on Horizon

    DevOps is regarded as practice that can drive performance advantages. Artificial intelligence is showing very real promise across the security market. Most public and private-sector organizations know that they must explore new and different ways of defending their networks against modern threats. These three factors make it clear that DevOps, AI and security are ripe for convergence.

    Defining AI

    Anyone reading this post doesn’t need me to explain to them what DevOps and security are; both of these categories are well-defined. However, AI is really in an emergent stage, with different types in use and many definitions floating around. Because of this, I think it is important to let readers know that in this post, AI refers to a class of technology that can:

    • Consume data, learn and get smarter on its own
    • Automatically identify and solve problems
    • Operate independently, without human supervision
    • Scale massively
    • Move at near real-time speed
    • Achieve levels of accuracy that are beyond human capabilities

    DevOps and Security are United

    DevOps and security have merged. For several years now, organizations have been leveraging automation technologies and DevOps practices to continuously deliver security and compliance policies across data centers and clouds.

    Further legitimizing the union is the fact that leading DevOps and automation players such as Puppet, Chef and Ansible have formed numerous partnerships that deliver effective security capabilities to their customers.

    There are, of course, other signs that show how successful the DevOps and security marriage has been. One of which is the emergence of the term “rugged DevOps.” It is now so widely recognized that it commands its own section on this site and is often the subject of discussion at several notable security conferences.  

    DevOps and AI are Dating

    The relationship between DevOps and AI is in the early stages, with the courtship between the two well underway. Examples of its progress are found in numerous blogs and articles, several of which include:

    DevOps and AI have certainly not yet intertwined as deeply as DevOps and security have. These examples (and others out there) do show they the two will continue to integrate beyond what we are currently witnessing.

    DevOps, Security and AI

    DevOps and security are wed. DevOps and AI are moving closer toward each other. It’s only a matter of time until all three get together.

    Because several DevOps leaders are already in the business of security, it’s logical to assume that a partnership between one of them and an AI-driven security provider will be what ultimately leads to a marketable solution.

    DevOps provider candidates with the potential to move on a partnership that can combine DevOps, security and AI have a raft of new and established security providers available to work with. Several of the startups in this class are recognized in the CB Insights AI 100 2017 infographic. Companies such as Cloudera (NYSE: CLDR), which is using AI and machine learning to solve security problems, are among the more established providers that may make for a perfect partner. 

    How quickly will the market see such a partnership? That remains to be seen. However, with DevOps now fully accepted as a methodology that can positively impact bottom lines, AI coming into its own, and the need for new and different ways of defending organizations against attacks at a critical stage, it seems almost certain that the convergence will be upon us sooner rather than later.

    — Joe Franscella

  • VMware Ties Desktop Virtualization to DevOps Productivity

    VMware Ties Desktop Virtualization to DevOps Productivity

    It’s no secret that when it comes to building applications, many developers prefer to use the Apple Macintosh. However, that preference can create multiple DevOps challenges. VMware is moving to reduce the friction with the release of VMware Fusion Pro 10, a desktop virtualization offering for Apple Macs that now supports REST application programming interfaces (APIs) to more easily programmatically invoke virtual machines on Macs.

    In addition, VMware has significantly improved support for graphical processors units (GPUs) and 3D graphics within VMware Fusion Pro 10 that are now more commonly being invoked by developers.

    At the same time, VMware is also updating VMware Workstation 14 and Workstation Player, which adds support for Windows 10 and Windows Server 2016 along with updated Linux support for Fedora 26 and Ubuntu 17.04 guest operating systems to the desktop virtualization software. Workstation Player is a subset of VMware Workstation 14 that IT organizations can employ to limit the size of a virtual machine running on a local workstation.

    Other new capabilities include support for Microsoft’s Virtualization Based Security (VBS) features of Windows 10 Enterprise and Windows Server 2016 guests, enhanced virtual networking and new support and controls for working with vSphere and the vCenter Server Appliance software.

    Michael Roy, product line marketing manager for VMware Fusion, says more organizations are making GPUs available to developers as part of an effort to build more robust applications. Support for GPUs make it easier for developers to build compute-intensive applications for multiple operating system environments within the context of a DevOps environment managed by an IT organization, he notes.

    Other new capabilities include a revamped user interface and support for the Apple Touch Bar to simplify moving between native applications and virtual machine environments, including applications hosted on the VMware PhotonOS distribution of Linux optimized for hosting container applications.

    In this release of Fusion Pro, VMware is also adding support for Microsoft’s VBS features—which include Credential Guard for Windows 10 virtual machines, unified extensible firmware interface (UEFI) Secure Boot and a virtual Trusted Platform Module—in the same way it supports them on VMware Workstation 14.

    Finally, VMware is providing access to enhanced networking controls to enable management of network address translation (NAT) rules, network packet loss and latency simulation and renaming of VM networks.

    The updates were announced ahead of VMware’s VMWorld annual conference, being held Aug. 27-31 in Las Vegas.

    Developers typically require more access to more IT environments than almost any other employee, so maximizing the number of operating systems that can be deployed on their systems is in the best financial interests of the organization. Even when an organization can afford multiple machines most developers don’t want to have to move files between physical machines. Desktop virtualization software provides a means to not only increase productivity but also reduce the amount of machine overhead associated with developing applications across multiple operating environments.

    — Mike Vizard

  • Automation: This Time, It’s Different

    Automation: This Time, It’s Different

    It took about 200,000 years for mankind to be able to figure out how to get an airplane to fly. The event took place Dec. 17, 1903, on a field in Kitty Hawk, N.C., when Wilbur Wright piloted the airplane he had made with his brother, Orville, into the air. The flight lasted for 12 seconds. The aircraft covered a distance of 120 feet. The next two flights went a distance of 175 and 200 feet, respectively. The last flight of the day covered a little more than 800 feet. The plane stayed in the air for 59 seconds, at an altitude never greater than 10 feet, before striking the ground and incurring minor damage.

    Although the flights were a significant technological breakthrough, they had absolutely no commercial value. Other forms of transportation could go further and travel for longer periods.

    Almost two years later, having learned from their mistakes, the Wright Brothers were able to keep an airplane flying for 38 minutes, covering a distance of 25 miles at a speed of 40 mph. The aircraft was 30 percent faster than a horse at full gallop, but still slower than a passenger train running at an average speed of 60 mph. Commercial viability was in sight.

    In June of 1919, 16 years after the Wright’s first flight at Kitty Hawk, Capt. John Alcock and Lt. Arthur Whitten Brown of the United Kingdom flew 1,690 miles from Newfoundland to Clifden, Ireland, in a little more than 16 hours. Fifty years later, it took 73 hours and and 5 minutes for the crew of Apollo 11 to fly the 238,857 miles from Cape Canaveral, Fla., to the moon.

    Think about it. It took mankind 200,00 years of technological progress to get a plane in the air, but only 63 years after that to travel to the moon. It’s pretty miraculous, in a way. Technology does not just move forward. It careens ahead exponentially.

     

    Figure 1: Mankind was able to travel from 12 feet to 238,857 miles by air in 63 years

    What was the stuff of science fiction in my childhood—think video conferencing—is commonplace today. And it’s cheaper than we ever imagined possible. The future possibilities of technology are limitless. Anything can come to be, given enough time.

    But, when it comes to considering artificial intelligence and machine autonomy, there are still a lot of people out there who think that the notion of machines taking over most of the jobs that humans do is far-fetched, if not daffy. According to conventional wisdom, history’s pattern is that for every job eliminated by technology, more are produced. And should machines displace humans from the workforce entirely, that day is a long way off.

    That’s what my grandmother thought. She was born in 1900. If you had told her when she was a teenage girl that the flying contraption she was reading about in the newspapers would have the result of putting a man on the moon in her lifetime, she would think you crazy, and rightly so. She had no historical precedent to think otherwise. Remember, in her day horses still pulled plows. Everything except birds and hot air balloons were land-bound. Yet, despite her disbelief, there came a time when she sat in front of a television to watch Neil Armstrong descend from the Apollo 11 Landing Module to put the first human footprint on the moon. She thought it would never happen. And yet, it did.

    Yes, the historical pattern has been that technology eliminates jobs and creates new ones for humans to do. When the automobile replaced the horse, the out-of-work blacksmiths went to work in factories that filled the ever-expanding industrial landscape. And, with each wave of technological innovation, there were the harbingers of doom predicting the demise of human labor. Each generation of naysayers uttered, “This time it’s different.” Conventional wisdom points out that it never is.

    That was then and this is now. This is the time of the autonomous machine. This time it is different.

    The Rise of the Autonomous Machine

    Machine autonomy is the ability for a device to make decisions and conduct itself independent from ongoing instruction, very much the way a human does. The most telling example is an automated stock trading program used by financial investors. The program is at work continually buying and selling stock with the goal of turning a profit. Certain safeguards are built in to prevent disaster. But for the most part, the application is left on its own to achieve its goal: to make money.

    Until very recently, machine autonomy was confined to software applications such as the stock trading example described above. However, modern robotics makes it so that not only can a machine “think” autonomously, it now also can move autonomously. The most apparent example is the self-driving car.

    Integrating physical and cognitive autonomy into machine behavior changes the game. In prior days, a taxi required a human driver to get the passenger’s destination, find the best route, drive the vehicle and collect payment for the ride. All a passenger needed to do was jump in the back seat and tell the driver where to go. The human driver figured out the rest. As technology improves, the passenger still will jump into the back seat, but in an autonomous vehicle that gets routing information and traffic conditions from a wireless connection to the internet.

    The ramifications are profound.

    For example, let’s imagine we have a diseased tree in our front yard that needs to be removed. Today, we call a landscaping company. The tree removal crew shows up, we point to the diseased tree and ask the foreman to remove it. That’s the only instruction we need to give. The landscaping crew has the ability to act autonomously to do whatever is necessary to remove the tree safely.

    Now, imagine the crew brings along a robot to help with the task. At this point, it’s safe to say that current robotic technology requires a lot of human guidance to remove the tree; the robot is more an aid than an independent worker. The robot might have no other ability than to pick up tree cuttings and take them to a truck to be hauled away. Or, the robot might be able to handle a tree-cutting tool to assist with demolition. Still, the independence of the robot it limited. Either its activities are limited to repeatable tasks limited in scope, or it can act in an ad hoc manner by taking one instruction at a time from a human. The robot is dependent on human instruction to get work done.

    However, let’s imagine that robot technology is on the trajectory of exponential innovation that has been the historic norm. Remember, in the scheme of 200,000 years of homo sapien activity, 63 years from a field in Kitty Hawk to the moon is but a blip in the historical timeline. Autonomous lumberjack robots are entirely possible.

    You call up a landscaping company. A crew of three lumberjack robots show up in an autonomously driven vehicle. These robots know everything there is to know about tree removal and they can do all the physical activities required. The “lead” robot asks you which tree needs removing. You point to the tree. The crew figures out the rest on its own, right down to charging your credit card for work done. Plausible? If you answer no, pretend you are my grandmother and you’ve just been asked whether you think it’s plausible that a man will walk on the moon in your lifetime.

    So the question remains, What happened to the human crew? Did they become data scientists? Don’t answer this question yet. We’ll get to it in moment. First, we need to talk about the next milestone on the road to complete machine autonomy: artificial general intelligence (AGI).

    Narrow AI and AGI

    In the tree-removal scenario described above, all robotic activity—autonomous or otherwise—was confined to a single task: removing a tree. The scope of work is limited. Working within a limited scope of behavior is called narrow AI (artificial intelligence).

    Examples of narrow AI are cutting down a tree, trading a stock, finding a date on Friday night, composing a song, making a pizza, etc. We’re going to see a lot of narrow AI emerge in the next few years. Venture capitalists such as Khosla Ventures, Greylock Partners and Goldman Sachs are already putting money into advancing narrow AI technologies. However, narrow AI is but a stepping stone to get across the pond to the final destination: general AI.

    Think of of it this way: If Kitty Hawk is the starting point of AI, the first transatlantic flight is narrow AI. AGI is landing on the moon.

    What will general AI look like? Let’s go back to the landscaping example.

    We’re back in your front yard sitting in some lawn chairs having ice tea on a hot summer’s night. A driverless vehicle shows up. Two robots emerge. One approaches you and asks your permission to deposit $500 in your PayPal account in exchange for cutting down a diseased tree in your front yard. “OK,” you say, “but how do you know the tree is diseased and why are you giving me $500?”

    While the second robot gets to work, the first robot responds, “The county keeps drones in the air 24/7 analyzing the landscape. A drone did a spectral analysis of your property and noticed the diseased tree. In addition to reporting back the location of the tree, the drone also included a full biological profile. If you don’t remove the tree, the disease will spread. That’s the bad news. The good news is that it’s a cherry tree. And it seems that only 10 percent of the tree is diseased. The rest is perfectly good wood. The price of cherry wood is quite high on the commodity markets right now. Also, there’s a legal statute that requires the county to reimburse property owners when a private landscape is altered for general good. So, the county sold a futures contract on the wood it can reclaim from your tree. The $500 we want to put in your PayPal account reflects your share of the revenue received from the futures contract plus the amount of the reimbursement entitlement required by law.”

    This is what AGI looks like. AGI is the ability for a machine to think in broad terms, using a multitude of knowledge domains. Combining AGI with the advances in physical robotic capabilities expected on the horizon produces a result in which machine autonomy is not only possible, but will exceed human capability.

    If you think AGI is a fantastic notion, go talk to Yves Bergquist, CEO over at Novamente. The company is actively working to improve AGI for general commercial use. One application Novamente is developing uses AGI to determine, if not create, movie scripts with a high probability for profitability. To quote Bergquist: “A story is an algorithm.”

    Making a modern-day Hollywood blockbuster is a billion-dollar undertaking. Given the choice, studios would rather not roll the dice. However, when it comes to scripts, predicting a winner is difficult. Of all the human endeavors that are tough to emulate with artificial intelligence, creative storytelling ranks high. Writing a script requires working in a multitude of knowledge domains: story, character, plotlines, scene design and historical continuity, to name a few. Narrow AI is not suited to the task. You need AGI. There’s too much to consider. In a way, it’s surprising to think of Hollywood is the perfect incubator for developing real-world AGI. But it makes sense. AGI might produce a few flops. But, it’s a whole lot safer to lose at the box office than to lose on the battlefield.

    Given companies such as Novamente, the entertainment industry might well become the incubator in which AGI is perfected. Then, if the trend in rate of technological innovation continues, eventually AGI will become viable everywhere. Then what? What happens when a machine can do everything a human does only faster and better?

    A Turkey’s Life

    Understanding the long-term impacts of a given technology has not been one of the highlights of human endeavor. As cars became commonplace, few people considered the possibility that too many would create too much carbon monoxide and thus threaten the health of the earth’s population. And nobody really thought about what was going to happen to the displaced blacksmith who was no longer needed to make shoes for a diminishing number of horses. Events just ran their course with little or no forethought.

    But, it’s getting better. Some people do think ahead. Military planners consider the improbable as do financial analysts. It’s called risk analysis. These are the people that get paid to think outside the box, so to speak. They understand the even small possibilities might happen. Whether they are heeded or not is another story.

    Today, machine autonomy is real. The possibility exists that in our lifetime automated AI will indeed be able to do everything a human does. And, the machine will do it better at less expense. There will be no new jobs for humans to do as old ones are destroyed. A machine will be able to do the new job faster and cheaper—even those jobs that require a significant amount of AGI. Then, what will happen to the humans?

    We have to think about it today!

    Sadly, few are. We are not hearing any articulation in general industry or in government, at any level, about ideas to address the the impact of automation on human employment as machine autonomy and AGI become more prevalent in the economy. It seems as though most people are relying on the old logic of the conventional wisdom.

    Conventional wisdom is easy to accept. The U.S. economy is reported to be at practically full employment levels. Employers are complaining about how difficult it is to find qualified workers. The stock market is achieving historic heights. Given history and current events, of course it’s reasonable to say there always will be jobs for humans to do.

    This assertion works until the day fully autonomous machines appear on the landscape. Then, conventional wisdom will be that which is uttered by turkeys on the day before Thanksgiving.

    What do I mean? Allow me to elaborate using a previously written analogy.

    Imagine you are a turkey on a farm. Every day the farmer comes by to feed you. This goes on for one week, two weeks, 10 weeks. Given your history, you are completely justified to predict that your future will be one of satisfying meals. It’s always been this way; how could it be otherwise? You go day in and day out predicting that the next day will be full of food and sunshine. You are correct … right up until the day before Thanksgiving.

    In other words, there are things that happen independent of historical precedent. The trick is to imagine what such events might be.

    Everybody agrees that AI is here and that machine autonomy is growing. The conventional wisdom is that, based on historical observation, there have always been jobs as technology grows. Many think the full replacement of human labor by autonomous machines is a possibility, but one that is coming in the far, distant future. When Wilbur Wright took off in 1903, my grandmother’s distant future as was 1969. Those 63 years passed in no time. She lived to see a man land on the moon. Those of us alive today are seeing the beginnings of true machine autonomy appearing on the technology landscape. A world of full machine autonomy is more than probable in the lifetimes of our grandchildren. It will happen. What will be the impact? What will they do if their labor is no longer required?

    Back in 1903, as automobiles began to chug along the planet’s roads, we missed predicting the possibility of air pollution and global warming. Today, will we allow conventional wisdom to prevail and miss preparing for the impact that full machine autonomy will have on human employment? Or will we plan ahead? Hopefully, we’ve learned from our mistakes.

    I’ll leave it to you to decide.

    Author’s Note: The analogy of prediction in terms of historical precedence is taken from the book, “The Black Swan,” by Nassim Nicholas Taleb

    — Bob Reselman

  • Jenkins World, Training and Infostretch

    Jenkins World, Training and Infostretch

    I’ve talked to a fair number of vendors about Jenkins World 2017, and I’ve spent a decent amount of time lately supporting DevOps training initiatives at a variety of vendors.

    The thing is, the DevOps world is changing fast enough and there are enough options out there that training is not something you need only before moving to DevOps. During one recent project, I ended up learning about a particular topic as I was developing support materials for a training session on that topic. And I’m pretty steeped in the DevOps world.

    So, while I don’t write about every vendor I’ve talked to about Jenkins World, Infostretch‘s new training program is worth talking about. Infostretch is unveiling an array of training solutions to help companies not only get a handle on DevOps needs, but also to grow their DevOps maturity.

    Among the offerings will be a DevOps maturity assessment and new Jenkins training programs. In conjunction with its visit to Jenkins World, Infostretch will be offering a free 90-minute webinar on adopting Jenkins 2.0.

    Demands of the job will keep me from attending Jenkins World, but if you’re there, it might be worth checking out Infostretch’s booth (#415) to see what there is to learn. If you do, feel free to drop me a line—I’m intrigued to learn more about the training and how it fits in with other available offerings. As an added bonus, the company is giving away “Game of Thrones”-themed DevOps Journey Maps marking various stages of DevOps journey and the “happy flow” of DevOps, and including the various tools available in the market for each stage. So you can snag that while stopping by for me to learn about Infostretch’s training.

    The other thing that interested me was a presentation. Sanil Pillai, director of Infostretch Labs, will be presenting a 15-minute demo titled, “Auto-Convert Your Freestyle Jenkins Jobs to Coded Pipeline” on Wednesday, Aug. 30, at 10:45 a.m. at the Sponsor Theater, in the Expo Hall. The variety of scripts that can make up the components of a Jenkins build environment are a problem many of us have struggled with; while better than what we had because they’re part of an automated process, the components are still technical debt with variable maintenance requirements. Someone, please go see the talk/demo and report back. It would be cool if Infostretch has an answer for this problem.

    I Reiterate: Training is Imperative

    It is human nature to make a large change and settle in with the known new world. DevOps is not designed to be that way. It is still growing and changing, so don’t get complacent. Challenge yourself and seek out training, tool enhancements and opportunities to improve. As others have said repeatedly and well, DevOps is a journey, not a destination. Learn, get better, find better ways and tools and keep improving.

    And, keep rocking it. Eliminating IT as a bottleneck is a huge step to improving product development and being more in sync with the business.

    Of course, now that I’ve written out the reasons why Infostretch’s plans for Jenkins World interested me, I am tempted to dig into some of the other offerings. Or to try and figure out how to go to Jenkins world without missing important things at work.

    You may be hearing more of Jenkins World from me before it arrives.

    — Don Macvittie

  • CollabNet Merges with VersionOne for ALM Supremacy

    CollabNet Merges with VersionOne for ALM Supremacy

    Thanks to the rise of DevOps, there has been a lot of focus on various forms of application lifecycle management (ALM) spanning multiple application development methodologies. But as IT organizations become more comfortable with multiple methodologies, it turns out they are not replacing one with another as much as simply trying to figure out where to employ one over another. That, in turn, is driving some consolidation across the ALM category.

    CollabNet this week announced it is merging with VersionOne, a provider of an ALM framework optimized for agile application development. While CollabNet has made some forays into the space, historically its primary focus has been on waterfall methodologies commonly used across larger enterprise IT organizations. CollabNet CEO Flint Brenton says the goal now is to combine the best of the ALM tools provided by both companies to enable IT organizations to leverage agile and waterfall methodologies as they best see fit. In fact, he says the biggest ALM issue facing organizations today is the need to balance developing applications faster and the inherent risks associated with potentially moving too quickly.

    Robert Holler, formerly the CEO of VersionOne, will assume the post of chief strategy officer for the combined company. He says there’s very little overlap between the two company’s product portfolios, and the one thing that will distinguish CollabNet going forward is an open approach to ALM that enables organizations to employ whatever tools they prefer. Instead of forcing organizations to rip and replace those tools, Holler says ALM frameworks need to foster collaboration rather than trying to impose a closed ALM environment. That environment also needs to be deployable on-premises or in the cloud, depending on the requirements of the customer.

    Holler notes that once any segment of the IT industry reaches a certain level of maturity, consolidation is all but inevitable. The opportunity CollabNet has is providing an ALM environment that makes it possible to automatically package and deploy applications that includes strong version-control mechanisms. Those capabilities will become even more critically important as IT organizations expand usage of microservices based on, for example Kubernetes, alongside traditional virtual machine deployments across the enterprise. Accomplishing that goal will require a common management layer capable of spanning both environments, he says.

    The combined companies have more than 20,000 customers. That number may not collectively represent the lion’s share of the ALM market, but it does make CollabNet a serious contender against a host of rivals that are both a lot older and larger. CollabNet’s challenge now is convincing customers of competitive organizations to switch to an ALM platform that CollabNet contends is a whole lot more flexible.

    In the meantime, it’ll be interesting to wait and see if the combination of CollabNet and VersionOne will drive any additional acquisitions at a time when IT organizations are becoming a lot less religious about what type of application development methodology gets employed by who and when.

    — Mike Vizard