Rename vncterm to xcp-vncterm #2
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Mike McClurg <[email protected]>
Author
|
This pull request depends on the related pull request for vncterm: |
jonludlam
pushed a commit
that referenced
this pull request
May 22, 2014
The read_records_where function in the database layer (used by the get_all_records and get_all_records_where APIs) was reading the database multiple times by calling find_refs_with_filter[1] to get the refs that matched the query and then calling read_record[2] for each of these refs. This violates point #2 of the locking strategy stated at the top of the module that read only functions must only call get_database once to ensure they operate on a consistent snapshot. Since [1] and [2] make get_database calls the get_all_records* functions make n+1 calls to get_database for a table with n records. Because of this, deleting a record during a get_all_records_where will result in a DBCache_NotFound exception with parameter "missing row". This commits adds internal variants of functions [1] and [2] that take an actual instance of Database.t rather than a Db_ref.t which is a Database.t ref ref. Signed-off-by: Si Beaumont <[email protected]>
jonludlam
pushed a commit
that referenced
this pull request
May 28, 2014
The read_records_where function in the database layer (used by the get_all_records and get_all_records_where APIs) was reading the database multiple times by calling find_refs_with_filter[1] to get the refs that matched the query and then calling read_record[2] for each of these refs. This violates point #2 of the locking strategy stated at the top of the module that read only functions must only call get_database once to ensure they operate on a consistent snapshot. Since [1] and [2] make get_database calls the get_all_records* functions make n+1 calls to get_database for a table with n records. Because of this, deleting a record during a get_all_records_where will result in a DBCache_NotFound exception with parameter "missing row". This commits adds internal variants of functions [1] and [2] that take an actual instance of Database.t rather than a Db_ref.t which is a Database.t ref ref. Signed-off-by: Si Beaumont <[email protected]>
jonludlam
pushed a commit
that referenced
this pull request
Sep 8, 2014
1. It's currently possible to make a halted VM, with ha_restart_priority="restart", non-agile. 2. It's not possible to set ha_restart_priority="restart" on a non-agile, halted VM. 3. It's not possible to start a non-agile VM that has ha_restart_priority="restart" 4. It's not possible to make a running VM, with ha_restart_priority="restart", non-agile. 5. It's not possible to set ha_restart_priority="restart" on a non-agile, running VM. Point #1 is inconsistent with point #2 - #2 should be allowed. Signed-off-by: Phus Lu <[email protected]>
jonludlam
pushed a commit
that referenced
this pull request
Sep 11, 2014
…64bit-2 CA-142107 #2: Improve logging around migration script
jonludlam
pushed a commit
that referenced
this pull request
Sep 11, 2014
1. It's currently possible to make a halted VM, with ha_restart_priority="restart", non-agile. 2. It's not possible to set ha_restart_priority="restart" on a non-agile, halted VM. 3. It's not possible to start a non-agile VM that has ha_restart_priority="restart" 4. It's not possible to make a running VM, with ha_restart_priority="restart", non-agile. 5. It's not possible to set ha_restart_priority="restart" on a non-agile, running VM. Point #1 is inconsistent with point #2 - #2 should be allowed. Signed-off-by: Phus Lu <[email protected]>
jonludlam
pushed a commit
that referenced
this pull request
Jan 14, 2015
[RFC]: Add a 'floppy' VBD type (take #2)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make appropriate change to xapi/debian/control
Signed-off-by: Mike McClurg [email protected]