[openstack-dev] [TripleO] a need to assert user ownership in preserved state
Steve Kowalik
steven at wedontsleep.org
Thu Oct 2 02:38:45 UTC 2014
On 02/10/14 12:26, Mike Spreitzer wrote:
> I do not understand the problem statement. Unfortunately, I am not
> familiar with image based updates using TripleO. What is updating what?
> If the UIDs are not asserted, what UIDs shift by one? Is this because
> some files keep owner UID while the some UID=name binding in /etc/passwd
> changes? Or the other way around? Why would there be a change in either?
>
> If there is no short answer, don't worry about it.
You build one image, which creates a 'ceilometer' user with UID 1001,
and deploy that to your cloud.
You then build a new image to deploy to your cloud, and due to element
ordering (or something else), the 'cinder' user now has UID 1001. When
you switch to this image, /mnt/state/var/lib/ceilometer is now owned by
cinder.
Cheers,
--
Steve
If it (dieting) was like a real time strategy game, I'd have loaded a
save game from ten years ago.
- Greg, Columbia Internet
More information about the OpenStack-dev
mailing list