Fedora CoreOS meeting canceled for 2019-06-26
by Benjamin Gilbert
Hi all,
Since there are no fedora-coreos-tracker tickets with the `meeting` label,
the Fedora CoreOS IRC meeting for 2019-06-26 is canceled.
Sincerely,
--meeting canceler shell script
3 years, 11 months
Fedora CoreOS status updates
by Jonathan Lebon
Hi all,
For those of you subscribed to the relevant repos (mostly the
tracker[1] and the config[2]), you've likely seen a lot of discussions
taking place lately. Things are progressing nicely, though there's
still a lot of work left ahead of us! If you're not subscribed, here
are some highlights:
- We have more precise definitions of the official streams[3] as well
as the tooling and workflow involved to generate them[4]. To
summarize, we will have 3 production streams (stable, testing, and
next), 2 development streams (testing-devel, and next-devel), and some
completely automated mechanical streams.
- We are building a subset of those streams in the OCP instance
running in CentOS CI (for now: testing, testing-devel, and
bodhi-updates). It is in fact very easy to get started hacking on
this; see the pipeline repo for information[5].
- We have moved away from the CentOS CI artifact server to a bucket in
AWS S3, which is fronted by http://builds.coreos.fedoraproject.org/.
The old output location[6] will now point you to the new page for
downloading builds[7].
These only scratch the surface of what's been going on. We're also
working on various brand-new userspace tools (such as Zincati[8] and
Airlock[9]), as well as refining how the OS itself is put together in
coreos-assembler (for example, moving away from Anaconda[10]). I could
keep throwing more links, but let's stop here for now. :)
As usual, if you'd like to participate or keep an eye on progress,
subscribe to the tracker and/or attend the weekly community meetings
on Wednesdays in #fedora-meeting-1 at 16:30 UTC.
Thanks!
Jonathan
[1] https://github.com/coreos/fedora-coreos-tracker
[2] https://github.com/coreos/fedora-coreos-config
[3] https://github.com/coreos/fedora-coreos-tracker/blob/master/Design.md#rel...
[4] https://github.com/coreos/fedora-coreos-tracker/blob/master/stream-toolin...
[5] https://github.com/coreos/fedora-coreos-pipeline
[6] http://artifacts.ci.centos.org/fedora-coreos/prod/builds/latest/
[7] https://builds.coreos.fedoraproject.org/browser
[8] https://github.com/coreos/zincati/
[9] https://github.com/coreos/airlock/
[10] https://github.com/coreos/coreos-assembler/pull/556
3 years, 11 months
Fedora CoreOS meeting canceled for 2019-06-19
by Benjamin Gilbert
Hi all,
Since there are no fedora-coreos-tracker tickets with the `meeting` label,
the Fedora CoreOS IRC meeting for 2019-06-19 is canceled.
Sincerely,
--meeting canceler shell script
3 years, 11 months
Fedora CoreOS Meeting Minutes 2019-06-12
by Benjamin Gilbert
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2019-06-12/fedora_core...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2019-06-12/fedora_core...
Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2019-06-12/fedora_core...
========================================
#fedora-meeting-1: fedora_coreos_meeting
========================================
Meeting started by bgilbert at 16:30:00 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2019-06-12/fedora_core...
.
Meeting summary
---------------
* roll call (bgilbert, 16:30:05)
* Action items from last meeting (bgilbert, 16:34:14)
* Stream metadata generator (bgilbert, 16:34:35)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/193
(bgilbert, 16:34:40)
* ACTION: ksinny to summarize discussion in ticket (bgilbert,
17:00:23)
* Release notes (bgilbert, 17:00:56)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/194
(bgilbert, 17:00:58)
* LINK: https://coreos.com/releases/ (bgilbert, 17:06:58)
* LINK:
https://lists.fedoraproject.org/archives/list/rel-eng@lists.fedoraproject...
(dustymabe, 17:10:21)
* ACTION: bgilbert to summarize discussion in ticket (bgilbert,
17:24:20)
* Open Floor (bgilbert, 17:25:27)
* streams and stream tooling progress:
https://github.com/coreos/fedora-coreos-config/issues/100
(dustymabe, 17:26:20)
* signing project proposal was created for fedora infra:
https://github.com/coreos/fedora-coreos-tracker/issues/187#issuecomment-4...
(dustymabe, 17:27:11)
* updates(.stg)coreos.fedoraproject.org progress
https://pagure.io/fedora-infrastructure/issue/7825#comment-574361
(kaeso[m], 17:28:01)
Meeting ended at 17:29:34 UTC.
Action Items
------------
* ksinny to summarize discussion in ticket
* bgilbert to summarize discussion in ticket
Action Items, by person
-----------------------
* bgilbert
* bgilbert to summarize discussion in ticket
* ksinny
* ksinny to summarize discussion in ticket
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* bgilbert (113)
* ksinny (32)
* jlebon (29)
* dustymabe (23)
* zodbot (18)
* kaeso[m] (10)
* ajeddeloh (7)
* slowrie (4)
* miabbott (1)
* lorbus (1)
* mnguyen_ (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
3 years, 11 months
Re: RFC: Atomic Updates configuration handling proposal by Thorsten Kukuk for CoreOS
by Thorsten Kukuk
Hi,
On Wed, Jun 05, Neal Gompa wrote:
> I agree about /usr/lib. Moreover, I think /usr/lib has been misused
> quite a lot for configuration files lately. The idea of a
> /usr/sysconfig makes a lot more sense to me. For the first time in a
> while, we're getting a descriptive name for it, and it's easily
> discoverable.
>
> If I could wave a wand, I'd move all of the stuff we'd been putting in
> /usr/lib into /usr/sysconfig. :)
I started a discussion about the directory name on the fhs mailing list:
https://lists.linuxfoundation.org/pipermail/fhs-discuss/2019-June/000500....
Please help and comment there, too, so that this discussion will not
end again with "use something below /usr/lib or /usr/share" and no
agreement on one directory.
Thanks,
Thorsten
--
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nuernberg)
3 years, 11 months
How to make ignition think it's the first boot?
by QingFeng Hao
Hi,
According to the link https://coreos.com/ignition/docs/latest/boot-process.html, ignition only takes effect at the first boot.
But we want to make it effect later if we missed something in the first boot, or we want to debug ignition.
So question is: how can I set file coreos/first_boot in the EFI System Partition, or set 'coreos.first_boot=detected' in kernel parameter line in an existing
coreos qcow2 image which can be started, so that I can make ignition work?
Thanks a lot!
--
Regards
QingFeng Hao
3 years, 12 months