Mirantis OpenStack 9.0 deployment-ISO to Fuel UI

Network Planning

It’s important to plan network prior to installation. You need 5 network segments for different purposes and two of them (Admin-PXE and Public) should have access to the internet. Rest of the networks can be closed but make sure your management client PC has access to management network. Due to my lab limitation, I made all 5 networks private and used VyOS NAT feature to make OpenStack environment accessible from public network. Also, all OpenStack nodes (Master, Control, Compute) are installed on VMs.


Fuel Master Node Installation

Install Mirantis OpenStack 9.0 Fuel Master Image on a VM.

-VM environment

  • Hypervisor: ESXi 5.5
  • Guest Operating System: CentOS 4/5/6 (64-bit)
  • vNICs: 1 vNIC connected to Admin-PXE network
  • Virtual disk size: 60GB
  •  Memory 8GB RAM

-Boot MirantisOpenStack-9.0.iso and select “Fuel Install (Static IP)”


-After installation, you will be automatically directed to the configuration UI.


-Change default configuration

  • Fuel User Password – Set password to login Fuel UI
  • Network Setup
    • IP address:
    • Netmask:
    • Default Gateway:
    • Check => Apply
  • Security setup – Specify network from which you want to SSH Fuel Master
  • PXE Setup
    • DHCP Pool Start:
    • DHCP Pool End:
    • DHCP Gateway:
  • DNS & Hostname
    • Hostname: fuel-master-01
    • Domain: lab.local
    • Search Domain: lab.local
    • External DNS: your dns server
    • Check => Apply
  • Bootstrap Image
    • HTTP              proxy http://yourproxyserver:8080
    • HTTPS            proxy http://yourproxyserver:8080
  • Root Password – Set root password
  • Time Sync – Set at least one NTP Server.
  • Feature Groups – Check Experimental features and Advanced features
  • Shell Login -If proxy server setting in Bootstrap image section never seems to work, go to shell login and add “proxy=http://yourproxyserver:8080” directly to /etc/yum.conf
  • Quit Setup – Save and Quit

-Wait until the installation is completed and you are directed to login prompt.


-Access Fuel Web UI ( and login with username “admin” and fuel UI password

For OpenStack deployment, please go to Mirantis OpenStack 9.0 deployment-Fuel UI to Horizon.

16 comments on “Mirantis OpenStack 9.0 deployment-ISO to Fuel UI
  1. Hi Harold,

    So, I need blank node with no operating system right ?
    and If I don’t have the blank node to configure can I configure the KVM in my bare-metal Mirantis OpenStack?

    Sorry for asking dump question but right now I’m in learning phase of OpenStack & in my current firm we want to deploy the OpenStack Infrastructure.

    Right now I would like to use 1 Single System for my Mirantis OpenStack as well as Nodes too.

    Please guide how can I do this on my Single Server because I have high-end Server & which allocated for this R&D purpose only.

    Thank you,


  2. OK, so you want to deploy fuel master & openstack nodes inside single high-spec server correct?
    In that case, yes you can use KVM to build Mirantis openstack environment. You need to install KVM(or ESXi) on bare-metal first. Then, create an instance for fuel master node. Install Mirantis fuel master from ISO file on that instance. Launch instances for openstack nodes too. I assume those virtual & blank instances supports pxe-boot and they will automatically load the bootstrap os images from fuel master instance.
    Since we are trying to build openstack inside single server, we end up running virtual host on top of virtual host and it’s possible. Unfortunately, I used ESXi instead of KVM but idea is the same. Hope this helps and feel free to reach out. Thanks

    • Hi Harold,

      Thank you very much for prompt reply.
      As you mentioned I need to install KVM in the Linux OS like Centos/Ubuntu, then need to configure the Mirantis fuel master from ISO.

      So will my other nodes will run from KVM it self right?
      No need of physical node.

      Guide me which OS will be better to run for KVM?
      Can I try to install Proxmox VE for Virtualization ?


      • Yeah you don’t need physical nodes. Just create virtual machines(nodes) from the same KVM where you created the virtual machine for fuel master.

        I don’t have much experience with KVM but I think redhat Enterprise Linux is good because it supports open vSwitch. So it’s better to pick anything that supports open vSwitch. Unlike Linux bridge, It allows you to configure network between virtual nodes more flexibly.

  3. Hi Thank you Harold,

    I am going to install ProxMox as my Visualization and top of that I am going to install Mirantis OpenStack Fuel.

    Will be this good idea to configure the OpenStack environment ?

    So I need 3 VM for OpenStack Right?

    1 Mirantis Fuel
    2 Compute
    3 Controller

    do I need any addition VM ?

    • Yeah those are the types of vms you need to build OpenStack environment. I think you need to have at least 3 controller nodes if you make them redundant. and minimum of 2 or 3 compute nodes if I remember correctly. If you have not enough nodes UI will give you warning so follow the instruction.

  4. Hey Harold,
    I have installed ProxMox VM on bare-metal.
    Then on top of that have created Fuel OpenStack VM.
    It’s simple infrastructure only.

    I can able to access Internet from my OpenStack VM which is my Fuel Master VM.

    But I’m getting error message after installation for bootstrap.

    Here is message:
    “WARNING: Failed to build the bootstrap image, see /var/log/fuel-bootstrap-image-build.log for details. Perhaps your Internet connection is broken. Please fix the problem and run `fuel-bootstrap build –activate`. While you don’t activate any bootstrap – new nodes cannot be discovered and added to cluster. For more information please visit http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/bootstrap/bootstrap_troubleshoot.html

    I am also sending you the attachment.

    Please let me about this soon so can i resolve this issue.


    • I’m assuming that your fuel master vm has internet connection through proxy server.
      Did you added proxy server configuration to /etc/yum.conf file? Since proxy settings in Boot strap configuration section never seem to work(I’m assuming it’s a bug), go to shell login and configure /etc/yum.conf file directly. See ‘Change default configuration’ section of this post for more detail. Hope this solves your problem.

    • Tushar,
      Oh good, having direct connection to the internet saves a lot of trouble.
      I see that your Fuel master has two interfaces and each configuration seems right.
      However, there may be a problem in your PXE setup. Tell me what IP address did you set for DHCP gateway? If you want to use interface with IP 10.xx.xx.xx for PXE network, you should advertise a gateway IP from 10.xx.xx.xx network too. And make sure all the nodes can access internet through that gateway. I see that you can connect Internet from fuel master through 172.xx network, but can each node access internet through 10.xx network? Your log also shows error in executing ‘apt-get’ from each node so securing internet connection from PXE network might solve your problem. Good luck!

  5. Hi Harold,
    Thank you for your prompt respond.
    I know you might be busy in your work too.

    Finally I can able to configure the Fuel Master and that can able to discover the additional nodes too.

    I can able to boot nodes with PXE frm 10.xx.xx.xx and they are able to get internet connection too from 10.xx.xx.xx gateway.

    Now my next challenge is my nodes installes with Ubuntu OS but I want to install the CentOs on those nodes and also Windows 7 also.

    How can I able to configure them on nodes ?

    I also sending you the snapshot of my configuration.

    Thank you once for replying….


Leave a Reply

Your email address will not be published. Required fields are marked *