Need to come up with a better strategy for versioning the guest agent's my.cnf

Registered by Nikhil Manchanda on 2013-01-03

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:
milestone icon 2013.2
Started by
Michael Basnight on 2013-07-08
Completed by
Michael Basnight on 2013-07-16

Related branches

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://review.openstack.org/#q,topic:bp/guestagent-mycnf-versioning,n,z

Addressed by: https://review.openstack.org/35530
    Create templated config files

Addressed by: https://review.openstack.org/41172
    Removing mycnf static files from contrib.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.