Hacker News new | past | comments | ask | show | jobs | submit login

Hello, I'm the author of the OP, And as always, I'm around to answer any questions.

Ok, here goes:

> Ok, so I’m going to ride the command line like a cowboy

That's a lot of kool-aid in a short sentence. Note, I'd rather have this over "Rackspace is the market-leading solution provider in the containerized virtualization space, empowered by award-winning Free and Open Source Software (FOSS) products such as Docker and LXC", but I do feel that you're pushing it a bit far in this post, here and there.

Yeah - I agree, I pushed some edges in the post - I'll keep that in mind. Thank you.

Ha, actually, I genuinely wonder: How did you feel when you wrote that you were going to ride the command line like a cowboy? :-)

Well, I moved to Texas in June and haven't really gone native yet, so I needed something to help me fit in.

Welcome to Texas! The winter will be a lot more fun than the summer was.

while docker seems really awesome for development, all articles i've read so far stop at the point where things run, but are not yet really production ready: your article ends with running django in a docker container, which is really cool - but on a random? nat'ed port.

what would be the next steps to actually expose this django container to the public via port 80 and surviving a host server reboot?

When you start the container you can specify which port you want using the -p command.

This command would start it on port 8000, but you could change to any other port you want, assuming it is free.

$ docker run -d -p :8000 kencochrane/django-docker

I'm also pretty sure that when your host is restarted the container will start back up when docker does, if the container was running before the host was restarted.

Please never act professional! That post is awesome.

I will not lie, I felt kind of silly opening the page at work and did the quick ctrl+1 to switch to a tab when a coworker walked by my office!

Aside from that, I have had a recent interest in Docker, LXC and QVD. Thanks for the information, jnoller. I have been doing the reading (without the typing), but this just reassured me that I am on the right path. The Docker part rolls in for segregating applications from each other. In case one app gets compromised, they do not all fall down. Another interest is hitting a few compliance standards by utilizing LXC on its own. Finally, virtualization with QVD and LXC.

Please tell me that "Performance Cloud Servers" are not the official response to the issue of normal servers being created very slooooowwwwly... The time spent in BUILDING is really annoying. Are you planning to improve those?

I know the performance servers improve it, but I'm specifically asking about the standard flavors. On your competitor's system for comparison (standard image, smallest flavor, no bonus payments):

    $ time nova boot ....
    0.24s user 0.04s system 1% cpu 20.724 total
    $ nova console-log
    Cloud-init v. 0.7.3 finished at Mon, 11 Nov 2013 19:08:50 +0000. Datasource DataSourceEc2.  Up 54.42 seconds
In practice that means <1min until the machine is ssh-able.

Smallest non-performance instance in rackspace ORD: around 5 minutes until ACTIVE.

As it says in the post - the prices of the performance instances is lower than the standard flavors, and we will be phasing out the standard (Non Performance) flavors as we complete the rollout to all data centers.

Sorry, but that's just marketing speak. Eliminating $16 option and making $29 the new lowest one is not lowering prices. I'm running a number of smallest servers, so it's just going to cost me 2x the total price.

I'm digging "Peanut Butter Docker Time". Crunchy. :)

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact