8000 colte architecture: policy actuator · Issue #26 · uw-ictd/colte · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
colte architecture: policy actuator #26
Open
@spencersevilla

Description

@spencersevilla

haulage is currently in charge of sensing user input (i.e. monitoring network usage) as well as actuating on this input (i.e. issuing iptables commands). This is a problematic architecture for us as we add more billing features, including but not limited to:

  • subscription model
  • ability to "cut off" a user via the admin portal, or otherwise override haulage's rules
  • ability for admin portal to see exactly what is going on (right now it just queries database)

I believe the right approach is to split haulage into (1) the monitoring software that writes updates to the database and (2) an actuator that takes all sorts of input (from haulage as well as the database rules, etc.) and is in charge of enacting all changes into the system. This gives us all sorts of tools/solutions for network management. We could grow/fold this into a PCRF or not, depends on what else we want to do with it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    1.0 BlockerenhancementNew feature or requesthelp wantedExtra attention is neededmaturityIssues that will need to be addressed before wide deployment

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0