IoT management
by Andy Monis
All,
I work for https://anthropos.io/ and we currently use stretch lite on pi3b as our core os. We have been investigating the use of Fedora IoT as a replacement given some of the advantages that lib-ostree promises.
With regards to using and deploying fedora, or hub is relatively simple, therefore we have been installing our software directly via rpm-ostree ( rather than using containers ). Most of the software is either Python or JavaScript, which leads to the question of, what is the best (current) approach for working with package managers, in this case pip3 and Npm, which make assumptions about what directories are available to install into. My current solution is to vendor all of the dependencies in the rpm.
Further to this, if there is a problem, currently we have the ability to ssh to the hubs and administer ( sudo x y z etc ). However in the Fedora, most of the filesystem is protected, which is good. However is it possible to “check out” the current filesystem to allow some modification, then at a future point either “revert” or “stash” the changes to put the hub back inline. The purpose here is to allow an emergency change to a specific device without having to re-package rpms etc if required.
Regards
Andy Monis
4 years, 3 months
Fedora IoT Working Group Meeting Minutes 2019-07-31
by Peter Robinson
=================================================
#fedora-meeting: Fedora IoT Working Group Meeting
=================================================
Meeting started by pbrobinson at 14:00:45 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2019-07-31/fedora_iot_wo...
.
Meeting summary
---------------
* roll call (pbrobinson, 14:00:46)
* 1) ==== Working Group process and admin ==== (pbrobinson, 14:04:57)
* there's now a IoT bugzilla component (pbrobinson, 14:05:53)
* LINK:
https://bugzilla.redhat.com/buglist.cgi?component=IoT&product=Fedora
(pbrobinson, 14:05:58)
* ACTION: pbrobinson to add details of this to the docs (pbrobinson,
14:06:43)
* 2) ==== Fedora 31 ==== (pbrobinson, 14:11:07)
* rawhide composes a generally running OK (pbrobinson, 14:11:43)
* mass rebuild is complete and I expect the remainder will be in
today's mainline compose (pbrobinson, 14:12:08)
* 3) ==== Fedora 30 ==== (pbrobinson, 14:17:17)
* latest stable IoT builds are at https://iot.fedoraproject.org
(pbrobinson, 14:20:18)
* 4) ==== Flock Budapest 2019 ==== (pbrobinson, 14:23:22)
* Flock is next week from Thurs until Sun (pbrobinson, 14:23:34)
* next week's IoT meeting is cancelled due to Flock (pbrobinson,
14:24:52)
* 4) ==== Open Floor ==== (pbrobinson, 14:26:08)
Meeting ended at 14:31:20 UTC.
Action Items
------------
* pbrobinson to add details of this to the docs
Action Items, by person
-----------------------
* pbrobinson
* pbrobinson to add details of this to the docs
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* pbrobinson (37)
* pwhalen (12)
* zodbot (7)
* bcotton (4)
* satellit (3)
* ipcloud (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
4 years, 4 months
A place to track IoT bugs
by Ben Cotton
It would be helpful to contributors and users alike if Fedora IoT had
a single place folks could submit bugs. We discussed this briefly in
the meeting this morning and decided to take it to the mailing list.
There are a few options.
1. Bugzilla bugs
Advantage: it's the place that other Fedora bugs live. This means it's
easy to reassign bugs that aren't strictly IoT-related (e.g. kernel
bugs) to the appropriate component.
Disadvantage: it's not exactly user-friendly
2. Pagure issues
Advantage: it looks a lot like git forges that people might already be
used to. Can refer to issues in commits when things are fixed
Disadvantage: bugs that belong to other components would need to be
manually moved. It also requires a FAS account
3. Taiga issues
Advantage: issues live near the planned work
Disadvantage: Requires a FAS account
I like option 1 the best. In fact, I think it would be pretty great if
all our Editions had a component that was the end-user interface and
contributors moved the issues to the right place. But I'm not the one
who will be doing much/any of the work, so what does everyone else
think?
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
4 years, 4 months
Fedora IoT Working Group Meeting Minutes 2019-07-24
by Peter Robinson
=================================================
#fedora-meeting: Fedora IoT Working Group Meeting
=================================================
Meeting started by pwhalen at 14:02:41 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2019-07-24/fedora_iot_wo...
.
Meeting summary
---------------
* roll call (pwhalen, 14:02:41)
* 1) ==== Working Group process and admin ==== (pbrobinson, 14:05:03)
* LINK: https://docs.fedoraproject.org/en-US/iot/edition-promotion/
(pbrobinson, 14:05:41)
* I'm working through the edition promotion pieces, feedback is still
welcome (pbrobinson, 14:06:07)
* bcotton has nudged badges team on an IoT badge. We're waiting for
design resources (bcotton, 14:07:35)
* ACTION: bcotton to follow up on bug-filing mailing list thread
(bcotton, 14:12:05)
* 2) ==== Fedora 31 ==== (pbrobinson, 14:16:48)
* regular rawhide IoT composes (pbrobinson, 14:18:02)
* mass rebuild for F-31 kicks off today (pbrobinson, 14:18:12)
* LINK: https://paste.fedoraproject.org/paste/y-CPEhdL6jJA2VR8BZcH4A
(pwhalen, 14:26:01)
* LINK: https://github.com/projectatomic/rpm-ostree/pull/1866
(nirik, 14:27:37)
* LINK:
https://discussion.fedoraproject.org/t/not-able-to-update-silverblue-31/2...
(nirik, 14:28:06)
* 3) ==== Fedora 30 ==== (pbrobinson, 14:33:00)
* F-30 has moved to stable branch (pbrobinson, 14:33:13)
* F-29 users will move to F-30 (pbrobinson, 14:33:47)
* F-30 users will need to do a "rpm-ostree rebase -b
fedora/stable/<ARCH>/iot" as per the docs (pbrobinson, 14:34:44)
* 4) ==== Open Floor ==== (pbrobinson, 14:39:27)
* LINK: https://github.com/latchset/clevis/issues/109 (pbrobinson,
14:45:37)
Meeting ended at 14:45:48 UTC.
Action Items
------------
* bcotton to follow up on bug-filing mailing list thread
Action Items, by person
-----------------------
* bcotton
* bcotton to follow up on bug-filing mailing list thread
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* pbrobinson (37)
* pwhalen (16)
* bcotton (10)
* zodbot (7)
* nirik (4)
* laubersm (3)
* jsmith (1)
* tdawson (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
4 years, 4 months
IoT stable ostree branch is moving to F-30
by Peter Robinson
Hi All,
Just a heads up that the ostree stable branch will be moving to F-30
beginning of next week so anyone still on F-29 will be heading to F-30
the next time they update.
Peter
4 years, 4 months