| 2016-03-28 22:54:44 |
Ron De Rose |
bug |
|
|
added bug |
| 2016-03-28 22:54:56 |
Ron De Rose |
keystone: assignee |
|
Ron De Rose (ronald-de-rose) |
|
| 2016-03-28 22:58:07 |
OpenStack Infra |
keystone: status |
New |
In Progress |
|
| 2016-03-28 23:04:48 |
Ron De Rose |
description |
Remove dependencies where backend code references code in the core. The reasoning being that the core should know about the backends, but the backends should not know anything about the core (separation of concerns). And part of the risk here is a potential for circular dependencies.
For example, identity backends imports identity:
https://github.com/openstack/keystone/blob/master/keystone/identity/backends/sql.py#L24
Backend code could then reference code in the core, as well as other modules inside identity; thus, creating a circular dependency. |
Remove dependencies where backend code references code in the core. For example, identity backends imports identity:
https://github.com/openstack/keystone/blob/master/keystone/identity/backends/sql.py#L24
The reasoning being that the core should know about the backends, but the backends should not know anything about the core (separation of concerns).
And part of the risk here is a potential for circular dependencies. Backend code could then reference code in the core, as well as other higher level modules inside identity; thus, creating a circular dependency. |
|
| 2016-03-28 23:05:16 |
Ron De Rose |
description |
Remove dependencies where backend code references code in the core. For example, identity backends imports identity:
https://github.com/openstack/keystone/blob/master/keystone/identity/backends/sql.py#L24
The reasoning being that the core should know about the backends, but the backends should not know anything about the core (separation of concerns).
And part of the risk here is a potential for circular dependencies. Backend code could then reference code in the core, as well as other higher level modules inside identity; thus, creating a circular dependency. |
Remove dependencies where backend code references code in the core. For example, identity backends imports identity:
https://github.com/openstack/keystone/blob/master/keystone/identity/backends/sql.py#L24
The reasoning being that the core should know about the backends, but the backends should not know anything about the core (separation of concerns).
And part of the risk here is a potential for circular dependencies. Backend code could reference code in the core, as well as other higher level modules inside identity; thus, creating a circular dependency. |
|
| 2016-03-29 13:09:04 |
Brant Knudson |
keystone: status |
In Progress |
Opinion |
|
| 2016-03-29 15:30:41 |
OpenStack Infra |
keystone: status |
Opinion |
In Progress |
|
| 2016-03-29 15:32:50 |
Ron De Rose |
description |
Remove dependencies where backend code references code in the core. For example, identity backends imports identity:
https://github.com/openstack/keystone/blob/master/keystone/identity/backends/sql.py#L24
The reasoning being that the core should know about the backends, but the backends should not know anything about the core (separation of concerns).
And part of the risk here is a potential for circular dependencies. Backend code could reference code in the core, as well as other higher level modules inside identity; thus, creating a circular dependency. |
Remove dependencies where backend code references code in the core. For example, identity backends imports identity:
https://github.com/openstack/keystone/blob/master/keystone/identity/backends/sql.py#L24
The reasoning being that the core should know about the backend interface, but the backends should not know anything about the core (separation of concerns).
And part of the risk here is a potential for circular dependencies. Backend code could reference code in the core, as well as other higher level modules inside identity; thus, creating a circular dependency. |
|
| 2016-04-29 19:26:23 |
OpenStack Infra |
keystone: assignee |
Ron De Rose (ronald-de-rose) |
Brant Knudson (blk-u) |
|
| 2016-05-01 17:39:49 |
Ron De Rose |
keystone: assignee |
Brant Knudson (blk-u) |
Ron De Rose (ronald-de-rose) |
|
| 2016-05-05 07:15:43 |
Steve Martinelli |
keystone: importance |
Undecided |
Medium |
|
| 2016-05-05 07:15:45 |
Steve Martinelli |
keystone: milestone |
|
newton-1 |
|
| 2016-07-07 02:41:01 |
Steve Martinelli |
keystone: milestone |
newton-1 |
newton-2 |
|
| 2016-07-08 15:54:10 |
Lance Bragstad |
description |
Remove dependencies where backend code references code in the core. For example, identity backends imports identity:
https://github.com/openstack/keystone/blob/master/keystone/identity/backends/sql.py#L24
The reasoning being that the core should know about the backend interface, but the backends should not know anything about the core (separation of concerns).
And part of the risk here is a potential for circular dependencies. Backend code could reference code in the core, as well as other higher level modules inside identity; thus, creating a circular dependency. |
Remove dependencies where backend code references code in the core. For example, identity backends imports identity:
https://github.com/openstack/keystone/blob/stable/mitaka/keystone/identity/backends/sql.py#L24
The reasoning being that the core should know about the backend interface, but the backends should not know anything about the core (separation of concerns).
And part of the risk here is a potential for circular dependencies. Backend code could reference code in the core, as well as other higher level modules inside identity; thus, creating a circular dependency. |
|
| 2016-07-08 23:55:08 |
OpenStack Infra |
keystone: status |
In Progress |
Fix Released |
|
