[Openstack] nova user management without the dashboard

. However, keystone seems to not have a equivalent command like this: nova-manage project zipfile projectname username username-projectname-nova.zip --sharif -- Sharif Islam Senior Systems Analyst/Programmer FutureGrid (http://futuregrid.org) Pervasive Technology Institute, Indiana University

Re: [Openstack] nova user management without the dashboard

On 05/24/2012 04:27 PM, Dean Troyer wrote: On Thu, May 24, 2012 at 1:36 PM, Sharif Islam isla...@indiana.edu wrote: the dashboard and grabbing the file. However, keystone seems to not have a equivalent command like this: nova-manage project zipfile projectname username username-projectname

[Openstack] keystone error (python setup)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I am trying to setup keystone with LDAP and noticing these errors. I have python-ldap installed. What else do I need? # python Python 2.7.3 (default, Apr 20 2012, 22:39:59) [GCC 4.6.3] on linux2 Type help, copyright, credits or license for more

Re: [Openstack] keystone error (python setup)

: # python -c import ldap; help(ldap) Another caveat: LDAP requires binaries (on most systems?) that can't be installed by python-specific tools (e.g. pip) alone. -Dolph On Tue, May 22, 2012 at 7:43 AM, Sharif Islam isla...@indiana.edu mailto:isla...@indiana.edu wrote: Hi, I am trying

[Openstack] enforce admin_required with LDAP admin user

I think my LDAP bind is working by tenant-list and user-list gives me admin_required error. Looks like the LDAP admin user does not have any roles. is that the issue? # keystone discover Keystone found at http://localhost:5000/v2.0/ - supports version v2.0 (beta) here

[Openstack] keystone user-list (The action you have requested has not been implemented)

says The action you have requested has not been implemented but as keystone can talk to LDAP, there should be a way to retrieve the list. - --sharif - -- Sharif Islam Senior Systems Analyst/Programmer FutureGrid (http://www.futuregrid.org) Pervasive Technology Institute, Indiana University

[Openstack] Bad rsync return code after adding two new disks

-- Sharif Islam Senior Systems Analyst/Programmer FutureGrid (http://futuregrid.org) Pervasive Technology Institute, Indiana University Bloomington ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe

[Openstack] Large Files in swift and ConnectionTimeout

-server ERROR with Object server 172.29.202.14:6000/sda3 re: Expect: 100-continue on /AUTH_system/newcontainer_segments/file130G.tmp/1320261131.87/139527716864/0031: ConnectionTimeout (0.5s) - --sharif - -- Sharif Islam Senior Systems Analyst/Programmer FutureGrid (http://futuregrid.org

[Openstack] swift-bench Container PUT failed

/swift/common/client.py, line 437, in put_container http_reason=resp.reason) swift.common.client.ClientException: Container PUT failed: https://xxx.xx.xxx.xx:8080/v1/AUTH_system/4c695aa6de5246a7be4b19ecb089973e_0 404 Not Found - --sharif - -- Sharif Islam Senior Systems Analyst/Programmer

Re: [Openstack] swift-bench Container PUT failed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I found some more details in the system log: http://paste.openstack.org/show/2800/ not sure if this is helpful: python: abrt: detected unhandled Python exception in /usr/bin/swift-bench - --sharif On 10/20/2011 02:42 PM, Sharif Islam wrote: Do

[Openstack] Solved ( was Re: Object PUT failed)

, line 200, in setxattr#012return xattr(f).set(attr, value, options=options)#012 File From Object Server re: /v1/AUTH_system/builders/etc/swift/object.builder xxx.xx.xxx.xx:6000 (client_ip: xxx.xx.xxx.xx) - --sharif On 10/17/2011 04:24 PM, Sharif Islam wrote: I just finished setting up

[Openstack] Object PUT failed

://paste.openstack.org/show/2745/ And these are services running in that proxy node: http://paste.openstack.org/show/2746/ Any idea what could be wrong? - --sharif - -- Sharif Islam Senior Systems Analyst/Programmer FutureGrid (http://futuregrid.org) Pervasive Technology Institute, Indiana

Re: [Openstack] OpenStack Academic Alliance|Circle|Initiative #unconference

. - --sharif - -- Sharif Islam Senior Systems Analyst/Programmer FutureGrid (http://futuregrid.org) Pervasive Technology Institute, Indiana University Bloomington -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

Re: [Openstack] dns issue?

in this machine. Any other suggestions? - --sharif On 10/10/2011 05:23 PM, Sharif Islam wrote: On 10/10/2011 05:01 PM, Jason Kölker wrote: nameserver 10.0.1.1 How does nova assign the nameserver to the VMs? Can I change it someone so it has 8.8.4.4? I assume you are using Vlan

[Openstack] nova-network-INPUT (was Re: dns issue?)

if this is related. I am running RHEL 6.1. thanks. - --sharif - -- Sharif Islam Senior Systems Analyst/Programmer FutureGrid (http://futuregrid.org) Pervasive Technology Institute, Indiana University Bloomington -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using

Re: [Openstack] dns issue?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/10/2011 05:01 PM, Jason Kölker wrote: nameserver 10.0.1.1 How does nova assign the nameserver to the VMs? Can I change it someone so it has 8.8.4.4? I assume you are using Vlan or Flatdhcp? If so add --dns-server=8.8.4.4 to your flags

[Openstack] dns issue?

. Any idea? - --sharif - -- Sharif Islam Senior Systems Analyst/Programmer FutureGrid (http://futuregrid.org) Pervasive Technology Institute, Indiana University Bloomington -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http

Re: [Openstack] dns issue?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/07/2011 01:44 PM, Jorge Luiz Correa wrote: Check if you have a dnsmasq running on host that runs nova-network. It's necessary a DNS service on 10.0.1.1. On the nova-network host: $ ps aux | grep dns # ps aux|grep dnsmasq nobody

Re: [Openstack] dns issue?

Thanks Jorge. On 10/07/2011 02:30 PM, Jorge Luiz Correa wrote: It seems that configs are OK. Yes, that's what baffling me. I am pretty sure it was working before. I applied some redhat update and rebooted the cluster couple weeks ago. If you use dig from the controller, could resolv