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
Ravishankar N
@itisravi
GlusterFS::AFR() - What you need to know as a sysadmin.
Submitted Mar 28, 2014
Section:
Full talk
Technical level:
Intermediate
Understand how synchronous replication a.k.a AFR works in GlusterFS, so that you, as a sysadmin can handle tricky situations like resolving split-brains with confidence.
Outline
Replication, as the name implies, maintains multiple copies of your data to ensure high availability. There are two popular strategies to replicating data: synchronous and asynchronous.
In synchronous replication, data is written to all the replica volumes in real time. For example if there are 2 hard-disk partitions in a replicate configuration, when the user does a single write() from the mount point, the replication module sends 2 writes(), one to each partition.
In asynchronous replication, the data is written real time only to one partition (master). The data is then synced to the other partition (slave) eventually and periodically using suitable mechanisms (say rsync).
Synchronous replication is generally used when you need real-time failover of transactions. For example, when reading a file, if one partition goes down, the application must be served the data from the other partition instantaneously.
Automatic File Replication(AFR) is the name given to the synchronous replication module in GlusterFS. This talk will be a mostly-everything-but-code overview of how AFR does what it does to ensure your data is kept consistent and in-sync across different replicas. Armed with this knowledge, you can understand how self-heals work, interpret the values of the file’s extended attributes maintained by AFR, identify if a split-brain occurs and what you need to do to resolve it.
Requirements
- You must have setup and used a gluster volume in a replicate configuration.
- You have peeked into the files in the backend bricks and observed that the files have some funny looking extended attributes set on them.
- You are too lazy to read https://github.com/gluster/glusterfs/blob/master/doc/split-brain.md or are not able to make any sense out of it.
Speaker bio
Currently working on GlusterFS at Red Hat.
Likes: Linux, electronics, D.I.Y.
Goes by the online nick of itisravi.
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}