Help with OneFS 7.0 REST api

aru.li...@gmail.com

unread,

Aug 22, 2013, 1:46:52 PM8/22/13

to isilon-u...@googlegroups.com

We had REST calls to create folders on Isilon share using OneFS 6.0 REST api. But recently we migrated to OneFS 7.0 and the code we had for 6.0 has stopped working since then.

There are quite bit changes with regards to REST calls now.

In 6.0, it was a simple PUT method to create a directory.

Taken from the 6.0 document, it was :

Filesystem API enables manipulation of files and directories on the /ifs file system. Files and directories on /ifs are mapped to Uniform Resource Identifiers (URIs) of the general form:

/1/ifs/<path><?scope>

So a GET was like this:

GET /1/ifs/<directory-path>[?verbose=<boolean>]

But now everything looks different:

A simple GET looks like this:

GET <resource-version>/<namespace>/object-id

And I tried these examples:

GET /platform/1/protocols/nfs/exports/ or

GET /platform/1/protocols/smb

What I am not able to figure out is what happened to the share we had created in 6.0. Will it be referenced as an ifs share or something else.

Because with all possible combinations I have tried, I am getting Forbidden status. And our system admin had not made any changes to the account that we are using.

For example:

curl -vvvvv --user xxx:xxx --insecure -X GET https://servername:8080/platform/1/ifs/SAS-ArchiveExport-dev

* About to connect() to servername port 8080 (#0)

* Trying 10.104.10.110... connected

* Connected to servername (xx.xxx.xx.xxx) port 8080 (#0)

* SSLv3, TLS handshake, Client hello (1):

* SSLv3, TLS handshake, Server hello (2):

* SSLv3, TLS handshake, CERT (11):

* SSLv3, TLS handshake, Server key exchange (12):

* SSLv3, TLS handshake, Server finished (14):

* SSLv3, TLS handshake, Client key exchange (16):

* SSLv3, TLS change cipher, Client hello (1):

* SSLv3, TLS handshake, Finished (20):

* SSLv3, TLS change cipher, Client hello (1):

* SSLv3, TLS handshake, Finished (20):

* SSL connection using DHE-RSA-AES256-XHX

* Server certificate:

* subject: C=US; ST=Washington; L=Seattle; O=Isilon Systems, Inc.; CN=Isilon Systems; emailAddress=sup...@isilon.com

* start date: 2005-11-23 17:17:38 GMT

* expire date: 2015-11-21 17:17:38 GMT

* common name: Isilon Systems (does not match 'servername')

* issuer: C=US; ST=Washington; L=Seattle; O=Isilon Systems, Inc.; CN=Isilon Systems; emailAddress=sup...@isilon.com

* SSL certificate verify result: self signed certificate (18), continuing anyway.

* Server auth using Basic with user 'api'

> GET /platform/1/ifs/SAS-ArchiveExport-dev HTTP/1.1

> Authorization: Basic YXXpXmFwaQ==

> User-Agent: curl/7.21.4 (universal-apple-darwin11.0) libcurl/7.21.4 OpenSSL/0.9.8r zlib/1.2.5

> Host: servername:8080

> Accept: */*

>

< HTTP/1.1 403 Forbidden

< Date: Thu, 22 Aug 2013 16:29:07 GMT

< Server: Apache/2.2.21 (FreeBSD) mod_ssl/2.2.21 OpenSSL/0.9.8x mod_webkit2/1.0 mod_fastcgi/2.4.6

< WWW-Authenticate: Basic

< Vary: Accept-Encoding

< Content-Length: 238

< Content-Type: text/html; charset=iso-8859-1

<

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

<title>403 Forbidden</title>

</head><body>

<h1>Forbidden</h1>

<p>You don't have permission to access /platform/1/ifs/SAS-ArchiveExport-dev

on this server.</p>

</body></html>

* Connection #0 to host 'servername' left intact

* Closing connection #0

* SSLv3, TLS alert, Client hello (1):

Not sure what changed the shares created on isilon with the upgrade. Any pointers is much appreciated.

Thanks,

AL

Rob Peglar

unread,

Aug 22, 2013, 4:21:50 PM8/22/13

to isilon-u...@googlegroups.com

Get a copy of the RAN (Restful Access to Namespace) API document. This came out in 7.0.2.

To create a directory foo looks like this

PUT /namespace//ifs/foo

with a header of

x-isi-ifs-target-type:container

There are also optional headers to do things like set perms.

Once again, the RAN API guide is very useful. Give it a read.

Rob

--
You received this message because you are subscribed to the Google Groups "Isilon Technical User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isilon-user-gr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Erik Weiman

unread,

Aug 22, 2013, 5:29:54 PM8/22/13

to isilon-u...@googlegroups.com

Not to mention the RAN setup in 7.0 is supposed to be much more robust of an implementation than previously was seen in older versions of OneFS.

--

Erik Weiman

Sent from my iPhone 4

aru.li...@gmail.com

unread,

Aug 23, 2013, 9:24:50 AM8/23/13

to isilon-u...@googlegroups.com

Rob,

Thank you very much for this pointer.I was provided only with the OneFS 7.0 Platform API Reference document by my admin. I will look up for the RAN API document.

Best,

AL

* subject: C=US; ST=Washington; L=Seattle; O=Isilon Systems, Inc.; CN=Isilon Systems; emailAddre...@isilon.com

* start date: 2005-11-23 17:17:38 GMT

* expire date: 2015-11-21 17:17:38 GMT

* common name: Isilon Systems (does not match 'servername')

* issuer: C=US; ST=Washington; L=Seattle; O=Isilon Systems, Inc.; CN=Isilon Systems; emailAddre...@isilon.com

aru.li...@gmail.com

unread,

Aug 23, 2013, 9:26:15 AM8/23/13

to isilon-u...@googlegroups.com

I agree with you. I see session management options in this version which is good for us.

* subject: C=US; ST=Washington; L=Seattle; O=Isilon Systems, Inc.; CN=Isilon Systems; emailAddre...@isilon.com

* start date: 2005-11-23 17:17:38 GMT

* expire date: 2015-11-21 17:17:38 GMT

* common name: Isilon Systems (does not match 'servername')

* issuer: C=US; ST=Washington; L=Seattle; O=Isilon Systems, Inc.; CN=Isilon Systems; emailAddre...@isilon.com

Reply all

Reply to author

Forward