Proposal of Private Stacks ( Stacks for limited users ) (Re: Private Stacks ( Stacks for limited users ))
Thanks for you reply.
This capability seems to be covered by Isolation Segments. You will beable to assign a space to have access to an Isolation Segment where the
“private” stack is available. Other spaces, while able to see the “private”
stack with `cf stacks`, won’t be able to deploy apps to that Isolation
Segment and will have to use the default stack.
We agree that Isolation Segments seems to be able to address similar use
cases. However, as described above, Isolation Segment can not hide
existence of the stack. We think there are cases that users (especially
using stacks that contains proprietary resources, referred in Design
Document) want to hide even existence of their stacks from public.
Private Stack can address such cases.
In addition, Private Stacks allows different stacks to coexist on the same
Cell. For example, cflinuxfs2 and centos can be delivered on in one Cell,
while Private Stacks can provide centos stack for the limited users. This
will contribute reducing both resource cost and management cost because
Isolation Segments requires different cells for each different stack.
2016-11-01 1:42 GMT+09:00 Nicholas Calugar <ncalugar(a)pivotal.io>: