[SERVER-29527] Use infrastructure_provisioning.sh and infrastructure_teardown.sh Created: 09/Jun/17  Updated: 30/Oct/23  Resolved: 09/Jun/17

Status: Closed
Project: Core Server
Component/s: Performance
Affects Version/s: None
Fix Version/s: 3.2.15, 3.4.6, 3.5.9

Type: Improvement Priority: Major - P3
Reporter: Henrik Ingo (Inactive) Assignee: Henrik Ingo (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.4, v3.2
Sprint: Performance Kanban
Participants:

 Description   
  • Use infrastructure_provisioning.sh instead of setup_cluster.sh.
  • The code to save and reuse terraform.tfstate in /data/infrastructure_provisioning/ goes into infrastructure_provisioning.sh. (From there, the good old setup_cluster.sh is called too.)
  • Rename destroy_cluster.sh to infrastructure_teardown.sh
  • In etc/longevity.yml, this introduces the saving of terraform.tfstate under /data/infrastructure_provisioning/. However, we still call infrastructure_teardown.sh at the end. The distro used in mongo-longevity doesn't currently specify a teardown hook, so there's nobody there to actually use the data from /data/infrastructure_provisioning/.


 Comments   
Comment by Githook User [ 21/Jun/17 ]

Author:

{u'username': u'henrikingo', u'name': u'Henrik Ingo', u'email': u'henrik.ingo@mongodb.com'}

Message: SERVER-29527 Use infrastructure_provisioning.sh and infrastructure_teardown.sh

  • Use infrastructure_provisioning.sh instead of setup_cluster.sh.
  • The code to save and reuse terraform.tfstate in
    /data/infrastructure_provisioning/ goes into infrastructure_provisioning.sh.
    (From there, the good old setup_cluster.sh is called too.)
  • Rename destroy_cluster.sh to infrastructure_teardown.sh

(cherry picked from commit 859d07ad4fcaafa4302149707afa17e58975e893)
Branch: v3.4
https://github.com/mongodb/mongo/commit/8a5147e6f0d31702f97903797a4c8e5afcb9e68b

Comment by Githook User [ 21/Jun/17 ]

Author:

{u'username': u'henrikingo', u'name': u'Henrik Ingo', u'email': u'henrik.ingo@mongodb.com'}

Message: SERVER-29527 Use infrastructure_provisioning.sh and infrastructure_teardown.sh

  • Use infrastructure_provisioning.sh instead of setup_cluster.sh.
  • The code to save and reuse terraform.tfstate in
    /data/infrastructure_provisioning/ goes into infrastructure_provisioning.sh.
    (From there, the good old setup_cluster.sh is called too.)
  • Rename destroy_cluster.sh to infrastructure_teardown.sh

(cherry picked from commit 859d07ad4fcaafa4302149707afa17e58975e893)
Branch: v3.2
https://github.com/mongodb/mongo/commit/5eb281442f55c68ee45a16d02204b98639249de3

Comment by Githook User [ 09/Jun/17 ]

Author:

{u'username': u'henrikingo', u'name': u'Henrik Ingo', u'email': u'henrik.ingo@mongodb.com'}

Message: SERVER-29527 Use infrastructure_provisioning.sh and infrastructure_teardown.sh

...in etc/system_perf.yml and etc/longevity.yml:

  • Use infrastructure_provisioning.sh instead of setup_cluster.sh.
  • The code to save and reuse terraform.tfstate in
    /data/infrastructure_provisioning/ goes into infrastructure_provisioning.sh.
    (From there, the good old setup_cluster.sh is called too.)
  • Rename destroy_cluster.sh to infrastructure_teardown.sh
  • In etc/longevity.yml, this introduces the saving of terraform.tfstate under
    /data/infrastructure_provisioning/. However, we still call
    infrastructure_teardown.sh at the end. The distro used in mongo-longevity
    doesn't currently specify a teardown hook, so there's nobody there to actually
    use the data from /data/infrastructure_provisioning/.
    Branch: master
    https://github.com/mongodb/mongo/commit/8d53685476630e6a0db502dab5fe35ad268ca44c
Generated at Thu Feb 08 04:21:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.