cloud December 2014

cloud@lists.fedoraproject.org

31 participants
76 discussions

[cloud] #89: Add Dockerfile Section to Downloads Page?
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#89: Add Dockerfile Section to Downloads Page? --------------------+-------------------- Reporter: jzb | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: --------------------+-------------------- For discussion - should we add a Dockerfile section on the downloads site? -- Ticket URL: <https://fedorahosted.org/cloud/ticket/89> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 2

[cloud] #83: participation in OpenShift Commons
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#83: participation in OpenShift Commons --------------------+--------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting --------------------+--------------------- Take a look at http://origin.openshift.com/commons I brought up joining this to the board, and got the reasonable response of "have you gotten the Cloud SIG committed to actually doing the participation asked for?" I've talked to a couple of people and I think there's sufficient interest, but it seemed reasonable to ask formally if this is something we're interested in. The actual formal requirements seem to be low: > OpenShift Commons is open to anyone. We have no Contributor License Agreement (CLA) or required donation to join. Instead we take each organization at their word to be active participants in forums, Special Interest Groups (SIGs), mailing lists and events. and I think it'd be _great_ to have Fedora officially involved in that way. What do you all think? -- Ticket URL: <https://fedorahosted.org/cloud/ticket/83> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 4

[cloud] #78: Draft charter change, new slate (Cloud WG members vote needed!)
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#78: Draft charter change, new slate (Cloud WG members vote needed!) --------------------+-------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: --------------------+-------------------- Joe has prepared a draft change to the charter https://lists.fedoraproject.org/pipermail/cloud/2014-October/004372.html making it easier to select new members. Additionally, I've proposed a new WG membership slate based on current activity: https://lists.fedoraproject.org/pipermail/cloud/2014-October/004372.html By the existing rules, both of these need 5 +1 votes from existing members of the WG to pass. That is, the people listed https://fedoraproject.org/w/index.php?title=Cloud/Governance&oldid=368062#C… — so, current members, please vote on each. If we can't reach quorum in a week, I'll take this to FESCo for "override approval", but I hope that won't be necessary. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/78> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 7

[cloud] #76: Explore possibility of shipping preconfigured KVM cloud image on live DVD
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#76: Explore possibility of shipping preconfigured KVM cloud image on live DVD --------------------+-------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: --------------------+-------------------- I suggested this for Fedora Server, and Josh mentioned to me that we could do it for the cloud. What about prepackaging the cloud image on-disk with a live Workstation- based image, with an existing KVM configuration including a preconfigured config-drive allowing SSH access to the local user. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/76> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

[cloud] #71: libmicrohttpd is back as a systemd dependency
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#71: libmicrohttpd is back as a systemd dependency --------------------+-------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: --------------------+-------------------- This was gone from F20 (https://bugzilla.redhat.com/show_bug.cgi?id=908081) but is back now. As noted in this bug, it is undesirable because libmicrohttpd pulls in gnutls (and nettle) , which is not otherwise on the base image. Reducing the number of crypto libraries there by default reduces the need to respin off-cycle security updates -- this is not an abstract concern. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/71> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 2

[cloud] #60: Enable serial console for bootloader
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#60: Enable serial console for bootloader ---------------------+-------------------- Reporter: fabiand | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: ---------------------+-------------------- The bootloader of the current cloud images is not attached to a serial console. Please change this, so we can also follow the bootloader part on the serial console, i.e. for test automation. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/60> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 5

[cloud] #53: anaconda doesn't allow installation of current fedora-cloud-base.ks
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#53: anaconda doesn't allow installation of current fedora-cloud-base.ks ---------------------+-------------------- Reporter: walters | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: ---------------------+-------------------- Cloud images are expected to come with: * root password locked * No user precreated; instead, an agent (cloud-init, min-metadata-service) pull config data from the hypervisor and inject ssh keys, create users, etc. The problem is Anaconda's user.py is a mandatory step. A suggested hack is to set a root password, then unset it in %post. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/53> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 2

[cloud] #44: hey we should have a vagrant base box
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#44: hey we should have a vagrant base box --------------------+-------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: --------------------+-------------------- This is a very long-standing request. Here is a ticket for it. :) -- Ticket URL: <https://fedorahosted.org/cloud/ticket/44> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 14

[cloud] #23: File F21 change: Re-factor cloud-init
by Nobody 13 Oct '16

13 Oct '16

#23: File F21 change: Re-factor cloud-init ------------------------------+------------------------------------------ Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Feature Deadline) Component: Cloud Base Image | Keywords: ------------------------------+------------------------------------------ '''Summary:''' Cloud Init was initially designed for a different distribution and is only loosely tailored for our needs. As it stands, it pulls in a rather large set of packages not used for other things. It is also written in Python, itself a large subsystem which it would eventually be nice to leave out of the base. Effort is moderate, with some low- hanging fruit which may be addressed easily. '''Importance:''' vital long term, but just moderate for F21 (We really need this, but if we don't get work it now, it's in acceptable shape for this release.) '''Timeframe:''' F21 alpha, or F22 / if we don't make alpha with changes, this can go in next release. '''Scope:''' Self-contained '''Cloud SIG owner:''' TBD -- Ticket URL: <https://fedorahosted.org/cloud/ticket/23> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 15

[cloud] #34: External need: batched updates
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#34: External need: batched updates --------------------+------------------------ Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Flock 2014 Component: --- | Keywords: --------------------+------------------------ '''Summary:''' We want to produce updated images on a monthly cadence. It would be nice if we could produce those from QA'd bunches of packages. '''Importance:''' moderate (it will be hard to implement image refresh without this, but we could do it) '''Timeframe:''' F21 release + 1 month / Obviously better if we get things lined up earlier '''Fedora Sub-Project/SIG:''' Primarily QA, but Rel Eng and Infrastructure too. This is pretty big. ''' Cloud SIG owner:''' TBD (this probably needs someone actively contributing to initial and ongoing work) See the related Change proposal "(A)Periodic Updates to the Images" http://flock2013.sched.org/event/8c4f702e42814598e0e4e31b188a0ae6 What's this ticket about? We need an owner for this — someone to drive it forward. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/34> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud December 2014