Re: [openstack-dev] [placement] The "intended purpose" of traits

Hi All, I'm quite late to the discussion, because I'm on vacation and I missed the beginning of this thread, but let me share a few thoughts. On Fri, Sep 28, 2018 at 6:13 PM Jay Pipes wrote: > * Does the provider belong to physical network "corpnet" and also > support creation of virtual NICs

[openstack-dev] [I18n] No Office Hour this week

Hello, due the national holiday in Germany tomorrow and the long weekend after that, there will be no I18n Office Hour this week. Next session will be held on 2018/10/11 13:00 UTC [1]. kind regards Frank [1] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting

[openstack-dev] [vitrage] I have some problems with Prometheus alarms in vitrage.

I have some problems with Prometheus alarms in vitrage. I receive a list of alarms from the Prometheus alarm manager well, but the alarm does not disappear when the problem(alarm) is resolved. The alarm that came once in both the alarm list and the entity graph does not disappear in vitrage. The

Re: [openstack-dev] [Horizon] Horizon tutorial didn`t work

Thanks for the reply. If you need any detailed information, let me know. Regards, 2018년 10월 1일 (월) 오후 6:53, Ivan Kolodyazhny 님이 작성: > Hi Jea-Min, > > Thank you for your report. I'll check the manual and fix it asap. > > > Regards, > Ivan Kolodyazhny, > http://blog.e0ne.info/ > > > On Mon, Oct

Re: [openstack-dev] [kolla][octavia] Containerize the amphora-agent

On Sun, Sep 30, 2018 at 8:47 PM Adam Harwell wrote: > I was coming to the same conclusion for a completely different goal -- > baking lighter weight VMs (and eliminating a number of compatibility > issues) by putting exactly what we need in containers and making the base > OS irrelevant. So, I

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

On Mon, Oct 1, 2018 at 3:37 PM Jay Pipes wrote: > On 10/01/2018 06:04 PM, Julia Kreger wrote: > > On Mon, Oct 1, 2018 at 2:41 PM Eric Fried wrote: > > > > > > > So say the user requests a node that supports UEFI because their > > image > > > needs UEFI. Which workflow would you

Re: [openstack-dev] Berlin Community Contributor Awards

Hello :) I wanted to bring this to the top of people's inboxes as we have three weeks left to submit community members[1]. I can think of a dozen people right now that deserve an award and I am sure you all could do the same. It only takes a few minutes and its an easy way to make sure they get

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

On 10/01/2018 06:04 PM, Julia Kreger wrote: On Mon, Oct 1, 2018 at 2:41 PM Eric Fried wrote: > So say the user requests a node that supports UEFI because their image > needs UEFI. Which workflow would you want here? > > 1) The operator (or ironic?) has already

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

On Mon, Oct 1, 2018 at 2:41 PM Eric Fried wrote: > > > So say the user requests a node that supports UEFI because their image > > needs UEFI. Which workflow would you want here? > > > > 1) The operator (or ironic?) has already configured the node to boot in > > UEFI mode. Only pre-configured

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

> So say the user requests a node that supports UEFI because their image > needs UEFI. Which workflow would you want here? > > 1) The operator (or ironic?) has already configured the node to boot in > UEFI mode. Only pre-configured nodes advertise the "supports UEFI" trait. > > 2) Any node that

[openstack-dev] [neutron] Bug deputy report week of Sept 24

All, Here is my Bug Deputy report for the week of 9/24 - 10/1. It was a busy week! It is my recollection that prety much anything that doesn't have a patchset next to it is probably unowned and available for working. High priority == * https://bugs.launchpad.net/bugs/1794406 -

Re: [openstack-dev] [ironic][neutron] SmartNics with Ironic

Greetings, Comments in-line. Thanks, -Julia On Sat, Sep 29, 2018 at 11:27 PM Moshe Levi wrote: > Hi Julia, > > > > I don't mind to update the ironic spec [1]. Unfortunately, I wasn't in the > PTG but I had a sync meeting with Isuku. > > > > As I see it there is 2 use-cases: > >1. Running

Re: [openstack-dev] [ironic][neutron] SmartNics with Ironic

Hello. I'm willing to help it. For detailed tech discussion, gerrit with updated spec would be better, though. I'd like to supplement on Neutron port binding. On Sun, Sep 30, 2018 at 06:25:58AM +, Moshe Levi wrote: > Hi Julia, > > I don't mind to update the ironic spec [1]. Unfortunately,

Re: [openstack-dev] [placement] The "intended purpose" of traits

>> I still want to use something like "Is capable of RAID5" and/or "Has >> RAID5 already configured" as part of a scheduling and placement >> decision. Being able to have the GET /a_c response filtered down to >> providers with those, ahem, traits is the exact purpose of that operation. > > And

Re: [openstack-dev] [nova][cinder][qa] Should we enable multiattach in tempest-full?

On 10/1/2018 10:28 AM, Matt Riedemann wrote: On 10/1/2018 8:37 AM, Ghanshyam Mann wrote: +1 on adding multiattach on integrated job. It is always good to cover more features in integrate-gate instead of separate jobs. These tests does not take much time, it should be ok to add in

Re: [openstack-dev] [placement] The "intended purpose" of traits

On 10/01/2018 01:20 PM, Eric Fried wrote: I agree that we should not overload placement as a mechanism to pass configuration information ("set up RAID5 on my storage, please") to the driver. So let's put that aside. (Looking forward to that spec.) ack. I still want to use something like "Is

Re: [openstack-dev] [placement] The "intended purpose" of traits

On 09/29/2018 10:40 AM, Jay Pipes wrote: > On 09/28/2018 04:36 PM, Eric Fried wrote: >> So here it is. Two of the top influencers in placement, one saying we >> shouldn't overload traits, the other saying we shouldn't add a primitive >> that would obviate the need for that. Historically, this

Re: [openstack-dev] [placement] The "intended purpose" of traits

> It sounds like you might be saying, "I would rather not see encoded > trait names OR a new key/value primitive; but if the alternative is > ending up with 'a much larger mess', I would accept..." ...which? > > Or is it, "We should not implement a key/value primitive, nor should we > implement

Re: [openstack-dev] [placement] The "intended purpose" of traits

Dan- On 10/01/2018 10:06 AM, Dan Smith wrote: > I was out when much of this conversation happened, so I'm going to > summarize my opinion here. > >> So from a code perspective _placement_ is completely agnostic to >> whether a trait is "PCI_ADDRESS_01_AB_23_CD", "STORAGE_DISK_SSD", or >>

Re: [openstack-dev] [horizon][plugins] npm jobs fail due to new XStatic-jQuery release (was: Horizon gates are broken)

Hi Shu, Thanks for proposing your fix. It looks good to me. I have submitted a similar patch for senlin-dashboard to unblock the broken gate test [1]. [1] https://review.openstack.org/#/c/607003/ Regards, Duc (dtruong) On Fri, Sep 28, 2018 at 2:24 AM Shu M. wrote: > > Hi Ivan, > > Thank you

Re: [openstack-dev] [Release-job-failures] Release of openstack/os-log-merger failed

Miguel Angel Ajo Pelayo writes: > Thank you for the guidance and ping Doug. > > Was this triggered by [1] ? or By the 1.1.0 tag pushed to gerrit? The release jobs are always triggered by the git tagging event. The patches in openstack/releases run a job that adds tags, but the patch you linked

Re: [openstack-dev] [python3-first] support in stable branches

Dariusz Krol writes: > Hello Doug, > > thanks for your explanation. I was a little bit confused by changes to > stable branches with python3-first topic as I thought it has to do > something with adding new test configuration for python3. > > But as you explained this is about moving

Re: [openstack-dev] [neutron][stadium][networking] Seeking proposals for non-voting Stadium projects in Neutron check queue

Hi Takashi, We are open to your suggestion. What job do you think will be helpful in minimizing the possibility of Neutron patches breaking your project? Best regards On Sun, Sep 30, 2018 at 11:25 PM Takashi Yamamoto wrote: > hi, > > what kind of jobs should it be? eg. unit tests, tempest,

Re: [openstack-dev] [placement] The "intended purpose" of traits

I was out when much of this conversation happened, so I'm going to summarize my opinion here. > So from a code perspective _placement_ is completely agnostic to > whether a trait is "PCI_ADDRESS_01_AB_23_CD", "STORAGE_DISK_SSD", or > "JAY_LIKES_CRUNCHIE_BARS". > > However, things which are using

Re: [openstack-dev] [placement] The "intended purpose" of traits

> So from a code perspective _placement_ is completely agnostic to > whether a trait is "PCI_ADDRESS_01_AB_23_CD", "STORAGE_DISK_SSD", or > "JAY_LIKES_CRUNCHIE_BARS". Right, but words have meanings, and everyone is better off if that meaning is common amongst everyone doing the talking. So if

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

On Mon, Oct 1, 2018 at 10:13 AM Jay Pipes wrote: > On 10/01/2018 09:01 AM, Jim Rollenhagen wrote: > > On Mon, Oct 1, 2018 at 8:03 AM Jay Pipes > > wrote: > > > > On 10/01/2018 04:36 AM, John Garbutt wrote: > > > On Fri, 28 Sep 2018 at 00:46, Jay Pipes >

Re: [openstack-dev] [placement] The "intended purpose" of traits

On 28/09/18 1:19 PM, Chris Dent wrote: They aren't arbitrary. They are there for a reason: a trait is a boolean capability. It describes something that either a provider is capable of supporting or it isn't. This is somewhat (maybe even only slightly) different from what I think the

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

On 10/01/2018 09:01 AM, Jim Rollenhagen wrote: On Mon, Oct 1, 2018 at 8:03 AM Jay Pipes > wrote: On 10/01/2018 04:36 AM, John Garbutt wrote: > On Fri, 28 Sep 2018 at 00:46, Jay Pipes mailto:jaypi...@gmail.com> >

Re: [openstack-dev] [nova][cinder][qa] Should we enable multiattach in tempest-full?

On Mon, 01 Oct 2018 21:22:46 +0900 Erlon Cruz wrote > > > Em seg, 1 de out de 2018 às 05:26, Balázs Gibizer > escreveu: > > > On Sat, Sep 29, 2018 at 10:35 PM, Matt Riedemann > wrote: > > Nova, cinder and tempest run the nova-multiattach job in their check > >

Re: [openstack-dev] [placement] The "intended purpose" of traits

On Sat, 29 Sep 2018, Jay Pipes wrote: I don't think that's a fair statement. You absolutely *do* care which way we go. You want to encode multiple bits of information into a trait string -- such as "PCI_ADDRESS_01_AB_23_CD" -- and leave it up to the caller to have to understand that this trait

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

On Sat, 29 Sep 2018 07:23:30 +0900 Lance Bragstad wrote > Alright - I've worked up the majority of what we have in this thread and > proposed a documentation patch for oslo.policy [0]. > I think we're at the point where we can finish the rest of this discussion > in gerrit if

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

On Sat, 29 Sep 2018 03:54:01 +0900 Lance Bragstad wrote > > On Fri, Sep 28, 2018 at 1:03 PM Harry Rybacki wrote: > On Fri, Sep 28, 2018 at 1:57 PM Morgan Fainberg > wrote: > > > > Ideally I would like to see it in the form of least specific to most > specific. But more

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

On Mon, Oct 1, 2018 at 8:03 AM Jay Pipes wrote: > On 10/01/2018 04:36 AM, John Garbutt wrote: > > On Fri, 28 Sep 2018 at 00:46, Jay Pipes > > wrote: > > > > On 09/27/2018 06:23 PM, Matt Riedemann wrote: > > > On 9/27/2018 3:02 PM, Jay Pipes wrote: > > >>

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

On Fri, 21 Sep 2018 23:13:02 +0900 Lance Bragstad wrote > > On Fri, Sep 21, 2018 at 2:10 AM Ghanshyam Mann > wrote: > On Thu, 20 Sep 2018 18:43:00 +0900 John Garbutt > wrote > > tl;dr+1 consistent names > > I would make the names mirror the API... because

Re: [openstack-dev] [qa] [infra] [placement] tempest plugins virtualenv

On Fri, 28 Sep 2018 23:10:06 +0900 Matthew Treinish wrote > On Fri, Sep 28, 2018 at 02:39:24PM +0100, Chris Dent wrote: > > > > I'm still trying to figure out how to properly create a "modern" (as > > in zuul v3 oriented) integration test for placement using gabbi and >

Re: [openstack-dev] [nova][cinder][qa] Should we enable multiattach in tempest-full?

Em seg, 1 de out de 2018 às 05:26, Balázs Gibizer < balazs.gibi...@ericsson.com> escreveu: > > > On Sat, Sep 29, 2018 at 10:35 PM, Matt Riedemann > wrote: > > Nova, cinder and tempest run the nova-multiattach job in their check > > and gate queues. The job was added in Queens and was a specific

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

On 10/01/2018 04:36 AM, John Garbutt wrote: On Fri, 28 Sep 2018 at 00:46, Jay Pipes > wrote: On 09/27/2018 06:23 PM, Matt Riedemann wrote: > On 9/27/2018 3:02 PM, Jay Pipes wrote: >> A great example of this would be the proposed "deploy template"

Re: [openstack-dev] [Horizon] Horizon tutorial didn`t work

Hi Jea-Min, Thank you for your report. I'll check the manual and fix it asap. Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Mon, Oct 1, 2018 at 9:38 AM Jea-Min Lim wrote: > Hello everyone, > > I`m following a tutorial of Building a Dashboard using Horizon. > (link: >

Re: [openstack-dev] [mistral] Extend created(updated)_at by started(finished)_at to clarify the duration of the task

On Wed, 26 Sep 2018 at 12:03, Олег Овчарук wrote: > Hi everyone! Please take a look to the blueprint that i've just created > https://blueprints.launchpad.net/mistral/+spec/mistral-add-started-finished-at > > I'd like to implement this feature, also I want to update CloudFlow when > this will be

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

On Fri, 28 Sep 2018 at 00:46, Jay Pipes wrote: > On 09/27/2018 06:23 PM, Matt Riedemann wrote: > > On 9/27/2018 3:02 PM, Jay Pipes wrote: > >> A great example of this would be the proposed "deploy template" from > >> [2]. This is nothing more than abusing the placement traits API in > >> order

Re: [openstack-dev] [python3-first] support in stable branches

Hello Doug, thanks for your explanation. I was a little bit confused by changes to stable branches with python3-first topic as I thought it has to do something with adding new test configuration for python3. But as you explained this is about moving zuul-related configuration, which is a part

Re: [openstack-dev] [Release-job-failures] Release of openstack/os-log-merger failed

Oh, ok 1.1.0 tag didn't have 'venv' in tox.ini, but master has it since: https://review.openstack.org/#/c/548618/7/tox.ini@37 On Mon, Oct 1, 2018 at 10:01 AM Miguel Angel Ajo Pelayo wrote: > Thank you for the guidance and ping Doug. > > Was this triggered by [1] ? or By the 1.1.0 tag pushed

Re: [openstack-dev] [nova][cinder][qa] Should we enable multiattach in tempest-full?

On Sat, Sep 29, 2018 at 10:35 PM, Matt Riedemann wrote: Nova, cinder and tempest run the nova-multiattach job in their check and gate queues. The job was added in Queens and was a specific job because we had to change the ubuntu cloud archive we used in Queens to get multiattach working.

Re: [openstack-dev] [Release-job-failures] Release of openstack/os-log-merger failed

Thank you for the guidance and ping Doug. Was this triggered by [1] ? or By the 1.1.0 tag pushed to gerrit? I'm working to make os-log-merger part of the OpenStack governance projects, and to make sure we release it as a tarball. It's a small tool I've been using for years making my life

Re: [openstack-dev] [python3-first] support in stable branches

Hello Doug, thanks for your explanation. I was a little bit confused by changes to stable branches with python3-first topic as I thought it has to do something with adding new test configuration for python3. But as you explained this is about moving zuul-related configuration, which is a part

[openstack-dev] [Horizon] Horizon tutorial didn`t work

Hello everyone, I`m following a tutorial of Building a Dashboard using Horizon. (link: https://docs.openstack.org/horizon/latest/contributor/tutorials/dashboard.html#tutorials-dashboard ) However, provided custom management command doesn't create boilerplate code. I typed tox -e manage --