| 1 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
|---|
| 2 | <html xmlns="http://www.w3.org/1999/xhtml"> |
|---|
| 3 | <head> |
|---|
| 4 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> |
|---|
| 5 | <meta http-equiv="Content-Style-Type" content="text/css" /> |
|---|
| 6 | <meta name="generator" content="pandoc" /> |
|---|
| 7 | <title>Ganeti: failures and recovery scenarios</title> |
|---|
| 8 | <style type="text/css">code{white-space: pre;}</style> |
|---|
| 9 | <link href="data:text/css,%2F%2A%0A%20%20%20%20Buttondown%0A%20%20%20%20A%20Markdown%2FMultiMarkdown%2FPandoc%20HTML%20output%20CSS%20stylesheet%0A%20%20%20%20Author%3A%20Ryan%20Gray%0A%20%20%20%20Date%3A%2015%20Feb%202011%0A%20%20%20%20Revised%3A%2021%20Feb%202012%0A%20%20%20%0A%20%20%20%20General%20style%20is%20clean%2C%20with%20minimal%20re%2Ddefinition%20of%20the%20defaults%20or%20%0A%20%20%20%20overrides%20of%20user%20font%20settings%2E%20The%20body%20text%20and%20header%20styles%20are%20%0A%20%20%20%20left%20alone%20except%20title%2C%20author%20and%20date%20classes%20are%20centered%2E%20A%20Pandoc%20TOC%20%0A%20%20%20%20is%20not%20printed%2C%20URLs%20are%20printed%20after%20hyperlinks%20in%20parentheses%2E%20%0A%20%20%20%20Block%20quotes%20are%20italicized%2E%20Tables%20are%20lightly%20styled%20with%20lines%20above%20%0A%20%20%20%20and%20below%20the%20table%20and%20below%20the%20header%20with%20a%20boldface%20header%2E%20Code%20%0A%20%20%20%20blocks%20are%20line%20wrapped%2E%20%0A%20%0A%20%20%20%20All%20elements%20that%20Pandoc%20and%20MultiMarkdown%20use%20should%20be%20listed%20here%2C%20even%20%0A%20%20%20%20if%20the%20style%20is%20empty%20so%20you%20can%20easily%20add%20styling%20to%20anything%2E%0A%20%20%20%20%0A%20%20%20%20There%20are%20some%20elements%20in%20here%20for%20HTML5%20output%20of%20Pandoc%2C%20but%20I%20have%20not%20%0A%20%20%20%20gotten%20around%20to%20testing%20that%20yet%2E%0A%2A%2F%0A%20%0A%2F%2A%20NOTES%3A%0A%20%0A%20%20%20%20Stuff%20tried%20and%20failed%3A%0A%20%20%20%20%0A%20%20%20%20It%20seems%20that%20specifying%20font%2Dfamily%3Aserif%20in%20Safari%20will%20always%20use%20%0A%20%20%20%20Times%20New%20Roman%20rather%20than%20the%20user%27s%20preferences%20setting%2E%0A%20%20%20%20%0A%20%20%20%20Making%20the%20font%20size%20different%20or%20a%20fixed%20value%20for%20print%20in%20case%20the%20screen%20%0A%20%20%20%20font%20size%20is%20making%20the%20print%20font%20too%20big%3A%20Making%20font%2Dsize%20different%20for%20%0A%20%20%20%20print%20than%20for%20screen%20causes%20horizontal%20lines%20to%20disappear%20in%20math%20when%20using%20%0A%20%20%20%20MathJax%20under%20Safari%2E%0A%2A%2F%0A%20%0A%2F%2A%20%2D%2D%2D%2D%20Front%20Matter%20%2D%2D%2D%2D%20%2A%2F%0A%20%0A%2F%2A%20Pandoc%20header%20DIV%2E%20Contains%20%2Etitle%2C%20%2Eauthor%20and%20%2Edate%2E%20Comes%20before%20div%23TOC%2E%20%0A%20%20%20Only%20appears%20if%20one%20of%20those%20three%20are%20in%20the%20document%2E%0A%2A%2F%0A%20%0Adiv%23header%2C%20header%0A%20%20%20%20%7B%0A%20%20%20%20%2F%2A%20Put%20border%20on%20bottom%2E%20Separates%20it%20from%20TOC%20or%20body%20that%20comes%20after%20it%2E%20%2A%2F%0A%20%20%20%20border%2Dbottom%3A%201px%20solid%20%23aaa%3B%0A%20%20%20%20margin%2Dbottom%3A%200%2E5em%3B%0A%20%20%20%20%7D%0A%20%0A%2Etitle%20%2F%2A%20Pandoc%20title%20header%20%28h1%2Etitle%29%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20text%2Dalign%3A%20center%3B%0A%20%20%20%20%7D%0A%20%0A%2Eauthor%2C%20%2Edate%20%2F%2A%20Pandoc%20author%28s%29%20and%20date%20headers%20%28h2%2Eauthor%20and%20h3%2Edate%29%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20text%2Dalign%3A%20center%3B%0A%20%20%20%20%7D%0A%20%0A%2F%2A%20Pandoc%20table%20of%20contents%20DIV%20when%20using%20the%20%2D%2Dtoc%20option%2E%0A%20%20%20NOTE%3A%20this%20doesn%27t%20support%20Pandoc%27s%20%2D%2Did%2Dprefix%20option%20for%20%23TOC%20and%20%23header%2E%20%0A%20%20%20Probably%20would%20need%20to%20use%20div%5Bid%24%3D%27TOC%27%5D%20and%20div%5Bid%24%3D%27header%27%5D%20as%20selectors%2E%0A%2A%2F%0A%20%0Adiv%23TOC%2C%20nav%23TOC%0A%20%20%20%20%7B%0A%20%20%20%20%2F%2A%20Put%20border%20on%20bottom%20to%20separate%20it%20from%20body%2E%20%2A%2F%0A%20%20%20%20border%2Dbottom%3A%201px%20solid%20%23aaa%3B%0A%20%20%20%20margin%2Dbottom%3A%200%2E5em%3B%0A%20%20%20%20%7D%0A%20%0A%40media%20print%0A%20%20%20%20%7B%0A%20%20%20%20div%23TOC%2C%20nav%23TOC%0A%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%2F%2A%20Don%27t%20display%20TOC%20in%20print%20%2A%2F%0A%20%20%20%20%20%20%20%20display%3A%20none%3B%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%0A%2F%2A%20%2D%2D%2D%2D%20Headers%20and%20sections%20%2D%2D%2D%2D%20%2A%2F%0A%20%0Ah1%2C%20h2%2C%20h3%2C%20h4%2C%20h5%2C%20h6%0A%7B%0A%20%20%20%20font%2Dfamily%3A%20%22Helvetica%20Neue%22%2C%20Helvetica%2C%20%22Liberation%20Sans%22%2C%20Calibri%2C%20Arial%2C%20sans%2Dserif%3B%20%2F%2A%20Sans%2Dserif%20headers%20%2A%2F%0A%20%0A%20%20%20%20%2F%2A%20font%2Dfamily%3A%20%22Liberation%20Serif%22%2C%20%22Georgia%22%2C%20%22Times%20New%20Roman%22%2C%20serif%3B%20%2F%2A%20Serif%20headers%20%2A%2F%0A%20%0A%20%20%20%20page%2Dbreak%2Dafter%3A%20avoid%3B%20%2F%2A%20Firefox%2C%20Chrome%2C%20and%20Safari%20do%20not%20support%20the%20property%20value%20%22avoid%22%20%2A%2F%0A%7D%0A%20%0A%2F%2A%20Pandoc%20with%20%2D%2Dsection%2Ddivs%20option%20%2A%2F%0A%20%0Adiv%20div%2C%20section%20section%20%2F%2A%20Nested%20sections%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20margin%2Dleft%3A%202em%3B%20%2F%2A%20This%20will%20increasingly%20indent%20nested%20header%20sections%20%2A%2F%0A%20%20%20%20%7D%0A%20%0Ap%20%7B%7D%0A%20%0Ablockquote%0A%20%20%20%20%7B%20%0A%20%20%20%20font%2Dstyle%3A%20italic%3B%0A%20%20%20%20%7D%0A%20%0Ali%20%2F%2A%20All%20list%20items%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%0A%20%0Ali%20%3E%20p%20%2F%2A%20Loosely%20spaced%20list%20item%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20margin%2Dtop%3A%201em%3B%20%2F%2A%20IE%3A%20lack%20of%20space%20above%20a%20%3Cli%3E%20when%20the%20item%20is%20inside%20a%20%3Cp%3E%20%2A%2F%0A%20%20%20%20%7D%0A%20%0Aul%20%2F%2A%20Whole%20unordered%20list%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%0A%20%0Aul%20li%20%2F%2A%20Unordered%20list%20item%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%0A%20%0Aol%20%2F%2A%20Whole%20ordered%20list%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%0A%20%0Aol%20li%20%2F%2A%20Ordered%20list%20item%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%0A%20%0Ahr%20%7B%7D%0A%20%0A%2F%2A%20%2D%2D%2D%2D%20Some%20span%20elements%20%2D%2D%2D%20%2A%2F%0A%20%0Asub%20%2F%2A%20Subscripts%2E%20Pandoc%3A%20H%7E2%7EO%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%0A%20%0Asup%20%2F%2A%20Superscripts%2E%20Pandoc%3A%20The%202%5End%5E%20try%2E%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%0A%20%20%20%20%0Aem%20%2F%2A%20Emphasis%2E%20Markdown%3A%20%2Aemphasis%2A%20or%20%5Femphasis%5F%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%0A%20%20%20%20%0Aem%20%3E%20em%20%2F%2A%20Emphasis%20within%20emphasis%3A%20%2AThis%20is%20all%20%2Aemphasized%2A%20except%20that%2A%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20font%2Dstyle%3A%20normal%3B%0A%20%20%20%20%7D%0A%20%0Astrong%20%2F%2A%20Markdown%20%2A%2Astrong%2A%2A%20or%20%5F%5Fstrong%5F%5F%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%0A%20%0A%2F%2A%20%2D%2D%2D%2D%20Links%20%28anchors%29%20%2D%2D%2D%2D%20%2A%2F%0A%20%0Aa%20%2F%2A%20All%20links%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%2F%2A%20Keep%20links%20clean%2E%20On%20screen%2C%20they%20are%20colored%3B%20in%20print%2C%20they%20do%20nothing%20anyway%2E%20%2A%2F%0A%20%20%20%20text%2Ddecoration%3A%20none%3B%0A%20%20%20%20%7D%0A%20%0A%40media%20screen%0A%20%20%20%20%7B%0A%20%20%20%20a%3Ahover%0A%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%2F%2A%20On%20hover%2C%20we%20indicate%20a%20bit%20more%20that%20it%20is%20a%20link%2E%20%2A%2F%0A%20%20%20%20%20%20%20%20text%2Ddecoration%3A%20underline%3B%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%0A%40media%20print%0A%20%20%20%20%7B%0A%20%20%20%20a%20%20%20%7B%0A%20%20%20%20%20%20%20%20%2F%2A%20In%20print%2C%20a%20colored%20link%20is%20useless%2C%20so%20un%2Dstyle%20it%2E%20%2A%2F%0A%20%20%20%20%20%20%20%20color%3A%20black%3B%0A%20%20%20%20%20%20%20%20background%3A%20transparent%3B%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%0A%20%20%20%20a%5Bhref%5E%3D%22http%3A%2F%2F%22%5D%3Aafter%2C%20a%5Bhref%5E%3D%22https%3A%2F%2F%22%5D%3Aafter%0A%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%2F%2A%20However%2C%20links%20that%20go%20somewhere%20else%2C%20might%20be%20useful%20to%20the%20reader%2C%0A%20%20%20%20%20%20%20%20%20%20%20so%20for%20http%20and%20https%20links%2C%20print%20the%20URL%20after%20what%20was%20the%20link%20%0A%20%20%20%20%20%20%20%20%20%20%20text%20in%20parens%0A%20%20%20%20%20%20%20%20%2A%2F%0A%20%20%20%20%20%20%20%20content%3A%20%22%20%28%22%20attr%28href%29%20%22%29%20%22%3B%0A%20%20%20%20%20%20%20%20font%2Dsize%3A%2090%25%3B%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%0A%2F%2A%20%2D%2D%2D%2D%20Images%20%2D%2D%2D%2D%20%2A%2F%0A%20%0Aimg%0A%20%20%20%20%7B%0A%20%20%20%20%2F%2A%20Let%20it%20be%20inline%20left%2Fright%20where%20it%20wants%20to%20be%2C%20but%20verticality%20make%20%0A%20%20%20%20%20%20%20it%20in%20the%20middle%20to%20look%20nicer%2C%20but%20opinions%20differ%2C%20and%20if%20in%20a%20multi%2Dline%20%0A%20%20%20%20%20%20%20paragraph%2C%20it%20might%20not%20be%20so%20great%2E%20%0A%20%20%20%20%2A%2F%0A%20%20%20%20vertical%2Dalign%3A%20middle%3B%0A%20%20%20%20%7D%0A%20%0Adiv%2Efigure%20%2F%2A%20Pandoc%20figure%2Dstyle%20image%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%2F%2A%20Center%20the%20image%20and%20caption%20%2A%2F%0A%20%20%20%20margin%2Dleft%3A%20auto%3B%0A%20%20%20%20margin%2Dright%3A%20auto%3B%0A%20%20%20%20text%2Dalign%3A%20center%3B%0A%20%20%20%20font%2Dstyle%3A%20italic%3B%0A%20%20%20%20%7D%0A%20%0Ap%2Ecaption%20%2F%2A%20Pandoc%20figure%2Dstyle%20caption%20within%20div%2Efigure%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%2F%2A%20Inherits%20div%2Efigure%20props%20by%20default%20%2A%2F%0A%20%20%20%20%7D%0A%20%0A%2F%2A%20%2D%2D%2D%2D%20Code%20blocks%20and%20spans%20%2D%2D%2D%2D%20%2A%2F%0A%20%0Apre%2C%20code%20%0A%20%20%20%20%7B%0A%20%20%20%20background%2Dcolor%3A%20%23fdf7ee%3B%0A%20%20%20%20%2F%2A%20BEGIN%20word%20wrap%20%2A%2F%0A%20%20%20%20%2F%2A%20Need%20all%20the%20following%20to%20word%20wrap%20instead%20of%20scroll%20box%20%2A%2F%0A%20%20%20%20%2F%2A%20This%20will%20override%20the%20overflow%3Aauto%20if%20present%20%2A%2F%0A%20%20%20%20white%2Dspace%3A%20pre%2Dwrap%3B%20%2F%2A%20css%2D3%20%2A%2F%0A%20%20%20%20white%2Dspace%3A%20%2Dmoz%2Dpre%2Dwrap%20%21important%3B%20%2F%2A%20Mozilla%2C%20since%201999%20%2A%2F%0A%20%20%20%20white%2Dspace%3A%20%2Dpre%2Dwrap%3B%20%2F%2A%20Opera%204%2D6%20%2A%2F%0A%20%20%20%20white%2Dspace%3A%20%2Do%2Dpre%2Dwrap%3B%20%2F%2A%20Opera%207%20%2A%2F%0A%20%20%20%20word%2Dwrap%3A%20break%2Dword%3B%20%2F%2A%20Internet%20Explorer%205%2E5%2B%20%2A%2F%0A%20%20%20%20%2F%2A%20END%20word%20wrap%20%2A%2F%0A%20%20%20%20%7D%0A%20%0Apre%20%2F%2A%20Code%20blocks%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%2F%2A%20Distinguish%20pre%20blocks%20from%20other%20text%20by%20more%20than%20the%20font%20with%20a%20background%20tint%2E%20%2A%2F%0A%20%20%20%20padding%3A%200%2E5em%3B%20%2F%2A%20Since%20we%20have%20a%20background%20color%20%2A%2F%0A%20%20%20%20border%2Dradius%3A%205px%3B%20%2F%2A%20Softens%20it%20%2A%2F%0A%20%20%20%20%2F%2A%20Give%20it%20a%20some%20definition%20%2A%2F%0A%20%20%20%20border%3A%201px%20solid%20%23aaa%3B%0A%20%20%20%20%2F%2A%20Set%20it%20off%20left%20and%20right%2C%20seems%20to%20look%20a%20bit%20nicer%20when%20we%20have%20a%20background%20%2A%2F%0A%20%20%20%20margin%2Dleft%3A%20%200%2E5em%3B%0A%20%20%20%20margin%2Dright%3A%200%2E5em%3B%0A%20%20%20%20%7D%0A%20%0A%40media%20screen%0A%20%20%20%20%7B%0A%20%20%20%20pre%0A%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%2F%2A%20On%20screen%2C%20use%20an%20auto%20scroll%20box%20for%20long%20lines%2C%20unless%20word%2Dwrap%20is%20enabled%20%2A%2F%0A%20%20%20%20%20%20%20%20white%2Dspace%3A%20pre%3B%0A%20%20%20%20%20%20%20%20overflow%3A%20auto%3B%0A%20%20%20%20%20%20%20%20%2F%2A%20Dotted%20looks%20better%20on%20screen%20and%20solid%20seems%20to%20print%20better%2E%20%2A%2F%0A%20%20%20%20%20%20%20%20border%3A%201px%20dotted%20%23777%3B%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%0Acode%20%2F%2A%20All%20inline%20code%20spans%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%0A%20%0Ap%20%3E%20code%2C%20li%20%3E%20code%20%2F%2A%20Code%20spans%20in%20paragraphs%20and%20tight%20lists%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%2F%2A%20Pad%20a%20little%20from%20adjacent%20text%20%2A%2F%0A%20%20%20%20padding%2Dleft%3A%20%202px%3B%0A%20%20%20%20padding%2Dright%3A%202px%3B%0A%20%20%20%20%7D%0A%20%20%20%20%0Ali%20%3E%20p%20code%20%2F%2A%20Code%20span%20in%20a%20loose%20list%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%2F%2A%20We%20have%20room%20for%20some%20more%20background%20color%20above%20and%20below%20%2A%2F%0A%20%20%20%20padding%3A%202px%3B%0A%20%20%20%20%7D%0A%20%0A%2F%2A%20%2D%2D%2D%2D%20Math%20%2D%2D%2D%2D%20%2A%2F%0A%20%0Aspan%2Emath%20%2F%2A%20Pandoc%20inline%20math%20default%20and%20%2D%2Djsmath%20inline%20math%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%2F%2A%20Tried%20font%2Dstyle%3Aitalic%20here%2C%20and%20it%20messed%20up%20MathJax%20rendering%20in%20some%20browsers%2E%20Maybe%20don%27t%20mess%20with%20at%20all%2E%20%2A%2F%0A%20%20%20%20%7D%0A%20%20%20%20%0Adiv%2Emath%20%2F%2A%20Pandoc%20%2D%2Djsmath%20display%20math%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%0A%20%20%20%20%0Aspan%2ELaTeX%20%2F%2A%20Pandoc%20%2D%2Dlatexmathml%20math%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%20%0A%20%0Aeq%20%2F%2A%20Pandoc%20%2D%2Dgladtex%20math%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%20%0A%20%0A%2F%2A%20%2D%2D%2D%2D%20Tables%20%2D%2D%2D%2D%20%2A%2F%0A%20%0A%2F%2A%20%20A%20clean%20textbook%2Dlike%20style%20with%20horizontal%20lines%20above%20and%20below%20and%20under%20%0A%20%20%20%20the%20header%2E%20Rows%20highlight%20on%20hover%20to%20help%20scanning%20the%20table%20on%20screen%2E%0A%2A%2F%0A%20%0Atable%0A%20%20%20%20%7B%0A%20%20%20%20border%2Dcollapse%3A%20collapse%3B%0A%20%20%20%20border%2Dspacing%3A%200%3B%20%2F%2A%20IE%206%20%2A%2F%0A%20%0A%20%20%20%20border%2Dbottom%3A%202pt%20solid%20%23000%3B%0A%20%20%20%20border%2Dtop%3A%202pt%20solid%20%23000%3B%20%2F%2A%20The%20caption%20on%20top%20will%20not%20have%20a%20bottom%2Dborder%20%2A%2F%0A%20%0A%20%20%20%20%2F%2A%20Center%20%2A%2F%0A%20%20%20%20margin%2Dleft%3A%20auto%3B%0A%20%20%20%20margin%2Dright%3A%20auto%3B%0A%20%20%20%20%7D%0A%20%20%20%20%0Athead%20%2F%2A%20Entire%20table%20header%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20border%2Dbottom%3A%201pt%20solid%20%23000%3B%0A%20%20%20%20background%2Dcolor%3A%20%23eee%3B%20%2F%2A%20Does%20this%20BG%20print%20well%3F%20%2A%2F%0A%20%20%20%20%7D%0A%20%0Atr%2Eheader%20%2F%2A%20Each%20header%20row%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%20%0A%20%0Atbody%20%2F%2A%20Entire%20table%20%20body%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%0A%20%0A%2F%2A%20Table%20body%20rows%20%2A%2F%0A%20%0Atr%20%20%7B%0A%20%20%20%20%7D%0Atr%2Eodd%3Ahover%2C%20tr%2Eeven%3Ahover%20%2F%2A%20Use%20%2Eodd%20and%20%2Eeven%20classes%20to%20avoid%20styling%20rows%20in%20other%20tables%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20background%2Dcolor%3A%20%23eee%3B%0A%20%20%20%20%7D%0A%20%20%20%20%0A%2F%2A%20Odd%20and%20even%20rows%20%2A%2F%0Atr%2Eodd%20%7B%7D%0Atr%2Eeven%20%7B%7D%0A%20%0Atd%2C%20th%20%2F%2A%20Table%20cells%20and%20table%20header%20cells%20%2A%2F%0A%20%20%20%20%7B%20%0A%20%20%20%20vertical%2Dalign%3A%20top%3B%20%2F%2A%20Word%20%2A%2F%0A%20%20%20%20vertical%2Dalign%3A%20baseline%3B%20%2F%2A%20Others%20%2A%2F%0A%20%20%20%20padding%2Dleft%3A%20%20%200%2E5em%3B%0A%20%20%20%20padding%2Dright%3A%20%200%2E5em%3B%0A%20%20%20%20padding%2Dtop%3A%20%20%20%200%2E2em%3B%0A%20%20%20%20padding%2Dbottom%3A%200%2E2em%3B%0A%20%20%20%20%7D%0A%20%20%20%20%0A%2F%2A%20Removes%20padding%20on%20left%20and%20right%20of%20table%20for%20a%20tight%20look%2E%20Good%20if%20thead%20has%20no%20background%20color%2A%2F%0A%2F%2A%0Atr%20td%3Alast%2Dchild%2C%20tr%20th%3Alast%2Dchild%0A%20%20%20%20%7B%0A%20%20%20%20padding%2Dright%3A%200%3B%0A%20%20%20%20%7D%0Atr%20td%3Afirst%2Dchild%2C%20tr%20th%3Afirst%2Dchild%20%0A%20%20%20%20%7B%0A%20%20%20%20padding%2Dleft%3A%200%3B%0A%20%20%20%20%7D%0A%2A%2F%0A%20%0Ath%20%2F%2A%20Table%20header%20cells%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20font%2Dweight%3A%20bold%3B%20%0A%20%20%20%20%7D%0A%20%0Atfoot%20%2F%2A%20Table%20footer%20%28what%20appears%20here%20if%20caption%20is%20on%20top%3F%29%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%0A%20%0Acaption%20%2F%2A%20This%20is%20for%20a%20table%20caption%20tag%2C%20not%20the%20p%2Ecaption%20Pandoc%20uses%20in%20a%20div%2Efigure%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20caption%2Dside%3A%20top%3B%0A%20%20%20%20border%3A%20none%3B%0A%20%20%20%20font%2Dsize%3A%200%2E9em%3B%0A%20%20%20%20font%2Dstyle%3A%20italic%3B%0A%20%20%20%20text%2Dalign%3A%20center%3B%0A%20%20%20%20margin%2Dbottom%3A%200%2E3em%3B%20%2F%2A%20Good%20for%20when%20on%20top%20%2A%2F%0A%20%20%20%20padding%2Dbottom%3A%200%2E2em%3B%0A%20%20%20%20%7D%0A%20%0A%2F%2A%20%2D%2D%2D%2D%20Definition%20lists%20%2D%2D%2D%2D%20%2A%2F%0A%20%0Adl%20%2F%2A%20The%20whole%20list%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20border%2Dtop%3A%202pt%20solid%20black%3B%0A%20%20%20%20padding%2Dtop%3A%200%2E5em%3B%0A%20%20%20%20border%2Dbottom%3A%202pt%20solid%20black%3B%0A%20%20%20%20%7D%0A%20%0Adt%20%2F%2A%20Definition%20term%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20font%2Dweight%3A%20bold%3B%0A%20%20%20%20%7D%0A%20%0Add%2Bdt%20%2F%2A%202nd%20or%20greater%20term%20in%20the%20list%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20border%2Dtop%3A%201pt%20solid%20black%3B%0A%20%20%20%20padding%2Dtop%3A%200%2E5em%3B%0A%20%20%20%20%7D%0A%20%20%20%20%0Add%20%2F%2A%20A%20definition%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20margin%2Dbottom%3A%200%2E5em%3B%0A%20%20%20%20%7D%0A%20%0Add%2Bdd%20%2F%2A%202nd%20or%20greater%20definition%20of%20a%20term%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20border%2Dtop%3A%201px%20solid%20black%3B%20%2F%2A%20To%20separate%20multiple%20definitions%20%2A%2F%0A%20%20%20%20%7D%0A%20%20%20%20%0A%2F%2A%20%2D%2D%2D%2D%20Footnotes%20%2D%2D%2D%2D%20%2A%2F%0A%20%0Aa%2Efootnote%2C%20a%2EfootnoteRef%20%7B%20%2F%2A%20Pandoc%2C%20MultiMarkdown%20footnote%20links%20%2A%2F%0A%20%20%20%20font%2Dsize%3A%20small%3B%20%0A%20%20%20%20vertical%2Dalign%3A%20text%2Dtop%3B%0A%7D%0A%20%0Aa%5Bhref%5E%3D%22%23fnref%22%5D%2C%20a%2Ereversefootnote%20%2F%2A%20Pandoc%2C%20MultiMarkdown%2C%20%3F%3F%20footnote%20back%20links%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%0A%20%0A%40media%20print%0A%20%20%20%20%7B%0A%20%20%20%20a%5Bhref%5E%3D%22%23fnref%22%5D%2C%20a%2Ereversefootnote%20%2F%2A%20Pandoc%2C%20MultiMarkdown%20%2A%2F%0A%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%2F%2A%20Don%27t%20display%20these%20at%20all%20in%20print%20since%20the%20arrow%20is%20only%20something%20to%20click%20on%20%2A%2F%0A%20%20%20%20%20%20%20%20display%3A%20none%3B%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%20%20%20%0Adiv%2Efootnotes%20%2F%2A%20Pandoc%20footnotes%20div%20at%20end%20of%20the%20document%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%0A%20%20%20%20%0Adiv%2Efootnotes%20li%5Bid%5E%3D%22fn%22%5D%20%2F%2A%20A%20footnote%20item%20within%20that%20div%20%2A%2F%0A%20%20%20%20%7B%0A%20%20%20%20%7D%0A%20%0A%2F%2A%20You%20can%20class%20stuff%20as%20%22noprint%22%20to%20not%20print%2E%20%0A%20%20%20Useful%20since%20you%20can%27t%20set%20this%20media%20conditional%20inside%20an%20HTML%20element%27s%20%0A%20%20%20style%20attribute%20%28I%20think%29%2C%20and%20you%20don%27t%20want%20to%20make%20another%20stylesheet%20that%20%0A%20%20%20imports%20this%20one%20and%20adds%20a%20class%20just%20to%20do%20this%2E%0A%2A%2F%0A%20%0A%40media%20print%0A%20%20%20%20%7B%0A%20%20%20%20%2Enoprint%0A%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20display%3Anone%3B%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A" rel="stylesheet" type="text/css" /> |
|---|
| 10 | </head> |
|---|
| 11 | <body> |
|---|
| 12 | <div id="header"> |
|---|
| 13 | <h1 class="title">Ganeti: failures and recovery scenarios</h1> |
|---|
| 14 | </div> |
|---|
| 15 | <div id="TOC"> |
|---|
| 16 | <ul> |
|---|
| 17 | <li><a href="#initial-setup"><span class="toc-section-number">1</span> Initial setup</a></li> |
|---|
| 18 | <li><a href="#scenario-planned-node-maintenance"><span class="toc-section-number">2</span> Scenario: Planned Node Maintenance</a><ul> |
|---|
| 19 | <li><a href="#step-1-migrate-primary-instances-away-from-hostb"><span class="toc-section-number">2.1</span> Step 1: Migrate primary instances away from hostB</a></li> |
|---|
| 20 | <li><a href="#step-2-move-secondary-instances-disks-on-hostb-to-another-host"><span class="toc-section-number">2.2</span> Step 2: Move secondary instances' disks on hostB to another host</a></li> |
|---|
| 21 | <li><a href="#step-3-move-plain-instances-away-from-hostb-to-another-host."><span class="toc-section-number">2.3</span> Step 3: Move plain instances away from hostB to another host.</a></li> |
|---|
| 22 | </ul></li> |
|---|
| 23 | <li><a href="#scenario-loss-of-a-slave-node"><span class="toc-section-number">3</span> Scenario: Loss of a Slave Node</a><ul> |
|---|
| 24 | <li><a href="#initial-state"><span class="toc-section-number">3.1</span> Initial state</a><ul> |
|---|
| 25 | <li><a href="#instance-recovery"><span class="toc-section-number">3.1.1</span> Instance recovery</a></li> |
|---|
| 26 | <li><a href="#re-adding-the-failed-node"><span class="toc-section-number">3.1.2</span> Re-adding the failed node</a></li> |
|---|
| 27 | </ul></li> |
|---|
| 28 | <li><a href="#completely-removing-hostb-from-the-cluster"><span class="toc-section-number">3.2</span> Completely removing hostB from the cluster</a></li> |
|---|
| 29 | </ul></li> |
|---|
| 30 | <li><a href="#scenario-planned-master-failover-node-maintenance"><span class="toc-section-number">4</span> Scenario: Planned master failover (node maintenance)</a></li> |
|---|
| 31 | <li><a href="#scenario-loss-of-master-node"><span class="toc-section-number">5</span> Scenario: Loss of Master Node</a><ul> |
|---|
| 32 | <li><a href="#promoting-slave"><span class="toc-section-number">5.1</span> Promoting slave</a></li> |
|---|
| 33 | </ul></li> |
|---|
| 34 | <li><a href="#some-key-commands"><span class="toc-section-number">6</span> Some key commands</a><ul> |
|---|
| 35 | <li><a href="#moving-all-instances-away-from-a-node"><span class="toc-section-number">6.1</span> Moving all instances away from a node</a></li> |
|---|
| 36 | <li><a href="#making-a-node-online-after-it-has-been-marked-as-offline"><span class="toc-section-number">6.2</span> Making a node online after it has been marked as offline</a></li> |
|---|
| 37 | </ul></li> |
|---|
| 38 | </ul> |
|---|
| 39 | </div> |
|---|
| 40 | <p>TODO: replace host -> node</p> |
|---|
| 41 | <p>We are going to simulate a number of failure situations, and recover from them.</p> |
|---|
| 42 | <p>Try and replicate the scenarios on your hosts.</p> |
|---|
| 43 | <h1 id="initial-setup"><a href="#initial-setup"><span class="header-section-number">1</span> Initial setup</a></h1> |
|---|
| 44 | <ul> |
|---|
| 45 | <li>Cluster with 3 or more Nodes</li> |
|---|
| 46 | <li>Master is up (hostA)</li> |
|---|
| 47 | <li>Slaves are up (hostB, hostC, etc.)</li> |
|---|
| 48 | <li>DRBD instance "debianX" (dX) is primary on hostA, secondary on hostB</li> |
|---|
| 49 | <li>DRBD instance "debianZ" (dY) is primary on hostB, secondary on hostC</li> |
|---|
| 50 | <li>Plain instance "debianY" (dZ) is on host B</li> |
|---|
| 51 | </ul> |
|---|
| 52 | <pre><code> host A host B host C |
|---|
| 53 | (master) |
|---|
| 54 | +-----------------+ +-----------------+ +-----------------+ |
|---|
| 55 | | | | | | | |
|---|
| 56 | | +====+ | drbd | ...... +====+ | drbd | ...... | |
|---|
| 57 | | | dX |.....................: dX : | dY |............: dY : | |
|---|
| 58 | | +====+ | | :....: +====+ | | :....: | |
|---|
| 59 | | | | | | | |
|---|
| 60 | | | | +----+ | | | |
|---|
| 61 | | | | plain | dZ | | | | |
|---|
| 62 | | | | +----+ | | | |
|---|
| 63 | +--------+--------+ +-------+---------+ +-------+---------+ |
|---|
| 64 | | | | |
|---|
| 65 | -----------+-------------------------+--------------------------+-----------</code></pre> |
|---|
| 66 | <h1 id="scenario-planned-node-maintenance"><a href="#scenario-planned-node-maintenance"><span class="header-section-number">2</span> Scenario: Planned Node Maintenance</a></h1> |
|---|
| 67 | <p>Let's imagine that we want to take down hostB for maintenance: more RAM, a disk replacement, etc.</p> |
|---|
| 68 | <p>You have probably many instances running on your cluster by now.</p> |
|---|
| 69 | <ul> |
|---|
| 70 | <li><p>We need to make sure hostB is not hosting any instances, primary, secondary or plain</p></li> |
|---|
| 71 | <li><p>We can use hostC and hostA to move instances away from hostB</p></li> |
|---|
| 72 | </ul> |
|---|
| 73 | <p>Here's the process:</p> |
|---|
| 74 | <ol style="list-style-type: decimal"> |
|---|
| 75 | <li><p>DRBD instances for which hostB is primary will need to migrate to their secondary, leaving hostB to only be secondary for any instances</p></li> |
|---|
| 76 | <li><p>We need to move the disks of secondary DRBD instances from hostB to another host.</p></li> |
|---|
| 77 | </ol> |
|---|
| 78 | <p>(if A is primary for debianX, we move its secondary disks from B to C)</p> |
|---|
| 79 | <ol start="3" style="list-style-type: decimal"> |
|---|
| 80 | <li>Plain instances running on hostB will need to be moved to another node (A or C)</li> |
|---|
| 81 | </ol> |
|---|
| 82 | <p>Below are the commands we'll be using for each of the steps above.</p> |
|---|
| 83 | <h2 id="step-1-migrate-primary-instances-away-from-hostb"><a href="#step-1-migrate-primary-instances-away-from-hostb"><span class="header-section-number">2.1</span> Step 1: Migrate primary instances away from hostB</a></h2> |
|---|
| 84 | <p>command: <code>gnt-instance migrate</code></p> |
|---|
| 85 | <p>We've used this command before - we have to make sure that if hostB is primary for any instances, we migrate them to the secondary node.</p> |
|---|
| 86 | <p>In the example above, hostB is primary for <code>dY</code>. Let's migrate it over to hostC.</p> |
|---|
| 87 | <pre><code># gnt-instance migrate dY</code></pre> |
|---|
| 88 | <p>After this is done, we are now in the following situation: hostB is only running the plain instance <code>dZ</code>.</p> |
|---|
| 89 | <pre><code> host A host B host C |
|---|
| 90 | (master) |
|---|
| 91 | +-----------------+ +-----------------+ +-----------------+ |
|---|
| 92 | | | | | | | |
|---|
| 93 | | +====+ | drbd | ...... ...... | drbd | +====+ | |
|---|
| 94 | | | dX |.....................: dX : : dY :............| dY | | |
|---|
| 95 | | +====+ | | :....: :....: | | +====+ | |
|---|
| 96 | | | | | | | |
|---|
| 97 | | | | +----+ | | | |
|---|
| 98 | | | | plain | dZ | | | | |
|---|
| 99 | | | | +----+ | | | |
|---|
| 100 | +--------+--------+ +-------+---------+ +-------+---------+ |
|---|
| 101 | | | | |
|---|
| 102 | -----------+-------------------------+--------------------------+-----------</code></pre> |
|---|
| 103 | <h2 id="step-2-move-secondary-instances-disks-on-hostb-to-another-host"><a href="#step-2-move-secondary-instances-disks-on-hostb-to-another-host"><span class="header-section-number">2.2</span> Step 2: Move secondary instances' disks on hostB to another host</a></h2> |
|---|
| 104 | <p>command: <code>gnt-instance replace-disks</code></p> |
|---|
| 105 | <pre><code># gnt-instance replace-disks XXX</code></pre> |
|---|
| 106 | <p>XXX example replace-disks for dX and dZ</p> |
|---|
| 107 | <h2 id="step-3-move-plain-instances-away-from-hostb-to-another-host."><a href="#step-3-move-plain-instances-away-from-hostb-to-another-host."><span class="header-section-number">2.3</span> Step 3: Move plain instances away from hostB to another host.</a></h2> |
|---|
| 108 | <p>command: <code>gnt-instance move</code></p> |
|---|
| 109 | <p>Note that this will require shutting down the instance, as its disk(s) will first have to be copied to host C before it can be restarted there.</p> |
|---|
| 110 | <pre><code># gnt-instance move -n hostC debianY |
|---|
| 111 | |
|---|
| 112 | Instance debianY will be moved. This requires a shutdown of the instance. |
|---|
| 113 | Continue? |
|---|
| 114 | y/[n]/?: y |
|---|
| 115 | Fri Sep 19 14:31:44 2014 - INFO: Shutting down instance debianY on source node hostB |
|---|
| 116 | Fri Sep 19 14:32:01 2014 disk/0 sent 450M, 77.2 MiB/s, 21%, ETA 21s |
|---|
| 117 | Fri Sep 19 14:32:37 2014 disk/0 finished receiving data |
|---|
| 118 | Fri Sep 19 14:32:37 2014 disk/0 finished sending data |
|---|
| 119 | Fri Sep 19 14:32:37 2014 - INFO: Removing the disks on the original node |
|---|
| 120 | Fri Sep 19 14:32:38 2014 - INFO: Starting instance debianY on node hostC</code></pre> |
|---|
| 121 | <p>The hostB is ready to be shut down. Don't do this!</p> |
|---|
| 122 | <h1 id="scenario-loss-of-a-slave-node"><a href="#scenario-loss-of-a-slave-node"><span class="header-section-number">3</span> Scenario: Loss of a Slave Node</a></h1> |
|---|
| 123 | <h2 id="initial-state"><a href="#initial-state"><span class="header-section-number">3.1</span> Initial state</a></h2> |
|---|
| 124 | <ul> |
|---|
| 125 | <li>Confirm that <code>debianX</code> (or what the name of the DRBD VM you are using is) is running on hostB (gnt-instance list). If necessary, run replace-disks again and migrate debianX so it is primary on hostB, and debianY is secondary on hostB.</li> |
|---|
| 126 | </ul> |
|---|
| 127 | <pre><code># gnt-instance list -o name,pnode,snodes,status</code></pre> |
|---|
| 128 | <pre><code>Instance Primary_node Secondary_Nodes Status |
|---|
| 129 | debianX hostB.ws.nsrc.org hostA.ws.nsrc.org running |
|---|
| 130 | debianY hostC.ws.nsrc.org hostB.ws.nsrc.org running |
|---|
| 131 | debianZ hostC.ws.nsrc.org running</code></pre> |
|---|
| 132 | <ul> |
|---|
| 133 | <li>Shut down (halt) hostB, the (<em>make sure you run this on hostB, the primary node for instance debianX!</em>)</li> |
|---|
| 134 | </ul> |
|---|
| 135 | <pre><code># halt -p</code></pre> |
|---|
| 136 | <ul> |
|---|
| 137 | <li>The VM goes down as a result (confirm this using ping / console)</li> |
|---|
| 138 | </ul> |
|---|
| 139 | <pre><code># gnt-instance list -o name,pnode,snodes,status |
|---|
| 140 | |
|---|
| 141 | Instance Primary_node Secondary_Nodes Status |
|---|
| 142 | debianX hostB.ws.nsrc.org hostA.ws.nsrc.org ERROR_nodedown |
|---|
| 143 | debianY hostC.ws.nsrc.org hostB.ws.nsrc.org running |
|---|
| 144 | debianZ hostC.ws.nsrc.org running</code></pre> |
|---|
| 145 | <ul> |
|---|
| 146 | <li><p>Run <code>gnt-cluster verify</code> (will take a while), and look at the output.</p></li> |
|---|
| 147 | <li><p>Run <code>gnt-node list</code>, and look at the output, too.</p></li> |
|---|
| 148 | </ul> |
|---|
| 149 | <p>As you notice, things are quite slow. This is because Ganeti is trying to contact the <code>gnt-noded</code> daemon on hostB, and it's timing out.</p> |
|---|
| 150 | <p>If this were a production environment, we'd have to examine hostB, and determine whether hostB was likely to come back online soon. If not, say, because of some hardware failure, we would decide to take the node "offline", so Ganeti would stop trying to talk to it.</p> |
|---|
| 151 | <p>Let's start by marking hostB as offline:</p> |
|---|
| 152 | <pre><code># gnt-node modify --offline=yes hostB.ws.nsrc.org |
|---|
| 153 | |
|---|
| 154 | Modified node hostB.ws.nsrc.org |
|---|
| 155 | - master_candidate -> False |
|---|
| 156 | - offline -> True</code></pre> |
|---|
| 157 | <p>It will take a little while, but now most commands will run faster as Ganeti stops trying to contact the other nodes in the cluster.</p> |
|---|
| 158 | <p>Try running <code>gnt-instance list</code> and <code>gnt-node list</code> again.</p> |
|---|
| 159 | <p>Also re-run <code>gnt-cluster verify</code></p> |
|---|
| 160 | <h3 id="instance-recovery"><a href="#instance-recovery"><span class="header-section-number">3.1.1</span> Instance recovery</a></h3> |
|---|
| 161 | <ul> |
|---|
| 162 | <li>We cannot live-migrate the host (hostB is down), so we need to <em>failover</em></li> |
|---|
| 163 | </ul> |
|---|
| 164 | <p>If you attempt to migrate, you will be told:</p> |
|---|
| 165 | <pre><code># gnt-instance migrate debianX |
|---|
| 166 | |
|---|
| 167 | Failure: prerequisites not met for this operation: |
|---|
| 168 | error type: wrong_state, error details: |
|---|
| 169 | Can't migrate, please use failover: Node is marked offline</code></pre> |
|---|
| 170 | <ul> |
|---|
| 171 | <li>Attempt failover</li> |
|---|
| 172 | </ul> |
|---|
| 173 | <pre><code># gnt-instance failover debianX</code></pre> |
|---|
| 174 | <p>Hopefully you will see messages ending with:</p> |
|---|
| 175 | <pre><code>... |
|---|
| 176 | Sat Jan 18 15:58:11 2014 * activating the instance's disks on target node hostA.ws.nsrc.org |
|---|
| 177 | Sat Jan 18 15:58:11 2014 - WARNING: Could not prepare block device disk/0 on node hostB.ws.nsrc.org (is_primary=False, pass=1): Node is marked offline |
|---|
| 178 | Sat Jan 18 15:58:11 2014 * starting the instance on the target node hostA.ws.nsrc.org</code></pre> |
|---|
| 179 | <p>If so, skip to the section "Confirm that the VM is now up on hostA"</p> |
|---|
| 180 | <p>If you see this message:</p> |
|---|
| 181 | <pre><code>Sat Jan 18 20:57:55 2014 Failover instance debianX |
|---|
| 182 | Sat Jan 18 20:57:55 2014 * checking disk consistency between source and target |
|---|
| 183 | Failure: command execution error: |
|---|
| 184 | Disk 0 is degraded on target node, aborting failover</code></pre> |
|---|
| 185 | <p>... you will need to <em>force</em> the operation. This should normally not happen when the node is marked offline. However, if you do get the message:</p> |
|---|
| 186 | <ul> |
|---|
| 187 | <li>Read man page on <code>gnt-instance</code>, find the section about <code>failover</code>:</li> |
|---|
| 188 | </ul> |
|---|
| 189 | <blockquote> |
|---|
| 190 | <p>If you are trying to migrate instances off a dead node, this will fail. Use the --ignore-consistency option for this purpose. Note that this option can be dangerous as errors in shutting down the instance will be ignored, resulting in possibly having the instance running on two machines in parallel (on disconnected DRBD drives).</p> |
|---|
| 191 | </blockquote> |
|---|
| 192 | <ul> |
|---|
| 193 | <li><p>We know that hostB is down - we halted it ourselves! In a real world scenario, you MUST verify that hostB really is down. Otherwise you risk ending up with two running instances of <code>VM</code> (if someone force starts it) and you will need to force a resolution.</p></li> |
|---|
| 194 | <li><p>Re-run <code>gnt-instance failover</code> with the '--ignore-consistency' flag. We are in a situation that requires this (hostB down)</p></li> |
|---|
| 195 | </ul> |
|---|
| 196 | <pre><code># gnt-instance failover --ignore-consistency debianX</code></pre> |
|---|
| 197 | <p>There will be much more output this time, pay attention in particular if you see some warnings - these are normal since the hostB node is down, but we did it mark it as offline.</p> |
|---|
| 198 | <pre><code>Sat Jan 18 21:03:15 2014 Failover instance debianX |
|---|
| 199 | Sat Jan 18 21:03:15 2014 * checking disk consistency between source and target |
|---|
| 200 | |
|---|
| 201 | [ ... messages ... ] |
|---|
| 202 | |
|---|
| 203 | Sat Jan 18 21:03:27 2014 * activating the instance's disks on target node hostA.ws.nsrc.org |
|---|
| 204 | |
|---|
| 205 | [ ... messages ... ] |
|---|
| 206 | |
|---|
| 207 | Sat Jan 18 21:03:33 2014 * starting the instance on the target node hostA.ws.nsrc.org</code></pre> |
|---|
| 208 | <ul> |
|---|
| 209 | <li>Confirm that the VM is now up on hostA:</li> |
|---|
| 210 | </ul> |
|---|
| 211 | <pre><code># gnt-instance list -o name,pnode,snodes,status |
|---|
| 212 | |
|---|
| 213 | Instance Primary_node Secondary_Nodes Status |
|---|
| 214 | debianX hostA.ws.nsrc.org hostB.ws.nsrc.org running |
|---|
| 215 | debianY hostC.ws.nsrc.org hostB.ws.nsrc.org running |
|---|
| 216 | debianZ hostC.ws.nsrc.org running</code></pre> |
|---|
| 217 | <h3 id="re-adding-the-failed-node"><a href="#re-adding-the-failed-node"><span class="header-section-number">3.1.2</span> Re-adding the failed node</a></h3> |
|---|
| 218 | <p>Ok, let's say hostB has been fixed.</p> |
|---|
| 219 | <ul> |
|---|
| 220 | <li><p>Restart hostB. (Depending on the class setup, you may need to ask the instructor to do this for you).</p></li> |
|---|
| 221 | <li><p>Make sure you can ping it and can log in to it</p></li> |
|---|
| 222 | </ul> |
|---|
| 223 | <p>We need to re-add it to the cluster. We do this using the <code>gnt-node add --readd</code> command on the cluster master node.</p> |
|---|
| 224 | <p>From the <code>gnt-node</code> man page:</p> |
|---|
| 225 | <blockquote> |
|---|
| 226 | <p>In case you're readding a node after hardware failure, you can use the --readd parameter. In this case, you don't need to pass the secondary IP again, it will reused from the cluster. Also, the drained and offline flags of the node will be cleared before re-adding it.</p> |
|---|
| 227 | </blockquote> |
|---|
| 228 | <pre><code># gnt-node add --readd hostB.ws.nsrc.org |
|---|
| 229 | |
|---|
| 230 | [ ... question about SSH ...] |
|---|
| 231 | |
|---|
| 232 | Sat Jan 18 22:09:43 2014 - INFO: Readding a node, the offline/drained flags were reset |
|---|
| 233 | Sat Jan 18 22:09:43 2014 - INFO: Node will be a master candidate</code></pre> |
|---|
| 234 | <p>We're good! It could take a while to re-sync the DRBD data if a lot of disk activity (writing) has taken place on <code>debianX</code>, but this will happen in the background.</p> |
|---|
| 235 | <p>Inspect the node list:</p> |
|---|
| 236 | <pre><code># gnt-node list</code></pre> |
|---|
| 237 | <p>Check the cluster configuration.</p> |
|---|
| 238 | <pre><code># gnt-cluster verify</code></pre> |
|---|
| 239 | <p>Probably the DRBD instances on hostB have not yet been activated by the. As a result you may see some errors about your instance's disk beging degraded, similar to this:</p> |
|---|
| 240 | <pre><code>Thu Sep 18 18:52:41 2014 * Verifying node status |
|---|
| 241 | Thu Sep 18 18:52:41 2014 - ERROR: node hostB: drbd minor 0 of instance debianX is not active |
|---|
| 242 | Thu Sep 18 18:52:41 2014 * Verifying instance status |
|---|
| 243 | Thu Sep 18 18:52:41 2014 - ERROR: instance debianX: disk/0 on hostA is degraded |
|---|
| 244 | Thu Sep 18 18:52:41 2014 - ERROR: instance debianX: couldn't retrieve status for disk/0 on hostB: Can't find device <DRBD8(hosts=03add4b7-d6d9-40d0-bf6e-74d1683aad49/0-93eef5d9-6b33-4c</code></pre> |
|---|
| 245 | <p>Don't panic! This is normal, as it's possible the disks haven't been re-synchronized yet.</p> |
|---|
| 246 | <p>If so, you can use the command <code>gnt-cluster verify-disks</code> to fix this:</p> |
|---|
| 247 | <pre><code># gnt-cluster verify-disks |
|---|
| 248 | |
|---|
| 249 | Submitted jobs 78 |
|---|
| 250 | Waiting for job 78 ... |
|---|
| 251 | Activating disks for instance 'debianX'</code></pre> |
|---|
| 252 | <p>Wait a few seconds, then run:</p> |
|---|
| 253 | <pre><code># gnt-cluster verify</code></pre> |
|---|
| 254 | <p>When all is OK, let's try and migrate debianX back to hostB:</p> |
|---|
| 255 | <pre><code># gnt-instance migrate debianX</code></pre> |
|---|
| 256 | <p>Test that the migration has worked.</p> |
|---|
| 257 | <h2 id="completely-removing-hostb-from-the-cluster"><a href="#completely-removing-hostb-from-the-cluster"><span class="header-section-number">3.2</span> Completely removing hostB from the cluster</a></h2> |
|---|
| 258 | <p>Let's now imagine that the failure of hostB wasn't temporary: we imagine that it cannot be fixed, and won't be back online for a while (it needs to be completely replaced). We could decide to remove hostB from the cluster.</p> |
|---|
| 259 | <p>To do this:</p> |
|---|
| 260 | <ul> |
|---|
| 261 | <li>If hostB has been restarted, let's shut it down (to simulate a failure)</li> |
|---|
| 262 | </ul> |
|---|
| 263 | <p>Note: RUN THIS ON hostB !!!</p> |
|---|
| 264 | <pre><code># halt -p</code></pre> |
|---|
| 265 | <ul> |
|---|
| 266 | <li>On the master:</li> |
|---|
| 267 | </ul> |
|---|
| 268 | <p>Mark hostB as offline:</p> |
|---|
| 269 | <pre><code># gnt-node modify --offline=yes hostB.ws.nsrc.org</code></pre> |
|---|
| 270 | <p>run <code>gnt-cluster verify</code>, and look at the output.</p> |
|---|
| 271 | <pre><code>Sat Jan 18 21:31:56 2014 - NOTICE: 1 offline node(s) found.</code></pre> |
|---|
| 272 | <ul> |
|---|
| 273 | <li><p>We marked hostB as down - let's assume hostB will be down for a while while it's being fixed.</p></li> |
|---|
| 274 | <li><p>We decide to remove hostB from the cluster:</p></li> |
|---|
| 275 | </ul> |
|---|
| 276 | <pre><code># gnt-node remove hostB.ws.nsrc.org |
|---|
| 277 | |
|---|
| 278 | Failure: prerequisites not met for this operation: |
|---|
| 279 | error type: wrong_input, error details: |
|---|
| 280 | Instance debianX is still running on the node, please remove first</code></pre> |
|---|
| 281 | <p>Ok, we are not allowed to remove the hostB, because Ganeti can see that we still have an instance (debianX) associated with hostB.</p> |
|---|
| 282 | <p>This is different from simply marking the node offline, as it means we are permanently getting rid of hostB, and we need to take a decision about what to do for DRBD instances that were associated with hostB.</p> |
|---|
| 283 | <!-- XXX: gnt-node failover goes here --> |
|---|
| 284 | |
|---|
| 285 | <pre><code># gnt-instance failover debianX |
|---|
| 286 | |
|---|
| 287 | Failover will happen to image debianX. This requires a shutdown of |
|---|
| 288 | the instance. Continue? |
|---|
| 289 | y/[n]/?: y |
|---|
| 290 | Thu Sep 18 20:29:32 2014 Failover instance debianX |
|---|
| 291 | Thu Sep 18 20:29:32 2014 * checking disk consistency between source and target |
|---|
| 292 | Thu Sep 18 20:29:32 2014 Node hostB.ws.nsrc.org is offline, ignoring degraded disk 0 on target node hostA.ws.nsrc.org |
|---|
| 293 | Thu Sep 18 20:29:32 2014 * shutting down instance on source node |
|---|
| 294 | Thu Sep 18 20:29:32 2014 - WARNING: Could not shutdown instance debianX on node hostB.ws.nsrc.org, proceeding anyway; please make sure node hostB.ws.nsrc.org is down; error details: Node is marked offline |
|---|
| 295 | Thu Sep 18 20:29:32 2014 * deactivating the instance's disks on source node |
|---|
| 296 | Thu Sep 18 20:29:33 2014 - WARNING: Could not shutdown block device disk/0 on node hostB.ws.nsrc.org: Node is marked offline |
|---|
| 297 | Thu Sep 18 20:29:33 2014 * activating the instance's disks on target node hostA.ws.nsrc.org |
|---|
| 298 | Thu Sep 18 20:29:33 2014 - WARNING: Could not prepare block device disk/0 on node hostB.ws.nsrc.org (is_primary=False, pass=1): Node is marked offline |
|---|
| 299 | Thu Sep 18 20:29:33 2014 * starting the instance on the target node hostA.ws.nsrc.org</code></pre> |
|---|
| 300 | <p>Followed by:</p> |
|---|
| 301 | <!-- XXX maybe we need to do a replace-disks instead --> |
|---|
| 302 | |
|---|
| 303 | <pre><code># gnt-node evacuate -s hostB |
|---|
| 304 | |
|---|
| 305 | Relocate instance(s) debianX from node(s) hostB? |
|---|
| 306 | y/[n]/?: y |
|---|
| 307 | Thu Sep 18 20:32:37 2014 - INFO: Evacuating instances from node 'hostB.ws.nsrc.org': debianX |
|---|
| 308 | Thu Sep 18 20:32:37 2014 - INFO: Instances to be moved: debianX (to hostA.ws.nsrc.org, hostC.ws.nsrc.org) |
|---|
| 309 | ... |
|---|
| 310 | Thu Sep 18 20:32:38 2014 STEP 3/6 Allocate new storage |
|---|
| 311 | Thu Sep 18 20:32:38 2014 - INFO: Adding new local storage on hostC.ws.nsrc.org for disk/0 |
|---|
| 312 | ... |
|---|
| 313 | Thu Sep 18 20:32:41 2014 STEP 6/6 Sync devices |
|---|
| 314 | Thu Sep 18 20:32:41 2014 - INFO: Waiting for instance debianX to sync disks |
|---|
| 315 | Thu Sep 18 20:32:41 2014 - INFO: - device disk/0: 1.20% done, 1m 55s remaining (estimated) |
|---|
| 316 | Thu Sep 18 20:33:41 2014 - INFO: Instance debianX's disks are in sync |
|---|
| 317 | All instances evacuated successfully.</code></pre> |
|---|
| 318 | <p>Ok, check out the instance list:</p> |
|---|
| 319 | <pre><code># gnt-instance list -o name,pnode,snodes,status |
|---|
| 320 | |
|---|
| 321 | Instance Primary_node Secondary_Nodes Status |
|---|
| 322 | debianX hostA.ws.nsrc.org hostC.ws.nsrc.org running |
|---|
| 323 | XXX</code></pre> |
|---|
| 324 | <p>Perfect, hostB is not used by any instance. We can now re-attempt to remove node hostB from the cluster:</p> |
|---|
| 325 | <pre><code># gnt-node remove hostB.ws.nsrc.org</code></pre> |
|---|
| 326 | <p>More WARNINGs! But did it work ?</p> |
|---|
| 327 | <pre><code># gnt-node list |
|---|
| 328 | |
|---|
| 329 | Node DTotal DFree MTotal MNode MFree Pinst Sinst |
|---|
| 330 | hostA.ws.nsrc.org 29.1G 12.6G 995M 145M 672M 2 0 |
|---|
| 331 | hostC.ws.nsrc.org 29.0G 12.7G 995M 137M 680M 0 1</code></pre> |
|---|
| 332 | <p>Yes, hostB is gone.</p> |
|---|
| 333 | <p>Note: Ganeti will modify <code>/etc/hosts</code> on your remaining nodes, and remove the line for hostB!</p> |
|---|
| 334 | <p>We can restart our debianX instance, by the way! (This may have already happened if you called <code>gnt-instance failover</code>)</p> |
|---|
| 335 | <pre><code># gnt-instance start debianX</code></pre> |
|---|
| 336 | <p>Test that it comes up normally.</p> |
|---|
| 337 | <h1 id="scenario-planned-master-failover-node-maintenance"><a href="#scenario-planned-master-failover-node-maintenance"><span class="header-section-number">4</span> Scenario: Planned master failover (node maintenance)</a></h1> |
|---|
| 338 | <p>Let's imagine that we need to temporarily service the cluster master (in this case, nodeA). It's rather easy. Decide first which of the other nodes will become master.</p> |
|---|
| 339 | <p>Read about <code>master-failover</code>: <code>man gnt-cluster</code>, find the MASTER-FAILOVER section.</p> |
|---|
| 340 | <p>Then, ON THE NODE YOU PICKED, run this command:</p> |
|---|
| 341 | <pre><code># gnt-cluster master-failover</code></pre> |
|---|
| 342 | <p>If everything goes well, after 5-10 seconds, the node you ran this command on is now the new master.</p> |
|---|
| 343 | <p>Test this! For example, if hostB is your new master, run these commands on it:</p> |
|---|
| 344 | <p>Verify that the cluster IP is now on this host:</p> |
|---|
| 345 | <pre><code># ifconfig br-lan:0</code></pre> |
|---|
| 346 | <p>Notice that the IP address in br-lan:0 is that of the cluster master.</p> |
|---|
| 347 | <p>This means that next time you log on using SSH using the cluster IP, you will be logged on to hostB.</p> |
|---|
| 348 | <p>Check which node is the master (remember, you need to run this on the master).</p> |
|---|
| 349 | <pre><code># gnt-cluster getmaster |
|---|
| 350 | hostB.ws.nsrc.org</code></pre> |
|---|
| 351 | <p>All good!</p> |
|---|
| 352 | <h1 id="scenario-loss-of-master-node"><a href="#scenario-loss-of-master-node"><span class="header-section-number">5</span> Scenario: Loss of Master Node</a></h1> |
|---|
| 353 | <p>Let's imagine a slightly more critical scenario: the crash of the master node.</p> |
|---|
| 354 | <p>Let's shut down the master node!</p> |
|---|
| 355 | <p>On hostB (it's now our master node, remember ?)</p> |
|---|
| 356 | <pre><code># halt -p</code></pre> |
|---|
| 357 | <p>The node is now down. VM still running on other nodes are unaffected, but you are not able to make any changes (stop, start, modify, add VMs, change cluster configuration, etc...)</p> |
|---|
| 358 | <h2 id="promoting-slave"><a href="#promoting-slave"><span class="header-section-number">5.1</span> Promoting slave</a></h2> |
|---|
| 359 | <p>Let's assume that hostB is not coming back right now, and we need to promote a master.</p> |
|---|
| 360 | <p>You will first need to decide which of the remaining nodes will become the master. Let's pick hostA.</p> |
|---|
| 361 | <p>To promote the slave:</p> |
|---|
| 362 | <ul> |
|---|
| 363 | <li><p>Log on to the node that will become master (hostA):</p></li> |
|---|
| 364 | <li><p>Run the following command:</p></li> |
|---|
| 365 | </ul> |
|---|
| 366 | <pre><code># gnt-cluster master-failover</code></pre> |
|---|
| 367 | <p>Note here that you will NOT be asked to confirm the operation!</p> |
|---|
| 368 | <p>If you have 3 or more nodes in the cluster, the operation should be as smooth as in the previous section.</p> |
|---|
| 369 | <p>On the other hand, if you only had 2 nodes in your cluster, you would have to specify <code>--no-voting</code> as an option. This is because, if one node is down, there is only one node left in the cluster, and no election can take place.</p> |
|---|
| 370 | <p>At this point, the chosen node (hostA) is now master. You can verify this using the <code>gnt-cluster getmaster</code> command.</p> |
|---|
| 371 | <p>From this point, recovering downed machines is similar to what we did in the first scenario. But to be on the safe side:</p> |
|---|
| 372 | <ul> |
|---|
| 373 | <li><p>Restart hostB, and log in to it as root</p></li> |
|---|
| 374 | <li><p>Try and run <code>gnt-instance list</code></p></li> |
|---|
| 375 | </ul> |
|---|
| 376 | <p>XXX error here - split brain</p> |
|---|
| 377 | <p>Normally, even though hostA was down while the promotion of hostB happened, the <code>ganeti-masterd</code> daemon running on hostA was informed, on startup, that hostA was no longer master. The above command should therefore fail with:</p> |
|---|
| 378 | <pre><code>This is not the master node, please connect to node 'hostB.ws.nsrc.org' and |
|---|
| 379 | rerun the command</code></pre> |
|---|
| 380 | <p>Which means that hostA is well aware that hostB is the master now.</p> |
|---|
| 381 | <p>Once you have done this, you may find that hostB and hostA have different versions of the cluster database. Type the following on hostB:</p> |
|---|
| 382 | <pre><code># gnt-cluster verify |
|---|
| 383 | ... |
|---|
| 384 | Sat Jan 18 16:11:12 2014 - ERROR: cluster: File /var/lib/ganeti/config.data found with 2 different checksums (variant 1 on hostB.ws.nsrc.org, hostC.ws.nsrc.org; variant 2 on hostA.ws.nsrc.org) |
|---|
| 385 | Sat Jan 18 16:11:12 2014 - ERROR: cluster: File /var/lib/ganeti/ssconf_master_node found with 2 different checksums (variant 1 on hostB.ws.nsrc.org, hostC.ws.nsrc.org; variant 2 on hostA.ws.nsrc.org)</code></pre> |
|---|
| 386 | <p>You can fix this by:</p> |
|---|
| 387 | <pre><code># gnt-cluster redist-conf</code></pre> |
|---|
| 388 | <p>which pushes out the config from the current master to all the other nodes.</p> |
|---|
| 389 | <p>Re-run <code>gnt-cluster verify</code> to check everything is OK again.</p> |
|---|
| 390 | <p>Then to make hostA take over the master role again, login to hostA and run:</p> |
|---|
| 391 | <pre><code># gnt-cluster master-failover</code></pre> |
|---|
| 392 | <h1 id="some-key-commands"><a href="#some-key-commands"><span class="header-section-number">6</span> Some key commands</a></h1> |
|---|
| 393 | <p>These are some of the commands we'll be making use of</p> |
|---|
| 394 | <p>UNUSED</p> |
|---|
| 395 | <h2 id="moving-all-instances-away-from-a-node"><a href="#moving-all-instances-away-from-a-node"><span class="header-section-number">6.1</span> Moving all instances away from a node</a></h2> |
|---|
| 396 | <p>command: <code>gnt-node evacuate</code></p> |
|---|
| 397 | <p>Read the man page for <code>gnt-node</code> and look for the section about the <code>evacuate</code> subcommand.</p> |
|---|
| 398 | <p>Note: for the time being, one needs to explicitly tell the evacuate command to move away either primary (<code>-p</code>) or secondary (<code>-s</code>) instances - it won't work for both at the same time.</p> |
|---|
| 399 | <p>Assuming we have:</p> |
|---|
| 400 | <ul> |
|---|
| 401 | <li>We have debianX running as a DRBD instance on hostA (primary)</li> |
|---|
| 402 | <li><p>hostB (secondary).</p></li> |
|---|
| 403 | <li><p>We have debianZ running as a plain instance on host B</p></li> |
|---|
| 404 | </ul> |
|---|
| 405 | <p>What happens if we do:</p> |
|---|
| 406 | <pre><code># gnt-node evacuate -p nodeB |
|---|
| 407 | |
|---|
| 408 | Relocate instance(s) debianY from node(s) nodeB? |
|---|
| 409 | y/[n]/?:</code></pre> |
|---|
| 410 | <p><code>gnt-node evacuate</code> has figured out that the <code>plain</code> debianY instance needs to be moved away. Answer <code>y</code></p> |
|---|
| 411 | <pre><code>Fri Sep 19 14:29:45 2014 - INFO: Evacuating instances from node 'hostB': debianY |
|---|
| 412 | Fri Sep 19 14:29:46 2014 - WARNING: Unable to evacuate instances debianY (Instances of type plain cannot be relocated) |
|---|
| 413 | Failure: command execution error: |
|---|
| 414 | Unable to evacuate instances debianY (Instances of type plain cannot be relocated)</code></pre> |
|---|
| 415 | <p>Uh oh :(</p> |
|---|
| 416 | <p>What about gnt-node evacuate -s nodeB ?</p> |
|---|
| 417 | <h2 id="making-a-node-online-after-it-has-been-marked-as-offline"><a href="#making-a-node-online-after-it-has-been-marked-as-offline"><span class="header-section-number">6.2</span> Making a node online after it has been marked as offline</a></h2> |
|---|
| 418 | <p>Note: if you are certain that the node <code>hostB</code> is healthy (let's say it was just a power failure, and no corruption has happened on its filesystem or disks), you could simply do the following (DON'T DO THIS NOW!):</p> |
|---|
| 419 | <pre><code># gnt-node modify -O no hostB.ws.nsrc.org |
|---|
| 420 | |
|---|
| 421 | Sat Jan 18 22:08:45 2014 - INFO: Auto-promoting node to master candidate |
|---|
| 422 | Sat Jan 18 22:08:45 2014 - WARNING: Transitioning node from offline to online state without using re-add. Please make sure the node is healthy!</code></pre> |
|---|
| 423 | <p>But you would be warned about this.</p> |
|---|
| 424 | </body> |
|---|
| 425 | </html> |
|---|
