On Wed, Aug 27, 2014 at 4:47 AM, Marcus <shadow...@gmail.com> wrote: > We had set up an agent in the VM that listens on the virtio serial port, > similar to how the virtual router gets its configurations now in KVM. Host > to guest communication is an option, and is fairly standardized (qemu guest > agent, VMware tools, xen tools). It takes a little more work to write a > daemon, but you could do a lot more with it. > > I'm not entirely convinced the current design is broken enough to warrant > a redesign (or at least I wouldn't want to see compatibility go away). >
I'm not saying it is broken in any way. I'm just saying that considering the fact that most people already use cloud-init for keys or bootstrapping or whatever, it would be great if we atleast discuss the possibility to somehow provide it with password resets as well. I'm not directly suggesting that we ditch the current way to do password resets either, I don't mind it being there. After all using cloud-init to password reset is currently working, but that you cannot update user-data after vm launch is a limiting factor in ACS. If we had that, which I think we should regardless of passwords, we could easily document how to do it as a first phase thing. -- Erik
