Skip to content

Commit

Permalink
Update releases page, update references to v2.0.0
Browse files Browse the repository at this point in the history
  • Loading branch information
olljanat committed Mar 8, 2024
1 parent 9d9128e commit 58fc346
Show file tree
Hide file tree
Showing 8 changed files with 38 additions and 44 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ Please file issues with the documentation at: https://github.com/burmilla/os/iss

License
=======
Copyright (c) 2020 Project Burmilla
Copyright (c) 2020-2024 [BurmillaOS community](https://burmillaos.org)

Copyright (c) 2014-2020 [Rancher Labs, Inc.](http://rancher.com)

Expand Down
2 changes: 1 addition & 1 deletion content/docs/additional-resources/recovery-console.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ In order to demonstrate how to use the recovery console, we choose a scene that

| Term | Definition |
|-----------------------|--------------------------------------------------|
| BurmillaOS | v1.9.0 |
| BurmillaOS | v2.0.0 |
| Platform | Virtualbox |
| Root Disk | 2GB |
| CPU | 1C |
Expand Down
2 changes: 1 addition & 1 deletion content/docs/installation/cloud/amazon-ecs.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ rancher:
environment:
ECS_CLUSTER: your-ecs-cluster-name
# Note: You will need to make sure to include the colon in front of the version.
ECS_AGENT_VERSION: :v1.9.0
ECS_AGENT_VERSION: :v2.0.0
# If you have selected a BurmillaOS AMI that does not have ECS enabled by default,
# you'll need to enable the system service for the ECS agent.
services_include:
Expand Down
12 changes: 6 additions & 6 deletions content/docs/installation/server/install-to-disk.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ Now that our `cloud-config.yml` contains our public SSH key, we can move on to i
```bash
$ sudo ros install -c cloud-config.yml -d /dev/sda
INFO[0000] No install type specified...defaulting to generic
Installing from burmilla/os:v1.9.0
Installing from burmilla/os:v2.0.0
Continue [y/N]:
```

Expand All @@ -44,12 +44,12 @@ $ sudo ros install -c https://link/to/cloud-config.yml
You will be prompted to see if you want to continue. Type **y**.

```bash
Unable to find image 'burmilla/os:v1.9.0' locally
v1.9.0: Pulling from burmilla/os
Unable to find image 'burmilla/os:v2.0.0' locally
v2.0.0: Pulling from burmilla/os
...
...
...
Status: Downloaded newer image for burmilla/os:v1.9.0
Status: Downloaded newer image for burmilla/os:v2.0.0
+ DEVICE=/dev/sda
...
...
Expand All @@ -62,13 +62,13 @@ After installing BurmillaOS to disk, you will no longer be automatically logged

### Installing a Different Version

By default, `ros install` uses the same installer image version as the ISO it is run from. The `-i` option specifies the particular image to install from. To keep the ISO as small as possible, the installer image is downloaded from DockerHub and used in System Docker. For example for BurmillaOS v1.9.0 the default installer image would be `burmilla/os:v1.9.0`.
By default, `ros install` uses the same installer image version as the ISO it is run from. The `-i` option specifies the particular image to install from. To keep the ISO as small as possible, the installer image is downloaded from DockerHub and used in System Docker. For example for BurmillaOS v2.0.0 the default installer image would be `burmilla/os:v2.0.0`.

You can use `ros os list` command to find the list of available BurmillaOS images/versions.

```bash
$ sudo ros os list
burmilla/os:v1.9.0 local
burmilla/os:v2.0.0 local
```

Alternatively, you can set the installer image to any image in System Docker to install BurmillaOS. This is particularly useful for machines that will not have direct access to the internet.
Expand Down
14 changes: 7 additions & 7 deletions content/docs/installation/upgrading.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Permanently upgrade your existing RancherOS installation to BurmillaOS and begin

```bash
$ sudo ros config set rancher.upgrade.url \
https://raw.githubusercontent.com/burmilla/releases/v1.9.x/releases.yml
https://raw.githubusercontent.com/burmilla/releases/v2.0.x/releases.yml
$ sudo ros os upgrade
$ sudo ros console switch default
```
Expand All @@ -29,16 +29,16 @@ First, let's check what version you have running on your system.

```bash
$ sudo ros os version
v1.9.0
v2.0.0
```

If you just want to find out the available releases from the command line, it's a simple command.

```bash
# List all available releases
$ sudo ros os list
burmilla/os:v1.9.0 local latest running
burmilla/os:v1.9.0-rc1 remote available
burmilla/os:v2.0.0 local latest running
burmilla/os:v2.0.0 remote available
```

The `local`/`remote` label shows which images are available to System Docker locally versus which need to be pulled from Docker Hub. If you choose to upgrade to a version that is remote, we will automatically pull that image during the upgrade.
Expand All @@ -49,7 +49,7 @@ Let's walk through upgrading! The `ros os upgrade` command will automatically up

```bash
$ sudo ros os upgrade
Upgrading to burmilla/os:v1.9.0
Upgrading to burmilla/os:v2.0.0
```

Confirm that you want to continue and the final step will be to confirm that you want to reboot.
Expand All @@ -65,7 +65,7 @@ INFO[0037] Rebooting

> **Note:** The default console container is persistent and will NOT be updated by default. Use `ros console switch default` to update the `os-console` container. This is a destructive operation - see [console persistence](/docs/installation/custom-builds/custom-console/#console-persistence) for info about what will be retained.
> **Note:** To make the default container non-persistent, set `io.docker.compose.rebuild: "always"` on the console container [os-config.tpl](https://github.com/burmilla/os/blob/v1.9.6/os-config.tpl.yml#L246)
> **Note:** To make the default container non-persistent, set `io.docker.compose.rebuild: "always"` on the console container [os-config.tpl](https://github.com/burmilla/os/blob/v2.0.0/os-config.tpl.yml#L246)
After rebooting, you can check that your version has been updated.

Expand Down Expand Up @@ -131,7 +131,7 @@ ros version 0.4.4
During an upgrade, the template of the upgrade is downloaded from the burmilla/os repository. You can download this template ahead of time so that it's saved locally. This will decrease the time it takes to upgrade. We'll use the `-s` option to stage the specific template. You will need to specify the image name with the `-i` option, otherwise it will automatically stage the current version.

```bash
$ sudo ros os upgrade -s -i burmilla/os:v1.9.0
$ sudo ros os upgrade -s -i burmilla/os:v2.0.0
```

### Custom Upgrade Sources
Expand Down
10 changes: 5 additions & 5 deletions content/docs/installation/workstation/docker-machine.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,11 @@ Get the latest ISO artifact from the BurmillaOS [releases](https://github.com/bu

Machine Driver | Recommended BurmillaOS version | ISO File
-------------- | ----------------------------- | -------------------------------------------------------------
VirtualBox | >=v1.9.0 | burmillaos.iso
VMWare VSphere | >=v1.9.0 | burmillaos-autoformat.iso
VMWare Fusion | >=v1.9.0 | burmillaos-autoformat.iso
Hyper-V | >=v1.9.0 | burmillaos.iso
Proxmox VE | >=v1.9.0 | burmillaos-autoformat.iso
VirtualBox | >=v2.0.0 | burmillaos.iso
VMWare VSphere | >=v2.0.0 | burmillaos-autoformat.iso
VMWare Fusion | >=v2.0.0 | burmillaos-autoformat.iso
Hyper-V | >=v2.0.0 | burmillaos.iso
Proxmox VE | >=v2.0.0 | burmillaos-autoformat.iso

## Docker Machine

Expand Down
14 changes: 7 additions & 7 deletions content/docs/quick-start-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,13 +38,13 @@ When you first launch BurmillaOS, there are no containers running in the Docker
$ sudo system-docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
07135915b03a burmilla/os-docker:19.03.13 "ros user-docker" 15 hours ago Up 15 hours docker
896c6169c2d5 burmilla/os-console:v1.9.0 "/usr/bin/ros entr..." 41 hours ago Up 24 hours console
74e57e5940de burmilla/os-base:v1.9.0 "/usr/bin/ros entr..." 41 hours ago Up 24 hours ntp
989e8f137fb7 burmilla/os-base:v1.9.0 "/usr/bin/ros entr..." 41 hours ago Up 24 hours network
79b750fa577a burmilla/os-base:v1.9.0 "/usr/bin/ros entr..." 41 hours ago Up 24 hours udev
896c6169c2d5 burmilla/os-console:v2.0.0 "/usr/bin/ros entr..." 41 hours ago Up 24 hours console
74e57e5940de burmilla/os-base:v2.0.0 "/usr/bin/ros entr..." 41 hours ago Up 24 hours ntp
989e8f137fb7 burmilla/os-base:v2.0.0 "/usr/bin/ros entr..." 41 hours ago Up 24 hours network
79b750fa577a burmilla/os-base:v2.0.0 "/usr/bin/ros entr..." 41 hours ago Up 24 hours udev
29c582619c67 burmilla/container-crontab:v0.5.0 "container-crontab" 41 hours ago Up 24 hours system-cron
cdd49fa26ecb burmilla/os-syslog:v1.9.0 "/usr/bin/entrypoi..." 41 hours ago Up 24 hours syslog
e490108ce8da burmilla/os-acpid:v1.9.0 "/usr/bin/ros entr..." 41 hours ago Up 24 hours acpid
cdd49fa26ecb burmilla/os-syslog:v2.0.0 "/usr/bin/entrypoi..." 41 hours ago Up 24 hours syslog
e490108ce8da burmilla/os-acpid:v2.0.0 "/usr/bin/ros entr..." 41 hours ago Up 24 hours acpid
```

Some containers are run at boot time, and others, such as the `console`, `docker`, etc. containers are always running.
Expand Down Expand Up @@ -110,7 +110,7 @@ Another useful command that can be used with BurmillaOS is `ros` which can be us

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

BurmillaOS state is controlled by a cloud config file. `ros` is used to edit the configuration of the system, to see for example the dns configuration of the system:
Expand Down
26 changes: 10 additions & 16 deletions content/docs/releases.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,24 +8,18 @@ weight: 12
The following is a list of the versions of the operating system in their different branches:

#### Stable
- [v2.0.0](https://github.com/burmilla/os/releases/tag/v2.0.0) | 2024-03-05

- [v1.9.6](https://github.com/burmilla/os/releases/tag/v1.9.6) | 2023.01.02
- [v1.9.5](https://github.com/burmilla/os/releases/tag/v1.9.5) | 2022.09.15
- [v1.9.3](https://github.com/burmilla/os/releases/tag/v1.9.3) | 2021.10.12
- [v1.9.2](https://github.com/burmilla/os/releases/tag/v1.9.2) | 2021.08.04
- [v1.9.1](https://github.com/burmilla/os/releases/tag/v1.9.1) | 2021.02.02
- [v1.9.0](https://github.com/burmilla/os/releases/tag/v1.9.0) | 2020.12.14
#### Old stable
- [v1.9.7-rc1](https://github.com/burmilla/os/releases/tag/v1.9.7-rc1) | 2023-02-01
- [v1.9.6](https://github.com/burmilla/os/releases/tag/v1.9.6) | 2023-01-02

#### Testing

- [v2.0.0-beta6](https://github.com/burmilla/os/releases/tag/v2.0.0-beta6) | 2023.01.26
- [v2.0.0-beta5](https://github.com/burmilla/os/releases/tag/v2.0.0-beta5) | 2022.07.25
- [v2.0.0-beta4](https://github.com/burmilla/os/releases/tag/v2.0.0-beta4) | 2021.04.12

#### Archived

- [v1.9.2-rc3](https://github.com/burmilla/os/releases/tag/v1.9.2-rc3) | 2021.05.09
- [v2.0.0-beta3](https://github.com/burmilla/os/releases/tag/v2.0.0-beta3) | 2021.01.24
- [v1.9.1-rc1](https://github.com/burmilla/os/releases/tag/v1.9.1-rc1) | 2021.01.07
- [v1.9.0-rc1](https://github.com/burmilla/os/releases/tag/v1.9.0-rc1) | 2020.11.23
- [v2.0.0-beta2](https://github.com/burmilla/os/releases/tag/v2.0.0-beta2) | 2020.11.19
- [v1.9.5](https://github.com/burmilla/os/releases/tag/v1.9.5) | 2022-09-15
- [v1.9.4](https://github.com/burmilla/os/releases/tag/v1.9.4) | 2022-03-10
- [v1.9.3](https://github.com/burmilla/os/releases/tag/v1.9.3) | 2021-10-12
- [v1.9.2](https://github.com/burmilla/os/releases/tag/v1.9.2) | 2021-08-04
- [v1.9.1](https://github.com/burmilla/os/releases/tag/v1.9.1) | 2021-02-02
- [v1.9.0](https://github.com/burmilla/os/releases/tag/v1.9.0) | 2020-12-14

0 comments on commit 58fc346

Please sign in to comment.