Opened 9 years ago

Closed 8 years ago

#768 closed task (invalid)

ACLS: configuration

Reported by: stephen Owned by:
Priority: medium Milestone:
Component: Unclassified Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket: ACL
Estimated Difficulty: 0.0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


Dependent on #767, this task is to implement the ACL syntax so that users of BIND-10 are able to enter ACLs into the configuration system and to associate them with the relevant entities.


Change History (7)

comment:1 Changed 9 years ago by vorner

  • Defect Severity set to N/A
  • Feature Depending on Ticket set to ACL
  • Milestone changed from Year 3 Task Backlog to Next-Sprint-Proposed
  • Sub-Project set to DNS

I created bunch of smaller items (which depend on each other). This will be partially implemented by #978, #980 and #982.

When the python wrapper is finished (#983), this will consist of writing a configuration plugin and spec file for ACL configuration section, so it is checked whenever user updates it.

comment:2 Changed 9 years ago by vorner

Note that there might be small catch about the spec, as we need a way to tell „anything can be here, I'll check it manually“, the ACLs have quite free form. This isn't possible now in the spec file, but it might turn out if the data aren't checked explicitly against the spec file, nobody does that and an almost-empty spec file would work.

comment:3 Changed 9 years ago by stephen

  • Milestone changed from Next-Sprint-Proposed to Sprint-20110614

comment:4 Changed 9 years ago by stephen

  • Estimated Difficulty changed from 0.0 to 7

comment:5 Changed 8 years ago by vorner

  • Milestone changed from Sprint-20110628 to Next-Sprint-Proposed

This ticket is missing its dependency in the sprint. After talking about if we want to include the dependency or postpone this one, we decided this is not that urgent and the sprint is large enough already, so I'm putting it to the proposed ones for the next sprint (together with the dependency).

comment:6 Changed 8 years ago by stephen

  • Milestone changed from Next-Sprint-Proposed to Sprint-20110712

comment:7 Changed 8 years ago by stephen

  • Estimated Difficulty changed from 7.0 to 0
  • Milestone Sprint-20110712 deleted
  • Resolution set to invalid
  • Status changed from new to closed

At the sprint planning meeting of 2011-07-12, it was agreed that this ticket is no longer descriptive of what is required and that it should be withdrawn.

Note: See TracTickets for help on using tickets.