Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
VILLASweb-backend-go
VILLASweb-backend-go
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1
    • Merge Requests 1
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ACS
    • P
      Public
  • VILLASframework
  • VILLASweb-backend-goVILLASweb-backend-go
  • Issues
  • #31

Closed
Open
Created Nov 21, 2019 by Steffen Vogel@stvogel🎅🏼Owner

Modify infrastructure components via AMQP / VILLAScontroller

Infrastructure components should be created/ updated/ deleted via AMQP and VILLAScontroller messages. The model of infrastructure components requires a new field controller-uuid to save the UUID of the VILLAScontroller that is responsible for the component. The POST, PUT and DELETE endpoints for infrastructure components should either

  • allow for a direct change of the component in the DB if controller-uuid is empty (= the way it works already)
  • or initiate the creation/ update/ deletion of an IC via the VILLAScontroller /AMPQ and NOT perform a direct change of the component in the DB. A VILLAScontroller infrastructure component is expected to send periodic updates of all ICs that it knows so that based on these periodic updates changes to the set of ICs can be made in the DB through the VILLASweb backend (create, update, delete).

This issue requires changes in the VILLAScontroller component.

CC @stvogel

Edited Feb 05, 2021 by Steffen Vogel
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None