Ask Your Question

Lily Xing's profile - activity

2016-01-27 22:04:32 -0600 received badge  Famous Question (source)
2015-09-09 09:57:52 -0600 received badge  Notable Question (source)
2015-09-09 02:33:04 -0600 answered a question cloud-init cannot find OpenStack datasource

Here is an answer from cloudbase:

Clear text passwords are bad for security. Nova does not pass them in the http metadata, only in configdrive as you already noticed.

The reason why this works on KVM, is that KVM injects the password in the guest file system before booting it. One of the reasons why we don't support that on Hyper-V is that the hosts wouldn't know how to deal with Linux filesystems.

2015-09-09 02:26:28 -0600 received badge  Popular Question (source)
2015-09-08 03:54:02 -0600 commented answer Help network configuration

Go through google, and you will find a lot of information similar to your problem. Most of them point to a failed installation. Maybe it's caused by your image, not related to OpenStack. Could you give cirros a try?

2015-08-25 02:10:58 -0600 received badge  Student (source)
2015-08-24 22:08:22 -0600 answered a question Help network configuration

First login your VM from console to verify if your VM really gets the IP address you give. If no, it's the network installation/configuration problem. If yes, you can follow the steps in this video "https://www.openstack.org/summit/openstack-summit-atlanta-2014/session-videos/presentation/troubleshooting-neutron-virtual-networks" to troubleshoot it.

2015-08-24 22:02:20 -0600 asked a question cloud-init cannot find OpenStack datasource

I use an image with cloud-init package installed. If I enable ConfigDrive or Ec2, the VM launched from it can read data from metadata service. But if I only enable OpenStack datasource, it reports " No instance datasource found! ". But curl command indicates that guest VM can access it:

# curl http://169.254.169.254/openstack/latest/meta_data.json
{"random_seed": "4Q7OT/Mowdw94Qc2XQ3hDLK2gpDvIhdWMBeOGIIorioIoVJqUEDKX+71HZvWyRuZQIvV0u6NPMCsgUYXEPqd9OY2VFmrhIVplgWnSYxnCzceq0sAFw1FN9gRiN1fYZGVAmGReCv/Oa90ulC7qtF+m1HIejrnPXiD80DnogFldA9KtiS+4qeKdxNOG9cNeM6Aw4msyKbICqW2Tjr7TYDjPmVoQUnk11irJvrEELx0Hs8L4fF0sUsFUHZwmncHaskED6tmLFfJc3QmYlFV7drU5ZFIwKdj1Npw20kA7L+1pAo2U+r0Uiua7Mghw18qRIH8x35YVvvmShSkBNSR20h8NShUb+dt8rUOcT1yRxBGR4gKO/v5Z5IJugnce2AQ6x0iVA55wIRJ1b32Rf6Q72a+ftJhhMqcbG/0pzI6ZxplgdWAG7wtf/fY23NV0WQZ4QR5WwRkLoCPHwhTnJU743wSj7N8VYjBNDQllfR99hYUaozLJYNjRlJD+2cjjODkQbpmsxTmztkBsDLYfiBLDNt013bsHAnqzLVZ9VR3+Wy69RO/yDAB6AO4+Ds5Causz/LJq69h7olOCf7CCukqO+QaNXv1ZGPXQotvHDWy6j9XRCntVocxW/2JIkw5qTHda9V+1BvkGhisbK2l1mWSCQBIukcvloG3G2i1h+Or3BlcCOM=", "uuid": "3f46f567-91c4-4ac5-a79b-763d06642070", "availability_zone": "nova", "hostname": "test.novalocal", "launch_index": 0, "meta": {"admin_pass": "root"}, "name": "test"}

Here is the cloud-init.log file: http://pastebin.com/pHPwAxF2

2015-07-12 23:13:19 -0600 received badge  Notable Question (source)
2015-07-12 23:13:19 -0600 received badge  Famous Question (source)
2015-07-02 04:57:48 -0600 received badge  Enthusiast
2015-06-30 02:30:06 -0600 answered a question Instances in one of the compute nodes can't get fixed ip address

It's not related to openvswitch. I found a very good video for Neutron troubleshooting: https://www.openstack.org/summit/openstack-summit-atlanta-2014/session-videos/presentation/troubleshooting-neutron-virtual-networks (https://www.openstack.org/summit/open...). And I found the root cause for my issue. Here is the solution:

On node 2:

# tcpdump -n -e -i eno2  #eno2 is the interface which has the ip address 192.168.240.40
......
ICMP host 192.168.240.39 unreachable - admin prohibited
......

On node 1:

# iptables-save | grep icmp
......
INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
......
# iptables -D INPUT -j REJECT --reject-with icmp-host-prohibited
# iptables -D FORWARD -j REJECT --reject-with icmp-host-prohibited

After these steps, VMs on node2 can get fixed ip correctly.

2015-06-30 02:24:38 -0600 received badge  Popular Question (source)
2015-06-30 02:24:34 -0600 received badge  Editor (source)
2015-06-29 15:00:40 -0600 asked a question Instances in one of the compute nodes can't get fixed ip address

I deployed a two node OpenStack env with DevStack. One node is controller + network + compute node(node1), and the other is only compute node(node2). The instances created on node1 work well and can get fixed ip correctly, while the instances created on node2 can't. The image I used is cirros-0.3.3-x86_64. The network type is GRE tunnel. Below is the part of the console log:

cirros-ds 'local' up at 0.71
found datasource (configdrive, local)
Starting network...
udhcpc (v1.20.1) started
Sending discover...
Sending discover...
Sending discover...
Usage: /sbin/cirros-dhcpc <up|down>
No lease, failing
WARN: /etc/rc3.d/S40-network failed

On node1:

# ovs-vsctl show

d2b65058-214e-41ff-ad09-9ef2ff297201
    Bridge br-tun
        fail_mode: secure
        Port "gre-0ac4f028"
            Interface "gre-0ac4f028"
                type: gre
                options: {df_default="true", in_key=flow, local_ip="192.168.240.39", out_key=flow, remote_ip="192.168.240.40"}
        Port br-tun
            Interface br-tun
                type: internal
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
    Bridge br-int
        fail_mode: secure
        Port br-int
            Interface br-int
                type: internal
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "qr-26aa69a9-42"
            tag: 1
            Interface "qr-26aa69a9-42"
                type: internal
        Port "tap2e833a5a-e5"
            tag: 1
            Interface "tap2e833a5a-e5"
                type: internal
    Bridge br-ex
        Port "qg-985d8bbf-53"
            Interface "qg-985d8bbf-53"
                type: internal
        Port br-ex
            Interface br-ex
                type: internal
        Port "eno2"
            Interface "eno2"
    ovs_version: "2.3.1"

neutron.conf on node1: http://pastebin.com/p1gPTT18

ml2_conf.ini on node1: http://pastebin.com/sJKEPsDV

On node2, there is no tap device listed, but I can find it wit 'ip a':

    # ovs-vsctl show
    bfe15e20-872f-4785-901e-56e8ce14d826
        Bridge br-int
            fail_mode: secure
            Port "qvo3ec478f8-a7"
                tag: 1
                Interface "qvo3ec478f8-a7"
            Port br-int
                Interface br-int
                    type: internal
            Port patch-tun
                Interface patch-tun
                    type: patch
                    options: {peer=patch-int}
        Bridge br-tun
            fail_mode: secure
            Port br-tun
                Interface br-tun
                    type: internal
            Port "gre-0ac4f027"
                Interface "gre-0ac4f027"
                    type: gre
                    options: {df_default="true", in_key=flow, local_ip="192.168.240.40", out_key=flow, remote_ip="192.168.240.39"}
            Port patch-int
                Interface patch-int
                    type: patch
                    options: {peer=patch-tun}
        ovs_version: "2.3.1"

# ip a 
........
11: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
    link/ether 8e:a4:83:22:2d:43 brd ff:ff:ff:ff:ff:ff
12: br-tun: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
    link/ether a2:ae:0c:fa:b0:4f brd ff:ff:ff:ff:ff:ff
13: qbr3ec478f8-a7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
    link/ether ee:62:7e:e5:b4:86 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::ec62:7eff:fee5:b486/64 scope link
       valid_lft forever preferred_lft forever
14: qvo3ec478f8-a7: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether da:48:83:d7:e5:b8 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::d848:83ff:fed7:e5b8/64 scope link
       valid_lft forever preferred_lft forever
15: qvb3ec478f8-a7: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master qbr3ec478f8-a7 state UP qlen 1000
    link/ether ee:62:7e:e5:b4:86 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::ec62:7eff:fee5:b486/64 scope link
       valid_lft forever preferred_lft forever
16: tap3ec478f8-a7: <BROADCAST,MULTICAST,UP ...
(more)
2015-03-08 23:29:57 -0600 received badge  Notable Question (source)
2015-03-06 06:49:22 -0600 received badge  Popular Question (source)
2015-03-01 19:37:09 -0600 received badge  Scholar (source)
2015-02-27 00:26:56 -0600 asked a question Is there any hardware dependencies in Openstack?
I know the design purpose of OpenStack architecture is to avoid any hardware dependencies in it and let the dependencies be external to OpenStack. But I just want to confirm again with your experts.