From Fedora Project Wiki
 
(98 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Please look at the [[Networking]] wiki page. It links to many other interesting wiki pages about linux networking. I moved most of the text from my user page there. Any help appreciated.
Mail: psimerda AT redhat DOT com, pavlix AT pavlix DOT net
 
Jabber: pavlix AT pavlix DOT net
 
IRC Freenode: pavlix (#nm, #gentoo, ...)
 
Phone: +420 775 996 256
 
Timezone: Europe/Prague (CET), sometimes available through later hours
 
== About ==
 
After learning a bit of programming, I was attracted by the networking world. I got from petty Pascal/C++ projects through web development using PHP and later Python, to years of freelancing work with most of the projects in server administration, network equipment configuration and a bit of programming. I was active in the community, wrote articles and spoke at conferences which finally led to my joining Red Hat in May 2012 to work on NetworkManager. I was already a Fedora user and package maintainer at that time. Since August 2013 I'm working on various network related packages and projects.
 
== Projects ==
 
Fedora projects:
 
* [https://github.com/pavlix/network-testing User space networking test suite] (owner)
* [https://github.com/pavlix/netresolve Non-blocking network name resolution library and tools] (owner)
* [https://github.com/pavlix/gentoo-rpm Gentoo ebuilds for Fedora and CentOS development] (owner)
* [https://github.com/pavlix/fptool Wrapper over Fedora package maintainance tools] (owner)
* DNSSEC in Fedora (contributor)
* IPv6 and dual-stack networking (contributor)
* [https://wiki.gnome.org/Projects/NetworkManager NetworkManager development] (contributor, former developer
 
Fedora wiki documentation:
 
* [[Networking]] – A starting point for information related to networking.
* [[Tools/NetworkManager]] – NetworkManager information page.
* [[QA/Networking]] – Dual-stack networking issues in Fedora.
 
(Contributions are welcome.)
 
Packages:
 
[https://admin.fedoraproject.org/pkgdb/packager/pavlix/ Fedora Package Database].
 
== Other resources ==
 
Fedora features:
 
* [[Changes/Default_Local_DNS_Resolver]]
 
Ideas:
 
* [[Networking/Ideas/ServiceOrdering]]
* [[Networking/Ideas/NameResolution]]
* [[Networking/Ideas/NetworkManagerMethods]]
* [[Networking/Ideas/NetworkManagerRuntimeConfiguration]]
* [[Networking/Ideas/ConfigurationService]]
* [[Networking/Ideas/AutomaticConfiguration]]
* [[Networking/Ideas/NetworkNameResolution]]
* [[Networking/Ideas/NetworkManagerBugReporting]]
* [[Networking/Ideas/NetworkManagerOnServers]]
 
== Fedora notes ==
 
=== Simple maintainance tasks ===
 
==== Make a fix and a build ====
 
<pre>
bug=123456
message="do something"
 
# ... add/modify files ...
rpmdev-bumpspec *.spec -c "Resolves: #$bug - $message"
fedpkg commit -c
# ... check using gitk ...
fedpkg push && fedpkg build
</pre>
 
==== Make a scratch build from locally generated SRPM ====
 
<pre>
fedpkg build --scratch --srpm
</pre>
 
==== Bump a rawhide package to a newer version ====
 
In the package git directory:
 
<pre>
version=...
 
# Prepare a commit
fedpkg switch-branch master
rpmdev-bumpspec --new="$version" --comment="new version $version" *.spec
spectool -g *.spec && fedpkg new-sources `spectool -l *.spec | grep / | sed 's/.*\///'`
fedpkg commit -c
 
# Test it
fedpkg build --scratch --srpm
 
# Create a public build
fedpkg push && fedpkg build
</pre>
 
Requires development version, see:


=== About me ===
* https://fedorahosted.org/rpmdevtools/attachment/ticket/14


From my Linux beginnings, I was attracted by the networking world. I kept experimenting, then started freelancing for companies and ISPs providing consultancy, training, network configuration, programming and other services. I started writing articles and talking at conferences about network-related topics. I was keeping more and more bug reports in various projects including Fedora. After a recent conference talk I was hired by Red Hat and finally started fixing those bugs and working on NetworkManager and other networking-related projects.
==== Prepare rawhide to replace branches ====


I have been using Fedora for some time. My primary interest is computer networking and I didn't like many things
Warning: This method discards changes in all branches and should only be used after all of the important changes are incorporated into master. Also, it is only suitable for packages where it's practical to maintain the same version in branches as in rawhide.
in linux networking and particularly in NetworkManager. I've been talking about it and watching and filing bug reports
for too long. When I recieved an offer to work regularly on NetworkManager, it was natural to accept.


At the time I joined NetworkManager development, I already had a history of articles, talks and trainings on IPv6
<pre>
so I started fixing IPv6 automatic configuration. In NetworkManager 0.9.6 it connects to any standard IPv6 networks.
branches="f20 f19"


I didn't particularly like how NetworkManager works so after learning a bit about it, I started working on some
# Fake-merge all branches into master:
larger-scale changes in a separate branch called 'pavlix/next' that is described below. All of the modifications
for branch in $branches; do
are made with the goal of making NetworkManager more robust, testable, debuggable and useful for all sorts of use
    fedpkg switch-branch master
cases including server, virtualization and desktop.
    git merge -s ours $branch
done


During my work on NetworkManager, I see more and more problems with other network-related tools including kernel,
# Build a new release
glibc, avahi, nss-mdns but also with the IETF standards. We have many more things to be fixed (or replaced, if
rpmdev-bumpspec
anyone likes that better) than just NetworkManager.
fedpkg commit -c
fedpkg push
fedpkg build
</pre>


=== Linux networking ===
==== Update branches to match rawhide and build them ====


I'm currently working on the following (may be outdated):
Use the above technique to prepare rawhide if branches can't be fast forwarded to rawhide.


* [http://bugzilla.gnome.org/show_bug.cgi?id=683173 New platform interaction framework]
<pre>
* NetworkManager upstream QA, bug triaging (component general) and bits of documentation
branches="f21 f20"
* Virtual device support (bridging, bonding, etc)
* Fixes and improvements for getaddrinfo() in glibc
* Configuration formats
* [http://bugzilla.gnome.org/show_bug.cgi?id=663602 Building NetworkManager on any distribution without unnecessary hassle]
* IPv4 and IPv6 automatic configuration improvements (NDP and DHCP)
* Various NetworkManager fixups and cleanups (like anyone else in the team)
* Various linux networking improvements


When working with linux networking, the following projects cause me headache:
# Fast-forward all branches to master HEAD:
for branch in $branches; do
    fedpkg switch-branch $branch
    git merge --ff-only master
    fedpkg push
    fedpkg build --nowait
done


* NetworkManager itself: I need to test NM in a virtual environment with bridges. These are not supported in the current release. I hope to make the next release mature enough to support its own development.
# Switch back to master
* Kernel: The kernel IPv6 networking layer is somewhat unmanagable. The rtnetlink interface doesn't provide enough funcionality to support IPv6 networking.
fedpkg switch-branch master
* GLIBC: The <code>getaddrinfo()</code> function doesn't work properly and is not supported in nsswitch.conf. It breaks whenever my development machine happens to be on an IPv4-only network.
</pre>
* nss-mdns (Avahi nsswitch plugin): Can't implement link-local name resolution because of the above problem in GLIBC.
* IETF networking standards: For some reasons many IPv6-related standards have serious design flaws that prevent them from working properly.


=== Contact ===
==== Issue updates ====


Mail: psimerda AT redhat DOT com, pavlix AT pavlix DOT net
<pre>
branches="f21 f20"
type=bugfix
bugs=
comment="Bug fix update."
 
# Create updates for all branches
for branch in $branches; do
    fedpkg switch-branch $branch
    bodhi --new --type="$type" --bugs="$bugs" --notes="$comment" --close-bugs `fedpkg verrel`
done
 
# Switch back to master
fedpkg switch-branch master
</pre>
 
Resources:
 
* [https://apps.fedoraproject.org/packages/ Package version in Fedora and EPEL]
* [https://admin.fedoraproject.org/updates/ Package updates]
 
=== Patchwork ===
 
==== Using vim ====
 
Open three panes containing (1) patch to be edited, (2) patched file and (3) rejected hunks.
 
<pre>
package=...
version=...
patch=...
file=...
 
vim -O $patch $package-$version/$file{,.rej}
</pre>
 
==== Using git ====
 
Warning: Untested. I used a similar command but lost it.
 
 
<pre>
package=...
version=...
dir=/path/to/upstream/workdir
 
(echo cd $dir; for patch in `awk '/^Patch[0-9]*: / { print $2 }' *.spec`; do echo -n "git apply --index "; realpath $patch; echo git commit -m $patch; done) | sh
</pre>
 
=== New package ===
 
==== Create a local Git repository ====
 
<pre>
package=...
editor=...
 
git init $package
cd $package
 
$editor $package.spec
git add $package.spec
 
fedpkg new-sources `spectool -l *.spec | grep / | sed 's/.*\///'`
 
rpmdev-bumpspec $package.spec -m 'initial build'
fedpkg commit -c
</pre>
 
==== Create a review request ====
 
<pre>
rawhide=f22
 
fedpkg --dist $rawhide srpm
fedora-create-review --no-scratch-build *.spec *.src.rpm
</pre>
 
==== Update a review request ====
 
<pre>
rawhide=f22
message="incorporated review feedback"
 
rpmdev-bumpspec *.spec -m "$message"
fedpkg commit -c
 
fedpkg --dist $rawhide srpm
fedora-create-review --amend --no-scratch-build *.spec *.src.rpm
</pre>
 
Requires:
 
* https://fedorahosted.org/FedoraReview/ticket/237
 
=== Review a new package ===
 
System configuration:
 
<pre>
yum install @fedora-packager fedora-review
ln -s /etc/mock/fedora-devel-x86_64.cfg /etc/mock/default.cfg
 
mockuser=...
 
usermod -a -G mock $mockuser
</pre>
 
Review local files:
 
<pre>
name=...
 
fedora-review -n $name
</pre>
 
Review bugzilla:
 
<pre>
bz=...


Jabber: pavlix AT pavlix DOT net
fedora-review -b $bz
</pre>


IRC Freenode: pavlix (#nm and a couple of other channels)
== Fedora tools on Gentoo ==


Phone: +420 775 996 256
<pre>
emerge -av layman
echo source /var/lib/layman/make.conf > /etc/portage.make.conf
layman -a ixit
mkdir -p /etc/portage/sets
cat > /etc/portage/sets/fedora-packaging <<EOF
dev-util/fedora-packager
dev-util/quilt
EOF
emerge -av @fedora-packaging
</pre>

Latest revision as of 13:29, 28 October 2016

Mail: psimerda AT redhat DOT com, pavlix AT pavlix DOT net

Jabber: pavlix AT pavlix DOT net

IRC Freenode: pavlix (#nm, #gentoo, ...)

Phone: +420 775 996 256

Timezone: Europe/Prague (CET), sometimes available through later hours

About

After learning a bit of programming, I was attracted by the networking world. I got from petty Pascal/C++ projects through web development using PHP and later Python, to years of freelancing work with most of the projects in server administration, network equipment configuration and a bit of programming. I was active in the community, wrote articles and spoke at conferences which finally led to my joining Red Hat in May 2012 to work on NetworkManager. I was already a Fedora user and package maintainer at that time. Since August 2013 I'm working on various network related packages and projects.

Projects

Fedora projects:

Fedora wiki documentation:

(Contributions are welcome.)

Packages:

Fedora Package Database.

Other resources

Fedora features:

Ideas:

Fedora notes

Simple maintainance tasks

Make a fix and a build

bug=123456
message="do something"

# ... add/modify files ...
rpmdev-bumpspec *.spec -c "Resolves: #$bug - $message"
fedpkg commit -c
# ... check using gitk ...
fedpkg push && fedpkg build

Make a scratch build from locally generated SRPM

fedpkg build --scratch --srpm

Bump a rawhide package to a newer version

In the package git directory: 

version=...

# Prepare a commit
fedpkg switch-branch master
rpmdev-bumpspec --new="$version" --comment="new version $version" *.spec
spectool -g *.spec && fedpkg new-sources `spectool -l *.spec | grep / | sed 's/.*\///'`
fedpkg commit -c

# Test it
fedpkg build --scratch --srpm

# Create a public build
fedpkg push && fedpkg build

Requires development version, see:

Prepare rawhide to replace branches

Warning: This method discards changes in all branches and should only be used after all of the important changes are incorporated into master. Also, it is only suitable for packages where it's practical to maintain the same version in branches as in rawhide. 

branches="f20 f19"

# Fake-merge all branches into master:
for branch in $branches; do
    fedpkg switch-branch master
    git merge -s ours $branch
done

# Build a new release
rpmdev-bumpspec
fedpkg commit -c
fedpkg push
fedpkg build

Update branches to match rawhide and build them

Use the above technique to prepare rawhide if branches can't be fast forwarded to rawhide. 

branches="f21 f20"

# Fast-forward all branches to master HEAD:
for branch in $branches; do
    fedpkg switch-branch $branch
    git merge --ff-only master
    fedpkg push
    fedpkg build --nowait
done

# Switch back to master
fedpkg switch-branch master

Issue updates

branches="f21 f20"
type=bugfix
bugs=
comment="Bug fix update."

# Create updates for all branches
for branch in $branches; do
    fedpkg switch-branch $branch
    bodhi --new --type="$type" --bugs="$bugs" --notes="$comment" --close-bugs `fedpkg verrel`
done

# Switch back to master
fedpkg switch-branch master

Resources:

Patchwork

Using vim

Open three panes containing (1) patch to be edited, (2) patched file and (3) rejected hunks. 

package=...
version=...
patch=...
file=...

vim -O $patch $package-$version/$file{,.rej}

Using git

Warning: Untested. I used a similar command but lost it. 


package=...
version=...
dir=/path/to/upstream/workdir

(echo cd $dir; for patch in `awk '/^Patch[0-9]*: / { print $2 }' *.spec`; do echo -n "git apply --index "; realpath $patch; echo git commit -m $patch; done) | sh

New package

Create a local Git repository

package=...
editor=...

git init $package
cd $package

$editor $package.spec
git add $package.spec

fedpkg new-sources `spectool -l *.spec | grep / | sed 's/.*\///'`

rpmdev-bumpspec $package.spec -m 'initial build'
fedpkg commit -c

Create a review request

rawhide=f22

fedpkg --dist $rawhide srpm
fedora-create-review --no-scratch-build *.spec *.src.rpm

Update a review request

rawhide=f22
message="incorporated review feedback"

rpmdev-bumpspec *.spec -m "$message"
fedpkg commit -c

fedpkg --dist $rawhide srpm
fedora-create-review --amend --no-scratch-build *.spec *.src.rpm

Requires:

Review a new package

System configuration: 

yum install @fedora-packager fedora-review
ln -s /etc/mock/fedora-devel-x86_64.cfg /etc/mock/default.cfg

mockuser=...

usermod -a -G mock $mockuser

Review local files: 

name=...

fedora-review -n $name

Review bugzilla: 

bz=...

fedora-review -b $bz

Fedora tools on Gentoo

emerge -av layman
echo source /var/lib/layman/make.conf > /etc/portage.make.conf
layman -a ixit
mkdir -p /etc/portage/sets
cat > /etc/portage/sets/fedora-packaging <<EOF
dev-util/fedora-packager
dev-util/quilt
EOF
emerge -av @fedora-packaging
Retrieved from "https://fedoraproject.org/w/index.php?title=User:Pavlix&oldid=478145"