Potential CFP's for GoRuCo

gistfile1.md

Develop your infrastructure like a deliverable product

What is the future of software delivery?

A quick google search, suggests that SaaS or LXC containers are the future. Unfortunately there is little mention of virtual appliances and immutable infrastructure.

LXC containers are making it easier to package up our software and run it anywhere, but you still need to build these anywhere host machines.

In this session we will cover how to use packer, vagrant, and terraform to develop your infrastructure like a deliverable product that targets any virtual hosting platform. I'll show you how to automate and archive immutable and platform agnostic host machines.

Do you want to sell your software to an Enterprise customer running esxi server behind a firewall? How about deploying that same application as a SaaS product to AWS with just a few terminal commands?

AWS, Heroku, DigitalOcean, Linode, VMWare, VirtualBox... no matter the target, if you want to empower your customers to "choose their own adventure" then this session is for you.

Revised_CFP.md

Never hear the phrase "works on my box" again!

Everyone has heard that phrase and everyone wants to reduce the frustrating situations that are bound to follow.

To eliminate this isse, I will show you how to get production environments and development environments on the same page by transforming your infrastructure into immutable, shareable, versioned archives that can be replicated across teams.

In this session we will talk about three different tools that will help you achieve this goal.

Vagrant is the tool that allows you to develop your application inside a virtual machine that is exactly the same as your production boxes.

Packer is the tool that allows automation of the provisioning and versioning of your vagrant and production boxes. It's like source control for your servers.

Thirdly, Terraform is the tool that allows you to deploy those boxes to any production platform you want.

1. Title: It needs to be more benefit-oriented. "Ship your SaaS anywhere with immutable infrastructure" or something that speaks toward the benefit to the audience
2. Audience: What does this have to do with Ruby?
3. The "In this session" paragraph is strong.
4. In the "do you want to sell..." paragraph, maybe play into "You already have a SaaS. What if you could ship your infrastructure anywhere, with a few terminal commands? You could X, Y, or even sell your product to enterprise customers using esxi behind a firewall."

Adding a bit to tehviking's points - let's start with the title.

You're telling me what to do without telling me why. You might consider rewording this to something that will offer me a benefit if I come listen - I like tehviking's title, but let's work on the rest of it first and then we can come up with a sensible title that reflects the point.

Your first paragraph fails at every level - I apologize for being direct please don't take this as an insult! However you have 3 seconds to capture someone's interest and you blow it here with a question that is so broad... so arguable and completely meaningless that I would probably just move right along.

The next paragraph you talk about "Googling" for an answer - which puts you completely outside the talk itself! "Let's Google the answer to the question I posed about my talk for what you need to know" - can you see the problem with this?

You then add some terms people may or may not know - for instance I have no idea what "LXC" is. "packer", "vagrant" - it's a Ruby conf so a good number of people will know what these are, but you *simply can't count on people understanding their benefits".

Finally in paragraph 4 we get to the point of the talk (I think):

In this session we will cover how to use packer, vagrant, and terraform to develop your infrastructure like a deliverable product that targets any virtual hosting platform. I'll show you how to automate and archive immutable and platform agnostic host machines

OK, you'll talk about the thing you hinted at in your title. I still don't have a clue as to why I care. The last two paragraphs are... I have no idea what you're talking about.

I'm completely confused. Again: this criticism is rather strong but at least you're asking for help which is triple great!!!!*. Love you for that!

Let's get positive now: WTF is this talk about???? < -- the answer to that should be sentence 1. Then why should I care at all <--- the answer to that is sentence 2. Please do not assume anyone knows what you're talking about with acronyms and leading questions - it's condescending.

This is a fairly broad topic you've chosen, so take some time right now to figure out what you'll offer people in 60 or so minutes. I have a feeling it's not going to be a full lesson in infrastructure - so let's be as precise as we can!

Hope you don't mind the directness :):):) - ping me on Twitter when you rework the first paragraph. I'd give it a shot but I (truly) have no idea what you're going for :).

Hey @robconery and @tehviking,

I did my best to incorporate your feedback, I took another stab at it.

Thanks so much for your help.

YES!!!!! I love this! So much better - I'd go to this talk in a heartbeat :). I have nothing more to add here - very well done!

Agreed: much improved, very well done! Couple of last points:

Typo: issue not isse in 2nd paragraph.

The title is a great sales tagline but talk abstracts need to have a "hook" into the tool or technique you're teaching. I'd prefer "Ending 'works on my machine' forever with immutable deploys" or "using Vagrant, Packer, and Terraform to...", or something like that that mentions the technology, since that's what the audience is coming to learn.