This post is more than 5 years old
10 Posts
0
1989
July 8th, 2015 09:00
ECS Weird Behavior
I was playing around with ECS in our Dallas lab and maybe I’m an idiot but this doesn’t seem right. Here’s what I did:
Created a namespace called swift, owner is rcc
Created user rcc tied to swift namespace
Created bucket rcc_bucket (owned by rcc)
Using Cyberduck I logged in successfully under rcc to /swift/rcc_bucket
I couldn’t upload a file or create a file (?) but I could created a new folder (I called “hi”)... and it created a new “hi” bucket within swift namespace (?!). I can upload a file into the “hi” bucket/folder.
Thinking it’s because I’m logged in as the namespace owner, I created a new user (rcc2) and a new bucket (rcc2_bucket) whose owner is rcc2 and part of same namespace (swift).
Using Cyberduck, I log into /swift/rcc2_bucket and I see the “hi” bucket (?!). I can’t upload a file still to “rcc2_bucket", but I can create a new folder (which, again, creates a new bucket). I’d assume I COULDN’T do this under rcc2 user as the account isn’t the owner of swift namespace...
Now I’m starting to think I’m just logged into swift namespace and Cyberduck can’t get into any of the buckets that I create via ECS portal. Yet when I put /swift/hi in the path it doesn’t go into “hi” bucket. I’ve confirmed I can log into just /swift and I see all the folders/buckets that I created under Cyberduck, and I can’t see rcc_bucket or rcc2_bucket…
Or is this because I’m looking at the namespace as a filesystem and the rcc buckets aren’t set to filesystem? I did try creating a new bucket in ECS with fs enabled but it still doesn’t show up.
Attached/below are screenshots
Here’s a couple of questions as well:
What’s the purpose of setting the replication group at the namespace level if you have to set it at the bucket level as well? What happens if those conflict?
For some reason I can’t create 2 name spaces tied to the same admin account. Is this expected behavior? Why is that?
What does “Access during outage” mean?
Retention settings (seconds, minutes, hours, etc)… is that only applied to deleted data (I’m assuming)?
[cid:7E7E210C-853D-4490-BF6D-09DA4E93F2A8@corp.emc.com][cid:FD84ECCA-3D04-43D0-ACA7-5388B2640367@corp.emc.com]
Ryan Clair
EMC Sr. Systems Engineer
214-552-4758
ryan_clair
10 Posts
1
July 9th, 2015 08:00
AHHH, buckets created in ECS portal is S3, S3+Hadoop, or CAS. So you can't create swift or atmos containers/subtenant. That has to be done outside of ECS portal?
Source:
http://www.emc.com/techpubs/ecs/ecs_create_bucket-1.htm
(CREATE A BUCKET USING ECS PORTAL section)
thakkd1
1 Rookie
•
13 Posts
1
July 8th, 2015 10:00
Ryan, that is interesting. We would need to look at the setup (Webex tomorrow?). in the meantime could you try to connect with S3 broswer and see if that works or not. Just to confirm.
[DT] Replication Group is a mandatory construct in ECS. It defines the level of protection and storage efficiency for your data. You specify a RG at the namespace level to specify a default RG. That way someone using S3 api (not the EMC extensions) can still create a bucket in the namespace and the bucket would be created using the default RG for the namespace.
Yes, in ECS a namespace admin can only be the administrator for one namespace. We have heard feedback from other channels too and are investigating to alleviate the limitation in future. The motivation stemmed from the fact that in ECS multi tenancy model, namespace = tenant.
Access during outage refers to the Temporary Site Outage feature in ECS 2.0. It is basically the ability to access the data at a secondary location in case of a network disruption. You can read more about it in the product documentation.
The idea of a retention setting is when does the system allow an object to be deleted. If you have rentention set on an object the object can only be deleted if the retention period has expired.
ryan_clair
10 Posts
0
July 8th, 2015 11:00
Yeah, tomorrow I should have some time. I'll send you a calendar invite.
I just tried S3 Browser and I see the buckets I created in ECS but not what I created with Cyberduck (which my user should see those that it has access to... shouldn't it?). Very strange.
So... what I create in ECS can only be seen with S3 Browser, not Cyberduck. And when I create a "folder" with Cyberduck the bucket can't be seen by S3 Browser but can be seen in ECS as a bucket.
thakkd1
1 Rookie
•
13 Posts
0
July 8th, 2015 12:00
Hi Ryan,
Jason Cwik, our resident swift guy, thinks it might be related to /swift that you have in the path in cyberduck. Could you leave that field blank and try again?
Thanks
Dharmesh
ryan_clair
10 Posts
0
July 8th, 2015 13:00
Interesting. I thought you had to specify the namespace you were accessing?
I tried it without specifying a path and I still only see the two buckets I'd created with Cyberduck and not the buckets created by ECS.
JasonCwik
281 Posts
0
July 8th, 2015 15:00
The buckets you create through the ECS console are S3-only buckets. Cross head is not supported yet.
Sent from my iPhone
ryan_clair
10 Posts
0
July 8th, 2015 15:00
Ahh, that would make sense. Except... how do you specify which API the bucket can be accessed by? The only option I see is CAS. Also, when I edit the hi bucket and compare it to the rcc_bucket, I see no difference.
I'd assumed that the port number you come into ECS with (plus the secret) dictates the API (ex: S3 on 9020/9021).