Difference between revisions of "Avahi Configuration for Pidora"
(→Project Leader) |
(→Project News) |
||
(43 intermediate revisions by the same user not shown) | |||
Line 7: | Line 7: | ||
== Project Leader == | == Project Leader == | ||
− | + | [[User:skullhat|Taylor Barras]] [http://tecknologikk.blogspot.ca/ (tsbarras)] | |
− | |||
− | [[Taylor Barras]] (tsbarras) | ||
== Project Contributor(s) == | == Project Contributor(s) == | ||
Line 16: | Line 14: | ||
NOTE: only the Project Leader should add names here. You should not add your own name to the Contributor list. --> | NOTE: only the Project Leader should add names here. You should not add your own name to the Contributor list. --> | ||
+ | |||
+ | None | ||
== Project Details == | == Project Details == | ||
<!-- Provides more depth than the Project Description. This is the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into multiple pages and linking to them. --> | <!-- Provides more depth than the Project Description. This is the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into multiple pages and linking to them. --> | ||
+ | |||
+ | Since the Raspberry Pi utlizies the same NIC throughout its two models, I predict that getting avahi to work should only be a matter of customizing the configuration files to fit the hardware on install (unless this is done automatically, like while running a configuration). | ||
+ | |||
+ | My main resource will be the [http://avahi.org/wiki/AboutAvahi Avahi website] and the references that are linked to from that page. | ||
+ | |||
+ | [http://www.dns-sd.org/ DNS Service Discovery] | ||
+ | |||
+ | [http://www.multicastdns.org/ Multicast DNS] | ||
+ | |||
+ | [http://www.freedesktop.org/wiki/Software/dbus/ D-Bus] | ||
+ | |||
+ | [http://en.wikipedia.org/wiki/Multicast_DNS General Info on MDNS] | ||
+ | |||
+ | I intend to use as pristine sources as I can get, although the first few hours of my project will be devoted to familiarizing myself with the Pi. | ||
+ | |||
+ | I will also probably have to install some form of Avahi on a PC at home to test operation. | ||
+ | |||
+ | [http://www.dns-sd.org/ServiceTypes.html Information on MDNS service types] | ||
== Project Plan == | == Project Plan == | ||
Line 25: | Line 43: | ||
=== Tracking === | === Tracking === | ||
<!-- Describe the tracking mechanisms you are using for your project (bugzilla, trac, github, ...) --> | <!-- Describe the tracking mechanisms you are using for your project (bugzilla, trac, github, ...) --> | ||
+ | For tracking I plan to use github. My github is located here. | ||
=== Key contacts === | === Key contacts === | ||
<!-- Add links to any mentors or key participants in the community. --> | <!-- Add links to any mentors or key participants in the community. --> | ||
+ | None yet | ||
=== Goals by Release === | === Goals by Release === | ||
Line 34: | Line 54: | ||
<!-- Note: Each student must have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. --> | <!-- Note: Each student must have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. --> | ||
* 0.1 | * 0.1 | ||
+ | |||
+ | • Scripts, commands, and files needed for auto configuration created/collected | ||
+ | |||
+ | • Creation of raspberry-pi-avahi-auto-config package in process | ||
+ | |||
* 0.2 | * 0.2 | ||
+ | |||
+ | • Automatic configuration packaged | ||
+ | |||
+ | • Successful build on ARMv6 | ||
+ | |||
* 0.3 | * 0.3 | ||
+ | |||
+ | • RPM package in Pidora repo/distribution | ||
== Communication == | == Communication == | ||
Line 41: | Line 73: | ||
=== Mailing Lists === | === Mailing Lists === | ||
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org --> | <!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org --> | ||
+ | Unsubcribed because Seneca outlook would not sort these email into a separate folder. | ||
− | === | + | === Upstream Wiki and Web === |
<!-- Links to upstream wiki/web pages --> | <!-- Links to upstream wiki/web pages --> | ||
=== Links/Bugs/Tracking === | === Links/Bugs/Tracking === | ||
<!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) --> | <!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) --> | ||
+ | [http://www.avahi.org/wiki/TracGuide Avahi Bug Tracking System] | ||
=== Source Code Control === | === Source Code Control === | ||
<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories --> | <!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories --> | ||
+ | To be added soon. | ||
=== Blogs === | === Blogs === | ||
<!-- Links to the blogs of people involved, both inside and outside Seneca --> | <!-- Links to the blogs of people involved, both inside and outside Seneca --> | ||
+ | [http://tecknologikk.blogspot.ca/ Taylor's Blog] | ||
=== Non-Seneca Participants === | === Non-Seneca Participants === | ||
Line 59: | Line 95: | ||
=== Planets === | === Planets === | ||
<!-- Links to any planets related to this project --> | <!-- Links to any planets related to this project --> | ||
+ | [http://zenit.senecac.on.ca/~chris.tyler/planet/ Planet CDOT] | ||
== Project News == | == Project News == | ||
− | <!-- This is where a permanent record of your releases and updates will go. In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc. --> | + | <!-- This is where a permanent record of your releases and updates will go. In these you should discuss the status or your work, your interactions with other members of the |
+ | community (e.g., Seneca and Mozilla), problems you have encountered, etc. --> | ||
+ | '''Jan 2nd, 2014''' | ||
+ | |||
+ | • [http://tecknologikk.blogspot.ca/ This project has changed into the avahi-advertise project and will be updated on my blog from now on.] | ||
+ | |||
+ | '''Dec 9th, 2013''' | ||
+ | |||
+ | • [http://tecknologikk.blogspot.com/2013/12/fixing-avahi-advertise-in-preparation.html Fixed bugs in avahi-advertise] | ||
+ | |||
+ | • [http://tecknologikk.blogspot.com/2013/12/packaging-avahi-advertise-03-release.html Packaged avahi-advertise for 0.3 release] | ||
+ | |||
+ | '''Dec 2nd, 2013''' | ||
+ | |||
+ | • yshin8 and I are in discussion on Avahi in Pidora 19 kickstart file | ||
+ | |||
+ | • Specfile work halted | ||
+ | |||
+ | • Working on avahi-config (avahi-advertise?) command which will be install with my package and change txt records or create new service files | ||
+ | |||
+ | • [http://tecknologikk.blogspot.com/2013/12/02-release-avahi-advertise-command.html 0.2 Release] | ||
+ | |||
+ | '''Nov 28th 2013''' | ||
+ | |||
+ | • Package spec file started | ||
+ | |||
+ | • yshin8 contacted about changing how avahi service is installed in kickstart file | ||
+ | |||
+ | '''Nov 22nd 2013''' | ||
+ | |||
+ | • [http://tecknologikk.blogspot.com/2013/11/avahi-auto-configuration-01-release.html 0.1 Released] | ||
+ | |||
+ | '''Nov 20th 2013''' | ||
+ | |||
+ | • Finished the majority of testing and scripts/commands required for 0.1 | ||
+ | |||
+ | • Preparing 0.1 presentation | ||
+ | |||
+ | • Will demonstrate avahi and nss-mdns resolution | ||
+ | |||
+ | • Will demonstrate avahi-tools and how it can automatically ssh | ||
+ | |||
+ | • Will explain the function of my config package (install nss-mdns, avahi-tools, iptables, TXT records) | ||
+ | |||
+ | '''Nov 16th, 2013''' | ||
+ | |||
+ | • Changed goals due to Avahi 0.6.31 already being repackaged in the Pidora 19 Alpha. | ||
+ | |||
+ | • [http://tecknologikk.blogspot.com/2013/11/what-to-put-in-avahi-configuration.html Posted plans for configuration package] | ||
+ | |||
+ | '''Nov 7th, 2013''' | ||
+ | |||
+ | • Fedora 19 upstream nss-mdns package will be packaged for pidora. | ||
+ | |||
+ | • This package is required for hostname resolution using multicast DNS | ||
+ | |||
+ | • My Avahi config package will require nss-mdns | ||
+ | |||
+ | |||
+ | '''Oct 29th, 2013''' | ||
+ | |||
+ | • nss-dns will most likely be part of my configuration package | ||
+ | |||
+ | [[User:Skullhat|Skullhat]] 13:05, 29 October 2013 (EDT) | ||
+ | |||
+ | '''Oct 24th, 2013''' | ||
+ | |||
+ | • Avahi 0.6.31 packaged and appears to be working | ||
+ | |||
+ | • Testing package optimization coming next week | ||
+ | |||
+ | • Blog posts on my Pi setup and packaging of Avahi 0.6.31 are written and are being polished | ||
+ | |||
+ | [[User:Skullhat|Skullhat]] 13:02, 29 October 2013 (EDT) | ||
+ | |||
+ | '''Oct 20th, 2013''' | ||
+ | |||
+ | • I have purchased and setup my Pi. It is running Pidora from NOOBS. [Here is the blog post] on my setup experience. | ||
+ | |||
+ | • Testing of Avahi and nss-mdns has begun. | ||
+ | |||
+ | • I will install, test, and package with the newest version of [http://avahi.org/download/avahi-0.6.31.tar.gz avahi (0.6.31)] as part of this project. | ||
+ | |||
+ | [[User:Skullhat|Skullhat]] 13:11, 20 October 2013 (EDT) | ||
+ | |||
+ | '''Oct 9th, 2013''' | ||
+ | |||
+ | • I have purchased some equipment for my Raspberry Pi and intend to buy the unit this week. | ||
+ | |||
+ | [[User:Skullhat|Skullhat]] 13:11, 20 October 2013 (EDT) | ||
+ | |||
+ | '''Oct 2nd, 2013''' | ||
+ | |||
+ | • I will be purchasing a Raspberry Pi and the equipment required to begin my project within the coming week or two. | ||
+ | |||
+ | [[User:Skullhat|Skullhat]] 13:11, 20 October 2013 (EDT) |
Latest revision as of 12:40, 2 January 2014
Contents
Avahi Configuration for Pidora
Project Description
Avahi (zeroconf) enables discovery of computers without DNS or IP numbers. This project involves configuring Avahi for use on the Raspberry Pi, so that other computers can connect to it by name without DNS support. This configuration must then be packaged in such a way that it can be included in the Pidora composes without causing conflicts.
Project Leader
Project Contributor(s)
None
Project Details
Since the Raspberry Pi utlizies the same NIC throughout its two models, I predict that getting avahi to work should only be a matter of customizing the configuration files to fit the hardware on install (unless this is done automatically, like while running a configuration).
My main resource will be the Avahi website and the references that are linked to from that page.
I intend to use as pristine sources as I can get, although the first few hours of my project will be devoted to familiarizing myself with the Pi.
I will also probably have to install some form of Avahi on a PC at home to test operation.
Information on MDNS service types
Project Plan
Tracking
For tracking I plan to use github. My github is located here.
Key contacts
None yet
Goals by Release
Goals for each release and plans for reaching those goals:
- 0.1
• Scripts, commands, and files needed for auto configuration created/collected
• Creation of raspberry-pi-avahi-auto-config package in process
- 0.2
• Automatic configuration packaged
• Successful build on ARMv6
- 0.3
• RPM package in Pidora repo/distribution
Communication
Mailing Lists
Unsubcribed because Seneca outlook would not sort these email into a separate folder.
Upstream Wiki and Web
Links/Bugs/Tracking
Source Code Control
To be added soon.
Blogs
Non-Seneca Participants
Planets
Project News
Jan 2nd, 2014
Dec 9th, 2013
• Fixed bugs in avahi-advertise
• Packaged avahi-advertise for 0.3 release
Dec 2nd, 2013
• yshin8 and I are in discussion on Avahi in Pidora 19 kickstart file
• Specfile work halted
• Working on avahi-config (avahi-advertise?) command which will be install with my package and change txt records or create new service files
Nov 28th 2013
• Package spec file started
• yshin8 contacted about changing how avahi service is installed in kickstart file
Nov 22nd 2013
Nov 20th 2013
• Finished the majority of testing and scripts/commands required for 0.1
• Preparing 0.1 presentation
• Will demonstrate avahi and nss-mdns resolution
• Will demonstrate avahi-tools and how it can automatically ssh
• Will explain the function of my config package (install nss-mdns, avahi-tools, iptables, TXT records)
Nov 16th, 2013
• Changed goals due to Avahi 0.6.31 already being repackaged in the Pidora 19 Alpha.
• Posted plans for configuration package
Nov 7th, 2013
• Fedora 19 upstream nss-mdns package will be packaged for pidora.
• This package is required for hostname resolution using multicast DNS
• My Avahi config package will require nss-mdns
Oct 29th, 2013
• nss-dns will most likely be part of my configuration package
Skullhat 13:05, 29 October 2013 (EDT)
Oct 24th, 2013
• Avahi 0.6.31 packaged and appears to be working
• Testing package optimization coming next week
• Blog posts on my Pi setup and packaging of Avahi 0.6.31 are written and are being polished
Skullhat 13:02, 29 October 2013 (EDT)
Oct 20th, 2013
• I have purchased and setup my Pi. It is running Pidora from NOOBS. [Here is the blog post] on my setup experience.
• Testing of Avahi and nss-mdns has begun.
• I will install, test, and package with the newest version of avahi (0.6.31) as part of this project.
Skullhat 13:11, 20 October 2013 (EDT)
Oct 9th, 2013
• I have purchased some equipment for my Raspberry Pi and intend to buy the unit this week.
Skullhat 13:11, 20 October 2013 (EDT)
Oct 2nd, 2013
• I will be purchasing a Raspberry Pi and the equipment required to begin my project within the coming week or two.
Skullhat 13:11, 20 October 2013 (EDT)