Open Stack

Resend the information about our problems to the list.

The problem we found is regarding networking part in 2016.08 and probably
also in 2017.01, specifically:

1. networks-l2-CRUD:

   - tempest.api.network.test_ports.PortsTestJSON.test_create_port_with_no_
   securitygroups
   - tempest.api.network.test_ports.PortsTestJSON.test_
   create_show_delete_port_user_defined_mac


*Our problem is that in our public cloud implementation, we mandate that
port creation must have security groups designated, and **at the moment all
the mac address are pre-allocated and not up to the user to define.*


2. volumes_action related rules:

   -
   tempest.api.volume.test_volumes_actions.VolumesV2ActionsTest.test_attach_detach_volume_to_instance
   -
   tempest.api.volume.test_volumes_actions.VolumesV2ActionsTest.test_get_volume_attachment
   -
   tempest.api.volume.test_volumes_actions.VolumesV2ActionsTest.test_reserve_unreserve_volume
   -
   tempest.api.volume.test_volumes_actions.VolumesV2ActionsTest.test_volume_bootable
   -
   tempest.api.volume.test_volumes_actions.VolumesV2ActionsTest.test_volume_readonly_update

*The problem for us is that in our public cloud implementation,
volumes_action related operations are only internally used for inter-module
calls (e.g between Nova and Cinder) or Admin ops, but not for directly
usage by the tenants/users.*


In summary our problems have to do with our public cloud requirements, i'm
not sure if these are reasonable questions for defcore guideline as well as
if these are suit for flagging ?

On Wed, Jan 18, 2017 at 3:46 AM, Chris Hoge <chris at openstack.org> wrote:

> The 2017.01 guideline will be going to the board for final approval
> at the end of this month. 2016.08 is finalized, but problematic
> tests can be flagged. We have our weekly working group
> meetings on Wednesdays, and we’d be happy to consider
> isses as part of our agenda. You can add an agenda item to the
> meeting etherpad:
>
> https://etherpad.openstack.org/p/DefCoreRoble.9
>
> It’s also useful to raise issues on this mailing list to give the wider
> community a chance to comment.
>
> Thanks,
> Chris Hoge
> Interop Engineer
> OpenStack Foundation
>
>
> On Jan 17, 2017, at 6:53 AM, Zhipeng Huang <zhipengh512 at gmail.com> wrote:
>
> Hi team,
>
> Is there still time for us to provide feedback for the 2016.08 defcore
> guideline or it is too late ?
>
> --
> Zhipeng (Howard) Huang
>
> Standard Engineer
> IT Standard & Patent/IT Prooduct Line
> Huawei Technologies Co,. Ltd
> Email: huangzhipeng at huawei.com
> Office: Huawei Industrial Base, Longgang, Shenzhen
>
> (Previous)
> Research Assistant
> Mobile Ad-Hoc Network Lab, Calit2
> University of California, Irvine
> Email: zhipengh at uci.edu
> Office: Calit2 Building Room 2402
>
> OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
> _______________________________________________
> Interop-wg mailing list
> Interop-wg at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/interop-wg
>
>
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Prooduct Line
Huawei Technologies Co,. Ltd
Email: huangzhipeng at huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipengh at uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/interop-wg/attachments/20170119/89852cfb/attachment.html>