, as per the new core team
process
(
https://wiki.openstack.org/wiki/Documentation/HowTo#Achieving_core_reviewer_status
),
and here's what I found:
Current cores not appearing in 30 or 90 day stats:
Alexander Adamov
Bryan D. Payne
Summer Long
Current appearances in 30 or 90 days stats
The quality of container isolation in LXC heavily depends on implementation.
While
pure LXC is generally well-isolated through various mechanisms (for example
AppArmor
in Ubuntu), LXC through libvirt is not. A guest who operates within one
container is
able to affect another containers
Where/when was this wording discussed though ?
It was discussed at the meetings on Jan 24, Jan 31, and Feb 7.
may be a good place for ad-hoc discussions around an issue, I don't really
think it is a good forum for reviewing of these final notices prior to an
The notes are also tracked
The best idea I've heard for a secure windows password
is the following:
a) put a public key on the instance via metadata or config drive (for ease of
use this could actually just be the ssh public key you normally use for
logging into the vm).
b) have a daemon in the windows instance
Data left on broken disks would be unreadable. -- You don't have to worry
about data destruction before selling/throwing out your disks.
I can certainly see the goal here. But this may be harder than you
think. For example, if you encrypt the disk image, then launch the
VM, are you sure that
5 matches
Mail list logo
