Sharing¶
Share a cluster like a document. Access appears when you share and disappears when you stop.
In RosettaCloud, almost everything you create can be shared with a right-click: with a person, a group, a project or a whole organization, including one at another institution. You do not need to be an administrator, and nobody has to write a policy or exchange credentials.
What you can share¶
| Share | What the other person can do |
|---|---|
| A formation | Launch the same environment for themselves, in their own account and budget |
| A running session | Open the same machine or desktop, to work on it with you |
| An image | Launch machines and desktops from your saved environment |
| Storage | Read or write the same bucket, file system or volume, from their own machines |
| A cluster | Run work on the same Kubernetes, HPC or big data cluster |
| Cloud keys, key pairs, scripts | Use them without seeing the secret behind them |
How access works¶
When you share, RosettaHub issues the recipient temporary credentials for exactly that resource, and revokes them when you stop sharing. A machine in one account, or on one cloud, can then use storage in another, with no IAM work by either side.
- Ownership stays with you. Recipients get access, not ownership, and can clone their own copy.
- Changes flow through. Update a shared formation and recipients see the new version.
- Budgets stay separate. What a recipient launches from your formation or image runs in their account, against their budget.
Common patterns¶
| Pattern | How |
|---|---|
| A course | The teacher shares one formation with the class's organization; every student launches the same lab |
| A research collaboration | A researcher shares data and images with a partner institution, whose members join the same project |
| A team catalogue | Bundle formations and images into a portfolio and share the portfolio |
| Pair work | Share a running session with a colleague for a debugging or teaching session |
More¶
- Sharing on the platform: visibility levels, sharing with portfolios, sharing versus publishing.
- Native resource sharing: sharing resources that already exist in your cloud accounts, such as buckets and machine images.
- Share an image: step by step.