Project

General

Profile

Actions

Task #1188

closed

Packaging binaries / ports

Added by Alex Afanasyev almost 11 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Category:
Build
Target version:
Start date:
01/31/2014
Due date:
% Done:

100%

Estimated time:

Description

Create packages for NFD and related software for macports, ubuntu, and maybe some other platforms (CentOS?).

The existing definitions for some NDN software for macports is here: https://github.com/named-data/macports

git-based packaging repositories for Ubuntu are combined in https://github.com/cawka/packaging-ndn-platform

Figure out a way to update all the packages to latest (latest stable) versions.

This update should be done by a script.
Currently, all packages needs to be updated manually and this process is slow and error-prone.

Actions #1

Updated by Junxiao Shi almost 11 years ago

  • Description updated (diff)
  • Category changed from Tools to Build
Actions #2

Updated by Junxiao Shi almost 11 years ago

  • Assignee set to Alex Afanasyev
Actions #3

Updated by Alex Afanasyev over 10 years ago

  • % Done changed from 0 to 50
Actions #4

Updated by Alex Afanasyev over 10 years ago

  • Status changed from New to In Progress
Actions #5

Updated by Alex Afanasyev over 10 years ago

  • % Done changed from 50 to 80

I've created a framework that will simplify maintenance of NDN packages: https://github.com/cawka/ppa-packaging

ndn-cxx library is already packages and is in process of being build by PPA build bots. Will continue working on NFD packaging.

Actions #6

Updated by Alex Afanasyev over 10 years ago

  • % Done changed from 80 to 100
Actions #7

Updated by Alex Afanasyev over 10 years ago

  • Status changed from In Progress to Feedback

I have finished binary for Ubuntu's. I have submitted packages for build to PPA and they should be ready some time tomorrow (I hope, for some reason process was slow). It is possible to build packages manually as well and I did basic tests on Ubuntu 12.04 (haven't tested on other Ubuntu's, but it should work...).

Please test. Until packages are building at PPA, you can use the following to build binary packages for ndn-cxx and NFD on ubuntu (process may fail because of broken gpg sign, but I think package will be build before the error):

git clone https://github.com/cawka/ppa-packaging
cd ppa-packaging
make build DISTROS=precise DEBUILD=debuild

.deb files will be in ndn-cxx/work/ and NFD/work/

Actions #8

Updated by Alex Afanasyev over 10 years ago

Hmm. Just checked again (on 14.04, but I think it applies to others as well). nfd and nrd start after installing, but they do not start automatically after the reboot.

I tried a couple of tricks (started on parameter of upstart scripts), but cannot yet figure out the correct setting that makes sure that NFD starts after networking is setup...

Actions #9

Updated by Alex Afanasyev over 10 years ago

Just to follow up. I kind of find a way to "fix" the problem.

The problem is that network interface can come up at random time during or after boot. I remember we talked about this before and decided that we need something to tell NFD when this happens. With upstart it is possible to detect such events, but the only thing I can do right now is to restart nfd/nrd. Would this be a reasonable solution for now? I checked and it works on 14.04, minus the fact that NFD is getting restarted.

Actions #10

Updated by Junxiao Shi over 10 years ago

nfd.upstart has a dependency on network-services. This should be correct.

Actions #11

Updated by Alex Afanasyev over 10 years ago

it does not work. there is no such upstart event as network services.

Actions #12

Updated by Junxiao Shi over 10 years ago

What about

start on started networking
Actions #13

Updated by Alex Afanasyev over 10 years ago

I have tried that. This event allows NFD to start, but it is emitted before any interfaces are actually up. As a result, there are no multicast UDP or ethernet faces created.

The "fix" is based on this http://web.dodds.net/~vorlon/wiki/blog/Network_services_and_Upstart/

Until we have a mechanism to re-scan interfaces, I think the only option is to restart nfd.

Actions #14

Updated by Alex Afanasyev over 10 years ago

PPA packages are ready to use. Junxia, can you check before I send an announcement email to ndn-dev@ mailing list. (PPA instructions: http://named-data.net/doc/NFD/current/FAQ.html#how-to-start-using-ndn-ppa-repository-on-ubuntu-linux)

Update: Just found a small bug with upstart that failed nfd. Will do the fix and will resubmit packages.

Actions #15

Updated by Junxiao Shi over 10 years ago

Verification fails on VMAPI UbuntuTrusty image:

Setting up ndn-cxx (0.1.0-ppa1~trusty) ...
Setting up nfd (0.1.0-ppa1~trusty) ...
OK: certificate with name [/localhost/daemons/nfd/KEY/ksk-1399679566307/ID-CERT/%00%00%01E%E3gB%92] has been successfully installed
OK: certificate with name [/localhost/daemons/nrd/KEY/ksk-1399679566610/ID-CERT/%00%00%01E%E3gD%CD] has been successfully installed
nfd start/running, process 1854
start: Unknown parameter: IFACE
invoke-rc.d: initscript nfd-restart, action "start" failed.
dpkg: error processing package nfd (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.19-0ubuntu6) ...
Processing triggers for ureadahead (0.100.0-16) ...
Errors were encountered while processing:
 nfd
E: Sub-process /usr/bin/dpkg returned an error code (1)
Actions #16

Updated by Alex Afanasyev over 10 years ago

Yep. I got the same error... This problem is because of just one wrong line in /etc/init/nfd-restart.conf (if you delete it, subsequent run of apt-get install will succeed).

I already submitted a fix and now again waiting time.

Just in case. I also have created packages for ndn-tlv-ping and ndn-traffic-generator (for both I didn't do anything for the server part).

Actions #17

Updated by Junxiao Shi over 10 years ago

Verified on VMAPI UbuntuTrusty image.

Actions #18

Updated by Alex Afanasyev over 10 years ago

  • Status changed from Feedback to Closed

I also double checked with my VMware images on 12.04 and 14.04. On both, installation based on the most recent FAQ succeeded, both daemons started and automatically started after the reboot.

Actions

Also available in: Atom PDF