Hi,
Could you explain this a bit more? Did all NICs appear, or did to many NICs appear?
I'm used to udev leave my NIC in sequence. And in this case it got messed up: common: eth0 -> port 1 eth1 -> port 2 ethx >> port X What happened: eth0 -> port 1 eth4 -> port 3 eth5 -> port 4 eth6 -> port 2 As follows attached file .. Not a big problem .. But it confused me a little time to configure the network of 'nodes' ... Had to use tcpdump (thankfully that was available) to find out which interface belonged to what port Switch for CDP: P 2014/1/17 Fabian Deutsch <fabiand@redhat.com>
Hi Laercio,
Am Freitag, den 17.01.2014, 14:49 -0200 schrieb Laercio Motta:
I tested the ISO here.
Thanks for being that brave! ;)
- I was able to register with the engine and aprove (thing with 'oVirt-node-3.0.1-iso-1.0.2.vdsm.el6.iso' version was not possible)
Great that this works now.
- Firewall: Being duplicated the rule of vdsm port (54321). - 'Sanlock' is being blocked by 'selinux' (audit.log attached)
Okay, those are probably bugs we need to take care of.
- NIC was messy .. :P (eth0, eth4, eth5, eth6... )..
Could you explain this a bit more? Did all NICs appear, or did to many NICs appear?
Thanks fabian
2014/1/17 Fabian Deutsch <fabiand@redhat.com> Hey,
as many of you have noticed there wasn't any well working oVirt Node ISO around for oVirt 3.3. To get this ball rolling again I've put together a draft image of ALPHA quality. It contains many fixes some of us have been working on over the last weeks.
- Source & ISO - To not drown Jenkins in a hell-of-a-patch-queue I've pushed the patches to
https://github.com/fabiand/ovirt-node/tree/teamsync
The ISO built from that patchset can be found here:
http://fedorapeople.org/~fabiand/node/3.0.4/ovirt-node-iso-3.0.3-0.999.20140...
Please test this draft image and provide feedback on how it works for you. If you encounter problems - and you probably will - please take a look here on how to debug them:
http://www.ovirt.org/Node_Troubleshooting
- Important Notes - SELinux: Boot this alpha image with enforcing=0 to log potential denials, but not block the calls. To fix those denials permanently please attach your /var/log/audit/audit.log to a bug in bugzilla.
Known problems: - Exception is raised after registration to Engine - Many bond devices are show on network page - Denials appear in /var/log/audit/audit.log
And don't hesitate to reach out to us if you want to get more involved with Node.
- fabian
-- ╔══════════════════════════════════════════════╗ ║▒▒▒▒▒▒▒▒▒▒▒ Laercio da Silva Motta ▒▒▒▒▒▒▒▒▒▒▒║ ║----------------------------------------------║ ║ Blog: http://www.laerciomotta.com/ ║ ║ Twitter: http://twitter.com/#!/laerciomasala ║ ║ Skype: laerciomasala ║ ║ Chave PGP: http://bit.ly/kXS6ga ║ ╚═════════════════════════════════════════v1.0═╝
-- ╔══════════════════════════════════════════════╗ ║▒▒▒▒▒▒▒▒▒▒▒ Laercio da Silva Motta ▒▒▒▒▒▒▒▒▒▒▒║ ║----------------------------------------------║ ║* Blog: *http://www.laerciomotta.com/ ║ ║ *Twitter:* http://twitter.com/#!/laerciomasala ║ ║ *Skype*: laerciomasala ║ ║ Chave PGP: http://bit.ly/kXS6ga ║ ╚═════════════════════════════════════════v1.0═╝