Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
slapos
slapos
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Merge Requests 73
    • Merge Requests 73
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Jobs
  • Commits
  • nexedi
  • slaposslapos
  • Merge Requests
  • !1259

Merged
Opened Sep 19, 2022 by Xavier Thompson@xavier_thompson
  • Report abuse
Report abuse

software/theia: Disable frontend forwarding from resilient clone

Until now, the resilient clone (theia1) also forwarded frontend requests from cloned embedded instances (e.g. ERP5) to the external master. This mirrored the request already sent from the main embedded instance in theia0. But since theia0 and theia1 belong to the same instance tree, from the point of view of the external master those two requests are the same.

So every time the backup instance was processed (once a day), there was a tug-of-war on this shared frontend, were theia1 would briefly overwrite its parameters to redirect to the cloned embedded instance, before thei0 would reprocess its embedded instance and tug the shared frontend back to the original embedded instance.

To fix this, frontend forwarding is now disabled for theia1. When the cloned embedded instance requests a frontend, the local proxy will now fall back to the harcoded default behavior of faking the frontend allocation by returning the original url. This allows the cloned embedded instance to instantiate normally while keeping it fully isolated.

Edited Sep 21, 2022 by Xavier Thompson
  • Discussion 3
  • Commits 2
  • Pipelines 5
  • Changes 5
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
0
Labels
None
Assign labels
  • View project labels
Reference: nexedi/slapos!1259

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7