[cloud] #14: Investigate systemd-networkd
by Nobody
#14: Investigate systemd-networkd
------------------------------+-------------------------------
Reporter: mattdm | Owner: janeznemanic
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Alpha)
Component: Cloud Base Image | Keywords:
------------------------------+-------------------------------
* What: new service to do very basic network config
* Where: remove the sysv network scripts, add config for this
* Why: remove very kludgey shell scripts; try the new hotness
* When: Before F21 alpha
* Who: Janez Nemanic
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/14>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
7 years, 1 month
[cloud] #13: Port Cloud Image Kickstart to anaconda/imagefactory
by Nobody
#13: Port Cloud Image Kickstart to anaconda/imagefactory
------------------------------+-----------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 21
Component: Cloud Base Image | Keywords:
------------------------------+-----------------------
Rel-Eng is updating to Koji 1.9, which will allow us to use Anaconda and
ImageFactory for image creation instead of appliance-creator.
* What: The current kickstart file is full of kludges for appliance-
creator. Port to anaconda/imagefactory kludges
* Where: same as ongoing maintenance of kickstart
* Why: appliance-creator is being retired; anaconda-based installs are the
way forward
* When: As soon as this is available in Koji. Need a new ImageFactory
release, then patches into Koji for support, then a new Koji release, then
Koji needs to be updated in Fedora production
* Who: Ian McLeod is working on ImageFactory; Jay Greguske on the Koji
patches, Mike McLean is Koji maintainer, Dennis Gilmore in release
engineering will do the Koji update. Need to work with them to get this in
place, and then someone from cloud wg needs to do the updating.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/13>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
7 years, 1 month
[cloud] #16: rename cloud spin kickstart to distinguish the cloud base image
by Nobody
#16: rename cloud spin kickstart to distinguish the cloud base image
--------------------+--------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: minor | Milestone: Fedora 21 (Branch)
Component: --- | Keywords: meeting
--------------------+--------------------------------
I have been calling the new general purpose cloud image "Fedora Cloud
Base" to distinguish it from the Docker image, the Big Data image, and a
potential OpenShift image (if that turns out to not be the Docker one.)
I propose we officially call the general-purpose cloud image (currently,
the only one) "Fedora Cloud Base". And I'm tagging this with the meeting
keyword for ratification.
One behind-the-scenes complication is that the spins process involves
assembling kickstart fragments, one of which is suffixed with "-base.ks"
already, so there is a "cloud-image-base.ks", which would presumably
became "cloud-base-base.ks", which is... awesome? silly? One of those.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/16>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
9 years, 6 months
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
9 years, 8 months
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
9 years, 8 months
enabling spam filter
by Matthew Miller
You don't usually see 'em because they hit the moderation queue, but this
list gets a ridiculous amount of spam. I've enabled spam filtering and will
now automatically discard highly-scored spam messages. This shouldn't affect
any legitimate messages, but if you post and it doesn't get through... that
might be it and I'll look at adjusting the settings.
--
Matthew Miller -- Fedora Project -- <mattdm(a)fedoraproject.org>
"Tepid change for the somewhat better!"
9 years, 8 months
