As Developers / Managers we almost everyday think and talk about faster / shorter Software Development cycles to increase our market presence/reach. Is there a way to measure how fast we are ?
Speaking of cycle: In Cycling a term “Cadence” is used, which simply means the speed at which you pedal. Cyclists measure this in revolutions per minute, or rpm. Similar to Cadence in Cycling, the cadence of a software team is measured by how fast and how frequent you can take your software live. Can you do this on every day, every week ? Do you have the tools for the same to Scale UP ?
While we try to improve the cadence of the team we have many challenges around Infrastructure Scaling, Test Integration, Configuration Management, Monitoring for uptime, Log Management, Security of Servers, Dev-Test-Prod setups, Maintaining single source of truth for your assets, etc… And how does these changes impact team dynamics ? If you have adopted some strategies have you noticed that your team has improved? do you need more QAs or do you need more sysadmins ? do you really need those many routers, servers or backups?
Rootconf is a conference which tries to address some of the challenges we face when we fine tune our infrastructure to be able to appropriately respond to a business need, while we Scale UP our Cloud or Web Infrastructure.
Developing a good Continuous Integration/Deployment/Testing/Delivery strategy is critical to improve the cadence of your team. Infrastructure and DevOps is an upfront investment human, time & money. The challenge always is whether you’re willing to make that investment right away, or in the future at a much higher cost and effort.
Rootconf is a conference which will help you to plan and develop a strategy map for infrastructure and devops. It will show you the building blocks for reaching a strategy for Infrastructure Scaling, Continuous Integration, Deployment and Delivery.
Rootconf is targeted at individuals, teams and companies that are seeking to scale the effectiveness of their developer teams and performance of their web stacks, thereby increase the Cadence of their software delivery.
Organizations which need a CI and CD strategy to achieve the above will find a substantial headstart in doing so, by attending Rootconf.
14th and 15th May 2014
The Energy and Research Institute,
4th Main Rd, Domlur II Stage,
16th and 17th May 2014
MLR Convention Centre,
J P Nagar 7th Phase,
Brigade Millenium campus,
For questions about submissions or the conference, write to firstname.lastname@example.org
For Rootconf 2014, we are accepting proposals for Full Talks, Crisp Talks & Flash Talks for the Conference, and proposals for hands-on 3 hour workshops on the below topics. For more information on the types of talks, please checkout the Format tab.
- Infrastructure Scaling & Automation
- Treating your infrastructure as code.
- How did you do scaling and what were your automation strategies while you were gunning for scaling.
- Continuous Integration
- Tell us how you have done it for your organization ?
- Any use case around how it impacted your development team / process.
- Reference Tools – Jenkins, Travis CI, CruiseControl, TeamCity.
- Tell us how you have done it for your organization ?
- Any use case on how you reduced your deployment time ? Did you reduce your time to market your product by Adopting CD ?
- Reference Tools – Chef, Puppet, Ansible, Salt
- Automating Testing
- How much manual can be automated ?
- How did you automate ? What tools di you use ?
- What framework(s) did you use ?
- Did you use heavy weight Selenium or Watir or Sahi?
- Tools that work across heterogeneous languages (PHP, Java, C, Mobile)
- Code Security
- Trust no one - including the developer.
- How are you testing your code ?
- Do you run vulnerability testing part of the CI ?
- Best Practices for secure coding
- Server side security
- Data at motion
- Is internet really safe, how do you protect your data. Is HTTPS alone sufficient ?
- Data at rest
- Do you need to implement standards?
- Code Security
- Log monitoring and server monitoring
- The heartbeat / lifeline of your business: tell us more about how you monitor.
- Do you use any of these tools? Graphite, Sentry, CopperEgg, Loggly, Papertrail, Splunk, Nagios, Monit, etc..
- Cloud databases:
- NoSQL Databases (DynamoDB, MongoDB, Couch)
- The good and bad of NoSQL
- Automation challenges of NoSQL
- Automatic remediation of services and servers.
- Process Protection using Service Protector, Monit
- Auto Scaling Groups
- New tools
- Do you have more tools that makes you a better DevOps Engineer ?
Talks can submitted for the following OSes:
CitoEngine: Alert management and automation tool.
Get rid of pesky duplicate alerts and fiddling through the runbooks. Try the new CitoEngine! It eats up all your alerts, takes actions based on smart rules you define and helps the environment[citation_needed]
When you were young and roaming around at night, like any decent kid, your parents would probably call asking when you were coming home. Now even though you said you would be back in 10 minutes, your parents would nag you by calling every hour, again and again! Totally redundant, right?
Now that you are an adult, you feel pretty much the same frustration when your systems are alerting. You keep getting paged, get calls from NOC, OpsGenie, Satan, PagerDuty, etc. to remind you of the impending doom caused when your ‘/var partition is at 100%’? If that’s not enough, now your Boss wants to know what’s going on! You have to mute the alarms in a gazillion places, tell NOC that you are working on the issue, go run some command from your server’s bash_history and go back to sleep, until you get paged again for something else.
What if you had a system that would accept such alarms, invoke the tools and scripts to mitigate the problem and clean up after that? What if there was a tool, which at the least, would know when to page you and when to inform NOC, based on the number of times the alert came? What if you didn’t have to work your notification policies in Nagios(eww!) but let a genetically superior system take care of it? What if you could do all this with an open source application?
If you have read so far, then you definitely need help! I had the same set of problems, and that led me to create CitoEngine. Let me show you the path to a hassle free alert management system that is ‘CitoEngine’. In this talk, I will be explaining my approach to solving this problem and (if time permits) a quick demo of the tool.
I have been cleaning /var partitions since ‘96. This was the time when Squid proxies were life savers (still are!), RAM was Rs. 1000 per MB, internet was 33.6kbps and setting up sendmail servers got you Rs. 25,000. I have seen technology evolve from dreamy theories to actual mainstream products but, at the same time, a lot of the practices still remain the same. With the better part of my career as a System Administrator, I know the pains for managing infrastructure.
I work for InMobi, solving operational problems.