[JIRA] (JENKINS-28870) allow specifying target host when cloning a VM
Title: Message Title pjdarton closed an issue as Won't Do Looks like it wasn't as "in progress" as shown. If I'm wrong, feel free to re-open this and submit a PR that does this. Jenkins / JENKINS-28870 allow specifying target host when cloning a VM Change By: pjdarton Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163328.1434024869000.3636.1565891280351%40Atlassian.JIRA.
[JIRA] (JENKINS-28870) allow specifying target host when cloning a VM
Title: Message Title pjdarton stopped work on JENKINS-28870 Change By: pjdarton Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163328.1434024869000.3633.1565891160239%40Atlassian.JIRA.
[JIRA] (JENKINS-28870) allow specifying target host when cloning a VM
Title: Message Title pjdarton edited a comment on JENKINS-28870 Re: allow specifying target host when cloning a VM I'd also like to see this implemented.While we don't have a "host per team", we have hosts that have finite GPU hardware resources and have found that when vSphere clones a template, it always targets the same host that the template is on, and when that host runs out of hardware resources for the VMs, vSphere continues to try putting the VM on the now-overloaded host and fails.So, as vSphere isn't managing the distribution of VMs across the different hosts, we're going to have to do that ourselves.So, I'd like to see a optional "Host" field in- The "Deploy VM from template" vSphere build step- The "Clone VM from VM or template" vSphere build step- The vSphere cloud-slave template field configuration .Ideally, the UI would allow the user to select a host from a drop-down list, but free-format text would suffice if that proves too tricky.I'd guess that this would require modifying VSphere.java's cloneOrDeployVm method and adding yet another nullable field, and then wiring that through (plus any other helper methods required to support the UI). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28870) allow specifying target host when cloning a VM
Title: Message Title pjdarton commented on JENKINS-28870 Re: allow specifying target host when cloning a VM I'd also like to see this implemented. While we don't have a "host per team", we have hosts that have finite GPU hardware resources and have found that when vSphere clones a template, it always targets the same host that the template is on, and when that host runs out of hardware resources for the VMs, vSphere continues to try putting the VM on the now-overloaded host and fails. So, as vSphere isn't managing the distribution of VMs across the different hosts, we're going to have to do that ourselves. So, I'd like to see a optional "Host" field in The "Deploy VM from template" vSphere build step The "Clone VM from VM or template" vSphere build step The vSphere cloud-slave template field. Ideally, the UI would allow the user to select a host from a drop-down list, but free-format text would suffice if that proves too tricky. I'd guess that this would require modifying VSphere.java's cloneOrDeployVm method and adding yet another nullable field, and then wiring that through (plus any other helper methods required to support the UI). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and
