[openstack-dev] [defcore] Proposal for new openstack/defcore repository

to help define the new capabilities with an eye towards interoperability across the entire OpenStack ecosystem. The creation of this repository is an important step in that direction. Thanks, Chris Hoge Interop Engineer OpenStack Foundation [1] https://etherpad.openstack.org/p/DefCoreScale.4 [2

Re: [openstack-dev] [tempest] UUID Tagging Requirement and Big Bang Patch

This work has landed. New tests will now be gated against existence of an idempotent_id. If you have open submissions to Tempest there’s a good possibility you’ll have to rebase. -Chris On Feb 26, 2015, at 2:30 PM, Chris Hoge chris+openstack...@openstack.org wrote: Update

[openstack-dev] [tempest] UUID Tagging Requirement and Big Bang Patch

is meant to give a stable point of reference to tests that will persist through test refactoring and moving. Thanks, Chris Hoge Interop Engineer OpenStack Foundation __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [tempest] UUID Tagging Requirement and Big Bang Patch

refactoring tests, please preserve the id value so that various projects (Defcore, Refstack, Rally) can track the actual location of tests for capability testing. Thanks, Chris Hoge Interop Engineer OpenStack Foundation On Feb 22, 2015, at 11:47 PM, Chris Hoge chris+openstack...@openstack.org

[openstack-dev] [defcore] Scoring for DefCore 2016.01 Guideline

The DefCore Committee is working on scoring capabilities for the upcoming 2016.01 Guideline, a solid draft of which will be available at the Mitaka summit for community review and will go to the Board of Directors for approaval in Janaury [1]. The current 2015.07 Guideline [2] covers Nova, Swift,

Re: [openstack-dev] [cinder][neutron][all] New third-party-ci testing requirements for OpenStack Compatible mark

> third-party CI systems to use to validate they work with a release. > > [1] https://etherpad.openstack.org/p/YVR-neutron-third-party-ci-liberty > <https://etherpad.openstack.org/p/YVR-neutron-third-party-ci-liberty> > > On Sun, Sep 27, 2015 at 11:39 AM, Armando M. <a

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

> On Sep 29, 2015, at 1:07 AM, Flavio Percoco wrote: > > On 28/09/15 16:29 -0400, Doug Hellmann wrote: >> Excerpts from Mark Voelker's message of 2015-09-28 19:55:18 +: >>> On Sep 28, 2015, at 9:03 AM, Doug Hellmann wrote: >>> > >>> > Excerpts from

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

> On Sep 25, 2015, at 6:59 AM, Doug Hellmann wrote: > > Excerpts from Mark Voelker's message of 2015-09-25 01:20:04 +: >>> >>> On Sep 24, 2015, at 5:55 PM, Sabari Murugesan wrote: >>> >>> Hi Melanie >>> >>> In general, images created by

[openstack-dev] [cinder][neutron][all] New third-party-ci testing requirements for OpenStack Compatible mark

is program, and are also happy to answer any questions you might have. Thanks! Chris Hoge Interop Engineer OpenStack Foundation __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-d

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

> On Sep 25, 2015, at 10:12 AM, Andrew Laski wrote: > > I understand that reasoning, but still am unsure on a few things. > > The direction seems to be moving towards having a requirement that the same > functionality is offered in two places, Nova API and Glance V2 API.

[openstack-dev] [tc] Request for comment on requiring running Linux as DefCore capability

issue and possible actions, and is requesting review and comment from the community, Board[3], and Technical Committee. The DefCore committee would like to bring this topic for formal discussion to the next TC meeting on December 8 to get input from TC on this issue. Thanks, Chris Hoge [1]

[openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

properties in responses are ignored and do not break existing client functionality. There is currently little to no harm done to downstream users by temporarily allowing additional data to be returned in responses. Thanks, Chris Hoge Interop Engineer OpenStack Foundation [1] https://specs.openstack.org

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

> On Jun 14, 2016, at 11:21 AM, Matthew Treinish <mtrein...@kortar.org> wrote: > > On Tue, Jun 14, 2016 at 10:57:05AM -0700, Chris Hoge wrote: >> Last year, in response to Nova micro-versioning and extension updates[1], >> the QA team added strict API schema ch

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

> On Jun 14, 2016, at 3:59 PM, Edward Leafe wrote: > > On Jun 14, 2016, at 5:50 PM, Matthew Treinish wrote: > >> But, if we add another possible state on the defcore side like conditional >> pass, >> warning, yellow, etc. (the name doesn't matter) which

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

> On Jun 20, 2016, at 5:10 AM, Sean Dague <s...@dague.net> wrote: > > On 06/14/2016 07:19 PM, Chris Hoge wrote: >> >>> On Jun 14, 2016, at 3:59 PM, Edward Leafe <e...@leafe.com> wrote: >>> >>> On Jun 14, 2016, at 5:50 PM, Matthew Treinish

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

> On Jun 22, 2016, at 11:24 AM, Sean Dague <s...@dague.net> wrote: > > On 06/22/2016 01:59 PM, Chris Hoge wrote: >> >>> On Jun 20, 2016, at 5:10 AM, Sean Dague <s...@dague.net >>> <mailto:s...@dague.net>> wrote: >>> >>>

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

of 2016-06-14 14:21:27 -0400: >>>>> On Tue, Jun 14, 2016 at 10:57:05AM -0700, Chris Hoge wrote: >>>>>> Last year, in response to Nova micro-versioning and extension updates[1], >>>>>> the QA team added strict API schema checking to

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

> On Jun 20, 2016, at 6:56 AM, Doug Hellmann wrote: > > > I'm also, I think, edging away from the "we need to find a compromise" > camp into the "why is this turning into such a big deal" camp. How did > we get into a situation where the community has set a clear

Re: [openstack-dev] [glance] [defcore] [interop] Proposal for a virtual sync dedicated to Import Refactor May 26th

+1 > On May 23, 2016, at 8:25 PM, Mike Perez wrote: > >> On 18:00 May 20, Nikhil Komawar wrote: >> Hello all, >> >> >> I want to propose having a dedicated virtual sync next week Thursday May >> 26th at 1500UTC for one hour on the Import Refactor work [1] ongoing in >>

Re: [openstack-dev] [deployment][kolla][openstack-helm] OpenStack on Helm Workgroup Meeting

Correction, the time is February 28 at 18:30 UTC/10:30 PT, zoom room https://deis.zoom.us/j/668276583 My sincere apologies for the error. > On Feb 27, 2017, at 11:45 AM, Chris Hoge <ch...@openstack.org> wrote: > > We will be holding an OpenStack on Helm Workgroup meeting on Tues

[openstack-dev] [deployment][kolla][openstack-helm] OpenStack on Helm Workgroup Meeting

We will be holding an OpenStack on Helm Workgroup meeting on Tuesday, February 28 at 19:30 UTC/11:30 PT. On the agenda will be the transition of the meeting from an informal working group to the kubernetes-sig-openstack efforts, with a proposal to seed the applications side of the sig-openstack

Re: [openstack-dev] [deployment][TripleO][kolla][ansible][fuel] Next steps for cross project collaboration

> > On Feb 27, 2017, at 8:02 AM, Steven Hardy wrote: > > Hi all, > > Over the recent PTG, and previously at the design summit in Barcelona, > we've had some productive cross-project discussions amongst the various > deployment teams. > > It's clear that we share many common

Re: [openstack-dev] [kubernetes][go] External OpenStack Cloud Provider for Kubernetes

On Friday, March 24, 2017 at 8:46:42 AM UTC-7, Antoni Segura Puimedon wrote: > > > > On Friday, March 24, 2017 at 3:59:18 PM UTC+1, Graham Hayes wrote: >> >> On 24/03/17 10:27 -0400, Davanum Srinivas wrote: >> >Folks, >> > >> >As discussed in the etherpad: >>

Re: [openstack-dev] [kubernetes][go] External OpenStack Cloud Provider for Kubernetes

> On Apr 2, 2017, at 4:16 PM, Monty Taylor <mord...@inaugust.com> wrote: > > On 04/02/2017 02:53 PM, Chris Hoge wrote: >> Now that the provider has a repository in the OpenStack project >> namespace, we need to move over the existing set of issues and pull >> re

Re: [openstack-dev] [kubernetes][go] External OpenStack Cloud Provider for Kubernetes

> On Apr 2, 2017, at 4:29 PM, Monty Taylor <mord...@inaugust.com> wrote: > > On 03/29/2017 03:39 PM, Steve Gordon wrote: >> - Original Message - >>> From: "Davanum Srinivas" <dava...@gmail.com> >>> To: "Chris Hoge"

Re: [openstack-dev] [kubernetes][go] External OpenStack Cloud Provider for Kubernetes

Now that the provider has a repository in the OpenStack project namespace, we need to move over the existing set of issues and pull requests and create an initial work list for migrating patches and fixing existing issues. I've started up an etherpad where we can track that work[1]. In the longer

Re: [openstack-dev] Affected by OSIC, Layoffs? Or want to help?

I would also like to donate a domestic round trip flight or an international one way. -Chris > On Apr 21, 2017, at 11:36 AM, Lauren Sell wrote: > > Hi everyone, > > The Foundation wants to help any Stackers affected by recent layoffs such as > OSIC get to the Boston

Re: [openstack-dev] [deployment][kolla][openstack-helm]k8s-sig-openstack meeting

Of course, US daylight savings bug bit. Please consider 18:30 UTC the official time. We will work out scheduling at the meeting. > On Mar 13, 2017, at 10:36 AM, Chris Hoge <ch...@openstack.org> wrote: > > Tomorrow, March 14 at 18:30 UTC/10:30 PT, we will be holding the new > ex

[openstack-dev] [deployment][kolla][openstack-helm]k8s-sig-openstack meeting

Tomorrow, March 14 at 18:30 UTC/10:30 PT, we will be holding the new extension to the k8s-sig-openstack meeting. This bi-weekly meeting will focus on Kubernetes as an deployment platform for OpenStack. This includes using Helm for orchestration. For this meeting, use the zoom id:

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

ited 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

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 <ch...@openstack.org> 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 disti

Re: [openstack-dev] [refstack][interop-wg] Candidacy for RefStack PTL

into the larger ecosystem. With many of the features of RefStack complete, we will investigate the possibility of moving the project into a mainteance state under the governance of the Interop Working Group. Thank you, Chris Hoge Interop Engineer OpenStack Foundation > On Aug 2, 2017, at 12:15 PM, Cather

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

> On Jun 21, 2017, at 2:35 PM, Jeremy Stanley wrote: > > On 2017-06-21 13:52:11 -0500 (-0500), Lauren Sell wrote: > [...] >> To make this actionable...Github is just a mirror of our >> repositories, but for better or worse it's the way most people in >> the world explore

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

> On Jun 15, 2017, at 5:57 AM, Thierry Carrez wrote: > > Sean Dague wrote: >> [...] >> I think those are all fine. The other term that popped into my head was >> "Friends of OpenStack" as a way to describe the openstack-hosted efforts >> that aren't official projects. It

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

> On Jun 21, 2017, at 9:20 AM, Clark Boylan <cboy...@sapwetik.org> wrote: > > On Wed, Jun 21, 2017, at 08:48 AM, Dmitry Tantsur wrote: >> On 06/19/2017 05:42 PM, Chris Hoge wrote: >>> >>> >>>> On Jun 15, 2017, at 5:57 AM, Thierry Carrez &

Re: [openstack-dev] [k8s][deployment][kolla-kubernetes][magnum][kuryr][qa][api] Proposal for SIG-K8s

Link to the etherpad for the upcoming meeting. https://etherpad.openstack.org/p/queens-ptg-sig-k8s <https://etherpad.openstack.org/p/queens-ptg-sig-k8s> > On Sep 14, 2017, at 10:23 AM, Chris Hoge <ch...@openstack.org> wrote: > > This Friday, September 15 at the P

[openstack-dev] [k8s][deployment][kolla-kubernetes][magnum][kuryr][qa][api] Proposal for SIG-K8s

This Friday, September 15 at the PTG we will be hosting an organizational meeting for SIG-K8s. More information on the proposal, meeting time, and remote attendance is in the openstack-sigs mailing list [1]. Thanks, Chris Hoge Interop Engineer OpenStack Foundation [1] http://lists.openstack.org

[openstack-dev] Fwd: [k8s][deployment][kolla-kubernetes][magnum][kuryr][qa][api] Proposal for SIG-K8s

ney-forum-topics> https://wiki.openstack.org/wiki/Forum/Sydney2017 <https://wiki.openstack.org/wiki/Forum/Sydney2017> PTG got me a little behind on this. Thanks, Chris > Begin forwarded message: > > From: Chris Hoge <ch...@openstack.org> > Subject: [openstack-d

[openstack-dev] [refstack] October 17, 2017 RefStack meeting cancelled

The October 17, 2017 RefStack meeting is cancelled. Our next team meeting will be held on October 24, 2017. -Chris __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [ptg][interop][refstack][all][ironic][cinder]RefStack and Interop WG PTG Agenda

> On Sep 4, 2017, at 1:04 AM, Dmitry Tantsur <dtant...@redhat.com> wrote: > > On 09/01/2017 07:07 PM, Chris Hoge wrote: >> The RefStack and Interop WG teams will host a small work room on Monday >> and Tuesday at the PTG. We would like for projects interested

[openstack-dev] [refstack] RefStack Meeting time change

At the previous RefStack meeting, the team unanimously decided to move our weekly meeting from Tuesdays at 19:00 UTC to Tuesdays at 17:00 UTC in #openstack-meeting-alt. [1][2] Thanks Chris [1] http://eavesdrop.openstack.org/meetings/refstack/2017/refstack.2017-09-26-19.00.log.html#l-58 [2]

Re: [openstack-dev] [k8s][deployment][kolla-kubernetes][magnum][kuryr][zun][qa][api] Proposal for SIG-K8s

working with Kubernetes in OpenStack. Sincerely, -Chris > > Best regards, > Hongbin > > From: Chris Hoge [mailto:ch...@openstack.org] > Sent: September-15-17 12:25 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev]

[openstack-dev] [ptg][interop][refstack][all]RefStack and Interop WG PTG Agenda

The RefStack and Interop WG teams will host a small work room on Monday and Tuesday at the PTG. We would like for projects interested in the interop guideline expansion to participate in guiding the development of future guidelines. The draft schedule focuses on Interop work for Monday, and

Re: [openstack-dev] [all][sdk] Integrating OpenStack and k8s with a service broker

Hi Zane, Do you think this effort would make sense as a subproject within the Cloud Provider OpenStack repository hosted within the Kubernetes org? We have a solid group of people working on the cloud provider, and while it’s not the same code, it’s a collection of the same expertise and test

[openstack-dev] [refstack][ptl] PTL Candidacy for Rocky

to the Tempest Autoconfig team, as this project is where the majority of future work is going to happen. Thank you, Chris Hoge __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ

[openstack-dev] [k8s] openstack-sig-k8s planning for Dublin

sig-k8s has a block of room time put aside for the Dublin PTG. I’ve set up a planning etherpad for work and discussion topics[1]. High priority items include: * openstack provider breakout [2] * provider testing * documentation updates Please feel free to add relevant agenda items, links, and

[openstack-dev] [k8s] SIG-K8s Scheduling for Dublin PTG

SIG-K8s has a planning etherpad available for the Dublin PTG. We have space scheduled for Tuesday, with approximately eight forty-minute work blocks. For the K8s on OpenStack side of things, we've identified a core set of priorities that we'll be working on that day, including: * Moving

[openstack-dev] [magnum] K8s Conformance Testing

As discussed at the Vancouver SIG-K8s and Copenhagen SIG-OpenStack sessions, we're moving forward with obtaining Kubernetes Conformance certification for Magnum. While conformance test jobs aren't reliably running in the gate yet, the requirements of the program make sumbitting results manually on

Re: [openstack-dev] [Openstack-sigs] [all] Bringing the community together (combine the lists!)

I also propose that we merge the interop-wg mailing list also, as the volume on that list is small but topics posted to it are of general interest to the community. Chris Hoge (Interop WG Secretary, amongst other things) > On Aug 30, 2018, at 10:03 AM, Jeremy Stanley wrote: > > The

[openstack-dev] [k8s] SIG-K8s PTG Meetings, Monday September 10, 2018

SIG-K8s has space reserved in Ballroom A for all of Monday, September 10 at the PTG. We will begin at 9:00 with a planning session, similar to that in Dublin, where we will organize topics and times for the remainder of the day. The planning etherpad can be found here:

[openstack-dev] [k8s] Hosting location for OpenStack Kubernetes Provider

. There is a sense of urgency, as Dims has asked that we relieve him of the responsibility of hosing the external provider work in his personal GitHub repository. Please chime in with your opinions on this here so that we can work out an where the appropriate hosting for this project should be. Thanks, Chris

[openstack-dev] [k8s][octavia][lbaas] Experiences on using the LB APIs with K8s

As I've been working more in the Kubernetes community, I've been evaluating the different points of integration between OpenStack services and the Kubernetes application platform. One of the weaker points of integration has been in using the OpenStack LBaaS APIs to create load balancers for

[openstack-dev] [k8s] OpenStack and Containers White Paper

participates in writing this document. I'm looking forward to working with you in the coming weeks to publish this important resource for clearly describing the multitude of interactions between these complementary technologies. -Chris Hoge K8s-SIG-OpenStack/OpenStack-SIG-K8s Co-Lead

Re: [openstack-dev] [k8s][octavia][lbaas] Experiences on using the LB APIs with K8s

> On Mar 16, 2018, at 7:40 AM, Simon Leinen wrote: > > Joe Topjian writes: >> Terraform hat! I want to slightly nit-pick this one since the words >> "leak" and "admin-priv" can sound scary: Terraform technically wasn't >> doing anything wrong. The problem was that

Re: [openstack-dev] [k8s][ptg] SIG-K8s Scheduling for Dublin PTG

on please add them to the schedule. If you’re working on k8s within the OpenStack community, there is a team photo at scheduled for 3:30. https://etherpad.openstack.org/p/sig-k8s-2018-dublin-ptg Chris > On Feb 21, 2018, at 7:41 PM, Chris Hoge <ch...@openstack.org> wrote: > &

[openstack-dev] [loci] Removing deprecated project-specific Loci repositories

On October 17, 2017, the Loci team retired the project-specific Loci repositories in favor of a single repository. This was done to consolidate development and prevent the anti-pattern of one repository with duplicated code for every OpenStack project. After this five month deprecation period, in

Re: [openstack-dev] OpenStack Foundation Community Meeting - October 24 - StarlingX

ntel.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Bruce E Jones;X-NUM-GUESTS=0:mailto:bruce.e.jo...@intel.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Chris Hoge;X-NUM-GUESTS=0:mailto:ch...@openstack.org ATTENDEE

[openstack-dev] [docs] New Four Opens Project

who will continue to grow and evolve this document. Chris Hoge OpenStack Foundation Four Opens: https://governance.openstack.org/tc/reference/opens.html New Project Review Patch: https://review.openstack.org/#/c/617005/ Four Opens Document Staging: https://github.com/hogepodge/four-opens

[openstack-dev] OpenStack Community Meeting - October 10 - Strategic Area Governance Update

ack.org/p/openstack-community-meeting> Thanks! Chris Hoge Strategic Program Manager OpenStack Foundation __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?su

[openstack-dev] [k8s][magnum][zun] Notification of removal of in-tree K8s OpenStack Provider

For those projects that use OpenStack as a cloud provider for K8s, there is a patch in flight[1] to remove the in-tree OpenStack provider from the kubernetes/kubernetes repository. The provider has been deprecated for two releases, with a replacement external provider available[2]. Before we merge

[openstack-dev] [k8s][tc] List of OpenStack and K8s Community Updates

In the last year the SIG-K8s/SIG-OpenStack group has facilitated quite a bit of discussion between the OpenStack and Kubernetes communities. In doing this work we've delivered a number of presentations and held several working sessions. I've created an etherpad that contains links to these