Category: Features

  • Education in the Age of Automation

    Education in the Age of Automation

    Automation is changing the nature of education and the ways people learn. More schools are using online learning to supplement in-class activities. In fact, some schools are completely online. Distributed computing on the internet and the automation that drives it makes this possible.

    Everything changes when the formal education process becomes embedded in the internet. Courseware delivery becomes asynchronous; people learn what they want, when they want to. Test administration becomes more about the efficient acquisition of data and evaluation thereof. Human-to-human interaction as a basis for a meaningful educational experience becomes optional. Today, it’s entirely possible to learn all you need to know to make a good living in the modern world without ever needing to sit in a classroom or interact with a human directly. Let’s face it: You can do a lot of learning from YouTube.

    As a result, more people are beginning to question the conventional wisdom of spending four years and thousands of dollars to get a bachelor’s degree—particularly now that companies including IBM, Google and Apple no longer require one to get hired.

    Coincidentally, as companies eliminate the college degree requirement for new hires, we’re seeing significant growth in technical bootcamps. One study reports that this year, 20,000 students will complete a course of study at a coding boot camp and be “job ready.” Considering that the number of students who graduated with a computer science degree from a typical college in 2017 numbered about 93,000, there’s a good case to be made that boot camps are siphoning off a number of students that otherwise would be headed to academia.

    Going to boot camp instead of college is an upward trend: The study projects that the number of boot camps are expected to grow 20 percent this year. The career path for a technical professional does not necessarily involve going college. Going to a boot camp for a year—if not less—will suffice.

    Is this a problem? I’m not sure. On the plus side, I am reminded of the scene in the film, “Good Will Hunting,” when Matt Damon’s character Will Hunting, a genius with a photographic memory who walked the halls of MIT working as a janitor, makes the profound remark:

    “… you dropped a hundred and fifty grand on a f****** education you coulda got for a dollar fifty in late charges at the public library.”

    There’s a good argument to be made that when it comes to getting a good paying job, the $15,000 median price tag for attending a coding boot camp has a better much better ROI than spending  ~$200,000, the cost of a four-year degree from MIT.

    But then, I am reminded of Aldous Huxley.

    In his book, “Brave New World,” people are grown in test tubes according to a specific formulas, the result of which is a biological caste system. Those in the Epsilon caste are grown to be 3 feet tall and abhor the outdoors. Their job is to work their way underneath the machines on the factory floor to do simple maintenance. Deltas, the next caste up in the hierarchy, do the menial chores—janitors, for example. Gammas are the bookkeepers and data entry clerks. Then you get to the higher levels, Alphas and Beta. Betas are technicians who do very sophisticated jobs, such as mixing dangerous chemical together. One mishap can result in an explosion, killing all. Finally, at the top of hierarchy are the Alphas. Alphas possess advanced analytical skills and a broad knowledge base. They are able to plan and strategize. They have a high degree of creativity. Their role is to run the society.

    Thus, I have a concern about the increasing role of technology and  automation education, and the emergence of tech-focused boot camps as the prime post-secondary educational experience for many.

    As more of those entering the workforce forgo a formal college education, we run the risk of creating a society in which most of the technical workforce is Betas. They’re able to do highly complex tasks, yet have no idea why they’re doing them.

    Let me be specific. Let’s talk about Kubernetes: It takes a lot of knowledge and experience to be good at getting Kubernetes to work. It’s a complex, evolving technology that you need to keep your eye on. Companies are spending a good deal of money making sure their IT staff are competent with Kubernetes—as well they should be. One little misstep can result in the digital equivalent of a chemical explosion. Yet, I wonder how many of those “working Kubernetes” are thinking about the bigger picture—for example, the purpose and value of the enterprise using Kubernetes. Are these engineers questioning if the technology they’re working is doing good or harm?

    Or, let’s turn the dials down a bit and ask a question that’s less loaded philosophically. How many of those working Kubernetes today wonder if an alternative orchestration technology such as Docker Swarm might be a better choice to meet the need at hand. Or are they so concerned with getting Kubernetes to run that they don’t have the bandwidth to think about anything else? Do they just defer such critical thinking to “the system architects”?

    Critical thinking, although an acquired skill, is not one that’s new on the cognitive landscape. It’s been taught for thousands of years, since the time Socrates sat under an olive tree asking simple questions that forced his students to transform their assumptions and allusions into thoughts based on reason and reflection.

    Developing the ability to think critically traditionally has been one the aims of a college education. The romantic ideal is that college is the place where students are exposed to a variety of ideas from a variety of viewpoints. The hope is that such exposure, along with instruction aimed at developing one’s ability to engage in higher-order thinking, will create graduates who will contribute to making a better-functioning, more prosperous and more humane society.

    But, that’s the traditional perception of college. The reality is changing. Maybe college is just the place you go to get the skills required to get a good job. If that’s the case, given that a college education is becoming less affordable to more people, maybe the boot camp approach is best. Yet, there is a risk.

    A good while back when I was considering enrolling in a doctoral program, I attended a required orientation at Harvard University. I sat in an auditorium composed of about 50 aspiring doctoral students. One of the department heads on stage said the following, “The objective of our doctoral programs is simple. We want to train you to run the world.”

    Yep, that’s right. And, I can say with a good deal of confidence that this objective is the same today—to create thinkers who have the skills and knowledge necessary to run the world. The Alphas, if you will.

    So, we’re at a crossroads. Automation is a liberating force in education in that it makes infinite knowledge available to anyone who wants it at a fraction of a cost of a traditional college education. All that’s required is the time and desire to take advantage of the opportunity at hand. However, if the result of such education is a workforce in which the concern of most is to ensure that the technology works and does not blow up, then the risk we run is that bigger decisions will be made by those who had the time and money for an increasingly elite education. In other words, as more people spend time focused on turning the dials and setting the levels to make the technology go, a very small minority actually will be determining the purpose and direction of the machine the technology supports.

    Still, the fact is, most of us need to make a buck to survive. This means being good at getting the tech to work. Yet, we will do well to understand that there is a Big Picture and if don’t pay attention to it, someone else who has been educated to run the world will.

    — Bob Reselman

  • DevOps Dozen 2018 – Nominations Are Now Open

    DevOps Dozen 2018 – Nominations Are Now Open

    The DevOps Dozen awards are back and now open for nominations. This fourth annual DevOps Dozen honors the best of the best—the leaders and innovators in the DevOps community. This year’s awards will include 12 categories, with a winner chosen from each. The top four to six nominees in each category will become finalists, who will be selected based upon the number of nominations they received. You can nominate up to two entrants in each category; however, you can make only one nomination per person. In addition, everyone nominating will be required to provide their name and email address; while that won’t thwart any ballot-stuffing, we hope people will be trustworthy during the nomination process. The winners will be selected by our panel of judges.

    Last day to submit your nominations for the DevOps Dozen 2018 awards is Oct 10, 2018. Here’s where to vote: https://www.surveymonkey.com/r/devopsdozen

    Who are the judges? This was tough. We couldn’t have anyone who might be eligible for an award. That disqualifies vendors, practitioners and many others. However, I think we have four great judges:

    1. Alan Shimel, founder and editor in chief, devopsy.kinsta.cloud
    2. George Hulme, longtime tech journalist and editor at devopsy.kinsta.cloud and Security Boulevard
    3. Jayne Groll, CEO and co-founder of the DevOps Institute
    4. Helen Beal, DevOpsologist at Ranger4.

    So what are the dozen categories for the DevOps Dozen this year? That you can get on the site itself, but here they are as well:

    [su_custom_gallery source=”media: 125437,125438,125439,125440,125441,125442,125443,125444,125445,125446,125447,125448,” link=”custom” target=”blank” width=”400″ height=”200″]

    Thank you again for your enthusiastic response to last year’s awards. The full list of 2017 finalists and winners are available to view here.

    There are so many great companies and people involved in DevOps that it’s always difficult to pick the winners. We know some worthy choices will not be voted tops in their category; however, acknowledging them in our awards process helps show how important they are in the DevOps space.

    As stated earlier, the top four to six nominees in each category will be designated as finalists, who then can submit a presentation on why they deserve the award to judges@devops.com. Finalists will be announced the second week of November and the winners, who will be chosen by our panel of judges, will be announced in December.

    If you have questions, send them to DD@devops.com. Voting for finalist nominees is open for three weeks, so don’t waste any time—nominate your favorites today. Good luck to everyone vying to be one of the DevOps Dozen 2018!

    — Alan Shimel

  • How to Convince Your Manager to Send You to DevOps World | Jenkins World 2018

    How to Convince Your Manager to Send You to DevOps World | Jenkins World 2018

    The largest gathering of Jenkins users and DevOps practitioners is less than a month away. DevOps World | Jenkins World 2018 will be held in two locations this year, Sept. 16-19 in San Francisco and Oct. 22-25 in Nice, France. With exciting keynotes from industry influencers including Dr. Nicole Forsgren, CEO and chief data scientist at DORA, and James Governor, analyst and co-founder of RedMonk, there will be tons of learning and networking opportunities. There will even be a “Westworld” themed party, making it an event you do not want to miss.

    So now that we’ve convinced you to attend, you need to convince your manager why they should send you to DevOps World | Jenkins World 2018. Don’t worry: There are lots of good reasons why attending would be beneficial to you and your company. Once you have successfully convinced your manager to attend DevOps World | Jenkins World, don’t forget to register! To sweeten the deal, you can enter the promotional code just for devopsy.kinsta.cloud readers: JWDEVOPSCUST. That code gets you 20 percent off your registration.

    Keep Learning

    With more than 70 sessions offered in San Francisco and 50 sessions in Nice, all presented by DevOps and Jenkins experts, DevOps World | Jenkins World provides a chance to learn from DevOps leaders. Be sure to emphasize to your manager the importance of learning from the very best in the DevOps community, in training and workshops and, of course, in the breakout sessions. From Jenkins founder Kohsuke Kawaguchi to CloudBees CEO Sacha Labourey and the aforementioned industry influencers, your manager will greatly appreciate the knowledge you bring back to the office from experienced industry experts.

    You should definitely take advantage of some outstanding training opportunities to enhance your continuous delivery, Jenkins and DevOps knowledge. Available training sessions include Jenkins Certification Training, Jenkins Fundamentals, DevOps Leader Certification Training, CloudBees Core Fundamentals, CloudBees Core on Kubernetes and Value Stream Mapping for DevOps. Additionally, you will receive a free Jenkins exam with the purchase of a full conference registration. That is a huge value-add for both your resume and your organization!

    Build Your Network

    DevOps World | Jenkins World brings together thousands of software development experts, thus providing numerous networking opportunities. The conference gives you the opportunity to learn of challenges other organizations in the industry have faced and how they’ve overcome them. If they have already solved a challenge you are just starting to tackle, you could walk away with knowledge that more than pays for the cost of the conference. Conference attendees can also share success stories that may inspire your organization’s next big win. Make it known to your manager that you will be exposed to people like you, who have similar business needs and challenges, whom you will be able to connect with and learn from.

    Invest in Your (and Your Company’s) Future

    As we previously mentioned, with the industry continuing to innovate and evolve, having the skill set to keep up with these changes help make you a valuable asset to your team. When convincing your manager to let you attend, make sure you also present how this knowledge will help push you and your team forward, ultimately propelling your entire organization forward. Highlighting the potential ROI of this opportunity will help your manager better justify the cost to send you to DevOps World | Jenkins World. Detail exactly how much airfare and lodging will cost, but also note what kind of impact it will have on the organization’s bottom line. The ROI will be evident—make that clear!

    We would like to think we have provided some pretty solid justifications for you, but if you still need an extra boost, we have also created an email template to use when sending all this over to your manager for review. Once your boss gives you the green light, go register!

    — Alan Shimel

  • VMware Extends DevOps Reach via SaaS Apps

    VMware Extends DevOps Reach via SaaS Apps

    VMware, at the VMworld 2018 conference today, announced it will be delving deeper in the realm of DevOps with the launch of a continuous delivery pipeline dubbed Code Stream.

    In addition, VMware announced Cloud Assembly, a set of declarative tools that enable IT organizations to spin up a cloud in as little as 10 minutes by managing infrastructure as code, and Service Broker, a catalog through which services residing on multiple clouds can be published, governed and secured.

    Milin Desai, vice president and general manager for the Cloud Services Business Unit of VMware, said these offerings extend the reach of VMware’s Cloud Automation Services that are all invoked as software-as-a-service (SaaS) applications.

    VMware also today announced a beta release of Secure State, a set of tools for tracking security alerts across Amazon Web Services (AWS) and Microsoft Azure that also can be used to investigate when changes to those environments were made. Secure Slate is based on the technology the company gained by acquiring CloudCoreo earlier this year. What’s more, VMware is updating the Wavefront by VMware monitoring service to add support for deeper support for containerized workloads running on Pivotal Kubernetes Service (PKS). Wavefront also now supports the Amazon Lambda serverless computing framework made available by Amazon Web Services (AWS).

    Code Stream is designed to track code across multiple platforms and comes with pre-built plug-ins for Wavefront, Harbor, Nexus, Pivotal Kubernetes Service (PKS), Ansible and Slack. VMware is also committed to providing integrations with continuous integration/continuous deployment (CI/CD) platforms such as Jenkins, Desai said.

    VMware has previously made extensive investments in software-defined data centers (SDDCs) based on a layer of management software deployed on top of VMware vSphere. As part of that effort, VMware today announced version 6.7 of VMware vSphere, which adds tools for verifying the state of a virtual machine, and a new Platinum edition of the platform that includes VMware AppDefense, to secure application workloads running on VMware vSphere.

    Beyond the virtual machine level, the scope of VMware’s DevOps portfolio has been limited. By adding a range of DevOps tools that are made available as SaaS applications, VMware now can provide tools spanning just about everything, from cloud orchestration to code delivery, Desai said.

    The expanded push into DevOps comes at a time when VMware is also extending the scope of its alliance with AWS. The company earlier this week announced it has lowered the cost of entry of VMware for AWS by 50 percent for a limited time and is making available a three-node configuration option. Previously, VMware required customers to set up a minimum four-node configuration. VMware will enable IT organizations to configure a three-host software-defined data center (SDDC) for the cost of two hosts.

    The company is further helping to reduce costs by make it possible for IT organizations to also specify the number of processor core counts for Oracle and Microsoft applications running on AWS, along with new options for deploying NSX network virtualization software.

    It’s unclear to what degree VMware will be able to leverage its historic strengths in server virtualization to become a significant force in the realm of DevOps. The acquisition of Wavefront in last year was clearly a significant step in that direction. But the individuals with an IT organization who decide what virtual machines to employ are not necessarily the same individuals selecting DevOps tools. VMware is clearly hoping that as more IT organizations embrace DevOps processes spanning multiple clouds, many more of them will view the company’s growing portfolio of SaaS applications as a natural extension.

    — Mike Vizard

  • When DevOps and ITSM Collide: Mistakes to Avoid

    When DevOps and ITSM Collide: Mistakes to Avoid

    In many ways the DevOps movement evolved as a reaction against the worst elements of IT service management (ITSM). IT leaders wanted to get from under the yoke of overly complex processes, bureaucracy and red tape to speed up software delivery, and to just get stuff done. Now that DevOps has kicked into full gear at so many organizations, the question remains: What do we do about ITSM?

    While the instinct in some may be to completely ditch ITSM or to just let the ITSM team operate in a separate orbit from DevOps practitioners, experts say that would be a big mistake.

    “DevOps aims to deliver high-quality software to the business faster and in shorter cycles,” explained Krishna Mohan Reddy, vice president and deputy global head of Cognitive Business Operations at Tata Consultancy Services. “However, it still does not eliminate the need for controls.”

    In many ways ITSM is the yin to DevOps’ yang—the two operating philosophies do offer contrasting viewpoints but when the operate in a single system they can be extremely complementary and synergistic.

    “Maintaining the proper balance between the ITSM and DevOps helps the organizations to scale and grow and become more organized,” said Sachin Agarwal, DevOps engineer and solution architect for Mantra Labs. Operating at DevOps speeds with ITSM frameworks in place keeps finger-pointing at a minimum and reduces the risks of failed deployments. “Both in harmony will increase the efficiency and reduce the blame-game within the organization.”

    As organizations try to figure out how to achieve that harmony, here are some pitfalls they should seek to avoid:

    Letting Each Tribe’s Preconceived Notions Hold Back Overall IT Progress

    It can be easy to get wrapped up into dogmatic fervor that your particular philosophy is the One True Path for IT success, but that really does nobody any favor. Organizations that want to pick up the best of both ITSM and DevOps need to encourage stakeholders to approach the table with an open mind.

    “You need to compromise. A lot of the new, young practitioners in DevOps and Agile will pretty much automatically discount opinions coming from people who have got ITIL certifications,” said Andi Mann, chief technology advocate for Splunk. “And vice versa—a lot of traditional operations and development teams will look at the people in DevOps and Agile and think they’re all cowboys. But they all have something to learn from each other.”

    For DevOps practitioners, it’s important to keep in mind that ITSM controls such as service requests, change management or structured management of incidents and problems don’t have to stop a team from delivering quality software at speed, said Troy Vetter, COO of Coda Global.

    “In fact, speed and quality are actually helped by being closely monitored. In IT, just like in science, if it isn’t seen, measured, and “reproducible, it doesn’t really count,” he noted. “So, ITSM is actually the perfect complement to DevOps because it aids in the visibility, measurement and reproducibility of key DevOps processes.”

    Failing to Address the Elephant in the Room: Change Management

    Analyst Roy Atkinson agrees that ITSM has a lot to bring to the table for DevOps workflows. ITSM’s rich history in thinking about and tracking operational best practices offers tons of value in improving the customer experience with the software being delivered. But on the flip side, ITSM teams can’t continue to operate as they did in the past. They need to compromise and learn new ways of accommodating DevOps approaches—particularly in the area of change management.

    “Change management has often been where DevOps and ITSM collide,” said Atkinson, who analyzes the service management market for HDI. “The stereotypical Change Advisory Board must radically revise its approach to be in sync with the enormous amount of change that DevOps can produce in a day.”

    The good news is that thought leaders in the ITSM world have been thinking hard about this issue and have been evolving practices so they can embed change management controls into a DevOps framework without holding back continuous delivery.

    “There is some excellent recent thinking in the ITSM world about how change management can serve its intended purpose without being a roadblock by acting as an enabler of change and being involved all along the way, rather than a bolt-on quality check at the end of the line before the production environment,” Atkinson said.

    Maintaining Separate Toolchains

    Often times one of the big reasons ITSM will remain a roadblock for DevOps isn’t because the ITSM folks aren’t willing to collaborate, but simply because each team relies on completely separate toolchains.

    “You might have a tool that developers use for tracking bugs or product backlog and then there’s a completely separate IT service management tool,” said Donna Knapp, curriculum development manager for ITSM Academy and author of the DevOps Institute’s course on ITSM for DevOps. “So what you end up doing is forcing developers to use some process that’s outside of their norm in order to address issues.”

    As Vetter explained, a lot of the knee-jerk DevOps reaction against ITSM has to do with an aversion to the historical view of ITSM requiring manual inputs in monolithic ticketing systems. But the technology of ITSM controls has advanced—it just needs to be appropriately implemented.

    “Self-service requests, automation flows and IT orchestration are now our front door to actions, and IT service management can and should be happening in the background, automagically created, maintained and measured by our DevOps tools,” he said.

    — Ericka Chickowski

  • Automated Management with Modern Architectures

    Automated Management with Modern Architectures

    We’ve come a long way. Just five years ago, with virtual machines (VMs) and decent monitoring, I would never have considered active automated system repairs for the average organization.

    There were many reasons for that. Monitoring was spread out and required a lot of work to spin together. The volume of logs from monitoring was generally huge once logging was consolidated, and that was the best source of automated recovery information. The time it takes a VM to start up and the space that a fully installed VM took up on disk were both negatives to doing automated response.

    But that was then, this is now. And the world has changed. A lot.

    Most companies using cloud or container based architectures with DevOps are doing monitoring. Tools such as DataDog and ExtraHop between them monitor the application side of performance and the networkwide responsiveness of the application infrastructure. Most container-based architectures are using one or both with alerting to keep track of their system’s and instance’s performance. Add in container management systems, and the infrastructure to support systemwide automation is starting to look pretty darned complete.

    Beyond Monitoring

    The most advanced DevOps and automation shops have gone a step further and are using these tools to do automated management on top of monitoring. While tooling varies—and I do not mean to use the above two as the only solutions—they show well the two sides of monitoring: application and environment (in the case of ExtraHop, networking). Most organizations have a wider selection, including in-source tooling and other monitoring systems. But a few have stepped up to basing the decision to auto-correct on these tools. If ExtraHop is showing extreme response times from an instance, but other instances are responding just fine, that scenario can trigger spinning up a new instance and taking the old one down. The same is true if DataDog shows one instance is taking forever to process requests, while other instances are performing admirably. If the overall system response time is lagging, new instances can be automatically added, either by directly spinning them up or making a call to the container management system to do so.

    In the case of the failing machine, companies that have been doing this for any length of time will happily tell you to keep the instance taken offline so you have a record of what went wrong and can fix it. Heartbleed would have been a different beast had this been followed, and others will give you the same story of, “It’s hard to troubleshoot when the evidence is destroyed.” So while many companies tend to think along the lines of, “If we pulled it down and replaced it, we don’t need it anymore,” what should be done is, from the start, set up to keep the container and take time to look at it to help determine what went wrong before it goes wrong again on a different instance.

    No Muss, No Fuss

    The idea of the “self-healing network” is certainly nothing new. The difference is that machine speed, monitoring tools, management tools and platform have all evolved to a point where all of us can implement it. That doesn’t remove work around problems with responsiveness, but it does offer a stopgap that will keep many applications up and responsive while you figure out why they’re having issues.

    One key is to have an alert system that lets the team responsible know what has happened. If automation replaces an instance, the team needs to know which instance it took down so it can grab the files and figure out what happened. If three of those notices come across in 10 or 15 minutes, you have a definite problem that needs more proactive interaction.

    For clarity: My caveats every time I say “this works” are simple—network issues (inside or outside your network) may be causing perceived performance issues, and these systems can’t do much about that. Hardware failures are not resolved by dropping an instance and spinning up a new one, etc. But until monitoring and management alerts reach alarming stage, the application is likely humming along. And the team can focus on enhancements, not spinning up replacement instances. The larger the server base, the more important this is.

    New products, enhancements to existing products, fixed bugs, improved architectures—concentrating on these issues instead of keeping the system live is always a win.

    So if you’re not using automated management, it certainly is worth a look. Your environment is unique, and it fits better in some than others. So I’ll leave it to you to evaluate in light of your architecture. But if you can free up time, I highly recommend you do.

    — Don Macvittie

  • A Certifiable Reason to Attend Training at DevOps World | Jenkins World 2018

    A Certifiable Reason to Attend Training at DevOps World | Jenkins World 2018

    There are many factors that make DevOps World | Jenkins World the essential DevOps event to attend each year. Whether it is the keynotes and speaker sessions from industry-leading DevOps experts, the expo where you can check out the latest and greatest from our friends in the software industry or the themed after-party, there are many reasons why year over year the conference grows. An added benefit that contributes to DevOps World | Jenkins World being the DevOps event of the year is the wealth of informative preconference training and certification. Think of them as the workout before the big game, providing you the tools and knowledge to make the most of the conference and beyond.

    The growth of attendance and variety of attendees of  the DevOps World | Jenkins World conference is one of the indicators that the industry is constantly innovating and evolving. Last year, Forrester declared 2018 as the “Year of DevOps,” with 50 percent of survey respondents reporting they had already implemented DevOps with plans to expand. For DevOps practitioners to keep up with the continuous pace of modern software development, there also has to be continuous learning. Training and certification at DevOps World | Jenkins World will cover relevant topics in software development, such as authorization and security, build management, instance administration and interfacing with cloud services, in addition to Jenkins and CloudBees Core fundamentals.

    Not only are all training sessions available to add on to your full conference sessions pass, but you also can receive a free Jenkins certification exam voucher—a $150 value—for the Certified Jenkins Engineer (CJE) and Certified CloudBees Jenkins Platform Engineer (CCJPE) exams. You can choose to sign up for an onsite exam at DevOps World | Jenkins World (first-come, first-serve) or use it at a later date. There are also several half-, one- and two-day courses that can be added during the event registration process.

    In addition to our recommendations below, check out the Training and Certification page to see what courses can help strengthen your software delivery pipeline skills.

    DevOps Leader Certification Training

    Successful implementation of DevOps requires leadership. Whether you are in a  tactical or strategic role, if you help design, influence, implement or motivate the cultural transformation in DevOps adoption, this course will take your DevOps leadership to the next level.

    Value Stream Mapping for DevOps

    If you’re looking to better understand DevOps, you are in the right place! Join Mike Orzen, a recognized and prominent Lean thought leader and author, to learn the ins and outs of DevOps value stream mapping, helping you identify inefficiencies in your current process, and optimize it to deliver more value to your customers.

    Jenkins Fundamentals

    It wouldn’t be Jenkins World without Jenkins! To prepare yourself for both the Certified Jenkins Engineer (CJE) or Certified CloudBees Jenkins Platform Engineer (CCJPE) certifications, Jenkins Fundamentals introduces you to the best practices for leveraging Jenkins to drive your continuous development life cycle with Jenkins.

    CloudBees Core Fundamentals

    As the foundation of CloudBees, once you’ve mastered Jenkins Fundamentals, CloudBees Core Fundamentals is the obvious next step. In this training, attendees will gain the skills needed to leverage the CloudBees Core product suite to successfully scale CD and DevOps in their organizations. The training includes an overview of the key proprietary features provided with CloudBees Core to enhance the capabilities of Jenkins.

    CloudBees Core on Kubernetes

    Kubernetes is seeing widespread adoption as the operating system for cloud native applications and the industry’s go-to container orchestration system. This course will provide attendees with the tools needs to run CloudBees Core on Kubernetes, and leverage public and private clouds to establish an elastic, scalable CD and DevOps platform. The course includes hands-on installation of CloudBees Core on Kubernetes. 

    Go to https://www.cloudbees.com/devops-world to learn more and to register. Additionally, use this special code just for devopsy.kinsta.cloud readers—JWDEVOPSCUST—at registration, and you’ll get a 20 percent discount.

    — Brian Dawson

  • DevOps World | Jenkins World 2018: Q&A with CloudBees CEO Sacha Labourey

    DevOps World | Jenkins World 2018: Q&A with CloudBees CEO Sacha Labourey

    Jenkins World has come to hold a regular spot on the calendars of the software development community. As the conference, and the industry, have grown over the years, the event has transformed—which is aptly the theme for this year’s event—into DevOps World | Jenkins World. CloudBees, the premier sponsor, also extended it for DevOps practitioners in Europe—specifically to Nice, France.

    In this Q&A, CloudBees CEO Sacha Labourey talks about the changes to this year’s conference and offers attendees a sneak preview.

    Gilmore: Why is Jenkins World changing its name to DevOps World?

    Sacha Labourey: Our goal with the change to DevOps World, was to scale the topics covered to create an event where people can meet and learn from each other and enhance their knowledge of not only Jenkins but the entire DevOps landscape. Although Jenkins remains a very important focus of the event, with the tremendous growth in DevOps adoption we wanted to expand Jenkins World to include a breadth of industry topics, such as cloud native, DevSecOps, software value streams and the more practical DevOps adoption use cases.

    Not only is the DevOps World | Jenkins World conference bringing together the best of both DevOps and Jenkins, but we’ve extended all of the learning opportunities for IT practitioners across the globe by introducing our first conference in Europe—in Nice, France, in October. Similar to what we’ve created in San Francisco, we’re hoping the event provides many opportunities for attendees to learn, network and explore in order to optimize their DevOps initiatives.

    Gilmore: What can attendees expect from this year’s event?

    Labourey: With the new name and additional location, attendees will get even more out of DevOps World | Jenkins World 2018. We’ll be hosting more than 70 sessions at the San Francisco conference and more than 50 in Nice, covering a variety of DevOps and Jenkins topics from security, pipeline automation, containers, DevOps adoption and continuous delivery best practices. Additionally, the workshops and training that precede the conference offer attendees the opportunity to get certified as a DevOps practitioner or Jenkins Certified Engineer, deploy applications to a Kubernetes cluster, learn how to get the most out of Jenkins Pipeline and also do a deep dive into what’s coming with Jenkins X.

    We have some amazing keynotes lined up for both conferences. Kohsuke Kawaguchi, CTO at CloudBees and Jenkins founder, will provide an update on the latest and greatest of Jenkins which is always cool to hear. Dr. Nicole Forsgren, CEO and chief scientist at DORA, will take the stage in San Francisco, sharing her insights into the key leadership, technical, architectural and product capabilities that drive positive outcomes based on the “2018 State of DevOps Report.” In Nice, you can catch James Governor, analyst and co-founder of RedMonk, who will be discussing why he’s devoted to putting developers first. Christina Noren, chief product officer at CloudBees, and I will also be keynoting in both locations.

    Here’s a glimpse of some of the conference sessions on the agenda:

    • Measuring and Quantifying DevOps Outcomes
      Panel discussion led by Chris Condo, Forrester
    • Mission Possible: Eliminating DevOps Security Roadblocks
      Jason Vanderhoof, CyberArk
    • Managing Hundreds of Jenkins Instances at the Eclipse Foundation
      Mikaël Barbero, Eclipse Foundation
    • Delivering Enterprise Architectures: Perspectives from Duke Energy and Wolters Kluwer
      Dwayne Culbertson, Duke Energy
      Harris Kirk, Wolters Kluwer
    • The Build That Cried Broken: Building Trust in Your Continuous Integration Tests
      Angie Jones, Twitter

    Gilmore: What are you looking forward to the most about DevOps World?

    Sacha Labourey: Jenkins World, and now DevOps World, is always the highlight of the year for me. I am excited to meet and learn from so many innovators in the DevOps industry and amongst the CloudBees’ partner ecosystem. The process of software delivery is in an era of rapid growth and tremendous innovation. In the last year, we’ve seen the rise of Kubernetes, more and more a desire for actionable metrics to measure the DevOps initiatives that have been adopted, and DevSecOps is coming on stronger than ever. This has inspired us to create expanded learning opportunities at DevOps World | Jenkins World 2018 that reflect the interests of people within the industry so that we can continue to foster learning and the advancement of software delivery. I’m thrilled to see this come to life every year—and proud that CloudBees and our sponsors make it all happen.

    I’m especially looking forward to hearing some of the cloud native sessions, since that’s a newer topic this year. We also have put together several DevOps experience panels from real-world practitioners who will be sharing their successes in the field—and maybe even more importantly, their failures. We learn the most from failure and sharing those experiences can help others avoid doing the same things.

    With two events this year, it means the DevOps World | Jenkins World fun will extend further into the fall! I hope devopsy.kinsta.cloud readers will join us in San Francisco or Nice. If they do, they can get 20 percent off their registration using the devopsy.kinsta.cloud special code: JWDEVOPSCUST

    — Heidi Gilmore

  • DevOps Abandonment: Reasons Not to Give Up

    DevOps Abandonment: Reasons Not to Give Up

    The Never-Ending Story

    When a new process or methodology comes along—particularly when one gets a lot of attention like DevOps has—there always will be failures. I’m not talking about those always-present group of people who say they’ve seen this cycle before and, thus, it is just a fad; I’m talking about actual implementers who, in the end, come up empty-handed.

    DevOps is no exception. In fact, because it radically changes much about IT, it probably has a higher rate of this problem than most new methodologies.

    The end result is easy enough to identify: Either an organization abandons DevOps altogether or shunts it off into that area where other processes and technologies have been implemented by only one team and eventually die.

    Problem Children

    In almost every case of DevOps failure, people are the problem. That is not to say people purposely undermine the system, but IT is built, managed and run by people. And the breadth of people in an organization has immense influence on the success or failure of DevOps (or any other IT initiative).

    With that said, let’s look at some problems that contribute to DevOps abandonment organizations should avoid in their attempts to evaluate/implement DevOps.

    Team Isolation

    It is a standard enterprise reaction to split off a team to look at a new technology/process and isolate them from the rest of IT. I was the first hire in a “New IT” at an organization—it was weird to have rooms of cubicles filled with people I was not allowed to talk to. One of several keys to success in DevOps is communication, and no application or application portfolio works in a vacuum. The need to discuss server space, security, routing and a host of other topics with core IT means isolation will not work. It is one thing to clear the pilot team’s workload to allow them to focus on assessing DevOps for the organization, but it is quite another to isolate them (functionally, geographically, whatever). If they find some quick-hit streamlining opportunities in standard operations, don’t you want those shared with the wider IT department?

    Getting the Tools Side Right, but Missing the Culture Side

    I make no secret about the fact that I’m a bigger fan of the automation side of DevOps than the culture side. But sooner or later, all the whiz-bang tools are deployed, and culture becomes the main focus. That includes not only communications between different parts of the DevOps team, but also the “can jump in and do” mentality that is more prevalent in DevOps than in a more divided IT environment. Getting the culture and communications down early is important for success. And success is important for wider gains in IT’s ability to meet the demands of the business.

    Adding to the Workload of Overloaded Team Members

    This is perhaps the most common pitfall that causes organizations to leave DevOps or minimize their exposure to DevOps practices. DevOps holds the promise of increased productivity and decreased backlog. But it is a promise. Implementing tools and forging new relationships and new paths of communication … these things take time. And that time is added to existing workloads, unless steps are taken to lighten existing workloads.

    The team working 10 to 12 hours a day just keeping the lights on will not side-track into anything that requires a definite investment of more man-hours unless it is mandated to them by the business. Asking them to start working on it is a recipe for failure; the best you can hope for is some automation that makes their life easier in some other way.

    Not Managing/Meeting the Expectations of Various Leaders

    What line of business (LoB) leaders and the CIO expect out of DevOps are different things. While vaguely similar—increased responsiveness to business needs is normally 100 percent shared—the details show different concerns.

    It is up to the CIO to manage what those under him in IT expect/demand from DevOps, and what those peers in the line of business expect from it. There is no reduction in commitment from LoB teams—indeed, one could argue there is an increase, as IT is no longer the bottleneck. And, perhaps most importantly for some organizations, DevOps doesn’t make IT mind readers any more than previous new methodologies did. The LoB still must define what is needed and get requirements into IT.

    Trying or Retrying DevOps? A Few Tips

    Pilot

    Run a pilot project. Lighten the load of the project team so members can focus on DevOps and bring its value into the team. Do not isolate them in any way. Including other teams by asking for help/ideas should be encouraged. In fact, if the pilot team is motivated and enjoying the pilot, this type of interaction can help smooth the way for extension of DevOps to the wider organization.

    Use Existing Resources/Management

    Don’t bring in specialists to do DevOps. DevOps can be learned, and there are a ton of resources available, so use people who know your environment and can apply standardized tools and practices to it. That includes management. The last thing an organization should have in a pilot is a manager that knows DevOps but not the relationships within and special quirks of your organization—both technical and social.

    Pick Your Pilot Carefully

    Pilot a project that is relatively small but is visible to the organization. Actively manage expectations, and see where DevOps takes you.

    Rethink Everything

    Empower the team to look critically at every single process/workflow and see where the most gain can be had. DevOps is not a switch; prioritizing high-value/important items for change in this iteration and lower-value items for future iterations is part of the process. But if you don’t look at everything, you can’t guarantee you’re getting the most bang for your buck on this—or any—iteration.

    Clearly Communicate Goals/Changes

    Make sure everyone in IT and out understands what the pilot is testing. Is it increased time to market? Is it ability to apply tools and processes to intractable sub-projects? Is it a test of the benefits touted by talking heads? Communicate what you are measuring and how you’re measuring it. If possible, share a dashboard showing those measurements with everyone who cares to follow along.

    This Time is Different

    DevOps is different from any other new methodology that has gained traction for the operations side. Ever. I’d say it was different than any other new methodology at all, but Agile is the precursor to DevOps on the Dev side, and they share a lot. It challenges decades-old thoughts on the best way to do things. It will fail sometimes, for a variety of reasons. Give it the best chance for success that you can, don’t tie the pilot team’s hands and use it where it succeeds, even if it doesn’t include every project in the portfolio.

    In the end, if it really does help the business succeed, then—like it or not—it is the right tool for the job.

    — Don Macvittie

  • DevOps TV: DOES18 London Video Panel Roundup

    DevOps TV: DOES18 London Video Panel Roundup

    The DevOps Enterprise Summit is one of my favorite places to connect with the world’s best technologists and DevOps practitioners. It’s the perfect forum for insightful conversations, valuable networking and immersive learning—and the comraderie is unmatched. For me, it’s always a pleasure to catch up with my great friends in DevOps and get an insider’s perspective from the leaders who are driving the industry and practices forward.

    This past June, DevOps Enterprise Summit London (DOES18) did not disappoint. We experienced firsthand some of the most iconic business transformation stories in DevOps. We also heard from the best technologists in the business. The programming committee introduced new themes and brought in fresh perspectives that reach beyond Dev and Ops. We got to see how the technology value stream influences the entire business from the standpoint of those impacted the most.

    Once again, devopsy.kinsta.cloud partnered with IT Revolution and DOES18 organizers for in-depth video panel conversations with the speakers and thought leaders. Next-generation ops and infrastructure, spanning the divide between tech and business, DevSecOps and experience reports were all topics of conversation at this year’s show. We talked about challenges, opportunities and what the future is going to look like for DevOps. Here are the highlights from the videos we shared on DevOps TV.

    Where are They Now?

    One of the things I look forward to most at DevOps Enterprise Summit (DOES) is reconnecting with leaders who have shared their DevOps journeys and experiences from the early days. These companies can act as the compass for those that are just starting IT transformation journeys. At DOES, we learn where these industry pioneers are headed, the ups, the downs and what they are working on/need help with next. For example, we continued the conversation with Jonathan Fletcher at Hiscox, whose DevOps journey has been incredible to follow. The Verizon team, who presented on Day, 2 sat down with me and talked about the long lasting effects their DevOps transformation has had on such an extremely large and already successful company. Last, but not least, representatives Capital One chronicled their DevOps transformation journey and their march toward high performing teams across the organization.

    DevOps Right Now

    If you want the scoop on where DevOps stands today, DOES is the place to be. I enjoyed the conversation I had with DevOps thought leader and author, Mirco Hering, who shared invaluable knowledge on the current state of DevOps. We also sat down with Ilkka Turunen, Zane Lackey and Margo Cronin to take a deep dive into one of today’s hottest topics: DevSecOps. Examining value streams of high performing companies was also top of mind and it was interesting to hear how adjusting that value depended on the changing needs of the customer. Nicole Bryan, Carmen DeArdo, Dominica DeGrandis, Mik Kersten and I had an insightful discussion about this topic.

    ITSM and DevOps Can Be Friends

    Whether you were a skeptic of ITSM or DevOps in the early years, it’s likely you didn’t predict that they would be compatible. We had a great conversation with the fantastic Jayne Groll, Rob England and Dr. Cherry Vu around ITSM, ITIL and DevOps—and how DevOps and ITSM can actually complement each other.

    Next Gen Operations and Infrastructure

    Gene Kim and the programming committee worked hard to make next-generation ops and infrastructure a big theme at this year’s conference by seeking some of the sharpest talents in this arena. We had the amazing opportunity to interview John Willis, Damon Edwards and Cornelia Davis to talk about where ops is headed.

    Spanning the Tech and Business Divide

    As I mentioned earlier, DOES18 examines how the technology value stream goes far beyond just Dev and Ops. We looked at its impact on HR, project management and more—and how DevOps applies to leadership these other areas of the organization. I had the pleasure of sitting down with Fin Goulding, Jelena Laketic and Mark Schwartz to discuss the role that IT leaders should play in a successful DevOps transformation and what things are of value when injecting high performance into a company. I also reflected on the different business organization strategies used to turn normal companies into high performers and common problems that can be overcome on that journey with Jon Smart, Morag McCall and Tom Clark.

    Competitiveness and DevOps

    If your organization isn’t constantly adapting to out compete the competition, regardless of whether you are practicing DevOps, you may have already lost. Jennifer Wood and Chris Hill stopped by to discuss the need for companies struggling to compete in their industries to adopt DevOps practices. We also got to get a glimpse into their own company’s transformation efforts as well. One industry in particular that is facing disruption is financial services. I was lucky enough to sit down with two high-profile finance based IT leaders, Shaun Norris and Nick Funnel, to engage in a discussion on the evolution of DevOps in their industry and the direction of DevOps in the future as technology continues to evolve for finance.

    Las Vegas is Around the Corner

    There are plenty more videos to check out on DevOps TV from DOES18 London and recordings of the onstage presentations at the conference as well. You can also view the PowerPoint slides here.

    I look forward to connecting with all my DevOps friends again at DOES18 USA in Las Vegas this October!

    — Alan Shimel