Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support resource segregation #66

Open
4 tasks
lorenzo-biava opened this issue Jun 21, 2016 · 1 comment
Open
4 tasks

Support resource segregation #66

lorenzo-biava opened this issue Jun 21, 2016 · 1 comment
Labels
1 priority feature High
Milestone
Next

Comments

@lorenzo-biava
Copy link
Contributor

  • SLAM
  • Chronos (Mesos, Marathon)
  • OneData (space or path?)
  • IM/OpenStack/IaaS provider (TBD!)
@alberto-brigandi alberto-brigandi added this to the 2nd release milestone Jul 29, 2016
@alberto-brigandi
Copy link
Member

alberto-brigandi commented Sep 1, 2016 •
edited
Loading

IM already segregates per user, should we segregate per user too? Or should we segregate per organization?
We also have to keep in mind that the IaaS providers can have different authorization configurations between each others, thus maybe we shouldn't set the deployment status to DELETE_FAILED if the problem is just about missing authorizations

@alberto-brigandi alberto-brigandi modified the milestones: 1.1, 2nd release Sep 1, 2016
@alberto-brigandi alberto-brigandi changed the title Support resource segregation per Virtual Organization Support resource segregation Sep 1, 2016
@alberto-brigandi alberto-brigandi mentioned this issue Sep 1, 2016
Open
@alberto-brigandi alberto-brigandi modified the milestones: 1.2, 1.3 Oct 21, 2016
@alberto-brigandi alberto-brigandi modified the milestones: 1.3, 2.0 Jan 24, 2017
@caifti caifti added the High label Feb 23, 2017
@alberto-brigandi alberto-brigandi modified the milestones: 1.3, Next Apr 5, 2017
@alberto-brigandi alberto-brigandi modified the milestones: Next, 1.5.0 Aug 25, 2017
@alberto-brigandi alberto-brigandi modified the milestones: 1.5.0, Next Nov 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1 priority feature High
Projects
None yet
Milestone
Next
Development

No branches or pull requests
3 participants
@alberto-brigandi @caifti @lorenzo-biava