Thank you all for your help!
It have started the proxy finally.
Here is the configuration that I used:
[filter:swift3]
use = egg:swift3#swift3
[filter:s3token]
paste.filter_factory = swift3.s3_token_middleware:filter_factory
auth_uri = http://keystone:35357/
Also I have installed dependencies:
Hello,
I try to use s3curl to test swift3 but I miss something.
Here is the command which I use:
./s3curl.pl - 'swift' -key '3d8b70ad194a4cf6857e59ec638d' -get - -s -v
http://proxy:8080/v1/AUTH_3f842db875cc48b99d7ff246c27a2e6a
It shows:
Can't locate Digest/HMAC_SHA1.pm in @INC (@INC contains
Hello again,
I'm not familier with s3curl in detail though,
> ./s3curl.pl - 'swift' -key '3d8b70ad194a4cf6857e59ec638d' -get - -s -v
> http://proxy:8080/v1/AUTH_3f842db875cc48b99d7ff246c27a2e6a
>
could you try:
./s3curl.pl - 'swift' -key 'swift' -get - -s -v http://proxy:8080/
IIRC, secret
On Oct 12, 2016, at 10:28 PM, Mark Kirkwood wrote:
> I think you can avoid having to do that by including 22 in tcp_ports variable
> (see trove/common/cfg.py). I only noticed this after laboriously amending sec
> groups many times myself…
Yeah, I did that a few months ago. It was in 'some' of
The same error..(
Can't locate Digest/HMAC_SHA1.pm in @INC (@INC contains:
/usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl
/usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at ./
s3curl.pl line 20.
BEGIN failed--compilation aborted at ./s3curl.pl line 20.
On Oct 13, 2016, at 9:29 AM, Alexandr Porunov wrote:
> Can't locate Digest/HMAC_SHA1.pm in @INC (@INC contains:
You need to install the "libdigest-hmac-perl" package..
--
Try not. Do. Or do not. There is no try!
- Yoda
___
Mailing list: http://lists.
To get token I use the next command:
curl -i \
-H "Content-Type: application/json" \
-d '
{ "auth": {
"identity": {
"methods": ["password"],
"password": {
"user": {
"name": "swift",
"domain": { "name": "default" },
"password": "swift"
Thank you. You were right.
Now s3curl works but I don't know how to use it.. I try to check if swift3
is working with the next command:
./s3curl.pl --id 'swift' -key '384c48d6a26244aebcfa26cff4567bc0' -get -s
-v http://proxy:8080/v1/AUTH_3f842db875cc48b99d7ff246c27a2e6a
and
./s3curl.pl --id
Dear Team,
I am working on liberty version of openstack environment.
As per generic liberty openstack guide, i was using linux bridging with
vxlan, but want to move to ovs.
I need your help to configure my platform as per OVS requirement.
My architecture is
Node 1 - controller + network + comp
Looks like no, there is no such method. I'm not sure why reassigning is
allowed, seems wrong to me.
Also I see you're using nova floating ip API. If you have neutron
enabled in your environment you should avoid using nova network-related
methods. There is an equivalent neutron call for this:
Awaiting your response please!
Can i use management interface as tunneling interface?
Regards
Gaurav Goyal
On Thu, Oct 13, 2016 at 6:52 AM, Gaurav Goyal
wrote:
> Dear Team,
>
> I am working on liberty version of openstack environment.
>
> As per generic liberty openstack guide, i was using li
Hi All,
The Ubuntu OpenStack team is pleased to announce the general availability
of OpenStack Newton, available in today’s release of Ubuntu 16.10 (Yakkety
Yak) [0] and also available for Ubuntu 16.04 LTS (Xenial Xerus) via the
Ubuntu Cloud Archive.
Ubuntu 16.04 LTS
Yo
Any help for this please?
-- Forwarded message --
From: Gaurav Goyal
Date: Thu, Oct 13, 2016 at 6:52 AM
Subject: Fwd: Help for replacing linux bridging with OpenVswitch
To: openstack@lists.openstack.org
Dear Team,
I am working on liberty version of openstack environment.
As
I did it.
First I need to create ec2 credentials:
openstack ec2 credentials create
Then I had to change "my @endpoints" parameter in s3curl.pl as following:
my @endpoints = ( 'proxy');
And then just use my credentials with s3curl.pl
For example. For containers list:
./s3curl.pl --id access_key
Guys,
I'm trying to launch a stack via Heat, by using the following template
(I'm copying just part of it here):
---
demosrv:
type: OS::Nova::Server
depends_on: ctrl_subnet
properties:
name: { str_replace: { params: { $stack_name: { get_param:
'OS::stack_name' } }, template:
On 13 October 2016 at 17:21, Martinx - ジェームズ
wrote:
> Guys,
>
> I'm trying to launch a stack via Heat, by using the following template
> (I'm copying just part of it here):
>
> ---
> demosrv:
> type: OS::Nova::Server
> depends_on: ctrl_subnet
> properties:
> name: { str_repla
Guys,
If I remove the following line out from my Heat template:
https://github.com/sandvine-eng/svauto/blob/dev/misc/os-heat-templates/demo-simple-stack-1.yaml#L80
---
depends_on: ctrl_subnet
---
Then, the stack creation fails... But, why?
I didn't used this option with Kilo / IceHouse / J
On 13 October 2016 at 17:26, Martinx - ジェームズ
wrote:
>
>
> On 13 October 2016 at 17:21, Martinx - ジェームズ
> wrote:
>
>> Guys,
>>
>> I'm trying to launch a stack via Heat, by using the following template
>> (I'm copying just part of it here):
>>
>> ---
>> demosrv:
>> type: OS::Nova::Server
>>
On Thu, 13 Oct 2016 11:58:58 +0900
Yu Watanabe wrote:
> Oct 12 19:44:45 opstack-objstorage1 swift-account-server[27793]: Error:
> [swift-hash]: both swift_hash_path_suffix and swift_hash_path_prefix are
> m...ft.conf
Leaving libshss aside, Swift being unable to read /etc/swift/swift.conf
is typi
Thanks Pete.
I got my openstack-swift-account.service up now.
SELINUX was the root cause for preventing the service to go up.
[root@opstack-objstorage1 srv 2016.10.14 10:46:00]# ls -lZ
/etc/swift/swift.conf
-rw-r--r--. root swift system_u:object_r:etc_t:s0
/etc/swift/swift.conf
On Fri, Oct 14,
Hi!
I am verifying the installation using the swift stat command but it returns
503 Service Unavailable.
[root@opstack-controller src 2016.10.14 11:55:37]# swift stat
Account HEAD failed:
http://opstack-cont-manage:8080/v1/AUTH_a31f7e8e9ecc4d0e9d0d6c1de6c4c004
503 Service Unavailable
I have chec
On 14/10/16 16:03, Yu Watanabe wrote:
Hi!
I am verifying the installation using the swift stat command but it
returns 503 Service Unavailable.
[root@opstack-controller src 2016.10.14 11:55:37]# swift stat
Account HEAD failed:
http://opstack-cont-manage:8080/v1/AUTH_a31f7e8e9ecc4d0e9d0d6c1de
Thanks for the reply.
I confirmed that proxy config has account_autocreate = true defined and
restarted the openstack-swift-proxy.service.
But still the account-server returns 404.
Oct 14 13:46:40 opstack-objstorage1 account-server: 10.1.0.6 - -
[14/Oct/2016:04:46:40 +] "HEAD
/sdd/292/AUTH_a
At the same time , I see connection errors in the proxy server.
Oct 14 14:05:08 opstack-controller proxy-server: Deferring reject downstream
Oct 14 14:05:08 opstack-controller proxy-server: - - 14/Oct/2016/05/05/08
HEAD /v1/AUTH_a31f7e8e9ecc4d0e9d0d6c1de6c4c004 HTTP/1.0 204 - Swift - - - -
tx60f54
On 14/10/16 18:07, Yu Watanabe wrote:
At the same time , I see connection errors in the proxy server.
Oct 14 14:05:08 opstack-controller proxy-server: Deferring reject
downstream
Oct 14 14:05:08 opstack-controller proxy-server: - -
14/Oct/2016/05/05/08 HEAD /v1/AUTH_a31f7e8e9ecc4d0e9d0d6c1de
25 matches
Mail list logo
