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

Shekhar Gulati

@shekhargulati

Let's Build Apps Not Configure Servers!!

Submitted Apr 21, 2014

  1. Learn how to use OpenShift PaaS to turn your idea into publicly hosted web site.
  2. How PaaS can help you build application faster?
  3. Learn OpenShift internals

Outline

Its Friday night and my friend said he would like to watch a movie released today. I don’t want to watch that movie so I have to convince him to watch cricket match instead. My friend said you have time till morning to convince me. Being a web developer, I decided to build a web application that would parse the tweet stream about the movie and give us the overall sentiment about the movie. If more that 60% people have positively tweeted about the movie then we would watch the movie otherwise we would watch the cricket match. To help others like me I decided to host it in the public cloud so that I can share the application URL with others.

To build this publicly accessible web application, we need application stack that includes language runtime, server, database, version control system, public DNS,etc. Configuring and setting up all these myself would consume all my night. Is there an automated solution that can help me get away from doing low level stuff so that I can focus on application development? PaaS or Platform as a Service is an awesome sauce for developers that can automate all the above mentioned and give you a template application that you can hack on.

In this session, we will first take a look at what is platform as a service and why you need PaaS with OpenShift as an example. We will look at different OpenShift components like gears, SELinux, etc. that help us achieve maximum utilization of our hardware. It is also feasible to run OpenShift on your own hardware by using either OpenShift Origin or OpenShift Enterprise. We will cover how you can get OpenShift Origin running on your hardware.

After covering OpenShift internals, we will look at the application source code I developed to convince my friend. Finally, we will look at how OpenShift can help us automate all the low level stuff and help us build scalable web applications.

Speaker bio

Shekhar Gulati is a developer and OpenShift evangelist working with Red Hat. He is evangelizing about OpenShift for last two years and regularly speaks at various conference and user groups around the world to spread goodness of OpenShift. Also, Shekhar has written many technical articles for IBM DeveloperWorks, Developer.com, and JavaLobby.

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