FSaaS - File Storage
### Summary For the most demanding use cases, a File Storage service allow all your servers and applications can access to data through shared file system. This is as well the perfect answer to K8s Read/Write-many Persistent Volumes use case. ### Intended Outcome Backend will be Netapp Ontap Single NFS Fileshare using NFSv3 Max size volume : 8 TB Max number of volumes per Public Cloud Project : 1000 Min Volume size : 250 GB Features will be available through OpenStack Manila Standard API: `$ manila endpoints` `$ manila credentials` `$ manila type-list` `$ manila create` `$ manila update` `$ manila list` `$ manila show` `$ manila access-allow` `$ manila access-deny` `$ manila access-list` `$ manila extend` `$ manila shrink` `$ manila share delete` `$ manila snapshot create` `$ manila snapshot-rename` `$ manila snapshot-list` `$ manila snapshot-show` `$ manila snapshot-delete` `$ manila revert-to-snapshot` `$ manila share-instance-export-location-list` `$ manila share-instance-export-location-show` Service will be as well exposed in OVHcloud customer control panel AND Horizon. Performance allocation will be linear, with 4 IOPS per GB provisioned: if a volume is resized performance is updated in consequence. Pricing being worked. ### How will it work Register to the BETA here : https://survey.ovh.com/index.php/988519?lang=en
Posted by JacquesMrz on Nov 25, 2020, 10:16 AM
Tags
Related issues
- Everything is too expensive for European bureaucrats.
- Yeah, the plan is far too expensive for what it provides.
- Crashed demand after one of the big AI labs (probably Anthropic because they focus way too hard on expensive frontier models) become inso...
- /dev/random is much too expensive for this.
- Yeah, this always bugged me.
- A year ago, I had the opinion that it'd be too expensive for developers to support offline mode, peer to peer, or community servers after...
Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments
pricing (Other)
Everything is too expensive for European bureaucrats.
NewYeah, the plan is far too expensive for what it provides.
NewCrashed demand after one of the big AI labs (probably Anthropic because they focus way too hard on expensive frontier models) become inso...
New/dev/random is much too expensive for this.
Yeah, this always bugged me.
A year ago, I had the opinion that it'd be too expensive for developers to support offline mode, peer to peer, or community servers after...
The weird thing about this product is that its biggest competitor is "an old ipad." I feel like most of their target customer base alread...
There's a talk from Travis Kalanick recently on a podcast about this.
FSaaS - File Storage
### Summary For the most demanding use cases, a File Storage service allow all your servers and applications can access to data through shared file system. This is as well the perfect answer to K8s Read/Write-many Persistent Volumes use case. ### Intended Outcome Backend will be Netapp Ontap Single NFS Fileshare using NFSv3 Max size volume : 8 TB Max number of volumes per Public Cloud Project : 1000 Min Volume size : 250 GB Features will be available through OpenStack Manila Standard API: `$ manila endpoints` `$ manila credentials` `$ manila type-list` `$ manila create` `$ manila update` `$ manila list` `$ manila show` `$ manila access-allow` `$ manila access-deny` `$ manila access-list` `$ manila extend` `$ manila shrink` `$ manila share delete` `$ manila snapshot create` `$ manila snapshot-rename` `$ manila snapshot-list` `$ manila snapshot-show` `$ manila snapshot-delete` `$ manila revert-to-snapshot` `$ manila share-instance-export-location-list` `$ manila share-instance-export-location-show` Service will be as well exposed in OVHcloud customer control panel AND Horizon. Performance allocation will be linear, with 4 IOPS per GB provisioned: if a volume is resized performance is updated in consequence. Pricing being worked. ### How will it work Register to the BETA here : https://survey.ovh.com/index.php/988519?lang=en
Comments (0)
No comments yet. Start the discussion.