From Fedora Project Wiki

No edit summary
No edit summary
(41 intermediate revisions by the same user not shown)
Line 3: Line 3:
Jabber: pavlix AT pavlix DOT net
Jabber: pavlix AT pavlix DOT net


IRC Freenode: pavlix (#nm and a couple of other channels)
IRC Freenode: pavlix (#nm, #gentoo, ...)


Phone: +420 775 996 256
Phone: +420 775 996 256
Line 9: Line 9:
Timezone: Europe/Prague (CET), sometimes available through later hours
Timezone: Europe/Prague (CET), sometimes available through later hours


=== Wiki resources ===
== 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 ugly PHP and later Python, to a freelancing work with most of the projects in server administration, network equipment configuration and a bit of programming. Most people in the business know me from my conference talks and articles.
 
One of my conference talk brought me an offer from Red Hat, which I joined in May 2012 to work on NetworkManager. I was already a Fedora user and package maintainer at that time. Since August 2013 I'm no longer working as a regular NetworkManager developer (staying an upstream contributor, though). Even before that I tried to put my hands on a number of other projects via bug reports, tests and code. I'm also interested in various network-related standards and especially bugs and bad assumptions in IETF documents.
 
== Wiki resources ==


* [[Networking]] – A starting point for information related to networking.
* [[Networking]] – A starting point for information related to networking.
Line 16: Line 22:
Contributions are welcome.
Contributions are welcome.


=== Upstream contributions ===
== Packages ==
 
=== Maintainer ===
 
* aiccu (IPv6 tunneling client)
* connman
* racoon2
* radvd (taken over from Petr Písař)
* strongswan
 
Help with specific features or integration issues welcome.
 
=== Co-maintainer ===
 
* bind
* bind10
* NetworkManager-ssh
* rsync
* squid
 
== Upstream contributions ==


* [https://sourceware.org/git/?p=netresolve.git;a=blob;f=README;hb=HEAD netresolve] (author)
* dnssec-trigger
** NetworkManager integration scripts (with [[User:thozza|Tomáš Hozza]])
** systemd integration
* glibc (name resolution patches)
* NetworkManager
* NetworkManager
** Separate operating system interaction module (nm-platform, with [[User:danw|Dan Winship]])
** [http://bugzilla.gnome.org/show_bug.cgi?id=663602 Building on any distribution]
** Userspace IPv6 autoconfiguration (nm-rdisc, with [[User:jpirko|Jiří Pírko]])
** Virtual device support (bridging/bonding, with others)
** Valgrind and code coverage support for tests
** [http://bugzilla.gnome.org/show_bug.cgi?id=683173 Separate platform interaction module] (nm-platform, with [[User:danw|Dan Winship]])
*** Refactored NetworkManager's bridging/bonding/vlan configuration
*** Refactored NetworkManager's IPv4/IPv6 configuration
** Userspace IPv6 autoconfiguration (nm-rdisc/libndp, with [[User:jpirko|Jiří Pírko]])
*** Getting IPv6 autoconf features on par with IPv4
*** Avoiding loads of kernel IPv6 bugs and design flaws
** Runtime (non-persistent) configuration support (with [[User:danw|Dan Winship]] and [[User:dcbw|Dan Williams]])
** Runtime (non-persistent) configuration support (with [[User:danw|Dan Winship]] and [[User:dcbw|Dan Williams]])
** A ''lot'' of bug triaging
* rpmdevtools
== Bug tracking/reporting ==
* glibc
** The getaddrinfo() support is very complicated while not giving correct results in ''many'' cases.
* kernel
** Network configuration is a real pain.
** Kernel IPv6 autoconfiguration is only designed for trivial use cases and is very buggy.
* libnl
** Most of the advanced stuff is very buggy.
* avahi
** Missing for IPv6 link-local addresses.
** IPv6 disabled by default.
** Problems with duplicates in discovery.
== Daily usage ==
=== Distributions ===
* Gentoo
* Fedora/CentOS
* Debian
* OpenWRT
=== Desktop ===
* Gnome 3 – Seeking something more mature and stable
* Gnome Terminal
* Evolution (for IMAP/SMTP mail) – Seeking something more mature and stable
* Empathy/Telepathy (for jabber and IRC) – Seeking something more mature and stable
* Evince
* Firefox
=== Development ===
* vim
* gcc
* make, autotools
* gdb
* valgrind
=== Presentation ===
* LaTeX/Beamer
== Idea pages ==
* [[Networking/Ideas/NetworkManagerMethods]]
* [[Networking/Ideas/NetworkManagerRuntimeConfiguration]]
* [[Networking/Ideas/ConfigurationService]]
* [[Networking/Ideas/AutomaticConfiguration]]
* [[Networking/Ideas/NetworkNameResolution]]
* [[Networking/Ideas/NetworkManagerBugReporting]]
* [[Networking/Ideas/NetworkManagerOnServers]]
== Fedora notes ==
=== Fedora tools on Gentoo ===
<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>
=== Bump a rawhide package to a newer version ===
In the package git directory:
<pre>
VERSION=...
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
fedpkg push
fedpkg build
</pre>
Requires developmet 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 ===


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="f20 f19"
* 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.

Revision as of 10:19, 16 April 2014

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 ugly PHP and later Python, to a freelancing work with most of the projects in server administration, network equipment configuration and a bit of programming. Most people in the business know me from my conference talks and articles.

One of my conference talk brought me an offer from Red Hat, which I joined in May 2012 to work on NetworkManager. I was already a Fedora user and package maintainer at that time. Since August 2013 I'm no longer working as a regular NetworkManager developer (staying an upstream contributor, though). Even before that I tried to put my hands on a number of other projects via bug reports, tests and code. I'm also interested in various network-related standards and especially bugs and bad assumptions in IETF documents.

Wiki resources

Contributions are welcome.

Packages

Maintainer

  • aiccu (IPv6 tunneling client)
  • connman
  • racoon2
  • radvd (taken over from Petr Písař)
  • strongswan

Help with specific features or integration issues welcome.

Co-maintainer

  • bind
  • bind10
  • NetworkManager-ssh
  • rsync
  • squid

Upstream contributions

  • netresolve (author)
  • dnssec-trigger
    • NetworkManager integration scripts (with Tomáš Hozza)
    • systemd integration
  • glibc (name resolution patches)
  • NetworkManager
    • Building on any distribution
    • Virtual device support (bridging/bonding, with others)
    • Valgrind and code coverage support for tests
    • Separate platform interaction module (nm-platform, with Dan Winship)
      • Refactored NetworkManager's bridging/bonding/vlan configuration
      • Refactored NetworkManager's IPv4/IPv6 configuration
    • Userspace IPv6 autoconfiguration (nm-rdisc/libndp, with Jiří Pírko)
      • Getting IPv6 autoconf features on par with IPv4
      • Avoiding loads of kernel IPv6 bugs and design flaws
    • Runtime (non-persistent) configuration support (with Dan Winship and Dan Williams)
    • A lot of bug triaging
  • rpmdevtools

Bug tracking/reporting

  • glibc
    • The getaddrinfo() support is very complicated while not giving correct results in many cases.
  • kernel
    • Network configuration is a real pain.
    • Kernel IPv6 autoconfiguration is only designed for trivial use cases and is very buggy.
  • libnl
    • Most of the advanced stuff is very buggy.
  • avahi
    • Missing for IPv6 link-local addresses.
    • IPv6 disabled by default.
    • Problems with duplicates in discovery.

Daily usage

Distributions

  • Gentoo
  • Fedora/CentOS
  • Debian
  • OpenWRT

Desktop

  • Gnome 3 – Seeking something more mature and stable
  • Gnome Terminal
  • Evolution (for IMAP/SMTP mail) – Seeking something more mature and stable
  • Empathy/Telepathy (for jabber and IRC) – Seeking something more mature and stable
  • Evince
  • Firefox

Development

  • vim
  • gcc
  • make, autotools
  • gdb
  • valgrind

Presentation

  • LaTeX/Beamer

Idea pages

Fedora notes

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

Bump a rawhide package to a newer version

In the package git directory:

VERSION=...

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
fedpkg push
fedpkg build

Requires developmet 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

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

BRANCHES="f20 f19"

# 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