Re: [Openstack] using vlan tagged ports in cluster

2013-03-15 Thread Rain Li
Hi, JR,

You should check your route. Before ovs-vsctl add-port br-ex p1p1.4, you
should have the route entry like:
192.168.251.0   0.0.0.0  255.255.255.0 U 0 0 0 p1p1.4
But after that, since p1p1.4 is plugged in br-ex, you should change the
above route to go through br-ex, and may also change other (default route)
to this interface as well, if they originally go through p1p1.4.

Regards,
Rain


On Thu, Mar 14, 2013 at 5:22 AM, JR botem...@gmail.com wrote:

 Greetings,

 I'm setting up openstack on some machines using

 https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst
 .

 I'm using 3 nodes: a controller, network node and compute node.  All the
 network interfaces are VLAN tagged use the same underlying physical 10G,
 e.g.,

 controller: p1p1.4 (public net: 192.168.251.*/24), p1p1.5 (management
 net: 10.10.10.*/24)
 network:p1p1.4 (public net: 192.168.251.*/24), p1p1.5 (management
 net: 10.10.10.*/24), p1p1.6 (vm net: 10.20.20.*/24)

 # I haven't gotten to the compute node yet but it should be
 compute:   p1p1.5 (management net: 10.10.10.*/24), p1p1.6 (vm net:
 10.20.20.*/24)

 When I bring up my openvswitch bridges on the network node, I can not
 longer get out to the public net (see *MORE* below).

 I'm running ubuntu 12.10 and have run apt-get dist-upgrade.  The 10G
 nics are intel 82599EB.  ubuntu seems a bit flakey; initially I'd
 created /etc/udev/rules/70-persistent-net.rules to map p1p1 to eth2,
 however, the config was ignored and eth2 wound up being a 1G NIC.

 Is it not allowed to use VLAN interfaces for my networks?

 If I remove, say, the br-ex bridge I can get out again:
 root@nebula03:~# ping 192.168.251.1
 PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
 ^C
 --- 192.168.251.1 ping statistics ---
 1 packets transmitted, 0 received, 100% packet loss, time 0ms

 root@nebula03:~# ovs-vsctl del-port p1p1.4
 root@nebula03:~# ovs-vsctl del-br br-ex
 root@nebula03:~# ping 192.168.251.1
 PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
 64 bytes from 192.168.251.1: icmp_req=1 ttl=64 time=0.650 ms
 ^C
 --- 192.168.251.1 ping statistics ---
 1 packets transmitted, 1 received, 0% packet loss, time 0ms
 rtt min/avg/max/mdev = 0.650/0.650/0.650/0.000 ms
 root@nebula03:~#


 Thanks for any help,
 JR

 
 *MORE*
 
 root@nebula03:~# ovs-vsctl show
 1bdf2f73-1a5d-4893-b745-7501557acaea
 Bridge br-int
 Port br-int
 Interface br-int
 type: internal
 Bridge br-ex
 Port br-ex
 Interface br-ex
 type: internal
 Port p1p1.4
 Interface p1p1.4
 Bridge br-vm
 Port br-vm
 Interface br-vm
 type: internal
 Port p1p1.6
 Interface p1p1.6
 ovs_version: 1.4.3
 root@nebula03:~# ifconfig p1.4
 p1.4: error fetching interface information: Device not found
 root@nebula03:~# ifconfig p1p1.4
 p1p1.4Link encap:Ethernet  HWaddr 90:e2:ba:2c:8a:08
   inet addr:192.168.251.92  Bcast:192.168.251.255
 Mask:255.255.255.0
   inet6 addr: fe80::92e2:baff:fe2c:8a08/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:20964 errors:0 dropped:0 overruns:0 frame:0
   TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:22269341 (22.2 MB)  TX bytes:594 (594.0 B)

 root@nebula03:~# ping 192.168.251.1
 PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
 ^C
 --- 192.168.251.1 ping statistics ---
 2 packets transmitted, 0 received, 100% packet loss, time 1007ms

 root@nebula03:~# ping 192.168.251.91`
  ^C
 root@nebula03:~# ping 192.168.251.91
 PING 192.168.251.91 (192.168.251.91) 56(84) bytes of data.
 ^C





 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] No output from nova list

2013-03-13 Thread Rain Li
Hi, all,

I set up a three-hosts openstack environment, but I can't synchronize nova
output with horizon output. When execute nova --list, it generates
Please enter password for encrypted keyring: message. Then I issue nova
--no-cache list, it output nothing.

I can initialize a instance from horizon interface, and the instance can
get an proper fixed ip address. And with nova --no-cache image-list, I
can see the uploaded image, it is the same image-id with glance index. So
can anyone guide me with this situation?

Thank you!
Rain
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] No output from nova list

2013-03-13 Thread Rain Li
Hi,

Thanks for help. Can anyone tell me how (besides the --no-cache option) to
get rid of the message Please enter password for encryped keyring? With
horizon interface, I get:
[image: Inline image 1]
But nova --debug list shows (no active servers):
Please enter password for encrypted keyring:

REQ: curl -i
http://192.168.1.200:8774/v2/2666e01122c5422e9224396f52e9a600/servers/detail-X
GET -H X-Auth-Project-Id: admin -H User-Agent: python-novaclient
-H
Accept: application/json -H X-Auth-Token:
cd4177ee1cc34da492be50e56a699c58

connect: (192.168.1.200, 8774)
send: u'GET /v2/2666e01122c5422e9224396f52e9a600/servers/detail
HTTP/1.1\r\nHost: 192.168.1.200:8774\r\nx-auth-project-id:
admin\r\nx-auth-token: cd4177ee1cc34da492be50e56a699c58\r\naccept-encoding:
gzip, deflate\r\naccept: application/json\r\nuser-agent:
python-novaclient\r\n\r\n'
reply: 'HTTP/1.1 200 OK\r\n'
header: X-Compute-Request-Id: req-596f1fb4-cf32-4405-af79-9c871a9f3faa
header: Content-Type: application/json
header: Content-Length: 15
header: Date: Thu, 14 Mar 2013 02:12:46 GMT
RESP:{'status': '200', 'content-length': '15', 'content-location': u'
http://192.168.1.200:8774/v2/2666e01122c5422e9224396f52e9a600/servers/detail',
'x-compute-request-id': 'req-596f1fb4-cf32-4405-af79-9c871a9f3faa', 'date':
'Thu, 14 Mar 2013 02:12:46 GMT', 'content-type': 'application/json'}
{servers: []}

nova --debug list  works fine, shows:
+--+---+++
| ID   | Name  | Status | Networks
  |
+--+---+++
| 6b52ed18-8768-4b58-95f1-a2aca9f39807 | demo2 | ACTIVE |
net_proj_one=50.50.1.4 |
| aea5e22d-3d00-4f0a-9b76-de0b9b5c9c87 | user_one_demo | ACTIVE |
net_proj_one=50.50.1.3 |
+--+---+++

nova --no-cache image-list shows:
+--+--+++
| ID   | Name | Status | Server |
+--+--+++
| cbb0351b-b4fa-4e63-af7f-c9d00d750671 | myFirstImage | ACTIVE ||
+--+--+++

nova --no-cache usage-list shows:
+--+---+--+---+---+
| Tenant ID| Instances | RAM MB-Hours | CPU Hours |
Disk GB-Hours |
+--+---+--+---+---+
| 092c550adf0f49cb9a1ccfd2367a29fb | 3 | 251806.33| 126.21|
2437.34   |
+--+---+--+---+---+

nova --no-cache network-list get an error:
ERROR: The server has either erred or is incapable of performing the
requested operation. (HTTP 500) (Request-ID:
req-d888fc8f-5a00-46a9-9bcd-a047293c88bb)

And nova --no-cache flavor-list works fine, nova --no-cache
hypervisor-list works fine, nova --no-cache floating-ip-pool-list works
fine.

 nova --no-cache floating-ip-list shows nothing, but quantum
floatingip-list shows:
+--+--+-+--+
| id   | fixed_ip_address |
floating_ip_address | port_id  |
+--+--+-+--+
| 3942424e-4ca5-4148-9440-26c254753bf5 |  | 192.168.1.227
|  |
| 5d437edc-5b6f-4f0a-8e0f-2a01d07afa13 | 50.50.1.3| 192.168.1.226
| 3d909d47-bb8b-4ef5-9688-a4dc314eed21 |
| 8f6da458-9dcc-4f8d-ac76-9b170fbacfa9 |  | 192.168.1.228
|  |
+--+--+-+--+

So is there any other information you guys needed to pinpoint the potential
problems?

Best,
Rain


On Wed, Mar 13, 2013 at 9:06 PM, Hanyu Xiao hanyu.x...@eayun.com wrote:

  what's the output of nova --debug list and nova --debug list
 --all-tenants?

 On 03/14/2013 08:33 AM, Rain Li wrote:

 Hi, all,

  I set up a three-hosts openstack environment, but I can't synchronize
 nova output with horizon output. When execute nova --list, it generates
 Please enter password for encrypted keyring: message. Then I issue nova
 --no-cache list, it output nothing.

  I can initialize a instance from horizon interface, and the instance can
 get an proper fixed ip address. And with nova --no-cache image-list, I
 can see the uploaded image, it is the same image-id with glance index. So
 can anyone guide me with this situation?

  Thank you!
 Rain

[Openstack] 'novarc' environment setting failed to authenticated

2013-02-08 Thread Rain Li
Hi Mark,

Thanks for replying. But still get the same output.

Best,
Rain


On Fri, Feb 8, 2013 at 10:52 AM, Miller, Mark M (EB SW Cloud - RD -
Corvallis) mark.m.mil...@hp.com wrote:

  Hi Rain,

 ** **

 I’ve been setting the following 2 environment variables instead:

 ** **

 **· **SERVICE_ENDPOINT=”http://10.0.0.1:35357/v2.0”

 **· **SERVICE_TOKEN=admin_token value  from the keystone.conf
 file

 ** **

 Mark

 ** **

 *From:* openstack-bounces+mark.m.miller=hp@lists.launchpad.net[mailto:
 openstack-bounces+mark.m.miller=hp@lists.launchpad.net] *On Behalf Of
 *Rain Li
 *Sent:* Thursday, February 07, 2013 7:13 PM
 *To:* openstack@lists.launchpad.net
 *Subject:* [Openstack] 'novarc' environment setting failed to
 authenticated

 ** **

 Hi, all,

 I am following OpenStack Basic Install guide (
 http://docs.openstack.org/folsom/basic-install/content/index.html), but
 when executing the keystone-endpoint.sh script on the controller-node, I
 always get this error message:
 Expecting authentication method via
   either a service token, --token or env[SERVICE_TOKEN],
   or credentials, --os-username or env[OS_USERNAME].
 usage: keystone endpoint-create [--region endpoint-region] --service-id
 service-id [--publicurl public-url]
 [--adminurl admin-url]
 [--internalurl internal-url]
 keystone endpoint-create: error: argument --service-id/--service_id:
 expected one argument
 ...

 But I already setup the environment variables like this:
 stack@folsom-controller:~$ env | grep OS_
 OS_PASSWORD=password
 OS_AUTH_URL=http://10.0.0.1:35357/v2.0
 OS_USERNAME=admin
 OS_TENANT_NAME=admin

 And get the similar error when executing the sample quantum-networking.sh
 script on the network-node:
 Expecting authentication method via
   either a service token, --token or env[SERVICE_TOKEN],
   or credentials, --os-username or env[OS_USERNAME].

 You must provide a username via either --os-username or env[OS_USERNAME]
 ...

 I have environment variables setting like:
 stack@folsom-network:~$ env | grep OS_
 OS_PASSWORD=password
 OS_AUTH_URL=http://10.0.0.1:5000/v2.0
 OS_USERNAME=admin
 OS_TENANT_NAME=admin

 Any suggestions to get around this?

 Regards,

 Rain

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] quantum net-list command get error

2013-02-08 Thread Rain Li
Hi all,

When setting the virtual network on network-node with the basic-install
guide, I failed to authenticate with the environment variables as suggested
in novarc. Then I directly execute command quantum net-list with credential
parameters contained. I get this error:

DEBUG: quantumclient.quantum.v2_0.network.ListNetwork
get_data(Namespace(columns=[], fields=[], filter_specs=[],
formatter='table', quote_mode='nonnumeric', request_format='json',
show_details=False))
DEBUG: quantumclient.client REQ: curl -i
http://10.0.0.1:35357/v2.0/tokens-X POST -H Content-Type:
application/json -H Accept: application/json
-H User-Agent: python-quantumclient

DEBUG: quantumclient.client REQ BODY: {auth: {tenantName: admin,
passwordCredentials: {username: admin, password: password}}}

DEBUG: quantumclient.client RESP:{'date': 'Fri, 08 Feb 2013 20:44:56 GMT',
'transfer-encoding': 'chunked', 'status': '200', 'content-type':
'application/json', 'vary': 'X-Auth-Token'}


ERROR: cliff.app An unknown exception occurred.
Traceback (most recent call last):
  File /usr/lib/python2.7/dist-packages/cliff/app.py, line 218, in
run_subcommand
result = cmd.run(parsed_args)
  File /usr/lib/python2.7/dist-packages/quantumclient/common/command.py,
line 35, in run
return super(OpenStackCommand, self).run(parsed_args)
  File /usr/lib/python2.7/dist-packages/cliff/display.py, line 84, in run
column_names, data = self.take_action(parsed_args)
  File /usr/lib/python2.7/dist-packages/quantumclient/common/command.py,
line 41, in take_action
return self.get_data(parsed_args)
  File
/usr/lib/python2.7/dist-packages/quantumclient/quantum/v2_0/__init__.py,
line 360, in get_data
quantum_client = self.get_client()
  File
/usr/lib/python2.7/dist-packages/quantumclient/quantum/v2_0/__init__.py,
line 187, in get_client
return self.app.client_manager.quantum
  File
/usr/lib/python2.7/dist-packages/quantumclient/common/clientmanager.py,
line 41, in __get__
self._handle = self.factory(instance)
  File /usr/lib/python2.7/dist-packages/quantumclient/quantum/client.py,
line 36, in make_client
instance.initialize()
  File
/usr/lib/python2.7/dist-packages/quantumclient/common/clientmanager.py,
line 78, in initialize
httpclient.authenticate()
  File /usr/lib/python2.7/dist-packages/quantumclient/client.py, line
207, in authenticate
self._extract_service_catalog(body)
  File /usr/lib/python2.7/dist-packages/quantumclient/client.py, line
176, in _extract_service_catalog
endpoint_type='adminURL')
  File /usr/lib/python2.7/dist-packages/quantumclient/client.py, line 80,
in url_for
raise exceptions.EndpointNotFound()
EndpointNotFound: An unknown exception occurred.
DEBUG: quantumclient.shell clean_up ListNetwork
DEBUG: quantumclient.shell got an error: An unknown exception occurred.

Does anyone know what's going on?

Regards,
Rain
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] 'novarc' environment setting failed to authenticated

2013-02-07 Thread Rain Li
Hi, all,

I am following OpenStack Basic Install guide (
http://docs.openstack.org/folsom/basic-install/content/index.html), but
when executing the keystone-endpoint.sh script on the controller-node, I
always get this error message:
Expecting authentication method via
  either a service token, --token or env[SERVICE_TOKEN],
  or credentials, --os-username or env[OS_USERNAME].
usage: keystone endpoint-create [--region endpoint-region] --service-id
service-id [--publicurl public-url]
[--adminurl admin-url]
[--internalurl internal-url]
keystone endpoint-create: error: argument --service-id/--service_id:
expected one argument
...
But I already setup the environment variables like this:
stack@folsom-controller:~$ env | grep OS_
OS_PASSWORD=password
OS_AUTH_URL=http://10.0.0.1:35357/v2.0
OS_USERNAME=admin
OS_TENANT_NAME=admin

And get the similar error when executing the sample quantum-networking.sh
script on the network-node:
Expecting authentication method via
  either a service token, --token or env[SERVICE_TOKEN],
  or credentials, --os-username or env[OS_USERNAME].
You must provide a username via either --os-username or env[OS_USERNAME]
...
I have environment variables setting like:
stack@folsom-network:~$ env | grep OS_
OS_PASSWORD=password
OS_AUTH_URL=http://10.0.0.1:5000/v2.0
OS_USERNAME=admin
OS_TENANT_NAME=admin

Any suggestions to get around this?

Regards,
Rain
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Problem with IP on VMs

2013-01-30 Thread Rain Li
Have you setup the secgroup rules?


On Wed, Jan 30, 2013 at 2:02 PM, Ritesh Nanda riteshnand...@gmail.comwrote:

 Can you give more details for your setup.

 On Thu, Jan 31, 2013 at 12:55 AM, Guilherme Russi 
 luisguilherme...@gmail.com wrote:

 Hello all,

  I'm using Folsom on Ubuntu server 12.04 and I'm getting problems with
 ping and login ssh. Can anybody help me?

 Regards.

 Guilherme.

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp




 --

 * With Regards
 *

 * Ritesh Nanda
 *

 ***
 *
 http://www.ericsson.com/




 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Metadata server unreachable and can't passwordless login to instance

2013-01-28 Thread Rain Li
Hi all,

I want to know if this bug has been fixed or not.
https://bugs.launchpad.net/nova/+bug/719798. When starting an instance, I
still get this error:

cloud-setup: checking
http://169.254.169.254/2009-04-04/meta-data/instance-id
wget: can't connect to remote host (169.254.169.254): Network is unreachable
cloud-setup: failed 1/30: up 10.57. request failed

But I have route table like this:
Destination Gateway Genmask Flags Metric RefUse
Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG0  00 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 eth0
172.24.17.0 192.168.1.130   255.255.255.0   UG0  00
br-ex
192.168.1.0 0.0.0.0 255.255.255.0   U 0  00 eth0
192.168.1.128   0.0.0.0 255.255.255.128 U 0  00
br-ex
192.168.122.0   0.0.0.0 255.255.255.0   U 0  00
virbr0

And I think maybe because of this error, I can't login to the instance via
password-less method with the following command:
ssh -i admin.pem -l cirros 192.168.1.131
I already change the permission property of admin.pem, and it asks the
password again.

Anyone know how to solve this? Thanks.

Regards,
Rain Lee
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] vm can not get ip

2013-01-22 Thread Rain Li
Hi, Sam,

I also install Openstack on ubuntu 12.10 via
http://devstack.org/guides/single-machine.html, and get this error as well.
Another weird thing is that I can start an instance from horizon, (it shows
the successful message), but I can not access (ping/ssh) the instance
from the controller host machine. I already add the corresponding secgroup
rules. With command route -n, I can see the route entry for 169.254.0.0.
Hope someone can show some clues for this problem.

Rain Li


On Mon, Jan 21, 2013 at 8:50 PM, sam lee lixq2...@gmail.com wrote:

 the following are my dhcp-agent configure and dnsmasq info.

 root@network:/home/openstack# ps -ef | grep dnsmasq

 nobody2299 1  0 Jan21 ?00:00:00 /usr/sbin/dnsmasq
 --no-hosts --no-resolv --strict-order --bind-interfaces
 --interface=tapc71e5285-a0 --except-interface=lo --domain=openstacklocal
 --pid-file=/var/lib/quantum/dhcp/93e695f6-5dae-41b1-8a92-2bce8cb0e785/pid
 --dhcp-hostsfile=/var/lib/quantum/dhcp/93e695f6-5dae-41b1-8a92-2bce8cb0e785/host
 --dhcp-optsfile=/var/lib/quantum/dhcp/93e695f6-5dae-41b1-8a92-2bce8cb0e785/opts
 --dhcp-script=/usr/bin/quantum-dhcp-agent-dnsmasq-lease-update
 --leasefile-ro --dhcp-range=set:tag0,50.50.1.0,static,120s

 root  2301  2299  0 Jan21 ?00:00:00 /usr/sbin/dnsmasq
 --no-hosts --no-resolv --strict-order --bind-interfaces
 --interface=tapc71e5285-a0 --except-interface=lo --domain=openstacklocal
 --pid-file=/var/lib/quantum/dhcp/93e695f6-5dae-41b1-8a92-2bce8cb0e785/pid
 --dhcp-hostsfile=/var/lib/quantum/dhcp/93e695f6-5dae-41b1-8a92-2bce8cb0e785/host
 --dhcp-optsfile=/var/lib/quantum/dhcp/93e695f6-5dae-41b1-8a92-2bce8cb0e785/opts
 --dhcp-script=/usr/bin/quantum-dhcp-agent-dnsmasq-lease-update
 --leasefile-ro --dhcp-range=set:tag0,50.50.1.0,static,120s
 root  9854  4475  0 10:44 pts/100:00:00 grep --color=auto dnsmasq
 root@network:/home/openstack#

 root@network:/home/openstack# grep -v # /etc/quantum/dhcp_agent.ini
 [DEFAULT]
 state_path = /var/lib/quantum
 interface_driver = quantum.agent.linux.interface.OVSInterfaceDriver
 dhcp_driver = quantum.agent.linux.dhcp.Dnsmasq
 use_namespaces = False
 root_helper = sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf
 root@network:/home/openstack#

 root@network:/var/lib/quantum/dhcp# ovs-vsctl show
 d120debb-b01b-4b9a-b824-5e7e23fa1cd4
 Bridge br-int
 Port tap9338c64b-13
 tag: 4095
 Interface tap9338c64b-13
 type: internal
 Port qr-ca596884-61
 tag: 1
 Interface qr-ca596884-61
 type: internal
 Port tap063c55b9-17
 tag: 4095
 Interface tap063c55b9-17
 type: internal
 Port br-int
 Interface br-int
 type: internal
 Port tap0dcaeb82-30
 tag: 4095
 Interface tap0dcaeb82-30
 type: internal
 Port tapc71e5285-a0
 tag: 1
 Interface tapc71e5285-a0
 type: internal
 Port int-br-eth1
 Interface int-br-eth1
 Bridge br-eth1
 Port phy-br-eth1
 Interface phy-br-eth1
 Port eth0
 Interface eth0
 Port br-eth1
 Interface br-eth1
 type: internal
 Bridge br-ex
 Port br-ex
 Interface br-ex
 type: internal
 Port qg-d5d39934-28
 Interface qg-d5d39934-28
 type: internal
 Port eth1
 Interface eth1
 ovs_version: 1.4.0+build0



 2013/1/22 sam lee lixq2...@gmail.com

 I install openstack folsom on ubuntu 12.04 following this guide
 https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/VLAN/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst.
 Everything is ok util run an instance.  I check the nova console log, it
 show that cloud-setup: checking
 http://169.254.169.254/2009-04-04/meta-data/instance-id
 wget: can't connect to remote host (169.254.169.254): Network is
 unreachable, ..., and i don't use namespace. I am a newbie for
 openstack. Appreciate all the help



 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp