[Users] VM MAC-Ranges and setting custom MACs via API

[Moti Asayag]

----- Original Message -----
> From: "Itamar Heim" <iheim at redhat.com>
> To: "Sven Kieske" <S.Kieske at mittwald.de>, users at ovirt.org, "Moti Asayag" <masayag at redhat.com>, "Mike Kolesnik"
> <mkolesni at redhat.com>, "Lior Vernia" <lvernia at redhat.com>
> Sent: Sunday, January 5, 2014 11:19:38 PM
> Subject: Re: [Users] VM MAC-Ranges and setting custom MACs via API
> 
> On 01/03/2014 04:34 PM, Sven Kieske wrote:
> > Hi,
> >
> > I got some questions regarding the MAC-Range in the engine
> > and how to utilize the set custom mac feature via API:
> >
> > We want to set a custom MAC per VM via REST-API (JSON)
> > The RSDL tells me, that this should be possible in general.
> >
> > However, I have two questions:
> >
> > Must the specified custom MAC be within the range defined in
> > engine?
> >

Your assumption is correct, you can provide either a mac address
from the pool or other.

> > I suppose not, as this range should just be a pool
> > to take MACs from when engine itself acquires one for a vm.
> > Also some users in IRC could use imported vms
> > with custom macs, but using REST might yield different results?
> >
> > Does this work via JSON in ovirt-engine 3.3.2 ?
> >
> > I just learned that the JSON implementation is not
> > feature complete until 3.4. so I wonder if I can use
> > JSON instead of XML to achieve this.
> >
> > I can not wait for the 3.4. release anyway.
> >
> > We had so far no problem with using JSON beside a nasty
> > Cloud-Init (documentation)bug (BZ 1045484)
> > and we don't want to rewrite all
> > our code to generate XML instead
> > of JSON if we can avoid it.
> >
> 
> iiuc, with moving to support json, some property name changes will
> happen (juan can provide more details).
> as for the mac question - moti/mike/lior?
>