search for: perset

...e is what I noticed: > > I see that in the yaml file we provide short-id as: > > os: > osinfo: 'rhel7.2' > > whereas kubevirt expects it in metadata: > > metadata: > labels: > kubevirt.io/os: win10 > > For windows vms we need to create perset like this one [1]. We can add > separator > > --- > > between the objects. I'm a bit confused about the second part. Is the VirtualMachinePreset file a separate file from the .yaml file that we're creating already or is it a replacement for it? We can create as many file...

Fixes some of the more egregious problems with v1, and also applies properly to the head of git without needing any other patches. Rich.

Richard, Great progress. I really like it!!! Here is what I noticed: I see that in the yaml file we provide short-id as: os: osinfo: 'rhel7.2' whereas kubevirt expects it in metadata: metadata: labels: kubevirt.io/os: win10 For windows vms we need to create perset like this one [1]. We can add separator --- between the objects. Thanks, Piotr [1] https://github.com/kubevirt/kubevirt/blob/master/manifests/release/demo-content.yaml.in On Tue, Mar 27, 2018 at 6:31 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > Fixes some of the more egregio...