As discussed at our nova meetings, reorganize the juno specs into
- proposed: things proposed which weren't approved
- approved: things we approved but didn't implement
- implemented: things approved and implemented
The first I suspect is the most controversial. I've done this
because I worry about the case where a future developer wants to
pick up something dropped by a previous developer, but has trouble
finding previous proposed specifications on the topic. Note that
the actual proposed specs for Juno are adding in a later commit.
some of the specs are coming in with literal \r characters,
probably from being created in windows notepad. This makes reading
the specs very cumbersome. We should test against these.
Currently, the pagination support for Nova does not allow the caller to
specify the sort order and direction of the data set. This blueprint
enhances the pagination support for the /servers and /servers/detail
APIs so that multiple sort keys and sort directions can be supplied on