Cloud Infrastructure

Resetting Cloud Shell

I’ve been using Cloud Shell a lot recently and found it very useful for many use cases. Preinstalled and preauthenticated cloud tools (OCI CLI, terraform, kubectl…), programming languages and simply its immediate availability at any time are great for occasional or not so occasional use!

The user directory is persistent as far as you log in at least once every 6 months – and this is great, but what if I want to get a clean brand new Cloud Shell like it was on the very first connection?

I prepare and conduct lots of training sessions, workshops and seminars where it can be useful to start from a clean slate to be sure I’m not relying on something that isn’t available to a regular new user – maybe I’ve installed some binary in the past or modified something, and my workshop is only “working” for me but not for everybody else?

The answer to this question is a little utility delivered in the Cloud Shell and called csreset.

Cloud Infrastructure

OCI Cloud Shell announcement

Have you seen this – OCI now has its own Cloud Shell – a Linux shell in the browser!

More in this announcement:

I’m preparing a small article about the Cloud Shell, stay connected 🙂

Cloud Infrastructure Hybrid Multicloud

Deploying K3S on Oracle Cloud Infrastructure – part 1

“Installing your own Kubernetes is hard!”


“Hold my kubectl!”


Who is this article for:

This is written for those of us who’s interested by Kubernetes and would like to install and run it easily and cheaply anywhere. You may already know that installing and running a “full” Kubernetes all by yourself can be rather difficult, the learning curve is really steep.

There are many alternatives out there – one of the solutions to the complexity is subscribing to one of the managed Kubernetes offerings in the cloud, for example Oracle OKE. Rancher Labs came up with another interesting solution, modifying and considerably slimming down a standard distribution.

K3S is a lightweight Kubernetes distribution made by Rancher Labs, targeted to edge computing, IoT devices and ephemeral infrastructure deployments (for example created in CI/CD pipelines). It can run on Intel and ARM processors.

I would say it’s a great case for learning and development environments too. It even runs on Raspberry Pi! Should you run your critical production workloads in k3s? Not sure this is a good idea, Rancher certainly doesn’t position it like that.

In this article I’m going to describe the installation steps needed to install K3S on OCI in an Oracle Linux VM, but pretty much any cloud or local install will be very similar. Was it as easy as advertised? Keep reading 🙂

Cloud Infrastructure

Administering OCI from WSL

Who is this article for:

This is written for those of us who use Windows as their primary workstation but also like to have Linux readily available to them. I describe a minimal setup I recommend for OCI administration purposes.


While it’s almost always possible to develop or administer cloud infrastructure from Windows using its native command line or Powershell, most examples you’ll find out there on internet will be written with Linux or MacOS in mind. Especially when we’re talking about open source software! There are situations when you’ll be better served, spend less time tinkering or have better support if you’re able to use Linux.
The fact is, knowing Linux today is pretty much an unavoidable necessity for a Cloud Architect, even if you were using Windows exclusively before and today are working with nothing but Azure!

As a Windows user, in the past you had to jump through few hoops to get access to Linux shell.

Before Windows 10, the options for running Linux locally on a Windows machine were the following:

  • Dual-boot between Windows and Linux (gah!)
  • Run Cygwin (collection of POSIX-compatible tools that offer a Linux-like environment).
  • Run Git Bash that includes a collection of Linux tools compiled to work on Windows. As most of us have Git for Windows installed anyway, the Git Bash will be already there in most cases.
  • Run a full Linux VM in Virtualbox, VMWare Workstation player or Hyper-V

All of them have their merits and are more or less compatible, easy to use or resource-heavy.
Since Windows 10, Microsoft introduced another more “native” way, the WSL:

Cloud Infrastructure

OCI: Receive notification when your instance is down

Absolutely everybody:

– I would like to be notified when my instances go down, please? (≧︿≦)

This is one of the most common questions I’ve heard, so let’s see what’s required to put such notifications in place in Oracle Cloud Infrastructure (OCI).

0. What are the prerequisites?

  • Quite obviously, a subscription to OCI. If you don’t have it yet, please go and grab one – you’ll have access to $300 you can spend on any IaaS or PaaS service during one month, but when this month (or credits) expire, you will still have access to “always free” resources. More details here:
    Everything described here will work with always free subscription, none of the services used require upgrading to a paid subscription.
  • You already have basic knowledge of OCI – you know how to navigate the OCI console and create and run instances.
  • Rights to “Manage” the Notifications Service and rights to “Use” the OCI Metrics. If you are the tenancy admin, then you already have those; if you aren’t – more on this later in the article.
  • Bare metal or Virtual instances which state you’re going to track. The instances should have the metrics enabled.
  • A valid email address to receive the notifications.

TLDR: We will send notifications when the instance stops producing metrics. This is typically true in 3 cases: 1) when the instance is stopped; 2) when it crashed or its network connection was severed for some reason; 3) when the metrics agent stopped working.