<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Tom,<br>
I'll definitely cast my vote for info on quotas belonging in admin
guides, and the Security Guide where relevant. <br>
<br>
Question for the intent of the Configuration Reference and its name.
If its audience is just the installer/system configurer, perhaps the
name should be 'System Configuration Reference', to make it obvious
that no end-user info is in there. <br>
<br>
This was the problem I was hitting between the naming of the admin
user guide and admin guide. Should the larger admin guide be renamed
to 'System Administration Reference'? Or use new roles of 'cloud
administrator' vs 'client administrator'...or something.<br>
<br>
(Still don't understand the function of the Operations Guide if the
larger admin guide goes forward for system/cloud admins and install
guides exist as well.)<br>
<br>
Ok, that was a bit of rambling. <br>
<br>
cheers, Summer<br>
<br>
<div class="moz-signature">
<div><font color="#666666">Summer Long<br>
OpenStack Documentation<br>
Engineering Content Services<br>
<br>
Red Hat Asia Pacific<br>
Brisbane, Australia</font><br>
<a href="mailto:slong@redhat.com">slong@redhat.com</a></div>
</div>
<br>
<span style="color:#000000;" class="headerSpan">
<div class="moz-cite-prefix">On 07/13/2013 01:54 PM, Tom Fifield
wrote:<br>
</div>
</span>
<blockquote cite="mid:51E0CF91.3090009@openstack.org" type="cite">Hi
all,
<br>
<br>
I've been having a nice little monologue over at:
<br>
<br>
<a class="moz-txt-link-freetext" href="https://bugs.launchpad.net/openstack-manuals/+bug/1090654">https://bugs.launchpad.net/openstack-manuals/+bug/1090654</a>
<br>
<br>
which is a bug to document the introduction (into grizzly) of a
feature called "Instance Resource Quotas", that allow you to set
limits on how much cpu/disk/network particular instance types
consume.
<br>
<br>
As you can read, I had some initial confusion on where this would
go. So here are my conclusions, provided so we can use it as an
excercise in scoping with the current restructure efforts:
<br>
<br>
The feature would _not_ be listed in:
<br>
* Install guide: the install guide is for a basic description of
installation, and this is not a necessary part
<br>
<br>
* Config reference: the configuration reference is for parts of
the system that need root access to systems be configured -
really, things that need to be tweaked in {nova,neutron,...}.conf.
This feature is always enabled, and set in user-space, using nova
commands.
<br>
<br>
<br>
The feature _may_ be listed in:
<br>
* The Operations Guide: it may be a best practice to set instance
resource limits when configuing flavors
<br>
<br>
* The Secuity Guide: there are security implications of not
setting these limits - where in certain situations guests could eg
consume all the bandwidth, leading to a DoS attack
<br>
<br>
<br>
This feature would predominantely live in:
<br>
<br>
* The Admin User manual: since configuring flavours lives there,
and this is a part of configuring flavours. A link to hypervisors
section in config ref might be included, with a note on support of
the feature across various hypervisors.
<br>
<br>
* The `Comprehensive` Admin Manual: if/when this exists, it would
contain an extensive discussion of the "extra_specs" metadata
field, which is used to implement the Instance Resource Quotas
<br>
<br>
<br>
Well that's my take - what's yours? If we can converge on this
simple bug, we have achieved a minor success in scoping :)
<br>
<br>
<br>
Regards,
<br>
<br>
<br>
Tom
<br>
<br>
_______________________________________________
<br>
Openstack-docs mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a>
<br>
</blockquote>
<br>
</body>
</html>