You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've experimented a bit with network namespaces on Linux and have been able to arrange for different processes to get different views of http://169.254.169.254.
What I would love is the ability to hologram different programs and shells independently. So I can keep one hologram pointing at one account in one terminal tab, and another hologram at a different account in another terminal tab. Given the network namespace work is done (I can post a sample script if it helps), I think this would be fairly easy.
Ultimately, I think it would make sense to break down the agent as follows:
A component that can serve up an EC2 metadata simulation with credentials supplied somehow (not necessarily hologram server; I have another use case mind which I might elaborate on in another ticket)
A hook for (1) that lets it get its credentials from the Hologram server
A user-facing program (perhaps called inrole or similar) that can set up the network namespaces as needed and spin up a one-off instance of (1) for the namespace.
After that, we can do things like:
inrole account1 role1 /bin/bash inrole account3 role5 aws iam list-account-aliases
And then all the Mac OS users (me included) are sad.
Thoughts?
The text was updated successfully, but these errors were encountered:
I'd prefer to not create a disparity between OS X and Linux users. I really appreciate the research you've done here, but until/unless we figure out how to make it cross-platform I'm not sure it fits in Hologram right now. Is there perhaps something that we can do with pfctl?
That's the issue; I don't think it's possible to emulate on Mac OS, at least at this stage. The pf in Mac OS lets me create rules by UID/GID, but not PID. The only option I could think of on that platform is to create a big pile of dummy users that we can setuid to when running processes, but unfortunately I think that setuid would have other undesirable consequences around file access and other permissions.
At the same time, it seems unfortunate not to offer this functionality (which I have wanted repeatedly in my daily use of hologram) on a platform that can support it.
I've experimented a bit with network namespaces on Linux and have been able to arrange for different processes to get different views of http://169.254.169.254.
What I would love is the ability to hologram different programs and shells independently. So I can keep one hologram pointing at one account in one terminal tab, and another hologram at a different account in another terminal tab. Given the network namespace work is done (I can post a sample script if it helps), I think this would be fairly easy.
Ultimately, I think it would make sense to break down the agent as follows:
inrole
or similar) that can set up the network namespaces as needed and spin up a one-off instance of (1) for the namespace.After that, we can do things like:
inrole account1 role1 /bin/bash
inrole account3 role5 aws iam list-account-aliases
And then all the Mac OS users (me included) are sad.
Thoughts?
The text was updated successfully, but these errors were encountered: