Ask Your Question

Harry996's profile - activity

2019-09-02 07:39:15 -0500 received badge  Notable Question (source)
2019-08-30 16:44:43 -0500 received badge  Popular Question (source)
2019-08-30 06:41:16 -0500 commented question [Desperately asking for help] Instances cannot ping to the internet and cannot use SSH

@Bernd Bausch any comments on this?

2019-08-30 05:29:49 -0500 commented answer openstack instance can not access internet

Wow so in Openstack they have a configuration for PUBLIC_INTERFACE. Do you know a similar configuration for PUBLIC_INTERFACE in multiple nodes? I mean I installed Openstack manually.

2019-08-30 00:31:51 -0500 commented question [Desperately asking for help] Instances cannot ping to the internet and cannot use SSH

Also, I cannot ping IP Floating (192.168.200.0/24). The interfaces are always down.

2019-08-30 00:29:06 -0500 commented question [Desperately asking for help] Instances cannot ping to the internet and cannot use SSH

I added ovs-vsctl add-port br-ex enp0s10 in which enp0s10 is an interface that using NAT Network (not NAT only) adapter on VirtualBox (here I set it as 192.168.200.0/24) as provider network but still couldnt ping the internet.

2019-08-29 21:20:15 -0500 commented question [Desperately asking for help] Instances cannot ping to the internet and cannot use SSH

yes, Instances can connect to each other. I changed the "public" network as 192. using NAT Network in virutalbox. But I still cannot ping to the internet. the interfaces are always down. Also, IDK I create flat network in provider network is correct or not, or it should be local or vxlan?

2019-08-29 12:02:47 -0500 asked a question [Desperately asking for help] Instances cannot ping to the internet and cannot use SSH

Hello everyone, I spent a whole day just tried to ping the internet from the instances that I created. But there was no luck!

The list below is all configuration for each node. I don't know what part I did wrongly which I could not ping to the internet and couldn't ssh to the instances as well. Please Help me, I will be very appreciated!

  1. This is Network Topology of my setup https://i.ibb.co/XsL26J3/Screenshot-f...
  2. The interfaces are always down https://i.ibb.co/vds5tqW/Screenshot-f...
  3. ml2_conf.ini on controller node

    root@controller:~# grep -o '^[^#]*'
    /etc/neutron/plugins/ml2/ml2_conf.ini 
    [DEFAULT]
    [l2pop]
    [ml2]
    type_drivers = flat,vlan,vxlan
    tenant_network_types = vxlan  
    extension_drivers = port_security  
    mechanism_drivers = opendaylight_v2
    [ml2_odl]
    enable_dhcp_service = False  
    port_binding_controller = pseudo-agentdb-binding  
    password = admin  
    username = admin  
    url = http://10.10.10.100:8181/controller/nb/v2/neutron  
    [ml2_type_flat]
    flat_networks = *
    [ml2_type_geneve]
    [ml2_type_gre]
    [ml2_type_vlan]
    [ml2_type_vxlan]
    vni_ranges =1:1000
    [securitygroup]
    enable_ipset = true
    firewall_driver = neutron.agent.not.a.real.FirewallDriver
    
  4. openstack network agent list

controller@controller:~$ openstack network agent list

+--------------------------------------+----------------+------------+-------------------+-------+-------+------------------------------+
| ID                                   | Agent Type     | Host       | Availability Zone | Alive | State | Binary                       |
+--------------------------------------+----------------+------------+-------------------+-------+-------+------------------------------+
| 0ddccc98-5d64-4235-9fed-ed90016fe4fd | DHCP agent     | compute2   | nova              | :-)   | UP    | neutron-dhcp-agent           |
| 12da6f0a-3b6c-476d-a49a-ab7ddf4b5b3c | ODL L2         | controller | None              | :-)   | UP    | neutron-odlagent-portbinding |
| 1ec6b8d2-ca34-40c8-8105-8fe868577535 | ODL L3         | network    | None              | :-)   | UP    | neutron-odlagent-portbinding |
| 2e8fdc4f-5647-4b8e-94af-83f3dcbfb790 | ODL L2         | compute1   | None              | :-)   | UP    | neutron-odlagent-portbinding |
| 36901483-0c5f-47ca-a8b1-16326c95944d | Metadata agent | network    | None              | :-)   | UP    | neutron-metadata-agent       |
| 3ee285dd-dfd1-491a-8e51-e616574607ce | Metadata agent | compute3   | None              | :-)   | UP    | neutron-metadata-agent       |
| 5ac2dbc4-ed92-40d3-8854-e3544a497535 | Metadata agent | controller | None              | :-)   | UP    | neutron-metadata-agent       |
| 674dfbdb-8f37-40ff-bc59-98da0db72f40 | DHCP agent     | compute3   | nova              | :-)   | UP    | neutron-dhcp-agent           |
| 813413b4-1752-474b-bdf9-96a234935e70 | DHCP agent     | network    | nova              | :-)   | UP    | neutron-dhcp-agent           |
| 895318f5-2d5b-4e04-bbfe-9dd0195ab92e | Metadata agent | compute1   | None              | :-)   | UP    | neutron-metadata-agent       |
| 8ca187fa-654d-4251-a52d-748293f29e56 | ODL L3         | controller | None              | :-)   | UP    | neutron-odlagent-portbinding |
| bca2843e-fc00-4efd-ba05-822b08c73ff2 | ODL L2         | compute2   | None              | :-)   | UP    | neutron-odlagent-portbinding |
| d3f189fd-3793-4f0e-acc5-f69310f0e08b | Metadata agent | compute2   | None              | :-)   | UP    | neutron-metadata-agent       |
| daaced5b-0066-47b4-95bf-52d299966b27 | ODL L2         | network    | None              | :-)   | UP    | neutron-odlagent-portbinding |
| e494efd1-4609-4e79-bc8b-ab1c42175077 | DHCP agent     | compute1   | nova              | :-)   | UP    | neutron-dhcp-agent           |
| ee5423ee-49bf-4021-8c05-1a8fb5c161c0 | ODL L2         | compute3   | None              | :-)   | UP    | neutron-odlagent-portbinding |
+--------------------------------------+----------------+------------+-------------------+-------+-------+------------------------------+

5 . ovs-vsctl show on controller node and compute node (same)

root@controller:~# ovs-vsctl show
39036e06-7866-4c47-b395-43b47c530ebe
    Manager "ptcp:6641:127.0.0.1"
    Manager "tcp:10.10.10.100:6640"
        is_connected: true
    Bridge br-int
        Controller "tcp:10.10.10.100:6653"
            is_connected: true
        fail_mode: secure
        Port br-ex
            Interface br-ex
                error: "could not open network device br-ex (No such device)"
        Port br-ex-patch
            Interface br-ex-patch
                type: patch
                options: {peer=br-ex-int-patch}
        Port br-int
            Interface br-int
                type: internal
        Port "tun693ebc93a18"
            Interface "tun693ebc93a18"
                type: vxlan
                options: {key=flow, local_ip="10.10.10.11", remote_ip="10.10.10.12"}
                bfd_status: {diagnostic="No Diagnostic", flap_count="1", forwarding="true", remote_diagnostic="Control Detection Time Expired", remote_state=up, state=up}
        Port "tun3c2754eee1d"
            Interface "tun3c2754eee1d"
                type: vxlan
                options: {key=flow, local_ip="10.10.10.11", remote_ip="10.10.10.14"}
                bfd_status: {diagnostic="No Diagnostic", flap_count="1", forwarding="true", remote_diagnostic="Control Detection Time Expired", remote_state=up, state=up}
        Port "tun84591bdc4c8"
            Interface "tun84591bdc4c8"
                type: vxlan
                options: {key=flow, local_ip="10.10.10.11",remote_ip="10.10.10.15"}
                bfd_status: {diagnostic="No Diagnostic",flap_count="1", forwarding="true",remote_diagnostic="Control Detection Time Expired", remote_state=up, state=up}
        Port "tun5a675391011"
            Interface "tun5a675391011"
                type: vxlan
                options: {key=flow, local_ip="10.10.10.11", remote_ip="10.10.10.13"}
                bfd_status: {diagnostic="No Diagnostic", flap_count="1", forwarding="true", remote_diagnostic="Control Detection ...
(more)
2019-08-26 10:42:02 -0500 received badge  Notable Question (source)
2019-08-26 00:54:14 -0500 received badge  Popular Question (source)
2019-08-25 22:19:51 -0500 commented answer Your CPU does not support KVM extention

Could you tell me where can I find the nova-novncproxy? I tried to find in /etc/nova but I did not see it.

2019-08-25 18:59:01 -0500 commented answer Your CPU does not support KVM extention

I set novncproxy_base_url = http://10.10.10.11:6082/vnc_auto.html as 10.10.10.11 is my management IP of controller node. But When I create an instance the console said 10.10.10.11 refused to connect. I couldnt go to the instance's console.

2019-08-25 18:56:40 -0500 received badge  Popular Question (source)
2019-08-25 08:10:52 -0500 commented question why novncproxy_base_url is required on compute nova.conf

Good question but no answers :(

2019-08-25 03:47:03 -0500 commented answer Your CPU does not support KVM extention

I used this command to show url link openstack console url show pussy --xvpvnchttp://127.0.0.1:6081/console?token=2... but I couldnt access this link, it said that refused to connect.

2019-08-25 03:31:31 -0500 commented answer Your CPU does not support KVM extention

The instance is up and running but when I clicked to console to open vm on horizon it said 127.0.0.1 refused to connect.

2019-08-25 03:10:46 -0500 commented answer Your CPU does not support KVM extention

Voila. OMG somehow I missed configure nova-compute.conf. It cost me several hours to investigate this :(. Thank you @Bernd.

2019-08-25 01:39:34 -0500 commented answer Your CPU does not support KVM extention

Oh sorry. This error (followed from this post https://ask.openstack.org/en/question...)

2019-08-25 01:31:06 -0500 commented answer Your CPU does not support KVM extention

Thank you. Followed the guideline but still got the same error. I couldn't create an instance.

2019-08-24 21:48:27 -0500 commented answer Your CPU does not support KVM extention

I see. As you said, Now I need to configure qemu instead of kvm right? Could you please tell me what I need to do to install and configure qemu?

2019-08-24 20:53:57 -0500 asked a question setup openstack network interface on qemu/kvm

Hello, its me again. So because of VirtualBox does not support KVM virtualization on Intel CPUs then I thought I have to mitigate multiple nodes from VirtualBox to qemu/kvm virt-manager. But I dont know how to create network interface same Virtual Box network adapter (Host-Only, Internal Network, NAT) on qemu/kvm virt-manager for Network Node.

2019-08-24 19:58:41 -0500 commented answer Your CPU does not support KVM extention

You're right! I am using Intel CPUs. But why I could run an instance in devstack installed another VM on VirtualBox but the multiple nodes could not.

2019-08-24 19:27:12 -0500 commented answer Your CPU does not support KVM extention

Well the problem is that I am using VirtualBox 6.0.6 but I checked egrep -c '(vmx|svm)' /proc/cpuinfo still got 0 on my controller node and compute node.

2019-08-24 11:26:27 -0500 asked a question Your CPU does not support KVM extention

On my host machine, I checked this command egrep -c '(vmx|svm)' /proc/cpuinfo and I got 12 which means KVM acceleration can be used. But In my Controller Node and Compute Node, I checked the same command but I got 0 which means KVM acceleration cannot be used. why this occurred? I am using VirtualBox to install multiple nodes

2019-08-24 06:17:04 -0500 asked a question Error: Exceeded maximum number of retries. Exceeded max scheduling attempts 3 for instance

Hello, I am trying to create an instance in OPENSTACK. But I got this error:

Error: Exceeded maximum number of retries. Exceeded max scheduling attempts 3 for instance c022d46c-464a-42ed-8250-71a0a9cb4a0e. Last exception: invalid argument: could not find capabilities for domaintype=kvm

I am very new to this. Please tell me what should I check and how can I fix this error? Thank you very much!

2019-08-24 04:53:43 -0500 asked a question why port tun automatically create after restarted

Hi tried to delete those ports that I don't use anymore. but after restarting openvswitch service, those ports that I've just deleted automatically created. why? Here is the sample of my ovs0vsctl show

root@network:~# ovs-vsctl show
f1fba31d-5ad7-4d96-a26c-2d7983d23da3
    Manager "ptcp:6641:127.0.0.1"
    Manager "tcp:10.10.10.100:6640"
        is_connected: true
    Bridge br-int
        Controller "tcp:10.10.10.100:6653"
        fail_mode: secure
        Port "tun185d1d14b3c"
            Interface "tun185d1d14b3c"
                type: vxlan
                options: {key=flow, local_ip="10.10.10.12", remote_ip="10.0.0.33"}
                bfd_status: {diagnostic="No Diagnostic", flap_count="0", forwarding="false", remote_diagnostic="No Diagnostic", remote_state=down, state=down}
        Port "tun5c25ecda721"
            Interface "tun5c25ecda721"
                type: vxlan
                options: {key=flow, local_ip="10.10.10.12", remote_ip="10.0.0.11"}
                bfd_status: {diagnostic="No Diagnostic", flap_count="0", forwarding="false", remote_diagnostic="No Diagnostic", remote_state=down, state=down}
        Port br-ex-patch
            Interface br-ex-patch
                type: patch
                options: {peer=br-ex-int-patch}
        Port "tun2c49a64907d"
            Interface "tun2c49a64907d"
                type: vxlan
                options: {key=flow, local_ip="10.10.10.12", remote_ip="10.0.0.32"}
                bfd_status: {diagnostic="No Diagnostic", flap_count="0", forwarding="false", remote_diagnostic="No Diagnostic", remote_state=down, state=down}
2019-08-24 04:08:00 -0500 commented answer Problem creating flat network: "Unknown provider:physical_network physnet1"

That just works fine :D

2019-08-23 07:23:52 -0500 commented question Openstack neutron l3 agent not alive

I am about to give up. :(( Could you help me, when l3-agent is dead, what things I need to check? I check the l3-agent using journalctl and check all the answers in Vikash Kathirvel's post but still got l3-agent not alive in openstack network agent list eventhough it is still up n running.

2019-08-23 02:25:29 -0500 received badge  Popular Question (source)
2019-08-23 00:45:17 -0500 commented question Openstack neutron l3 agent not alive

@Bernd Bausch Do you think that I should have installed l3-agent on controller node instead of network node?

2019-08-23 00:45:17 -0500 received badge  Commentator
2019-08-23 00:35:19 -0500 commented question Openstack neutron l3 agent not alive

And configuration as well. All same.

2019-08-22 22:46:18 -0500 commented question Openstack neutron l3 agent not alive

Yes. I have the same symptoms and error messages exactly him.

2019-08-22 09:47:13 -0500 received badge  Student (source)
2019-08-22 09:22:11 -0500 commented answer Openstack neutron l3 agent dead

I dont have any q-l3-plugin service running on Controller Node :((