Since 2024 Storage Gateway is removed from oracle cloud infrastructure. However, there are other options mentioned to use buckets in OCI as file system. Detailed in this article.

Options

1) Access via OCIFs.

This is the most viable option to use the bucket as file-system, from the workload VM or server.
For this option, you’ll need to set up OCI config and API Key, configured somewhere , then use it for the tool.

• Install the OCI CLI.

# On RHEL-based OS ..
sudo dnf python36-oci-cli
# Or install the CLI for other OS (on-premise).
bash -c "$(curl -L https://raw.githubusercontent.com/oracle/oci-cli/master/scripts/install/install.sh)"

     When I was writing the expiry calculator gem (extracted from a license management system), the library’s main logic has some sort of integration with ActiveRecord, and I needed to verify that the easy way.

     Mocking the built-in active record connection pool and tables mapping showed to be cumbersome and may not ideally allow to validate the intended behaviour. Luckily, I found pieces in SO and Github to do the unit testing in few simple steps, with on the fly db (Sqlite). I have put it together in the following guide, polished for Rspec with ad-hoc migration methods.

This post reviews four main virtualization options in short.

💡 VM technologies are essentially considered by people when addressing on-premise use cases or when building DR for data centers.

VMware Virtualization

• Started at (2003).

• Offers type-1 hypervisor that runs on bare-metal called ESXi with minimum disk image footprint (32MB), with resources, storage, and networking capabilities, and UI console (DCUI).

This post is a follow up on the previous one where I discussed the concept of infrastructure as code and Terraform. In this post, I will provide few useful notes I took while working on IaC projects, with examples to illustrate the techniques on two of the public providers (AWS / Oracle).

An interesting usecase I have encountered recently is establishing a secure path (bridge) between Traefik as ingress controller and its destination backends.

The post addresses traefik usage within Kubernetes, however it is applicable to other setups.