Re: [Openstack] LXC on Folsom
Hi Chuan, Did you manage to resolve the following issue? init: Unable to create device: /dev/kmsg I'm having a similar problem while running LXC on Folsom. https://lists.launchpad.net/openstack/msg23438.html Thanks and Regards, Shashank Sahni ___ 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] Error running instance on LXC(Folsom)
Hi everyone, I've configured LXC successfully on the compute node. Its running Ubuntu 12.04. After adding ubuntu-cloud repo, I installed nova-compute-lxc(folsom). The node is being recognized by the controller. For the image, I downloaded ubuntu uec image. http://uec-images.ubuntu.com/releases/precise/release/ubuntu-12.04-server-cloudimg-amd64.tar.gz Extracted and added the .img file to glance using the following command. $ glance image-create --disk-format=raw --container-format=bare --name=ubuntu-12.04-amd64-lxc --is-public=true --property hypervisor_type=lxc --file precise-server-cloudimg-amd64.img I booted the instance and it was scheduled on the LXC node. There is no error message in the nova-compute logs but the instance doesn't boot. Here's the console log. init: Unable to create device: /dev/kmsg cloud-init-container: emitted ifup for eth0 cloud-init start-local running: Wed, 08 May 2013 18:39:22 +. up 12985071.30 seconds no instance data found in start-local The instance boots after sometime without any IP. I've already configured bridge, br100, on the compute-node. I'm not sure what am I missing. Additionally, while troubleshooting I found these error in the libvirtd.log when the instance was running. 2013-05-08 18:39:27.060+: 8034: error : virDomainGetVcpus:8912 : this function is not supported by the connection driver: virDomainGetVcpus 2013-05-08 18:39:27.186+: 8041: error : virDomainGetVcpus:8912 : this function is not supported by the connection driver: virDomainGetVcpus 2013-05-08 18:39:29.439+: 8032: error : virDomainGetVcpus:8912 : this function is not supported by the connection driver: virDomainGetVcpus Any suggestions? -- Shashank Sahni ___ 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] Failed db sync while upgrading from essex to folsom
Hi Calvin, Thank you for the reply. It solved the db sync issue. But soon after this, the nova-compute daemons started throwing the following trace. 2013-04-30 15:53:21 TRACE nova OperationalError: (OperationalError) (1054, Unknown column 'instance_metadata_1.instance_id' in 'field list') When I checked the instance_metatdata table, I found that it has instance_uuid as a field and not instance_id. It seems to be another issue with db sync. Suggestions? -- Shashank Sahni On Tue, Apr 30, 2013 at 2:32 AM, Calvin Walton calvin.wal...@kepstin.cawrote: On Mon, 2013-04-29 at 20:16 +0530, Shashank Sahni wrote: Hi everyone, I'm having some trouble upgrading from essex to folsom. The cloud is currently running on Ubuntu 12.04. For the upgrade, I included the folsom repo(ubuntu cloud archive) and upgraded the packages. Things went fine until I issued nova-manage db sync. It failed with the following error. 2013-04-29 20:13:50 23254 TRACE nova raise exc.NoSuchTableError(full_name) 2013-04-29 20:13:50 23254 TRACE nova NoSuchTableError: `projects` Ironically, the table exists. But I get the same message accessing it through mysql console. This is due to a bug in one version of the Ubuntu package that included a broken database migration; it had a foreign key on a latin-1 table (dns_domains) referencing a text column on a utf-8 table (projects), which mysql does not support. As a result, a *later* migration that changed the projects table partially failed, and left the table in a half-created state. I ran into this problem, and the only way I found to *fix* the error was to dump the database to a sql file, drop the entire database, manually edit the dump file to correct the referencing table charset on the 'dns_domains' table, add the definition for the projects table back, then restore the database from the dump. Related issues on launchpad: https://bugs.launchpad.net/nova/+bug/993663 https://bugs.launchpad.net/ubuntu/+source/nova/+bug/975085 Amusingly, if you're using keystone, the 'projects' table is actually not used by anything, but it still has to exist. -- Calvin Walton calvin.wal...@kepstin.ca ___ 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] Failed db sync while upgrading from essex to folsom
Thanks Calvin. It was an update issue. I ran apt-get upgrade instead of dist-upgrade. -- Shashank Sahni On Tue, Apr 30, 2013 at 6:05 PM, Calvin Walton calvin.wal...@kepstin.cawrote: On Tue, 2013-04-30 at 16:06 +0530, Shashank Sahni wrote: Hi Calvin, Thank you for the reply. It solved the db sync issue. But soon after this, the nova-compute daemons started throwing the following trace. 2013-04-30 15:53:21 TRACE nova OperationalError: (OperationalError) (1054, Unknown column 'instance_metadata_1.instance_id' in 'field list') When I checked the instance_metatdata table, I found that it has instance_uuid as a field and not instance_id. It seems to be another issue with db sync. Suggestions? From https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/migrate_repo/versions/133_folsom.py#L349 It looks like 'instance_uuid' is the correct column name in Folsom. Are you sure that you've updated your nova-compute packages to the Folsom version and restarted all of the nova services? The simplest explanation for this error is that you have an Essex service accessing the Folsom database. -- Calvin Walton calvin.wal...@kepstin.ca ___ 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] Failed db sync while upgrading from essex to folsom
Hi everyone, I'm having some trouble upgrading from essex to folsom. The cloud is currently running on Ubuntu 12.04. For the upgrade, I included the folsom repo(ubuntu cloud archive) and upgraded the packages. Things went fine until I issued nova-manage db sync. It failed with the following error. 2013-04-29 20:13:50 23254 TRACE nova raise exc.NoSuchTableError(full_name) 2013-04-29 20:13:50 23254 TRACE nova NoSuchTableError: `projects` Ironically, the table exists. But I get the same message accessing it through mysql console. Any suggestions? -- Shashank Sahni ___ 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] Failed db sync while upgrading from essex to folsom
Hello Yaguang, Thanks for your response, but no luck :( This table, projects, and related ones - users, user_project_association etc. seem to be skeleton from the time authentication service was a part of nova. The related tables are all empty. I tried to delete it, but got table doesn't exist error. Although, the .frm file exists in /var/lib/mysql. Something seems to have gone wrong with InnoDB. -- Shashank Sahni On Mon, Apr 29, 2013 at 9:29 PM, Yaguang Tang heut2...@gmail.com wrote: This is a MYsql DB issue, you can try to restart MYsql if possible. 2013/4/29 Shashank Sahni shredde...@gmail.com Hi everyone, I'm having some trouble upgrading from essex to folsom. The cloud is currently running on Ubuntu 12.04. For the upgrade, I included the folsom repo(ubuntu cloud archive) and upgraded the packages. Things went fine until I issued nova-manage db sync. It failed with the following error. 2013-04-29 20:13:50 23254 TRACE nova raise exc.NoSuchTableError(full_name) 2013-04-29 20:13:50 23254 TRACE nova NoSuchTableError: `projects` Ironically, the table exists. But I get the same message accessing it through mysql console. Any suggestions? -- Shashank Sahni ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Tang Yaguang Canonical Ltd. | www.ubuntu.com | www.canonical.com Mobile: +86 152 1094 6968 gpg key: 0x187F664F ___ 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] Swift container's rwx permissions
Thanks David, Clay and Vaidy for your suggestions. I'm curious about what version of that Hadoop-Swift-integration project you're trying to run. You shouldn't have been able to create containers with it in any of the more recent versions. Yes, my bad. Container creation isn't supported. As part of the the Swift's implementation in Hadoop Filesystem class, we need to explicitly mention a container which will be considered as DFS root. You might want to try the converged branch of https://github.com/hortonworks/Hadoop-and-Swift-integration. This is the branch that's getting submitted back to Apache for inclusion in Hadoop. Yes, we have already tried it. Same result. FYI we are using Hadoop 1.1.2 -- Shashank Sahni ___ 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] Swift container's rwx permissions
Hi everyone, I've been experimenting with using Swift(1.8) as Hadoop's DFS backend. https://github.com/DmitryMezhensky/Hadoop-and-Swift-integration After a few glitches, I'm able to create/access/delete objects/containers using hadoop's cli fs tool. But whenever I'm trying to run the job it fails with the following error. ERROR security.UserGroupInformation: PriviledgedActionException as:dharmesh cause:java.io.IOException: The ownership/permissions on the staging directory swift://hadooptest.rackspace/tmp/app/mapred/staging/dharmesh/.staging is not as expected. It is owned by and permissions are rwxrwxrwx. The directory must be owned by the submitter dharmesh or by dharmesh and permissions must be rwx-- Note that, the local system username is dharmesh and the openstack account and associated tenant is dharmesh too. I tried setting the permissions by creating tmp container using swift post -r 'dharmesh:dharmesh', but unfortunately ended up with the same result. Is there an other way to set rwx ACLs in swift? -- Shashank Sahni ___ 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] Error uploading large objects(1G) on swift
Hi, Here is a detailed overview of my setup. Two machines(each 4G RAM and one 2TB disk) 1. Configured as proxy + storage 2. Configured as storage I followed the folsom object storage administrator guide and created ring partitions using the following commands. # swift-ring-builder account.builder 9 2 1 # swift-ring-builder container.builder 9 2 1 # swift-ring-builder object.builder 9 2 1 I added both the storage units in the same zone, copied the *.ring.gz files to each host and restarted the services. The setup seems to be working fine for small files, but while copying large files I get errors(as stated in the previous mail). Any help would be greatly appreciated. Thanks. -- Shashank Sahni On Fri, Mar 8, 2013 at 12:51 PM, Shashank Sahni shredde...@gmail.comwrote: Hi everyone, I'm running a small test setup of swift with one proxy+storage and one storage instance. The setup seems to be running well for small objects. I'm able to create and upload them successfully using swift cli tool, but for large objects(1G), I get error of 503 service unavailable(on swift cli) after a long wait. I dig into logs and found that none of the replicator services are running. All of them give the following error(array index out of range) Mar 8 12:42:03 yahoo-128 account-replicator Beginning replication run Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: Traceback (most recent call last): Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: File /usr/lib/python2.7/dist-packages/eventlet/greenpool.py, line 80, in _spawn_n_impl Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: func(*args, **kwargs) Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: File /usr/lib/python2.7/dist-packages/swift/common/db_replicator.py, line 398, in _replicate_object Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: nodes = self.ring.get_part_nodes(int(partition)) Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: File /usr/lib/python2.7/dist-packages/swift/common/ring/ring.py, line 201, in get_part_nodes Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: if not (r[part] in seen_ids or seen_ids.add(r[part]))] Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: IndexError: array index out of range Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: Traceback (most recent call last): Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: File /usr/lib/python2.7/dist-packages/eventlet/greenpool.py, line 80, in _spawn_n_impl Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: func(*args, **kwargs) Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: File /usr/lib/python2.7/dist-packages/swift/common/db_replicator.py, line 398, in _replicate_object Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: nodes = self.ring.get_part_nodes(int(partition)) Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: File /usr/lib/python2.7/dist-packages/swift/common/ring/ring.py, line 201, in get_part_nodes Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: if not (r[part] in seen_ids or seen_ids.add(r[part]))] Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: IndexError: array index out of range Mar 8 12:42:03 yahoo-128 account-replicator Replication run OVER Mar 8 12:42:03 yahoo-128 account-replicator Attempted to replicate 3 dbs in 0.02536 seconds (118.26332/s) Mar 8 12:42:03 yahoo-128 account-replicator Removed 0 dbs Mar 8 12:42:03 yahoo-128 account-replicator 1 successes, 0 failures Mar 8 12:42:03 yahoo-128 account-replicator no_change:1 ts_repl:0 diff:0 rsync:0 diff_capped:0 hashmatch:0 empty:0 Additionally, while the transfer of a big file was going on(4GB), I got the following error in logs. proxy-server ERROR with Object server 10.0.1.1:6000/sdb1 re: Trying to write to /v1/AUTH_28c949f34bd3b5fb295cffb69ed4/data_dir/data_dir/Feb27/PRIVATE/AVCHD/BDMV/STREAM/2.MTS: ChunkWriteTimeout (10s) Any suggestions? -- Shashank Sahni ___ 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] Error uploading large objects(1G) on swift
Hi everyone, I'm running a small test setup of swift with one proxy+storage and one storage instance. The setup seems to be running well for small objects. I'm able to create and upload them successfully using swift cli tool, but for large objects(1G), I get error of 503 service unavailable(on swift cli) after a long wait. I dig into logs and found that none of the replicator services are running. All of them give the following error(array index out of range) Mar 8 12:42:03 yahoo-128 account-replicator Beginning replication run Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: Traceback (most recent call last): Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: File /usr/lib/python2.7/dist-packages/eventlet/greenpool.py, line 80, in _spawn_n_impl Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: func(*args, **kwargs) Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: File /usr/lib/python2.7/dist-packages/swift/common/db_replicator.py, line 398, in _replicate_object Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: nodes = self.ring.get_part_nodes(int(partition)) Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: File /usr/lib/python2.7/dist-packages/swift/common/ring/ring.py, line 201, in get_part_nodes Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: if not (r[part] in seen_ids or seen_ids.add(r[part]))] Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: IndexError: array index out of range Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: Traceback (most recent call last): Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: File /usr/lib/python2.7/dist-packages/eventlet/greenpool.py, line 80, in _spawn_n_impl Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: func(*args, **kwargs) Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: File /usr/lib/python2.7/dist-packages/swift/common/db_replicator.py, line 398, in _replicate_object Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: nodes = self.ring.get_part_nodes(int(partition)) Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: File /usr/lib/python2.7/dist-packages/swift/common/ring/ring.py, line 201, in get_part_nodes Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: if not (r[part] in seen_ids or seen_ids.add(r[part]))] Mar 8 12:42:03 yahoo-128 account-replicator STDOUT: IndexError: array index out of range Mar 8 12:42:03 yahoo-128 account-replicator Replication run OVER Mar 8 12:42:03 yahoo-128 account-replicator Attempted to replicate 3 dbs in 0.02536 seconds (118.26332/s) Mar 8 12:42:03 yahoo-128 account-replicator Removed 0 dbs Mar 8 12:42:03 yahoo-128 account-replicator 1 successes, 0 failures Mar 8 12:42:03 yahoo-128 account-replicator no_change:1 ts_repl:0 diff:0 rsync:0 diff_capped:0 hashmatch:0 empty:0 Additionally, while the transfer of a big file was going on(4GB), I got the following error in logs. proxy-server ERROR with Object server 10.0.1.1:6000/sdb1 re: Trying to write to /v1/AUTH_28c949f34bd3b5fb295cffb69ed4/data_dir/data_dir/Feb27/PRIVATE/AVCHD/BDMV/STREAM/2.MTS: ChunkWriteTimeout (10s) Any suggestions? -- Shashank Sahni ___ 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] How to enable EC2 compatibility layer in Keystone
Hi everyone, I've successfully installed keystone(folsom release), glance and swift. I'm able to create the ec2 credentials for any user, but keystone daemon isn't listening on port 8773. I've configured services and endpoints appropriately to point to url http://keystone_ip:8773/services/Cloud, but there doesn't seem to be any service listening on port 8773(netstat returns only port 5000 as up). Please find 'ec2' specific configuration in my keystone.conf file below. [ec2] driver = keystone.contrib.ec2.backends.sql.Ec2 [filter:ec2_extension] paste.filter_factory = keystone.contrib.ec2:Ec2Extension.factory [pipeline:public_api] pipeline = stats_monitoring url_normalize token_auth admin_token_auth xml_body json_body debug ec2_extension user_crud_extension public_service [pipeline:admin_api] pipeline = stats_monitoring url_normalize token_auth admin_token_auth xml_body json_body debug stats_reporting ec2_extension s3_extension crud_extension admin_service Any suggestions? -- Shashank Sahni ___ 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] Swift installation verification fails
Hi,
I got it running. A foolish mistake. I mentioned the swift endpoint as
http, where as proxy was running https :O
--
Shashank Sahni
On Thu, Nov 22, 2012 at 12:27 PM, Shashank Sahni shredde...@gmail.comwrote:
Hi,
I'm following the steps mentioned in the official object storage
documentation.
http://docs.openstack.org/folsom/openstack-object-storage/admin/content/verify-swift-installation.html
I followed the steps as it is and all the services are up and running with
no traces of any error in /var/log/syslog. Note that, I'm trying to run
swift proxy and storage service on the same node. Keystone is on a separate
server. I've already configured glance successfully, hence I believe
keystone is successfully up. As I mentioned previously, keystone is even
responding to swift because if I enter wrong password it returns
'authentication failed'.
Any thoughts?
--
Shashank Sahni
On Wed, Nov 21, 2012 at 2:02 PM, Kuo Hugo tonyt...@gmail.com wrote:
Hi ,
For keystone 2.0 auth
the request should provide a json format which includes username / tenant
/ password .
In your curl test , you provide two headers to auth 2.0 .
Please have a look at officail document to get the right API call.
2012/11/21 Shashank Sahni shredde...@gmail.com
Hi,
Thanks for the response. I went head to verify using curl and ran.
$ curl -k -v -H 'X-Storage-User: admin:admin' -H 'X-Storage-Pass: '
http://10.2.4.115:5000/v2.0
Here is the output. I don't see the token or storage-url anywhere. Note
that, 10.2.4.115 is the keystone server.
* About to connect() to 10.2.4.115 port 5000 (#0)
* Trying 10.2.4.115... connected
GET /v2.0 HTTP/1.1
User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0
OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
Host: 10.2.4.115:5000
Accept: */*
X-Storage-User: admin:admin
X-Storage-Pass: x
HTTP/1.1 200 OK
Vary: X-Auth-Token
Content-Type: application/json
Date: Wed, 21 Nov 2012 05:46:25 GMT
Transfer-Encoding: chunked
* Connection #0 to host 10.2.4.115 left intact
* Closing connection #0
{version: {status: beta, updated: 2011-11-19T00:00:00Z,
media-types: [{base: application/json, type:
application/vnd.openstack.identity-v2.0+json}, {base:
application/xml, type: application/vnd.openstack.identity-v2.0+xml}],
id: v2.0, links: [{href: http://10.2.4.115:5000/v2.0/;, rel:
self}, {href:
http://docs.openstack.org/api/openstack-identity-service/2.0/content/;,
type: text/html, rel: describedby}, {href:
http://docs.openstack.org/api/openstack-identity-service/2.0/identity-dev-guide-2.0.pdf;,
type: application/pdf, rel: describedby}]}}
--
Shashank Sahni
On Wed, Nov 21, 2012 at 12:48 AM, Hugo tonyt...@gmail.com wrote:
In my suggestion, using curl for verifying keystone first. And then
using curl to access swift proxy with the returned token and
service-endpoint from previous keystone operation.
It must give u more clear clues.
從我的 iPhone 傳送
Shashank Sahni shredde...@gmail.com 於 2012/11/20 下午6:40 寫道：
Hi,
I'm trying to install Swift 1.7.4 on Ubuntu 12.04. The installation is
multi-node with keystone and swift(proxy+storage) running on separate
systems. Keystone is up and running perfectly fine. Swift user and service
endpoints are created correctly to point to the swift_node. Swift is
configured and all its services are up. But during swift installation
verification, the following commands hangs with no output.
swift -V 2 -A
http://keystone_server:5000/v2.0http://localhost:5000/v2.0-U admin:admin
-K admin_pass stat
I'm sure its able to contact the keystone server. This is because if I
change admin_pass, it throws authentication failure error. It probably
fails in the next step which I'm unaware of.
Here is my proxy-server.conf file.
[DEFAULT]
# Enter these next two values if using SSL certifications
cert_file = /etc/swift/cert.crt
key_file = /etc/swift/cert.key
bind_port =
user = swift
[pipeline:main]
#pipeline = healthcheck cache swift3 authtoken keystone proxy-server
pipeline = healthcheck cache swift3 authtoken keystone proxy-server
[app:proxy-server]
use = egg:swift#proxy
allow_account_management = true
account_autocreate = true
[filter:swift3]
use=egg:swift3#swift3
[filter:keystone]
paste.filter_factory = keystone.middleware.swift_auth:filter_factory
operator_roles = Member,admin, swiftoperator
[filter:authtoken]
paste.filter_factory = keystone.middleware.auth_token:filter_factory
# Delaying the auth decision is required to support token-less
# usage for anonymous referrers ('.r:*').
delay_auth_decision = 10
service_port = 5000
service_host = keystone_server
auth_port = 35357
auth_host = keystone_server
auth_protocol = http
auth_uri = http://keystone_server:5000/
auth_token =
admin_token =
admin_tenant_name = service
admin_user = swift
admin_password =
signing_dir = /etc/swift
[filter:cache]
use = egg:swift#memcache
[Openstack] Keystone doesn't return X-Auth-Token and X-Storage-URL
Hi,
I'm trying to install swift. I'm able to start all the relevant services,
but I'm getting error during verification while following the instructions
mentioned here.
http://docs.openstack.org/trunk/openstack-object-storage/admin/content/verify-swift-installation.html
The first command
$ swift -V 2.0 -A http://AUTH_HOSTNAME:5000/v2.0 -U demo:admin -K
$ADMINPASS stat
returns
Account: AUTH_2b2f3b2f1db5442ca05a823dcbb047e1
Containers: 0
Objects: 0
Bytes: 0
Accept-Ranges: bytes
X-Timestamp: 1353569489.57971
But when I try to run
$ curl -k -v -H 'X-Storage-User: demo:admin' -H 'X-Storage-Pass:
$ADMINPASS' http://AUTH_HOSTNAME:5000/auth/v2.0
It doesn't return X-Auth-Token and X-Storage-URL. I believe this shows some
trouble with Keystone, but I already have glance successfully configured.
Here is the output.
* About to connect() to 10.2.4.115 port 5000 (#0)
* Trying 10.2.4.115... connected
GET /v2.0 HTTP/1.1
User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0
OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
Host: 10.2.4.115:5000
Accept: */*
X-Storage-User: admin:admin
X-Storage-Pass: x
HTTP/1.1 200 OK
Vary: X-Auth-Token
Content-Type: application/json
Date: Wed, 21 Nov 2012 05:46:25 GMT
Transfer-Encoding: chunked
* Connection #0 to host 10.2.4.115 left intact
* Closing connection #0
{version: {status: beta, updated: 2011-11-19T00:00:00Z,
media-types: [{base: application/json, type:
application/vnd.openstack.
identity-v2.0+json}, {base: application/xml, type:
application/vnd.openstack.identity-v2.0+xml}], id: v2.0, links:
[{href: http://10.2.4.115:5000/v2.0/;, rel: self}, {href:
http://docs.openstack.org/api/openstack-identity-service/2.0/content/;,
type: text/html, rel: describedby}, {href:
http://docs.openstack.org/api/openstack-identity-service/2.0/identity-dev-guide-2.0.pdf;,
type: application/pdf, rel: describedby}]}}
Any thoughts?
--
Shashank Sahni
___
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] Keystone doesn't return X-Auth-Token and X-Storage-URL
Hi Kuo,
Thanks for a quick reply. This method got me the token, but the service
catalog was returned empty. Here is the comman ran and output.
$ curl -d '{auth:{passwordCredentials:{username: admin, password:
}}}' -H Content-type: application/json
http://10.2.4.115:5000/v2.0/tokens
{access: {token: {expires: 2012-11-23T11:14:46Z, id:
8f047727d3144658a521b9a9443c060c}, serviceCatalog: {}, user:
{username: admin, roles_links: [], id:
0d34dea491c746ecae426adb301430e6, roles: [], name: admin}}}
--
Shashank Sahni
On Thu, Nov 22, 2012 at 4:35 PM, Kuo Hugo tonyt...@gmail.com wrote:
http://docs.openstack.org/developer/keystone/api_curl_examples.html
curl -d '{auth:{passwordCredentials:{username: admin, password:
$ADMINPASS}}}' -H Content-type: application/json
http://localhost:35357/v2.0/tokens
2012/11/22 Shashank Sahni shredde...@gmail.com
Hi,
I'm trying to install swift. I'm able to start all the relevant services,
but I'm getting error during verification while following the instructions
mentioned here.
http://docs.openstack.org/trunk/openstack-object-storage/admin/content/verify-swift-installation.html
The first command
$ swift -V 2.0 -A http://AUTH_HOSTNAME:5000/v2.0 -U demo:admin -K
$ADMINPASS stat
returns
Account: AUTH_2b2f3b2f1db5442ca05a823dcbb047e1
Containers: 0
Objects: 0
Bytes: 0
Accept-Ranges: bytes
X-Timestamp: 1353569489.57971
But when I try to run
$ curl -k -v -H 'X-Storage-User: demo:admin' -H 'X-Storage-Pass:
$ADMINPASS' http://AUTH_HOSTNAME:5000/auth/v2.0
It doesn't return X-Auth-Token and X-Storage-URL. I believe this shows
some trouble with Keystone, but I already have glance successfully
configured. Here is the output.
* About to connect() to 10.2.4.115 port 5000 (#0)
* Trying 10.2.4.115... connected
GET /v2.0 HTTP/1.1
User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0
OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
Host: 10.2.4.115:5000
Accept: */*
X-Storage-User: admin:admin
X-Storage-Pass: x
HTTP/1.1 200 OK
Vary: X-Auth-Token
Content-Type: application/json
Date: Wed, 21 Nov 2012 05:46:25 GMT
Transfer-Encoding: chunked
* Connection #0 to host 10.2.4.115 left intact
* Closing connection #0
{version: {status: beta, updated: 2011-11-19T00:00:00Z,
media-types: [{base: application/json, type:
application/vnd.openstack.
identity-v2.0+json}, {base: application/xml, type:
application/vnd.openstack.identity-v2.0+xml}], id: v2.0, links:
[{href: http://10.2.4.115:5000/v2.0/;, rel: self}, {href:
http://docs.openstack.org/api/openstack-identity-service/2.0/content/;,
type: text/html, rel: describedby}, {href:
http://docs.openstack.org/api/openstack-identity-service/2.0/identity-dev-guide-2.0.pdf;,
type: application/pdf, rel: describedby}]}}
Any thoughts?
--
Shashank Sahni
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
+Hugo Kuo+
tonyt...@gmail.com
+ tonyt...@gmail.com886 935004793
___
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] Keystone doesn't return X-Auth-Token and X-Storage-URL
Hi,
Additionally, I'm unable to create a container using swift cli. When I run
swift post mycontainer I get the following error.
Container POST failed:
http://10.2.4.130:/v1/AUTH_2b2f3b2f1db5442ca05a823dcbb047e1/mycontainer400
Bad Request [first 60 chars of response] Invalid path:
/sdb1/188788/AUTH_2b2f3b2f1db5442ca05a823dcbb0
10.2.4.130 is running swift-proxy and storage node services. I'm running
the command with 'admin' credentials. Hence, I believe it shouldn't be a
role issue considering that by default admin is allowed to perform storage
operations.
--
Shashank Sahni
On Thu, Nov 22, 2012 at 4:47 PM, Shashank Sahni shredde...@gmail.comwrote:
Hi Kuo,
Thanks for a quick reply. This method got me the token, but the service
catalog was returned empty. Here is the comman ran and output.
$ curl -d '{auth:{passwordCredentials:{username: admin,
password: }}}' -H Content-type: application/json
http://10.2.4.115:5000/v2.0/tokens
{access: {token: {expires: 2012-11-23T11:14:46Z, id:
8f047727d3144658a521b9a9443c060c}, serviceCatalog: {}, user:
{username: admin, roles_links: [], id:
0d34dea491c746ecae426adb301430e6, roles: [], name: admin}}}
--
Shashank Sahni
On Thu, Nov 22, 2012 at 4:35 PM, Kuo Hugo tonyt...@gmail.com wrote:
http://docs.openstack.org/developer/keystone/api_curl_examples.html
curl -d '{auth:{passwordCredentials:{username: admin, password:
$ADMINPASS}}}' -H Content-type: application/json
http://localhost:35357/v2.0/tokens
2012/11/22 Shashank Sahni shredde...@gmail.com
Hi,
I'm trying to install swift. I'm able to start all the relevant
services, but I'm getting error during verification while following the
instructions mentioned here.
http://docs.openstack.org/trunk/openstack-object-storage/admin/content/verify-swift-installation.html
The first command
$ swift -V 2.0 -A http://AUTH_HOSTNAME:5000/v2.0 -U demo:admin -K
$ADMINPASS stat
returns
Account: AUTH_2b2f3b2f1db5442ca05a823dcbb047e1
Containers: 0
Objects: 0
Bytes: 0
Accept-Ranges: bytes
X-Timestamp: 1353569489.57971
But when I try to run
$ curl -k -v -H 'X-Storage-User: demo:admin' -H 'X-Storage-Pass:
$ADMINPASS' http://AUTH_HOSTNAME:5000/auth/v2.0
It doesn't return X-Auth-Token and X-Storage-URL. I believe this shows
some trouble with Keystone, but I already have glance successfully
configured. Here is the output.
* About to connect() to 10.2.4.115 port 5000 (#0)
* Trying 10.2.4.115... connected
GET /v2.0 HTTP/1.1
User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0
OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
Host: 10.2.4.115:5000
Accept: */*
X-Storage-User: admin:admin
X-Storage-Pass: x
HTTP/1.1 200 OK
Vary: X-Auth-Token
Content-Type: application/json
Date: Wed, 21 Nov 2012 05:46:25 GMT
Transfer-Encoding: chunked
* Connection #0 to host 10.2.4.115 left intact
* Closing connection #0
{version: {status: beta, updated: 2011-11-19T00:00:00Z,
media-types: [{base: application/json, type:
application/vnd.openstack.
identity-v2.0+json}, {base: application/xml, type:
application/vnd.openstack.identity-v2.0+xml}], id: v2.0, links:
[{href: http://10.2.4.115:5000/v2.0/;, rel: self}, {href:
http://docs.openstack.org/api/openstack-identity-service/2.0/content/;,
type: text/html, rel: describedby}, {href:
http://docs.openstack.org/api/openstack-identity-service/2.0/identity-dev-guide-2.0.pdf;,
type: application/pdf, rel: describedby}]}}
Any thoughts?
--
Shashank Sahni
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
+Hugo Kuo+
tonyt...@gmail.com
+ tonyt...@gmail.com886 935004793
___
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] Swift installation verification fails
Hi,
I'm following the steps mentioned in the official object storage
documentation.
http://docs.openstack.org/folsom/openstack-object-storage/admin/content/verify-swift-installation.html
I followed the steps as it is and all the services are up and running with
no traces of any error in /var/log/syslog. Note that, I'm trying to run
swift proxy and storage service on the same node. Keystone is on a separate
server. I've already configured glance successfully, hence I believe
keystone is successfully up. As I mentioned previously, keystone is even
responding to swift because if I enter wrong password it returns
'authentication failed'.
Any thoughts?
--
Shashank Sahni
On Wed, Nov 21, 2012 at 2:02 PM, Kuo Hugo tonyt...@gmail.com wrote:
Hi ,
For keystone 2.0 auth
the request should provide a json format which includes username / tenant
/ password .
In your curl test , you provide two headers to auth 2.0 .
Please have a look at officail document to get the right API call.
2012/11/21 Shashank Sahni shredde...@gmail.com
Hi,
Thanks for the response. I went head to verify using curl and ran.
$ curl -k -v -H 'X-Storage-User: admin:admin' -H 'X-Storage-Pass: '
http://10.2.4.115:5000/v2.0
Here is the output. I don't see the token or storage-url anywhere. Note
that, 10.2.4.115 is the keystone server.
* About to connect() to 10.2.4.115 port 5000 (#0)
* Trying 10.2.4.115... connected
GET /v2.0 HTTP/1.1
User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0
OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
Host: 10.2.4.115:5000
Accept: */*
X-Storage-User: admin:admin
X-Storage-Pass: x
HTTP/1.1 200 OK
Vary: X-Auth-Token
Content-Type: application/json
Date: Wed, 21 Nov 2012 05:46:25 GMT
Transfer-Encoding: chunked
* Connection #0 to host 10.2.4.115 left intact
* Closing connection #0
{version: {status: beta, updated: 2011-11-19T00:00:00Z,
media-types: [{base: application/json, type:
application/vnd.openstack.identity-v2.0+json}, {base:
application/xml, type: application/vnd.openstack.identity-v2.0+xml}],
id: v2.0, links: [{href: http://10.2.4.115:5000/v2.0/;, rel:
self}, {href:
http://docs.openstack.org/api/openstack-identity-service/2.0/content/;,
type: text/html, rel: describedby}, {href:
http://docs.openstack.org/api/openstack-identity-service/2.0/identity-dev-guide-2.0.pdf;,
type: application/pdf, rel: describedby}]}}
--
Shashank Sahni
On Wed, Nov 21, 2012 at 12:48 AM, Hugo tonyt...@gmail.com wrote:
In my suggestion, using curl for verifying keystone first. And then
using curl to access swift proxy with the returned token and
service-endpoint from previous keystone operation.
It must give u more clear clues.
從我的 iPhone 傳送
Shashank Sahni shredde...@gmail.com 於 2012/11/20 下午6:40 寫道：
Hi,
I'm trying to install Swift 1.7.4 on Ubuntu 12.04. The installation is
multi-node with keystone and swift(proxy+storage) running on separate
systems. Keystone is up and running perfectly fine. Swift user and service
endpoints are created correctly to point to the swift_node. Swift is
configured and all its services are up. But during swift installation
verification, the following commands hangs with no output.
swift -V 2 -A
http://keystone_server:5000/v2.0http://localhost:5000/v2.0-U admin:admin
-K admin_pass stat
I'm sure its able to contact the keystone server. This is because if I
change admin_pass, it throws authentication failure error. It probably
fails in the next step which I'm unaware of.
Here is my proxy-server.conf file.
[DEFAULT]
# Enter these next two values if using SSL certifications
cert_file = /etc/swift/cert.crt
key_file = /etc/swift/cert.key
bind_port =
user = swift
[pipeline:main]
#pipeline = healthcheck cache swift3 authtoken keystone proxy-server
pipeline = healthcheck cache swift3 authtoken keystone proxy-server
[app:proxy-server]
use = egg:swift#proxy
allow_account_management = true
account_autocreate = true
[filter:swift3]
use=egg:swift3#swift3
[filter:keystone]
paste.filter_factory = keystone.middleware.swift_auth:filter_factory
operator_roles = Member,admin, swiftoperator
[filter:authtoken]
paste.filter_factory = keystone.middleware.auth_token:filter_factory
# Delaying the auth decision is required to support token-less
# usage for anonymous referrers ('.r:*').
delay_auth_decision = 10
service_port = 5000
service_host = keystone_server
auth_port = 35357
auth_host = keystone_server
auth_protocol = http
auth_uri = http://keystone_server:5000/
auth_token =
admin_token =
admin_tenant_name = service
admin_user = swift
admin_password =
signing_dir = /etc/swift
[filter:cache]
use = egg:swift#memcache
set log_name = cache
[filter:catch_errors]
use = egg:swift#catch_errors
[filter:healthcheck]
use = egg:swift#healthcheck
Any suggestion?
--
Shashank Sahni
___
Mailing list
[Openstack] Swift installation verification fails
Hi,
I'm trying to install Swift 1.7.4 on Ubuntu 12.04. The installation is
multi-node with keystone and swift(proxy+storage) running on separate
systems. Keystone is up and running perfectly fine. Swift user and service
endpoints are created correctly to point to the swift_node. Swift is
configured and all its services are up. But during swift installation
verification, the following commands hangs with no output.
swift -V 2 -A http://keystone_server:5000/v2.0
http://localhost:5000/v2.0-U admin:admin -K admin_pass stat
I'm sure its able to contact the keystone server. This is because if I
change admin_pass, it throws authentication failure error. It probably
fails in the next step which I'm unaware of.
Here is my proxy-server.conf file.
[DEFAULT]
# Enter these next two values if using SSL certifications
cert_file = /etc/swift/cert.crt
key_file = /etc/swift/cert.key
bind_port =
user = swift
[pipeline:main]
#pipeline = healthcheck cache swift3 authtoken keystone proxy-server
pipeline = healthcheck cache swift3 authtoken keystone proxy-server
[app:proxy-server]
use = egg:swift#proxy
allow_account_management = true
account_autocreate = true
[filter:swift3]
use=egg:swift3#swift3
[filter:keystone]
paste.filter_factory = keystone.middleware.swift_auth:filter_factory
operator_roles = Member,admin, swiftoperator
[filter:authtoken]
paste.filter_factory = keystone.middleware.auth_token:filter_factory
# Delaying the auth decision is required to support token-less
# usage for anonymous referrers ('.r:*').
delay_auth_decision = 10
service_port = 5000
service_host = keystone_server
auth_port = 35357
auth_host = keystone_server
auth_protocol = http
auth_uri = http://keystone_server:5000/
auth_token =
admin_token =
admin_tenant_name = service
admin_user = swift
admin_password =
signing_dir = /etc/swift
[filter:cache]
use = egg:swift#memcache
set log_name = cache
[filter:catch_errors]
use = egg:swift#catch_errors
[filter:healthcheck]
use = egg:swift#healthcheck
Any suggestion?
--
Shashank Sahni
___
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] Swift installation verification fails
Hi,
Thanks for the response. I went head to verify using curl and ran.
$ curl -k -v -H 'X-Storage-User: admin:admin' -H 'X-Storage-Pass: '
http://10.2.4.115:5000/v2.0
Here is the output. I don't see the token or storage-url anywhere. Note
that, 10.2.4.115 is the keystone server.
* About to connect() to 10.2.4.115 port 5000 (#0)
* Trying 10.2.4.115... connected
GET /v2.0 HTTP/1.1
User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0
OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
Host: 10.2.4.115:5000
Accept: */*
X-Storage-User: admin:admin
X-Storage-Pass: x
HTTP/1.1 200 OK
Vary: X-Auth-Token
Content-Type: application/json
Date: Wed, 21 Nov 2012 05:46:25 GMT
Transfer-Encoding: chunked
* Connection #0 to host 10.2.4.115 left intact
* Closing connection #0
{version: {status: beta, updated: 2011-11-19T00:00:00Z,
media-types: [{base: application/json, type:
application/vnd.openstack.identity-v2.0+json}, {base:
application/xml, type: application/vnd.openstack.identity-v2.0+xml}],
id: v2.0, links: [{href: http://10.2.4.115:5000/v2.0/;, rel:
self}, {href:
http://docs.openstack.org/api/openstack-identity-service/2.0/content/;,
type: text/html, rel: describedby}, {href:
http://docs.openstack.org/api/openstack-identity-service/2.0/identity-dev-guide-2.0.pdf;,
type: application/pdf, rel: describedby}]}}
--
Shashank Sahni
On Wed, Nov 21, 2012 at 12:48 AM, Hugo tonyt...@gmail.com wrote:
In my suggestion, using curl for verifying keystone first. And then using
curl to access swift proxy with the returned token and service-endpoint
from previous keystone operation.
It must give u more clear clues.
從我的 iPhone 傳送
Shashank Sahni shredde...@gmail.com 於 2012/11/20 下午6:40 寫道：
Hi,
I'm trying to install Swift 1.7.4 on Ubuntu 12.04. The installation is
multi-node with keystone and swift(proxy+storage) running on separate
systems. Keystone is up and running perfectly fine. Swift user and service
endpoints are created correctly to point to the swift_node. Swift is
configured and all its services are up. But during swift installation
verification, the following commands hangs with no output.
swift -V 2 -A http://keystone_server:5000/v2.0http://localhost:5000/v2.0-U
admin:admin -K admin_pass stat
I'm sure its able to contact the keystone server. This is because if I
change admin_pass, it throws authentication failure error. It probably
fails in the next step which I'm unaware of.
Here is my proxy-server.conf file.
[DEFAULT]
# Enter these next two values if using SSL certifications
cert_file = /etc/swift/cert.crt
key_file = /etc/swift/cert.key
bind_port =
user = swift
[pipeline:main]
#pipeline = healthcheck cache swift3 authtoken keystone proxy-server
pipeline = healthcheck cache swift3 authtoken keystone proxy-server
[app:proxy-server]
use = egg:swift#proxy
allow_account_management = true
account_autocreate = true
[filter:swift3]
use=egg:swift3#swift3
[filter:keystone]
paste.filter_factory = keystone.middleware.swift_auth:filter_factory
operator_roles = Member,admin, swiftoperator
[filter:authtoken]
paste.filter_factory = keystone.middleware.auth_token:filter_factory
# Delaying the auth decision is required to support token-less
# usage for anonymous referrers ('.r:*').
delay_auth_decision = 10
service_port = 5000
service_host = keystone_server
auth_port = 35357
auth_host = keystone_server
auth_protocol = http
auth_uri = http://keystone_server:5000/
auth_token =
admin_token =
admin_tenant_name = service
admin_user = swift
admin_password =
signing_dir = /etc/swift
[filter:cache]
use = egg:swift#memcache
set log_name = cache
[filter:catch_errors]
use = egg:swift#catch_errors
[filter:healthcheck]
use = egg:swift#healthcheck
Any suggestion?
--
Shashank Sahni
___
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] Error while enabling s3 support in swift
Hi, I'm trying to install swift 1.7.4 on Ubuntu 12.04. In order to enable the s3 support, I added the appropriate parameters in the /etc/swift/proxy-server.conf file [filter:swift3] use=egg:swift#swift3 and installed the package swift-plugin-s3. But when I try to start the proxy-server I get the following error. LookupError: Entry point 'swift3' not found in egg 'swift' (dir: /usr/lib/python2.7/dist-packages; protocols: paste.filter_factory, paste.filter_app_factory; entry_points: ) Note that, proxy server runs fine without s3 support. Suggestions? -- Shashank Sahni ___ 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] Error while enabling s3 support in swift
I haven't tested but the proxy server has started fine. Thanks. -- Shashank Sahni On Tue, Nov 20, 2012 at 12:55 PM, John Dickinson m...@not.mn wrote: check out the README at https://github.com/fujita/swift3 for the correct proxy server config section. --john On Nov 19, 2012, at 11:22 PM, Shashank Sahni shredde...@gmail.com wrote: Hi, I'm trying to install swift 1.7.4 on Ubuntu 12.04. In order to enable the s3 support, I added the appropriate parameters in the /etc/swift/proxy-server.conf file [filter:swift3] use=egg:swift#swift3 and installed the package swift-plugin-s3. But when I try to start the proxy-server I get the following error. LookupError: Entry point 'swift3' not found in egg 'swift' (dir: /usr/lib/python2.7/dist-packages; protocols: paste.filter_factory, paste.filter_app_factory; entry_points: ) Note that, proxy server runs fine without s3 support. Suggestions? -- Shashank Sahni ___ 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] Dashboard doesn't list out multiple projects associated with a user
Hi, I'm trying to make use of tenant feature provided by keystone. I want each user to have one default project and based on the requirements make them part of others enabling them to work in groups. Tenant is perfect for such setup. My understanding is that in order to add a user to a tenant we use 'user-role-add' option of python keystone client. I've been playing with it for a while and it seems to be working. I can see the same user as part of multiple projects(with member roles) in the admin syspanel. But when I log in as the user I can't see the list of projects the user is part of. The default project is the one in which the user has been most recently added. I believe the project title button is meant to be a drop down list but isn't showing anything. I might be missing something trivial here. Some help would be greatly appreciated. Kind Regards, Shashank Sahni ___ 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 attaching disks to an instance
Thanks for the info. This way is indeed more convenient. -- Shashank Sahni On Tue, May 15, 2012 at 10:57 PM, Vishvananda Ishaya vishvana...@gmail.comwrote: FYI iscsi_ip_prefix doesn't exist in essex. The ip is passed back to the compute node based on what it has stored in the database, so the compute node no longer finds it through discovery and matching to the prefix. You should only need iscsi_ip_address on the volume node to make sure that the db entry is created properly. Vish On May 15, 2012, at 12:25 AM, Razique Mahroua wrote: In fact, it looks like the service is not able to retrieve the nova-volume' IP; as if there were some issue parsing the flag or something like that. Could you try by commenting that entry on all your servers : --iscsi_ip_address and only keep the prefix ? Razique Shashank Sahni shredde...@linuxers.org 14 mai 2012 18:22 Hi, Oh! They are same. I just masked the values before pasting the configuration files. Although, now that I think of it, its pretty harmless. Here are the originals. controller node - http://paste.openstack.org/show/17513/ compute node - http://paste.openstack.org/show/17514/ volume node - http://paste.openstack.org/show/17515/ As per my understanding, I just need to figure out how the volume node is identified. Thank you for replying. Regards, Shashank Sahni ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Nuage Co - Razique Mahroua razique.mahr...@gmail.com image.jpg ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp postbox-contact.jpg___ 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] Problem with attaching disks to an instance
Hi everyone, I'm trying to configure a multi-node installation. Here is a brief overview. 1) controller - api+network+scheduler+novnc+glance+keystone (nova.conf - http://paste.openstack.org/show/17470/) 2) compute node (nova.conf - http://paste.openstack.org/show/17469) 3) volume node(single) Compute and vnc are working fine. I'm able to create and delete volumes. Iscsi discovery from the compute nodes is working too. But when I try to attach a volume, the compute node tries to connect to the controller node instead of volume and hence crashes with the following error. 2012-05-14 17:32:13 TRACE nova.rpc.amqp ProcessExecutionError: Unexpected error while running command. 2012-05-14 17:32:13 TRACE nova.rpc.amqp Command: sudo nova-rootwrap iscsiadm -m node -T iqn.2010-10.org.openstack:volume-0003 -p controller:3260 --rescan 2012-05-14 17:32:13 TRACE nova.rpc.amqp Exit code: 255 2012-05-14 17:32:13 TRACE nova.rpc.amqp Stdout: '' 2012-05-14 17:32:13 TRACE nova.rpc.amqp Stderr: 'iscsiadm: No portal found.\n' Any suggestions? Kind Regards, Shashank Sahni ___ 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 attaching disks to an instance
Hi, I set this option in the configuration files of both compute and controller. Restarted the service, but unfortunately same result. Regards, Shashank Sahni On 05/14/2012 05:58 PM, Razique Mahroua wrote: Hi, do you have the flag iscsi_ip_prefix configured in your nova.conf ? Razique Shashank Sahni 14 mai 2012 14:22 Hi everyone, I'm trying to configure a multi-node installation. Here is a brief overview. 1) controller - api+network+scheduler+novnc+glance+keystone (nova.conf - http://paste.openstack.org/show/17470/) 2) compute node (nova.conf - http://paste.openstack.org/show/17469) 3) volume node(single) Compute and vnc are working fine. I'm able to create and delete volumes. Iscsi discovery from the compute nodes is working too. But when I try to attach a volume, the compute node tries to connect to the controller node instead of volume and hence crashes with the following error. 2012-05-14 17:32:13 TRACE nova.rpc.amqp ProcessExecutionError: Unexpected error while running command. 2012-05-14 17:32:13 TRACE nova.rpc.amqp Command: sudo nova-rootwrap iscsiadm -m node -T iqn.2010-10.org.openstack:volume-0003 -p controller:3260 --rescan 2012-05-14 17:32:13 TRACE nova.rpc.amqp Exit code: 255 2012-05-14 17:32:13 TRACE nova.rpc.amqp Stdout: '' 2012-05-14 17:32:13 TRACE nova.rpc.amqp Stderr: 'iscsiadm: No portal found.\n' Any suggestions? Kind Regards, Shashank Sahni ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Nuage Co - Razique Mahroua razique.mahr...@gmail.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
Re: [Openstack] Problem with attaching disks to an instance
Hi,
Thanks for your suggestion. I had earlier configured them to be the
controller node. I tried setting them to the volume node but no
result. I get the following error on running "nova volume-list"
ERROR: n/a (HTTP 400)
As I previously mentioned, volume creation and deletion is working
fine, its the volume node assignment that's flawed.
Regards,
Shashank Sahni
On 05/14/2012 07:00 PM, Yong Sheng Gong wrote:
Hi,
consider to change
catalog.RegionOne.volume.publicURL = http://volumenode:8776/v1/$(tenant_id)s
catalog.RegionOne.volume.adminURL = http://volumenode:8776/v1/$(tenant_id)s
catalog.RegionOne.volume.internalURL = http://v:8776/v1/$(tenant_id)s
catalog.RegionOne.volume.name = Volume Service
It seems your openstack is looking for the volume on
wrong volume server.
-openstack-bounces+gongysh=cn.ibm@lists.launchpad.net
wrote: -
To: Razique Mahroua razique.mahr...@gmail.com
From: Shashank Sahni <shredde...@linuxers.org>
Sent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.net
Date: 05/14/2012 09:20PM
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Problem with attaching disks to
an instance
Hi,
I set this option in the configuration files of both
compute and controller. Restarted the service, but
unfortunately same result.
Regards,
Shashank Sahni
On 05/14/2012 05:58 PM, Razique Mahroua wrote:
Hi,
do you have the flag iscsi_ip_prefix configured in
your nova.conf ?
Razique
Shashank Sahni
14 mai 2012 14:22
Hi everyone,
I'm trying to configure a multi-node
installation. Here is a brief overview.
1) controller -
api+network+scheduler+novnc+glance+keystone
(nova.conf - http://paste.openstack.org/show/17470/)
2) compute node (nova.conf - http://paste.openstack.org/show/17469)
3) volume node(single)
Compute and vnc are working fine. I'm able to
create and delete volumes. Iscsi discovery from
the compute nodes is working too. But when I try
to attach a volume, the compute node tries to
connect to the controller node instead of volume
and hence crashes with the following error.
2012-05-14 17:32:13 TRACE nova.rpc.amqp
ProcessExecutionError: Unexpected error while
running command.
2012-05-14 17:32:13 TRACE nova.rpc.amqp Command:
sudo nova-rootwrap iscsiadm -m node -T
iqn.2010-10.org.openstack:volume-0003 -p
controller:3260 --rescan
2012-05-14 17:32:13 TRACE nova.rpc.amqp Exit
code: 255
2012-05-14 17:32:13 TRACE nova.rpc.amqp Stdout:
''
2012-05-14 17:32:13 TRACE nova.rpc.amqp Stderr:
'iscsiadm: No portal found.\n'
Any suggestions?
Kind Regards,
Shashank Sahni
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
Nuage
Co - Razique Mahroua
razique.mahr...@gmail.com
___
Re: [Openstack] Problem with attaching disks to an instance
Hi,
Thanks for the reply.
Yes, I've gone through the document. Volume creation and deletion
are working perfectly fine. When I run "iscsiadm -m discovery -t st
-p volume_node" on the compute node, I can see the volumes. But
somehow the compute node is being misinformed about the volume node
after giving the attach command.
I'm not using iscsitarget as per that document. Installation of
nova-volume on ubuntu precise automatically took care of it using
tgt.
Kind Regards,
Shashank Sahni
On 05/14/2012 07:34 PM, raja.me...@wipro.com wrote:
Hi
Shashank ,
I
preassume that the steps outlined in the link below has been
followed.
http://docs.openstack.org/trunk/openstack-compute/admin/content/managing-volumes.html
Thanks
Meena
Raja
From:
openstack-bounces+raja.meena=wipro@lists.launchpad.net
[mailto:openstack-bounces+raja.meena=wipro@lists.launchpad.net]
On Behalf Of
Shashank Sahni
Sent: Monday, May 14, 2012 6:23 PM
To: Razique Mahroua
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Problem with attaching
disks to an instance
Hi,
I set this option in the configuration files of both compute
and controller. Restarted the service, but unfortunately same
result.
Regards,
Shashank Sahni
On 05/14/2012 05:58 PM, Razique Mahroua wrote:
Hi,
do you have the flag iscsi_ip_prefix configured in your
nova.conf ?
Razique
Shashank
Sahni
14 mai
2012 14:22
Hi
everyone,
I'm trying to configure a multi-node installation. Here
is a brief overview.
1) controller -
api+network+scheduler+novnc+glance+keystone (nova.conf -
http://paste.openstack.org/show/17470/)
2) compute node (nova.conf -
http://paste.openstack.org/show/17469)
3) volume node(single)
Compute and vnc are working fine. I'm able to create and
delete volumes. Iscsi discovery from the compute nodes
is working too. But when I try to attach a volume, the
compute node tries to connect to the controller node
instead of volume and hence crashes with the following
error.
2012-05-14 17:32:13 TRACE nova.rpc.amqp
ProcessExecutionError: Unexpected error while running
command.
2012-05-14 17:32:13 TRACE nova.rpc.amqp Command: sudo
nova-rootwrap iscsiadm -m node -T
iqn.2010-10.org.openstack:volume-0003 -p
controller:3260 --rescan
2012-05-14 17:32:13 TRACE nova.rpc.amqp Exit code: 255
2012-05-14 17:32:13 TRACE nova.rpc.amqp Stdout: ''
2012-05-14 17:32:13 TRACE nova.rpc.amqp Stderr:
'iscsiadm: No portal found.\n'
Any suggestions?
Kind Regards,
Shashank Sahni
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
Nuage Co - Razique Mahroua
razique.mahr...@gmail.com
Please do not print this email unless it is absolutely
necessary.
The information contained in this electronic message and any
attachments to this message are intended for the exclusive use
of the addressee(s) and may contain proprietary, confidential or
privileged information. If you are not the intended recipient,
you should not d
Re: [Openstack] Problem with attaching disks to an instance
Hi,
Oh! They are same. I just masked the values before pasting the
configuration files. Although, now that I think of it, its pretty
harmless. Here are the originals.
controller node - http://paste.openstack.org/show/17513/
compute node - http://paste.openstack.org/show/17514/
volume node - http://paste.openstack.org/show/17515/
As per my understanding, I just need to figure out how the volume
node is identified. Thank you for replying.
Regards,
Shashank Sahni
On 05/14/2012 09:43 PM, George Mihaiescu wrote:
Is it possible that
you have two similar
entries in your hosts file?
I see that your nova.conf on the the compute node mentions volume-node but your successful "iscsiadm -m discovery -t st -p volume_node used a different host (volume-node vs. volume_node).
Try using IP addresses in the config and while testing iscsi discovery.
From:
openstack-bounces+george.mihaiescu=q9@lists.launchpad.net
[mailto:openstack-bounces+george.mihaiescu=q9@lists.launchpad.net]
On Behalf Of Shashank
Sahni
Sent:
Monday, May 14, 2012 10:28
AM
To:
raja.me...@wipro.com
Cc:
openstack@lists.launchpad.net
Subject:
Re: [Openstack] Problem
with attaching disks to an instance
Hi,
Thanks for the reply.
Yes, I've gone through the document. Volume creation and
deletion are working
perfectly fine. When I run "iscsiadm -m discovery -t st -p
volume_node" on the compute node, I can see the volumes.
But somehow the
compute node is being misinformed about the volume node
after giving the attach
command.
I'm not using iscsitarget as per that document.
Installation of nova-volume on
ubuntu precise automatically took care of it using tgt.
Kind Regards,
Shashank Sahni
On 05/14/2012 07:34 PM, raja.me...@wipro.com
wrote:
Hi Shashank ,
I
preassume that the
steps outlined in the link below has been followed.
http://docs.openstack.org/trunk/openstack-compute/admin/content/managing-volumes.html
Thanks
Meena
Raja
From: openstack-bounces+raja.meena=wipro@lists.launchpad.net
[mailto:openstack-bounces+raja.meena=wipro@lists.launchpad.net]
On Behalf Of Shashank
Sahni
Sent:
Monday, May 14, 2012 6:23 PM
To:
Razique Mahroua
Cc: openstack@lists.launchpad.net
Subject:
Re: [Openstack] Problem
with attaching disks to an instance
Hi,
I set this option in the configuration files of both
compute and controller.
Restarted the service, but unfortunately same result.
Regards,
Shashank Sahni
On 05/14/2012 05:58 PM, Razique Mahroua wrote:
Hi,
do you have the flag iscsi_ip_prefix configured in your
nova.conf ?
Razique
Shashank Sahni
14 mai 2012 14:22
Hi
everyone,
I'm trying to configure a multi-node installation.
Here is a brief overview.
1) controller -
api+network+scheduler+novnc+glance+keystone (nova.conf
- http://paste.openstack.org/show/17470/)
2) compute node (nova.conf - http://paste.openstack.org/show/17469)
3) volume node(single)
Compute and vnc are working fine. I'm able to create
and delete volumes. Iscsi
discovery from the compute nodes
Re: [Openstack] Problem with attaching disks to an instance
Hi Vish, Yeah you are right. I checked the settings in the volume database and for all volumes the entry is similar to following. controller_node:3260,3 iqn.2010-10.org.openstack:volume-0004 But it seems these entries are being generated automatically, i.e. as soon as I issue volume creation command. How do I fix this? I am already using properly configured iscsi_ip_address option in the controller's nova.conf file. Regards, Shashank Sahni On 05/15/2012 02:15 AM, Vishvananda Ishaya wrote: It should be getting the connection properties via the call to the volume node. Is it possible your volume in the database has incorrect properties stored in provider_location? It is set from the cofig iscsi_ip_address, so if you have not set that configuration option to a routable ip from compute - volume then it will not work. Also, changing the config option will not change the existing values in the db, so you might have to change those manually. Vish On May 14, 2012, at 7:28 AM, Shashank Sahni wrote: Hi, Thanks for the reply. Yes, I've gone through the document. Volume creation and deletion are working perfectly fine. When I run iscsiadm -m discovery -t st -p volume_node on the compute node, I can see the volumes. But somehow the compute node is being misinformed about the volume node after giving the attach command. I'm not using iscsitarget as per that document. Installation of nova-volume on ubuntu precise automatically took care of it using tgt. Kind Regards, Shashank Sahni On 05/14/2012 07:34 PM, raja.me...@wipro.com wrote: Hi Shashank , I preassume that the steps outlined in the link below has been followed. http://docs.openstack.org/trunk/openstack-compute/admin/content/managing-volumes.html Thanks Meena Raja *From:*openstack-bounces+raja.meena=wipro@lists.launchpad.net [mailto:openstack-bounces+raja.meena=wipro@lists.launchpad.net] *On Behalf Of *Shashank Sahni *Sent:* Monday, May 14, 2012 6:23 PM *To:* Razique Mahroua *Cc:* openstack@lists.launchpad.net *Subject:* Re: [Openstack] Problem with attaching disks to an instance Hi, I set this option in the configuration files of both compute and controller. Restarted the service, but unfortunately same result. Regards, Shashank Sahni On 05/14/2012 05:58 PM, Razique Mahroua wrote: Hi, do you have the flag iscsi_ip_prefix configured in your nova.conf ? Razique postbox-contact.jpg *Shashank Sahni* mailto:shredde...@linuxers.org 14 mai 2012 14:22 Hi everyone, I'm trying to configure a multi-node installation. Here is a brief overview. 1) controller - api+network+scheduler+novnc+glance+keystone (nova.conf - http://paste.openstack.org/show/17470/) 2) compute node (nova.conf - http://paste.openstack.org/show/17469) 3) volume node(single) Compute and vnc are working fine. I'm able to create and delete volumes. Iscsi discovery from the compute nodes is working too. But when I try to attach a volume, the compute node tries to connect to the controller node instead of volume and hence crashes with the following error. 2012-05-14 17:32:13 TRACE nova.rpc.amqp ProcessExecutionError: Unexpected error while running command. 2012-05-14 17:32:13 TRACE nova.rpc.amqp Command: sudo nova-rootwrap iscsiadm -m node -T iqn.2010-10.org.openstack:volume-0003 -p controller:3260 --rescan 2012-05-14 17:32:13 TRACE nova.rpc.amqp Exit code: 255 2012-05-14 17:32:13 TRACE nova.rpc.amqp Stdout: '' 2012-05-14 17:32:13 TRACE nova.rpc.amqp Stderr: 'iscsiadm: No portal found.\n' Any suggestions? Kind Regards, Shashank Sahni ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp -- Nuage Co - Razique Mahroua *razique.mahr...@gmail.com mailto:razique.mahr...@gmail.com* image.jpg *Please do not print this email unless it is absolutely necessary. * The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net
Re: [Openstack] Problem with attaching disks to an instance
Thank you Vish. That did the trick :) Regards, Shashank Sahni On 05/15/2012 02:43 AM, Vishvananda Ishaya wrote: you have to set iscsi_ip_address on the volume node. The volume node is the one that creates this db entry. Vish On May 14, 2012, at 1:54 PM, Shashank Sahni wrote: Hi Vish, Yeah you are right. I checked the settings in the volume database and for all volumes the entry is similar to following. controller_node:3260,3 iqn.2010-10.org.openstack:volume-0004 But it seems these entries are being generated automatically, i.e. as soon as I issue volume creation command. How do I fix this? I am already using properly configured iscsi_ip_address option in the controller's nova.conf file. Regards, Shashank Sahni On 05/15/2012 02:15 AM, Vishvananda Ishaya wrote: It should be getting the connection properties via the call to the volume node. Is it possible your volume in the database has incorrect properties stored in provider_location? It is set from the cofig iscsi_ip_address, so if you have not set that configuration option to a routable ip from compute - volume then it will not work. Also, changing the config option will not change the existing values in the db, so you might have to change those manually. Vish On May 14, 2012, at 7:28 AM, Shashank Sahni wrote: Hi, Thanks for the reply. Yes, I've gone through the document. Volume creation and deletion are working perfectly fine. When I run iscsiadm -m discovery -t st -p volume_node on the compute node, I can see the volumes. But somehow the compute node is being misinformed about the volume node after giving the attach command. I'm not using iscsitarget as per that document. Installation of nova-volume on ubuntu precise automatically took care of it using tgt. Kind Regards, Shashank Sahni On 05/14/2012 07:34 PM, raja.me...@wipro.com wrote: Hi Shashank , I preassume that the steps outlined in the link below has been followed. http://docs.openstack.org/trunk/openstack-compute/admin/content/managing-volumes.html Thanks Meena Raja *From:*openstack-bounces+raja.meena=wipro@lists.launchpad.net [mailto:openstack-bounces+raja.meena=wipro@lists.launchpad.net] *On Behalf Of *Shashank Sahni *Sent:* Monday, May 14, 2012 6:23 PM *To:* Razique Mahroua *Cc:* openstack@lists.launchpad.net *Subject:* Re: [Openstack] Problem with attaching disks to an instance Hi, I set this option in the configuration files of both compute and controller. Restarted the service, but unfortunately same result. Regards, Shashank Sahni On 05/14/2012 05:58 PM, Razique Mahroua wrote: Hi, do you have the flag iscsi_ip_prefix configured in your nova.conf ? Razique postbox-contact.jpg *Shashank Sahni* mailto:shredde...@linuxers.org 14 mai 2012 14:22 Hi everyone, I'm trying to configure a multi-node installation. Here is a brief overview. 1) controller - api+network+scheduler+novnc+glance+keystone (nova.conf - http://paste.openstack.org/show/17470/) 2) compute node (nova.conf - http://paste.openstack.org/show/17469) 3) volume node(single) Compute and vnc are working fine. I'm able to create and delete volumes. Iscsi discovery from the compute nodes is working too. But when I try to attach a volume, the compute node tries to connect to the controller node instead of volume and hence crashes with the following error. 2012-05-14 17:32:13 TRACE nova.rpc.amqp ProcessExecutionError: Unexpected error while running command. 2012-05-14 17:32:13 TRACE nova.rpc.amqp Command: sudo nova-rootwrap iscsiadm -m node -T iqn.2010-10.org.openstack:volume-0003 -p controller:3260 --rescan 2012-05-14 17:32:13 TRACE nova.rpc.amqp Exit code: 255 2012-05-14 17:32:13 TRACE nova.rpc.amqp Stdout: '' 2012-05-14 17:32:13 TRACE nova.rpc.amqp Stderr: 'iscsiadm: No portal found.\n' Any suggestions? Kind Regards, Shashank Sahni ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp -- Nuage Co - Razique Mahroua *razique.mahr...@gmail.com mailto:razique.mahr...@gmail.com* image.jpg *Please do not print this email unless it is absolutely necessary. * The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any
Re: [Openstack] nova-compute is unable to contact the metadata server
Hi, Here are the network configuration parameters in my nova.conf --network_manager = nova.network.manager.FlatManager --flat_network_bridge=br100 --flat_injected=true --flat_interface=eth0 --public_interface=eth0 Hence, I ran tcpdump with following three filters on the interfaces - eth0, lo br100. ip host 169.254.169.254 port 8773 port 80 but, nothing was returned for around a minute. Do I need to use different filters? Thank you. Regards, Shashank Sahni On Sun, Oct 2, 2011 at 11:31 PM, Jesse Andrews anotherje...@gmail.comwrote: If the request isn't coming into the nova-api then I recommend checking the network path using tcpdump (or wireshark - there is a curses version). As you can see it tries 100 times to hit the metadata server so you should see traffic every couple seconds On Sat, Oct 1, 2011 at 1:59 PM, Shashank Sahni shredde...@linuxers.org wrote: Hi everyone, I'm working on a single node installation of openstack(for testing). I'm using ubuntu uec images and am successfully able to boot them. But unfortunately, I get the error DataSourceEc2.py[WARNING]: 20:07:30 [17/100]: url error [[Errno 101] Network is unreachable] at the end of euca-get-console-output. I believe that is the reason why I'm not able to either ping or ssh into the instance. There already exists a pre-routing rule to redirect all the communication from 169.254.169.254:80 to nova-api:8773. -A nova-network-PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT --to-destination 10.2.4.135:8773 Any suggestions? Regards, Shashank Sahni ___ 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] nova-compute is unable to contact the metadata server
Hi everyone, I'm working on a single node installation of openstack(for testing). I'm using ubuntu uec images and am successfully able to boot them. But unfortunately, I get the error DataSourceEc2.py[WARNING]: 20:07:30 [17/100]: url error [[Errno 101] Network is unreachable] at the end of euca-get-console-output. I believe that is the reason why I'm not able to either ping or ssh into the instance. There already exists a pre-routing rule to redirect all the communication from 169.254.169.254:80 to nova-api:8773. -A nova-network-PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT --to-destination 10.2.4.135:8773 Any suggestions? Regards, Shashank Sahni ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
