Man pages in cloud images - documentation
by Gergely Gombos
Hello,
I just installed a F28 image on a Scaleway cloud server. Runs fine, except there were no man pages, even after installing man-pages package.
It turned out after a lot of searching that this is not a bug but a feature.
Issue on GitHub: https://github.com/fedora-cloud/docker-brew-fedora/issues/9#issuecomment-...
So the culprit is the Kickstarts file, here: https://pagure.io/fedora-kickstarts/blob/master/f/fedora-docker-common.ks... (and other nearby .ks files)
It says "%packages --excludedocs --instLangs=en --nocore [...]"
According to the Kickstart docs (http://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#chapter-4...) this won't install man pages, presumably to save space, but the end user won't know this, because man will simply not find any man pages and that's it.
A solution was to edit /etc/dnf/dnf.conf, comment "tsflags=nodocs" and then reinstall everything with dnf reinstall.
My question: I understand that it's important to save space with containers, but often cloud users wish to use man pages, as they are using the cloud server just as any remote computer. Is there a way to document the above situation e.g. when the user tries to view a man page gets a notification about why they are not installed (and how to install them)?
Thanks!
Best regards,
Greg Gombos
5 years, 2 months
More frequent Fedora Cloud updates
by Joe Doss
Hello!
My name is Joe Doss and I want to help the Fedora Cloud SIG bring more
frequent tested releases of Fedora Cloud it's user base. The goal of
this project is to provide more frequent updates of Fedora Cloud to
users on a set cadence or on a case per case basis for major security
events.
One major pain point that Fedora Cloud currently faces is the fact that
once a new Fedora release comes out, the cloud images are no longer
updated over time. This brings a poor user experience if bugs that are
fixed later on in the current release cycle but are painful on the first
boot of a Fedora Cloud instance until the user updates the instance.
I reached out to Dusty Mabe and he agreed to mentor me on this project
along with help from Kellin and Mohan.
The current ideas on the table for bringing this project to light are:
* Standardize and improve Fedora Cloud tests
* Create a Fedora Cloud test day for these updates to help improve tests
* Set a release cadence policy post Fedora Release
* Set a security update policy for major security updates
We will create issues under pagure.io/cloud-sig and try to get this
project rolling by Fedora 30 at the latest. Any comments or suggestions
on this topic are very welcome.
Thanks!
Joe
--
Joe Doss
joe(a)solidadmin.com
5 years, 3 months
Fedora AWS Resource IDs migrates to longer format
by Sayan Chowdhury
In February 2018, AWS announced the migration of Resource IDs to
longer format. Post June 2018, all the new resources will be created
with longer IDs by default.[1]
This email is to announce that the Fedora AMIs has been migrated to
the longer resource IDs format. The new format will migrate from the
current 8-character string to a 17-character string. For example, if
the AMI IDs are like "ami-1234abc0", post the migration the AMI IDs
would be like "ami-1234567890abcdef0".
If you have any questions, drop an email to the list or drop in
#fedora-atomic or #fedora-cloud on Freenode IRC.
[1] https://aws.amazon.com/about-aws/whats-new/2018/02/longer-fo
rmat-resource-ids-are-now-available-in-amazon-ec2/
--
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Senior Software Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13 AB3C B023 9931 9CD0 5C8B
Proud to work at The Open Organization!
5 years, 3 months
