[Starlingx-discuss] How to update an installed image

Thu Apr 25 13:44:25 UTC 2019

The software update/patching framework, as Bart notes, provides a controlled mechanism for system software updates (such as delivery of CVE fixes), bundling updated packages for user management of published fixes and enhancements. In general, this is a post-release mechanism, but can also be used by designers as part of their development in applying or removing controlled updates to a running system. For formal patches, there are considerations around patch removal, interoperability between nodes, config changes, etc.

The upgrade framework provides for migration from one release to the next, supporting database migrations, config changes, etc, and is not for moving between weekly or nightly development builds.

The only recommended and supported approach for migrating to a new nightly development build is a reinstallation. While some merged development changes may be patchable to a running system, there is no guarantee all updates will be  (ex: api changes, db schema changes).

We will get wikis published describing the software update/patching framework and build tools shortly.

Cheers,
Don.

-----Original Message-----
From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] 
Sent: Wednesday, April 24, 2019 11:45 AM
To: Saul Wold
Cc: starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] How to update an installed image

On Wed, Apr 24, 2019 at 10:05 AM Saul Wold <sgw at linux.intel.com> wrote:
>
>
>
> On 4/24/19 5:50 AM, Wensley, Barton wrote:
> > Victor,
> >
> > StarlingX has two mechanisms for updating software on a running system:
> > - updates (also known as patching): This allows the user to build an updated version of a set of RPMs, bundle them into a patch file and apply them to a running system. We are also working on an update mechanism for containerized applications, which will allow new versions the docker images for an application to be deployed to a running system.
> Is this process being used to build patches between the daily/weekly
> builds? Can we even patch between these?  If I understand this uses the
> "smart" package manager, or is that for the upgrade process?
>
> I understand that there is not yet a process for updating the
> containers, is there a specification being worked on for describing how
> the containerized applications will be updated?
>
> Sau!
> > - upgrades: This allows the user to upgrade a running system from one StarlingX release to the next, including the OS, RPMs and applications. This mechanism will only be supported when moving between StarlingX releases - any fixes delivered to an existing release will use the update mechanism.
> >
> > The update mechanism would be used to deliver a CVE fix (as per your example) to a running system.
> >
> > Bart
> >

Thanks a lot, Bart, following Saul question, is there any place where
I can get documentation about it.

The actual problem that I have is that I have a dedicated HW for
measuring the footprint of the STX image ( described in the
performance presentation I gave 2 weeks ago ) but I really don't want
to reinstall the ISO every time there is a new ISO released in CEGN
that I have to measure and send the results to my personal DB to track
any degradation. Curtis and I have the AR to make it work on packet
infra , Curtis has been working very hard to make the packet infra, I
am in charge fo the test suite. But I had the roadblock of asking
myself, do I have to reinstall the ISO every time. I am glad that you
clarify me that point that there is a way, now if you can point to
more documentation about it I can use to unblock my AR

Thanks a lot

Victor Rodriguez

> > -----Original Message-----
> > From: Victor Rodriguez [mailto:vm.rod25 at gmail.com]
> > Sent: April 23, 2019 7:02 PM
> > To: starlingx-discuss at lists.starlingx.io; Thebeau, Michel
> > Subject: Re: [Starlingx-discuss] How to update an installed image
> >
> > Hi
> >
> > Based on recommendations from Michael I am going to rewrite my question:
> >
> > I have a server, all in one with STX simplex configuration but I
> > installed the ISO like a month ago, now I want to get the latest
> > version of STX
> >
> > I think this a really important part of the project. I don't see
> > myself as sysadmin with a new CVE fixed in the latest version of
> > starling x and have to reinstall the full iso in all my nodes. I was
> > pretty sure we had this component like starling x update.
> >
> > Any feedback more than welcome, if this is already a project under
> > development is perfect if not, we might spend some time discussing it
> >
> > Regards
> >
> > Victor Rodriguez
> >
> >
> >
> >
> > Something like preupg or update-manager in the case of Centos and Ubuntu
> >
> > On Mon, Apr 22, 2019 at 9:11 AM Victor Rodriguez <vm.rod25 at gmail.com> wrote:
> >>
> >> Hi team
> >>
> >> I would like to know more about the image update mechanism we have in
> >> starting X. I have a simplex system installed and I want to keep my
> >> system updated with the latest version released in
> >> http://mirror.starlingx.cengn.ca/mirror/ but I don't want to reinstall
> >> the full ISO again every week. Is there any way to do a sw update in
> >> the starling x system so I keep my infrastructure updated w/o having
> >> to reinstall the ISO?
> >>
> >> Thanks a lot
> >>
> >> Regards
> >>
> >> Victor Rodriguez
> >
> > _______________________________________________
> > Starlingx-discuss mailing list
> > Starlingx-discuss at lists.starlingx.io
> > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
> > _______________________________________________
> > Starlingx-discuss mailing list
> > Starlingx-discuss at lists.starlingx.io
> > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
> >
>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss