Release HassOS by pvizeli · Pull Request #5747 · home-assistant/home-assistant.io

pvizeli · 2018-07-10T20:47:37Z

Description:

Pull request in home-assistant (if applicable): home-assistant/home-assistant#

Checklist:

Branch: Fixes, changes and adjustments should be created against current. New documentation for platforms/components and features should go to next.
The documentation follow the standards.

arsaboo · 2018-07-10T20:55:16Z

+
+## {% linkable_title Migration %}
+
+The design of HassOS is diferent to ResinOS. That is the reason why we can't provide a OTA update from old too new System.


HassOS is fundamentally different from ResinOS, hence, we cannot provide a OTA update for you to update from Hass.io.

DubhAd · 2018-07-10T21:22:03Z

+og_image: /images/blog/2018-07-hassio-images/blogpost.png
+---
+
+After 4 month we are happy to announce our new images for Hass.io, based on HassOS.


After 4 months

DubhAd · 2018-07-10T21:22:48Z

+
+## {% linkable_title What is new %}
+
+We build HassOS on top of the [Buildroot] framework. The focus of the system is to be a very small and high efficent operating system to run Docker like a hypervisor. It have exactly that software installed is need to run a supervisor. We have the focus also on security, there are no default passwords and we use [AppArmor] to protect application and containers on HassOS.


high efficient doesn't read well, maybe highly efficient?

DubhAd · 2018-07-10T21:24:29Z

+
+## {% linkable_title What is new %}
+
+We build HassOS on top of the [Buildroot] framework. The focus of the system is to be a very small and high efficent operating system to run Docker like a hypervisor. It have exactly that software installed is need to run a supervisor. We have the focus also on security, there are no default passwords and we use [AppArmor] to protect application and containers on HassOS.


It have exactly that software installed is need to run a supervisor maybe instead It has only the software installed that is needed to run a supervisor

We have the focus also on security, maybe instead We have also focused on security,

protect application and containers -> protect the applications and containers

DubhAd · 2018-07-10T21:24:57Z

+We build HassOS on top of the [Buildroot] framework. The focus of the system is to be a very small and high efficent operating system to run Docker like a hypervisor. It have exactly that software installed is need to run a supervisor. We have the focus also on security, there are no default passwords and we use [AppArmor] to protect application and containers on HassOS.
+
+Key features:
+- Safe and Secure updating with [Rauc] over USB or internet (OTA)


Remove the capital from Secure => secure

DubhAd · 2018-07-10T21:25:45Z

+
+## {% linkable_title Migration %}
+
+The design of HassOS is diferent to ResinOS. That is the reason why we can't provide a OTA update from old too new System.


provide a OTA update from old too new System => provide an OTA update from from the old Hass.io to the new HassOS system?

DubhAd · 2018-07-10T21:26:07Z

+
+The design of HassOS is diferent to ResinOS. That is the reason why we can't provide a OTA update from old too new System.
+
+1. Make a snapshot of current system. You should remove the bluetooth add-on before, that is not need anymore.


that is not need anymore => as that is not needed anymore

DubhAd · 2018-07-10T21:26:31Z

+1. Make a snapshot of current system. You should remove the bluetooth add-on before, that is not need anymore.
+2. Download the latest [HassOS stable] version.
+3. Flash the images with [Etcher] to SD card.
+5. On Raspberry: if you modify the `config.txt`, you need applay this also on boot partition of HassOS, but __don't__ copy this file!


applay => apply

DubhAd · 2018-07-10T21:26:59Z

+2. Download the latest [HassOS stable] version.
+3. Flash the images with [Etcher] to SD card.
+5. On Raspberry: if you modify the `config.txt`, you need applay this also on boot partition of HassOS, but __don't__ copy this file!
+4. If you used custom network configuration or ssh development access, we can use a [USB stick]. You can simple copy the resin-sample into `network` folder on USB stick.


If you used custom network configuration or ssh development access, we can use a => If you used a custom network configuration or ssh development access, you can use a

DubhAd · 2018-07-10T21:27:27Z

+5. On Raspberry: if you modify the `config.txt`, you need applay this also on boot partition of HassOS, but __don't__ copy this file!
+4. If you used custom network configuration or ssh development access, we can use a [USB stick]. You can simple copy the resin-sample into `network` folder on USB stick.
+5. Take SD card into device slot and boot your system like before.
+6. Copy the snapshot into host with SSH or samba add-on.


Copy the snapshot into host => Copy the snapshot to the host

DubhAd · 2018-07-10T21:27:39Z

+4. If you used custom network configuration or ssh development access, we can use a [USB stick]. You can simple copy the resin-sample into `network` folder on USB stick.
+5. Take SD card into device slot and boot your system like before.
+6. Copy the snapshot into host with SSH or samba add-on.
+7. Restore it over the Hass.io panel


Restore it over the => Restore it using the

DubhAd · 2018-07-10T21:28:25Z

+2. Download the latest [HassOS stable] version.
+3. Flash the images with [Etcher] to SD card.
+5. On Raspberry: if you modify the `config.txt`, you need apply this also on boot partition of HassOS, but __don't__ copy this file!
+4. If you used custom network configuration or ssh development access, we can use a [USB stick]. You can simple copy the resin-sample into `network` folder on USB stick.


If you used custom network configuration or ssh development access, we can => If you used a custom network configuration, or SSH development access, you can

DubhAd · 2018-07-10T21:29:01Z

+2. Download the latest [HassOS stable] version.
+3. Flash the images with [Etcher] to SD card.
+5. On Raspberry: if you modify the `config.txt`, you need apply this also on boot partition of HassOS, but __don't__ copy this file!
+4. If you used custom network configuration or ssh development access, we can use a [USB stick]. You can simple copy the resin-sample into `network` folder on USB stick.


sample into network folder on USB stick => sample into the network folder on the USB stick

DubhAd · 2018-07-10T21:29:30Z

+3. Flash the images with [Etcher] to SD card.
+5. On Raspberry: if you modify the `config.txt`, you need apply this also on boot partition of HassOS, but __don't__ copy this file!
+4. If you used custom network configuration or ssh development access, we can use a [USB stick]. You can simple copy the resin-sample into `network` folder on USB stick.
+5. Take SD card into device slot and boot your system like before.


Take SD card into device slot => Put the SD card into the device slot

DubhAd · 2018-07-10T21:29:53Z

+5. On Raspberry: if you modify the `config.txt`, you need apply this also on boot partition of HassOS, but __don't__ copy this file!
+4. If you used custom network configuration or ssh development access, we can use a [USB stick]. You can simple copy the resin-sample into `network` folder on USB stick.
+5. Take SD card into device slot and boot your system like before.
+6. Copy the snapshot into host with SSH or samba add-on.


Copy the snapshot into host with => Copy the snapshot to the host with the

DubhAd · 2018-07-10T21:30:07Z

+4. If you used custom network configuration or ssh development access, we can use a [USB stick]. You can simple copy the resin-sample into `network` folder on USB stick.
+5. Take SD card into device slot and boot your system like before.
+6. Copy the snapshot into host with SSH or samba add-on.
+7. Restore it over the Hass.io panel


Restore it over the => Restore it using the

balloob · 2018-07-11T10:23:37Z

+
+You need to perform the following steps to upgrade:
+
+1. If you have installed the Bluetooth add-on, please remove it, since it is not required anymore.


What happens if they keep it enabled, will the snapshot be able to be restored?

The end of the world?

No sure, I'll guess it simply doesn't work, but still will boot. So removing it afterward?
@pvizeli Could you confirm?

balloob · 2018-07-11T10:27:11Z

+
+## {% linkable_title What is new %}
+
+We have build HassOS on top of the [Buildroot] framework. The focus of the system is to be a very small and high efficient operating system to run Docker like a hypervisor. It has installed just enough software to run a supervisor. We have also focussed on security, there are, for example, no default passwords and we use [AppArmor] to protect the applications and containers on HassOS.


balloob · 2018-07-11T10:27:17Z

+og_image: /images/blog/2018-07-hassio-images/blogpost.png
+---
+
+After 4 months we are happy to announce our new images for Hass.io, based on HassOS.


Add some more text:

HassOS is a brand new operating system that we have created specifically for the purpose to run Hass.io.

balloob · 2018-07-11T10:27:26Z

+
+After 4 months we are happy to announce our new images for Hass.io, based on HassOS.
+
+Note that the descriptions of the new system can get quite technical. Feel free to jump to the [migration steps].


Let's remove this paragraph.

Agreed. ✔️

balloob · 2018-07-11T10:27:42Z

+
+## {% linkable_title What is new %}
+
+We have build HassOS on top of the [Buildroot] framework. The focus of the system is to be a very small and high efficient operating system to run Docker like a hypervisor. It has installed just enough software to run a supervisor. We have also focussed on security, there are, for example, no default passwords and we use [AppArmor] to protect the applications and containers on HassOS.


just enough software installed

balloob · 2018-07-11T10:28:20Z

+
+## {% linkable_title Migration %}
+
+The design of HassOS is different from ResinOS. Because of this, we can't provide an OTA update from the old (ResinOS) too new system (HassOS).


we can't provide an OTA update from the old ResinOS system to the new HassOS based system.

MartinHjelmare · 2018-07-11T12:23:44Z

+- Latest Docker-ce version
+- Fully supported NetworkManager
+- Bluetooth support using Bluez
+- Supports lots different hardware


lots of different

MartinHjelmare · 2018-07-11T12:25:39Z

+3. Download the latest [Hass.io stable][installation] version.
+4. Flash the downloaded Hass.io image with [Etcher] to your SD card.
+5. Raspberry Pi: In case you have modified the `config.txt` (in the boot partition), you will also need to apply these changes to HassOS. Do **NOT** simply copy the file from your old setup into HassOS! Apply those changes manually!
+6. If you use a custom network configuration or have configured SSH development access, you need to create a configuration [USB stick]. Copy the resin-sample into `network` folder on a USB stick and insert it into your device.


Copy the resin-sample into the network folder

balloob · 2018-07-11T13:37:54Z

+og_image: /images/blog/2018-07-hassio-images/blogpost.png
+---
+
+After 4 months of hard work, we are happy to announce our new images for Hass.io, based on HassOS. HassOS is a brand new operating system that we have created specifically for the purpose of running Hass.io.


Let's add one more sentence: And yes, this supports the Raspberry Pi 3 B+!

frenck · 2018-07-11T17:54:25Z

@pvizeli Thanks for all your hard work!

Release HassOS

261b870

homeassistant added the cla-signed label Jul 10, 2018

ghost assigned pvizeli Jul 10, 2018

ghost added the ready-for-review This PR needs to be reviewed label Jul 10, 2018

Update 2018-07-11-hassio-images.markdown

f7d4c8a

homeassistant added the cla-signed label Jul 10, 2018

arsaboo reviewed Jul 10, 2018

View reviewed changes

Update 2018-07-11-hassio-images.markdown

2018ee2

home-assistant deleted a comment from arsaboo Jul 10, 2018

DubhAd reviewed Jul 10, 2018

View reviewed changes

Update 2018-07-11-hassio-images.markdown

8648c01

homeassistant added the cla-signed label Jul 10, 2018

DubhAd reviewed Jul 10, 2018

View reviewed changes

Update index.markdown

7119781

DubhAd reviewed Jul 10, 2018

View reviewed changes

frenck added the blog This PR adds a blog article to the Home Assistant website label Jul 10, 2018

balloob reviewed Jul 11, 2018

View reviewed changes

✏️ Blog post tweaks

a0cfc7c

balloob reviewed Jul 11, 2018

View reviewed changes

frenck and others added 8 commits July 11, 2018 12:33

✏️ Getting started index tweaks

1e3c2db

✏️ Tweaks to Hassio index

1d862fd

✏️ Tweaks to Hassio installation guide

08ca319

✏️ Processes review feedback

d4a3f16

✏️ Updates title & description.

fb1abdc

✏️ Processed review

1179e18

Redundant information

23277d0

Merge branch 'current' into hassos

994367f

MartinHjelmare reviewed Jul 11, 2018

View reviewed changes

balloob reviewed Jul 11, 2018

View reviewed changes

pvizeli added 7 commits July 11, 2018 19:03

Update 2018-07-11-hassio-images.markdown

fb7b275

Update 2018-07-11-hassio-images.markdown

d795e6e

Add files via upload

c9865e4

Delete blogpost.png

3b106e7

Create TEST.TXT

3874049

Add files via upload

9169acd

Delete TEST.TXT

53e8482

pvizeli changed the title ~~WIP: Release HassOS~~ Release HassOS Jul 11, 2018

frenck approved these changes Jul 11, 2018

View reviewed changes

pvizeli merged commit b0a1e16 into current Jul 11, 2018

ghost removed the ready-for-review This PR needs to be reviewed label Jul 11, 2018

pvizeli deleted the hassos branch July 11, 2018 17:51


		## {% linkable_title Migration %}

		The design of HassOS is diferent to ResinOS. That is the reason why we can't provide a OTA update from old too new System.


		## {% linkable_title What is new %}

		We build HassOS on top of the [Buildroot] framework. The focus of the system is to be a very small and high efficent operating system to run Docker like a hypervisor. It have exactly that software installed is need to run a supervisor. We have the focus also on security, there are no default passwords and we use [AppArmor] to protect application and containers on HassOS.


		The design of HassOS is diferent to ResinOS. That is the reason why we can't provide a OTA update from old too new System.

		1. Make a snapshot of current system. You should remove the bluetooth add-on before, that is not need anymore.


		You need to perform the following steps to upgrade:

		1. If you have installed the Bluetooth add-on, please remove it, since it is not required anymore.


		## {% linkable_title What is new %}

		We have build HassOS on top of the [Buildroot] framework. The focus of the system is to be a very small and high efficient operating system to run Docker like a hypervisor. It has installed just enough software to run a supervisor. We have also focussed on security, there are, for example, no default passwords and we use [AppArmor] to protect the applications and containers on HassOS.


		After 4 months we are happy to announce our new images for Hass.io, based on HassOS.

		Note that the descriptions of the new system can get quite technical. Feel free to jump to the [migration steps].


		## {% linkable_title Migration %}

		The design of HassOS is different from ResinOS. Because of this, we can't provide an OTA update from the old (ResinOS) too new system (HassOS).

Uh oh!

Conversation

pvizeli commented Jul 10, 2018

Checklist:

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

balloob Jul 11, 2018 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

frenck commented Jul 11, 2018

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

balloob Jul 11, 2018 •

edited

Loading