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.
Target audience
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.
Venue
Workshops
14th and 15th May 2014
The Energy and Research Institute,
4th Main Rd, Domlur II Stage,
Domlur, Bangalore
Conference
16th and 17th May 2014
MLR Convention Centre,
J P Nagar 7th Phase,
Brigade Millenium campus,
Bangalore
Tickets
Online Presence
For questions about submissions or the conference, write to support@hasgeek.com
Theme
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.
- Deployment
- 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)
- Security
- 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
- Self-healing
- 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:
- Windows
- Linux
- Cross-platform
RN
Rohit Nair
@sobertooth
Tsuru - Serve it yourself.
Submitted Apr 2, 2014
Section:
Crisp talk
Technical level:
Intermediate
Through this session we would like to emphasize on how scaling infrastructure can be done seamlessly with the usage of containers and also focus on better ways of deployment, build and testing.
Outline
Tsuru is a open source PAAS system. It helps Sysads to create generic infrastructure and platform in place which comes into life once the developer pushes the code. This self servicing mechanism will be useful to reduce the layers like config management. Since Tsuru leverages the features of docker, it supports both - isolation and scaling. For not so adventurous sysads, who are not ready to risk a software which is in heavy development in production, tsuru can be integrated with the build system, the testing infrastructure can be containers which can be spawned and stopped as needed.
Tsuru’s Overview:
The platform(say Apache, nginx, rails) will be a prebuilt docker image. On tsuru create an app specifying the platform required. The app will be given a domain name. Once the user pushes the code which is to be run on the platform, tsuru creates the container, does a checkout of the code. Hipache is used as a reverse proxy. Tsuru associates the domain name of the app in Hipache with the container. The containers can be increased on the fly and the Hipache will be updated accordingly.
To run services like redis, mysql Tsuru uses rest api to contact our server for info of the services. These info are set as Env Variables on the containers which will be used by the code. It’s our logic to provide different instances of services for different apps, or share same instance of services.
Requirements
Docker, Linux containers (LXC).
Speaker bio
Currenly working with Directi as a Senior System Adminstrator.
Known for including humour in everything. Even Tsuru.
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}