[OpenStack-DefCore] Fw: Draft 2015.03 Spec

Catherine Cuong Diep cdiep at us.ibm.com
Sat Feb 28 19:18:11 UTC 2015


Hello,

Totally agree with your observation.  The Refstack team has identified 9
tests that are currently included in the havanacore.json as must-pass tests
and needed review.  The 9 tests are listed in the "Tests Required SSH to
VM", "Tests Skipped with Tempest Identified Bugs " and "Set VM Admin
Password Test " sections  in this document
https://docs.google.com/document/d/12GUhUphBSzPuQqp7WreZ-DXaINnUWSrYAYb4CyPmpAw/edit#

More important,   at the time when we create the test list associated with
the capabilities included  the 2015.03 spec,  we will need to carefully
review the individual test  to exclude the tests that are skipped because
of either Tempest identified bugs or tests that would mostly not pass when
testing a public cloud.

Catherine Cuong Diep
High Performance On Demand Solutions
IBM Silicon Valley Laboratory, San Jose, California 95141
cdiep at us.ibm.com, Tel: (408) 463-4352  T/L: 543-4352
----- Forwarded by Catherine Cuong Diep/San Jose/IBM on 02/28/2015 10:08 AM
-----

From:	Justin Shepherd <jshepher at rackspace.com>
To:	Van Lindberg <van.lindberg at RACKSPACE.COM>
Cc:	Catherine Cuong Diep/San Jose/IBM at IBMUS, Egle Sigler
            <egle.sigler at rackspace.com>,
            "defcore-committee at lists.openstack.org"
            <defcore-committee at lists.openstack.org>, Adrian Otto
            <adrian.otto at rackspace.com>
Date:	02/27/2015 09:12 PM
Subject:	Re: [OpenStack-DefCore] Draft 2015.03 Spec



Had two questions about two of the tests under the compute-servers
capability.

The following test is listed, however this feature is not implemented for
most hypervisors. And per developer documentation is "not considered
mandatory for drivers to support":

“tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_change_server_password"
http://docs.openstack.org/developer/nova/support-matrix.html#operation_set_admin_password

-----

The following test is listed, however this feature is skipped when neutron
is being used:

"tempest.api.compute.servers.test_list_server_filters.ListServerFiltersTestJSON.test_list_servers_filtered_by_ip_regex"
https://github.com/openstack/tempest/blob/master/tempest/api/compute/servers/test_list_server_filters.py#L297-L313
https://bugs.launchpad.net/tempest/+bug/1182883

—shep

      On Feb 27, 2015, at 3:42 PM, Van Lindberg <van.lindberg at rackspace.com
      > wrote:

      Thanks, didn't see that.

      From: Catherine Cuong Diep <cdiep at us.ibm.com>
      Date: Friday, February 27, 2015 at 1:13 PM
      To: Van Lindberg <van.lindberg at rackspace.com>
      Cc: "defcore-committee at lists.openstack.org" <
      defcore-committee at lists.openstack.org>, Egle Sigler <
      egle.sigler at rackspace.com>, Adrian Otto <adrian.otto at rackspace.com>,
      Rob Hirschfeld <rob at zehicle.com>
      Subject: Fw: [OpenStack-DefCore] Draft 2015.03 Spec



      Hello Van,

      The reason why compute-servers-metadata does not exist in havanacore
      is because this capability was merged into the computer-servers
      capability (please see the "Proposed Final Naming/Mapping" tab in
      http://goo.gl/AwaJYU).  All compute-servers-metadata related tests
      were, in fact, included in the compute-servers capability and are
      classified as "core" tests in the havancore.json.

      Catherine Cuong Diep
      High Performance On Demand Solutions
      IBM Silicon Valley Laboratory, San Jose, California 95141
      cdiep at us.ibm.com, Tel: (408) 463-4352  T/L: 543-4352

      >>>> On Feb 25, 2015, at 3:11 PM, Van Lindberg
      >>>> <van.lindberg at rackspace.com> wrote:
      >>>>
      >>>> Should we forward this on to the board?
      >>>>
      >>>> From: Van Lindberg <van.lindberg at rackspace.com> Date:
      >>>> Wednesday, February 25, 2015 at 1:51 PM To:
      >>>> "defcore-committee at lists.openstack.org"
      >>>> <defcore-committee at lists.openstack.org> Cc: Egle Sigler
      >>>> <egle.sigler at rackspace.com>, Adrian Otto
      >>>> <adrian.otto at rackspace.com> Subject: [OpenStack-DefCore]
      >>>> Draft 2015.03 Spec
      >>>>
      >>>> Hello all
      >>>>
      >>>> Per the discussion today and at the face to face meeting last
      >>>> week, we have the following draft 2015.03 spec for comments
      >>>> and approval:
      >>>>
      >>>> https://etherpad.openstack.org/p/defcore-draft-spec-2015.03
      >>>>
      >>>> Notes: - There are two advisory sections: auth-token (which
      >>>> we created a placeholder for) and compute-servers-metadata
      >>>> (which didn’t exist in havanacore, but was in icehousecore).
      >>>> Because the point of this doc is “havanacore - anything
      >>>> possibly troublesome,” we suggested moving
      >>>> compute-servers-metadata to advisory for action in 2015.04. -
      >>>> This is .rst formatted and designed for human consumption.
      >>>> There is a linked (and also authoritative) .json file for
      >>>> machine consumption. - The .json file (draft in gdoc for easy
      >>>> multi-editing right now) has everything that is not mandatory
      >>>> or advisory removed. - We updated the versioning of the .json
      >>>> file (to 1.1), removed “status” from the top-level, and added
      >>>> “advisory” flags for those two items that were advisory. We
      >>>> also updated “core” to false for the two advisory items. - We
      >>>> need designated sections for keystone.
      >>>>
      >>>> Thanks, Van
      >>>>
      >>>> _______________________________________________
      >>>> Defcore-committee mailing list
      >>>> Defcore-committee at lists.openstack.org
      >>>>
      http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
      >>>
      >>>
      >>>>
      _______________________________________________
      >>> Defcore-committee mailing list
      >>> Defcore-committee at lists.openstack.org
      >>>
      http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
      >
      >>>
      >
      >
      > _______________________________________________ Defcore-committee
      > mailing list Defcore-committee at lists.openstack.org
      >
      http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
      >


      _______________________________________________
      Defcore-committee mailing list
      Defcore-committee at lists.openstack.org
      http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee

      -----BEGIN PGP SIGNATURE-----
      Comment: GPGTools - https://gpgtools.org

      iQIcBAEBCgAGBQJU8LNIAAoJELUJLUWGN7CbM1YQALLsk6qLWQib7gj8HCXYGLrw
      oJHIt9hnz24BBlsY2gIiVUkqLrO7kEJUvqynFAxbwnyUSAKihPeSqa0VHd/MchId
      BjRo/xqm+Ghhu3fWOBMJj1eIEjLYpQIjpu5ZRN+FgF6N+bYQx93Z+R/cKmcueVce
      mL9pt25gcCGGBzjAXlCzcdgsTm4i9eShr36/n8reAUmECl5ssULyEJsL174KKhdV
      g/uIuhDfuOG3e7JeGTLurrvyy6FMs9BLjZmFdBd8yqfFdYNfWFhmremx6wNd+pcQ
      DhQrTwV4sk4HbOeQw4/ijomf8ahCeeCCnpLshg4YHgAP8OU6XoU03uJROuby+bJS
      pmrSwVLA/2HmFdXW5/91KonQnJpxcxHH8FtlSTSAfoeC7JmKrEQ/ZkfvPBktCLPa
      FiR/TwQnRvXADehV4Q3by13ffga2cEk4q0O3mRZHRC2THc8+/7fy5shx7Vsi4ivS
      ANDg2GRufby2+Yf7zKtj4gvs8Lq1/lvekILqaUShkc/tYFpn4dYnrNsz4/MUWNBS
      1froKJu4IKKl9KNdjybxImMUHE/E4ATixNQdd5BJL7tfQMMWf7TqItsWh+KiYUlY
      jP551y8mswi5DZLvocyl4/DwZGqs/eWXM4F+SPGe4udFQu2ZrkFhrLSqDAWW49Xf
      PcykTtpGFByCA2sI7z87
      =yHhx
      -----END PGP SIGNATURE-----
      _______________________________________________
      Defcore-committee mailing list
      Defcore-committee at lists.openstack.org
      http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee


      _______________________________________________
      Defcore-committee mailing list
      Defcore-committee at lists.openstack.org
      http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/defcore-committee/attachments/20150228/b285e33d/attachment-0001.html>


More information about the Defcore-committee mailing list