Open Stack

Hi Tom,
I'll definitely cast my vote for info on quotas belonging in admin 
guides, and the Security Guide where relevant.

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.

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.

(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.)

Ok, that was a bit of rambling.

cheers, Summer

Summer Long
OpenStack Documentation
Engineering Content Services

Red Hat Asia Pacific
Brisbane, Australia
slong at redhat.com <mailto:slong at redhat.com>

On 07/13/2013 01:54 PM, Tom Fifield wrote:
> Hi all,
>
> I've been having a nice little monologue over at:
>
> https://bugs.launchpad.net/openstack-manuals/+bug/1090654
>
> 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.
>
> 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:
>
> The feature would _not_ be listed in:
> * Install guide: the install guide is for a basic description of 
> installation, and this is not a necessary part
>
> * 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.
>
>
> The feature _may_ be listed in:
> * The Operations Guide: it may be a best practice to set instance 
> resource limits when configuing flavors
>
> * 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
>
>
> This feature would predominantely live in:
>
> * 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.
>
> * 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
>
>
> Well that's my take - what's yours? If we can converge on this simple 
> bug, we have achieved a minor success in scoping :)
>
>
> Regards,
>
>
> Tom
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20130715/5ce1eae4/attachment.html>