• Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • labmanager-plugin
    • None

      This Plugin is realy great but two things we are missing.

      Create and Restore Snapshot:
      If you build a software a do tests on a virtual machine which is created and configured for special test scenario it would be ver useful to store and restore this state "before test"
      Every test will change the machines setup an therefore potentialy danger the result of the following turn.
      If you could save the state before euting the deploy-test turn, than run it and the restore to begin, the machine state wouldn't change.

      I think the only vmware feature that will do it is snapshots. In our experience it it not good to have many snapshots, so if a snaphot is created there shall be a way to remove another (or even all) or "overwrite" one, not to get performance issues.

      System lines:
      A distributed tier architecture has more than one machine the application is installed and tested on (web server, application sever, database, que server ..) . So it is nececarry to create and restore not only one machine per build, but all of them as a bundle.

          [JENKINS-10165] Create and Restore Snapshot and system lines

          Tom Rini added a comment -

          To be clear, you want more than the current "Restore to a snapshot" behavior when the system is taken down?

          Tom Rini added a comment - To be clear, you want more than the current "Restore to a snapshot" behavior when the system is taken down?

          cforce added a comment -

          Umm sorry, if that is already possible "restore to a named point when system is taken down" that is what we need. Improvement would be to be able optional create a named snashot right before the system is used/taken up in build, just to be sure that changes on the system won't be lost.
          Furthermore not only one vm shall be controlled this way but many (tabase, middle tier, web server ..)

          cforce added a comment - Umm sorry, if that is already possible "restore to a named point when system is taken down" that is what we need. Improvement would be to be able optional create a named snashot right before the system is used/taken up in build, just to be sure that changes on the system won't be lost. Furthermore not only one vm shall be controlled this way but many (tabase, middle tier, web server ..)

          Tom Rini added a comment -

          So, at least in what I have access to I can only see how to make single snapshots of a given VM and the SOAP API only supports restoring to that snapshot, not a specific named one. But the "Shutdown and Revert" behavior sounds like it should give you what you want. ie define a "cloud" which in turn points at a configuration of 4 VMs (web server, application server, db server, que server) each of which has a snapshot taken at the point where you want to start things up at. Then add them as slaves and set the idle behavior to Shutdown and Revert.

          Tom Rini added a comment - So, at least in what I have access to I can only see how to make single snapshots of a given VM and the SOAP API only supports restoring to that snapshot, not a specific named one. But the "Shutdown and Revert" behavior sounds like it should give you what you want. ie define a "cloud" which in turn points at a configuration of 4 VMs (web server, application server, db server, que server) each of which has a snapshot taken at the point where you want to start things up at. Then add them as slaves and set the idle behavior to Shutdown and Revert.

            tomrini Tom Rini
            cforce cforce
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: