Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-3344

Automatically control starting and stopping of Elastic Agents based on load

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • 2.6
    • Elastic Bamboo
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

          [BAM-3344] Automatically control starting and stopping of Elastic Agents based on load

          AntonA added a comment -

          Hi Stuart,

          BAM-5376 has been made public.

          Cheers,
          Anton

          AntonA added a comment - Hi Stuart, BAM-5376 has been made public. Cheers, Anton

          So the issue this is a duplicate of is private, any chance we can know what's going on?

          Stuart Gilberd added a comment - So the issue this is a duplicate of is private, any chance we can know what's going on?

          Anatoli added a comment -

          Resolving as a duplicate of BAM-5376

          Anatoli added a comment - Resolving as a duplicate of BAM-5376

          Oh! That's a great news. Thanks for info! I'll look into it then.

          Cheers,
          Krystian

          Krystian Nowak added a comment - Oh! That's a great news. Thanks for info! I'll look into it then. Cheers, Krystian

          MarkC added a comment -

          Krystian,

          We're working at supplementing the new REST endpoints for 2.3.1. I'll see if the queues information can be made available through the REST API.

          As far as plugin points goes, there is a CustomPreBuildQueuedAction (see http://confluence.atlassian.com/display/BAMBOO/Pre+Build+Queued+Action) that you can hook into. We have a plugin for LabManger for example, that starts a VM based on the Build that is being triggerred.

          Cheers,

          Mark C

          MarkC added a comment - Krystian, We're working at supplementing the new REST endpoints for 2.3.1. I'll see if the queues information can be made available through the REST API. As far as plugin points goes, there is a CustomPreBuildQueuedAction (see http://confluence.atlassian.com/display/BAMBOO/Pre+Build+Queued+Action ) that you can hook into. We have a plugin for LabManger for example, that starts a VM based on the Build that is being triggerred. Cheers, Mark C

          So the only way to do it is outside the core - either by plugin (I'm not sure if the necessary hooks are available) or remote API (but I couldn't find any method to query the current queue length)?

          Cheers,
          Krystian

          Krystian Nowak added a comment - So the only way to do it is outside the core - either by plugin (I'm not sure if the necessary hooks are available) or remote API (but I couldn't find any method to query the current queue length)? Cheers, Krystian

          edwin added a comment -

          Hi guys,

          After using EC2 internally here at Atlassian, what we have found was that to be able to scale up and down of agents purely based on load may be a little cost ineffective and a little too un-predictable.

          What we have found that worked better for us was a schedule/time based scaling up and down. We have implemented this in BAM-4326.

          Cheers,
          Edwin

          edwin added a comment - Hi guys, After using EC2 internally here at Atlassian, what we have found was that to be able to scale up and down of agents purely based on load may be a little cost ineffective and a little too un-predictable. What we have found that worked better for us was a schedule/time based scaling up and down. We have implemented this in BAM-4326 . Cheers, Edwin

            akazatchkov Anatoli
            edwin@atlassian.com edwin
            Votes:
            11 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: