DevOps practices emphasize small, independent teams and continuous deployment. This leads to system structures with: 1) a deep service-oriented hierarchy to enable reuse across small teams; 2) versioning and backward compatibility to allow simultaneous deployment from multiple teams; and 3) packaging of multiple services per virtual machine while avoiding race conditions during deployment.
Fifteen Years of DevOps -- LISA 2012 keynoteGeoff Halprin
There has been a lot of hullabaloo over the past few years around a concept called “DevOps.” The idea is that we need to break down the barriers between development and operations teams, and treat infrastructure as code, in order to move towards better software, more reliable and scalable systems, and continuous deployment.
For some of us who have been around a while, this is just a new label for something we’ve always done.
They say those that don’t learn from history are destined to repeat it. In this talk, we will look back at how the DevOps movement evolved, what it advocates, what it doesn’t address, and what you should take away from the movement that will help you in your professional life. We will also use this opportunity to look back over the past decade or two of system administration, and see how our challenges have changed, and how they have remained the same.
Continuous Delivery Pipelines help developers safely iterate on and test new code in production-like environments. But what if your team is tasked with developing the CD Pipeline itself? How do you empower multiple SCM engineers to make changes in a controlled way without impacting each other or degrading developer productivity?
Learn how Sony has leveraged ElectricFlow and DevOps principles to construct a flexible, version-able, review-able, test-able, revert-able and resilient CD pipeline. This talk will focus on the infrastructure, tools and processes used to create and operate this pipeline, and the methods used to safely and rapidly onboard new business groups, developers and SCM engineers.
Fifteen Years of DevOps -- LISA 2012 keynoteGeoff Halprin
There has been a lot of hullabaloo over the past few years around a concept called “DevOps.” The idea is that we need to break down the barriers between development and operations teams, and treat infrastructure as code, in order to move towards better software, more reliable and scalable systems, and continuous deployment.
For some of us who have been around a while, this is just a new label for something we’ve always done.
They say those that don’t learn from history are destined to repeat it. In this talk, we will look back at how the DevOps movement evolved, what it advocates, what it doesn’t address, and what you should take away from the movement that will help you in your professional life. We will also use this opportunity to look back over the past decade or two of system administration, and see how our challenges have changed, and how they have remained the same.
Continuous Delivery Pipelines help developers safely iterate on and test new code in production-like environments. But what if your team is tasked with developing the CD Pipeline itself? How do you empower multiple SCM engineers to make changes in a controlled way without impacting each other or degrading developer productivity?
Learn how Sony has leveraged ElectricFlow and DevOps principles to construct a flexible, version-able, review-able, test-able, revert-able and resilient CD pipeline. This talk will focus on the infrastructure, tools and processes used to create and operate this pipeline, and the methods used to safely and rapidly onboard new business groups, developers and SCM engineers.
The pursuit for the perfect synchrony between software development and IT operations is still ongoing, and striking the balance won’t happen any time soon. Understand and address these 5 common DevOps challenges to achieve a higher- functioning and collaborative organization.
How do measure our progress in a journey towards continuous integration? What are other people doing?
This presentation provides an measuring stick for CD Maturity and simple pattern for reviewing your current situation and deciding what to work on next.
At Ustream the teams developing the streaming technology stack are also responsible for operating it. This means we have our monitoring and alerting in place (including those based on error logs I mentioned above, but many others too) which alert the engineers themselves. I would like to talk about how we made this transition from the traditional setup where the devs did the coding and the sysops did the operation - what lessons we learned, how we convinced the sysop guys to give us permissions and so on
Deployments of larger server applications are often risky and error-prone. They cost development teams, system administrators and customers a lot of nerves and gray hair. The path from the development environment into production is often much more difficult than planned. Continuous Delivery - against all intuition - propagates as the solution for this problem to make more deployments.
In this talk, we want to have a look at this paradox and show how ideas from Continuous Delivery can help to optimize the software delivery process. We talk about our experiences in customer projects and what tools we use to automate and optimize our software delivery process, to minimize effort and risk and increase the quality of deployments.
DevOps is not a new technology or a product. It’s an approach or culture of software development that seeks stability and performance at the same time that it speeds software deliveries to the business. In this sharing, we will discuss what DevOps is from CAMS model that represents culture, automation, measurement and sharing. In addition, I will share some practical experiences in Trend Micro.
Al Wagner from IBM presents how to avoid deployment failures, reviewing such topics as: Deployment models like canary, blue/green and rolling that can help prevent major production outages; How to pinpoint deployment failures in your process and correct them; Pulling together a basic failure response plan; and How you can roll forward while improving your deployment process.
Learn more about IBM UrbanCode: http://www.ibm.biz/learnurbancode
EduXFactor presents to you a comprehensive up-to-date DevOps certification program. This course will empower you with job-relevant skills and power you ahead in your career.
With this course, master various aspects of software development, operations, continuous integration, continuous delivery, automated configuration management, test, and deployment using DevOps tools like Git, Docker, Jenkins, Ansible, Kubernetes, Puppet & Nagios..
Packed with hands-on exercise for every module, this course is suitable for software developers, technical project managers, architects, operations support, deployment engineers, IT managers, and development managers.
Managing IT environment complexity in a Multi-Cloud WorldShashi Kiran
IT environments are continuing to get complex. How do you better manage this to speed up digitization and application modernization efforts using environments-as-a-service
Webinar on "DevOps LifeCycle and SCM using common Git commands for version co...Agile Testing Alliance
Agile Testing Alliance and DevOps++ Alliance has started a new learning initiative this year. #WednesdayWebinar, as a part of this, we have hosted the first webinar on 10th Jan, 2018. The topic of the webinar was "DevOps LifeCycle and SCM using common Git commands for version control". The webinar was conducted by Valerian D'Souza. Valerian is Steering Committee Member of ATA and DevOps++ Alliance
Introduction To DevOps | Devops Tutorial For Beginners | DevOps Training For ...Simplilearn
This presentation on "Introduction to DevOps" will help you understand what is waterfall model, what is an agile model, what is DevOps, DevOps phases, DevOps tools and DevOps advantages. In traditional software development lifecycle, there is a lot of gap between development and operations team. DevOps addresses the gap between developers and operations. The development team will submit the application to the operations team for implementation. Operations team will monitor the application and provide relevant feedback to developers. According to DevOps practices, the workflow in software development and delivery is divided into 8 phases, Now, let us get started and understand these 8 phases in DevOps.
Below topics are explained in this "Introduction to DevOps" presentation:
1. Waterfall model
2. Agile model
3. What is DevOps?
4. DevOps phases
5. DevOps tools
6. DevOps advantages
Simplilearn's DevOps Certification Training Course will prepare you for a career in DevOps, the fast-growing field that bridges the gap between software developers and operations. You’ll become an expert in the principles of continuous development and deployment, automation of configuration management, inter-team collaboration and IT service agility, using modern DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios. DevOps jobs are highly paid and in great demand, so start on your path today.
Why learn DevOps?
Simplilearn’s DevOps training course is designed to help you become a DevOps practitioner and apply the latest in DevOps methodology to automate your software development lifecycle right out of the class. You will master configuration management; continuous integration deployment, delivery and monitoring using DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios in a practical, hands-on and interactive approach. The Devops training course focuses heavily on the use of Docker containers, a technology that is revolutionizing the way apps are deployed in the cloud today and is a critical skillset to master in the cloud age.
Who should take this course?
DevOps career opportunities are thriving worldwide. DevOps was featured as one of the 11 best jobs in America for 2017, according to CBS News, and data from Payscale.com shows that DevOps Managers earn as much as $122,234 per year, with DevOps engineers making as much as $151,461. DevOps jobs are the third-highest tech role ranked by employer demand on Indeed.com but have the second-highest talent deficit.
1. This DevOps training course will be of benefit the following professional roles:
2. Software Developers
3. Technical Project Managers
4. Architects
5. Operations Support
6. Deployment engineers
7. IT managers
8. Development managers
Learn more at: https://www.simplilearn.com/
Presented at Richmond SQL Server Users group, this presentation provides an introduction to Continuous Delivery principles, practices, tools and how to apply these to SQL Server Database. It also presents a case study and lessons learned from adopting these practices on a real project.
A proven path for migrating from clearcase to git and or subversionCollabNet
Open Source Software (OSS) offers compelling benefits, including affordability (TCO), security & stability, speed of innovation and flexibility. This especially is evident with OSS source code management (SCM) software such as Git and Subversion. In this Webinar we will provide a proven framework to guide your decision – when to move, and if OSS is the right answer.
We will present a proven path for migration from ClearCase or other proprietary SCM systems that has helped over 30,000 users to make the switch. This webinar will present an actionable strategy, covering the phases of discovery and planning, and a practical guide for the actual migration itself.
Topics Covered:
The pro’s and con’s of open source software for SCM
Git and Subversion– the leading enterprise SCM tools
TCO and other considerations for ClearCase migration
Key Takeaways:
The 3-step path: Discover, plan, migrate
Consideration for people and processes
Tools for migration and OSS management
The increasing adoption of DevOps principles has led to greater integration between software development (both application and software engineering) and IT operations (both systems administration and infrastructure). In this online seminar, we will explore the DevOps approaches
The pursuit for the perfect synchrony between software development and IT operations is still ongoing, and striking the balance won’t happen any time soon. Understand and address these 5 common DevOps challenges to achieve a higher- functioning and collaborative organization.
How do measure our progress in a journey towards continuous integration? What are other people doing?
This presentation provides an measuring stick for CD Maturity and simple pattern for reviewing your current situation and deciding what to work on next.
At Ustream the teams developing the streaming technology stack are also responsible for operating it. This means we have our monitoring and alerting in place (including those based on error logs I mentioned above, but many others too) which alert the engineers themselves. I would like to talk about how we made this transition from the traditional setup where the devs did the coding and the sysops did the operation - what lessons we learned, how we convinced the sysop guys to give us permissions and so on
Deployments of larger server applications are often risky and error-prone. They cost development teams, system administrators and customers a lot of nerves and gray hair. The path from the development environment into production is often much more difficult than planned. Continuous Delivery - against all intuition - propagates as the solution for this problem to make more deployments.
In this talk, we want to have a look at this paradox and show how ideas from Continuous Delivery can help to optimize the software delivery process. We talk about our experiences in customer projects and what tools we use to automate and optimize our software delivery process, to minimize effort and risk and increase the quality of deployments.
DevOps is not a new technology or a product. It’s an approach or culture of software development that seeks stability and performance at the same time that it speeds software deliveries to the business. In this sharing, we will discuss what DevOps is from CAMS model that represents culture, automation, measurement and sharing. In addition, I will share some practical experiences in Trend Micro.
Al Wagner from IBM presents how to avoid deployment failures, reviewing such topics as: Deployment models like canary, blue/green and rolling that can help prevent major production outages; How to pinpoint deployment failures in your process and correct them; Pulling together a basic failure response plan; and How you can roll forward while improving your deployment process.
Learn more about IBM UrbanCode: http://www.ibm.biz/learnurbancode
EduXFactor presents to you a comprehensive up-to-date DevOps certification program. This course will empower you with job-relevant skills and power you ahead in your career.
With this course, master various aspects of software development, operations, continuous integration, continuous delivery, automated configuration management, test, and deployment using DevOps tools like Git, Docker, Jenkins, Ansible, Kubernetes, Puppet & Nagios..
Packed with hands-on exercise for every module, this course is suitable for software developers, technical project managers, architects, operations support, deployment engineers, IT managers, and development managers.
Managing IT environment complexity in a Multi-Cloud WorldShashi Kiran
IT environments are continuing to get complex. How do you better manage this to speed up digitization and application modernization efforts using environments-as-a-service
Webinar on "DevOps LifeCycle and SCM using common Git commands for version co...Agile Testing Alliance
Agile Testing Alliance and DevOps++ Alliance has started a new learning initiative this year. #WednesdayWebinar, as a part of this, we have hosted the first webinar on 10th Jan, 2018. The topic of the webinar was "DevOps LifeCycle and SCM using common Git commands for version control". The webinar was conducted by Valerian D'Souza. Valerian is Steering Committee Member of ATA and DevOps++ Alliance
Introduction To DevOps | Devops Tutorial For Beginners | DevOps Training For ...Simplilearn
This presentation on "Introduction to DevOps" will help you understand what is waterfall model, what is an agile model, what is DevOps, DevOps phases, DevOps tools and DevOps advantages. In traditional software development lifecycle, there is a lot of gap between development and operations team. DevOps addresses the gap between developers and operations. The development team will submit the application to the operations team for implementation. Operations team will monitor the application and provide relevant feedback to developers. According to DevOps practices, the workflow in software development and delivery is divided into 8 phases, Now, let us get started and understand these 8 phases in DevOps.
Below topics are explained in this "Introduction to DevOps" presentation:
1. Waterfall model
2. Agile model
3. What is DevOps?
4. DevOps phases
5. DevOps tools
6. DevOps advantages
Simplilearn's DevOps Certification Training Course will prepare you for a career in DevOps, the fast-growing field that bridges the gap between software developers and operations. You’ll become an expert in the principles of continuous development and deployment, automation of configuration management, inter-team collaboration and IT service agility, using modern DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios. DevOps jobs are highly paid and in great demand, so start on your path today.
Why learn DevOps?
Simplilearn’s DevOps training course is designed to help you become a DevOps practitioner and apply the latest in DevOps methodology to automate your software development lifecycle right out of the class. You will master configuration management; continuous integration deployment, delivery and monitoring using DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios in a practical, hands-on and interactive approach. The Devops training course focuses heavily on the use of Docker containers, a technology that is revolutionizing the way apps are deployed in the cloud today and is a critical skillset to master in the cloud age.
Who should take this course?
DevOps career opportunities are thriving worldwide. DevOps was featured as one of the 11 best jobs in America for 2017, according to CBS News, and data from Payscale.com shows that DevOps Managers earn as much as $122,234 per year, with DevOps engineers making as much as $151,461. DevOps jobs are the third-highest tech role ranked by employer demand on Indeed.com but have the second-highest talent deficit.
1. This DevOps training course will be of benefit the following professional roles:
2. Software Developers
3. Technical Project Managers
4. Architects
5. Operations Support
6. Deployment engineers
7. IT managers
8. Development managers
Learn more at: https://www.simplilearn.com/
Presented at Richmond SQL Server Users group, this presentation provides an introduction to Continuous Delivery principles, practices, tools and how to apply these to SQL Server Database. It also presents a case study and lessons learned from adopting these practices on a real project.
A proven path for migrating from clearcase to git and or subversionCollabNet
Open Source Software (OSS) offers compelling benefits, including affordability (TCO), security & stability, speed of innovation and flexibility. This especially is evident with OSS source code management (SCM) software such as Git and Subversion. In this Webinar we will provide a proven framework to guide your decision – when to move, and if OSS is the right answer.
We will present a proven path for migration from ClearCase or other proprietary SCM systems that has helped over 30,000 users to make the switch. This webinar will present an actionable strategy, covering the phases of discovery and planning, and a practical guide for the actual migration itself.
Topics Covered:
The pro’s and con’s of open source software for SCM
Git and Subversion– the leading enterprise SCM tools
TCO and other considerations for ClearCase migration
Key Takeaways:
The 3-step path: Discover, plan, migrate
Consideration for people and processes
Tools for migration and OSS management
The increasing adoption of DevOps principles has led to greater integration between software development (both application and software engineering) and IT operations (both systems administration and infrastructure). In this online seminar, we will explore the DevOps approaches
Presentazione dello speech tenuto da Carmine Spagnuolo (Postdoctoral Research Fellow - Università degli Studi di Salerno/ ACT OR) dal titolo "Technology insights: Decision Science Platform", durante il Decision Science Forum 2019, il più importante evento italiano sulla Scienza delle Decisioni.
The Reality of Managing Microservices in Your CD PipelineDevOps.com
As we shift from monolithic software development practices to microservices, our well-designed CD pipeline will need to change. Microservices are small functions, deployed independently and linked via APIs at run-time. While these differences seem minor, they actually have a large impact on your overall CD structure. Think hundreds of workflows, small of any builds and the loss of a monolithic 'application.'
Join Tracy Ragan, CEO of DeployHub and Brendan O'Leary, Developer Evangelist at GitLab, to learn more.
It's never too early to start the conversation.
Presentation used at the CollabNet Dallas CI/CD/DevOps highly practical and interactive workshop which was designed to address specific challenges, opportunities and specific recommendations on how to scale CI, CD and DevOps across the enterprise to support decision making.
Docker has taken the software world by storm, but what does it actually mean for enterprise IT teams? Containers along with microservices are components definitely worth investigating for any modern software delivery pipeline when considering speed, portability and scalability.
Understanding whether they are right for you, and how you could introduce them into your enterprise tool chain and delivery pipeline can be challenging.
This is an educational webinar where you'll learn:
What Docker means for your existing software delivery processes
Practical considerations to successfully implement containers as part of your enterprise release pipeline
Common pitfalls when considering microservices technology for enterprise applications
The microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API.
In this slide we have discussed, Monolithic application vs Microservices, applicable scenarios for adopting the architectural pattern, when we need microservices, what are the benefits, case study of an e-commerce platform by compartmentalizing the scopes into different sample microservices and Docker implementations.
The full talk has been recorded here: https://youtu.be/tNlp7HS533g
An introduction to the technology underlying blockchains. If you want to hear a voice over, you can find it at http://presentationtube.com/watch?v=tCZDIEezrpbhttp://presentationtube.com/watch?v=tCZDIEezrpb
A collection of exercises to build a simple deployment pipeline. This comes from the course I have taught in DevOps and is targeted at instructors or individuals who want to learn the basics of a pipeline.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Le nuove frontiere dell'AI nell'RPA con UiPath Autopilot™UiPathCommunity
In questo evento online gratuito, organizzato dalla Community Italiana di UiPath, potrai esplorare le nuove funzionalità di Autopilot, il tool che integra l'Intelligenza Artificiale nei processi di sviluppo e utilizzo delle Automazioni.
📕 Vedremo insieme alcuni esempi dell'utilizzo di Autopilot in diversi tool della Suite UiPath:
Autopilot per Studio Web
Autopilot per Studio
Autopilot per Apps
Clipboard AI
GenAI applicata alla Document Understanding
👨🏫👨💻 Speakers:
Stefano Negro, UiPath MVPx3, RPA Tech Lead @ BSP Consultant
Flavio Martinelli, UiPath MVP 2023, Technical Account Manager @UiPath
Andrei Tasca, RPA Solutions Team Lead @NTT Data
The Metaverse and AI: how can decision-makers harness the Metaverse for their...Jen Stirrup
The Metaverse is popularized in science fiction, and now it is becoming closer to being a part of our daily lives through the use of social media and shopping companies. How can businesses survive in a world where Artificial Intelligence is becoming the present as well as the future of technology, and how does the Metaverse fit into business strategy when futurist ideas are developing into reality at accelerated rates? How do we do this when our data isn't up to scratch? How can we move towards success with our data so we are set up for the Metaverse when it arrives?
How can you help your company evolve, adapt, and succeed using Artificial Intelligence and the Metaverse to stay ahead of the competition? What are the potential issues, complications, and benefits that these technologies could bring to us and our organizations? In this session, Jen Stirrup will explain how to start thinking about these technologies as an organisation.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex ProofsAlex Pruden
This paper presents Reef, a system for generating publicly verifiable succinct non-interactive zero-knowledge proofs that a committed document matches or does not match a regular expression. We describe applications such as proving the strength of passwords, the provenance of email despite redactions, the validity of oblivious DNS queries, and the existence of mutations in DNA. Reef supports the Perl Compatible Regular Expression syntax, including wildcards, alternation, ranges, capture groups, Kleene star, negations, and lookarounds. Reef introduces a new type of automata, Skipping Alternating Finite Automata (SAFA), that skips irrelevant parts of a document when producing proofs without undermining soundness, and instantiates SAFA with a lookup argument. Our experimental evaluation confirms that Reef can generate proofs for documents with 32M characters; the proofs are small and cheap to verify (under a second).
Paper: https://eprint.iacr.org/2023/1886
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Enhancing Performance with Globus and the Science DMZGlobus
ESnet has led the way in helping national facilities—and many other institutions in the research community—configure Science DMZs and troubleshoot network issues to maximize data transfer performance. In this talk we will present a summary of approaches and tips for getting the most out of your network infrastructure using Globus Connect Server.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
2. Outline
• What is DevOps?
• What are the implications of DevOps practices
on system structure?
– Team practices.
– Deployment practices.
NICTA Copyright 2012
From imagination to impact
2
3. What is DevOps?
• “DevOps is a software development method that stresses
communication, collaboration, and integration between software
developers and IT professionals” – Wikipedia
• “DevOps is a new term describing what has also been called “agile
system administration” or “agile operations” joined together with the
values of agile collaboration between development and operations
staff.
Effectively, you can define DevOps as system administrators
participating in an agile development process alongside developers
and using a many of the same agile techniques for their systems
work. “ - http://theagileadmin.com/what-is-devops/
NICTA Copyright 2012
From imagination to impact
3
4. What is DevOps - 2
• DevOps is accompanied by a certain amount of
mysticism.
– “Be Self-Aware
– Be aware of a project’s maturity
– Be aware of others”
http://architects.dzone.com/articles/zen-and-art-collaborative
• Similar to the early days of agile.
NICTA Copyright 2012
From imagination to impact
4
5. What problem is DevOps trying to solve?
• Poor communication between developers and
operations personnel
• Slow release schedule
• Limited capacity of operations staff
• Limited organizational insight into operations
NICTA Copyright 2012
From imagination to impact
5
6. My Take on DevOps
• DevOps is a set of practices intended to
–
–
–
–
–
Reduce management overhead
Speed up deployment
Move some (formerly) IT responsibilities to developers
Increase communication between developers and operations
Reduce operations costs
• These practices have implications on
– Team size, communication, and responsibilities.
– Deployment
• In turn, there are implications for
– System structure
NICTA Copyright 2012
From imagination to impact
6
7. Outline
• What is DevOps?
• What are the implications of DevOps practices
on system structure?
– Team practices.
– Deployment practices.
NICTA Copyright 2012
From imagination to impact
7
9. Team Size
• Teams are small. Amazon has a “two pizza”
rule.
• It is easy for small teams to have good internal
coordination.
• Small teams mean
–
–
–
–
A lot of teams
Small scope for each team
Short delivery times
Coordination among teams
becomes an issue
NICTA Copyright 2012
From imagination to impact
9
10. Coordination among teams
• Asynchronous rather than synchronous
– Allows team members to respond when it is
convenient for them
– Avoids time zone coordination
• Persistent and visible
– E-mail is not generally visible to all of the team
– Chat boards, Wikis, issue trackers, comments in code
are all persistent and visible
– Connect a message to something – issue, feature,
person.
NICTA Copyright 2012
From imagination to impact
10
11. Team Responsibilities with respect to Services
• Requirements are sliced thinly both horizontally (breadth
of requirement) and vertically (decomposition of service
into utilities)
• Each service has an owner (a developer)
• Service owner decides when to deploy service to
production. Deployment done with tooling.
• Deployment may involve use of canaries (discussed with
deployment)
• When a service is deployed, service owner examines
monitoring data and decides when/if to roll back.
• Service owner is called if there is a problem.
NICTA Copyright 2012
From imagination to impact
11
12. Structural Implications of Team Practices
• Conway’s Law (1968)
– The structure of a system reflects the structure of the
organization that constructed the system.
• DevOps advocates
– Small teams
– Mostly independent teams
• Conway’s Law & many small, mostly
independent teams => Service Oriented
Architecture with
– Many services with small scope of each service
– Loose coupling between services
NICTA Copyright 2012
From imagination to impact
12
13. Outline
• What is DevOps?
• What are the implications of DevOps practices
on system structure?
– Team practices.
– Deployment practices.
NICTA Copyright 2012
From imagination to impact
13
14. Deployment Practices
• Deployment can be either an initial deployment
or an upgrade of an existing system.
• We will discuss
– Upgrade
– Continuous deployment
– Roll back
NICTA Copyright 2012
From imagination to impact
14
15. Deployment tools
• Have “recipes” for standard configurations
• Moving outside standard configurations may
introduce errors
• Recipes managed by DevOps group
• Configuration specification is version controlled
• Leads to “scripts are code too” mentality
– Development
– Staging
– Deployment
• Goal is to support developer’s ability to
automatically deploy
NICTA Copyright 2012
From imagination to impact
15
16. Upgrade
• How many at once?
– One at a time (rolling upgrade)
– Groups at a time (staged upgrade, e.g. canaries)
– All at once (big flip)
• Big flip requires double the number of resources.
Infeasible in environment that uses large
numbers of resources.
• Standard practice is rolling upgrade, possibly
with canaries.
NICTA Copyright 2012
From imagination to impact
16
17. Rolling Upgrade Process
• Suppose there are 100s or 1000s of
instances of an application running in the
cloud.
• Then it is too expensive to make a copy
of a new version while leaving the old
version running with all of its instances.
• The solution is to install the new version
on one server at a time – called a rolling
upgrade
• Figure on the right is an example of a
process for a rolling upgrade.
• This process is implemented by a
deployment tool.
Update Auto Scaling
Group
Sort Instances
Confirm Upgrade Spec
Remove & Deregister
Old Instance from ELB
Terminate Old
Instance
Wait for ASG to Start
New Instance
Register New Instance
with ELB
NICTA Copyright 2012
From imagination to impact
17
18. Upgrading a service within the service hierarchy
Suppose we are doing a rolling upgrade at Service
level N+1
Version B assumes new features from Service level
N+2
Service
level N
Service
level N+1
(A)
Service
level N+2
NICTA Copyright 2012
Service
level N+2
From imagination to impact
Service
level N+1
(B)
Service
level N+1
(B)
Service
level N+2
Service
level N+2
18
19. Staging Upgrades
• Service level N+2 must be activated before
activating service level N+1.
• Distinction between upgrading and activating.
Upgrades can occur at any time as long as they
are not activated.
• Structural implication
– Upgrades can be activated through software
switches. Could use Zookeeper for coordinating
active versions.
– Activates all of the instances at (essentially) same
time.
NICTA Copyright 2012
From imagination to impact
19
20. Upgrades can fail
• Functionally incorrect
• Incompatibility with other portions of the
application or infrastructure
• Resource limitations
• Configuration inconsistency
NICTA Copyright 2012
From imagination to impact
20
21. After failure is detected
• Turn off new features in level N+1 and its clients
(level N).
• May need to propagate to top of hierarchy.
• Structural implications
• Features are software switchable
• Require all versions to be backward compatible with previous
versions. If new version on level N+1 is switched off, do not need
to worry about level N+2.
NICTA Copyright 2012
From imagination to impact
21
22. Canaries
• Canaries are a small number of new versions in order to
perform live testing in a production environment.
• A/B testing is similar to canaries in that A/B testing
compares two proposed new interfaces. Different in that
canaries test new functionality.
NICTA Copyright 2012
From imagination to impact
22
23. Canary Issues
• Canaries are a form of live testing. Put a new
version into limited production to test its
correctness.
• Issues
– How long are new versions tested
to determine correctness?
• Period based – for some period of time
• Load based – under some utilization assumptions
• Result based – until some criteria is met
– How are clients of new version chosen and how is
this choice enforced?
NICTA Copyright 2012
From imagination to impact
23
24. Continuous Deployment
• Puts deployment decisions into developers hands.
• May mean simultaneous deployment from independent
teams. Some organizations report dozens of
deployments a day.
• Deployment tool must set configuration information e.g.,
in Zookeeper, so that services know what features are
currently active.
NICTA Copyright 2012
From imagination to impact
24
25. Structural Implications of Continuous
Deployment
• Packaging
• Maintaining Backward Compatibility
NICTA Copyright 2012
From imagination to impact
25
26. Packaging
• Two dimensions
– Flat vs deep service hierarchy
– One service per virtual machine vs many services per
virtual machine
NICTA Copyright 2012
From imagination to impact
26
27. Flat vs Deep Service Hierarchy
• Trading off independence of teams and
possibilities for reuse.
• Flat Service Hierarchy
– Limited dependence among services & limited
coordination needed among teams
– Difficult to reuse services
• Deep Service Hierarchy
– Provides possibility for reusing services
– Requires coordination among teams to discover
reuse possibilities.
NICTA Copyright 2012
From imagination to impact
27
28. Services per VM Image
One service per VM
VM image
Service
Develop
Embed
Multiple services per VM
Develop
Service
1
Embed
VM image
Develop
NICTA Copyright 2012
Service
2
From imagination to impact
Embed
28
29. One Possible Race Condition with Multiple
Services per VM
Initial State: VM image with Version N of Service 1 and Version N of Service 2
Developer 1
Developer 2
TIME
Build new image with VN+1|VN
Begin provisioning
process with new image
Build new image with VN|VN+1
Begin provisioning
process with new image
without new version of
Service 1
Results in Version N+1 of Service 1 not being
updated until next build of VM image
Could be prevented by VM image build tool
NICTA Copyright 2012
From imagination to impact
29
30. Another Possible Race Condition with Multiple
Services per VM
Initial State: VM image with Version N of Service 1 and Version N of Service 2
Developer 1
Developer 2
TIME
Build new image with VN+1|VN
Build new image with VN+1|VN+1
Begin provisioning
process with new image
overwrites image
created by developer 2
Begin provisioning
process with new image
Results in Version N+1 of Service 2 not being
updated until next build of VM image
Could be prevented by provisioning tool
NICTA Copyright 2012
From imagination to impact
30
31. Trade offs
• One service per VM
– Message from one service to another must go
through inter VM communication mechanism – adds
latency
– No possibility of race condition
• Multiple Services per VM
– Inter VM communication requirements reduced –
reduces latency
– Adds possibility of race condition caused by
simultaneous deployment
NICTA Copyright 2012
From imagination to impact
31
32. Motivating Backward Compatibility
• New version of a service may be introduced at
any time
• Existing clients of that service should not have to
be changed
• Require APIs and DB schemas to be backward
compatible.
NICTA Copyright 2012
From imagination to impact
32
33. Achieving Backwards Compatibility
• APIs and DB schemas can be extended but
must always be backward compatible.
• Leads to a translation layer
Client
Client
External APIs (unchanging but with ability to extend
or add new ones)
Translation to internal APIs
Internal APIs (changes require changes to
translation layer but do not propagate further)
NICTA Copyright 2012
From imagination to impact
34. Summary
• DevOps is a collection of practices that have
implications on system structure.
– These practices can be categorized into
• Team practices
• Deployment practices
• Some structural implications are
– Loosely coupled systems with deep hierarchy of
services
– Version aware
– Backward compatible
– Packaging services per VM
NICTA Copyright 2012
From imagination to impact
34