Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-5731

vsphere : Add ability to define what network the created vm will be attached to

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: vsphere
    • Labels:
      None
    • Template:
    • QA Risk Assessment:
      Needs Assessment

      Description

      Basic Info
      1.2.2:
      2016.5:
      All OSes:

      Describe your issue in as much detail as possible...

      Desired Behavior:
      Assign the VM to the desired network as part of the Puppet code. This is not OS-level configuration of the interface, but rather VM-level. Each VM can be assigned to a 'VM Network' defined at the vSwitch. We have 50-ish of these so assigning them in the template is not workable.

      Actual Behavior:
      When creating a VM from a template the VM is assigned to whatever network is defined in the template.

      Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            agrewel Aaron Grewell
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Zendesk Support