A DevOps experiment to make a Jira ticket describing a feature into a deployed application reachable at jira-ticket.serv.sg with a twist: the AWS infrastructure is dynamically created and destroyed once the feature is approved/rejected by the product team.
We use Slack, Jenkins, Ansible, Packer, Terraform, AWS, Jinja2 Cli, github
Building software by feature with immutable infrastructures on AWSNicolas Mas
How serv.sg deliver features using AWS infrastructure: programatically building and provisioning a stack before destroying it. This talk will explain what they do, why they do it and the tools they use (packer.io, terraform.io, ansible etc.). Includes a live demo of the whole cycle.
Video of the talk: http://engineers.sg/v/474
Continuous Delivery with TFS msbuild msdeployPeter Gfader
If you are deploying your software manually, you are doing it wrong.
If you deploying once a month, you are doing it wrong.
If you as a developer are deploying from Visual Studio by clicking "Publish", you are doing it wrong.
If a bug-fix takes you 1 hour but your customer needs to wait a week until he gets it, you are doing it wrong.
Manual deployments are NOT fun. See a good way on how to automate the deployment with TFS 2010, msbuild and msdeploy.
Pietro Di Bello, Paolo D'Incau - Continuous Delivery su progetti Java: cosa a...Codemotion
Condivideremo esperienze reali tratte da progetti dove applichiamo pratiche di Continous Delivery. Racconteremo di come si può far evolvere iterativamente una pipeline partendo da semplici task (build e deploy mono-ambiente) fino ad arrivare ad unica pipeline multi-ambiente ispirata allo stato dell’arte e alle lezioni che abbiamo imparato facendoci del male. Forniremo esempi concreti, focalizzandoci sugli aspetti relativi al codice, all’infrastruttura e rapporto con gli stakeholders.
London Atlassian User Group - February 2014Steve Smith
Continuous deployment is causing organisations to rethink how they build and release software. Atlassian Bamboo is rapidly adding features to help with automating deployment, but there are a lot of other practical and organisational issues that need to be addressed when adopting this development model. The Atlassian business-platforms team has been dealing with these issues over the last few months as we transition our order system to continuous deployment. This talk will cover why we adopted this model, some of challenges we encountered, and the approaches and tools we used to overcome them.
Building software by feature with immutable infrastructures on AWSNicolas Mas
How serv.sg deliver features using AWS infrastructure: programatically building and provisioning a stack before destroying it. This talk will explain what they do, why they do it and the tools they use (packer.io, terraform.io, ansible etc.). Includes a live demo of the whole cycle.
Video of the talk: http://engineers.sg/v/474
Continuous Delivery with TFS msbuild msdeployPeter Gfader
If you are deploying your software manually, you are doing it wrong.
If you deploying once a month, you are doing it wrong.
If you as a developer are deploying from Visual Studio by clicking "Publish", you are doing it wrong.
If a bug-fix takes you 1 hour but your customer needs to wait a week until he gets it, you are doing it wrong.
Manual deployments are NOT fun. See a good way on how to automate the deployment with TFS 2010, msbuild and msdeploy.
Pietro Di Bello, Paolo D'Incau - Continuous Delivery su progetti Java: cosa a...Codemotion
Condivideremo esperienze reali tratte da progetti dove applichiamo pratiche di Continous Delivery. Racconteremo di come si può far evolvere iterativamente una pipeline partendo da semplici task (build e deploy mono-ambiente) fino ad arrivare ad unica pipeline multi-ambiente ispirata allo stato dell’arte e alle lezioni che abbiamo imparato facendoci del male. Forniremo esempi concreti, focalizzandoci sugli aspetti relativi al codice, all’infrastruttura e rapporto con gli stakeholders.
London Atlassian User Group - February 2014Steve Smith
Continuous deployment is causing organisations to rethink how they build and release software. Atlassian Bamboo is rapidly adding features to help with automating deployment, but there are a lot of other practical and organisational issues that need to be addressed when adopting this development model. The Atlassian business-platforms team has been dealing with these issues over the last few months as we transition our order system to continuous deployment. This talk will cover why we adopted this model, some of challenges we encountered, and the approaches and tools we used to overcome them.
Webhooks with Azure Functions - Live 360 ConferenceSparkPost
Azure Functions make it easy to create and host webhook interfaces without maintaining a server. You can quickly setup an endpoint to receive data and act on it. Being able to ingest, process, and respond to data from a variety of sources without building out an infrastructure gives you time to focus on building functionality.
In this presentation, Nick Zimmerman, Sr. Site Reliability Engineer at SparkPost, will show you how to setup an Azure Function, accept webhook data, process that data with C#, and integrate that data into an application in real time.
Why is Performance important?
Applications in general
Web applicaitons
What can we as devs do?
Tips: How to optimize
Web applications, Silverlight, Backend, …
Regression
How to maintain performance over time
How to get faster over time
Discussion: What tips do you have in your toolbox?
These slides are about my personal experience from creating a continuous delivery process in the last 2 years.
The main focus lies in the tools I used and my experience with them.
10 Deployments a day - A brief on extreme release protocolsVivek Parihar
A reflection on how we migrated from an era of production deployments once a week to more than 10 deployments a day. The story of transforming a mere sys-admin to super sophisticated DevOps team, armed with multiple tools, scripts and plugins for achieving automations, accuracy and invincible agility. As we continue on our endeavor for further improvisation, I believe its worth sharing the experience with community. Tentative topics outline:
1.Arming teams for their transformation to DevOps from mere sys-admins.
2.Killing manual deployments (manual deployment->capistrano->webistrano)
3.Automation (for daily backups,monitoring applications and servers deploying dependencies)
4.Saving up time on setting up new instances(using golden image).
5.Using LDAP to maintain servers with public key(avoiding individual logins to every server makes it less messy)
6.Using Puppet for instantiating multiple servers at once.
7.Commissioning our own Cloud Infrastructure.
Continuous Delivery su progetti Java: cosa abbiamo imparato facendoci del malePietro Di Bello
In questa presentazione io e Paolo D'Incau condividiamo esperienze reali tratte da progetti dove applichiamo pratiche di Continous Delivery.
Raccontiamo di come si può far evolvere iterativamente una pipeline partendo da semplici task (build e deploy mono-ambiente) fino ad arrivare ad unica pipeline multi-ambiente ispirata allo stato dell'arte e alle lezioni che abbiamo imparato facendoci del male.
Forniamo esempi concreti, focalizzandoci sugli aspetti relativi al codice, all'infrastruttura e rapporto con gli stakeholders.
Autori: Paolo D'Incau, Pietro Di Bello
Confoo-Montreal-2016: Controlling Your Environments using Infrastructure as CodeSteve Mercier
Slides from my talk at ConFoo Montreal, February 2016. A presentation on how to apply configuration management (CM) principles for your various environments, to control changes made to them. You apply CM on your code, why not on your environments content? This presentation will present the infrastructure as code principles using Chef and/or Ansible. Topics discussed include Continuous Integration, Continuous Delivery/Deployment principles, Infrastructure As Code and DevOps.
North American Collaboration Summit 2018 - SharePoint Framework, Angular & Az...Sébastien Levert
Things are moving fast. Sometimes you might even feel that you own comfort zone is getting of control. But in a Mobile-First, Cloud-First world, things are changing to a crazy pace and to stay on the top of your game, you need keep up with the latest and greatest technologies that are available out there. By staying up to date, you will give to yourself new options that will let you be more productive, write better code and push you in a more open and more collaborative world.
With the official shipment of Angular 5 and the current release of the SharePoint Framework, it is now the time to start moving towards those new technologies in your SharePoint Solutions.
In this session, we will cover the modern tool belt of the SharePoint developer by covering the SharePoint Framework as the new surface to express yourself, Angular as a Framework to enable you to build complete applications within your SharePoint modern experiences and Azure Function as the perfect server-side companion for all your Office 365 & Azure development.
This very demo-intensive session will make sure that at the end you get those 3 key takeaways :
- Understand the role of the SharePoint Framework, Angular and Azure Functions in this Cloud-First, Mobile-First world
- Have a complete sample where the modern tool belt is relevant and useful in a real-world scenario
- Change the way you will think for your next SharePoint project
Closer To the Metal - Why and How We Use XCTest and Espresso by Mario Negro P...Sauce Labs
In this SauceCon 2019 presentation, Mario describes the practices that ABN AMRO adopted in mobile teams when it comes to testing native applications on real devices. Since using Espresso and XCUITest is still relatively uncommon for large apps and there are various unique challenges due to being in an EU-regulated industry with various security restrictions, Mario will share the ABN AMRO team’s experiences, including:
- A brief architectural overview of the Mobile Banking app: why it is all native (Objective-C/Swift and Java/Kotlin), how it communicates with other apps and websites
- Why ABN AMRO choose to adopt Espresso and XCUITest: the advantages and the limitations of this choice
- How ABN AMRO runs their test pipelines to spread them across time and devices and prevent teams from being blocked
WinOps Conf 2016 - Matteo Emili - Development and QA Dilemmas in DevOpsWinOps Conf
The quick rise of Continuous Delivery in the enterprise means that common problems are often approached the other way round. Concepts like Feature Flags and Testing In Production caused several headaches to developers and QA engineers, especially where they have a wealth of experience about traditional development.
There are some challenges and approaches which are very common, and they still scare newcomers. Let's have a look at a few of these, with the most common solutions.
Continuous Integration, the minimum viable productJulian Simpson
What does it mean to 'do' Continuous Integration? It used to be enough to execute your unit tests in CI. But the bar is steadily raising for engineering practices. In the last decade we've seen tremendous improvements inacceptance testing. JavaScript is now a platform in it's own right. Cloudcomputing is now vital. There's growing interest in deployment to prod.So Continuous Integration is under more pressure than ever. As the bar slowly raises for engineering practices, we ll present 2011's minimum viable feature set for Continuous Integration
Presentation given at SPNHC 2015, Gainsville, FL
Kurator: An extensible, open-source workflow platform for users and makers of data curation tools
B. Ludäscher, J. Hanken, D. Lowery, J.A. Macklin, T. McPhillips, P.J. Morris, R.A. Morris, T. Song
The recently funded Kurator project builds upon earlier experiences with workflow-based approaches for quality control of biodiversity data. We are developing workflow components (“actors”) to examine data collections and perform checks, e.g., on scientific names, name authorship, collecting date, collector name (recorded by), georeference, locality, and phenological state (where applicable). Kurator is based on a number of ideas: 1) We allow “cleaning data with data”: in addition to checking the internal consistency of records, we can employ external resources to spot quality issues and suggest repairs. 2) Human curators remain in control: Kurator tools keep track of processing history and data lineage (computational provenance) to show original records, alternative forms and the respective sources, thus allowing human curators to make informed decisions about which suggested repairs and flagged records require action. 3) Kurator aims to serve both makers of data curation tools and end users. Initially, we are focusing on a modular, easily extensible approach to data curation workflows and scripts so that curation tool makers (ourselves included) are empowered to quickly develop new curation functionality. We also need to expose curation sources and curation logic to make programming of new features easy and In the second phase, the Kurator toolkit will also include a web interface for end users who might not be programmers or tool makers themselves. The ultimate goal is to allow users who don’t think of themselves as tool makers to build more complex curation workflows from simple components, thus diminishing the gap between makers and users.
Continuous Delivery using blue-green deployments and immutable infrastructure...Rubén Rubio Rey
Immutable Infrastructure is a topic drawing large amount of attention, namely as a reliable, safe, and effective system architecture pattern to manage server infrastructure generally in cloud ecosystems. Using this concept along with blue-green deployments, a powerful and versatile paradigm opens paving the way for rapid and low-risk deployments with minimal human and infrastructure over-head.
Webhooks with Azure Functions - Live 360 ConferenceSparkPost
Azure Functions make it easy to create and host webhook interfaces without maintaining a server. You can quickly setup an endpoint to receive data and act on it. Being able to ingest, process, and respond to data from a variety of sources without building out an infrastructure gives you time to focus on building functionality.
In this presentation, Nick Zimmerman, Sr. Site Reliability Engineer at SparkPost, will show you how to setup an Azure Function, accept webhook data, process that data with C#, and integrate that data into an application in real time.
Why is Performance important?
Applications in general
Web applicaitons
What can we as devs do?
Tips: How to optimize
Web applications, Silverlight, Backend, …
Regression
How to maintain performance over time
How to get faster over time
Discussion: What tips do you have in your toolbox?
These slides are about my personal experience from creating a continuous delivery process in the last 2 years.
The main focus lies in the tools I used and my experience with them.
10 Deployments a day - A brief on extreme release protocolsVivek Parihar
A reflection on how we migrated from an era of production deployments once a week to more than 10 deployments a day. The story of transforming a mere sys-admin to super sophisticated DevOps team, armed with multiple tools, scripts and plugins for achieving automations, accuracy and invincible agility. As we continue on our endeavor for further improvisation, I believe its worth sharing the experience with community. Tentative topics outline:
1.Arming teams for their transformation to DevOps from mere sys-admins.
2.Killing manual deployments (manual deployment->capistrano->webistrano)
3.Automation (for daily backups,monitoring applications and servers deploying dependencies)
4.Saving up time on setting up new instances(using golden image).
5.Using LDAP to maintain servers with public key(avoiding individual logins to every server makes it less messy)
6.Using Puppet for instantiating multiple servers at once.
7.Commissioning our own Cloud Infrastructure.
Continuous Delivery su progetti Java: cosa abbiamo imparato facendoci del malePietro Di Bello
In questa presentazione io e Paolo D'Incau condividiamo esperienze reali tratte da progetti dove applichiamo pratiche di Continous Delivery.
Raccontiamo di come si può far evolvere iterativamente una pipeline partendo da semplici task (build e deploy mono-ambiente) fino ad arrivare ad unica pipeline multi-ambiente ispirata allo stato dell'arte e alle lezioni che abbiamo imparato facendoci del male.
Forniamo esempi concreti, focalizzandoci sugli aspetti relativi al codice, all'infrastruttura e rapporto con gli stakeholders.
Autori: Paolo D'Incau, Pietro Di Bello
Confoo-Montreal-2016: Controlling Your Environments using Infrastructure as CodeSteve Mercier
Slides from my talk at ConFoo Montreal, February 2016. A presentation on how to apply configuration management (CM) principles for your various environments, to control changes made to them. You apply CM on your code, why not on your environments content? This presentation will present the infrastructure as code principles using Chef and/or Ansible. Topics discussed include Continuous Integration, Continuous Delivery/Deployment principles, Infrastructure As Code and DevOps.
North American Collaboration Summit 2018 - SharePoint Framework, Angular & Az...Sébastien Levert
Things are moving fast. Sometimes you might even feel that you own comfort zone is getting of control. But in a Mobile-First, Cloud-First world, things are changing to a crazy pace and to stay on the top of your game, you need keep up with the latest and greatest technologies that are available out there. By staying up to date, you will give to yourself new options that will let you be more productive, write better code and push you in a more open and more collaborative world.
With the official shipment of Angular 5 and the current release of the SharePoint Framework, it is now the time to start moving towards those new technologies in your SharePoint Solutions.
In this session, we will cover the modern tool belt of the SharePoint developer by covering the SharePoint Framework as the new surface to express yourself, Angular as a Framework to enable you to build complete applications within your SharePoint modern experiences and Azure Function as the perfect server-side companion for all your Office 365 & Azure development.
This very demo-intensive session will make sure that at the end you get those 3 key takeaways :
- Understand the role of the SharePoint Framework, Angular and Azure Functions in this Cloud-First, Mobile-First world
- Have a complete sample where the modern tool belt is relevant and useful in a real-world scenario
- Change the way you will think for your next SharePoint project
Closer To the Metal - Why and How We Use XCTest and Espresso by Mario Negro P...Sauce Labs
In this SauceCon 2019 presentation, Mario describes the practices that ABN AMRO adopted in mobile teams when it comes to testing native applications on real devices. Since using Espresso and XCUITest is still relatively uncommon for large apps and there are various unique challenges due to being in an EU-regulated industry with various security restrictions, Mario will share the ABN AMRO team’s experiences, including:
- A brief architectural overview of the Mobile Banking app: why it is all native (Objective-C/Swift and Java/Kotlin), how it communicates with other apps and websites
- Why ABN AMRO choose to adopt Espresso and XCUITest: the advantages and the limitations of this choice
- How ABN AMRO runs their test pipelines to spread them across time and devices and prevent teams from being blocked
WinOps Conf 2016 - Matteo Emili - Development and QA Dilemmas in DevOpsWinOps Conf
The quick rise of Continuous Delivery in the enterprise means that common problems are often approached the other way round. Concepts like Feature Flags and Testing In Production caused several headaches to developers and QA engineers, especially where they have a wealth of experience about traditional development.
There are some challenges and approaches which are very common, and they still scare newcomers. Let's have a look at a few of these, with the most common solutions.
Continuous Integration, the minimum viable productJulian Simpson
What does it mean to 'do' Continuous Integration? It used to be enough to execute your unit tests in CI. But the bar is steadily raising for engineering practices. In the last decade we've seen tremendous improvements inacceptance testing. JavaScript is now a platform in it's own right. Cloudcomputing is now vital. There's growing interest in deployment to prod.So Continuous Integration is under more pressure than ever. As the bar slowly raises for engineering practices, we ll present 2011's minimum viable feature set for Continuous Integration
Presentation given at SPNHC 2015, Gainsville, FL
Kurator: An extensible, open-source workflow platform for users and makers of data curation tools
B. Ludäscher, J. Hanken, D. Lowery, J.A. Macklin, T. McPhillips, P.J. Morris, R.A. Morris, T. Song
The recently funded Kurator project builds upon earlier experiences with workflow-based approaches for quality control of biodiversity data. We are developing workflow components (“actors”) to examine data collections and perform checks, e.g., on scientific names, name authorship, collecting date, collector name (recorded by), georeference, locality, and phenological state (where applicable). Kurator is based on a number of ideas: 1) We allow “cleaning data with data”: in addition to checking the internal consistency of records, we can employ external resources to spot quality issues and suggest repairs. 2) Human curators remain in control: Kurator tools keep track of processing history and data lineage (computational provenance) to show original records, alternative forms and the respective sources, thus allowing human curators to make informed decisions about which suggested repairs and flagged records require action. 3) Kurator aims to serve both makers of data curation tools and end users. Initially, we are focusing on a modular, easily extensible approach to data curation workflows and scripts so that curation tool makers (ourselves included) are empowered to quickly develop new curation functionality. We also need to expose curation sources and curation logic to make programming of new features easy and In the second phase, the Kurator toolkit will also include a web interface for end users who might not be programmers or tool makers themselves. The ultimate goal is to allow users who don’t think of themselves as tool makers to build more complex curation workflows from simple components, thus diminishing the gap between makers and users.
Continuous Delivery using blue-green deployments and immutable infrastructure...Rubén Rubio Rey
Immutable Infrastructure is a topic drawing large amount of attention, namely as a reliable, safe, and effective system architecture pattern to manage server infrastructure generally in cloud ecosystems. Using this concept along with blue-green deployments, a powerful and versatile paradigm opens paving the way for rapid and low-risk deployments with minimal human and infrastructure over-head.
Creating and maintaining different environments can be difficult and a real time-sink. We'll see in this talk how you can automate this tasks by building and updating your development and production environments on demand using Chef, Vagrant, Docker and Amazon Web Services.
CI and CD Across the Enterprise with Jenkins (devops.com Nov 2014)CloudBees
Delivering value to the business faster thanks to Continuous Delivery and DevOps is the new mantra of IT organizations. In this webinar, CloudBees will discuss how Jenkins, the most popular open source Continuous Integration tool, allows DevOps teams to implement Continuous Delivery.
You will learn how to:
* Orchestrate Continuous Delivery pipelines with the new workflow feature,
* Scale Jenkins horizontally in your organization using Jenkins Operations Center by CloudBees,
* Implement end to end traceability with Jenkins and Puppet and Chef.
http://devops.com/news/ci-and-cd-across-enterprise-jenkins/
https://github.com/CloudBees-community/vagrant-puppet-petclinic
I recently presented this 2 hours session about the automation model developed in Videobet, the tools used in the R&D, QA and operations:
Issue mgmt.: JIRA/Greenhopper
Build system and repository: Maven & Nexus
Build server: QuickBuild
Code quality: Sonar
Continuous Integration: Selenium Grid
Crash dump analysis: Socorro
Database versioning: Flyway DB
Many of our customers have adopted DevOps for faster and reliable software delivery. Applying software engineering best practices such as revision control and continuous delivery to your infrastructure is essential for adopting DevOps.
In this session, find out how AWS CloudFormation and the associated AWS tools enable DevOps by allowing you to treat infrastructure as code and applying those software engineering best practices to your infrastructure.
Speakers:
Steven Bryen, AWS Solutions Architect
Bruce Jackson, Chief Technology Officer, Myriad Group
Rajpal Singh Wilkhu,Principal Engineer, Just Eat
Infrastructure as Code (IaC), how to choose the right tool, terraform vs. CDK vs. Pulumi, best practices, Principles, and a lot of the underlying principles are described in this crash course.
Pilot Tech Talk #10 — Practical automation by Kamil CholewińskiPilot
See how Kamil Cholewiński talks about Practical automation in Tech Talk episode 10
Visit pilot.co — World’s best engineering and design talent on demand.
YouTube: https://youtu.be/x0eQ7x7xN8o
Scaling Up Lookout was originally presented at Lookout's Scaling for Mobile event on July 25, 2013. R. Tyler Croy is a Senior Software Engineer at Lookout, Inc. Lookout has grown immensely in the last year. We've doubled the size of the company—added more than 80 engineers to the team, support 45+ million users, have over 1000 machines in production, see over 125,000 QPS and more than 2.6 billion requests/month. Our analysts use Hadoop, Hive, and MySQL to interactively manipulate multibillion row tables. With that, there are bound to be some growing pains and lessons learned.
Hadoop: Big Data Stacks validation w/ iTest How to tame the elephant?Dmitri Shiryaev
. Problem we are facing
. Big Data Stacks
. Why validation
. What is "Success" and the effort to achieve it
. Solutions
. Ops testing
. Platform certification
. Application testing
. Stack on stack
. Test artifacts are First Class Citizen
. Assembling validation stack (vstack)
. Tailoring vstack for target clusters
. D3: Deployment/Dependencies/Determinism
Deep dive - Concourse CI/CD and PipelinesSyed Imam
A deep dive into how Nine Publishing (formerly Fairfax media) continuously deliver and integrate new features and bug fixes into the microservices platform.
Investing in a good software factory and automating the build processNicolas Mas
Talk from a Singapore Spring user group. Investing in a software factory, automating it as much as possible. Can we also automate the creation of the software factory?
"Veuillez valider votre titre de transport, merci", dit une voix féminine douce à un groupe de passagers qui vient de s’engouffrer
par la porte arrière du véhicule Il y a deux ans à peine, c’est le chauffeur lui-même qui aurait fait l'effort de rappeler à l'ordre les passagers n’ayant pas validé leur coupon. Aujourd'hui, le chauffeur dispose d’un bouton qui déclenche les différentes phrases pré-enregistrées en fonction des situations.
Pensez-vous que le futur del'intégration des mondes virtuels avec Internet signifie parcourir des allées d'un magasin virtuel en 3D ou pousser les touches en 3D d'un distributeur de billets virtuel ? Nous pensons que non ! Internet propose déjà de nombreuses interfaces efficaces et ergonomiques pour effectuer ce type d'action. Il serait idiot de revenir en arrière en
reproduisant ces actions dans des espaces virtuels qui suppriment complètement l'intérêt de telles interfaces.
Virtual Worlds : Anew kind of Sociability FrNicolas Mas
Avec son mélange de textes, graphiques, images et vidéos, Internet permet aux utilisateurs de parcourir rapidement un important volume d'information. Or l’être humain est avant tout un animal social qui a besoin de vivre l’information, sous la forme d’un mélange de contenu « live » et de présence. Le Web s’est donc progressivement doté d’un aspect communautaire - le Web 2.0 - permettant d’influer sur les contenus et de les personnaliser. Son évolution sociale naturelle : les mondes virtuels.
Depuis quelques temps nous parlons beaucoup de mondes virtuels, de 3D sur Internet (le Web 3D), de Web 2.0 et autres médias sociaux. Mais quel est le point commun à tout cela ? L'Information - ou plutôt les informations, les données.
Qu'est-ce qu'un site Internet si ce n'est la mise en forme du contenu d'une base de données ? Qu'est-ce qu'un chat si ce n'est un échange d'information entre deux ou plusieurs individus ? Qu'est-ce qu'un avatar si ce n'est une représentation (symbolique) des informations concernant un individu (fantasmé ou non) ?
Ce document est une synthèse de notre intervention à l'École Nationale Supérieure des Beaux-arts (Paris) lors des Journées PraTIC de Mars 2009
L'Homme n'est plus le seul à disposer d'un double interactif. Pour s'interfacer avec les objets communicants, nous préconisons le recours à des avatars susceptibles de représenter aussi bien la machine, que des programmes voire des institutions.
« Les avatars comme médiateurs autonomes entre réel et virtuel »
par Yohan Launay et Nicolas Mas, ingénieurs de ConceptSL
L’humain n’est plus le seul à disposer d’un double interactif. Pour s’interfacer avec les objets communicants, ces ingénieurs-conseils préconisent le recours à des avatars susceptibles de
représenter aussi bien la machine, des programmes, voire des institutions. Quelques cas concrets aideront à cerner ces évolutions à la fois technologiques et sociétales.
http://nicolasmas.typepad.com/nm/2009/03/conceptsl-intervenant-aux-journ%C3%A9es-d%C3%A9tude-pratic-avatars-en-ligne-lundi-23-mars-2009-par-nicolas-mas.html
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
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/
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
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.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
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.
DevOps: Building by feature with immutable infrastructure at Serv.sg
1. How we build features at
Serv.sg
in a Pandan Leaf...
November 25th 2015
Nicolas Mas
Nicolas@serv.sg
Nicolas.Mas@gmail.com
https://www.linkedin.com/in/nicolasmas
https://github.com/nicolasmas
2. Acknowledgment
“Alone we can do so little; together we can
do so much”
Sandeep Isac Marco Yang Alex Hayden
Alexander Bulat Andrei Ping Yang
3. What this talk won’t do
⬗ Entertain you with funny
pictures (sorry). This will be
the only one.
⬗ Describe the tools being
used, unless there is a
specific request (let’s keep
the focus).
⬗ Guarantee that Murphy’s law
won’t impact the demo.
4. So what is it going to be?
⬗ What do we do at Serv.sg?
⬗ Our (current) technology stack
⬗ Feature build (+ DEMO)
⬗ What is the problem we solved?
⬗ Limits
⬗ Enhancements
⬗ B Tracks: if we really have time
Disclaimer: I am a DevOps padawan, what is described tonight is probably
not the best solution ever. Any suggestion is welcome~
5. What we do at Serv.sg
✓ Real time Mobile workforce location tracking
✓ Automated scheduling of service appointments
✓ Automated email / SMS reminders of upcoming appointments and contracts.
✓ Manage customer data and all history of service appointments
✓ Manage Services offered, including recurring contracts and packages, etc.
✓ Advanced reports on employee utilization as well as business
10. It all starts in Jira
⬗ The developer takes ownership of, let’s say the item “JIRA-456” during a
sprint.
⬘ Actually, he does not do it in JIRA, but from github by branching out the
codebase.
⬘ The Branch HAS TO BE named after the jira item, e.g. JIRA-456
11. It continues on Slack
⬗ The moment the branch is created, we can actually build the
infrastructure:
⬘ In slack: “/serv-branch-build”
⬗ Slack is asking a Jenkins job to monitor the github repository for
new/deleted branches
12. What happens in the jenkins monitoring job
⬗ The Jenkins job will do a few things:
⬘ 1. It will connect to github and get all the branches
⬘ 2. It will detect our new branch
⬘ 3. A custom jenkins job will be created for that branch
⬘ Terraform will be invocated
⬗ It will also keep you updated of the progress in Slack
13. The Infra is built...
...But not yet provisioned !!
Note: we use a pre-baked OS image for
the instances
17. Destroying the build
⬗ The features has been validated or ditched, the branch is either merged
or destroyed on github
Note: If we need a few back and forth between the product and the dev for the
feature, it’s just a matter of running the jenkins branch job to deploy again
18. Back in Slack
⬗ “/serv-branch-build”
⬗ AWS quick check.. the instances are terminated
19. BTW, What problem are we solving?
⬗ Deploying by feature is not new. Immutable infra seems to be less
common. The two combined? Anyone doing it?
⬗ From a business/product perspective
⬘ More responsive to bug fixing, features deliveries
⬘ No confusion on what has been deployed
⬘ The branch can be hotfixed => one step closer to CD
⬗ From a technical perspective
⬘ Leveraging the cloud infrastructure, programmatically
⬘ No environment recycling or reconfiguring with the related uncertainty
⬘ As close to production as we can
⬘ A good way to craft baked OS with the latest update and test it
20. Limits/Challenges
⬗ Hard to keep track of the full cycle, from the OS baking to the feature
deployed:
⬘ Packer: need to manually describe the target provisioned OS. Hard to test,
need to manage the produced artifacts
⬘ Ansible: need to manually write the roles, hard to test and a pain to
maintain
⬘ Terraform: need to manually describe the infra, hard to test, painful to
maintain and evolve. Some bugs with route 53
⬘ Dependency on Jenkins
⬘ A fair amount of templating (jinja2 style) with a risk induced by the dynamic
aspect of the build (hostnames, EIP...)
⬗ Many pieces in movement, dependency
⬗ Need to be in sync with the product team to check and act upon the
feature as soon as it is available. We don’t want a stack running for ages..
21. Enhancement
⬗ Use a tool to orchestrate the branch + infra build aspect (Spinnaker.io?
StackStorm.io?) or build a simple micro service to do it
⬗ Choose the branch to build in slack instead of all the branches with the
pattern “JIRA-XYZ”
⬗ Improve the provisioning and better manage the ansible playbook
(Tower.io?)
⬗ How is this compatible with our next architecture steps? (micro services)
22. Bonus Track - Did you know ?
“The mother of all demos” http://en.wikipedia.
org/wiki/The_Mother_of_All_Demos
⬗ Douglas Engelbart's December 9, 1968
⬗ 90-minute live public demonstration of the online system, NLS, they had
been working on since 1962
⬗ 1000 attendees and a demo of almost all features we use today
⬘ Mouse
⬘ hypertext, object addressing and dynamic file linking
⬘ shared-screen collaboration involving two persons at different sites
communicating over a network with audio and video interface.
http://web.stanford.
edu/dept/SUL/library/extra4/sloan/mousesite/1968Demo.html