Re: Changing file system for Cloud images to ext4, xfs or something custom

[Dusty Mabe]

On 4/9/24 10:00, Neal Gompa wrote:
> On Tue, Apr 9, 2024 at 9:53 AM Tadej Janež  wrote:
>>
>> Hey Fedora Cloud WG!
>>
>> Firstly, thanks for providing Fedora for the popular cloud providers!
>>
>> Since Fedora 35, the Fedora Cloud images use btrfs by default [1].
>> For my deployments, I would like to use ext4 or xfs, so my question
>> are:
>> 1) Is it possible to change the root file system at deploy time?
>> 2) If not, how could one change the cloud images to use a different
>> root file system?
>>
> 
> It is not possible to change at deployment time, you would need to
> build your own custom images.

We do have Fedora CoreOS, which may or may not fit your use case (i.e.
run software in containers, automatic updates, rpm-ostree as the
update mechanism), which can re-provision the root filesystem on first
boot and does provide images for various clouds:

- https://fedoraproject.org/coreos/download?stream=stable
- 
https://docs.fedoraproject.org/en-US/fedora-coreos/storage/#_reconfiguring_the_root_filesystem

This may or may not be an option for you, but figured I'd mention.

> 
> Our images are now defined here:
> https://pagure.io/fedora-kiwi-descriptions/blob/rawhide/f/teams/cloud/cloud.xml
> 
> If you want to use something else, you'd want to have your own version
> of the definitions and modify that file to use the filesystem of your
> choice.
> 
> Is there a particular reason you want to use ext4 or xfs for your
> rootfs? Typically the pattern we see is that people attach a secondary
> volume or use S3 and put their data on that instead of the rootfs.
> 
> 
> 
--
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Heads-up / for discussion: dnf not working with 1G of RAM or less

[Dusty Mabe]

On 8/22/22 20:44, Adam Williamson wrote:
> Hey folks! I apologize for the wide distribution, but this seemed like
> a bug it'd be appropriate to get a wide range of input on.
> 
> There's a bug that was proposed as an F37 Beta blocker:
> https://bugzilla.redhat.com/show_bug.cgi?id=1907030
> 
> it's quite an old bug, but up until recently, the summary was
> apparently accurate - dnf would run out of memory with 512M of RAM, but
> was OK with 1G. However, as of quite recently, on F36 at least (not
> sure if anyone's explicitly tested F37), dnf operations are commonly
> failing on VMs/containers with 1G of RAM due to running out of RAM and
> getting OOM-killed.
> 
> There's some discussion in the bug about what might be causing this and
> potential ways to resolve it, and please do dig into/contribute to that
> if you can, but the other question here I guess is: how much do we care
> about this? How bad is it that you can't reliably run dnf operations on
> top of a minimal Fedora environment with 1G of RAM?

I think we need to stop thinking about this as just a single computer
problem.

In a containerized world you could have numerous containers running dnf
operations on a machine at any given time. Making the dnf operations take
less memory means we'll hit many fewer issues as single machines are
able to run many dnf operations at a given moment.

> 
> This obviously has some overlap with our stated hardware requirements,
> so here they are for the record:
> 
> https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/welcome/Hardware_Overview/
> 
> that specifies 2GB as the minimum memory for "the default
> installation", by which I think it's referring to a default Workstation
> install, though this should be clarified. But then there's a "Low
> memory installations" boxout, which suggests that "users with less than
> 768MB of system memory may have better results performing a minimal
> install and adding to it afterward", which kinda is recommending that
> people do exactly the thing that doesn't work (do a minimal install
> then use dnf on it), and implying it'll work.
> 
> After some consideration I don't think it makes sense to take this bug
> as an F37 blocker, since it already affects F36, and that's what I'll
> be suggesting at the next blocker review meeting. However, it does seem
> a perfect candidate for prioritized bug status, and I've nominated it
> for that.
> 
> I guess if folks can chime in with thoughts here and/or in the bug
> report, maybe a consensus will emerge on just how big of an issue this
> is (and how likely it is to get fixed). There will presumably be a
> FESCo ticket related to prioritized bug status too.
> 
> Thanks folks!
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [Fedocal] Reminder meeting : Fedora Cloud Workgroup

[Dusty Mabe]

Hi Cloud WG,

This week I'd like to add an agenda item to discuss a potential change to the 
way we handle the default hostname in Fedora.

Thanks!
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Cloud tooling (sub)SIG?

[Dusty Mabe]

On 11/18/21 5:39 AM, Mikel Olasagasti wrote:
> Hi all,

Hi Mikel, Nice to meet you.

> 
> First mail to fedora-cloud, so I'll present myself as a Red Hat
> employee that contributes to Fedora in my free time.
> 
> Last week I contacted Major Hayden about $SUJECT and he suggested
> discussing it on the list, so here I am.
> 
> Some weeks ago I packaged `doctl`[1], the official CLI for
> DigitalOcean. Also sent a PR for `linode-cli`[2] and updated some
> Google API packages[3] to fix some other packages. Doing some new
> package reviews, I found Major was working on `vultr-cli`[4] for Vultr
> and `hcloud`[5] for Hetzner. I know he is also working on packaging
> major public cloud CLI and API packages.
> 
> For me having these packages, and others, improves user experience
> with Fedora, as we avoid users having to go GitHub or alike and
> download some binary while we also provide a way to keep them updated.

I agree. Thank you for packaging doctl.

> 
> I wrote Major asking if a new SIG or sub-SIG (is this a thing?) for
> public cloud tools would be interesting and he pointed me to
> fedora-cloud for further discussion.
> 
> For me it is, as we could have the following:
> 
> - A SIG packager group that could ease permission assignment rather
> than have to go package by package or the need to be part of a larger
> group like go-sig to be able to maintain some of the packages.
> - A dashboard at packager-dashboard.fp.o to show the status of packages.
> - Single Point of Contact in case any of the providers wants to
> contact/suggest something about their tooling in Fedora.
> 
> I might be wrong due to ignorance, but I understand fedora-cloud as a
> SIG to provide Fedora in the clouds and that’s why I was suggesting a
> new SIG. If this effort can be part of fedora-cloud because it shares
> the mission, then I’m in the correct forum.

This "effort" sounds amazing. I don't personally care if it is a new SIG
or part of the cloud SIG. Unfortunately I don't have much to offer other than
guidance and moral support. I can definitely help test the packages on the
clouds I use too.

Either way thanks for reaching out and trying to build a community for this
effort in Fedora.

Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Any reason fedora server isn't uploaded to all regions?

[Dusty Mabe]

On 10/15/21 12:19 PM, Carl Hörberg wrote:
> Didn't know about the marketplace option, thanks!
> 
> Not sure if there's any difference or release delay with the marketplace 
> option? In that case the regions we're missing are:
> 
> Canada (Montreal)
> EU (Stockholm)
> EU (Paris)
> EU (Milan)
> Asia Pacific (Mumbai)
> Asia Pacific (Seoul)
> Asia Pacific (Osaka)
> Asia Pacific (Hong Kong) SAR
> Middle East (Bahrain)
> Africa (Cape Town)

Can you open an issue at pagure.io/cloud-sig for these missing regions?

Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Any reason fedora server isn't uploaded to all regions?

[Dusty Mabe]

On 10/15/21 10:25 AM, Carl Hörberg wrote:
> Hi, we looking into moving from ubuntu to Fedora server for thousands of our 
> servers on AWS, but I wondering if the AWS images could be uploaded to all 
> AWS regions instead of just the few? Happy to contribute financially or 
> technically if needed. 

Hey Carl,

That's awesome news! Glad to have you in the Fedora community.

Hmm. Is there a particular region you're interested in? We currently upload to:

US East (N. Virginia)   ami-09e08e82e8f927ba4   
US East (Ohio)  ami-04d6c97822332a0a6   
US West (Oregon)ami-00a4fdd3db8bb2851   
US West (N. California) ami-0d828c0715f284b51   
EU West (Ireland)   ami-03a2d2ea7d3d04d8c   
EU Central (Frankfurt)  ami-0efd1b90025adc1a0   
EU West (London)ami-034794b0310a1d8b7   
Asia Pacific SE (Singapore) ami-0de1a1ee38e9d0267   
Asia Pacific NE (Tokyo) ami-0eaac58066939c2ff   
Asia Pacific SE (Sydney)ami-0627bcdb0bea81d1b   
South America East (Sāo Paulo)  ami-0231fa741ad2e0a08   
Asia Pacific (Seoul)ami-08b7a97648409e75b   
Asia Pacific (Mumbai)   ami-01d3bd808e1fd393c   
Canada (Central) ami-005b80509885a0ea1


See the links at the bottom of the page on https://alt.fedoraproject.org/cloud/


Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora website - revamp

[Dusty Mabe]

On 6/21/21 2:31 PM, Pawel Zelawski wrote:
> Dear team,
> we decided it's time to rethink our needs and redesign Fedora main website 
> from scratch.
> I would like to encourage your team to take a part in this initiative and 
> work on this together as we need to make sure that we have everybody on board 
> and all needs are taken into consideration.
> 
> Based on initial input I gather from Fedora forum and meeting with Matthew I 
> prepared one page with summary of what we are going to do and it's available 
> here https://fedoraproject.org/wiki/Websites/Fedora_Website_Revamp
> It's possible I'll move it to other place in the future but for now it will 
> be our workspace.
> 
> As a short term strategy I would like you to choose one representative from 
> your team for upcoming kick-off meeting with other stakeholders and send me 
> directly details like name, Feroda ID and e-mail address. It will be much 
> easier for me to contact chosen person having this. Please try to do this by 
> 30th June. I'm aware holiday period started and probably not everyone will be 
> available but let's try to do our best and push forward this exciting 
> initiative :)

Hey Pawel,

From Fedora Cloud we'll nominate David Duncan (davdunc, davd...@gmail.com).

> When I have all participants gathered I'll try to find common slot to 
> organize session for us. Agenda will be included in invitation.
> Main goal of this kick-off will be to discuss known facts, go through goals, 
> assumptions and requirements and also plan next steps for next couple of 
> weeks.
> I'll propose long term strategy, approach and wider plan after meeting with 
> all of you.
> 
> Please read in advance 
> https://fedoraproject.org/wiki/Websites/Fedora_Website_Revamp and if you 
> already have some requests, suggestion please send it to your representative 
> and then each person can send it to me before kick-off. Taking into 
> consideration we will have huge amount of stakeholders I don't see other way 
> to work on this than having one person from each team, I hope you understand.
> 
> Looking forward to work with all of you.
> Stay safe!
> 
> 
> --
> Pawel Zelawski
> ___
> cloud mailing list -- cloud@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
> 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

New Meeting Time

[Dusty Mabe]

We're going to try out a new meeting time to try to overcome existing conflicts.

The new time is on Thursdays (starting July 8th) at 1500UTC.

See https://pagure.io/cloud-sig/issue/333

See you in the meeting!
Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora Cloud Meeting Minutes 2021-06-22

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-06-22/fedora_cloud_meeting.2021-06-22-15.59.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-06-22/fedora_cloud_meeting.2021-06-22-15.59.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-06-22/fedora_cloud_meeting.2021-06-22-15.59.log.html

===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 15:59:18 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-06-22/fedora_cloud_meeting.2021-06-22-15.59.log.html
.



Meeting summary
---
* roll call  (dustymabe, 15:59:24)

* Action items from last meeting  (dustymabe, 16:04:58)

* new meeting time  (dustymabe, 16:05:32)
  * LINK: https://pagure.io/cloud-sig/issue/333   (dustymabe, 16:05:37)
  * AGREED: we'll move the meeting one hour earlier and to thursday
(bi-weekly on thursday at 1500 UTC)  (dustymabe, 16:20:58)

* Fedora-34 nightly images in AWS do not boot  (dustymabe, 16:21:44)
  * LINK: https://pagure.io/cloud-sig/issue/331   (dustymabe, 16:21:50)
  * LINK:
https://pagure.io/pungi-fedora/blob/f34/f/fedora-final.conf#_374
(cmurf[m], 16:26:13)
  * LINK: https://pagure.io/pungi-fedora/blob/f34/f/fedora-cloud.conf
(dustymabe, 16:27:38)
  * LINK:
https://pagure.io/pungi-fedora/blob/f34/f/fedora-cloud.conf#_225
(cmurf[m], 16:33:57)
  * LINK:
https://pagure.io/pungi-fedora/blob/main/f/fedora-cloud.conf#_226
(cmurf[m], 16:34:04)
  * we think we should be able to fix this problem with a patch to
pungi-fedora  (dustymabe, 16:36:24)
  * ACTION: Eighth_Doctor to submit PR to pungi-fedora to fix BIOS
booting issues for f34 cloud nightlights  (dustymabe, 16:39:26)

* updates on f35 changes  (dustymabe, 16:40:03)
  * change to btrfs has been implemented in rawhide cloud image builds -
working as expected  (dustymabe, 16:41:53)
  * hitting some issues getting hybrid boot + GPT working - still
working through the issues  (dustymabe, 16:46:12)

* sparse disk images or not  (dustymabe, 16:46:28)
  * LINK:

https://dustymabe.com/2013/06/11/recover-space-from-vm-disk-images-by-using-discardfstrim/
(dustymabe, 16:51:57)

* open floor  (dustymabe, 16:59:20)
  * ACTION: cmurf to make a ticket about image creation optimizations
(Eighth_Doctor, 17:08:20)

* New lead for Cloud WG  (Eighth_Doctor, 17:09:04)
  * ACTION: dustymabe to file ticket and announce change to davdunc as
Cloud WG lead  (Eighth_Doctor, 17:16:49)

Meeting ended at 17:18:26 UTC.




Action Items

* Eighth_Doctor to submit PR to pungi-fedora to fix BIOS booting issues
  for f34 cloud nightlights
* cmurf to make a ticket about image creation optimizations
* dustymabe to file ticket and announce change to davdunc as Cloud WG
  lead




Action Items, by person
---
* davdunc
  * dustymabe to file ticket and announce change to davdunc as Cloud WG
lead
* dustymabe
  * dustymabe to file ticket and announce change to davdunc as Cloud WG
lead
* Eighth_Doctor
  * Eighth_Doctor to submit PR to pungi-fedora to fix BIOS booting
issues for f34 cloud nightlights
* **UNASSIGNED**
  * cmurf to make a ticket about image creation optimizations




People Present (lines said)
---
* dustymabe (121)
* Eighth_Doctor (107)
* cmurf[m] (78)
* davdunc (19)
* dcavalca (13)
* zodbot (13)
* adamw (2)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora Cloud Meeting Minutes 2021-06-08

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-06-08/fedora_cloud_meeting.2021-06-08-16.07.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-06-08/fedora_cloud_meeting.2021-06-08-16.07.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-06-08/fedora_cloud_meeting.2021-06-08-16.07.log.html

===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 16:07:06 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-06-08/fedora_cloud_meeting.2021-06-08-16.07.log.html



Meeting summary
---
* roll call  (dustymabe, 16:07:12)

* Action items from last meeting  (dustymabe, 16:16:11)
  * davdunc has submitted the GPT + hybrid boot proposal:
https://fedoraproject.org/wiki/Changes/FedoraCloudHybridBoot
(dustymabe, 16:17:57)
  * still debugging f34 cloud nightly image boot issues  (dustymabe,
16:21:04)

* topics for this meeting  (dustymabe, 16:22:10)
  * LINK: https://pagure.io/cloud-sig/issues   (dustymabe, 16:22:28)
  * LINK: https://pagure.io/cloud-sig/issue/325   (King_InuYasha,
16:22:56)
  * LINK: https://pagure.io/cloud-sig/issue/329   (King_InuYasha,
16:23:59)
  * LINK: https://pagure.io/cloud-sig/issue/320   (King_InuYasha,
16:24:37)

* Please publish Fedora AMI to af-south-1  (dustymabe, 16:25:08)
  * LINK: https://pagure.io/cloud-sig/issue/325   (dustymabe, 16:25:12)
  * LINK:

https://aws.amazon.com/blogs/security/setting-permissions-to-enable-accounts-for-upcoming-aws-regions/
(davdunc, 16:28:20)

* Add Ignition support to Fedora Cloud  (dustymabe, 16:34:54)
  * LINK: https://pagure.io/cloud-sig/issue/320   (dustymabe, 16:34:57)

* fedora cloud image: enable ipv6 (accept RAs by default)  (dustymabe,
  16:42:51)
  * LINK: https://pagure.io/cloud-sig/issue/320   (dustymabe, 16:42:54)

* systemd-oomd by default  (dustymabe, 16:46:04)
  * LINK: https://pagure.io/cloud-sig/issue/324   (dustymabe, 16:46:09)
  * LINK: https://github.com/kubernetes/kubernetes/issues/53533 tracks
swap support for k8s  (dcavalca, 16:53:51)
  * AGREED: for f35 fedora cloud we will enable swap-on-zram and
sytemd-oomd  (dustymabe, 16:56:52)

* Btrfs as the default filesystem\  (dustymabe, 16:57:42)
  * LINK: https://pagure.io/cloud-sig/issue/308   (dustymabe, 16:57:46)
  * AGREED: the cloud wg will move to btrfs for the f35 unless techincal
hurdles are hit  (dustymabe, 17:24:30)

* open floor  (dustymabe, 17:24:36)

Meeting ended at 17:25:50 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dustymabe (128)
* King_InuYasha (64)
* davdunc (34)
* Eighth_Doctor (30)
* michel (29)
* jdoss (24)
* cmurf (23)
* zodbot (22)
* dcavalca (14)
* cmurf[m] (7)
* cyberpear (2)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora Cloud Meeting Minutes 2021-05-11

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-05-11/fedora_cloud_meeting.2021-05-11-15.58.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-05-11/fedora_cloud_meeting.2021-05-11-15.58.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-05-11/fedora_cloud_meeting.2021-05-11-15.58.log.html

===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 15:58:58 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-05-11/fedora_cloud_meeting.2021-05-11-15.58.log.html
.



Meeting summary
---
* roll call  (dustymabe, 15:59:03)

* Action items from last meeting  (dustymabe, 16:06:45)
  * thank you nb for handing out badges!  (dustymabe, 16:06:58)

* open floor  (dustymabe, 16:07:32)
  * the GCP cloud agent rpm was merged into rawhide so that GCP cloud
image should now no longer use cloud-init  (dustymabe, 16:08:04)
  * LINK: https://src.fedoraproject.org/rpms/libdnf-plugin-txnupd
(Eighth_Doctor, 16:13:07)
  * LINK:
https://build.opensuse.org/package/show/devel:kubic:ignition/combustion
(Eighth_Doctor, 16:35:33)
  * LINK: https://pagure.io/cloud-sig/issue/308   (Eighth_Doctor,
16:38:31)
  * LINK: https://pagure.io/cloud-sig/issue/329   (jdoss, 16:44:30)

Meeting ended at 16:46:49 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* Eighth_Doctor (61)
* dustymabe (46)
* jdoss (11)
* zodbot (10)
* davdunc (7)
* nb (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora 34 GCP image

[Dusty Mabe]

FYI - I published the Fedora 34 GCP image to the `fedora-cloud` project in GCP.

See https://pagure.io/cloud-sig/issue/328 for more details. 

Currently you do have to provide cloud-init userdata to the instance (via the 
user-data key).
This hopefully won't be the case once we include the newly added google compute 
enging config rpm.
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora Cloud Meeting Minutes 2021-04-27

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-04-27/fedora_cloud_meeting.2021-04-27-15.59.html
  
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-04-27/fedora_cloud_meeting.2021-04-27-15.59.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-04-27/fedora_cloud_meeting.2021-04-27-15.59.log.html
  

===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 15:59:56 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-04-27/fedora_cloud_meeting.2021-04-27-15.59.log.html
.



Meeting summary
---
* roll call  (dustymabe, 16:00:01)

* fedora cloud test day  (dustymabe, 16:02:20)
  * LINK:
https://communityblog.fedoraproject.org/fedora-linux-34-cloud-test-day/
(dustymabe, 16:02:57)
  * test day results are at
http://testdays.fedorainfracloud.org/events/112  (dustymabe,
16:03:15)
  * ACTION: nb to hand out Fedora Badges to everyone who participated in
the test day  (dustymabe, 16:05:02)

* packaging cloud agents for GCP  (dustymabe, 16:05:37)
  * LINK: https://pagure.io/cloud-sig/issue/313   (dustymabe, 16:05:43)
  * GCP packaging reviews from ericedens has been approved. pending
import and build in rawhide  (dustymabe, 16:07:32)

* cloud-init doesn't properly forward nameservers to systemd-resolved
  (dustymabe, 16:08:56)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1950770
(dustymabe, 16:09:01)

* triage cloud-init bugs  (dustymabe, 16:17:16)
  * LINK:

https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__=cloud-init_id=11836878=Fedora_format=advanced
(dustymabe, 16:17:28)

* open floor  (dustymabe, 16:21:50)

Meeting ended at 16:25:58 UTC.




Action Items

* nb to hand out Fedora Badges to everyone who participated in the test
  day




Action Items, by person
---
* nb
  * nb to hand out Fedora Badges to everyone who participated in the
test day
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dustymabe (47)
* otubo (15)
* zodbot (14)
* mcatanzaro (7)
* Eighth_Doctor (4)
* nb (3)
* cyberpear (1)
* michaelgugino (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fix fallocate issue on cloud-init 19.4 for Fedora 33 cloud images

[Dusty Mabe]

On 4/26/21 10:17 AM, Federico Ressi wrote:
> Hello all,

Hey Frederico,


> 
> I am writing to this list because I found out F33 cloud image cloud init 
> support for creating swap files looks to be broken probably because of a 
> known Linux 5.7+ kernel issue [1].
> 
> The problem is cloud-init is trying to create a new swap file by using 
> fallocate command that is not working well (kernel is complaining the file 
> has holes when executing swapon command just later). The easy workaround for 
> this issue is to use dd command instead of fallocate command in cloud-init.
> 
> Because I don't know the whole procedure required for submitting a patch I am 
> writing to you in the hope you can help me in having the F33 cloud image 
> fixed.
> Please find attached to this e-mail the simple fix for cloud init 19.4 I just 
> wrote. The patch should apply the procedure documented in Fedora docs [2]

Do you know if this is fixed in upstream cloud-init already? Fedora 34, which 
is about to be released tomorrow has cloud-init-20.4-1.fc34.
> 
> Thank you in advance.
> Federico
> 
> [1] https://marcelhauri.ch/blog/swapon-swapfile-has-holes/ 
>  
> [2] 
> https://docs.fedoraproject.org/en-US/Fedora/14/html/Storage_Administration_Guide/s2-swap-creating-file.html
>  
> 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: systemd update breaks DNS resolution on Fedora 33 cloud instances

[Dusty Mabe]

On 1/15/21 2:50 PM, Tadej Janež wrote:
> Hi all!

Hey Tadej

> 
> I was recently hit by this and it took me some time to figure out what
> was going on.

Thanks for sharing and for investigating.

> 
> I provisioned a fresh Fedora 33 cloud instance on DigitalOcean.
> After completing the initial upgrade via 'dnf update' and rebooting the
> system, DNS resolution stopped working.
> 
> I did a little debugging and saw that no DNS servers were configured:
> 
> $ resolvectl dns
> Global:
> Link 2 (eth0):
> Link 3 (eth1):
> $ resolvectl status
> Global
>Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
> resolv.conf mode: stub 
> 
> Link 2 (eth0)
> Current Scopes: LLMNR/IPv4 LLMNR/IPv6 
>  Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS
> DNSSEC=no/unsupported
> 
> Link 3 (eth1)
> 
> I was confused how could that happen since running 'dnf update' on the
> first boot clearly required DNS resolution to work.
> 
> It turns out a recent systemd update, namely systemd-246.7-2.fc33
> (https://bodhi.fedoraproject.org/updates/FEDORA-2020-3616681a70),
> includes this commit:
> https://src.fedoraproject.org/rpms/systemd/c/ed795fb1fc9a2c20ebcac34bdf7e7c7ae17322a2?branch=f33
> which removes the fallback DNS server list (i.e. Cloudflare's and/or
> Google's DNS servers) due to concerns over DNS requests being
> personally identifying information (PII) in the sense of GDPR?
> 
> In combination with NetworkManager's DNS server handling being disabled
> via cloud-init:
> 
> $ cat /etc/NetworkManager/conf.d/99-cloud-init.conf 
> # Created by cloud-init on instance boot automatically, do not edit.
> #
> [main]
> dns = none
> 
> this results in no DNS servers being configured on the system.
> 
> The consequence is that Fedora 33 cloud instances are broken after
> updating the systemd package to version 246.7-2.fc33.

There is a bug in cloud-init where it doesn't seem to properly handle
systemd-resolved. It edits /etc/resolv.conf directly (which is already
managed by systemd-resolved) and thus the configuration gets lost
after the first boot.

https://bugzilla.redhat.com/show_bug.cgi?id=1950770

I just tried to reproduce on DigitalOcean and it seems like maybe DO recently
added a workaround for this (i'm not able to reproduce). I see this workaround:

# cat lib/cloud/instances/242253247/boothooks/resolver-fix
#!/bin/sh -x
# DigitalOcean resolver fixup script
[ -f /etc/systemd/resolved.conf ] || exit 0
logger -t DigitalOcean 'writing resolvers  to /etc/systemd/resolved.conf'
printf "[Resolve]\nDNS=67.207.67.2 67.207.67.3\n" > /etc/systemd/resolved.conf


Can you try again and see if a new f33 instance you start is OK?

> 
> (I haven't checked but if Fedora 34 cloud images include this version
> of systemd, then DNS resolution won't work even on first boot.)

Thanks, I'll look into it.

> 
> Please advise on the best steps to fix this issue
> 
> Regards,
> Tadej
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora Cloud Meeting Minutes 2021-03-30

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-03-30/fedora_cloud_meeting.2021-03-30-16.00.html
  
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-03-30/fedora_cloud_meeting.2021-03-30-16.00.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-03-30/fedora_cloud_meeting.2021-03-30-16.00.log.html
  

===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 16:00:51 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-03-30/fedora_cloud_meeting.2021-03-30-16.00.log.html
.



Meeting summary
---
* roll call  (dustymabe, 16:01:01)

* open floor  (dustymabe, 16:06:25)
  * the server WG has approached us again about possible
collaboration/merging. There seems to be more interest this time.
Meeting minutes from a meeting a few weeks back:  (dustymabe,
16:07:17)
  * LINK:

https://meetbot.fedoraproject.org/fedora-meeting/2021-03-03/fedora-server.2021-03-03-18.04.html
(dustymabe, 16:07:28)
  * please test out the 34 beta cloud images. grab them here
https://alt.fedoraproject.org/prerelease/index.html  (dustymabe,
16:10:12)
  * LINK: https://src.fedoraproject.org/rpms/libdnf-plugin-txnupd
(Eighth_Doctor, 16:13:47)
  * LINK: https://pagure.io/fedora-server/issue/10   (dustymabe,
16:15:27)

Meeting ended at 16:20:42 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dustymabe (32)
* zodbot (9)
* Eighth_Doctor (7)
* cyberpear (7)
* michaelgugino (7)
* copperi_ (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora Cloud Meeting Minutes 2020-12-08

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-12-08/fedora_cloud_meeting.2020-12-08-16.02.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-12-08/fedora_cloud_meeting.2020-12-08-16.02.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-12-08/fedora_cloud_meeting.2020-12-08-16.02.log.html

===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 16:02:37 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-12-08/fedora_cloud_meeting.2020-12-08-16.02.log.html
.



Meeting summary
---
* roll call  (dustymabe, 16:02:42)

* Action items from last meeting  (dustymabe, 16:04:46)

* OpenStack cloud image: include and enable qemu-guest-image
  (dustymabe, 16:05:10)
  * LINK: https://pagure.io/cloud-sig/issue/319   (dustymabe, 16:05:19)
  * AGREED: since the unit appears to be inert on any system that can't
take advantage of the service, we propose to add qemu-guest-agent to
the base package set. We won't include it on GCP since we have a
separate image for GCP already. In the future we may make other
images specific to cloud providers, in which case we'll also remove
it from those variants.  (dustymabe, 16:20:33)

* open floor  (dustymabe, 16:21:33)
  * LINK: https://pagure.io/cloud-sig/issue/320   (danken, 16:31:27)

* fedora cloud image: enable ipv6 (accept RAs by default)  (dustymabe,
  16:32:02)
  * LINK: https://pagure.io/cloud-sig/issue/320   (dustymabe, 16:32:08)
  * AGREED: we should/will remove networking configuration from the
cloud images and let NetworkManager default configs apply, which
should get us in a situation where ipv6 is no longer ignored.
(dustymabe, 16:39:52)

* open floor  (dustymabe, 16:40:04)
  * ACTION: davdunc to make changes to the cloud base image to include
qemu-guest-agent and drop the networking configuration  (dustymabe,
16:43:32)
  * we have a PR open to rebase cloud-init to the new upstream version:
https://src.fedoraproject.org/rpms/cloud-init/pull-request/11
(dustymabe, 16:48:05)

Meeting ended at 16:51:07 UTC.




Action Items

* davdunc to make changes to the cloud base image to include
  qemu-guest-agent and drop the networking configuration




Action Items, by person
---
* davdunc
  * davdunc to make changes to the cloud base image to include
qemu-guest-agent and drop the networking configuration
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dustymabe (74)
* King_InuYasha (18)
* jdoss (15)
* zodbot (14)
* danken (14)
* davdunc (12)
* cyberpear (5)
* michaelgugino (3)
* otubo (2)
* roshi (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: [Fedocal] Reminder meeting : Fedora Cloud Workgroup

[Dusty Mabe]

I won't be able to make it tomorrow. Anyone else want to run the meeting?

Dusty

On 11/22/20 11:00 AM, du...@dustymabe.com wrote:
> Dear all,
> 
> You are kindly invited to the meeting:
>Fedora Cloud Workgroup on 2020-11-24 from 16:00:00 to 17:00:00 UTC
>At fedora-meetin...@irc.freenode.net
> 
> The meeting will be about:
> Standing meeting for the Fedora Cloud Workgroup
> 
> 
> Source: https://apps.fedoraproject.org/calendar/meeting/1999/
> 
> ___
> cloud mailing list -- cloud@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
> 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Fedora 33 in GCP

[Dusty Mabe]

We have published an image into GCP for Fedora 33 (see [1]).

The details are:

image project: fedora-cloud
image name:fedora-cloud-base-gcp-33-1-2-x86-64

We're hoping to get this information added to the website at some point.

Dusty

[1] https://pagure.io/cloud-sig/issue/318
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Issue on Fedora Cloud 32 & 33 cloud-init

[Dusty Mabe]

Responded in the bug: 
https://bugzilla.redhat.com/show_bug.cgi?id=1895461#c1


On 11/9/20 7:10 AM, Oliver Falk wrote:
> Hi!
> 
> I'm watching the BZ now. I hope Dusty finds some time to look into it!
> 
> Oliver
> 
> On Fri, Nov 6, 2020 at 6:54 PM Edouard  > wrote:
> 
> Hi Oliver,
> 
> Thanks for your answer. I followed your advice and opened a bug : 
> https://bugzilla.redhat.com/show_bug.cgi?id=1895461 
> 
> 
> Edouard
> ___
> cloud mailing list -- cloud@lists.fedoraproject.org 
> 
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org 
> 
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ 
> 
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines 
> 
> List Archives: 
> https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org 
> 
> 
> 
> ___
> cloud mailing list -- cloud@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
> 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Can't use F33 EC2 image: SSH key doesn't work

[Dusty Mabe]

On 11/9/20 3:40 PM, Kevin White wrote:
> AWS's EC2 launch process can inject an SSH key into an image, however, it can 
> only inject RSA keys.  It won't accept anything else.
> 
> Fedora 33 doesn't allow RSA keys for SSH.
> 
> Thus, when I launch an F33 image in EC2 (using the Cloud images, specifically:
> 
> Fedora-Cloud-Base-33-1.2.x86_64-hvm-us-east-2-gp2-0  (ami-0c54097900b6afcbe)
> 
> I can't ssh into it.
> 
> Is there any way to actually use Fedora-Cloud-Base-33 in EC2?
> 

Fedora recently upgraded it's crypto policies to be more secure including 
removing some
support for weak algorithms. See https://www.openssh.com/txt/release-8.3 for 
more information.

Try `ssh -oHostKeyAlgorithms=-ssh-rsa fedora@x.x.x.x`

Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Fedora 33 final AMIs

[Dusty Mabe]

Fedora-Cloud-Base-33-1.2.x86_64   ap-northeast-1   
ami-0d3ac0b331a940336 hvm   gp2
Fedora-Cloud-Base-33-1.2.x86_64   ap-northeast-2   
ami-09256ce41c4d2a8a6 hvm   gp2
Fedora-Cloud-Base-33-1.2.x86_64   ap-south-1   
ami-0eb3c7a619db0c8fc hvm   gp2
Fedora-Cloud-Base-33-1.2.x86_64   ap-southeast-1   
ami-0de4ad689ee8fde12 hvm   gp2
Fedora-Cloud-Base-33-1.2.x86_64   ap-southeast-2   
ami-06e080dd692099361 hvm   gp2
Fedora-Cloud-Base-33-1.2.x86_64   ca-central-1 
ami-0c633fc0c88eaa491 hvm   gp2
Fedora-Cloud-Base-33-1.2.x86_64   eu-central-1 
ami-04c4b559df358b45a hvm   gp2
Fedora-Cloud-Base-33-1.2.x86_64   eu-west-1
ami-044a473797ac1fb5a hvm   gp2
Fedora-Cloud-Base-33-1.2.x86_64   eu-west-2
ami-0edca001b0a05f840 hvm   gp2
Fedora-Cloud-Base-33-1.2.x86_64   sa-east-1
ami-0097991dab681274e hvm   gp2
Fedora-Cloud-Base-33-1.2.x86_64   us-east-1
ami-01efb339f953fdf36 hvm   gp2
Fedora-Cloud-Base-33-1.2.x86_64   us-east-2
ami-0c54097900b6afcbe hvm   gp2
Fedora-Cloud-Base-33-1.2.x86_64   us-west-1
ami-03cd6589f3954c8ff hvm   gp2
Fedora-Cloud-Base-33-1.2.x86_64   us-west-2
ami-0467cd5075b6ae963 hvm   gp2

Fedora-Cloud-Base-33-1.2.aarch64  eu-west-1
ami-0eafb5442e7e66c54 hvm   gp2
Fedora-Cloud-Base-33-1.2.aarch64  us-east-1
ami-07b7fa952a4ad5fd2 hvm   gp2
Fedora-Cloud-Base-33-1.2.aarch64  us-east-2
ami-0881cb6f13f7ee51e hvm   gp2
Fedora-Cloud-Base-33-1.2.aarch64  us-west-2
ami-0adb8ca55714fcde5 hvm   gp2
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Fedora 33 Cloud image bug? Or new packaging "feature"?

[Dusty Mabe]

On 10/29/20 6:45 PM, Mike Savage wrote:
> Hi,

Hi Mike,

> 
> I have some Ansible code that inspects qcow images to verify the distro and 
> version via shell -->  virt-inspector...and then set facts for use later on 
> in the code. However, upon downloading Fedora-Cloud-Base-33-1.2.x86_64.qcow2 
> image and executing my playbooks, Ansible errored out.
> 
> To see what was going on, I received the following when I manually executed 
> "virt-inspector -a" against the image to inspect:
> # virt-inspector -a Fedora-Cloud-Base-33-1.2.x86_64.qcow2 
> libguestfs: error: filesize: /var/lib/rpm/Name: No such file or directory
> 
> Using the guestfs-browser, I noticed that the /var/lib/rpm directory for the 
> F33 Cloud image was essentially empty, whereas on previous Fedora Cloud image 
> releases I inspected ( 32-1.6, 31-1.9, 30-1.2 ), all had /var/lib/rpm 
> directories that were populated (ie, Name was present). Is this a packaging 
> "miss" for the F33 Cloud OpenStack QCOW image? Or a "feature" new to Fedora 
> 33...and if so, should I adjust my automation to move to a more distro 
> agnostic method, like probing and parsing /etc/os-release within images?

I did some overhaul of the cloud kickstarts in the following PR:
https://pagure.io/fedora-kickstarts/pull-request/679#

but I don't really think there is anything in there that stands out.
This is probably related to the switch of the rpm database in F33 to sqlite:
https://www.fedoraproject.org/wiki/Changes/Sqlite_Rpmdb

Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Cloud Meeting Canceled 2020-10-27

[Dusty Mabe]

Hey All,

We're cancelling the cloud meeting because a good number of us can't make it.
See you in two weeks.

Dusty

P.S. Fedora 33 was released today. Go grab the new stuff!
 https://alt.fedoraproject.org/cloud/
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Fedora Cloud Meeting Minutes 2020-10-13

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-10-13/fedora_cloud_meeting.2020-10-13-16.00.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-10-13/fedora_cloud_meeting.2020-10-13-16.00.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-10-13/fedora_cloud_meeting.2020-10-13-16.00.log.html

===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 16:00:29 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-10-13/fedora_cloud_meeting.2020-10-13-16.00.log.html
.



Meeting summary
---
* roll call  (dustymabe, 16:00:37)

* Action items from last meeting  (dustymabe, 16:05:37)
  * dustymabe provided GCP credentials to King_InuYasha for testing
(dustymabe, 16:06:11)
  * LINK:
https://gist.github.com/michaelgugino/e742b83d3950c6cdbfaa25fe262a86bf
(michaelgugino, 16:11:56)
  * ACTION: King_InuYasha to discuss the options for packaging go
applications that use go modules with the golang fedora SIG to see
if there are any implications there.  (dustymabe, 16:12:24)
  * ACTION: dustymabe to add example to the ticket that shows the
command to run to do image uploads to GCP with ore  (dustymabe,
16:15:24)

* adding GCP image to the download page  (dustymabe, 16:20:23)
  * LINK: https://pagure.io/cloud-sig/issue/314   (dustymabe, 16:20:28)
  * LINK: https://pagure.io/cloud-sig/issue/313   (dustymabe, 16:27:45)

* open floor  (dustymabe, 16:29:47)

Meeting ended at 16:34:21 UTC.




Action Items

* King_InuYasha to discuss the options for packaging go applications
  that use go modules with the golang fedora SIG to see if there are any
  implications there.
* dustymabe to add example to the ticket that shows the command to run
  to do image uploads to GCP with ore




Action Items, by person
---
* dustymabe
  * dustymabe to add example to the ticket that shows the command to run
to do image uploads to GCP with ore
* King_InuYasha
  * King_InuYasha to discuss the options for packaging go applications
that use go modules with the golang fedora SIG to see if there are
any implications there.
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dustymabe (70)
* King_InuYasha (25)
* michaelgugino (16)
* zodbot (13)
* darkmuggle (5)
* nb (2)
* jdoss (1)
* cyberpear (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Fedora Cloud Meeting Minutes 2020-09-29

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-09-29/fedora_cloud_meeting.2020-09-29-15.58.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-09-29/fedora_cloud_meeting.2020-09-29-15.58.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-09-29/fedora_cloud_meeting.2020-09-29-15.58.log.html

===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 15:58:47 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-09-29/fedora_cloud_meeting.2020-09-29-15.58.log.html
.



Meeting summary
---
* roll call  (dustymabe, 15:58:52)

* Action items from last meeting  (dustymabe, 16:01:43)
  * ACTION: King_InuYasha to discuss the options for packaging go
applications that use go modules with the golang fedora SIG to see
if there are any implications there.  (dustymabe, 16:05:05)

* regular releases: uploading to clouds  (dustymabe, 16:06:16)
  * LINK: https://pagure.io/cloud-sig/issue/301   (dustymabe, 16:06:24)
  * ACTION: michaelgugino to schedule some time for a few of us to get
together to flesh out design and next steps for cloud image upload
bits  (dustymabe, 16:20:04)

* publish a cloud image for GCP  (dustymabe, 16:24:44)
  * LINK: https://pagure.io/cloud-sig/issue/310   (dustymabe, 16:24:59)
  * LINK: https://pagure.io/cloud-sig/issue/310#comment-688932
(dustymabe, 16:25:49)
  * ACTION: dustymabe to give King_InuYasha access to a project in GCP
to do testing  (dustymabe, 16:28:45)
  * ACTION: King_InuYasha to test out f33 fedora cloud base GCP images
(dustymabe, 16:29:05)

* open floor  (dustymabe, 16:32:48)
  * ACTION: King_InuYasha to work with davdunc on structure for files to
add to the cloud-sig repo for AWS marketplace enablement
(dustymabe, 16:44:20)

Meeting ended at 16:49:48 UTC.




Action Items

* King_InuYasha to discuss the options for packaging go applications
  that use go modules with the golang fedora SIG to see if there are any
  implications there.
* michaelgugino to schedule some time for a few of us to get together to
  flesh out design and next steps for cloud image upload bits
* dustymabe to give King_InuYasha access to a project in GCP to do
  testing
* King_InuYasha to test out f33 fedora cloud base GCP images
* King_InuYasha to work with davdunc on structure for files to add to
  the cloud-sig repo for AWS marketplace enablement




Action Items, by person
---
* dustymabe
  * dustymabe to give King_InuYasha access to a project in GCP to do
testing
* King_InuYasha
  * King_InuYasha to discuss the options for packaging go applications
that use go modules with the golang fedora SIG to see if there are
any implications there.
  * dustymabe to give King_InuYasha access to a project in GCP to do
testing
  * King_InuYasha to test out f33 fedora cloud base GCP images
  * King_InuYasha to work with davdunc on structure for files to add to
the cloud-sig repo for AWS marketplace enablement
* michaelgugino
  * michaelgugino to schedule some time for a few of us to get together
to flesh out design and next steps for cloud image upload bits
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dustymabe (90)
* King_InuYasha (76)
* michaelgugino (22)
* jdoss (16)
* zodbot (12)
* darkmuggle (2)
* cyberpear (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Fedora Cloud Meeting Minutes 2020-09-15

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-09-15/fedora_cloud_meeting.2020-09-15-16.00.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-09-15/fedora_cloud_meeting.2020-09-15-16.00.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-09-15/fedora_cloud_meeting.2020-09-15-16.00.log.html

===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 16:00:43 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-09-15/fedora_cloud_meeting.2020-09-15-16.00.log.html
.



Meeting summary
---
* roll call  (dustymabe, 16:00:48)

* packaging cloud agents for GCP  (dustymabe, 16:04:10)
  * LINK: https://pagure.io/cloud-sig/issue/313   (dustymabe, 16:04:18)
  * ACTION: Eighth_Doctor to work with ericedens on getting the google
cloud agents packaged for a GCP image  (dustymabe, 16:06:37)

* rewrite kickstart files - remove cruft  (dustymabe, 16:07:01)
  * LINK: https://pagure.io/cloud-sig/issue/311   (dustymabe, 16:07:05)
  * LINK:

https://kojipkgs.fedoraproject.org/compose/branched/Fedora-33-20200914.n.0/compose/Cloud/x86_64/images/
(dustymabe, 16:10:28)
  * LINK: https://paste.centos.org/view/c94d291a   (dustymabe, 16:14:53)
  * please help us test the recent f33 cloud images. The kickstart was
recently overhauled and we'd like to know we didn't break anything.
Image downloads are at

https://kojipkgs.fedoraproject.org/compose/branched/Fedora-33-20200914.n.0/compose/Cloud/
. AMI info is at https://paste.centos.org/view/c94d291a  (dustymabe,
16:15:43)
  * please help us test the recent f33 cloud images. The kickstart was
recently overhauled and we'd like to know we didn't break anything.
Image downloads are at

https://kojipkgs.fedoraproject.org/compose/branched/Fedora-33-20200914.n.0/compose/Cloud/
. AMI info is at https://hackmd.io/p8SDg7tUQrmn0kxnHNdZ9w?edit
(dustymabe, 16:18:24)

* regular releases: uploading to clouds  (dustymabe, 16:19:30)
  * LINK: https://pagure.io/cloud-sig/issue/301   (dustymabe, 16:19:36)

* open floor  (dustymabe, 16:23:33)

Meeting ended at 16:26:18 UTC.




Action Items

* Eighth_Doctor to work with ericedens on getting the google cloud
  agents packaged for a GCP image




Action Items, by person
---
* Eighth_Doctor
  * Eighth_Doctor to work with ericedens on getting the google cloud
agents packaged for a GCP image
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dustymabe (48)
* Eighth_Doctor (15)
* zodbot (12)
* darkmuggle (3)
* cyberpear (2)
* michaelgugino (2)
* jdoss (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Fedora Cloud Meeting Minutes 2020-08-18

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-08-18/fedora_cloud_meeting.2020-08-18-15.58.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-08-18/fedora_cloud_meeting.2020-08-18-15.58.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-08-18/fedora_cloud_meeting.2020-08-18-15.58.log.html


===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 15:58:21 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-08-18/fedora_cloud_meeting.2020-08-18-15.58.log.html
.



Meeting summary
---
* roll call  (dustymabe, 15:58:26)

* Action items from last meeting  (dustymabe, 16:01:59)
  * ACTION: King_InuYasha to engage mhayden to see if the cloud base
images might be a good candidate for Image Builder  (dustymabe,
16:05:21)

* publish a cloud image for GCP  (dustymabe, 16:07:47)
  * LINK: https://pagure.io/cloud-sig/issue/310   (dustymabe, 16:07:51)
  * The engineer from google has posted up a proposed kickstart for
creating and image for GCP  (dustymabe, 16:08:18)

* regular releases: uploading to clouds  (dustymabe, 16:15:12)
  * LINK: https://pagure.io/cloud-sig/issue/301   (dustymabe, 16:15:16)
  * POC for listening to fedora-messaging for doing cloud image uploads:
https://github.com/michaelgugino/fed-image-watcher  (dustymabe,
16:17:21)
  * LINK: https://github.com/SUSE-Enceladus/mash   (King_InuYasha,
16:29:02)
  * ACTION: King_InuYasha and michaelgugino to work together to see if
mash is a viable avenue for uploading disk images to the clouds
(dustymabe, 16:35:20)

* open floor  (dustymabe, 16:36:01)
  * LINK:
https://github.com/jamescassell/fedora-kickstarts/commits/cloud-cleanup
(cyberpear, 16:41:07)

Meeting ended at 16:44:22 UTC.




Action Items

* King_InuYasha to engage mhayden to see if the cloud base images might
  be a good candidate for Image Builder
* King_InuYasha and michaelgugino to work together to see if mash is a
  viable avenue for uploading disk images to the clouds




Action Items, by person
---
* King_InuYasha
  * King_InuYasha to engage mhayden to see if the cloud base images
might be a good candidate for Image Builder
  * King_InuYasha and michaelgugino to work together to see if mash is a
viable avenue for uploading disk images to the clouds
* michaelgugino
  * King_InuYasha and michaelgugino to work together to see if mash is a
viable avenue for uploading disk images to the clouds
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dustymabe (57)
* King_InuYasha (23)
* michaelgugino (19)
* zodbot (13)
* jdoss (7)
* cyberpear (7)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Fedora Cloud Meeting Minutes 2020-08-04

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-08-04/fedora_cloud_meeting.2020-08-04-16.00.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-08-04/fedora_cloud_meeting.2020-08-04-16.00.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-08-04/fedora_cloud_meeting.2020-08-04-16.00.log.html

===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 16:00:50 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-08-04/fedora_cloud_meeting.2020-08-04-16.00.log.html
.



Meeting summary
---
* roll call  (dustymabe, 16:00:55)

* Action items from last meeting  (dustymabe, 16:08:47)
  * ACTION: King_InuYasha to engage mhayden to see if the cloud base
images might be a good candidate for Image Builder  (dustymabe,
16:09:20)

* open floor  (dustymabe, 16:10:54)
  * LINK: https://pagure.io/cloud-sig/issue/310#comment-63
(dustymabe, 16:11:29)
  * LINK:

https://github.com/osbuild/osbuild/commit/925530ac0ab6fef7c2ddba3887a3a61d77b5e75a
(King_InuYasha, 16:15:51)

Meeting ended at 16:24:46 UTC.




Action Items

* King_InuYasha to engage mhayden to see if the cloud base images might
  be a good candidate for Image Builder




Action Items, by person
---
* King_InuYasha
  * King_InuYasha to engage mhayden to see if the cloud base images
might be a good candidate for Image Builder
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dustymabe (29)
* King_InuYasha (19)
* zodbot (10)
* nasirhm (5)
* jdoss (2)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Fedora Cloud Meeting Minutes 2020-07-21

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-07-21/fedora_cloud_meeting.2020-07-21-15.59.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-07-21/fedora_cloud_meeting.2020-07-21-15.59.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-07-21/fedora_cloud_meeting.2020-07-21-15.59.log.html

===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 15:59:06 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-07-21/fedora_cloud_meeting.2020-07-21-15.59.log.html
.



Meeting summary
---
* roll call  (dustymabe, 15:59:29)

* Action items from last meeting  (dustymabe, 16:05:40)

* open floor  (dustymabe, 16:06:49)

* Cloud images should support UEFI  (dustymabe, 16:10:18)
  * LINK: https://pagure.io/cloud-sig/issue/309   (dustymabe, 16:10:22)
  * LINK: https://osinside.github.io/kiwi/   (King_InuYasha, 16:17:13)
  * ACTION: King_InuYasha to engage mhayden to see if the cloud base
images might be a good candidate for Image Builder  (dustymabe,
16:20:36)

* open floor 2  (dustymabe, 16:22:36)

Meeting ended at 16:34:03 UTC.




Action Items

* King_InuYasha to engage mhayden to see if the cloud base images might
  be a good candidate for Image Builder




Action Items, by person
---
* King_InuYasha
  * King_InuYasha to engage mhayden to see if the cloud base images
might be a good candidate for Image Builder
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dustymabe (43)
* King_InuYasha (41)
* zodbot (9)
* michaelgugino (4)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Fedora Cloud Meeting Minutes 2020-07-07

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-07-07/fedora_cloud_meeting.2020-07-07-16.00.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-07-07/fedora_cloud_meeting.2020-07-07-16.00.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-07-07/fedora_cloud_meeting.2020-07-07-16.00.log.html
 


===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 16:00:22 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-07-07/fedora_cloud_meeting.2020-07-07-16.00.log.html
.



Meeting summary
---
* roll call  (dustymabe, 16:00:29)

* Action items from last meeting  (dustymabe, 16:03:34)
  * King_InuYasha created #308 for us to discuss btrfs  (dustymabe,
16:04:24)
  * LINK: https://pagure.io/cloud-sig/issue/308   (dustymabe, 16:04:28)
  * LINK: https://pagure.io/fesco/issue/2429   (King_InuYasha, 16:05:23)

* regular releases: uploading to clouds  (dustymabe, 16:05:47)
  * LINK: https://pagure.io/cloud-sig/issue/301   (dustymabe, 16:05:54)

* swaponzram for the cloud base image  (dustymabe, 16:10:23)
  * LINK: https://pagure.io/cloud-sig/issue/307   (dustymabe, 16:10:29)
  * LINK: https://paste.centos.org/view/fe0cc4d0   (dustymabe, 16:11:57)

* open floor  (dustymabe, 16:38:43)
  * LINK:

https://github.com/openshift/release/blob/248d72a6beb742f8dd8c71454034ab0a09ff670f/ci-operator/jobs/openshift/release/openshift-release-release-4.5-periodics.yaml#L580
(dustymabe, 16:43:28)

Meeting ended at 17:21:04 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dustymabe (64)
* michaelgugino (14)
* King_InuYasha (13)
* zodbot (12)
* jdoss (8)
* otubo (2)
* clcollins (2)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Building local cloud image

[Dusty Mabe]

On 6/12/20 10:20 PM, Michael Hall wrote:
> Just wondering what the current best platform is for building Fedora 
> cloud-base images (specifically, for AWS). We're looking at potentially doing 
> this as part of a community college IT course, then contributing the 
> documented process back to the Fedora Documentation project.
> 
> I've installed ImageFactory with libvirt/qemu on a couple of Fedora machines 
> now but cannot get an image to build. No matter what I do I get one of two 
> error messages.
> 
> One error seems to read the value out of the  tages in the 
> TCL template file, and return that as the error. So if I make the version 
> "32", it returns "Error: '32'"
> 
> The second error mentions needing to run "add_image()' first, but no 
> documentation I can find addresses this issue so not sure where to go from 
> here.
> 
> Is ImageFactory the current recommended tool, a lot of its documentation 
> seems to potentially be out of date?

In general if you are building images for Fedora (i.e. you want the changes 
you're doing to make it back into
Fedora at some point) it's going to have to go through image factory at some 
point.

> 
> Is HashiCorp's Packer a useful alternative?

I've never used it but I hear a lot of people do.

> 
> Is it absolutely necessary to get the whole Koji toolchain involved?

No, you can do it with just imagefactory. I used to do this inside a vagrant 
box with something
like:

Vagrant.configure(2) do |config|

config.ssh.insert_key = 'true'
config.vm.synced_folder "/var/b/shared", "/var/b/shared", type: "sshfs"

config.vm.provider :libvirt do |domain|
  domain.memory = 6096
  domain.cpus = 2
end

host = 'imagefactory'
box  = 'fedora/31-cloud-base'

config.vm.define host do | tmp |
tmp.vm.hostname = host
tmp.vm.box = box

end

# Install tools for rpm-ostree
config.vm.provision "shell", inline: <<-SHELL
  dnf install -y git imagefactory imagefactory-plugins* libvirt-client 
pykickstart
  systemctl enable libvirtd --now # the --now should work but doesn't for 
some reason
  sed -i.orig 's/\# memory = 1024/memory = 2048/' /etc/oz/oz.cfg
SHELL

end

Then run:

sudo imagefactory --debug base_image --file-parameter install_script 
fedora-cloud-base.ks --parameter offline_icicle true ./fedora-rawhide.tdl
qemu-img convert -O qcow2 
/var/lib/imagefactory/storage/9637af5b-4174-49f5-aab1-2bda7897a1d6.body 
image.qcow2

For the tdl file you can grab one from a recent koji build:

- https://koji.fedoraproject.org/koji/taskinfo?taskID=45568107
- https://koji.fedoraproject.org/koji/taskinfo?taskID=45568112
- 
https://kojipkgs.fedoraproject.org//work/tasks/8112/45568112/tdl-x86_64.xml

you can replace the repos in there with other ones like the ones from release 
day if you want.


> 
> Can we just build a normal VM image on libvirt with a suitable kickstart file 
> and use that?

If you are just messing around with an image for your use I would just use 
`virt-install --noreboot` and
give anaconda a kickstart file. Something like: 

virt-install --name builder1 --ram  4500 --vcpus 4 --disk 
path=/path/to/image/file.img,size=10 \
--accelerate --location 
https://dl.fedoraproject.org/pub/fedora/linux/development/32/Everything/x86_64/os/
 \
--initrd-inject /path/fo/kickstart.cfg --force --noreboot --network 
bridge=virbr0 --extra-args='ks=file://kickstart.cfg'

> 
> Looking for solutions that aren't too arduous as most students have limited 
> Linux experience.

+1 - This stack is a bit daunting. Depending on what you are trying to do you 
might give Fedora CoreOS
a try as it's much easier to get that building locally. See 
https://github.com/coreos/coreos-assembler/#the-coreos-assembler
Once you get up and running it would be `cosa build && cosa buildextend-aws` 
then take that file and
upload it into ec2.

> 
> Thanks
> Mike
> 
> ___
> cloud mailing list -- cloud@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
> 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Fedora Cloud Meeting Minutes 2020-05-27

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-05-26/fedora_cloud_meeting.2020-05-26-15.59.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-05-26/fedora_cloud_meeting.2020-05-26-15.59.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-05-26/fedora_cloud_meeting.2020-05-26-15.59.log.html

===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 15:59:53 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-05-26/fedora_cloud_meeting.2020-05-26-15.59.log.html
.



Meeting summary
---
* roll call  (dustymabe, 16:00:05)

* Action items from last meeting  (dustymabe, 16:04:43)
  * dustymabe created the tickets for releasing cloud images
periodically  (dustymabe, 16:05:37)

* releasing cloud images periodically  (dustymabe, 16:06:20)
  * dustymabe created tickets #301 #302 and #303 for creating cloud
images periodicially  (dustymabe, 16:07:12)
  * 301: regular releases: uploading to clouds  (dustymabe, 16:07:31)
  * LINK: https://pagure.io/cloud-sig/issue/301   (dustymabe, 16:07:39)
  * 302:  regular releases: running tests locally and on clouds
(dustymabe, 16:08:00)
  * LINK: https://pagure.io/cloud-sig/issue/302   (dustymabe, 16:08:10)
  * 303: regular releases: promoting release candidates  (dustymabe,
16:08:34)
  * LINK: https://pagure.io/cloud-sig/issue/303   (dustymabe, 16:08:42)
  * ACTION: dustymabe to work with michaelgugino to get a better
definition for the work in 301 and perform knowledge sharing
(dustymabe, 16:14:33)

* open floor  (dustymabe, 16:17:35)

Meeting ended at 16:27:45 UTC.




Action Items

* dustymabe to work with michaelgugino to get a better definition for
  the work in 301 and perform knowledge sharing




Action Items, by person
---
* dustymabe
  * dustymabe to work with michaelgugino to get a better definition for
the work in 301 and perform knowledge sharing
* michaelgugino
  * dustymabe to work with michaelgugino to get a better definition for
the work in 301 and perform knowledge sharing
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dustymabe (58)
* zodbot (9)
* jdoss (8)
* clcollins (5)
* michaelgugino (5)
* mboddu (4)
* misc (3)
* nirik (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Fedora Cloud Info

[Dusty Mabe]

On 5/18/20 2:56 AM, Michael Hall wrote:
> Hi

Hi Michael,

> 
> I am an instructor in a community college in Australia. We are making 
> increasing use of Fedora Cloud images in our practical labs on AWS.
> 
> Fedora just works and has been a great option for us, but we're wondering if 
> there is more information anywhere about what goes into (and comes out of) a 
> Fedora Cloud image, in comparison with regular Fedora.

That's good to hear!

> 
> We have noticed several things, eg:
> - cronjobs (cronie) not installed

systemd timers are one alternative, or dnf install cronie 

> - firewall not installed (not really necessary in AWS environment)

Yeah the standard there has been no firewall on by default because cloud 
providers generally have 
firewalling primitives built in at a higher level.

> - cloud-init installed
> 
> So we're interested in more information about the Fedora Cloud AMI in 
> general, if you could point us to anything relevant. I'm interested in making 
> it clear to students the choices, options and requirements involved in 
> putting together an AMI.

We build the cloud base image using an Anaconda kickstart located here:
https://pagure.io/fedora-kickstarts/blob/master/f/fedora-cloud-base.ks


> 
> Some of the documentation around Fedora Cloud seems a little out of date, 
> maybe we could look at updating some docs as a class project somewhere down 
> the line.

Would love to have you be more involved in the community. We hang out in 
#fedora-cloud on IRC
and our next meeting is bi-weekly. See the Meetings section of 
https://pagure.io/cloud-sig/blob/master/f/README.md

Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Commit access to fedora-cloud / official-images

[Dusty Mabe]

On 4/30/20 3:11 PM, Vipul Siddharth wrote:
> On Fri, May 1, 2020 at 12:39 AM Dusty Mabe  wrote:
>>
>>
>>

>> Which repo?
> oops, should have added a link
> https://github.com/fedora-cloud/official-images/
> Thank you for a super fast response Dusty

I added Clement to the `fedora-docker-images` group, which has admin access.
He will be able to invite you to that same team after accepting the invite.

Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Commit access to fedora-cloud / official-images

[Dusty Mabe]

On 4/30/20 3:04 PM, Vipul Siddharth wrote:
> Hi folks,

Hi Vipul,

Good to meet you!

> I want to help with updating Fedora's dockerhub official image ~once
> in every 2 weeks.

Are you referring to our container images? The Cloud SIG doesn't really
deal specifically with those, but more the Cloud base images.

> I worked with Clement who was kind enough to help me get started.
> I can work with someone creating a new synced branch every 2 weeks so
> that I can send a PR but that's seems a but more trouble to others
> (unless someone volunteers to do it so that I can bug them :)).
> I am requesting to be added to the repo with commit access.

Which repo?

> 
> My FAS is siddharthvipul1 and I am part of CPE team at Red Hat.
> Thank you
> 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Fedora Cloud Meeting Minutes 2020-04-28

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-04-28/fedora_cloud_meeting.2020-04-28-15.32.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-04-28/fedora_cloud_meeting.2020-04-28-15.32.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-04-28/fedora_cloud_meeting.2020-04-28-15.32.log.html

===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 15:32:29 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-04-28/fedora_cloud_meeting.2020-04-28-15.32.log.html
.



Meeting summary
---
* roll call  (dustymabe, 15:32:34)

* Action items from last meeting  (dustymabe, 15:37:12)
  * ACTION: dustymabe to create tickets for the work related to
releasing cloud images periodically  (dustymabe, 15:37:54)

* Fedora 32 is now released  (dustymabe, 15:38:32)
  * LINK: https://fedoramagazine.org/announcing-fedora-32/   (dustymabe,
15:38:45)
  * LINK: https://getfedora.org/cloud/   (dustymabe, 15:39:19)
  * LINK: https://app.vagrantup.com/fedora/boxes/32-cloud-base
(dustymabe, 15:40:15)

* open floor  (dustymabe, 15:42:21)
  * we will move the regularly scheduled meeting time back by 30 minutes
to 16:00 UTC to accomodate mhayden  (dustymabe, 15:46:04)
  * LINK: https://pagure.io/cloud-sig   (dustymabe, 15:48:30)
  * we have an issue tracker at https://pagure.io/cloud-sig - it needs
some documentation work to help with getting started as a SIG member
(dustymabe, 15:49:53)
  * LINK: https://apps.fedoraproject.org/calendar/cloud/   (dustymabe,
15:52:47)

Meeting ended at 15:54:14 UTC.




Action Items

* dustymabe to create tickets for the work related to releasing cloud
  images periodically




Action Items, by person
---
* dustymabe
  * dustymabe to create tickets for the work related to releasing cloud
images periodically
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dustymabe (48)
* zodbot (12)
* x3mboy (6)
* michaelgugino (6)
* cyberpear (4)
* jdoss (2)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Fedora 32 Final validation testing: Cloud

[Dusty Mabe]

On 4/15/20 3:42 PM, Adam Williamson wrote:
> Hi folks! So I'm checking over the F32 Final validation test results
> for the current RC (1.3) and one thing we're missing is Cloud tests:
> 
> https://fedoraproject.org/wiki/Test_Results:Fedora_32_RC_1.3_Cloud
> 
> so far we only have the results from automated testing via the old
> autocloud test suite (now run by openQA). No-one has yet done testing
> in real cloud environments. If folks could help get those tests run,
> it'd be great. Image download and AMI links, and general testing
> instructions, can be found at the top of the page. You can edit results
> directly into the page, or use 'relval report-results' (after 'dnf -y
> install relval') to report results.
> 
> Thanks a lot!
> 

Just to make things a little easier here is the list of Amazon AWS AMIs:

Fedora-Cloud-Base-32-1.3.x86_64   ap-northeast-1   
ami-0953690841e86c4d1 hvm   gp2
Fedora-Cloud-Base-32-1.3.x86_64   ap-northeast-2   
ami-06cb889e4ef68d91d hvm   gp2
Fedora-Cloud-Base-32-1.3.x86_64   ap-south-1   
ami-0fb04a73f1fd1f2e1 hvm   gp2
Fedora-Cloud-Base-32-1.3.x86_64   ap-southeast-1   
ami-0509b672f46e88aaf hvm   gp2
Fedora-Cloud-Base-32-1.3.x86_64   ap-southeast-2   
ami-012f126b663eaf1a9 hvm   gp2
Fedora-Cloud-Base-32-1.3.x86_64   ca-central-1 
ami-027774d7a4a9158be hvm   gp2
Fedora-Cloud-Base-32-1.3.x86_64   eu-central-1 
ami-08187340abfd8df98 hvm   gp2
Fedora-Cloud-Base-32-1.3.x86_64   eu-west-1
ami-01d6773360d48dd55 hvm   gp2
Fedora-Cloud-Base-32-1.3.x86_64   eu-west-2
ami-0024c659643e3af72 hvm   gp2
Fedora-Cloud-Base-32-1.3.x86_64   sa-east-1
ami-0a36a76e0eda36b5a hvm   gp2
Fedora-Cloud-Base-32-1.3.x86_64   us-east-1
ami-0061ee85a95862bef hvm   gp2
Fedora-Cloud-Base-32-1.3.x86_64   us-east-2
ami-0d2bda053d12b10d1 hvm   gp2
Fedora-Cloud-Base-32-1.3.x86_64   us-west-1
ami-0c31c0d9be9a788f2 hvm   gp2
Fedora-Cloud-Base-32-1.3.x86_64   us-west-2
ami-0f5ed4ff9a69cfff7 hvm   gp2
Fedora-Cloud-Base-32-1.3.x86_64   ap-northeast-1   
ami-077c4a1a751d4563b hvm   standard   
Fedora-Cloud-Base-32-1.3.x86_64   ap-northeast-2   
ami-0d721a56309bb1f63 hvm   standard   
Fedora-Cloud-Base-32-1.3.x86_64   ap-south-1   
ami-0b48d60fe77c11ce9 hvm   standard   
Fedora-Cloud-Base-32-1.3.x86_64   ap-southeast-1   
ami-022f463ddb4097aa3 hvm   standard   
Fedora-Cloud-Base-32-1.3.x86_64   ap-southeast-2   
ami-0ae7491757c9f8f48 hvm   standard   
Fedora-Cloud-Base-32-1.3.x86_64   ca-central-1 
ami-01c4060605c1b2200 hvm   standard   
Fedora-Cloud-Base-32-1.3.x86_64   eu-central-1 
ami-0b0df7071df68c65d hvm   standard   
Fedora-Cloud-Base-32-1.3.x86_64   eu-west-1
ami-0b1283ae0d1b7927f hvm   standard   
Fedora-Cloud-Base-32-1.3.x86_64   eu-west-2
ami-0556e8ab675119ffe hvm   standard   
Fedora-Cloud-Base-32-1.3.x86_64   sa-east-1
ami-0a6aaca25b6d229bc hvm   standard   
Fedora-Cloud-Base-32-1.3.x86_64   us-east-1
ami-0b6fb2f8c0a3244cd hvm   standard   
Fedora-Cloud-Base-32-1.3.x86_64   us-east-2
ami-0f9238eab0f31b3c2 hvm   standard   
Fedora-Cloud-Base-32-1.3.x86_64   us-west-1
ami-0f1385da3a9564030 hvm   standard   
Fedora-Cloud-Base-32-1.3.x86_64   us-west-2
ami-06810d4f95850a349 hvm   standard   

Fedora-Cloud-Base-32-1.3.aarch64  ap-northeast-1   
ami-00a4c5cfc162ae5d2 hvm   gp2
Fedora-Cloud-Base-32-1.3.aarch64  ap-northeast-2   
ami-00a7b51981839b167 hvm   gp2
Fedora-Cloud-Base-32-1.3.aarch64  ap-south-1   
ami-09c196a2acb1e2ef2 hvm   gp2
Fedora-Cloud-Base-32-1.3.aarch64  ap-southeast-1   
ami-0ca9b2016f6efaf75 hvm   gp2
Fedora-Cloud-Base-32-1.3.aarch64  ap-southeast-2   
ami-0e3f06954d78db89f hvm   gp2
Fedora-Cloud-Base-32-1.3.aarch64  ca-central-1 
ami-018c47e185cc01f9e hvm   gp2
Fedora-Cloud-Base-32-1.3.aarch64  eu-central-1 
ami-0ed9396544d2b32fb hvm   

Fedora Cloud Meeting Minutes 2020-04-14

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-04-14/fedora_cloud_meeting.2020-04-14-15.35.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-04-14/fedora_cloud_meeting.2020-04-14-15.35.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-04-14/fedora_cloud_meeting.2020-04-14-15.35.log.html

===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 15:35:00 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-04-14/fedora_cloud_meeting.2020-04-14-15.35.log.html
.



Meeting summary
---
* roll call  (dustymabe, 15:35:06)

* testing candidate RC composes for F32  (dustymabe, 15:39:45)
  * Candidate RC-1.2 I see just came out  (dustymabe, 15:39:52)
  * LINK:

https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org/thread/ACAEQ6XTMJBKOIXHKPNLM7C4TEGLGZYH/
(cyberpear, 15:42:51)
  * LINK:
https://fedoraproject.org/wiki/Test_Results:Fedora_32_RC_1.2_Cloud
(cyberpear, 15:43:35)
  * LINK:
https://fedoraproject.org/wiki/Test_Results:Fedora_32_RC_1.2_Cloud
(dustymabe, 15:44:49)
  * LINK:

https://kojipkgs.fedoraproject.org/compose/32/Fedora-32-20200414.0/compose/Cloud/x86_64/images/
(dustymabe, 15:48:15)

* open floor  (dustymabe, 15:50:49)

* periodic releases of Fedora Cloud images  (dustymabe, 16:01:15)
  * we agree we would all like to upload and release cloud images more
often. releng has agreed to try to achieve the following items: 1)
copy files to a more permanent location 2) get them on some mirrors
3) update website 4) sending release email. Cloud working group will
try to do the following items: 1) uploading to clouds 2) running
tests on clouds 3) promoting release candidates  (dustymabe,
16:27:38)
  * ACTION: dustymabe to create tickets for the work related to
releasing cloud images periodically  (dustymabe, 16:30:11)

* open floor 2  (dustymabe, 16:30:23)

Meeting ended at 16:33:21 UTC.




Action Items

* dustymabe to create tickets for the work related to releasing cloud
  images periodically




Action Items, by person
---
* dustymabe
  * dustymabe to create tickets for the work related to releasing cloud
images periodically
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dustymabe (84)
* mboddu (37)
* cyberpear (22)
* nirik (17)
* zodbot (9)
* jdoss (8)
* otubo (6)
* fldu1 (5)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Fedora Cloud Meeting Minutes 2020-03-31

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-03-31/fedora_cloud_meeting.2020-03-31-15.30.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-03-31/fedora_cloud_meeting.2020-03-31-15.30.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-03-31/fedora_cloud_meeting.2020-03-31-15.30.log.html

===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 15:30:36 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-03-31/fedora_cloud_meeting.2020-03-31-15.30.log.html
.



Meeting summary
---
* roll call  (dustymabe, 15:30:41)

* Action items from last meeting  (dustymabe, 15:33:58)

* fedora cloud test day  (dustymabe, 15:34:46)
  * LINK: http://testdays.fedorainfracloud.org/events/79   (dustymabe,
15:35:43)

* backlog of cloud-init BZs  (dustymabe, 15:40:38)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1798729   (otubo,
15:41:20)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1798732   (otubo,
15:41:27)

* open floor  (dustymabe, 15:46:13)

Meeting ended at 15:49:52 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dustymabe (42)
* otubo (16)
* zodbot (10)
* jdoss (7)
* cyberpear (3)
* x3mboy (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Fedora 32 Cloud Test Day 2020-03-20

[Dusty Mabe]

On 3/19/20 2:54 PM, Sumantro Mukherjee wrote:
> Hey All,
> 
> Fedora 32 Cloud Test Day is underway!
> 
> A test day is an event where anyone can help make sure that changes in
> Fedora are working well in the upcoming release. Fedora community
> members often participate, but the public is welcome also. You only
> need to be able to download materials (including some large files),
> and read and follow technical directions step by step, to contribute.
> 
> The wiki page[0] for the Cloud test day has a lot of good information
> on what and how to test. After you’ve done some testing, you can log
> your results in the test day app[1].
> 
> [0] https://fedoraproject.org/wiki/Test_Day:2020-03-20_Cloud_Testday
> [1] http://testdays.fedorainfracloud.org/events/79
> 


Here are the AMIs for the beta:

Fedora-Cloud-Base-32_Beta-1.2.aarch64 ap-northeast-1   
ami-0e2d0ec7efa1b8ab3 hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.aarch64 ap-northeast-2   
ami-062f10c8b8294e994 hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.aarch64 ap-south-1   
ami-00079397a56c100f1 hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.aarch64 ap-southeast-1   
ami-06f833d5fa0c15197 hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.aarch64 ap-southeast-2   
ami-0dfdfaafec7792bfd hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.aarch64 ca-central-1 
ami-02ef0473035f36b99 hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.aarch64 eu-central-1 
ami-0cbc0cb681225a2d1 hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.aarch64 eu-west-1
ami-04eecc0083c2c1588 hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.aarch64 eu-west-2
ami-02e2b58b7cc0bb9a0 hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.aarch64 sa-east-1
ami-0491c2c92be47fdec hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.aarch64 us-east-1
ami-032fccb1cb4ee0530 hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.aarch64 us-east-2
ami-04a772681cfd0d769 hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.aarch64 us-west-1
ami-0d764508c381285a6 hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.aarch64 us-west-2
ami-09b5db3c568a73c2d hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.aarch64 ap-northeast-1   
ami-07609be171a746469 hvm   standard   
Fedora-Cloud-Base-32_Beta-1.2.aarch64 ap-northeast-2   
ami-09c47c63c9b5053a8 hvm   standard   
Fedora-Cloud-Base-32_Beta-1.2.aarch64 ap-south-1   
ami-0254bbc7831ec3e4c hvm   standard   
Fedora-Cloud-Base-32_Beta-1.2.aarch64 ap-southeast-1   
ami-0bdb751c1c8232d18 hvm   standard   
Fedora-Cloud-Base-32_Beta-1.2.aarch64 ap-southeast-2   
ami-04091daac7ae2437a hvm   standard   
Fedora-Cloud-Base-32_Beta-1.2.aarch64 ca-central-1 
ami-09b35f81cf57c4d26 hvm   standard   
Fedora-Cloud-Base-32_Beta-1.2.aarch64 eu-central-1 
ami-08c7508c66d10d4d5 hvm   standard   
Fedora-Cloud-Base-32_Beta-1.2.aarch64 eu-west-1
ami-07531ad50e0f8f210 hvm   standard   
Fedora-Cloud-Base-32_Beta-1.2.aarch64 eu-west-2
ami-0342fd715a54f6ce3 hvm   standard   
Fedora-Cloud-Base-32_Beta-1.2.aarch64 sa-east-1
ami-09507736ba73cb278 hvm   standard   
Fedora-Cloud-Base-32_Beta-1.2.aarch64 us-east-1
ami-0717887b79d906fa8 hvm   standard   
Fedora-Cloud-Base-32_Beta-1.2.aarch64 us-east-2
ami-02412e7cad7ab7423 hvm   standard   
Fedora-Cloud-Base-32_Beta-1.2.aarch64 us-west-1
ami-010bdf3663382e463 hvm   standard   
Fedora-Cloud-Base-32_Beta-1.2.aarch64 us-west-2
ami-000a5e4f1eae697df hvm   standard   

Fedora-Cloud-Base-32_Beta-1.2.x86_64  ap-northeast-1   
ami-0a3e5ecd1af437cf6 hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.x86_64  ap-northeast-2   
ami-0b045a55b71328675 hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.x86_64  ap-south-1   
ami-0af5597b67dca44b2 hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.x86_64  ap-southeast-1   
ami-0f7c110aa63ebf24f hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.x86_64  ap-southeast-2   
ami-06a13536a962bff9f hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.x86_64  ca-central-1 
ami-0500fc6a8144abc1e hvm   gp2
Fedora-Cloud-Base-32_Beta-1.2.x86_64  eu-central-1 
ami-0bfe51e7af68b9980 hvm   gp2   

Fedora Cloud Meeting Minutes 2020-03-17

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-03-17/fedora_cloud_meeting.2020-03-17-15.31.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-03-17/fedora_cloud_meeting.2020-03-17-15.31.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-03-17/fedora_cloud_meeting.2020-03-17-15.31.log.html

===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 15:31:44 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-03-17/fedora_cloud_meeting.2020-03-17-15.31.log.html
.



Meeting summary
---
* roll call  (dustymabe, 15:31:50)

* fedora 32 beta released - fedora cloud test day  (dustymabe, 15:36:15)
  * LINK: https://pagure.io/fedora-qa/issue/577   (dustymabe, 15:37:05)
  * we're going to have a Fedora Cloud test day on the 03/20 (this
friday) - please join us in #fedora-cloud and #fedora-test-day on
freenode to help us test the Fedora 32 beta images  (dustymabe,
15:42:19)

* open floor  (dustymabe, 15:42:38)

Meeting ended at 15:50:13 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dustymabe (32)
* zodbot (10)
* cyberpear (8)
* otubo (4)
* mhayden (3)
* sumantro_ (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Fedora Cloud Meeting Minutes 2020-03-10

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-03-10/fedora_cloud_meeting.2020-03-10-14.31.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-03-10/fedora_cloud_meeting.2020-03-10-14.31.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-03-10/fedora_cloud_meeting.2020-03-10-14.31.log.html

===
#fedora-meeting-1: fedora_cloud_meeting
===


Meeting started by dustymabe at 14:31:24 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-03-10/fedora_cloud_meeting.2020-03-10-14.31.log.html
.



Meeting summary
---
* roll call  (dustymabe, 14:31:31)

* [F32] Cloud Base Test Day  (dustymabe, 14:34:48)
  * LINK: https://pagure.io/fedora-qa/issue/577   (dustymabe, 14:34:52)

* fedora cloud images in GCP  (dustymabe, 14:43:05)
  * we're hoping to have official Fedora images in GCP for the Fedora 32
release  (dustymabe, 14:44:25)

* open floor  (dustymabe, 14:45:32)
  * jdoss will try to look at deploying joystick, which will help us
upload to other clouds  (dustymabe, 14:48:51)
  * otubo has plans to cross check fedora-rhel bzs this week and close
out anything that we think has been fixed by the new version of
cloud-init  (dustymabe, 14:49:25)
  * we are going to start having bi-weekly cloud meetings in the cloud
working group again. Starting next tuesday (03/17), then 03/31 in
#fedora-meeting-1 at 15:30 UTC  (dustymabe, 14:51:51)
  * fedocal link is
https://apps.fedoraproject.org/calendar/cloud/2020/3/16/#m1999
(dustymabe, 14:52:51)

Meeting ended at 14:54:42 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dustymabe (42)
* jdoss (16)
* otubo (7)
* zodbot (7)
* sumantro (5)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Fedora 31 - Cockpit - AWS

[Dusty Mabe]

On 3/7/20 10:40 PM, Michael Hall wrote:
> Hi

Hi Michael,

Thanks for reaching out.

> 
> I have created an EC2 instance on AWS using the official Fedora 31 cloud 
> image.
> I installed cockpit and opened port 9090 in the security group.
> I created a user account and gave it a password.
> I can log in to cockpit as my custom user and see a few things, but most 
> importantly for me the terminal isn't working.
> I'm exploring options to have IT students complete labs on Fedora, so access 
> to the terminal is critical.
> 
> Any ideas or hopefully simple fix?
> Is this something to do with AWS networking?

Hmm.. This should work. I just tested it out locally and it worked for me.
A few things to try:

1. make sure your system is completely up to date (`dnf update --refresh -y`)
2. to test if the security group is causing issues open it up to allow all 
traffic
   and see if the problem goes away. If it does then we know it's something to 
do
   with the security group and we can investigate further down that path to find
   exactly what rules we need to allow it.


Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: No swap on Vagrant images. On purpose?

[Dusty Mabe]

On 2/13/20 11:25 AM, Vincent Rubiolo wrote:
> Hi Dusty,
> 
> On 2/12/20 4:43 PM, Dusty Mabe wrote:
>> This is mostly because the cloud images don't configure any swap and we keep 
>> our
>> image builds for the vagrant boxes and for the cloud images pretty much the 
>> same.
> 
> Thanks for your quick answer. This makes sense.
> 
> Would you have a pointer on which scripts/stack are generating the base 
> boxes? One way I see would be to remake the base boxes here.

We generate them using kickstart. Here are the kickstart files (the ones
with *cloud* in the name):

https://pagure.io/fedora-kickstarts/tree/master
> 
>>
>> There are two pretty easy options:
>>
>> - increase the amount of ram for the vagrant box
> 
> Yes, this is my current solution, I am doing that in the Vagrantfile.
> 
>> - configure a second disk in your vagrantfile and then set it up for swap
> 
> Do you have a pointer on how to do that? AFAIS[1] the Vagrant disk 
> feature is still experimental and not fully documented.
> 
> I am using the VirtualBox provider so maybe you were referring to using 
> the VBoxManage configuration hook[2] or remaking the base box itself[3] 
> (hence my question above about how the Fedora base boxes are made)?

I just add a second disk in my configuration file:
https://github.com/dustymabe/vagrantdirs/blob/430520bcc8fe06430e205366e15f11f45236407d/vanilla/f31/Vagrantfile#L13-L14

I use libvirt, so it may be specific to that provider, but I didn't think
it was. You can also try https://www.vagrantup.com/docs/disks/configuration.html

> 
> Thanks again for your help here!
> 
> Vincent
> 
> [1] https://www.vagrantup.com/docs/disks/usage.html
> [2] 
> https://www.vagrantup.com/docs/virtualbox/configuration.html#vboxmanage-customizations
> [3] https://www.vagrantup.com/docs/virtualbox/boxes.html#virtual-machine
> 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: No swap on Vagrant images. On purpose?

[Dusty Mabe]

On 2/10/20 9:26 AM, Vincent Rubiolo [IoT.bzh] wrote:
> Good afternoon everyone,
> 
> I am currently using the nice Fedora 30 Vagrant boxes[1] to host some 
> local dev environment (doing builds) and stumbled upon the fact that the 
> machines do not provide any swap partition/space (cf attached session 
> log). My build inside it is thus getting killed when running out of RAM.
> 
> I have not found my answer on the list but from some of the searches 
> I've done[2], it looks like this is a balance between the time spent by 
> the Fedora cloud team and the users (as to who should do the customization).
> 
> Was that the rationale behind this decision to not have swap space into 
> the images (that users would configure that themselves)?
> 
> Thanks for your feedback,
> 

This is mostly because the cloud images don't configure any swap and we keep our
image builds for the vagrant boxes and for the cloud images pretty much the 
same.

There are two pretty easy options:

- increase the amount of ram for the vagrant box
- configure a second disk in your vagrantfile and then set it up for swap

Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: earlyoom by default

[Dusty Mabe]

On 1/8/20 5:21 PM, Chris Murphy wrote:
> On Mon, Jan 6, 2020 at 7:56 PM Dusty Mabe  wrote:
>>
>> For cloud at least it's very common to not have swap. I'd argue for servers
>> you don't want them swapping either but resources aren't quite as elastic as
>> in the cloud so you might not be able to burst resources like you can in the 
>> cloud.
> 
> There's also discussion about making oomd a universal solution for
> this; but I came across this issue asserting PSI (kernel pressure
> stall information) does not work well without swap.
> https://github.com/facebookincubator/oomd/issues/80
> 
> Ignoring whether+what+when a workaround may be found for that, what do
> you think about always having swap-on-ZRAM enabled in these same
> environments? The idea there is a configurable size /dev/zram block
> device (basically a compressible RAM disk) on which swap is created.
> Based on discussions with anaconda, IoT, Workstation, and systemd
> folks - I think there's a potential to converge on systemd-zram
> generator (rust) to do this.
> https://github.com/systemd/zram-generator
> 
> Workstation wg is mulling over the idea of dropping separate swap
> partitions entirely, and using a swap-on-ZRAM device instead; possibly
> with a dynamically created swapfile for certain use cases like
> hibernation. So I'm curious if this might have broader appeal, and get
> systemd-zram generator production ready.
> 


Seems like an interesting concept. Since it doesn't require any disk setup
it's easy to turn it off or configure it I assume.

+1

Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: earlyoom by default

[Dusty Mabe]

On 1/6/20 1:18 PM, Chris Murphy wrote:
> Hi server@ and cloud@ folks,
> 
> There is a system-wide change to enable earlyoom by default on Fedora
> Workstation. It came up in today's Workstation working group meeting
> that I should give you folks a heads up about opting into this change.

Thanks for the heads up!

> 
> Proposal
> https://fedoraproject.org/wiki/Changes/EnableEarlyoom
> Devel@ discussion
> https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/YXDODS3G4YCS7MT4J2QJMJ7EXCVR7NQ2/
> 
> The main issue on a workstation, heavy swap leading to an unresponsive
> system, is perhaps not as immediately frustrating on a server.  But
> the consequences of indefinite hang or the kernel oom-killer
> triggering, which is a SIGKILL, are perhaps worse.
> 
> On the plus side, earlyoom is easy to understand, and its first
> attempt is a SIGTERM rather than SIGKILL. It uses oom_score, same as
> kernel oom-killer, to determine the victim.
> 
> The SIGTERM is issued to the process with the highest oom_score only
> if both memory and swap reach 10% free. And SIGKILL is issued to the
> process with the highest oom_score once memory and swap reach 5% free.
> Those percentages can be tweaked, but the KILL percentage is always
> 1/2 of the TERM  percentage, so it's a bit rudimentary.

Yeah. Adding more ways to relate SIGTERM to SIGKILL (other the 1/2) would 
be nice. 

> 
> One small concern I have is, what if there's no swap? That's probably
> uncommon for servers, but I'm not sure about cloud. But in this case,

For cloud at least it's very common to not have swap. I'd argue for servers
you don't want them swapping either but resources aren't quite as elastic as
in the cloud so you might not be able to burst resources like you can in the 
cloud.


> SIGTERM happens at 10% of RAM, which leaves a lot of memory on the
> table, and for a server with significant resources it's probably too
> high. What about 4%? Maybe still too high? One option I'm thinking of
> is a systemd conditional that would not run earlyoom on systems
> without a swap device, which would leave these systems no worse off
> than they are right now. [i.e. they eventually recover (?),
> indefinitely hang (likely), or oom-killer finally kills something
> (less likely).]

Seems like it on these systems it would nice to make earlyoom SIGTERM just
right before SIGKILL. i.e. try the nice way and then bring in the hammer.
In this case a 1% difference in threshold would be useful. i.e. SIGTERM at
5% SIGKILL at 4% or something like that.


> 
> I've been testing earlyoom, nohang, and the kernel oom-killer for > 6
> months now, and I think it would be completely sane for Server and
> Cloud products to enable earlyoom by default for fc32, while
> evaluating other solutions that can be more server oriented (e.g.
> nohang, oomd, possibly others) for fc33/fc34. What is clear: this
> isn't going to be solved by kernel folks, the kernel oom-killer only
> cares about keeping the kernel alive, it doesn't care about user space
> at all.
> 
> In the cases where this becomes a problem, either the kernel hangs
> indefinitely or does SIGKILL for your database or whatever is eating
> up resources. Whereas at least earlyoom's first attempt is a SIGTERM
> so it has a chance of gracefully quitting.
> 
> There are some concerns, those are in the devel@ thread, and I expect
> they'll be adequately addressed or the feature will not pass the FESCo
> vote. But as a short term solution while evaluating more sophisticated
> solutions, I think this is a good call so I thought I'd just mention
> it, in case you folks want to be included in the change.
> 
> 

Thanks!
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Automatic Network Configuration in Cloud with NetworkManager (nm-cloud-setup)

[Dusty Mabe]

On 11/27/19 4:50 PM, Thomas Haller wrote:
> Hello,
> 
> 
> We (NetworkManager) are working on a tool that should help configuring
> NetworkManager in cloud.
> 
> This is for example for configuring the secondary IP addresses on
> AWS/EC2 ([1], [2])
> 
> [1] 
> https://aws.amazon.com/premiumsupport/knowledge-center/ec2-centos-rhel-secondary-interface/
> [2] 
> https://aws.amazon.com/premiumsupport/knowledge-center/ec2-ubuntu-secondary-network-interface/
> 
> 
> It's inspired by and serves a similar purpose as SuSE's cloud-netconfig 
> ([3], [4]) and ec2-net-utils package on Amazon Linux ([5]).
> 
> [3] https://www.suse.com/c/multi-nic-cloud-netconfig-ec2-azure/
> [4] https://github.com/SUSE-Enceladus/cloud-netconfig
> [5] https://github.com/aws/ec2-net-utils
> 
> 
> 
> The tool can be triggered via a systemd.timer and/or a NetworkManager
> dispatcher scripts. Then it fetches meta data from the Instance
> Metadata Service (thereby detecting whether it runs in a cloud
> environment). Finally it configures the networking using
> NetworkManager.
> 
> Currently it only supports EC2 and IPv4. But if the tool shows to be
> useful, it could be extended to also support other cloud providers
> (Azure).
> 
> 
> There is a merge request on review ([6], [7]). There is a bit of a
> hurry to get this merged, because it should make the cut for the next
> NetworkManager release. So, I will merge it soon to master, albeit
> still in an experimental state.
> 
> [6] 
> https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/348
> [7] https://bugzilla.redhat.com/show_bug.cgi?id=1642461
> 
> 
> The plan is that cloud images could install and enable the tool, so you
> boot a (Fedora) image and networking would just work.
> 
> 
> Is there interrest in something like this? Any comments, questions?


I think the cloud images are already using Network Manager. Would we need to 
include
another rpm and enable a service?

Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Fedora Atomic Host Nearing End Of Life

[Dusty Mabe]

On 11/25/19 11:41 AM, Normand wrote:
> 
> 
> On 11/21/19 11:33 PM, Dusty Mabe wrote:
>> This content also exists at: 
>> https://www.projectatomic.io/blog/2019/11/fedora-atomic-host-nearing-eol/
>>
>> Last year we [introduced the plans for Fedora CoreOS] [1] including that
>> Fedora CoreOS would be the successor to Fedora Atomic Host and Container
>> Linux (from CoreOS Inc.). As part of that succession plan we decided that
>> Fedora 29 Atomic Host would be the last stream of Fedora Atomic Host to be
>> released.
>>
>> Fedora 29 Atomic Host has served us well, but with Fedora 29 End of
>> Life coming soon [2], so will the last release of Fedora 29 Atomic Host.
>> The next release of Fedora 29 Atomic Host (in the next few weeks) will be
>> the last two-week release. It will contain all of the latest content
>> from Fedora 29. After that release, Fedora 29, and Fedora 29 Atomic
>> Host will no longer receive any updates.
>>
>> Please try out the Fedora CoreOS preview to help us get it towards
>> stable. Documentation and download links can be found at 
>> https://getfedora.org/coreos/
>>
>> The Atomic Host Team
>>
>> [1] https://fedoramagazine.org/announcing-fedora-coreos/
>> [2] 
>> https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/VUK3CJ5LO4ROUH3JTCDVHYAVVYAOCU62/
>> ___
>> devel mailing list -- de...@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: 
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org
>>
> 
> 
> Thanks for the info,
> 
> But what about arches that are not x86_64 ?
> Where could we found for exemple the ppc64le coreos replacement of 
> Atomic Host ? Is there already a web page to retrieve them ?
> 

Hi Normand,

Thank you for bringing this up. You have indeed pointed out a gap in what we're 
currently
delivering with Fedora CoreOS preview and what we were delivering with Atomic 
Host. The good
news is that we have done enablement work to allow for Fedora CoreOS to be run 
on other
platforms. The bad news is that we don't currently run our build infrastructure 
in an environment
that has other architectures available.

So while you can build it yourself today, there is currently no where to 
download it from the Fedora
website. I have added Jakub Cajka who was working on getting some space to host 
unofficial builds of
Fedora CoreOS for other architectures for now. I'll also link you to our open 
issues where we're working
through our strategy for delivering multi-arch FCOS:

- https://github.com/coreos/fedora-coreos-tracker/issues/262
- https://pagure.io/fedora-infrastructure/issue/8370

- Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Fedora Atomic Host Nearing End Of Life

[Dusty Mabe]

This content also exists at: 
https://www.projectatomic.io/blog/2019/11/fedora-atomic-host-nearing-eol/

Last year we [introduced the plans for Fedora CoreOS] [1] including that 
Fedora CoreOS would be the successor to Fedora Atomic Host and Container
Linux (from CoreOS Inc.). As part of that succession plan we decided that
Fedora 29 Atomic Host would be the last stream of Fedora Atomic Host to be
released.

Fedora 29 Atomic Host has served us well, but with Fedora 29 End of
Life coming soon [2], so will the last release of Fedora 29 Atomic Host.
The next release of Fedora 29 Atomic Host (in the next few weeks) will be
the last two-week release. It will contain all of the latest content
from Fedora 29. After that release, Fedora 29, and Fedora 29 Atomic
Host will no longer receive any updates.

Please try out the Fedora CoreOS preview to help us get it towards
stable. Documentation and download links can be found at 
https://getfedora.org/coreos/

The Atomic Host Team

[1] https://fedoramagazine.org/announcing-fedora-coreos/
[2] 
https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/VUK3CJ5LO4ROUH3JTCDVHYAVVYAOCU62/
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: rawhide vagrant box will not start

[Dusty Mabe]

On 11/21/19 4:59 AM, Pavel Březina wrote:
Hi Pavel

> I'm trying to run rawhide vagrant box from [1] but rawhide composes do 
> not work correctly (vagrant up gets stuck) since August.
> 
> I opened https://bugzilla.redhat.com/show_bug.cgi?id=1771446 against 
> kernel but I've been told fedora-cloud maintains those images so I'm 
> reaching you here.

Thanks for opening the issue. I think this could be related to the fact that the
cloud images are having trouble booting at all right now. See 
https://bugzilla.redhat.com/show_bug.cgi?id=1754471

Once that fix is in let's retry booting in vagrant.

Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: [Xen-devel] Criteria / validation proposal: drop Xen

[Dusty Mabe]

On 11/1/19 5:05 PM, Adam Williamson wrote:
> On Mon, 2019-07-29 at 14:58 -0400, Ben Cotton wrote:
>> On Tue, Jul 23, 2019 at 7:16 PM Adam Williamson
>>  wrote:
>>> OK, so, to move forward with this (and looping in cloud list): does
>>> someone want to propose a set (ideally small - 2 would be great, one
>>> Xen and one non-Xen, if we can cover most common usages that way!) of
>>> EC2 instance types we should test on? With that, we could tweak the
>>> criteria a bit to specify those instance types, tweak the Cloud
>>> validation page a bit, and then drop the Xen criterion and test case.
>>>
>>
>> I'd suggest c5.large (KVM, afaict) and t3.large (Xen).
>>
>> My AWS experience is probably not representative (being mostly in the
>> HPC space), but these seem like they'd hit the two use cases I'd
>> expect to see for Fedora (compute and small servers). I would expect
>> more people would use M rather than C for Fedora, but this gets us a
>> KVM-based instance.
>>
>> Happy to hear why I'm wrong. :-)
> 
> So, let's pick this up again.
> 
> Here's my latest proposal for the criteria wording:
> 
> "Release-blocking cloud disk images must be published to Amazon EC2 as
> AMIs, and these must boot successfully and meet other relevant release
> criteria on at least one KVM-based x86 instance type and at least one
> Xen-based x86 instance type."
> 
> I also propose we tweak the Cloud matrix:
> 
> https://fedoraproject.org/wiki/Template:Cloud_test_matrix
> 
> and replace the single "EC2" column with separate "EC2 (KVM)" and "EC2
> (Xen)" columns. We would update the ec2 instructions on that page to
> include Matt Wilson's list of KVM and Xen instance types, and provide
> info on how to actually find the right AMIs (the page it currently
> links doesn't do that).
> 
> How does that sound to everyone?

Sounds good to me.

Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Fedora 31 final AMIs

[Dusty Mabe]

Fedora-Cloud-Base-31-1.9.x86_64   ap-northeast-1ami-0d8e872ddc3206741 hvm   
gp2
Fedora-Cloud-Base-31-1.9.x86_64   ap-northeast-2ami-08a47fe608e852f01 hvm   
gp2
Fedora-Cloud-Base-31-1.9.x86_64   ap-south-1ami-0a0a5815e614466e4 hvm   
gp2
Fedora-Cloud-Base-31-1.9.x86_64   ap-southeast-1ami-049d4c4233514a931 hvm   
gp2
Fedora-Cloud-Base-31-1.9.x86_64   ap-southeast-2ami-033b4a0bd9a622f58 hvm   
gp2
Fedora-Cloud-Base-31-1.9.x86_64   ca-central-1  ami-06449af04bac4eac0 hvm   
gp2
Fedora-Cloud-Base-31-1.9.x86_64   eu-central-1  ami-0417b5ec8768794f9 hvm   
gp2
Fedora-Cloud-Base-31-1.9.x86_64   eu-west-1 ami-0ce2a6144475cf269 hvm   
gp2
Fedora-Cloud-Base-31-1.9.x86_64   eu-west-2 ami-0f6b2a3d45505c6ae hvm   
gp2
Fedora-Cloud-Base-31-1.9.x86_64   sa-east-1 ami-0e5c67f0e4306e372 hvm   
gp2
Fedora-Cloud-Base-31-1.9.x86_64   us-east-1 ami-0c830793775595d4b hvm   
gp2
Fedora-Cloud-Base-31-1.9.x86_64   us-east-2 ami-04f8478f9bc7f1453 hvm   
gp2
Fedora-Cloud-Base-31-1.9.x86_64   us-west-1 ami-0e76ece0a3a8ad72f hvm   
gp2
Fedora-Cloud-Base-31-1.9.x86_64   us-west-2 ami-0e82cc6ce8f393d4b hvm   
gp2

Fedora-Cloud-Base-31-1.9.aarch64  eu-west-1 ami-010f0ac509b6d5c90 hvm   
gp2
Fedora-Cloud-Base-31-1.9.aarch64  us-east-1 ami-05927168596f8f271 hvm   
gp2
Fedora-Cloud-Base-31-1.9.aarch64  us-east-2 ami-04e5f7d4b25051814 hvm   
gp2
Fedora-Cloud-Base-31-1.9.aarch64  us-west-2 ami-0b7237050e6efd06d hvm   
gp2
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

AMIs for F31 candidate RC 1.8

[Dusty Mabe]

Fedora-Cloud-Base-31-1.8.aarch64   eu-west-1ami-052a5e155993e375a hvm  
gp2
Fedora-Cloud-Base-31-1.8.aarch64   us-east-1ami-07cb56e4404050d62 hvm  
gp2
Fedora-Cloud-Base-31-1.8.aarch64   us-east-2ami-025d7bc11b02af9cb hvm  
gp2
Fedora-Cloud-Base-31-1.8.aarch64   us-west-2ami-048a18fb9f4394cb5 hvm  
gp2
Fedora-Cloud-Base-31-1.8.aarch64   eu-west-1ami-0e4578cdf11cdb145 hvm  
standard   
Fedora-Cloud-Base-31-1.8.aarch64   us-east-1ami-0bfd16b8c249eeb3b hvm  
standard   
Fedora-Cloud-Base-31-1.8.aarch64   us-east-2ami-0efc2d219a58bb668 hvm  
standard   
Fedora-Cloud-Base-31-1.8.aarch64   us-west-2ami-077d7d1322376e0e5 hvm  
standard   

Fedora-Cloud-Base-31-1.8.x86_64ap-northeast-1   ami-003e0a0473b29a507 hvm  
gp2
Fedora-Cloud-Base-31-1.8.x86_64ap-northeast-2   ami-0aa4cf0bd9bc5e28c hvm  
gp2
Fedora-Cloud-Base-31-1.8.x86_64ap-south-1   ami-029cd92abeb2b7faa hvm  
gp2
Fedora-Cloud-Base-31-1.8.x86_64ap-southeast-1   ami-0b0b32b7cd846fe79 hvm  
gp2
Fedora-Cloud-Base-31-1.8.x86_64ap-southeast-2   ami-001ccfbcf4a8e0814 hvm  
gp2
Fedora-Cloud-Base-31-1.8.x86_64ca-central-1 ami-00959ce04407ab113 hvm  
gp2
Fedora-Cloud-Base-31-1.8.x86_64eu-central-1 ami-0fb2b5c5c573dc952 hvm  
gp2
Fedora-Cloud-Base-31-1.8.x86_64eu-west-1ami-03583526ea23c6718 hvm  
gp2
Fedora-Cloud-Base-31-1.8.x86_64eu-west-2ami-0b47c0ce589992750 hvm  
gp2
Fedora-Cloud-Base-31-1.8.x86_64sa-east-1ami-0e13ff70f442837d9 hvm  
gp2
Fedora-Cloud-Base-31-1.8.x86_64us-east-1ami-0dac56fc82898e1b8 hvm  
gp2
Fedora-Cloud-Base-31-1.8.x86_64us-east-2ami-0251f0f3f451b09db hvm  
gp2
Fedora-Cloud-Base-31-1.8.x86_64us-west-1ami-0f3626e988d9a8c9b hvm  
gp2
Fedora-Cloud-Base-31-1.8.x86_64us-west-2ami-0f684b56a3fbfdfad hvm  
gp2
Fedora-Cloud-Base-31-1.8.x86_64ap-northeast-1   ami-080d846b774b82fe9 hvm  
standard   
Fedora-Cloud-Base-31-1.8.x86_64ap-northeast-2   ami-060c61dcebb734391 hvm  
standard   
Fedora-Cloud-Base-31-1.8.x86_64ap-south-1   ami-04c5a757c0fc5c06d hvm  
standard   
Fedora-Cloud-Base-31-1.8.x86_64ap-southeast-1   ami-0af574325b6b25519 hvm  
standard   
Fedora-Cloud-Base-31-1.8.x86_64ap-southeast-2   ami-044c4347c3defa5e8 hvm  
standard   
Fedora-Cloud-Base-31-1.8.x86_64ca-central-1 ami-0e3846696e37140ad hvm  
standard   
Fedora-Cloud-Base-31-1.8.x86_64eu-central-1 ami-0d3f2ce179d5f9e55 hvm  
standard   
Fedora-Cloud-Base-31-1.8.x86_64eu-west-1ami-0a519a21d908af0ff hvm  
standard   
Fedora-Cloud-Base-31-1.8.x86_64eu-west-2ami-04883cac48b8dadcc hvm  
standard   
Fedora-Cloud-Base-31-1.8.x86_64sa-east-1ami-0b1a124adad777d96 hvm  
standard   
Fedora-Cloud-Base-31-1.8.x86_64us-east-1ami-0d1dc9ac8e8a6ebc6 hvm  
standard   
Fedora-Cloud-Base-31-1.8.x86_64us-east-2ami-09566913942136356 hvm  
standard   
Fedora-Cloud-Base-31-1.8.x86_64us-west-1ami-0ed1b8f368e5b113c hvm  
standard   
Fedora-Cloud-Base-31-1.8.x86_64us-west-2ami-051d77f438f689555 hvm  
standard
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Fedora Atomic Host Two Week Release Announcement: 29.20191001.0

[Dusty Mabe]

On 10/2/19 5:25 PM, nore...@fedoraproject.org wrote:
> 
> A new Fedora Atomic Host update is available via an OSTree update:
> 
> Version: 29.20191001.0
> Commit(x86_64): 
> 15b8a10f8b587c2a037a592806dc04e9cdf6ab1c73c6e49fdaacab1b1174b9ab
> Commit(aarch64): 
> 2b83282e976249b8e1910a7292379753b006851078e9bcea279ff3b6483ee602
> Commit(ppc64le): 
> 7ed4f0395e22000ffe372132c791a8dded291063d5c184e2470dde13c0eb3ba2
> 
> 
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
> 
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
> 
> Corresponding image media for new installations can be downloaded from:
> 
> https://getfedora.org/en/atomic/download/
> 
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191001.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20191001.0.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191001.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20191001.0.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191001.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-29-20191001.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191001.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20191001.0.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191001.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20191001.0.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191001.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-29-20191001.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191001.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20191001.0.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191001.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20191001.0.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191001.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20191001.0.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191001.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20191001.0.x86_64.vagrant-virtualbox.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191001.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-29-20191001.0.iso
> 
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191001.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20191001.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191001.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-29-20191001.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191001.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20191001.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191001.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-29-20191001.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191001.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20191001.0-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191001.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-29-20191001.0-x86_64-CHECKSUM
> 
> For direct download, the "latest" targets are always available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest
> https://getfedora.org/atomic_raw_x86_64_latest
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest
> 
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest
> https://getfedora.org/atomic_raw_aarch64_latest
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest
> 
> ppc64le:
> https://getfedora.org/atomic_qcow2_ppc64le_latest
> https://getfedora.org/atomic_raw_ppc64le_latest
> https://getfedora.org/atomic_dvd_ostree_ppc64le_latest
> 
> Filename fetching URLs are available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest_filename
> https://getfedora.org/atomic_raw_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename
> 
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest_filename
> https://getfedora.org/atomic_raw_aarch64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest_filename
> 

Re: EC2 access for testing?

[Dusty Mabe]

On 9/13/19 4:51 PM, Adam Williamson wrote:
> On Fri, 2019-09-13 at 16:25 -0400, Dusty Mabe wrote:
>>
>> On 9/13/19 3:44 PM, Adam Williamson wrote:
>>> Hi folks! We're currently still discussing adjusting the release
>>> criteria to explicitly require Fedora releases to boot in EC2. Someone
>>> pointed out that if we're going to require that, it would be good if we
>>> had an account allowing EC2 access for testing, so individual Fedora
>>> testers don't have to potentially pay out-of-pocket just to test Fedora
>>> works in EC2. Does anyone know if we have an existing arrangement with
>>> Amazon for this? Thanks!
>>>
>>
>> cc Paul Frields
>>
>> I have access to an account I think we use explicitly for testing Fedora in 
>> AWS.
>> Adam, if Paul doesn't point out any reason not to I can hand you some 
>> credentials.
> 
> It'd be better for it to be something more robust and 'team-accessible' 
> than just people emailing each other passwords, ideally :)
> 
Encrypted of course :-P 

It would be better to have it be something more managed but I don't have 
anything
more robust that I can offer right now. Maybe fedora infra does.

Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: EC2 access for testing?

[Dusty Mabe]

On 9/13/19 3:44 PM, Adam Williamson wrote:
> Hi folks! We're currently still discussing adjusting the release
> criteria to explicitly require Fedora releases to boot in EC2. Someone
> pointed out that if we're going to require that, it would be good if we
> had an account allowing EC2 access for testing, so individual Fedora
> testers don't have to potentially pay out-of-pocket just to test Fedora
> works in EC2. Does anyone know if we have an existing arrangement with
> Amazon for this? Thanks!
> 

cc Paul Frields

I have access to an account I think we use explicitly for testing Fedora in AWS.
Adam, if Paul doesn't point out any reason not to I can hand you some 
credentials.

Dusty  
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: [atomic-announce] Fedora Atomic 29 EOL date?

[Dusty Mabe]

On 8/24/19 6:27 AM, Feilong Wang wrote:
> Hi team,
> 

Hi Feilong! I'm adding in Spyros who has worked with us in the past on Atomic 
Host and Magnum.

> Could you please help me understand when will be the EOL date for Fedora 
> Atomic 29? I understand generally it takes 13 months. But given Fedora Atomic 
> 29 -> Fedora CoreOS 30 is a big jump, is there any special considering for 
> this case?

Fedora 29 Atomic Host will follow the EOL schedule for Fedora 29. It will EOL 
approximately a month
after Fedora 31 is released. Fedora 31 is scheduled to be released at the end 
of October, so the EOL
for Fedora 29 will probably be around the end of November. 

> 
> The background is OpenStack Magnum is using Fedora Atomic as the base 
> operating system to deploy Kubernetes cluster, but because of the big change 
> from FA29 to FCOS 30, we haven't got enough resources on this work. So it 
> would be really helpful if the Fedora Atomic/CorOS community can help me 
> understand the roadmap and plan. Thank you very much.
> 

The Fedora CoreOS preview release is out now. We're hoping to bring that to 
stable ASAP but we've got
some things we'd like to finish before we make that declaration. The best thing 
that can be done is to
get some experience trying out OpenStack Magnum on Fedora CoreOS so that we can 
get in fixes now before
we declare stable. 

We'd like to work with you more closely to make sure the transition is smooth 
for the Magnum project. Can
you all share some time/resources to work with us to make sure we smooth out 
any wrinkles?

Dusty 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Fedora 30 cloud image inline_data

[Dusty Mabe]

On 8/13/19 5:40 PM, Thomas Meyer wrote:
> Hi,
> 
> As the base image has a lot of small files, did someone test what is the 
> influence of setting ext4 feature inline_data?
> 
> Are there other reasons why this feature is not active by default?
> 
> And:
> 
> Why are there so many duplicate files in the cloud image?
> 
> Most of them seem to be from pycache and the filename ends in .opt-1.pyc and 
> an equal file ending in .pyc

We just run a normal Fedora install using a kickstart and the resulting image 
is what we ship. 
 


> Would it be possible to add an extra step after creating the cloud image to 
> hard link all duplicate files or what would speak against that?

Possibly, but there hasn't been a lot of interest in working on or changing the 
cloud image right now. We need to get a group of people who are interested in 
"care and feeding" of the cloud image if we want to make changes to it.

If you'd like to join then say so :)

Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Xen / EC2 release criteria proposal

[Dusty Mabe]

On 8/9/19 8:56 PM, Adam Williamson wrote:
> Hey folks! I'm starting a new thread for this to trim the recipient
> list a bit and include devel@ and coreos@.

Hey Adam!

> 
> The Story So Far: there is a Fedora release criterion which requires
> Fedora to boot on Xen:
> 
> "The release must boot successfully as Xen DomU with releases providing
> a functional, supported Xen Dom0 and widely used cloud providers
> utilizing Xen."
> 
> We (QA group) had a discussion about removing this criterion entirely.
> That has now morphed into the idea that we should tweak it to be
> focused exclusively on the "widely used cloud providers utilizing
> Xen"...by which we mean EC2. At the time this criterion was invented,
> all EC2 instance types used Xen; now, some still use Xen, and some use
> KVM.
> 
> So it seems like this would also be a good opportunity to revisit and
> nail down more specifically exactly what our cloud requirements are.
> bcotton suggested  that we require two sample instance types to be
> tested, c5.large (KVM) and t3.large (Xen). (I've also mailed Thomas
> Cameron, ex-of Red Hat, now of Amazon, for his opinion, as it seemed
> like it might be worthwhile - he's promised to get back to me).
> 
> So, for now, let me propose this as a trial balloon: we rewrite the
> above criterion to say:
> 
> "Release-blocking cloud disk images must be published to Amazon EC2 as
> AMIs, and these must boot successfully and meet other relevant release
> criteria on c5.large and t3.large instance types."

Sounds good to me if we trim it down to a few instance types that we think
will cover Xen and KVM based booting in EC2. For Fedora CoreOS we'll be doing
some automated testing in EC2. I don't know if we have a certain set of instance
types we'll be using for that, but the information that Matt provided should
help us decide.

Dusty 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: cloud-init regression F30 cloud image

[Dusty Mabe]

On 8/7/19 4:48 PM, Michael Gugino wrote:
> Looks like https://bugzilla.redhat.com/show_bug.cgi?id=1596062 has
> come back based on my testing on GCE.
> 
> https://pagure.io/cloud-sig/issue/289
> 
> logs: https://gist.github.com/michaelgugino/342f08608c4795c8241d38d9a72e3261
> 
> related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1644692
> 
> Thoughts?
> 


Hey Mike,

Unfortunately we don't currently offer images for GCE. If you're interested in 
helping
out with that effort let me know and we can try to get some people together.

In the mean time here is one guide for how to get going: 
https://major.io/2019/08/07/fedora-30-on-google-compute-engine/

Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: [atomic-devel] Failed to deploy/upgrade on Fedora Atomic 29

[Dusty Mabe]

On 7/15/19 10:33 PM, Feilong Wang wrote:
> Hello, could anybody please take a look at this issue? Thanks.

Hi Feilong,

> 
> On Thu, Jul 11, 2019 at 9:43 AM Feilong Wang  > wrote:
> 
> Hi team,
> 
> Now I'm testing upgrade for Fedora Atomic 29 image, but when I run 
> command "atomic host deploy " I got below error. Could you please 
> help me understand how to fix this? Thank you in advance.
> 
> /[root@test-fc29 log]# atomic host status
> /usr/lib/python3.7/site-packages/Atomic/util.py:469: YAMLLoadWarning: 
> calling yaml.load() without Loader=... is deprecated, as the default Loader 
> is unsafe. Please read https://msg.pyyaml.org/load for full details.
>   return yaml_load(conf_file)
> State: idle
> AutomaticUpdates: disabled
> Deployments:
> * ostree://fedora-atomic:fedora/29/x86_64/atomic-host
>                    Version: 29.20190528.0 (2019-05-28T00:23:56Z)
>                     Commit: 
> cb50ac29d58f4e7e8dcfc3c2dd4156c6acd17038577437e4744edee7b7c02eda
>               GPGSignature: Valid signature by 
> 5A03B4DD8254ECA02FDA1637A20AA56B429476B4
> [root@test-fc29 log]# atomic host deploy 
> cb50ac29d58f4e7e8dcfc3c2dd4156c6acd17038577437e4744edee7b7c02eda
> /usr/lib/python3.7/site-packages/Atomic/util.py:469: YAMLLoadWarning: 
> calling yaml.load() without Loader=... is deprecated, as the default Loader 
> is unsafe. Please read https://msg.pyyaml.org/load for full details.
>   return yaml_load(conf_file)
> Validating checksum 
> 'cb50ac29d58f4e7e8dcfc3c2dd4156c6acd17038577437e4744edee7b7c02eda'
> error: While fetching mirrorlist 
> 'https://ostree.fedoraproject.org/mirrorlist': While fetching 
> https://ostree.fedoraproject.org/mirrorlist: [6] Couldn't resolve host name

That's odd. It seems to work for me.

Are you still having trouble? Can you tell me what is in the files in your 
/etc/ostree/remotes.d/ directory?

Dusty 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Fedora Atomic Host Two Week Release Announcement: 29.20190625.0

[Dusty Mabe]

On 6/25/19 1:38 PM, nore...@fedoraproject.org wrote:
> 
> A new Fedora Atomic Host update is available via an OSTree update:
> 
> Version: 29.20190625.0
> Commit(x86_64): 
> c50cc86ad7972f85853f1deafda3899eb86a0e5220c613744eed64320298716e
> Commit(aarch64): 
> 0e82ac50808a1513cab1f8ad4c6262c091b19f39e3dfad8f22c2252aec38fd34
> Commit(ppc64le): 
> 72c06a8c8c18ff47ae9f7385a322dee325480ccc8a9276eafe9ac18b9a296422
> 
> 
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
> 
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
> 
> Corresponding image media for new installations can be downloaded from:
> 
> https://getfedora.org/en/atomic/download/
> 
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190625.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190625.0.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190625.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190625.0.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190625.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-29-20190625.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190625.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190625.0.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190625.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190625.0.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190625.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-29-20190625.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190625.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190625.0.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190625.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190625.0.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190625.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20190625.0.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190625.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20190625.0.x86_64.vagrant-virtualbox.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190625.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-29-20190625.0.iso
> 
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190625.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190625.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190625.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-29-20190625.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190625.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190625.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190625.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-29-20190625.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190625.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190625.0-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190625.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-29-20190625.0-x86_64-CHECKSUM
> 
> For direct download, the "latest" targets are always available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest
> https://getfedora.org/atomic_raw_x86_64_latest
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest
> 
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest
> https://getfedora.org/atomic_raw_aarch64_latest
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest
> 
> ppc64le:
> https://getfedora.org/atomic_qcow2_ppc64le_latest
> https://getfedora.org/atomic_raw_ppc64le_latest
> https://getfedora.org/atomic_dvd_ostree_ppc64le_latest
> 
> Filename fetching URLs are available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest_filename
> https://getfedora.org/atomic_raw_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename
> 
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest_filename
> https://getfedora.org/atomic_raw_aarch64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest_filename
> 

Re: Fedora Atomic Host Two Week Release Announcement: 29.20190516.0

[Dusty Mabe]

On 5/16/19 6:27 PM, nore...@fedoraproject.org wrote:
> 
> A new Fedora Atomic Host update is available via an OSTree update:
> 
> Version: 29.20190516.0
> Commit(x86_64): 
> 7f719bf60b865ca96aacd0e8ae3e6074c7eb5783d8ceb9003dbba5dfd5a29ba3
> Commit(aarch64): 
> 3930a03b8ffcce1aa66f17b8811e2a4da80aedb8234a1f47b62d603986b580ec
> Commit(ppc64le): 
> 144bb02d1485234b79ba385b47dc64199a7df159d3a0a3f17837cc7fb90cf7e1
> 
> 
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
> 
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
> 
> Corresponding image media for new installations can be downloaded from:
> 
> https://getfedora.org/en/atomic/download/
> 
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190516.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190516.0.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190516.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190516.0.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190516.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-29-20190516.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190516.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190516.0.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190516.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190516.0.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190516.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-29-20190516.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190516.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190516.0.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190516.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190516.0.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190516.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20190516.0.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190516.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20190516.0.x86_64.vagrant-virtualbox.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190516.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-29-20190516.0.iso
> 
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190516.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190516.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190516.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-29-20190516.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190516.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190516.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190516.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-29-20190516.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190516.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190516.0-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190516.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-29-20190516.0-x86_64-CHECKSUM
> 
> For direct download, the "latest" targets are always available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest
> https://getfedora.org/atomic_raw_x86_64_latest
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest
> 
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest
> https://getfedora.org/atomic_raw_aarch64_latest
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest
> 
> ppc64le:
> https://getfedora.org/atomic_qcow2_ppc64le_latest
> https://getfedora.org/atomic_raw_ppc64le_latest
> https://getfedora.org/atomic_dvd_ostree_ppc64le_latest
> 
> Filename fetching URLs are available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest_filename
> https://getfedora.org/atomic_raw_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename
> 
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest_filename
> https://getfedora.org/atomic_raw_aarch64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest_filename
> 

Re: Fedora Atomic Host Two Week Release Announcement: 29.20190513.0

[Dusty Mabe]

On 5/15/19 8:25 AM, Sven Kieske wrote:
> Hi,
> 
> is there a reason why _all_ links below:
> 
> https://getfedora.org/en/atomic/*
> 
> are dead?
> 
> I always get, e.g.:
> 
> Not Found
> 
> The requested URL /en/atomic/download/ was not found on this server.
> Apache Server at getfedora.org Port 443

Hey Sven,

Thanks for reporting this. There was a recent update to the getfedora.org 
website and I imagine the redirects that we had set up no longer work.

I have opened this ticket to track fixing it: 
https://pagure.io/fedora-infrastructure/issue/7802

Dusty

> 
> Am 13.05.19 um 21:09 schrieb nore...@fedoraproject.org:
>> Corresponding image media for new installations can be downloaded from:
>>
>> https://getfedora.org/en/atomic/download/
> 
> 
> ___
> devel mailing list -- de...@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org
> 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Fedora 30 Beta Release Readiness meeting

[Dusty Mabe]

On 3/15/19 5:23 PM, M. Edward (Ed) Borasky wrote:
> Is Silverblue on the same go-no go schedule as the rest of the versions?

yes
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Fedora Cloud SIG github organization

[Dusty Mabe]

On 3/7/19 2:56 PM, Clement Verna wrote:
> Hi all,
> 
> For a while now I take care to update the Fedora container image on Docker 
> Hub using this repo https://github.com/fedora-cloud/docker-brew-fedora. I 
> would like to make this a bit easier and self serviced using a jenkins 
> pipeline. For that I would need administration write to add to that repo so 
> that I can create the tokens needed by jenkins.
> 
> Would it be possible to add me to the github organization ? and give me admin 
> permission to this repo.

Done!
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Cloud/Server merge

[Dusty Mabe]

On 1/29/19 7:20 AM, Matthew Miller wrote:
> Okay, we've talked about this but not actually done anything because
> everyone is busy. Here's my proposal for F30: not actually do anything
> different, but, we are redesigning the website, and I think we should
> consolidate Cloud into the Fedora Server section as a download/launch
> option. What do you think?
> 


I'm not opposed. Maybe we can have cloud.fedoraproject.org redirect to
the "cloud" section of the server download page? 

Dusty 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Fedora 29 Atomic and Cloud Test Day on Monday, 1st October

[Dusty Mabe]

On 09/28/2018 12:42 PM, Sinny Kumari wrote:
> Hi all,
> 
> We are organizing Atomic and Cloud Test Day on Monday, 1st October. This
> Test Day is to make sure that Atomic Host and Cloud artifacts are working as
> expected in Fedora 29. If something is broken, we catch it and fix them as
> soon as possible to make sure they are all set before Fedora 29 GA.
> 
> Details about this Test Day are available in wiki page
> https://fedoraproject.org/wiki/Test_Day:2018-10-01_Cloud-Atomic_Testday .
> Once you are done with testing, please enter your results at
> http://testdays.fedorainfracloud.org/events/49 .
> 
> See you all on Monday!
> 

Just rebased one of my f28AH boxes to f29. All looking good so far!

Dusty 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Fedora Atomic Host Two Week Release Announcement: 28.20180917.0

[Dusty Mabe]

On 09/17/2018 03:19 PM, nore...@fedoraproject.org wrote:
> 
> A new Fedora Atomic Host update is available via an OSTree update:
> 
> Version: 28.20180917.0
> Commit(x86_64): 
> 17b11d74047ded1264a57555a64ae6fc5d02a332c556679bfcf32864fc91f11e
> Commit(aarch64): 
> 95cdc6d02ed7f3645bdd513b07b2c2db9b04e91d8aae897fa88e378285a2b551
> Commit(ppc64le): 
> ca3012e5792f84499783510e5586526b9eaf8d98f535e3de0157ec7f7ad369ae
> 

FYI. With this release you may notice long boot times for VMs as the VM waits 
for
enough entropy to continue. This should be fixed soon. Follow this [1] issue and
this [2] bodhi update in order to receive updates on that status. 

[1] https://pagure.io/atomic-wg/issue/511
[2] https://bodhi.fedoraproject.org/updates/FEDORA-2018-f93103ae20



___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Man pages in cloud images - documentation

[Dusty Mabe]

On 06/29/2018 03:23 AM, Gergely Gombos wrote:
>
> So my solution proposal:
> 
>   *
> I'm going to create PRs to add this piece of info to the Scaleway Fedora 
> (https://github.com/scaleway/image-fedora), Docker Brew 
> (https://github.com/fedora-cloud/docker-brew-fedora), and possibly Docker 
> library (https://hub.docker.com/_/fedora/) readmes. Just a warning that 
> documentation has been permanently turned off, referencing to this 
> discussion: https://github.com/fedora-cloud/docker-brew-fedora/issues/9
>   *
> I'll create an RFE for DNF (instead of man) - to show a warning when 
> tsflags have been set. Even something like: "Current transaction flags: 
> [...]" would be sufficient. This at least informs the user about the 
> configuration.
> 
> What do you think?

Sounds good to me for DNF RFE. That would be useful.

Sorry about the delayed reply.

Dusty 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/message/TW2SWXZGCYACNTTLLX5EYXPVFZ4Z6CLR/

Re: Man pages in cloud images - documentation

[Dusty Mabe]

On 06/28/2018 05:38 AM, Gergely Gombos wrote:
> Hello,

Hi Greg,

> 
> I just installed a F28 image on a Scaleway cloud server. Runs fine, except 
> there were no man pages, even after installing man-pages package.
> 
> It turned out after a lot of searching that this is not a bug but a feature.
> 
> Issue on GitHub: 
> https://github.com/fedora-cloud/docker-brew-fedora/issues/9#issuecomment-365176011
> 
> So the culprit is the Kickstarts file, here: 
> https://pagure.io/fedora-kickstarts/blob/master/f/fedora-docker-common.ks#_32 
> (and other nearby .ks files)
> It says "%packages --excludedocs --instLangs=en --nocore  [...]"
> 
> According to the Kickstart docs 
> (http://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#chapter-4-package-selection)
>  this won't install man pages, presumably to save space, but the end user 
> won't know this, because man will simply not find any man pages and that's it.
> 
> A solution was to edit /etc/dnf/dnf.conf, comment "tsflags=nodocs" and then 
> reinstall everything with dnf reinstall.
> 
> My question: I understand that it's important to save space with containers, 
> but often cloud users wish to use man pages, as they are using the cloud 
> server just as any remote computer. Is there a way to document the above 
> situation e.g. when the user tries to view a man page gets a notification 
> about why they are not installed (and how to install them)?

This is subjective to who you are, but here is my opinion. A "Cloud" server is
usually one that is spun up and provisioned automatically (i.e. a person does
not SSH into the machine to configure it). The cloud instance has a specific
purpose and can be thrown away easily and re-provisioned. In this scenario docs
are wasted space and people generally value smaller image size over having the
documentation.

Now there are certainly cases where you just spin up a cloud instance and want
to configure it yourself, but that's not what we're optimizing for. It would be
nice if 'man' were able to detect this situation and offer an alternative. Maybe
open an RFE BZ against man for this??

- Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/message/7XWQ3RAQWZNQ55P3UXNCVTIN7E6KVTTU/

Re: More frequent Fedora Cloud updates

[Dusty Mabe]

On 06/18/2018 03:25 AM, Peter Robinson wrote:
> On Fri, Jun 15, 2018 at 10:21 PM, Joe Doss  wrote:
>> Hello!
>>
>> One major pain point that Fedora Cloud currently faces is the fact that once
>> a new Fedora release comes out, the cloud images are no longer updated over
>> time. This brings a poor user experience if bugs that are fixed later on in
>> the current release cycle but are painful on the first boot of a Fedora
>> Cloud instance until the user updates the instance.
> 
> That's not entirely true, the cloud images are updated for major
> security events. They are also built every day [1]. The issue is to
> date there's not been a proper process in which they're
> updated/communicated etc. Over all I welcome what you generally
> propose.

Yeah we build images every night (I talked to Joe about it), but as far
as I know we haven't "released" any updated images after GA, even for security
issues, for some time.

Dusty
 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/message/PHXHN5ZQP6YOAUE4H4HQT5R3H6FUR2A2/

Re: Fedora Atomic Host Two Week Release Announcement: 28.20180613.0

[Dusty Mabe]

On 06/13/2018 06:23 PM, nore...@fedoraproject.org wrote:
> 
> A new Fedora Atomic Host update is available via an OSTree update:
> 
> Version: 28.20180613.0
> Commit(x86_64): 
> c51100f14cf12b25c16562cede7455191e536c0534e3b2ef87e66be9e12899ae
> Commit(aarch64): 
> 5492bb19612e4c9e4f93c63e0af81e6b5f896ac95e1b18c29d11c5f7cecdcc05
> Commit(ppc64le): 
> c6c10a323d55f6782fc7cf575d2f7d46d2a507e6fb475645fec13a7837268f46
> 
> 
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
> 
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
> 
> Corresponding image media for new installations can be downloaded from:
> 
> https://getfedora.org/en/atomic/download/
> 
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180613.1/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180613.1.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180613.1/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180613.1.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180613.1/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-28-20180613.1.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180613.1/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180613.1.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180613.1/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180613.1.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180613.1/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-28-20180613.1.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180613.1/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180613.1.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180613.1/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180613.1.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180613.1/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180613.1.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180613.1/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180613.1.x86_64.vagrant-virtualbox.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180613.1/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-28-20180613.1.iso
> 
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180613.1/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180613.1-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180613.1/AtomicHost/aarch64/iso/Fedora-AtomicHost-28-20180613.1-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180613.1/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180613.1-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180613.1/AtomicHost/ppc64le/iso/Fedora-AtomicHost-28-20180613.1-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180613.1/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180613.1-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180613.1/AtomicHost/x86_64/iso/Fedora-AtomicHost-28-20180613.1-x86_64-CHECKSUM
> 
> For direct download, the "latest" targets are always available here:
> https://getfedora.org/atomic_iso_latest
> https://getfedora.org/atomic_qcow2_latest
> https://getfedora.org/atomic_raw_latest
> https://getfedora.org/atomic_vagrant_libvirt_latest
> https://getfedora.org/atomic_vagrant_virtualbox_latest
> 
> Filename fetching URLs are available here:
> https://getfedora.org/atomic_iso_latest_filename
> https://getfedora.org/atomic_qcow2_latest_filename
> https://getfedora.org/atomic_raw_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_latest_filename
> 
> For more information about the latest targets, please reference the Fedora
> Atomic Wiki space.
> 
> 
> https://fedoraproject.org/wiki/Atomic_WG#Fedora_Atomic_Image_Download_Links
> 
> Do note that it can take some of the mirrors up to 12 hours to "check-in" at
> their own discretion.
> 
> Thank you,
> Fedora Release Engineering
> 


This week's release of Fedora 28 Atomic Host comes with a new Docker, Podman, 
Skopeo. Also oci-register-machine was dropped and skopeo-containers was 
renamed to containers-common.

Note that we are shipping AMIs with longer resource IDs in anticipation of 
the July cut off for short resource IDs in AWS. Unfortunately the eu-central-1
and sa-east-1 regions got 

Re: Fedora Atomic Host Two Week Release Announcement: 28.20180527.0

[Dusty Mabe]

On 05/29/2018 03:06 PM, nore...@fedoraproject.org wrote:
> 
> A new Fedora Atomic Host update is available via an OSTree update:
> 
> Version: 28.20180527.0
> Commit(x86_64): 
> 291ea90da29bc5abe757b5a50813b3de1396b08412939a89b3b671aba9856093
> Commit(aarch64): 
> f3f1b43c6bb1fa705d36f4e2b470e1dc510af421b3d122457f21f1664b37182e
> Commit(ppc64le): 
> 372a253acef6db9acced3d1cb09090473567d10a2a9e5d488f487e7df441c696
> 
> 
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
> 
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
> 
> Corresponding image media for new installations can be downloaded from:
> 
> https://getfedora.org/en/atomic/download/
> 
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180528.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180528.0.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180528.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180528.0.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180528.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-28-20180528.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180528.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180528.0.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180528.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180528.0.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180528.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-28-20180528.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180528.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180528.0.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180528.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180528.0.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180528.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180528.0.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180528.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180528.0.x86_64.vagrant-virtualbox.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180528.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-28-20180528.0.iso
> 
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180528.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180528.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180528.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-28-20180528.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180528.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180528.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180528.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-28-20180528.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180528.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180528.0-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180528.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-28-20180528.0-x86_64-CHECKSUM
> 
> For direct download, the "latest" targets are always available here:
> https://getfedora.org/atomic_iso_latest
> https://getfedora.org/atomic_qcow2_latest
> https://getfedora.org/atomic_raw_latest
> https://getfedora.org/atomic_vagrant_libvirt_latest
> https://getfedora.org/atomic_vagrant_virtualbox_latest
> 
> Filename fetching URLs are available here:
> https://getfedora.org/atomic_iso_latest_filename
> https://getfedora.org/atomic_qcow2_latest_filename
> https://getfedora.org/atomic_raw_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_latest_filename
> 
> For more information about the latest targets, please reference the Fedora
> Atomic Wiki space.
> 
> 
> https://fedoraproject.org/wiki/Atomic_WG#Fedora_Atomic_Image_Download_Links
> 
> Do note that it can take some of the mirrors up to 12 hours to "check-in" at
> their own discretion.
> 
> Thank you,
> Fedora Release Engineering


This is our third release of Fedora 28 Atomic Host. This release
contains a security fix for CVE-2018-3639: 
https://access.redhat.com/security/cve/cve-2018-3639
and other updated packages such as podman and rpm-ostree.

An example of the diff between this and the previous released version (for 
x86_64) is:

ostree diff commit old: 

Re: Fedora Atomic Host Two Week Release Announcement: 28.20180515.1

[Dusty Mabe]

On 05/16/2018 02:03 PM, nore...@fedoraproject.org wrote:
> 
> A new Fedora Atomic Host update is available via an OSTree update:
> 
> Version: 28.20180515.1
> Commit(x86_64): 
> a29367c58417c28e2bd8306c1f438b934df79eba13706e078fe8564d9e0eb32b
> Commit(aarch64): 
> ec501e5a6833e6117632c3a7fc90ef17530399b6411ad9ba2c5c85f22cabe8dd
> Commit(ppc64le): 
> dfe24e5d495ec16fbe2d61e6b494def2b119301f6565b8b6ecd542d79b02df89
> 
> 
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
> 
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
> 
> Corresponding image media for new installations can be downloaded from:
> 
> https://getfedora.org/en/atomic/download/
> 
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180515.1/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180515.1.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180515.1/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180515.1.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180515.1/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-28-20180515.1.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180515.1/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180515.1.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180515.1/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180515.1.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180515.1/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-28-20180515.1.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180515.1/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180515.1.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180515.1/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180515.1.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180515.1/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180515.1.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180515.1/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180515.1.x86_64.vagrant-virtualbox.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180515.1/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-28-20180515.1.iso
> 
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180515.1/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180515.1-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180515.1/AtomicHost/aarch64/iso/Fedora-AtomicHost-28-20180515.1-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180515.1/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180515.1-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180515.1/AtomicHost/ppc64le/iso/Fedora-AtomicHost-28-20180515.1-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180515.1/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180515.1-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180515.1/AtomicHost/x86_64/iso/Fedora-AtomicHost-28-20180515.1-x86_64-CHECKSUM
> 
> For direct download, the "latest" targets are always available here:
> https://getfedora.org/atomic_iso_latest
> https://getfedora.org/atomic_qcow2_latest
> https://getfedora.org/atomic_raw_latest
> https://getfedora.org/atomic_vagrant_libvirt_latest
> https://getfedora.org/atomic_vagrant_virtualbox_latest
> 
> Filename fetching URLs are available here:
> https://getfedora.org/atomic_iso_latest_filename
> https://getfedora.org/atomic_qcow2_latest_filename
> https://getfedora.org/atomic_raw_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_latest_filename
> 
> For more information about the latest targets, please reference the Fedora
> Atomic Wiki space.
> 
> 
> https://fedoraproject.org/wiki/Atomic_WG#Fedora_Atomic_Image_Download_Links
> 
> Do note that it can take some of the mirrors up to 12 hours to "check-in" at
> their own discretion.
> 
> Thank you,
> Fedora Release Engineering
> 

This is our second release of Fedora 28 Atomic Host. This release contains
a security fix for CVE-2018-: 
https://access.redhat.com/security/cve/cve-2018-
It also contains a new kernel, systemd, ostree, selinux, podman, etc.
Note in the diff output below that buildah was removed. buildah is no
longer a dependency for `podman build` to work so the 

Re: Kernel update breaks GCE VM (or: how to update kernel)

[Dusty Mabe]

On 05/04/2018 02:28 PM, spike wrote:
> Hi,
> 
> I've got a Fedora 28 image running on GCP which is basically just the raw 
> disk image found in Fedora-Cloud-Base-28-1.1.x86_64.raw.xz. For the record, 
> here's how I instantiated the VM:
> 
> xz --decompress Fedora-Cloud-Base-28-1.1.x86_64.raw.xz
> mv Fedora-Cloud-Base-28-1.1.x86_64.raw disk.raw
> tar cfz Fedora-Cloud-Base-28-1.1.x86_64.tar.gz disk.raw --sparse
> gsutil cp Fedora-Cloud-Base-28-1.1.x86_64.tar.gz gs://fedora-cloud-base/
> gcloud compute images create --source-uri 
> gs://fedora-cloud-base/Fedora-Cloud-Base-28-1.1.x86_64.tar.gz 
> fedora-cloud-base-28
> gcloud compute instances create fedora28 --machine-type f1-micro --image 
> fedora-cloud-base-28 --zone us-east1-b
> 
> So far so good. Everything works as expected and I can log into the VM with 
> 'gcloud compute ssh fedora@fedora28'.
> 
> However, as soon as I run 'dnf update', or to be more specific, as soon as I 
> update the 'kernel-core' package and reboot the VM, it takes hours (yes, 
> literally) for it to come up again. The log output I can grab over the serial 
> port is not particularly helpful 
> (https://paste.fedoraproject.org/paste/reRXgIX-z0bz0W~dw33b8A).

You are seeing bug https://bugzilla.redhat.com/show_bug.cgi?id=1572944

Follow https://bodhi.fedoraproject.org/updates/FEDORA-2018-cf65b3a7a2

You can grab the new kernel from the updates-testing repo 'dnf update kernel 
--enablerepo=updates-testing'

> 
> I'm quite sure I'm just missing the obvious here. How does one usually update 
> the kernel inside a GCE VM?
> 
> Cheers!
> ___
> cloud mailing list -- cloud@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
> 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Fedora Atomic Host Two Week Release Announcement: 28.20180425.0

[Dusty Mabe]

A new Fedora Atomic Host update is available via an OSTree update:

Version: 28.20180425.0
Commit(x86_64): 94a9d06eef34aa6774c056356d3d2e024e57a0013b6f8048dbae392a84a137ca
Commit(aarch64): 
12a95314084eaa2242bdfe24197774aac163433d2405bc2813b4d89180434630
Commit(ppc64le): 
d29c4549226ca8a50846360cf2f7149fbe15b4ab9d1c91d0d2aff1858b3ab1f3

This is our first release of Fedora 28 Atomic Host! We will be sending out blog
posts covering new features and upgrades very soon. In the meantime here is how
you go from F27 to F28:

# sudo ostree remote add --set=gpg-verify=true 
--set=gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-28-primary atomicrepo 
https://dl.fedoraproject.org/atomic/repo/
# sudo rpm-ostree rebase atomicrepo:fedora/28/x86_64/atomic-host


We are releasing images from multiple architectures but please note
that x86_64 architecture is the only one that undergoes automated
testing at this time.

Existing systems can be upgraded in place via e.g. `atomic host upgrade`.

Corresponding image media for new installations can be downloaded from:

https://getfedora.org/en/atomic/download/

Alternatively, image artifacts can be found at the following links:
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180425.0.aarch64.qcow2
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180425.0.aarch64.raw.xz
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-28-20180425.0.iso
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180425.0.ppc64le.qcow2
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180425.0.ppc64le.raw.xz
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-28-20180425.0.iso
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180425.0.x86_64.qcow2
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180425.0.x86_64.raw.xz
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180425.0.x86_64.vagrant-libvirt.box
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180425.0.x86_64.vagrant-virtualbox.box
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-28-20180425.0.iso

Respective signed CHECKSUM files can be found here:
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180425.0-aarch64-CHECKSUM
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-28-20180425.0-aarch64-CHECKSUM
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180425.0-ppc64le-CHECKSUM
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-28-20180425.0-ppc64le-CHECKSUM
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180425.0-x86_64-CHECKSUM
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180425.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-28-20180425.0-x86_64-CHECKSUM

For direct download, the "latest" targets are always available here:
https://getfedora.org/atomic_iso_latest
https://getfedora.org/atomic_qcow2_latest
https://getfedora.org/atomic_raw_latest
https://getfedora.org/atomic_vagrant_libvirt_latest
https://getfedora.org/atomic_vagrant_virtualbox_latest

Filename fetching URLs are available here:
https://getfedora.org/atomic_iso_latest_filename
https://getfedora.org/atomic_qcow2_latest_filename
https://getfedora.org/atomic_raw_latest_filename
https://getfedora.org/atomic_vagrant_libvirt_latest_filename
https://getfedora.org/atomic_vagrant_virtualbox_latest_filename

The AMIs for this release are here:

Fedora-AtomicHost-28-20180425.0.x86_64 ap-northeast-1 ami-cb17f1b4 hvm standard
Fedora-AtomicHost-28-20180425.0.x86_64 ap-northeast-2 ami-70fc551e hvm standard
Fedora-AtomicHost-28-20180425.0.x86_64 ap-south-1 ami-833110ec hvm standard
Fedora-AtomicHost-28-20180425.0.x86_64 ap-southeast-1 ami-4ddbf431 hvm standard
Fedora-AtomicHost-28-20180425.0.x86_64 ap-southeast-2 ami-7b65af19 hvm standard

Re: Fedora Atomic Host Two Week Release Announcement: 27.122

[Dusty Mabe]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On 04/19/2018 05:55 PM, nore...@fedoraproject.org wrote:
> 
> A new Fedora Atomic Host update is available via an OSTree update:
> 
> Version: 27.122
> Commit(x86_64): 
> 931ebb3941fc49af706ac5a90ad3b5a493be4ae35e85721dabbfd966b1ecbf99
> Commit(aarch64): 
> 837cd0c5e3a5656316ebf6142315ac107c8592d5c8d64a02e8a62919eee9f46f
> Commit(ppc64le): 
> a1f565d73f1f1b6f6d7ef992251f21a704c4a8de40c41fc62be69c5ec2a65329
> 
> 
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
> 
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
> 
> Corresponding image media for new installations can be downloaded from:
> 
> https://getfedora.org/en/atomic/download/
> 
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/Atomic/aarch64/iso/Fedora-Atomic-ostree-aarch64-27-20180419.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/Atomic/ppc64le/iso/Fedora-Atomic-ostree-ppc64le-27-20180419.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-27-20180419.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/aarch64/images/Fedora-Atomic-27-20180419.0.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/aarch64/images/Fedora-Atomic-27-20180419.0.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/ppc64le/images/Fedora-Atomic-27-20180419.0.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/ppc64le/images/Fedora-Atomic-27-20180419.0.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/x86_64/images/Fedora-Atomic-27-20180419.0.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/x86_64/images/Fedora-Atomic-27-20180419.0.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20180419.0.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20180419.0.x86_64.vagrant-virtualbox.box
> 
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/Atomic/aarch64/iso/Fedora-Atomic-27-20180419.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/Atomic/ppc64le/iso/Fedora-Atomic-27-20180419.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/Atomic/x86_64/iso/Fedora-Atomic-27-20180419.0-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/aarch64/images/Fedora-CloudImages-27-20180419.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/ppc64le/images/Fedora-CloudImages-27-20180419.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419.0/CloudImages/x86_64/images/Fedora-CloudImages-27-20180419.0-x86_64-CHECKSUM
> 
> For direct download, the "latest" targets are always available here:
> https://getfedora.org/atomic_iso_latest
> https://getfedora.org/atomic_qcow2_latest
> https://getfedora.org/atomic_raw_latest
> https://getfedora.org/atomic_vagrant_libvirt_latest
> https://getfedora.org/atomic_vagrant_virtualbox_latest
> 
> Filename fetching URLs are available here:
> https://getfedora.org/atomic_iso_latest_filename
> https://getfedora.org/atomic_qcow2_latest_filename
> https://getfedora.org/atomic_raw_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_latest_filename
> 
> For more information about the latest targets, please reference the Fedora
> Atomic Wiki space.
> 
> 
> https://fedoraproject.org/wiki/Atomic_WG#Fedora_Atomic_Image_Download_Links
> 
> Do note that it can take some of the mirrors up to 12 hours to "check-in" at
> their own discretion.
> 
> Thank you,
> Fedora Release Engineering
>

Hi everyone!

We apologize for the delay in getting this release out the door. As a
bonus for the wait we have AMIs that are available in additional regions
(ap-northeast-2, ap-south-1). We'll be adding additional regions (the
remaining missing regions) next release.

Additionally, this will most likely be our last release of Fedora 27 Atomic
Host. Very soon Fedora 28 will be released and we will 

Re: Cloud Base validation tests missing for Fedora 28 Beta

[Dusty Mabe]

On 04/04/2018 01:43 PM, Joe Doss wrote:
> I was signed in when I tried to fill out the wiki page. I just checked again 
> and it states You need to have at least CLA+1 (group). I just checked my 
> Fedora account and I am approved in the cla_done group. Is there another one 
> I need to apply for?
> 

Hey.. Apparently this text should say:

"You need to have CLA groups, plus one additional non CLA group"

You've been added to the wikiedit group so you should be good now. 

Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Stop creating PV AMIs in AWS

[Dusty Mabe]

FYI: https://pagure.io/cloud-sig/issue/284

We are going to stop creating/releasing PV AMIs in AWS. We've never
created them for Atomic Host and we'd like to stop creating them for
cloud as it is another avenue for us to test.

Dusty 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Cloud Base validation tests missing for Fedora 28 Beta

[Dusty Mabe]

On 03/30/2018 10:34 AM, Joe Doss wrote:
> I spun up Fedora 28 Beta 1.3 Cloud AMI in us-west-2, ran through the tests 
> and it had no issues aside from selinux-policy needed to get updated to 
> selinux-policy-3.14.1-19.fc28 
> (https://bodhi.fedoraproject.org/updates/FEDORA-2018-234de0ee13) so you can 
> start services like Nginx.

Thanks!

> 
> I would fill out the wiki page to check some boxes but it looks like I need 
> some special privs to do so. 
> 
>> You need to have at least CLA+1 (group)

I think this should be covered if you have a fedora account. You have to be 
signed in. Can you try again? 

> 
> Let me know if you folks need anything else tested.
> ___
> cloud mailing list -- cloud@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
> 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Cloud Base validation tests missing for Fedora 28 Beta

[Dusty Mabe]

On 03/29/2018 08:56 AM, Dusty Mabe wrote:
> 
> 
> On 03/28/2018 09:48 PM, Adam Williamson wrote:
>> Hi folks! I noticed that none of the Base validation tests for Cloud
>> have been run for F28 Beta:
>>
>> https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
>>
>> It'd be great if we could get those filled out. We are also missing the
>> Cloud validation tests for actual cloud environments (EC2 and
>> Openstack):
>>
>> https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
>>
>> Note some Cloud images are still considered release blocking at
>> present:
>>
>> https://fedoraproject.org/wiki/Releases/28/ReleaseBlocking
>>
>> so we do need these tests. Thanks!
>>
> 
> I just pinged some people to ask them to help with testing. I've
> been using the vagrant images from f28 almost continuously for the
> past few weeks so at least that angle should be covered.
> 

Also.. Here is the list of AMIs for Beta 1.3:

Fedora-Cloud-Base-28_Beta-1.3.x86_64  EC2 (ap-northeast-1) ami-cf4348b3hvm  
standard   
Fedora-Cloud-Base-28_Beta-1.3.x86_64  EC2 (ap-southeast-1) ami-b0dc85cchvm  
standard   
Fedora-Cloud-Base-28_Beta-1.3.x86_64  EC2 (ap-southeast-2) ami-717bb713hvm  
standard   
Fedora-Cloud-Base-28_Beta-1.3.x86_64  EC2 (eu-central-1)   ami-8b623f60hvm  
standard   
Fedora-Cloud-Base-28_Beta-1.3.x86_64  EC2 (eu-west-1)  ami-4207553bhvm  
standard   
Fedora-Cloud-Base-28_Beta-1.3.x86_64  EC2 (sa-east-1)  ami-4662352ahvm  
standard   
Fedora-Cloud-Base-28_Beta-1.3.x86_64  EC2 (us-east-1)  ami-b6a47fcbhvm  
standard   
Fedora-Cloud-Base-28_Beta-1.3.x86_64  EC2 (us-west-1)  ami-224c5d42hvm  
standard   
Fedora-Cloud-Base-28_Beta-1.3.x86_64  EC2 (us-west-2)  ami-a98c17d1hvm  
standard   
Fedora-Cloud-Base-28_Beta-1.3.x86_64  EC2 (ap-northeast-1) ami-78434804hvm  
gp2
Fedora-Cloud-Base-28_Beta-1.3.x86_64  EC2 (ap-southeast-1) ami-51de872dhvm  
gp2
Fedora-Cloud-Base-28_Beta-1.3.x86_64  EC2 (ap-southeast-2) ami-4775b925hvm  
gp2
Fedora-Cloud-Base-28_Beta-1.3.x86_64  EC2 (eu-central-1)   ami-91613c7ahvm  
gp2
Fedora-Cloud-Base-28_Beta-1.3.x86_64  EC2 (eu-west-1)  ami-111d4f68hvm  
gp2
Fedora-Cloud-Base-28_Beta-1.3.x86_64  EC2 (sa-east-1)  ami-e063348chvm  
gp2
Fedora-Cloud-Base-28_Beta-1.3.x86_64  EC2 (us-east-1)  ami-f4a47f89hvm  
gp2
Fedora-Cloud-Base-28_Beta-1.3.x86_64  EC2 (us-west-1)  ami-114a5b71hvm  
gp2
Fedora-Cloud-Base-28_Beta-1.3.x86_64  EC2 (us-west-2)  ami-128e156ahvm  
gp2

Dusty 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Cloud Base validation tests missing for Fedora 28 Beta

[Dusty Mabe]

On 03/28/2018 09:48 PM, Adam Williamson wrote:
> Hi folks! I noticed that none of the Base validation tests for Cloud
> have been run for F28 Beta:
> 
> https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
> 
> It'd be great if we could get those filled out. We are also missing the
> Cloud validation tests for actual cloud environments (EC2 and
> Openstack):
> 
> https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
> 
> Note some Cloud images are still considered release blocking at
> present:
> 
> https://fedoraproject.org/wiki/Releases/28/ReleaseBlocking
> 
> so we do need these tests. Thanks!
> 

I just pinged some people to ask them to help with testing. I've
been using the vagrant images from f28 almost continuously for the
past few weeks so at least that angle should be covered.

Dusty 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[cloud-sig] Issue #284: Deprecate releasing PV AMIs

[Dusty Mabe]

dustymabe added a new comment to an issue you are following:
``
yes please stop releasing PV images. 
``

To reply, visit the link below or just reply to this email
https://pagure.io/cloud-sig/issue/284
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [Fedocal] Reminder meeting : Fedora Cloud Workgroup

[Dusty Mabe]

On 03/26/2018 08:20 PM, Blu3 Dr33m wrote:
> HOW DO I ACCESS THE MEETING SERIOUSLY
>

Unfortunately we haven't been meeting regularly. I'd like to revamp that
and start having them again. Is there anything in particular you are interested
in?

Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[cloud-sig] Issue #283: F28 Vagrant fails to set network correctly

[Dusty Mabe]

The status of the issue: `F28 Vagrant fails to set network correctly` of 
project: `cloud-sig` has been updated to: Closed as fixed by dustymabe.

https://pagure.io/cloud-sig/issue/283
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[cloud-sig] Issue #283: F28 Vagrant fails to set network correctly

[Dusty Mabe]

dustymabe added a new comment to an issue you are following:
``
ok this should now be fixed by: 
https://pagure.io/fedora-kickstarts/pull-request/366
``

To reply, visit the link below or just reply to this email
https://pagure.io/cloud-sig/issue/283
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[cloud-sig] Issue #283: F28 Vagrant fails to set network correctly

[Dusty Mabe]

dustymabe added a new comment to an issue you are following:
``
Thanks for reporting. I'll look into this tomorrow. 
``

To reply, visit the link below or just reply to this email
https://pagure.io/cloud-sig/issue/283
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [atomic-announce] Fedora Atomic Host Two Week Release Announcement

[Dusty Mabe]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On 02/13/2018 03:02 PM, nore...@fedoraproject.org wrote:
> 
> A new Fedora Atomic Host update is available via an OSTree update:
> 
> Version: 27.81
> Commit(x86_64): 
> b25bde0109441817f912ece57ca1fc39efc60e6cef4a7a23ad9de51b1f36b742
> Commit(aarch64): 
> bb5bc5afbf27333a70c1f3bf8d0117baa45e862e0440be5c779cd5f0bb35aab4
> Commit(ppc64le): 
> e484af3c5a5c88c0de486eee195dff4c6c7ef41d07c41b5d356305db237066d7
> 
> 
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
> 
> Existing systems can be upgraded in place via e.g. `atomic host upgrade` or
> `atomic host deploy`.
> 
> Corresponding image media for new installations can be downloaded from:
> 
> https://getfedora.org/en/atomic/download/
> 
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180212.2/Atomic/aarch64/iso/Fedora-Atomic-ostree-aarch64-27-20180212.2.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180212.2/Atomic/ppc64le/iso/Fedora-Atomic-ostree-ppc64le-27-20180212.2.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180212.2/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-27-20180212.2.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180212.2/CloudImages/aarch64/images/Fedora-Atomic-27-20180212.2.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180212.2/CloudImages/aarch64/images/Fedora-Atomic-27-20180212.2.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180212.2/CloudImages/ppc64le/images/Fedora-Atomic-27-20180212.2.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180212.2/CloudImages/ppc64le/images/Fedora-Atomic-27-20180212.2.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180212.2/CloudImages/x86_64/images/Fedora-Atomic-27-20180212.2.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180212.2/CloudImages/x86_64/images/Fedora-Atomic-27-20180212.2.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180212.2/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20180212.2.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180212.2/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20180212.2.x86_64.vagrant-virtualbox.box
> 
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180212.2/Atomic/aarch64/iso/Fedora-Atomic-27-20180212.2-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180212.2/Atomic/ppc64le/iso/Fedora-Atomic-27-20180212.2-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180212.2/Atomic/x86_64/iso/Fedora-Atomic-27-20180212.2-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180212.2/CloudImages/aarch64/images/Fedora-CloudImages-27-20180212.2-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180212.2/CloudImages/ppc64le/images/Fedora-CloudImages-27-20180212.2-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180212.2/CloudImages/x86_64/images/Fedora-CloudImages-27-20180212.2-x86_64-CHECKSUM
> 
> For direct download, the "latest" targets are always available here:
> https://getfedora.org/atomic_iso_latest
> https://getfedora.org/atomic_qcow2_latest
> https://getfedora.org/atomic_raw_latest
> https://getfedora.org/atomic_vagrant_libvirt_latest
> https://getfedora.org/atomic_vagrant_virtualbox_latest
> 
> Filename fetching URLs are available here:
> https://getfedora.org/atomic_iso_latest_filename
> https://getfedora.org/atomic_qcow2_latest_filename
> https://getfedora.org/atomic_raw_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_latest_filename
> 
> For more information about the latest targets, please reference the Fedora
> Atomic Wiki space.
> 
> 
> https://fedoraproject.org/wiki/Atomic_WG#Fedora_Atomic_Image_Download_Links
> 
> Do note that it can take some of the mirrors up to 12 hours to "check-in" at
> their own discretion.
> 
> Thank you,
> Fedora Release Engineering

In this week's release of Fedora Atomic Host we have a new kernel, atomic CLI,
and runc.

An example of the diff between this and the previous released version (for 
x86_64) is:

ostree diff commit old: 
39848372585a65dc63fb3052f997139b8b30d6b55ce378337db3664177489d28
ostree diff commit new: 
b25bde0109441817f912ece57ca1fc39efc60e6cef4a7a23ad9de51b1f36b742
Upgraded:
  atomic 

Re: Fedora Atomic Host Two Week Release Announcement

[Dusty Mabe]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On 02/01/2018 06:51 PM, nore...@fedoraproject.org wrote:
> 
> A new Fedora Atomic Host update is available via an OSTree update:
> 
> Version: 27.72
> Commit(x86_64): 
> 39848372585a65dc63fb3052f997139b8b30d6b55ce378337db3664177489d28
> Commit(aarch64): 
> 8048d384f231f90a7479cf94bfe94053970fb9a0f196ba4485d779696db81fa1
> Commit(ppc64le): 
> 3fce2908406e41e2ffe533908e840f44311576befe7e49396d1894407341aef9
> 
> 
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
> 
> Existing systems can be upgraded in place via e.g. `atomic host upgrade` or
> `atomic host deploy`.
> 
> Corresponding image media for new installations can be downloaded from:
> 
> https://getfedora.org/en/atomic/download/
> 
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180201.0/Atomic/aarch64/iso/Fedora-Atomic-ostree-aarch64-27-20180201.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180201.0/Atomic/ppc64le/iso/Fedora-Atomic-ostree-ppc64le-27-20180201.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180201.0/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-27-20180201.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180201.0/CloudImages/aarch64/images/Fedora-Atomic-27-20180201.0.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180201.0/CloudImages/aarch64/images/Fedora-Atomic-27-20180201.0.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180201.0/CloudImages/ppc64le/images/Fedora-Atomic-27-20180201.0.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180201.0/CloudImages/ppc64le/images/Fedora-Atomic-27-20180201.0.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180201.0/CloudImages/x86_64/images/Fedora-Atomic-27-20180201.0.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180201.0/CloudImages/x86_64/images/Fedora-Atomic-27-20180201.0.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180201.0/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20180201.0.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180201.0/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20180201.0.x86_64.vagrant-virtualbox.box
> 
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180201.0/Atomic/aarch64/iso/Fedora-Atomic-27-20180201.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180201.0/Atomic/ppc64le/iso/Fedora-Atomic-27-20180201.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180201.0/Atomic/x86_64/iso/Fedora-Atomic-27-20180201.0-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180201.0/CloudImages/aarch64/images/Fedora-CloudImages-27-20180201.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180201.0/CloudImages/ppc64le/images/Fedora-CloudImages-27-20180201.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180201.0/CloudImages/x86_64/images/Fedora-CloudImages-27-20180201.0-x86_64-CHECKSUM
> 
> For direct download, the "latest" targets are always available here:
> https://getfedora.org/atomic_iso_latest
> https://getfedora.org/atomic_qcow2_latest
> https://getfedora.org/atomic_raw_latest
> https://getfedora.org/atomic_vagrant_libvirt_latest
> https://getfedora.org/atomic_vagrant_virtualbox_latest
> 
> Filename fetching URLs are available here:
> https://getfedora.org/atomic_iso_latest_filename
> https://getfedora.org/atomic_qcow2_latest_filename
> https://getfedora.org/atomic_raw_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_latest_filename
> 
> For more information about the latest targets, please reference the Fedora
> Atomic Wiki space.
> 
> 
> https://fedoraproject.org/wiki/Atomic_WG#Fedora_Atomic_Image_Download_Links
> 
> Do note that it can take some of the mirrors up to 12 hours to "check-in" at
> their own discretion.
> 
> Thank you,
> Fedora Release Engineering
> 


In this week's release of Fedora Atomic Host we have a new kernel,
ostree/rpm-ostree, glibc, and cloud-utils-growpart (fixes for aarch64
partition resize issues [1]).

[1] https://pagure.io/atomic-wg/issue/382


An example of the diff between this and the previous released version (for 
x86_64) is:

ostree diff commit old: 

Re: [atomic-announce] Fedora Atomic Host Two Week Release Announcement

[Dusty Mabe]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On 01/18/2018 02:17 PM, nore...@fedoraproject.org wrote:
> 
> A new Fedora Atomic Host update is available via an OSTree update:
> 
> Version: 27.61
> Commit(x86_64): 
> 772ab185b0752b0d6bc8b2096d08955660d80ed95579e13e136e6a54e3559ca9
> Commit(aarch64): 
> 598626fd61dc6ed4b702159e50b6029ee70a527e855fce7d8e61a870b141f893
> Commit(ppc64le): 
> 16ce78ee689066f582dbfc0672dab1706051fefab496fcebd8109d58738eb8fe
> 
> 
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
> 
> Existing systems can be upgraded in place via e.g. `atomic host upgrade` or
> `atomic host deploy`.
> 
> Corresponding image media for new installations can be downloaded from:
> 
> https://getfedora.org/en/atomic/download/
> 
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180117.1/Atomic/aarch64/iso/Fedora-Atomic-ostree-aarch64-27-20180117.1.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180117.1/Atomic/ppc64le/iso/Fedora-Atomic-ostree-ppc64le-27-20180117.1.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180117.1/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-27-20180117.1.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180117.1/CloudImages/aarch64/images/Fedora-Atomic-27-20180117.1.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180117.1/CloudImages/aarch64/images/Fedora-Atomic-27-20180117.1.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180117.1/CloudImages/ppc64le/images/Fedora-Atomic-27-20180117.1.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180117.1/CloudImages/ppc64le/images/Fedora-Atomic-27-20180117.1.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180117.1/CloudImages/x86_64/images/Fedora-Atomic-27-20180117.1.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180117.1/CloudImages/x86_64/images/Fedora-Atomic-27-20180117.1.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180117.1/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20180117.1.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180117.1/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20180117.1.x86_64.vagrant-virtualbox.box
> 
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180117.1/Atomic/aarch64/iso/Fedora-Atomic-27-20180117.1-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180117.1/Atomic/ppc64le/iso/Fedora-Atomic-27-20180117.1-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180117.1/Atomic/x86_64/iso/Fedora-Atomic-27-20180117.1-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180117.1/CloudImages/aarch64/images/Fedora-CloudImages-27-20180117.1-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180117.1/CloudImages/ppc64le/images/Fedora-CloudImages-27-20180117.1-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180117.1/CloudImages/x86_64/images/Fedora-CloudImages-27-20180117.1-x86_64-CHECKSUM
> 
> For direct download, the "latest" targets are always available here:
> https://getfedora.org/atomic_iso_latest
> https://getfedora.org/atomic_qcow2_latest
> https://getfedora.org/atomic_raw_latest
> https://getfedora.org/atomic_vagrant_libvirt_latest
> https://getfedora.org/atomic_vagrant_virtualbox_latest
> 
> Filename fetching URLs are available here:
> https://getfedora.org/atomic_iso_latest_filename
> https://getfedora.org/atomic_qcow2_latest_filename
> https://getfedora.org/atomic_raw_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_latest_filename
> 
> For more information about the latest targets, please reference the Fedora
> Atomic Wiki space.
> 
> 
> https://fedoraproject.org/wiki/Atomic_WG#Fedora_Atomic_Image_Download_Links
> 
> Do note that it can take some of the mirrors up to 12 hours to "check-in" at
> their own discretion.
> 
> Thank you,
> Fedora Release Engineering
> 
> 

In this week's release of Fedora Atomic Host we have an updated
kernel (the spectre patches are slowly working their way out [1]),
and an updated docker with a security fix [2]. We also are *including*
firewalld in the ostree now [3], but we are *not* enabling it by
default. I'll post a follow up blog post on this topic in the next day
or two.

[1] 

Re: [atomic-announce] Fedora Atomic Host Two Week Release Announcement

[Dusty Mabe]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On 01/04/2018 02:14 PM, nore...@fedoraproject.org wrote:
> 
> A new Fedora Atomic Host update is available via an OSTree update:
> 
> Version: 27.47
> Commit(x86_64): 
> 397e907961adafaeff11b807ceade8da5783134072406fcdba627f1195e0db76
> Commit(aarch64): 
> 25965b64256417d7dfed37511ffe0cf842ebe64bd6adc8c57a3c603dcfd79885
> Commit(ppc64le): 
> c0d0a28a01fd363dfc317e3418935efae6d728a718320dfb3709c4282160f20f
> 
> 
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
> 
> Existing systems can be upgraded in place via e.g. `atomic host upgrade` or
> `atomic host deploy`.
> 
> Corresponding image media for new installations can be downloaded from:
> 
> https://getfedora.org/en/atomic/download/
> 
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180104.5/Atomic/aarch64/iso/Fedora-Atomic-ostree-aarch64-27-20180104.5.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180104.5/Atomic/ppc64le/iso/Fedora-Atomic-ostree-ppc64le-27-20180104.5.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180104.5/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-27-20180104.5.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180104.5/CloudImages/aarch64/images/Fedora-Atomic-27-20180104.5.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180104.5/CloudImages/aarch64/images/Fedora-Atomic-27-20180104.5.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180104.5/CloudImages/ppc64le/images/Fedora-Atomic-27-20180104.5.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180104.5/CloudImages/ppc64le/images/Fedora-Atomic-27-20180104.5.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180104.5/CloudImages/x86_64/images/Fedora-Atomic-27-20180104.5.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180104.5/CloudImages/x86_64/images/Fedora-Atomic-27-20180104.5.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180104.5/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20180104.5.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180104.5/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20180104.5.x86_64.vagrant-virtualbox.box
> 
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180104.5/Atomic/aarch64/iso/Fedora-Atomic-27-20180104.5-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180104.5/Atomic/ppc64le/iso/Fedora-Atomic-27-20180104.5-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180104.5/Atomic/x86_64/iso/Fedora-Atomic-27-20180104.5-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180104.5/CloudImages/aarch64/images/Fedora-CloudImages-27-20180104.5-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180104.5/CloudImages/ppc64le/images/Fedora-CloudImages-27-20180104.5-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180104.5/CloudImages/x86_64/images/Fedora-CloudImages-27-20180104.5-x86_64-CHECKSUM
> 
> For direct download, the "latest" targets are always available here:
> https://getfedora.org/atomic_iso_latest
> https://getfedora.org/atomic_qcow2_latest
> https://getfedora.org/atomic_raw_latest
> https://getfedora.org/atomic_vagrant_libvirt_latest
> https://getfedora.org/atomic_vagrant_virtualbox_latest
> 
> Filename fetching URLs are available here:
> https://getfedora.org/atomic_iso_latest_filename
> https://getfedora.org/atomic_qcow2_latest_filename
> https://getfedora.org/atomic_raw_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_latest_filename
> 
> For more information about the latest targets, please reference the Fedora
> Atomic Wiki space.
> 
> 
> https://fedoraproject.org/wiki/Atomic_WG#Fedora_Atomic_Image_Download_Links
> 
> Do note that it can take some of the mirrors up to 12 hours to "check-in" at
> their own discretion.
> 
> Thank you,
> Fedora Release Engineering


This is a security related release of Fedora Atomic Host to
address CVE-2017-5754 [1] (Meltdown). This release does not
yet handle the "Spectre" vulnerabilities [2][3]. Those will
come in a future update. For more information see the Red Hat
KB article [4].

kernel-4.14.11-300.fc27.x86_64 fixes BZ1530826 [5] related to
CVE-2017-5754. It also fixes some other CVEs as well. 

Re: [atomic-announce] Fedora Atomic Host Two Week Release Announcement

[Dusty Mabe]

On 12/12/2017 02:49 PM, nore...@fedoraproject.org wrote:
> 
> A new Fedora Atomic Host update is available via an OSTree update:
> 
> Version: 27.25
> Commit(x86_64): 
> a2b80278eea897eb1fec7d008b18ef74941ff5a54f86b447a2f4da0451c4291a
> Commit(aarch64): 
> 0a7bd764394cc4e1afa6e35b20ed20a00dc8b449fc9563624fb47d9940af6a1d
> Commit(ppc64le): 
> 46dfc00f165aa29b030acc5fdc5603de0084a1e6fc71005e82ccc3d5145d168d
> 
> 
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
> 
> Existing systems can be upgraded in place via e.g. `atomic host upgrade` or
> `atomic host deploy`.
> 
> Corresponding image media for new installations can be downloaded from:
> 
> https://getfedora.org/en/atomic/download/
> 
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171211.0/Atomic/aarch64/iso/Fedora-Atomic-ostree-aarch64-27-20171211.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171211.0/Atomic/ppc64le/iso/Fedora-Atomic-ostree-ppc64le-27-20171211.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171211.0/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-27-20171211.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171211.0/CloudImages/aarch64/images/Fedora-Atomic-27-20171211.0.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171211.0/CloudImages/aarch64/images/Fedora-Atomic-27-20171211.0.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171211.0/CloudImages/ppc64le/images/Fedora-Atomic-27-20171211.0.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171211.0/CloudImages/ppc64le/images/Fedora-Atomic-27-20171211.0.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171211.0/CloudImages/x86_64/images/Fedora-Atomic-27-20171211.0.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171211.0/CloudImages/x86_64/images/Fedora-Atomic-27-20171211.0.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171211.0/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20171211.0.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171211.0/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20171211.0.x86_64.vagrant-virtualbox.box
> 
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171211.0/Atomic/aarch64/iso/Fedora-Atomic-27-20171211.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171211.0/Atomic/ppc64le/iso/Fedora-Atomic-27-20171211.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171211.0/Atomic/x86_64/iso/Fedora-Atomic-27-20171211.0-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171211.0/CloudImages/aarch64/images/Fedora-CloudImages-27-20171211.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171211.0/CloudImages/ppc64le/images/Fedora-CloudImages-27-20171211.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171211.0/CloudImages/x86_64/images/Fedora-CloudImages-27-20171211.0-x86_64-CHECKSUM
> 
> For direct download, the "latest" targets are always available here:
> https://getfedora.org/atomic_iso_latest
> https://getfedora.org/atomic_qcow2_latest
> https://getfedora.org/atomic_raw_latest
> https://getfedora.org/atomic_vagrant_libvirt_latest
> https://getfedora.org/atomic_vagrant_virtualbox_latest
> 
> Filename fetching URLs are available here:
> https://getfedora.org/atomic_iso_latest_filename
> https://getfedora.org/atomic_qcow2_latest_filename
> https://getfedora.org/atomic_raw_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_latest_filename
> 
> For more information about the latest targets, please reference the Fedora
> Atomic Wiki space.
> 
> 
> https://fedoraproject.org/wiki/Atomic_WG#Fedora_Atomic_Image_Download_Links
> 
> Do note that it can take some of the mirrors up to 12 hours to "check-in" at
> their own discretion.
> 
> Thank you,
> Fedora Release Engineering


This is the 3rd release of Fedora 27 Atomic Host, including mulit-arch 
artifacts.

An example of the diff between this and the previous released version (for 
x86_64) is:

ostree diff commit old: 
86727cdbc928b7f7dd0e32f62d3b973a8395d61e0ff751cfea7cc0bc5222142f
ostree diff commit new: 
a2b80278eea897eb1fec7d008b18ef74941ff5a54f86b447a2f4da0451c4291a
Upgraded:
  atomic 1.20.1-3.fc27.x86_64 -> 1.20.1-6.fc27.x86_64
  

Re: [atomic-devel] Fedora Atomic Host Two Week Release Announcement

[Dusty Mabe]

On 11/30/2017 11:48 AM, nore...@fedoraproject.org wrote:
> 
> A new Fedora Atomic Host update is available via an OSTree update:
> 
> Version: 27.16
> Commit(x86_64): 
> 86727cdbc928b7f7dd0e32f62d3b973a8395d61e0ff751cfea7cc0bc5222142f
> Commit(aarch64): 
> 49f9b422bc53b30aea3074c75a15e8322ed1d14980ff0b5f9c694089598b4f2f
> Commit(ppc64le): 
> 600955d77630fec6d1d3a76af31d872f2fed8af1495399256a0dfff013a518f3
> 
> 
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
> 
> Existing systems can be upgraded in place via e.g. `atomic host upgrade` or
> `atomic host deploy`.
> 
> Corresponding image media for new installations can be downloaded from:
> 
> https://getfedora.org/en/atomic/download/
> 
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/Atomic/aarch64/iso/Fedora-Atomic-ostree-aarch64-27-20171129.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/Atomic/ppc64le/iso/Fedora-Atomic-ostree-ppc64le-27-20171129.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-27-20171129.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/CloudImages/aarch64/images/Fedora-Atomic-27-20171129.0.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/CloudImages/aarch64/images/Fedora-Atomic-27-20171129.0.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/CloudImages/ppc64le/images/Fedora-Atomic-27-20171129.0.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/CloudImages/ppc64le/images/Fedora-Atomic-27-20171129.0.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/CloudImages/x86_64/images/Fedora-Atomic-27-20171129.0.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/CloudImages/x86_64/images/Fedora-Atomic-27-20171129.0.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20171129.0.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20171129.0.x86_64.vagrant-virtualbox.box
> 
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/Atomic/aarch64/iso/Fedora-Atomic-27-20171129.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/Atomic/ppc64le/iso/Fedora-Atomic-27-20171129.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/Atomic/x86_64/iso/Fedora-Atomic-27-20171129.0-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/CloudImages/aarch64/images/Fedora-CloudImages-27-20171129.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/CloudImages/ppc64le/images/Fedora-CloudImages-27-20171129.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/CloudImages/x86_64/images/Fedora-CloudImages-27-20171129.0-x86_64-CHECKSUM
> 
> For direct download, the "latest" targets are always available here:
> https://getfedora.org/atomic_iso_latest
> https://getfedora.org/atomic_qcow2_latest
> https://getfedora.org/atomic_raw_latest
> https://getfedora.org/atomic_vagrant_libvirt_latest
> https://getfedora.org/atomic_vagrant_virtualbox_latest
> 
> Filename fetching URLs are available here:
> https://getfedora.org/atomic_iso_latest_filename
> https://getfedora.org/atomic_qcow2_latest_filename
> https://getfedora.org/atomic_raw_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_latest_filename
> 
> For more information about the latest targets, please reference the Fedora
> Atomic Wiki space.
> 
> 
> https://fedoraproject.org/wiki/Atomic_WG#Fedora_Atomic_Image_Download_Links
> 
> Do note that it can take some of the mirrors up to 12 hours to "check-in" at
> their own discretion.
> 
> Thank you,
> Fedora Release Engineering
> 
> 



This is the 2nd release of Fedora 27 Atomic Host, including mulit-arch 
artifacts.

An example of the diff between this and the previous released version (for 
x86_64) is:

ostree diff commit old: 
d428d3ad8ecf44e53d138042bad56a10308883a0c5d64b9c51eff27fdc9da82c
ostree diff commit new: 
86727cdbc928b7f7dd0e32f62d3b973a8395d61e0ff751cfea7cc0bc5222142f
Upgraded:
  NetworkManager 1:1.8.4-2.fc27.x86_64 -> 

Re: [atomic-devel] Fedora Atomic Host Two Week Release Announcement

[Dusty Mabe]

On 11/14/2017 02:10 PM, nore...@fedoraproject.org wrote:
> 
> A new Fedora Atomic Host update is available via an OSTree update:
> 
> Version: 27.1
> Commit(x86_64): 
> d428d3ad8ecf44e53d138042bad56a10308883a0c5d64b9c51eff27fdc9da82c
> Commit(aarch64): 
> da1bd08012699a0aacaa11481d3ed617477858aab0f2ea7300168ce106202255
> Commit(ppc64le): 
> 362888edfac04f8848072ae4fb8193b3da2f4fd226bef450326faff4be290abd
> 
> 
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
> 
> Existing systems can be upgraded in place via e.g. `atomic host upgrade` or
> `atomic host deploy`.
> 
> Corresponding image media for new installations can be downloaded from:
> 
> https://getfedora.org/en/atomic/download/
> 
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171110.1/Atomic/aarch64/iso/Fedora-Atomic-ostree-aarch64-27-20171110.1.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171110.1/Atomic/ppc64le/iso/Fedora-Atomic-ostree-ppc64le-27-20171110.1.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171110.1/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-27-20171110.1.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171110.1/CloudImages/aarch64/images/Fedora-Atomic-27-20171110.1.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171110.1/CloudImages/aarch64/images/Fedora-Atomic-27-20171110.1.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171110.1/CloudImages/ppc64le/images/Fedora-Atomic-27-20171110.1.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171110.1/CloudImages/ppc64le/images/Fedora-Atomic-27-20171110.1.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171110.1/CloudImages/x86_64/images/Fedora-Atomic-27-20171110.1.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171110.1/CloudImages/x86_64/images/Fedora-Atomic-27-20171110.1.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171110.1/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20171110.1.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171110.1/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20171110.1.x86_64.vagrant-virtualbox.box
> 
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171110.1/Atomic/aarch64/iso/Fedora-Atomic-27-20171110.1-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171110.1/Atomic/ppc64le/iso/Fedora-Atomic-27-20171110.1-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171110.1/Atomic/x86_64/iso/Fedora-Atomic-27-20171110.1-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171110.1/CloudImages/aarch64/images/Fedora-CloudImages-27-20171110.1-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171110.1/CloudImages/ppc64le/images/Fedora-CloudImages-27-20171110.1-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20171110.1/CloudImages/x86_64/images/Fedora-CloudImages-27-20171110.1-x86_64-CHECKSUM
> 
> For direct download, the "latest" targets are always available here:
> https://getfedora.org/atomic_iso_latest
> https://getfedora.org/atomic_qcow2_latest
> https://getfedora.org/atomic_raw_latest
> https://getfedora.org/atomic_vagrant_libvirt_latest
> https://getfedora.org/atomic_vagrant_virtualbox_latest
> 
> Filename fetching URLs are available here:
> https://getfedora.org/atomic_iso_latest_filename
> https://getfedora.org/atomic_qcow2_latest_filename
> https://getfedora.org/atomic_raw_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_latest_filename
> 
> For more information about the latest targets, please reference the Fedora
> Atomic Wiki space.
> 
> 
> https://fedoraproject.org/wiki/Atomic_WG#Fedora_Atomic_Image_Download_Links
> 
> Do note that it can take some of the mirrors up to 12 hours to "check-in" at
> their own discretion.
> 
> Thank you,
> Fedora Release Engineering
> 
> 


We are proud to release the first release of Fedora 27 Atomic Host, 
including multi-arch artifacts!

The diff between this and the previous released version is:

ostree diff commit old: 
c099633883cd8d06895e32a14c63f6672072430c151de882223e4abe20efa7ca
ostree diff commit new: 
d428d3ad8ecf44e53d138042bad56a10308883a0c5d64b9c51eff27fdc9da82c
Upgraded:
  GeoIP 1.6.11-1.fc26.x86_64 -> 1.6.11-3.fc27.x86_64
  

please help us test the f27 cloud images in RC1.2

[Dusty Mabe]

You can grab the image download links and fill out the results here:

https://fedoraproject.org/wiki/Test_Results:Fedora_27_RC_1.2_Cloud


Unfortunately only half the AMIs uploaded: 

Fedora-Cloud-Base-27-1.2.x86_64   EC2 (us-east-1)  ami-acaa02d6 
   paravirtual   gp2
Fedora-Cloud-Base-27-1.2.x86_64   EC2 (us-east-1)  ami-00ac047a 
   paravirtual   standard   
Fedora-Cloud-Base-27-1.2.x86_64   EC2 (us-west-2)  ami-38b07b40 
   hvm   standard   
Fedora-Cloud-Base-27-1.2.x86_64   EC2 (us-west-1)  ami-69586709 
   hvm   standard   
Fedora-Cloud-Base-27-1.2.x86_64   EC2 (sa-east-1)  ami-68cfb704 
   hvm   standard   
Fedora-Cloud-Base-27-1.2.x86_64   EC2 (eu-west-1)  ami-f564c58c 
   hvm   standard   
Fedora-Cloud-Base-27-1.2.x86_64   EC2 (eu-central-1)   ami-a067e2cf 
   hvm   standard   
Fedora-Cloud-Base-27-1.2.x86_64   EC2 (ap-southeast-2) ami-6df41a0f 
   hvm   standard   
Fedora-Cloud-Base-27-1.2.x86_64   EC2 (ap-southeast-1) ami-04612c67 
   hvm   standard   
Fedora-Cloud-Base-27-1.2.x86_64   EC2 (ap-northeast-1) ami-da963abc 
   hvm   standard   
Fedora-Cloud-Base-27-1.2.x86_64   EC2 (us-east-1)  ami-a9a800d3 
   hvm   standard

I've opened a ticket to get this resolved: https://pagure.io/releng/issue/7126
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: firewalld in atomic host

[Dusty Mabe]

On 04/21/2017 10:16 AM, Dusty Mabe wrote:
> NOTE: if you respond to this message please 'reply-all'.
> 
> I'd like to discuss firewalld on atomic host. Recently I was trying to
> figure out the best way to explain to other users how to set firewall rules
> on atomic host.
> 
> Usually I would say add your rules and then iptables-save, but on Atomic
> Host docker has added it's firewall rules in there dynamically so if you 
> iptables-save
> you'll get a bunch of stuff that you don't want in your static configuration.
> 
> There are ways around this; manually create your config file, or use 
> iptables-save
> and then rip the docker stuff out. Either way it's a bit of a pain. I think 
> firewalld would make this easier on the user. Not sure of the pro/con ratio 
> though.
> 

reviving this old discussion: I am proposing we add firewalld do atomic host:
 
https://pagure.io/atomic-wg/issue/372
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[fedora-atomic] PR #91: Base for f27

[Dusty Mabe]

dustymabe merged a pull-request against the project: `fedora-atomic` that you 
are following.

Merged pull-request:

``
Base for f27
``

https://pagure.io/fedora-atomic/pull-request/91
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org