cloud October 2014

cloud@lists.stg.fedoraproject.org

29 participants
99 discussions

Fedora 21 Beta RC2 status is **FAILED**, RC3 will be coming
by Adam Williamson 29 Oct '14

29 Oct '14

Wanted to keep everyone in the loop so people don't feel like their time has been wasted. We discovered at the blocker review meeting today that there's a problem with the RC2 compose. Blocker and FE packages that were pushed stable yesterday - https://fedorahosted.org/rel-eng/ticket/5988#comment:17 - were taken out of the 'bleed' repository where blocker/FE fixes are pulled into composes before they go stable, but they did not actually get mashed/distributed in time to be included in the RC2 compose. The upshot is that RC2 has incorrect (old) versions of initscripts, systemd and fedup-dracut. This means that RC2 will be subject to at least https://bugzilla.redhat.com/show_bug.cgi?id=1114786 , https://bugzilla.redhat.com/show_bug.cgi?id=1099299 and https://bugzilla.redhat.com/show_bug.cgi?id=1146580 , so it definitely cannot be released as the Beta. We will need an RC3 compose, and testing of RC2 will not be sufficient to clear RC3 for release due to the significance of systemd. Testing of RC2 is not entirely useless - it's still useful to check there are no regressions in anaconda 21.48-13, for instance - but we will need to do a good degree of testing on RC3 when it lands later today before we can consider clearing RC3 for release. I'm very sorry to folks who've already put work into testing RC2 for the mistake. Keep your eyes peeled for RC3! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Notes on Fedora Atomic TC for Beta
by Joe Brockmeier 29 Oct '14

29 Oct '14

Hi all, Grabbed the latest test compose [1] this morning to see what shape Atomic is in for the release. A couple of notes: * Boots fine * Able to log in with cloud-init taking info via an ISO image * Docker package present * No kubernetes packages or cockpit packages * Disk size is only 3GB so the image alone is kind of not-useful, since "docker pull fedora" fails as it fills up the disk entirely Pinged walters on IRC, he said he made changes to the json files[2] so that we'd get the right packages, but we also need to bump up the disk size to (I'd say) at least 8GB. Have not tested rpm-ostree at all on this image yet. Best, jzb [1] http://koji.fedoraproject.org/koji/taskinfo?taskID=7974506 [2] https://git.fedorahosted.org/cgit/fedora-atomic.git/tree/?h=f21 -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

2 1

[Action Required] Fedora 21 Cloud Beta Validation
by Matthew Miller 28 Oct '14

28 Oct '14

Soooo, basically, what Stephen says, but for Cloud, including the URL change to <https://www.happyassassin.net/testcase_stats/21/Cloud.html> :) ----- Forwarded message from Stephen Gallagher <sgallagh(a)redhat.com> ----- > Date: Tue, 28 Oct 2014 08:23:18 -0400 > From: Stephen Gallagher <sgallagh(a)redhat.com> > To: server(a)lists.fedoraproject.org > Cc: Paul Whalen <pwhalen(a)redhat.com> > Subject: [Action Required] Fedora 21 Server Beta Validation > X-Bogo25: H 2.5912e-05 > > As I assume everyone on this list knows by now, Beta was delayed by a > week due to several blocker bugs. (The only known blocker bug unique to > Server was an SELinux issue that has been subsequently resolved). > > Part of this slippage was due to late receipt of a viable release > candidate build (we really only got it on Thursday and had very limited > time to validate and determine its suitability). > > We are expecting to receive another release candidate build sometime > hopefully today, but possibly tomorrow. We are going to desperately need > to run through the release validation tests again. I did all of the > x86_64 testing myself last time around (with some help from the ARM > folks to do a basic smoke-test on that platform). I'd very much like to > parcel out the validation responsibilities for RC2 so that we can get > the coverage done quicker. > > The set of validation tests that have to pass are listed here: > https://www.happyassassin.net/testcase_stats/21/Server.html > > You can use Adam Williamson's handy-dandy relval tool[1] (release > validation, not to be confused with relative value) to submit the test > results. > > All of the x86_64 tests can be performed against virtual instances; > there are no hardware testing requirements there. The ARM tests might be > more complicated; I'm going to ask Kevin Fenzi and Paul Whalen to chime > in on how to get that set up. > > Since I've already got an environment set up for Active Directory, I > will handle the Testcase_realmd_join_kickstart and > Testcase_realmd_join_kickstart tests for x86_64 as well as any of the > other tests that I can get around to (Consider only the AD tests > covered; I will be double-checking some of the more important ones). > > The firewall tests are very easy, so these would be useful for a > beginner to jump into. The Cockpit tests are also pretty > straightforward, though the Cockpit realm join will require setting up > some infrastructure (such as running the "Testcase_Server_role_deploy - > Domain Controller" test first). > > If you volunteer for this, please commit yourself to the time (sometime > in the 24 hours following the RC2 availability announcement) to finish > them. If after volunteering you discover that you cannot manage it, > please inform the list as soon as possible so we can find someone to > take over. > > Volunteering should be done by replying to this email, keeping the > Server list in the TO: or CC: so that everyone knows what has been > claimed. I will be talking to the Badges folks about getting a badge for > assisting with Release Validation for Fedora 21. > > > [1] > https://www.happyassassin.net/2014/10/14/i-wrote-a-thing-relval-wikitcms-1-… > _______________________________________________ > server mailing list > server(a)lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/server ----- End forwarded message ----- -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

1 0

More on terminology (or, did we settle that yet?)
by Joe Brockmeier 28 Oct '14

28 Oct '14

Hey all, I can't quite recall where we landed on the terminology for Docker images, containers, etc. Was reading an OpenShift blog today and this is how they're defining container/image: Docker image: Defines a filesystem for running an isolated Linux process (typically an application) Docker container: Running instance of a Docker image with its own isolated filesystem, network, and process spaces. Not sure if this clarifies things, or muddies them... See: https://blog.openshift.com/openshift-v3-deep-dive-docker-kubernetes/ -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

2 1

good news everyone: f21 beta rc cloud builds now working
by Matthew Miller 27 Oct '14

27 Oct '14

Cloud Base: http://koji.fedoraproject.org/koji/taskinfo?taskID=7953754 Docker Base Image: http://koji.fedoraproject.org/koji/taskinfo?taskID=7953754 (Atomic to come, presumably) These are release candidate 1; presumably there will be an RC2 really soon now. But we can start testing with these just for sanity. -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

1 0

[cloud] #51: start communication/collaboration on cloud image updates
by Fedora Cloud Trac Tickets 27 Oct '14

27 Oct '14

#51: start communication/collaboration on cloud image updates --------------------+--------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting --------------------+--------------------- At today's FESCo meeting, FESCo approved https://fedoraproject.org/wiki/Changes/%28A%29Periodic_Updates_to_Cloud_Ima… but wants us to get started actually changing the hand-waving parts about * policies (when exactly we will do off-cycle updates) * QA expectations (the exact testing requirements) * QA contribution (commitments to help with the automation and possible manual testing) * release engineering help (contributing scripts/code/effort as needed) We really need people to sign up for each of these -- not necessarily to do all the work, but to take ownership of the communication and coordination for each. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/51> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 9

proposal for new "FOSCo" group to mirror FESCo
by Matthew Miller 27 Oct '14

27 Oct '14

I posted individual messages to a number of other mailing lists, but this one I'm just cross-posting to the three lists for the product working groups. We've floated a proposal to have a new "Fedora Outreach Steering Committee", which would replace FAmSCo — so no net new governance groups added, following Mitr's ban on such things :). The idea is to help coordinate marketing, support, and evangelism like we do the engineering side of things. I'm posting this on _these_ lists, because I think that if we do go this route, we should have FOSCo WG liaisons just like the FESCo liaison. -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

1 0

ostree/atomic composes + MM update
by David Gay 24 Oct '14

24 Oct '14

Hey -- An update on progress with the ostree/atomic work: lmacken has written up a Fedmsg-triggered composer that runs ostree composes when repos are updated: https://github.com/fedora-infra/fedmsg-atomic-composer. As of our conversation earlier today, it's almost ready for testing in stg. We're thinking that we'll use compose01.stg for this purpose temporarily, since nothing's running on it at the moment. We'll stand up MM1 there and see if we can get it to play with the composer. The idea lmacken suggested is to inject the ostree summary data into the yum metadata, pointing repomd.xml at it (using modifyrepo). IMO this sounds like a solid plan. That's about it for now. Another update in a few days. -- oddshocks

4 3

No Meeting Today
by Dusty Mabe 24 Oct '14

24 Oct '14

Per discussion on the "New Meeting Time" thread we have decided to cancel the meeting for today. The next meeting will be next week at the new time. Dusty

1 0

last minute f21 change -- workstation dropping installable tree
by Matthew Miller 23 Oct '14

23 Oct '14

So in today's FESCo meeting, it was decided that since the workaround for making the netinstall image isn't all... worked around... rel-eng wants to just drop making a separate installable Workstation tree. On the mirrors, Workstation will just contain the live images. (Netinstall will still be possible, from the server netinstall, but not the default.) I'm thinking that if that's being done, we should do the same with Cloud, and just have Cloud images directly under Cloud (with no repo or rpms there). What do you think? This will all need to be revisited for F22 in any case. -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

2 2

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud October 2014