In this interview from today I mention Rackspace’s support for Azure, the OpenStack Innovation Center, for which we will be turning up two 1,000 node (yes, bare metal node) test clusters for OpenStack across two unique regions, OpenStack Magnum, now offering Kubernetes, Docker Swarm, and Apache Mesos bay types, and the difference between declarative and imperative orchestration systems, and what the key advantages to each are.
I normally use Linux to batch resize images from a CLI, or using scripts. My go-to tool on Linux is ImageMagick, or something like
mogrify -resize 1200 *.jpg. When my wife turned to me from her MacBook Pro laptop asking me how to resize a few dozen images, I remembered that there is a tool that comes with OSX called
A moment later, I had figured out how to shrink the whole batch of JPEG images in that directory:
sips -Z 1200 *.jpg
That was so easy, I had to share it with you. If you want to check on all the other things you can do with
sips, you can run:
Note that all the images I wanted to shrink were bigger than 1200 pixels wide, so this worked fine. You don’t want to do this for smaller images because it will try to grow them for you.
I had the honor of introducing Magnum during the morning Keynote of the OpenStack Summit today before an audience of 6,000 attendees. You can tell these are authentic live demos because there were some tiny quirks. If you can take the 50 minutes to watch the whole thing, It’s worth the time. If you want to fast forward to the parts with Magnum and Kubernetes, check out these sections:
21:36-31:46 Magnum Introduction and Demo
42:31-50:00 Google+Racksapce Multi-Cloud Demo with Kubernetes
Note that toward the end of the Rackspace + Google demo, Sandeep refreshes the page, and an unexpected error happened because the load balancer continued routing requests to the application server with the database he turned off. This happened because it had not yet drained the active connections. We had interference from the audience!! They viewed the IP Address of the app, and accessed it while Sandeep was showing the demo. The Rackspace load balancer does not close new connections to a node in the middle of servicing active concurrent connections unless you *remove* the node. In other words, disabling a node is non-disruptive. If there were no other requests happening at the time we were showing this, it would have acted like it did the night before in the hotel.
If Sandeep had pressed refresh one more time before giving up, it would have worked! Members of the audience were visiting the page literally two seconds later, and they said the app remained on-line flawlessly for another 300+ hits while we were still on stage, and after we finished. They showed us backstage afterward that it was actually still up, and responding correctly.
I am happy that our Kubernetes and OpenStack communities are working together to make sure that container technology is equally useful and accessible for all types of clouds.