{"id":5985,"date":"2021-10-25T22:27:19","date_gmt":"2021-10-25T20:27:19","guid":{"rendered":"https:\/\/nil.uniza.sk\/?p=5985"},"modified":"2022-02-16T00:07:08","modified_gmt":"2022-02-15T23:07:08","slug":"how-to-install-microstack-on-vmware-with-ubuntu-guest-os","status":"publish","type":"post","link":"https:\/\/nil.uniza.sk\/en\/how-to-install-microstack-on-vmware-with-ubuntu-guest-os\/","title":{"rendered":"How to install Microstack on VMware with Ubuntu guest OS"},"content":{"rendered":"<p>Microstack is a pure upstream OpenStack distribution. It includes core OpenStack services and the most popular compute, network and storage options. Installation is fast and easy to perform.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"my-enviroment\"><strong>My enviroment<\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\"><li>VMware ESXI 6.7.0<\/li><li>Guest system:<ul><li>server install of Ubuntu 20.04.3 LTS<\/li><li>static public IP address<\/li><li>16GB RAM (8GB recommended)<\/li><li>4 vCPU<\/li><li>100GB of HDD (actual installation with one tiny instace of cirros running takes about 8GB of storage)<\/li><\/ul><\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"single-node-installation-steps-using-snap\"><strong>Single-node installation steps using snap<\/strong><\/h2>\n\n\n\n<p>Official documentation uses the snap system for installation. The installation, together with initialization, will take about 10 to 30 minutes, depending on your internet speed and HW specification.<\/p>\n\n\n\n<p>Installation steps:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># Update and upgrade system packages\n<strong>sudo apt update<\/strong>\n<strong>sudo apt upgrade<\/strong><\/pre>\n\n\n\n<p>Snap should be already installed and available for use on the majority of the latest Ubuntu distributions. If you have any issues regarding Snap, we recommend installing it by using the command below.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># Install snapd\n<strong>sudo apt install snapd<\/strong><\/pre>\n\n\n\n<p>Guest operating systems running under VMware virtualization have installed a set of tools called open-vm-tools. This project provides a set of useful utilities and drivers to improve the functionality and user experience of virtualization. However, we need to disable this tool for the installation of Microstack to finish successfully. <\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># Disable open-vm-tools\n<strong>sudo systemctl disable open-vm-tools.service<\/strong><\/pre>\n\n\n\n<p>We need to reboot the system for changes to apply.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># Reboot system\n<strong>sudo reboot now<\/strong><\/pre>\n\n\n\n<p>Now we can finally proceed to the actual installation of the Microstack. Official documentation recommends using installation channel beta with dev mode for now. There are many channels and options to be used for installation. To list all of them with descriptions use the command below. <\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># List all channels and available options\n<strong>sudo snap install microstack --help<\/strong>\n\n# Install microstack\n<strong>sudo snap install microstack --devmode --beta<\/strong>\n\nEnsure prerequisites for \"microstack\" are available\nFetch and check assertions for snap \"microstack\" (233)\nMount snap \"microstack\" (233)\nCopy snap \"microstack\" data\nSetup snap \"microstack\" (233) security profiles\nConnect microstack:network-bind to core:network-bind\nSetup snap \"microstack\" (233) security profiles for auto-connections\nRun install hook of \"microstack\" snap if present\nStart snap \"microstack\" (233) services\nRun configure hook of \"microstack\" snap if present\nRun health check of \"microstack\" snap\nmicrostack (beta) ussuri from Canonical\u2713 installed<\/pre>\n\n\n\n<p>To verify the installation use the command below. You should see similar output.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># Verification\n<strong>sudo snap list microstack<\/strong>\n\nName        Version  Rev  Tracking     Publisher    Notes\nmicrostack  ussuri   233  latest\/beta  canonical\u2713  devmode<\/pre>\n\n\n\n<p>After the installation, it is necessary to initialize the Microstack. There are a few options available when initializing. We used the one mentioned and recommended in the official documentation. To list all available options please see the command below.<\/p>\n\n\n\n<p><strong>Important!<\/strong> Make sure that your VM will have the same IP address as was assigned during the initialization process. Once the IP address changes (e.g. after reboot) you may encounter problems. We recommend setting up the IP address statically to avoid issues.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># List all options with descriptions\n<strong>sudo microstack init --help<\/strong>\n\n# Initialize the microstack\n<strong>sudo microstack init --auto --controll<\/strong>\n\n2021-10-21 07:57:06,407 - microstack_init - INFO - Configuring clustering ...\n2021-10-21 07:57:06,669 - microstack_init - INFO - Setting up as a control node.\n2021-10-21 07:57:12,796 - microstack_init - INFO - Configuring networking ...\n2021-10-21 07:57:24,152 - microstack_init - INFO - Opening horizon dashboard up to *\n2021-10-21 07:57:25,960 - microstack_init - INFO - Waiting for RabbitMQ to start ...\nWaiting for 158.193.152.66:5672\n2021-10-21 07:57:35,782 - microstack_init - INFO - RabbitMQ started!\n2021-10-21 07:57:35,783 - microstack_init - INFO - Configuring RabbitMQ ...\n2021-10-21 07:57:37,540 - microstack_init - INFO - RabbitMQ Configured!\n2021-10-21 07:57:37,591 - microstack_init - INFO - Waiting for MySQL server to start ...\nWaiting for 158.193.152.66:3306\n2021-10-21 07:57:49,434 - microstack_init - INFO - Mysql server started! Creating databases ...\n2021-10-21 07:57:52,587 - microstack_init - INFO - Configuring Keystone Fernet Keys ...\n2021-10-21 07:58:15,239 - microstack_init - INFO - Bootstrapping Keystone ...\n2021-10-21 07:58:31,731 - microstack_init - INFO - Creating service project ...\n2021-10-21 07:58:42,962 - microstack_init - INFO - Keystone configured!\n2021-10-21 07:58:43,018 - microstack_init - INFO - Configuring the Placement service...\n2021-10-21 07:59:24,191 - microstack_init - INFO - Running Placement DB migrations...\n2021-10-21 07:59:30,592 - microstack_init - INFO - Configuring nova control plane services ...\n2021-10-21 07:59:53,117 - microstack_init - INFO - Running Nova API DB migrations (this may take a lot of time)...\n2021-10-21 08:00:39,871 - microstack_init - INFO - Running Nova DB migrations (this may take a lot of time)...\nWaiting for 158.193.152.66:8774\n2021-10-21 08:02:09,087 - microstack_init - INFO - Creating default flavors...\n2021-10-21 08:03:01,463 - microstack_init - INFO - Configuring nova compute hypervisor ...\n2021-10-21 08:03:01,464 - microstack_init - INFO - Checking virtualization extensions presence on the host\n2021-10-21 08:03:01,516 - microstack_init - WARNING - Unable to determine hardware virtualization support by CPU vendor id \"GenuineIntel\": assuming it is not supported.\n2021-10-21 08:03:01,516 - microstack_init - WARNING - Hardware virtualization is not supported - software emulation will be used for Nova instances\n2021-10-21 08:03:04,249 - microstack_init - INFO - Configuring the Spice HTML5 console service...\n2021-10-21 08:03:05,189 - microstack_init - INFO - Configuring Neutron\nWaiting for 158.193.152.66:9696\n2021-10-21 08:05:51,571 - microstack_init - INFO - Configuring Glance ...\nWaiting for 158.193.152.66:9292\n2021-10-21 08:07:02,380 - microstack_init - INFO - Adding cirros image ...\n2021-10-21 08:07:08,775 - microstack_init - INFO - Creating security group rules ...\n2021-10-21 08:07:29,512 - microstack_init - INFO - Configuring the Cinder services...\n2021-10-21 08:09:31,094 - microstack_init - INFO - Running Cinder DB migrations...\n2021-10-21 08:09:49,284 - microstack_init - INFO - restarting libvirt and virtlogd ...\n2021-10-21 08:10:12,349 - microstack_init - INFO - Complete. Marked microstack as initialized!<\/pre>\n\n\n\n<p>Great! Your Microstack is now ready for use. Before we jump into creating our first instance, let&#8217;s verify the initialization using the commands below.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># List all available images\n<strong>microstack.openstack image list<\/strong>\n\n+--------------------------------------+--------+--------+\n| ID                                   | Name   | Status |\n+--------------------------------------+--------+--------+\n| 2a61f2e6-ea86-4161-8ea1-17d0955c0717 | cirros | active |\n+--------------------------------------+--------+--------+\n\n# List default flavors\n<strong>microstack.openstack flavor list<\/strong>\n\n+----+-----------+-------+------+-----------+-------+-----------+\n| ID | Name      |   RAM | Disk | Ephemeral | VCPUs | Is Public |\n+----+-----------+-------+------+-----------+-------+-----------+\n| 1  | m1.tiny   |   512 |    1 |         0 |     1 | True      |\n| 2  | m1.small  |  2048 |   20 |         0 |     1 | True      |\n| 3  | m1.medium |  4096 |   20 |         0 |     2 | True      |\n| 4  | m1.large  |  8192 |   20 |         0 |     4 | True      |\n| 5  | m1.xlarge | 16384 |   20 |         0 |     8 | True      |\n+----+-----------+-------+------+-----------+-------+-----------+<\/pre>\n\n\n\n<p>If you got similar outputs as mentioned above, we can move on and create a VM instance. By default the only OS available for use is cirros. If not specified, a tiny flavor will be used when creating an instance. The command below will launch a VM with the name firstTry, cirros OS, one CPU core, 1 GB HDD and 512 MB RAM (see m1.tiny flavor). <\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># List all launch options with descriptions\n<strong>microstack launch --help<\/strong>\n\n# Launch VM instance\n<strong>microstack launch cirros --name firstTry<\/strong>\n\nLaunching server ...\nAllocating floating ip ...\nServer firstTry launched! (status is BUILD)\n\nAccess it with `ssh -i \/home\/user\/snap\/microstack\/common\/.ssh\/id_microstack cirros@10.20.20.34`\nYou can also visit the OpenStack dashboard at http:\/\/10.20.20.1:80<\/pre>\n\n\n\n<p>There are two ways on how to access the created VM. The first way is with the use of SSH, second is with the use of the WEB dashboard. All information needed to access the VM using SSH are provided when you create the instance. In our case, the command is shown below.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># Access VM using SSH\n<strong>ssh -i \/home\/user\/snap\/microstack\/common\/.ssh\/id_microstack cirros@10.20.20.34<\/strong><\/pre>\n\n\n\n<p>To list every created instance and its corresponding status execute the following command.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># List all instances\n<strong>microstack.openstack server list<\/strong>\n\n+--------------------------------------+----------+--------+-----------------------------------+--------+---------+\n| ID                                   | Name     | Status | Networks                          | Image  | Flavor  |\n+--------------------------------------+----------+--------+-----------------------------------+--------+---------+\n| 79bd75d0-24be-4ebb-99d1-6a9d2da613c7 | firstTry | ACTIVE | test=192.168.222.195, 10.20.20.34 | cirros | m1.tiny |\n+--------------------------------------+----------+--------+-----------------------------------+--------+---------+<\/pre>\n\n\n\n<p>If you need more information on OpenStack commands try the command below.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># List OpenStack commands and help<strong>\nmicrostack.openstack --help<\/strong><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"web-access\"><strong>WEB access<\/strong><\/h2>\n\n\n\n<p>The Microstack installation supports access via cloud dashboard. You can log in to the web UI by pointing your browser to the following URL: http:\/\/VM_IP_address<\/p>\n\n\n\n<p>Our IPv4 address was 158.193.152.66 which means that our URL to access the cloud dashboard is: https:\/\/158.193.152.66. We are presented with a login screen.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large is-resized\"><img alt=\"\" decoding=\"async\" src=\"https:\/\/nil.uniza.sk\/wp-content\/uploads\/2021\/10\/Login-Screen-1024x516.png\" class=\"wp-image-6004\" width=\"839\" height=\"423\" srcset=\"https:\/\/nil.uniza.sk\/wp-content\/uploads\/2021\/10\/Login-Screen-1024x516.png 1024w, https:\/\/nil.uniza.sk\/wp-content\/uploads\/2021\/10\/Login-Screen-300x151.png 300w, https:\/\/nil.uniza.sk\/wp-content\/uploads\/2021\/10\/Login-Screen-768x387.png 768w, https:\/\/nil.uniza.sk\/wp-content\/uploads\/2021\/10\/Login-Screen.png 1260w\" sizes=\"(max-width: 839px) 100vw, 839px\" \/><\/figure>\n\n\n\n<p>Login credentials are as follows. The username is &#8222;<strong>admin<\/strong>&#8220; and the password can be obtained by executing the command below. <\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># Print password for WEB dashboard\n<strong>sudo snap get microstack config.credentials.keystone-password<\/strong><\/pre>\n\n\n\n<p>In the output, you should see your login password. <\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># Sample password\nOAEHxLgCBz7Wz4usvolAAt61TrDUz6zz<\/pre>\n\n\n\n<p>After login, you should be able to see your project overview. Now you can enjoy the functionality of the cloud dashboard. <\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img alt=\"\" decoding=\"async\" width=\"1024\" height=\"497\" src=\"https:\/\/nil.uniza.sk\/wp-content\/uploads\/2021\/10\/Overview-1024x497.png\" class=\"wp-image-6007\" srcset=\"https:\/\/nil.uniza.sk\/wp-content\/uploads\/2021\/10\/Overview-1024x497.png 1024w, https:\/\/nil.uniza.sk\/wp-content\/uploads\/2021\/10\/Overview-300x146.png 300w, https:\/\/nil.uniza.sk\/wp-content\/uploads\/2021\/10\/Overview-768x372.png 768w, https:\/\/nil.uniza.sk\/wp-content\/uploads\/2021\/10\/Overview-1536x745.png 1536w, https:\/\/nil.uniza.sk\/wp-content\/uploads\/2021\/10\/Overview.png 1635w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Congratulations! Now you can enjoy your single-node microstack. <\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"problems\"><strong>Problems<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"1\"><strong>1::<\/strong><\/h3>\n\n\n\n<p>Installation using commands below.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">sudo snap install microstack --beta\nsudo snap install microstack --classic\nsudo snap install microstack --edge\n\n2021-10-21 09:32:45,655 - microstack_init - INFO - Configuring clustering ...\n2021-10-21 09:32:49,797 - microstack_init - INFO - Setting up as a control node.\n2021-10-21 09:32:59,667 - microstack_init - INFO - Configuring networking ...\nTraceback (most recent call last):\n  File \"\/snap\/microstack\/233\/bin\/microstack\", line 11, in &lt;module&gt;\n    load_entry_point('microstack==0.0.1', 'console_scripts', 'microstack')()\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/microstack\/main.py\", line 44, in main\n    cmd()\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/main.py\", line 60, in wrapper\n    return func(*args, **kwargs)\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/main.py\", line 227, in init\n    question.ask()\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/questions\/question.py\", line 210, in ask\n    self.yes(awr)\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/questions\/__init__.py\", line 189, in yes\n    enable('ovs-vswitchd')\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/shell.py\", line 162, in enable\n    check('snapctl', 'start', 'microstack.{}'.format(service), '--enable')\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/shell.py\", line 69, in check\n    raise subprocess.CalledProcessError(proc.returncode, \" \".join(args))\n<span style=\"background-color:#fcb900\" class=\"background-color\">subprocess.CalledProcessError: Command 'snapctl start microstack.ovs-vswitchd --enable' returned non-zero exit status 1.<\/span><\/pre>\n\n\n\n<p><strong>Solution: <\/strong>Remove the snap installation using<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># Remove microstack installation\n<strong>sudo snap remove microstack<\/strong><\/pre>\n\n\n\n<p>and try the install process mentioned above.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"2-the-ip-address-of-guest-system-has-changed\"><strong>2:: The IP address of guest system has changed<\/strong><\/h3>\n\n\n\n<p>If the IP address on your VM changes, you might encounter some issues. For example, when you initialized your microstack, the IP address of your VM was 10.20.20.87, but for some reason (DHCP or statically on purpose) the actual IP address is now 10.20.20.80. In this case, you may encounter an error message as shown below. <\/p>\n\n\n\n<p>Error message: <\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><strong>sudo microstack.openstack keypair list<\/strong>\n\nFailed to discover available identity versions when contacting http:\/\/10.20.20.87:5000. Attempting to parse version from URL.\nCould not find versioned identity endpoints when attempting to authenticate. Please check that your auth_url is correct. Unable to establish connection to http:\/\/<span style=\"background-color:#fcb900\" class=\"background-color\">10.20.20.87<\/span>:5000: HTTPConnectionPool(host='10.20.20.87', port=5000): Max retries exceeded with url: \/ (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 113] No route to host'))<\/pre>\n\n\n\n<p><strong>Solution<\/strong><\/p>\n\n\n\n<p>Remove the snap installation with <\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># Remove microstack installation\n<strong>sudo snap remove microstack<\/strong><\/pre>\n\n\n\n<p>Set the IP address statically.<\/p>\n\n\n\n<p>Install Microstack with the guide above.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"3-open-vm-tools-is-not-disabled\"><strong>3:: open-vm-tools is not disabled<\/strong><\/h3>\n\n\n\n<p>As mentioned in the installation guide above, if you are trying to install Microstack on a guest system running on VMware, the OS is probably running open-vm-tools. If so, you may encounter an error during the installation process. <\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">Start snap \"microstack\" (233) services                                         |\nerror: cannot perform the following tasks:\n<span style=\"background-color:#fcb900\" class=\"background-color\">- Start snap \"microstack\" (233) services (systemctl command [start snap.microstack.load-modules.service] failed with exit status 1: Job for snap.microstack.load-modules.service failed because the control process exited with error code.<\/span>\nSee \"systemctl status snap.microstack.load-modules.service\" and \"journalctl -xe\" for details.\n)<\/pre>\n\n\n\n<p>Debugging:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><strong>systemctl status snap.microstack.load-modules.service<\/strong>\n\nsnap.microstack.load-modules.service\n     Loaded: not-found (Reason: Unit snap.microstack.load-modules.service not found.)\n     Active: failed (Result: exit-code) since Thu 2021-10-21 09:10:41 UTC; 3min 4s ago\n   Main PID: 4408 (code=exited, status=1\/FAILURE)\n\nOct 21 09:10:40 ubuntu systemd[1]: Starting Service for snap application microstack.load-modules...\nOct 21 09:10:40 ubuntu microstack.load-modules[4484]: ++ systemd-detect-virt --container\nOct 21 09:10:40 ubuntu microstack.load-modules[4408]: + [[ none == \\n\\o\\n\\e ]]\nOct 21 09:10:40 ubuntu microstack.load-modules[4408]: + modprobe -a vhost vhost-net vhost-scsi vhost-vsock vfio nbd dm-mod dm-thin-pool dm-snapshot iscsi-tcp target-core-mod\n<span style=\"background-color:#fcb900\" class=\"background-color\">Oct 21 09:10:41 ubuntu microstack.load-modules[4486]: modprobe: ERROR: could not insert 'vhost_vsock': Device or resource busy<\/span>\nOct 21 09:10:41 ubuntu systemd[1]: snap.microstack.load-modules.service: Main process exited, code=exited, status=1\/FAILURE\nOct 21 09:10:41 ubuntu systemd[1]: snap.microstack.load-modules.service: Failed with result 'exit-code'.\nOct 21 09:10:41 ubuntu systemd[1]: Failed to start Service for snap application microstack.load-modules.<\/pre>\n\n\n\n<p> <strong>Solution: <\/strong>Remove the snap installation using <\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># Remove microstack installation\n<strong>sudo snap remove microstack<\/strong><\/pre>\n\n\n\n<p>and install Microstack using the guide above.<\/p>\n\n\n\n<p><strong>Note: <\/strong>don&#8217;t miss the part where you need to disable open-vm-tools.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"4-nginx\"><strong>4:: NGINX <\/strong><\/h3>\n\n\n\n<p>If your host OS is running NGINX you may encounter an error during initialization. <\/p>\n\n\n\n<p>Error message:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">2021-10-25 20:00:20,658 - microstack_init - INFO - Mysql server started! Creating databases ...\nTraceback (most recent call last):\n  File \"\/snap\/microstack\/233\/bin\/microstack\", line 11, in &lt;module&gt;\n    load_entry_point('microstack==0.0.1', 'console_scripts', 'microstack')()\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/microstack\/main.py\", line 44, in main\n    cmd()\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/main.py\", line 60, in wrapper\n    return func(*args, **kwargs)\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/main.py\", line 227, in init\n    question.ask()\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/questions\/question.py\", line 210, in ask\n    self.yes(awr)\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/questions\/__init__.py\", line 388, in yes\n    enable('nginx')\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/shell.py\", line 162, in enable\n    check('snapctl', 'start', 'microstack.{}'.format(service), '--enable')\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/shell.py\", line 69, in check\n    raise subprocess.CalledProcessError(proc.returncode, \" \".join(args))\nsubprocess.CalledProcessError: <span style=\"background-color:#fcb900\" class=\"background-color\">Command 'snapctl start microstack.nginx --enable' returned non-zero exit status 1.<\/span><\/pre>\n\n\n\n<p><strong>Solution:<\/strong><\/p>\n\n\n\n<p>Uninstall Nginx with<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><strong>sudo apt-get remove nginx<\/strong>\n<strong>sudo apt-get autoremove<\/strong><\/pre>\n\n\n\n<p>and retry the initialization process. <\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"some-links\">Some links<\/h2>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/microstack.run\/\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/microstack.run\/<\/a><\/li><li><a href=\"https:\/\/ubuntu.com\/openstack\/install\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/ubuntu.com\/openstack\/install<\/a><\/li><\/ul>\n\n\n\n<p><\/p>","protected":false},"excerpt":{"rendered":"<p>Microstack is a pure upstream OpenStack distribution. It includes core OpenStack services and the most popular compute, network and storage options. Installation is fast and easy to perform. My enviroment VMware ESXI 6.7.0 Guest system: server install of Ubuntu 20.04.3 LTS static public IP address 16GB RAM (8GB recommended) 4 vCPU 100GB of HDD (actual&#8230;<\/p>","protected":false},"author":34,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_seopress_robots_primary_cat":"","_seopress_titles_title":"","_seopress_titles_desc":"","_seopress_robots_index":"","_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"categories":[637,1479],"tags":[1483,1484,1485],"class_list":["post-5985","post","type-post","status-publish","format-standard","hentry","category-cloud-en","category-cloud-microstack","tag-cloud","tag-microstack","tag-ubuntu"],"taxonomy_info":{"category":[{"value":637,"label":"Cloud"},{"value":1479,"label":"MicroStack"}],"post_tag":[{"value":1483,"label":"cloud"},{"value":1484,"label":"microstack"},{"value":1485,"label":"ubuntu"}]},"featured_image_src_large":false,"author_info":{"display_name":"Martin Sochor","author_link":"https:\/\/nil.uniza.sk\/en\/author\/martin-sochor\/"},"comment_info":197,"category_info":[{"term_id":637,"name":"Cloud","slug":"cloud-en","term_group":0,"term_taxonomy_id":635,"taxonomy":"category","description":"","parent":0,"count":2,"filter":"raw","cat_ID":637,"category_count":2,"category_description":"","cat_name":"Cloud","category_nicename":"cloud-en","category_parent":0},{"term_id":1479,"name":"MicroStack","slug":"cloud-microstack","term_group":0,"term_taxonomy_id":1477,"taxonomy":"category","description":"","parent":637,"count":2,"filter":"raw","cat_ID":1479,"category_count":2,"category_description":"","cat_name":"MicroStack","category_nicename":"cloud-microstack","category_parent":637}],"tag_info":[{"term_id":1483,"name":"cloud","slug":"cloud","term_group":0,"term_taxonomy_id":1481,"taxonomy":"post_tag","description":"","parent":0,"count":1,"filter":"raw"},{"term_id":1484,"name":"microstack","slug":"microstack","term_group":0,"term_taxonomy_id":1482,"taxonomy":"post_tag","description":"","parent":0,"count":1,"filter":"raw"},{"term_id":1485,"name":"ubuntu","slug":"ubuntu","term_group":0,"term_taxonomy_id":1483,"taxonomy":"post_tag","description":"","parent":0,"count":2,"filter":"raw"}],"_links":{"self":[{"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/posts\/5985","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/users\/34"}],"replies":[{"embeddable":true,"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/comments?post=5985"}],"version-history":[{"count":0,"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/posts\/5985\/revisions"}],"wp:attachment":[{"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/media?parent=5985"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/categories?post=5985"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/tags?post=5985"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}