cloud November 2014

cloud@lists.fedoraproject.org

25 participants
90 discussions

2014-11-26 @ 1600 UTC ** Blocker Review Meeting
by Mike Ruckman 24 Nov '14

24 Nov '14

# F21 Blocker Review meeting # Date: 2014-11-26 # Time: 16:00 UTC (run "date -d '2014-11-26 16:00 UTC'" to see local time) # Location: #fedora-blocker-review on irc.freenode.net While we just had a out of band blocker review today after the QA meeting, we'll still be having our regularly scheduled blocker review this Wednesday. We managed to knock out all of the blockers and FEs this morning, but still we had 2 proposed blockers and 1 proposed FE since. I would get ready for more proposals before the meeting on Wednesday, but if we don't get any it should be a short meeting. Maybe this time around we can all watch the FEsCo meeting :) If you want to take a look at the accepted blockers, the full list can be found here: https://qa.fedoraproject.org/blockerbugs/milestone/21/final/buglist We'll be evaluating these bugs to see if they violate the Final Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F21 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting See you Wednesday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- // Mike -- Fedora QA freenode: roshi http://roshi.fedorapeople.org

1 0

Testimonial #1
by Joe Brockmeier 24 Nov '14

24 Nov '14

Here's the first testimonial - big thanks to Dusty for running this down and Major for being massively responsive! This should be about the right length. Please lemme know if not. "Fedora 21 gives me the balance I'm looking for - a leading edge operating system with enterprise-level tools for fast provisioning and configuration." Major Hayden, Principal Architect at Rackspace Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

4 3

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 24 Nov '14

24 Nov '14

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2014-11-26 from 19:00:00 to 20:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: Standing meeting for the Fedora Cloud Workgroup Source: https://apps.fedoraproject.org/calendar//meeting/482/

1 0

cloud image network config, virtio-net, libvirt autodetection, and network vs NetworkManager, F20 vs F21
by Colin Walters 23 Nov '14

23 Nov '14

TL;DR: KB, I think the CentOS cloud images should use: https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?h=f21&id=98c4… Dennis, we should revert: https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?h=f21&id=5ae3… Longer story: I tried the CentOS 7 GenericCloud image: http://cloud.centos.org/centos/7/devel/ and it didn't have networking on boot. Let's look at the actors: - A base cloud image: Fedora 20, Fedora 21, CentOS 7 - Network configuration: As specified in the kickstart - A network driver: virtio-net, rtl8139 - virt-install guest autodetection: Determines whether or not you get virtio-net - network system (or NetworkManager, or systemd-networkd) - systemd: http://lists.freedesktop.org/archives/systemd-devel/2014-July/020906.html - Anaconda/kickstart behavior First, let's look at the current F20: https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-cloud-bas… It hardcodes eth0. And the version of systemd there uses eth0 for virtio-net. Now, let's look at some changes Dennis committed in the F21 cycle: ens3: https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?h=f21&id=e177… link: https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?h=f21&id=98c4… eth0 (but only for atomic): https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?h=f21&id=5ae3… (Dennis and others, can you send patches to the list for review? This issue would have been more obvious if I'd noticed the changes going by) A really critical variable here is whether or not libvirt guest autodetection works. Currently: libvirt automatically provides virtio-net: Fedora 20, Fedora 21 Generic libvirt gives you rtl8193: Fedora 21 Atomic, CentOS 7 It took me a while to figure out here that the reason the CentOS 7 image wasn't working was becuase of the libvirt autodetection. I have this utterly trivial "create-cloud-vm.sh" script I've been using: https://gist.github.com/cgwalters/a366c14b2fc58e0f7367 It does work if I specify --os-variant rhel7 for CentOS7. Which I'm now going to start doing by default in my script (I don't use it to boot anything else). But...the change to do DHCP on all links by default is also an important change. One we should highlight in the release notes.

2 2

please help test and +1 the server installer graphics
by Matthew Miller 20 Nov '14

20 Nov '14

https://admin.fedoraproject.org/updates/fedora-productimg-cloud-21-5.fc21 See testing notes on desktop list - same basically applies. Can also test using product.img as an updates.img. https://lists.fedoraproject.org/pipermail/desktop/2014-November/011178.html https://fedoraproject.org/wiki/Anaconda/Updates The installer still isn't fully "cloudified" and really only makes sense for cloud images when used with our kickstarts from https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/. But, hey, might as well make it pretty. -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

1 1

AMIs for Test Day?
by Joe Brockmeier 19 Nov '14

19 Nov '14

IIRC somebody sent the list of AMIs but I have not been able to dig it up -- do we have a list of AMIs for current Atomic builds to use for tomorrow's Test Day? Thanks, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

4 5

Fedora Cloud meeting on 2014-11-19
by Kushal Das 19 Nov '14

19 Nov '14

=========================== #fedora-cloud: Fedora Cloud =========================== Meeting started by kushal at 19:07:51 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-cloud/2014-11-19/fedora_cloud_sig.2… . Meeting summary --------------- * Roll Call (kushal, 19:08:17) * Previous Meeting follow-up (kushal, 19:11:22) * ACTION: roshi to bring new criteria to QA meeting Monday (2014-11-24) (roshi, 19:15:40) * Plan test days for Atomic image (#74) (kushal, 19:17:57) * Article for Fedora Magazine on "state of cloud SIG/product" for beta release (#75) (kushal, 19:21:28) * Fedora Magazine story will be pushed by jzb (kushal, 19:24:44) * publicize fedora-dockerfiles (#84) (kushal, 19:25:05) * LINK: https://twitter.com/dustymabe/status/535153359603265536 (dustymabe, 19:32:17) * Public Uploaded Images Criteria (#80) (kushal, 19:33:59) * participation in OpenShift Commons (83) (kushal, 19:37:40) * Open Floor (kushal, 19:41:10) Meeting ended at 19:59:24 UTC. Action Items ------------ * roshi to bring new criteria to QA meeting Monday (2014-11-24) Action Items, by person ----------------------- * roshi * roshi to bring new criteria to QA meeting Monday (2014-11-24) * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * kushal (99) * roshi (90) * dustymabe (28) * zodbot (12) * scollier (9) * mattdm (9) * jsmith (6) * kilted1 (3) * agrimm (3) * oddshocks (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot Kushal -- Fedora Cloud Engineer CPython Core Developer Director Python Software Foundation http://kushaldas.in

1 0

Regrets for today's meeting
by Joe Brockmeier 19 Nov '14

19 Nov '14

Hey all, Sorry - today's meeting would be 8 p.m. my time. Will try to get the "State of Cloud" piece pushed to Fedora Magazine sometime tonight or early tomorrow morning. Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

1 0

Testing Day Thursday - Please promote, and add yourselves to the wiki
by Joe Brockmeier 19 Nov '14

19 Nov '14

Hey all, Fedora Magazine post here: http://fedoramagazine.org/fedora-21-atomic-test-day-this-thursday/ Wiki page here: https://fedoraproject.org/wiki/Test_Day:2014-11-20_Atomic Please do spread the word and if you're going to participate, even for a few hours, please add yourself to the wiki page. I feel kinda lonely at the moment! Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

1 0

Fwd: [atomic-devel] recommending Flannel (w/ vxlan backend) for atomic -- thoughts?
by Joe Brockmeier 19 Nov '14

19 Nov '14

Upstream discussion to try to figure out which tool to use to set up networks for Atomic/Docker. Thoughts, comments, suggestions? -------- Forwarded Message -------- Subject: [atomic-devel] recommending Flannel (w/ vxlan backend) for atomic -- thoughts? Date: Tue, 18 Nov 2014 14:36:03 -0500 From: John W. Linville <linville(a)redhat.com> To: atomic-devel(a)projectatomic.io Greetings, Internally we've been doing a little looking at projects for setting-up overlay networks between minions in a Kubernetes cluster. One of the most interesting options has been Flannel (formerly Rudder). Flannel requires minimal configuration to slice a large subnet into a series of smaller subnets, one per minion running flanneld. Flannel uses a configuration stored as a JSON file in etcd. The JSON configuration looks a bit like this: { "Network": "192.168.88.0/24", "SubnetLen": 28, "Backend": { "Type": "vxlan" } } The above configuration would allow up to 16 minions to each allocate a /28 subnet for use by their local docker daemon. (Larger or smaller subnets are, of course, a simple matter of configuration.) The local configuration information is written by flanneld to a file under /var/run, and the info is used to pass the --bip option to docker so that it configures its docker0 bridge appropriately. Beyond that, the vxlan backend for flanneld on each minion creates a vxlan tunnel endpoint and configures it to use the DOVE extensions for routing. The route to the larger (e.g. /24) subnet points at the vxlan interface, so traffic to other minions is directed through it. Such traffic triggers L2MISS and L3MISS messages that are handled by flanneld, directing traffic to the appropriate minions. The result is a vxlan-based overlay network that enables connectivity between all the minions (and their pods) with a minimal amount of configuration required. This seems like a powerful and usable means to enable this communication. Given the description above (and whatever other sources you might have at your disposal), does anyone have any objections to using this as a default Kubernetes networking solution in Atomic? Or any questions about the use of Flannel in general? Thanks, John -- John W. Linville Hope is a good breakfast, but it is a linville(a)redhat.com bad supper. -- Sir Francis Bacon -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

1 0

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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud November 2014