> having access to the LXD API is basically equivalent (straightforward path) to root on the physical host, so it's something which must be very closely guarded.
FTR, we have an incredibly (painfully) tight firewall there, and the Scalingstack instances are basically throwaway ones -- they run tons of crappy code and thus aren't very reliable (i. e. need to be rebuilt from time to time) anyway. So I think from that point it should be fine. (ATM my main problem isn't performance yet anyway, but keeping LXD alive for more than two or three runs) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1538174 Title: ways to speed up overhead of "lxc exec" on remote containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1538174/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
