[openstack-dev] [all]Naming the T release of OpenStack -- Poll open

Hi folks, It is time again to cast your vote for the naming of the T Release. As with last time we'll use a public polling option over per user private URLs for voting. This means, everybody should proceed to use the following URL to cast their vote:

[openstack-dev] [Searchlight][release] Searchlight will release Stein-1

Hi team, I'm doing a release for Searchlight projects (searchlight, searchlight-ui, python-searchlightclient) [1]. Please help to review and make sure everything is ok. [1] https://review.openstack.org/#/c/614066/ Finally \m/ :D Bests, -- *Trinh Nguyen* *www.edlab.xyz

[openstack-dev] [goal][upgrade-checkers][Searchlight] Upgrade check command framework initial code

Hi team, The initial code for upgrade-checker framework has been submitted to Searchlight [1]. Please take some time to review. [1] https://review.openstack.org/#/c/613789/ Thanks, -- *Trinh Nguyen* *www.edlab.xyz *

Re: [openstack-dev] [nova] Volunteer needed to write reshaper FFU hook

I would like to help since I have now finished all the downstream works. But I may need to take some time understanding all the background information On Mon, Oct 29, 2018 at 11:25 PM Matt Riedemann wrote: > Given the outstanding results of my recruiting job last week [1] I have > been tasked

[openstack-dev] [NOVA] nova GPU suppot and find GPU type

Dear Nova community, This is the first time I work with GPUs. I have a Dell C4140 with x4 Nvidia Tesla V100 SXM2 16GB I would like to setup on Openstack Rocky. I checked the documentation and I have 2 questions I would like to ask: 1. Docs (1) says As of the Queens release, there is no

[openstack-dev] [qa] [api] [all] gabbi-tempest for integration tests

Earlier this month I produced a blog post on something I was working on to combine gabbi (the API tester used in placement, gnocchi, heat, and a few other projects) with tempest to create a simple two step process for having some purely YAML-driven and HTTP API-based of any project that can test

Re: [openstack-dev] [qa] patrole] Nominating Sergey Vilgelm and Mykola Yakovliev for Patrole core

+1 for both of them as well. On 10/29/18, 2:54 PM, "MONTEIRO, FELIPE C" wrote: -Original Message- From: Ghanshyam Mann [mailto:gm...@ghanshyammann.com] Sent: Monday, October 22, 2018 7:09 PM To: OpenStack Development Mailing List \ Subject: Re:

Re: [openstack-dev] [publiccloud-wg][sdk][osc][tc] Extracting vendor profiles from openstacksdk

Monty Taylor writes: > On 10/29/18 10:47 AM, Doug Hellmann wrote: >> Monty Taylor writes: >> >>> Heya, >>> >>> Tobias and I were chatting at OpenStack Days Nordic about the Public >>> Cloud Working Group potentially taking over as custodians of the vendor >>> profile information [0][1] we keep

Re: [openstack-dev] [publiccloud-wg][sdk][osc][tc] Extracting vendor profiles from openstacksdk

On 10/29/18 10:47 AM, Doug Hellmann wrote: Monty Taylor writes: Heya, Tobias and I were chatting at OpenStack Days Nordic about the Public Cloud Working Group potentially taking over as custodians of the vendor profile information [0][1] we keep in openstacksdk (and previously in

Re: [openstack-dev] [all] We're combining the lists!

On 2018-10-29 12:58:09 -0400 (-0400), Jay Pipes wrote: > I'm not willing to subscribe with a password over a non-TLS > connection... [...] Up to you, certainly. You don't actually need to enter anything in the password fields on the subscription page (as the instructions on it also indicate). You

[openstack-dev] [user-committee] UC Meeting Reminder

UC meeting in #openstack-uc at 1800UTC -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: (832) 264-2646 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [nova] FYI: change in semantics for virt driver update_provider_tree()

This is a notice to any out of tree virt driver implementors of the ComputeDriver.update_provider_tree() interface that they now need to set the allocation_ratio and reserved amounts for VCPU, MEMORY_MB and DISK_GB inventory from the update_provider_tree() method assuming [1] merges. The patch

Re: [openstack-dev] [all] We're combining the lists!

I'm not willing to subscribe with a password over a non-TLS connection... -jay On 10/29/2018 12:53 PM, Jeremy Stanley wrote: REMINDER: The openstack, openstack-dev, openstack-sigs and openstack-operators mailing lists (to which this is being sent) will be replaced by a new

Re: [openstack-dev] [all] We're combining the lists! (was: Bringing the community together...)

REMINDER: The openstack, openstack-dev, openstack-sigs and openstack-operators mailing lists (to which this is being sent) will be replaced by a new openstack-disc...@lists.openstack.org mailing list. The new list is open for subscriptions[0] now, but is not yet accepting posts until Monday

[openstack-dev] [tripleo] retirement of instack

With the proposed retirement of instack-undercloud[0], we will no longer be supporting future development of the instack project as well. As with instack-undercloud, we will continue to support the stable branches of instack for their life but will not being doing any future development. Please

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

Hi, On Fri, Oct 26, 2018 at 10:34 AM Won wrote: > > I solved the problem of not updating the Prometheus alarm. > Alarms with the same Prometheus alarm name are recognized as the same > alarm in vitrage. > > --- alert.rules.yml > groups: > - name: alert.rules > rules: > - alert:

Re: [openstack-dev] [publiccloud-wg][sdk][osc][tc] Extracting vendor profiles from openstacksdk

Monty Taylor writes: > Heya, > > Tobias and I were chatting at OpenStack Days Nordic about the Public > Cloud Working Group potentially taking over as custodians of the vendor > profile information [0][1] we keep in openstacksdk (and previously in > os-client-config) > > I think this is a

[openstack-dev] [nova] Volunteer needed to write reshaper FFU hook

Given the outstanding results of my recruiting job last week [1] I have been tasked with recruiting one of our glorious and most talented contributors to work on the fast-forward-upgrade script changes needed for the reshape-provider-tree blueprint. The work item is nicely detailed in the

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,

Re: [openstack-dev] [heat][nova] Does Heat support Nova micro versions

On Sat, Oct 27, 2018 at 10:08 PM Gary Kotton wrote: > Hi, > > Does heat support os-compute-api-version? Say for example I am using > queens but have a use case via heat that requires a API parameter that was > capped in the 2.56 > There isn't a way to specify compute microversion in the