[Openstack] Question about undo delete in Swift with Object Version
Hi stackers, I'm trying to understand the object version feature in Swift. In the current implementation we can store multi-versions of the same object in Swift. However when you delete it from the container, the latest version is deleted and this is not recoverable, right? Is there any magic to restore the deleted version? As I know, some users want to keep the history versions, like svn. --yuan ___ 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] Question about undo delete in Swift with Object Version
With the current implementation of versioning in Swift, this isn't possible. It's better to think of the feature as versioned writes. --John On Aug 22, 2012, at 12:13 AM, ZHOU Yuan dunk...@gmail.com wrote: Hi stackers, I'm trying to understand the object version feature in Swift. In the current implementation we can store multi-versions of the same object in Swift. However when you delete it from the container, the latest version is deleted and this is not recoverable, right? Is there any magic to restore the deleted version? As I know, some users want to keep the history versions, like svn. --yuan ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] implementing custom keystone module
On Tue, 21 Aug 2012 17:38:54 -0400, Adam Young wrote On 08/21/2012 05:10 PM, pat wrote: Hello, I want to implement custom keystone authentication module. I went through the What are you trying to do? There is a good chance that one of the other modules can be a good example. Well, probably multi-LDAP module, so probably start with current LDAP. documentation and I'm not sure where to start :-\ Please, could you point me to specific page describing this? Thanks. And one more: please, could you point me to document which describes relation between keystone and WSGI? And WSGI is a standard for writing Web applicaions in Python. Keystone complies with the WSGI contract. THus, while Keystone is usually run in the Eventlet web container, it can run in Apache HTTPD as well. Both are WSGI containers. Thanks for explanation. yes, I've never used python :-) Thanks for help. Pat P.S. I've googled a lot, but keystone is too common world :-( Google for Openstack Keystone and you will have more success. Thanks Pat Freehosting PIPNI - http://www.pipni.cz/ ___ 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] Question about undo delete in Swift with Object Version
Hi John, Thanks, versioned writes sounds really cool! Do you have any plan on this now? On Wed, Aug 22, 2012 at 3:25 PM, John Dickinson m...@not.mn wrote: With the current implementation of versioning in Swift, this isn't possible. It's better to think of the feature as versioned writes. --John On Aug 22, 2012, at 12:13 AM, ZHOU Yuan dunk...@gmail.com wrote: Hi stackers, I'm trying to understand the object version feature in Swift. In the current implementation we can store multi-versions of the same object in Swift. However when you delete it from the container, the latest version is deleted and this is not recoverable, right? Is there any magic to restore the deleted version? As I know, some users want to keep the history versions, like svn. --yuan ___ 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
Re: [Openstack] [Openstack-operators] ERROR: Malformed request url (HTTP 400)
Hi,
I am having the same problem as the subject. I am just wondering how do
people solve the problem. This is the error message that I got.
sysadmin@Cloud-director:/usr/lib/python2.7/dist-packages/novaclient/v1_1$
sudo nova --debug --os_username admin --os_password best97in
--os_tenant_name openstackDemo --os_auth_url
http://5.168.2.213:5000/v2.0/image-list
connect: (5.168.2.213, 5000)
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost: 5.168.2.213:5000\r\nContent-Length:
111\r\ncontent-type: application/json\r\naccept-encoding: gzip,
deflate\r\naccept: application/json\r\nuser-agent:
python-novaclient\r\n\r\n{auth: {tenantName: openstackDemo,
passwordCredentials: {username: admin, password: x}}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Type: application/json
header: Vary: X-Auth-Token
header: Date: Wed, 22 Aug 2012 08:14:38 GMT
header: Transfer-Encoding: chunked
connect: (5.168.2.213, 8774)
send: u'GET /v2/4c1afcfbaad747398d89c2fc7efa8e85/images/detail
HTTP/1.1\r\nHost: 5.168.2.213:8774\r\nx-auth-project-id:
openstackDemo\r\nx-auth-token:
2dfb3f6c74c7489883778843025ba849\r\naccept-encoding: gzip,
deflate\r\naccept: application/json\r\nuser-agent:
python-novaclient\r\n\r\n'
reply: 'HTTP/1.1 400 Bad Request\r\n'
header: Content-Length: 65
header: Content-Type: application/json; charset=UTF-8
header: X-Compute-Request-Id: req-55a95046-bd8e-4a9c-a30a-c1a24cac9b25
header: Date: Wed, 22 Aug 2012 08:14:38 GMT
DEBUG (shell:416) Malformed request url (HTTP 400)
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 413, in
main
OpenStackComputeShell().main(sys.argv[1:])
File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 364, in
main
args.func(self.cs, args)
File /usr/lib/python2.7/dist-packages/novaclient/v1_1/shell.py, line
350, in do_image_list
image_list = cs.images.list()
File /usr/lib/python2.7/dist-packages/novaclient/v1_1/images.py, line
47, in list
return self._list(/images/detail, images)
File /usr/lib/python2.7/dist-packages/novaclient/base.py, line 71, in
_list
resp, body = self.api.client.get(url)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 136,
in get
return self._cs_request(url, 'GET', **kwargs)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 124,
in _cs_request
**kwargs)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 107,
in request
raise exceptions.from_response(resp, body)
BadRequest: Malformed request url (HTTP 400)
ERROR: Malformed request url (HTTP 400)
The keystone service setting for volume service is as following:
{adminurl: http://5.168.2.213:8776/v1/%(tenant_id)s, internalurl:
http://5.168.2.213:8776/v1/%(tenant_id)s, publicurl:
http://5.168.2.213:8776/v1/%(tenant_id)s}
Any idea how to solve the problem?
Thanks in advance for the help!
Regards,
Wilson
___
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] uninstall
Guillermo Alvarado wrote: Which is the best way to uninstall all the components? I want to re-install it because I have an inconsistent environment. It is highly dependent on the way you installed them. Could you give us some details on that ? -- Thierry Carrez (ttx) Release Manager, OpenStack ___ 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] Closr.it
Hello guys,
I'm having a problem with nova command line. I've added this to .bashrc:
export OS_TENANT_NAME=admin
export OS_USERNAME=admin
export OS_PASSWORD=admin
export OS_AUTH_URL=http://127.0.0.1:5000/v2.0/;
but when i do nova --debug list i get:
connect: (127.0.0.1, 5000)
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost: 127.0.0.1:5000\r\nContent-Length:
115\r\ncontent-type: application/json\r\naccept-encoding: gzip,
deflate\r\naccept: application/json\r\nuser-agent:
python-novaclient\r\n\r\n{auth: {tenantName: admin,
passwordCredentials: {username: admin, password: admin}}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Type: application/json
header: Vary: X-Auth-Token
header: Date: Wed, 22 Aug 2012 09:39:20 GMT
header: Transfer-Encoding: chunked
DEBUG (shell:416) n/a (HTTP 400)
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 413, in main
OpenStackComputeShell().main(sys.argv[1:])
File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 364, in main
args.func(self.cs, args)
File /usr/lib/python2.7/dist-packages/novaclient/v1_1/shell.py, line 520,
in do_list
utils.print_list(cs.servers.list(search_opts=search_opts), columns,
File /usr/lib/python2.7/dist-packages/novaclient/v1_1/servers.py, line 279,
in list
return self._list(/servers%s%s % (detail, query_string), servers)
File /usr/lib/python2.7/dist-packages/novaclient/base.py, line 71, in _list
resp, body = self.api.client.get(url)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 136, in get
return self._cs_request(url, 'GET', **kwargs)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 124, in
_cs_request
**kwargs)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 107, in
request
raise exceptions.from_response(resp, body)
BadRequest: n/a (HTTP 400)
ERROR: n/a (HTTP 400)
I've dumped the traffic with tcpdump and i see a correct response from
keystone, this is the output:
http://pastie.org/private/ms7c5jlpatolsgiosjsva
How can i solve this?
Best Regards
--
Alessandro Tagliapietra | VISup srl
piazza 4 novembre 7
20124 Milano
http://www.visup.it
___
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] uninstall
Il giorno 21/ago/2012, alle ore 23:15, Guillermo Alvarado stallion.a...@gmail.com ha scritto: Hello everyone, Which is the best way to uninstall all the components? I want to re-install it because I have an inconsistent environment. if you're on debian/ubuntu apt-get purge nova.* keystone.* glance.* swift.* Best Thanks in advance!! ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Alessandro Tagliapietra | VISup srl piazza 4 novembre 7 20124 Milano http://www.visup.it ___ 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] Closr.it
Sorry for the wrong subject, it was another mail that i was sending.
--
Alessandro Tagliapietra | VISup srl
piazza 4 novembre 7
20124 Milano
http://www.visup.it
Il giorno 22/ago/2012, alle ore 11:40, Alessandro Tagliapietra
tagliapietra.alessan...@gmail.com ha scritto:
Hello guys,
I'm having a problem with nova command line. I've added this to .bashrc:
export OS_TENANT_NAME=admin
export OS_USERNAME=admin
export OS_PASSWORD=admin
export OS_AUTH_URL=http://127.0.0.1:5000/v2.0/;
but when i do nova --debug list i get:
connect: (127.0.0.1, 5000)
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost: 127.0.0.1:5000\r\nContent-Length:
115\r\ncontent-type: application/json\r\naccept-encoding: gzip,
deflate\r\naccept: application/json\r\nuser-agent:
python-novaclient\r\n\r\n{auth: {tenantName: admin,
passwordCredentials: {username: admin, password: admin}}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Type: application/json
header: Vary: X-Auth-Token
header: Date: Wed, 22 Aug 2012 09:39:20 GMT
header: Transfer-Encoding: chunked
DEBUG (shell:416) n/a (HTTP 400)
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 413, in
main
OpenStackComputeShell().main(sys.argv[1:])
File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 364, in
main
args.func(self.cs, args)
File /usr/lib/python2.7/dist-packages/novaclient/v1_1/shell.py, line 520,
in do_list
utils.print_list(cs.servers.list(search_opts=search_opts), columns,
File /usr/lib/python2.7/dist-packages/novaclient/v1_1/servers.py, line
279, in list
return self._list(/servers%s%s % (detail, query_string), servers)
File /usr/lib/python2.7/dist-packages/novaclient/base.py, line 71, in
_list
resp, body = self.api.client.get(url)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 136, in
get
return self._cs_request(url, 'GET', **kwargs)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 124, in
_cs_request
**kwargs)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 107, in
request
raise exceptions.from_response(resp, body)
BadRequest: n/a (HTTP 400)
ERROR: n/a (HTTP 400)
I've dumped the traffic with tcpdump and i see a correct response from
keystone, this is the output:
http://pastie.org/private/ms7c5jlpatolsgiosjsva
How can i solve this?
Best Regards
--
Alessandro Tagliapietra | VISup srl
piazza 4 novembre 7
20124 Milano
http://www.visup.it
___
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] Closr.it
Hi Alessandro,
When I get 400 errors from nova command line it is usually because of
invalid values in the cache.
Try executing your commands with the --no_cache option or destroying the
cache altogether by removing the .novaclient directory in your home dir.
Salvatore
On 22 August 2012 11:45, Alessandro Tagliapietra
tagliapietra.alessan...@gmail.com wrote:
Sorry for the wrong subject, it was another mail that i was sending.
--
Alessandro Tagliapietra | VISup srl
piazza 4 novembre 7
20124 Milano
http://www.visup.it
Il giorno 22/ago/2012, alle ore 11:40, Alessandro Tagliapietra
tagliapietra.alessan...@gmail.com ha scritto:
Hello guys,
I'm having a problem with nova command line. I've added this to .bashrc:
export OS_TENANT_NAME=admin
export OS_USERNAME=admin
export OS_PASSWORD=admin
export OS_AUTH_URL=http://127.0.0.1:5000/v2.0/;
but when i do nova --debug list i get:
connect: (127.0.0.1, 5000)
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost: 127.0.0.1:5000\r\nContent-Length:
115\r\ncontent-type: application/json\r\naccept-encoding: gzip,
deflate\r\naccept: application/json\r\nuser-agent:
python-novaclient\r\n\r\n{auth: {tenantName: admin,
passwordCredentials: {username: admin, password: admin}}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Type: application/json
header: Vary: X-Auth-Token
header: Date: Wed, 22 Aug 2012 09:39:20 GMT
header: Transfer-Encoding: chunked
DEBUG (shell:416) n/a (HTTP 400)
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 413,
in main
OpenStackComputeShell().main(sys.argv[1:])
File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 364,
in main
args.func(self.cs, args)
File /usr/lib/python2.7/dist-packages/novaclient/v1_1/shell.py, line
520, in do_list
utils.print_list(cs.servers.list(search_opts=search_opts), columns,
File /usr/lib/python2.7/dist-packages/novaclient/v1_1/servers.py, line
279, in list
return self._list(/servers%s%s % (detail, query_string), servers)
File /usr/lib/python2.7/dist-packages/novaclient/base.py, line 71, in
_list
resp, body = self.api.client.get(url)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 136,
in get
return self._cs_request(url, 'GET', **kwargs)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 124,
in _cs_request
**kwargs)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 107,
in request
raise exceptions.from_response(resp, body)
BadRequest: n/a (HTTP 400)
ERROR: n/a (HTTP 400)
I've dumped the traffic with tcpdump and i see a correct response from
keystone, this is the output:
http://pastie.org/private/ms7c5jlpatolsgiosjsva
How can i solve this?
Best Regards
--
Alessandro Tagliapietra | VISup srl
piazza 4 novembre 7
20124 Milano
http://www.visup.it
___
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
Re: [Openstack] Closr.it
Hi Salvatore,
sorry but in nova i don't see any --no_cache option nor a .novaclient folder in
user home. :/
--
Alessandro Tagliapietra | VISup srl
piazza 4 novembre 7
20124 Milano
http://www.visup.it
Il giorno 22/ago/2012, alle ore 11:52, Salvatore Orlando sorla...@nicira.com
ha scritto:
Hi Alessandro,
When I get 400 errors from nova command line it is usually because of invalid
values in the cache.
Try executing your commands with the --no_cache option or destroying the
cache altogether by removing the .novaclient directory in your home dir.
Salvatore
On 22 August 2012 11:45, Alessandro Tagliapietra
tagliapietra.alessan...@gmail.com wrote:
Sorry for the wrong subject, it was another mail that i was sending.
--
Alessandro Tagliapietra | VISup srl
piazza 4 novembre 7
20124 Milano
http://www.visup.it
Il giorno 22/ago/2012, alle ore 11:40, Alessandro Tagliapietra
tagliapietra.alessan...@gmail.com ha scritto:
Hello guys,
I'm having a problem with nova command line. I've added this to .bashrc:
export OS_TENANT_NAME=admin
export OS_USERNAME=admin
export OS_PASSWORD=admin
export OS_AUTH_URL=http://127.0.0.1:5000/v2.0/;
but when i do nova --debug list i get:
connect: (127.0.0.1, 5000)
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost: 127.0.0.1:5000\r\nContent-Length:
115\r\ncontent-type: application/json\r\naccept-encoding: gzip,
deflate\r\naccept: application/json\r\nuser-agent:
python-novaclient\r\n\r\n{auth: {tenantName: admin,
passwordCredentials: {username: admin, password: admin}}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Type: application/json
header: Vary: X-Auth-Token
header: Date: Wed, 22 Aug 2012 09:39:20 GMT
header: Transfer-Encoding: chunked
DEBUG (shell:416) n/a (HTTP 400)
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 413, in
main
OpenStackComputeShell().main(sys.argv[1:])
File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 364, in
main
args.func(self.cs, args)
File /usr/lib/python2.7/dist-packages/novaclient/v1_1/shell.py, line
520, in do_list
utils.print_list(cs.servers.list(search_opts=search_opts), columns,
File /usr/lib/python2.7/dist-packages/novaclient/v1_1/servers.py, line
279, in list
return self._list(/servers%s%s % (detail, query_string), servers)
File /usr/lib/python2.7/dist-packages/novaclient/base.py, line 71, in
_list
resp, body = self.api.client.get(url)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 136, in
get
return self._cs_request(url, 'GET', **kwargs)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 124, in
_cs_request
**kwargs)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 107, in
request
raise exceptions.from_response(resp, body)
BadRequest: n/a (HTTP 400)
ERROR: n/a (HTTP 400)
I've dumped the traffic with tcpdump and i see a correct response from
keystone, this is the output:
http://pastie.org/private/ms7c5jlpatolsgiosjsva
How can i solve this?
Best Regards
--
Alessandro Tagliapietra | VISup srl
piazza 4 novembre 7
20124 Milano
http://www.visup.it
___
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
Re: [Openstack] Closr.it
Found the problem,
in the endpoint list i had an url with http:/10.x.. so it was missing a /
I'm writing just to keep track of this possible error.
Best
--
Alessandro Tagliapietra | VISup srl
piazza 4 novembre 7
20124 Milano
http://www.visup.it
Il giorno 22/ago/2012, alle ore 11:55, Alessandro Tagliapietra
tagliapietra.alessan...@gmail.com ha scritto:
Hi Salvatore,
sorry but in nova i don't see any --no_cache option nor a .novaclient folder
in user home. :/
--
Alessandro Tagliapietra | VISup srl
piazza 4 novembre 7
20124 Milano
http://www.visup.it
Il giorno 22/ago/2012, alle ore 11:52, Salvatore Orlando
sorla...@nicira.com ha scritto:
Hi Alessandro,
When I get 400 errors from nova command line it is usually because of
invalid values in the cache.
Try executing your commands with the --no_cache option or destroying the
cache altogether by removing the .novaclient directory in your home dir.
Salvatore
On 22 August 2012 11:45, Alessandro Tagliapietra
tagliapietra.alessan...@gmail.com wrote:
Sorry for the wrong subject, it was another mail that i was sending.
--
Alessandro Tagliapietra | VISup srl
piazza 4 novembre 7
20124 Milano
http://www.visup.it
Il giorno 22/ago/2012, alle ore 11:40, Alessandro Tagliapietra
tagliapietra.alessan...@gmail.com ha scritto:
Hello guys,
I'm having a problem with nova command line. I've added this to .bashrc:
export OS_TENANT_NAME=admin
export OS_USERNAME=admin
export OS_PASSWORD=admin
export OS_AUTH_URL=http://127.0.0.1:5000/v2.0/;
but when i do nova --debug list i get:
connect: (127.0.0.1, 5000)
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost:
127.0.0.1:5000\r\nContent-Length: 115\r\ncontent-type:
application/json\r\naccept-encoding: gzip, deflate\r\naccept:
application/json\r\nuser-agent: python-novaclient\r\n\r\n{auth:
{tenantName: admin, passwordCredentials: {username: admin,
password: admin}}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Type: application/json
header: Vary: X-Auth-Token
header: Date: Wed, 22 Aug 2012 09:39:20 GMT
header: Transfer-Encoding: chunked
DEBUG (shell:416) n/a (HTTP 400)
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 413, in
main
OpenStackComputeShell().main(sys.argv[1:])
File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 364, in
main
args.func(self.cs, args)
File /usr/lib/python2.7/dist-packages/novaclient/v1_1/shell.py, line
520, in do_list
utils.print_list(cs.servers.list(search_opts=search_opts), columns,
File /usr/lib/python2.7/dist-packages/novaclient/v1_1/servers.py, line
279, in list
return self._list(/servers%s%s % (detail, query_string), servers)
File /usr/lib/python2.7/dist-packages/novaclient/base.py, line 71, in
_list
resp, body = self.api.client.get(url)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 136,
in get
return self._cs_request(url, 'GET', **kwargs)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 124,
in _cs_request
**kwargs)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 107,
in request
raise exceptions.from_response(resp, body)
BadRequest: n/a (HTTP 400)
ERROR: n/a (HTTP 400)
I've dumped the traffic with tcpdump and i see a correct response from
keystone, this is the output:
http://pastie.org/private/ms7c5jlpatolsgiosjsva
How can i solve this?
Best Regards
--
Alessandro Tagliapietra | VISup srl
piazza 4 novembre 7
20124 Milano
http://www.visup.it
___
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] Openstack Folsom - 3 Installation
Hi All- I'm installing Openstack Components of Folsom-3 milestone from the Tar files available from launchpad. Can any one guide me on the installation of the these components like the Essex component installation and configuration. I'm upto this level of Installation. For instance, Keystone component, I have untar the file and executed the following commands. *Keystone $* python setup.py build *Keystone $* python setup.py install. Will these two steps install the respective component and all its necessary components. With this type of Install can I use the Openstack components as I use them in the 'apt-get' based Essex installation. Kindly guide me on this... Thanking you all. -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ 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] Unable to start nova-scheduler : duplicate option: scheduler_host_manager
Hi, No idea for my scheduler problem ? It was working at the beginning (I suppose because I could launch instances), but I did a lot of modification, modifying networks, deleting nova db, rebuild it, etc. Any idea on what I can do to identify the problem ? Where can I find the mentionned option except in nova.conf ? Ben Le 22/08/2012 00:46, Ben a écrit : Hi, I'm trying to setup a little nova cluster with 3 nodes : - 1 controller node running all services but compute - 2 compute nodes running compute and network only I have faced a lot of issues, but I can't understand this one. When I start nova-scheduler on controller node, the process dies instantly with this error : CRITICAL nova [-] duplicate option: scheduler_host_manager So I can't start an instance, it remains stuck in building state. I have checked my nova.conf file, and I only see this line : --scheduler_driver=nova.scheduler.simple.SimpleScheduler What does means this error, how can I solve it ? Thanks, Ben ___ 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] ldaps support in keystone?
Hi, all Could I ask if ldaps is supported in keystone? I do know that ldap is supported in keystone, but I couldn't find any information about ladps support in keystone via google nor openstack doc. Could anyone give some explicit information about that? Thanks. Best Regards. Yanping ___ 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] Unable to start nova-scheduler : duplicate option: scheduler_host_manager
Ben, As the error message suggests, it is due to a duplicated option of scheduler_host_manager. It is specified more than once somewhere. Thanks, Joseph - Original Message - From: Ben ben@gmail.com To: openstack@lists.launchpad.net Sent: Wednesday, August 22, 2012 8:27:39 AM Subject: Re: [Openstack] Unable to start nova-scheduler : duplicate option: scheduler_host_manager Hi, No idea for my scheduler problem ? It was working at the beginning (I suppose because I could launch instances), but I did a lot of modification, modifying networks, deleting nova db, rebuild it, etc. Any idea on what I can do to identify the problem ? Where can I find the mentionned option except in nova.conf ? Ben Le 22/08/2012 00:46, Ben a écrit : Hi, I'm trying to setup a little nova cluster with 3 nodes : - 1 controller node running all services but compute - 2 compute nodes running compute and network only I have faced a lot of issues, but I can't understand this one. When I start nova-scheduler on controller node, the process dies instantly with this error : CRITICAL nova [-] duplicate option: scheduler_host_manager So I can't start an instance, it remains stuck in building state. I have checked my nova.conf file, and I only see this line : --scheduler_driver=nova.scheduler.simple.SimpleScheduler What does means this error, how can I solve it ? Thanks, Ben ___ 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
Re: [Openstack] Unable to start nova-scheduler : duplicate option: scheduler_host_manager
Hi Joseph, Thank you for your answer. Yes, but where could be that option ? It's not duplicated in my nova.conf file, and this is the file the nova-scheduler uses. My nova.conf file joined. Regards, Ben Le 22/08/2012 16:37, Joseph Suh a écrit : Ben, As the error message suggests, it is due to a duplicated option of scheduler_host_manager. It is specified more than once somewhere. Thanks, Joseph - Original Message - From: Ben ben@gmail.com To: openstack@lists.launchpad.net Sent: Wednesday, August 22, 2012 8:27:39 AM Subject: Re: [Openstack] Unable to start nova-scheduler : duplicate option: scheduler_host_manager Hi, No idea for my scheduler problem ? It was working at the beginning (I suppose because I could launch instances), but I did a lot of modification, modifying networks, deleting nova db, rebuild it, etc. Any idea on what I can do to identify the problem ? Where can I find the mentionned option except in nova.conf ? Ben Le 22/08/2012 00:46, Ben a écrit : Hi, I'm trying to setup a little nova cluster with 3 nodes : - 1 controller node running all services but compute - 2 compute nodes running compute and network only I have faced a lot of issues, but I can't understand this one. When I start nova-scheduler on controller node, the process dies instantly with this error : CRITICAL nova [-] duplicate option: scheduler_host_manager So I can't start an instance, it remains stuck in building state. I have checked my nova.conf file, and I only see this line : --scheduler_driver=nova.scheduler.simple.SimpleScheduler What does means this error, how can I solve it ? Thanks, Ben ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp --dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --allow_admin_api=true --use_deprecated_auth=false --auth_strategy=keystone --scheduler_driver=nova.scheduler.simple.SimpleScheduler --s3_host=94.103.xx.xx --ec2_host=94.103.xx.xx --rabbit_host=94.103.xx.xx --cc_host=94.103.xx.xx --nova_url=http://94.103.xx.xx:8774/v1.1/ --routing_source_ip=94.103.xx.xx --glance_api_servers=94.103.xx.xx:9292 --image_service=nova.image.glance.GlanceImageService --iscsi_ip_prefix=192.168.28 --sql_connection=mysql://novadbadmin:hiddenp...@94.103.xx.xx/nova --ec2_url=http://94.103.xx.xx:8773/services/Cloud --keystone_ec2_url=http://94.103.xx.xx:5000/v2.0/ec2tokens --api_paste_config=/etc/nova/api-paste.ini --libvirt_type=kvm --libvirt_use_virtio_for_bridges=true --start_guests_on_host_boot=true --resume_guests_state_on_host_boot=true --vnc_enabled=true --vncproxy_url=http://94.103.xx.xx:6080 --vnc_console_proxy_url=http://94.103.xx.xx:6080 # network specific settings --network_manager=nova.network.manager.FlatDHCPManager --public_interface=eth0 --flat_interface=eth1 --flat_network_bridge=br100 --fixed_range=192.168.28.0/25 --floating_range=94.103.136.55/29 --network_size=128 --flat_network_dhcp_start=192.168.28.2 --flat_injected=False --force_dhcp_release --iscsi_helper=tgtadm --connection_type=libvirt --root_helper=sudo nova-rootwrap --verbose --libvirt_use_virtio_for_bridges --ec2_private_dns_show --novnc_enable=true --novncproxy_base_url=http://94.103.xx.xx:6080/vnc_auto.html --vncserver_proxyclient_address=127.0.0.1 --vncserver_listen=0.0.0.0 ___ 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] Unable to start nova-scheduler : duplicate option: scheduler_host_manager
Ben, It is possible to have the option specified in a code. Try grep -r on whole code. Thanks, Joseph - Original Message - From: Ben ben@gmail.com To: Joseph Suh j...@isi.edu Cc: openstack@lists.launchpad.net Sent: Wednesday, August 22, 2012 10:47:35 AM Subject: Re: [Openstack] Unable to start nova-scheduler : duplicate option: scheduler_host_manager Hi Joseph, Thank you for your answer. Yes, but where could be that option ? It's not duplicated in my nova.conf file, and this is the file the nova-scheduler uses. My nova.conf file joined. Regards, Ben Le 22/08/2012 16:37, Joseph Suh a écrit : Ben, As the error message suggests, it is due to a duplicated option of scheduler_host_manager. It is specified more than once somewhere. Thanks, Joseph - Original Message - From: Ben ben@gmail.com To: openstack@lists.launchpad.net Sent: Wednesday, August 22, 2012 8:27:39 AM Subject: Re: [Openstack] Unable to start nova-scheduler : duplicate option: scheduler_host_manager Hi, No idea for my scheduler problem ? It was working at the beginning (I suppose because I could launch instances), but I did a lot of modification, modifying networks, deleting nova db, rebuild it, etc. Any idea on what I can do to identify the problem ? Where can I find the mentionned option except in nova.conf ? Ben Le 22/08/2012 00:46, Ben a écrit : Hi, I'm trying to setup a little nova cluster with 3 nodes : - 1 controller node running all services but compute - 2 compute nodes running compute and network only I have faced a lot of issues, but I can't understand this one. When I start nova-scheduler on controller node, the process dies instantly with this error : CRITICAL nova [-] duplicate option: scheduler_host_manager So I can't start an instance, it remains stuck in building state. I have checked my nova.conf file, and I only see this line : --scheduler_driver=nova.scheduler.simple.SimpleScheduler What does means this error, how can I solve it ? Thanks, Ben ___ 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
Re: [Openstack] ldaps support in keystone?
On 08/22/2012 09:38 AM, Yanping Xie wrote: Hi, all Could I ask if ldaps is supported in keystone? I do know that ldap is supported in keystone, but I couldn't find any information about ladps support in keystone via google nor openstack doc. Could anyone give some explicit information about that? Thanks. Best Regards. Yanping ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp LDAPS is not currently supported. Since this is This is the second time I've been asked this today, I am filing a ticket for it: https://bugs.launchpad.net/keystone/+bug/1040115 ___ 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] Unable to start nova-scheduler : duplicate option: scheduler_host_manager
# grep -R scheduler_host_manager /usr/lib/python2.7/dist-packages/nova
/usr/lib/python2.7/dist-packages/nova/scheduler/driver.py:
cfg.StrOpt('scheduler_host_manager',
/usr/lib/python2.7/dist-packages/nova/scheduler/driver.py:
FLAGS.scheduler_host_manager)
Fichier binaire
/usr/lib/python2.7/dist-packages/nova/scheduler/driver.pyc concordant
grep: /usr/lib/python2.7/dist-packages/nova/CA/reqs/.gitignore: Aucun
fichier ou dossier de ce type
grep: /usr/lib/python2.7/dist-packages/nova/CA/.gitignore: Aucun fichier
ou dossier de ce type
grep: /usr/lib/python2.7/dist-packages/nova/CA/projects/.gitignore:
Aucun fichier ou dossier de ce type
If I comment the portion of code that raise the error (in
_is_opt_registered(opts, opt) of cfg.py), I get the following error :
ClassNotFound: Class SimpleScheduler could not be found: cannot import
name vnc
I have the same error if I replace --scheduler_driver by
--scheduler_manager in nova.conf.
novnc is not installed because it give a configure error, but
nova-vncproxy is well installed.
I suspect the error raised is not the original error, only side effect...
I joined the trace of nova-scheduler before and after the code comment.
What can I try now ?
Ben
Le 22/08/2012 17:00, Joseph Suh a écrit :
Ben,
It is possible to have the option specified in a code. Try grep -r on whole
code.
Thanks,
Joseph
- Original Message -
From: Ben ben@gmail.com
To: Joseph Suh j...@isi.edu
Cc: openstack@lists.launchpad.net
Sent: Wednesday, August 22, 2012 10:47:35 AM
Subject: Re: [Openstack] Unable to start nova-scheduler : duplicate option:
scheduler_host_manager
Hi Joseph,
Thank you for your answer. Yes, but where could be that option ? It's
not duplicated in my nova.conf file, and this is the file the
nova-scheduler uses.
My nova.conf file joined.
Regards,
Ben
Le 22/08/2012 16:37, Joseph Suh a écrit :
Ben,
As the error message suggests, it is due to a duplicated option of
scheduler_host_manager. It is specified more than once somewhere.
Thanks,
Joseph
- Original Message -
From: Ben ben@gmail.com
To: openstack@lists.launchpad.net
Sent: Wednesday, August 22, 2012 8:27:39 AM
Subject: Re: [Openstack] Unable to start nova-scheduler : duplicate option:
scheduler_host_manager
Hi,
No idea for my scheduler problem ? It was working at the beginning (I
suppose because I could launch instances), but I did a lot of
modification, modifying networks, deleting nova db, rebuild it, etc.
Any idea on what I can do to identify the problem ? Where can I find the
mentionned option except in nova.conf ?
Ben
Le 22/08/2012 00:46, Ben a écrit :
Hi,
I'm trying to setup a little nova cluster with 3 nodes :
- 1 controller node running all services but compute
- 2 compute nodes running compute and network only
I have faced a lot of issues, but I can't understand this one. When I
start nova-scheduler on controller node, the process dies instantly with
this error :
CRITICAL nova [-] duplicate option: scheduler_host_manager
So I can't start an instance, it remains stuck in building state. I have
checked my nova.conf file, and I only see this line :
--scheduler_driver=nova.scheduler.simple.SimpleScheduler
What does means this error, how can I solve it ?
Thanks,
Ben
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--allow_admin_api=true
--use_deprecated_auth=false
--auth_strategy=keystone
--scheduler_driver=nova.scheduler.simple.SimpleScheduler
--s3_host=94.103.xx.xx
--ec2_host=94.103.xx.xx
--rabbit_host=94.103.xx.xx
--cc_host=94.103.xx.xx
--nova_url=http://94.103.xx.xx:8774/v1.1/
--routing_source_ip=94.103.xx.xx
--glance_api_servers=94.103.xx.xx:9292
--image_service=nova.image.glance.GlanceImageService
--iscsi_ip_prefix=192.168.28
--sql_connection=mysql://novadbadmin:hiddenp...@94.103.xx.xx/nova
--ec2_url=http://94.103.xx.xx:8773/services/Cloud
--keystone_ec2_url=http://94.103.xx.xx:5000/v2.0/ec2tokens
--api_paste_config=/etc/nova/api-paste.ini
--libvirt_type=kvm
--libvirt_use_virtio_for_bridges=true
--start_guests_on_host_boot=true
--resume_guests_state_on_host_boot=true
--vnc_enabled=true
--vncproxy_url=http://94.103.xx.xx:6080
--vnc_console_proxy_url=http://94.103.xx.xx:6080
# network specific settings
--network_manager=nova.network.manager.FlatDHCPManager
--public_interface=eth0
--flat_interface=eth1
--flat_network_bridge=br100
--fixed_range=192.168.28.0/25
--floating_range=94.103.136.55/29
--network_size=128
--flat_network_dhcp_start=192.168.28.2
--flat_injected=False
--force_dhcp_release
--iscsi_helper=tgtadm
--connection_type=libvirt
--root_helper=sudo nova-rootwrap
--verbose
Re: [Openstack] Unable to start nova-scheduler : duplicate option: scheduler_host_manager
You have a circular import somewhere That is causing scheduler/driver.py to be
imported twice.
Vish
On Aug 22, 2012, at 8:33 AM, Ben ben@gmail.com wrote:
# grep -R scheduler_host_manager /usr/lib/python2.7/dist-packages/nova
/usr/lib/python2.7/dist-packages/nova/scheduler/driver.py:
cfg.StrOpt('scheduler_host_manager',
/usr/lib/python2.7/dist-packages/nova/scheduler/driver.py:
FLAGS.scheduler_host_manager)
Fichier binaire /usr/lib/python2.7/dist-packages/nova/scheduler/driver.pyc
concordant
grep: /usr/lib/python2.7/dist-packages/nova/CA/reqs/.gitignore: Aucun fichier
ou dossier de ce type
grep: /usr/lib/python2.7/dist-packages/nova/CA/.gitignore: Aucun fichier ou
dossier de ce type
grep: /usr/lib/python2.7/dist-packages/nova/CA/projects/.gitignore: Aucun
fichier ou dossier de ce type
If I comment the portion of code that raise the error (in
_is_opt_registered(opts, opt) of cfg.py), I get the following error :
ClassNotFound: Class SimpleScheduler could not be found: cannot import name
vnc
I have the same error if I replace --scheduler_driver by --scheduler_manager
in nova.conf.
novnc is not installed because it give a configure error, but nova-vncproxy
is well installed.
I suspect the error raised is not the original error, only side effect...
I joined the trace of nova-scheduler before and after the code comment.
What can I try now ?
Ben
Le 22/08/2012 17:00, Joseph Suh a écrit :
Ben,
It is possible to have the option specified in a code. Try grep -r on whole
code.
Thanks,
Joseph
- Original Message -
From: Ben ben@gmail.com
To: Joseph Suh j...@isi.edu
Cc: openstack@lists.launchpad.net
Sent: Wednesday, August 22, 2012 10:47:35 AM
Subject: Re: [Openstack] Unable to start nova-scheduler : duplicate option:
scheduler_host_manager
Hi Joseph,
Thank you for your answer. Yes, but where could be that option ? It's
not duplicated in my nova.conf file, and this is the file the
nova-scheduler uses.
My nova.conf file joined.
Regards,
Ben
Le 22/08/2012 16:37, Joseph Suh a écrit :
Ben,
As the error message suggests, it is due to a duplicated option of
scheduler_host_manager. It is specified more than once somewhere.
Thanks,
Joseph
- Original Message -
From: Ben ben@gmail.com
To: openstack@lists.launchpad.net
Sent: Wednesday, August 22, 2012 8:27:39 AM
Subject: Re: [Openstack] Unable to start nova-scheduler : duplicate option:
scheduler_host_manager
Hi,
No idea for my scheduler problem ? It was working at the beginning (I
suppose because I could launch instances), but I did a lot of
modification, modifying networks, deleting nova db, rebuild it, etc.
Any idea on what I can do to identify the problem ? Where can I find the
mentionned option except in nova.conf ?
Ben
Le 22/08/2012 00:46, Ben a écrit :
Hi,
I'm trying to setup a little nova cluster with 3 nodes :
- 1 controller node running all services but compute
- 2 compute nodes running compute and network only
I have faced a lot of issues, but I can't understand this one. When I
start nova-scheduler on controller node, the process dies instantly with
this error :
CRITICAL nova [-] duplicate option: scheduler_host_manager
So I can't start an instance, it remains stuck in building state. I have
checked my nova.conf file, and I only see this line :
--scheduler_driver=nova.scheduler.simple.SimpleScheduler
What does means this error, how can I solve it ?
Thanks,
Ben
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
nova.conftrace.log___
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
Re: [Openstack] Unable to start nova-scheduler : duplicate option: scheduler_host_manager
Hum, ok but why ? I'm running essex out of the box packaged in Ubuntu
12.04. I didn't modify the code (except comment the raise line in cfg.py
for this problem), but I did a lot of reinstall, modify configuration,
drop nova db, etc.
What would cause this circular import ? Can I tweak the code to avoid
this circular import (as workaround to validate this hypothesis) ?
Thanks to all for your help.
Ben
Le 22/08/2012 18:00, Vishvananda Ishaya a écrit :
You have a circular import somewhere That is causing scheduler/driver.py to be
imported twice.
Vish
On Aug 22, 2012, at 8:33 AM, Ben ben@gmail.com wrote:
# grep -R scheduler_host_manager /usr/lib/python2.7/dist-packages/nova
/usr/lib/python2.7/dist-packages/nova/scheduler/driver.py:
cfg.StrOpt('scheduler_host_manager',
/usr/lib/python2.7/dist-packages/nova/scheduler/driver.py:
FLAGS.scheduler_host_manager)
Fichier binaire /usr/lib/python2.7/dist-packages/nova/scheduler/driver.pyc
concordant
grep: /usr/lib/python2.7/dist-packages/nova/CA/reqs/.gitignore: Aucun fichier
ou dossier de ce type
grep: /usr/lib/python2.7/dist-packages/nova/CA/.gitignore: Aucun fichier ou
dossier de ce type
grep: /usr/lib/python2.7/dist-packages/nova/CA/projects/.gitignore: Aucun
fichier ou dossier de ce type
If I comment the portion of code that raise the error (in
_is_opt_registered(opts, opt) of cfg.py), I get the following error :
ClassNotFound: Class SimpleScheduler could not be found: cannot import name vnc
I have the same error if I replace --scheduler_driver by --scheduler_manager in
nova.conf.
novnc is not installed because it give a configure error, but nova-vncproxy is
well installed.
I suspect the error raised is not the original error, only side effect...
I joined the trace of nova-scheduler before and after the code comment.
What can I try now ?
Ben
Le 22/08/2012 17:00, Joseph Suh a écrit :
Ben,
It is possible to have the option specified in a code. Try grep -r on whole
code.
Thanks,
Joseph
- Original Message -
From: Ben ben@gmail.com
To: Joseph Suh j...@isi.edu
Cc: openstack@lists.launchpad.net
Sent: Wednesday, August 22, 2012 10:47:35 AM
Subject: Re: [Openstack] Unable to start nova-scheduler : duplicate option:
scheduler_host_manager
Hi Joseph,
Thank you for your answer. Yes, but where could be that option ? It's
not duplicated in my nova.conf file, and this is the file the
nova-scheduler uses.
My nova.conf file joined.
Regards,
Ben
Le 22/08/2012 16:37, Joseph Suh a écrit :
Ben,
As the error message suggests, it is due to a duplicated option of
scheduler_host_manager. It is specified more than once somewhere.
Thanks,
Joseph
- Original Message -
From: Ben ben@gmail.com
To: openstack@lists.launchpad.net
Sent: Wednesday, August 22, 2012 8:27:39 AM
Subject: Re: [Openstack] Unable to start nova-scheduler : duplicate option:
scheduler_host_manager
Hi,
No idea for my scheduler problem ? It was working at the beginning (I
suppose because I could launch instances), but I did a lot of
modification, modifying networks, deleting nova db, rebuild it, etc.
Any idea on what I can do to identify the problem ? Where can I find the
mentionned option except in nova.conf ?
Ben
Le 22/08/2012 00:46, Ben a écrit :
Hi,
I'm trying to setup a little nova cluster with 3 nodes :
- 1 controller node running all services but compute
- 2 compute nodes running compute and network only
I have faced a lot of issues, but I can't understand this one. When I
start nova-scheduler on controller node, the process dies instantly with
this error :
CRITICAL nova [-] duplicate option: scheduler_host_manager
So I can't start an instance, it remains stuck in building state. I have
checked my nova.conf file, and I only see this line :
--scheduler_driver=nova.scheduler.simple.SimpleScheduler
What does means this error, how can I solve it ?
Thanks,
Ben
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
nova.conftrace.log___
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] Multi-Hypervisor Support
Looking at the Hypervisor section of the documentation, http://docs.openstack.org/trunk/openstack-compute/admin/content/selecting-a-hypervisor.html , it states You cannot configure more than one virtualization type on the compute nodes, so the hypervisor selection is for the entire installation. Is this statement still true with the recent filter additions, specifically the ImagePropertiesFilter and ComputeCapabilitiesFilter? Thanks. Michael - Michael Fork Cloud Architect, Emerging Solutions IBM Systems Technology Group___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] quantum-rootwrap
Hi Dan and ttx. I've posted what I sincerely hope is the last rev of changes for bug https://bugs.launchpad.net/quantum/+bug/1037815 I believe this addresses the last round of cleanups and questions, with the exception of amotoki's request for other agent support, eg L3. Since I don't have a good way to test that, I'd like to lobby for getting the fixes to the mechanism in, and treating extra agent cleanup as further bugs to be fixed later. I don't believe I'm breaking anything with the current patch, so it wouldn't make anything worse to install it. Trying to get all this sorted before end of week. Feedback appreciated. TIA... ___ 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] Changes to #openstack-meeting meetbot
Hi, I've updated the meetbot that lives in #openstack-meeting to require a meeting name argument after #startmeeting. This meeting name will be used in the path to the meeting logs. In the future, if you are going to start (for example) the Nova team meeting, you should say: #startmeeting nova We've had a practice for a while of linking to previous meeting logs on the wiki, however if someone forgets to do that immediately after a meeting, it can be difficult to track down the exact link. By requiring a meeting name, we're able to put more useful information in the URL of the links, which should make the task of finding older meetings easier. For instance, here's a link to a meeting I started with #startmeeting test: http://eavesdrop.openstack.org/meetings/test/2012/test.2012-08-22-17.11.html And all the test meetings in 2012: http://eavesdrop.openstack.org/meetings/test/2012/ And so forth. The text of the meeting name is free-form (though it is normalized to lower case and non-alphanumerics are translated to underscores), so please choose a name for your meeting and use it consistently so the directory structure remains useful. -Jim ___ 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] Multi-Hypervisor Support
We've managed to get things working by hardwiring the filtering scheduler to route instances to particular hosts that are running nova compute with different virtualization layers. (in our case, kvm and lxc for GPUs) -nld On Wed, Aug 22, 2012 at 12:34 PM, Michael J Fork mjf...@us.ibm.com wrote: Looking at the Hypervisor section of the documentation, http://docs.openstack.org/trunk/openstack-compute/admin/content/selecting-a-hypervisor.html, it states You cannot configure more than one virtualization type on the compute nodes, so the hypervisor selection is for the entire installation. Is this statement still true with the recent filter additions, specifically the ImagePropertiesFilter and ComputeCapabilitiesFilter? Thanks. Michael - Michael Fork Cloud Architect, Emerging Solutions IBM Systems Technology Group ___ 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
Re: [Openstack] VM can't ping self floating IP after a snapshot is taken
My friend has found a way to enable ping itself, when this problem happened. But not found why this happen. sudo echo 1 /sys/class/net/br1000/brif/virtual-interface-name/hairpin_mode I file a ticket to report this problem: https://bugs.launchpad.net/nova/+bug/1040255 hopefully someone can find why this happen and solve it. Thanks, Sam On Fri, Jul 20, 2012 at 3:50 PM, Gabriel Hurley gabriel.hur...@nebula.comwrote: I ran into some similar issues with the _*enable*_hairpin() call. The call is allowed to fail silently and (in my case) was failing. I couldn’t for the life of me figure out why, though, and since I’m really not a networking person I didn’t trace it along too far. ** ** Just thought I’d share my similar pain. ** ** **- **Gabriel ** ** *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *Sam Su *Sent:* Thursday, July 19, 2012 11:50 AM *To:* Brian Haley *Cc:* openstack *Subject:* Re: [Openstack] VM can't ping self floating IP after a snapshot is taken ** ** Thank you for your support. ** ** I checked the file nova/virt/libvirt/connection.py, the sentence self._enable_hairpin(instance) is already added to the function _hard_reboot(). It looks like there are some difference between taking snapshot and reboot instance. I tried to figure out how to fix this bug but failed. ** ** It will be much appreciated if anyone can give some hints. ** ** Thanks, Sam ** ** On Thu, Jul 19, 2012 at 8:37 AM, Brian Haley brian.ha...@hp.com wrote:** ** On 07/17/2012 05:56 PM, Sam Su wrote: Hi, Just This always happens in Essex release. After I take a snapshot of my VM ( I tried Ubuntu 12.04 or CentOS 5.8), VM can't ping its self floating IP; before I take a snapshot though, VM can ping its self floating IP. This looks closely related to https://bugs.launchpad.net/nova/+bug/933640, but still a little different. In 933640, it sounds like VM can't ping its self floating IP regardless whether we take a snapshot or not. Any suggestion to make an easy fix? And what is the root cause of the problem? It might be because there's a missing _enable_hairpin() call in the reboot() function. Try something like this... nova/virt/libvirt/connection.py, _hard_reboot(): self._create_new_domain(xml) +self._enable_hairpin(instance) self.firewall_driver.apply_instance_filter(instance, network_info) At least that's what I remember doing myself recently when testing after a reboot, don't know about snapshot. Folsom has changed enough that something different would need to be done there. -Brian ** ** ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] VM can't ping self floating IP after a snapshot is taken
Hello, Is it possible that, during snapshotting, libvirt just tears down virtual interface at some point, and then re-creates it, with hairpin_mode disabled again? This bugfix [https://bugs.launchpad.net/nova/+bug/933640] implies that fix works on spawn of instance. This means that upon resume after snapshot, hairpin is not restored. May be if we insert the _enable_hairpin() call in snapshot procedure, it helps. We're currently investigating this issue in one of our environments, hope to come up with answer by tomorrow. -- Best regards, Oleg On Wed, Aug 22, 2012 at 11:29 PM, Sam Su susltd...@gmail.com wrote: My friend has found a way to enable ping itself, when this problem happened. But not found why this happen. sudo echo 1 /sys/class/net/br1000/brif/virtual-interface-name/hairpin_mode I file a ticket to report this problem: https://bugs.launchpad.net/nova/+bug/1040255 hopefully someone can find why this happen and solve it. Thanks, Sam On Fri, Jul 20, 2012 at 3:50 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote: I ran into some similar issues with the _*enable*_hairpin() call. The call is allowed to fail silently and (in my case) was failing. I couldn’t for the life of me figure out why, though, and since I’m really not a networking person I didn’t trace it along too far. ** ** Just thought I’d share my similar pain. ** ** **- **Gabriel ** ** *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *Sam Su *Sent:* Thursday, July 19, 2012 11:50 AM *To:* Brian Haley *Cc:* openstack *Subject:* Re: [Openstack] VM can't ping self floating IP after a snapshot is taken ** ** Thank you for your support. ** ** I checked the file nova/virt/libvirt/connection.py, the sentence self._enable_hairpin(instance) is already added to the function _hard_reboot(). It looks like there are some difference between taking snapshot and reboot instance. I tried to figure out how to fix this bug but failed. ** ** ** ** It will be much appreciated if anyone can give some hints. ** ** Thanks, Sam ** ** On Thu, Jul 19, 2012 at 8:37 AM, Brian Haley brian.ha...@hp.com wrote:* *** On 07/17/2012 05:56 PM, Sam Su wrote: Hi, Just This always happens in Essex release. After I take a snapshot of my VM ( I tried Ubuntu 12.04 or CentOS 5.8), VM can't ping its self floating IP; before I take a snapshot though, VM can ping its self floating IP. This looks closely related to https://bugs.launchpad.net/nova/+bug/933640, but still a little different. In 933640, it sounds like VM can't ping its self floating IP regardless whether we take a snapshot or not. Any suggestion to make an easy fix? And what is the root cause of the problem? It might be because there's a missing _enable_hairpin() call in the reboot() function. Try something like this... nova/virt/libvirt/connection.py, _hard_reboot(): self._create_new_domain(xml) +self._enable_hairpin(instance) self.firewall_driver.apply_instance_filter(instance, network_info) At least that's what I remember doing myself recently when testing after a reboot, don't know about snapshot. Folsom has changed enough that something different would need to be done there. -Brian ** ** ___ 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] how to configure network on controller with 2 nics ?
Hello, I follow the instruction below to install openstack on RHEL6, but it only shows how to configure network with one NIC. Where can I find the doc about configuring openstack network with both public facing and private facing NICs, on RHEL6? http://docs.openstack.org/essex/openstack-compute/install/yum/content/compute-configuring-guest-network.html By the way, the official doc in the above link is for ubuntu. Please correct it for RHEL6 usage. Thanks, Xin smime.p7s Description: S/MIME Cryptographic Signature ___ 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] Keyring support in openstack
On Mon, Jul 30, 2012 at 5:48 PM, Adam Young ayo...@redhat.com wrote: On 07/30/2012 06:00 PM, Doug Hellmann wrote: On Mon, Jul 30, 2012 at 5:30 PM, Adam Young ayo...@redhat.com wrote: On 07/30/2012 05:17 PM, Kevin L. Mitchell wrote: On Mon, 2012-07-30 at 13:50 -0700, Bhuvaneswaran A wrote: The wiki mentions the password being saved using keyring.backend.UncryptedFileKeyring. Does that mean the password is saved in cleartext? Is the file protected in some way besides filesystem permissions? As mentioned in wiki page, the password is stored in base64 format. Which means it's stored in cleartext. That is Not Good(tm) :) Can Keyring be used to store a token instead? That would A) be better than password and B) avoid a Keystone hit. Don't tokens expire? Yes, they do, but that is no reason not to put them in the keyring, With the PKI tokens, you will be able to query a token's expiry without going across the wire. Adam, can you please file a ticket to use keyring to store tokens for keystone? I'll work on it. -- Regards, Bhuvaneswaran A www.livecipher.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] Keyring support in openstack
On Mon, Jul 30, 2012 at 2:30 PM, Doug Hellmann doug.hellm...@dreamhost.comwrote: On Mon, Jul 30, 2012 at 4:51 PM, Bhuvaneswaran A bhu...@apache.orgwrote: On Mon, Jul 30, 2012 at 7:46 AM, David Kranz david.kr...@qrclab.com wrote: I share Doug's concerns but would state some more strongly. IMO, it is simply unacceptable to modify user-visible behavior based on whether some package that happens to be used in an implementation is installed or not. This package is installed on Ubuntu by default and may be used by other applications that have nothing to do with OpenStack at all. Yes, as python-keyring is installed in almost all systems, the behaviour is unchanged. If we really want to go down this road there should be an environment variable that can be set to turn off this behavior for applications that do not want it. David, good point. I'll revise the patch to not use keyring, if environment variable USE_KEYRING=0. If environment variable is not set or if it is USE_KEYRING=1, then keyring is used to store password. How about OS_USE_KEYRING so it is clearer that the variable is related to openstack? Just to close the loop ... Doug, thank you for all the review comments. The patch to store encrypted password in keyring, for openstackclient, is merged today: I''ll extend this feature to other clients that prompt for password, like keystoneclient. https://review.openstack.org/#/c/9497/ It's also documented here: http://wiki.openstack.org/KeyringSupport -- Regards, Bhuvaneswaran A www.livecipher.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] Keyring support in openstack
Sweet thx all :-) This is great and a step forward… https://blueprints.launchpad.net/openstack-common/+spec/pw-keyrings Now just to get it into those config files to use something similar (no passwords in those pweeease…) -Josh From: Bhuvaneswaran A bhu...@apache.orgmailto:bhu...@apache.org Date: Wednesday, August 22, 2012 4:15 PM To: Adam Young ayo...@redhat.commailto:ayo...@redhat.com Cc: openstack openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Keyring support in openstack On Mon, Jul 30, 2012 at 5:48 PM, Adam Young ayo...@redhat.commailto:ayo...@redhat.com wrote: On 07/30/2012 06:00 PM, Doug Hellmann wrote: On Mon, Jul 30, 2012 at 5:30 PM, Adam Young ayo...@redhat.commailto:ayo...@redhat.com wrote: On 07/30/2012 05:17 PM, Kevin L. Mitchell wrote: On Mon, 2012-07-30 at 13:50 -0700, Bhuvaneswaran A wrote: The wiki mentions the password being saved using keyring.backend.UncryptedFileKeyring. Does that mean the password is saved in cleartext? Is the file protected in some way besides filesystem permissions? As mentioned in wiki page, the password is stored in base64 format. Which means it's stored in cleartext. That is Not Good(tm) :) Can Keyring be used to store a token instead? That would A) be better than password and B) avoid a Keystone hit. Don't tokens expire? Yes, they do, but that is no reason not to put them in the keyring, With the PKI tokens, you will be able to query a token's expiry without going across the wire. Adam, can you please file a ticket to use keyring to store tokens for keystone? I'll work on it. -- Regards, Bhuvaneswaran A www.livecipher.comhttp://www.livecipher.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
[Openstack] Question on tests
Hi all, I'm getting anvil to run tests and I was just wondering on a couple of tests I see there (the issues might be bugs?) I have had to exclude the following since they error (when say swift isn't there, or memcache/ldap isn't there), should those instead be skipping themselves when there needed 3rd party libraries is not installed? Thoughts? That would seem more appropriate then errorring out (when those things really aren't core keystone…) [ # These 2 seem to require swift, not always installed... 'test_swift_auth_middleware', 'test_s3_token_middleware', # Aren't always installing memcache... 'test_backend_memcache', # Oddness: 'unable to access signing dir /root/keystone-signing' 'test_nomemcache', # Aren't always installing ldap... 'test_backend_ldap', ] This running: http://pastebin.com/3Aaz4iLC To accomplish this new feature if u want to try it on RHEL6+ (getting ubuntu back in shape for the core components that anvil is supporting)… $ sudo ./smithy -a install …. $ sudo ./smithy -p conf/personas/solo/keystone.yaml -a test … That Is It :-P -Josh ___ 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] [openstack-dev] Translation, Internationalization and Localization in OpenStack
Update on Horizon pt_BR Translated 234 32.28% Remaining 491 67.72% Reviewed 0 0.00% About a third of the way through now. On Tue, Aug 21, 2012 at 6:14 PM, Matt Joyce matt.jo...@cloudscaling.comwrote: I've already put a dent in the pt / pt_br translations for horizon. I'd love some assistance though. Especially since my portuguese is secondary and honestly not very fluent. -Matt On Tue, Aug 21, 2012 at 6:07 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote: In conjunction with the PTLs, the Docs team, the Infrastructure team, various community members and more, I'm very happy to say that we are ready to share out a complete set of documentation and processes for translation, internationalization, and localization for OpenStack as a whole. The document lives on the wiki here: http://wiki.openstack.org/Translations The critical infrastructure is already in place, and Nova, Horizon, Keystone and Docs are already up and running with the new processes (and have been successfully for a little while now). Of immediate importance is the fact that we are technically under string freeze right now, so (as Thierry pointed out at the meeting earlier today) any review that alters strings marked for translation should be flagged and requires special consideration and coordination with translators before being merged. The string freeze gives translators a period of time before a release in which translations do not change so they can complete their work properly. Comments and critiques of the process are welcome, but let's keep them on the mailing list before making edits to the wiki page. Obviously we'll continue to refine this over time. Thanks, and happy translating! - Gabriel ___ OpenStack-dev mailing list openstack-...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ 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] Keyring support in openstack
On 08/22/2012 07:15 PM, Bhuvaneswaran A wrote: On Mon, Jul 30, 2012 at 5:48 PM, Adam Young ayo...@redhat.com mailto:ayo...@redhat.com wrote: On 07/30/2012 06:00 PM, Doug Hellmann wrote: On Mon, Jul 30, 2012 at 5:30 PM, Adam Young ayo...@redhat.com mailto:ayo...@redhat.com wrote: On 07/30/2012 05:17 PM, Kevin L. Mitchell wrote: On Mon, 2012-07-30 at 13:50 -0700, Bhuvaneswaran A wrote: The wiki mentions the password being saved using keyring.backend.UncryptedFileKeyring. Does that mean the password is saved in cleartext? Is the file protected in some way besides filesystem permissions? As mentioned in wiki page, the password is stored in base64 format. Which means it's stored in cleartext. That is Not Good(tm) :) Can Keyring be used to store a token instead? That would A) be better than password and B) avoid a Keystone hit. Don't tokens expire? Yes, they do, but that is no reason not to put them in the keyring, With the PKI tokens, you will be able to query a token's expiry without going across the wire. Adam, can you please file a ticket to use keyring to store tokens for keystone? I'll work on it. https://bugs.launchpad.net/keystone/+bug/1040361 -- Regards, Bhuvaneswaran A www.livecipher.com http://www.livecipher.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] [openstack-dev] Translation, Internationalization and Localization in OpenStack
I'm Brazilian, and I'll help with the translation. Marcelo Dieder On 22-08-2012 22:38, Matt Joyce wrote: Update on Horizon pt_BR Translated 234 32.28% Remaining 491 67.72% Reviewed0 0.00% About a third of the way through now. On Tue, Aug 21, 2012 at 6:14 PM, Matt Joyce matt.jo...@cloudscaling.com mailto:matt.jo...@cloudscaling.com wrote: I've already put a dent in the pt / pt_br translations for horizon. I'd love some assistance though. Especially since my portuguese is secondary and honestly not very fluent. -Matt On Tue, Aug 21, 2012 at 6:07 PM, Gabriel Hurley gabriel.hur...@nebula.com mailto:gabriel.hur...@nebula.com wrote: In conjunction with the PTLs, the Docs team, the Infrastructure team, various community members and more, I'm very happy to say that we are ready to share out a complete set of documentation and processes for translation, internationalization, and localization for OpenStack as a whole. The document lives on the wiki here: http://wiki.openstack.org/Translations The critical infrastructure is already in place, and Nova, Horizon, Keystone and Docs are already up and running with the new processes (and have been successfully for a little while now). Of immediate importance is the fact that we are technically under string freeze right now, so (as Thierry pointed out at the meeting earlier today) any review that alters strings marked for translation should be flagged and requires special consideration and coordination with translators before being merged. The string freeze gives translators a period of time before a release in which translations do not change so they can complete their work properly. Comments and critiques of the process are welcome, but let's keep them on the mailing list before making edits to the wiki page. Obviously we'll continue to refine this over time. Thanks, and happy translating! - Gabriel ___ OpenStack-dev mailing list openstack-...@lists.openstack.org mailto:openstack-...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ 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
Re: [Openstack] [openstack-dev] Translation, Internationalization and Localization in OpenStack
Muito Brigado. =P I'm American and I could use the assistance. =P On Wed, Aug 22, 2012 at 6:48 PM, Marcelo Dieder mdie...@sinos.net wrote: I'm Brazilian, and I'll help with the translation. Marcelo Dieder On 22-08-2012 22:38, Matt Joyce wrote: Update on Horizon pt_BR Translated 234 32.28% Remaining 491 67.72% Reviewed 0 0.00% About a third of the way through now. On Tue, Aug 21, 2012 at 6:14 PM, Matt Joyce matt.jo...@cloudscaling.comwrote: I've already put a dent in the pt / pt_br translations for horizon. I'd love some assistance though. Especially since my portuguese is secondary and honestly not very fluent. -Matt On Tue, Aug 21, 2012 at 6:07 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote: In conjunction with the PTLs, the Docs team, the Infrastructure team, various community members and more, I'm very happy to say that we are ready to share out a complete set of documentation and processes for translation, internationalization, and localization for OpenStack as a whole. The document lives on the wiki here: http://wiki.openstack.org/Translations The critical infrastructure is already in place, and Nova, Horizon, Keystone and Docs are already up and running with the new processes (and have been successfully for a little while now). Of immediate importance is the fact that we are technically under string freeze right now, so (as Thierry pointed out at the meeting earlier today) any review that alters strings marked for translation should be flagged and requires special consideration and coordination with translators before being merged. The string freeze gives translators a period of time before a release in which translations do not change so they can complete their work properly. Comments and critiques of the process are welcome, but let's keep them on the mailing list before making edits to the wiki page. Obviously we'll continue to refine this over time. Thanks, and happy translating! - Gabriel ___ OpenStack-dev mailing list openstack-...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ 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 ___ 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] [openstack-dev] Translation, Internationalization and Localization in OpenStack
onde e como ? :P Em 22/08/2012, às 22:48, Marcelo Dieder mdie...@sinos.net escreveu: I'm Brazilian, and I'll help with the translation. Marcelo Dieder On 22-08-2012 22:38, Matt Joyce wrote: Update on Horizon pt_BR Translated 234 32.28% Remaining491 67.72% Reviewed 0 0.00% About a third of the way through now. On Tue, Aug 21, 2012 at 6:14 PM, Matt Joyce matt.jo...@cloudscaling.com wrote: I've already put a dent in the pt / pt_br translations for horizon. I'd love some assistance though. Especially since my portuguese is secondary and honestly not very fluent. -Matt On Tue, Aug 21, 2012 at 6:07 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote: In conjunction with the PTLs, the Docs team, the Infrastructure team, various community members and more, I'm very happy to say that we are ready to share out a complete set of documentation and processes for translation, internationalization, and localization for OpenStack as a whole. The document lives on the wiki here: http://wiki.openstack.org/Translations The critical infrastructure is already in place, and Nova, Horizon, Keystone and Docs are already up and running with the new processes (and have been successfully for a little while now). Of immediate importance is the fact that we are technically under string freeze right now, so (as Thierry pointed out at the meeting earlier today) any review that alters strings marked for translation should be flagged and requires special consideration and coordination with translators before being merged. The string freeze gives translators a period of time before a release in which translations do not change so they can complete their work properly. Comments and critiques of the process are welcome, but let's keep them on the mailing list before making edits to the wiki page. Obviously we'll continue to refine this over time. Thanks, and happy translating! - Gabriel ___ OpenStack-dev mailing list openstack-...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ 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 ___ 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] [openstack-dev] Translation, Internationalization and Localization in OpenStack
Here: https://www.transifex.com/projects/p/openstack/ Marcelo Dieder On 22-08-2012 23:21, Elias Mussi wrote: onde e como ? :P Em 22/08/2012, às 22:48, Marcelo Dieder mdie...@sinos.net mailto:mdie...@sinos.net escreveu: I'm Brazilian, and I'll help with the translation. Marcelo Dieder On 22-08-2012 22:38, Matt Joyce wrote: Update on Horizon pt_BR Translated 234 32.28% Remaining 491 67.72% Reviewed0 0.00% About a third of the way through now. On Tue, Aug 21, 2012 at 6:14 PM, Matt Joyce matt.jo...@cloudscaling.com mailto:matt.jo...@cloudscaling.com wrote: I've already put a dent in the pt / pt_br translations for horizon. I'd love some assistance though. Especially since my portuguese is secondary and honestly not very fluent. -Matt On Tue, Aug 21, 2012 at 6:07 PM, Gabriel Hurley gabriel.hur...@nebula.com mailto:gabriel.hur...@nebula.com wrote: In conjunction with the PTLs, the Docs team, the Infrastructure team, various community members and more, I'm very happy to say that we are ready to share out a complete set of documentation and processes for translation, internationalization, and localization for OpenStack as a whole. The document lives on the wiki here: http://wiki.openstack.org/Translations The critical infrastructure is already in place, and Nova, Horizon, Keystone and Docs are already up and running with the new processes (and have been successfully for a little while now). Of immediate importance is the fact that we are technically under string freeze right now, so (as Thierry pointed out at the meeting earlier today) any review that alters strings marked for translation should be flagged and requires special consideration and coordination with translators before being merged. The string freeze gives translators a period of time before a release in which translations do not change so they can complete their work properly. Comments and critiques of the process are welcome, but let's keep them on the mailing list before making edits to the wiki page. Obviously we'll continue to refine this over time. Thanks, and happy translating! - Gabriel ___ OpenStack-dev mailing list openstack-...@lists.openstack.org mailto:openstack-...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ 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 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 ___ 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] [ceilometer] Metering meeting agenda for Thursday at 16:00 UTC (Aug 23rd, 2012)
Hi, The metering project team holds a meeting in #openstack-meeting, Thursdays at 1600 UTC http://www.timeanddate.com/worldclock/fixedtime.html?hour=16min=0sec=0. Everyone is welcome. Agenda: http://wiki.openstack.org/Meetings/MeteringAgenda * Review last week's actions - jaypipes to create ceilometer cookbook - nijaba to write description of component responsibility - dhellmann and nijaba to work on sessions for summit via email - dhellmann to ask jtrans about interest in reviewer status - nijaba to give core reviewer rights to gmb * Open discussion If you are not able to attend or have additional topic you would like to cover, please update the agenda on the wiki. Cheers, -- Nick Barcet nick.bar...@canonical.com aka: nijaba, nicolas signature.asc Description: OpenPGP digital signature ___ 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] Openstack Folsom - 3 Installation
Hi- Any inputs for understanding and resolving the issue... Kindly help me in this regard. -- Trinath On Wed, Aug 22, 2012 at 4:43 PM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi All- I'm installing Openstack Components of Folsom-3 milestone from the Tar files available from launchpad. Can any one guide me on the installation of the these components like the Essex component installation and configuration. I'm upto this level of Installation. For instance, Keystone component, I have untar the file and executed the following commands. *Keystone $* python setup.py build *Keystone $* python setup.py install. Will these two steps install the respective component and all its necessary components. With this type of Install can I use the Openstack components as I use them in the 'apt-get' based Essex installation. Kindly guide me on this... Thanking you all. -- Regards, -- Trinath Somanchi, +91 9866 235 130 -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
