9:47 a.m.
Hi,
I plan to extend the MacPoolRange.
If I also completely change the pool, in a way that does not implies the
previous setting, will the manager ban all the previous MACs, now
outside the defined pool? (and stop the VMs?)
Regards,
--
Nicolas Ecarnot
1:43 p.m.
On 09/10/2014 09:47 AM, Nicolas Ecarnot wrote:
Hi,
I plan to extend the MacPoolRange.
If I also completely change the pool, in a way that does not implies the
previous setting, will the manager ban all the previous MACs, now
outside the defined pool? (and stop the VMs?)
Regards,
no, just affect future mac allocations.
2:36 p.m.
just to add one more comment: nothing changes for MACs allocated using previous
MacPoolRange. After MacPoolRange change, they will be treated like user specified MAC
addresses, which also don't have to be part of any range.
m.
----- Original Message -----
From: "Itamar Heim" <iheim(a)redhat.com>
To: "Nicolas Ecarnot" <nicolas(a)ecarnot.net>, users(a)ovirt.org, "Lior
Vernia" <lvernia(a)redhat.com>
Sent: Wednesday, September 10, 2014 12:43:12 PM
Subject: Re: [ovirt-users] Modify the MacPoolRange : Former MACs?
On 09/10/2014 09:47 AM, Nicolas Ecarnot wrote:
Hi,
I plan to extend the MacPoolRange.
If I also completely change the pool, in a way that does not implies the
previous setting, will the manager ban all the previous MACs, now
outside the defined pool? (and stop the VMs?)
Regards,
no, just affect future mac allocations.
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
3:44 p.m.
Le 10/09/2014 13:36, Martin Mucha a écrit :
just to add one more comment: nothing changes for MACs allocated
using previous MacPoolRange. After MacPoolRange change, they will be
treated like user specified MAC addresses, which also don't have to
be part of any range.
OK.
I'm asking about banning, because I witnessed that when (ovirt-shell)
provisionning a new VM and its nic with a MAC outside of the pool range,
the adding gets refused.
I still dare not changing it unless you swear and sign it with your
blood that this macpoolrange modification won't prevent me from running
my existing VMs.
m.
----- Original Message ----- From: "Itamar Heim" <iheim(a)redhat.com>
To: "Nicolas Ecarnot" <nicolas(a)ecarnot.net>, users(a)ovirt.org, "Lior
Vernia" <lvernia(a)redhat.com> Sent: Wednesday, September 10, 2014
12:43:12 PM Subject: Re: [ovirt-users] Modify the MacPoolRange :
Former MACs?
On 09/10/2014 09:47 AM, Nicolas Ecarnot wrote:
> Hi,
>
> I plan to extend the MacPoolRange.
>
> If I also completely change the pool, in a way that does not
> implies the previous setting, will the manager ban all the previous
> MACs, now outside the defined pool? (and stop the VMs?)
>
> Regards,
>
no, just affect future mac allocations.
_______________________________________________ Users mailing list
Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--
Nicolas Ecarnot
4:54 p.m.
On 09/10/2014 03:44 PM, Nicolas Ecarnot wrote:
Le 10/09/2014 13:36, Martin Mucha a écrit :
> just to add one more comment: nothing changes for MACs allocated
> using previous MacPoolRange. After MacPoolRange change, they will be
> treated like user specified MAC addresses, which also don't have to
> be part of any range.
OK.
I'm asking about banning, because I witnessed that when (ovirt-shell)
provisionning a new VM and its nic with a MAC outside of the pool range,
the adding gets refused.
I still dare not changing it unless you swear and sign it with your
blood that this macpoolrange modification won't prevent me from running
my existing VMs.
that's strange, since you should be able to set any mac you want iirc.
mac pool is just for engine auto assigning.
>
> m.
>
> ----- Original Message ----- From: "Itamar Heim" <iheim(a)redhat.com>
> To: "Nicolas Ecarnot" <nicolas(a)ecarnot.net>, users(a)ovirt.org,
"Lior
> Vernia" <lvernia(a)redhat.com> Sent: Wednesday, September 10, 2014
> 12:43:12 PM Subject: Re: [ovirt-users] Modify the MacPoolRange :
> Former MACs?
>
> On 09/10/2014 09:47 AM, Nicolas Ecarnot wrote:
>> Hi,
>>
>> I plan to extend the MacPoolRange.
>>
>> If I also completely change the pool, in a way that does not
>> implies the previous setting, will the manager ban all the previous
>> MACs, now outside the defined pool? (and stop the VMs?)
>>
>> Regards,
>>
>
> no, just affect future mac allocations.
> _______________________________________________ Users mailing list
> Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users
>
9:18 a.m.
----- Original Message -----
From: "Nicolas Ecarnot" <nicolas(a)ecarnot.net>
To: "Martin Mucha" <mmucha(a)redhat.com>
Cc: users(a)ovirt.org
Sent: Wednesday, September 10, 2014 3:44:33 PM
Subject: Re: [ovirt-users] Modify the MacPoolRange : Former MACs?
Le 10/09/2014 13:36, Martin Mucha a écrit :
> just to add one more comment: nothing changes for MACs allocated
> using previous MacPoolRange. After MacPoolRange change, they will be
> treated like user specified MAC addresses, which also don't have to
> be part of any range.
OK.
I'm asking about banning, because I witnessed that when (ovirt-shell)
provisionning a new VM and its nic with a MAC outside of the pool range,
the adding gets refused.
What is the rejection message ? Perhaps it is a mac address which is already
in use by other vm ?
I still dare not changing it unless you swear and sign it with your
blood that this macpoolrange modification won't prevent me from running
my existing VMs.
>
> m.
>
> ----- Original Message ----- From: "Itamar Heim" <iheim(a)redhat.com>
> To: "Nicolas Ecarnot" <nicolas(a)ecarnot.net>, users(a)ovirt.org,
"Lior
> Vernia" <lvernia(a)redhat.com> Sent: Wednesday, September 10, 2014
> 12:43:12 PM Subject: Re: [ovirt-users] Modify the MacPoolRange :
> Former MACs?
>
> On 09/10/2014 09:47 AM, Nicolas Ecarnot wrote:
>> Hi,
>>
>> I plan to extend the MacPoolRange.
>>
>> If I also completely change the pool, in a way that does not
>> implies the previous setting, will the manager ban all the previous
>> MACs, now outside the defined pool? (and stop the VMs?)
>>
>> Regards,
>>
>
> no, just affect future mac allocations.
> _______________________________________________ Users mailing list
> Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users
>
--
Nicolas Ecarnot
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
9:28 a.m.
----- Original Message -----
From: "Moti Asayag" <masayag(a)redhat.com>
To: "Nicolas Ecarnot" <nicolas(a)ecarnot.net>
Cc: "Martin Mucha" <mmucha(a)redhat.com>, users(a)ovirt.org
Sent: Thursday, September 11, 2014 9:18:03 AM
Subject: Re: [ovirt-users] Modify the MacPoolRange : Former MACs?
----- Original Message -----
> From: "Nicolas Ecarnot" <nicolas(a)ecarnot.net>
> To: "Martin Mucha" <mmucha(a)redhat.com>
> Cc: users(a)ovirt.org
> Sent: Wednesday, September 10, 2014 3:44:33 PM
> Subject: Re: [ovirt-users] Modify the MacPoolRange : Former MACs?
>
> Le 10/09/2014 13:36, Martin Mucha a écrit :
> > just to add one more comment: nothing changes for MACs allocated
> > using previous MacPoolRange. After MacPoolRange change, they will be
> > treated like user specified MAC addresses, which also don't have to
> > be part of any range.
>
> OK.
>
> I'm asking about banning, because I witnessed that when (ovirt-shell)
> provisionning a new VM and its nic with a MAC outside of the pool range,
> the adding gets refused.
What is the rejection message ? Perhaps it is a mac address which is already
in use by other vm ?
Please note that currently the API doesn't support specifying network interfaces
at vm creation [1], only after the vm is created, the user can add/update/delete vm
network
interfaces.
So could you explain the scenario which lead to the rejection ?
[1] https://bugzilla.redhat.com/show_bug.cgi?id=999969
> I still dare not changing it unless you swear and sign it with
your
> blood that this macpoolrange modification won't prevent me from running
> my existing VMs.
>
> >
> > m.
> >
> > ----- Original Message ----- From: "Itamar Heim"
<iheim(a)redhat.com>
> > To: "Nicolas Ecarnot" <nicolas(a)ecarnot.net>, users(a)ovirt.org,
"Lior
> > Vernia" <lvernia(a)redhat.com> Sent: Wednesday, September 10, 2014
> > 12:43:12 PM Subject: Re: [ovirt-users] Modify the MacPoolRange :
> > Former MACs?
> >
> > On 09/10/2014 09:47 AM, Nicolas Ecarnot wrote:
> >> Hi,
> >>
> >> I plan to extend the MacPoolRange.
> >>
> >> If I also completely change the pool, in a way that does not
> >> implies the previous setting, will the manager ban all the previous
> >> MACs, now outside the defined pool? (and stop the VMs?)
> >>
> >> Regards,
> >>
> >
> > no, just affect future mac allocations.
> > _______________________________________________ Users mailing list
> > Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users
> >
>
>
> --
> Nicolas Ecarnot
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
10:43 a.m.
Le 11/09/2014 08:28, Moti Asayag a écrit :
>> I'm asking about banning, because I witnessed that when
(ovirt-shell)
>> provisionning a new VM and its nic with a MAC outside of the pool range,
>> the adding gets refused.
>
> What is the rejection message ? Perhaps it is a mac address which is already
> in use by other vm ?
>
Please note that currently the API doesn't support specifying network interfaces
at vm creation [1], only after the vm is created, the user can add/update/delete vm
network
interfaces.
So could you explain the scenario which lead to the rejection ?
Hi,
This morning, I had to provision one more VM, using the same script as
usual.
This script obviously creates a VM, *then* adds a NIC attached to this VM.
What I saw some days ago was that I had troubles creating the nic. The
exact error msg is forgotten, but it was related to MAC issues.
In the MAC pool range, the first half part is related to Qumranet, the
original company that created oVirt. The second half is free for users
to change (and is maybe drawn randomly on install ?)
In a hurry, I change a bit in the first part, to be absolutely sure I
could not hit a MAC conflict (being outside the macpoolrange).
And the creation failed.
This morning, I tried the same, and it succeed.
Damn, I thought I cought a bug, but it escaped.
--
Nicolas Ecarnot
3724
days inactive
3726
days old
7 comments
4 participants
participants (4)
-
Itamar Heim -
Martin Mucha -
Moti Asayag -
Nicolas Ecarnot