[openstack-dev] [ironic][triploe] support for firmware update

Hi all, I saw that ironic-python-agent support custom hardware manager. I would like to support firmware updates (In my case Mellanox nic) and I was wandering how custom hardware manager can be used in such case? How it is integrated with ironic-python agent and also is there an integration to

[openstack-dev] [ironic][neutron] bare metal on vxlan network

Hi all, Ironic supports mutli tenancy for quite few releases and according to the spec [1] it can work with vlan/vxlan networks. I see lot of mechanism driver that support vlan network such as [2] and [3] , but I didn't find any mechanism driver that work on vxlan network. Is there a mechanism

[openstack-dev] [PTL][SIG][PTG]Team Photos

Hello PTLs and SIG Chairs! So here's the deal, we have 50 spots that are first come, first served. We have slots available before and after lunch both Tuesday and Thursday. The google sheet here[1] should be set up so you have access to edit, but if you can't for some reason just reply directly

[openstack-dev] [QA] Meeting Thursday Feb 8th at 8:00 UTC

Hello everyone, Hope everyone is back from vacation. QA team is resuming the regular weekly meeting from today. OpenStack QA team IRC meeting will be Thursday, Feb 8th at 8:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here:

[openstack-dev] RefStack disable anonymous upload and database cleanup

Hello all! Over the course of the last few months, we have implemented and merged into production the option in RefStack server to disable the ability to upload refstack results as an anonymous user. In its current state, the RefStack database includes many anonymous test results that

Re: [openstack-dev] [All][Elections] End of PTL Nominations

Hi Kendall, There is a small typo for cyborg PTL name, rushil helped e submit the patch, but the name of the PTL should be Zhipeng Huang :) if you could correct that on the governance page that would be less confusing :) On Feb 8, 2018 8:06 AM, "Kendall Nelson" wrote:

[openstack-dev] [All][Elections][QA][Mistral][Kolla] Polling Begins!

Hello! Polls for PTL elections are now open and will remain open for you to cast your vote until Feb 14, 2018 23:45 UTC. We are having elections for Kolla, Mistral & QA. If you are a Foundation individual member and had a commit in one of the program's projects[0] over the Pike-Queens timeframe

[openstack-dev] [ptg] Lightning talks

Hey all! I'm looking for six 5-minute lightning talks for the PTG in Dublin. This will be on Friday March 2nd at 13:00-13:30 local time. Appropriate 5 minute talk examples: * Neat features in libraries like oslo that we should consider adopting in our community wide goals. * Features and

Re: [openstack-dev] [ptg] Track around release cycle, consumption models and stable branches

I would be interested in taking part in this discussion as well, -- bm On 02/07/2018 03:42 AM, Thierry Carrez wrote: Hi everyone, I was wondering if anyone would be interested in brainstorming the question of how to better align our release cycle and stable branch maintenance with the

[openstack-dev] [All][Elections] End of PTL Nominations

Hello Everyone! The PTL Nomination period is now over. The official candidate list is available on the election website[0]. There are 0 projects without candidates, so the TC will not have to appoint any PTL's. There are 3 projects that will have elections: Kolla, QA, & Mistral. The details for

Re: [openstack-dev] [glance][cinder]Question about cinder as glance store

That will depend on the Cinder/OS-brick iscsiadm versions right? Can you tell what are the versions from where the problem was fixed? Erlon 2018-02-07 8:27 GMT-02:00 Gorka Eguileor : > On 07/02, Rikimaru Honjo wrote: > > Hello, > > > > I'm planning to use cinder as glance

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 18-02-08 00:08:40, Ivan Kolodyazhny wrote: > Hi Matt, > > As discussed earlier today at the Horizon's meeting [2], we're not going to > release horizon-cisco-ui and django_openstack_auth because of projects > retirement [3] and [4]. > > > [2]

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 Matt, As discussed earlier today at the Horizon's meeting [2], we're not going to release horizon-cisco-ui and django_openstack_auth because of projects retirement [3] and [4]. [2] http://eavesdrop.openstack.org/meetings/horizon/2018/horizon.2018-02- 07-20.02.html [3]

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 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 included as an ironic project[1] NOT because

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 Wed, Feb 07, 2018 at 06:11:33PM +0100, Dmitry Tantsur wrote: > 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

[openstack-dev] [horizon][ptl] Rocky PTL Candidacy

Hello Team, I would like to announce my candidacy for PTL of Horizon for Rocky release. I use Horizon since I begin to work with OpenStack in Diablo timeframe. I wasn't active contributor before Pike release, nevertheless, I can see how both Horizon project and community changed over the times.

Re: [openstack-dev] [ptg] Track around release cycle, consumption models and stable branches

On Wed, Feb 07, 2018 at 12:42:05PM +0100, Thierry Carrez wrote: > Would anyone be interested in such a discussion ? It would be scheduled > on the Tuesday. How much time would we need ? I was thinking we could > use only Tuesday afternoon. +1 Sounds good to me. I'll be there :) Yours Tony.

[openstack-dev] [k8s] openstack-sig-k8s planning for Dublin

sig-k8s has a block of room time put aside for the Dublin PTG. I’ve set up a planning etherpad for work and discussion topics[1]. High priority items include: * openstack provider breakout [2] * provider testing * documentation updates Please feel free to add relevant agenda items, links, and

Re: [openstack-dev] [heat][rally] What should we do with legacy-rally-dsvm-fakevirt-heat

Hi Rico and stackers, Thanks for raising this topic. Short answer: please leave it as is for now. Rally team will work on ZuulV3 jobs soon. Detailed: We are planning to make some big changes in our architecture which includes splitting the main repo into a separate repository for a framework

[openstack-dev] [openstack-helm] OpenStack-Helm Office Hours

Team, The OpenStack-Helm team will begin holding weekly Office Hours in IRC, with a goal of knowledge sharing and Q between the more experienced and the newer team members. The project cores have committed to giving attention to at least one office hour during the week, and it should be a

Re: [openstack-dev] [ptg] Track around release cycle, consumption models and stable branches

On 18-02-07 12:42:05, Thierry Carrez wrote: > Hi everyone, > > I was wondering if anyone would be interested in brainstorming the > question of how to better align our release cycle and stable branch > maintenance with the OpenStack downstream consumption models. That > includes discussing the

[openstack-dev] [manila] [ptl] announcing PTL candidacy for manila

Friends, Stackers, Community, I write to announce my candidacy for the Manila PTL position for the Rocky cycle. I've worked in in OpenStack since Juno and actively in Manila since Mitaka or so. I've had more than one employer in that time and think it's fair to say that I have a reputation for

[openstack-dev] [all] [ptg] Reminder: Sign up for project interviews at PTG

A reminder - the PTG is now less than 3 weeks out. As you plan your schedule, please set aside time for a project/team interview, and sign up at https://docs.google.com/spreadsheets/d/1MK7rCgYXCQZP1AgQ0RUiuc-cEXIzW5RuRzz5BWhV4nQ/edit#gid=0 That document also contains a description of what

Re: [openstack-dev] [ptg] Track around release cycle, consumption models and stable branches

I am interested in contributing to this discussion. Michael On Wed, Feb 7, 2018 at 3:42 AM, Thierry Carrez wrote: > Hi everyone, > > I was wondering if anyone would be interested in brainstorming the > question of how to better align our release cycle and stable branch >

Re: [openstack-dev] [all][Kingbird]Multi-Region Orchestrator

Hi Chris, Thanks for writing to us. Our idea is just the same. and we are working on how to do it :) Thanks for the use-case :) On Wed, Feb 7, 2018 at 9:50 PM, Chris Friesen wrote: > On 02/05/2018 06:33 PM, Jay Pipes wrote: > > It does seem to me, however, that

[openstack-dev] [Kuryr] Rocky Kuryr PTL candidacy

Dear all, I'd like to announce my candidacy for PTL of the Kuryr project for the Rocky cycle. After being part of the Kuryr community for a while and running the Upstream meetings for a while I'd be delighted to continue the Toni's great work as PTL for the next six months as he won't be running

Re: [openstack-dev] [all][Kingbird]Multi-Region Orchestrator

Hi Zane, Thanks for writing to us. We have a doubt and I have mentioned in the inline comments can you please help us in that regard. On Tue, Feb 6, 2018 at 11:53 PM, Zane Bitter wrote: > On 31/01/18 01:49, Goutham Pratapa wrote: > >> *Kingbird (The Multi Region

[openstack-dev] [packaging-rpm] PTL candidacy

Hello fellow packagers! I would like to announce my candidacy to be the PTL for the Packaging Rpm project during the Rocky development cycle. During the last cycles, the project has become a great collaboration space for people working on RPM packages for OpenStack products. We have a number of

Re: [openstack-dev] [heat][horizon][ironic][neutron][swift][tricircle][vitrage][watcher] Help needed for your release

Hi, I will request to a create stable/queens branch for Vitrage later today. Thanks, Ifat. On 07/02/2018, 18:49, "Matthew Thode" wrote: On 18-02-07 16:33:52, Luke Hinds wrote: > On Wed, Feb 7, 2018 at 4:23 PM, Matthew Thode >

Re: [openstack-dev] [release][ptl] Missing and old intermediary projects

Hi Sean, thanks for the reminder. The changes for Monasca release are under way [1, 2]. Best greetings Witek [1] https://review.openstack.org/541767 [2] https://review.openstack.org/541776 > -Original Message- > From: Sean McGinnis [mailto:sean.mcgin...@gmx.com] > Sent: Freitag, 2.

Re: [openstack-dev] [vitrage] Vitrage alarm processing behavior

Hi Paul, I’m glad that my fix helped. Regarding the Doctor datasource: the purpose of this datasource was to be used by the Doctor test scripts. Do you intend to modify it, or to create a new similar datasource that also supports polling? Modifying the existing datasource could be

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] [api-wg] [api] [cinder] [nova] Support specify action name in request url

On Feb 2, 2018, at 2:11 AM, Duncan Thomas wrote: > > So I guess my question here is why is being RESTful good? Sure it's (very, > very loosely) a standard, but what are the actual advantages? Standards come > and go, what we want most of all is a good quality, easy to

Re: [openstack-dev] [all][Kingbird]Multi-Region Orchestrator

On Tue, Feb 6, 2018 at 6:03 AM, Jay Pipes wrote: > Goutham, comments inline... > > Also, FYI, using HTML email with different color fonts to indicate > different people talking is not particularly mailing list-friendly. For > reasons why, just check out your last post: > >

Re: [openstack-dev] [heat][horizon][ironic][neutron][swift][tricircle][vitrage][watcher] Help needed for your release

On 18-02-07 16:33:52, Luke Hinds wrote: > On Wed, Feb 7, 2018 at 4: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? > > > > The following

[openstack-dev] [docs] Documentation meeting minutes for 2018-02-07

=== #openstack-doc: docteam === Meeting started by pkovar at 16:00:38 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/docteam/2018/docteam.2018-02-07-16.00.log.html . Meeting summary --- * retired internal -core

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 Wed, Feb 7, 2018 at 4: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? > > The following is the list I'm working off of (will be updated as >

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

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? The following is the list I'm working off of (will be updated as projects release) https://gist.github.com/prometheanfire/9449355352d97207aa85172cd9ef4b9f As of

Re: [openstack-dev] [all][Kingbird]Multi-Region Orchestrator

On 02/05/2018 06:33 PM, Jay Pipes wrote: It does seem to me, however, that if the intention is *not* to get into the multi-cloud orchestration game, that a simpler solution to this multi-region OpenStack deployment use case would be to simply have a global Glance and Keystone infrastructure

Re: [openstack-dev] [requirements][release] FFE for constraints update for python-tackerclient bug-fix release

On 18-02-07 23:01:25, Yongsheng Gong wrote: > Hi, > > The tacker client has na initial queens release which does not have right > reno notes. Recently I have added some reno patches. > And also the team wants a feature to land in the queens release. > > I have requested the newer release at >

Re: [openstack-dev] [all][kolla][rdo] Collaboration with Kolla for the RDO test days

Please note that the RDO test days have currently been re-scheduled to (at least) next week, February 15th and 16th. We are currently working our way through different issues and hope they'll be sorted out in time by then. David Moreau Simard Senior Software Engineer | OpenStack RDO dmsimard =

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

On 02/07/2018 05:28 AM, 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.

[openstack-dev] [tacker] PTL candidacy from yong sheng gong

This is my self-nomination to continue running as Tacker PTL for the Rocky cycle. Lots happened in Takcer Queens cycle. More documents, More features are coming in. VNFFG is enhanced, Kubernetes vim and container VNF are introduced. Private Zabbix based application monitoring is done too.

[openstack-dev] [requirements][release] FFE for constraints update for python-tackerclient bug-fix release

Hi, The tacker client has na initial queens release which does not have right reno notes. Recently I have added some reno patches. And also the team wants a feature to land in the queens release. I have requested the newer release at https://review.openstack.org/#/c/541638/

[openstack-dev] [docs] Documentation meeting today

Hi all, The docs meeting will continue today at 16:00 UTC in #openstack-doc, as scheduled. For more details, see the meeting page: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting Cheers, pk __ OpenStack Development

[openstack-dev] [TripleO] Meet DoubleNO³

Dear all, In the need of a "lab TripleO" in order to validate updates before pushing to production, I created some ansible receipt, and a whole isolated network. This isolated network mimic 1:1 the current production, and is mainly based on libvirt. I named this "project" DoubleNO³, and it tells

Re: [openstack-dev] [ptg] Track around release cycle, consumption models and stable branches

On Wed, Feb 07, 2018 at 12:42:05PM +0100, Thierry Carrez wrote: > Hi everyone, > > I was wondering if anyone would be interested in brainstorming the > question of how to better align our release cycle and stable branch > maintenance with the OpenStack downstream consumption models. That >

Re: [openstack-dev] [vitrage] Vitrage alarm processing behavior

Hi Ifat, Yes I’ve checked the 1.3.1 refers to a deb package (python-vitrage) version built by us, so the git tag used to build that deb is 1.3.0. But I also backported doctor datasource from vitreage git master branch. I also noticed that when I configure snapshots_interval=10 I also get this

[openstack-dev] [acceleration]Cyborg Team Weekly Meeting 2018.02.07

Hi Team, Weekly meeting happen starting UTC1500 at #openstack-cyborg , we will wrap up all the remaining patches and discuss PTG schedule. -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Product Line Huawei Technologies Co,. Ltd Email: huangzhip...@huawei.com Office: Huawei

Re: [openstack-dev] [ptg] Track around release cycle, consumption models and stable branches

Hi Thierry On Wed, 7 Feb 2018 at 11:42 Thierry Carrez wrote: > Hi everyone, > > I was wondering if anyone would be interested in brainstorming the > question of how to better align our release cycle and stable branch > maintenance with the OpenStack downstream consumption

[openstack-dev] [ptg] Track around release cycle, consumption models and stable branches

Hi everyone, I was wondering if anyone would be interested in brainstorming the question of how to better align our release cycle and stable branch maintenance with the OpenStack downstream consumption models. That includes discussing the place of the distributions, the need for LTS, and where

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] [ptg] Dublin PTG proposed track schedule

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 possibility of fitting that in on

Re: [openstack-dev] [vitrage] Vitrage alarm processing behavior

Hi Paul, It sounds like a bug. Alarms created by a datasource are not supposed to be deleted later on. It might be a bug that was fixed in Queens [1]. I’m not sure which Vitrage version you are actually using. I failed to find a vitrage version 1.3.1. Could it be that you are referring to a

Re: [openstack-dev] [nova] Notification update week 6

On Tue, Feb 6, 2018 at 7:04 PM, Matt Riedemann wrote: On 2/5/2018 9:32 AM, Balázs Gibizer wrote: Introduce instance.lock and instance.unlock notifications - A specless bp has been proposed to the Rocky cycle

Re: [openstack-dev] [glance][cinder]Question about cinder as glance store

On 07/02, Rikimaru Honjo wrote: > Hello, > > I'm planning to use cinder as glance store. > And, I'll setup cinder to connect storage by iSCSI multipath. > > In this case, can I run glance-api and cinder-volume on the same node? > > In my understanding, glance-api will attach a volume to own node

Re: [openstack-dev] [tripleo] how to reproduce tripleo ci

On 6.2.2018 19:58, Wesley Hayutin wrote: Greetings, The TripleO-CI team has added a recreate / reproduce script to all the tripleo upstream ci jobs as an artifact [1-2] much like the devstack reproduce.sh script. If you find yourself in need of recreating a tripleo ci job please take a look at

[openstack-dev] [vitrage] Vitrage alarm processing behavior

Hi Vitrage developers, I have a question about vitrage innerworkings, I ported doctor datasource from master branch to an earlier version of vitrage (1.3.1). I noticed some behavior I am wondering if it's ok or it is bug of some sort. Here it is: 1. I am sending some event for rasing an alarm to

Re: [openstack-dev] [all] [tc] Community Goals for Rocky

Matt Riedemann wrote: > On 2/6/2018 8:44 AM, Emilien Macchi wrote: >> TC voted (but not approved yet) and selected 2 goals that will likely >> be approved if no strong voice is raised this week: >> >> Remove mox >> https://review.openstack.org/#/c/532361/ >> >> Toggle the debug option at runtime

[openstack-dev] [heat][rally] What should we do with legacy-rally-dsvm-fakevirt-heat

Hi heat and rally team Right now, in heat's zuul jobs. We still got one legacy job to change `legacy-rally-dsvm-fakevirt-heat` [1] which I already put a patch out here [2], but after discussion with infra team, it seems best if we can define this in rally, and reference it in heat. So my question