Perhaps we'll switch to uuid project ids in which case naming won't matter as much, but for now we need to document and enforce that project names without punctuation or mixed case.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | aborrero | T296411 cloud: decide on general idea for having cloud-dedicated hardware provide service in the cloud realm & the internet | |||
| Resolved | aborrero | T297596 have cloud hardware servers in the cloud realm using a dedicated LB layer | |||
| Resolved | aborrero | T324992 cloudlb: create PoC on codfw | |||
| Resolved | aborrero | T338937 cloudlb: review swift/radosgw status | |||
| Resolved | Andrew | T341509 radosgw+keystone chokes on projects with '-' in their id | |||
| Resolved | Andrew | T366301 Document and enforce restrictions on openstack project names |
Event Timeline
Comment Actions
Keystone already enforces that new project names be url safe, which is part of the battle here. With the closing of T343158, CamelCase shouldn't matter.