Re: [openstack-dev] [all][interop][heat][designate] Proposed updates to OpenStack Powered trademarks: extensions and verticals

[Egle Sigler]

Thank you Chris! We will be discussing these programs in our next weekly 
meeting, on Wednesday, August 16th, 11:00 AM CST/ 16:00 UTC in 
#openstack-meeting-3. Join us if you would like to be part of the discussion, 
and reviews are very welcome!


Thank you,

Egle



From: Chris Hoge 
Sent: Thursday, August 10, 2017 5:30 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [all][interop][heat][designate] Proposed updates 
to OpenStack Powered trademarks: extensions and verticals


> On Aug 10, 2017, at 2:47 PM, Chris Hoge  wrote:
>
> At the upcoming board meeting in September, the Interop Working Group
> will be proposing a new trademark program to supplement the OpenStack
> Powered mark. This update formally defines two distinct types of programs.
>
> 1) Platforms. This captures the three existing trademarks, OpenStack
> Powered Compute, OpenStack Powered Storage, and OpenStack Powered
> Platform. A platform can be thought of as a complete collection of
> OpenStack software to give a core set of functionality. For example,
> OpenStack Powered Storage provides Swift Object Storage and Horizon

Correction to above:
Swift and Keystone. Horizon is not required


> Identity. Compute offers Nova, Horizon, Glance, Cinder and Neutron.

Correction to the above:
Nova, Keystone, Glance, Cinder, and Neutron. Horizon is not required.


>
> We are generalizing the idea of platforms to be able to capture other
> verticals within the OpenStack ecosystem. For example, we are currently
> working with NFV leaders to potentially build out an OpenStack Powered
> NFV guideline that could be used in a future trademark program.
>
> 2) Extensions. This captures projects that provide additional
> functionality to platforms, but require certain core services to be
> available.  The intent is for an OpenStack Powered cloud to be able to
> advertise interoperable capabilities that would be nice for users to
> have but aren't strictly required for general interoperability. The
> first two extensions we are focusing on are Heat Orchestration and
> Designate DNS. If a public cloud were offering the Designate API,
> they could qualify to present themselves as "OpenStack Powered Platform
> with DNS".
>
> We are seeking advisory status from the board at the September board
> meeting, with a goal to launch the new extension programs after the
> January board meeting. The Interop Working Group would also like to
> work with the TC on encouraging more projects to adopt the Interop
> Working Group schema to define what public-facing interfaces and code
> should be present for a deployed instance of that project to qualify
> as interoperable.
>
> If you would like to see the new extension programs, I have reviews
> up for both Heat and Designate.
>
> Heat: https://review.openstack.org/#/c/490648/
Gerrit Code Review
review.openstack.org
ID: Subject: Status: Owner: Project: Branch: Updated: Size: CR: V: W: 491096: 
Add unit tests for dns_domain for ports



> Designate: https://review.openstack.org/#/c/492635/
Gerrit Code Review
review.openstack.org
ID: Subject: Status: Owner: Project: Branch: Updated: Size: CR: V: W: 491096: 
Add unit tests for dns_domain for ports



>
> The new interop guideline schema format is also ready to be presented
> to the board:
>
> 2.0 schema documentation:
>  
> https://git.openstack.org/cgit/openstack/interop/tree/doc/source/schema/2.0.rst
> 2.0 schema example:
>  
> https://git.openstack.org/cgit/openstack/interop/tree/doc/source/schema/next.2.0.json
>
> The review for the 2.0 schema (merged):
>  https://review.openstack.org/#/c/430556/
Gerrit Code Review
review.openstack.org
ID: Subject: Status: Owner: Project: Branch: Updated: Size: CR: V: W: 491096: 
Add unit tests for dns_domain for ports



>
> If you are the PTL of a project that would like to be considered for an
> extension trademark program, please don't hesitate to reach out to me or
> any other member of the Interop Working Group.
>
> We're pretty excited about how we're planning on extending the trademark
> program next year, and are looking forward to working with the developer
> community to help guarantee the interoperability of OpenStack clouds
> through testing and trademark compliance.
>
> Thanks!
>
> Chris Hoge
> Interop Engineer
> OpenStack Foundation
>
>
> __
> 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
openstack-dev mailing list - lists.openstack.org Mailing 
Lists
lists.openstack.org
This list for the 

Re: [openstack-dev] [Interop-wg] [refstack][interop-wg] Non-candidacy for RefStack PTL

[Egle Sigler]

Thank you Catherine for all your outstanding leadership and work on RefStack 
and Interop (defcore).


-Egle



From: Catherine Cuong Diep 
Sent: Wednesday, August 2, 2017 2:15 PM
To: openstack-dev@lists.openstack.org; interop...@lists.openstack.org
Subject: [Interop-wg] [openstack-dev][refstack][interop-wg] Non-candidacy for 
RefStack PTL


Hi Everyone,

As I had announced in the RefStack IRC meeting a few weeks ago, I will not run 
for RefStack PTL in the upcoming cycle. I have been PTL for the last 2 years 
and it is time to pass the torch to a new leader.

I would like to thanks everyone for your support and contribution to make the 
RefStack project and interoperability testing a reality. We would not be where 
we are today without your
commitment and dedication.

I will still be around to help the project and to work with the next PTL for a 
smooth transition.

Catherine Diep

__
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

Re: [openstack-dev] [Interop-wg] [tc][qa][all]Potential New Interoperability Programs: The Current Thinking

[Egle Sigler]

Thank you Mark for writing this up! If you are interested in new interop
programs, please comment on https://review.openstack.org/#/c/472785/.
In addition, we will also be discussing this during our weekly meeting on
Wednesday, 11:00 AM CST/ 16:00 UTC in #openstack-meeting-3. If you cannot
join us for the meeting at that time, find us in #openstack-interop
channel.

Thank you,

Egle

On 6/9/17, 3:55 PM, "Mark Voelker"  wrote:

>Hi Everyone,
>
>Happy Friday!  There have been a number of discussions (at the PTG, at
>OpenStack Summit, in Interop WG and Board of Directors meetings, etc)
>over the past several months about the possibility of creating new
>interoperability programs in addition to the existing OpenStack Powered
>program administered by the Interop Working Group (formerly the DefCore
>Committee).  In particular, lately there have been a lot of discussions
>recently [1] about where to put tests associated with trademark programs
>with respect to some existing TC guidance [2] and community goals for
>Queens [3].  Although these potential new programs have been discussed in
>a number of places, it¹s a little hard to keep tabs on where we¹re at
>with them unless you¹re actively following the Interop WG.  Given the
>recent discussions on openstack-dev, I thought it might be useful to try
>and brain dump our current thinking on what these new programs might look
>like into a document somewhere that people could point at in discussions
>rather than discussing abstracts and working off memories from prior
>meetings.  To that end, I took a first stab at it this week which you can
>find here:
>
>https://review.openstack.org/#/c/472785/
>
>Needless to say this is just a draft to try to get some of the ideas out
>of neurons and on to electrons, so please don¹t take it to be firm
>consensus‹rather consider it a draft of what we¹re currently thinking and
>an invitation to collaborate.  I expect that other members of the Interop
>Working Group will be leaving comments in Gerrit as we hash through this,
>and we¹d love to have input from other folks in the community as well.
>These programs potentially touch a lot of you (in fact, almost all of
>you) in some way or another, so we¹re happy to hear your input as we work
>on evolving the interop programs.  Quite a lot has happened over the past
>couple of years, so we hope this will help folks understand where we came
>from and think about whether we want to make changes going forward.
>
>By the way, for those of you who might find an HTML-rendered document
>easier to read, click on the "gate-interop-docs-ubuntu-xenial² link in
>the comments left by Jenkins and then on ³Extension Programs - Current
>Direction².  Thanks, and have a great weekend!
>
>[1] 
>http://lists.openstack.org/pipermail/openstack-dev/2017-May/thread.html#11
>7657
>[2] 
>https://governance.openstack.org/tc/resolutions/20160504-defcore-test-loca
>tion.html
>[3] 
>https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.htm
>l
>
>At Your Service,
>
>Mark T. Voelker
>___
>Interop-wg mailing list
>interop...@lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/interop-wg


__
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

[openstack-dev] [Interop-wg] Interop/RefStack PTG Agenda

[Egle Sigler]

Hello Everyone,

If you are in Atlanta next week and care about interop, please join us.
Schedule: https://etherpad.openstack.org/p/RefStackInteropWGAtlantaPTG
Thank you,
Egle

On 2/17/17, 3:20 PM, "Mark Voelker"  wrote:

>Hi Folks,
>
>We¹re looking forward to seeing many of you in Atlanta next week!  Please
>take a look at the agenda below:
>
>https://etherpad.openstack.org/p/RefStackInteropWGAtlantaPTG
>
>If you have any last-minute suggestions or changes, please let us know
>ASAP.  Otherwise, safe travels!
>
>At Your Service,
>
>Mark T. Voelker
>___
>Interop-wg mailing list
>interop...@lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/interop-wg


__
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

[openstack-dev] [all] [interop] Name Change: Interop Working Group, formerly known as DefCore Committee

[Egle Sigler]

Hello Everyone,

As you may have already heard, DefCore Committee is changing its name to
Interop Working Group. Why the name change? At the Board of Directors
meeting on April 24, 2016 the Board of
Directors indicated that as DefCore has evolved it's focus on
interoperability and it's working structure, it's name may be a source of
some confusion to those outside of the community or who are new to the
community. The Board made an informal request that the DefCore Committee
consider changing it's name to more clearly reflect it's focus
and structure. The Board then approved the name "Interop Working Group" at
it's August 23, 2016 meeting [1].
Over the last several months we have been working on renaming everything
(you'll see a few more changes coming to our git repo and the
documentation therein in the next few weeks). The change means that we now
have a new mailing list, new IRC channel and renamed wiki.
If you have not done so yet, please subscribe to our new mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/interop-wg
Join us in our IRC channel: #openstack-interop
Wiki has moved to: https://wiki.openstack.org/wiki/Governance/InteropWG

As usual, we will continue holding our weekly meetings on Wedensdays, at
16:00 UTC in #openstack-meeting-3 IRC channel.  Since the meeting name is
changing, you may want to note that logs from past meetings can still be
found at their old location [2] but will be in a new directory going
forward.[3]
Please let us know if you have any questions.

Thank you,
Interop WG chairs Egle Sigler and Mark Voelker

[1] 
https://wiki.openstack.org/wiki/Governance/Foundation/23Aug2016BoardMinutes
[2] http://eavesdrop.openstack.org/meetings/defcore/
[3] http://eavesdrop.openstack.org/meetings/interopwg/


__
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

[openstack-dev] [DefCore][Interop] Fall 2016 OpenStack Interoperability Issues Report

[Egle Sigler]

Hello Everyone,

The DefCore Committee has been working to provide a periodic report on a
tractable, small number of major barriers we have uncovered during the
course of work to the community that we wish to focus
attention on.  The report is intended to be constructive rather than
critical, and assist the community in recognizing barriers to
interoperability so that they can be addressed.

The full report is available here:
https://github.com/openstack/defcore/blob/master/doc/source/periodic_report
s/fall_2016.rst

Our first report covers the following issues:
* Issue 1: Testing Interoperability
https://github.com/openstack/defcore/blob/master/doc/source/periodic_report
s/fall_2016.rst#issue-1-testing-interoperability
* Issue 2: Varying Models for API Evolution
https://github.com/openstack/defcore/blob/master/doc/source/periodic_report
s/fall_2016.rst#issue-2-varying-models-for-api-evolution
* Issue 3: External Network Connectivity
https://github.com/openstack/defcore/blob/master/doc/source/periodic_report
s/fall_2016.rst#issue-3-external-network-connectivity
* Issue 4: API and Policy Discoverability
https://github.com/openstack/defcore/blob/master/doc/source/periodic_report
s/fall_2016.rst#issue-4-api-and-policy-discoverability
* Issue 5: Lack of Clarity on DefCore's Purpose and Abilities
https://github.com/openstack/defcore/blob/master/doc/source/periodic_report
s/fall_2016.rst#issue-5-lack-of-clarity-on-defcore-s-purpose-and-abilities


Please let us know if you have any questions about the report.

If you are attending OpenStack Summit in Barcelona, please join us for
DefCore and RefStack sessions:

* Interop (DefCore) Working Group Work Session: Tuesday, October 25,
2:15pm-2:55pm, AC Hotel - P14 - Pedralbes,
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/1679
8
* OpenStack Interoperability Challenge: Running Unmodified Apps in Any
OpenStack Cloud, Wednesday, October 26, 9:25am-9:35am, Keynote stage,
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/1736
2
* RefStack Work Sessions  Wednesday, Octover 26, 5:05 - 5:45 pm, 5:55 -
6:35 pm,  AC Hotel - P3 - Gràcia ,
https://etherpad.openstack.org/p/refstack-ocata-summit
* Interop? You Keep Using That Word, I Do Not Think It Means What You
Think It Means. Thursday, October 27, 9:50am-10:30am, CCIB - Centre de
Convencions Internacional de Barcelona - P1 - Room 117,
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/1633
9
* Beyond Refstack: The Interop Challenge. Thursday, October 27,
11:00am-11:40am, Hilton Diagonal Mar - P0 - Ballroom A.
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/1641
2
* Heat: Work Session (DefCore related) Friday, October 28,
11:00am-11:40am, AC Hotel - P3 - Gràcia,
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/1706
3

Thank you,
Egle Sigler








__
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

Re: [openstack-dev] [interop][defcore][ptl] Intro to creating next Interop (DefCore) guideline

[Egle Sigler]

Hello Everyone,

Thanks everyone for tuning into presentation by Chris Hoge on how the next 
interop guideline is created. If you missed the session, here is the recording:
<https://www.youtube.com/watch?v=kDn4jj0iSK8=youtu.be=260>https://www.youtube.com/watch?v=kDn4jj0iSK8=youtu.be=260

Slides from the presentation: 
https://docs.google.com/presentation/d/1DqhUD4jdc8Cvmcid215age1AAp-K0xyqYHvgr45hWYE/edit?usp=sharing

Please let us know if you have any questions on 
defcore-commit...@lists.openstack.org<mailto:defcore-commit...@lists.openstack.org>
 mailing list or #openstack-defcore IRC channel.

Thank you,
Egle

From: Egle Sigler <egle.sig...@rackspace.com<mailto:egle.sig...@rackspace.com>>
Date: Wednesday, September 7, 2016 at 8:52 PM
To: openstack-dev 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
"defcore-commit...@lists.openstack.org<mailto:defcore-commit...@lists.openstack.org>"
 
<defcore-commit...@lists.openstack.org<mailto:defcore-commit...@lists.openstack.org>>
Subject: [interop][defcore][ptl] Intro to creating next Interop (DefCore) 
guideline

Hello Everyone,

Interop Working Group (aka DefCore Committee) is starting to work on the next 
guideline. The next guideline will be published on 2017.01, but before then, we 
need to evaluate and score additional components to see if they should be added 
to the guideline. What is scoring? How does a component get added to the 
guideline? Will your favorite project be added to the next guideline? We are 
going to have a google hangout session on Friday and Chris Hoge will answer all 
these questions. The session will be recorded, so if you are not able to attend 
it, you can watch it later.

Event Page: https://plus.google.com/events/cuejgn5k8keg0j0c11qi3k4j15c
YouTube page: http://www.youtube.com/watch?v=kDn4jj0iSK8

Reading list for those that would like to prepare questions ahead of time:

  *   Hacking: https://github.com/openstack/defcore/blob/master/HACKING.rst

  *   Scoring: 
https://github.com/openstack/defcore/blob/master/working_materials/scoring.txt

  *   Lexicon: 
https://github.com/openstack/defcore/blob/master/doc/source/process/Lexicon.rst

  *   Core Criteria: 
https://github.com/openstack/defcore/blob/master/doc/source/process/CoreCriteria.rst

  *   Core Definition: 
https://github.com/openstack/defcore/blob/master/doc/source/process/CoreDefinition.rst

  *   Designated Sections: 
https://github.com/openstack/defcore/blob/master/doc/source/process/DesignatedSections.rst

As always, we are available to answer questions on #openstack-defcore IRC 
channel or 
defcore-commit...@lists.openstack.org<mailto:defcore-commit...@lists.openstack.org>
 mailing list.

Thank you,
Egle Sigler
__
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

[openstack-dev] [interop][defcore][ptl] Intro to creating next Interop (DefCore) guideline

[Egle Sigler]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Central Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Egle Sigler:MAILTO:egle.sig...@rackspace.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=openstack
 -dev:MAILTO:openstack-dev@lists.openstack.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=defcore-c
 ommit...@lists.openstack.org:MAILTO:defcore-commit...@lists.openstack.org
DESCRIPTION;LANGUAGE=en-US:Hello Everyone\,\n\n\nInterop Working Group (aka
  DefCore Committee) is starting to work on the next guideline. The next gu
 ideline will be published on 2017.01\, but before then\, we need to evalua
 te and score additional components to see if they should be added to the g
 uideline. What is scoring? How does a component get added to the guideline
 ? Will your favorite project be added to the next guideline? We are going 
 to have a google hangout session on Friday and Chris Hoge will answer all 
 these questions. The session will be recorded\, so if you are not able to 
 attend it\, you can watch it later.\n\n\nEvent Page: https://plus.google.c
 om/events/cuejgn5k8keg0j0c11qi3k4j15c\nYouTube page: http://www.youtube.co
 m/watch?v=kDn4jj0iSK8\n\n\nReading list for those that would like to prepa
 re questions ahead of time:\n   *   Hacking: https://github.com/openstack/
 defcore/blob/master/HACKING.rst\n   *   Scoring: https://github.com/openst
 ack/defcore/blob/master/working_materials/scoring.txt\n   *   Lexicon: htt
 ps://github.com/openstack/defcore/blob/master/doc/source/process/Lexicon.r
 st\n   *   Core Criteria: https://github.com/openstack/defcore/blob/master
 /doc/source/process/CoreCriteria.rst\n   *   Core Definition: https://gith
 ub.com/openstack/defcore/blob/master/doc/source/process/CoreDefinition.rst
 \n   *   Designated Sections: https://github.com/openstack/defcore/blob/ma
 ster/doc/source/process/DesignatedSections.rst\n\n\nAs always\, we are ava
 ilable to answer questions on #openstack-defcore IRC channel or defcore-co
 mmit...@lists.openstack.org mailing list.\n\n\nThank you\,\nEgle Sigler\n
SUMMARY;LANGUAGE=en-US:[interop][defcore][ptl] Intro to creating next Inter
 op (DefCore) guideline
DTSTART;TZID=Central Standard Time:20160909T13
DTEND;TZID=Central Standard Time:20160909T14
UID:17DF4CD1-46F2-4038-BE81-DA5CB24F095F
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20160908T015254Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:Google Hangout
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2114534223
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR
__
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

Re: [openstack-dev] [glance][tempest][defcore] Process to imrpove tests coverge in temepest

[Egle Sigler]

Thank you Flavio for bringing this up! We are using tempest tests for
DefCore testing, and we would like to work with anyone willing to increase
coverages in any of the current covered capabilities. We would also like
to hear from the teams when they are planning on removing, changing, or
renaming tests, as that could affect what DefCore tests.

Upcoming DefCore guidelines and tests:
https://github.com/openstack/defcore/blob/master/2016.01.json

Thank you,
Egle

On 12/8/15, 1:25 PM, "Flavio Percoco"  wrote:

>Greetings,
>
>I just reviewed a patch in tempest that proposed adding new tests for
>the Glance's task API. While I believe it's awesome that folks in the
>tempest team keep adding missing tests for projects, I think it'd be
>better for the tempest team, the project's team and defcore if we'd
>discuss these tests before they are worked on. This should help people
>avoid wasting time.
>
>I believe these cases are rare but the benefits of discussing missing
>tests across teams could also help prioritizing the work based on what
>the teams goals are, what the defcore team needs are, etc.
>
>So, I'd like to start improving this process by inviting folks from
>the tempest team to join project's meeting whenever new tests are
>going to be worked on.
>
>I'd also like to invite PTLs (or anyone, really) from each team to go
>through what's in tempest and what's missing and help this team
>improve the test suite. Remember that these tests are also used by the
>defcore team and they are not important just for the CI but have an
>impact on other areas as well.
>
>I'm doing the above for Glance and I can't stress enough how important
>it is for projects to do the same.
>
>Do teams have a different workflow/process to increase tests coverage
>in tempest?
>
>Cheers,
>Flavio
> 
>-- 
>@flaper87
>Flavio Percoco
>
>__
>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


__
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

[openstack-dev] [DefCore] Request for comments: Is booting Linux VM required for OpenStack interoperability?

[Egle Sigler]

Hello Everyone,

DefCore committee would like to hear your input on this issue: 
https://review.openstack.org/#/c/244782/
The issue is not really vendor specific. At the heart of the issue is this 
question: for interoperability reasons, should certified OpenStack powered 
compute clouds be able to boot a Linux VM? And if so, would OpenStack based 
clouds running only Linux based containers be excluded? How about bare metal 
clouds?

Please comment, and let me know if you have any questions.


Thank you,

Egle Sigler

DefCore Committee Co-Chair


DefCore sets base requirements by defining 1) capabilities, 2) code and 3) 
must-pass tests for all OpenStack products. This definition uses community 
resources and involvement to drive interoperability by creating the minimum 
standards for products labeled "OpenStack."

Our mission is to define "OpenStack Core" as chartered by the by-laws.

How to get involved in DefCore:

Join the mailing list: 
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee

Find us on IRC (chat.freenode.net): #openstack-defcore

Submit, review, comment: 
https://review.openstack.org/#/q/status:open+project:openstack/defcore,n,z

Join our weekly meetings on IRC: 
https://wiki.openstack.org/wiki/Governance/DefCoreCommittee#Meetings


New to DefCore?  Some pointers:

Intro to DefCore with heavy references to Dr. Who 
http://www.slideshare.net/markvoelker/defcore-the-interoperability-standard-for-openstack-53040869

DefCore 101 Tokyo presentation and slides: 
https://www.youtube.com/watch?v=MfUAuObSkK8  
http://www.slideshare.net/rhirschfeld/tokyo-defcore-presentation

Wiki: https://wiki.openstack.org/wiki/DefCore

Hacking file: https://github.com/openstack/defcore/blob/master/HACKING.rst


__
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

[openstack-dev] [DefCore] Request for reviews and comments for 2016.01 DefCore (interop) guideline

[Egle Sigler]

Hello OpenStack Community,


The DefCore guideline for 2016.01 is now up for review, and we need your 
feedback. Please review and comment: https://review.openstack.org/#/c/239830/


At this time, we need feedback for capabilities that will become advisory in 
2016.01 and required in 2016.07:


"advisory": [
   "networks-l3-router",
   "networks-l2-CRUD",
   "networks-l3-CRUD",
   "networks-security-groups-CRUD",
   "compute-list-api-versions",
   "images-v2-remove",
   "images-v2-update",
   "images-v2-share",
   "images-v2-import",
   "images-v2-list",
   "images-v2-delete",
   "images-v2-get",
   "volumes-v2-create-delete",
   "volumes-v2-attach-detach",
   "volumes-v2-snapshot-create-delete",
   "volumes-v2-get",
   "volumes-v2-list",
   "volumes-v2-update",
   "volumes-v2-copy-image-to-volume",
   "volumes-v2-copy-volume-to-image",
   "volumes-v2-clone",
   "volumes-v2-qos",
   "volumes-v2-availability-zones",
   "volumes-v2-extensions",
   "volumes-v2-metadata",
   "volumes-v2-transfer",
   "volumes-v2-reserve",
   "volumes-v2-readonly",
   "identity-v3-api-discovery"
 ],


Each of these capabilities have Tempest tests associated with them. Please 
review and provide feedback. At this point, we can only remove advisory 
capabilities, and not others.


How to get involved in DefCore:

Join the mailing list: 
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee

Find us on IRC (chat.freenode.net): #openstack-defcore

Submit, review, comment: 
https://review.openstack.org/#/q/status:open+project:openstack/defcore,n,z

Join our weekly meetings on IRC: 
https://wiki.openstack.org/wiki/Governance/DefCoreCommittee#Meetings


New to DefCore?  Some pointers:

Intro to DefCore with heavy references to Dr. Who 
http://www.slideshare.net/markvoelker/defcore-the-interoperability-standard-for-openstack-53040869

DefCore 101 Tokyo presentation and slides: 
https://www.youtube.com/watch?v=MfUAuObSkK8  
http://www.slideshare.net/rhirschfeld/tokyo-defcore-presentation

Wiki: https://wiki.openstack.org/wiki/DefCore

Hacking file: https://github.com/openstack/defcore/blob/master/HACKING.rst


Please let me know if you have any questions!

Thank you,

Egle Sigler

DefCore Committee Co-Chair


__
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