Hi Somesh,

thanks for your quick response. 

That was also my hope but the protocol in the url seems to be ignored. 
In the database is a attribute called protocol which was set to http in all my 
tries. 
It seems to be the default if you not explicitly set the protocol. 

I tried to set the protocol via a key value pair in the details part of the api 
call and via a separate option which I named protocol. 
There was never an error but it hasn't worked either. 

Here is the last call I tried:
update cloudtouseobjectstore name=Secondary 
zoneId=01b01ed7-ed98-4908-93a3-8729ef0db427 url=https://my.s3.storage 
details[0].key=accesskey details[0].value=XXXXX details[1].key=secretkey 
details[1].value=XXXXX details[2].key=bucket details[2].value=secondary 
details[3].key=endpoint details[3].value=my.s3.storage details[4].key=protocol 
details[4].value=https provider=S3

Kind regards
Christian

> Am 11.08.2015 um 18:36 schrieb Somesh Naidu <somesh.na...@citrix.com>:
> 
> Christian,
> 
> I am not 100% as I haven’t tried this before but I was thinking the parameter 
> "URL" would affect this?
> 
> Regards,
> Somesh
> 
> 
> -----Original Message-----
> From: christian.kir...@zv.fraunhofer.de 
> [mailto:christian.kir...@zv.fraunhofer.de] 
> Sent: Tuesday, August 11, 2015 11:22 AM
> To: users@cloudstack.apache.org
> Subject: updatecloudtouseobjectstore options
> 
> Hi all,
> 
> we are fairly new to all the cloudstack stuff, so excuse me if I ask kinda 
> stupid questions.
> 
> We had set up our cloudstack with nfs as secondary storage, now we like to 
> use our s3 storage.
> I read through many threads how to add my own certificates, root ca and 
> intermediate ca, now I am at the point where I need to test all the fancy 
> stuff I configured.
> Therefore I need to switch from nfs secondary to s3.
> I found the updatecloudtouseobjectstore api call and gave it a couple of 
> tries with cloudmonkey.
> On the first glance it seems to do what it should do, but I wasn’t able to 
> figure out the right argument to tell the api call to set the protocol to 
> https.
> 
> Any suggestions?
> 
> Kind Regards
> Christian

Reply via email to