Comment 5 for bug 1619282

We should not use common directory already assigned for dedicated service, here it is glance.
If we have limitations with partitioning, and we still want to use one storage partition for glance and swift, I'm proposing to do next:

1st variant:
- create /var/lib/storage and mount it as storage partition
- create /var/lib/storage/glance, symlink it to /var/lib/glance and set proper access permissions
- create /var/lib/storage/swift, symlink it to /var/lib/swift and set proper access permissions

2nd variant:
- add user swift into group glance

Otherwise issue will not disappeared because systemd units are checking permissions in pre start stage.
Example:
# systemctl status glance-registry.service
● glance-registry.service - OpenStack Image Service Registry
   Loaded: loaded (/lib/systemd/system/glance-registry.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2016-09-16 12:02:18 UTC; 1h 10min ago
  Process: 4547 ExecStartPre=/bin/chown glance:adm /var/log/glance (code=exited, status=0/SUCCESS)
  Process: 4343 ExecStartPre=/bin/chown glance:glance /var/lock/glance /var/lib/glance (code=exited, status=0/SUCCESS)
  Process: 4135 ExecStartPre=/bin/mkdir -p /var/lock/glance /var/log/glance /var/lib/glance (code=exited, status=0/SUCCESS)
 Main PID: 4798 (glance-registry)
   CGroup: /system.slice/glance-registry.service