Video recording and production done by DevOpsDays.
About quality and reliability in complex systems
During last May we were required to migrate our main NY datacenter to a new physical facility.
As you can imagine a data center migration requires careful planning to mitigate risks and avoid network outages.
But we had only 1 month notice.
The challenge was big, there were twists in the plot, but I assure you there is a happy end to this story.
During the lecture you will also get a glimpse to the Outbrain culture of DevOps, the collaboration between the groups and how it works in real life under stressful time.
On ev, Ops, Culture and everything in between
Developers and Operations people are different creatures – sometimes they seem that they come from a totally different planet. They think differently – have different outlooks on life, on how tasks should be managed, and how an infrastructure should be managed. Can the twain meet? This session will discuss the intricate differences between the two species, and how one should bridge the gaps between them – so that your company can make true use of a Devops culture – and take your company to a whole different level.
While A/B test is a very known and familiar methodology for conducting experiments on production when you do that on a large scale it has many challenges in the organization level and operational level.
At Wix we are practicing continuous delivery for over 4 years. Conducting A/B tests and writing feature toggles is at the core of our development process. However when doing so on a large scale, with over 1000 experiments every month, it holds many challenges and affect everyone in the company, from developers, product managers, QA, marketing and management.
In this talk we will explain what is the lifecycle of an experiment, some of the challenges we faced and the effect on our development process.
* How an experiment begins its life
* How an experiment is defined
* How do you let non technical people control the experiment while preventing mistakes
* How an experiment go live, what is the lifecycle of an experiment from beginning to end
* What is the difference between client and server experiments
* How do you keep the user experience and not confuse them
* How does it affect the development process
* How can QA test an environment that changes every 9 minutes
* How can support help users when every user may be part of different experiment
* How can we find if an experiment is causing errors when you have millions of permutations [at least 2^(number of active experiments)]
* What are the effects of always having multiple experiments on system architecture
* What are the development patterns when working with AB test
At Wix we have developed our 3rd generation experiment system called PETRI, which is (will be) open sourced, that helps us maintain some order in a chaotic system that keep changing. We will also explain how PETRI works, what are the patterns in conducting experiments that will have a minimal effect on performance and user experience.
JFrog is handling huge amount of binaries files for all our customers. Since each customer has its own space and domain, using a global Object Store can be tricky.
Also our application cannot work with an ""eventually consistent"" storage, and cannot deliver customer requirements with current S3 performance.
Learn in this session how we managed fast upload, critical replication and backups, and global download availability of the terabytes of JFrog customer binaries files.
Large enterprises today are pacing a flood of multiple devops tools to choose from for their infrastructure.
The problem intensifies when you have dozens of devops teams across the world, each with his own background
of devops tools and knowledge and each with his own agenda of pushing to use his tools.
How would you leverage this distributed, disconnected knowledge into a single working devops knowledge source,
and common infrastructure to leverage the whole enterprise?
Come and hear about Red Hat Global CI initiative to hear on one possible approach for taking on the battle.