Ensure that agent calls are persisted on Instance Boot
Xenstore is reloaded on a reboot of the guest. During Windows Boot, if sysprep is ran, the instance is rebooted. This causes the Xenstore to be flushed and drops all configurations that may have initially been injected. The pump would monitor the instance during boot time and ensure the configurations are maintained in the proper xenstore domain until the instance is completely booted
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Antony Messerli
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- Proposed for diablo
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Antony Messerli
Related branches
Related bugs
Sprints
Whiteboard
I can't quite tell without the details of the use-case, but by the sounds of it, this could be achieved more easily by replicating the data to inject into the xapi database using VM.xenstore_data. If it's in here, it will be repopulated when the VM reboots. -- Ewan Mellor.
Ewan, the main use case was for Windows which experiences multiple boots due to sysprep so the agent calls have to carry over to other reboots but not persist once the messages have been consumed by the agent. This has been fixed and merged into trunk now so this blueprint is obsolete. I'll go ahead and close it out. - Antony Messerli
