API -- Do I need to use templates? Can I change network for the nic?
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
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). 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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
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?
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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "Lior Vernia" <lvernia@redhat.com>, "Morgan McLean" <wrx230@gmail.com> Cc: users@ovirt.org 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?
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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 02/10/14 10:22, Tomas Jelinek wrote:
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "Lior Vernia" <lvernia@redhat.com>, "Morgan McLean" <wrx230@gmail.com> Cc: users@ovirt.org 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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
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@redhat.com> wrote:
On 02/10/14 10:22, Tomas Jelinek wrote:
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com <javascript:;>> To: "Lior Vernia" <lvernia@redhat.com <javascript:;>>, "Morgan McLean"
Cc: users@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
<wrx230@gmail.com <javascript:;>> that anyway triggers two different actions.
But now as I have tried it, if I create a VM from template or instance
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
type (using API), the NICs are completely ignored. 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@ovirt.org <javascript:;> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org <javascript:;> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org <javascript:;> http://lists.ovirt.org/mailman/listinfo/users
-- Thanks, Morgan
I'm actually having issues across the board...maybe its because I'm going against the design ideals but I was told that in order to use the local storage on the box and sacrifice VM migration capabilities, all machines had to be in their own datacenter. Pain point number one. Second pain point is adding additional networks aside from the initial management network doesn't seem to be very intuitive. I'm a network engineer for a living...and I can't figure it out. Third pain point is ovirt management UI requires a restart semi frequently due to crashing. I added the network under the networks tab, but I noticed it doesn't ask any interface questions (ok, it could technically attempt arp on all interfaces like a citrix netscaler). I notice theres no ifconfig changes on the host. I also notice that the other interface has a bridge named exactly as the management name in the UI; ovirtmgmt, which is bridged to eth0. OK, so I create a bridge called utility (my network name) and mapped it to a vlan tagged interface I had setup on eth1.21. Everything looks identical to how ovirt setup the initial network. The interface itself works, I can see things on the network etc. Traffic passes. Trying to run the VM results in errors because its failing network filters, says it doesn't exist etc. All I want to do, is create a VM with some memory, some disk, with a nic on a network, across individual machines. My PXE provisioning will take over from there. Whats the best way to do this? Sorry for all the questions -- your guys' response is great, and I really appreciate the help thus far. The exact message I get is: Error while executing action: utiltest: - Cannot run VM. There are no available running Hosts with all the networks used by the VM. - Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details: - The host load3.pod1.########.com did not satisfy internal filter Network Thanks, Morgan On Thu, Oct 2, 2014 at 1:30 AM, Morgan McLean <wrx230@gmail.com> wrote:
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@redhat.com> wrote:
On 02/10/14 10:22, Tomas Jelinek wrote:
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "Lior Vernia" <lvernia@redhat.com>, "Morgan McLean" <
Cc: users@ovirt.org 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
wrx230@gmail.com> that anyway triggers two different actions.
But now as I have tried it, if I create a VM from template or instance
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
type (using API), the NICs are completely ignored. 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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Thanks, Morgan
On 2-10-2014 23:05, Morgan McLean wrote:
I'm actually having issues across the board...maybe its because I'm going against the design ideals but I was told that in order to use the local storage on the box and sacrifice VM migration capabilities, all machines had to be in their own datacenter. Pain point number one.
For reference: http://www.ovirt.org/OVirt_Administration_Guide
Second pain point is adding additional networks aside from the initial management network doesn't seem to be very intuitive. I'm a network engineer for a living...and I can't figure it out.
See below
Third pain point is ovirt management UI requires a restart semi frequently due to crashing.
Don't know about your version and whether you have a dedicated or a hosted-engine setup but in my case I have both types running and don't experience any crashes, running a dedicated 3.4.3 engine(s)
I added the network under the networks tab, but I noticed it doesn't ask any interface questions (ok, it could technically attempt arp on all interfaces like a citrix netscaler). I notice theres no ifconfig changes on the host. I also notice that the other interface has a bridge named exactly as the management name in the UI; ovirtmgmt, which is bridged to eth0. Sofar everything OK
OK, so I create a bridge called utility (my network name) and mapped it to a vlan tagged interface I had setup on eth1.21. Everything looks identical to how ovirt setup the initial network. The interface itself works, I can see things on the network etc. Traffic passes.
Not needed. If you have created your networks then goto to the hosts tab, select your host, select the Network Interfaces tab and hit Setup Host Networks. You'll get a window where you can drag and drop your defined networks to an interface and define properties for them.
Trying to run the VM results in errors because its failing network filters, says it doesn't exist etc. All I want to do, is create a VM with some memory, some disk, with a nic on a network, across individual machines. My PXE provisioning will take over from there. Whats the best way to do this? Sorry for all the questions -- your guys' response is great, and I really appreciate the help thus far.
I use theForeman for that and it works perfectly. No problem with the questions, oVirt tries to solve a complex problem and sometimes its easy to forget that one had the same problems a whole while back :-) Joop
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02.10.2014 23:05, Morgan McLean wrote:
I'm actually having issues across the board...maybe its because I'm going against the design ideals but I was told that in order to use the local storage on the box and sacrifice VM migration capabilities, all machines had to be in their own datacenter. Pain point number one.
Yes it's painful to use local storage, that's true, but will eventually change with 3.6 or something.
Second pain point is adding additional networks aside from the initial management network doesn't seem to be very intuitive. I'm a network engineer for a living...and I can't figure it out.
Well I'm sure I can assist with that one even if I'm no network engineer ;)
Third pain point is ovirt management UI requires a restart semi frequently due to crashing.
You should submit bugs for crashes, I have never seen a UI crash in ovirt, not even in 3.2. Which version are you using and what are you doing when it crashes?
I added the network under the networks tab, but I noticed it doesn't ask any interface questions (ok, it could technically attempt arp on all interfaces like a citrix netscaler).
I notice theres no ifconfig changes on the host. There will not be any if you didn't apply any logical networks to the host in the first place. Furthermore it's important to know your ovirt version because there was a change in recent vdsm versions regarding
Well, the UI is a little cluttered, so I have to ask: Which network tab? You define a logical network on a datacenter level you then have to add this to the logical cluster in this datacenter. It should get added by default to the logical cluster in fact, and it should be marked as "required" (which is a bad default, I have a BZ tracking this). You need then to manually add this logical network to your host. You can further adjust your networking by adding network profiles. In short: the whole network management takes place in ovirt! You do _not_ need to configure anything on the compute node/host yourself. You can do bonding, bridging, v-lans, port mirroring, qos and so on. the path where network configuration is stored. (I don't recall that path out of my head but others may provide the info here) I also notice that the other interface has a bridge named exactly
as the management name in the UI; ovirtmgmt, which is bridged to eth0. OK, so I create a bridge called utility (my network name) and mapped it to a vlan tagged interface I had setup on eth1.21. Everything looks identical to how ovirt setup the initial network. The interface itself works, I can see things on the network etc. Traffic passes.
I guess you tried to define the network yourself on the host? First wrong step :) jut add your logical networks to the host, either through UI or via API. Here are some docs you should read: http://www.ovirt.org/OVirt_Administration_Guide#Hosts_and_Networking http://www.ovirt.org/OVirt_Administration_Guide#Logical_Networks
Trying to run the VM results in errors because its failing network filters, says it doesn't exist etc. All I want to do, is create a VM with some memory, some disk, with a nic on a network, across individual machines. My PXE provisioning will take over from there. Whats the best way to do this? Sorry for all the questions -- your guys' response is great, and I really appreciate the help thus far.
The exact message I get is:
Error while executing action: utiltest:
- Cannot run VM. There are no available running Hosts with all the networks used by the VM. - Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details: - The host load3.pod1.########.com did not satisfy internal filter Network
Of course, you did not attach the logical network you defined for your datacenter to your host (compute node) through ovirt. HTH Sven -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQGcBAEBAgAGBQJULpF5AAoJEAq0kGAWDrql51oL+gPRWfL97Kli8ZXPdjlVhNxg Udj8Jv7ayZyvQpxAzp+J7e06Fmk+kw6rcCY6agT7BmqHKIrJoC2trrIq89hGQqMS dM9ltcFuvkmHWP12POIroca5rF7i/efZ859jVwI0uKmsGxpT09mZQK0rnhgpKFTL yClTY+q2rtrahgQ5pNrBVFQ13X5c7ZzSjOr0VplA73IqYF5lokxjj1/btRREj6B+ 80LunNUCOX9qNRh/+DkDzWl/Z1Gh6YL5dTdV53JUBF4uv38LmDgEcIlggU6KNtC3 DE2m1vdS6LtAEco3CyXoAPb+pkm4T5mFwp4nKqvTAcY2HZUuESdrZOXiABeYpvvU M9EIvNTuomqdAJRdJi2UwgagINnDwoiUFlCvbhgB/G31h9lyQw3QY3yV4C501N98 u/ezhPHmuWCuAR3EFBpexVsL/lXDotqg+eEauJXL0SXv94G73FBoZHUrm1n8O4Zw cyHH/G2yB1WGBv9SL/OFS6/qYHADTYBwG/NjoQIrAQ== =NH99 -----END PGP SIGNATURE-----
On 03/10/14 00:05, Morgan McLean wrote:
I'm actually having issues across the board...maybe its because I'm going against the design ideals but I was told that in order to use the local storage on the box and sacrifice VM migration capabilities, all machines had to be in their own datacenter. Pain point number one.
Wait, what? :) This doesn't sound right. What is it that you're trying to achieve exactly? I'm guessing you'll be able to achieve the same thing just by pinning VMs to hosts (via the VM dialog) and using a single DC. However, I'm not sure you even need to do that... I don't use local storage so I don't really know, but things will probably work even if you don't do anything special (except migration might not work).
Second pain point is adding additional networks aside from the initial management network doesn't seem to be very intuitive. I'm a network engineer for a living...and I can't figure it out.
Third pain point is ovirt management UI requires a restart semi frequently due to crashing.
Could you give any further details? Version you're using, exact symptoms? This isn't by design :) And I haven't run into anything of the sort.
I added the network under the networks tab, but I noticed it doesn't ask any interface questions (ok, it could technically attempt arp on all interfaces like a citrix netscaler). I notice theres no ifconfig changes on the host. I also notice that the other interface has a bridge named exactly as the management name in the UI; ovirtmgmt, which is bridged to eth0. OK, so I create a bridge called utility (my network name) and mapped it to a vlan tagged interface I had setup on eth1.21. Everything looks identical to how ovirt setup the initial network. The interface itself works, I can see things on the network etc. Traffic passes.
You shouldn't have to configure anything manually on a host, e.g. set up bridges, oVirt does this for you. Once you create the network in the tab, you can assign it to hosts by heading to the Host/Interfaces secondary tab and clicking "Setup Host Networks". Once you do that - VMs using that network should be able to run on that host.
Trying to run the VM results in errors because its failing network filters, says it doesn't exist etc. All I want to do, is create a VM with some memory, some disk, with a nic on a network, across individual machines. My PXE provisioning will take over from there. Whats the best way to do this? Sorry for all the questions -- your guys' response is great, and I really appreciate the help thus far.
The exact message I get is:
Error while executing action: utiltest:
* Cannot run VM. There are no available running Hosts with all the networks used by the VM. * Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details: * The host load3.pod1.########.com did not satisfy internal filter Network
Thanks, Morgan
On Thu, Oct 2, 2014 at 1:30 AM, Morgan McLean <wrx230@gmail.com <mailto:wrx230@gmail.com>> wrote:
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@redhat.com <mailto:lvernia@redhat.com>> wrote:
On 02/10/14 10:22, Tomas Jelinek wrote: > > > ----- Original Message ----- >> From: "Itamar Heim" <iheim@redhat.com> >> To: "Lior Vernia" <lvernia@redhat.com>, "Morgan McLean" <wrx230@gmail.com> >> Cc: users@ovirt.org >> 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@ovirt.org >>>> http://lists.ovirt.org/mailman/listinfo/users >>>> >>> _______________________________________________ >>> Users mailing list >>> Users@ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> >> >> _______________________________________________ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >>
-- Thanks, Morgan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05.10.2014 10:13, Lior Vernia wrote:
Wait, what? :) This doesn't sound right. What is it that you're trying to achieve exactly? I'm guessing you'll be able to achieve the same thing just by pinning VMs to hosts (via the VM dialog) and using a single DC.
However, I'm not sure you even need to do that... I don't use local storage so I don't really know, but things will probably work even if you don't do anything special (except migration might not work).
Well, this _is_ right. For local storage, you need a single host in a single cluster in a single DC, this is an old design limitation. I agree, a design with just cpu pinning and no migration would be better :) regards Sven -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQGcBAEBAgAGBQJUMT5zAAoJEAq0kGAWDrqlWK8L/jVzCy0BfeIsTIQU9//E5V3Y 3Xq2K3BguOBSGbxyA9Qv2n8uNpCEkcU5SDCgGN6sZz0hQZwVEJUcpiNhe7vKDprY dQ3VLoGFQ8CSwRe0EpY7tlYZQtdAznHOqEXIBbNYRXA5goUWRWiP67ZUYNzm2RBV Uv14WqS/9/DTf3kn58xcBWujFGbjCz+nhI0hXjiSTWn/Tb+0V43uuBlac9/wBdZh XHQyN59bNjwNxUMyOkfCm67bXMAFx8zdznj02v05qsc7b9QYqhkaMCgc/nN5rIc4 /lqAgAPVwJWBMKgtUWt0rzo6xZpG84bGXkQ9C716ZtANQ3rWKDMs5LSe2U3xHkWI FN6ukxhey7b8117bxPks1Hehb14zIHieIJgt4pJi9Q0U55WZ//553DSCTlX9e9kp LacUZ2t41KuQFd9Y9Uce5/8ntxwGezaLZ2kGRoSqfF7OthiWWMci/cZzJHt7toLr FsY3cofka27WdYAjpzcHfU0NTX93fLkim258RAwjGw== =FEVb -----END PGP SIGNATURE-----
participants (6)
-
Itamar Heim -
Lior Vernia -
Morgan McLean -
noc -
Sven Kieske -
Tomas Jelinek