logging: Remove logging.conf, use log_dir only

Phase 1 of 2. This removes the custom logging configuration and should unblock any debugging efforts.
@craigtracey @paulczar 
For the record, all of this will be moved around in the refactor I have
underway. In fact, the controller role will disappear completely.

One of the objectives of that refactor is to constrain all the resources of
a service within the service's role(s). No more meta roles like
'controller' and 'compute.'
On Oct 25, 2014 10:06 PM, "Paul Czarkowski" <notifications@github.com>
wrote:

> In roles/keystone-common/tasks/main.yml:
>
> >  - name: policy.json
> >    template: src=etc/keystone/policy.json dest=/etc/keystone/policy.json mode=0644
> >    notify:
> >      - restart keystone services
> >
> > +- name: keystone services - start and enable
>
> this isn't needed here and causes errors. keystone service is
> enabled/started as part of the controller role here -
> https://github.com/blueboxgroup/ursula/blob/master/roles/controller/tasks/keystone.yml#L2-L6
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/blueboxgroup/ursula/pull/525/files#r19378591>.
>