Bug 806468

Summary:	/etc/stickshift/district.conf should be put under /var
Product:	OKD	Reporter:	Thomas Wiest <twiest>
Component:	Containers	Assignee:	Jhon Honce <jhonce>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	low	Docs Contact:
Priority:	medium
Version:	2.x	CC:	dmcphers, jhonce, mpatel, xtian
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-25 18:26:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Thomas Wiest 2012-03-23 20:45:48 UTC

Description of problem:
/etc/stickshift/district.conf should be put somewhere under /var.

This is runtime data. In talking with Dan, he agreed that it should probably be put somewhere under var.

Version-Release number of selected component (if applicable):
rhc-node-0.88.12-1.el6_2.x86_64

Comment 1 Dan McPherson 2012-03-24 23:30:30 UTC

Mike, got a strong opinion about this one?  Thinking where the best place for this should be.  /var/lib and /var/run don't seem quite right either.  It is configuration but is only really modifiable by the mcollective agent.

Comment 2 Mike McGrath 2012-03-30 16:22:04 UTC

/var/lib is probably the right spot.

Question: We don't config manage this since it's generated.  If a node dies and we lose this information, how do we re-create it?

Comment 3 Dan McPherson 2012-03-30 16:52:39 UTC

It wouldn't be difficult to recreate.  Just needs the district uuid and whether it is active.

Are you thinking /var/lib/stickshift/district.conf ?

Comment 4 Jhon Honce 2012-06-11 17:36:47 UTC

commit 90d2ebde3023471eb533dc460163bb3b1ad82da5 cucumber tests
commit 6590897a899e4807fe2877d7c8ab24dc0cbe8240 code refactor

Comment 5 Jhon Honce 2012-06-12 20:56:48 UTC

File renamed to /var/lib/stickshift/.settings/district.info in place of  /var/lib/stickshift/district.conf.

Comment 6 Jhon Honce 2012-06-12 23:17:43 UTC

li commit 2dca38aba7d1db60212ae9126760f5ec6d37bcf8

Comment 7 Xiaoli Tian 2012-06-14 08:35:04 UTC

Tested it on devenv_1843:
create district
add node to the district and check the following file:
ls  /var/lib/stickshift/.settings/
district.info

Comment 8 Xiaoli Tian 2012-06-14 08:36:41 UTC

[root@ip-10-42-105-73 .settings]# cat district.info 
#Do not modify manually!
uuid='19836ce8172843faa22c75200b2de053'
active='true