Call for testers: distgit gitolite3@rhel7
by Pierre-Yves Chibon
Dear testers,
Mathieu Bridon and I have been working for a little while now on migrating our
existing distgit solution from RHEL6 to RHEL7, this as involved three migrations
in one:
* Migrate from RHEL6 to RHEL7
* Migrate from puppet to Ansible
* Migrate from gitolite2 to gitolite3
All this running now with SELinux enforcing (Many thanks to tfirg on #selinux for
his more than generous help on this point).
We are at the point were we are satisfied with it and all our tests have passed.
So before we actually migrate our production instance we would like to ask for
broader testing.
How to test?
1/ On /etc/rpkg/fedpkg.conf add the following block:
[fedpkgstg]
lookaside = http://pkgs.stg.fedoraproject.org/repo/pkgs
lookasidehash = md5
lookaside_cgi = https://pkgs.stg.fedoraproject.org/repo/pkgs/upload.cgi
gitbaseurl = ssh://%(user)s@pkgs.stg.fedoraproject.org/%(module)s
anongiturl = git://pkgs.stg.fedoraproject.org/%(module)s
tracbaseurl = https://%(user)s:%(password)s@fedorahosted.org/rel-eng/login/xmlrpc
branchre = f\d$|f\d\d$|el\d$|olpc\d$|master$
kojiconfig = /etc/koji.conf
build_client = koji
2/ create your fedpkgstg
ln -s /usr/bin/fedpkg ~/bin/fedpkgstg
(might involve creating the ~/bin directory)
3/ call fedpkgstg instead of fedpkg
What to test?
* clone a package
* push allowed on packages you have commit ACL for
* push blocked on packages you do not have commit ACL for (unless provenpackager
of course)
* push blocked on branches named: origin/<something>
* upload new sources work
* download existing sources work (note: we synced most of the git repos from
two days ago but we did not sync the lookaside cache, so you will most likely
have to upload to test the download)
When you test, you can drop by #fedora-fedmsg on IRC and see that the fedmsg
messages are sent properly.
You should also be receiving the emails about your upload/changes as you do with
the production system.
If you want to play further with the system and need to change the ACLs on some
packages, feel free to poke at pkgdb in stg (and give it a couple of minutes to
sync between pkgdb and gitolite):
https://admin.stg.fedoraproject.org/pkgdb/
All the change made there are only valid for stg, so you can orphan all your
packages without risk, just be sure of the URL ;-)
If you face any problem, please let us know
* by email
* on irc #fedora-admin
* on the fedora infrastructure trac: https://admin.stg.fedoraproject.org/pkgdb/
Thanks in advance for your help,
Pierre, Mathieu and your dear Fedora Infrastructure team
8 years, 4 months
[Guielines Change] Changes to the packaging guidelines
by Jason L Tibbitts III
%license must be used in place of %doc to designate any file containing
the license information for a package. See
https://fedoraproject.org/wiki/Packaging:Guidelines#Documentation and
https://fedoraproject.org/wiki/Packaging:LicensingGuidelines
Guidelines for DevAssistant packages (DAP) were added:
https://fedoraproject.org/wiki/Packaging:DevAssistant
The Python guidelines relating to naming of executables in /usr/bin were
updated to account for F22's "Python3 by default" feature:
https://fedoraproject.org/wiki/Packaging:Python#Executables_in_.2Fusr.2Fbin
The Python Egg packaging guidelines have been cleaned up to properly
refer to egg packages and egg metadata:
https://fedoraproject.org/wiki/Packaging:Python_Eggs
Clarified the naming guidelines to indicate how language bindings are
named: lua-randomdb instead of randomdb-lua:
https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Addon_Packages_.28General.29
Added information on dealing with unversioned shared libraries:
https://fedoraproject.org/wiki/Packaging:Guidelines#Downstream_.so_name_v...
The systemd guidelines were revised to include a section about the use
of PrivateDevices and PrivateNetwork:
https://fedoraproject.org/wiki/Packaging:Systemd#Private_devices_and_networking
Information on when timer activation must and must not be used was
added to the Systemd guidelines:
https://fedoraproject.org/wiki/Packaging:Systemd#Timer_activation
Removed pre-Fedora 18 information from systemd section of
https://fedoraproject.org/wiki/Packaging:ScriptletSnippets
A section has been added on log files and logrotate:
https://fedoraproject.org/wiki/Packaging:Guidelines#Log_Files
Several changes have been made to the MinGW packaging guidelines to
reflect new macros and changes to accepted practice:
https://fedoraproject.org/wiki/Packaging:MinGW
The mono guidelines were modified to mention the %{_monodir} and
%{_monogacdir} macros:
https://fedoraproject.org/wiki/Packaging:Mono
Guidelines for the application of patches have been added:
https://fedoraproject.org/wiki/Packaging:Guidelines#Applying_patches
Added information to the PHP guidelines on dealing with PSR-4
libraries:
http://fedoraproject.org/wiki/Packaging:PHP
The Ruby guidelines have been updated to account for the removal of the
testrb utility:
https://fedoraproject.org/wiki/Packaging:Ruby
Added a section to the review guidelines indicating how to handle
packages with unreviewed dependencies:
https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#A_note_on_dependencies
A class of exceptions for bundling of libraries was added. This class
applies to reverse bundling, where a large upstream has had a piece
forked off into a separate library. The exception allows for reverse
bundling in cases where an API from an upstream is being forked into its
own library so that code using an older version of that upstream is able
to make use of the new API. Packagers making use of this exception need
to still apply to the FPC for a virtual provide for tracking this
usage. This exception is not applicable to all cases of reverse bundling
so please read the full guideline:
https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries#Reverse_Bundling
and open an FPC ticket if things are still unclear.
8 years, 4 months
FESCo elections are open
by Jaroslav Reznik
Greetings,
FESCo elections are now open and we're looking for five new
committee members. Elections closes promptly at 23:59 UTC
on February 3rd. Don't forget to vote!
To cast your vote, go to:
https://admin.fedoraproject.org/voting
Read more about Fedora elections at
https://fedoraproject.org/wiki/Elections
and about the new FESCo at
http://fedoraproject.org/wiki/Development/SteeringCommittee
We use range voting in this process — vote for as many or as
few candidates as you like on a sliding scale.
Note: we were planning Env and Stacks WG elections too but
as number of candidates was the same as open seats, Env and
Stacks group decided not to run elections this time and
accept all candidates as committee members. See the announce-
ment from Honza Horak.
The Fedora Magazine interviews got delayed as we were waiting
for more questions being asked from the community. If you
need it to make your decision, please check magazine later.
Jaroslav
8 years, 4 months
F22 Self Contained Change: Vagrant
by Jaroslav Reznik
= Proposed Self Contained Change: Vagrant =
https://fedoraproject.org/wiki/Changes/Vagrant
Change owner(s): Josef Stribny <jstribny(a)redhat.com>
Provide Vagrant http://www.vagrantup.com/ with the libvirt provider
as a default.
== Detailed Description ==
Vagrant is an automation tool used to manage development environments
using virtualization and configuration management tools. It allows
developers and teams to work on their projects and test them in an
environment similar to production. Historically, Vagrant had a
dependency on VirtualBox, but the newer versions have a plugin system
allowing it to work with other virtualization technologies, including
libvirt. The plan is to package Vagrant with the support for libvirt
(coming as vagrant-libvirt plugin) replacing VirtualBox as a default
provider.
== Scope ==
* Proposal Owners: Initial work has been done in for Vagrant on F20
in a Copr repository. Patches and quick fixes should be cleaned up
or revisited. Also we need to depend on newer version of libvirt
through rubygem-fog. Some commits for that are already in upstream
repositories for vagrant-libvirt and fog. See upstream issue for
details.
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
8 years, 4 months
F22 Self Contained Change: qtile
by Jaroslav Reznik
= Proposed Self Contained Change: qtile =
https://fedoraproject.org/wiki/Changes/qtile
Change owner(s): John Dulaney <jdulaney(a)fedoraproject.org>
qtile is a tiling window manager written in python. More can be
found at the project's website [1].
== Detailed Description ==
Once qtile 0.9 is released upstream, package it for Fedora.
All of the dependencies are already in Rawhide as of this writing.
== Scope ==
* Proposal owners: Work with upstream to get releae out and then package for Fedora
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
[1] http://www.qtile.org/
8 years, 4 months
F22 Self Contained Change: Tunir
by Jaroslav Reznik
= Proposed Self Contained Change: Tunir =
https://fedoraproject.org/wiki/Changes/tunir
Change owner(s): Kushal Das <kushaldas(a)gmail.com>
Tunir is a self contained CI Continuous Integration [1] which will be used to
test Fedora Cloud images nightly. This tool can be used separately by any
developer in their Fedora 21 system to run/test their local tests/jobs.
== Detailed Description ==
Tunir is a very simple CI system written keeping Fedora Cloud images at mind.
At the same time it is generic enough to be used by anyone to configure and run
jobs/tests in their local system. We will be able to track the status of
nightly cloud builds, we can also keep track other changes like, the
dependencies pulled in, or the overall size of the images. The same tool can
used as a self contained CI system by any Fedora user to run their own tests
locally. The tool has a minimal dependency and very simple to configure and
maintain.
This tool right now can create vm(s) based on cloud images (without needing an
actual cloud), or can run the tests in a bare metal box, or it can even create
jobs inside Docker containers.
Example:
$ sudo tunir --job dockerjob --stateless
The above command will run a stateless job named "dockerjob", it will not save
the result into any database as it is a stateless run.
== Scope ==
* Proposal owners: kushaldas(a)gmail.com to work on tunir
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
[1] http://en.wikipedia.org/wiki/Continuous_integration
8 years, 4 months
F22 Self Contained Change: Local Test Cloud
by Jaroslav Reznik
= Proposed Self Contained Change: Local Test Cloud =
https://fedoraproject.org/wiki/Changes/Local_Test_Cloud
Change owner(s): Mike Ruckman <roshi(a)fedoraproject.org>
testCloud [1] is a small tool to download and boot cloud images locally.
== Detailed Description ==
testCloud was created because manually booting a cloud image locally can be a
pain. It handles downloading the image, spoofing cloud-init metadata as well as
providing an ssh_config to easily connect to the booted instance. What was
usually several different steps to get an image to boot locally is now just
one:
python testCloud.py <url for qcow2 image>
It currently supports both the Fedora Cloud Base as well as the Atomic host
image.
Note: testCloud will likely change names in the near future.
== Scope ==
* Proposal owners: Mike Ruckman, Kushal Das to implement proposed change
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
[1] https://github.com/Rorosha/testCloud
8 years, 4 months
F22 System Wide Change: Vagrant Box for Fedora Atomic and Fedora Cloud
by Jaroslav Reznik
= Proposed System Wide Change: Vagrant Box for Fedora Atomic and Fedora Cloud
=
https://fedoraproject.org/wiki/Changes/Vagrant_Box_Atomic
Change owner(s): Joe Brockmeier <jzb(a)fedoraproject.org>, Ian McLeod
<imcleod(a)redhat.com>, Langdon White <langdon(a)fedoraproject.org>
To produce Vagrant boxes based on the Fedora Atomic Host and Fedora Cloud
flavors so that users can easily work with Fedora in the Vagrant environment.
== Detailed Description ==
Vagrant is a tool for building and distributing development environments.
Vagrant boxes can easily be used on a number of local virtualization platforms
such as VirtualBox, VMware, via AWS or OpenStack, or with other platforms.
Vagrant is used on Linux, Mac OS X, and Microsoft Windows and would present
Fedora with an opportunity to reach a larger developer audience than it
currently does.
Many developers prefer to work with Vagrant [1] for their development work,
using Vagrant to lower their development setup time, increase productivity,
and avoid having to specifically install an OS each time they wish to use it
for development.
A number of people have produced unofficial Vagrant boxes, but the Fedora
project does not currently produce an "official" Vagrant box for consumption. We
would like to close the gap here and offer Vagrant users easy-to-consume Fedora
22 Atomic and Cloud flavored Vagrant boxes.
== Scope ==
* Proposal owners:
** Provide a kickstart file and additional definition for the Vagrant Boxes.
** Provide scripts and patches for Koji to generate Vagrant Boxes.
** Encourage testing of the new Vagrant Boxes by the rest of the Cloud Working
Group.
* Other developers:
** Encourage other Fedora developers to make use of the Fedora Vagrant Boxes
for their own development work.
** Ensure that Vagrant is packaged for Fedora 22.
* Release engineering:
** Would need to work with owners of this proposal to add needed features to
Koji, and add Vagrant Boxes to list of output formats required for release.
* Policies and Guidelines:
** No known impact.
== Contingency Plan ==
If feature is incomplete by Fedora 22 beta, it would be pulled from the
release. No contingency necessary for fallback as this does not exist in
Fedora 21.
* Contingency deadline: Beta
* Blocks release? No
* Blocks product? No
[1] https://www.vagrantup.com/
8 years, 4 months
