Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • ansible-collection-vdc ansible-collection-vdc
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 63
    • Issues 63
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • privazioprivazio
  • ansible-collection-vdcansible-collection-vdc
  • Issues
  • #73
Closed
Open
Issue created Dec 05, 2020 by Rafael del Valle@rafaelOwner

VRACK Mesh: networkd attachment

ACS manages bridges and interfaces dynamically, much more than Opennebula, the previous cloud stack used.

In order to provide "external connectivity" from the Mesh (normally to connect public networks) the mesh should listen to the network and then attach the external interface to the bridges created by ACS, wihtout any other interference.

Assignee
Assign to
Time tracking