Remove 'mount_point' from guestagent RPC calls and CONF
The 'mount_point' parameter in guestagent holds path where volume should be mounted to.
trove.guestagen
But in come occasions its value is taken from CONF rather than from the parameter, see
https:/
https:/
vs
https:/
Moreover, in some occasions the CONF is the only source where the value of the 'mount_point' parameter
can be obtained, see
https:/
It is suggested to remove 'mount_point' from both RPC API calls and Trove configuration files.
When needed, this value should be taken from existing datastorage configuration,
e.g. my.cnf for MyySQL.
Blueprint information
- Status:
- Complete
- Approver:
- Michael Basnight
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Illia Khudoshyn
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Started
- Milestone target:
-
next
- Started by
- Thierry Carrez
- Completed by
- Nikhil Manchanda
Related branches
Sprints
Whiteboard
The only thing that scares me is that we arent versioning the client messages yet. But this is for a create call, so in theory the new instances should have a new guest anyway so its likely not a problem.
Gerrit topic: https:/
Addressed by: https:/
Remove 'mount_point' from guestagent RPC API
Work Items
Dependency tree
* Blueprints in grey have been implemented.
