run_instance message in ~17K in size due to duplicated information
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
The RPC call for run_instance includes in its parameters instance, filter_properties, and request_spec. However filter_properties itself includes request_spec, and request_spec included a copy of the instance record as 'instance_
Therefore each run_instance massage in effect includes 3 copies of the instance data and 2 copies of the request_spec
Total size for a single request in DevStack is ~15k, of which at least 60% is replicated data.
Whilst a very small amount of data is examined in the compute manager from filter_properties and request_spec:
filter-properties: 'limits' & 'retry'
request-spec: -security_group'
the main reason for having these structures seems to be so that they can be passed back to the scheduler when a retry is required.
It feels that some simple work in here should be able to reduce the message size significantly.
A formatted print of a typical message captured in DevStack is attached.
| Phil Day (philip-day) wrote | #1 |
| Changed in nova: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Markus Zoeller (markus_z) (mzoeller) wrote Cleanup EOL bug report | #2 |
| Changed in nova: | |
| importance: | Medium → Undecided |
| status: | Confirmed → Expired |
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
Valid example: CONFIRMED FOR: LIBERTY