I have to do this already with thousands of servers all running apps. This makes it much easier to do so. No longer to I have to have some kind of monitoring in place to insure that every nginx box has the latest ssl and bash fix along with vendor patches and other crap. One container, redeploy everywhere and restart. Only one thing to check.
You've added a few. For one Jruby is compiled to run on the jvm. Unless you're just playing around at worst that stack should be -|JVM| - locked in container it's isolation not a layer -Linux -Hardware
Or if you're doing development you might have something more like
-|JVM| - locked in container it's isolation not a layer -Linux -VirtualBox -Windows or OSX -Hardware
Docker and it's like are more than just containers. Docker is more like a format and eco system around the core LXC containers that have been around for ever.
Just speaking of the container is is more in line with chroot/jail with even more isolation.
Docker the entire ecosystem is more like Amazons AWS in that there are many prebuilt containers.
And kinda like a configuration management system (chef, puppet, cfengine) in that there is a scriptible interface for building new containers.
And kind of a continuous integration environment because you can spin up instances of code for testing with minimal resources then destroy them and spin up the next iteration, rinse repeat within minutes if not seconds.
But docker's probably biggest benfit is it's repeatably. You can run the exact same object in every environment. If designed with service discovery then you can do so with exactly zero configuration changes between dev/qa and prod. Otherwise you may need to pass some environment variables in order to establish database connections and the like.
except your example is just the memorization part. the class A, B, C or/8/16/24, the primary subnets I spent many years in the Novell 4.x days with not knowing what they were and only known what they had to be in order for things to work.
because installing security updates is always easy. At least with a container system you can install and test it in isolation then just run the new container with confidence. Rather than the old fun of "Its patch day! Everyone get ready to validate everything still works again."
being able to go from zero to fully functional and testable running application with mulitple tiers in minutes is a bit different.
Being able to completely uninstall without dpkg-old or random.bak files laying around is kinda nice.
rolling back 3 versions ago is as simple as docker run
Honestly I've been doing this for 22 years and docker is the first time I've looked at a tech and it scared me. It is going to relegate systems administration to little more than rack and stackers. The current DevOps trend is going to become just Dev and everything will be code.
If you're an administrator of pretty much any type you better start learning to program. The days of long lived static apps with a full time support staff is going to go away. The art of setting and configuring the exact combination of packages, standards, access etc will be gone.
That it exists and perhaps some memorization of the major ABC classes. Nothing about what it actually is or anything about the math involved in calculating it.
I worked at Motorola about 10 years ago on a team that was just there to keep old applications written in the 80s and 90s around so that when non-upgraded customers wanted changes they could pay through the nose for us to dig up their applications and make changes. This was big money for Motorola and I guess the customers thought it was better than going through the upgrades.
Just think if Amazon could ship you products next or even same day for very low prices. While others had to rely on USPS, UPS or FedEx prices to get products to you quickly. The outcry for this would be horrible. There would be blood in the streets.
I want my games and voip to be low latency, but not necessarily high bandwidth. I want my streaming content to be very high bandwidth but I don't care if it's got even a multi-second latency.
The thing that will really chap your hide then is that the post office offered to send items faster if the content providers payed more money. They'd even send DVDs next day if a competitor was willing to pay for it. This kind of outrage is why the post office is only out for them selves and screwing over the customers.
Slashdot Mirror
Vagrant is nice for development integration, but we use it with Docker rather than virtual box. Works much much faster.
s/US/World/g
Probably Universe.
Would you like to fly on my new airline "Crash and Burn!!"
I have to do this already with thousands of servers all running apps. This makes it much easier to do so. No longer to I have to have some kind of monitoring in place to insure that every nginx box has the latest ssl and bash fix along with vendor patches and other crap. One container, redeploy everywhere and restart. Only one thing to check.
You've added a few. For one Jruby is compiled to run on the jvm. Unless you're just playing around at worst that stack should be
-|JVM| - locked in container it's isolation not a layer
-Linux
-Hardware
Or if you're doing development you might have something more like
-|JVM| - locked in container it's isolation not a layer
-Linux
-VirtualBox
-Windows or OSX
-Hardware
Docker and it's like are more than just containers. Docker is more like a format and eco system around the core LXC containers that have been around for ever.
Just speaking of the container is is more in line with chroot/jail with even more isolation.
Docker the entire ecosystem is more like Amazons AWS in that there are many prebuilt containers.
And kinda like a configuration management system (chef, puppet, cfengine) in that there is a scriptible interface for building new containers.
And kind of a continuous integration environment because you can spin up instances of code for testing with minimal resources then destroy them and spin up the next iteration, rinse repeat within minutes if not seconds.
But docker's probably biggest benfit is it's repeatably. You can run the exact same object in every environment. If designed with service discovery then you can do so with exactly zero configuration changes between dev/qa and prod. Otherwise you may need to pass some environment variables in order to establish database connections and the like.
except your example is just the memorization part. the class A, B, C or /8 /16 /24, the primary subnets I spent many years in the Novell 4.x days with not knowing what they were and only known what they had to be in order for things to work.
because installing security updates is always easy. At least with a container system you can install and test it in isolation then just run the new container with confidence. Rather than the old fun of "Its patch day! Everyone get ready to validate everything still works again."
being able to go from zero to fully functional and testable running application with mulitple tiers in minutes is a bit different.
Being able to completely uninstall without dpkg-old or random .bak files laying around is kinda nice.
rolling back 3 versions ago is as simple as
docker run
Honestly I've been doing this for 22 years and docker is the first time I've looked at a tech and it scared me. It is going to relegate systems administration to little more than rack and stackers. The current DevOps trend is going to become just Dev and everything will be code.
If you're an administrator of pretty much any type you better start learning to program. The days of long lived static apps with a full time support staff is going to go away. The art of setting and configuring the exact combination of packages, standards, access etc will be gone.
not what you're looking for but cool for the static linker fan:
http://blog.xebia.com/2014/07/...
That it exists and perhaps some memorization of the major ABC classes. Nothing about what it actually is or anything about the math involved in calculating it.
I don't understand the point. Unix is some Archaic Linux like OS as well.
Evolution? Pretty sure this just means god hates gays a little less.
This is really just a way for the FCC to privatize their IT department without the liberals even noticing.
I worked at Motorola about 10 years ago on a team that was just there to keep old applications written in the 80s and 90s around so that when non-upgraded customers wanted changes they could pay through the nose for us to dig up their applications and make changes. This was big money for Motorola and I guess the customers thought it was better than going through the upgrades.
Exactly, when you see a cable for $2.99, $19.99, and $199.99, the get the 20 dollar one.
who cares, BSD is just some long forgotten Linux like operating system that nobody uses any more.
ROFL!
for black Friday spam. just come to Slashdot.
Just think if Amazon could ship you products next or even same day for very low prices. While others had to rely on USPS, UPS or FedEx prices to get products to you quickly. The outcry for this would be horrible. There would be blood in the streets.
I want my games and voip to be low latency, but not necessarily high bandwidth. I want my streaming content to be very high bandwidth but I don't care if it's got even a multi-second latency.
The thing that will really chap your hide then is that the post office offered to send items faster if the content providers payed more money. They'd even send DVDs next day if a competitor was willing to pay for it. This kind of outrage is why the post office is only out for them selves and screwing over the customers.
It actually packages it's own embedded ruby instance, and if you excluding ruby and by extension Vagrant you really are missing out.
The chef server is in Erlang, of course the chef server doesn't do very much but auth hosts and server files. the client does pretty much everything.
It's getting close https://www.google.com/webhp?s...