Palo Alto Networks made the most of a short week by announcing its plan to acquire container security company Twistlock for $410 million. It also announced plans to acquire serverless security company PureSec and launched Prisma, its new cloud security service. With cloud and container security top of mind for many, the acquisitions will prove to be valuable assets as enterprises seek to build security in.
Wonder how your DevOps efforts compare to others in the industry? Atlassian recently surveyed 500 software development and IT professionals about their tools and practices and released seven key findings from their research. Namely, the average respondee uses 3.3 different tools to unearth the status of a project (the company notes that for Jira users, it’s a mere 2.3); a full three-fourths of dev teams face bugs, defects, or delays at release; 71% of teams who use microservices report that it’s easier to test or deploy features; and 47% of teams ship changes and receive customer feedback faster with a CI/CD cloud solution.
A new report from Synergy Research Group reveals that Q4 2018 spending on cloud infrastructure services grew 45% over the year prior, resulting in a full-year growth rate of 48% for 2018. Synergy notes that Amazon continues to move its market share upwards and remains equivalent in size to its next four competitors combined.
With competitive pressures demanding organizations innovate and bring new products and services to market faster, we’re seeing more and more enterprises moving to the cloud for IT modernization that maximizes the benefits of DevOps automation. Interestingly, Chef this week shared results of a recent survey it conducted finding a dramatic shift to the cloud among its survey respondents.
We have been working closely with a customer who is undergoing a business transformation. As a multimedia equipment manufacturer, the organization has a loyal following of its high quality devices. However, like many companies facing the convergence of markets and new customer demands, the company has embarked on a metamorphosis. Traditionally very focused on hardware, their software was largely ignored even though it offered customers real value. Part of the company’s transformation was a move to treat their software like a full-fledged offering, rather than a free supplement. An upcoming product release marked the first (and biggest steps), in cementing this change in company direction.
In our last year in review blog, we took a look at how to best use new features and tools to streamline DevOps processes like Continuous Integration and Continuous Delivery (CI/CD). Today we are turning our attention to another topic that garnered a lot of interest this year, Configuration Management.
At this year’s re:Invent, Flux7’s CEO, Aater Suleman, had the great pleasure of presenting with Hemanth Jayaraman, Rent-A-Center’s director of DevOps. (You can watch the full presentation here.) We shared with the audience the story of how we worked with Rent-A-Center to help them address their challenge to architect, deploy, and manage a mission-critical SAP Hybris ecommerce platform that could scale to 6+ million users a month.
In our last article, we took a look at how marrying Ansible and AWS makes a great deal of sense for DevOps enterprises and discussed eight specific ways Ansible helps create greater efficiency and effectiveness for AWS deployments. Today we will dive into the recently refactored Ansible to discuss its newest features and how they can further help bolster your AWS efforts. In addition, Ansible likes to bill itself as “batteries included”. As a result, we will also review the new "batteries" or modules that are available with the release of Ansible 2.0.
In our last blog post, we discussed how Ansible’s configuration management tools can benefit Amazon Web Services (AWS) environments – especially for DevOps focused organizations. Today we’d like to share how to realize those benefits with Ansible Playbooks.
Playbooks are Ansible’s configuration, deployment, and orchestration language. Keeping in line with Ansible’s focus on simplicity without sacrificing security and reliability, Playbooks purposefully have a minimum of syntax because they aren’t meant to be a programming language or script, but rather a model of a configuration or a process.
One of the key benefits of cloud computing is the opportunity to replace up-front capital infrastructure expenses with low variable costs that scale with your business. And, while it is easy to quickly spin up hundreds or thousands of new servers in minutes with Amazon Web Services (AWS), it’s much more difficult to ensure that those new machines are configured appropriately. Enter the marriage of configuration management tools and AWS.
Ansible is an IT automation tool that provides continuous deployment capabilities and zero downtime rolling updates. It’s simplicity, agentless features, and scalability is what makes it stand out. In this post, let’s discuss some common terms used in Ansible to get a better grasp of this tool.