Re: [openstack-dev] [TripleO] Backwards compatibility policy for our projects

Why is OOO being singled out for backwards compatibility? -Original Message- From: Duncan Thomas [mailto:duncan.tho...@gmail.com] Sent: Monday, June 16, 2014 11:42 AM To: jr...@redhat.com; OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev]

[openstack-dev] [NOVA] https://review.openstack.org/91486

Why is this blueprint dropped? We really like it to be in the code base. It has been submitted to Icehouse and has been ready for review for more than 2 months. The code is ready for review and we have been using it for a while internally. Thanks, Arkady Arkady Kanevsky, Ph.D. Director of SW

[openstack-dev] licenses

What is the license that should be used for specs and for the code? While all the code I had seen is under Apache 2 license, many of the specs are under CCPL-3 license. Is that the guidance? Thanks, Arkady ___ OpenStack-dev mailing list

Re: [openstack-dev] [oslo][cinder][nova][neutron] going forward to oslo-config-generator ...

Jay, That sound reasonable. We will need to document in a guide for driver developers what to do when new option is added deprecated in conf file for a driver. Expect that nothing extra will need to be done beyond what we are doing now when new functionality added/deprecated from

Re: [openstack-dev] [OpenStack-Dev] [third-party-ci] Clarifications on the goal and skipping tests

Another scenario. The default LVM driver is local to cinder service. Thus, it may work fine as soon as you go outside controller node it does not. We had a discussion on choosing different default driver and expect that discussion to continue. Not all drivers support all features. We have a

Re: [openstack-dev] Cinder Review Inbox Was RE: Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

Dell - Internal Use - Confidential The link from cinder page to Cinder review inbox (https://review.openstack.org/#/dashboard/) from https://wiki.openstack.org/wiki/Cinder#Resources is empty. Link to bugs does work. -Original Message- From: Mike Perez [mailto:thin...@gmail.com] Sent:

Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

Dell - Internal Use - Confidential +2 on Mike’s job From: Duncan Thomas [mailto:duncan.tho...@gmail.com] Sent: Tuesday, March 24, 2015 3:07 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: [cinder] Request

[openstack-dev] [RefStackl] - http://refstack.org/ - does not resolve

What are we doing to have name resolved? Meanwhile what is IP address to reach it? Do we really expect people to submit results to that web site? Thanks, Arkady __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [tripleo] Building images separation and moving images into right place at right time

Dell - Internal Use - Confidential We need an ability for an Admin to add/remove new images at will to deploy new overcloud images at any time. Expect that it is standard glance functionality. -Original Message- From: Jaromir Coufal [mailto:jcou...@redhat.com] Sent: Friday, April 17,

Re: [openstack-dev] [tripleo] Building images separation and moving images into right place at right time

Dell - Internal Use - Confidential If images under consideration are for overcloud nodes then they will changing all the time also. It all depends on which layer you are working on. Just consider images for overcloud nodes as a cloud application, and then follow rules you would apply to any

Re: [openstack-dev] [cinder] Some Changes to Cinder Core

Well deserved. Congrat! -Original Message- From: yang, xing [mailto:xing.y...@emc.com] Sent: Friday, May 22, 2015 8:52 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [cinder] Some Changes to Cinder Core Definitely +1! Thanks, Xing

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

Agree with Thierry. Let's define requirements. We are trying to solve HA not scale infinitely number of cinder instances running. Thanks, Arkady -Original Message- From: Gorka Eguileor [mailto:gegui...@redhat.com] Sent: Monday, August 03, 2015 3:44 AM To: OpenStack Development Mailing

Re: [openstack-dev] [cinder] Dependencies of snapshots on volumes

You can do lazy copy that happens only when volume or snapshot is deleted. You will need to have refcount on metadata. -Original Message- From: Li, Xiaoyan [mailto:xiaoyan...@intel.com] Sent: Tuesday, December 08, 2015 10:11 PM To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [puppet] [tripleo] stop maintaining puppet-tuskar

Emilien, So what is the statement we (OpenStack) wants to provide about UI for OOO? If we will not provide it people outside our community and compatitors to OpenStack will fill the void. Thanks, Arkady -Original Message- From: Emilien Macchi [mailto:emil...@redhat.com] Sent: Wednesday,

Re: [openstack-dev] Gerrit Upgrade 12/16

Here. Here. Even trivial thing like review button to submit is hard to find. New UI is much less intuitive than old one From: Vikram Choudhary [mailto:viks...@gmail.com] Sent: Thursday, December 17, 2015 3:59 AM To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

When you state Swift I assume you mean TripleO will use swift APIs to access objects in it (template, metadata, etc). There are many environment where there is no swift but Ceph or other object store that can be used for it using swift APIs. Are all these will be under single user/project that

Re: [openstack-dev] [ironic]Ironic operations on nodes in maintenance mode

Another use cases for maintenance node are: * HW component replacement, e.g. NIC, or disk * FW upgrade/downgrade - we should be able to use ironic FW management API/CLI for it. * HW configuration change. Like re-provision server, like changing RAID configuration.

Re: [openstack-dev] [all] Proposal: copyright-holders file in each project, or copyright holding forced to the OpenStack Foundation

Either 1 or 3. 2 does not solve anything. -Original Message- From: Monty Taylor [mailto:mord...@inaugust.com] Sent: Friday, January 15, 2016 10:01 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [all] Proposal: copyright-holders file in each project, or copyright

Re: [openstack-dev] Proposal: Separate design summits from OpenStack conferences

I think this will be very detrimental to development community. The best feedback we get is from user/customer community that are at the summit but most likely will not attend separate design summit. I will ignore financial implication of 2 separate summits. -Original Message- From:

Re: [openstack-dev] [TripleO] Stable branch policy for Mitaka

I like any formal documented process. Having only bug fixes for stable releases is a good and consistent stand. But we are bumping into fundamental issue of integrated release. By the time release comes out the new functionality of nova, or neutron or most other components do not triple heat

Re: [openstack-dev] [cinder] adding a new /v3 endpoint for api-microversions

With nova and Keystone both at v3 is helps to consistent versioning across all projects. Still need documentation for transition clients from one API version to next. With new functionality not available in previous version it should be easier than API changes. -Original Message- From:

Re: [openstack-dev] [tripleo] Contributing to TripleO is challenging

Emilien, Agree on the rant. But not clear on concrete proposal to fix it. Spend more time "fixing" CI and use Tempest as a gate is a bit wage. Unless we test known working version of each project in TripleO CI you are dependent on health of other components. Thanks, Arkady -Original

[openstack-dev] [Rally][Product] Rally roadmap slide updated

Team, I had updated the slide based on Rally team feedback https://docs.google.com/presentation/d/1GmJ2iaDfLkQda_TGxHpFEEIQgrm_scvDsvep_wXVeUQ/edit#slide=id.g84f9afb4d_0_0 Thanks, Arkady __ OpenStack Development Mailing List

Re: [openstack-dev] [cinder] Proposal: changes to our current testing process

Rally is not part of the gate. Also making performance test without 3rd party CI will not be very useful. It is a good idea to run Rally performance and scenario testing but outside gate process. From: Ivan Kolodyazhny [mailto:e...@e0ne.info] Sent: Wednesday, March 02, 2016 8:36 AM To: OpenStack

[openstack-dev] [refstack] configuration user story

Per our discussion at midcycle, I had submitted user story for configuration info use cases. https://review.openstack.org/#/c/300057/ Looking forward to reviews. Once user story settles we will start the work on blueprints. Thanks, Arkady Arkady Kanevsky, Ph.D. Director of SW Development Dell

Re: [openstack-dev] [tripleo] service validation during deployment steps

What about ability of service expert to plug-in remediation module? If remediation action succeed - proceed, if not then stop. Remediation module can be extended independently from main flow. Thanks, Arkady -Original Message- From: Steven Hardy [mailto:sha...@redhat.com] Sent: Wednesday,

Re: [openstack-dev] [TripleO] TripleO deep dive hour?

Dell - Internal Use - Confidential +2 From: Emilien Macchi [mailto:emil...@redhat.com] Sent: Tuesday, June 28, 2016 6:01 PM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [TripleO] TripleO deep dive hour? Excellent idea, it would also be

Re: [openstack-dev] [all] Proposal: Architecture Working Group

+1 -Original Message- From: Nikhil Komawar [mailto:nik.koma...@gmail.com] Sent: Monday, June 20, 2016 10:37 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [all] Proposal: Architecture Working Group +1 , great idea. if we can add a

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

There is a version of Tempest that is released as part of OpenStack release. Agree with Mark that we should stick to versions parity. -Original Message- From: Mark Voelker [mailto:mvoel...@vmware.com] Sent: Monday, June 20, 2016 8:25 AM To: OpenStack Development Mailing List (not for

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

Chris, If we add openstack config to refstack submission will that provide sufficient info for "interoperability" LOGO? That includes version of APIs for each service. https://review.openstack.org/#/c/300057/ Thanks, Arkady -Original Message- From: Chris Hoge

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

Sorry if touch 3rd rail. But should backport bug fixes to older releases be done in distros and not upstream? -Original Message- From: Walter A. Boring IV [mailto:walter.bor...@hpe.com] Sent: Tuesday, August 09, 2016 12:34 PM To: openstack-dev@lists.openstack.org Subject: Re:

Re: [openstack-dev] [all][massively distributed][architecture] Coordination between actions/WGs

Please, drive new multi projects requirements thru use cases of Product WG. Thanks, Arkady -Original Message- From: joehuang [mailto:joehu...@huawei.com] Sent: Tuesday, August 23, 2016 9:01 PM To: OpenStack Development Mailing List (not for usage questions) ; openstack-operators Cc:

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

That is the question of how many releases backwards community is willing to “support”. The current answer is 1 year. If customer wants something earlier – do it yourself. Or to be precise work with you vendor whose driver you want updated. This creates vendor driver mismatch issues for

Re: [openstack-dev] [TripleO] a new Undercloud install driven by Heat

What is the goal of undercloud? Primarily to deploy and manage/upgrade/update overcloud. It is not targeted for multitenancy and the only "application" running on it is overcloud. While it may have a couple of VMs running in undercloud it is more convenience than actual need. So what are the