-
Suggestion
-
Resolution: Duplicate
-
None
-
None
-
Jira Studio Hosted (https://componence2.jira.com)
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.
This issue is same as https://studio.atlassian.com/browse/JST-3293 and the one that is irrelevant may be closed.
Thanks & Regards
- duplicates
-
BAM-5930 Option to specify ebs volume instead of snapshot - keep volume alive after elastic instance shutdown
- Closed
[BAM-7319] Capability to reuse the existing EBS volume by elastic bamboo instead on creating a fresh volume everytime from the snapshot
Workflow | Original: JAC Suggestion Workflow [ 3018310 ] | New: JAC Suggestion Workflow 3 [ 3603241 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2699253 ] | New: JAC Suggestion Workflow [ 3018310 ] |
Backlog Order (Obsolete) | Original: 21800000000 | |
Issue Type | Original: New Feature [ 2 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1418344 ] | New: Confluence Workflow - Public Facing v4 [ 2699253 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 609740 ] | New: Bamboo Workflow 2016 v1 [ 1418344 ] |
Workflow | Original: Bamboo Workflow 2014 [ 603501 ] | New: Bamboo Workflow 2014 v2 [ 609740 ] |
Workflow | Original: Bamboo Workflow 2010 [ 269032 ] | New: Bamboo Workflow 2014 [ 603501 ] |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Resolving as a duplicate. See
BAM-5930.