Hey folks,

I’ve summarized the User API Improvement forum session.  I seem to recall that 
Clark Boyland and I were “volunteered” to project manage the effort to get 
these tracked and scheduled (which I would assume also means eiterh spec’ed, 
bp’ed or bugged), but I’m real fuzzy on that.  Any/all comments welcome.  The 
etherpad for this session is here:
https://etherpad.openstack.org/p/openstack-user-api-improvements

--Rocky

Summary:
This session’s focus was how to both improve the user experience in using 
OpenStack APIs through identification of issues and inconsistencies and raising 
their visibility in the developer community.  There were general observations, 
then observation specific to individual projects. The major themes of this 
session were:
Consistency:

·         Use the same verbs for same/similar actions across all OpenStack

·          Make states the same across all projects

·         UTF8 everywhere for user provided info and metadata

·         Make ports 80/443 defaults across OpenStack so that deployments that 
have to think about nonstandard port assignments

·         Services other than core/base services should be design to run *on* 
cloud, not *in* cloud

·         All clouds should accept qcow2 uploads and convert to cloud native if 
necessary

·         Cloud provided images should have immutable names

·         Label ephemeral drives and swap disks consistently across clouds

·         Enforce consistency in the service catalog across projects
Missing Functionality:

·         Search function with wildcarding for entities within a cloud

·         Automation for API self description (sort of like APINAME –help)

·         Ability to take a “show” or “get” response and pass response to a 
“create” call (piping)

·         support for image aliases

·         Image annotations, both for cloud provider and user

·         Provide information with net addresses as to whether internal to 
cloud only or internet accessible

·         Clarify DHCP APIs and documentation

·         Document config drive – important functionality the currently 
requires reading the code

·         Nested virt

·         Multi-attach read-only volumes

·         Support for master+slave impactless backups
Improve Functionality:

·         Better info/differentiation on custom attributes of images:  
read-only vs user-defined vs ??

·         Create internet attached network with a single API call based on user 
expressible rules/options

·         Move towards Neutron+IPv6 as default networking

·         Default Security groups default needs improvement

·         Improve clarity of which device each volume is attached to

·         Make quota management simpler

·         Horizon: move security groups to networking menus

·         User facing docs on how to use all the varieties of auth and scopes

·         Heat should be able to run on top of clouds (improves consistency and 
interop)

·         Heat support for multi region and multi cloud



________________________________
华为技术有限公司 Huawei Technologies Co., Ltd.
[Company_logo]
Rochelle Grober
Sr. Staff Architect, Open Source
Office Phone:408-330-5472
Email:rochelle.gro...@huawei.com
________________________________
 本邮件及其附件含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中
的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件!
This e-mail and its attachments contain confidential information from HUAWEI, 
which
is intended only for the person or entity whose address is listed above. Any 
use of the
information contained herein in any way (including, but not limited to, total 
or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify 
the sender by
phone or email immediately and delete it!

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to