i started a new guide  focusing Cloud users. Currently we have
different guides spread over different wiki pages, and blog posts. But
we don't have any single place which at least points to the current
and updated docs. I first suggested about this during Flock cloud
working group meeting.
The docs are written using reStructured Text format, using sphinx
project. When Fedora docs team comes up with the new tooling, they can
just pull in the files from here. The source can be found at .
Right now it contains a very few things I just put in today. Because i
am using readthedocs.org here, any commit will be reflected on the
docs very fast. I am yet to add the download chapter. Feel free to
add anything you think is important for our users, PR(s) are always
Fedora Cloud Engineer
CPython Core Developer
#117: [VOTE] Make Atomic the primary focus of the Cloud Working Group
Reporter: jzb | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Future
Component: Planning | Keywords: vote, meeting
We've discussed on the mailing list:
And in this week's cloud working group meeting in IRC:
I'm asking for a formal vote so we can move forward on some deliverables.
1. The new primary focus of the WG will be the atomic cloud image.
2. The cloud base image will remain.
3. The group will also be looking to improve and reduce the size of the
Fedora Docker image.
Ticket URL: <https://fedorahosted.org/cloud/ticket/117>
Fedora Cloud Working Group Ticketing System
we have set up a process to do a compose nightly for Docker base image, Cloud
Images and Atomic installer isos based on Fedora 22 the results will land in
http://dl.fedoraproject.org/pub/alt/stage/ in a directory 22-<date>/
These composes should be the basis for the two week deliverable. One thing I
would like to do but we will need to figure out how best to do it is to have a
report come to the cloud list when the compose is complete and give some
useful info like kernel version, docker version, kubernetes, version etc.
restorecon changes many file labels following a clean install
This bug is not Cloud specific, but because Cloud_Atomic is read-only
it can't be fixed with restorecon. I mention this in the bug.
I don't know the quantity of metadata changes: selinux policy,
permissions, all other xattr, happen in the course of a release; but
in an "Atomic" context it looks like only option is to duplicate the
affected files to uniquely set new metadata on just that file in a
particular tree. The alternative, changing the metadata on the
hardlink, punches through to the original file in a completely
different tree, affecting all trees, and is therefore not atomic. (On
Btrfs this duplication can be made efficient with reflinks instead of
hardlinks, but that's trivia.)
I was wondering if someone has a set of reproducible steps to setup
file sync using NFS and 9pfs in a Vagrant/libvirt box.
Related issues with NFS setup on Vagrant:
If someone has already solved this problem, I'd like to work on top of
it, rather than starting from scratch :)
GPG Fingerprint: 033C 8041 A0E9 CDBA 2E02 B785 2119 5486 F245 DFD6