Bug #835
Must pass wait-for-sync=false to Ganeti when creating DRBD instances
| Status: | Closed | Start date: | 07/15/2011 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | Vangelis Koukis | % Done: | 0% |
|
| Category: | Ganeti | Spent time: | - | |
| Target version: | v0.5.2 |
Description
When synnefo is configured to created drbd instances, the creation stays on a building state for quite a shile esp. when the requested disk size is large. This happens because Ganeti by default goes on and syncs the two disks and this takes several minutes (think 40GB disk over 65MB/s, which is the default limit).
One good tradeoff/workaround may be to tell Ganeti to return before the drbd syncs; this happens by passing wait-for-sync=false to the create instance RAPI call.
Related issues
Associated revisions
Make RAPI CreateInstance() arguments configurable
Make RAPI CreateInstance() arguments deployment-specific.
Add the GANETI_CREATEINSTANCE_KWARGS setting, which allows the administrator
to set arbitrary arguments to RAPI CreateInstance().
Also add initial version of README.Upgrade, detailing
upgrades of Synnefo deployments.
Fixes #835
History
#1 Updated by Vangelis Koukis almost 13 years ago
- Status changed from New to Closed
- Assignee set to Vangelis Koukis
- Priority changed from Medium to High
1c3822471a makes arguments to RAPI CreateInstance() a deployment-specific setting under settings.d/10-backend.conf.
This is a generic solution, both to #785 and #835, allowing the administrator to set any flags necessary for Synnefo VMs to work properly, hopefully without needing any further changes to Synnefo's API implementation.
Important: Ganeti does not honor the wait_for_sync flag over RAPI, patch is provided under contrib/patches.
This has been documented in initial version of README.Upgrade.