Re: Inter-WG coordination: Stable application runtimes - SCC
On 12.01.2014 22:34, Alek Paunov wrote: So, finally on that road we have: ... - NTH: remote SCC DB for the instance, - NTH: SCC local state for multiple instances (e.g. deployment nodes or local containers) kept in the same SCC DB - NTH: SCC local state inheritance between instances Another closely related topic is the system snapshotting or in other words - system "flavors" variants/subvariants tree. Even before the btrfs magic, we have at hand wonderful snapshot mechanisms - LVM, qcow2+qemu-nbd-connect, ceph rbd, etc. Probably, LVM thinp currently is the best for the purpose of supporting tree of system variants. Once we apply FS snapshotting, combined with the SCC NTHs above, there are at least two appealing use-cases: - reusing one base e.g. F20 server container image for both the host and the incompatible containers (e.g. when one application requires nodejs 0.8 and another nodejs 0.10) - easy testbed for resolving the upgrade path for an existing, possibly non "pure Fedora" server with care about the deployed services. -- 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: Inter-WG coordination: Stable application runtimes - SCC
On Jan 12, 2014, at 1:51 PM, Alek Paunov wrote: > > Once we apply FS snapshotting, combined with the SCC NTHs above, there > are at least two appealing use-cases: > > - reusing one base e.g. F20 server container image for both the host and > the incompatible containers (e.g. when one application requires nodejs > 0.8 and another nodejs 0.10) > > - easy testbed for resolving the upgrade path for an existing, possibly > non "pure Fedora" server with care about the deployed services. I agree, there are quite a few use cases for file system snapshots. Do the snapshots need to be bootable? Chris Murphy -- 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: Inter-WG coordination: Stable application runtimes - SCC: Fedora social
On 12.01.2014 22:34, Alek Paunov wrote: - sccd-web: WebUI exposing full functionality, alternatively Cockpit (OpenLMI WebUI) extension. ... - NTH: SCC local state inheritance between instances Fedora Social: Almost every developer or sysadmins like to demonstrate how clean and clever is his own design :-). Currently we do not have a service where Sandra, Joe and George [1] could: - show and share with the others their Fedora based setups - conveniently keep the setup for their own reuse in the future Once we have sccd-web and few NTHs, we will be nearly (at least as code) equipped to provide something like "github for Fedora setups" for publishing, referring in the e-mails and forking Fedora users work. [1] http://fedoraproject.org/wiki/Server/Personas -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
