May 2014
12 Mon
13 Tue
14 Wed 10:00 AM – 06:30 PM IST
15 Thu 10:00 AM – 06:30 PM IST
16 Fri 09:30 AM – 10:30 PM IST
17 Sat 09:30 AM – 06:15 PM IST
18 Sun
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,
Domlur, Bangalore
16th and 17th May 2014
MLR Convention Centre,
J P Nagar 7th Phase,
Brigade Millenium campus,
Bangalore
For questions about submissions or the conference, write to support@hasgeek.com
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.
Talks can submitted for the following OSes:
Anshu Prateek
@anshprat
Submitted Mar 11, 2014
To introduce Mock to the audience.
What is Mock?
How does it help?
When and why to use it?
How to get going with a full fledged build in different RH versions using few lines of command?
What and why reproducible build?
Who uses Mock?!
Mock is used for setting up a sanitised build environment. It caches and reuses downloaded OS environment to recreate a new sane environment. Using mock, we can setup an altogether different version environment like Centos5 on a Centos6 machine. This is done using chroot and hence no overhead of virtualization is involved.
Mock helps in setting up a reproducible build environment.
=Why reproducible build?=
From https://wiki.debian.org/ReproducibleBuilds
Allow independent verifications that a binary matches what the source intended to produce.
Help Multi-Arch: same packages co-installation (as they need every matching file to be byte identical).
Be able to generate debug symbols for packages which do not have a “debug package”.
Ensure packages can be built from source.
Access to a RH base environment (Redhat, Fedora, Centos or similar) with mock installed.
A source rpm of a package to be build.
I work as DevOps TechLead for Aerospike, a distributed NoSQL database.
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}