Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
cameo
cameo
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 42
    • Issues 42
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Cameo
  • cameocameo
  • Issues
  • #16

Closed
Open
Opened Apr 10, 2017 by yannick legoc@legoc
  • Report abuse
  • New issue
Report abuse New issue

Deployment of a new version of a managed application

  • Solution
    • new set of states for an Application that are independent from the current states: UP_TO_DATE, WAITING_FOR_UPDATE (version is waiting to be installed), UPDATING, ERROR (blocking the application?). We call it the update state.
    • push a new version on a Cameo server. It is a request when processed:
      • application becomes WAITING_FOR_UPDATE immediately
      • the new version data is saved locally and replaces the previous new version if it is not installed yet
      • the server installs it when the application is stopped (option: stop the application immediately)
      • the application has the state UPDATING (new state in the current list)
      • the config file is modified after each installation (to memorize the version number)
        • the server shall not be brutally stopped
        • enable to stop nicely the server
      • default installation: copy file (jar) to install_directory, untar a tar to install_directory
      • or an installation script
      • command line: cmo app1 update app1.jar 1.2.3
    • monitoring notifications:
      • the Cameo server publishes a new status when the version is installed
      • status VERSION value
      • version in the application info
    • class This can access version
Edited Oct 01, 2020 by yannick legoc
To upload designs, you'll need to enable LFS. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
suggestion
Assign labels
  • View project labels
Reference: cameo/cameo#16