From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7145531540303249408 X-Gmail-Labels: Topic type: DISCUSSION Date: Thu, 22 Sep 2022 02:37:44 -0700 (PDT) From: vt To: isar-users Message-Id: <2891fd01-6d6f-402d-b50a-1c26b7411077n@googlegroups.com> In-Reply-To: <25602913.1r3eYUQgxm@home> References: <25602913.1r3eYUQgxm@home> Subject: Re: Questions upgrade mechanism and read-only file system MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_8130_1200035983.1663839464749" X-TUID: xRKuW8Js2s1r ------=_Part_8130_1200035983.1663839464749 Content-Type: multipart/alternative; boundary="----=_Part_8131_434446671.1663839464749" ------=_Part_8131_434446671.1663839464749 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Thanks Uladzimir. I will check it out. On Wednesday, 21 September, 2022 at 12:03:45 pm UTC+5:30 ub...@ilbers.de wrote: > In the email from Tuesday, 20 September 2022 21:31:46 +03 user vt wrote: > > > I am new to Isar (and embedded software development too). I have gone > > > through the documentation and have had some success running through the > > > samples, generating images and booting them in qemu and vmware. I still > > > have to dig deeper into how it all works, but overall I like the > > > layered/modular approach and the build performance. > > > > > > I am trying to figure out if it would fit our requirements which at a > high > > > level are: > > > > > > 1. Debian based OS for our intel based appliances. > > > 2. Preferably read-only file system to prevent accidental installation of > > > software and modifications. Configuration is modifiable and hence would > > > need to be read-write. > > > 3. Preferably atomic image based upgrades so that we can keep > > > OS+app+dependencies in sync. A failed upgrade should go back to the last > > > working version. > > > > > > What is the recommended upgrade mechanism for Isar? Are image based > > > upgrades possible? Where can I find samples or documentation regarding > this. > > > > > > Is read-only file system an option? Any pointers? > > > > > > Thanks in advance. > > > - venu > > Hello. > > You might want to look at swupdate that is implemented in 'isar-cip-core' > layer on top of Isar: > > https://gitlab.com/cip-project/cip-core/isar-cip-core > > It does what you've requested (read-only rootfs, image-based upgrade) and > provides some documentation. > > -- > > Uladzimir Bely > > ------=_Part_8131_434446671.1663839464749 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit Thanks Uladzimir. I will check it out.

On Wednesday, 21 September, 2022 at 12:03:45 pm UTC+5:30 ub...@ilbers.de wrote:

In the email from Tuesday, 20 September 2022 21:31:46 +03 user vt wrote:

> I am new to Isar (and embedded software development too). I have gone

> through the documentation and have had some success running through the

> samples, generating images and booting them in qemu and vmware. I still

> have to dig deeper into how it all works, but overall I like the

> layered/modular approach and the build performance.

>

> I am trying to figure out if it would fit our requirements which at a high

> level are:

>

> 1. Debian based OS for our intel based appliances.

> 2. Preferably read-only file system to prevent accidental installation of

> software and modifications. Configuration is modifiable and hence would

> need to be read-write.

> 3. Preferably atomic image based upgrades so that we can keep

> OS+app+dependencies in sync. A failed upgrade should go back to the last

> working version.

>

> What is the recommended upgrade mechanism for Isar? Are image based

> upgrades possible? Where can I find samples or documentation regarding this.

>

> Is read-only file system an option? Any pointers?

>

> Thanks in advance.

> - venu


Hello.


You might want to look at swupdate that is implemented in 'isar-cip-core' layer on top of Isar:

https://gitlab.com/cip-project/cip-core/isar-cip-core


It does what you've requested (read-only rootfs, image-based upgrade) and provides some documentation.


--

Uladzimir Bely


------=_Part_8131_434446671.1663839464749-- ------=_Part_8130_1200035983.1663839464749--