Re: [ovirt-users] oVirt 3.6: Dummy interfaces

[Dan Kenigsberg]

On Mon, Dec 28, 2015 at 03:11:29PM -0800, Alan Murrell wrote:
> Hi Frank,
> 
> Thanks for info!  Does your script automatically load the dummy module as
> well, or do you create a separate file in '/etc/modprobe.d' to load it
> (that's how I currently do my dummy NICs)
> 
> Thanks! :-)
> 
> Quoting "Frank Wall" :
> 
> >Hi Alan,
> >
> >On Thu, Dec 24, 2015 at 10:37:17AM -0800, Alan Murrell wrote:
> >>Are dummy interfaces still supported in 3.6?
> >
> >I'm running ovirt 3.6 AiO and dummy interfaces are working just fine.
> >Instead of modifying oVirt's python source files, I'd recommend you
> >rename the dummy interface(s) to match the required pattern.
> >
> >I've setup a service for this by creating
> >/etc/systemd/system/dummynics.service
> >with the following content:
> >
> >[Unit]
> >Description=Rename dummy network interfaces for oVirt
> >
> >[Service]
> >Type=oneshot
> >ExecStart=/usr/sbin/ip l set dev dummy0 name dummy_0
> >ExecStart=/usr/sbin/ip l set dev dummy1 name dummy_1
> >ExecStart=/usr/sbin/ip l set dev dummy2 name dummy_2
> >ExecStart=/usr/sbin/ip l set dev dummy3 name dummy_3
> >RemainAfterExit=yes
> >
> >[Install]
> >WantedBy=multi-user.target
> >
> >
> >Then enable this service as follows:
> >
> >systemctl daemon-reload
> >systemctl enable dummynics
> >systemctl status dummynics
> >
> >Of course, you need to use the new dummy_* names when configuring the
> >network interfaces. I'd recommend to reboot the host after making these
> >changes.

Modifying fake_nics in vdsm.conf is still supported and should still
work (though it requires restarting both vdsmd and supervdsmd). If it
does not - please file a bug.

However, I would recommend to initially creat the dummy devices with
their proper name

ip link add dummy_1 type dummy

instead of creating them with dummy1 and then renaming them.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt 3.6: Dummy interfaces

[Alan Murrell]

Hi Frank,

Thanks for info!  Does your script automatically load the dummy module  
as well, or do you create a separate file in '/etc/modprobe.d' to load  
it (that's how I currently do my dummy NICs)


Thanks! :-)

Quoting "Frank Wall" :


Hi Alan,

On Thu, Dec 24, 2015 at 10:37:17AM -0800, Alan Murrell wrote:

Are dummy interfaces still supported in 3.6?


I'm running ovirt 3.6 AiO and dummy interfaces are working just fine.
Instead of modifying oVirt's python source files, I'd recommend you
rename the dummy interface(s) to match the required pattern.

I've setup a service for this by creating  
/etc/systemd/system/dummynics.service

with the following content:

[Unit]
Description=Rename dummy network interfaces for oVirt

[Service]
Type=oneshot
ExecStart=/usr/sbin/ip l set dev dummy0 name dummy_0
ExecStart=/usr/sbin/ip l set dev dummy1 name dummy_1
ExecStart=/usr/sbin/ip l set dev dummy2 name dummy_2
ExecStart=/usr/sbin/ip l set dev dummy3 name dummy_3
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target


Then enable this service as follows:

systemctl daemon-reload
systemctl enable dummynics
systemctl status dummynics

Of course, you need to use the new dummy_* names when configuring the
network interfaces. I'd recommend to reboot the host after making these
changes.


Regards
- Frank



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt 3.6: Dummy interfaces

[Yaniv Dary]

Isolated network interfaces didn't make it to 3.6
On Dec 24, 2015 20:39, "Alan Murrell"  wrote:

> Hello,
>
> I just upgraded my oVirt 3.5.1 install to 3.6.  I have a self-hosted
> engine setup all on a single server.
>
> I make use of dummy interfaces for internal networks for my various
> labs/testing setups.  Normally I edit the following file:
>
> /usr/lib/python2.7/site-packages/vdsm/config.py
>
> I then go to the variable 'fake_nics' and add 'dummy*", so it looks like
> this:
>
> ('fake_nics', 'dummy_*,veth_*,dummy*', ),
>
> After I added my entry, I even restarted the whole server (which restarts
> the VDSM on the host as well as the engine VM), but when I go into the
> "Network Interfaces" on the host the dummy interfaces are not showingup.
>
> Are dummy interfaces still supported in 3.6?  I see a feature called
> "Isolated Networks" in 3.6; is this essentially a replacement?  The
> Features page is a bit confusing to me on how to create an isolated network?
>
> Thanks!
>
> Regards,
>
> Alan
>
> ___
> 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

Re: [ovirt-users] oVirt 3.6: Dummy interfaces

[Frank Wall]

Hi Alan,

On Thu, Dec 24, 2015 at 10:37:17AM -0800, Alan Murrell wrote:
> Are dummy interfaces still supported in 3.6?

I'm running ovirt 3.6 AiO and dummy interfaces are working just fine.
Instead of modifying oVirt's python source files, I'd recommend you 
rename the dummy interface(s) to match the required pattern.

I've setup a service for this by creating /etc/systemd/system/dummynics.service
with the following content:

[Unit]
Description=Rename dummy network interfaces for oVirt

[Service]
Type=oneshot
ExecStart=/usr/sbin/ip l set dev dummy0 name dummy_0
ExecStart=/usr/sbin/ip l set dev dummy1 name dummy_1
ExecStart=/usr/sbin/ip l set dev dummy2 name dummy_2
ExecStart=/usr/sbin/ip l set dev dummy3 name dummy_3
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target


Then enable this service as follows:

systemctl daemon-reload
systemctl enable dummynics
systemctl status dummynics

Of course, you need to use the new dummy_* names when configuring the 
network interfaces. I'd recommend to reboot the host after making these
changes.


Regards
- Frank
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] oVirt 3.6: Dummy interfaces

[Alan Murrell]

Hello,

I just upgraded my oVirt 3.5.1 install to 3.6.  I have a self-hosted  
engine setup all on a single server.


I make use of dummy interfaces for internal networks for my various  
labs/testing setups.  Normally I edit the following file:


/usr/lib/python2.7/site-packages/vdsm/config.py

I then go to the variable 'fake_nics' and add 'dummy*", so it looks like this:

('fake_nics', 'dummy_*,veth_*,dummy*', ),

After I added my entry, I even restarted the whole server (which  
restarts the VDSM on the host as well as the engine VM), but when I go  
into the "Network Interfaces" on the host the dummy interfaces are not  
showingup.


Are dummy interfaces still supported in 3.6?  I see a feature called  
"Isolated Networks" in 3.6; is this essentially a replacement?  The  
Features page is a bit confusing to me on how to create an isolated  
network?


Thanks!

Regards,

Alan

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users