For the past couple of years everybody from your cat to the Gartner analysts have been talking about devops, but what is this devops thing. Why does it matter .. and what does it have to do with Open Source?
We've come a long way since introducing new ideas in server automation and deployment, and also in creating a culture of collaboration between the traditional silos in organizations. But how does this impact the traditional sysadmin world? Are we all a DevOps now? Does a DevOps person = sysadmin 2.0? Will DevOps put us out of a job? I will give a brief overview of how culture, workflow, and behavior have evolved.
After evaluating the past and the present, I will talk about the future, identifying technical gaps in monitoring, packaging, and data collection and identifying emerging human, organizational evolutions.
This document discusses best practices for building JavaScript rich internet applications (RIAs). It covers topics like testing techniques, design patterns, testing tools, and approaches like test-driven development. Some of the key recommendations include writing code for humans rather than machines, keeping servers simple as an event bus between clients, and focusing on concepts rather than specific tools. Test-driven development is emphasized as important for code quality and maintainability.
This document summarizes 7 tools for a DevOps stack: Puppet, MCollective, Logstash, Kibana, Graphite, Vagrant, and FPM. It provides an overview of what each tool is used for, such as configuration management with Puppet, distributed orchestration with MCollective, log aggregation with Logstash, log visualization with Kibana, metrics collection and graphing with Graphite, infrastructure automation with Vagrant, and packaging with FPM. The document also includes examples and screenshots demonstrating how some of the tools can be used.
The document summarizes 7 tools for a devops stack:
1) Automation tools like Puppet, Chef, and Jenkins are used to automate deployments and configurations.
2) The Marionette Collective allows orchestrating tasks across servers like checking statuses and restarting services.
3) FPM helps create software packages to address issues with packaging dependencies and versions.
4) Logstash is used for centralized logging and shipping logs anywhere while filtering and indexing them.
5) Graphite and Kibana provide visualization and graphing of metrics at scale for monitoring.
11 Tools for your Open Source devops stack Kris Buytaert
11 Tools for your devops stack
- Devops is a growing movement to break down barriers between development and operations teams. It promotes automation, measurement, and sharing.
- Popular tools include Jenkins for continuous integration, FPM for packaging, Logstash for log collection, Graphite for metrics collection and visualization, Puppet/Chef for configuration management, and Vagrant for portable development environments.
- Other tools like MCollective and friends help with distributed automation tasks like checking server statuses or package versions across many servers.
11 tools for your devops stack summarizes key tools for a devops workflow including:
Jenkins for continuous integration; FPM for packaging; Logstash for centralized logging; Graphite for metrics and monitoring; Puppet and Vagrant for configuration management and environment provisioning; and tools like Mcollective and Kibana to help with automation, monitoring and visualization. Sharing code, environments and experiences through open source is also emphasized as important for a collaborative devops culture.
7 Tools for your Puppetized Devops stackKris Buytaert
7 Tools for your puppetized devops stack discusses Puppet, Jenkins, fpm, Logstash, Graphite, the Marionette Collective, and Vagrant as tools for a DevOps stack. Puppet is used for configuration management. Jenkins is used for continuous integration. fpm creates packages. Logstash handles log collection and analysis. Graphite provides metrics graphing. The Marionette Collective provides distributed SSH commands. And Vagrant allows consistent environments. The talk emphasizes culture, automation, measurement, and sharing as key DevOps principles.
Devops, the future is here, it's just not evenly distributed yet.Kris Buytaert
This document discusses the DevOps movement and how operations and development teams can work more collaboratively. Some key points:
- DevOps aims to break down barriers between development and operations teams through better communication and automation.
- In the past, developers would deploy code without considering operational requirements, leading to problems once code was in production. DevOps promotes developing and deploying code as a team effort between devs and ops.
- Automating processes like configuration management, continuous integration, deployment and monitoring helps align dev and ops goals and allows more frequent, lower-risk deployments. Tools like Puppet, Chef, Jenkins and Nagios are mentioned.
- The document advocates for practices like test-driven
This document discusses best practices for building JavaScript rich internet applications (RIAs). It covers topics like testing techniques, design patterns, testing tools, and approaches like test-driven development. Some of the key recommendations include writing code for humans rather than machines, keeping servers simple as an event bus between clients, and focusing on concepts rather than specific tools. Test-driven development is emphasized as important for code quality and maintainability.
This document summarizes 7 tools for a DevOps stack: Puppet, MCollective, Logstash, Kibana, Graphite, Vagrant, and FPM. It provides an overview of what each tool is used for, such as configuration management with Puppet, distributed orchestration with MCollective, log aggregation with Logstash, log visualization with Kibana, metrics collection and graphing with Graphite, infrastructure automation with Vagrant, and packaging with FPM. The document also includes examples and screenshots demonstrating how some of the tools can be used.
The document summarizes 7 tools for a devops stack:
1) Automation tools like Puppet, Chef, and Jenkins are used to automate deployments and configurations.
2) The Marionette Collective allows orchestrating tasks across servers like checking statuses and restarting services.
3) FPM helps create software packages to address issues with packaging dependencies and versions.
4) Logstash is used for centralized logging and shipping logs anywhere while filtering and indexing them.
5) Graphite and Kibana provide visualization and graphing of metrics at scale for monitoring.
11 Tools for your Open Source devops stack Kris Buytaert
11 Tools for your devops stack
- Devops is a growing movement to break down barriers between development and operations teams. It promotes automation, measurement, and sharing.
- Popular tools include Jenkins for continuous integration, FPM for packaging, Logstash for log collection, Graphite for metrics collection and visualization, Puppet/Chef for configuration management, and Vagrant for portable development environments.
- Other tools like MCollective and friends help with distributed automation tasks like checking server statuses or package versions across many servers.
11 tools for your devops stack summarizes key tools for a devops workflow including:
Jenkins for continuous integration; FPM for packaging; Logstash for centralized logging; Graphite for metrics and monitoring; Puppet and Vagrant for configuration management and environment provisioning; and tools like Mcollective and Kibana to help with automation, monitoring and visualization. Sharing code, environments and experiences through open source is also emphasized as important for a collaborative devops culture.
7 Tools for your Puppetized Devops stackKris Buytaert
7 Tools for your puppetized devops stack discusses Puppet, Jenkins, fpm, Logstash, Graphite, the Marionette Collective, and Vagrant as tools for a DevOps stack. Puppet is used for configuration management. Jenkins is used for continuous integration. fpm creates packages. Logstash handles log collection and analysis. Graphite provides metrics graphing. The Marionette Collective provides distributed SSH commands. And Vagrant allows consistent environments. The talk emphasizes culture, automation, measurement, and sharing as key DevOps principles.
Devops, the future is here, it's just not evenly distributed yet.Kris Buytaert
This document discusses the DevOps movement and how operations and development teams can work more collaboratively. Some key points:
- DevOps aims to break down barriers between development and operations teams through better communication and automation.
- In the past, developers would deploy code without considering operational requirements, leading to problems once code was in production. DevOps promotes developing and deploying code as a team effort between devs and ops.
- Automating processes like configuration management, continuous integration, deployment and monitoring helps align dev and ops goals and allows more frequent, lower-risk deployments. Tools like Puppet, Chef, Jenkins and Nagios are mentioned.
- The document advocates for practices like test-driven
Kris Buytaert gave a talk on DevOps at DrupalCon Munich in 2012. He discussed how the silos between development and operations created problems, and how the DevOps movement aims to break down those barriers through automation, collaboration, and continuous delivery. DevOps is not defined by specific tools but by cultural and process changes like integrating operations work into the entire software lifecycle from early on. The talk covered challenges like managing data and environments across different stages and how tools like Vagrant and configuration management can help address them.
OSDC 2015: Kris Buytaert | From ConfigManagementSucks to ConfigManagementLoveNETWAYS
Kris Buytaert discussed the evolution of infrastructure deployment and configuration management over the past 20 years. Early methods involved manual installations and copying config files (1996) while later approaches included tools like Mondo Rescue for single instances (2001), SystemImager for reproducible infrastructures (2003), and Kickstart/FAI for OS installation (2005). The talk advocates treating infrastructure as code using tools like Puppet, Chef, and CFEngine, with best practices like versioning, testing, and separate environments. It acknowledges early challenges in getting operators to adopt new methods but argues they are now essential for managing modern, distributed systems.
Devops, the future is here it's not evenly distributed yetKris Buytaert
Devops, the future is here, but it is not evenly distributed. The document discusses the history and principles of devops. It summarizes that traditionally, development and operations teams had different goals and worked in silos, but devops aims to break down these barriers by advocating for automated testing, continuous integration, infrastructure as code, and cross-functional teams to improve collaboration and speed of delivery. Achieving devops culture and practices can help organizations release changes more quickly, reliably and with higher quality.
Devops and Drupal focuses on the current state of devops practices among Drupal developers and system administrators. A survey of over 200 Drupal professionals found that while many are aware of devops concepts like continuous integration and deployment, few have fully implemented best practices for areas like automated testing, configuration management, and disaster recovery. Adopting a devops approach can help Drupal teams improve collaboration, deploy more frequently, and better manage systems over time.
Years of (not) learning , from devops to devoopsKris Buytaert
This document discusses the history of devops from 2009 to the present. It began as a movement in 2009 in Ghent to improve software delivery using open source tools and has since grown globally with over 250 events held. While tools have evolved from things like Puppet and Jenkins to Docker and Kubernetes, the core challenges of culture change, continuous delivery, monitoring, and cloud infrastructure remain. The document cautions that tools alone will not solve problems and that the industry focuses too much on hype and certification over meaningful change. The key takeaway is that after over 10 years, many organizations still struggle with devops principles due to cultural barriers, and the work of bridging development and operations is ongoing.
Deploying your Drupal site, Upgrading your Drupal Site, Scaling, Clustering and Monitoring it ... all topics Developers are often not involved with ...
Devops For Drupal explains the Devops problem, to a Drupal audience .
This document discusses the DevOps movement and related concepts. It provides background on how development and operations teams historically worked separately ("Devs vs Ops") and the problems that caused. DevOps aims to break down barriers between teams through practices like automation, continuous integration/delivery, infrastructure as code, and collaboration between teams from the beginning of a project. The document outlines problems DevOps aims to solve and gives examples of tools and approaches for bringing development and operations cultures together.
1) Devops aims to break down barriers between development and operations teams through a culture of collaboration, automation of processes, and using metrics to improve performance.
2) Automating builds, testing, deployments, and infrastructure management is key to ensure quality and allow teams to deploy changes quickly.
3) Collecting various metrics about code, deployments, systems, applications and business helps teams understand performance, identify issues, and continuously improve.
4) Sharing metrics, experiences, and code openly helps spread best practices and prevents teams from being locked into proprietary solutions.
Kris Buytaert discusses the Devops movement and how bringing developers and operations teams together earlier improves systems. He advocates for automation throughout the development and deployment process, from version control and testing to configuration management, monitoring, and upgrades. Adopting a Devops culture and practices like continuous integration, delivery, and deployment can help teams deploy better systems faster at lower risk.
Groovy there's a docker in my application pipelineKris Buytaert
This document discusses using containers and pipelines to automate the deployment of a Dashing dashboard application. It describes building containers for different components like Ruby, then using those containers to build and test the Dashing application. Jenkins pipelines are used to automate the build, test, and deployment process. Key challenges addressed include managing dependencies, running tests across environments, and reproducing builds. The document advocates defining pipelines as code using the Jenkins Job DSL plugin to centrally manage and version pipeline jobs.
OSMC 2017 | Groovy There is a Docker in my Dashing Pipeline by Kris Buytaert NETWAYS
Dashing or rather Smashing is an awesome Monitoring Dashboard, but it’s a pita to deploy. This talk will document the efforts we went trough to make the deployment of both dashing and the dashboards fully automated. It also will show how we test these dashboards using docker and how we build these pipelines with the JenkinsDSL.
This document discusses deploying software at scale through automation. It advocates treating infrastructure as code and using version control, continuous integration, and packaging tools. The key steps are to automate deployments, make them reproducible, and deploy changes frequently and consistently through a pipeline that checks code, runs tests, builds packages, and deploys to testing and production environments. This allows deploying changes safely and quickly while improving collaboration between developers and operations teams.
This document discusses the concepts of DevOps, SecOps, and DevSecOps. It describes how the traditional divisions between development, operations, and security can lead to problems, and how adopting a DevOps culture and practices like continuous integration, infrastructure as code, and automation can help break down silos. It emphasizes that DevSecOps is about collaboration, culture change, and bringing security practices into the development lifecycle from the beginning.
Automating MySQL operations with PuppetKris Buytaert
This document summarizes a presentation about automating MySQL operations with Puppet. It discusses:
- Why automation is important for consistency, security, and disaster recovery. Manual changes can introduce bugs and inconsistencies.
- Puppet is an open source configuration management tool that can be used to automate MySQL configuration, users, backups, replication, and high availability clustering with tools like Corosync/Pacemaker.
- Puppet modules define the desired state and Puppet ensures the actual state matches by making necessary changes. This provides auditability and change tracking through version control of Puppet code.
apidays LIVE New York - Navigating the Sea of Javascript Tools to Discover Sc...apidays
apidays LIVE New York - API for Legacy Industries: Banking, Insurance, Healthcare and Retail
Navigating the Sea of Javascript Tools to Discover Scalable Tools for Continuous Delivery
Menelaos Kotsollaris, Senior Software Engineer
Viki Green, Senior Software Developer at Trulioo
OSMC 2014: From monitoringsucks to monitoringlove (and back) | Kris BuytaertNETWAYS
Back in June 2011 John Vincent ranted on twitter that #monitoringsucks, and for a lot of us he was absolutely right.
At #devopsdays Rome 2012, in November, Ulf Mansson proclaimed his new found love for monitoring and we changed the hashtag into #monitoringlove.
Based on a new era of open source tools, Ulf started loving monitoring again. And for a lot of us he was absolutely right. Over the past 5 years an enormous amount of new tools and new patterns has come out of the community sometimes tagged with #devops, pretty much all of them open source. Do you still know what you should be using for what? And what the differences are?
An opinionated overview of the open source monitoring landscape to clear up the confusion on what you should use, or make the decision even more difficult on you :)
This document discusses the concepts of devops and how to transition an organization to a devops model. Some key points:
- Devops aims to break down silos between development and operations through culture, automation, measurement, and sharing.
- Traditional organizations have opposing goals between dev and ops that cause issues. Devops promotes a cross-functional team approach.
- Automating builds, testing, deployments, infrastructure management reduces risk and improves collaboration.
- Monitoring and metrics should be built in from the start so teams can learn from data and continuously improve.
- Culture change can be difficult but focusing on mindset, collaboration and incremental goals can help transition teams.
Kris Buytaert gave a talk on open source monitoring tools. He discussed how monitoring used to be an afterthought but new tools now focus on automation and integration. Popular modern tools like Prometheus focus on metrics collection and short-term storage while shipping long-term data to systems like Graphite. Prometheus excels at containerized environments through scraping but can also monitor other systems. Visualization and alerting have many options like Grafana, Icinga, and AlertManager. The landscape continues evolving towards full observability of applications and services.
Kris Buytaert gave a talk on DevOps at DrupalCon Munich in 2012. He discussed how the silos between development and operations created problems, and how the DevOps movement aims to break down those barriers through automation, collaboration, and continuous delivery. DevOps is not defined by specific tools but by cultural and process changes like integrating operations work into the entire software lifecycle from early on. The talk covered challenges like managing data and environments across different stages and how tools like Vagrant and configuration management can help address them.
OSDC 2015: Kris Buytaert | From ConfigManagementSucks to ConfigManagementLoveNETWAYS
Kris Buytaert discussed the evolution of infrastructure deployment and configuration management over the past 20 years. Early methods involved manual installations and copying config files (1996) while later approaches included tools like Mondo Rescue for single instances (2001), SystemImager for reproducible infrastructures (2003), and Kickstart/FAI for OS installation (2005). The talk advocates treating infrastructure as code using tools like Puppet, Chef, and CFEngine, with best practices like versioning, testing, and separate environments. It acknowledges early challenges in getting operators to adopt new methods but argues they are now essential for managing modern, distributed systems.
Devops, the future is here it's not evenly distributed yetKris Buytaert
Devops, the future is here, but it is not evenly distributed. The document discusses the history and principles of devops. It summarizes that traditionally, development and operations teams had different goals and worked in silos, but devops aims to break down these barriers by advocating for automated testing, continuous integration, infrastructure as code, and cross-functional teams to improve collaboration and speed of delivery. Achieving devops culture and practices can help organizations release changes more quickly, reliably and with higher quality.
Devops and Drupal focuses on the current state of devops practices among Drupal developers and system administrators. A survey of over 200 Drupal professionals found that while many are aware of devops concepts like continuous integration and deployment, few have fully implemented best practices for areas like automated testing, configuration management, and disaster recovery. Adopting a devops approach can help Drupal teams improve collaboration, deploy more frequently, and better manage systems over time.
Years of (not) learning , from devops to devoopsKris Buytaert
This document discusses the history of devops from 2009 to the present. It began as a movement in 2009 in Ghent to improve software delivery using open source tools and has since grown globally with over 250 events held. While tools have evolved from things like Puppet and Jenkins to Docker and Kubernetes, the core challenges of culture change, continuous delivery, monitoring, and cloud infrastructure remain. The document cautions that tools alone will not solve problems and that the industry focuses too much on hype and certification over meaningful change. The key takeaway is that after over 10 years, many organizations still struggle with devops principles due to cultural barriers, and the work of bridging development and operations is ongoing.
Deploying your Drupal site, Upgrading your Drupal Site, Scaling, Clustering and Monitoring it ... all topics Developers are often not involved with ...
Devops For Drupal explains the Devops problem, to a Drupal audience .
This document discusses the DevOps movement and related concepts. It provides background on how development and operations teams historically worked separately ("Devs vs Ops") and the problems that caused. DevOps aims to break down barriers between teams through practices like automation, continuous integration/delivery, infrastructure as code, and collaboration between teams from the beginning of a project. The document outlines problems DevOps aims to solve and gives examples of tools and approaches for bringing development and operations cultures together.
1) Devops aims to break down barriers between development and operations teams through a culture of collaboration, automation of processes, and using metrics to improve performance.
2) Automating builds, testing, deployments, and infrastructure management is key to ensure quality and allow teams to deploy changes quickly.
3) Collecting various metrics about code, deployments, systems, applications and business helps teams understand performance, identify issues, and continuously improve.
4) Sharing metrics, experiences, and code openly helps spread best practices and prevents teams from being locked into proprietary solutions.
Kris Buytaert discusses the Devops movement and how bringing developers and operations teams together earlier improves systems. He advocates for automation throughout the development and deployment process, from version control and testing to configuration management, monitoring, and upgrades. Adopting a Devops culture and practices like continuous integration, delivery, and deployment can help teams deploy better systems faster at lower risk.
Groovy there's a docker in my application pipelineKris Buytaert
This document discusses using containers and pipelines to automate the deployment of a Dashing dashboard application. It describes building containers for different components like Ruby, then using those containers to build and test the Dashing application. Jenkins pipelines are used to automate the build, test, and deployment process. Key challenges addressed include managing dependencies, running tests across environments, and reproducing builds. The document advocates defining pipelines as code using the Jenkins Job DSL plugin to centrally manage and version pipeline jobs.
OSMC 2017 | Groovy There is a Docker in my Dashing Pipeline by Kris Buytaert NETWAYS
Dashing or rather Smashing is an awesome Monitoring Dashboard, but it’s a pita to deploy. This talk will document the efforts we went trough to make the deployment of both dashing and the dashboards fully automated. It also will show how we test these dashboards using docker and how we build these pipelines with the JenkinsDSL.
This document discusses deploying software at scale through automation. It advocates treating infrastructure as code and using version control, continuous integration, and packaging tools. The key steps are to automate deployments, make them reproducible, and deploy changes frequently and consistently through a pipeline that checks code, runs tests, builds packages, and deploys to testing and production environments. This allows deploying changes safely and quickly while improving collaboration between developers and operations teams.
This document discusses the concepts of DevOps, SecOps, and DevSecOps. It describes how the traditional divisions between development, operations, and security can lead to problems, and how adopting a DevOps culture and practices like continuous integration, infrastructure as code, and automation can help break down silos. It emphasizes that DevSecOps is about collaboration, culture change, and bringing security practices into the development lifecycle from the beginning.
Automating MySQL operations with PuppetKris Buytaert
This document summarizes a presentation about automating MySQL operations with Puppet. It discusses:
- Why automation is important for consistency, security, and disaster recovery. Manual changes can introduce bugs and inconsistencies.
- Puppet is an open source configuration management tool that can be used to automate MySQL configuration, users, backups, replication, and high availability clustering with tools like Corosync/Pacemaker.
- Puppet modules define the desired state and Puppet ensures the actual state matches by making necessary changes. This provides auditability and change tracking through version control of Puppet code.
apidays LIVE New York - Navigating the Sea of Javascript Tools to Discover Sc...apidays
apidays LIVE New York - API for Legacy Industries: Banking, Insurance, Healthcare and Retail
Navigating the Sea of Javascript Tools to Discover Scalable Tools for Continuous Delivery
Menelaos Kotsollaris, Senior Software Engineer
Viki Green, Senior Software Developer at Trulioo
OSMC 2014: From monitoringsucks to monitoringlove (and back) | Kris BuytaertNETWAYS
Back in June 2011 John Vincent ranted on twitter that #monitoringsucks, and for a lot of us he was absolutely right.
At #devopsdays Rome 2012, in November, Ulf Mansson proclaimed his new found love for monitoring and we changed the hashtag into #monitoringlove.
Based on a new era of open source tools, Ulf started loving monitoring again. And for a lot of us he was absolutely right. Over the past 5 years an enormous amount of new tools and new patterns has come out of the community sometimes tagged with #devops, pretty much all of them open source. Do you still know what you should be using for what? And what the differences are?
An opinionated overview of the open source monitoring landscape to clear up the confusion on what you should use, or make the decision even more difficult on you :)
This document discusses the concepts of devops and how to transition an organization to a devops model. Some key points:
- Devops aims to break down silos between development and operations through culture, automation, measurement, and sharing.
- Traditional organizations have opposing goals between dev and ops that cause issues. Devops promotes a cross-functional team approach.
- Automating builds, testing, deployments, infrastructure management reduces risk and improves collaboration.
- Monitoring and metrics should be built in from the start so teams can learn from data and continuously improve.
- Culture change can be difficult but focusing on mindset, collaboration and incremental goals can help transition teams.
Kris Buytaert gave a talk on open source monitoring tools. He discussed how monitoring used to be an afterthought but new tools now focus on automation and integration. Popular modern tools like Prometheus focus on metrics collection and short-term storage while shipping long-term data to systems like Graphite. Prometheus excels at containerized environments through scraping but can also monitor other systems. Visualization and alerting have many options like Grafana, Icinga, and AlertManager. The landscape continues evolving towards full observability of applications and services.
Similar to OSDC 2012 | Devops and Open Source by Kris Buyaert (20)
Mobile app Development Services | Drona InfotechDrona Infotech
Drona Infotech is one of the Best Mobile App Development Company In Noida Maintenance and ongoing support. mobile app development Services can help you maintain and support your app after it has been launched. This includes fixing bugs, adding new features, and keeping your app up-to-date with the latest
Visit Us For :
Need for Speed: Removing speed bumps from your Symfony projects ⚡️Łukasz Chruściel
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
Hand Rolled Applicative User ValidationCode KataPhilip Schwarz
Could you use a simple piece of Scala validation code (granted, a very simplistic one too!) that you can rewrite, now and again, to refresh your basic understanding of Applicative operators <*>, <*, *>?
The goal is not to write perfect code showcasing validation, but rather, to provide a small, rough-and ready exercise to reinforce your muscle-memory.
Despite its grandiose-sounding title, this deck consists of just three slides showing the Scala 3 code to be rewritten whenever the details of the operators begin to fade away.
The code is my rough and ready translation of a Haskell user-validation program found in a book called Finding Success (and Failure) in Haskell - Fall in love with applicative functors.
Top 9 Trends in Cybersecurity for 2024.pptxdevvsandy
Security and risk management (SRM) leaders face disruptions on technological, organizational, and human fronts. Preparation and pragmatic execution are key for dealing with these disruptions and providing the right cybersecurity program.
WWDC 2024 Keynote Review: For CocoaCoders AustinPatrick Weigel
Overview of WWDC 2024 Keynote Address.
Covers: Apple Intelligence, iOS18, macOS Sequoia, iPadOS, watchOS, visionOS, and Apple TV+.
Understandable dialogue on Apple TV+
On-device app controlling AI.
Access to ChatGPT with a guest appearance by Chief Data Thief Sam Altman!
App Locking! iPhone Mirroring! And a Calculator!!
UI5con 2024 - Boost Your Development Experience with UI5 Tooling ExtensionsPeter Muessig
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
Malibou Pitch Deck For Its €3M Seed Roundsjcobrien
French start-up Malibou raised a €3 million Seed Round to develop its payroll and human resources
management platform for VSEs and SMEs. The financing round was led by investors Breega, Y Combinator, and FCVC.
Top Benefits of Using Salesforce Healthcare CRM for Patient Management.pdfVALiNTRY360
Salesforce Healthcare CRM, implemented by VALiNTRY360, revolutionizes patient management by enhancing patient engagement, streamlining administrative processes, and improving care coordination. Its advanced analytics, robust security, and seamless integration with telehealth services ensure that healthcare providers can deliver personalized, efficient, and secure patient care. By automating routine tasks and providing actionable insights, Salesforce Healthcare CRM enables healthcare providers to focus on delivering high-quality care, leading to better patient outcomes and higher satisfaction. VALiNTRY360's expertise ensures a tailored solution that meets the unique needs of any healthcare practice, from small clinics to large hospital systems.
For more info visit us https://valintry360.com/solutions/health-life-sciences
UI5con 2024 - Keynote: Latest News about UI5 and it’s EcosystemPeter Muessig
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...XfilesPro
Wondering how X-Sign gained popularity in a quick time span? This eSign functionality of XfilesPro DocuPrime has many advancements to offer for Salesforce users. Explore them now!
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
OSDC 2012 | Devops and Open Source by Kris Buyaert
1. 7 Tools for your devops stack
Kris Buytaert
European Tour April 2012
2. Kris Buytaert
•I used to be a Dev,
•Then Became an Op
•Chief Trolling Officer and Open Source Consultant @inuits.eu
•Everything is an effing DNS Problem
•Building Clouds since before the bookstore
•Some books, some papers, some blogs
•But mostly, trying to be good at my job
4. World , 200X-2009
Patrick Debois, Gildas Le Nadan, Andrew Clay Shafer, Kris Buytaert, Jezz Humble, Lindsay Holmwood, John Willis, Chris Read,
Julian Simpson, Luke Kanies, John Allspaw and lots of others ..
Gent , October 2009
Mountain View , June 2010
Hamburg , October 2010
Boston, March 2011
Mountain View, June 2011
Bangalore, Melbourne,
Goteborg , October 2011
....
5. ● Devops is a growing professional and cultural
movement
● We don't have all the answers yet
● We are reaching out to different communities
● We will point out problems we see..
● Only the name is new
While we are still working out the solutions
7. ●Adopt the new philosophy. We are in a new economic age. Western management must awaken to the challenge, must learn their responsibilities, and
take on leadership for change.
●Cease dependence on inspection to achieve quality. Eliminate the need for massive inspection by building quality into the product in the first place.
●Improve constantly and forever the system of production and service, to improve quality and productivity, and thus constantly decrease costs.
●Institute training on the job.
●Institute leadership The aim of supervision should be to help people and machines and gadgets do a better job.
●Drive out fear, so that everyone may work effectively for the company.
●Break down barriers between departments. People in research, design, sales, and production must work as a team, in order to foresee problems of
production and usage that may be encountered with the product or service.
●Eliminate slogans, exhortations, and targets for the work force asking for zero defects and new levels of productivity. Such exhortations only create
adversarial relationships, as the bulk of the causes of low quality and low productivity belong to the system and thus lie beyond the power of the work
force.
● Eliminate management by objective. Eliminate management by numbers and numerical goals. Instead substitute with leadership.
● Remove barriers that rob the hourly worker of his right to pride of workmanship. The responsibility of supervisors must be
changed from sheer numbers to quality.
● Remove barriers that rob people in management and in engineering of their right to pride of workmanship.
●Institute a vigorous program of education and self-improvement.
●Put everybody in the company to work to accomplish the transformation. The transformation is everybody's job.
20. The Marionette Collective
● Distributed ssh ++
● What version of ssh do I have installed on my servers
?
● On what servers is XYZ running ?
● Clean al my ssl certs ?
● Restart apache on all servers with fact X
28. #monitoringsucks
Monitoring is AWESOME. Metrics are AWESOME. I love it. Here's what I don't love:
● Having my hands tied with the model of host and service bindings.
● Having to set up "fake" hosts just to group arbitrary metrics together
● Having to either collect metrics twice - once for alerting and another for trending
● Only being able to see my metrics in 5 minute intervals
● Having to chose between shitty interface but great monitoring or shitty monitoring but great
interface
● Dealing with a monitoring system that thinks IT is the system of truth for my environment
● Not actually having any real choices
● John Vincent (@lusis) on his blog http://lusislog.blogspot.com/2011/06/why-monitoring-sucks.html
29. A sub movement
● #monitoringsucks trending
● https://github.com/monitoringsucks/
● 2008 Study :Nagios + Friends
● 2011 Conclusion : Nagios/Icinga are the only
automatable alternatives
● Monitoring and trending at scale , new kids
Graphite, Icinga, flapjack, etc
● Old Cool Kids, Ganglia
30.
31. Logstash
● Not your average centralized logging tool
● Elasticsearch backed
● Shipper
● Indexer
● Web
40. ● Open Source
● Github
● Talk about Experiences
● Open Spaces
41. Sharing environments
● Build identical environments
● Share code
● Shared ownership of content , code and configuration
42. Vagrant
● Abstraction layer for VirtualBox
● Integrates well with Puppet/Chef
● Project =
● Vagrantfile
● Manifests / Cookbooks
● Portable, Small , Versionable
● Use veewee to build your boxen
43. Vagrantfile
Vagrant::Config.run do |config|
# All Vagrant configuration is done here. The most common configuration
# options are documented and commented below. For a complete reference,
# please see the online documentation at vagrantup.com.
config.vm.define :mongo1 do |mongo1_config|
mongo1_config.ssh.max_tries = 100
mongo1_config.vm.box = "MyCentOS2"
mongo1_config.vm.network("192.168.99.101")
mongo1_config.vm.host_name = "mongo1"
mongo1_config.vm.provision :puppet do |mongo1_puppet|
mongo1_puppet.pp_path = "/tmp/vagrant-puppet"
mongo1_puppet.manifests_path = "manifests"
mongo1_puppet.module_path = "modules"
mongo1_puppet.manifest_file = "site.pp"
end
end
config.vm.define :mongo2 do |mongo2_config|
mongo2_config.ssh.max_tries = 100
mongo2_config.vm.box = "MyCentOS2"
mongo2_config.vm.network("192.168.99.102")
mongo2_config.vm.host_name = "mongo2"
mongo2_config.vm.provision :puppet do |mongo2_puppet|
mongo2_puppet.pp_path = "/tmp/vagrant-puppet"
mongo2_puppet.manifests_path = "manifests"
mongo2_puppet.module_path = "modules"
mongo2_puppet.manifest_file = "site.pp"
end
44. Vagrant Rocks
● Vagrant init
● Vagrant up
● Vagrant provision
● Vagrant down
● Vagrant destroy