-
-
Save perigrin/1d458d89abc427af20f57f2ba1e8417d to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| │21:35:07 bryan.horstmann-allen | So a customer would be, like, "Samsung Mobile". And everything we do now would be shoved under that Org. │ | |
| │21:35:26 bryan.horstmann-allen | Then when we add JPC, there would be a "Joyent Cloud" customer. And we'd create new datacenters/room/racks for that. │ | |
| │21:35:38 bryan.horstmann-allen | Each org/customer would have its own builds/workspaces/whatever. │ | |
| │- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - │ | |
| │21:35:59 bryan.horstmann-allen | So there's a physical hier of all the assets, and then there are logical views of those assets that have permissions associated with them. │ | |
| │21:36:08 bryan.horstmann-allen | A build is really "just" a workspace with a time range component, in my mind. │ | |
| │21:36:32 bryan.horstmann-allen | And there are other user perms we need to add to facilitate that, but those are minor (I think.) │ | |
| │21:36:39 bryan.horstmann-allen | I really have no idea if I'm helping or not. │ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment