How can I access my VMs using names instead of IP addresses?

The VM-s are seen simultaneously in several networks, at least in your „private” LAN and in public Internet. By default the public addresses (floating-ip, 185.48.x.x) have no associated names. You may assign such names from your DNS domain or you may request a name from us (as an additional service). The names provided by us have the following format: computer_name.users.creodias.eu, where "computer_name" is chosen by you.

If you need the name just to access the machine from your office workstation, the simplest way is to add its address and friendly name to /etc/hosts.

The VM-s in a given project share common „private” network – by default it is 192.168.0.x. You may create additional private networks with any addresses you like. However, they will not be equipped with DNS. If the machines are expected to recognize other by their names, either /etc/hosts need to be created and copied to all machines, or private DNS may be run on one of them. Moreover, although the addresses are dynamically assigned they are constant – they do not change from the moment of creation to deletion of the machine.

 

OpenStackClient is very useful tool to gain a powerful management of our projects in Command Line Interface.

It implements new features and advantages: You can run the commands from the CLI, or include prepared scripts in Python to automate the functionality of your cloud storage.

Moreover we could reach our OpenStack access on any computer if we inset credentials (username and password).

Eventually everyone may admit that generally OpenStackClient provides more opportunities to look into our compute facility deeply and much more precisely.

 

 

In Microsoft Family Systems the case of implementation of serviceable CLI client is more complicated than in Linux Distributions. Configuration file for Openstack is not prepared for clear injection into CMD or Powershell and the "export" syntax is not recognized. Hence we need to install bash emulators.

To supply our operating system into Manageable OpenstackClient we have to accessorize our Windows in:

List:

  • Python 2 or 3 ( this tutorial is prepared for 2.7.8 version)
  • Pip (tool for installing python packages)
  • GIT for Windows or Cygwin64 Terminal
  • Microsoft Visual C++ Compiler for Python 2.7

     

Step one:

Let's start with the Python Installation. Move on to official website with all stable releases:

www.python.org

 

 

Head to Downloads and next to Windows while the list is currently enrolled.

Pick up the latest version for Python 2. In our case it is seen 2.7.15.