I deployed a private cloud in openstack with the help of packstack, Everything is working fine, I can create new instances, Launch it, use it to install software from internet and delete it, All the set up is running on my Local machine as virtual machine in vmware, I created a router, a public and a private network. I can access Internet from my instance as well as from my main server. Basically everything is working as expected. But I can only access my cloud from the network in which I am using it.
I want to Access my horizon dashboard and my instance from an external network, how can I do this? currently I can only access my cloud from ip as http://10.0.5.2/dashboard but I want to assign a public ip to my cloud.
From the dashboard/horizon " http://10.0.5.2/dashboard " link it means you are using the NAT/NAT network/any other internal network IP for OpenStack setup. So you can't access it outside the VMware VM.
If you need to access the horizon from outside VMware:
Create two interfaces in VM, one with NAT and other with Host-Only networking
Use the NAT IP for internet and Host-Only networking IP as HOST_IP for openstack setup.
Install the openstack and then you will have horizon link as http://Host-only_network_IP/dashboard
Then you can able to access the openstack from outside of VMware VM
Related
We're setting up our own openstack cloud using OVH dedicated sever. We couldn't connect to our openstack instances using public ips. Because OVH allow traffic based on MAC-IP_Address binding match.
We've found this link useful but this is quite outdated.
=> https://dohuyhoang.github.io/openstack/ovh/neutron/2014/07/07/Configure-OpenStack-network-on-OVH.html
We use CentOS 7.7 and the openstack release is centos-release-openstack-stein-1-1.el7.centos.noarch
We have already configure xx.xx.xx.xx/29 public ip pool in neutron.However it doesn't connect from external world.
Anyone has experience in setting up vRack for OpenStack cloud environment ?
Thanks in advance.
If you're using vRack, you'll not need to used the MAC to IP Address static binding. However, you'll be limited in the traffic you can use to Internet (two years ago, the public IP traffic inside a vRack was limited to 300 or 500Mbps for the whole vrack.
To use vRack, you'll need compatible server (check OVH website for compatibility) and setup the secondary network Interface (vRack compatible servers come with at least two network card, one for the management traffic and one for the vRack traffic) and used it with neutron to host your IP pool.
You'll then need to move the IP Pool to your vRack in the OVH Control Panel.
In a vmware environment, should the external address become populated with the VM's (or hosts) ip address?
I have three clusters, and have found that only those using a "cloud provider" have external addresses when I run kubectl get nodes -o wide. It is my understanding that the "cloud provider" plugin (GCP, AWS, Vmware, etc) is what assigns the public ip address to the node.
KOPS deployed to GCP = external address is the real public IP addresses of the nodes.
Kubeadm deployed to vwmare, using vmware cloud provider = external address is the same as the internal address (a private range).
Kubeadm deployed, NO cloud provider = no external ip.
I ask because I have a tool that scrapes /api/v1/nodes and then interacts with each host that is finds, using the "external ip". This only works with my first two clusters.
My tool runs on the local network of the clusters, should it be targeting the "internal ip" instead? In other words, is the internal ip ALWAYS the IP address of the VM or physical host (when installed on bare metal).
Thank you
Baremetal will not have an "extrenal-IP" for the nodes and the "internal-ip" will be the IP address of the nodes. You are running your command from inside the same network for your local cluster so you should be able to use this internal IP address to access the nodes as required.
When using k8s on baremetal the external IP and loadbalancer functions don't natively exist. If you want to expose an "External IP", quotes because most cases it would still be a 10.X.X.X address, from your baremetal cluster you would need to install something like MetalLB.
https://github.com/google/metallb
I'm having trouble creating a network link between my Hyper-V host machine and its VM (both are running Windows 10).
I created an virtual external switch for both the host and VM so that both can access the internet and download programs and Windows updates, but I could not get them to communicate with each other directly. My research told me to create a virtual internal switch in Hyper-V and then have the devices be able to access each other that way (presumably by doing something like typing \\host_machine_IP\c$ into an explorer window once the network connection had been made). But once I created the virtual internal switch and assigned static IP address to both the host and VM on it, I still could not ping the host from the VM, or vice versa.
Am I missing a step? Let me know what more details you guys need.
By default you would have Windows Firewall blocking your communications until you confirm network profile to be other than Public. Try selecting a home\work network location profile via Control Panel > Network and Sharing canter. Or disable the firewall on the machine you try connecting to. Otherwise you should have no communication problem with the setup described, provided the subnet is the same for both machines.
I am running a windows in oracle virtualbox and my virtualbox is inside Amazon EC2. Is it possible to access my IIS server which is inside virtualbox using a public IP address. I have been trying all these time. I created two network interfaces and assigned one to my EC2 and the other one to Virtual box. but it's not assigning a IP and it says unidentified network. Is it possible to do this or not?
I have a dedicated virtual debian server running with my website, and now have a copy of that so that I can try some configurations by running it virtually on my own PC. It runs fine, but I'm unable to access the machine through http.
The problem is that my machine has a fixed ip, something like 194.247.x.x . My home network however has computers in the range of 192.168.1.x
Is it possible to not change anything in my virtual machine and still configure vmware networking so that I'm able to access the websites it's running?
The only way I can see this happening for you is to use NAT (Network Address Translation) between your home network and your VM.
To do this, you could use a free software based router - something like Vyatta (www.vyatta.org) - and create a VM with two NICs - one with an IP on your home network, and the other with an IP on the same network as your VM. You then configure NAT to translate your home IP to your web server IP and then you're done.
There's nothing 'de-facto' VMware that will allow you to do this (other than using vShield - which will do NAT'ing anyway)...