Re: [Openstack] [Fuel] Use other NIC

[John Petrini]

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.

That will solve you eth0 problem also.

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.

On Sun, Jan 29, 2017 at 1:12 PM, Georgios Dimitrakakis  wrote:

> Hi!
>
> 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: http://docs.openstack.org/deve
> loper/fuel-docs/userdocs/fuel-install-guide/install/install_
> install_fuel_master_node.html
>
> Even this attempt was without success since the Fuel bootstrap script is
> looking for connectivity on eth0 which is not connected.
>
> 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"?
>
> 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.
>
> Your help is much appreciated!
>
> Thank you,
>
>
> George
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [Fuel] Use other NIC

[Georgios Dimitrakakis]

Hi!

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: 
http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/install/install_install_fuel_master_node.html


Even this attempt was without success since the Fuel bootstrap script 
is looking for connectivity on eth0 which is not connected.


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"?


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.


Your help is much appreciated!

Thank you,


George

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack