<div dir="ltr">I've always run it as a VM. In my opinion there's no real need to dedicate hardware to Fuel since it doesn't even need to be running all the time. Once you deploy your cloud you can shut it down until the next time it's needed.<div><br></div><div>That will solve you eth0 problem also.</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><p style="margin-top:8px;margin-bottom:8px;font-family:Helvetica,Verdana,Arial,sans-serif;font-size:0.85em;color:rgb(51,51,51);line-height:1.4"><span style="font-size:0.6em;line-height:1.4">The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.</span><br></p></div></div></div></div><a href="http:///" target="_blank"></a></div></div></div></div>
<br><div class="gmail_quote">On Sun, Jan 29, 2017 at 1:12 PM, Georgios Dimitrakakis <span dir="ltr"><<a href="mailto:giorgis@acmac.uoc.gr" target="_blank">giorgis@acmac.uoc.gr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi!<br>
<br>
I am a new user of Fuel and would like to deploy it on a physical SuperMicro machine. Unfortunately I wasn't able to install it via the ISO file since I 've tried several times (with both the community and the Mirantis edition) and every time there is a problem with the boot loader which cannot be installed correctly thus resulting in a non-bootable system. That's the reason I moved on, I installed CentOS and tried to follow the instructions from here: <a href="http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/install/install_install_fuel_master_node.html" rel="noreferrer" target="_blank">http://docs.openstack.org/deve<wbr>loper/fuel-docs/userdocs/fuel-<wbr>install-guide/install/install_<wbr>install_fuel_master_node.html</a><br>
<br>
Even this attempt was without success since the Fuel bootstrap script is looking for connectivity on eth0 which is not connected.<br>
<br>
The machine is the property of a DataCenter and out of the 4interfaces only the two are cabled and those two are not the first ones but the third and forth. So my CentOS has connectivity on "eno3" and "eno4" devices. So my question is how can I instruct Fuel to look for connectivity on "eno3" rather than on "eth0" or "eno1"?<br>
<br>
I did try to disable the first two interfaces from the BIOS but couldn't find any option. Then I thought that I could perform a trick and rename the devices but that doesn't seem correct...If there isn't any other option I will try it but I am sure that Fuel has a way to instract the bootstarp script to use a specific device but haven't found it yet.<br>
<br>
Your help is much appreciated!<br>
<br>
Thank you,<br>
<br>
<br>
George<br>
<br>
______________________________<wbr>_________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k</a><br>
</blockquote></div><br></div></div>