Should store podm info in valence.conf into etcd
Bug #1653158 reported by
Lin Yang
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Valence |
Fix Committed
|
Critical
|
Unassigned | ||
Bug Description
Usually admin will put podm config into valence.conf. Because api allow user to add multiply podm, to make these config consistent, when start valence api, it should store podm conifg in valence.conf into database, and fetch it from database, not valence.conf any more.
| Changed in openstack-valence: | |
| importance: | Undecided → Critical |
| Changed in openstack-valence: | |
| assignee: | nobody → Ananth Narayan S (ananth-narayan) |
| assignee: | Ananth Narayan S (ananth-narayan) → nobody |
| milestone: | none → ocata-1 |
| milestone: | ocata-1 → none |
Revision history for this message
| hubian (hubian) wrote | #1 |
| Changed in openstack-valence: | |
| assignee: | nobody → Ananth Narayan S (ananth-narayan) |
| assignee: | Ananth Narayan S (ananth-narayan) → nobody |
| Changed in openstack-valence: | |
| status: | New → Fix Committed |
To post a comment you must log in.
@Yang Lin
In my opinion that , Valence service could run without any podms in etcd.
And the valence.conf won't stor the podm config properties any more ~
User could send composed request only after admin input podm into valence, and there would be site for admin to input podms.