Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why I left Heroku, and notes on my new AWS setup

holovaty.com

Post reply on HN
Print view View original

161–170 of 231 posts

Re: Why I left Heroku, and notes on my new AWS setup

#161

Post by juanvallejos »

THIS IS A MESSAGE OF SPANISH intellegence AGENCIES IN VENEZUELA.

aINTELIGENCIA, INTELLIGENCE AGAINST THEM SOMETHING TO BELIEVE THAT NO OTHER aCONOZCAN to OPERATIONS. to

-------------------------------------------------- ----------------------------

to http://www.liberenlosya.com/foros/?mingleforumaction=viewfor...

to Good morning gentlemen, through this medium, I am writing to you in order to notify them: a

to my recordings SHOWING IN THE NEWS OF MARIO SILVA aa ARE A MONTAGE OF INTELLIGENCE AGAINST OTHER SURVEYS to STATISTICS SHOWING WHERE IS Capriles Ensim to FAR IN THAT NUMBER OF VOTES NICOLAS MADURO.a

to GIVE THEM SOMETIMES AGENCIES SUCH gravaciones TO THINK THAT ARE REALES.a

to TO HIDE SATELLITE TECHNOLOGY TYPE WITH INFORMATION DERIVED to THE INHABITANTS OF THE PAIS.a

to send it to CAPRILES RADONSKI.a to

-------------------------------------------------- -----------------------

TECHNOLOGIES ARE SHOWING PEOPLE THAT COME IN A MONITOR IN AGENCIES

INTELLIGENCE.

-------------------------------------------------- ----------------

IN THIS FORUM IS AS AGENTS AND KOREAN CHINESE JAPANESE ASIAN TREAT THESE to

EVENTS AND INFORMATION TO BE SHOWN IN MEDIA, WE GIVE A SHEET THE PRACTICE TO LOOK to REAL.a

IN CHINESE SATELLITE'S PAGES WITH THAT THESE ARE CRIMENES.a

GET VISUAL MOTION INFORMATION AND HEARING OF PERSONAS.a

see the string so that my recordings are not of MARIO.a

YOU SEE A MATURE NICOLAS SEEN THAT did not sleep, BY THE NEWS THAT SHOWED aa

CHECKED THE FORUM IN BUTTON FOROS.aaaa WWW.LIBERENLOSYA.COM

-------------------------------------------------- --------------------------------- aaaaaaa

Re: Why I left Heroku, and notes on my new AWS setup

#162

Post by StavrosK »

mpdehaan2 wrote: post #136
23david wrote: post #122

Earlier quoted context omitted.

FWIW, I tested juju a few months ago and found it to be buggy and unreliable. Sometimes the instances would connect together correctly, and sometimes they would fail inexplicably. Didn't seem ready for any kind of production use to replace config mgmt tools.

If you are looking for another general purpose orchestrator, I'd suggest taking a look at Ansible - http://ansible.cc/ Disclaimer: I am the primary author.

I have tried ansible and love it. I invested the time (a few hours) to get a script working for my stack, and now I have a 70ish line script that will provision a server or VM (with a shared code directory in the VM), from clean installation to the codebase up and running in its production state, in one command.

New project? I just copy the script, change a few variables (names and packages it needs), and I get deployment for free.

Re: Why I left Heroku, and notes on my new AWS setup

#163

Post by adrianh »

pramodliv1 wrote: post #127

I saw your video ( http://37signals.com/svn/posts/3446-adrian-holovaty-talks-so... ) on the 37signals blog where you mentioned that the server stuff was boring. Now it just got interesting!

Ha, I guess you're right! I must say it's become more interesting than I expected.

Re: Why I left Heroku, and notes on my new AWS setup

#164

Post by borlak »

andrewgodwin wrote: post #3

Sad to see the recommendation to use MySQL - in my experience RDS hasn't been worth the effort - but I'm probably biased since I already invested the time in automating PostgreSQL replication setup.

In my experience RDS has been amazing, and I am a MySQL guy. I say it like that because as a MySQL guy I would much prefer to setup my own server and use a third party engine like Percona or Maria, but RDS(MySQL) performance has been incredible.

The only thing I would complain about is the lack of a proxy or load balancer in front of their Multi-AZ setup. With any failover you are forced to have a downtime of 3-5 minutes while DNS propagates.

Re: Why I left Heroku, and notes on my new AWS setup

#165

Post by uggedal »

sigmavirus24 wrote: post #23
boothead wrote: post #16

If you think puppet/chef is too much complexity you might find saltstack worth some attention. I haven't used it in real anger yet, but I've really liked what I've seen so far. I see they've even got instructions specific to aws now too [1] Also worth mentioning cloud formation as well [2]. That might make the pain of chef/puppet more of a worthwhile investment! [1] https://salt-cloud.readthedocs.org/en/latest/topics…

Also there are some useful example states on GitHub: https://github.com/esacteksab/salt-states

My salt states are public[1] and include among other things setup for nginx/redis/postgresql/uwsgi which powers a few Django and Flask sites.

[1]: https://github.com/uggedal/states

Re: Why I left Heroku, and notes on my new AWS setup

#166

Post by lelandbatey »

jcampbell1 wrote: post #150
skinnymuch wrote: post #98

Earlier quoted context omitted.

What's the difference between EC2 and a VPS for you? Do your VPSs already have things installed or a GUI? I've used EC2 before as a single server, never scaling. The main difference was installing things that are usually pre-installed (like on Ubuntu's official desktop image). Is that it or is it more about the scaling? And thanks for the reference to Digital Ocean. Never heard of them before. Seems great, might try…

> What's the difference between EC2 and a VPS for you? For me it that restarting an EC2 instance deletes all the local storage. I have had good success just getting a big ass VPS, and running the database locally, and pushing text backups to S3. It is trivial to manage, and in the real world, downtime is more likely to be caused by configuration wonkiness than hardware failures. You also have to have a huge amount of…

If you where having all your data deleted when you restarted your EC2 server, then something was VERY wrong. I'm not an expert, but I've used EC2 a little bit and I think I hit that exact problem.

The thing is that for whatever reason, data wasn't being written to the EBS (the virtual hard disks for use with EC2 instances) and was instead being written to the "ephemeral storage", a really big local data store that every EC2 instance has that is basically a `/tmp` directory. If the server restarts, everything in the ephemeral storage is destroyed.

Re: Why I left Heroku, and notes on my new AWS setup

#167

Post by makerops »

bearwithclaws wrote: post #4

> The way we set up Soundslice is relatively simple. We made a custom AMI with our code/dependencies, then set up an Elastic Load Balancer with auto-scaling rules that instantiate app servers from that AMI based on load. Doesn't sound that simple to me (as a complete sysadmin noob). Somebody should write a book about this.

I am working on a site right now http://makerops.com that will walk through via screencasts, texts, and interactive learning a lot of the issues described by the OP. How to interact, as a dev with various cloud APIs, to auto scale, manage configurations, etc.

Re: Why I left Heroku, and notes on my new AWS setup

#168

Post by [deleted] »

tptacek wrote: post #125
toomuchtodo wrote: post #26

Earlier quoted context omitted.

You know those days when you think you know a bit, and stumble upon someone who knows vastly more than you? Today was one of those days. It appears we're both Devops guys in Chicago; can I buy you a beer sometime?

If free beer is the price of entry here, I'd love to pick your brains as well, since we're about to run into this exact same problem. (I'm in Chicago as well)

[deleted]

Re: Why I left Heroku, and notes on my new AWS setup

#169

Post by grosskur »

tlrobinson wrote: post #139

I love Heroku: git deployment, the "dyno" abstraction, Procfiles, buildpacks, putting configuration in environment variables (all the 12 Factor App stuff: http://www.12factor.net/ ). Is there an open source implementation of Heroku (close to 100% compatible, not just similar ideas) that runs on your own cloud?

See OpenRuko:

https://github.com/openruko

I haven't used it myself, but it seems to be a Heroku clone written in Node.js.

There's also CloudFoundry, which used to be quite different but is now adding support for Heroku-style buildpacks in V2:

http://docs.cloudfoundry.com/

Re: Why I left Heroku, and notes on my new AWS setup

#170

Post by ia »

toomuchtodo wrote: post #14
bearwithclaws wrote: post #4

> The way we set up Soundslice is relatively simple. We made a custom AMI with our code/dependencies, then set up an Elastic Load Balancer with auto-scaling rules that instantiate app servers from that AMI based on load. Doesn't sound that simple to me (as a complete sysadmin noob). Somebody should write a book about this.

Would you be interested in a blog post about it? I'm a sysadmin/devops with 12 years in, and build stuff like this on a daily basis. I wouldn't mind sharing how the sausage is made.

yes. very interested. very very interested :)
Post reply on HN