> Ah, thanks! That gets me a bit further: > > Beginning work on en-US > Validation failed: > cloudstack.xml:6: validity error : Element book content does not follow the > DTD, expecting ((title , subtitle? , titleabbrev?)? , bookinfo? , > (dedication | toc | lot | glossary | bibliography | preface | chapter | > reference | part | article | appendix | index | setindex | colophon)*), got > (bookinfo chapter chapter chapter chapter chapter chapter book appendix ) > Book_Info.xml:6: validity error : ID book-release-notes-3.0.4 already > defined >
Yeah, it's broken as of last night. I'll fix it shortly. > > The builds on Jenkins.cloudstack.org seem to have only some release notes > information? > > And as the last question: What is the exact goal of the runbook? It will > have duplicate documentation as it seems. Do we continue with that? Or was > it intermediate? I intended it as a 'here's a guaranteed successful/prescriptive method' to get a cloudstack instance up and working. The install guide has so much information it's bewildering to a newcomer (albeit necessary information, choosing between layer-3 isolation and layer-2 isolation is difficult enough) Can it be integrated, perhaps, it's very different content, but not necessarily impossible to merge. > > And how do you build the runbook? Runbook is similar, just do the above in the docs/runbook directory. > > A lot of questions, I know! > > Wido > > >
