#DevOpsDays Austin is approaching fast. Today, I was awoken by an email about the attendee information for the event. The Flux7 team will be attending the event, and we are looking forward to networking with the #DevOps community in Austin.
For the readers outside of Austin, our Texan city has one of the largest #DevOps communities in the country, and possibly around the world. Austin has many tech startups. There are more than 150 that are registered with Austin’s Capital Factory, and there are many more like Flux7 that are not registered. A large number of these startups are working with web or mobile technologies, thus #DevOps is a word very familiar to a lot of people in Texas Hill Country.
I anticipate that It’s going to be a big show. The attendee list is showing approximately 360 people, and there are 34 people registered as speakers. So, with a total of more than 400 attendees, plus volunteers and organizers, we’re talking about a strong interest in #DevOps and the Austin tech scene. The program spans two days. Day One is full of talks from Rackspace, Chef, PagerDuty, Baldaresh, Sumo Logic, Flux7 (that’s us), StormPath and Data Fundamentals.
On Monday, my plan is to attend the following:
Matt Ray’s talk on Chef. I want to hear Matt’s thoughts on Chef’s maturity model as we move towards deploying Chef at scale for our enterprise clients.
Who Watches the Watchman.
Pete Carapetyan’s talk on Chef pitfalls.
On Tuesday, I plan to attend:
Instant Ops by AVAST.
Dockerify your CI/CD. I want to see what Rackspace is cooking up.
My presentation, entitled “Using Docker to Improve Web Developer Productivity,” is set for 11:15AM to 11:45AM on Monday, May 5, at The Marchesa Hall & Theatre (6226 Middle Fiskville Rd., Austin).
I will be presenting the work we have done at Flux7 with our clients Auto.com and Horan & Bird.
For both clients, we have implemented standardized local developer environments such that their developers are able to code from their laptops, with no internet dependency. The key is that the local environments are faithfully identical to production so as to avoid bugs due to mismatches between the developer environment and the production environment.
As we always say, though, the devil is in the details.
I will talk about the reasons why we chose #Docker, how we implemented the entire workflow, and the details we had to figure out to allow developers to be highly productive. Some of these follow best practices, and others defy conventional wisdom.
Finally, I will present some results of the impact of our work the clients are now realizing in the field.
See you there.