Re: Announce: fedostree/rpm-ostree v2014.3
From the website: Although yum is installed, it will operate in read-only mode. Do not attempt to use it at the moment. See Seems like the part talking about it is somehow missing i.e see what? ;) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Announce: fedostree/rpm-ostree v2014.3
On Fri, 2014-01-24 at 18:52 +0100, drago01 wrote: From the website: Although yum is installed, it will operate in read-only mode. Do not attempt to use it at the moment. See Seems like the part talking about it is somehow missing i.e see what? ;) I updated the text a bit on http://rpm-ostree.cloud.fedoraproject.org/#/ under Development area: Local package assembly. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Announce: fedostree/rpm-ostree v2014.3
On 21.01.2014 08:30, Colin Walters wrote: Hi Dennis, On Tue, 2014-01-21 at 07:40 +0100, Dennis Jacobfeuerborn wrote: Interesting. I've downloaded the VM Image and tried to understand the setup. Some bits are documented here https://people.gnome.org/~walters/ostree/doc/layout.html Apparently there exist sort of two root trees / and /sysroot in the system with some links targeting the /sysroot tree. With OSTree, you boot directly into a chroot - dracut switches root and starts systemd right after mounting the rootfs. See: https://git.gnome.org/browse/ostree/tree/src/switchroot/ostree-prepare-root.c /sysroot is a bind mount to the real root /. What I'm wondering about is that /dev/mapper/fedora-root is mounted several times on /, /var, /usr and /sysroot (twice!) sometimes rw and sometimes ro. /usr is simply a bind mount to itself so it can be mounted read-only. This is important because otherwise one could corrupt the object store in /ostree/repo by mutating the hardlink farm in /usr. Note the /usr here is really /ostree/deploy/fedostree/deploy/checksum.serial/usr as seen from the physical root. /var is a special bind mount to /ostree/deploy/fedostree/var which is shared between each deployment (chroot). The impression I get is that /sysroot is the actual root fs in the image and / the ostree directory at least that's what the links seem to suggest. I still don't understand the mount-voodoo though. Is there some documentation about this available? I'll look at adding more to the gtk-doc, though I suspect I may need to make a separate system administrators new to OSTree document which is a bit distinct from the how to use OSTree underneath your package manager document that the current one is. Thanks for the information. I think I was thrown off by the fact that the root device is mounted in several places with different content but now I realize that's probably because the external path isn't available from inside the jail so mount can only display the device. Previously I've only used bind mounts in a non-chroot context. Regards, Dennis -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Announce: fedostree/rpm-ostree v2014.3
On 21.01.2014 20:07, Richard W.M. Jones wrote: On Tue, Jan 21, 2014 at 07:40:00AM +0100, Dennis Jacobfeuerborn wrote: Interesting. I've downloaded the VM Image and tried to understand the setup. Apparently there exist sort of two root trees / and /sysroot in the system with some links targeting the /sysroot tree. What I'm wondering about is that /dev/mapper/fedora-root is mounted several times on /, /var, /usr and /sysroot (twice!) sometimes rw and sometimes ro. The impression I get is that /sysroot is the actual root fs in the image and / the ostree directory at least that's what the links seem to suggest. I still don't understand the mount-voodoo though. Is there some documentation about this available? Out of interest, did you boot into the alternate tree, ie: bls_import at the boot prompt? (Documented in http://rpm-ostree.cloud.fedoraproject.org/#/installation) Yes, hence the funky directory layout :) Regards, Dennis -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Announce: fedostree/rpm-ostree v2014.3
Hello devel@, I'm excited to announce the first public release (v2014.3) of the fedostree/rpm-ostree project. The web page is here: http://rpm-ostree.cloud.fedoraproject.org/#/ rpm-ostree is a quite new, raw, and also quite unofficial project (the instance above is in the Fedora private scratch cloud). It is suitable for evaluation primarily by engineers who are working on build/packaging/deployment tooling in Fedora, and advanced testers. If you're one of those people, before you read any more, if you have a few minutes, please jump to: http://rpm-ostree.cloud.fedoraproject.org/images/ and start downloading the preconfigured VM. (Or alternatively see http://rpm-ostree.cloud.fedoraproject.org/#/installation for parallel install instructions inside an existing system). I've often struggled with explaining OSTree to people - but for the audience here, I want to emphasize that OSTree is designed to be *complementary* to package systems like rpm/dpkg. While OSTree does take over some roles from RPM such as handling /etc, if you study it carefully, I think you'll come to agree. The overall vision is to change Fedora (and really its prominent downstream) into a less flexible, but more reliable set of products, tested and delivered *much* *much* faster. That's about all for this mail - the Background section of the web page has more. As for what's coming next - I plan to bring gnome-continuous style fast testing to the rpm-ostree codebase too (assuming I get push notification from Koji). For example, test boot both fedostree/20/x86_64/base/minimal, fedostree/20/x86_64/workstation/gnome/core after any package affecting them changes. Then if the tests pass, tag those trees as smoketested, like: fedostree/20/smoketested/x86_64/base/minimal. If you have questions, please follow up here! (There's no mailing list for rpm-ostree at the moment; you can use ostree-l...@gnome.org for questions about the core OSTree model). What I need now is evaluation from some of the stakeholders in various parts of the deployment stack; for example, the changes to the handling of /var in RPM needs discussion. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Announce: fedostree/rpm-ostree v2014.3
On 20.01.2014 19:03, Colin Walters wrote: Hello devel@, I'm excited to announce the first public release (v2014.3) of the fedostree/rpm-ostree project. The web page is here: http://rpm-ostree.cloud.fedoraproject.org/#/ rpm-ostree is a quite new, raw, and also quite unofficial project (the instance above is in the Fedora private scratch cloud). It is suitable for evaluation primarily by engineers who are working on build/packaging/deployment tooling in Fedora, and advanced testers. If you're one of those people, before you read any more, if you have a few minutes, please jump to: http://rpm-ostree.cloud.fedoraproject.org/images/ and start downloading the preconfigured VM. (Or alternatively see http://rpm-ostree.cloud.fedoraproject.org/#/installation for parallel install instructions inside an existing system). I've often struggled with explaining OSTree to people - but for the audience here, I want to emphasize that OSTree is designed to be *complementary* to package systems like rpm/dpkg. While OSTree does take over some roles from RPM such as handling /etc, if you study it carefully, I think you'll come to agree. The overall vision is to change Fedora (and really its prominent downstream) into a less flexible, but more reliable set of products, tested and delivered *much* *much* faster. That's about all for this mail - the Background section of the web page has more. As for what's coming next - I plan to bring gnome-continuous style fast testing to the rpm-ostree codebase too (assuming I get push notification from Koji). For example, test boot both fedostree/20/x86_64/base/minimal, fedostree/20/x86_64/workstation/gnome/core after any package affecting them changes. Then if the tests pass, tag those trees as smoketested, like: fedostree/20/smoketested/x86_64/base/minimal. If you have questions, please follow up here! (There's no mailing list for rpm-ostree at the moment; you can use ostree-l...@gnome.org for questions about the core OSTree model). What I need now is evaluation from some of the stakeholders in various parts of the deployment stack; for example, the changes to the handling of /var in RPM needs discussion. Interesting. I've downloaded the VM Image and tried to understand the setup. Apparently there exist sort of two root trees / and /sysroot in the system with some links targeting the /sysroot tree. What I'm wondering about is that /dev/mapper/fedora-root is mounted several times on /, /var, /usr and /sysroot (twice!) sometimes rw and sometimes ro. The impression I get is that /sysroot is the actual root fs in the image and / the ostree directory at least that's what the links seem to suggest. I still don't understand the mount-voodoo though. Is there some documentation about this available? Regards, Dennis -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Announce: fedostree/rpm-ostree v2014.3
Hi Dennis, On Tue, 2014-01-21 at 07:40 +0100, Dennis Jacobfeuerborn wrote: Interesting. I've downloaded the VM Image and tried to understand the setup. Some bits are documented here https://people.gnome.org/~walters/ostree/doc/layout.html Apparently there exist sort of two root trees / and /sysroot in the system with some links targeting the /sysroot tree. With OSTree, you boot directly into a chroot - dracut switches root and starts systemd right after mounting the rootfs. See: https://git.gnome.org/browse/ostree/tree/src/switchroot/ostree-prepare-root.c /sysroot is a bind mount to the real root /. What I'm wondering about is that /dev/mapper/fedora-root is mounted several times on /, /var, /usr and /sysroot (twice!) sometimes rw and sometimes ro. /usr is simply a bind mount to itself so it can be mounted read-only. This is important because otherwise one could corrupt the object store in /ostree/repo by mutating the hardlink farm in /usr. Note the /usr here is really /ostree/deploy/fedostree/deploy/checksum.serial/usr as seen from the physical root. /var is a special bind mount to /ostree/deploy/fedostree/var which is shared between each deployment (chroot). The impression I get is that /sysroot is the actual root fs in the image and / the ostree directory at least that's what the links seem to suggest. I still don't understand the mount-voodoo though. Is there some documentation about this available? I'll look at adding more to the gtk-doc, though I suspect I may need to make a separate system administrators new to OSTree document which is a bit distinct from the how to use OSTree underneath your package manager document that the current one is. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
