[atomic-wg] Issue #160 `Ship fedora-motd in F24 atomic image`
by Pagure
walters added a new comment to an issue you are following:
``
The previous discussion on this was https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2016-A...
which I didn't reply to.
Okay, so you said:
```
The file
/etc/motdgen.d/02-updateinfo.sh
does nothing but cat the content of /var/run/updateinfo.txt if
available.
```
which, looking at https://kojipkgs.fedoraproject.org//packages/fedora-motd/0.1.2/2.fc25/noa...
isn't true, since I see this code:
```
cat etc/motdgen.d/02-updateinfo.sh
...
if [ ! -f "$firstrun" ]; then
touch $firstrun
nohup /usr/bin/motdgen-cache-updateinfo &
fi
# cat usr/bin/motdgen-cache-updateinfo
#!/bin/sh
if [ -f /run/ostree-booted ]; then
rpm-ostree upgrade --check --preview > /var/run/rpmostree_updateinfo.out
...
```
We're hence starting a potentially long running process out of the PAM stack, which is really not a good idea. Invoking rpm-ostree like this will also block other clients as I said (And that's also true of yum/dnf) - which is again very problematic if the "login" is actually Ansible where you're trying to do things like configure a proxy or mirror.
Deleting the first run bit would deal with the biggest of my objections, but then we'd still have the cron job (which itself is problematic because we *just* got rid of cron - this should be a systemd timer)
An architecture which is event driven and would implement the "only check automatically if explicitly invoked at least once" is to patch rpm-ostree to do something like `systemctl start --no-block system-motdgen.service` after it's completed a transaction. Then the motd code could call back with the DBus API for `GetCachedUpdateDetails`.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/160
4 years, 6 months
[atomic-wg] Issue #160 `Ship fedora-motd in F24 atomic image`
by Pagure
walters added a new comment to an issue you are following:
``
The previous discussion on this was https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2016-A...
which I didn't reply to.
Okay, so you said:
```
The file
/etc/motdgen.d/02-updateinfo.sh
does nothing but cat the content of /var/run/updateinfo.txt if
available.
```
which, looking at https://kojipkgs.fedoraproject.org//packages/fedora-motd/0.1.2/2.fc25/noa...
isn't true, since I see this code:
```
cat etc/motdgen.d/02-updateinfo.sh
...
if [ ! -f "$firstrun" ]; then
touch $firstrun
nohup /usr/bin/motdgen-cache-updateinfo &
fi
# cat usr/bin/motdgen-cache-updateinfo
#!/bin/sh
if [ -f /run/ostree-booted ]; then
rpm-ostree upgrade --check --preview > /var/run/rpmostree_updateinfo.out
...
```
We're hence starting a potentially long running process out of the PAM stack, which is really not a good idea. Invoking rpm-ostree like this will also block other clients as I said (And that's also true of yum/dnf) - which is again very problematic if the "login" is actually Ansible where you're trying to do things like configure a proxy or mirror.
Deleting the first run bit would deal with the biggest of my objections, but then we'd still have the cron job (which itself is problematic because we *just* got rid of cron - this should be a systemd timer)
An architecture which is event driven and would implement the "only check automatically if explicitly invoked at least once" is to patch rpm-ostree to do something like `systemctl start --no-block system-motdgen.service` after it's completed a transaction. Then the motd code could call back with the DBus API for `GetCachedUpdateDetails`.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/160
4 years, 6 months
Test Day: Docker Swarm Test -- PASSED
by Josh Berkus
As an additional test, I set up a 3-node Docker Swarm cluster.
This worked fine (after fixing the docker-storage-setup issues). I was
able to deploy a service to multiple nodes.
Note that the Docker documentation isn't accurate when it comes to what
ports you need to expose.
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
4 years, 6 months
should we release new fedora cloud image for f24
by Dusty Mabe
As part of the next release of Fedora 24 atomic host should we also
release the Fedora 24 base image so that the released version doesn't
have the latest huge kernel bug in it by default?
Dusty
4 years, 6 months
weird error with docker-storage-setup
by Dusty Mabe
I haven't had time to really investigate but figured I would pass this along:
qcow:
http://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161021.n.0...
test results from last night's test run:
https://apps.fedoraproject.org/autocloud/jobs/971/output
error:
[fedora@cloudhost ~]$ sudo systemctl status -l docker-storage-setup.service
● docker-storage-setup.service - Docker Storage Setup
Loaded: loaded (/usr/lib/systemd/system/docker-storage-setup.service; enabled; vendor preset: disabled)
Active: inactive (dead)
Oct 21 18:40:37 localhost.localdomain systemd[1]: docker-storage-setup.service: Job docker-storage-setup.service/start deleted to break ordering cycle starting with multi-user.target/start
Warning: docker-storage-setup.service changed on disk. Run 'systemctl daemon-reload' to reload units.
[fedora@cloudhost ~]$ echo $?
3
4 years, 6 months
Join Us for a Fedora 25 Test Day Next Week (October 24, 2016)
by Jason Brooks
Want to help make Fedora Atomic Host even better? Join us next week
for the Fedora Cloud Test Day, where we’ll be banging on the Atomic
Host image for Fedora. As always, we’re looking for many hands to help
put the release through its paces.
To participate, you’ll need a system with Vagrant, libvirt/KVM, or
access to OpenStack or another IaaS that can consume the qcow or raw
images for Atomic. Alternately, if you have an Amazon Web Services
account, there will be AMIs you can test; check the wiki page for
links on the test day.
Grab the image from the wiki [0], and then check out the test results
page [1] to see the tests you should run and report the results.
[0] https://fedoraproject.org/w/index.php?title=Test_Day:2016_10_24_Cloud
[1] http://testdays.fedorainfracloud.org/events/11
We also encourage freestyle testing as well, so if you have use cases
that go beyond the described tests please do put the image through
those tests as well. For example, you could test setting up a
Kubernetes cluster or even OpenShift.
Found bugs? Be sure to report them on Bugzilla.
Always Be Testing
If you can’t make it for the scheduled test day, no sweat. You can
play along at home any time. You can find updated nightly images for
Fedora Atomic and Fedora Cloud Base, alongside the results of
automated tests, at the Autocloud site [2]. You can find an image type
and version you’re interested in testing, click the Output button next
to the test results, and download the image using the Download Image
on the output page.
[2] https://apps.fedoraproject.org/autocloud/jobs/
Communicating During and After Test Days
We’ll have folks watching #fedora-test-day on Freenode, and (as
always) folks in #fedora-cloud and #atomic. If you have questions, or
think you can help others, please join in!
Also, there’s always the cloud(a)lists.fedoraproject.org mailing list
[3] for additional conversations around the Fedora Atomic Host images.
Please sign up, and feel free to chime in any time with questions,
comments, suggestions, or to raise a hand to help out. See you on Test
Day!
[3] https://lists.fedoraproject.org/admin/lists/cloud.lists.fedoraproject.org/
4 years, 6 months
