cloud December 2015

cloud@lists.fedoraproject.org

29 participants
97 discussions

Cancel next two meetings?
by Joe Brockmeier 28 Dec '15

28 Dec '15

Hey all, I can't recall if we discussed this last time - but I suspect many folks are going to be on vacation this and next Wednesday. Shall we cancel those meetings and plan to re-adjourn on the 6th? Best, jzb -- Joe Brockmeier | Community Team, OSAS jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

3 3

Hiatus
by Mike Ruckman 24 Dec '15

24 Dec '15

Greetings list! I wanted to give a heads up to the list that due to some personal stuff, I will be taking a hiatus from my regularly scheduled activities. I'll still be filing test results and sporadically responding to emails - but you won't be likely to find me in our usual meetings and whatnot. Rest assured, everything is fine and I will get back into things; I just have to take care of some stuff. Thanks! -- // Mike -- Fedora QA

1 0

atomic host grub2 version
by Chris Murphy 23 Dec '15

23 Dec '15

On two UEFI systems, one with F23 Workstation, the other with F23 Cloud Atomic, I'm finding the grubx64.efi do not have the same hash, even though rpm -q reports the same rpm installed on both. This is unexpected. Does the atomic tree include /boot/efi/EFI/fedora? And if not, is that on the future feature list? CVE-2015-8370 is what made me look at this. On BIOS computers, whether conventional or atomic, GRUB2 user space tools are updated with grub2-2.02-0.25.fc23, but that only updates user space tools. The user has to manually run grub2-install to actually fix the problem. On UEFI conventional installations, grubx64.efi is replaced automatically when the RPM is updated; but apparently not on UEFI atomic installations. Using grub2-install fails because grub2-efi-modules isn't installed by default, and even if it were the resulting grubx64.efi is now no longer signed by Fedora so it'll fail UEFI Secure Boot code signing checks. -- Chris Murphy

1 1

Fedora Atomic Host Two Week Release Announcement
by Adam Miller 23 Dec '15

23 Dec '15

A new update of Fedora Cloud Atomic Host has been released and can be downloaded at: https://getfedora.org/en/cloud/download/atomic.html Respective signed CHECKSUM files can be found here: https://alt.fedoraproject.org/pub/alt/atomic/stable/Cloud-Images/x86_64/Ima… https://alt.fedoraproject.org/pub/alt/atomic/stable/Cloud_Atomic/x86_64/iso… Thank you, Fedora Release Engineering

2 5

Putting Networkd on cloud Atomic and base image for F24
by Kushal Das 22 Dec '15

22 Dec '15

Hi, This email is to resume the discussion on putting Networkd as network stack in Fedora Cloud Atomic and base images. During Fedora 23 release we had some discussion on the same. I made couple of images [1], and also AMI on AWS [2], so that people can play around. Major Hayden did some excellent write up [3] [4] [5] about Networkd in Fedora [6]. Last time when we discussed this issue, one of the major concern was QA cycle. We all know how much overloaded the QA team is. Now we have some level of automated testing (increasing regularly), and also a new volunteer group from the Cloud SIG to help by doing manual QA on the images. If we can make a list of things to be tested (or what all tests are currently being done) on the network stack for current Fedora releases, we all can help in, and make sure that the images with this new feature get proper testing. "Features", and "First" are part of our four foundations. I personally think putting Networkd on our cloud images will certainly help us to grow the features where latest technology is involved. [1] https://kushaldas.in/posts/testing-fedora-cloud-image-with-systemd-networkd… [2] https://kushaldas.in/posts/testing-systemd-networkd-based-fedora-22-ami-s.h… [3] https://major.io/2015/10/26/systemd-networkd-and-macvlan-interfaces/ [4] https://major.io/2015/10/16/gre-tunnels-with-systemd-networkd/ [5] https://major.io/2015/09/28/customizing-systemds-network-device-names/ [6] https://fedoraproject.org/wiki/Cloud/Network-Requirements Kushal -- Fedora Cloud Engineer CPython Core Developer CentOS Cloud SIG lead http://kushaldas.in

14 24

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 22 Dec '15

22 Dec '15

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2015-12-23 from 17:00:00 to 18:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Standing meeting for the Fedora Cloud Workgroup Source: https://apps.fedoraproject.org/calendar/meeting/1999/

1 0

Weekly meeting log from 2015-12-16
by Kushal Das 17 Dec '15

17 Dec '15

=========================== #fedora-meeting-1: cloud_wg =========================== Meeting started by kushal at 17:01:15 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-1/2015-12-16/cloud_wg.2015-… . Meeting summary --------------- * Roll Call (kushal, 17:01:20) * Action items from last meeting (kushal, 17:03:39) * LINK: https://fedoraproject.org/wiki/Changes/Cloud_MOTD (kushal, 17:08:50) * Fedora Cloud FAD (late 2015/early 2016) https://fedorahosted.org/cloud/ticket/115 (kushal, 17:18:57) * Migrate all Dockerfiles / Images to systemd where possible https://fedorahosted.org/cloud/ticket/121 (kushal, 17:23:42) * AGREED: Cloud group agrees to continue to maintain dockerfils on GitHub for now until a more concrete proposal and timeline is proposed to move them elsewhere. Work will re-commence on updating Dockerfiles for dnf, systemd, etc. (jzb, 17:35:52) * make docker archived image get imported with lowercase tag https://fedorahosted.org/cloud/ticket/131 (kushal, 17:37:29) * Fedora 23 Retrospective https://fedorahosted.org/cloud/ticket/135 (kushal, 17:39:49) * ACTION: jzb will update #135 on Fedora 23 retrospective (kushal, 17:42:00) * vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136 (kushal, 17:42:23) * LINK: https://fedoramagazine.org/fedora-cloud-vagrant-boxes-atlas/ (dustymabe, 17:56:10) * Producing 2 week atomic images https://fedorahosted.org/cloud/ticket/139 (kushal, 17:56:28) * Open Floor (kushal, 17:57:40) * LINK: https://fedoraproject.org/wiki/Cloud/Network-Requirements (jzb, 18:08:51) * LINK: https://fedoraproject.org/wiki/Changes/Cloud_Systemd_Networkd (jzb, 18:13:08) Meeting ended at 18:18:42 UTC. Action Items ------------ * jzb will update #135 on Fedora 23 retrospective Action Items, by person ----------------------- * jzb * jzb will update #135 on Fedora 23 retrospective * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * kushal (141) * jzb (83) * dustymabe (75) * linuxmodder (48) * tflink (27) * jbrooks (22) * mhayden (19) * nzwulfin (18) * zodbot (15) * siXy (14) * gholms (11) * scollier (6) * rtnpro (4) * jsmith (3) * number80 (3) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot Kushal -- Fedora Cloud Engineer CPython Core Developer CentOS Cloud SIG lead http://kushaldas.in

1 0

Fedora cloud image feedback
by P J P 17 Dec '15

17 Dec '15

Hello, Today in another conversation[1], I received this feedback about Fedora cloud images. Not sure if there is bug open for this, if not, do I file one? [1] https://pjps.wordpress.com/2015/12/15/fad-singapore-2015/ +-- On Tue, 15 Dec 2015, Deepak C Shetty wrote --+ | ... | How about having Fedora images that can be used out-of-the-box ? | | For eg: if we go to getfedora.org today, we have AMI, cloud images, | but to really use these, u either need a AWS account or need to have | a local cloud/openstack setup, otherwise (most typically) people | fire up a VM using the cloud image it gets stuck at the cloud-init | stage (thats where most of excitement of usign fedora goes down), | then after waiting for several minutes when the cloud-init times | out, it gives a login shell, where nothing works (which is expected | bcos you are supposed to use this with pre-injected ssh keys) and | then the end user just gets frustrated that he did everything he | could, came so close to using a bleedign edge fedora. but still | can't get into it. | | How about giving good documentation around hacking cloud images | (using virt-* tools) to enable ssh passwd auth, enabling root/user | login, so that its easy for newcomers to embrace cloud images | | Alternative could be to provide out-of-the-box working fedora | images, which anyone can use to boot using virt-manager, | virt-* utils or qemu cmdline and be able to login as root or | non-root with sudo access, also image comes with decent enough | root disk free space, so that embracing/trying out (which is | the first time experience) becomes memorable than frustrating | | Thoughts ? Thank you. --- -P J P http://feedmug.com

6 13

Fedora cloud image feedback
by Jonathan Lebon 17 Dec '15

17 Dec '15

Hi all, > https://fedoraproject.org/wiki/Changes/Local_Test_Cloud Interesting tool. Hadn't seen it before. I've also been working on a similar feature for the Atomic image (although it should work just fine for the Base images as well if we want). Basically, it adds a new boot menu item labeled "Developer Mode" (working title ;) ). It's meant for users with little experience (e.g. don't know anything about cloud-init or how to use Vagrant, or even Linux in general) or for those who want to "kick the tire", so to speak. When booted in Dev Mode: - cloud-init is configured to set a password for the cloud-user and root accounts - tty1 is automatically logged in as root with a tmux shell set up - cockpit is automatically downloaded and started and a URL is printed out for users to open in their browsers. There is a card on the platinfra Trello board for this work: https://trello.com/c/eK54YRTp One advantage of this approach is that everything necessary is encapsulated in the image, so there are no pkg (or even OS) requirements on the user env (other than being able to boot the image). But it does require a small kickstart tweak as well as a new package added. Cheers, Jonathan

2 1

Cloud Atomic ISO, missing items for baremetal usage
by Chris Murphy 17 Dec '15

17 Dec '15

Hi, Is there a wish list for things to consider adding to a future ISO? These are things not on the current ISO that often are on other baremetal installs like Workstation and Server products. I don't have enough familiarity with whether these things should just be included in the base installation and those that could be gathered in one or more "util" or "extras" type of Fedora docker image. So far I'm running into: /lib/fimware/ is read-only so I can't add this: [ 14.599501] iwlwifi 0000:02:00.0: request for firmware file 'iwlwifi-7265D-13.ucode' failed. I don't know whether a /var/lib/firmware being bind mounted to /lib/firmware can be done soon enough that it'll be picked up by the kernel. pciutils, which contains lspci hdparm smartmontools iotop These I have running in a fedora container. lspci mostly works, but getting full -vvnn detail requires --privileged=true. And the other three require it. iotop additionally needs --net=host. I'd be OK with them just being available in a container, but it might make more sense to just include them in the atomic ISO installation, maybe even borrowing a list from the Server product? -- Chris Murphy

6 16

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud December 2015