Time |
S |
Nick |
Message |
00:53 |
|
pdurbin |
Master Foo and the Programming Prodigy - http://catb.org/esr/writings/unix-koans/prodigy.html |
10:00 |
|
prologic |
pdurbin, aditsu got a questin for you guys |
10:00 |
|
prologic |
so I'm nearly done writing this blog article |
10:00 |
|
prologic |
but I'm kind of thinking |
10:00 |
|
prologic |
factory should manage DNS too |
10:00 |
|
aditsu |
sup? |
10:00 |
|
prologic |
or at least not manage it per se but be able to create domains and DNS for some arbitrary service/provider |
10:01 |
|
prologic |
I just want to: |
10:01 |
|
prologic |
factory up |
10:01 |
|
prologic |
and expect not only the Docker infrastructure to come up |
10:01 |
|
prologic |
but a DNS ready to go too |
10:01 |
|
prologic |
unless of course I create a whole different tool to do this |
10:01 |
|
prologic |
it *could* be one of those "separatin of concerns" type things |
10:02 |
|
prologic |
I don't know of a pluggable/agnostic/declarative way of managing domains at present |
10:03 |
|
prologic |
thoughts? |
10:06 |
|
aditsu |
sounds like you want a programmable dns server? |
10:15 |
|
prologic |
well |
10:15 |
|
prologic |
I already have one of those |
10:16 |
|
prologic |
https://github.com/prologic/udns |
10:16 |
|
prologic |
*which* I could use :) |
10:16 |
|
prologic |
but many registrars suck and have poor API(s) |
10:25 |
|
aditsu |
what does it have to do with registrars and their APIs? |
10:26 |
|
aditsu |
do you want to register a new domain when you use your factory thing? |
10:30 |
|
pdurbin |
prologic: yes, it makes sense that factory would manage DNS |
10:40 |
|
pdurbin |
would or could |
11:20 |
|
prologic |
ahh really? |
11:20 |
|
prologic |
you wouldn't consider thing as a searpate tool or such? |
11:20 |
|
prologic |
aditsu, no disregard registrars |
11:21 |
|
prologic |
we *should* assume that a domain is already registered and pointed to some dns servers |
11:21 |
|
prologic |
the point I was trying to make was that since factory builds and sets up Docker infrastructure on varisu cloud providers |
11:21 |
|
prologic |
should it also be capable of managing/creating dns for domains pointed at those same cloud providers (assuming they provide dns services) |
11:26 |
|
pdurbin |
prologic: are you basically re-inventing openstack? I haven't checked if openstack supports docker these days. |
11:34 |
|
prologic |
it does |
11:34 |
|
prologic |
via heatmap |
11:34 |
|
prologic |
but no I'm not really |
11:34 |
|
prologic |
when Docker first became a thing |
11:34 |
|
prologic |
and then started gaining a lot of tractin |
11:34 |
|
prologic |
a lot of PaaS and IaaS type software and services were spawned |
11:35 |
|
prologic |
Deis, Flynn, Flocker, Shipyard, etc |
11:35 |
|
prologic |
but they all have their pros/cons obviously |
11:35 |
|
prologic |
one of the biggest cons for me was their complexity; either in design; features or setup |
11:36 |
|
prologic |
when I blogged about a Docker-based mini PaaS here: http://shortcircuit.net.au/~prologic/blog/article/2015/03/24/a-docker-based-mini-paas/ |
11:36 |
|
prologic |
I mentioned and linked to the blog post and comments I was referring to |
11:36 |
|
prologic |
and a promise I made to deliver |
11:36 |
|
prologic |
this glob post: http://www.centurylinklabs.com/flynn-vs-deis-the-tale-of-two-docker-micro-paas-technologies/ |
11:36 |
|
prologic |
and my comments: http://www.centurylinklabs.com/flynn-vs-deis-the-tale-of-two-docker-micro-paas-technologies/#comment-1910702097 |
11:44 |
|
prologic |
(todoapp) |
11:44 |
|
prologic |
prologicdaisy |
11:44 |
|
prologic |
Tue Jul 07 21:48:12 |
11:44 |
|
prologic |
~/todoapp |
11:44 |
|
prologic |
$ docker-compose ps |
11:44 |
|
prologic |
Name Command State Ports |
11:44 |
|
prologic |
------------------------------------------------------------------ |
11:44 |
|
prologic |
todoapp_redis_1 /entrypoint.sh redis-server Up 6379/tcp |
11:45 |
|
prologic |
todoapp_todoapp_1 todoapp Up 8000/tcp |
11:45 |
|
prologic |
well |
11:45 |
|
prologic |
I've proven my point |
11:45 |
|
prologic |
You *can* quite literally go from development to proudction in ~5mins |
11:45 |
|
prologic |
now I just have to tie a few more pieces together |
11:45 |
|
prologic |
like dns |
11:45 |
|
prologic |
pdurbin, aditsu any further thoughts? |
11:54 |
|
prologic |
pdurbin, aditsu I'm now thinking of something like this: https://gist.github.com/83e8ee24ad6e56758927 |
11:54 |
|
prologic |
with quite literally a single command to bring it all up: |
11:54 |
|
prologic |
$ factory up |
12:01 |
|
pdurbin |
nice. I think codex and hydrajump are docker enthusiasts. |
12:01 |
|
pdurbin |
prologic: is your blog post ready to go? |
12:05 |
|
prologic |
no not yet |
12:06 |
|
prologic |
as I've been saying all along |
12:06 |
|
prologic |
this last piece to tidy up and finish |
12:06 |
|
prologic |
I don't want users to have to fuff around with dns/zones/etc |
12:06 |
|
prologic |
point a domain at digitalocean for examplea |
12:06 |
|
prologic |
and factory up |
12:09 |
|
pdurbin |
right. ok |
13:22 |
|
aditsu |
prologic: the only other thought is "what is all this stuff for?" |
13:37 |
|
pdurbin |
aditsu: where do you deploy your apps to? Heroku? AWS? physical servers? |
13:38 |
|
aditsu |
physical servers and a couple of VPS'es (rackspace, buyvm, potentially linode) |
13:39 |
|
pdurbin |
running ubuntu? |
13:39 |
|
aditsu |
99% gentoo |
13:40 |
|
aditsu |
I think the linode one has ubuntu but I haven't deployed anything there so far |
13:41 |
|
aditsu |
(I didn't set up that one) |
13:41 |
|
pdurbin |
interesting |
15:33 |
|
codex |
:nod: on docker |
15:33 |
|
codex |
fantastic concept and nicely put together |
15:34 |
|
codex |
if only they add out of the box gre/openvswitch meshing with an EASY config |
15:34 |
|
codex |
so you can cluster accross multiple providers |
15:34 |
|
codex |
(but it's coming) |
15:46 |
|
pdurbin |
gre? |
20:07 |
|
prologic |
aditsu, what is this stuff for? well not for you :P haha |
20:08 |
|
prologic |
Containers are the future man :) |
20:36 |
|
aditsu |
if you can't articulate a clear advantage, then they're obviously just a fad |
20:46 |
|
pdurbin |
are we talking about Docker vs. Gentoo? :) |
21:32 |
|
prologic |
aditsu: of course I can clearly articulate what the advantage is and what I'm doing |
21:32 |
|
prologic |
in a nutshell I'm developing a set of tools to build and deploy web applications with a single command/step |
21:33 |
|
prologic |
I'm also writing a blog post about it :) |
21:33 |
|
prologic |
if that isn't clear I don't know what is :P |
21:33 |
|
prologic |
and lol Gento and Docker don't even compare |
21:33 |
|
prologic |
haha |
21:41 |
|
aditsu |
that's like apples vs parachutes |
21:43 |
|
aditsu |
about deploying with a single command - that's what shell scripts are for, or ant, or whatever |
21:52 |
|
aditsu |
and you didn't even mention containers |
21:55 |
|
prologic |
ok good point |
21:56 |
|
prologic |
let me think about it :) |
22:01 |
|
prologic |
Okay so I'm writing this blog post on how to go from development to production in 5 mins using Docker and several other related tools including Docker Machine, Docker Compose, autodock and factory |
22:01 |
|
prologic |
It's just more of a guide of what's possible with Docker and Containers |
22:02 |
|
prologic |
factory is (as an aside) one of the other tools I've written (as well as autodock) to declaratively configure and manage Docker machines in a single, simple YAML based configuration file |
22:03 |
|
prologic |
The "clear" advantage here is that this will work with just about any web application; and no you don't have to write any shell scripts. I'll be talking about that in the blog post too; how you can apply this to a Ruby or Java web app. |
22:23 |
|
pdurbin |
can't you go from dev to prod in 5 minutes with Heroku? |
22:23 |
|
pdurbin |
I've never tried it but that's the impression I get. |
22:38 |
|
prologic |
Yes in fact you can! |
22:38 |
|
prologic |
That's one of the wonderful things about PaaS(es) right? :P |
22:39 |
|
prologic |
So one of the clear advantages and differences here is no vendor/platform lockins |
22:39 |
|
prologic |
Use your own hardware, or a cloud provider of some kind. |