Re: [Openstack] [GLANCE] Ready to move to GitHub/Gerrit?

2011-08-02 Thread Andrey Brindeyev
 Right now i will take anything but prefer rpms. :)
 
 Here ya go :)
 
 http://yum.griddynamics.net/yum/master/openstack/

Jan,

take you risk and try these RPMs on CentOS 6.
Feel free to provide a feedback to me.
We tested our RPMs on RHEL 6.1 x86_64.

Our Diablo-3 branch is almost ready for release:
http://yum.griddynamics.net/yum/diablo-3/openstack/

It's under QA now and should be released at the end of this week.

Andrey Brindeyev
Grid Dynamics, Development Manager
abrinde...@griddynamics.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] Nova/Keystone integration and /usr/bin/nova

2011-08-02 Thread Andrey Brindeyev
Hi all!

Is /usr/bin/nova supposed to work when you enable Keystone integration in Nova?

Me got following:

# nova list
'x-server-management-url'

# nova show 1
'x-server-management-url'

strace output:
recvfrom(3, 305 Use Proxy\n\nThe resource must..., 136, 0, NULL, NULL) = 136

Andrey Brindeyev
Grid Dynamics, Development Manager
abrinde...@griddynamics.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] Nova/Keystone integration and /usr/bin/nova

2011-08-02 Thread Carlo Impagliazzo
Alle martedì 02 agosto 2011, Andrey Brindeyev ha scritto:
 Hi all!

 Is /usr/bin/nova supposed to work when you enable Keystone integration in
 Nova?

 Me got following:

 # nova list
 'x-server-management-url'

 # nova show 1
 'x-server-management-url'

 strace output:
 recvfrom(3, 305 Use Proxy\n\nThe resource must..., 136, 0, NULL, NULL) =
 136

 Andrey Brindeyev
 Grid Dynamics, Development Manager
 abrinde...@griddynamics.com

Hi all
I've experienced the same problem, I've opened an issue in python novaclient 
for this thing:

https://github.com/rackspace/python-novaclient/issues/35

when  novaclient library tries to call something in the API server keystone 
give response to redirect the connection to perform authentication.

This is the right behaviour ( from keystone side ) but python library ( client 
side ) is yet unable to understand so we have this crash.

Carlo

___
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] Nova/Keystone integration and /usr/bin/nova

2011-08-02 Thread Kevin L. Mitchell
On Tue, 2011-08-02 at 10:24 +0200, Carlo Impagliazzo wrote:
 when  novaclient library tries to call something in the API server keystone 
 give response to redirect the connection to perform authentication.
 
 This is the right behaviour ( from keystone side ) but python library ( 
 client 
 side ) is yet unable to understand so we have this crash.

I have sent email here about my solution to this issue, and there's also
a blueprint open:

https://blueprints.launchpad.net/glance/+spec/pluggable-auth
http://wiki.openstack.org/ClientAuthenticationPlugin

So far there haven't been any comments, and I won't be able to get to
this likely until our next sprint...
-- 
Kevin L. Mitchell kevin.mitch...@rackspace.com

This email may include confidential information. If you received it in error, 
please delete 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


[Openstack] Questions About test_localization.py

2011-08-02 Thread Zed A. Shaw
Hi All,

I'm going to be spending my days for a little while just taking tests
and source files that haven't been touched in a while and refactoring
them or cleaning them up.  The first one I picked was
tests/test_localization.py, and I've refactored it to be this:

http://codepad.org/YTODudUt

It does the same thing, but it's using the Python AST so it's accurate
about what it's checking and source lines, etc.  It is slower though,
but about 2 seconds.

Now, after refactoring that, I'm sort of confused about actually what
this test is doing.  I mean, it's just checking % signs in strings,
which seems sort of pointless as a gettext check.

I want to either:

1.  Make this confirm that the strings are in gettext, and
find other strings that should also be in gettext but aren't.

2. Get rid of this test as it's not doing much.

Comments welcome.

-- 
Zed A. Shaw
http://zedshaw.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] Questions About test_localization.py

2011-08-02 Thread Vishvananda Ishaya

On Aug 2, 2011, at 4:23 PM, Zed A. Shaw wrote:

 Hi All,
 I'm going to be spending my days for a little while just taking tests
 and source files that haven't been touched in a while and refactoring
 them or cleaning them up.

Awesome.  This should be very helpful.

 The first one I picked was
 tests/test_localization.py, and I've refactored it to be this:
 
 http://codepad.org/YTODudUt
 
 It does the same thing, but it's using the Python AST so it's accurate
 about what it's checking and source lines, etc.  It is slower though,
 but about 2 seconds.

:( No one likes slower, but i guess it gives us a chance to do some additional 
checking.

 
 Now, after refactoring that, I'm sort of confused about actually what
 this test is doing.  I mean, it's just checking % signs in strings,
 which seems sort of pointless as a gettext check.
 
 I want to either:
 
 1.  Make this confirm that the strings are in gettext, and
 find other strings that should also be in gettext but aren't.

+0 I like finding other strings, although I'm not sure if it is possible to 
define what should be in gettext.  Verifying that the strings are in gettext 
seems a little bit pointless.
 
 2. Get rid of this test as it's not doing much.

-1  The original purpose of the test was that people would add strings with 
multiple positional replacement strings.  This is hard to translate in some 
cases, because the translators may need control over word order.  We had a 
series of 10 or so reviews, which was please convert your positional 
replacement strings to keyword replacement strings.  After a bunch of reviews, 
someone finally wrote a test to verify it so we didn't have to repeat it a 
million times.

The original naive code was fine for that application.  Your refactor is very 
useful if you want to do some of the things you mentioned in 1., otherwise the 
existing test was solving the one issue that we had.

 
 Comments welcome.
 
 -- 
 Zed A. Shaw
 http://zedshaw.com/
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


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


Re: [Openstack] Questions About test_localization.py

2011-08-02 Thread Dan Wendlandt
On Tue, Aug 2, 2011 at 4:48 PM, Vishvananda Ishaya vishvana...@gmail.comwrote:


 -1  The original purpose of the test was that people would add strings with
 multiple positional replacement strings.  This is hard to translate in some
 cases, because the translators may need control over word order.  We had a
 series of 10 or so reviews, which was please convert your positional
 replacement strings to keyword replacement strings.  After a bunch of
 reviews, someone finally wrote a test to verify it so we didn't have to
 repeat it a million times.


as a data point, I was ignorant of this positional replacement string issue,
my code tripped this test, and I learned without a core dev having to
explain.  Definitely valuable.



 The original naive code was fine for that application.  Your refactor is
 very useful if you want to do some of the things you mentioned in 1.,
 otherwise the existing test was solving the one issue that we had.

 
  Comments welcome.
 
  --
  Zed A. Shaw
  http://zedshaw.com/
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp


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




-- 
~~~
Dan Wendlandt
Nicira Networks, Inc.
www.nicira.com | www.openvswitch.org
Sr. Product Manager
cell: 650-906-2650
~~~
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp