Re: [atomic-devel] Storage for system containers
by Daniel Walsh
On 04/28/2017 01:09 PM, Giuseppe Scrivano wrote:
> Hi,
>
> Dusty Mabe <dusty(a)dustymabe.com> writes:
>
>> i'm going to show how little I know with this question, but would it be possible
>> to have a separate partition for system containers that was essentially xfs + an
>> overlayfs of the host filesystem?
> yes we could do that, we will just need to use a separate OSTree
> repository, so that it won't be shared with the OS. This is possible
> already today, as the OSTree storage to use is configurable.
> The disadvantage is that files in common with the host will still need
> to be copied in the new repository.
>
> Regards,
> Giuseppe
Ok, We should be able to support both environments, where you want to
maximize disk space savings by taking advantage of sharing OS Content
with the Host OS by running your system container storage on the same
disk as /usr. If you want to totally isolate your container content
from the host, we can mount /var/lib/containers on an separate
partition/disk and keep storage isolated. The only problem here is that
/var/lib/docker would need to be modified to use
/var/lib/containers/docker. From CRI-O/buildah and all container
storage we store by default in /var/lib/containers/storage. With the
move to ThePackageFormallyKnownAsDocker (TPFKAD), we should move the
default storage to /var/lib/containers/TPFKAD.
7 years, 1 month
Atomic WG Meeting Minutes April 19
by Josh Berkus
... just for the record, since I forgot them last week.
===================================
#fedora-meeting-1: fedora_atomic_wg
===================================
Meeting started by jberkus at 17:02:11 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-04-19/fedora_atom...
.
Meeting summary
---------------
* roll call (jberkus, 17:02:22)
* previous meeting action items (dustymabe, 17:05:32)
* LINK: https://pagure.io/atomic-wg/issue/268 that's mine (jbrooks,
17:06:45)
* LINK:
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.o...
(dustymabe, 17:08:26)
* Meeting Issues (jberkus, 17:14:59)
* ACTION: jbrooks to lead writing up the new support policy and plan
for rolling releases (jberkus, 17:26:28)
* Open Floor (jberkus, 17:26:53)
* LINK: https://github.com/moby/moby/pull/32691 (miabbott, 17:41:25)
* LINK: http://www.navops.io/navops-roadshow.html (jberkus,
17:48:15)
Meeting ended at 17:54:06 UTC.
Action Items
------------
* jbrooks to lead writing up the new support policy and plan for rolling
releases
Action Items, by person
-----------------------
* jbrooks
* jbrooks to lead writing up the new support policy and plan for
rolling releases
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* dustymabe (91)
* jberkus (82)
* roshi (18)
* zodbot (15)
* sayan (11)
* jbrooks (8)
* miabbott (6)
* dgilmore (6)
* deuscapturus (5)
* walters (3)
* yzhang (2)
* linuxmodder (1)
* gholms (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
7 years, 1 month
Atomic WG Meeting Minutes 2017-04-26
by Dusty Mabe
summary: https://meetbot.fedoraproject.org/teams/atomic-wg/atomic-wg.2017-04-26-17...
full log: https://meetbot.fedoraproject.org/teams/atomic-wg/atomic-wg.2017-04-26-17...
============================
#fedora-meeting-1: atomic-wg
============================
Meeting started by dustymabe at 17:01:50 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-04-26/atomic-wg.2...
.
Meeting summary
---------------
* roll call (dustymabe, 17:01:56)
* previous meeting action items (dustymabe, 17:05:32)
* ACTION: jbrooks to lead writing up the new support policy and plan
for rolling (dustymabe, 17:07:54)
* fedimg: don't use 'builder' instance for uploading AMIs (dustymabe,
17:08:25)
* LINK: https://pagure.io/atomic-wg/issue/269 (dustymabe, 17:08:33)
* 2WK Atomic Release Criteria (dustymabe, 17:10:01)
* LINK: https://pagure.io/atomic-wg/issue/264 (dustymabe, 17:10:07)
* clarify policy on atomic host support for older Fedora "number"
releases (dustymabe, 17:10:55)
* LINK: https://pagure.io/atomic-wg/issue/228 (dustymabe, 17:11:01)
* design, deploy and document Fedora OpenShift Playground (FOSP)
(dustymabe, 17:11:39)
* LINK: https://pagure.io/atomic-wg/issue/153 (dustymabe, 17:11:45)
* LINK: https://pagure.io/atomic-wg/issue/153#comment-432517
(jbrooks, 17:12:51)
* containers tickets (dustymabe, 17:14:47)
* LINK: https://pagure.io/atomic-wg/issues?status=Open&tags=containers
(dustymabe, 17:14:52)
* IDEA: <gholms> I'm also prettyy sure it would be a good idea to ask
the package's maintainer about that proactively when creating a new
container (kushal, 17:18:55)
* please review as many containers as you can! (dustymabe, 17:20:36)
* open floor (dustymabe, 17:20:44)
* LINK:
https://fedoraproject.org/wiki/Changes/ContainerMinimalImage#Summary
(dustymabe, 17:23:37)
* LINK:
http://dl.fedoraproject.org/pub/fedora/linux/releases/test/26_Alpha/Docke...
(dustymabe, 17:25:07)
* LINK: https://pagure.io/releng/issue/6619 (dustymabe, 17:27:33)
* LINK: https://github.com/projectatomic/atomic-site/issues/423
(jberkus, 17:36:10)
Meeting ended at 17:44:59 UTC.
Action Items
------------
* jbrooks to lead writing up the new support policy and plan for rolling
Action Items, by person
-----------------------
* jbrooks
* jbrooks to lead writing up the new support policy and plan for
rolling
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* dustymabe (147)
* jberkus (43)
* fatherlinux (29)
* maxamillion (26)
* roshi (17)
* jbrooks (16)
* zodbot (15)
* kushal (12)
* gholms (12)
* jzb (10)
* walters (7)
* miabbott (5)
* mrguitar (4)
* sayan (3)
* nb (2)
* yzhang (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
7 years, 1 month
Re: [atomic-devel] Storage for system containers
by Daniel Walsh
On 04/27/2017 06:44 AM, Giuseppe Scrivano wrote:
> Daniel Walsh <dwalsh(a)redhat.com> writes:
>
>> On 04/24/2017 01:56 PM, Dusty Mabe wrote:
>>> NOTE: please reply-all when responding to this message
>>>
>>>
>>> In Fedora Atomic Host if we use system containers as advertised
>>> we end up using `atomic pull --storage ostree` which by default
>>> throws images into /var/lib/containers/atomic/. This is on the
>>> root filesystem which may be undesirable.
>>>
>>> Since in Fedora 26 the new version of container-storage-setup allows
>>> us greater control over a "CONTAINER_ROOT" should we consider trying
>>> to make sure both ostree storage and docker storage get placed under
>>> that CONTAINER_ROOT?
>>>
>>> The current default [1] is to just mount the CONTAINER_ROOT on
>>> /var/lib/docker.
>>>
>>> Dusty
>>>
>>> [1] https://src.fedoraproject.org/cgit/rpms/docker.git/tree/docker.spec?h=f26...
>>>
>> Perhaps we should just mount a partition at /var or move
>> /var/lib/docker to /var/lib/containers/docker and make a symbolic link
>> from /var/lib/docker-> /var/lib/containers/docker.
> Mounting a partition at /var wouldn't work with system containers.
>
> System containers are stored in the OSTree storage and on Atomic Host
> they are checked out to /ostree/deploy/$OS/var/lib/containers/atomic/ so
> that the checkout and the OSTree storage are on the same file system.
> This is required to use hard links instead of copying files from OSTree.
>
> Regards,
> Giuseppe
Thanks for giving us a clue. This breaks the assumptions that spawned
this conversation.
We want to keep system containers on the same file system as /usr, and
since we use OSTRee
and most system containers will match the arch, then we should see a lot
of sharing so much smaller
disk usage then if they were standard docker images. Dusty what do you
think? I guess we should think about increasing the size of the "root"
file system to handle the need of system containers.
7 years, 1 month
[atomic-wg] Issue #243 `Require DESCRIPTION label for FLIBS containers`
by Josh Berkus
jberkus reported a new issue against the project: `atomic-wg` that you are following:
``
We should require a "description" label in FLIBS containers. This would contain a long, narrative description of the container and how it's supposed to be used, intended for human readability. This would include, for all containers:
* what service/software the container provides
It would also include all of the following which are applicable to the container:
* what purpose it fulfills in a larger infrastructure
* what each VOLUME in the container is for and what kinds of storage they need
* any details about dependencies on other container images
* links to documentation or software project pages
* any special requirements the container has (like lots of RAM, or sound server access)
* details on any required configuration, or links to documentation on configuration
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/243
7 years, 1 month
Many new dependencies in f25 updates-testing
by Dusty Mabe
Difference between 25.113 from fedora-atomic/25/x86_64/updates/docker-host
and 25.119 from fedora-atomic/25/x86_64/testing/docker-host introduces
quite a few new deps:
Upgraded:
atomic 1.15.1-1.fc25 -> 1.17.1-2.fc25
cockpit-bridge 137-1.fc25 -> 138-1.fc25
cockpit-docker 137-1.fc25 -> 138-1.fc25
cockpit-networkmanager 137-1.fc25 -> 138-1.fc25
cockpit-ostree 137-1.fc25 -> 138-1.fc25
cockpit-system 137-1.fc25 -> 138-1.fc25
emacs-filesystem 1:25.1-3.fc25 -> 1:25.2-1.fc25
kernel 4.10.11-200.fc25 -> 4.10.12-200.fc25
kernel-core 4.10.11-200.fc25 -> 4.10.12-200.fc25
kernel-modules 4.10.11-200.fc25 -> 4.10.12-200.fc25
nspr 4.13.1-1.fc25 -> 4.14.0-2.fc25
nss 3.29.3-1.1.fc25 -> 3.30.2-1.0.fc25
nss-softokn 3.29.5-1.0.fc25 -> 3.30.2-1.0.fc25
nss-softokn-freebl 3.29.5-1.0.fc25 -> 3.30.2-1.0.fc25
nss-sysinit 3.29.3-1.1.fc25 -> 3.30.2-1.0.fc25
nss-tools 3.29.3-1.1.fc25 -> 3.30.2-1.0.fc25
nss-util 3.29.5-1.0.fc25 -> 3.30.2-1.0.fc25
oci-systemd-hook 1:0.1.6-1.gitfe22236.fc25 -> 1:0.1.7-1.git1788cf2.fc25
python3 3.5.3-4.fc25 -> 3.5.3-5.fc25
python3-libs 3.5.3-4.fc25 -> 3.5.3-5.fc25
system-python 3.5.3-4.fc25 -> 3.5.3-5.fc25
system-python-libs 3.5.3-4.fc25 -> 3.5.3-5.fc25
vim-minimal 2:8.0.562-1.fc25 -> 2:8.0.586-1.fc25
Added:
binutils-2.26.1-1.fc25.x86_64
deltarpm-3.6-17.fc25.x86_64
dnf-conf-1.1.10-6.fc25.noarch
dnf-plugins-core-0.1.21-5.fc25.noarch
dwz-0.12-2.fc24.x86_64
elfutils-0.168-1.fc25.x86_64
fpc-srpm-macros-1.0-1.fc25.noarch
gdb-headless-7.12.1-48.fc25.x86_64
ghc-srpm-macros-1.4.2-4.fc25.noarch
gnat-srpm-macros-4-1.fc25.noarch
go-srpm-macros-2-7.fc25.noarch
hawkey-0.6.4-3.fc25.x86_64
libcomps-0.1.7-5.fc25.x86_64
libipt-1.5-1.fc25.x86_64
ocaml-srpm-macros-2-4.fc24.noarch
patch-2.7.5-3.fc24.x86_64
perl-srpm-macros-1-20.fc25.noarch
python-srpm-macros-3-12.fc25.noarch
python3-dnf-1.1.10-6.fc25.noarch
python3-dnf-plugins-core-0.1.21-5.fc25.noarch
python3-hawkey-0.6.4-3.fc25.x86_64
python3-iniparse-0.4-20.fc25.noarch
python3-libcomps-0.1.7-5.fc25.x86_64
python3-librepo-1.7.18-3.fc25.x86_64
python3-pygpgme-0.3-18.fc25.x86_64
qt5-srpm-macros-5.7.1-1.fc25.noarch
redhat-rpm-config-45-1.fc25.noarch
rpm-build-4.13.0.1-1.fc25.x86_64
rpm-plugin-systemd-inhibit-4.13.0.1-1.fc25.x86_64
unzip-6.0-31.fc25.x86_64
zip-3.0-16.fc24.x86_64
What's bringing in all of this stuff?
Dusty
7 years, 1 month
