Hello, I'm trying to understand how to work with file system/share resources and how to organize binding between them, client hosts, users, and groups.
I have a block device (a Volume allocated on some StoragePool) which is implicitly allocated before creating filesystem there. First of all, I need a CRUD API to manage lists of named network IP address ranges (subnets). Secondly, I need an API to assign/remove those subnets to a file share so only client hosts with an ip address matching assigned subnets could access the share. Thirdly, I need an API to manage a file share root directory user/groups access control list so only users/groups in this ACL are permitted to access the file share root directory.
-So, when I create filesystem, could I say, that Capacity Source for that is some Volume? Or should it be StoragePool? -Could I use Storage group for binding between a file system/share and subnets? Where will the subnets be in that case? Or should I create some oem StorageFileGroup and use it? -When I want to list or edit subnets, which resource should contain them? Could I create new oem resource Subnet and resource collection SubnetCollection and put it on the Storage level? -How should I organize binding between users, groups and file system/share? And where should these users and groups be located originally? In the account service or somewhere else?