Hi, Hao
Did you already do the setting for where shared jerasure library located?
The log message looks that Linux system doesn't have a seach path for that.
Like:
- Add /usr/local/lib path (if you installed libJerasure.so in another location,
you should set the path here) into /etc/ld.so.conf
Hi Venkatesh,
Your setting seems wrong for authtoken middleware in proxy-server.conf.
The log shows proxy-server was trying to look up "auth_token" due to your pipeline setting (probably there is "auth_token" string in your pipeline) but the section name of the middleware setting would
be someth
Hello Alexandr,
As the error message described, region and zone take an integer value[1] so
probably you should set the value like as:
swift-ring-builder account.builder add --region 1 --zone 1 --ip 192.168.57.51
--port 6002 --device d1 --weight 100
Although you need to keep your own map like
ack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
--
--
Kota Tsuyuzaki(露﨑 浩太)
NTT Software Innovation Ce
Correct. Thanks John for your quick response.
Kota
(2016/10/13 12:14), John Dickinson wrote:
> Unfortunately, no (as far as i know). It's a proprietary library used by NTT.
>
> However, if you update to the latest version of liberasurecode, that warning
> message is suppressed.
>
> --John
>
>
r_factory
>>>> auth_port = 35357
>>>> auth_host = keystone
>>>> auth_protocol = http
>>>>
>>>> The swift3 docs need updating, as it is not obvious what has gone wrong
>>>>
}
> }
> }
> }' \
> http://keystone:5000/v3/auth/tokens ; echo
>
> *http://proxy:8080/v1/AUTH_3f842db875cc48b99d7ff246c27a2e6a
> <http://proxy:8080/v1/AUTH_3f842db875cc48b99d7ff246c27a2e6a>* - is the
> public endpoint
>
> Am I doing correctly?
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
--
>>> - Community : *Openstack Korea Community*
>>> - Name : Nalee Jang (장현정)
>>> - Company: ASD Korea Cloudike System Engineer.
>>> - Contact : +82-10-3454-4260 / nalee...@gmail.com
>>> - Blog: http://naleejang.tistory.com
&g
Hello Shyam,
I did not have so much experience with s3curl but it looks like the problem is
caused by client but it seems like the s3token middleware, which is to get
authentication with keystone.
So let us check "What authentication are you using", then check "your exisiting
configuration". Th
Hi, Shyam
> tester => {
> id => 'test:tester',
> key => 'testing',
> },
If you are using this id/password to get your token from keystone,
you should set them as access_key and secret key for your s3 client.
You don't have to set any token information from keystone for you
Hi Shyam,
You should specify the path starts from bucket. It will be like
http://20.20.20.229:8080/testBucket
assuming you didn't configure virtual-hosted style.
Even if your *Swift* endpoint is
http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578,
swift3 doesn't require the accoun
e4d-005b10de09
> < Date: Fri, 01 Jun 2018 05:47:53 GMT
> < Transfer-Encoding: chunked
> * HTTP error before end of send, stop sending
> <
>
> * Closing connection 0
> SignatureDoesNotMatchThe request signature we
> calculated does not match the signature you provided.
ack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
--
lets provide such capability.
>
> Another example is that a user may want to install a Swift3-like
> middleware to provide APIs to a 3rd party, but she doesn't want other
> users to see this middleware.
>
> Regards,
> Qiao
>
> On Mon, Sep 17, 2018 at 9:19 PM Kota TSU
or
It might work for your use case.
Thanks,
Kota
(2018/09/19 5:52), Qiao Kang wrote:
> Dear Kota,
>
> On Mon, Sep 17, 2018 at 11:43 PM Kota TSUYUZAKI
> wrote:
>>
>> Hi Quio,
>>
>>> I know Storlets can provide user-defined computation functionalities,
>>>
Hi Quao,
See inline responses below, please.
(2018/09/27 0:58), Qiao Kang wrote:
> Kota,
>
> Sorry for the late response, see more below:
>
> On Fri, Sep 21, 2018 at 2:59 AM Kota TSUYUZAKI
> wrote:
>>
>> Hi Qiao,
>>
>>> Thanks! I'm intere
17 matches
Mail list logo
