Re: [openstack-dev] [all] 2019 summit during May holidays?

t share our feeling and the level of commitment to openstack. These occasional contributors we talked about when discussing the cycle length. I don't think asking them to abandon 3-5 days of holidays is a productive way to engage them. And again, as much as I love meeting you all, I think we're outgrowing

[openstack-dev] [all] 2019 summit during May holidays?

)? Dmitry [1] https://www.openstack.org/summit/denver-2019/ [2] https://en.wikipedia.org/wiki/Golden_Week_(Japan) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ

[openstack-dev] [ironic] Team gathering at the Forum

Crowne Plaza Hotel can take bus 200 directly to Postdamer Platz. You'll need an A-B zone ticket for the travel. The restaurant is located in a court behind the tall DB building. If you want to come but did not sign up in the doodle, please let me know off-list. See you in Berlin, Dmitry On 10/29

Re: [openstack-dev] [ironic] Team gathering at the Forum?

Hi, You mean Lindenbrau, right? I was thinking of changing the venue, but if you're there, I think we should go there too! I just hope they can still fit 15 ppl :) Will try reserving tomorrow. Dmitry On 11/1/18 12:11 AM, Stig Telfer wrote: Hello Ironicers - We’ve booked the same venue

Re: [openstack-dev] Ironic integration CI jobs

On 10/31/18 2:57 PM, Julia Kreger wrote: On Wed, Oct 31, 2018 at 5:44 AM Dmitry Tantsur <mailto:dtant...@redhat.com>> wrote: Hi, On 10/31/18 1:36 AM, Julia Kreger wrote: [trim] > > ironic-tempest-dsvm-ipa-wholedisk-agent_ipmitool-tinyipa-multinode

Re: [openstack-dev] Ironic integration CI jobs

interface supports boot from volume. It was superseded by ironic-tempest-dsvm-ipxe-bfv which focuses on the use of the 'ipxe' boot interface. The underlying code is all the same deep down in all of the helper methods. +1 to this. Dmitry I'll go ahead and put this up as a topic for our weekly

Re: [openstack-dev] [ironic] Team gathering at the Forum?

Hi folks! This is your friendly reminder to vote on the day. Even if you're fine with all days, please leave a vote, so that we know how many people are coming. We will need to make a reservation, and we may not be able to accommodate more people than voted! Dmitry On 10/22/18 6:06 PM

[openstack-dev] [ironic] Team gathering at the Forum?

Hi ironicers! :) We are trying to plan an informal Ironic team gathering in Berlin. If you care about Ironic and would like to participate, please fill in https://doodle.com/poll/iw5992px765nthde. Note that the location is tentative, also depending on how many people sign up. Dmitry

[openstack-dev] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"

t less consistent with typical marketing term around the "Edge" movement. Now, I don't have really great suggestions. Something that came up in TripleO discussions [1] is Core/Hub/Edge, which I think reflects the idea better. I'd be very interested to hear your ideas. Dmitry [1]

Re: [openstack-dev] [oslo][taskflow] Thoughts on moving taskflow out of openstack/oslo

On 10/17/18 5:59 PM, Joshua Harlow wrote: Dmitry Tantsur wrote: On 10/10/18 7:41 PM, Greg Hill wrote: I've been out of the openstack loop for a few years, so I hope this reaches the right folks. Josh Harlow (original author of taskflow and related libraries) and I have been discussing

Re: [openstack-dev] [oslo][taskflow] Thoughts on moving taskflow out of openstack/oslo

On 10/10/18 7:41 PM, Greg Hill wrote: I've been out of the openstack loop for a few years, so I hope this reaches the right folks. Josh Harlow (original author of taskflow and related libraries) and I have been discussing the option of moving taskflow out of the openstack umbrella recently.

Re: [openstack-dev] [ironic] Stepping down as core

I'm sad to hear it :( Good luck, do not disappear completely, it was a pleasure to work with you. See you in Berlin! On 10/11/18 1:40 PM, Sam Betts (sambetts) wrote: As many of you will have seen on IRC, I've mostly been appearing AFK for the last couple of development cycles. Due to other

Re: [openstack-dev] [tc] [all] TC Report 18-40

++ that was very helpful, thanks Chris! On 10/2/18 6:18 PM, Steven Dake (stdake) wrote: Chris, Thanks for all the hard work you have put into this. FWIW I found value in your reports, but perhaps because I am not involved in the daily activities of the TC. Cheers -steve On 10/2/18, 8:25

Re: [openstack-dev] [Openstack-operators] [ironic] [nova] [tripleo] Deprecation of Nova's integration with Ironic Capabilities and ComputeCapabilitiesFilter

On 10/2/18 6:17 PM, Mark Goddard wrote: On Tue, 2 Oct 2018 at 17:10, Jim Rollenhagen > wrote: On Tue, Oct 2, 2018 at 11:40 AM Eric Fried wrote: > What Eric is proposing (and Julia and I seem to be in favor of), is > nearly the same as

Re: [openstack-dev] [Openstack-operators] [ironic] [nova] [tripleo] Deprecation of Nova's integration with Ironic Capabilities and ComputeCapabilitiesFilter

e it, but I guess it has two downsides: 1. Adding something to Nova API just for Ironic. 2. Ability for operators to shoot their legs by requesting some RAID configuration via deploy_template_id but not requesting the ability to use RAID in traits. Also will it really help with flavor explosio

Re: [openstack-dev] [Openstack-sigs] Are we ready to put stable/ocata into extended maintenance mode?

On 9/18/18 9:27 PM, Matt Riedemann wrote: The release page says Ocata is planned to go into extended maintenance mode on Aug 27 [1]. There really isn't much to this except it means we don't do releases for Ocata anymore [2]. There is a caveat that project teams that do not wish to maintain

Re: [openstack-dev] Bumping eventlet to 0.24.1

On 9/6/18 8:52 AM, Matthew Thode wrote: On 18-08-23 09:50:13, Matthew Thode wrote: This is your warning, if you have concerns please comment in https://review.openstack.org/589382 . cross tests pass, so that's a good sign... atm this is only for stein. I pushed the big red button. Ironic

Re: [openstack-dev] [all]-ish : Updates required for readthedocs publishers

On 09/05/2018 06:10 PM, Doug Hellmann wrote: Excerpts from Ian Wienand's message of 2018-09-05 18:53:10 +1000: Hello, If you're interested in the projects mentioned below, you may have noticed a new, failing, non-voting job "your-readthedocs-job-requires-attention". Spoiler alert: your

Re: [openstack-dev] [all]-ish : Updates required for readthedocs publishers

On 09/05/2018 10:53 AM, Ian Wienand wrote: Hello, If you're interested in the projects mentioned below, you may have noticed a new, failing, non-voting job "your-readthedocs-job-requires-attention". Spoiler alert: your readthedocs job requires attention. It's easy to miss because publishing

Re: [openstack-dev] [api] Open API 3.0 for OpenStack API

. Dmitry and generate cloud tool adapters for OpenStack, like ansible module, terraform providers and so on. Also we can make an API UI to provide an online and visible API search, API Calling for every OpenStack API. 3rd party developers can also do some self-defined development. [1] https

Re: [openstack-dev] [Openstack-operators] [ironic][tripleo][edge] Discussing ironic federation and distributed deployments

e the PTG, not the PTG itself. You're still very welcome to join! Dmitry -- Emilien Macchi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubsc

Re: [openstack-dev] [TripleO]Addressing Edge/Multi-site/Multi-cloud deployment use cases (new squad)

then: it currently depends on swift for storing collected data. Fortunately, there is a spec to fix it, but it hasn't been our team's priority. Reviews are welcome: https://review.openstack.org/#/c/587698/ Dmitry -- Jirka

[openstack-dev] [ironic] proposing metalsmith for inclusion into ironic governance

members. Please let me know if you have any questions or concerns. Dmitry [1] https://github.com/openstack/metalsmith [2] https://metalsmith.readthedocs.io/en/latest/ [3] http://tripleo.org/install/advanced_deployment/node_placement.html

Re: [openstack-dev] [TripleO]Addressing Edge/Multi-site/Multi-cloud deployment use cases (new squad)

ogether ongoing work that relates to these use cases together so that we're all collaborating with shared vision and purpose and we can help prioritize reviews/ci/etc. - Identifying any discussion items we need to work through in person at the upcoming Denver PTG. Count me in (modulo the

Re: [openstack-dev] [ironic][bifrost][sushy][ironic-inspector][ironic-ui][virtualbmc] sub-project/repository core reviewer changes

+1 to all On Thu, Aug 23, 2018, 20:25 Julia Kreger wrote: > Greetings everyone! > > In our team meeting this week we stumbled across the subject of > promoting contributors to be sub-project's core reviewers. > Traditionally it is something we've only addressed as needed or > desired by

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

On 08/17/2018 07:45 AM, Cédric Jeanneret wrote: On 08/17/2018 12:25 AM, Steve Baker wrote: On 15/08/18 21:32, Cédric Jeanneret wrote: Dear Community, As you may know, a move toward Podman as replacement of Docker is starting. One of the issues with podman is the lack of daemon, precisely

Re: [openstack-dev] [mistral] No Denver PTG Sessions

showed up at the former, so the next time we only had one slot. As with the PTG, having an agenda upfront helps a lot. We did synchronization and notes through an etherpad - exactly the same was as on the PTG. Hope that helps, Dmitry Than

Re: [openstack-dev] [ironic] ironic-staging-drivers: what to do?

CI. I know there are concerns over responsibility in terms of code ownership and quality, but I feel like we already hit such issues[5], like those encountered when Dmitry removed classic drivers[6] from the repository and also encountered issues just prior to the latest release[7][8].

Re: [openstack-dev] [releases][rocky][tempest-plugins][ptl] Reminder to tag the Tempest plugins for Rocky release

On 08/13/2018 03:46 PM, Doug Hellmann wrote: Excerpts from Dmitry Tantsur's message of 2018-08-13 15:35:23 +0200: Hi, The plugins are branchless and should stay so. Let us not dive into this madness again please. You are correct that we do not want to branch, because we want the same tests

Re: [openstack-dev] [releases][rocky][tempest-plugins][ptl] Reminder to tag the Tempest plugins for Rocky release

Hi, The plugins are branchless and should stay so. Let us not dive into this madness again please. Dmitry On 08/12/2018 10:41 AM, Ghanshyam Mann wrote: Hi All, Rocky release is few weeks away and we all agreed to release Tempest plugin with cycle-with-intermediary. Detail discussion

Re: [openstack-dev] [release] Release countdown for week R-3, August 6-10

On 08/03/2018 06:40 PM, Sean McGinnis wrote: On Fri, Aug 03, 2018 at 11:23:56AM -0500, Sean McGinnis wrote: - More information on deadlines since we appear to have some conflicting information documented. According to the published release schedule:

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 08/01/2018 02:21 PM, Andrey Kurilin wrote: ср, 1 авг. 2018 г. в 14:11, Dmitry Tantsur <mailto:dtant...@redhat.com>>: On 08/01/2018 12:49 PM, Andrey Kurilin wrote: > Hey Ian and stackers! > > ср, 1 авг. 2018 г. в 8:45, Ian Wienand mailto:i

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 08/01/2018 12:49 PM, Andrey Kurilin wrote: Hey Ian and stackers! ср, 1 авг. 2018 г. в 8:45, Ian Wienand >: Hello, It seems freenode is currently receiving a lot of unsolicited traffic across all channels.  The freenode team are aware [1] and doing

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

Is it possible to ignore message or kick users by keywords? It seems that most messages are more or less the same and include a few URLs that are unlikely to appear in a normal conversation. On 08/01/2018 07:45 AM, Ian Wienand wrote: Hello, It seems freenode is currently receiving a lot of

Re: [openstack-dev] [tc] [all] TC Report 18-26

f folks are interested in continuing this discussion, lets open a new > thread. > > Thanks, > Kevin > > > From: Dmitry Tantsur [dtant...@redhat.com] > Sent: Wednesday, July 04, 2018 4:24 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [ope

Re: [openstack-dev] [tc] [all] TC Report 18-26

Tried hard to avoid this thread, but this message is so much wrong.. On 07/03/2018 09:48 PM, Fox, Kevin M wrote: I don't dispute trivial, but a self hosting k8s on bare metal is not incredibly hard. In fact, it is easier then you might think. k8s is a platform for deploying/managing services.

Re: [openstack-dev] [Puppet] Requirements for running puppet unit tests?

On 07/02/2018 08:57 PM, Lars Kellogg-Stedman wrote: On Thu, Jun 28, 2018 at 8:04 PM, Lars Kellogg-Stedman > wrote: What is required to successfully run the rspec tests? On the odd chance that it might be useful to someone else, here's the Docker image I'm using to

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

cerpts from Andrea Frittoli's message of 2018-06-26 13:35:11 +0100: > > > > On Tue, 26 Jun 2018, 1:08 pm Thierry Carrez, wrote: > > > > > > > > > Dmitry Tantsur wrote: > > > > > > [...] > > > > > > My suggesti

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

On 06/26/2018 11:57 AM, Ghanshyam Mann wrote: On Tue, 26 Jun 2018 18:37:42 +0900 Dmitry Tantsur wrote > On 06/26/2018 11:18 AM, Ghanshyam Mann wrote: > > Hello Everyone, > > > > In Queens cycle, community goal to split the Tempest Plugin has been

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

On 06/26/2018 11:18 AM, Ghanshyam Mann wrote: Hello Everyone, In Queens cycle, community goal to split the Tempest Plugin has been completed [1] and i think almost all the projects have separate repo for tempest plugin [2]. Which means each tempest plugins are being separated from their

[openstack-dev] [sdk] announcing first release of rust-openstack (+ call for contributors)

to the OpenLab project for providing the CI for the project. Cheers, Dmitry [1] https://docs.rs/openstack/latest/openstack/ [2] https://github.com/dtantsur/rust-openstack/blob/master/CONTRIBUTING.md __ OpenStack Development

Re: [openstack-dev] [TripleO] config-download/ansible next steps

On 06/13/2018 03:17 PM, James Slagle wrote: On Wed, Jun 13, 2018 at 6:49 AM, Dmitry Tantsur wrote: Slightly hijacking the thread to provide a status update on one of the items :) Thanks for jumping in. The immediate plan right now is to wait for metalsmith 0.4.0 to hit the repositories

Re: [openstack-dev] [TripleO] config-download/ansible next steps

, some might be wondering where we're going next. 4. Ansible driven baremetal deployment Dmitry Tantsur has indicated he's going to be looking at driving TripleO baremetal provisioning with Ironic and ansible directly. This would remove Heat+Nova from the baremetal provisioning workflows we

Re: [openstack-dev] use of storyboard (was [TC] Stein Goal Selection)

Hi, On 06/11/2018 03:53 PM, Ruby Loo wrote: Hi, I don't want to hijack the initial thread, but am now feeling somewhat guilty about not being vocal wrt Storyboard. Yes, ironic migrated to Storyboard in the beginning of this cycle. To date, I have not been pleased with replacing Launchpad

Re: [openstack-dev] [release] openstack-tox-validate: python setup.py check --restructuredtext --strict

In Ironic world we run doc8 on README.rst as part of the pep8 job. Maybe we should make it a common practice? On 06/06/2018 03:35 PM, Jeremy Stanley wrote: On 2018-06-06 16:36:45 +0900 (+0900), Akihiro Motoki wrote: [...] In addition, unfortunately such checks are not run in project gate, so

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

On 05/30/2018 03:54 PM, Julia Kreger wrote: On Tue, May 29, 2018 at 7:42 PM, Zane Bitter wrote: [trim] Since I am replying to this thread, Julia also mentioned the situation where two core reviewers are asking for opposite changes to a patch. It is never ever ever the contributor's

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

ir initial state, I promise :) Dmitry On 05/29/2018 03:55 PM, Julia Kreger wrote: During the Forum, the topic of review culture came up in session after session. During these discussions, the subject of our use of nitpicks were often raised as a point of contention and frustration, especially by

Re: [openstack-dev] Proposing Mark Goddard to ironic-core

On 05/20/2018 04:45 PM, Julia Kreger wrote: Greetings everyone! I would like to propose Mark Goddard to ironic-core. I am aware he recently joined kolla-core, but his contributions in ironic have been insightful and valuable. The kind of value that comes from operative use. I also make this

Re: [openstack-dev] [all][api] late addition to forum schedule

On 05/18/2018 12:23 AM, Matt Riedemann wrote: On 5/17/2018 11:02 AM, Doug Hellmann wrote: After some discussion on twitter and IRC, we've added a new session to the Forum schedule for next week to discuss our options for cleaning up some of the design/technical debt in our REST APIs. Not to

Re: [openstack-dev] [tripleo] Encrypted swift volumes by default in the undercloud

Hi, On 05/15/2018 09:19 PM, Juan Antonio Osorio wrote: Hello! As part of the work from the Security Squad, we added the ability for the containerized undercloud to encrypt the overcloud plans. This is done by enabling Swift's encrypted volumes, which require barbican. Right now it's turned

Re: [openstack-dev] [ironic][stable] Re-adding Jim Rollenhagen to ironic stable maintenance team?

Hi, Funny, I was just about to ask you about it :) Jim is a former PTL, so I cannot see why we wouldn't add him to the stable team. On 05/11/2018 01:50 PM, Julia Kreger wrote: Greetings folks, Is there any objection if we re-add Jim to the ironic-stable-maint team? He was a member prior to

Re: [openstack-dev] [ironic] Monthly bug day?

use your bluejeans line again? Thanks! Mike Turek On 4/30/18 7:33 AM, Dmitry Tantsur wrote: Hi, On 04/29/2018 10:17 PM, Michael Turek wrote: Awesome! If everyone doesn't mind the short notice, we'll have it again this Thursday @ 1:00 PM to 3:00 PM UTC. ++ I can provide video conferencing

[Openstack-operators] [ironic] [all] The last reminder about the classic drivers removal

to delay it past Rocky, since it requires my time and effort to track this process. Cheers, Dmitry On 03/06/2018 12:11 PM, Dmitry Tantsur wrote: Hi all, As you may already know, we have deprecated classic drivers in the Queens release. We don't have specific removal plans yet. But according

[openstack-dev] [ironic] [all] The last reminder about the classic drivers removal

to delay it past Rocky, since it requires my time and effort to track this process. Cheers, Dmitry On 03/06/2018 12:11 PM, Dmitry Tantsur wrote: Hi all, As you may already know, we have deprecated classic drivers in the Queens release. We don't have specific removal plans yet. But according

Re: [openstack-dev] [ironic] Monthly bug day?

Hi, On 04/29/2018 10:17 PM, Michael Turek wrote: Awesome! If everyone doesn't mind the short notice, we'll have it again this Thursday @ 1:00 PM to 3:00 PM UTC. ++ I can provide video conferencing through hangouts here https://goo.gl/xSKBS4 Let's give that a shot this time! Note that the

Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

)? [0] https://review.openstack.org/#/q/topic:cleaning+status:open On 04/25/2018 03:14 PM, Dmitry Tantsur wrote: Hi all, I'd like to restart conversation on enabling node automated cleaning by default for the undercloud. This process wipes partitioning tables (optionally, all the data) from

Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

Date: Thursday, 26 April 2018 at 17:39 To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org>, Dmitry Tantsur <dtant...@redhat.com> Subject: Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

On 04/26/2018 05:12 PM, James Slagle wrote: On Thu, Apr 26, 2018 at 10:24 AM, Dmitry Tantsur <dtant...@redhat.com> wrote: Answering to both James and Ben inline. On 04/25/2018 05:47 PM, Ben Nemec wrote: On 04/25/2018 10:28 AM, James Slagle wrote: On Wed, Apr 25, 2018 at 10:55 AM,

Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

Answering to both James and Ben inline. On 04/25/2018 05:47 PM, Ben Nemec wrote: On 04/25/2018 10:28 AM, James Slagle wrote: On Wed, Apr 25, 2018 at 10:55 AM, Dmitry Tantsur <dtant...@redhat.com> wrote: On 04/25/2018 04:26 PM, James Slagle wrote: On Wed, Apr 25, 2018 at 9:14 AM,

Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

On 04/25/2018 04:26 PM, James Slagle wrote: On Wed, Apr 25, 2018 at 9:14 AM, Dmitry Tantsur <dtant...@redhat.com> wrote: Hi all, I'd like to restart conversation on enabling node automated cleaning by default for the undercloud. This process wipes partitioning tables (optionally, all th

[openstack-dev] [tripleo] ironic automated cleaning by default?

no longer be possible to easily restore a deleted overcloud node. What do you think? If I don't hear principal objections, I'll prepare a patch in the coming days. Dmitry __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [all] [api] Re-Reminder on the state of WSME

ironic-inspector is using Flask, and it has been quite nice so far. On 04/11/2018 12:56 AM, Michael Johnson wrote: I echo Ben's question about what is the recommended replacement. Not long ago we were advised to use WSME over the alternatives which is why Octavia is using the WSME types and

Re: [openstack-dev] Proposal: The OpenStack Client Library Guide

Hi Adrian, Thanks for starting this discussion. I'm adding openstack-sigs ML, please keep it in the loop. We in API SIG are interested in providing guidance on not only writing OpenStack APIs, but also consuming them. For example, we have merged a guideline on consuming API versions:

Re: [openstack-dev] Following the new PTI for document build, broken local builds

On 03/22/2018 04:39 PM, Sean McGinnis wrote: That's unfortunate. What we really need is a migration path from the 'pbr' way of doing things to something else. I see three possible avenues at this point in time: 1. Start using 'sphinx.ext.autosummary'. Apparently this can do similar

[openstack-dev] [charms] [tripleo] [puppet] [fuel] [kolla] [openstack-ansible] [cloudcafe] [magnum] [mogan] [sahara] [shovel] [watcher] [helm] [rally] Heads up: ironic classic drivers deprecation

PMI driver with the virtualbmc project [3] instead. Please reach out to the ironic team (here or on #openstack-ironic) if you have any questions or need help with the transition. Dmitry [1] https://docs.openstack.org/ironic/latest/install/enabling-drivers.html [2] https://docs.openstack.o

Re: [openstack-dev] [tripleo] TLS by default

On 03/15/2018 12:51 AM, Julia Kreger wrote: On Wed, Mar 14, 2018 at 4:52 AM, Dmitry Tantsur <dtant...@redhat.com> wrote: Just to clarify: only for public endpoints, right? I don't think e.g. ironic-python-agent can talk to self-signed certificates yet. For what it is worth, it is po

Re: [openstack-dev] Poll: S Release Naming

3-14 13:14, schrieb Jeremy Freudberg: Hi Dmitry, According to Wikipedia [0] the trademark was removed. The citation [1] is actually inaccurate; it was not the final ruling. Regardless [2] seems to reflect the final result which is that the trademark is cancelled. Hope this helps. [0] https://en.wik

Re: [openstack-dev] [tripleo] Blueprints for Rocky

Hi Alex, I have two small ironic-related blueprints pending approval: https://blueprints.launchpad.net/tripleo/+spec/ironic-rescue https://blueprints.launchpad.net/tripleo/+spec/networking-generic-switch and one larger: https://blueprints.launchpad.net/tripleo/+spec/ironic-inspector-overcloud

Re: [openstack-dev] [tripleo] TLS by default

Just to clarify: only for public endpoints, right? I don't think e.g. ironic-python-agent can talk to self-signed certificates yet. On 03/14/2018 07:03 AM, Juan Antonio Osorio wrote: Hello, As part of the proposed changed by the Security Squad [1], we'd like the deployment to use TLS by

Re: [openstack-dev] Poll: S Release Naming

On 03/14/2018 10:05 AM, Thierry Carrez wrote: Jens Harbott wrote: 2018-03-14 9:21 GMT+01:00 Sławomir Kapłoński : Hi, Are You sure this link is good? I just tried it and I got info that "Already voted" which isn't true in fact :) Comparing with previous polls, these

Re: [openstack-dev] Poll: S Release Naming

Hi, I suspect that S-Bahn may be a protected (copyright, trademark, whatever) name. Did you have a chance to check it? On 03/14/2018 12:58 AM, Paul Belanger wrote: Greetings all, It is time again to cast your vote for the naming of the S Release. This time is little different as we've

Re: [openstack-dev] [ironic] PTG Summary

is). Tim -Original Message- From: Dmitry Tantsur <dtant...@redhat.com> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: Monday, 12 March 2018 at 12:47 To: "openstack-dev@lists.openstack.org" &l

Re: [openstack-dev] [ironic] PTG Summary

Hi Tim, Thanks for the information. I personally don't see problems with cleaning running weeks, when needed. What I'd avoid is replicating the same cleaning machinery but with a different name. I think we should try to make cleaning work for this case instead. Dmitry On 03/12/2018 12:33

[Openstack-operators] [ironic] heads-up: classic drivers deprecation and future removal

it around then. The `online_data_migrations` script will handle migrating nodes, if all required hardware interfaces and types are enabled before the upgrade to Queens. Otherwise, check the documentation [1] on how to update your nodes. Dmitry [1] https://docs.openstack.org/ironic/latest/admin

[openstack-dev] [ironic] heads-up: classic drivers deprecation and future removal

it around then. The `online_data_migrations` script will handle migrating nodes, if all required hardware interfaces and types are enabled before the upgrade to Queens. Otherwise, check the documentation [1] on how to update your nodes. Dmitry [1] https://docs.openstack.org/ironic/latest/admin

Re: [openstack-dev] [tripleo] Queens RC1 was released!

Hi! A reminder that https://review.openstack.org/534842 is quite important, as it will enable upgrade to hardware types from classic drivers. The latter will be removed in one of the future releases. As it applies to online_data_migrations it will not be run after you upgrade to Queens

Re: [openstack-dev] [ironic] Polling for new meeting time?

On 03/04/2018 09:46 PM, Zhipeng Huang wrote: Thx Julia, Another option is instead of changing meeting time, you could establish a tick-tock meeting, for example odd weeks for US-Euro friendly times and even weeks for US-Asia friendly times. We tried that roughly two years ago, and it did

Re: [openstack-dev] [ironic] Polling for new meeting time?

On 03/04/2018 07:00 PM, Julia Kreger wrote: Greetings everyone! As our community composition has shifted to be more global, the question has arisen if we should consider shifting the meeting to be more friendly to some of our contributors in the APAC time zones. Alternatively this may involve

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

Hi Vasyl, I'm sad to hear it :( Thank YOU for everything! The only thing in the world more valuable than your contributions to ironic is the joy of hanging out with you at the events :) Good luck and do not disappear. Dmitry On 02/23/2018 10:02 AM, Vasyl Saienko wrote: Hey Ironic community

Re: [openstack-dev] [OpenStackClient][Security][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][masakari][neutron][senlin][shade][solum][swift][tacker][tricircle][vitrage][watcher][winstackers]

On 02/07/2018 10:31 PM, Tony Breeds wrote: On Thu, Feb 08, 2018 at 08:18:37AM +1100, Tony Breeds wrote: Okay It's safe to ignore then ;P We should probably remove it from projects.txt if it really is empty I'll propose that. Oh my bad, ironic-python-agent-builder was included as it's

Re: [openstack-dev] [OpenStackClient][Security][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][masakari][neutron][senlin][shade][solum][swift][tacker][tricircle][vitrage][watcher][winstackers]

Hi, On 02/07/2018 05:23 PM, Matthew Thode wrote: Hi all, it looks like some of your projects may need to cut a queens branch/release. Is there anything we can do to move it along? Review patches? Make the gate work faster? :) The Ironic team is working on it, we expect stable/queens

Re: [openstack-dev] [ptg] Dublin PTG proposed track schedule

On 02/07/2018 12:28 PM, Thierry Carrez wrote: Lance Bragstad wrote: On 02/05/2018 09:34 AM, Thierry Carrez wrote: Lance Bragstad wrote: Colleen started a thread asking if there was a need for a baremetal/vm group session [0], which generated quite a bit of positive response. Is there still a

Re: [openstack-dev] [ironic] Nominating Hironori Shiina for ironic-core

+1 On 02/05/2018 07:12 PM, Julia Kreger wrote: I would like to nominate Hironori Shiina to ironic-core. He has been working in the ironic community for some time, and has been helping over the past several cycles with more complex features. He has demonstrated an understanding of Ironic's code

[openstack-dev] [ironic] driver composition: help needed from vendors

types on master (queens and newer). Please make sure that the coverage does not suffer. For example, if you used to test pxe_foo and agent_foo, the updates CI should test "foo" hardware type with "iscsi" and "direct" deploy interfaces. Please let us know if you have

[openstack-dev] [requirements][release] FFE for sushy bug-fix release

bug in the authentication code, without it authentication will not work in some cases. Thanks, Dmitry [1] https://review.openstack.org/540824 P.S. We really need a feature freeze period for libraries to avoid this.. But it cannot be introduced with the current library release freeze. Another

[openstack-dev] [ironic] Not running for PTL this cycle

forward :) Of course I'm not going anywhere far, and I'm ready to help whoever gets this chair with their new challenge. Now a small request: please leave me anonymous feedback at https://goo.gl/forms/810u3j8Yh2fymUMG2 that'll help me to improve further :) Thank you all, Dmitry

Re: [openstack-dev] [barbican] [glance] [ironic] [neutron] [tacker] [tc] policy in code goal

On 01/31/2018 06:23 PM, Lance Bragstad wrote: On 01/31/2018 11:20 AM, Dmitry Tantsur wrote: Hi! On 01/31/2018 06:16 PM, Lance Bragstad wrote: Hey folks, The tracking tool for the policy-and-docs-in-code goal for Queens [0] lists a couple projects remaining for the goal [1].  I wanted

Re: [openstack-dev] [keystone][nova][ironic][heat] Do we want a BM/VM room at the PTG?

On 01/31/2018 06:15 PM, Matt Riedemann wrote: On 1/30/2018 9:33 AM, Colleen Murphy wrote: At the last PTG we had some time on Monday and Tuesday for cross-project discussions related to baremetal and VM management. We don't currently have that on the schedule for this PTG. There is still some

Re: [openstack-dev] [barbican] [glance] [ironic] [neutron] [tacker] [tc] policy in code goal

Hi! On 01/31/2018 06:16 PM, Lance Bragstad wrote: Hey folks, The tracking tool for the policy-and-docs-in-code goal for Queens [0] lists a couple projects remaining for the goal [1].  I wanted to start a discussion with said projects to see how we want to go about the work in the future, we

[openstack-dev] [ironic] ansible deploy, playbooks and containers?

Hi all, I'd like to discuss one idea that came to me while trying to use the ansible deploy in TripleO. The ansible deploy interface is all about customization. Meaning, we expect people to modify the playbooks. I have two concerns with it: 1. Nearly any additions requires a full copy of

Re: [openstack-dev] [nova][ironic] Tagging newton EOL

Hi! Ironic is ready for newton EOL. On 01/31/2018 05:17 AM, Tony Breeds wrote: Hi All, When we tagged newton EOL in October there were in-flight reviews for nova and ironic that needed to land before we could EOL them. That work completed but I dropped the ball. So can we tag those last

[openstack-dev] [ironic] FFE - classic drivers deprecation

, if it gets an exception. Dmitry [1] http://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/classic-drivers-future.html [2] https://review.openstack.org/536298 [3] http://specs.openstack.org/openstack/ironic-specs/specs/7.0/driver-composition-reform.html

Re: [openstack-dev] [ironic] FFE request for node rescue feature

I'm +1 on this, because the feature has been proposed for a while (has changed the contributor group at least once) and is needed for feature parity with virtual machines in nova. On 01/23/2018 06:56 AM, Shivanand Tendulker wrote: Hi The rescue feature [1] is an high priority for ironic in

Re: [openstack-dev] [ironic] FFE request for node traits

+1 on keeping moving forward with it. that's important for future nova work, as well as our deploy steps work. On 01/22/2018 10:11 PM, Mark Goddard wrote: The node traits feature [1] is an essential priority for ironic in Queens, and is an important step in the continuing evolution of

[openstack-dev] [ironic] Deadlines, feature freeze and exceptions

, and include their names. This is important, we don't need FFEs that won't get reviewed. Happy hacking, Dmitry __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org

Re: [openstack-dev] [ironic] FFE - Requesting FFE for Routed Networks support.

This FFE was approved on today's meeting. Please note that the deadline to merging it is Fri, Feb 2nd. On 01/17/2018 10:54 AM, Harald Jensås wrote: Requesting FFE for Routed Network support in networking-baremetal. --- # Pros

Re: [openstack-dev] [ironic] Remove in-tree policy and config?

+1 I would really hate to not have a place to reference people to, but the documentation now provides such place. Keeping the examples up-to-date is quite annoying, I'm all for dropping them. On 01/22/2018 01:45 PM, John Garbutt wrote: Hi, While I was looking at the traits work, I noticed

Re: [openstack-dev] [release] Lib branching for stable/queens

Hi! Unfortunately, it seems that we've discovered a critical issue in one of our libs (sushy) right after branching :( What's the procedure for emergency fixes to stable/queens right now? On 01/19/2018 10:15 PM, Sean McGinnis wrote: Happy Friday all. Now that we are past the non-client lib

[openstack-dev] [ironic] Rocky PTG planning

Hi all! The PTG is slowly approaching. Make sure to do your visa paperwork (those unfortunate of us who need it) and let's start planning! Drop your ideas on the etherpad: https://etherpad.openstack.org/p/ironic-rocky-ptg Please do check the rules there before proposing, and please add your

Re: [openstack-dev] [ironic] FFE - Requesting FFE for Routed Networks support.

Hi! I'm essentially +1 on granting this FFE, as it's a low-risk work for a great feature. See one comment inline. On 01/17/2018 10:54 AM, Harald Jensås wrote: Requesting FFE for Routed Network support in networking-baremetal.

  1   2   3   4   5   6   7   8   9   10   >