Using Portainer to Manage and Deploy Oracle Containers with Pure Storage

 

In this blog I will show you how can we can install Portainer ( A platform-agnostic tool for managing containerized applications ) to manage Oracle database containers and persistent volumes running Pure Storage FlashArray



 


Install Portainer



Portainer runs as container, so installing it is just like installing any other container on Docker.

Note: Docker and the Oracle container image is already installed - if you want more detail on that check out - http://bannaych.blogspot.com/2021/02/oracle-19c-database-clones-using-pure.html

  • Lets create a persistent volume to run Portainer on, using the Pure Docker plugin
# docker volume create port_vol
port_vol
  • Lets create the Portainer container
# docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always \
-v /var/run/docker.sock:/var/run/docker.sock -v port_vol:/data \
portainer/portainer-ce
  • Lets confirm the new Portainer container is running
# docker ps
CONTAINER ID        IMAGE                                                        COMMAND                  CREATED             STATUS                 PORTS                                            NAMES
b9da841acf8b        portainer/portainer-ce                                       "/portainer"             2 hours ago         Up 2 hours             0.0.0.0:8000->8000/tcp, 0.0.0.0:9000->9000/tcp   portainer
  • Now we connect to Portainer using the Port 9000 and the IP address of the host http://192.168.111.198:9000 - login as admin and the root password





  • Select the local stack  - then select containers ( you can see we have our 3 containers including Portainer container




Let's create a new clone Oracle container using Portainer.


  • First lets create our persistent volume by cloning the original Oracle volume ora19c
    • Enter the new volume name ora19clone1
    • Select the Pure driver
    • Select the driver options - Enter the following  (name: source value: ora19c)
    • Select create the volume

  • Confirm the volume has been created

  • Log into the array and confirm



  • Lets new create our new clone container - select create container 
    • Provide the new container name: new-ora19clone
    • Enter the container image for oracle 19c
    • enter the Volume mapping details ( path and clone volume name )
      • path = /opt/oracle/oradata
      • volume = ora19clone1
    • Select Deploy container





  • In a few seconds the container is up and running


  • Lets now confirm this from the command line on the docker host, you can see our clone container up and running using container id: dca9b8d00cc1

  • Lets log into the container ( dca9b8d00cc1) , confirm the new clone volume is mounted and the clone database copy is up and running


Note: you see the clone volume mounted on /opt/oracle/oradata ending in the S/N 532d


  • Lets now log into Oracle and confirm we have data from the original table (table1) from the master database 


Summary


In this blog we have seen how we can manage and deploy Oracle containers using Portainer.
Portainer can remove some of the complexities around docker container and Kubernetes to give you an easy and comprehensive management tool.













Comments

Post a Comment

Popular posts from this blog

Oracle Containers on Kubernetes and Pure Service Orchestrator

Image
Pure Service Orchestrator allows for smart provisioning of storage to one or many arrays, this provides administrators and developers the ability to  provision storage on demand with cloud like functionality, ease and flexibility. In this blog I will use Pure Service Orchestrator ( PSO ) to automate the provisioning of volumes to Kubernetes which will then be used to create Oracle containers using persistent storage.   My next blog will demonstrate the  power of using  Pure Storage snapshots and cloning to rapidly create instant copies of the source Oracle database. Environment NOTE:  In this blog I will not be going through the Kubernetes cluster install Role FQDN IP OS RAM CPU K8 Ver Master master.localdomain.com 192.168.111.231 Ubuntu 18.04 5G 3 1.18 Worker1 worker1.localdomain.com 192.168.111.232 Ubuntu 18.04 8G 4 1.18 # kubectl get nodes -o wide NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME m
Read more

SQL Server container with Pure Storage Docker volumes

Image
SQL Server on Docker with Pure Storage Persistent Volumes Docker and containers have become an integral part of virtualisation. Having the ability to spin up containers has almost instantly transformed the way we build, develop and manage applications. Many of us have been using some sort of virtualisation for decades as this is not a new concept. Due to their speed, simplicity and automation, container usage has garnered substantial popularity and are becoming ubiquitous in the field of virtualisations. So why use containers ? Decouple application runtime from infrastructure. Runs instantly. Process and user isolation for application multi-tenancy. Key building blocks for microservices. But what happens when you delete the container ? The main issue in deleting a container is that you delete the writeable layer and any data that was there, hence no data persistence. Docker volumes provide us a way to decouple your application from its state, to the point where you c
Read more