[ovirt-users] API -- Do I need to use templates? Can I change network for the nic?

[Morgan McLean]

Hi,

I think template configuration is definitely not an option for networks
with a large amount of segments.

I haven't played with VNIC profiles, but I will tomorrow. I didn't remember
seeing any documentation on changing that with a PUT, but I'll look into
it. Will report back shortly, thank you!

Morgan

On Thursday, October 2, 2014, Lior Vernia <lvernia at redhat.com> wrote:

>
>
> On 02/10/14 10:22, Tomas Jelinek wrote:
> >
> >
> > ----- Original Message -----
> >> From: "Itamar Heim" <iheim at redhat.com <javascript:;>>
> >> To: "Lior Vernia" <lvernia at redhat.com <javascript:;>>, "Morgan McLean"
> <wrx230 at gmail.com <javascript:;>>
> >> Cc: users at ovirt.org <javascript:;>
> >> Sent: Wednesday, October 1, 2014 12:38:13 PM
> >> Subject: Re: [ovirt-users] API -- Do I need to use templates? Can I
> change network for the nic?
> >>
> >> On 10/01/2014 10:54 AM, Lior Vernia wrote:
> >>> Hi Morgan,
> >>>
> >>> I'm not sure if you want all VMs to use the same network or not. If you
> >>> do, the best way would be to create a template with one interface, and
> >>> the relevant network (profile) attached.
> >>>
> >>> If you want certain VMs to be connected to other networks, once you
> >>> create the VM you can send a PUT request on /api/vms/{id}/nics/{id}/
> and
> >>> update it with the relevant network (profile).
> >>
> >> I thought we allow to change the logical network at vm creation since
> >> instance types were added?
> >
> > Not on API level. In webadmin/userportal you can do it in one go, but
> that anyway triggers two different actions.
> >
> > But now as I have tried it, if I create a VM from template or instance
> type (using API), the NICs are completely ignored.
> > It does not matter if template or instance type since instance types
> just inherit the behavior of the templates so are inheriting also the
> bug/missing logic etc.
> >
> > For me it seems like a bug but not sure. Is there a reason why the NICs
> are ignored when the VM is created from a template with NICs using API?
> > What I think is that since the NIC can have different profiles assigned
> and this can be edited on the FE, this functionality of sending different
> profile for the specific NIC is just not implemented on API level, so the
> API just
> > completely ignores the NICs.
> > What do you think Lior?
> >
> >
>
> If I correctly understand what you mean, then that is the current
> "intended" behavior - supplying NICs as part of VM creation isn't
> supported, and there's this RFE to support it:
> https://bugzilla.redhat.com/show_bug.cgi?id=999969
>
> My two original suggestions will apparently have to suffice until this
> RFE is realised; either properly configuring the template's NICs before
> VM creation or modifying the VMs' NICs following creation.
>
> >>
> >>>
> >>> Hope this helps! Let us know please :)
> >>> Yours, Lior.
> >>>
> >>> On 01/10/14 10:32, Morgan McLean wrote:
> >>>> Hi,
> >>>>
> >>>> Trying to remotely spawn a large amount of VM's. It would appear I can
> >>>> only use templates...which would have a NIC stuck to one network vlan.
> >>>> It doesn't appear that I can change that vlan remotely.
> >>>>
> >>>> Is there any easy way I can get this done?
> >>>>
> >>>> Thanks,
> >>>> Morgan
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> Users mailing list
> >>>> Users at ovirt.org <javascript:;>
> >>>> http://lists.ovirt.org/mailman/listinfo/users
> >>>>
> >>> _______________________________________________
> >>> Users mailing list
> >>> Users at ovirt.org <javascript:;>
> >>> http://lists.ovirt.org/mailman/listinfo/users
> >>>
> >>
> >> _______________________________________________
> >> Users mailing list
> >> Users at ovirt.org <javascript:;>
> >> http://lists.ovirt.org/mailman/listinfo/users
> >>
>


-- 
Thanks,
Morgan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20141002/acddabd7/attachment-0001.html>