[cloud] #21: File F21 change: Install without i10n / l18n support (w/optional install)
by Nobody
#21: File F21 change: Install without i10n / l18n support (w/optional install)
------------------------------+------------------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Feature Deadline)
Component: Cloud Base Image | Keywords:
------------------------------+------------------------------------------
'''Summary''' We need to have a cloud image without the overhead/extra
space requirements of i10n / l18n support, but want to provide the option
to install these packages if needed. In many cases these are not necessary
for images running in the cloud.
'''Importance:''' moderate (Should not be overly difficult to implement,
but is not a show-stopper if it's not complete by F21.)
'''Timeframe:''' F21 alpha / should be at least mostly implemented by
alpha or won't be ready for this release.
'''Scope:''' self-contained
'''Cloud SIG owner:''' mattdm (I already have a conversation open with
anaconda and the packaging team)
https://fedoraproject.org/wiki/Changes/Optional_i10n_and_l18n_support_clo...
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/21>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
10 years
Process to Create New Cloud Images?
by Sandro "red" Mathys
I see we're now using the spin-kickstarts git, but do we also follow
the usual Spin SIG processes?
Or, to rephrase that: How do I start working on the Docker Host image?
I know, all the big changes are still up for discussion but I'd rather
be ready early so the actual work can start as soon as we know where
we're going.
Also, how is a kickstart file turned into an image (most notably
automated nightly rawhide builds)? Do I open a ticket with rel-eng or
is there some other process?
Thanks,
Sandro
10 years
Re: [cloud] #4: new release criteria for post-f20 cloud image
by Fedora Cloud Trac Tickets
#4: new release criteria for post-f20 cloud image
------------------------------+--------------------------------
Reporter: mattdm | Owner: red
Type: task | Status: accepted
Priority: major | Milestone: Fedora 21 (Alpha)
Component: Cloud Base Image | Resolution:
Keywords: |
------------------------------+--------------------------------
Changes (by red):
* milestone: Fedora 21 (Final) => Fedora 21 (Alpha)
* owner: => red
* status: new => accepted
Comment:
IMHO, this really goes hand-in-hand with ticket #41 (proven by comment 3)
so taking this, too.
Also, since Fedora has separate Alpha, Beta AND Final release criteria,
I'm going to change the milestone accordingly. There might or might not be
any Alpha/Beta criteria but it's easier to postpone to a later milestone
than the other way around.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/4#comment:5>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
10 years
[cloud] #22: File F21 change: Ability to install without documentation (w/optional install later)
by Nobody
#22: File F21 change: Ability to install without documentation (w/optional
install later)
----------------------------+------------------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Feature Deadline)
Component: Docker (Other) | Keywords:
----------------------------+------------------------------------------
'''Summary:''' In many cases, users will not want documentation on cloud
images. We should be able to provide support to create/deliver cloud
images without documentation but still have it available for installation
if desired.
'''NOTE:''' we need to decide on an image-by-image basis whether we will
include the docs by default. Previously there was strong SIG support for
leaving man pages in the image for administrator convenience. We should
affirm that decision or, if we want to change it, do so intentionally.
It's likely that the docker host image _won't_ contain docs but the cloud
base host image will. Docker _container_ images more certainly won't.
'''Importance:''' moderate
'''Timeframe:''' F21 alpha / should be at least mostly implemented by
alpha or will not be ready for this release.
Scope. self-contained
Cloud SIG owner. mattdm
https://fedoraproject.org/wiki/Changes/Optional_documentation_cloud_image
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/22>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
10 years
Automatic Smoketests for the Cloud Images: What to Test?
by Sandro "red" Mathys
Heads-up: I've taken ownership for the external need "Automatic
Smoketests on Image Build" [0]
Testing an image takes time and resources, and with several images, it
takes several times that. Since that simply doesn't scale - well,
doesn't even work well without scaling - we want to automate the
smoketests using Taskotron. Unfortunately, Taskotron is still in a
very early development phase and having mentioned only just our (most)
basic needs, Tim estimates it won't be good enough for us in the
target timeframe (i.e. by F21 Alpha). There's a slight chance it will
be ready, but even then we still need time to implement the
smoketests.
So if we want to have Taskotron ready for us in time, we need to find
some developer(s) committing some of their resources. Any takers? If
you're interested, head to [1] to learn more, there's also a
contribution guide linked from there. I'm sure tflink in #fedora-qa is
happy to talk to people still interested after reading through the
wiki if there's further questions.
Also, we need to compile our actual needs. What kind of tests do we
want to run? Most basic tests (things that we manually tested in the
past) are probably:
- Was the IP correctly set up?
- Is SSH running and reachable?
- Does the fedora user exist?
- Is the ssh pubkey installed for the fedora user?
- Is the fedora user able to use sudo?
- Is the root account locked?
- Is package installation working?
- Is the firewall disabled?
- Checking cloud-init and systemctl for bootup errors - does that make
sense or is there too much noise?
What else can / should we test? Obviously the tailored images should
be tested for their specific stuff but lets first focus on the common
ground.
Thanks,
Sandro
[0] https://fedoraproject.org/wiki/Cloud_Changelist#External_Need:_Automatic_...
[1] https://fedoraproject.org/wiki/Taskotron
10 years
help needed (soooo much help needed)
by Matthew Miller
Please take a look at
https://fedorahosted.org/cloud/query?status=accepted&status=assigned&stat...
These are the about-a-dozen changes we decided we are going to file for F21.
We need to actually file them by Tuesday.
A couple of these have been spoken for, but most of them not. It would be
incredibly excellent if people could help out here. You don't necessarily
need to do all of the work, or in fact (in some cases at least) any of it,
as long as you can talk to people and coordinate effort. These are all
things we've already agreed we want to work on so there should be no actual
controversy.
And, even if you don't want that level of commitment, it actually helps to
just start filling out the empty templates (linked in the bugs above).
I am super-busy today, and probably tomorrow, and my weekend is spoken for
by Northeast Linux Fest and hopefully some family time on Sunday. So, I'm
planning on devoting Monday to this, but I'd also not like to leave it all
til then, so -- whatever you can contribute to between now and then =
awewsome.
Thanks everyone!
--
Matthew Miller -- Fedora Project -- <mattdm(a)fedoraproject.org>
"Tepid change for the somewhat better!"
10 years
[cloud] #32: Remove uboot-tools from cloud base package set
by Fedora Cloud Trac Tickets
#32: Remove uboot-tools from cloud base package set
------------------------------+--------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: minor | Milestone: Fedora 21 (Branch)
Component: Cloud Base Image | Keywords:
------------------------------+--------------------------------
{{{
Name : uboot-tools
Version : 2013.10
Release : 3.fc20
Architecture: x86_64
Install Date: Thu 12 Dec 2013 01:14:00 AM UTC
Group : Development/Tools
Size : 362997
License : GPLv2+
Signature : RSA/SHA256, Tue 03 Dec 2013 03:08:43 AM UTC, Key ID
2eb161fa246110c1
Source RPM : uboot-tools-2013.10-3.fc20.src.rpm
Build Date : Tue 03 Dec 2013 01:38:10 AM UTC
Build Host : buildvm-24.phx2.fedoraproject.org
Relocations : (not relocatable)
Packager : Fedora Project
Vendor : Fedora Project
URL : http://www.denx.de/wiki/U-Boot
Summary : U-Boot utilities
Description :
This package contains a few U-Boot utilities - mkimage for creating boot
images
and fw_printenv/fw_setenv for manipulating the boot environment variables.
}}}
Also pulls in:
{{{
Name : dtc
Arch : x86_64
Version : 1.4.0
Release : 2.fc20
Size : 193 k
Repo : installed
From repo : koji-override-0
Summary : Device Tree Compiler
URL : http://git.jdl.com/gitweb/?p=dtc.git;a=summary
License : GPLv2+
Description : The Device Tree Compiler generates flattened Open Firmware
style device trees
: for use with PowerPC machines that lack an Open Firmware
implementation
}}}
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/32>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
10 years
