Rootconf 2014

On devops and cloud infrastructure

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

http://rootconf.doattend.com

Online Presence

Website | Facebook | twitter

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.

  1. 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.
  2. 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.
  3. 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
  4. 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)
  5. 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?
  6. 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..
  7. Cloud databases:
    • NoSQL Databases (DynamoDB, MongoDB, Couch)
    • The good and bad of NoSQL
    • Automation challenges of NoSQL
  8. Self-healing
    • Automatic remediation of services and servers.
    • Process Protection using Service Protector, Monit
    • Auto Scaling Groups
  9. 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

Hosted by

Rootconf is a forum for discussions about DevOps, infrastructure management, IT operations, systems engineering, SRE and security (from infrastructure defence perspective). more
Leena S N

Leena S N

@leenasn

Continuous Delivery using Jenkins

Submitted Mar 8, 2014

This workshop is aimed at beginners to help them to set up Continuous Delivery using Jenkins and its build pipeline plugin.

The workshop will give an overview of:

  • What is Continuous Integration [CI]?
  • What is Continuous Delivery [CD]?
  • How to setup Jenkins CI server
  • Overview of Jenkins Build Pipeline Plugin
  • Overview of other handy Jenkins plugins for CD implementation
  • Overview of the CD practices such as:
    • Mainline Development
    • Feature Toggles
    • Build Automation
    • Deployment Automation

If time permits, we will also show an overview of how to use a similar setup of CD for Mobile Applications.

Outline

It does not matter how good our design or architecture is, at the end of the day what matters is whether our code is ready for production. But the question is, how we make sure that our code is always production ready. As described by Jez Humble [Co-author of Continuous Delivery book] Continuous Delivery [CD] is fast, automated feedback for production readiness of our code when any change that happens to the code or DB or config or the infrastructure.

During this workshop, we will give an overview of Continuous Integration[CI] and Continuous Delivery[CD] and also talk about the practices that are required for implementing CI and CD such as:

  • Mainline Development
  • Feature Toggles
  • Build Automation
  • Deployment Automation

We will also walk you through setting up CD using Jenkins and its Build Pipeline Plugin. We will also briefly touch upon open source tools that help with deployment automation such as Chef/Puppet, Capistrano etc.

Requirements

Participants are expected to get their laptops with Jenkins installed.

Speaker bio

Leena S N
Head of Engineering @ Multunus Software, Bangalore. At Multunus, we’ve been doing Continuous Delivery[CD] across platforms, languages and framework such as Ruby/Rails, Javascript, Android and iOS [with RubyMotion]. I’ve spoken about CD during DroidCon India 2011 and AgileIndia 2012. I’ve also conducted workshops on TDD in Android using Roboletric during Droidcon India 2014 and TDD in Angular.js during Angular MiniConf 2014. I will be speaking @ RailsConf, 2014 on a similar topic.

Akshay S Murthy
Product Developer @ Multunus. I have been practicing CD ever since I joined Multunus 2 years ago. Also I have worked with Ruby/Rails, Javascript and Backbone JS.

Links

Slides

http://www.slideshare.net/leenasn/continuous-delivery-using-jenkins-34730623

Comments

{{ gettext('Login to leave a comment') }}

{{ gettext('Post a comment…') }}
{{ gettext('New comment') }}
{{ formTitle }}

{{ errorMsg }}

{{ gettext('No comments posted yet') }}

Hosted by

Rootconf is a forum for discussions about DevOps, infrastructure management, IT operations, systems engineering, SRE and security (from infrastructure defence perspective). more