Presentation to the Perth MS Cloud Computing User Group on November 14, 2017. Covered off on how Chef, InSpec, Habitat and Chef Automate work with Windows, Azure and the Microsoft ecosystem.
Infrastructure and Compliance Delight with Chef AutomateMatt Ray
The document discusses Chef Automate, a platform for continuous automation, infrastructure automation, compliance automation, and application automation. It describes how Chef Automate can help increase development speed, improve efficiency, and decrease risk by defining infrastructure, applications, and compliance rules as code. It provides an example workflow of how Chef Automate can enable the continuous compliance process of scanning for compliance, building and testing locally and in CI/CD, remediating issues, and verifying compliance. Finally, it summarizes how Chef Automate supports the entire journey from detecting compliance issues to correcting them to automating continuous detection and correction.
DevOpsDays Singapore - Continuous Auditing with Compliance as CodeMatt Ray
This document discusses using Chef Automate to enable continuous compliance through a three step process of detecting issues, correcting problems, and automating compliance. It notes that many organizations currently assess compliance inconsistently or after deploying code to production. Chef Automate allows detecting and correcting issues across infrastructure in a single platform using the same language for both DevOps and InfoSec teams. This enables deploying applications with confidence while maintaining security and compliance.
Chef Automate provides a full-stack collaboration platform to help organizations achieve DevOps success by managing infrastructure, containers, applications, and compliance through automation. It addresses barriers to DevOps adoption like disparate tooling and lack of skills/cultural adoption. New capabilities in Chef Automate and Compliance accelerate and de-risk adoption by providing automation, governance, and compliance as code.
InSpec is an open source testing framework for infrastructure with a human-readable language for specifying compliance, security, and other policy requirements. Easily integrate automated tests that check for advherence to policy into any stage of your deployment pipeline.
Chef Automate - Wellington DevOps August 2, 2017Matt Ray
Chef Automate is a platform that provides continuous automation for infrastructure, compliance, and applications. It allows users to define infrastructure, compliance policies, and application configuration as code. It also provides workflows to collaborate, build, deploy, manage, and secure automation through an integrated platform. Chef Automate utilizes open source automation engines and works with technology partners and AWS OpsWorks to provide these capabilities at scale across environments.
Compliance Automation with InSpec
InSpec is an open source testing framework for infrastructure with a human- and machine-readable language for specifying compliance, security, and policy requirements. Using a combination of command-line and remote-execution tools, InSpec can help you keep your infrastructure aligned with security and compliance guidelines on an ongoing basis, rather than waiting for and then remediating from arduous annual audits. InSpec’s flexibility makes it a key tool choice for incorporating security into a complete continuous delivery workflow, reducing the risk of new features and releases breaking established host-based security guidelines. This talk covers the basics of working with InSpec, writing tests to reflect your organization’s security guidelines, and managing InSpec as part of a high-velocity workflow.
Effective Testing with Ansible and InSpecNathen Harvey
Ansible is an incredibly easy way to manage infrastructure and configuration. But what's the best way to ensure the changes to your Ansible playbooks have the intended outcome and do not introduce unwanted changes? And how can you verify your your playbook changes do not negatively impact the compliance status of your infrastructure?
In this session, we will learn about InSpec and how it's incredibly easy-to-read language allows for integration and compliance requirements to be expressed as code. We will look at how Test Kitchen and InSpec can be used to validate your Ansible playbooks and empower developers to test for compliance earlier in the development cycle. Additionally, we will also explore how to use and modify InSpec profiles created by others.
Chef Automate - Infracoders Canberra August 8, 2017Matt Ray
Slides from the overview and demo of Chef Automate from Canberra Infracoders.
https://www.meetup.com/Infrastructure-Coders-Canberra/events/241775704/
Using Habitat to Unify Dev to CI to Production - Configmgmt Camp Feb/2018 GentSalim Afiune Maya
This talk is about the journey of a developer that starts working in a company (day one) and goes through the process from getting her computer setup all the way until she makes her first contribution to an application in production.
We will talk about Habitat, a tool to build, deploy, and manage applications. We will explain what is the Habitat Studio and the benefits of doing development in it and how we can leverage it to unity our application workflow.
Find here a recording of the demo: https://asciinema.org/a/160762
Here are the steps to run a compliance scan:
1. Click the checkbox next to your node.
2. Select the "cis-3.1" profile from the dropdown menu.
3. Click the "Scan Now" button.
4. The scan will run and you'll see the status change to "Scanning".
5. Once complete, the status will change to "Compliant" or "Non-Compliant" and you can view the detailed results and any failures/warnings.
Let me know if you have any other questions!
The document discusses Habitat, an open source tool for automating the packaging, deployment, and management of applications. It describes how Habitat packages applications and all of their dependencies into artifacts called "packages" that can run on any Linux system. It also explains how Habitat uses supervisors to deploy packages, form service groups, and provide update strategies and REST APIs for managing applications in a continuous delivery model.
This document discusses how Chef configuration management is used centrally at Sky Betting and Gaming to provide tools and services for developers to deploy applications. It describes how the Platform Services team started by "fixing disaster recovery" and introduced Chef. Key aspects of their process include using Chef configuration for infrastructure, applications, CI pipelines, and integration tests. The document also outlines their use of a tool called pscli, which acts as "glue" by pulling Docker images containing tools like ChefDK, Terraform, and Packer and executing commands in containers to perform tasks like generating cookbooks, running Kitchen tests, and applying Terraform configurations.
Chef Delivery provides a unified workflow for software development with fixed stages and phases for approving and delivering code changes. It ensures high velocity, safety, and visibility through automation of infrastructure as code, testing, and deployment. The shared pipeline can be used across projects and teams.
The document discusses remediating compliance issues by writing a remediation recipe on the target node to update the SSH version. It describes testing the recipe locally using Kitchen, verifying compliance with InSpec from the CLI, converging the recipe, and rescanning the node to ensure compliance. Key steps include generating a cookbook and server recipe for SSH, creating an SSH config template, updating the template, deploying locally, and re-running the compliance scan to show the issue is now resolved.
The document describes a conference agenda for ChefConf. It includes workshops, keynotes, technical sessions, and social events. It also discusses challenges faced by organizations around manual processes, legacy systems, silos, and infrequent releases. Finally, it outlines how Chef's tools and practices around automation, dynamic infrastructure, DevOps workflows, and continuous delivery can help address these challenges.
This document introduces Jon Aykroyd, an automation engineer with over 10 years of experience in Linux systems administration and automation. It provides an overview of Jon's background and role in helping organizations transition to DevOps practices. The document also shares a case study of how introducing Chef automation tools helped a clothing retailer reduce time-to-deployment from 2 weeks to just 2 hours. It closes with some details about Jon's initial work helping his own organization transition to Chef from various other tools and scripts.
Continuously serving the developer community with Continuous Integration and...Thoughtworks
Snap CI enables software teams to do Continuous Delivery (CD). When practicing CD, the goal is to automate the deployment process and build software in such a way that it can be deployed to production any time. As a deployment tool, Snap CI cannot have downtime. If it did, our users would not be able to deploy their own software. We had to change Snap CI’s architecture to ensure zero-downtime and we chose to do blue-green deployments to achieve it. In this approach, we had to maintain two instances of our system: one active instance, and one inactive instance. Based on our experiences, we will share some tricks of the trade from the numerous challenges we faced such as: making the application aware of whether it was active or inactive, handling data migrations, and babysitting long-running jobs.
These are the slides from Akshay Karle and Fernando Junior's presentation on Agile Brazil 2015.
The document discusses DevOps and infrastructure as code. It describes how using infrastructure as code allows organizations to automate infrastructure provisioning and management. This enables continuous delivery of applications and infrastructure through a unified software development pipeline. Chef is presented as a tool that can help implement such a DevOps approach through its support for infrastructure as code, compliance automation, and a shared development workflow.
This document provides an overview of new features in Puppet Enterprise 2016.4, including improved change reporting, orchestration capabilities, container support, and integrations with VMware vRealize Automation, Jenkins, and Microsoft Azure. It also highlights client tools for Windows and Mac, improved simulation reporting, faster node classification and visualization, and a live demo.
The document introduces Chef Delivery, which provides a shared workflow from code to customer. It features a unified pipeline with fixed stages and phases for approving, verifying, building, deploying, and testing changes. The workflow provides visibility, reliability, and safety for moving quickly from ideas to shipped software. It also allows visualization of changes and uses build cookbooks and APIs to automate deployments across a project's infrastructure.
This document provides an overview of Chef and its capabilities for infrastructure automation and deployment. It discusses how Chef works using infrastructure as code to define reusable resources and automate deployment. It also covers Chef's porting to Linux on POWER systems and partnership with IBM, including support for Chef on various IBM platforms. The document concludes with an advertisement for a demo of using Chef to automate application deployment on Linux on POWER.
In this session, we will learn about Teamcity CI Server. We will look at the different options available and how we can set a CI pipeline using Teamcity.
This document discusses the benefits of continuous integration. It describes the pain points of the previous system such as broken builds, manual testing and deployment. The new system uses a build server to continuously build every check-in. It also uses unit tests, automated deployment scripts, and pushes latest builds automatically to reduce errors and deployment time. The verdict is that build issues are now identified rapidly, regression tests provide higher confidence, deployments can be done by one person with no downtime and in only 6 minutes, and rollbacks are also quicker.
This document discusses continuous delivery fundamentals and how serverless platforms can help realize them. It covers topics like automated software releases through pipelines, building quality into products from the start, and how serverless handles infrastructure concerns so developers can focus on code. Examples are provided of using AWS Lambda, API Gateway, S3, Route53, CloudFormation, CodePipeline and other services to implement continuous delivery of serverless applications.
This document provides an agenda for a Chef Hack Day event hosted by Trace3 on April 26, 2016. The agenda includes times for lunch, welcome/kick-off, hacking sessions, and demo/wrap-up periods throughout the day. Guidelines are also listed for the hack day projects, encouraging teams to track work, share demonstrations, ask for help, be open to learning, and have fun. Suggested hack day project ideas include using InSpec to verify CIS Benchmarks and scanning/remediating with Chef Compliance.
This document provides an introduction and overview of Puppet Enterprise:
- It begins with an agenda for the meeting including introductions, an introduction to Puppet Enterprise, a live demo, and a Q&A session.
- It discusses how Puppet Enterprise helps companies become great software companies by delivering experiences to users faster and more simply and securely.
- A live demo is then given showing how Puppet Enterprise works by defining configurations, simulating changes, enforcing configurations, and reporting on changes.
An overview of Chef Automate and the various resources for Chef, InSpec and Habitat for Azure and Microsoft's other products. Presented September 20, 2017 at Tank Stream Labs.
This document discusses challenges faced by organizations in managing their infrastructure and applications, and how Chef and related tools can help address those challenges. It outlines Chef's approach of treating infrastructure as code and using automation to enable continuous delivery of infrastructure and applications. This allows for faster innovation, better quality/compliance, and rapid time to value. Key aspects covered include infrastructure as code, automation of the development stack, enabling DevOps workflows, and integrating security and compliance into the software delivery pipeline.
Today, the development and operations landscape has shifted to a more collaborative model merging the two (DevOps). Developers need to know much more about the operational components of their software - especially around network programming, services development, and continuous deployment. Likewise, the developer's IT counterpart needs to know much more about development - especially around infrastructure automation (Chef/Puppet), automated testing, and continuous deployment.
Chef Automate - Infracoders Canberra August 8, 2017Matt Ray
Slides from the overview and demo of Chef Automate from Canberra Infracoders.
https://www.meetup.com/Infrastructure-Coders-Canberra/events/241775704/
Using Habitat to Unify Dev to CI to Production - Configmgmt Camp Feb/2018 GentSalim Afiune Maya
This talk is about the journey of a developer that starts working in a company (day one) and goes through the process from getting her computer setup all the way until she makes her first contribution to an application in production.
We will talk about Habitat, a tool to build, deploy, and manage applications. We will explain what is the Habitat Studio and the benefits of doing development in it and how we can leverage it to unity our application workflow.
Find here a recording of the demo: https://asciinema.org/a/160762
Here are the steps to run a compliance scan:
1. Click the checkbox next to your node.
2. Select the "cis-3.1" profile from the dropdown menu.
3. Click the "Scan Now" button.
4. The scan will run and you'll see the status change to "Scanning".
5. Once complete, the status will change to "Compliant" or "Non-Compliant" and you can view the detailed results and any failures/warnings.
Let me know if you have any other questions!
The document discusses Habitat, an open source tool for automating the packaging, deployment, and management of applications. It describes how Habitat packages applications and all of their dependencies into artifacts called "packages" that can run on any Linux system. It also explains how Habitat uses supervisors to deploy packages, form service groups, and provide update strategies and REST APIs for managing applications in a continuous delivery model.
This document discusses how Chef configuration management is used centrally at Sky Betting and Gaming to provide tools and services for developers to deploy applications. It describes how the Platform Services team started by "fixing disaster recovery" and introduced Chef. Key aspects of their process include using Chef configuration for infrastructure, applications, CI pipelines, and integration tests. The document also outlines their use of a tool called pscli, which acts as "glue" by pulling Docker images containing tools like ChefDK, Terraform, and Packer and executing commands in containers to perform tasks like generating cookbooks, running Kitchen tests, and applying Terraform configurations.
Chef Delivery provides a unified workflow for software development with fixed stages and phases for approving and delivering code changes. It ensures high velocity, safety, and visibility through automation of infrastructure as code, testing, and deployment. The shared pipeline can be used across projects and teams.
The document discusses remediating compliance issues by writing a remediation recipe on the target node to update the SSH version. It describes testing the recipe locally using Kitchen, verifying compliance with InSpec from the CLI, converging the recipe, and rescanning the node to ensure compliance. Key steps include generating a cookbook and server recipe for SSH, creating an SSH config template, updating the template, deploying locally, and re-running the compliance scan to show the issue is now resolved.
The document describes a conference agenda for ChefConf. It includes workshops, keynotes, technical sessions, and social events. It also discusses challenges faced by organizations around manual processes, legacy systems, silos, and infrequent releases. Finally, it outlines how Chef's tools and practices around automation, dynamic infrastructure, DevOps workflows, and continuous delivery can help address these challenges.
This document introduces Jon Aykroyd, an automation engineer with over 10 years of experience in Linux systems administration and automation. It provides an overview of Jon's background and role in helping organizations transition to DevOps practices. The document also shares a case study of how introducing Chef automation tools helped a clothing retailer reduce time-to-deployment from 2 weeks to just 2 hours. It closes with some details about Jon's initial work helping his own organization transition to Chef from various other tools and scripts.
Continuously serving the developer community with Continuous Integration and...Thoughtworks
Snap CI enables software teams to do Continuous Delivery (CD). When practicing CD, the goal is to automate the deployment process and build software in such a way that it can be deployed to production any time. As a deployment tool, Snap CI cannot have downtime. If it did, our users would not be able to deploy their own software. We had to change Snap CI’s architecture to ensure zero-downtime and we chose to do blue-green deployments to achieve it. In this approach, we had to maintain two instances of our system: one active instance, and one inactive instance. Based on our experiences, we will share some tricks of the trade from the numerous challenges we faced such as: making the application aware of whether it was active or inactive, handling data migrations, and babysitting long-running jobs.
These are the slides from Akshay Karle and Fernando Junior's presentation on Agile Brazil 2015.
The document discusses DevOps and infrastructure as code. It describes how using infrastructure as code allows organizations to automate infrastructure provisioning and management. This enables continuous delivery of applications and infrastructure through a unified software development pipeline. Chef is presented as a tool that can help implement such a DevOps approach through its support for infrastructure as code, compliance automation, and a shared development workflow.
This document provides an overview of new features in Puppet Enterprise 2016.4, including improved change reporting, orchestration capabilities, container support, and integrations with VMware vRealize Automation, Jenkins, and Microsoft Azure. It also highlights client tools for Windows and Mac, improved simulation reporting, faster node classification and visualization, and a live demo.
The document introduces Chef Delivery, which provides a shared workflow from code to customer. It features a unified pipeline with fixed stages and phases for approving, verifying, building, deploying, and testing changes. The workflow provides visibility, reliability, and safety for moving quickly from ideas to shipped software. It also allows visualization of changes and uses build cookbooks and APIs to automate deployments across a project's infrastructure.
This document provides an overview of Chef and its capabilities for infrastructure automation and deployment. It discusses how Chef works using infrastructure as code to define reusable resources and automate deployment. It also covers Chef's porting to Linux on POWER systems and partnership with IBM, including support for Chef on various IBM platforms. The document concludes with an advertisement for a demo of using Chef to automate application deployment on Linux on POWER.
In this session, we will learn about Teamcity CI Server. We will look at the different options available and how we can set a CI pipeline using Teamcity.
This document discusses the benefits of continuous integration. It describes the pain points of the previous system such as broken builds, manual testing and deployment. The new system uses a build server to continuously build every check-in. It also uses unit tests, automated deployment scripts, and pushes latest builds automatically to reduce errors and deployment time. The verdict is that build issues are now identified rapidly, regression tests provide higher confidence, deployments can be done by one person with no downtime and in only 6 minutes, and rollbacks are also quicker.
This document discusses continuous delivery fundamentals and how serverless platforms can help realize them. It covers topics like automated software releases through pipelines, building quality into products from the start, and how serverless handles infrastructure concerns so developers can focus on code. Examples are provided of using AWS Lambda, API Gateway, S3, Route53, CloudFormation, CodePipeline and other services to implement continuous delivery of serverless applications.
This document provides an agenda for a Chef Hack Day event hosted by Trace3 on April 26, 2016. The agenda includes times for lunch, welcome/kick-off, hacking sessions, and demo/wrap-up periods throughout the day. Guidelines are also listed for the hack day projects, encouraging teams to track work, share demonstrations, ask for help, be open to learning, and have fun. Suggested hack day project ideas include using InSpec to verify CIS Benchmarks and scanning/remediating with Chef Compliance.
This document provides an introduction and overview of Puppet Enterprise:
- It begins with an agenda for the meeting including introductions, an introduction to Puppet Enterprise, a live demo, and a Q&A session.
- It discusses how Puppet Enterprise helps companies become great software companies by delivering experiences to users faster and more simply and securely.
- A live demo is then given showing how Puppet Enterprise works by defining configurations, simulating changes, enforcing configurations, and reporting on changes.
An overview of Chef Automate and the various resources for Chef, InSpec and Habitat for Azure and Microsoft's other products. Presented September 20, 2017 at Tank Stream Labs.
This document discusses challenges faced by organizations in managing their infrastructure and applications, and how Chef and related tools can help address those challenges. It outlines Chef's approach of treating infrastructure as code and using automation to enable continuous delivery of infrastructure and applications. This allows for faster innovation, better quality/compliance, and rapid time to value. Key aspects covered include infrastructure as code, automation of the development stack, enabling DevOps workflows, and integrating security and compliance into the software delivery pipeline.
Today, the development and operations landscape has shifted to a more collaborative model merging the two (DevOps). Developers need to know much more about the operational components of their software - especially around network programming, services development, and continuous deployment. Likewise, the developer's IT counterpart needs to know much more about development - especially around infrastructure automation (Chef/Puppet), automated testing, and continuous deployment.
1) The document discusses delivering software at speed using Chef Automate and AWS OpsWorks for Chef Automate. It describes how Chef Automate provides capabilities for continuous automation, compliance, and visibility across infrastructure, applications, and workflows.
2) AWS OpsWorks for Chef Automate is introduced as a native Amazon service that provides a fully managed Chef server on AWS, allowing customers to take advantage of Chef Automate's capabilities in an AWS environment.
3) The document argues that Chef Automate is foundational for DevOps initiatives by enabling organizations to define infrastructure and compliance as code, increase speed of software delivery, improve efficiency, and decrease risk through continuous automation and compliance monitoring.
Pivotal CloudFoundry on Google cloud platformRonak Banka
This document is a slide presentation by Ronak Banka on using Pivotal Cloud Foundry (PCF) and Google Cloud Platform (GCP) together. It discusses how PCF provides a platform for deploying applications on GCP that enables both developer and operator productivity through features like automated deployments, service integration, and operations. It also highlights benefits of using PCF on GCP like performance, scale, cost savings, and access to differentiated GCP services.
Thomas Seibert and Gregor Zurowski demonstrate how Mercedes-Benz.io has achieved to go from idea to production in no time. Through the evolution of an effective and developer oriented application generation framework, utilization of a highly automated tool chain, organizational improvements and the infrastructure provided by PCF they will describe how their delivery performance has increased on many dimensions and how their ecosystem allows for scaling to a multitude of teams.
Adopting PCF At An Automobile ManufacturerVMware Tanzu
This document discusses the adoption of Pivotal Cloud Foundry at an automobile manufacturer. It describes the initial state with a Java portal and broken customer journey. The vision was to create the best customer experience. The target state used Pivotal Cloud Foundry, microservices architecture, and cloud infrastructure. Key decisions included using the cloud foundry PaaS, adopting a microservices style, and enabling development teams. Challenges included integrating cloud foundry and implementing shared services and versioning. Lessons learned included the need for automation and that cloud foundry is not a panacea and requires integration work.
Brisbane AWS Meetup: OpsWorks for Chef AutomateMatt Ray
June 28, 2017 presentation at the Brisbane AWS Meetup.
OpsWorks for Chef Automate is a service directly available from AWS, managed by Chef as a joint offering.
SoCal DevOps Meetup 1/26/2017 - Habitat by ChefTrevor Hess
The document discusses Habitat, a tool for building and managing applications. It provides an overview of Habitat and how it makes containers better by allowing applications to declare dependencies and resolve them from the application to infrastructure for a minimum viable OS. The document also demonstrates Habitat's approach through examples of building immutable infrastructure that allows last mile configuration changes, decoupling application builds from final containers, and orchestrating application launch order and topology.
Now, this is a story all about how
ZS got flipped-turned upside down
And I'd like to take a minute
Just sit right back,
I'll tell you how we used Chef on the Microsoft stack.
Come hear the rap on how ZS Associates, a Global Sales and Marketing Data Firm, massively accelerated their change velocity and eradicated manual config errors by implementing Chef on Azure. Hear about ZS’s cool end-to-end provisioning process that uses Powershell and Chef to automate deploy, config and test with one button.
Join 10th Magnitude Senior Consultant John Smyth, 10th Magnitude Consultant and Arrested DevOps Podcast co-host Trevor Hess and ZS Associates Software Engineering Lead-Applications Mahesh Velaga, who will take you through the implementation verse by verse. Trevor, by the way, will literally be rapping--with props to Will Smith.
https://youtu.be/6EQTbrw4OyM
REAN Cloud provides a comprehensive list of services and solutions for cloud migration and managed services. REAN Cloud has innovative approaches to DevOps, Security & Compliance, and Cloud Computing for highly-regulated industries such as Financial Services, Healthcare/Life Sciences, Public Sector, and Education verticals.
Continuous delivery is the process of automating the deployment of code changes to production. It involves building, testing, and deploying code changes through successive environments like integration, testing, and production. Continuous integration starts the process by automatically building and testing code changes. The release pipeline then automates deploying through environments. This finds issues early and allows for rapid deployment of code changes to production through automated testing and infrastructure provisioning.
This presentation walks through AWS Developer Tools like AWS CodeCommit, AWS CodeBuild, AWS CodeDeploy, and AWS CodePipeline to setup Continous Integration and Continous Delivery in your software development. You will learn with a CI / CD model how Developers and IT operations professionals practicing DevOps can use these services to rapidly and safely deliver software.
This document discusses automating the deployment of WebSphere Message Broker environments using RapidDeploy. Some key benefits of automation include reducing effort, improving productivity, accelerating growth by releasing additional scalability, eliminating errors to minimize downtime, and expediting time to value. The demonstration shows RapidDeploy running on Windows deploying a Message Broker binary to a Linux VM, creating and deploying environments, taking snapshots, cloning an environment, deploying changes, and comparing snapshots. Automation helps address challenges of manual deployments, composite deployments, upgrades, and providing a consistent framework.
The document summarizes the mission, teams, work, process, and technology of an interactive media company. The company's mission is to create high-performance and easy-to-use entertainment experiences for customers. It has various teams that develop interactive applications, manage processes, design graphics, test software quality, and more. The teams work using agile methodologies and technologies like HTML, JavaScript, databases, and tools for version control, continuous integration, testing and project management.
DevOps for the Mainframe aims to leverage continuous integration, cloud technologies, and beyond to deliver z/OS applications. The document discusses how DevOps principles can help enable rapid evolution of deployed z/OS services by reducing risk, decreasing costs, and improving quality. It provides examples of how tools from IBM can help implement a continuous delivery pipeline for mainframe development and testing that incorporates automated testing, configuration, and deployment.
Eseguire Applicazioni Cloud-Native con Pivotal Cloud Foundry su Google Cloud ...VMware Tanzu
Eseguire Applicazioni Cloud-Native con Pivotal Cloud Foundry su Google Cloud Platform (Pivotal Cloud-Native Workshop: Milan)
Fabio Marinelli
7 February 2018
Global Azure 2024 - On-Premises to Azure Cloud: .NET Web App JourneyCallon Campbell
In this session, we embark on a transformative journey from traditional on-premises hosting to the dynamic Azure cloud. Focused specifically on .NET web applications, we’ll explore the challenges, strategies, and best practices for migrating your beloved web apps to the Azure ecosystem.
Open Source Summit NA 2024: Open Source Cloud Costs - OpenCost's Impact on En...Matt Ray
Discover how a leading enterprise achieved visibility into their cloud costs with the CNCF project OpenCost. OpenCost models current and historical Kubernetes cloud spend and resource allocation by service, deployment, namespace, labels, and much more. This data provides transparency for cloud bills and can be used as the basis for optimizing your Kubernetes deployments based on cost allocation. This session delves into the real-world journey of implementing OpenCost for tracking cloud costs and how they optimized their infrastructure with this information. We’ll start with an introduction to OpenCost, its capabilities, and how to get started as a user and as a contributor. Then we’ll explore the challenges faced, lessons learned, and the tangible impact observed. From initial deployment to ongoing management, learn how OpenCost empowered the enterprise to make data-driven decisions, avoid cost overruns, and streamline their cloud budgeting. Join us for practical insights, success stories, and actionable steps to harness the power of OpenCost in your enterprise.
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostMatt Ray
KubeCon EU 2024 Lightning Talk
Understanding the cost and efficiency of Kubernetes on public clouds is essential once you start expanding your infrastructure with real production workloads. The FinOps Certified Solution and CNCF Sandbox OpenCost project monitors cloud costs and models current and historical Kubernetes cloud spend and resource allocation by service, deployment, namespace, labels, and much more. This data provides transparency for cloud bills and can be used as the basis for optimizing your Kubernetes deployments based on cost allocation. This quick introduction to OpenCost will start your foundation for monitoring and Kubernetes and cloud costs.
SCaLE 20X: Kubernetes Cloud Cost Monitoring with OpenCost & Optimization Stra...Matt Ray
Understanding the cost and efficiency of Kubernetes on public clouds is essential once you start expanding your infrastructure with real production workloads. The CNCF Sandbox OpenCost project and specification models current and historical Kubernetes cloud spend and resource allocation by service, deployment, namespace, labels, and much more. This data provides transparency for cloud bills and can be used as the basis for optimizing your Kubernetes deployments based on cost allocation. Optimizing Kubernetes for cost and performance is an ongoing iterative process that starts with applications and works through the entire stack.
HashiTalks 2020 - Chef Tools & Terraform: Better TogetherMatt Ray
This document discusses how Chef and Terraform can be used together for infrastructure automation and compliance. It provides overviews of Chef Infra, Chef Habitat, Chef InSpec, and how each integrates with Terraform. Key points include the Chef Provisioner and Provider for Terraform, the Habitat Provisioner, using Kitchen-Terraform for testing, and InSpec-Iggy for generating compliance profiles from Terraform configs. The document emphasizes that these tools can work better together for provisioning, deploying applications, and verifying infrastructure and security compliance as code.
EmacsConf 2019: Interactive Remote Debugging and Development with TRAMP ModeMatt Ray
Emacs’ TRAMP Mode allows for remotely editing files and using Emacs Shell Mode with remote systems. This session walked through the basics of using TRAMP Mode with the Free Software tools Vagrant, Chef, InSpec, and the interactive Ruby debugging shell Pry. The speaker notes are included along with the demo notes. The YouTube recording of the talk is available here: https://youtu.be/4pHid-kTBHw
Wellington DevOps: Bringing Your Applications into the Future with HabitatMatt Ray
This document discusses Habitat, an open source application automation platform from Chef that allows teams to build, deploy, and manage any application in any environment. Habitat addresses challenges like modernizing legacy applications to run in cloud-native environments and accelerating adoption of platforms like Kubernetes. It achieves application portability by separating platform-independent and dependent components and packaging applications immutably. Customers like a large automaker and agribusiness have used Habitat to modernize legacy apps and optimize their platform adoption efforts.
DevOps Days Singapore 2018 Ignite - Bringing Your Applications into the Futur...Matt Ray
Ignite talks are 20 slides auto-advancing every 15 seconds. This session attempts to share the value of migrating existing applications from legacy to modern platforms.
Cloud Expo Asia 20181010 - Bringing Your Applications into the Future with Ha...Matt Ray
What are we going to do about all these legacy applications? Kubernetes, Docker or Server Core? With Habitat it doesn’t matter anymore! As companies make the transition from traditional IT infrastructure to cloud-native container platforms packaging, deploying and managing applications becomes the focus for developers and operators. Having a consistent approach to managing dependencies and building applications brings stability to CI/CD pipelines and frees developers to prioritize on features. Automated, repeatable builds with immutable artifacts and consistent management of any application on any platform allow operators to focus on stability and speed. Chef's Habitat project brings all of this together in an open source automation platform that enables modern application teams to build, deploy, and run any application in any environment - from traditional data-centers to containerized microservices. This presentation provided an overview of the benefits of Habitat and a live demo of applications being built and deployed on traditional operating systems across Docker and Kubernetes, seamlessly.
Presentation from Cloud Expo Asia Hong Kong covering the rationale for "Compliance as Code" and how InSpec may be applied to servers, cloud platforms, and much more to keep track of your compliance everywhere.
Opening keynote for DevOpsDays Jakarta. I attempted to tie the themes of DevOps to a timeline of when they received increasing focus. Books on the subjects provided a convenient way to mark those times.
https://www.devopsdays.org/events/2018-jakarta/program/matt-ray/
DevOps Talks Melbourne 2018: Whales, Cats and KubernetesMatt Ray
Kubernetes, Docker or VMs? With Habitat it doesn’t matter anymore! As companies make the transition from traditional IT infrastructure to cloud-native container platforms packaging, deploying and managing applications becomes the focus for developers and operators. Having a consistent approach to managing dependencies and building applications brings stability to CI/CD pipelines and frees developers to prioritize on features. Automated, repeatable builds with immutable artefacts and consistent management of any application on any platform allow operators to focus on stability and speed. Meet Habitat! This session will provide an overview of the benefits of Habitat and a live demo of applications being built and deployed on traditional operating systems across Docker and Kubernetes, seamlessly.
Habitat is an open source application automation platform that allows development and operations teams to build, deploy, and manage any application on any infrastructure. It implements automation best practices like immutable infrastructure, declarative deployments, and configuration as code. Habitat provides tools for building packages, running services, and managing applications across platforms in a standardized way. The Habitat community is open source and supports many languages and platforms.
Automating Compliance with InSpec - AWS North SydneyMatt Ray
Automating Compliance with InSpec provides a concise summary of how InSpec can be used to automate compliance testing across operating systems and applications. InSpec uses a single language to test configuration across Linux, Windows, databases and cloud platforms. It can test infrastructure as code, servers, containers and APIs. InSpec is open source and supported by Chef.
Automating Applications with Habitat - Sydney Cloud Native MeetupMatt Ray
Habitat is an open source tool for automating the build, deployment, and management of applications. It defines a standard lifecycle for applications that includes building, deploying, running, and managing applications and their dependencies. Habitat packages applications and dependencies together, and uses supervisors to manage applications in production. It aims to simplify and standardize the delivery of developer services by automating common tasks like configuration, service discovery, and clustering across different runtime environments.
Presentation from the Sydney AWS Security Meetup - August 10, 2017.
https://www.meetup.com/Sydney-AWS-Security-User-Group/events/239370748/
Compliance as Code: Shifting Compliance Left in Continuous DeliveryMatt Ray
This document discusses shifting compliance left into continuous delivery pipelines using compliance as code. It describes integrating security and compliance checks into regular development processes through automation. Compliance policies and rules are expressed as testable code that can be checked alongside infrastructure and application code in CI/CD pipelines. This allows organizations to more quickly detect and fix compliance issues while accelerating development cycles.
Automating Compliance with InSpec - Chef Singapore MeetupMatt Ray
July 24, 2017 slides and demo for Automating Compliance with InSpec. The associated GitHub repository is here: https://github.com/mattray/inspec-workshop
Melbourne Chef Meetup: Automating Azure Compliance with InSpecMatt Ray
June 26, 2017 presentation. With the move to infrastructure as code and continuous integration/continuous delivery pipelines, it looked like releases would become more frequent and less problematic. Then the auditors showed up and made everyone stop what they were doing. How could this have been prevented? What if the audits were part of the process instead of a roadblock? What sort of visibility do we have into the state of our Azure infrastructure compliance? This talk will provide an overview of Chef's open-source InSpec project (https://inspec.io) and how you can build "Compliance as Code" into your Azure-based infrastructure.
Compliance as Code with InSpec - DevOps Melbourne 2017Matt Ray
DevOps Melbourne Meetup March 28, 2017
PCI and auditors slowing you down? Compliance and security are the next steps in building your software-defined infrastructure. Chef's open-source project InSpec (https://inspec.io) and audit cookbooks provide an accessible pattern for building compliance into your continuous delivery pipelines.
Andrew Marnell: Transforming Business Strategy Through Data-Driven InsightsAndrew Marnell
With expertise in data architecture, performance tracking, and revenue forecasting, Andrew Marnell plays a vital role in aligning business strategies with data insights. Andrew Marnell’s ability to lead cross-functional teams ensures businesses achieve sustainable growth and operational excellence.
Spark is a powerhouse for large datasets, but when it comes to smaller data workloads, its overhead can sometimes slow things down. What if you could achieve high performance and efficiency without the need for Spark?
At S&P Global Commodity Insights, having a complete view of global energy and commodities markets enables customers to make data-driven decisions with confidence and create long-term, sustainable value. 🌍
Explore delta-rs + CDC and how these open-source innovations power lightweight, high-performance data applications beyond Spark! 🚀
Linux Support for SMARC: How Toradex Empowers Embedded DevelopersToradex
Toradex brings robust Linux support to SMARC (Smart Mobility Architecture), ensuring high performance and long-term reliability for embedded applications. Here’s how:
• Optimized Torizon OS & Yocto Support – Toradex provides Torizon OS, a Debian-based easy-to-use platform, and Yocto BSPs for customized Linux images on SMARC modules.
• Seamless Integration with i.MX 8M Plus and i.MX 95 – Toradex SMARC solutions leverage NXP’s i.MX 8 M Plus and i.MX 95 SoCs, delivering power efficiency and AI-ready performance.
• Secure and Reliable – With Secure Boot, over-the-air (OTA) updates, and LTS kernel support, Toradex ensures industrial-grade security and longevity.
• Containerized Workflows for AI & IoT – Support for Docker, ROS, and real-time Linux enables scalable AI, ML, and IoT applications.
• Strong Ecosystem & Developer Support – Toradex offers comprehensive documentation, developer tools, and dedicated support, accelerating time-to-market.
With Toradex’s Linux support for SMARC, developers get a scalable, secure, and high-performance solution for industrial, medical, and AI-driven applications.
Do you have a specific project or application in mind where you're considering SMARC? We can help with Free Compatibility Check and help you with quick time-to-market
For more information: https://www.toradex.com/computer-on-modules/smarc-arm-family
Role of Data Annotation Services in AI-Powered ManufacturingAndrew Leo
From predictive maintenance to robotic automation, AI is driving the future of manufacturing. But without high-quality annotated data, even the smartest models fall short.
Discover how data annotation services are powering accuracy, safety, and efficiency in AI-driven manufacturing systems.
Precision in data labeling = Precision on the production floor.
Semantic Cultivators : The Critical Future Role to Enable AIartmondano
By 2026, AI agents will consume 10x more enterprise data than humans, but with none of the contextual understanding that prevents catastrophic misinterpretations.
Noah Loul Shares 5 Steps to Implement AI Agents for Maximum Business Efficien...Noah Loul
Artificial intelligence is changing how businesses operate. Companies are using AI agents to automate tasks, reduce time spent on repetitive work, and focus more on high-value activities. Noah Loul, an AI strategist and entrepreneur, has helped dozens of companies streamline their operations using smart automation. He believes AI agents aren't just tools—they're workers that take on repeatable tasks so your human team can focus on what matters. If you want to reduce time waste and increase output, AI agents are the next move.
Dev Dives: Automate and orchestrate your processes with UiPath MaestroUiPathCommunity
This session is designed to equip developers with the skills needed to build mission-critical, end-to-end processes that seamlessly orchestrate agents, people, and robots.
📕 Here's what you can expect:
- Modeling: Build end-to-end processes using BPMN.
- Implementing: Integrate agentic tasks, RPA, APIs, and advanced decisioning into processes.
- Operating: Control process instances with rewind, replay, pause, and stop functions.
- Monitoring: Use dashboards and embedded analytics for real-time insights into process instances.
This webinar is a must-attend for developers looking to enhance their agentic automation skills and orchestrate robust, mission-critical processes.
👨🏫 Speaker:
Andrei Vintila, Principal Product Manager @UiPath
This session streamed live on April 29, 2025, 16:00 CET.
Check out all our upcoming Dev Dives sessions at https://community.uipath.com/dev-dives-automation-developer-2025/.
This is the keynote of the Into the Box conference, highlighting the release of the BoxLang JVM language, its key enhancements, and its vision for the future.
Increasing Retail Store Efficiency How can Planograms Save Time and Money.pptxAnoop Ashok
In today's fast-paced retail environment, efficiency is key. Every minute counts, and every penny matters. One tool that can significantly boost your store's efficiency is a well-executed planogram. These visual merchandising blueprints not only enhance store layouts but also save time and money in the process.
Enhancing ICU Intelligence: How Our Functional Testing Enabled a Healthcare I...Impelsys Inc.
Impelsys provided a robust testing solution, leveraging a risk-based and requirement-mapped approach to validate ICU Connect and CritiXpert. A well-defined test suite was developed to assess data communication, clinical data collection, transformation, and visualization across integrated devices.
HCL Nomad Web – Best Practices und Verwaltung von Multiuser-Umgebungenpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-nomad-web-best-practices-und-verwaltung-von-multiuser-umgebungen/
HCL Nomad Web wird als die nächste Generation des HCL Notes-Clients gefeiert und bietet zahlreiche Vorteile, wie die Beseitigung des Bedarfs an Paketierung, Verteilung und Installation. Nomad Web-Client-Updates werden “automatisch” im Hintergrund installiert, was den administrativen Aufwand im Vergleich zu traditionellen HCL Notes-Clients erheblich reduziert. Allerdings stellt die Fehlerbehebung in Nomad Web im Vergleich zum Notes-Client einzigartige Herausforderungen dar.
Begleiten Sie Christoph und Marc, während sie demonstrieren, wie der Fehlerbehebungsprozess in HCL Nomad Web vereinfacht werden kann, um eine reibungslose und effiziente Benutzererfahrung zu gewährleisten.
In diesem Webinar werden wir effektive Strategien zur Diagnose und Lösung häufiger Probleme in HCL Nomad Web untersuchen, einschließlich
- Zugriff auf die Konsole
- Auffinden und Interpretieren von Protokolldateien
- Zugriff auf den Datenordner im Cache des Browsers (unter Verwendung von OPFS)
- Verständnis der Unterschiede zwischen Einzel- und Mehrbenutzerszenarien
- Nutzung der Client Clocking-Funktion
Complete Guide to Advanced Logistics Management Software in Riyadh.pdfSoftware Company
Explore the benefits and features of advanced logistics management software for businesses in Riyadh. This guide delves into the latest technologies, from real-time tracking and route optimization to warehouse management and inventory control, helping businesses streamline their logistics operations and reduce costs. Learn how implementing the right software solution can enhance efficiency, improve customer satisfaction, and provide a competitive edge in the growing logistics sector of Riyadh.
AI Changes Everything – Talk at Cardiff Metropolitan University, 29th April 2...Alan Dix
Talk at the final event of Data Fusion Dynamics: A Collaborative UK-Saudi Initiative in Cybersecurity and Artificial Intelligence funded by the British Council UK-Saudi Challenge Fund 2024, Cardiff Metropolitan University, 29th April 2025
https://alandix.com/academic/talks/CMet2025-AI-Changes-Everything/
Is AI just another technology, or does it fundamentally change the way we live and think?
Every technology has a direct impact with micro-ethical consequences, some good, some bad. However more profound are the ways in which some technologies reshape the very fabric of society with macro-ethical impacts. The invention of the stirrup revolutionised mounted combat, but as a side effect gave rise to the feudal system, which still shapes politics today. The internal combustion engine offers personal freedom and creates pollution, but has also transformed the nature of urban planning and international trade. When we look at AI the micro-ethical issues, such as bias, are most obvious, but the macro-ethical challenges may be greater.
At a micro-ethical level AI has the potential to deepen social, ethnic and gender bias, issues I have warned about since the early 1990s! It is also being used increasingly on the battlefield. However, it also offers amazing opportunities in health and educations, as the recent Nobel prizes for the developers of AlphaFold illustrate. More radically, the need to encode ethics acts as a mirror to surface essential ethical problems and conflicts.
At the macro-ethical level, by the early 2000s digital technology had already begun to undermine sovereignty (e.g. gambling), market economics (through network effects and emergent monopolies), and the very meaning of money. Modern AI is the child of big data, big computation and ultimately big business, intensifying the inherent tendency of digital technology to concentrate power. AI is already unravelling the fundamentals of the social, political and economic world around us, but this is a world that needs radical reimagining to overcome the global environmental and human challenges that confront us. Our challenge is whether to let the threads fall as they may, or to use them to weave a better future.
The Evolution of Meme Coins A New Era for Digital Currency ppt.pdfAbi john
Analyze the growth of meme coins from mere online jokes to potential assets in the digital economy. Explore the community, culture, and utility as they elevate themselves to a new era in cryptocurrency.
The Evolution of Meme Coins A New Era for Digital Currency ppt.pdfAbi john
Cooking Up Windows with Chef Automate
1. Cooking Up Windows with Chef
Automate
Perth MS Cloud Computing User Group
November 14, 2017
Matt Ray
Chef Manager/Solutions Architect APJ
[email protected]
3. We’re no longer an airline.We’re a software
company with wings.
–Veresh Sita, CIO,Alaska Airlines
Every business is a software business
4. Velocity: time from idea to ship
Continuous automation success metrics
Quantifying outcomes to deliver software at speed
Deployment
frequency
Time from
commit to deploy
Mean time
to resolve
Time deploying
remediation
Change failure
rate
SPEED
Measure of rate
of software change
EFFICIENCY
Measure of effectiveness
of software change
RISK
Measure of quality
of software change
Compliance audit
frequency
Idea Ship
5. The Chef Automate Platform
Continuous Automation for High Velocity IT
Workflow • Local development • Integration • Tooling (APIs & SDKs)
COLLABORATE
▪ Package
▪ Test
▪ Approve
BUILD
▪ Provision
▪ Configure
▪ Execute
▪ Update
DEPLOY
▪ Secure
▪ Comply
▪ Audit
▪ Measure
▪ Log
MANAGE
Infrastructure Automation Compliance AutomationApplication Automation
OSS AUTOMATION ENGINES
Increase Speed
▪ Package infrastructure and app
configuration as code
▪ Continuously automate
infrastructure and app updates
Improve Efficiency
▪ Define and execute standard
workflows and automation
▪ Audit and measure
effectiveness of automation
Decrease Risk
▪ Define compliance rules as
code
▪ Deliver continuous compliance
as part of standard workflow
6. Chef
▪ Manages deployment
and on-going automation
▪ Define reusable resources
and infrastructure state as code
▪ Scale elegantly from one to tens of
thousands of managed nodes across
multiple complex environments
▪ Community, Certified Partner, and
Chef supported content available
for all common automation tasks
Infrastructure automation
and delivery at scale
windows_feature ‘IIS-WebServerRole’ do
action :install
end
windows_feature ‘IIS-ASPNET’ do
action :install
end
iis_pool FooBarPool do
runtime_version “4.0”
action :add
end
package "apache" do
action :install
end
template “/etc/httpd/https.conf” do
source “httpd.conf.erb”
mode 0075
owner “root”
group “root”
end
service “apache2” do
action :start
end
7. PART OF A PROCESS OF CONTINUOUS COMPLIANCE
Scan for
Compliance
Build & Test
Locally
Build & Test
CI/CD Remediate Verify
A SIMPLE EXAMPLE OF AN INSPEC CIS RULE
InSpec
▪ Translate compliance into Code
▪ Clearly express statements of policy
▪ Move risk to build/test from runtime
▪ Find issues early
▪ Write code quickly
▪ Run code anywhere
▪ Inspect machines, data, APIs, and
Cloud platforms
Turn security and
compliance into code
control 'windows-base-201' do
title 'Strong Windows NTLMv2 Authentication Enabled;
Weak LM Disabled'
desc 'http://support.microsoft.com/en-us/kb/823659'
impact 1.0
describe registry_key
('HKLMSystemCurrentControlSetControlLsa') do
it { should exist }
its('LmCompatibilityLevel') { should eq 4 }
end
8. Habitat
▪ Ease the burden of managing microservice
apps and bring benefits of apps architected
for microservices to traditional applications
▪ Gain consistent management of new
and traditional applications across their lifecycle
▪ Provides application portability for new and
traditional apps
▪ Autonomous nodes self-manage runtime state
of application based upon policy you define
▪ APIs expose application behaviors
as data for better management
▪ Works in tandem with infrastructure automation
▪ Makes applications running on containers,
PaaS, virtual machines, bare metal, … better
Automation that travels with the app
10. A single platform to Detect, Correct, and Automate
Chef Automate enables the entire journey
Detect
▪ Test against industry benchmarks
▪ Report and address audit needs
Correct
▪ Close detect/correct loop in one platform
▪ Develop baselines for automation
Automate
▪ Detect and correct before production
▪ Single language across DevOps, InfoSec
Chef Automate is a single platform to support the entire journey
11. Chef and Microsoft Integrations
• Chef Automate now live on the Azure Marketplace and Azure Gov Cloud
• Supports Azure Stack
• Continue to enhance Chef VM Extension (Linux & Windows)
• OMS integration with Chef client and server
• Knife, Test Kitchen, and InSpec plugins for Azure
Azure/OMS
• Support for PowerShell DSC since 2014, WMF 5.0 support added
• New Chef Client resources added, continued focus to bring popular resources into the “core” Chef Client
• Windows Server 2016 and Nano Server as supported platforms as well as Windows Container support
• ChefDK is now supported on Client and Server platforms
• Chef Supermarket contains Windows-specific cookbooks
• Test Kitchen support for Windows via WinRM and SSH
• InSpec resources for Windows
• Habitat support for Windows
Windows
• Chef VSCode extension for syntax and tooling plugins
• Chef and InSpec Extensions for Visual Studio Team Services (VSTS)
• Working with Visual Studio engineering team on other possible integrations/white space, possibly around InSpec &
Habitat
Visual Studio
13. Chef Automate is at the heart of software delivery
The vendors you trust, trust Chef for continuous automation
Workflow • Local development • Integration • Tooling (APIs & SDKs)
COLLABORATE
▪ Package
▪ Test
BUILD
▪ Secure
▪ Comply
MANAGE
Infrastructure
Automation
Compliance
Automation
Application
Automation
OSS AUTOMATION ENGINES
▪ Provision
▪ Configure
DEPLOY
MANAGEMENT
RUNTIME
WORKFLOW
ENVIRONMENT
SECURITY AND
GOVERNANCE