I created a vm in horizon, I use dhcp server of neutron to allocate IP and the following is the horizon show:
But in my vm console,it display:
so i want to know why it don't have an ip address?
Check out neutron logs, it should give some clues. Mostly the log file will be located in /var/log folder of neutron host.
Probably you should also check for "dnsmasq" related logs and errors in /var/log/ folders
Related
I installed Octavia service in Openstack and it worked! But in my openstack port list there are two related ports (amphora and loadbalancer) and LB port is down! What's wrong?
Note that my loadbalancer has active and online statuses, but I don't know why its port is down or what is its effect.
Summary: This is completely normal and how Octavia manages high availability.
Octavia uses a VIP address that can be moved between amphora (service VMs) for recovery from hypervisor failures. Inside the amphora, the port gets this VIP address assigned as a "secondary" IP.
In neutron, this address is handled with a VIP port, which reserves the VIP IP address (so we can move it to a replacement amphora VM if needed). This port is in the "DOWN" status.
To allow multiple IPs on a neutron port you have to use what neutron calls an "allowed address pair". If you look at the details of the port that is up, you will see the "allowed address pair" setting on the port that references the VIP port information and IP.
I am running Devstack on my machine and i would like to know if it is possible to ping an instance from Host. The default external network of Devstack is 172.24.4.0/24 and br-ex on Host has the IP 172.24.4.1. I launch an instance using the internal network of Devstack (192.168.233.0/24) and the instance gets the IP 192.168.233.100. My Host's IP is 192.168.1.10. Is there a way to ping 192.168.233.100 from my Host? Another thing i thought is to boot up a VM directly to the external network (172.24.4.0/24) but the VM does not boot up correctly. I can only use that network for associating floating IP's.
I have edited the security group and i have allowed ICMP and SSH, so this is not a problem.
Am curious about how OpenStack handles IP configuration, i have a complete working openstack dashboard with a static IP of 192.168.1.73/24 and i want to change it to something else. Running as a VM using RHEL\Scientific Linux\Centos 7.5 as the Guest Host.
Am running openstack-queens (repo) -- /etc/yum.repos.d
What i've tried and failed...
1.Changing static IP in /etc/sysconfig/network-scripts/ifcfg-eth0
2.Made sure in /etc/resolv.conf reflects my new configuration.
2.Replacing IP configuration in packstack-answerfile for the compute node and the rest of the services i've configured.
What i have noted!!!
1.systemctl status -l redis.service --- fails when i change the IP configuration, this is active (running) with its initial configuration.
2.Virtualization daemon also fails during boot--(running as KVM)
How "deep" does Networking go for OpenStack and how do i achieve my goals of setting a different IP and still have my dashboard up and running?
This was Easy. What I missed to do is to only re-run my packstack answerfile.
First, change the IP address on the machine in /etc/sysconfig/network-scripts/ifcfg-br-ex thats if you already gone ahead in setting up networking for your OpenStack Env.
If you have done a backup of your ifcfg-eth0, revert to it and change to new IP configuration.
Second, Replace new IP configuration in packstack-answerfile for the compute node and the rest of the services configured.
Last But not Least: Requires Steady Internet Connection!!!
Last Step is to re-run your packstack-answerfile with the new IP configuration.
I am facing a strange issue these days. I have a list of IP addresses which I want to connect to during the deployment using Jenkins. Now what is happening is, if I am deploying at one IP address (remote machine but in same location) in my local location server, I can successfully do that. But If I am trying to deploy to an IP address (remote machine in other country/region) It is throwing the error, saying
Error : Ip address XYZ is not reachable or is invalid.
Please be notified that I am able to get the response from the machine when I ping it using:
ping XYZ
But while trying to deploy on it using Jenkins, I am not.
Please let me know if there's any solution for this problem.
There isn't enough data points but you can look for these things
1. IP address, Check if all three machines are in same n/w (Jenkins Server, target and your machine)
You can check it with IP address of each machine
2. check Gateway set for Jenkins server
3. Best way if feasible is to ssh / rdp to your Jenkins server and try running your command manually that will give you
Local machine get loopback address(127.0.0.1), so it will be reachable or any local machine having IP address with same subnet mask thats called LAN.
When you are reaching out to remote machine, either it should be public IP address(visible to everyone in the world) or you must have connect to that Area-Network via VPN, this is called tunnelling to remote over the WAN (wide area network). Their(remote location) again, you will notice that all the IP address have same subnet mask as you have on the local machine.
So their could be be IP address duplication case in VPN scenario, where you are bale to ping but not able to reach. This is because, IP address is assigned to other machine but not you yours and ping responses are coming from that other machine. That means your machine is in failed to resolve ARP and in dormant state.
I would like to configure my openstack to use IP's from the same network as my physical server. I do not want to use dhcp or floating IP's.
neutron net-create --tenant-id TENANT-ID --shared sharednet1 --provider:network_type flat --provider:physical_network physnet1
neutron subnet-create sharednet1 10.68.10.0/24 --gateway-ip 10.68.10.11 --diable-dhcp
When create an instance , Nova should able to 'inject a ip' to instance.
Is that possiable ?
How to configure it?
Please follow the basic installation guidehttp://docs.openstack.org/ for grizzly or havana in the networksection.
You can use the static IPs of your physical servers by hard coding the static values in /etc/network/interface files so that when you create your router, it will use that IP