#128: Extra ifcfg file in the cloud base image
--------------------+--------------------
Reporter: kushal | Owner: kushal
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords:
--------------------+--------------------
We now have an extra ifcfg-ens3 file in cloud base image, that is
resulting the failure of the network service in the image.
For more details please read
https://lists.fedoraproject.org/pipermail/cloud/2015-October/005939.html
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/128>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
This is just a reminder that Daylight savings time has hit many of us.
In the past few cycles we have decided to stick with the same UTC time.
We'll be doing that again this time so the meeting will stay at 17:00
UTC. Click the link below to see what that means for you:
https://apps.fedoraproject.org/calendar/cloud/
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2015-11-04 from 17:00:00 to 18:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://apps.fedoraproject.org/calendar/meeting/1999/
#132: Fedora AMIs should use corresponding s3 mirrors
------------------------------+--------------------
Reporter: voltagex | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: Cloud Base Image | Keywords:
------------------------------+--------------------
Currently, Fedora AMIs on Amazon EC2 are still using the mirror list. This
results in slow download speeds for dnf and a sub-par experience
https://lists.stg.fedoraproject.org/archives/list/infrastructure@lists.fedo…
is the best list of these mirrors I could find.
Changing this would require either
* changing the template that builds the AMIs for each region
* making the mirrorlist service smart enough to detect requests from AWS
and send them to the correct region
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/132>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
We found out today that all RC images for Atomic are broken. They are
building against a much older yum repo (the beta repos) and thus have
a very old systemd, which has some breakages with ostree. dgilmore and
maxamillion have done some investigation and believe they have
somewhat pinpointed the issue, although I don't know if they know of
an exact fix yet.
This would have been caught by tunir/autocloud but tunir skips this
test for atomic images. I have submitted a PR for it to not do that [1].
Right now the last booting atomic image is TC11. If we don't do
another compose then we won't have an atomic image for release.
Dusty
[1] - https://github.com/kushaldas/tunirtests/pull/6