dustymabe added a new comment to an issue you are following:
``
another option here is to slightly change how mirrormanager tracks what mirrors
have the 2 week atomic content. Right now it's all tracked as part of one "2WA"
module so if any mirror has any 2W content then it passes and will be
A new update of Fedora Cloud Atomic Host has been released and can be
downloaded at:
Images can be found here:
https://getfedora.org/en/cloud/download/atomic.html
Respective signed CHECKSUM files can be found here:
chrismurphy added a new comment to an issue you are following:
``
dwalsh mentioned the a way to flip between them
https://www.spinics.net/linux/fedora/fedora-cloud/msg07620.html
Missing from that sequence is actually configuring the new storage if it
doesn't exist yet.
I think putting custom
vgoyal added a new comment to an issue you are following:
``
I think you will have to destroy all images and containers stored in overlay
and then setup devicemapper from that freed space.
Having said that, in theory a path might exist. If overlay2 does not use all
free space, then in theory,
jberkus added a new comment to an issue you are following:
``
OK, so regarding (2), a follow-up question:
Is there any mechanism by which I can take a running system configured for
overlay (with two partitons) and convert it to devicemapper without:
a) needing to re-partition?
b) needing to
vgoyal added a new comment to an issue you are following:
``
Sharing rootfs and overlay2 makes configuration easy. Agreed with that. But 2)
is a requirement. If overlay2 does not work for a user, we want them an option
to go back to devicemapper.
overlay2 is fairly new and is not fully posix
jberkus added a new comment to an issue you are following:
``
So, there's two questions here:
Aha, thanks. Seems like DOCKER_ROOT_VOLUME should default to "on" then if
we're going to do partitioning. That leaves us with two questions:
1) What do we feel is the best default settup for an
vgoyal added a new comment to an issue you are following:
``
> So I just did a test of using OverlayFS on Fedora Atomic 25 as a cloud-init
> option. This resulted in having the whole disk as one volume, shared with
> the overlay, instead of multiple partitions. That's the desireable default
>
vgoyal added a new comment to an issue you are following:
``
if you use DOCKER_ROOT_VOLUME=yes, that will create a new logical volume,
create xfs filesystem on it, and mount it on /var/lib/docker/. And now if you
are using overlay2 driver, it should put all images, containers and volumes on
dustymabe added a new comment to an issue you are following:
``
> Except that docker storage can still cannibalize your rootfs, because in
> Atomic we put volumes and images on the rootfs. So it's never been an
> effective measure.
That is why the DOCKER_ROOT_VOLUME option was added to
dustymabe added a new comment to an issue you are following:
``
> So I just did a test of using OverlayFS on Fedora Atomic 25 as a cloud-init
> option. This resulted in having the whole disk as one volume, shared with
> the overlay, instead of multiple partitions. That's the desireable default
vgoyal added a new comment to an issue you are following:
``
Upstream dokcer-storage-setup will continue to have devicemapper as default
graph driver. So for this to work properly on atomic host, we probably require
following two options set in /etc/sysconfig/docker-storage-setup.
jberkus added a new comment to an issue you are following:
``
So I just did a test of using OverlayFS on Fedora Atomic 25 as a cloud-init
option. This resulted in having the whole disk as one volume, shared with the
overlay, instead of multiple partitions. That's the desireable default setup,
vgoyal added a new comment to an issue you are following:
``
If we want to give all the free space to docker by default, then we will also
have to set.
DOCKER_ROOT_VOLUME_SIZE=100%FREE
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/186
walters reported a new issue against the project: `atomic-wg` that you are
following:
``
walters: so there are two options. One is changing default to
overlay2, which is common across all variants
walters: another new option is specifying where the storage from
overlayfs comes from. Does it
Kushal, Sayan,
We don't have a fedmsg from autocloud so we can't do the release.
https://apps.fedoraproject.org/datagrepper/raw?topic=org.fedoraproject.prod.autocloud.compose.complete=1278000_per_page=1=1
Can you look in to this?
Thanks
Dusty
___
dustymabe added a new comment to an issue you are following:
``
>>
>> We were also affected by this issue and spent a huge amount of time figuring
>> out why the installation fails. Are there any updates from releng?
>
> hi @nightvisi0n - due to the recent holidays we didn't have much time to
dustymabe added a new comment to an issue you are following:
``
> Yeah, merged /boot with ostree doesn't quite work for us yet. See
> https://github.com/ostreedev/ostree/pull/215
hmm. and that is only an issue on UEFI because I've been doing legacy boot
without a /boot partition for a while
walters added a new comment to an issue you are following:
``
Yeah, merged /boot with ostree doesn't quite work for us yet. See
https://github.com/ostreedev/ostree/pull/215
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/185
dustymabe added a new comment to an issue you are following:
``
I'll note that if I give myself a boot partition (i.e. a filesystem mounted at
`/boot`) then things work ok:
```text
# Partition info
zerombr
clearpart --all
reqpart
part pv.01 --grow
volgroup atomicos pv.01
logvol / --size=3000
dustymabe added a new comment to an issue you are following:
``
Hey @walters I created an
[updates.img](https://dustymabe.fedorapeople.org/fixuefi-updates.img) with your
change in it and I'm seeing an issue where the install succeeds but the
grub.cfg in the efi partition seems to have the
dustymabe added a new comment to an issue you are following:
``
> We were also affected by this issue and spent a huge amount of time figuring
> out why the installation fails. Are there any updates from releng?
hi @nightvisi0n - due to the recent holidays we didn't have much time to work
sayanchowdhury added a new comment to an issue you are following:
``
The old boxes has been shutdown and now autocloud is showing the correct number
of images.
Going ahead and closing the issue.
``
To reply, visit the link below or just reply to this email
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170106.0/compose/CloudImages/x86_64/images/
please give these images a spin. There was one failure in the autocloud tests.
I'm investigating that now.
Dusty
___
cloud mailing list
24 matches
Mail list logo
