Openstack dev on
•Download as PPTX, PDF•
0 likes•400 views
The document discusses OpenStack and its readiness for public service. It questions whether OpenStack is ready to handle issues like scalability, reliability, and security needed for public clouds. OpenStack responds that it provides basic tools and APIs, but that each implementation needs to address weaknesses and ensure their own applications and infrastructure are cloud-ready. It concludes that OpenStack provides open source tools, not complete solutions, and users need to improve upon and test the tools for their own needs.
Report
Share
Report
Share
Recommended
Blast Radius
A talk I gave a DevopsdayGalway about continuous deployment and minimising how much you deploy for any given commit.
Anti patterns of testing for continuous delivery adoption
Presentation on World Conference on Next Generation Testing 2015 conducted at Bangalore,India on ' Anti Patterns of Testing for Continuous Delivery adoption'. This presentation covered the anti patterns of testing during the continuous delivery adoption. It covered the details related to Collaboration, test automation architecture, test suite organization, lack of test strategy for parallel execution in the build pipeline, test code issues and some others.It also highlighted how it is difficult for any team to adopt continuous delivery in true sense and and further move into the continuous deployment and Devops practices due to such challenges.
Principles Of Chaos Engineering - Chaos Engineering Hamburg
This document discusses chaos engineering and its principles. It provides an agenda for a talk on AWS basics, the evolution of chaos testing, tooling for chaos engineering, and chaos engineering itself. It describes how chaos engineering experiments are used to test systems by simulating failures like instance or availability zone outages. The key principles of chaos engineering are to understand normal system behavior, build hypotheses around steady states, vary real-world events by conducting experiments in production, and automate experiments continuously. Popular tools for chaos engineering include Chaos Monkey, Chaos Gorilla, and Chaos Kong.
Chaos Engineering when you're not Netflix
This document discusses chaos engineering and how organizations that are not Netflix can implement it. It begins with defining chaos engineering as experimenting on systems to build confidence in their ability to withstand turbulent conditions. It then discusses why Netflix uses chaos engineering due to their large scale microservices architecture. While most organizations are not the size of Netflix, the document outlines how chaos engineering can still be beneficial by challenging common assumptions about architectures and validating system resilience. It provides examples of chaos engineering experiments and tools that can be used to implement chaos engineering.
Chaos Engineering - Limiting Damage During Chaos Experiments
When doing chaos experiments, how can we avoid damage and how can we limit experiments to certain infrastructure/application parts.
Orca webinar: Fix Your Configs Before You Wreck Your Release
Speedy software releases are great. But speedy software releases free of configuration errors are even better. Agile and DevOps-oriented Dev teams work hard to deliver new software, but they are often in the dark regarding the latest Production-level configurations in their application, middleware, databases and operating systems. Capturing, comparing, and keeping configs in compliance is a time-consuming, error-prone mess for Ops teams – and nearly impossible for Dev.
DevSecCon Singapore 2018 - Insecurity in information technology by Tanya Janca
The document discusses insecurity in information technology and its negative effects such as deviant behavior, moral disengagement, and reduced job involvement. It recommends supporting development and security teams with training, processes, and resources so they can do their jobs confidently. It also recommends initiating and maintaining a culture change.
Puppet Camp Portland 2015: Keynote
Lindsey Smith from Puppet Labs discusses the benefits of automating IT infrastructure using Puppet to define and enforce a desired state. Puppet allows organizations to standardize configurations, accelerate change processes, and gain insights into infrastructure changes. It helps teams deploy code more frequently with fewer failures, contributing to higher business performance. Puppet is an open source tool for automating server configuration management tasks like firewalls, packages, and services across physical, virtual, and cloud environments.
Recommended
Blast Radius
A talk I gave a DevopsdayGalway about continuous deployment and minimising how much you deploy for any given commit.
Anti patterns of testing for continuous delivery adoption
Presentation on World Conference on Next Generation Testing 2015 conducted at Bangalore,India on ' Anti Patterns of Testing for Continuous Delivery adoption'. This presentation covered the anti patterns of testing during the continuous delivery adoption. It covered the details related to Collaboration, test automation architecture, test suite organization, lack of test strategy for parallel execution in the build pipeline, test code issues and some others.It also highlighted how it is difficult for any team to adopt continuous delivery in true sense and and further move into the continuous deployment and Devops practices due to such challenges.
Principles Of Chaos Engineering - Chaos Engineering Hamburg
This document discusses chaos engineering and its principles. It provides an agenda for a talk on AWS basics, the evolution of chaos testing, tooling for chaos engineering, and chaos engineering itself. It describes how chaos engineering experiments are used to test systems by simulating failures like instance or availability zone outages. The key principles of chaos engineering are to understand normal system behavior, build hypotheses around steady states, vary real-world events by conducting experiments in production, and automate experiments continuously. Popular tools for chaos engineering include Chaos Monkey, Chaos Gorilla, and Chaos Kong.
Chaos Engineering when you're not Netflix
This document discusses chaos engineering and how organizations that are not Netflix can implement it. It begins with defining chaos engineering as experimenting on systems to build confidence in their ability to withstand turbulent conditions. It then discusses why Netflix uses chaos engineering due to their large scale microservices architecture. While most organizations are not the size of Netflix, the document outlines how chaos engineering can still be beneficial by challenging common assumptions about architectures and validating system resilience. It provides examples of chaos engineering experiments and tools that can be used to implement chaos engineering.
Chaos Engineering - Limiting Damage During Chaos Experiments
When doing chaos experiments, how can we avoid damage and how can we limit experiments to certain infrastructure/application parts.
Orca webinar: Fix Your Configs Before You Wreck Your Release
Speedy software releases are great. But speedy software releases free of configuration errors are even better. Agile and DevOps-oriented Dev teams work hard to deliver new software, but they are often in the dark regarding the latest Production-level configurations in their application, middleware, databases and operating systems. Capturing, comparing, and keeping configs in compliance is a time-consuming, error-prone mess for Ops teams – and nearly impossible for Dev.
DevSecCon Singapore 2018 - Insecurity in information technology by Tanya Janca
The document discusses insecurity in information technology and its negative effects such as deviant behavior, moral disengagement, and reduced job involvement. It recommends supporting development and security teams with training, processes, and resources so they can do their jobs confidently. It also recommends initiating and maintaining a culture change.
Puppet Camp Portland 2015: Keynote
Lindsey Smith from Puppet Labs discusses the benefits of automating IT infrastructure using Puppet to define and enforce a desired state. Puppet allows organizations to standardize configurations, accelerate change processes, and gain insights into infrastructure changes. It helps teams deploy code more frequently with fewer failures, contributing to higher business performance. Puppet is an open source tool for automating server configuration management tasks like firewalls, packages, and services across physical, virtual, and cloud environments.
Intro to Devops
The document introduces DevOps and discusses its goals of simplicity, no code, and minimal jargon. DevOps is defined as the combination of cultural philosophies, practices, and tools that increases an organization's ability to deliver applications and services at high velocity. A simple example shows the journey of code from development to operations and the limitations of scaling, reliability, speed, and security when these functions are separated. DevOps addresses these limitations through automation, tools for continuous integration, monitoring, and configuration management. While DevOps helps with complexity from multiple teams and environments, additional challenges arise from microservices, containers, and redundancy across critical services.
DockerCon SF 2019 - TDD is Dead
In this talk we'll talk about what you should and shouldn't be testing in app development when modern monitoring tools are in place.
DevSecCon Singapore 2018 - Pushing left like a boss by Tanya Janca
- The document discusses "pushing left" in application security, which means involving security teams earlier in the software development lifecycle from requirements through testing.
- It outlines the key elements of an application security program including vulnerability assessments, threat modeling, code reviews, penetration testing, secure coding practices, and bug bounty programs.
- It provides advice for individuals to push left in their own work by testing their own code using a web proxy, conducting threat modeling, reviewing code for security issues, and training themselves in secure coding best practices.
The Journey to DevSecOps
This document discusses the evolution of DevSecOps and provides guidance for security professionals. It notes that DevSecOps approaches have gained popularity as DevOps has grown over the past decade. It recommends that security professionals focus on detection over protection, embrace a blameless culture of continuous improvement, and get involved in DevSecOps communities to help build security tools and practices.
Principles of Chaos Engineering
Slide deck from my talk about "Principles of Chaos Engineering" at the first ever Chaos Engineering Hamburg meet up.
Come join us at http://www.meetup.com/Chaos-Engineering-Hamburg/ and stay up to date with new events and other news.
Speeding Up the Dinosaur: Continuous Testing in Continuous Delivery - Martijn...
Customers understand how continuously delivering new features can help their business. But it is still uncertain how to make the journey towards continuous delivery in a safe way. In order to increase the release frequency, more regression testing is needed and test automation should be fully embedded in the delivery pipeline. We show how we built automated delivery pipelines that support the fast building, deployment and testing of the applications in a banking environment. This helped in increasing the release frequency from twice a year to multiple times a day.
2020-Feb: Testing: Cables and Chains
Maybe developer testing is more trouble than it's worth. Teams have found writing tests to be a hinderance. Then they reduce testing in order to deliver "faster". They feel that tests actually make changing the code and fixing bugs harder. They might be right.
see also: https://www.linkedin.com/pulse/testing-cable-chain-mark-windholtz/
Static Analysis For Security and DevOps Happiness w/ Justin Collins
Justin Collins, Brakeman Security
It is not enough to have fast, automated code deployment. We also need some level of assurance the code being deployed is stable and secure. Static analysis tools that operate on source code can be an efficient and reliable method for ensuring properties about the code - such as meeting basic security requirements. Automated static analysis security tools help prevent vulnerabilities from ever reaching production, while avoiding slow, fallible manual code reviews.
This talk will cover the benefits of static analysis and strategies for integrating tools with the development workflow.
Making Continuous Security a Reality with OWASP’s AppSec Pipeline - Matt Tesa...
You’ve probably heard many talks about DevSecOps and continuous security testing but how many provided the tools needed to actually start that testing? This talk does exactly that. It provides an overview of the open source AppSec Pipeline tool which has been used in real world companies to do real security work. Beyond a stand alone tool, the OWASP AppSec Pipeline provides numerous docker containers ready to automate, a specification to customize with the ability to create your own implementation and references to get you started.
The talk will also cover how to add an AppSec Pipeline to your team’s arsenal and provide example templates of how best to run the automated tools provided. Finally, we’ll briefly cover using OWASP Defect Dojo to store and curate the issues found by your AppSec Pipeline. The goal of this talk is to share the field-tested methods of two AppSec professionals with nearly 20 years of experience between them. If you want to start your DevSecOps journey by continuously testing rather then hear about it, this talk is for you.
ICSE 2014: Unit Test Virtualization with VMVM
Presentation of the ACM SigSoft Distinguished Paper, "Unit Test Virtualization with VMVM" given at ICSE 2014. Unit Test Virtualization significantly decreases the amount of time necessary to run unit tests.
Unittesting_AlexMeade
Unit tests are small sections of code written during development to test individual parts of an application. They help find bugs earlier, improve code quality, act as documentation, and prevent defects from being reintroduced. Research shows unit tests can find 85% of defects during development and help implement features correctly the first time.
Railsonfire @ cloudcamp.sk
This document discusses continuous integration and continuous deployment (CI/CD) using cloud infrastructure. It notes that the cloud is well-suited for CD with standardized, automated deployments and rollbacks. Following CI/CD practices allows for robust applications through fast, frequent iterations that are easy to test. The future of CD involves more automation around testing, deployment, rollbacks, and deploying to staging environments, with the goal of automatically deploying to production.
PuppetConf 2017: Moving faster with Puppet & Splunk- Hal Rottenberg, Andrew B...
Together, Splunk + Puppet have the capabilities to address multiple enterprise initiatives that allow organizations to analyze with intelligence and act quickly - all while successfully scaling their DevOps and transformational practices across the enterprise. Unifying machine data analytics with infrastructure and application orchestration enables IT to speed time from insight to action. In this session, learn how Puppet + Splunk are monitoring, troubleshooting and automating all the things with a set of new integrations to make your DevOps transformation a reality!
AppSec Pipeline - Velcocity NY 2015
Take the ideas of DevOps and the notion of a delivery pipeline and combine them for an AppSec Pipeline. This talk covers the open source components used to create an AppSec Pipeline and the benefits we received from its implementation.
Microservices Summit - The Human Side of Services
This document discusses the importance of the human side of services at Yelp and outlines several best practices for operating microservices. It emphasizes the importance of clear organizational objectives, service level agreements to define key metrics like performance and reliability, emphasis on cooperation between teams with varied skills, and avoiding common pitfalls like depending too heavily on libraries or assuming all developers can do operations work. The overall message is that successful microservices require both technical excellence and a focus on the human factors of collaboration, clear goals, and ownership.
Shifting Testing Left - The Pain Points and Solutions
Learn what shift left is, why it usually doesn't work and how to solve those problems. We will focus on test automation and the struggles of having it incorporated into the continuous integration (CI) or continuous deployment (cd) strategy.
Testability is Everyone's Responsibility
Testability is a first class concern for all disciplines within software development. There, I said it. No hedging, no nebulous phrasing, maybes or it depends.
Too often we labour under systems that are hard to test, manifesting themselves with frantic searches for more testers, lengthy acceptance test runs, fearful testing for regressions with a hopeful release at the end. Worst of all, it usually ends up with a project manager sat on the testers desk asking 'when will testing be done.' It's never done, it can only stop, just so you know.
Throughout my career, often the testability of a system has been deemed to be the testers concern. If something was hard to test, then it was the testers problem. However, the causes of low testability effect the activities of all disciplines, whether it be speed of feedback to developers or flow of value generating features for product managers.
During the talk, we will cover:
* How testability is a key advantage in building systems of ever increasing complexity.
* Why it's important for developers and operational stakeholders to build inherently testable systems.
* What testers can do to be catalysts for testability improvements.
The activity of testing is rarely the bottleneck, how testable your system is is your problem. Poor testability cannot be remedied by one discipline alone. It's for all of us to care about.
DevOps for AI Apps
DevOps for AI Applications - How to apply best practices from software engineering to the world of data science and machine learning
MongoDB World 2018: Tutorial - MongoDB Meets Chaos Monkey
Speaker: Justin LaBreck, Sr Consulting Engineer, MongoDB | Timo Geusch, Sr Consulting Engineer, MongoDB
Что нам стоіт таск манагер построіт. Ігор Лущик. LvivPy #6
Підсумує по огляду, тобто, що це, які вони є, юзкейси і чому не треба придумувати власний, а чому треба.
From monitoring to automated testing, Jesse Reynolds, Puppet
Don't have time to write automated tests for your infrastructure code? Don't see the point? Or don't know where to start? This talk is for you.
Now we're writing code to manage our infrastructure with tools like Puppet we are effectively developing software. One of the wonderful aspects to this is that we have the world of software development quality best practices to draw on in order to achieve a high rate of change while not compromising on reliability. Writing tests for infrastructure code, and having them execute automatically as part of a continuous integration pipeline, is a key element to this and is the focus for this talk.
But how do you get started on this? What are some tools to help? How should we think about this problem? This talk will provide an overview of the different types of tests that can be written, from small unit tests to integration and acceptance testing. It will focus on integration testing where existing monitoring checks can provide a useful starting point.
After this talk attendees will:
* better understand the value of automated tests for infrastructure code
* be motivated to write tests and implement CI pipelines to execute these tests automatically
* know how to get started with some suggested tooling
2016 - Daniel Lebrero - REPL driven development
New computers have more and more available memory which for us, programmers means we can use more memory in our applications.
However in JAVA (actually all JVM based languages) at some certain point things may get tricky, especially when we expect from our applications to be responsive all the time. This talk will focus on Garbage First collector (the new default in JDK9) which is the newest algorithm available in HotSpot JVM (not so new though) and the only one which can handle 32+GB heap size without blocking your application threads for longer than 200ms. After this talk you will have overview how G1 works, how to read the log, spot common problems and which gc settings you should avoid.
More Related Content
What's hot
Intro to Devops
The document introduces DevOps and discusses its goals of simplicity, no code, and minimal jargon. DevOps is defined as the combination of cultural philosophies, practices, and tools that increases an organization's ability to deliver applications and services at high velocity. A simple example shows the journey of code from development to operations and the limitations of scaling, reliability, speed, and security when these functions are separated. DevOps addresses these limitations through automation, tools for continuous integration, monitoring, and configuration management. While DevOps helps with complexity from multiple teams and environments, additional challenges arise from microservices, containers, and redundancy across critical services.
DockerCon SF 2019 - TDD is Dead
In this talk we'll talk about what you should and shouldn't be testing in app development when modern monitoring tools are in place.
DevSecCon Singapore 2018 - Pushing left like a boss by Tanya Janca
- The document discusses "pushing left" in application security, which means involving security teams earlier in the software development lifecycle from requirements through testing.
- It outlines the key elements of an application security program including vulnerability assessments, threat modeling, code reviews, penetration testing, secure coding practices, and bug bounty programs.
- It provides advice for individuals to push left in their own work by testing their own code using a web proxy, conducting threat modeling, reviewing code for security issues, and training themselves in secure coding best practices.
The Journey to DevSecOps
This document discusses the evolution of DevSecOps and provides guidance for security professionals. It notes that DevSecOps approaches have gained popularity as DevOps has grown over the past decade. It recommends that security professionals focus on detection over protection, embrace a blameless culture of continuous improvement, and get involved in DevSecOps communities to help build security tools and practices.
Principles of Chaos Engineering
Slide deck from my talk about "Principles of Chaos Engineering" at the first ever Chaos Engineering Hamburg meet up.
Come join us at http://www.meetup.com/Chaos-Engineering-Hamburg/ and stay up to date with new events and other news.
Speeding Up the Dinosaur: Continuous Testing in Continuous Delivery - Martijn...
Customers understand how continuously delivering new features can help their business. But it is still uncertain how to make the journey towards continuous delivery in a safe way. In order to increase the release frequency, more regression testing is needed and test automation should be fully embedded in the delivery pipeline. We show how we built automated delivery pipelines that support the fast building, deployment and testing of the applications in a banking environment. This helped in increasing the release frequency from twice a year to multiple times a day.
2020-Feb: Testing: Cables and Chains
Maybe developer testing is more trouble than it's worth. Teams have found writing tests to be a hinderance. Then they reduce testing in order to deliver "faster". They feel that tests actually make changing the code and fixing bugs harder. They might be right.
see also: https://www.linkedin.com/pulse/testing-cable-chain-mark-windholtz/
Static Analysis For Security and DevOps Happiness w/ Justin Collins
Justin Collins, Brakeman Security
It is not enough to have fast, automated code deployment. We also need some level of assurance the code being deployed is stable and secure. Static analysis tools that operate on source code can be an efficient and reliable method for ensuring properties about the code - such as meeting basic security requirements. Automated static analysis security tools help prevent vulnerabilities from ever reaching production, while avoiding slow, fallible manual code reviews.
This talk will cover the benefits of static analysis and strategies for integrating tools with the development workflow.
Making Continuous Security a Reality with OWASP’s AppSec Pipeline - Matt Tesa...
You’ve probably heard many talks about DevSecOps and continuous security testing but how many provided the tools needed to actually start that testing? This talk does exactly that. It provides an overview of the open source AppSec Pipeline tool which has been used in real world companies to do real security work. Beyond a stand alone tool, the OWASP AppSec Pipeline provides numerous docker containers ready to automate, a specification to customize with the ability to create your own implementation and references to get you started.
The talk will also cover how to add an AppSec Pipeline to your team’s arsenal and provide example templates of how best to run the automated tools provided. Finally, we’ll briefly cover using OWASP Defect Dojo to store and curate the issues found by your AppSec Pipeline. The goal of this talk is to share the field-tested methods of two AppSec professionals with nearly 20 years of experience between them. If you want to start your DevSecOps journey by continuously testing rather then hear about it, this talk is for you.
ICSE 2014: Unit Test Virtualization with VMVM
Presentation of the ACM SigSoft Distinguished Paper, "Unit Test Virtualization with VMVM" given at ICSE 2014. Unit Test Virtualization significantly decreases the amount of time necessary to run unit tests.
Unittesting_AlexMeade
Unit tests are small sections of code written during development to test individual parts of an application. They help find bugs earlier, improve code quality, act as documentation, and prevent defects from being reintroduced. Research shows unit tests can find 85% of defects during development and help implement features correctly the first time.
Railsonfire @ cloudcamp.sk
This document discusses continuous integration and continuous deployment (CI/CD) using cloud infrastructure. It notes that the cloud is well-suited for CD with standardized, automated deployments and rollbacks. Following CI/CD practices allows for robust applications through fast, frequent iterations that are easy to test. The future of CD involves more automation around testing, deployment, rollbacks, and deploying to staging environments, with the goal of automatically deploying to production.
PuppetConf 2017: Moving faster with Puppet & Splunk- Hal Rottenberg, Andrew B...
Together, Splunk + Puppet have the capabilities to address multiple enterprise initiatives that allow organizations to analyze with intelligence and act quickly - all while successfully scaling their DevOps and transformational practices across the enterprise. Unifying machine data analytics with infrastructure and application orchestration enables IT to speed time from insight to action. In this session, learn how Puppet + Splunk are monitoring, troubleshooting and automating all the things with a set of new integrations to make your DevOps transformation a reality!
AppSec Pipeline - Velcocity NY 2015
Take the ideas of DevOps and the notion of a delivery pipeline and combine them for an AppSec Pipeline. This talk covers the open source components used to create an AppSec Pipeline and the benefits we received from its implementation.
Microservices Summit - The Human Side of Services
This document discusses the importance of the human side of services at Yelp and outlines several best practices for operating microservices. It emphasizes the importance of clear organizational objectives, service level agreements to define key metrics like performance and reliability, emphasis on cooperation between teams with varied skills, and avoiding common pitfalls like depending too heavily on libraries or assuming all developers can do operations work. The overall message is that successful microservices require both technical excellence and a focus on the human factors of collaboration, clear goals, and ownership.
Shifting Testing Left - The Pain Points and Solutions
Learn what shift left is, why it usually doesn't work and how to solve those problems. We will focus on test automation and the struggles of having it incorporated into the continuous integration (CI) or continuous deployment (cd) strategy.
Testability is Everyone's Responsibility
Testability is a first class concern for all disciplines within software development. There, I said it. No hedging, no nebulous phrasing, maybes or it depends.
Too often we labour under systems that are hard to test, manifesting themselves with frantic searches for more testers, lengthy acceptance test runs, fearful testing for regressions with a hopeful release at the end. Worst of all, it usually ends up with a project manager sat on the testers desk asking 'when will testing be done.' It's never done, it can only stop, just so you know.
Throughout my career, often the testability of a system has been deemed to be the testers concern. If something was hard to test, then it was the testers problem. However, the causes of low testability effect the activities of all disciplines, whether it be speed of feedback to developers or flow of value generating features for product managers.
During the talk, we will cover:
* How testability is a key advantage in building systems of ever increasing complexity.
* Why it's important for developers and operational stakeholders to build inherently testable systems.
* What testers can do to be catalysts for testability improvements.
The activity of testing is rarely the bottleneck, how testable your system is is your problem. Poor testability cannot be remedied by one discipline alone. It's for all of us to care about.
DevOps for AI Apps
DevOps for AI Applications - How to apply best practices from software engineering to the world of data science and machine learning
MongoDB World 2018: Tutorial - MongoDB Meets Chaos Monkey
Speaker: Justin LaBreck, Sr Consulting Engineer, MongoDB | Timo Geusch, Sr Consulting Engineer, MongoDB
Что нам стоіт таск манагер построіт. Ігор Лущик. LvivPy #6
Підсумує по огляду, тобто, що це, які вони є, юзкейси і чому не треба придумувати власний, а чому треба.
What's hot (20)
DevSecCon Singapore 2018 - Pushing left like a boss by Tanya Janca
DevSecCon Singapore 2018 - Pushing left like a boss by Tanya Janca
Speeding Up the Dinosaur: Continuous Testing in Continuous Delivery - Martijn...
Speeding Up the Dinosaur: Continuous Testing in Continuous Delivery - Martijn...
Static Analysis For Security and DevOps Happiness w/ Justin Collins
Static Analysis For Security and DevOps Happiness w/ Justin Collins
Making Continuous Security a Reality with OWASP’s AppSec Pipeline - Matt Tesa...
Making Continuous Security a Reality with OWASP’s AppSec Pipeline - Matt Tesa...
PuppetConf 2017: Moving faster with Puppet & Splunk- Hal Rottenberg, Andrew B...
PuppetConf 2017: Moving faster with Puppet & Splunk- Hal Rottenberg, Andrew B...
Shifting Testing Left - The Pain Points and Solutions
Shifting Testing Left - The Pain Points and Solutions
MongoDB World 2018: Tutorial - MongoDB Meets Chaos Monkey
MongoDB World 2018: Tutorial - MongoDB Meets Chaos Monkey
Что нам стоіт таск манагер построіт. Ігор Лущик. LvivPy #6
Что нам стоіт таск манагер построіт. Ігор Лущик. LvivPy #6
Similar to Openstack dev on
From monitoring to automated testing, Jesse Reynolds, Puppet
Don't have time to write automated tests for your infrastructure code? Don't see the point? Or don't know where to start? This talk is for you.
Now we're writing code to manage our infrastructure with tools like Puppet we are effectively developing software. One of the wonderful aspects to this is that we have the world of software development quality best practices to draw on in order to achieve a high rate of change while not compromising on reliability. Writing tests for infrastructure code, and having them execute automatically as part of a continuous integration pipeline, is a key element to this and is the focus for this talk.
But how do you get started on this? What are some tools to help? How should we think about this problem? This talk will provide an overview of the different types of tests that can be written, from small unit tests to integration and acceptance testing. It will focus on integration testing where existing monitoring checks can provide a useful starting point.
After this talk attendees will:
* better understand the value of automated tests for infrastructure code
* be motivated to write tests and implement CI pipelines to execute these tests automatically
* know how to get started with some suggested tooling
2016 - Daniel Lebrero - REPL driven development
New computers have more and more available memory which for us, programmers means we can use more memory in our applications.
However in JAVA (actually all JVM based languages) at some certain point things may get tricky, especially when we expect from our applications to be responsive all the time. This talk will focus on Garbage First collector (the new default in JDK9) which is the newest algorithm available in HotSpot JVM (not so new though) and the only one which can handle 32+GB heap size without blocking your application threads for longer than 200ms. After this talk you will have overview how G1 works, how to read the log, spot common problems and which gc settings you should avoid.
May 2021 Spark Testing ... or how to farm reputation on StackOverflow
Slides from the St. Louis Big Data IDEA meetup. Kit Menke presented on how to test your Apache Spark applications. May 2021 meetup notes
Testing for Logic App Solutions | Integration Monday
In this Integration Monday session, Mike discussed the challenges and approaches for some of the common testing scenarios when delivering integration solutions with Microsoft Azure.
InteropWG Intro & Vertical Programs (May. 2017)
The document summarizes the OpenStack Interoperability Working Group's efforts to promote interoperability across OpenStack distributions and products. It discusses how the group develops guidelines specifying required capabilities and tests. Products must pass these tests to be considered interoperable and qualify for the OpenStack logo program. The guidelines aim to ensure a consistent user experience while allowing flexibility in implementations. The document also outlines the group's governance process and opportunities for participants to provide feedback to help improve interoperability standards over time.
DevOps - Boldly Go for Distro
This is a 90 min talk with some exercises and discussion that I gave at the DHS Agile Expo. It places DevOps as a series of feedback loops and emphasizes agile engineering practices being at the core.
Open Closed Principle kata
The document discusses the Open/Closed Principle (OCP), which states that software entities should be open for extension but closed for modification. It provides an example of an OCP kata using a bowling scoring problem. Programmers are instructed to write tests, then refactor the code by changing the object composite returned by a factory to make each new test pass without modifying existing code. The document also provides credits to people involved in developing and promoting OCP and related katas.
DefCore: The Interoperability Standard for OpenStack
This presentation provides an introduction to the OpenStack DefCore Committee, which is working to create interoperability standards for OpenStack Powered clouds. You'll gain insight into the interoperability challenges of OpenStack clouds, and learn how DefCore creates it's Guidelines. Learn why the Technical Committee, Board of Directors, end users, and vendors have a seat at the table. You'll laugh, you'll cry, you'll immediately want to stop talking about cloud computing and go watch science fiction all night.
This talk was originally presented at the Triangle OpenStack Meetup Group's September 21, 2015 meeting in Durham, NC. A recording can be found here (this talk starts at the 46:10 mark): https://vmware.webex.com/vmware/lsr.php?RCID=a51f9e6882f54ccab8b715c8c0162484
A new revision with updates was given at a meeting of the China Open Source Cloud League on May 20, 2016 in Beijing. The slides here on Slideshare represent that presentation.
OOP Java
The course aims to provide you with an understanding of the fundamental concepts involved in object-oriented programming (object, class, protocol, hierarchy, inheritance, encapsulation, polymorphism and collaboration).
The programming language you will use is Java. However, the purpose of the course is not to teach you the minutiae of the Java language, but rather to teach you fundamental object-oriented programming concepts and skills that will be transferable to any object¬ oriented language
Opticon 2017 How Developers Can Take Experimentation
The document discusses how developers can take experimentation to new levels with full stack experimentation. It describes an architecture that allows experiments across platforms and flexibility to experiment deep within the technical stack. Examples are given of how full stack experimentation could be used for tasks like A/B tests, feature rollouts, and algorithm changes. The benefits of the SDK architecture are outlined as being flexible, stateless, and replaceable.
What should you know to become a better Java programmer?
There is a difference between becoming a programmer and becoming a better programmer. You have to be a better Java developer, and for that, you should follow an outstanding learning roadmap. Java development services providers always look for experts who are well in java programming. So read this guide to know the steps.
2014 #vBrownBag OpenStack Summit Atlanta Ju Lim -- OpenStack Personas
The document discusses OpenStack personas, which are profiles of fictional users developed based on real user research. It provides an overview of personas and their benefits for product development. Two sample personas, Ben and Daichi, are presented to illustrate how personas describe a user's goals, frustrations, and expectations to help guide design decisions. The document encourages involvement in the OpenStack Personas Working Group and ends with useful links for more information.
Big data made easy with a Spark
This document provides an agenda and slides for a presentation on introducing big data concepts using open source tools. The presentation covers ingesting and analyzing sample data using Spark SQL, including joining datasets to count the number of books by author. It also demonstrates basic machine learning by loading sample revenue data, applying data quality rules to correct anomalies, and using linear regression to predict revenue for a party of 40 guests. The goal is to make big data concepts accessible to audiences of all experience levels.
Test Driven Development - Workshop
Test Driven Development (TDD) is a software development process that relies on the repetition of a very short development cycle: requirements are turned into very specific test cases that are failed, then the software is improved to pass the new tests, and finally any newly introduced code is refactored. The document outlines the TDD lifecycle and process, describes unit testing and how it verifies isolated units of code, and discusses how TDD results in testable, clean code through refactoring. It provides examples of unit testing code for a bank account class.
DevOps in the Real World
The document discusses DevOps practices for real world companies. It defines DevOps as people, processes and tools working together to enable continuous delivery of value to end users faster. It provides advice on establishing baselines, starting simple with one codebase, automating tests and infrastructure, implementing feature flags, improving cycle times through automation and removing bottlenecks, and shifting to a no-silos culture with collaboration between teams. The overall message is that DevOps requires cultural and operational changes to break down barriers and deliver value to users faster.
[Japan Selenium User Community in Remote] Test Automation Journey
This document summarizes a presentation given to the Japan Selenium User Community about optimizing end-to-end test execution time through parallel test execution. It discusses initially trying a Maven plugin to run tests in parallel threads, but this caused errors due to WebDriver not being thread-safe. The solution was to use the parallel test capabilities of TestNG, which supports WebDriver more reliably for multi-threaded test execution. With this approach, execution time was reduced significantly without issues. The presentation also provided an overview of the speaker's test automation journey and considerations for justifying test automation.
Developers’ mDay u Banjoj Luci - Duško Bajić, Kotlin User Group Bosnia – Kotl...
Kotlin is here to stay
- Kotlin was unveiled in 2011 by JetBrains and has grown significantly since then
- It is now fully supported by Google for Android development and is widely adopted in the Android community
- Kotlin code runs on the JVM and is 100% interoperable with Java, allowing use of existing Java libraries
- Key advantages of Kotlin include its conciseness, null safety, and support for functional programming patterns
Java Basics
The document outlines the course details for a Mobile App Development class. It includes:
- The course instructor's contact information.
- Recommended reference books and websites for learning Java.
- The marking criteria for assignments, projects, exams.
- General classroom rules around cell phones, food, and behavior.
- An outline of lecture topics that will cover what Java is, its history and features.
OpenStack at EBSCO
This document discusses Ebsco's implementation and use of OpenStack for their IT infrastructure. Some key points:
- Ebsco is a leading provider of online research content and discovery services for libraries. They needed a self-service infrastructure and full-stack automation for their development and operations teams.
- They chose OpenStack because it provides standardized compute, network and storage interfaces that allow various products to integrate easily. It also allows them to build an infrastructure as a service platform for their teams.
- Currently, Ebsco runs 3 OpenStack clouds supporting over 1,100 instances across development, testing and production environments. They have focused on skills training, vendor integration challenges, deployment difficulties and adoption rates over the course of
Giving automated tests the love they deserve at Listings
The document summarizes the speaker's approach to automated testing at their company Listings. Their key points are:
1. They focus on short feedback loops in testing and builds to help developers identify and fix bugs quickly. Tests and builds should be fast.
2. Their "test pyramid" is non-traditional, with fast broad stack tests using in-memory implementations of side-effecting components like databases.
3. They invest in tooling to provide really good test failure feedback.
4. They only run tests affected by a code change to keep the testing process fast. They modularize their codebase with testing in mind.
Similar to Openstack dev on (20)
From monitoring to automated testing, Jesse Reynolds, Puppet
From monitoring to automated testing, Jesse Reynolds, Puppet
May 2021 Spark Testing ... or how to farm reputation on StackOverflow
May 2021 Spark Testing ... or how to farm reputation on StackOverflow
Testing for Logic App Solutions | Integration Monday
Testing for Logic App Solutions | Integration Monday
DefCore: The Interoperability Standard for OpenStack
DefCore: The Interoperability Standard for OpenStack
Opticon 2017 How Developers Can Take Experimentation
Opticon 2017 How Developers Can Take Experimentation
What should you know to become a better Java programmer?
What should you know to become a better Java programmer?
2014 #vBrownBag OpenStack Summit Atlanta Ju Lim -- OpenStack Personas
2014 #vBrownBag OpenStack Summit Atlanta Ju Lim -- OpenStack Personas
[Japan Selenium User Community in Remote] Test Automation Journey
[Japan Selenium User Community in Remote] Test Automation Journey
Developers’ mDay u Banjoj Luci - Duško Bajić, Kotlin User Group Bosnia – Kotl...
Developers’ mDay u Banjoj Luci - Duško Bajić, Kotlin User Group Bosnia – Kotl...
Giving automated tests the love they deserve at Listings
Giving automated tests the love they deserve at Listings
More from Andrew Yongjoon Kong
Tunnel without tunnel
The document discusses MPLS and how it can improve tenant network performance issues in OpenStack environments. It explains that MPLS solves the problem of tenant network link layer separation by adding labels to packets at the L3 routing level, instead of using an overlay network IP. This means MPLS tunnels packets without using fat L2 frames or requiring NAT, avoiding issues like increased latency from geographical separation or bottlenecks. By using existing IP routing and networks, MPLS can enhance performance without needing to change the existing network modeling.
Nightmare with ceph : Recovery from ceph cluster total failure
This document discusses issues encountered with a Ceph configuration. The key points are:
- The Ceph configuration had 3 monitor servers and 12 OSDs with a replica count of 2. 4 of the 12 OSDs failed which caused 386 incomplete placement groups.
- Troubleshooting efforts like adjusting the PG count, scrubbing, and killing incomplete PGs did not resolve the issue for 3 weeks.
- The real problem was the missing data from the failed OSDs that was needed to complete the placement groups. Restarting the failed OSDs allowed the backfilling to eventually resolve the incomplete placement groups.
- Lessons learned include having more than 3 replicas, taking frequent snapshots
Stream analysis with kafka native way and considerations about monitoring as ...
Stream analysis with kafka native way and considerations about monitoring as ...Andrew Yongjoon Kong
The document discusses stream analysis with Kafka and considerations for monitoring as a service. It provides background on the speaker including their roles in government, academia, and industry related to big data. It then covers some key concepts in stream processing versus batch processing and examples of popular stream processors like Apache Flume, Storm, Spark, and Samza. The document also discusses real-time analytics and defines the term. It introduces the Kafka Streams library and provides sample code for simple pipelines and wordcount analytics. Finally, it briefly mentions the KSQL query language for Kafka.Graph analysis platform comparison, pregel/goldenorb/giraph
Graph data based scalable analysis platform.Introduction to graph theory. comparison mapreduce f vs graph platform.
Automating auto-scaled load balancer based on linux and vm orchestrator
story about developing automatic scaleout loadbalancer using ECMP and Orchestrator for the container service
GPU cloud with Job scheduler and Container
share the story about building GPU cloud based on container and Batch Job Scheduler for machine learning and deep learning application
Embracing clouds
1) The document discusses Kakao's journey with cloud computing from a CMMI perspective, ranging from CMMI levels 0 to 5.
2) At CMMI level 1, Kakao produced Krane (OpenStack cloud) to provide self-service developer resources. At level 2, KEMI (monitoring platform) provided limited production resources.
3) Kakao achieved CMMI level 3 automation with DKOS (container as a service platform) that deployed containers and services across 4000 compute nodes.
openstack, devops and people
The document discusses DevOps practices at Kakaocorp. It provides background on Andrew Yongjoon Kong and describes some key metrics of Kakaocorp's OpenStack deployment. It then covers concepts like collaboration, affinity, tools, and scaling in a DevOps context. Specific examples at Kakaocorp include using GitHub, Jira, Chef, and Jenkins. It also introduces initiatives like KEMI for integration and DKOS for container management.
Cloud data center and openstack
This document provides an overview of Kakaocorp's cloud and data center technologies and practices. It discusses Kakaocorp's use of OpenStack for its cloud computing platform, as well as its adoption of DevOps culture and tools like Chef configuration management. The document also describes Kakaocorp's centralized CMDB, monitoring, and deployment systems that form the control plane for its data center automation. Kakaocorp's integrated information service bus called KEMI is presented as well.
Openstack summit 2015
With more than 140 million users, KakaoTalk is the most popular mobile messaging platform in South Korea. The team at daumkakao has been using OpenStack with the intention for tranforming the current legacy infrastructure into scale out based cloud to build and offer new services for its users. In this session, we'd like to share our experiences with the OpenStack community, specifically in regards to meeting our needs for networking with Neutron.OpenStack Neutron offers a lot of methods to implement networking for VMs and containers. For production operations, VM migration can be a common activity to manage resources and improve uptime. It's not hard using shared storage like Ceph, but network settings, such as IP addresses need to be preserved. With a shared storage environment, an image can be attached anywhere inside of a data center, but a service IP for a virtual machine is different story. And when you don't use the floating IPs, keeping the same IP across a data center-wide set of VLANs is hard job.To maintain a virtual machine's IP settings and balance IPs between VLANS, we tried several options including overlay, SDN, and NFV technologies. In the end we came to use a route-only network for our virtual machine networks, leveraging technology like Quagga for RIP, OSPF BGP integrated with Neutron.
Cloud: From Unmanned Data Center to Algorithmic Economy using Openstack
This document discusses Kakaocorp's transition from an unmanned datacenter to using algorithms and OpenStack for resource management. It describes the development of an integrated monitoring system called "Crow" to gather metrics from physical and virtual resources. This system analyzes resource usage to identify unused virtual machines, allowing Kakaocorp to automatically garbage collect over 40% of potential candidates. The monitoring data also helps create a new controlled volume subsystem for improved resource allocation.
Way to cloud
This document discusses simplifying, standardizing, and automating application deployment processes before moving to the cloud. It recommends using central configuration repositories and automation tools like Chef to deploy identical environments for development, staging, and production. This allows using the same processes and tools across environments. AWS services like OpsWorks can then be used to deploy production using the same Chef configurations. The key is treating the cloud as a tool to deploy standardized, automated applications at scale.
More from Andrew Yongjoon Kong (12)
Nightmare with ceph : Recovery from ceph cluster total failure
Nightmare with ceph : Recovery from ceph cluster total failure
Stream analysis with kafka native way and considerations about monitoring as ...
Stream analysis with kafka native way and considerations about monitoring as ...
Graph analysis platform comparison, pregel/goldenorb/giraph
Graph analysis platform comparison, pregel/goldenorb/giraph
Automating auto-scaled load balancer based on linux and vm orchestrator
Automating auto-scaled load balancer based on linux and vm orchestrator
Cloud: From Unmanned Data Center to Algorithmic Economy using Openstack
Cloud: From Unmanned Data Center to Algorithmic Economy using Openstack
Recently uploaded
Pushing the limits of ePRTC: 100ns holdover for 100 days
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
Video Streaming: Then, Now, and in the Future
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.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Programming Foundation Models with DSPy - Meetup Slides
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
Infrastructure Challenges in Scaling RAG with Custom AI models
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
Communications Mining Series - Zero to Hero - Session 1
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
Microsoft - Power Platform_G.Aspiotis.pdf
Revolutionizing Application Development
with AI-powered low-code, presentation by George Aspiotis, Sr. Partner Development Manager, Microsoft
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
Full-RAG: A modern architecture for hyper-personalization
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
How to Get CNIC Information System with Paksim Ga.pptx
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Recently uploaded (20)
Pushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 days
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
Infrastructure Challenges in Scaling RAG with Custom AI models
Infrastructure Challenges in Scaling RAG with Custom AI models
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Communications Mining Series - Zero to Hero - Session 1
Communications Mining Series - Zero to Hero - Session 1
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
Full-RAG: A modern architecture for hyper-personalization
Full-RAG: A modern architecture for hyper-personalization
How to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptx
Openstack dev on
- 1. OpenStack Distance from Public Service Andrew yongjoon Kong sstrato.open@gmail.com Facebook: 엔지니어를 위한 정치
- 2. Who’s No 1 Cloud 1. 2. 3. 4. 5. Amazon Web Service. Force.com Google App. Engine Rack Space Micro Soft Azure
- 3. When is your heyday?
- 4. When was the cloud’s heyday
- 5. Every Body’s Question • Is OpenStack Ready for the public service?
- 6. The Answer from OpenStack • “Is your Application Ready for the Cloud?” Open Stack 2010 ~
- 7. WTF? • What The F ? • What is The First?
- 9. What about you? OpenStack? you, loosely Coupled?
- 10. See? MY APIs
- 11. Your Code is too buggy!
- 12. OpenStack • Fix it! • be quite! Open Stack 2010 ~
- 13. You’re saying you have testing framework. But it’s not perfect.
- 14. OpenStack • You should have your test case set! It‟s basic(your version of gerrit, test and CI ) Open Stack 2010 ~
- 15. Your API server’s is the SPOF. The base component is also the SPOF
- 16. OpenStack • Use your Brain. if you‟re good engineer, you can solve that issue. Open Stack 2010 ~
- 17. Your API’s response result is not Good enough to tackle issue.
- 18. OpenStack • That‟s your problem. you have to check through the API, not from response. Open Stack 2010 ~
- 19. Your Metering/Monitoring API(Savanna) is not enough. because it’s not matured yet (actually Sucks!)
- 20. OpenStack • That‟s your problem. If your infra is matured enough to serve cloud ? There‟s that kind of system already. Open Stack 2010 ~
- 21. • What about Network? The Network Node is SPOF. and Performance Bottle neck. I mean the „Distributed Network Model‟
- 22. OpenStack • That‟s your problem. You should make „blue print!‟. and Get the proof from community. Open Stack 2010 ~
- 23. • What about user authentication? • the keystone is OK?
- 24. OpenStack • IF your service is good, you have your authentication method. make the driver for keystone. Open Stack 2010 ~
- 25. • That means we should prepare something for public service?
- 26. • We make API. and Give simple working scenario. you should improve that. That’s what opensource is working. t • We are not solution! • Ask you again “ Are you ready for the cloud?”
- 27. By The Way • KT & Cloudware is hiring