Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] Do we need to add Caddyfile based NSE? #1134

Open
denis-tingaikin opened this issue May 1, 2021 · 0 comments
Open

[Question] Do we need to add Caddyfile based NSE? #1134

denis-tingaikin opened this issue May 1, 2021 · 0 comments
Labels
question Further information is requested

Comments

@denis-tingaikin
Copy link
Member

Motivation

We could create one cmd-${TODO: consider name}-nse that would parse config based on caddyfile format. The main point is: Have a possible to build NSEs based on SDKs without building new app. That can be used for testing goals (we do not more add new cmd-repo for each new typically NSE) and for users that do not want to code NSE and want just a play with NSM.

Example

To create an copy of current cmd-icmp-responder we could use this config:

my-endpoint {
   point2pointipam
   recvfd
   mechanisms {
      'kernel' {
            kernel
      }
   }
   dnscontext
   sendfd
}

To create a copy of the current cmd-icmp-responder-vpp we could use this config:

my-vpp-endpoint {
   point2pointipam
   mechanisms {
      'memif' {
        sendfd
        up
        connectioncontext
        tag
        memif
      }
   }
}

Let me know if this direction can be interested, then I can provide more technical details on how to achieve this :)

@denis-tingaikin denis-tingaikin changed the title Add Caddyfile based NSE Do we need to add Caddyfile based NSE? May 1, 2021
@denis-tingaikin denis-tingaikin added the question Further information is requested label May 1, 2021
@denis-tingaikin denis-tingaikin changed the title Do we need to add Caddyfile based NSE? [Question] Do we need to add Caddyfile based NSE? May 1, 2021
@denis-tingaikin denis-tingaikin added this to Backlog in Issue/PR tracking via automation May 2, 2021
@denis-tingaikin denis-tingaikin moved this from Backlog to To do in Issue/PR tracking May 2, 2021
@edwarnicke edwarnicke moved this from To do to Open questions in Issue/PR tracking Jul 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
Issue/PR tracking
  
Open questions
Development

No branches or pull requests

1 participant