Changes between Version 2 and Version 3 of ZapStack

10/28/09 15:34:55 (13 years ago)

added user stories and explanation of zap stack


  • ZapStack

    v2 v3  
     1Zap stands for Zone d'accès publique (public access zone) and the Zap Stack is everything necessary to run a wireless community.  Wifidog is just a piece of this stack.  This page is intended as a reference to help people build their community.  Existing communities share what they use on their systems. 
     3In Quebec, the Alliance des Communautés sans fil du Québec has a project to build a full stack of software tools, ready to deploy by a new community or be used by existing ones.  This page is also a work base for this project, and anyone is welcome to share here.   
     5== Wireless Toronto == 
     7by gabe shawney 
    19I dunno exactly what the Zap Stack is, but I like the idea of us sharing tips on all the stuff around WifiDog which we use to run our networks.  Here's Wireless Toronto's "stack"; I hope it helps to get us started: 
     35== Zap stack user stories == 
     37by Alexis Cornellier and from the page [wiki:TNG] 
     39 - Firmware should update automatically and remotely.  Even if maintenance may be necessary after update 
     40 - Wifidog config should be hosted on the server instead of on the router, so that changes can be done easily 
     41 - It should be possible to show statistics to hotspot owner so he can see the evolution of the service 
     42 - A monitoring system should be available so acces point behavior can be monitored over a long period 
     43 - a QOS system should be put in place 
     44 - Support several modes: Authentification, Agreement et Content+Redirect 
     45 - Development of a geolocation API for session/content/context 
     46 - Integration with open source CMS for portal pages (via plugins): Wordpress is first candidate (Drupal and Pylons are considered) (see [wiki:WifidogAPI] for a discussion on the api) 
     47 - Doc. the stack : Auth Server (hub), Gateway (node) and CMS (api) 
     48 - Exploration of MESH and other hardware and integration with meshing protocols and management. 
     49 - Ability to group nodes in different ways (several nodes per "hotspot", serveral hotspots in a group, overlaping groups, etc.). 
     50 - Federation 
     51 - Ability to use MySQL (database abstraction) 
     52 - Reporting (to hotspot owners)