Red Hat OpenShift OpenShift 3.4, 19 Jan 2017

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Dynamic Provisioning of Container-Native Storage on Red Hat OpenShift Container Platform 3.4

Description

Watch Jose A Rivera – Software Engineer, Red Hat Storage - walk you through the new dynamic provisioning of storage on OpenShift 3.4

A

A

Welcome back in this video we'll be covering the use of dynamically provision, glossary, fair value from an open shift application. If you haven't seen the first part where we deployed container native storage on terr openshift cluster. Please click here to view that video now, let's create a sample application to take advantage of our recently deployed container native storage in this directory. I have a couple yellow files that will describe the storage and the applications that will use that storage.

A

So, first, we will need to establish a storage class for Gloucester FS. This is fairly simple. You just provide the rest URL for michetti for the heck Hetty interface and you will need to specify the requirements. The required parameters for rest, user and rescues are key, but these are not strictly required for our demonstration, so we're just setting them to arbitrary values, so we go and create the storage class.

A

Next we want to create a clustered PVC or persistent volume claim on this is fairly simple. The only thing you need to specify is that the persistent volume that will be created will be of 5 gigabytes in size.

A

So we do again OC create a.

A

Glove surface PVC and persistent volume claim created. So now you can see at the bottom that the PVC Gluster one is pending, and if we wait a little bit, we now have a persistent volume for our PVC created or the capacity of 5 gigabytes and a claim gluster one in our applo project.

A

So now let we look at creating a sample application in this case, we're just going to run a simple engine. X pod.

A

With a service and a route attached to it, so at the top you can see our service that will be using port 80 and it will select a pod name engine X pod one. We also have a route that will, sir, that will point to the service called engine X, and here we have a simple pod definition for our engine. X pod.

A

We obviously use the image for engine X, we specify the port and of course, we specify a volume amount to use. Our recently created Gloucester volumes as our HTML storage, and then you specify the volume as a persistent volume claim down the bottom.

A

Alright, so we do OC create betcha engine X pod and all three resources have been created and if we just wait a little bit for this to change, we have a ninja next pod running.

A

So we can see, for instance,.

A

That we are receiving messages over our service address and to verify that this is in fact working. We will put some information in an index.html file on the pot itself. This is done, the OC exec we expect to the engine X pod and run a shell command to echo, some information to index.html and the appropriate location, and now we can say hello world from glitter effect.

A

Finally, to show you that we are in fact using the surface under the hood, we will go into the Gloucester FS pod itself and then we can do a check for mounted volumes that are mounted by a kitty and then, let's just grab this one here.

A

And we'll do an LS and because I know the directory structure, I know that's under brick and there's the index.html file.

A

Thank you very much for watching. This has been a video presentation for red hat container native storage.