Proposed Presentation Title*: Data-driven release decisions for your private IaaS cloud.
Abstract:
Are you using OpenStack in production?
Do you need to manage feature list delivered in production by yourself?
It sounds like you are working on your own product which is based on OpenStack's community and maybe on some existing OpenStack's distribution. If you really want to be flexible in release management for your OpenStack production solution, then you need to develop and maintain product.
Let's assume for beginning that you are using some OpenStack's distribution and you are not planning to maintain independent version of source code.You just want to control you feature list in production, support change management process and support few development teams which are working on new features for production.
"Opensource","RM", "CI", "CD": all these words together for your own little cheese shop link1[https://www.youtube.com/watch?v=cWDdd5KKhts] link2[http://www.space.com/10459-wheel-cheese-launched-space-private-spacecraft.html].
This talk is about internal implementation of few CICD components and about what do you need to support few regular releases and few change management incidents in year.
Are you using OpenStack in production?
Do you need to manage feature list delivered in production by yourself?
It sounds like you are working on your own product which is based on OpenStack's community and maybe on some existing OpenStack's distribution. If you really want to be flexible in release management for your OpenStack production solution, then you need to develop and maintain product.
Let's assume for beginning that you are using some OpenStack's distribution and you are not planning to maintain independent version of source code.You just want to control you feature list in production, support change management process and support few development teams which are working on new features for production.
"Opensource","RM", "CI", "CD": all these words together for your own little cheese shop link1[https://www.youtube.com/watch?v=cWDdd5KKhts] link2[http://www.space.com/10459-wheel-cheese-launched-space-private-spacecraft.html].
This talk is about internal implementation of few CICD components and about what do you need to support few regular releases and few change management incidents in year.
What is the problem or use case you’re addressing in this session?
The term "production environment" means that you are using approach based on products in your business operations. And infrastructure as a service can be delivered by using solution that will be built from OpenStack's components. There is one thing that can help to integrate your business operation model and open source community model of software development. This thing is the product that should be developed and maintained. It should be compiled from open source components, but it should have own release cycle. This release cycle should be based on release cycle of open source components and should help integrate business requirements for new features and development model ( release cycle, methodology etc) of different open source projects.
The term "production environment" means that you are using approach based on products in your business operations. And infrastructure as a service can be delivered by using solution that will be built from OpenStack's components. There is one thing that can help to integrate your business operation model and open source community model of software development. This thing is the product that should be developed and maintained. It should be compiled from open source components, but it should have own release cycle. This release cycle should be based on release cycle of open source components and should help integrate business requirements for new features and development model ( release cycle, methodology etc) of different open source projects.
What should attendees expect to learn?
This talk will be about product example that can be built from OpenStack's projects. What do you need to support release cycle? How CICD automation can help?
Also it can be interesting to learn about CICD automation as a product: data structure/API design session, components and api calls.
Why should this session be selected?
This session should be selected if you are interested to know what are the relations between CICD, product development and using open source technologies. How open discussion can help collaborate and integrate? Release management as final integration point. Because delivery is a process that can integrate.
There are different people, different ideas, different approaches, different experience, difference between short term strategy and midterm strategy, huge gap between long term strategy and every day routine life, gap between future and present. Open discussion in open source community can help to present different things in formal way. Formal logic, it is an integration point. Public form of discussion, it is validation method. Talk on summit should help to share experience and open discussion can help to verify problem statement and implementation approach.
No comments:
Post a Comment