Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
slapos slapos
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 122
    • Merge requests 122
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slaposslapos
  • Merge requests
  • !266

Closed
Created Jan 04, 2018 by Tristan Cavelier@tcContributor
  • Report abuse
Report abuse

WIP: stack/erp5: completely remove cloudooo (part 2)

  • Overview 5
  • Commits 2
  • Changes 9

Was Revert by Seb:

Using the public cloudooo for all unit tests makes things unreliable, we have every day many tests failing due to this. It would be required to reapply this change to :

  • make ERP5 more resilient to network failures when there is issues connecting to cloudooo
  • find some automated ways to have a cloudooo per testnode machine, with idea of having possibility to request "where is the nearest service doing that"
  • possibly having a CDN of cloudooo, but this does not prevent having a cloudooo per testnode

This MR provides two commits :

  • Remove Cloudooo from stack/erp5 ;
  • Add parameter to configure Cloudooo URL.

By default, ERP5 will be configured (at instanciation) to use the public cloudooo cluster on https://cloudooo.erp5.net/ (defined on Default System Preference).

But you can choose which URL to use. Here is an example of instanciation parameter : {"cloudooo-url":"https://example.com/"}

caution /!\ as concequences Cloudooo will become orphean if you upgrade your site from a slapos computer or from a webrunner :

  • from a slapos computer, the Cloudooo instance won't be requested anymore by the root instance. So here would be the suggested steps to upgrade :
    • run slapos node software to build the new software ;
    • configure Cloudooo URL on your site to point to an external Cloudooo ;
    • stop Cloudooo service ;
    • request Cloudooo stop (or destroy) ;
    • once software built, run slapos node instance.
  • from webrunner, the differences is that it's not possible to destroy (or stop?) the Cloudooo instance. Here are the suggested steps to upgrade :
    • configure Cloudooo URL on your site to point to an external Cloudooo ;
    • stop Cloudooo service ;
    • then hack to make slapos proxy to think Cloudooo does not exist anymore (stopped or destroyed) ;
    • click Play.
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: noooo
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7