Rootconf is HasGeek’s annual conference -- and now a growing community -- around DevOps, systems engineering, DevSecOps, security and cloud. The annual Rootconf conference takes place in May each year, with the exception of 2019 when the conference will be held in June.
Besides the annual conference, we also run meetups, one-off public lectures, debates and open houses on DevOps, systems engineering, distributed systems, legacy infrastructure, and topics related to Rootconf.
This is the place to submit proposals for your work, and get them peer reviewed by practitioners from the community.
##Topics for submission:
We seek proposals -- for short and long talks, as well as workshops and tutorials -- on the following topics:
- Case studies of shift from batch processing to stream processing
- Real-life examples of service discovery
- Case studies on move from monolith to service-oriented architecture
- Network security
- Monitoring, logging and alerting -- running small-scale and large-scale systems
- Cloud architecture -- implementations and lessons learned
- Optimizing infrastructure
- Immutable infrastructure
- Aligning people and teams with infrastructure at scale
- Security for infrastructure
If you have questions/queries, write to us on email@example.com
Infrastructure QA in Devops team
Compliance & security testing from the eyes of QA in Devops team
Flow of session will be as follow:
- Brief about the core components of an ideal infrastructure (monitoring, security, resilience)
- How to find the loop holes in your cloud infrastrucre
- Which all tools you can choose to ensure compliance and security
- How to write test case
- Report generation & maintainence
NA, as i will be demoing how to create a framework and make test strategies to ensure environment is secure and robust along with my talk
I have grown as a QA-Ops in devops team of blockchain project where ensuring the stability of whole infrastructure(because drop in any single node can turn whole infrastructure dowm of blockchain network) keeping security at first place was the core requirement.