From 16 to 17 November 2021, and with Workshops on 15th and 18th, Continuous Lifecycle and ContainerConf will be held again. The conference is aimed at developers, software architects, DevOps, administrators, project managers and IT strategists.
Continuous Lifecycle will provide them a complete look on all aspects of the software lifecycle, focussing on processes and tools for Continuous Delivery and DevOps – including DevSecOps and GitOps.
ContainerConf will provide them with the basics and essential aspects of the popular container technologies and familiarize them with the most important processes and tools for delivering high-quality software based on containers, Kubernetes and their increasingly larger ecosystem.
As the topics of both conferences are constantly merging together we will issue a combined Call for Proposals this year.
Until May 18, 2022
the program comittee
of Continuous Lifecycle and ContainerConf is looking for proposals for talks (40 minutes) and all-day workshops (6 to 7 hours). The following list gives you some pointers for suitable topics. You are, of course, free to suggest topics that go beyond these.
The following list is intended as a guide only.
- Automated Development with CI/CD
- Quality assurance throughout the entire development process
- DevOps and DevSecOps, BizDevOps, GitOps
- Organizational effects of DevOps and Continuous Delivery in (agile) processes
- Requirements Engineering
- Pitfalls and peculiarities of development in distributed teams
- Necessary corporate culture for DevOps
- Version Control
- Configuration Management
- Review and Testing
- Operations and Monitoring
- Continuous Delivery and Continuous Integration
- Cloud Deployment (PaaS etc.) and Build
- Service Discovery
- Infrastructure as Code (IaC)
- Experiences in the transition from classical business models and organizations to DevOps, DevSec and BizDevOps
- Special features in the development of cloud services
- Continuous Delivery in times of Serverless Computing and Microservices
- Experiences from ongoing and completed projects that are committed to Continuous Delivery and/or DevOps
- Interaction and integration of different tools
Best Practices (Container)
- Containerisation with Docker and alternatives
- Orchestration of application containers and cluster management (e.g. Kubernetes, Rancher)
- The ecosystem around Kubernetes
- Important tools from the container ecosystem
- Development of cloud native applications
- Management of applications/services on container platforms (operator or custom controller that extend the Kubernet API)
- Integration: Dockers and other tools of the container ecosystem in combination with other technologies such as KVM, VMware, Xen, OpenStack, Fabric, Ansible, Chef, Puppet and SaltStack
- Monitoring, logging and tracing
- Security aspects of container environments
- The use of service meshes, e.g. Istio, Linkerd or Consul
- Cloud and Container: Experience with Container Engines and other infrastructure providers, Open Service Broker API, Cluster Federation
- How do deployment pipelines and containers fit together?
- Experience reports: tips & tricks, best practices and pitfalls in the container workflow
- Migration scenarios: how do the "old" and "new" world fit together?
- The use of container technologies in the Internet of Things and in embedded scenarios
- Patterns and architecture
- Everyone on the same page: standardization efforts around Containers, and Kubernetes etc.
- Cultural aspects of the introduction and operation of containers etc. ("DevOps")
- Container applications as sample technology for microservice architectures
- development of cloud native services
The main focus is on practical introductions, conceptual considerations, live demos or comparisons of different approaches, not just product presentations. We would like to receive lectures of 40 minutes or tutorials (6 to 7 hours).
The program committee asks for your submission
abstracts (approx. 400 to 700 characters) until May 18, 2022.
Additional material supporting the application (long abstracts, slides, essays, etc.) is also welcome.
The conference program is expected to be published beginning of June .
Please submit your suggestions via our online form.