As we settle into the dog days of summer, it can be a good time to take a step back and examine some of the bigger trends in the industry and examine how we can take advantage of emerging technologies to gain new advantage. Doing just that this week was SDXcentral who released the findings of two separate studies on Containers and Cloud Security and Forrester research who issued its list of The Top Emerging Technologies To Watch in 2018.
According to recent research from SDxCentral, Scaling Clouds – Infrastructure Orchestration and DevOps at Scale, security remains a top concern among enterprises adopting public cloud. In fact, 62% of those surveyed listed “compliance and security issues” as the number one concern. Rounding out the list of challenges were “cost management” (46%), “lack of visibility into underlying performance” (44%) and “predictability of costs” (41%).
Yet, these challenges aren’t keeping the majority of organizations from moving to public cloud. Whether they’ve standardized on a single cloud vendor or have taken a hybrid approach, 64% say they use DevOps tools. Not surprising to our DevOps team are the findings that the most used solutions are Ansible (50%), Puppet (29%) and Chef (21%). In line with the calls we’re receiving as well is SDXcentral’s finding that CI/CD methods and tools are hitting a tipping point with 58% of respondents reporting they’ve adopted these modern development practices.
The takeaway: Odds are likely that your peer group is moving quickly to adopt DevOps tools and methodologies as well as methods like CI/CD. While these approaches help grow development throughput, speed time to market, and more, they are a natural place to start an IT modernization conversation for competitive advantage.
In a separate report from SDxCentral, Container Infrastructure – What You Need to Know in 2018, the publisher found that while containers can be beneficial, deployment challenges still exist. Indeed, the primary barrier remained the same from last year’s survey: provisioning persistent storage, which they note is connected to the broader challenge of integrating containers into existing IT environments.
At Flux7, we recently worked with a large American carrier who was challenged to use KOPS to Run Kubernetes with CIS Benchmark AMIs. The challenge in this is that KOPS assumes the use of a vanilla (non-CIS benchmarked) AMI. You can read the full case study with technical solution here.
Top Emerging Technologies
Last, Forrester announced this week its list of Top 12 Emerging Technologies that should be on everyone’s radar. Broken into four categories -- Physical/Digital, New Compute Paradigm, Digital Ecosystem and AI -- enterprises should start researching and exploring these technologies today. Why? Forrester notes that the pace of technology and innovation is accelerating so quickly that enterprises need to shoot further ahead to avoid getting run over. “We think that by the time something like that [quantum computing] gets here, if you aren’t ready, you could get run over,” said Brian Hopkins, VP/Principal Analyst.
The takeaway: According to the report, implementing new technology is the leading action businesses are taking to change their models. So, to stay ahead of the competition, CIOs should look to implement new forms of technology into their strategies, especially emerging tech, in ways that they can pair these technologies to build on and accelerate one another for exponential gain.
A few things caught the eyes of our DevOps team:
- Amazon announced Bring Your Own IP for Amazon Virtual Private Cloud, a preview. The news is that Amazon VPC now allows you to use your own publicly-routable IP addresses with AWS resources such as EC2 instances, Network Load Balancers, and NAT Gateways. After you bring your IPs to AWS, AWS will advertise your public IP addresses on the Internet. You will continue to have access to Amazon IP addresses and can choose to use your own IP addresses, Amazon’s IP addresses, or both with your AWS resources.
This new feature is helpful when migrating applications to AWS that rely on IP address reputation, such as specific partner apps, or for commercial email services that rely on IP address reputation to allow traffic from your endpoints to reach intended recipients.
- Our DevOps consulting team also enjoyed this Jenkins blog about Abhishek Gautam’s prjoect: Pipeline as YAML: Alpha release. This project aims to develop a pull request Job Plugin, allowing users to configure job type using YAML file placed in root directory of the Git repository being the subject of the pull request. The plugin should interact with various platforms like Bitbucket, Github, Gitlab, etc whenever a pull request is created or updated.
The plugin detects the presence of certain types of reports at conventional locations, and publishes them automatically. If the reports are not present at their respective conventional location, the location of the report can be configured in the YAML file. This simplifies the pull request build process, with build reports automatically published to Github, Bitbucket, etc, and status updates sent to git servers automatically.
- Last, our DevOps team liked this YouTube video from HashiCorp co-founder and CTO Armon Dadgar who gives a brief, whiteboard overview of a typical four-stage Terraform adoption journey.
DevOps Adoption Series
After a brief hiatus, the AWS consulting team continues its DevOps blog series on DevOps adoption, which started with a discussion of what motivates organizations to begin an IT modernization project. We last featured AWS Cloud Migration Strategy: Replatform vs Refactor. Subscribe to our DevOps blog to make sure you get the whole series.