[atomic-wg] Issue #422: Evaluate podman for inclusion in atomic host
by Dusty Mabe
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
We've had a few discussions about including `cri-o` in atomic host and one [recently](https://pagure.io/atomic-wg/issue/407) discussing both `cri-o` and `podman`. The consensus on `cri-o` was that if someone needs to get openshift/kubernetes then it's not that much harder to also get `cri-o` as part of the same process (for example, using the `openshift-ansible` installer).
`podman`, however, is something we could consider adding because it gives us a nice familiar CLI with possibly less bloat. `podman` is brand new and there is still some work to be done on it. It was decided that we should evaluate adding `podman` into atomic host in a few months time. This was proposed at the [feb 7th WG meeting](https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-February/msg00024.html).
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422
5 years, 5 months
[atomic-wg] Issue #386: Provide updated examples for composing custom ostrees
by Micah Abbott
miabbott reported a new issue against the project: `atomic-wg` that you are following:
``
We've received requests/complaints from #atomic on Freenode about the lack of up to date documentation for composing custom ostrees.
```
I've been trying to build my own atomic repo using rpm-ostree for the past couple days.
I'm using a Fedora 27 workstation to build a repo for Atomic Fedora 27.
I've tried adapting multiple instructions found online (most of them very old).
Do working instructions exist anywhere for Fedora 27 Atomic?
```
It seems like we could benefit from an updated version of @jasonbrooks blog post for Fedora 27:
https://www.projectatomic.io/blog/2014/11/build-your-own-atomic-updates/
And perhaps another edition that covers composing your own F27 Workstation ostree?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/386
5 years, 5 months
[atomic-wg] Issue #439: Container Release
by Clement Verna
cverna reported a new issue against the project: `atomic-wg` that you are following:
``
The Fedora container release are quite difficult to get out, while the tooling might still need some work, I also feel that it is not really clear what we are expecting from the release.
Following a discussion on atomic-devel, I propose the following :
* Release containers that are based on the current stable fedora ( would be f27 currently)
* Release containers that are based on the next stable fedora release (beta) ( would be f28 currently) with the idea to have these available for testing.
This process would exclude rebuilding the f26 and rawhide based containers.
Any feedback on this proposition ?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/439
5 years, 6 months
Fedora Atomic WG Meeting Minutes 2018-03-28
by Micah Abbott
minutes:
https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-28/fedora_atom...
minutes (text):
https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2018-03-28/fedora_...
log:
https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-28/fedora_atom...
===================================
#fedora-meeting-1: fedora_atomic_wg
===================================
Meeting started by miabbott at 16:30:37 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-28/fedora_atom...
.
Meeting summary
---------------
* roll call (miabbott, 16:30:45)
* previous meeting action items (miabbott, 16:34:57)
* LINK: https://pagure.io/atomic-wg/issue/438 (miabbott, 16:35:52)
* LINK: https://pagure.io/atomic-wg/issue/439 (cverna, 16:37:52)
* ACTION: cverna to add some more details to the ticket (439) and
email adam miller for feedback (miabbott, 16:39:38)
* ACTION: drakonis to open an atomic-wg issue to track container tools
in debian discussion (miabbott, 16:40:07)
* coordinate Project Atomic-related talks for devconf.us (miabbott,
16:40:48)
* LINK: https://pagure.io/atomic-wg/issue/421 (miabbott, 16:40:57)
* devconf.us CfP closes on April 3 (miabbott, 16:42:28)
* engage sanja for talk ideas or travel costs related to
devconf.us/devconf.in (miabbott, 16:43:34)
* ACTION: sanja to start email thread with talk volunteers to make
sure abstracts are submitted on time (miabbott, 16:45:24)
* jberkus has volunteered to review defconf.us submissions before CfP
closes (miabbott, 16:49:37)
* Evaluate podman for inclusion in atomic host (miabbott, 16:50:31)
* LINK: https://pagure.io/atomic-wg/issue/422 (miabbott, 16:50:41)
* ACTION: ashcrow to make a PR to include podman in Fedora Rawhide
Atomic Host (miabbott, 16:54:43)
* use botbot.me to log #atomic channel (miabbott, 16:55:14)
* LINK: https://pagure.io/atomic-wg/issue/438 (miabbott, 16:55:21)
* ACTION: dustymabe to configure botbot.me to log #atomic channel
(miabbott, 17:01:50)
* Container Release (miabbott, 17:02:20)
* LINK: https://pagure.io/atomic-wg/issue/439 (miabbott, 17:02:23)
* Fedora 28 Talking Points (miabbott, 17:04:05)
* LINK: https://pagure.io/atomic-wg/issue/445 (miabbott, 17:04:08)
* open floor (miabbott, 17:12:51)
* cverna planning on container release mar 29 for f27 (miabbott,
17:13:58)
* ACTION: sayan to open ticket with cloud-sig about deprecating pv
AMIs (miabbott, 17:18:42)
* first project atomic community meeting in asia/australia to be held
April 03, 2018 - 05:00 UTC (miabbott, 17:20:38)
* everyone should publicize the asia/australia meeting via social
media, etc (miabbott, 17:26:02)
Meeting ended at 17:28:23 UTC.
Action Items
------------
* cverna to add some more details to the ticket (439) and email adam
miller for feedback
* drakonis to open an atomic-wg issue to track container tools in debian
discussion
* sanja to start email thread with talk volunteers to make sure
abstracts are submitted on time
* ashcrow to make a PR to include podman in Fedora Rawhide Atomic Host
* dustymabe to configure botbot.me to log #atomic channel
* sayan to open ticket with cloud-sig about deprecating pv AMIs
Action Items, by person
-----------------------
* ashcrow
* ashcrow to make a PR to include podman in Fedora Rawhide Atomic Host
* cverna
* cverna to add some more details to the ticket (439) and email adam
miller for feedback
* dustymabe
* dustymabe to configure botbot.me to log #atomic channel
* sayan
* sayan to open ticket with cloud-sig about deprecating pv AMIs
* **UNASSIGNED**
* drakonis to open an atomic-wg issue to track container tools in
debian discussion
* sanja to start email thread with talk volunteers to make sure
abstracts are submitted on time
People Present (lines said)
---------------------------
* miabbott (84)
* sanja1 (64)
* dustymabe (59)
* ashcrow (32)
* zodbot (27)
* rubao (15)
* lorbus (12)
* jberkus (10)
* cverna (8)
* sayan (7)
* ksinny (5)
* giuseppe (4)
* puiterwijk (3)
* jlebon (3)
* strigazi (1)
* walters (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
5 years, 6 months
[atomic-wg] Issue #443: Boot from ISO stuck at Reached target Basic System
by Rares Vernica
rares reported a new issue against the project: `atomic-wg` that you are following:
``
I got `Fedora-Atomic-ostree-x86_64-27-20180314.0.iso` on a USB stick. When booting from USB, I get as far as:
~~~~
...
[ OK ] Reached target paths.
[ OK ] Reached target Basic System.
_
~~~~
Than it get stack there forever.
On the same hardware, I was able to boot and install previous versions of the ISO.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/443
5 years, 6 months
