Need to come up with a better strategy for versioning the guest agent's my.cnf
Today, the my.cnf file on the guest agent is pulled down from an apt repository that is set up (by redstack) on the host. This seems overkill just for supporting different flavors. One way would be that we could store configurable, targeted settings somewhere in the database and have the guestagent get them from there.
We need some more discussion around this, before we agree upon a suitable solution.
Blueprint information
- Status:
- Complete
- Approver:
- Michael Basnight
- Priority:
- High
- Drafter:
- Nikhil Manchanda
- Direction:
- Approved
- Assignee:
- Michael Basnight
- Definition:
- Approved
- Series goal:
- Accepted for havana
- Implementation:
-
Implemented
- Milestone target:
-
2013.2
- Started by
- Michael Basnight
- Completed by
- Michael Basnight
Related branches
Related bugs
Sprints
Whiteboard
Id love to see the configuration management code put this in as a feature. seems like its right inline w/ config mgmt. -hub_cap
Gerrit topic: https:/
Addressed by: https:/
Create templated config files
Addressed by: https:/
Removing mycnf static files from contrib.
