http://cgtek.it/uyrsoyrj/jivjynwm.bnligkqbxewrhs
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Yes tempurl and and tempauth are tessted together, your pipeline looks good.
"allow_overrides = false" in the tempauth section could cause this, but
it's default is true.
Are you creating the tempurl's with "bin/swift-temp-url" ???
clayg@swift:~$ swift post -m temp-url-key:asdf
clayg@swift:~$ s
Wow, so I glanced quickly at the github project to try and get some
context, but I think I actually start getting *more* confused when I see
"swift" in the same class name as "file-system" ;)
I'd like you (or maybe vaidy, hi vaidy!) to correct me if I'm wrong, but
this hadoop integration will *not
Did you get this worked out?
Starting the replicators on the new nodes should create the objects
directory.
On Sat, Apr 13, 2013 at 2:26 AM, Philip wrote:
> Hi,
>
> I just tried to add two new servers into the ring. Only the containers
> were replicated to the new servers but there are no obje
Hi Peter,
No, nothing special should be needed - sometimes it's tricky to get your
launchpad account hooked into to review.openstack.org - but if that's
giving you trouble just ask for help in #openstack-dev (we've all been
there).
So yeah, if you've got some code that helps fix a problem or is s
On Fri, Sep 28, 2012 at 4:37 AM, Ahmed Al-Mehdi wrote:
> Who manages LVM VG - "nova-volumes".
The operator is responsible for creating the LVM volume group, from
the physical volumes's available on the system. This options
specifies the name of the volume group that the volume-manager will
use
On Thu, Jun 28, 2012 at 4:52 AM, Milind wrote:
> Thanks for reply.
>
> When I ran following command
>
> tgtadm --lld iscsi --mode target --op show
>
> It hangs forever
>
So I guess the command to create the export probably hangs too, and
the greenthread in nova-volume never joins... which is
On Fri, Jun 22, 2012 at 11:18 AM, jsb wrote:
> Hello,
> I am able to create a volume (Essex released version). But, I am not able to
> attach it to an instance.
>
> I am using the following in nova.conf:
> --iscsi_ip_address=10.1.2.0
Is that correct? shouldn't it be like 10.1.2.*
> --iscsi_help
On Thu, Apr 12, 2012 at 7:35 AM, J. Daniel Schmidt wrote:
> In our point of view foreign keys should be used in all possible places. This
> would not harm any database that does not support them but helps all of us to
> find data inconsistencies and related bugs, which leads to faster development
rereqs met, both can probably be used to mount a
> new volume.
Exactly.
> Reasonable?
>
So should the distinction be purely and implementation detail or will the OSAPI
support a way to expose the difference to the consumer? Naming aside, there's
uses cases where one may be bette
Hey Jon,
Specially regarding "expanding the ring" - one of the Cloud Files ops wrote
some tips in a lp answer awhile back:
https://answers.launchpad.net/swift/+question/152024
Clay Gerrard
Software Developer
Rackspace
> -Original Message-
> From: openstack-boun
Unittest2 lets you define a test case that is expected to fail:
http://docs.python.org/library/unittest.html#unittest.expectedFailure
new in 2.7, but it could be possible to backport - or do something similar...
May have issues with nose:
http://code.google.com/p/python-nose/issues/detail?id=325
12 matches
Mail list logo
