Welcome!

DevOps Journal Authors: Elizabeth White, Pat Romanski, Mike Kavis, Roger Strukhoff, Yeshim Deniz

Related Topics: DevOps Journal, Virtualization, Cloud Expo, SDN Journal

DevOps Journal: Blog Feed Post

Puppet Supported

It's an application world; a world that is rapidly expanding

It's an application world; a world that is rapidly expanding. With new opportunities and markets arising driven by mobility and the Internet of Things, it is only going to keep expanding as applications are deployed to provision, license, and manage the growing sensors and devices in the hands of consumers.

Applications are not isolated containers of functionality. No application winds up in production without a robust stack of resources and services to support it. Storage and compute, of course, are required, but so are the networking - both stateless and stateful - services that provide for scale, security and performance.

the app deployment stackUltimately this places a significant burden on operations and networking teams to provision and configure services faster and more frequently and with fewer errors that disrupt deployment timelines or result in undesirable downtime.

Increasingly operations (and sometimes networking) teams are turning to DevOps to achieve consistent, predictable and repeatable application deployments by leveraging automation and orchestration to meet application deployment expectations.

CPR-devopsOne of the forerunners of frameworks designed to automate and orchestrate application provisioning and deployment is Puppet Labs. No stranger to DevOps, Puppet has focused primarily on establishing a solid and yet flexible foundation for deploying the compute infrastructure required to deploy and ultimately scale an application in production.

But once you're finished with the compute, you aren't done. Applications require storage and networking, and if you're only rapidly deploying one of the three, you're missing out on the lion's share of the benefits. While the focus of Puppet has been primarily on the compute component of the application deployment stack, there's nothing that prevents storage and networking from also being automated and orchestrated via Puppet. No surprise, then, that many platforms have freely available Puppet plug-ins, and F5 is no exception.

Puppet itself is freely available and community supported, but like other open source-based solutions it also has a commercial, enterprise-grade offering. And while the free version of Puppet has supported the entire application deployment stack through community-developed plug-ins, its commercial offering was hitherto officially focused on just compute.

That changed with the announcement of PuppetSupported.

Virtualization and cloud have long held out the promise of faster and more efficient deployments, but network and storage management have not kept up with IT system management, when it comes to automation. The challenges network and storage admins face are very similar to those sysadmins have long dealt with — manual, error-prone processes, ticket proliferation, a growing backlog of technical debt, and the inability to realize the full benefits of cloud and virtualization.

Puppet Labs has always been about helping sysadmins free themselves of the work that computers actually do better, so they can do the work that people do best: analyzing metrics and applying their learning to make IT better serve business needs. Puppet Supported is our next step toward helping all admins, and promoting better collaboration between different technical teams. With Puppet Enterprise automating all the layers in the data center, admins will be able to design their companies’ technology strategies to better meet customer demand and adapt quickly to ever-shifting market conditions.

What does that mean? it means officially supported Puppet modules for provisioning, configuring and managing F5 services in an enterprise-class environment. Initially support will focus on the stateful L4-7 services critical to modern data center architectures requiring elastic scalability.

We're excited to be a part of PuppetSupported, not only because customers will enjoy the benefits of automation and orchestration of the network, but also because we see this move as embracing the network as a first class citizen in its framework for operationalizing application deployments as critical for organizations to realize a fully operationalized data center.

Read the original blog entry...

More Stories By Lori MacVittie

Lori MacVittie is responsible for education and evangelism of application services available across F5’s entire product suite. Her role includes authorship of technical materials and participation in a number of community-based forums and industry standards organizations, among other efforts. MacVittie has extensive programming experience as an application architect, as well as network and systems development and administration expertise. Prior to joining F5, MacVittie was an award-winning Senior Technology Editor at Network Computing Magazine, where she conducted product research and evaluation focused on integration with application and network architectures, and authored articles on a variety of topics aimed at IT professionals. Her most recent area of focus included SOA-related products and architectures. She holds a B.S. in Information and Computing Science from the University of Wisconsin at Green Bay, and an M.S. in Computer Science from Nova Southeastern University.

Latest Stories from DevOps Journal
Achieve continuous delivery of applications by leveraging ElasticBox and Jenkins. In his session at DevOps Summit, Monish Sharma, VP of Customer Success at ElasticBox, will demonstrate how you can achieve the following using ElasticBox and the ElasticBox Jenkins Plugin: Create consistency across dev, staging, and production environments Continuous delivery across multiple clouds to handle high loads Ensure consistent policy management across environments: tagging, admin boxes, traceability Spin up machines and environments quickly Deploy applications to any cloud Enable real-time collaboration between developers and operations
Docker offers a new, lightweight approach to application portability. Applications are shipped using a common container format and managed with a high-level API. Their processes run within isolated namespaces that abstract the operating environment independently of the distribution, versions, network setup, and other details of this environment. This "containerization" has often been nicknamed "the new virtualization." But containers are more than lightweight virtual machines. Beyond their smaller footprint, shorter boot times, and higher consolidation factors, they also bring a lot of new features and use cases that were not possible with classical virtual machines.
High performing enterprise Software Quality Assurance (SQA) teams validate systems are ready for use – getting most actively involved as components integrate and form complete systems. These teams catch and report on defects, making sure the customer gets the best software possible. SQA teams have leveraged automation and virtualization to execute more thorough testing in less time – bringing Dev and Ops together, ensuring production readiness. Does the emergence of DevOps mean the end of Enterprise SQA? Does the SQA function become redundant?
WaveMaker CEO Samir Ghosh is taking a new pass at aPaas, and leveraging the increasingly popular Docker open-source platform, with the announcement of WaveMaker Enterprise. The new version of the company's eponymous software “enables instant, end-to-end custom web app creation and management by professional and non-professional developers (alike) and development teams,” according to the company. We asked Samir a few questions about this, and here's what he had to say: Cloud Computing Journal: You've mentioned the previous challenge of business-side developers making that jump from design to deployment. What sort of learning curve will they still face with Wavemaker Enterprise? Samir Ghosh: “Business-side developers” can include non-programming business users or professional developers under tight schedules or with limited mobile or front-end programming expertise. Both can use WaveMaker to meet their app development needs, but may have different deployment needs. I think business users just want their app to run as easily as possible. In WaveMaker, they can literally click a button and their application will run, either on our public cloud or on the enterprise’s private...
The old monolithic style of building enterprise applications just isn't cutting it any more. It results in applications and teams both that are complex, inefficient, and inflexible, with considerable communication overhead and long change cycles. Microservices architectures, while they've been around for a while, are now gaining serious traction with software organizations, and for good reasons: they enable small targeted teams, rapid continuous deployment, independent updates, true polyglot languages and persistence layers, and a host of other benefits. But truly adopting a microservices architecture requires dramatic changes across the entire organization, and a DevOps culture is absolutely essential.
Leysin American School is an exclusive, private boarding school located in Leysin, Switzerland. Leysin selected an OpenStack-powered, private cloud as a service to manage multiple applications and provide development environments for students across the institution. Seeking to meet rigid data sovereignty and data integrity requirements while offering flexible, on-demand cloud resources to users, Leysin identified OpenStack as the clear choice to round out the school's cloud strategy. Additionally, the school sought a partner to provide OpenStack infrastructure deployment and operations expertise. They ultimately selected Blue Box’s Private Cloud as a Service, powered by OpenStack, leveraging Blue Box's Zurich, Switzerland data center.
In a world of ever-accelerating business cycles and fast-changing client expectations, the cloud increasingly serves as a growth engine and a path to new business models. Dynamic clouds enable businesses to continuously reinvent themselves, adapting their business processes, their service and software delivery and their operations to achieve speed-to-market and quick response to customer feedback. As the cloud evolves, the industry has multiple competing cloud technologies, offering on-premises and off-premises cloud platforms for both Infrastructure as a Service (IaaS) and Platform as a Service (PaaS). In parallel, cloud standards are also evolving, including community standards like OpenStack and CloudFoundry. Most organizations who are adopting the Cloud today are ending up adopting it in complex ‘dynamic-hybrid’ environments. There is physical infrastructure that now co-exists along with the new dynamic-hybrid on-premises and off-premises Cloud hosted environments.
This story came in from Joseph – one of our fellow dynaTrace users and a performance engineer at a large fleet management service company. Their fleet management software runs on .NET, is developed in-house, is load tested with JMeter and monitored in Production with dynaTrace. A usage and configuration change of their dependency injection library turned out to dramatically impact CPU and memory usage while not yet impacting end user experience. Lessons learned: resource usage monitoring is as important as response time and throughput. On Wednesday, July 3, Joseph’s ops team deployed the latest version into their production environment. Load (=throughput) and response time are two key application health measures the application owner team has on their production dashboards.
The recent trends like cloud computing, social, mobile and Internet of Things are forcing enterprises to modernize in order to compete in the competitive globalized markets. However, enterprises are approaching newer technologies with a more silo-ed way, gaining only sub optimal benefits. The Modern Enterprise model is presented as a newer way to think of enterprise IT, which takes a more holistic approach to embracing modern technologies. This model makes use of Composable Enterprise framework put forward by Jonathan Murray of WMG.
Software development, like manufacturing, is a craft that requires the application of creative approaches to solve problems given a wide range of constraints. However, while engineering design may be craftwork, the production of most designed objects relies on a standardized and automated manufacturing process. By contrast, much of moving an application from prototype to production and, indeed, maintaining the application through its lifecycle has often remained craftwork. In his session at DevOps Summit, Gordon Haff, senior cloud strategy marketing and evangelism manager at Red Hat, will discuss the many lessons and processes that DevOps can learn from manufacturing and the assembly line-like tools, such as Platform-as-a-Service, that provide the necessary abstraction and automation to make industrialized DevOps possible.