I like the idea but shouldn't it be part of the source code and extracted from there? What is the need to have it in a separate wiki?
On Mon, Feb 15, 2016 at 9:18 AM, Rohit Yadav <rohit.ya...@shapeblue.com> wrote: > Nice, maybe put this on our cwiki so others can collaborate than do this > over a word doc? > > Regards. > > > [image: ShapeBlue] <http://www.shapeblue.com> > Rohit Yadav > Software Architect , ShapeBlue > d: * | s: +44 203 603 0540* <%7C%20s:%20+44%20203%20603%200540> | m: > *+91 8826230892* <+91%208826230892> > e: *rohit.ya...@shapeblue.com | t: * > <rohit.ya...@shapeblue.com%20%7C%20t:> | w: *www.shapeblue.com* > <http://www.shapeblue.com> > a: 53 Chandos Place, Covent Garden London WC2N 4HS UK > Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue > Services India LLP is a company incorporated in India and is operated under > license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a > company incorporated in Brasil and is operated under license from Shape > Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of > South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is > a registered trademark. > This email and any attachments to it may be confidential and are intended > solely for the use of the individual to whom it is addressed. Any views or > opinions expressed are solely those of the author and do not necessarily > represent those of Shape Blue Ltd or related companies. If you are not the > intended recipient of this email, you must neither take any action based > upon its contents, nor copy or show it to anyone. Please contact the sender > if you believe you have received this email in error. > > > On 14-Feb-2016, at 5:37 AM, Rajsekhar K <rajsekharkpa...@gmail.com> wrote: > > Hi, All, > > This is part of the effort to create a Reference Guide for CloudStack > configuration parameters. This guide intends to provide a single point of > reference for the configuration parameters that we use in CloudStack. Each > parameter will be treated as a topic in this guide. > > I am planning to document the following information for each parameter: > > > - Name and description of the parameter. > - List of features that the users can configure using the parameter. > - Changes in the behavior of each parameter when users provide low, > optimal, and high values to the parameters. > - Warnings, notes, and limitations for each parameter. > - Example for each parameter - Explaining the parameter with the help > of scenarios. > - Impact of each configuration parameter on APIs. > - Scope of the parameter - global, zone-level, or cluster-level. > - Dependencies among the configuration parameters. > - Category to which the parameter belongs. > > > Will let you know more about this effort as we progress with this guide. > > Please find attached the list of CloudStack parameters that are > categorized according to the functional areas they belong to. Could you > please review this list and let me know your review comment/confirmation? > > Also, I have a few parameters listed under the heading * Others (To be > categorized)*. Could you please help me categorize these parameters? > > Thanks, > Rajsekhar > <cloudstack-config-param-categories.docx> > > > Regards. > > Find out more about ShapeBlue and our range of CloudStack related services: > IaaS Cloud Design & Build > <http://shapeblue.com/iaas-cloud-design-and-build//> | CSForge – rapid > IaaS deployment framework <http://shapeblue.com/csforge/> > CloudStack Consulting <http://shapeblue.com/cloudstack-consultancy/> | > CloudStack > Software Engineering > <http://shapeblue.com/cloudstack-software-engineering/> > CloudStack Infrastructure Support > <http://shapeblue.com/cloudstack-infrastructure-support/> | CloudStack > Bootcamp Training Courses <http://shapeblue.com/cloudstack-training/> > -- Daan
