Skip to content

Commit

Permalink
Correct Azure deployment guide
Browse files Browse the repository at this point in the history
  • Loading branch information
@olljanat
olljanat committed Mar 8, 2024
1 parent 58fc346 commit c42fa2c
Show file tree
Hide file tree
Showing 2 changed files with 37 additions and 31 deletions.
50 changes: 26 additions & 24 deletions content/docs/installation/cloud/azure.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,32 +2,32 @@
bookToc: false
---
# Azure
Because BurmillaOS community is small we do not publish images in Azure. However, you can still use old RancherOS image and simply [upgrade to BurmillaOS](/docs/installation/upgrading/)

BurmillaOS has been published in Azure Marketplace, you can get it from [here](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/rancher.burmillaos).
## Launching RancherOS through the Azure Portal
RancherOS has been published in Azure Marketplace, you can get it from [here](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/rancher.rancheros).

## Launching BurmillaOS through the Azure Portal

Using the new Azure Resource Management portal, click on **Marketplace**. Search for **BurmillaOS**. Click on **Create**.
Using the new Azure Resource Management portal, click on **Marketplace**. Search for **RancherOS**. Click on **Create**.

Follow the steps to create a virtual machine.

In the _Basics_ step, provide a **name** for the VM, use _burmilla_ as the **user name** and select the **SSH public key** option of authenticating. Add your ssh public key into the appropriate field. Select the **Resource group** that you want to add the VM to or create a new one. Select the **location** for your VM.
In the _Basics_ step, provide a **name** for the VM, use _rancher_ as the **user name** and select the **SSH public key** option of authenticating. Add your ssh public key into the appropriate field. Select the **Resource group** that you want to add the VM to or create a new one. Select the **location** for your VM.

In the _Size_ step, select a virtual machine that has at least **1GB** of memory.

In the _Settings_ step, you can use all the default settings to get BurmillaOS running.
In the _Settings_ step, you can use all the default settings to get RancherOS running.

Review your VM and buy it so that you can **Create** your VM.

After the VM has been provisioned, click on the VM to find the public IP address. SSH into your VM using the _burmilla_ username.
After the VM has been provisioned, click on the VM to find the public IP address. SSH into your VM using the _rancher_ username.

```
$ ssh burmilla@<public_ip_of_vm> -p 22
$ ssh rancher@<public_ip_of_vm> -p 22
```

## Launching BurmillaOS with custom data
## Launching RancherOS with custom data

_Available as of RancherOS v1.5.2_
_Available as of RancherOS v1.5.4_

Instance Metadata Service provides the ability for the VM to have access to its custom data. The binary data must be less than 64 KB and is provided to the VM in base64 encoded form.
You can get more details from [here](https://docs.microsoft.com/en-us/azure/virtual-machines/linux/instance-metadata-service#custom-data)
Expand All @@ -36,27 +36,29 @@ For example, you can add custom data through [CLI](https://docs.microsoft.com/en

```bash
# list images from marketplace
az vm image list --location westus --publisher Rancher --offer burmillaos --sku os --all --output table

Offer Publisher Sku Urn Version
--------- ----------- ----- ----------------------------- ---------
burmillaos burmilla os burmilla:burmillaos:os:1.5.1 1.5.1
burmillaos burmilla os152 burmilla:burmillaos:os152:1.5.2 1.5.2
az vm image list --location westus --publisher Rancher --offer rancheros --sku os --all --output table

Architecture Offer Publisher Sku Urn Version
-------------- --------- ----------- ----- ----------------------------- ---------
x64 rancheros rancher os rancher:rancheros:os:1.5.1 1.5.1
x64 rancheros rancher os152 rancher:rancheros:os152:1.5.2 1.5.2
x64 rancheros rancher os153 rancher:rancheros:os153:1.5.3 1.5.3
x64 rancheros rancher os154 rancher:rancheros:os154:1.5.4 1.5.4
...

# accept the terms
az vm image accept-terms --urn burmilla:burmillaos:os152:1.5.2
az vm image accept-terms --urn rancher:rancheros:os154:1.5.4

# create the vm
AZURE_ROS_SSH_PUBLIC_KEY="xxxxxx"
az vm create --resource-group mygroup \
--name myvm \
--image burmilla:burmillaos:os152:1.5.2 \
--image rancher:rancheros:os154:1.5.4 \
--plan-name os152 \
--plan-product burmillaos \
--plan-publisher burmilla \
--plan-product rancheros \
--plan-publisher rancher \
--custom-data ./custom_data.txt \
--admin-username burmilla \
--admin-username rancher \
--size Standard_A1 \
--ssh-key-value "$AZURE_ROS_SSH_PUBLIC_KEY"
```
Expand All @@ -66,11 +68,11 @@ The `custom_data.txt` can be the cloud-config format or a shell script, such as:
```yaml
#cloud-config
runcmd:
- [ touch, /home/burmilla/test1 ]
- echo "test" > /home/burmilla/test2
- [ touch, /home/rancher/test1 ]
- echo "test" > /home/rancher/test2
```
```
#!/bin/sh
echo "aaa" > /home/burmilla/aaa.txt
echo "aaa" > /home/rancher/aaa.txt
```
18 changes: 11 additions & 7 deletions content/docs/installation/upgrading.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,12 @@ Permanently upgrade your existing RancherOS installation to BurmillaOS and begin
$ sudo ros config set rancher.upgrade.url \
https://raw.githubusercontent.com/burmilla/releases/v2.0.x/releases.yml
$ sudo ros os upgrade
```
After reboot run also:
```bash
$ sudo ros console switch default
```
other why you are still using console from RancherOS (visible in `sudo system-docker ps` output)

## Version Control

Expand Down Expand Up @@ -71,7 +75,7 @@ After rebooting, you can check that your version has been updated.

```bash
$ sudo ros -v
ros version v0.5.0
version v2.0.0 from os image burmilla/os:v2.0.0
```

> **Note:** If you are booting from ISO and have not installed to disk, your upgrade will not be saved. You can view our guide to [installing to disk](/docs/installation/server/install-to-disk).
Expand All @@ -81,8 +85,8 @@ ros version v0.5.0
If you are a couple of versions behind the current version, use the `-i` option to pick the version that you want to upgrade to.

```bash
$ sudo ros os upgrade -i burmilla/os:v0.5.0
Upgrading to burmilla/os:v0.5.0
$ sudo ros os upgrade -i burmilla/os:v2.0.0
Upgrading to burmilla/os:v2.0.0
Continue [y/N]: y
...
...
Expand All @@ -105,9 +109,9 @@ The `ros os upgrade` command works for rolling back. We'll use the `-i` option t

```bash
$ sudo ros -v
ros version v0.4.5
$ sudo ros os upgrade -i burmilla/os:v0.4.4
Upgrading to burmilla/os:v0.4.4
ros version v1.9.0
$ sudo ros os upgrade -i burmilla/os:v2.0.0
Upgrading to burmilla/os:v2.0.0
Continue [y/N]: y
...
...
Expand All @@ -119,7 +123,7 @@ After rebooting, the rollback will be complete.

```bash
$ sudo ros -v
ros version 0.4.4
version v2.0.0 from os image burmilla/os:v2.0.0
```

<br>
Expand Down

0 comments on commit c42fa2c

Please sign in to comment.