Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Kea
Kea
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 457
    • Issues 457
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 75
    • Merge Requests 75
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • KeaKea
  • Issues
  • #274

Closed
Open
Created Nov 20, 2018 by Thomas Markwalder@tmarkMaintainer0 of 1 task completed0/1 task

Possible improvements to dhcp-queue-control member parsing

The following discussion from !120 (merged) should be addressed:

  • @fdupont started a discussion: (+1 comment)

    This can be postponed but the dhcp-queue-syntax is not defined enough:

    • you should create a context for the two keywords
    • to make it easy to extend just add a STRING COLON value rule (value is the generic JSON value defined at the beginning of dhcpX_parser.yy and is used for instance to define a generic mao, cf map_value rule)

@tmark

The basic rules for dhcp-queue-control are:

  1. Require enable-queue
  2. Ensure that if queue-type is specified, it is a string (it can have any arbitrary value)
  3. beyond those two rules, it can contain arbitrary content

I wasn't sure how to go about accomplishing rule 3, and do not want to use user-context. The parsing that is in place does what is needed but I am open to suggestions.

Edited Dec 06, 2018 by Tomek Mrugalski
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
kea1.7.2
Milestone
kea1.7.2 (Past due)
Assign milestone
Time tracking
None
Due date
None