Uploaded image for project: 'VCL'
  1. VCL
  2. VCL-967

Libvirt provisioning does not allow virtual network name to be specified in the VM host profile

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.5
    • vcld (backend)
    • None

    Description

      The libvirt.pm provisioning module currently requires that the VM profile VM Network 0 and VM Network 1 settings be set to the name of physical interfaces on the VM host (eth0, br1, etc).

      Under libvirt-managed hypervisors such as KVM, you can define virtual networks and give them names such as private or public.

      Currently, reservations will fail if you were to specify private in the VM profile. This isn't intuitive and the behavior differs from how VMware VM hosts are configured. The only way a VCL administrator could figure out the problem would be to dig through and interpret vcld.log.

      The libvirt.pm code should be extended to allow either a physical interface (br0) or virtual network name (private) to be specified in the VM profile.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            arkurth Andrew Kurth
            arkurth Andrew Kurth
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment