Fedora 25 Cloud Base Images
We currently don't have a download page for the Fedora 25 cloud base image. This is because we did a poor job of communicating with the websites team (our fault, not theirs) before Fedora 25 release. There will be a new site for the cloud base image at https://cloud.fedoraproject.org/ This is tracked by https://pagure.io/fedora-websites/issue/57 In the meantime here is the information for the cloud base image for Fedora 25 release: RAW - https://download.fedoraproject.org/pub/fedora/linux/releases/25/CloudImages/x86_64/images/Fedora-Cloud-Base-25-1.3.x86_64.raw.xz QCOW - https://download.fedoraproject.org/pub/fedora/linux/releases/25/CloudImages/x86_64/images/Fedora-Cloud-Base-25-1.3.x86_64.qcow2 Vagrant Libvirt - https://download.fedoraproject.org/pub/fedora/linux/releases/25/CloudImages/x86_64/images/Fedora-Cloud-Base-Vagrant-25-1.3.x86_64.vagrant-libvirt.box Vagrant Virtualbox - https://download.fedoraproject.org/pub/fedora/linux/releases/25/CloudImages/x86_64/images/Fedora-Cloud-Base-Vagrant-25-1.3.x86_64.vagrant-virtualbox.box And for AWS: Fedora-Cloud-Base-25-1.3.x86_64EC2 (us-west-1) ami-c28bdea2hvm standard Fedora-Cloud-Base-25-1.3.x86_64EC2 (us-west-2) ami-0bea476bhvm standard Fedora-Cloud-Base-25-1.3.x86_64EC2 (sa-east-1) ami-001c836chvm standard Fedora-Cloud-Base-25-1.3.x86_64EC2 (eu-west-1) ami-ffe8b88chvm standard Fedora-Cloud-Base-25-1.3.x86_64EC2 (eu-central-1) ami-b2c603ddhvm standard Fedora-Cloud-Base-25-1.3.x86_64EC2 (ap-southeast-2) ami-499ea12ahvm standard Fedora-Cloud-Base-25-1.3.x86_64EC2 (ap-southeast-1) ami-992182fahvm standard Fedora-Cloud-Base-25-1.3.x86_64EC2 (sa-east-1) ami-031c836f paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64EC2 (us-west-2) ami-8aeb46ea paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64EC2 (us-west-1) ami-688edb08 paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64EC2 (eu-west-1) ami-c8e7b7bb paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64EC2 (eu-central-1) ami-2ac10445 paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64EC2 (ap-southeast-2) ami-eb9ea188 paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64EC2 (ap-southeast-1) ami-6a258609 paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64EC2 (us-west-2) ami-36eb4656 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64EC2 (ap-northeast-1) ami-633f9402hvm standard Fedora-Cloud-Base-25-1.3.x86_64EC2 (ap-northeast-1) ami-f3248f92 paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64EC2 (us-west-2) ami-3dea475dhvm gp2 Fedora-Cloud-Base-25-1.3.x86_64EC2 (sa-east-1) ami-c51986a9 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64EC2 (us-west-1) ami-6889dc08 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64EC2 (us-west-1) ami-5c8bde3chvm gp2 Fedora-Cloud-Base-25-1.3.x86_64EC2 (sa-east-1) ami-021c836ehvm gp2 Fedora-Cloud-Base-25-1.3.x86_64EC2 (eu-west-1) ami-40e6b633hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64EC2 (eu-central-1) ami-bac603d5hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64EC2 (ap-southeast-2) ami-ca9fa0a9hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64EC2 (ap-southeast-1) ami-00278463hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64EC2 (ap-northeast-1) ami-68389309hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64EC2 (eu-west-1) ami-03e6b670 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64EC2 (eu-central-1) ami-fec60391 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64EC2 (ap-southeast-2) ami-cb9fa0a8 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64EC2 (ap-southeast-1) ami-6e25860d paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64EC2 (ap-northeast-1) ami-663f9407 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64EC2 (us-east-1) ami-e5ad85f2hvm standard Fedora-Cloud-Base-25-1.3.x86_64EC2 (us-east-1) ami-0fac8418 paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64EC2 (us-east-1) ami-86ac8491 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64EC2 (us-east-1) ami-56a08841hvm gp2 - Dusty ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #180 `Future of Fedora Dockerfiles`
scollier added a new comment to an issue you are following: `` Per the Fedora Cloud meeting: https://meetbot.fedoraproject.org/fedora-meeting-1/2016-11-23/fedora_atomic_working_group.2016-11-23-17.03.log.html We agreed that I will post on the Fedora-Dockerfiles repo that we are going to stop accepting new PRs and that once @maxamillion gives us the go ahead with a good stable docs link and FESco approved policy, I'll link to that. Looks like it should be around 2 weeks. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/180 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Cloud Meeting Minutes 2016-11-23
Summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2016-11-23/fedora_atomic_working_group.2016-11-23-17.03.html Full Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2016-11-23/fedora_atomic_working_group.2016-11-23-17.03.log.html == #fedora-meeting-1: Fedora Atomic Working Group == Meeting started by kushal at 17:03:57 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2016-11-23/fedora_atomic_working_group.2016-11-23-17.03.log.html . Meeting summary --- * Roll Call (kushal, 17:04:05) * Action items from last meeting (trishnag, 17:06:12) * Future of Fedora Dockerfiles https://pagure.io/atomic-wg/issue/180 (trishnag, 17:08:57) * ACTION: kushal will write to list for the agenda of the features meeting for Atomic group (sayan, 17:09:12) * Fedora Cloud Base Vagrant Boxes Don't Allow Vagrant User To su To Other Users https://pagure.io/atomic-wg/issue/173 (trishnag, 17:11:11) * Finish new Fedora Cloud PRD https://pagure.io/atomic-wg/issue/170 (trishnag, 17:12:49) * Spec for IRC bot to notify about blockers https://pagure.io/atomic-wg/issue/169 (trishnag, 17:14:23) * ACTION: kushal to update #169 (kushal, 17:24:58) * Ship fedora-motd in F24 atomic image https://pagure.io/atomic-wg/issue/160 (trishnag, 17:25:34) * Proposed website changes for Cloud Base → Atomic Host switch https://pagure.io/atomic-wg/issue/158 (trishnag, 17:27:22) * make Fedora Atomic download page clearer https://pagure.io/atomic-wg/issue/154 (trishnag, 17:29:23) * design, deploy and document Fedora OpenShift Playground (FOSP) https://pagure.io/atomic-wg/issue/153 (trishnag, 17:30:12) * vagrant boxes fixups https://pagure.io/atomic-wg/issue/136 (trishnag, 17:38:35) * Future of Fedora Dockerfiles https://pagure.io/atomic-wg/issue/180 (trishnag, 17:43:13) * Open Floor (trishnag, 17:53:18) * LINK: https://pagure.io/fedora-websites/issue/57 (dustymabe, 17:54:27) Meeting ended at 18:00:25 UTC. Action Items * kushal will write to list for the agenda of the features meeting for Atomic group * kushal to update #169 Action Items, by person --- * kushal * kushal will write to list for the agenda of the features meeting for Atomic group * kushal to update #169 * **UNASSIGNED** * (none) People Present (lines said) --- * trishnag (73) * dustymabe (65) * kushal (35) * scollier (23) * misc (19) * zodbot (15) * gholms (13) * sayan (12) * maxamillion (9) * rmartinelli (6) * jbrooks (2) * bowlofeggs (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
[atomic-wg] Issue #160 `Ship fedora-motd in F24 atomic image`
trishnag added a new comment to an issue you are following: `` We need to ship this for f25. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/160 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #154 `make Fedora Atomic download page clearer`
mattdm added a new comment to an issue you are following: `` I have two small ones. First, I think the freshness indicator is not visible enough in the top bar. Maybe that's just me. I guess, for one thing, it's easy to gloss over header-section text, but also, there's no indication that that's a dynamic value. What about changing "Produced N days ago" to "Produced N days ago, on -MM-DD" (or whatever internationalized date format the web team prefers)? Second, it currently says "1 days ago". I'd love that to be properly special-cased to "1 day ago", or even better, "yesterday". And "0 days ago" could be "today" or "fresh for you just today!" `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/154 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #154 `make Fedora Atomic download page clearer`
dustymabe added a new comment to an issue you are following: `` I would say update the wiki page, but whatever works. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/154 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #154 `make Fedora Atomic download page clearer`
mattdm added a new comment to an issue you are following: `` Should we update Josh's wiki page above or put proposals here? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/154 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #154 `make Fedora Atomic download page clearer`
dustymabe added a new comment to an issue you are following: `` @jberkus - now we can propose new changes to the F25 page. please schedule some time for interested parties to get together and go over your proposed changes. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/154 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #173 `Fedora Cloud Base Vagrant Boxes Don't Allow Vagrant User To su To Other Users`
The issue: `Fedora Cloud Base Vagrant Boxes Don't Allow Vagrant User To su To Other Users` of project: `atomic-wg` has been assigned to `dustymabe` by trishnag. https://pagure.io/atomic-wg/issue/173 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`
walters added a new comment to an issue you are following: `` Oh, sorry, I was reading the git log and missed that we already did back out the change: https://pagure.io/fedora-kickstarts/c/6f3661e3a5f2625b73ee8e998087285d7c6e7e63?branch=f25 Nevermind. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`
dustymabe added a new comment to an issue you are following: `` > One should be able to configure static IPs via nmcli in bootcmd hooks in > cloud-init, so I'd like to back out the change to enable network.service. hmm. I don't think we enabled network.service ``` -bash-4.3# systemctl status NetworkManager | cat ● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2016-11-22 20:20:04 UTC; 19h ago Docs: man:NetworkManager(8) Main PID: 32401 (NetworkManager) Tasks: 4 (limit: 4915) Memory: 44.0M CPU: 1min 29.555s CGroup: /system.slice/NetworkManager.service ├─32401 /usr/sbin/NetworkManager --no-daemon └─32465 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-eth0.pid -lf /var/lib/NetworkManager/dhclient-5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03-eth0.lease -cf /var/lib/NetworkManager/dhclient-eth0.conf eth0 Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: [1479915956.6560] device (veth01b40c4): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: [1479915956.6563] policy: disabling autoconnect for connection 'Wired connection 6'. Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: [1479915956.6564] device (veth01b40c4): Activation: failed for connection 'Wired connection 6' Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: [1479915956.6565] device (veth158a7ac): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: [1479915956.6567] policy: disabling autoconnect for connection 'Wired connection 5'. Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: [1479915956.6568] device (veth158a7ac): Activation: failed for connection 'Wired connection 5' Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: [1479915956.6575] device (veth01b40c4): state change: failed -> disconnected (reason 'none') [120 30 0] Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: [1479915956.6584] device (veth158a7ac): state change: failed -> disconnected (reason 'none') [120 30 0] Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: [1479915956.6595] device (veth01b40c4): enslaved to non-master-type device ovs-system; ignoring Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: [1479915956.6597] device (veth158a7ac): enslaved to non-master-type device ovs-system; ignoring Warning: NetworkManager.service changed on disk. Run 'systemctl daemon-reload' to reload units. -bash-4.3# -bash-4.3# systemctl status network | cat Warning: network.service changed on disk. Run 'systemctl daemon-reload' to reload units. ● network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network; generated; vendor preset: disabled) Active: inactive (dead) Docs: man:systemd-sysv-generator(8) ``` `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`
jasonbrooks added a new comment to an issue you are following: `` We talked about enabling the network service, but we instead patched cloud-init to make NM work. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`
dustymabe added a new comment to an issue you are following: `` @walters. what exactly do you want to revert? We added the [patch](http://pkgs.fedoraproject.org/cgit/rpms/cloud-init.git/commit/?id=b48cb59de23027b5b647baaf7d7dbe8eb52c95ad) to cloud-init to make it so that networkmanager can read the files and bring up networking. @gholms we need to send that patch upstream. Are you game? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`
kushal added a new comment to an issue you are following: `` Somehow I want to shout "networkd" "networkd" :) `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`
walters added a new comment to an issue you are following: `` I think this: `` this has prevented me from then managing the network (I tried w/ a static ip) from a cloud-init datasource. I'm pretty sure we don't want that. ``` is independent of the "no networking on boot" problem, which is what was fixed by cloud-init. One should be able to configure static IPs via `nmcli` in `bootcmd` hooks in cloud-init, so I'd like to back out the change to enable `network.service`. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`
walters added a new comment to an issue you are following: `` Err wait, so can't we revert this now? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
