Re: [openstack-dev] [OpenStack-Infra] Gerrit Upgrade to ver 2.11 completed.

On 12/16/2015 10:22 PM, Zaro wrote: On Tue, Dec 1, 2015 at 6:38 PM, Spencer Krum wrote: Hi All, The infra team will be taking gerrit offline for an upgrade on December 16th. We will start the operation at 17:00 UTC and will continue until about 21:00 UTC. This outage is

Re: [openstack-dev] [TripleO] RFC: profile matching

On 11/09/2015 03:51 PM, Dmitry Tantsur wrote: Hi folks! I spent some time thinking about bringing profile matching back in, so I'd like to get your comments on the following near-future plan. First, the scope of the problem. What we do is essentially kind of capability discovery. We'll help

Re: [openstack-dev] [docs][stable][ironic] Stable branch docs

On 12/14/2015 03:42 PM, Jim Rollenhagen wrote: Hi all, In the big tent, project teams are expected to maintain their own install guides within their projects' source tree. There's a conversation going on over in the docs list[1] about changing this, but in the meantime... Ironic (and

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

On 12/09/2015 10:58 PM, Jim Rollenhagen wrote: On Fri, Dec 04, 2015 at 05:38:43PM +0100, Dmitry Tantsur wrote: Hi! As you all probably know, we've switched to reno for managing release notes. What it also means is that the release team has stopped managing milestones for us. We have

Re: [openstack-dev] [all] using reno for release note management

On 12/08/2015 08:33 PM, Emilien Macchi wrote: This morning the Puppet OpenStack had the weekly meeting [1] and we discussed about using reno [2] for release note management. We saw three possibilities: 1/ we use reno and enforce each contributions (bugfix, feature, etc) to also edit a release

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

iring a LP blueprint reference to be specified in the body of a spec (e.g. gate-ironic-specs-python27). No gate jobs require a blueprint reference anywhere (otherwise we would not be able to land bug fixes :) Best regards, On Mon, Dec 7, 2015 at 3:52 PM Dmitry Tantsur <dtant...@redhat.com &l

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

, Dec 8, 2015 at 11:31 AM Dmitry Tantsur <dtant...@redhat.com <mailto:dtant...@redhat.com>> wrote: On 12/08/2015 08:12 AM, Pavlo Shchelokovskyy wrote: > Hi all, > > I have a question regarding #1 (Stop using LP for blueprints): > > wha

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

On 12/07/2015 02:42 PM, Doug Hellmann wrote: Excerpts from Dmitry Tantsur's message of 2015-12-07 13:18:22 +0100: On 12/07/2015 10:48 AM, Thierry Carrez wrote: Dmitry Tantsur wrote: 2015-12-04 18:26 GMT+01:00 Doug Hellmann <d...@doughellmann.com <mailto:d...@doughellma

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

On 12/07/2015 10:48 AM, Thierry Carrez wrote: Dmitry Tantsur wrote: 2015-12-04 18:26 GMT+01:00 Doug Hellmann <d...@doughellmann.com <mailto:d...@doughellmann.com>>: Please don't delete anything older than Mitaka. Do you have any hints how to not confuse users in th

Re: [openstack-dev] [TripleO] Summary of In-Progress TripleO Workflow and REST API Development

On 12/07/2015 04:33 AM, Tzu-Mainn Chen wrote: On 04/12/15 23:04, Dmitry Tantsur wrote: On 12/03/2015 08:45 PM, Tzu-Mainn Chen wrote: 5. In-Progress Development The initial spec

Re: [openstack-dev] [TripleO] workflow

On 12/06/2015 05:33 PM, John Trowbridge wrote: On 12/03/2015 03:47 PM, Dan Prince wrote: On Tue, 2015-11-24 at 15:25 +, Dougal Matthews wrote: On 23 November 2015 at 14:37, Dan Prince wrote: There are lots of references to "workflow" within TripleO conversations

Re: [openstack-dev] [ironic]"No valid host was found" when creating node in Ironic

On 12/07/2015 10:45 AM, Zhi Chang wrote: Hi, all I install devstack with Ironic in physical machine. And I want to deploy a another physical machine which IPMI info is "username:root password:12345 ip_address: 192.168.0.100". I use this command "ironic node-create -c

Re: [openstack-dev] [TripleO] Summary of In-Progress TripleO Workflow and REST API Development

On 12/03/2015 08:45 PM, Tzu-Mainn Chen wrote: Hey all, Over the past few months, there's been a lot of discussion and work around creating a new REST API-supported TripleO deployment workflow. However most of that discussion has been fragmented within spec reviews and weekly IRC meetings, so I

Re: [openstack-dev] [ironic] specs process for ironic-inspector

to use it for tracking features. Now some more complex blueprints will need a spec in addition. Does it answer your question? Cheers, On Thu, Dec 3, 2015 at 4:00 PM Dmitry Tantsur <dtant...@redhat.com <mailto:dtant...@redhat.com>> wrote: FYI: the process is in effect now.

Re: [openstack-dev] [all] [tc] [ironic] Picking an official name for a subproject (ironic-inspector in this case)

On 12/04/2015 04:30 PM, Thierry Carrez wrote: Julien Danjou wrote: On Fri, Dec 04 2015, Dmitry Tantsur wrote: Specifically, I'm talking about ironic-inspector, which is a auxiliary service under the bare metal program. My first assumption is to prefix with ironic's official name, so it should

Re: [openstack-dev] [all] [tc] [ironic] Picking an official name for a subproject (ironic-inspector in this case)

On 12/04/2015 03:33 PM, Julien Danjou wrote: On Fri, Dec 04 2015, Dmitry Tantsur wrote: Specifically, I'm talking about ironic-inspector, which is a auxiliary service under the bare metal program. My first assumption is to prefix with ironic's official name, so it should be something like

[openstack-dev] [all] [tc] [ironic] Picking an official name for a subproject (ironic-inspector in this case)

Hi everyone! I'd like to get guidance on how to pick an official name (e.g. appearing in keystone catalog or used in API versioning headers) for a subproject of an official project. Specifically, I'm talking about ironic-inspector, which is a auxiliary service under the bare metal program.

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

particular > > release. > > > > Important note: if you vote for keeping things for ironic-inspector, I > > may ask you to volunteer in helping with them ;) > > > > Dmitry. > > > > __ > OpenStack Dev

[openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

Hi! As you all probably know, we've switched to reno for managing release notes. What it also means is that the release team has stopped managing milestones for us. We have to manually open/close milestones in launchpad, if we feel like. I'm a bit tired of doing it for inspector, so I'd

Re: [openstack-dev] [ironic] specs process for ironic-inspector

FYI: the process is in effect now. Please submit specs to https://github.com/openstack/ironic-inspector-specs/ Approved specs will appear on http://specs.openstack.org/openstack/ironic-inspector-specs/ On 11/19/2015 02:19 PM, Dmitry Tantsur wrote: Hi folks! I've been dodging subj for some

Re: [openstack-dev] [nova] [ironic] Hardware composition

On 12/01/2015 02:44 PM, Vladyslav Drok wrote: Hi list! There is an idea of making use of hardware composition (e.g. http://www.intel.com/content/www/us/en/architecture-and-technology/rack-scale-architecture/intel-rack-scale-architecture-resources.html) to create nodes for ironic. The current

Re: [openstack-dev] [ironic][inspector] CMDB integration

On 11/30/2015 03:07 PM, Pavlo Shchelokovskyy wrote: Hi all, we are looking at how ironic-inspector could integrate with external CMDB solutions and be able fetch a minimal set of data needed for discovery (e.g. IPMI credentials and IPs) from CMDB. This could probably be achieved with data

Re: [openstack-dev] [TripleO] RFC: profile matching

On 12/01/2015 06:55 PM, Ben Nemec wrote: Sorry for not getting to this earlier. Some thoughts inline. On 11/09/2015 08:51 AM, Dmitry Tantsur wrote: Hi folks! I spent some time thinking about bringing profile matching back in, so I'd like to get your comments on the following near-future plan

Re: [openstack-dev] [release] using reno for libraries

On 11/28/2015 02:48 PM, Doug Hellmann wrote: Excerpts from Doug Hellmann's message of 2015-11-27 10:21:36 -0500: Liaisons, We're making good progress on adding reno to service projects as we head to the Mitaka-1 milestone. Thank you! We also need to add reno to all of the other deliverables

Re: [openstack-dev] [release] using reno for libraries

On 11/30/2015 05:14 PM, Doug Hellmann wrote: Excerpts from Dmitry Tantsur's message of 2015-11-30 10:06:25 +0100: On 11/28/2015 02:48 PM, Doug Hellmann wrote: Excerpts from Doug Hellmann's message of 2015-11-27 10:21:36 -0500: Liaisons, We're making good progress on adding reno to service

Re: [openstack-dev] [tripleo][ironic][heat] Adding back the tripleo check job

On 11/30/2015 04:19 PM, Derek Higgins wrote: Hi All, A few months tripleo switch from its devtest based CI to one that was based on instack. Before doing this we anticipated disruption in the ci jobs and removed them from non tripleo projects. We'd like to investigate adding it back

Re: [openstack-dev] [ironic] Announcing Third Party CI for Proliant iLO Drivers

On 11/30/2015 05:34 PM, Anita Kuno wrote: On 11/30/2015 11:25 AM, Gururaj Grandhi wrote: Hi, This is to announce that we have setup a Third Party CI environment for Proliant iLO Drivers. The results will be posted under "HP Proliant CI check" section in Non-voting mode. We will

Re: [openstack-dev] [ironic] Announcing Third Party CI for Proliant iLO Drivers

On 11/30/2015 06:24 PM, Anita Kuno wrote: On 11/30/2015 12:17 PM, Dmitry Tantsur wrote: On 11/30/2015 05:34 PM, Anita Kuno wrote: On 11/30/2015 11:25 AM, Gururaj Grandhi wrote: Hi, This is to announce that we have setup a Third Party CI environment for Proliant iLO Drivers

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 11/25/2015 10:43 PM, Ben Nemec wrote: On 11/23/2015 06:50 AM, Dmitry Tantsur wrote: On 11/17/2015 04:31 PM, Tzu-Mainn Chen wrote: On 10 November 2015 at 15:08, Tzu-Mainn Chen <tzuma...@redhat.

Re: [openstack-dev] [openstack-announce] [release][stable][keystone][ironic] keystonemiddleware release 1.5.3 (kilo)

I suspect it could break ironic stable/kilo in the same way as 2.0.0 release. Still investigating, checking if https://review.openstack.org/#/c/250341/ will also fix it. Example of failing patch: https://review.openstack.org/#/c/248365/ On 11/23/2015 08:54 PM, d...@doughellmann.com wrote: We

Re: [openstack-dev] [TripleO] RFC: profile matching

On 11/09/2015 03:51 PM, Dmitry Tantsur wrote: Hi folks! I spent some time thinking about bringing profile matching back in, so I'd like to get your comments on the following near-future plan. First, the scope of the problem. What we do is essentially kind of capability discovery. We'll help

Re: [openstack-dev] [ironic] [inspector] Releases and things

FYI the same thing applies to both inspector and (very soon) inspector-client. On 11/26/2015 04:30 PM, Ruby Loo wrote: On 25 November 2015 at 18:02, Jim Rollenhagen > wrote: Hi all, We're approaching OpenStack's M-1 milestone,

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 11/17/2015 04:31 PM, Tzu-Mainn Chen wrote: On 10 November 2015 at 15:08, Tzu-Mainn Chen > wrote: Hi all, At the last IRC meeting it was

Re: [openstack-dev] [devstack]Question about using Devstack

On 11/23/2015 12:07 PM, Oleksii Zamiatin wrote: On Mon, Nov 23, 2015 at 12:58 PM, Young Yang > wrote: Hi, I'm using devstack to deploy stable/Kilo in my Xenserver. I successfully deploy devstack. But I found that every time I

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

On 11/23/2015 05:42 PM, Morgan Fainberg wrote: Hi everyone, This email is being written in the context of Keystone more than any other project but I strongly believe that other projects could benefit from a similar evaluation of the policy. Most projects have a policy that prevents the

Re: [openstack-dev] [ironic] Redfish drivers in ironic

On 11/20/2015 12:50 AM, Bruno Cornec wrote: Hello, Vladyslav Drok said on Thu, Nov 19, 2015 at 03:59:41PM +0200: Hi list and Bruno, I’m interested in adding virtual media boot interface for redfish ( https://blueprints.launchpad.net/ironic/+spec/redfish-virtual-media-boot). It depends on

Re: [openstack-dev] [ironic] [inspector] Auto discovery extension for Ironic Inspector

On 11/19/2015 11:57 AM, Sam Betts (sambetts) wrote: What Yuiko has described makes a lot of sense, and from that perspective perhaps instead of us defining what driver a node should and shouldn’t be using a config file, we should just provide a guide to using the inspector rules for this and

[openstack-dev] [ironic] specs process for ironic-inspector

Hi folks! I've been dodging subj for some time (mostly due to my laziness), but now it seems like the time has come. We're discussing 2 big features: autodiscovery and HA that I would like us to have a proper consensus on. I'd like to get your opinion on one of the options: 1. Do not have

Re: [openstack-dev] [Ironic] Do we need to have a mid-cycle?

On 11/16/2015 03:05 PM, Jim Rollenhagen wrote: On Wed, Nov 11, 2015 at 12:16:34PM -0500, Ruby Loo wrote: On 10 November 2015 at 12:08, Dmitry Tantsur <dtant...@redhat.com> wrote: On 11/10/2015 05:45 PM, Lucas Alvares Gomes wrote: Hi, In the last Ironic meeting [1] we started a disc

Re: [openstack-dev] [ironic] specs process for ironic-inspector

and docs should be consistent. This is a good point. It's very likely that we'll post documentation to a separate site. Best regards, On Thu, Nov 19, 2015 at 3:20 PM Dmitry Tantsur <dtant...@redhat.com <mailto:dtant...@redhat.com>> wrote: Hi folks! I've been dodging subj f

Re: [openstack-dev] [ironic][inspector][documentation] any suggestions

On 11/18/2015 10:10 AM, Serge Kovaleff wrote: Hi Stackers, I am going to help my team with the Inspector installation instruction. Hi, that's great! Any ideas or suggestions what and how to contribute back to the community? I see that Ironic Inspector could benefit from Documentation

Re: [openstack-dev] [ironic] [inspector] Auto discovery extension for Ironic Inspector

I have to admin I forgot about this thread. Please find comments inline. On 11/06/2015 05:25 PM, Bruno Cornec wrote: Hello, Pavlo Shchelokovskyy said on Tue, Nov 03, 2015 at 09:41:51PM +: For auto-setting driver options on enrollment, I would vote for option 2 with default being fake

Re: [openstack-dev] [ironic] [inspector] Auto discovery extension for Ironic Inspector

On 11/02/2015 05:07 PM, Sam Betts (sambetts) wrote: Auto discovery is a topic which has been discussed a few times in the past for Ironic, and its interesting to solve because its a bit of a chicken and egg problem. The ironic inspector allows us to inspect nodes that we don't know the mac

Re: [openstack-dev] [all] [oslo] Please stop removing usedevelop from tox.ini (at least for now)

make sure to communicate this to people first? Because the error message is really vague to anyone who is not aware of these version tags. -- Dims On Mon, Nov 16, 2015 at 5:37 AM, Dmitry Tantsur <dtant...@redhat.com> wrote: On 11/16/2015 11:35 AM, Julien Danjou wrote: On Mon, Nov

Re: [openstack-dev] [all] [oslo] Please stop removing usedevelop from tox.ini (at least for now)

On 11/16/2015 11:35 AM, Julien Danjou wrote: On Mon, Nov 16 2015, Dmitry Tantsur wrote: Before you ask: using 'sudo pip install -U setuptools pbr' is out of question in binary distributions :) so please make sure to remove this line only when everyone is updated to whatever version is required

[openstack-dev] [all] [oslo] Please stop removing usedevelop from tox.ini (at least for now)

Hi all! I've seen a couple of patches removing "usedevelop = true" from tox.ini. This has 2 nasty consequences: 1. It's harder to manually experiment in tox environment, as you have to explicitly use 'tox' command every time you change code 2. The most important, it breaks tox invocation for

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

On 11/10/2015 03:32 PM, Steve Martinelli wrote: So I don't know the intricacies of the baremetal APIs, but hopefully I can shed some light on best practices. Do try to reuse the existing actions (http://docs.openstack.org/developer/python-openstackclient/commands.html#actions) Do use "create",

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

On 11/10/2015 05:14 PM, Dean Troyer wrote: On Tue, Nov 10, 2015 at 9:46 AM, Dmitry Tantsur <dtant...@redhat.com <mailto:dtant...@redhat.com>> wrote: inspect, manage, provide, active and abort are all provisioning verbs used in ironic API. they usually represent

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 11/10/2015 04:37 PM, Giulio Fidente wrote: On 11/10/2015 04:16 PM, Dmitry Tantsur wrote: On 11/10/2015 04:08 PM, Tzu-Mainn Chen wrote: Hi all, At the last IRC meeting it was agreed that the new TripleO REST API should forgo the Tuskar name, and simply be called... the TripleO API. There's

Re: [openstack-dev] [Ironic] Quick poll: OpenStackClient command for provision action

On 11/10/2015 05:21 PM, Brad P. Crochet wrote: On Tue, Nov 10, 2015 at 4:09 AM, Dmitry Tantsur <dtant...@redhat.com> wrote: Hi all! I'd like to seek consensus (or at least some opinions) on patch https://review.openstack.org/#/c/206119/ It proposed the following command: I think it'

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

. Definitely. I think I used word deprecation somewhere in this long letter :) A few more thoughts inline. On 11/09/2015 06:44 AM, Dmitry Tantsur wrote: Hi OOO'ers, hopefully the subject caught your attentions :) Currently, tripleoclient exposes several commands in "openstack baremetal" and

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 11/10/2015 04:08 PM, Tzu-Mainn Chen wrote: Hi all, At the last IRC meeting it was agreed that the new TripleO REST API should forgo the Tuskar name, and simply be called... the TripleO API. There's one more point of discussion: where should the API live? There are two possibilities: a)

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 11/10/2015 06:08 PM, Ben Nemec wrote: On 11/10/2015 10:28 AM, John Trowbridge wrote: On 11/10/2015 10:43 AM, Ben Nemec wrote: On 11/10/2015 05:26 AM, John Trowbridge wrote: On 11/09/2015 07:44 AM, Dmitry Tantsur wrote: Hi OOO'ers, hopefully the subject caught your attentions

Re: [openstack-dev] [Ironic] Do we need to have a mid-cycle?

On 11/10/2015 05:45 PM, Lucas Alvares Gomes wrote: Hi, In the last Ironic meeting [1] we started a discussion about whether we need to have a mid-cycle meeting for the Mitaka cycle or not. Some ideas about the format of the midcycle were presented in that conversation and this email is just a

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

On 11/10/2015 10:28 AM, Lucas Alvares Gomes wrote: Hi, Let's have a quick poll, which would you prefer and why: 1. openstack baremetal provision state --provide UUID 2. openstack baremetal provision --provide UUID 3. openstack baremetal provide UUID 4. openstack baremetal set provision state

[openstack-dev] [Ironic] Quick poll: OpenStackClient command for provision action

Hi all! I'd like to seek consensus (or at least some opinions) on patch https://review.openstack.org/#/c/206119/ It proposed the following command: openstack baremetal provision state --provide UUID (where --provide can also be --active, --deleted, --inspect, etc). I have several issues

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 11/10/2015 12:26 PM, John Trowbridge wrote: On 11/09/2015 07:44 AM, Dmitry Tantsur wrote: Hi OOO'ers, hopefully the subject caught your attentions :) Currently, tripleoclient exposes several commands in "openstack baremetal" and "openstack baremetal introspection"

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

onize the integrational aspects of the openstack client project, going forward." :) On Mon, Nov 9, 2015 at 1:44 PM, Dmitry Tantsur <dtant...@redhat.com> wrote: Hi OOO'ers, hopefully the subject caught your attentions :) Currently, tripleoclient exposes several commands in "

[openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

Hi OOO'ers, hopefully the subject caught your attentions :) Currently, tripleoclient exposes several commands in "openstack baremetal" and "openstack baremetal introspection" namespaces belonging to ironic and ironic-inspector accordingly. TL;DR of this email is to deprecate them and move to

[openstack-dev] [TripleO] RFC: profile matching

Hi folks! I spent some time thinking about bringing profile matching back in, so I'd like to get your comments on the following near-future plan. First, the scope of the problem. What we do is essentially kind of capability discovery. We'll help nova scheduler with doing the right thing by

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 11/09/2015 03:04 PM, Dougal Matthews wrote: On 9 November 2015 at 12:44, Dmitry Tantsur <dtant...@redhat.com <mailto:dtant...@redhat.com>> wrote: Hi OOO'ers, hopefully the subject caught your attentions :) Currently, tripleoclient exposes several commands in "openst

Re: [openstack-dev] [ironic] Next meeting is November 9

On 10/22/2015 12:33 PM, Miles Gould wrote: I've just joined - what is the usual place and time? Hi and welcome! All the information you need you can find here: https://wiki.openstack.org/wiki/Meetings/Ironic Thanks, Miles - Original Message - From: "Beth Elwell"

[openstack-dev] [release][stable][ironic] ironic-inspector release 2.2.2 (liberty)

We are gleeful to announce the release of: ironic-inspector 2.2.2: Hardware introspection for OpenStack Bare Metal With source available at: http://git.openstack.org/cgit/openstack/ironic-inspector The most important change is a fix for CVE-2015-5306, all users (including users of

Re: [openstack-dev] [QA] Design Summit Schedule

On 10/15/2015 06:42 PM, Matthew Treinish wrote: Hi Everyone, I just pushed up the QA schedule for design summit: https://mitakadesignsummit.sched.org/overview/type/qa Let me know if there are any big schedule conflicts or other issues, so we can work through the problem. Hi! I wonder if

Re: [openstack-dev] Requests + urllib3 + distro packages

On 10/15/2015 12:18 AM, Robert Collins wrote: On 15 October 2015 at 11:11, Thomas Goirand wrote: One major pain point is unfortunately something ridiculously easy to fix, but which nobody seems to care about: the long & short descriptions format. These are usually buried into

[openstack-dev] [TripleO] Introspection rules aka advances profiles replacement: next steps

Hi OoO'ers :) It's going to be a long letter, fasten your seat-belts (and excuse my bad, as usual, English)! In RDO Manager we used to have a feature called advanced profiles matching. It's still there in the documentation at

Re: [openstack-dev] [all] jobs that make break when we remove Devstack extras.d in 10 weeks

On 10/09/2015 05:41 PM, Dmitry Tantsur wrote: On 10/09/2015 12:58 PM, Dmitry Tantsur wrote: On 10/09/2015 12:35 PM, Sean Dague wrote: From now until the removal of devstack extras.d support I'm going to send a weekly email of jobs that may break. A warning was added that we can track

[openstack-dev] [ironic] [inspector] Ideas for summit discussions

Hi inspectors! :) We don't have a proper design session in Tokyo, but I hope it won't prevent us from having an informal one, probably on Friday morning during the contributor meetup. I'm collecting the ideas of what we could discuss, so please feel free to jump in:

Re: [openstack-dev] [ironic] Nominating two new core reviewers

On 10/08/2015 11:47 PM, Jim Rollenhagen wrote: Hi all, I've been thinking a lot about Ironic's core reviewer team and how we might make it better. I'd like to grow the team more through trust and mentoring. We should be able to promote someone to core based on a good knowledge of *some* of the

Re: [openstack-dev] [all] jobs that make break when we remove Devstack extras.d in 10 weeks

On 10/09/2015 12:58 PM, Dmitry Tantsur wrote: On 10/09/2015 12:35 PM, Sean Dague wrote: From now until the removal of devstack extras.d support I'm going to send a weekly email of jobs that may break. A warning was added that we can track in logstash. Here are the top 25 jobs (by volume

Re: [openstack-dev] [all] jobs that make break when we remove Devstack extras.d in 10 weeks

On 10/09/2015 12:35 PM, Sean Dague wrote: From now until the removal of devstack extras.d support I'm going to send a weekly email of jobs that may break. A warning was added that we can track in logstash. Here are the top 25 jobs (by volume) that are currently tripping the warning:

Re: [openstack-dev] [CI] Try to introduce RFC mechanism to CI.

On 10/09/2015 12:06 PM, Tang Chen wrote: On 10/09/2015 05:48 PM, Jordan Pittier wrote: Hi, On Fri, Oct 9, 2015 at 11:00 AM, Tang Chen > wrote: Hi, CI systems will run tests for each patch once it is submitted or modified.

Re: [openstack-dev] [TripleO] Defining a public API for tripleo-common

On 09/30/2015 03:15 PM, Ryan Brown wrote: On 09/30/2015 04:08 AM, Dougal Matthews wrote: Hi, What is the standard practice for defining public API's for OpenStack libraries? As I am working on refactoring and updating tripleo-common I have to grep through the projects I know that use it to

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 09/25/2015 04:44 PM, Ihar Hrachyshka wrote: Hi all, releases are approaching, so it’s the right time to start some bike shedding on the mailing list. Recently I got pointed out several times [1][2] that I violate our commit message requirement [3] for the message lines that says:

Re: [openstack-dev] [Ironic] New dhcp provider using isc-dhcp-server

ys have any idea ? > > Regards, > Ionut Balutoiu > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.

Re: [openstack-dev] [Ironic] Stepping down from IPA core

On 09/21/2015 05:49 PM, Josh Gachnang wrote: Hey y'all, it's with a heavy heart I have to announce I'll be stepping down from the IPA core team on Thurs, 9/24. I'm leaving Rackspace for a healthcare startup (Triggr Health) and won't have the time to dedicate to being an effective OpenStack

Re: [openstack-dev] [ironic] [inspector] Liberty soft freeze

Note for inspector folks: this applies to us as well. Lets land whatever we have planned for 2.2.0 and fix any issues arising. Please see milestone page for list of things that we still need to review/fix: https://launchpad.net/ironic-inspector/+milestone/2.2.0 On 09/18/2015 03:50 AM, Jim

[openstack-dev] [Ironic] [Inspector] Finishing Liberty (was: final liberty cycle client library releases needed)

Hi folks! As you can see below, we have to make the final release of python-ironic-inspector-client really soon. We have 2 big missing parts: 1. Introspection rules support. I'm working on it: https://review.openstack.org/#/c/223096/ This required a substantial requirement, so that our

Re: [openstack-dev] [Ironic] [Inspector] Finishing Liberty

On 09/15/2015 05:02 PM, Dmitry Tantsur wrote: Hi folks! As you can see below, we have to make the final release of python-ironic-inspector-client really soon. We have 2 big missing parts: 1. Introspection rules support. I'm working on it: https://review.openstack.org/#/c/223096

Re: [openstack-dev] [Ironic] [Inspector] Finishing Liberty (was: final liberty cycle client library releases needed)

can update > > requirements constraints by early next week before the RC1. > > > > https://wiki.openstack.org/wiki/Liberty_Release_Schedule > > > > Doug > > > > > > > > Sorry if you hear this question too often :) > > > > > >

Re: [openstack-dev] [all][ptl][release] final liberty cycle client library releases needed

On 09/14/2015 04:18 PM, Doug Hellmann wrote: Excerpts from Doug Hellmann's message of 2015-09-14 08:46:02 -0400: PTLs and release liaisons, In order to keep the rest of our schedule for the end-of-cycle release tasks, we need to have final releases for all client libraries in the next day or

Re: [openstack-dev] [Ironic] Suggestion to split install guide

On 09/14/2015 03:54 PM, Ruby Loo wrote: On 11 September 2015 at 04:56, Dmitry Tantsur <dtant...@redhat.com <mailto:dtant...@redhat.com>> wrote: Hi all! Our install guide is huge, and I've just approved even more text for it. WDYT about splitting it into "Ba

[openstack-dev] [Ironic] Suggestion to split install guide

Hi all! Our install guide is huge, and I've just approved even more text for it. WDYT about splitting it into "Basic Install Guide", which will contain bare minimum for running ironic and deploying instances, and "Advanced Install Guide", which will the following things: 1. Using Bare Metal

Re: [openstack-dev] [Ironic] Command structure for OSC plugin

On 09/09/2015 06:48 PM, Jim Rollenhagen wrote: On Tue, Sep 01, 2015 at 03:47:03PM -0500, Dean Troyer wrote: [late catch-up] On Mon, Aug 24, 2015 at 2:56 PM, Doug Hellmann wrote: Excerpts from Brad P. Crochet's message of 2015-08-24 15:35:59 -0400: On 24/08/15 18:19

Re: [openstack-dev] [TripleO] Releasing tripleo-common on PyPI

On 09/09/2015 12:15 PM, Dougal Matthews wrote: Hi, The tripleo-common library appears to be registered or PyPI but hasn't yet had a release[1]. I am not familiar with the release process - what do we need to do to make sure it is regularly released with other TripleO packages? I think this is

Re: [openstack-dev] [all] Mitaka Design Summit - Proposed slot allocation

On 09/04/2015 12:14 PM, Thierry Carrez wrote: Hi PTLs, Here is the proposed slot allocation for every "big tent" project team at the Mitaka Design Summit in Tokyo. This is based on the requests the liberty PTLs have made, space availability and project activity & collaboration needs. We have a

Re: [openstack-dev] [nova][manila] latest microversion considered dangerous

not break the world, until you merge it and start updating tests. Probably it's not that important for projects who have their integration tests in-tree though.. So, I raise hand for restricting latest. On Fri, Aug 28, 2015 at 10:20 AM, Dmitry Tantsur dtant...@redhat.com mailto:dtant...@redhat.com

Re: [openstack-dev] [nova][manila] latest microversion considered dangerous

On 08/27/2015 09:38 PM, Ben Swartzlander wrote: Manila recently implemented microversions, copying the implementation from Nova. I really like the feature! However I noticed that it's legal for clients to transmit latest instead of a real version number. THIS IS A TERRIBLE IDEA! I recommend

Re: [openstack-dev] [api] [wsme] [ceilometer] Replacing WSME with _____ ?

On 08/28/2015 04:36 PM, Lucas Alvares Gomes wrote: Hi, If you just want to shoot the breeze please respond here. If you have specific comments on the spec please response there. I have been thinking about doing it for Ironic as well so I'm looking for options. IMHO after using WSME I would

Re: [openstack-dev] [ironic] Re: New API for node create, specifying initial provision state

...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- -- -- Dmitry Tantsur -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev

Re: [openstack-dev] [ironic] Re: New API for node create, specifying initial provision state

On 08/27/2015 11:40 AM, Lucas Alvares Gomes wrote: On Wed, Aug 26, 2015 at 11:09 PM, Julia Kreger juliaashleykre...@gmail.com wrote: My apologies for not expressing my thoughts on this matter sooner, however I've had to spend some time collecting my thoughts. To me, it seems like we do not

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

On 08/25/2015 07:38 PM, Chris Dent wrote: WSME version 0.8.0 was released today with several fixes to error handling and error messages. These fixes make WSME behave more in the way it says it would like to behave (and should behave) with regard to input validation and HTTP handling. You want

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

On 08/26/2015 11:05 AM, Lucas Alvares Gomes wrote: On Wed, Aug 26, 2015 at 9:27 AM, Chris Dent chd...@redhat.com wrote: On Wed, 26 Aug 2015, Dmitry Tantsur wrote: Note that this is an API breaking change, which can potentially break random users of all projects using wsme. I think we should

[openstack-dev] [Ironic] [Inspector] Addition to ironic-inspector-core: Sam Betts

Hi all! Please join me in welcoming Sam to our team! He has been doing very smart reviews recently, was contributing core features and expressed clear interest in the ironic-inspector project. Thanks and welcome! __

Re: [openstack-dev] [all][release] ACL for library-release team for release:managed projects

On 08/22/2015 11:36 PM, Doug Hellmann wrote: Excerpts from Dmitry Tantsur's message of 2015-08-22 16:12:44 +0200: 2015-08-22 0:25 GMT+02:00 Davanum Srinivas dava...@gmail.com: Folks, In the governance repo a number of libraries are marked with release:managed tag:

Re: [openstack-dev] [Ironic] Command structure for OSC plugin

On 08/24/2015 05:41 PM, Jay Pipes wrote: On 08/24/2015 08:03 AM, Brad P. Crochet wrote: I am working on extending the current set of patches that implement the OSC plugin for Ironic. I would like some discussion/guidance about a couple of command structures. Currently provisioning state is set

Re: [openstack-dev] [Ironic] Command structure for OSC plugin

On 08/24/2015 07:25 PM, Brad P. Crochet wrote: On 24/08/15 17:56 +0200, Dmitry Tantsur wrote: On 08/24/2015 05:41 PM, Jay Pipes wrote: On 08/24/2015 08:03 AM, Brad P. Crochet wrote: I am working on extending the current set of patches that implement the OSC plugin for Ironic. I would like

Re: [openstack-dev] [all][release] ACL for library-release team for release:managed projects

__ 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 -- -- -- Dmitry Tantsur

Re: [openstack-dev] [TripleO] Moving instack upstream

On 08/19/2015 06:42 PM, Derek Higgins wrote: On 06/08/15 15:01, Dougal Matthews wrote: - Original Message - From: Dan Prince dpri...@redhat.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Thursday, 6 August, 2015 1:12:42 PM

Re: [openstack-dev] [ironic] Re: New API for node create, specifying initial provision state

To be honest, I'm tired of repeating the same arguments again and again... I personally would like to get something cool done, rather than discussing how to work around our new state machine again and again. Now to some trolling: please include a way to users to opt-out from NOSTATE -

<    1   2   3   4   5   6   7   >