Ask Your Question

yas's profile - activity

2018-09-18 09:02:29 -0600 received badge  Famous Question (source)
2018-09-14 06:47:56 -0600 received badge  Famous Question (source)
2018-04-27 13:18:41 -0600 received badge  Notable Question (source)
2018-04-27 13:18:41 -0600 received badge  Popular Question (source)
2018-04-01 11:50:25 -0600 answered a question destination port unreachable when pinging 8.8.8.8 from instance

Hello @gaurav_garg.

  1. Make sure that your instances have floating ip addresses.
  2. Make sure that your security rules allow pinging (egress and ingress rules)
  3. Make sure that you configured the instances to use the correct gateway. The gateway should be accessible by the instances and should exist because when you don't specify the gateway ip to be used by the instances OpenStack neutron will pick the first ip address from the provided network and uses it as a Gateway IP (not always the case)
2018-04-01 11:38:39 -0600 answered a question Can't ping/ssh new build instaces but with the old ones everything is ok

Hello @magdallena . Your problem could have different causes. I suggest you try the following tips:

  1. Verify the security groups (make sure that the ingress and the egress rules allow icmp)
  2. create networks using CLI (Horizon has problems creating functional networks (I've experienced that few months ago))
  3. Try to use the default cirros image (maybe the image that you are using is misconfigured snapshot)
  4. Verify the Gateway ip (make sure that you correctly configured the instances to use the correct gateway ip)
  5. If you use Neutron router make sure that the router's interfaces that are linking the instance and the external network are active and the external interface can be pinged from outside Openstack if so try to ping the instance from the eutron router using the following command :

       ip netns exec qrouter-ROUTER_ID ping IP_ADDRESS_OF_THE_INSTANCE
    
  6. Verify that your provider network is correctly configured

2018-03-19 16:35:13 -0600 received badge  Scholar (source)
2018-03-12 07:39:04 -0600 received badge  Famous Question (source)
2018-03-01 03:35:12 -0600 commented answer router external interface is down

Hello @stefws. Could you please paste the characteristics of your networks (vlan ID, types ...) ?

2018-03-01 01:32:33 -0600 received badge  Teacher (source)
2018-02-26 03:34:36 -0600 answered a question router external interface is down

Try to create your public and private networks and your router using the Neutron CLI. Sometimes using Horizon dashboard causes problems.

  1. create external network :

    neutron net-create external-flat-network --provider:network_type flat --provider:physical_network extnet --router:external

  2. create a subnet :

    neutron subnet-create --name public-flat-subnet --enable_dhcp=False --allocation-pool=start=192.168.15.5,end=192.168.15.15 external-flat-network 192.168.15.0/24

  3. create router:

    neutron router-create router-flat-network

  4. setting gateway

    neutron router-gateway-set router-flat-network external-flat-network

  5. creating private network:

    neutron net-create private-management-network

  6. create private subnet

    neutron subnet-create --name private-management-subnet private-management-network 10.0.0.0/8

  7. Finally, connect your new private network to the public network through the router,

    neutron router-interface-add router-flat-network private-management-subnet

2018-02-25 09:55:37 -0600 answered a question vm on multiple networks

Let's assume that you have 2 external networks Network A with the Network address (192.168.255.0/24) and Network B with a network address (192.168.0.0/24). Network A is linked through a neutron router to a private internal Network A_internal with the Network address (10.0.0.0/24) and Network B is linked also through a neutron router to a private internal Network B_internal with the Network address (10.0.1.0/24):

  1. First, start an instance from the dashboard and link it to the private internal network A_internal (Let's assume that it has the following internal address 10.0.0.2

  2. attach a second NIC to the instance (you can do it from the dashboard) (Let's assume that the second NIC has the following internal IP address (from Network B_internal) 10.0.1.8)

Now you will have an instance that is connected to A_internal and B_internal

Adding floating IP addresses

If you want your instance to be reachable from outside you need to add a floating IP address to your instance to be reachable from outside. In the case when you want your instance to be reachable from outside by machines in the Network A and machines in Network B you need to associate two floating IP addresses. You can associate the first floating IP address (from Network A 192.168.255.0/24) from the Horizon dashboard. In order to add a second floating IP address to the second interface which is linked to the network B_internal you need to do the following:

  1. determine the port id of internal ip address 10.0.1.8 using the following command:

    neutron port-list

    copy that id (port_id)

  2. Determine which floating ip address you want to use:

    neutron floatingip-list

    copy the floating ip address (192.168.0.3 for example) id (floating_ip_id)

  3. associate the floating ip to the port id

    neutron floatingip-associate floating_ip_id port_id

Now you should have an instance that is connected to two networks with two floating IPs. In order to the have the second interface fully working you to do the following in the instance (through vnc or ssh) :

echo "1 rt2" >> /etc/iproute2/rt_tables

ip route add 192.168.0.0/24 dev eth1 src 192.168.0.3 table rt2

ip route add default via 192.168.0.1 dev eth1 table rt2

ip rule add from 192.168.0.3/32 table rt2

ip rule add to 192.168.0.3/32 table rt2

Now you might be able to ping the second floating ip address 192.168.0.3 from outside. In the case when you can ping it but cannot ssh it try to use a lower mtu in the instance:

sudo ip link set eth1 mtu 1400

You can add as many interfaces as you want. Hope it helps I use this technique to access multiple instances that are connected to different VLANs from one single management network and it works fine ... (more)

2018-02-24 05:14:54 -0600 received badge  Student (source)
2018-02-23 05:17:07 -0600 received badge  Notable Question (source)
2018-02-22 04:58:22 -0600 answered a question How to access an instance conncted to a VLAN

The solution is to create another network provider. do the necessary changes (configuration files)

  • Launch an instance connected to the VLANi

  • Attach an interface to link the instance to the new created network

  • add a second floating ip (https://mcwhirter.com.au/craige/blog/2015/Attaching_Multiple_Network_Interfaces_and_Floating_IPs_to_OpenStack_Instances_with_Neutron/ (add second floating ip to an instance)) do not tey to add a floating ip address from Horizon it does not allow you to do that.
  • add a second routing table to be able to ssh the instance (https://ask.openstack.org/en/question/11901/how-to-configure-multiple-floating-ip-for-one-instance/ (configure multiple Floating IP for one instance))
  • Sometimes you need to reduce the mtu (maximum transport unit) of the instance NIC (in case when the ping works but the ssh won't)

    sudo ip link set mtu 1400 dev NIC_name

This configuration is tested and it works for me. Hope this help someone in the future

2018-02-18 00:34:08 -0600 received badge  Popular Question (source)
2018-02-16 04:07:36 -0600 commented question How to access an instance conncted to a VLAN

The machine we use to access VMs should not be in any VLAN and must access all VMs connected to different VLANs. I am looking for a solution because I cannot associate two floating IP to an instance.

2018-02-16 04:04:39 -0600 commented question How to access an instance conncted to a VLAN

In another word, each instance belongs to a VLAN. It can ping physical equipment that belongs to its VLAN (I have no problem doing that). My problem is that I cannot access the instance from an external network. I am looking for a solution how to access to a VM in a VLANx through ssh

2018-02-16 04:01:47 -0600 commented question How to access an instance conncted to a VLAN

yes it is. Multiple External Networks (of type VLAN) are created. VLAN with Segmentation ID=100 and VLAN with segmentation ID =101. each of which is linked to a private Openstack network through a router. Each instance has a floating IP.

2018-02-15 09:57:16 -0600 asked a question How to access an instance conncted to a VLAN

I recently installed Openstack pike (using packstack). Network configuration works fine(flat networks, instances works fine). I did the following tasks:

  • Multiple VLANs should be created (done)
  • each VLAN has an instance (done)
  • Instances should ping and access "Network equipment" in the same VLAN (also done)

Each instance should be accessed through ssh from an external network. I faced a problem achieving this because the instances belong to VLANs (one instance per VLAN). each instance has a floating IP from the appropriate VLAN (to be able to communicate with equipment from the same VLAN). Is there any solution to access the instance from a machine that did not belong to the VLAN. (I cannot associate two floating IPs to the same instance)

Thank you

2018-02-15 05:11:11 -0600 answered a question Could not create VLAN (VlanAllocation is not mapped error)

I resolved the issue by reinstalling openstack through packstack and specifying the keyword vlan in the command option or by manually specifying the type drivers in the generated answer file:

packstack --allinone --provision-demo=n --os-neutron-ovs-bridge-mappings=extnet:br-ex --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --os-neutron-ml2-type-drivers=vxlan,flat,vlan

I tried to create a VLAN and it works fine. I hope this answer will help someone in the future. :)

2018-02-14 07:48:47 -0600 commented question Could not create VLAN (VlanAllocation is not mapped error)

@bernd-bausch The bug occurs only when you change the VLAN ranges without updating the neutron database only.In my case, the error persists even after updating the neutron database.

2018-02-14 07:42:02 -0600 commented question Could not create VLAN (VlanAllocation is not mapped error)

Yes I consulted it. It seems that we need to run packstack (during the installation process) with the option --os-neutron-ml2-type-drivers=vxlan,flat,vlan not sure but I will confirm after trying it in the next few hours

2018-02-14 07:38:58 -0600 received badge  Notable Question (source)
2018-02-13 12:54:20 -0600 received badge  Popular Question (source)
2018-02-13 09:00:27 -0600 commented question Could not create VLAN (VlanAllocation is not mapped error)

I tried to leave tenant_network_types empty but the same thing neutron cannot be restarted

2018-02-12 10:06:34 -0600 asked a question Could not create VLAN (VlanAllocation is not mapped error)

I installed Openstack RDO recently and I am able to launch instances with tenant_network_types=vxlan everything works good (ping, ssh ...). I need to create VLANs so I did the following configuration:

/etc/neutron/plugins/ml2/ml2_conf.ini file: (The portion that I changed)

[ml2]
type_drivers=vxlan,vlan,flat
tenant_network_types=vxlan,vlan
mechanism_drivers=openvswitch
[ml2_type_vlan]
 network_vlan_ranges =extnet:100:200

[ml2_type_vxlan]
vni_ranges=10:100
vxlan_group=224.0.0.1

/etc/neutron/plugins/ml2/openvswitch_agent.ini file (I did not change it)

[ovs]
bridge_mappings=extnet:br-ex

After the changes made on /etc/neutron/plugins/ml2/ml2_conf.ini I could not restart neutron:

sudo service neutron-server restart

RESULT:

Redirecting to /bin/systemctl restart neutron-server.service
Job for neutron-server.service failed because the control process exited with error code. See "systemctl status neutron-server.service" and "journalctl -xe" for details.


Feb 12 16:58:15 localhost.localdomain neutron-server[11967]: Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibilit
Feb 12 16:58:18 localhost.localdomain systemd[1]: neutron-server.service: main process exited, code=exited, status=1/FAILURE
Feb 12 16:58:18 localhost.localdomain systemd[1]: Failed to start OpenStack Neutron Server.
-- Subject: Unit neutron-server.service has failed

After consulting the neutron log files I found this error:

'neutron.objects.plugins.ml2.vlanallocation.VlanAllocation' is not mapped

Thank you

2018-02-12 07:13:50 -0600 answered a question Cannot launch instance with custom video RAM setting

I fixed my issue by adding a new custom nova flavor with the custom metadata value hw_video:ram_max_mb. then I update the image metadata using the following command:

glance image-update --property hw_video_model=vga --property hw_video_ram=64 IMAGE-ID

Then the instance is launched successfully.

source: https://docs.openstack.org/python-glanceclient/latest/cli/property-keys.html (glance property keys)

2018-02-12 05:04:04 -0600 asked a question Cannot launch instance with custom video RAM setting

I recently installed Openstack pike using packstack. I successfully configured networking. I can create instances on connect to them using ssh. My problem is when I tried to run an instance with custom RAM setting I got the following error:

Message: No valid host was found.

Code: 500

Details File "/usr/lib/python2.7/site-packages/nova/conductor/manager.py", line 1031, in schedule_and_build_instances instance_uuids) File "/usr/lib/python2.7/site-packages/nova/conductor/manager.py", line 626, in _schedule_instances request_spec, instance_uuids) File "/usr/lib/python2.7/site-packages/nova/scheduler/utils.py", line 586, in wrapped return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/nova/scheduler/client/__init__.py", line 52, in select_destinations instance_uuids) File "/usr/lib/python2.7/site-packages/nova/scheduler/client/__init__.py", line 37, in __run_method return getattr(self.instance, __name)(*args, **kwargs) File "/usr/lib/python2.7/site-packages/nova/scheduler/client/query.py", line 33, in select_destinations instance_uuids) File "/usr/lib/python2.7/site-packages/nova/scheduler/rpcapi.py", line 137, in select_destinations return cctxt.call(ctxt, 'select_destinations', **msg_args) File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/client.py", line 169, in call retry=self.retry) File "/usr/lib/python2.7/site-packages/oslo_messaging/transport.py", line 123, in _send timeout=timeout, retry=retry) File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 566, in send retry=retry) File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 557, in _send raise result

I uploaded the image metadata using the following command:

glance image-update --property hw_video_model=vga --property hw_video_ram=64 CENTOS-IMAGE-ID

RESULT:

+------------------+--------------------------------------+
| Property         | Value                                |
+------------------+--------------------------------------+
| checksum         | 9eca98f4b3ad7e6dd4390a9d181381c9     |
| container_format | bare                                 |
| created_at       | 2018-02-09T20:44:20Z                 |
| description      | centos7_x86_64                       |
| disk_format      | qcow2                                |
| hw_video_model   | cirrus                               |
| hw_video_ram     | 64                                   |
| id               | f17a4cf5-99b0-4ff7-b4b6-f7a9cb78a61b |
| min_disk         | 0                                    |
| min_ram          | 0                                    |
| name             | centos                               |
| owner            | 7a130a48c0dc48f88c18a4677e151ab0     |
| protected        | False                                |
| size             | 1004994560                           |
| status           | active                               |
| tags             | []                                   |
| updated_at       | 2018-02-12T16:23:21Z                 |
| virtual_size     | None                                 |
| visibility       | public                               |
+------------------+--------------------------------------+

I also tried all hardware video models

vga, cirrus, vmvga and qxl

but none of them is working.

2017-07-25 00:41:19 -0600 received badge  Notable Question (source)
2017-07-25 00:41:19 -0600 received badge  Famous Question (source)
2017-03-14 10:41:34 -0600 received badge  Famous Question (source)
2016-12-12 11:31:10 -0600 commented question I build a openstack instance,but when I ssh to it with sshkey ,need password?

if it is cirros use cubswin:) if not please provide us with the error you've encountered

2016-12-12 11:26:26 -0600 commented question cant ssh into instance using key..

try

 ssh-keygen -R 141.30.74.137

then

 ssh -v -i your_key.pem centos@141.30.74.137
2016-12-12 11:19:44 -0600 received badge  Commentator
2016-12-12 11:19:44 -0600 commented question Error: Failed to launch instance [Error: No valid host was found. ].

wow this error again try to change the hypervisor (from kvm to qemu) in the nova.conf file under /etc/nova [libvirt] virt_type =qemu then restart nova services

2016-11-27 03:59:22 -0600 commented question cannot create image

glance image-create --name "cirros" --disk-format qcow2 --container-format bare --is-public False < ./cirros.qcow2 Try this

2016-11-18 09:11:05 -0600 commented answer packet loss metric openstack ceilometer

Thank you @Shaoman for your answer i'll try it

2016-11-04 15:26:26 -0600 received badge  Popular Question (source)
2016-11-02 02:14:10 -0600 commented answer nova scheduler: No valid host was found. There are not enough hosts available.

This is a well known issue try to change kvm by qemu in the nova.conf file (/etc/nova/nova.conf)

2016-10-28 17:59:55 -0600 received badge  Popular Question (source)