digitalwonk's profile - activity

2019-11-04 21:35:23 -0600 received badge  Notable Question (source)
2017-04-24 06:52:49 -0600 received badge  Popular Question (source)
2017-04-24 06:52:49 -0600 received badge  Notable Question (source)
2015-12-23 01:21:50 -0600 received badge  Famous Question (source)
2015-07-14 06:57:55 -0600 received badge  Famous Question (source)
2015-06-10 02:07:16 -0600 received badge  Notable Question (source)
2015-02-10 04:15:09 -0600 received badge  Popular Question (source)
2015-01-12 13:11:28 -0600 received badge  Famous Question (source)
2014-12-31 03:08:39 -0600 received badge  Notable Question (source)
2014-11-19 03:45:12 -0600 received badge  Popular Question (source)
2014-11-03 22:27:05 -0600 received badge  Notable Question (source)
2014-11-01 08:42:44 -0600 received badge  Popular Question (source)
2014-08-25 02:23:56 -0600 received badge  Popular Question (source)
2014-08-06 10:59:55 -0600 received badge  Popular Question (source)
2013-05-23 18:37:07 -0600 answered a question instance cannot attach volume, although compute-host establishes valid session?

It needs to be loaded as part of an image or within an instance before you attach a cinder volume.

2013-05-21 14:34:20 -0600 answered a question instance cannot attach volume, although compute-host establishes valid session?

It turned out to be the acpiphp module that was missing from within the vm, at least for one of my images.

2013-05-21 13:22:28 -0600 answered a question instance cannot attach volume, although compute-host establishes valid session?

On another vm, I attempted to attach a volume with the same results. I was able to determine that the /etc/libvirt/qemu/instance-xxxx.xml, the following was created:

<disk type='block' device='disk'>
  <driver name='qemu' type='raw' cache='none'/>
  <source dev='/dev/disk/by-path/ip-10.0.0.137:3260-iscsi-iqn.2010-10.org.openstack:volume-f30aa828-c1dd-4786-9cde-7d36f6be9777-lun-1'/>
  <target dev='vdd' bus='virtio'/>
  <serial>f30aa828-c1dd-4786-9cde-7d36f6be9777</serial>
  <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
</disk>

Hopefully, that will provide a clue.

2013-05-21 03:56:58 -0600 asked a question instance cannot attach volume, although compute-host establishes valid session?

I am using grizzly stable from cloud archive, and currently have a problem with cinder volumes not being mounted within instances. I am using tgtadm as the iscsi helper, which is set on cinder, nova controller, and nova compute hosts. The iscsi targets seem to be connected within the compute-host, as seen by iscsiadm. Is there a particular config option or setting that might cause this behavior? Or is there a way I can further investigate what the problem might be?

This appears to be the only warning I receive on the compute host:

/var/log/nova/nova-compute.log 2013-05-20 20:32:19.882 AUDIT nova.compute.manager [req-fbb43291-5251-4514-b977-8ce3cbbdfaf1 a0c94431c8f942b9a8b67d7cab818364 e953f96c7b2a4598ae0b507b936970e2] [instance: 8f530429-7a86-49e2-b5d8-505a75d7669d] Attaching volume e48ecedb-8580-4262-8488-97f8d7c116ee to /dev/vdc 2013-05-20 20:32:22.021 WARNING nova.virt.libvirt.volume [req-fbb43291-5251-4514-b977-8ce3cbbdfaf1 a0c94431c8f942b9a8b67d7cab818364 e953f96c7b2a4598ae0b507b936970e2] ISCSI volume not yet found at: vdc. Will rescan & retry. Try number: 0

From the /var/log/syslog, the compute host seems to have mounted it correctly: May 20 20:32:20 os-compute04 kernel: [24493.934883] scsi11 : iSCSI Initiator over TCP/IP May 20 20:32:21 os-compute04 kernel: [24494.945033] scsi 11:0:0:0: Direct-Access IET VIRTUAL-DISK 0 PQ: 0 ANSI: 4 May 20 20:32:21 os-compute04 kernel: [24494.945495] sd 11:0:0:0: Attached scsi generic sg3 type 0 May 20 20:32:21 os-compute04 kernel: [24494.948319] sd 11:0:0:0: [sdc] 62914560 512-byte logical blocks: (32.2 GB/30.0 GiB) May 20 20:32:21 os-compute04 kernel: [24494.949132] sd 11:0:0:0: [sdc] Write Protect is off May 20 20:32:21 os-compute04 kernel: [24494.949139] sd 11:0:0:0: [sdc] Mode Sense: 77 00 00 08 May 20 20:32:21 os-compute04 kernel: [24494.950632] sd 11:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA May 20 20:32:21 os-compute04 kernel: [24494.957304] sdc: unknown partition table May 20 20:32:21 os-compute04 kernel: [24494.960315] sd 11:0:0:0: [sdc] Attached SCSI disk May 20 20:32:21 os-compute04 dnsmasq-dhcp[2716]: DHCP packet received on br-ex which has no address May 20 20:32:22 os-compute04 iscsid: connection1:0 is operational now

When I perform the "iscsiadm -m session -o show", I get this session, which is the correct volume tcp: [1] 10.0.0.137:3260,1 iqn.2010-10.org.openstack:volume-e48ecedb-8580-4262-8488-97f8d7c116ee

However, when I login to the VM, the device is not created (or any new device for that matter). Thanks in advance for any assistance.

2013-04-14 04:27:17 -0600 answered a question 'quantum floatingip-list' does not seem match 'quantum port-list'

Thanks dan wendlandt, that solved my question.

2013-04-13 05:11:52 -0600 asked a question 'quantum floatingip-list' does not seem match 'quantum port-list'

When I do a 'quantum floatingip-list', the number of ports assigned (10) is significantly less that the number of ports with floating ips shown in 'quantum port-list' (95). Is that expected?

Even if I exclude the ports that are assigned to tenant router gateways and vms, I still have some number of ports (76 ports) that I don't know where they come from and have floating ip addresses. I attempted to port-delete them, but I receive a "Port xxx has owner network:floatingip and therefore cannot be deleted directly via the port API." Where are these assigned or are these somehow orphan ports/ips?

If it matters, I'm still on folsom and I'm using per tenant routers with private network and overlapping ips.

Thanks, Ed

2013-03-19 17:53:48 -0600 answered a question quantum single flat network, but cannot ping instances

I actually rebooted the quantum network node (which has the dhcp agent) and now the tap interface is present, but strangely I cannot access or ping the quantum server (on the nova controller) from the network node. The quantum server also has the rabbitmq service and quantum database. I will provide more information after I debug a bit more.

2013-03-19 02:54:34 -0600 answered a question Cannot ping instance after creating vm (using quantum networking)

chown -R quantum.quantum /var/lib/quantum

I installed from the folsom packages from the ubuntu cloud archive, using 12.04.

2013-03-18 14:41:42 -0600 answered a question quantum single flat network, but cannot ping instances

Ok, so, apparently the tap device cannot be found, according to the dhcp-agent.log on the network node:

Stderr: 'Cannot find device "tapdd91d332-c6"\n' 2013-03-18 07:37:52 ERROR [quantum.agent.dhcp_agent] Unable to enable dhcp. Traceback (most recent call last):

How do can I make it be found?

2013-03-18 14:29:31 -0600 answered a question quantum single flat network, but cannot ping instances

I just checked the ovs-ofctl on the quantum network node:

ovs-ofctl show br-int

OFPT_FEATURES_REPLY (xid=0x1): ver:0x1, dpid:0000d6b390e5324c n_tables:255, n_buffers:256 features: capabilities:0xc7, actions:0xfff 1(int-br-eth0): addr:ee:ae:e4:44:7d:3b config: 0 state: 0 current: 10GB-FD COPPER 3(tapdd91d332-c6): addr:e7:00:00:00:00:00 config: PORT_DOWN state: LINK_DOWN LOCAL(br-int): addr:d6:b3:90:e5:32:4c config: 0 state: 0 OFPT_GET_CONFIG_REPLY (xid=0x3): frags=normal miss_send_len=0

And it seems to think that the tap is down. Is that ok? If not, how can I get the link state up? The dhcp agent is running or at least there are two processes for it:

nobody 24743 0.0 0.0 28820 1096 ? S Mar17 0:00 dnsmasq --no-hosts --no-resolv --strict-order --bind-interfaces --interface=tapdd91d332-c6 --except-interface=lo --domain=openstacklocal --pid-file=/var/lib/quantum/dhcp/6f12748f-2cae-4746-815d-66338e267b2f/pid --dhcp-hostsfile=/var/lib/quantum/dhcp/6f12748f-2cae-4746-815d-66338e267b2f/host --dhcp-optsfile=/var/lib/quantum/dhcp/6f12748f-2cae-4746-815d-66338e267b2f/opts --dhcp-script=/usr/bin/quantum-dhcp-agent-dnsmasq-lease-update --leasefile-ro --dhcp-range=set:tag0,1.1.1.0,static,120s root 24744 0.0 0.0 28792 244 ? S Mar17 0:00 dnsmasq --no-hosts --no-resolv --strict-order --bind-interfaces --interface=tapdd91d332-c6 --except-interface=lo --domain=openstacklocal --pid-file=/var/lib/quantum/dhcp/6f12748f-2cae-4746-815d-66338e267b2f/pid --dhcp-hostsfile=/var/lib/quantum/dhcp/6f12748f-2cae-4746-815d-66338e267b2f/host --dhcp-optsfile=/var/lib/quantum/dhcp/6f12748f-2cae-4746-815d-66338e267b2f/opts --dhcp-script=/usr/bin/quantum-dhcp-agent-dnsmasq-lease-update --leasefile-ro --dhcp-range=set:tag0,1.1.1.0,static,120s

2013-03-18 14:22:28 -0600 answered a question quantum single flat network, but cannot ping instances

No, it does not from the console.logs (an excerpt):

[ OK ]^M Bringing up loopback interface: [ OK ]^M Bringing up interface eth0:
Determining IP information for eth0... failed. [FAILED]^M Starting system logger: [ OK ]^M Starting kernel logger: [ OK ]^M iscsid (pid 1231) is running... Setting up iSCSI targets: iscsiadm: No records found [ OK ]^M

2013-03-18 06:12:24 -0600 answered a question Necessary configuration needed to disable L3 agent but keep DHCP agent, quantum network node

Thanks Sumit Naiksatam, that solved my question.

2013-03-18 06:11:28 -0600 answered a question Cannot ping instance after creating vm (using quantum networking)

Ultimately, the cause for this problem was that the dhcp agent kept on dying immediately after starting up. It was not immediately apparent since no errors were made in any logs. After fixing a file permission on the filesystem in /var/lib, the dhcp agent ran fine and the instances received the ips as expected.

2013-03-18 06:03:09 -0600 asked a question quantum single flat network, but cannot ping instances

Hello,

I setup a single flat network according to the following documentation demo:

http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo_flat.html (http://docs.openstack.org/trunk/opens...)

However, instances cannot be pinged from either the compute nodes or the quantum network node (the node with the dhcp agent). Here is a paste from 'quantum net-show', 'quantum subnet-show', 'nova list', 'ip link', and 'ovs-vsctl show'.

http://paste.openstack.org/show/33935/

I created three instances, and they all seem to be assigned the right ip address, within the 1.1.1.0/24 network. The nova compute and quantum network nodes are also on the 1.1.1.0/24 network (they have ips assigned to br-eth0 after bridge setup). Can anyone provide tips as to what to check?

Thank you, Ed

2013-03-18 05:31:34 -0600 answered a question Attempting to add a custom store file, but I receive an CONF error

The solution was that I was invoking register_opt, when I should have invoked register_opts

2013-03-06 06:04:54 -0600 answered a question Attempting to add a custom store file, but I receive an CONF error

If I import the irods.py file from within /usr/lib/python2.7/dist-packages/glance/store, the error is also seen (but not with s3.py):

python

Python 2.7.3 (default, Aug 1 2012, 05:14:39) [GCC 4.6.3] on linux2 Type "help", "copyright", "credits" or "license" for more information.

import s3 import irods Traceback (most recent call last): File "<stdin>", line 1, in <module> File "irods.py", line 27, in <module> CONF.register_opt(irods_opts) File "/usr/lib/python2.7/dist-packages/glance/openstack/common/cfg.py", line 983, in __inner return f(self, args, *kwargs) File "/usr/lib/python2.7/dist-packages/glance/openstack/common/cfg.py", line 1090, in register_opt if _is_opt_registered(self._opts, opt): File "/usr/lib/python2.7/dist-packages/glance/openstack/common/cfg.py", line 469, in _is_opt_registered if opt.dest in opts: AttributeError: 'list' object has no attribute 'dest'

2013-03-06 05:59:58 -0600 asked a question Attempting to add a custom store file, but I receive an CONF error

Hi all,

Hopefully, this is the right place for this question. I basically wrote my own store to glance, which can be found here:

http://paste.openstack.org/show/32823/

But, I get this error:

2013-03-05 22:55:51 28157 DEBUG glance.store [-] Attempting to import store glance.store.irods.Store _get_store_class /usr/lib/python2.7/dist-packages/glance/store/__init__.py:145 ERROR: Unable to load glance-api-keystone from configuration file /etc/glance/glance-api-paste.ini. Got: ImportError('Class Store cannot be found ([\'Traceback (most recent call last):\n\', \' File "/usr/lib/python2.7/dist-packages/glance/openstack/common/importutils.py", line 30, in import_class\n __import__(mod_str)\n\', \' File "/usr/lib/python2.7/dist-packages/glance/store/irods.py", line 27, in <module>\n CONF.register_opt(irods_opts)\n\', \' File "/usr/lib/python2.7/dist-packages/glance/openstack/common/cfg.py", line 983, in __inner\n return f(self, args, *kwargs)\n\', \' File "/usr/lib/python2.7/dist-packages/glance/openstack/common/cfg.py", line 1090, in register_opt\n if _is_opt_registered(self._opts, opt):\n\', \' File "/usr/lib/python2.7/dist-packages/glance/openstack/common/cfg.py", line 469, in _is_opt_registered\n if opt.dest in opts:\n\', "AttributeError: \'list\' object has no attribute \'dest\'\n"])',) 2013-03-05 22:55:51 28116 ERROR eventlet.wsgi.server [-] Removing dead child 28157

The irods.py store file is located in /usr/lib/python2.7/dist-packages/glance/store/irods.py. After looking at s3.py and filesystem.py, I'm not sure what else I'm missing.

Thanks in advance, Ed

2013-03-05 18:46:21 -0600 answered a question Adding a second external network using gre, second network does not route?

I installed using the ubuntu cloud archive packages, which only seems to only provide one agent, at least out of the box. Would I need to launch a separate agent manually? Also, would I need to setup a separate bridge if br-ex is already used? If so, would I be able to attach that new bridge to the same interface?

Thanks!

2013-03-05 17:10:47 -0600 answered a question Adding a second external network using gre, second network does not route?

Thanks for the response Yong.

The l3 log currently report the following error message repeatedly:

2013-03-04 14:14:56 ERROR [quantum.agent.l3_agent] Error running l3_nat daemon_loop Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/quantum/agent/l3_agent.py", line 171, in daemon_loop self.do_single_loop() File "/usr/lib/python2.7/dist-packages/quantum/agent/l3_agent.py", line 202, in do_single_loop target_ex_net_id = self._fetch_external_net_id() File "/usr/lib/python2.7/dist-packages/quantum/agent/l3_agent.py", line 185, in _fetch_external_net_id raise Exception("must configure 'gateway_external_network_id' if " Exception: must configure 'gateway_external_network_id' if Quantum has more than one external network.

So, if I have two separate external subnets, is there no way to have both of them being used on the same network node? Or would I need to somehow setup a separate quantum network node?

If I have to specify only one gateway_external_network_id, then why would anyone have more than external networks?

Thank you, Edwin

2013-03-04 20:13:27 -0600 asked a question Adding a second external network using gre, second network does not route?

I was successful in creating an initial gre-based external network using the following guide "Per-tenant Routers with Private Networks": http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo_routers_with_private_networks.html (http://docs.openstack.org/trunk/opens...) . However, when I create a second external network and attempt to add a second tenant network, router, vm, etc. It does not seem to route. Are there any special steps to add the second external network that isn't mentioned in the documentation?

Thanks in advance! Ed

Here are the steps I used to create everything on the second network:

NOTE: the first external network was 192.168.1.0/24

quantum net-create EXTERNAL_NETWORK2 --provider:network_type local --router:external true quantum subnet-create EXTERNAL_NETWORK2 --gateway 192.168.2.1 192.168.2.0/24

NOTE: the first tenant network was 172.16.1.0/24

quantum net-create TENANT_NET2 quantum subnet-create TENANT_NET2 172.16.2.0/24 nova boot --image ${image_id} --flavor 1 --nic net-id=<tenant_net2 id=""> TESTVM quantum router-create TENANT_ROUTER2 quantum router-interface-add TENANT_ROUTER2 <tenant_net2 subnet="" id=""> quantum router-gateway-set TENANT_ROUTER2 EXTERNAL_NETWORK2 quantum floatingip-create EXTERNAL_NETWORK2 quantum floatingip-associate <floating ip="" id=""> <vm port="" id="">

2013-03-04 19:51:53 -0600 answered a question Error about "Specifying 'tenant_id' other than authenticated tenant in request requires admin privileges"

Just adding a comment to report that my previous comment solved it.

2013-03-03 22:44:35 -0600 answered a question Cannot ping instance after creating vm (using quantum networking)

I have since switched my configuration to a shared flat network in order to try a simpler setup. I will revisit this question if I can get the simple case working. Thanks!

2013-03-01 13:47:49 -0600 asked a question Necessary configuration needed to disable L3 agent but keep DHCP agent, quantum network node

I would like to disable the L3 agent but keep the DHCP agent running on the network node. Quantum server is on a separate server (colocated on the nova controller). Can anyone point me to any documentation or maybe just list the configuration and files that would need to be changed on the quantum server, network node, and compute nodes?

2013-03-01 13:34:04 -0600 answered a question non-NATed cloud network to provider network

Robert: Do you happen to know of any instructions or could provide the configurations needed for a quantum deployment without l3 as you described? I would be interested in that configuration. Thanks!

2013-03-01 12:56:37 -0600 answered a question Cannot ping instance after creating vm (using quantum networking)

The problem still exists..

2013-03-01 12:55:40 -0600 answered a question Cannot ping instance after creating vm (using quantum networking)

http://paste.openstack.org/show/32695/

This is a paste of the following config files:

nova controller's nova.conf quantum server's quantum.conf (on nova controller) quantum server's ovs_quantum_plugin.ini (on nova controller)

network node's dhcp_agent.ini network node's l3_agent.ini

network and compute nodes' quantum.conf network and compute nodes' ovs_quantum_plugin.ini

Are there any other configs that would be useful to provide?

2013-02-27 06:46:33 -0600 answered a question Cannot ping instance after creating vm (using quantum networking)

Thanks for the tips so far! After setting the --nic option on "nova boot" and then re-issuing the "quantum net-create" without the --shared option, I was able to progress farther down the instructions, including issuing floating ips. While I can now ping, it would seem that I cannot ssh. I tried manually adding the floating ips to the br-ex bridge, but that did not seem to help. Here are some observations:

  • From the quantum network node and quantum server (on the nova controller), I can ping any ip between 172.16.1.1 - 172.16.1.101.
  • From the compute node, I can only ping 172.16.1.1. Any other 172.16.1.x ip results in a "sendmsg: Operation not permitted"
  • From the quantum network node, I can ping 1.1.1.131 and 1.1.1.132; however, I cannot ping those ips from the quantum server or the nova compute node.
  • I cannot ssh into any instance, though I added tcp/22 into the default security group (using nova, not quantum)

I will upload the config files shortly.

Here are the outputs from some commands:

http://paste.openstack.org/show/32572/

Other notes: * I created two vms * On the quantum network node, I attempted to add the floating ips using 'ip addr', e.g. "ip addr add 1.1.1.131/24 dev br-ex". The ips added to br-ex, but I could not ssh into the vms * I attempted to use "route add -net 172.16.1.0/24 gw 172.16.1.1", but I received "SIOCADDRT: No such process". It didn't add, but do I need to do this?

Again, thank you for the help, Ed

2013-02-26 06:24:14 -0600 asked a question Cannot ping instance after creating vm (using quantum networking)

Hi there,

I attempted to follow the steps outlined here to configure an initial network for a tenant/vm:

http://docs.openstack.org/trunk/openstack-network/admin/content/demo_logical_network_config.html (http://docs.openstack.org/trunk/opens...)

The primary difference I made from the steps is that I setup the external network to be shared.

1) quantum net-create --tenant-id db6ffb835f294f86979998dc65b59b0b net1 --provider:network_type vlan --provider:physical_network physnet1 --provider:segmentation_id 1

id = 5ca4b65d-6d54-4b2b-b783-2965702ef1cd

2) quantum subnet-create --tenant-id db6ffb835f294f86979998dc65b59b0b net1 172.16.1.0/24

id = e848983f-dd27-4a33-a833-ebcbd867ab02

3) quantum net-create ext_net --shared --router:external=True

id = 766c713e-3778-4497-bbb5-e816dffc4289

4) quantum subnet-create ext_net --allocation-pool start=1.1.1.130,end=1.1.1.249 --gateway 1.1.1.1 1.1.1.0/24 -- --enable_dhcp=False

id = 03221555-3c1c-4e84-963e-bae1b077f279

5) quantum router-create --tenant_id db6ffb835f294f86979998dc65b59b0b router1

id = 9aa3fb8a-d774-4a7b-9478-b64f12ce7eb9

6) quantum router-interface-add 9aa3fb8a-d774-4a7b-9478-b64f12ce7eb9 e848983f-dd27-4a33-a833-ebcbd867ab02

7) quantum router-gateway-set 9aa3fb8a-d774-4a7b-9478-b64f12ce7eb9 766c713e-3778-4497-bbb5-e816dffc4289

8) Launched a VM (NOTE: For some reason I didn't need to allocated an ip). Here is the VM information:

$ nova list +--------------------------------------+---------+--------+------------------------------------------+ | ID | Name | Status | Networks | +--------------------------------------+---------+--------+------------------------------------------+ | 5fdc74be-b2e3-4bcb-8429-4d8f9f30fbcd | TestVM1 | ACTIVE | ext_net=1.1.1.131; net1=172.16.1.2 | +--------------------------------------+---------+--------+------------------------------------------+

I had a couple of questions 1) According to the quantum documention page, I should have been required to allocate a floating ip first. However, it seems to automatically be allocated when the vm booted. I haven't defined auto_assign_floating_ip, and it appears to be false by default (according to nova-scheduler.log). Is there a reason why didn't I need to allocate a floating ip?
2) I can't ssh or ping this instance. On the nova controller and the quantum network node, I get destination unreachable; on the compute node, I get "ping: sendmsg: Operation not permitted". What step(s) am I potentially missing when configuring this vm's network?

Using cloud archive, OpenStack Folsom.

Thank you in advance! Ed

2013-02-23 18:22:37 -0600 answered a question Error about "Specifying 'tenant_id' other than authenticated tenant in request requires admin privileges"

I was able to finally execute the command _after_ I created a role that was named "admin" (the assumed role name from a stock installation), added the quantum_user to that role for the "service" tenant, and and finally reverting the /etc/quantum/policy.json to reflect the assumed role name.

My original /etc/quantum/policy.json had:

"admin_or_owner": [["role:adminrl"], ["tenant_id:%(tenant_id)s"]],
"admin_or_network_owner": [["role:adminrl"], ["tenant_id:%(network_tenant_id)s"]],
"admin_only": [["role:adminrl"]],

And the policy.json reversion was (that worked):

"admin_or_owner": [["role:admin"], ["tenant_id:%(tenant_id)s"]],
"admin_or_network_owner": [["role:admin"], ["tenant_id:%(network_tenant_id)s"]],
"admin_only": [["role:admin"]],

Note: the other services (nova, glance, etc) seem to support the renamed role name after modifying the corresponding policy.json. Did I miss changing the admin role somewhere else for quantum? Could this be a bug? While minor, it would still be nice to support role names that are different.

Thank you, Edwin

2013-02-23 07:08:06 -0600 asked a question Error about "Specifying 'tenant_id' other than authenticated tenant in request requires admin privileges"

I attempted to setup an initial quantum network according to the following link:

http://docs.openstack.org/trunk/openstack-network/admin/content/demo_logical_network_config.html (http://docs.openstack.org/trunk/opens...)

However, when I execute the quantum command to create an network for a tenant using the following command:

quantum net-create --tenant-id db6ffb835f294f86978888dc65b59b0b net1 --provider:network_type vlan --provider:physical_network physnet1 --provider:segmentation_id 1

I get the following error:

Specifying 'tenant_id' other than authenticated tenant in request requires admin privileges

My question is what user do I use or how do I give it "admin" privileges? I attempted to use the quantum admin user and the nova admin user that were created in the keystone services and endpoints. The quantum admin user and nova admin user are also specified in the api-paste.ini, such as the following:

/etc/quantum/api-paste.ini

[filter:authtoken] admin_tenant_name = service admin_user = quantum_user admin_password = quantum_user_somepass

/etc/nova/api-paste.ini

[filter:authtoken] admin_tenant_name = service admin_user = nova_user admin_password = nova_user_somepass

I have added these users as admin roles in the tenant that is declared with "tenant-id" parameter in the net-create command.

Thank you in advance for any tips.

2013-02-22 21:55:20 -0600 answered a question quantum network node cannot ping anything after bridges configured using ovs-vsctl

Thanks Aaron Rosen, that solved my question.

2013-02-22 21:55:06 -0600 answered a question quantum network node cannot ping anything after bridges configured using ovs-vsctl

I set eth1 and eth3 to 0.0.0.0 and then set the IPs on br-eth3 and br-ex as per your instructions and now I can ping ips on the respective networks again.

Thank you! Edwin

2013-02-22 21:11:40 -0600 asked a question quantum network node cannot ping anything after bridges configured using ovs-vsctl

Hi there,

I have been using the following resources for configuring openstack:

https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst (https://github.com/mseknibilel/OpenSt...) http://docs.openstack.org/trunk/openstack-network/admin/content/install_ubuntu.html (http://docs.openstack.org/trunk/opens...)

Here are the results in of my interfaces as it stands (ifconfig -a):

br-eth3 Link encap:Ethernet HWaddr d4:85:64:30:40:14
BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:6 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:360 (360.0 B) TX bytes:0 (0.0 B)

br-ex Link encap:Ethernet HWaddr d4:85:64:30:40:10
BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:164407 errors:0 dropped:10462 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:19379008 (19.3 MB) TX bytes:0 (0.0 B)

br-int Link encap:Ethernet HWaddr 02:91:ea:a3:39:4c
BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth0 Link encap:Ethernet HWaddr e4:11:5b:e6:56:ae
inet addr:10.140.65.64 Bcast:10.140.65.255 Mask:255.255.255.0 inet6 addr: fe80::e611:5bff:fee6:56ae/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:144732 errors:0 dropped:78210 overruns:0 frame:0 TX packets:6759 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:24574621 (24.5 MB) TX bytes:842415 (842.4 KB) Memory:f5f60000-f5f80000

eth1 Link encap:Ethernet HWaddr d4:85:64:30:40:10
inet addr:10.140.65.63 Bcast:10.140.65.255 Mask:255.255.255.0 inet6 addr: fe80::d685:64ff:fe30:4010/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:281705 errors:0 dropped:67743 overruns:0 frame:0 TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:37442048 (37.4 MB) TX bytes:594 (594.0 B) Interrupt:89

eth2 Link encap:Ethernet HWaddr e4:11:5b:e6:56:af
BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Memory:f5fe0000-f6000000

eth3 Link encap:Ethernet HWaddr d4:85:64:30:40:14
inet addr:192.168.65.64 Bcast:192.168.255.255 Mask:255.255.0.0 inet6 addr: fe80::d685:64ff:fe30:4014/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:3773 errors:0 dropped:0 overruns ...
(more)

2012-08-20 13:24:57 -0600 answered a question upload a kernel error

Sadly, after posting this, I had a typo in my keystone database after having to resort to the python debugger. You have to ensure you that your os_parameters (or OS_ env) are exactly right for it to work.

Here is the minimum set of OS_* environment I needed for glance to work: OS_TENANT_NAME OS_USERNAME OS_PASSWORD OS_AUTH_URL

One thing I found a little frustrating is that the glance client does not accept the same parameters as the keystone client in this regard. For example, I needed to use names instead of the ids (e.g. tenant name vs. tenant id). Another thing that is a little confusing is that if you define os_ name AND id, it's not clear to the user which one is used, and this could cause the user to get a bad catalog list or invalid authentication.

To verify that you have the right environment or settings, use "keystone catalog" (or "keystone catalog --service image") with the same environment. A successful call should result in the list service endpoints.

As a note to the developers, it would be nice if the command-line tools would produce more information, such as the settings used to authenticate particularly if debugging is enabled.

2012-08-19 23:35:44 -0600 answered a question upload a kernel error

I'm encountering the same problem. I would be interested in the solution, too.

Thanks, Ed