Are you new to blogging, and do you want step-by-step guidance on how to publish and grow your blog? Learn more about our new Blogging for Beginners course and get 50% off through December 10th.
WordPress.com is excited to announce our newest offering: a course just for beginning bloggers where you’ll learn everything you need to know about blogging from the most trusted experts in the industry. We have helped millions of blogs get up and running, we know what works, and we want you to to know everything we know. This course provides all the fundamental skills and inspiration you need to get your blog started, an interactive community forum, and content updated annually.
In this blog post I am going to explain how to create and configure the Kubernetes Cluster in the Oracle Cloud Infrastructure. Oracle offers its own service called Oracle Kubetnetes Engine (OKE).
As a prerequisite, a user must already exist in the cloud who has permission to create and manage the Kubernetes cluster in a compartment. The following policies are necessary to create, update and delete cluster components:
Allow group <group-name> to manage instance-family in <location>
Allow group <group-name> to use subnets in <location>
Allow group <group-name> to read virtual-network-family in <location>
Allow group <group-name> to use vnics in <location>
Allow group <group-name> to inspect compartments in <location>
In the previous blog post I explained the creation and configuration of the instance pool and autoscaling configuration.
If you run farm from the web server and the application server, you should route the client accesses to these servers via a load balancer. The load balancer receives the client requests and distributes them within the server pool.
In this blog post I am going to explain the provisioning of the compute pool node with autoscaling configuration. I have already created the VM instance-bne and installed the Nginx web server in the VM.
During the provisioning of the Linux VM I added the Cloud-Init script as the advanced option that executes the installation and configuration of the Nginx webserver in my vm:
Auf der Go DevOps 2019 am 2. und 3. September in Berlin dreht sich alles um Infrastruktur, Security und kulturelle Aspekte von DevOps. In drei laufenden Streams wird viel Know-how geboten, um allerlei Herausforderungen im IT-Umfeld bewältigen zu können. Beugen Sie verzögerten Projekten oder verpassten Deadlines vor und tauschen Sie sich mit Gleichgesinnten aus. Melden Sie sich jetzt an: GoDevOps
A user in the OCI can access, create and administer cloud services. The permissions for users can be consolidated in groups as policies. Policies define the allowed actions for group members and in which department.
A Compartment is logical group of resources that represents an organizational unit. Resources will be created in a compartment. You cannot move the cloud resources from one compartment into another…
Every cloud administrator wants to administer and monitor their cloud resources from a central location. The Cloud (OCI) Command-Line interface OCI CLI enables this. In this blog post I will describe the installation and configuration of the Cloud CLI on an Linux Server with OS Oracle Enterprise Linux.
To install and use the Cloud CLI you must have the following data:
OCI User: Users for connecting to cloud services
A SSH Keypair used for signing API requests, with the public key uploaded to Oracle OCI
This blog entry is the third and last part of the series „Create APEX in AWS“. Here I describe the installation and configuration of Apache Tomcat and the deployment of the ORDS application in Tomcat. Later I will explain the installation of the Webserver Nginx and configure it to access APEX via Apache Tomcat and ORDS.
Information about the installation of the APEX application in AWS can be found here. The installation and configuration of Oracle Data rest service is described here.