Hi Rustam,
You are right, the udev persistent rule was preventing for a correct
network configuration.
We've updated the appliance to remove the rule:
http://marketplace.c12g.com/appliance/53e4e9258fb81d6a8207
Let us know if you find anything else, we appreciate the feedback.
Best regards,
-Tino
--
OpenNebula - Flexible Enterprise Cloud Made Simple
--
Constantino Vázquez Blanco, PhD, MSc
Senior Infrastructure Architect at C12G Labs
www.c12g.com | @C12G | es.linkedin.com/in/tinova
--
Confidentiality Warning: The information contained in this e-mail and
any accompanying documents, unless otherwise expressly indicated, is
confidential and privileged, and is intended solely for the person
and/or entity to whom it is addressed (i.e. those identified in the
To and cc box). They are the property of C12G Labs S.L..
Unauthorized distribution, review, use, disclosure, or copying of this
communication, or any part thereof, is strictly prohibited and may be
unlawful. If you have received this e-mail in error, please notify us
immediately by e-mail at ab...@c12g.com and delete the e-mail and
attachments and any copy from your system. C12G thanks you for your
cooperation.
On 2 September 2014 02:36, Rustam Ismail rustam.ism...@gmail.com wrote:
Hi,
I want to inform you that the appliance linked here OpenNebula 4.8 ESX
Sandbox has no eth0 available. I was using VMware ESXi. The result was the
same when running it via Virtualbox. Only br0 availble. It gave me a lot
headache to find out why since eth0 is standard nowadays, a must have one. I
thought that when building the appliance, then he/she must have at least one
ethernet card attached physically, right?
I saw that /etc/sysconfig/network-script/ifcfg-eth0 was there, using dhcp as
bootproto. Running ifcofig eth0 up showed up a failure message.
I found the answer why while reading an ebook, I noticed that there is a
mention that you need to remove the
/etc/udev/rules.d/70-persistent-net.rules in order to prevent the network
interface coming up as an interface other than eth0. So, I did just as told,
restart the network service, and voila! It works, the eth0 is now there and
enabling me to login to Sunstone.
The funny thing is, that ebook I read and found the answer is an ebook about
OpenStack :)
Perhaps you guys should add a note about this and howto overcome the missing
eth0 in the appliances.
Regards,
Salam,
Rustam
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
