Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/romancin/terraform-oracle-cloud-always-free
Terraform module to deploy OCI instances in Oracle Cloud Free Tier
https://github.com/romancin/terraform-oracle-cloud-always-free
Last synced: 9 days ago
JSON representation
Terraform module to deploy OCI instances in Oracle Cloud Free Tier
- Host: GitHub
- URL: https://github.com/romancin/terraform-oracle-cloud-always-free
- Owner: romancin
- Created: 2020-10-01T13:00:35.000Z (about 4 years ago)
- Default Branch: master
- Last Pushed: 2020-10-04T20:40:18.000Z (about 4 years ago)
- Last Synced: 2024-08-01T13:32:55.654Z (3 months ago)
- Language: HCL
- Size: 31.3 KB
- Stars: 4
- Watchers: 2
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
terraform-oracle-cloud-always-free
==================================
This Terraform module provisions 2 OCI instances using Oracle Cloud's Always Free services: https://www.oracle.com/cloud/free/
Also, this repo now includes an Ansible playbook you optionally can use to install docker on both instances, including also portainer installation.
Variables
=========
region = Region where instances will be deployed ("eu-frankfurt-1" by default).
vcn_dns_label = The label you want to use for your DNS.
Most types of Oracle Cloud Infrastructure resources have an Oracle-assigned unique ID called an Oracle Cloud Identifier (OCID). It's included as part of the resource's information in both the Console and API.
Check the documentation to see how can you extract this values from your account: https://docs.cloud.oracle.com/en-us/iaas/Content/General/Concepts/identifiers.htm
tenancy_ocid = ""
compartment_ocid = ""
And for authentication objects: https://docs.cloud.oracle.com/en-us/iaas/Content/API/Concepts/apisigningkey.htm
private_key_path = ""
user_ocid = ""
fingerprint = ""
Execution
=========
1.- ```terraform init```
2.- Take terraform.tfvars file in the repo and fill it with your own data
3.- ```terraform plan```
4.- ```terraform apply```
4.- Optional: If you are going to deploy traefik + portainer, it is time to take the Terraform outputs (Public IP of the instances) and create 2 DNS entries for each of them:
For example:
```
cloudserver1.mydomain.com. 0 A 1.1.1.1
cloudserver2.mydomain.com. 0 A 2.2.2.2
*.cloudserver1.mydomain.com. 0 CNAME cloudserver1.mydomain.com.
*.cloudserver2.mydomain.com. 0 CNAME cloudserver2.mydomain.com.
```
In my case, the main domain is pointing to another traefik, so I need to give an entire new subdomain to traefik running on the public cloud instances. This way, every host label under *.cloudserver1.mydomain.com will be exposed by traefik, and routed to the container where the service is running.
Now, when the DNS entries are created, edit the yml files in the host_vars directory to overwrite the configuration for each instance:
```
---
domain_name: "cloudserver1.mydomain.com"
root_access_name: "portal.cloudserver1.mydomain.com" #This is used to "publish" services under this domain, with the default configuration, portainer will be accessed in https://portal.cloudserver1.mydomain.com/portainer/
acme_email: "[email protected]"
```
Feel free to adapt it to your own configuration.
5.- To install only docker, execute:
```
ansible-playbook -i inventory install-docker.yml -e install_traefik_and_portainer=false
```
6.- To install only docker with portainer, execute:
```
ansible-playbook -i inventory install-docker.yml -e install_portainer=true
```
7.- To install docker with traefik and portainer, execute:
```
ansible-playbook -i inventory install-docker.yml -e traefik_web_user="admin" -e traefik_web_password="password"
```
After playbook finishes, you can access this URLS:
https://traefik.cloudserver1.mydomain.com --> Traefik dashboard on instance 1. Default username and password are "admin" and "password"
https://traefik.cloudserver2.mydomain.com --> Traefik dashboard on instance 2. Default username and password are "admin" and "password"
https://portal.cloudserver1.mydomain.com/portainer/ --> Portainer on instance 1. **IMPORTANT**: Configure it just after deploy, as in the first use will ask you for the password.
https://portal.cloudserver2.mydomain.com/portainer/ --> Portainer dashboard on instance 2. **IMPORTANT**: Configure it just after deploy, as in the first use will ask you for the password.