Skip to main content


Showing posts from August, 2018

Learn Docker in 12 Minutes ��

Server 2016: Permissions (Text)

Permissions are not local, but based upon network access. Basic: Read, Read/Write Advance: Full Control, Change, Read NTFS Full Control Modify Read & Execute Read Write Traverse/Execute List/Read Attributes Create Files/Write Data Append Data Write Attributes (Extended) Delete      ↪ Subfolders      ↪ Files Read/Change Permissions. Now; Permissions in Pictures;

AWS Pricing

The Price Is…. Varied. How it works is more important than how it’s priced at this point, so this will be brief(er). E2 and RDS have Reserved Capacity, save up to 75% over the equivalent of on-demand capacity. Instances are;

It's An Ubuntu Server!: But You Can't Visit

We didn’t stop the Ubuntu party! Let’s block domains! I had to check to remind myself that yes, we do have dnsmasq installed.

Kubernetes: A Rolling Deployment...

This is the last module of our beginner’s tutorial! My how time flies. So, what’s the last piece of knowledge? Rolling updates that allow Deployments updates to take place with no downtime. How?

AWS: The Video Star

Or; How to Stream Video within Network Confines (And prevent piracy). How it’s Delivered   Content ————> Consumer Compression happens. Packaging happens based upon protocols. How does it adapt to the variation in network speeds?

Docker: With Networking

Now we're going to start an nginx container that's bound to port 80.

Building Small Containers (Kubernetes Best Practices)

Exactly what it says on the tin.

Docker: The Whale's Unstuck

So I did want to post that other Docker blog post , and it sat in my drafts for a week, but now I'm happy to show that yes, I did get Docker installed on Xenial; It's the 'get' part of install that seems to be out of fashion these days. So, let's get this tutorial on the road, finally.

Docker: The Whale's Stuck

Docker 1.2 - Words Mean Things Images - The blueprints, make up the basis of containers. [docker pull to get Busybox] Containers - Made from images to run the application [docker run of Busybox image] Daemon - Background service managing running, building, distributing docker containers Client - The Command Line that talks to the daemon, though it can be a GUI. I prefer cmd line. Hub - Registry - Directory - of images. 2.0 - How to Run A Static Website Pull image from Hub Run Container See how to run a webserver Well, mission (sort of) accomplished!

New Google Kubernetes Marketplace: A Look at the Partnered Vendors

An article by Tyler Stearns on Solutions Review. Read it at the source, the gist is - Google Cloud Launcher is now Google Cloud Platform Marketplace. Container based applications like Kubernetes. The New Marketplace has easily deployable apps. Security partners Aqua, DivvyCloud, and CyberArk approach Kubernetes security differently. There's more things about Databases, Storage, and Machine Learning at the article, so go read it.

Why Microsoft Can't Design a Consistent Windows

In the end, Windows 10 is still very reductive and looks like a child's toy. The only understandable aspect is people using legacy programs and 10 having to be on a HUGE variety of devices.

Kubernetes: Scale Every Application

SCALING: Changing the number of replicas in a Deployment. The Deployment only created one Pod to run our application, and that just won't do. We need more when traffic increases. When you scale, you make sure new Pods are created and scheduled to Nodes who have the resources. Scaling in will "reduce the number of Pods to the new desired state". "Can we do this automatically?" Yes! But not now. Running multiple application instances require a way to distribute traffic to them all. There is an integrated load-balancers with Services to do so, and they will continuously monitor the running Pods with endpoints , ensuring the traffic is sent only to available Pods.