PortCheck, a WaitCondition-like Resource
In many cases, we are interested in waiting for a particular service to become available on a newly booted VM. This can currently be achieved by combining WaitConditions with UserData scripts (or an external service) that perform the port checks. It would be much simpler in these scenarios to have a resource that waits for a particular (TCP) port to begin accepting connections.
Blueprint information
- Status:
- Complete
- Approver:
- Angus Salkeld
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Stephen Sugden
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Slow progress
- Milestone target:
- None
- Started by
- Stephen Sugden
- Completed by
- Rico Lin
Whiteboard
https:/
randallburt: While I agree that this seems somewhat reasonable, I worry that we're going down a slippery slope with various tailor-built wait condition implementations. Between this and things like https:/
stephensugden: I've updated this Blueprint to reflect that I'm no longer working on it. Once I realized that heat supports custom resources I didn't feel there was a very compelling reason to push it up into Heat core.
