Uploaded image for project: 'Atlassian Cloud'
  1. Atlassian Cloud
  2. CLOUD-3293

Capability to reuse the existing EBS volume by elastic bamboo instead on creating a fresh volume everytime from the snapshot

    XMLWordPrintable

Details

    • 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.

    Description

      We are using a single agent elastic bamboo instance with Auto-mount EBS volume everytime option. But, as opposed to the description, it doesn't mounts the EBS volume (the one mounted last time) and creates a fresh EBS from the snapshot.

      This makes sense for those using many agents configuration, but, for several developers with a single agent license, the same EBS volume must be used instead on creating a fresh one every time.

      I mean that there should be an option for this at least. Currently, I assume the process is as follows:

      1) Create a EBS volume from the snapshot (snapshotId is provided in configuration) and get its volumeId.
      2) Mount the volumeId to the new instance.

      I propose that it should be modified as:
      1) Ask for a snapshotId and a EBS volumeId(s) in elastic bamboo instance configuration and keep those in record.
      2) Launch a new instance and check if a volumeId provided is valid and not mounted already, and if its free, mount it to the new instance and if none of the volumeId(s) is valid and free, create a new volume from the snapshotId, get newly created volumeId and mount it.
      3) Optional: Update the newly created volumeId in record (array) for reuse.

      I think the option to reuse the existing EBS volume (the same which was used last time) may be provided easily in the elastic bamboo, at least for those using a single instance and this will be of great help for many customers.

      Thanks & Regards

      Attachments

        Activity

          People

            Unassigned Unassigned
            8216b246-c9e6-42be-83e2-6afede32352f Deleted Account (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: