-
Notifications
You must be signed in to change notification settings - Fork 299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
debian/ubuntu package files #121
Conversation
@vladfedin, take a look pls. |
May be it's also possible / desirable to somehow install auto-testing script? |
At the moment selftests code are mixed with library code. I have create a new issue about - #124 |
OK, thanks. @altexy, can you please verify if the package installs everything what we need? |
The simplest way is to run any test which does not require test data, rate_limiter for example: End of rate_limiter selftest FYI: if not ok then
print("selftest failed")
os.exit(1)
end
print("selftest passed") |
@vnaum, is it enough info to proceed? |
Link to binary packages (snabb/nova/qemu/libvirt/neutron) I've built: I've built from my source repos: |
Do end users have any need for this test data? If it's just for development purposes - let it stay in source repo, no need to clutter binary package. If it can be handy for users as an example of how snabbswitch can work or as a template for custom scripts/scenarios, If test data is essential for snabbswitch (snabb is useless without it, and everybody will need it) - /usr/lib/snabbswich is a correct place.
Wait, there is some installation script / routine? |
I think we should have as few files as we possibly can in the package for snabbswitch. The snabbswitch binary, a manpage, maybe an example config... can we get away with so little? |
(OK, maybe we'll want an init.d script, but we don't have that yet...) |
From my point of view we totally can. |
That sounds good :) |
See also: #93 |
|
||
Package: snabbswitch | ||
Architecture: any | ||
Depends: ${shlibs:Depends}, ${misc:Depends}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
snabbswitch package can probably have a short (even empty?) dependency list.
Perhaps we will want to make a snabbswitch-nfv meta-package that installs the base snabbswitch + all of the virtualisation stuff, but I think we can take that later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, It's never empty — you depend on libc at least, and probably need some minimum kernel version, but the idea behind this was "user installs snabbswitch and gets every requirement pulled". As you suggest, meta-package can be done that depends in both snabb and "everything".
This one is now obsolete, see #131 |
JFYI Here is a mailing list thread with somebody else trying to build a patched version of Neutron for an Ubuntu PPA: http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg20902.html |
(Obsoleted by #131) |
Refactor header handling, make outgoing ICMP work
Please check list of files to install: I have no idea what has to be installed, and there was no 'install' rule in Makefile, so I added single file install into /usr/bin/snabbsandwich
If there are more files (config file, man page, scripts, crontab entries), or if /usr/sbin fits better for snabbsandwich (like, if this root-only program) - let me know.
I added some description/URLS in control file, rest of package is fresh out of dh_make — lots of example stuff and such.