Re: [openstack-dev] [Magnum] New Core Reviewers

+1 from me for both. On Mon, Feb 1, 2016 at 10:00 AM, Gal Sagie wrote: > Not part of Magnum team, but Egor is a great help for Kuryr as well and is > a great addition in my eyes > > On Mon, Feb 1, 2016 at 7:00 PM, Davanum Srinivas > wrote: > >> +1 from

Re: [openstack-dev] [Cinder] the spec of Add-ServiceGroup-using-Tooz

On 01/31/2016 10:43 PM, dong.wenj...@zte.com.cn wrote: > > Hi all, > > I proposed the spec of Add-ServiceGroup-using-Tooz in Ciner[1]. > > Project doctor[2] in OPNFV community is its upstream. > The goal of this project is to build fault management and > maintenance framework for high

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

Hi Fausto, To be clear, I am not in any way critical of Freezer and the folk putting in work. (Please, I want to be *entirely* clear on this point! Also, saw your presentation in Vancouver.) That said, Freezer is a bit of a Swiss-Army-Knife set of combined backup functions. Sometimes it is

[openstack-dev] [nova][virt] rebuild action not in support-matrix

Hi   We have been trying to enablement of our CI work for our nova virt layer code ,so we need to configure the tempest cases based on our nova driver capability  I found that rebuild action is not listed in [1] (only talk about rebuild in evacuate), but code [2] seems support

Re: [openstack-dev] [nova][API]what's the purpose of fping in nova API?

ok, a potential work for N release, thanks-Sean Dague wrote: -To: openstack-dev@lists.openstack.orgFrom: Sean Dague Date: 02/01/2016 11:07AMSubject: Re: [openstack-dev] [nova][API]what's the purpose of fping in nova API?On 01/29/2016 09:18 AM, Chen CH Ji

Re: [openstack-dev] [Horizon] Recent integration tests failures

Ugh, dependencies with breaking API changes in minor point releases :/ On 2 February 2016 at 04:53, Timur Sufiev wrote: > Maintainers of outside dependencies continue to break our stuff :(. New > issue is https://bugs.launchpad.net/horizon/+bug/1540495 patch is > currently

Re: [openstack-dev] [keystone][nova][cinder][horizon] Projects acting as a domain at the top of the project hierarchy

On 01/30/2016 07:02 PM, Henry Nash wrote: > Hi > > One of the things the keystone team was planning to merge ahead of > milestone-3 of Mitaka, was “projects acting as a domain”. Up until now, > domains in keystone have been stored totally separately from projects, even > though all projects

Re: [openstack-dev] [Cinder] Nominating Patrick East to Cinder Core

On 01:04 Jan 30, Sean McGinnis wrote: > Patrick has been a strong contributor to Cinder over the last few releases, > both with great code submissions and useful reviews. He also participates > regularly on IRC helping answer questions and providing valuable feedback. > > I would like to add

[openstack-dev] [Magnum] Kuryr-Magnm integration spec

Hi Magnum team, FYI, you might interest to review the Magnum integration spec from Kuryr team: https://review.openstack.org/#/c/269039/ Best regards, Hongbin From: Gal Sagie [mailto:gal.sa...@gmail.com] Sent: January-31-16 2:57 AM To: OpenStack Development Mailing List (not for usage

[openstack-dev] [ironic] weekly subteam status report

Hi, We are elated to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 25.01.2016): - Ironic: 151 bugs (-1) + 171 wishlist items (+7). 14 new (-1), 111 in progress

[openstack-dev] Google Sumer of Code 2016 - Call for ideas and mentors (deadline 19/02/2016)

Hi all, Google Summer of Code (GSoC) is a program that matches mentoring organizations with college and university student developers who are paid to write open source code. It has been around 2005 and we had been accepted as a mentor organization in only one opportunity (2014) having a great

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

Hi Preston, Thank you. You saw Fabrizio in Vancouver, I'm Fausto, but it's allright, : P The challenge is interesting. If we want to build a dedicated backup API service (which is always what we wanted to do), probably we need to: - Place out of Nova and Cinder the backup features, as it

[openstack-dev] [keystone] Domain Specific Roles vs Local Groups

Hi During the recent keystone midcycle, it was suggested than an alternative domain specific roles (see spec: https://github.com/openstack/keystone-specs/blob/master/specs/mitaka/domain-specific-roles.rst

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Mon, 2016-02-01 at 15:17 +0600, Renat Akhmerov wrote: > Hi, > > I’ve read only part of letters in this huge interesting thread so far > but I’d like to try to jump in and give some comments. > > API > I personally don’t support using Mistral API as is. Maybe you came to > agreement already

[openstack-dev] [Infra] Meeting Tuesday February 2nd at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday February 2nd, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting Anyone is welcome to to add

[openstack-dev] [NFV][tacker] Notes from Tacker Midcycle Meetup

Thanks for all those who participated in last week's 2-day Tacker Midcycle meetup. It was a quite an engaging discussion! Here are the notes from the meetup, https://etherpad.openstack.org/p/tacker-mitaka-midcycle-notes - Sridhar PS: quick remainder, as we just met we are skipping our weekly

[openstack-dev] [nova] New API DB in use

(Sorry I usually hate cross-posting, but I've been told to reach both communities) Starting from Kilo, a new DB has been added for Nova that we call "API DB" [1]. It's part of the on-going Cells V2 effort that is not yet to be production-ready. During Liberty, we populated this fresh

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

On Mon, Feb 1, 2016 at 8:23 PM, Preston L. Bannister wrote: > Hi Fausto, > > To be clear, I am not in any way critical of Freezer and the folk putting > in work. (Please, I want to be *entirely* clear on this point! Also, saw > your presentation in Vancouver.) > > That

Re: [openstack-dev] [Magnum] New Core Reviewers

+ 1 for both @Ton and @Egor, they all have good review comments and suggestions. Thanks Best Wishes, Kai Qiang Wu (吴开强 Kennan） IBM China System and Technology Lab, Beijing E-mail: wk...@cn.ibm.com Tel:

Re: [openstack-dev] [all] towards a keystone v3 only devstack

Thanks for bringing this up Sean. I went ahead and documented all the way the projects/gates/clients broke in an etherpad: https://etherpad.openstack.org/p/v3-only-devstack These are all the projects that I know that were affected, if someone knows others, please add your findings. Sean, you

[openstack-dev] [tc][cross-project] #openstack-meeting-cp

Hi all, I'm not certain who needs to decide this but I think the time has come to get explicit about which project teams can use the #openstack-meeting-cp room. The room was created in November after: * http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-11-17-20.01.log.html (skim

Re: [openstack-dev] [Cinder] the spec of Add-ServiceGroup-using-Tooz

Hi Dulko, A VIM can't not detect certain NFVI fault. The external systems don't monitor the servise state. Fault as CPU failure, CPU condition not OK, Memory failure and network card failure, e.g. If the external systems detect the storage controller failure, Live migration if storage is still

Re: [openstack-dev] [nova][virt] rebuild action not in support-matrix

On 2/1/2016 12:39 PM, Chen CH Ji wrote: Hi We have been trying to enablement of our CI work for our nova virt layer code ,so we need to configure the tempest cases based on our nova driver capability I found that rebuild action is not listed in [1] (only talk about

Re: [openstack-dev] [NFV][tacker] Notes from Tacker Midcycle Meetup

Hi tacker team, Sorry for missing the midcycle, I have put down some of my thoughts re tosca-parser and Multisite on the etherpad. : ) On Tue, Feb 2, 2016 at 7:47 AM, Sridhar Ramaswamy wrote: > Thanks for all those who participated in last week's 2-day Tacker Midcycle >

[openstack-dev] [UX] Opinion/help for the eavesdrop home page

Hi All, eavesdrop.openstack.org collates all of our meeting information. The front page has a list of all the meetings. The list is long and mostly a free-form paragraph. Sometime ago we recieved a review [1] to change the layout to be more tabular. Compare [2] with [3] It's be great to

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

On Mon, Feb 1, 2016 at 10:32 PM, Fausto Marzi wrote: > Hi Preston, > Thank you. You saw Fabrizio in Vancouver, I'm Fausto, but it's allright, : > P > > The challenge is interesting. If we want to build a dedicated backup API > service (which is always what we wanted to

Re: [openstack-dev] [Magnum] New Core Reviewers

+1 +1 thanks for both harding reviewing. On 2016年02月01日 23:58, Adrian Otto wrote: Magnum Core Team, I propose Ton Ngo (Tango) and Egor Guz (eghobo) as new Magnum Core Reviewers. Please respond with your votes. Thanks, Adrian Otto

Re: [openstack-dev] [neutron] - L3 flavors and issues with use casesfor multiple L3 backends

Hi Kevin, I am probably talking about non-sense. But will we allow chaining routers with different flavors? Taking it to the real world, if a router failed to attach to the external network in your description, it may probably need another gateway device which can do the bridging.

Re: [openstack-dev] [openstack-infra] Call for papers already closed?

Hi Team, Same problem for me also .. Please help ! -Mohankumar On Mon, Feb 1, 2016 at 2:11 PM, M Ranga Swami Reddy wrote: > Yep, I have too seen this issue. > > On Mon, Feb 1, 2016 at 1:13 PM, Christian Berendt > wrote: > > Hello. > > > > I am a

Re: [openstack-dev] Call for papers already closed?

Yep, I have too seen this issue. On Mon, Feb 1, 2016 at 1:13 PM, Christian Berendt wrote: > Hello. > > I am a little bit confused, according to openstack.org: > > FEBRUARY 1 IS THE DEADLINE TO SUBMIT A TALK (11:59PM PST) > > I tried to edit a submitted talk and got the

Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

On Fri, Jan 29, 2016 at 6:30 PM, Julien Danjou wrote: > On Fri, Jan 29 2016, Foley, Emma L wrote: > > > Supporting statsd would require some more investigation, as collectd's > > statsd plugin supports reading stats from the system, but not writing > > them. > > I'm not sure

Re: [openstack-dev] Call for papers already closed?

It's definitely broken. We're getting the same messages for people who haven't submittted ANY talks. That said, the 3 proposal limit is NOT just for speakers, but also for SUBMITTERS. So be prepared, unless they broke it trying to change that, your colleagues are going to have to submit

Re: [openstack-dev] Call for papers already closed?

Hope somebody on the website infrastructure can help us. I have one presentation which was filled into the form but not submitted. Best Regards. -- Shane -Original Message- From: Nick Chase [mailto:nch...@mirantis.com] Sent: Monday, February 01, 2016 4:09 PM To:

Re: [openstack-dev] [mistral] Promoting Anastasia Kuznetsova to core reviewers

I'm not a core reviewer, but if I was, I'd definitely vote with +1. Great job, Anastasia! On Mon, Feb 1, 2016 at 4:45 PM, Nikolay Makhotkin wrote: > Hi, great work, Anastasia! > > +1 for you! > > On Fri, Jan 29, 2016 at 11:27 AM, Lingxian Kong >

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

Hi, I’ve read only part of letters in this huge interesting thread so far but I’d like to try to jump in and give some comments. API I personally don’t support using Mistral API as is. Maybe you came to agreement already about that, don’t know. I think that API should reflect user needs in

[openstack-dev] [puppet] weekly meeting #68

Hey, we'll have our weekly meeting tomorrow at 3pm UTC on #openstack-meeting4. https://wiki.openstack.org/wiki/Meetings/PuppetOpenStack As usual, free free to bring topics in this etherpad: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160201 We'll also have open discussion

Re: [openstack-dev] [stable][ceilometer][all] stable/kilo 2015.1.3 delayed

Jeremy Stanley wrote: I'm perfectly okay uploading a tarball I or someone else builds for this, as long as it's acceptable to leadership from stable branch management, Telemetry and the community at large. Our infrastructure exists to make things more consistent and convenient, but it's there to

Re: [openstack-dev] [mistral] Team meeting - 02/01/2016

Hi, guys, It's hardly for me to attend the meeting due to the inconvenient time for me. In M-3, I want to see resource sharing feature(particularly for workflow first) landed and support UUID in URL and mistralclient, which I have been working on currently. Hope you could consider that when you

[openstack-dev] [nova][neutron] New BP for live migration with direct pci passthru

Hi, all, I have registered a new BP about the live migration with a direct pci passthru device. Could you please help me to review it? Thanks in advance. The following is the details: -- SR-IOV has been supported

Re: [openstack-dev] Call for papers already closed?

Christian Berendt wrote: FEBRUARY 1 IS THE DEADLINE TO SUBMIT A TALK (11:59PM PST) I tried to edit a submitted talk and got the following message: Call for speaker closed! Also I have the following note in my interface: Warning! You reached presentations submissions limit (3). Yeah, it

Re: [openstack-dev] [nova][API]what's the purpose of fping in nova API?

On 01/29/2016 09:18 AM, Chen CH Ji wrote: > In doing some API work on > http://developer.openstack.org/api-ref-compute-v2.1.html > noticed that fping was [1] and try to ping the instance to check whether > it's pingable or not.. > but this is running on API service host which mostly have no access

Re: [openstack-dev] [nova][API] Question about HTTPNotImplementError

On 01/31/2016 09:45 PM, Ken'ichi Ohmichi wrote: > Hi Chen, > > The API guideline came from this Nova's implementation. > 501 case is not exception of microversion bumping[1] on Nova's rule > now, so I feeling we need a new microversion if changing the 501 > response to the other on *current

[openstack-dev] [Glance] [Artifacts] [app-catalog] Proposal to move artifacts meeting time

Hi all, Please find the request to move the artifacts meeting pushed half an hour later on the same day in the following review request. I got positive response from the initial poll. If you happened to miss today's meeting, please take a moment to vote on the review. The proposal is to have the

Re: [openstack-dev] [Horizon] Recent integration tests failures

Maintainers of outside dependencies continue to break our stuff :(. New issue is https://bugs.launchpad.net/horizon/+bug/1540495 patch is currently being checked by Jenkins On Sat, Jan 30, 2016 at 2:28 PM Timur Sufiev wrote: > Problematic Selenium versions have been

[openstack-dev] [oslo][all] Announcing our new Olso Project

The Olso team is proud to announce the release of Oslo Bingo. In Oslo we like to spice up our release notes using meaningful random adjectives [1]. Each month the Oslo team will select an adjective to be the Oslo Bingo word of the month. For February 2016 we have selected "jazzed" (from

Re: [openstack-dev] [stable][trove] Need help with replication API test failures on stable/liberty

Matt, Yes, I know of the earlier change you speak of. What I've been trying to figure out is how that change impacted stable branch. I think I've found the problem. Will push a fix as soon as I can run the idea by a couple of smarter people. -amrith > -Original Message- > From: Matt

[openstack-dev] [Neutron] Integrating physical appliance into virtual infrastructure

Hi , How to integrate a physical appliance into the virtual OpenStack infrastructure (with L2 population)? Can you please point me to any relevant material. We want to add the capability to "properly" schedule the port on the physical appliance, so that the rest of the virtual infrastructure

[openstack-dev] [neutron] - L3 flavors and issues with use cases for multiple L3 backends

Hi all, I've been working on an implementation of the multiple L3 backends RFE[1] using the flavor framework and I've run into some snags with the use-cases.[2] The first use cases are relatively straightforward where the user requests a specific flavor and that request gets dispatched to a

Re: [openstack-dev] [Horizon] Django

Hi Sandeep, If I understand you correctly, looks like you need to change 'row_actions' field here: https://github.com/openstack/horizon/blob/stable/kilo/openstack_dashboard/dashboards/project/networks/subnets/tables.py#L152 and replace UpdateSubnet with your custom action. You also might be

Re: [openstack-dev] It's better to ask forgiveness than permission

(I changed the title to stop hijacking the Oslo thread.) Hi, Le 30/01/2016 22:25, Julien Danjou a écrit : > (...) And it's easier/faster to fix with a larger team than a few. > Which mean inclusion. Which mean openness. While I think that Julien is a little bit rude and his email is stongly

Re: [openstack-dev] [senlin] translatin setup

Thanks Andreas, we'll propose patches to set this up. Regards, Qiming On Sun, Jan 31, 2016 at 07:36:29PM +0100, Andreas Jaeger wrote: > I noticed that senlin and python-senline havepot file in the tree > but is not using our usual translation setup - and have no > translations. > > Do you

Re: [openstack-dev] [api] service type vs. project name for use in headers

On Wed, Jan 27, 2016 at 1:47 PM, michael mccune wrote: > hi all, > > there have been a few reviews recently where the issue of service type > versus project name have come up for use in the headers. as usual this > conversation can get quite murky as there are several good

Re: [openstack-dev] Call for papers already closed?

Thierry Carrez wrote: Christian Berendt wrote: FEBRUARY 1 IS THE DEADLINE TO SUBMIT A TALK (11:59PM PST) I tried to edit a submitted talk and got the following message: Call for speaker closed! Also I have the following note in my interface: Warning! You reached presentations submissions

Re: [openstack-dev] [Magnum]Remove node object from Magnum

I think this is an excellent idea. I noticed this endpoint last week for the first time and was really confused about it. Since Heat is managing all the nodes, I agree Magnum shouldn't be tracking them. Corey On Mon, Feb 1, 2016 at 1:48 AM 王华 wrote: > Hi all, > > I

Re: [openstack-dev] [Neutron] Integrating physical appliance into virtual infrastructure

There is a project that aims at solving your use cases (at least from a general view) Its called L2GW and uses OVSDB Hardware VTEP schema (which is supported by many physical appliances for switching capabilities) Some information: https://wiki.openstack.org/wiki/Neutron/L2-GW There are also

Re: [openstack-dev] [Magnum] New Core Reviewers

+1 from me! On Mon, Feb 1, 2016 at 9:58 AM, Adrian Otto wrote: > Magnum Core Team, > > I propose Ton Ngo (Tango) and Egor Guz (eghobo) as new Magnum Core Reviewers. > Please respond with your votes. > > Thanks, > > Adrian Otto >

Re: [openstack-dev] [Neutron] Team meeting this Tuesday at 1400 UTC

I almost missed this because [Neutron] was missing from the subject. I'm replying now to add it in case someone else missed it. On Sat, Jan 30, 2016 at 2:27 PM, Armando M. wrote: > Hi neutrinos, > > According to [1], this is a kind reminder for next week's meeting: please do >

Re: [openstack-dev] [Magnum] New Core Reviewers

+1+1 Well deserved! On 01/02/2016, 15:58, "Adrian Otto" wrote: >Magnum Core Team, > >I propose Ton Ngo (Tango) and Egor Guz (eghobo) as new Magnum Core Reviewers. >Please respond with your votes. > >Thanks, > >Adrian Otto

Re: [openstack-dev] [Magnum]Remove node object from Magnum

Agreed. > On Jan 31, 2016, at 10:46 PM, 王华 wrote: > > Hi all, > > I want to remove node object from Magnum. The node object represents either a > bare metal or virtual machine node that is provisioned with an OS to run the > containers, or alternatively, > run

Re: [openstack-dev] [Neutron] Integrating physical appliance into virtual infrastructure

L2GW seems like a good option for bridging/linking /integrating physical appliances which does not support overlay technology (say VXLAN) natively. In my case the physical appliance supports VXLAN natively, meaning it can act as a VTEP. The appliance is capable of decapsulating packets that

Re: [openstack-dev] [nova][novaclient] Failing functional tests

On 02/01/2016 11:59 AM, Kevin L. Mitchell wrote: > I've been noticing that the functional tests on novaclient have been > consistently failing, and the test failures appear to be related to > keystone. I'm seeing tenant-create (using "admin" credentials) failing > with 404, and a tenant-get on

[openstack-dev] [mistral] Team meeting minutes/log - 02/01/2016

Thanks everyone for very productive meeting. We formed scope for M-3, link to the list of bps: https://launchpad.net/mistral/+milestone/mitaka-3 Meeting minutes and log: - http://eavesdrop.openstack.org/meetings/mistral/2016/mistral.2016-02-01-16.06.html -

Re: [openstack-dev] [Nova] notification subteam meeting

Hi, The next meeting of the nova notification subteam will happen 2016-02-02 Tuesday _17:00_ UTC [1] on #openstack-meeting-alt on freenode Agenda: - Status of the outstanding specs and code reviews - AOB See you there. Cheers, Gibi [1]

[openstack-dev] [puppet] Midcycle Sprint Summary

Last week, we had our midcycle sprint. Our group did a great job and here is a summary of what we worked on: * Make good progress on bug triage & bug fixing. ~25 bugs were triaged. * Unit & Functional testing for puppet-openstack-spec-helper (jobs are voting).

Re: [openstack-dev] [Horizon] Django

Hi Matthias, Thanks for your reply. As mentioned, I need to change the 'action' attribute of the 'Edit Subnet' button.\ Regards, Sandeep Makhija -Original Message- From: Matthias Runge [mailto:mru...@redhat.com] Sent: Monday, February 01, 2016 6:03 PM To:

[openstack-dev] [nova] Nova API sub-team meeting

We have weekly Nova API meeting tomorrow. The meeting is being held Tuesday UTC1200. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks

Re: [openstack-dev] [Nova] notification subteam meeting

> -Original Message- > From: Balázs Gibizer [mailto:balazs.gibi...@ericsson.com] > Sent: February 01, 2016 12:57 > To: 'OpenStack Development Mailing List (not for usage questions)' > Subject: Re: [openstack-dev] [Nova] notification subteam meeting > > Hi, > > The next meeting of the

Re: [openstack-dev] [nova] Non-priority Feature Freeze update (including deadlines)

On 31 January 2016 at 15:53, John Garbutt wrote: > Hi, > > We have recently past the deadline for the non-priority Feature Freeze: > http://docs.openstack.org/releases/schedules/mitaka.html#m-nova-npff > > We do this to make sure we prioritise review and developer bandwidth

Re: [openstack-dev] [Horizon] Django

On Mon, Feb 01, 2016 at 10:56:14AM +, Sandeep Makhija wrote: > Hi, > > I have been trying to fix a bug in horizon but I am a beginner in Django and > couldn't get my way through this code. > > Could somebody please help me with it? Below given are the details of what I > am looking for.

Re: [openstack-dev] [Cinder] Nominating Patrick East to Cinder Core

+1 from me. Patrick has done a great job the last several releases and his dedication to making Cinder better has been very visible. Patrick has been a strong contributor to Cinder over the last few releases, both with great code submissions and useful reviews. He also participates

[openstack-dev] [all] towards a keystone v3 only devstack

On Friday last week I hit the go button on a keystone v3 default patch change in devstack. While that made it through tests for all the tightly integrated projects, we really should have stacked up some other spot tests to see how this was going to impact the rest of the ecosystem. Novaclient,

[openstack-dev] [nova][novaclient] Failing functional tests

I've been noticing that the functional tests on novaclient have been consistently failing, and the test failures appear to be related to keystone. I'm seeing tenant-create (using "admin" credentials) failing with 404, and a tenant-get on "admin" fails with "No tenant with a name or ID of 'admin'

Re: [openstack-dev] [heat-translator][tacker] Openstack Artifact Repository

Hi Bruce, This is interesting and I would like to join the discussion at the summit. Regards, Sahdev Zala From: "Bruce Thompson (brucet)" To: "openstack-dev@lists.openstack.org" Date: 02/01/2016 10:53 AM Subject:

Re: [openstack-dev] [Cinder] Nominating Patrick East to Cinder Core

On 01/29/2016 07:04 PM, Sean McGinnis wrote: > Patrick has been a strong contributor to Cinder over the last few releases, > both with great code submissions and useful reviews. He also participates > regularly on IRC helping answer questions and providing valuable feedback. > > I would like to

[openstack-dev] [vitrage] Vitrage meeting tomorrow

Hi, We will have Vitrage weekly meeting tomorrow, Wednesday at 9:00 UTC, on #openstack-meeting-3 channel. Agenda: * Current status * Review action items * Next steps * Open Discussion You are welcome to join. Thanks, Ifat.

Re: [openstack-dev] [Magnum] New Core Reviewers

+1 for both. Welcome! From: 大塚元央 [mailto:yuany...@oeilvert.org] Sent: Tuesday, February 2, 2016 9:39 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Magnum] New Core Reviewers +1 welcome!! 2016年2月2日(火) 10:14

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

> On 02 Feb 2016, at 03:55, Dan Prince wrote: > > On Mon, 2016-02-01 at 15:17 +0600, Renat Akhmerov wrote: >> Hi, >> >> I’ve read only part of letters in this huge interesting thread so far >> but I’d like to try to jump in and give some comments. >> >> API >> I personally

Re: [openstack-dev] [mistral] Promoting Anastasia Kuznetsova to core reviewers

Alright, I think we all agree on that. Anastasia, welcome to the core team! Renat Akhmerov @ Mirantis Inc. > On 01 Feb 2016, at 14:50, Hardik Parekh wrote: > > I'm not a core reviewer, but if I was, I'd definitely vote with +1. > > Great job, Anastasia! > > On

Re: [openstack-dev] [openstack-ansible][designate] : Ansible Designate Role : NoEndpointFound error

Hi Jimmy, I have already included the designate_service_setup.yml file in the designate roles, but still I get this 'NoEndpointFound' error. Can you please take a look at the attached file. Thanks & Regards Swati Sharma System Engineer Tata Consultancy Services Ground to 8th Floors,

Re: [openstack-dev] [keystone][nova][cinder][horizon] Projects acting as a domain at the top of the project hierarchy

See inline response for horizon-related feedback. Hope this helps. -Lin On Sat, Jan 30, 2016 at 7:02 PM, Henry Nash wrote: > Hi > > One of the things the keystone team was planning to merge ahead of > milestone-3 of Mitaka, was “projects acting as a domain”. Up until now,

Re: [openstack-dev] [kuryr] Failed to create network with kuryr driver type

hi Vikas, ubuntu@kuryr1:~$ docker network create --driver=kuryr --ipam-driver=kuryr --subnet 10.10.0.0/16 --gateway 10.10.0.1 --ip-range 10.10.0.0/24 foo 68f14fe701710d6f3472d1626c33f0036a145aaa8d81265429e509cf759adfe1 ubuntu@kuryr1:~$ docker network ls NETWORK ID NAME

Re: [openstack-dev] [Horizon] Django

Hi Sandeep, Edit Subnet is a workflow that uses a _workflow.html to generate the HTML. The form attribute is generated by looking up workflow.attr_string in https://github.com/openstack/horizon/blob/5ef14e17961a699e5980b98aa7edb2a95a905c1b/horizon/templates/horizon/common/_workflow.html#L6 You

Re: [openstack-dev] [Magnum] New Core Reviewers

+1 welcome!! 2016年2月2日(火) 10:14 Eli Qiao : > +1 +1 thanks for both harding reviewing. > > On 2016年02月01日 23:58, Adrian Otto wrote: > > Magnum Core Team, > > > > I propose Ton Ngo (Tango) and Egor Guz (eghobo) as new Magnum Core > Reviewers. Please respond with your votes.

Re: [openstack-dev] [neutron] - L3 flavors and issues with use cases for multiple L3 backends

Yes, scheduling was a big gnarly wart that was punted for the first pass. The intention was that any driver you put in a single flavor had equivalent capabilities/plumbed to the same networks/etc. doug > On Feb 1, 2016, at 7:08 AM, Kevin Benton wrote: > > Hi all, > >

Re: [openstack-dev] [mistral] Team meeting - 02/01/2016

Yes, Lingxian, we did. Renat Akhmerov @ Mirantis Inc. > On 01 Feb 2016, at 16:27, Lingxian Kong wrote: > > Hi, guys, > > It's hardly for me to attend the meeting due to the inconvenient time for me. > In M-3, I want to see resource sharing feature(particularly for

Re: [openstack-dev] [Magnum] New Core Reviewers

+1 for both. Welcome! On Tue, Feb 2, 2016 at 12:12 PM, Kumari, Madhuri wrote: > +1 for both. Welcome! > > > > *From:* 大塚元央 [mailto:yuany...@oeilvert.org] > *Sent:* Tuesday, February 2, 2016 9:39 AM > *To:* OpenStack Development Mailing List (not for usage questions) <

[openstack-dev] [release][documentation] openstack-doc-tools release 0.33.0 (independent)

We are eager to announce the release of: openstack-doc-tools 0.33.0: Tools for OpenStack Documentation This release is part of the independent release series. With source available at: http://git.openstack.org/cgit/openstack/openstack-doc-tools With package available at:

Re: [openstack-dev] [openstack-ansible] Helion HLM on GitHub and what next?

Hi Kevin, At the moment don't think I'll be able to make it, however a number of my colleagues will be there, so definitely an opportunity. Be happy to start the discussion here so anyone not attending can get an idea of where things are going. My initial thoughts are that the first 2 places

Re: [openstack-dev] [api] service type vs. project name for use in headers

On 02/01/2016 09:13 AM, Brant Knudson wrote: > > > On Wed, Jan 27, 2016 at 1:47 PM, michael mccune > wrote: > > hi all, > > there have been a few reviews recently where the issue of service > type versus project name have come up for use

[openstack-dev] New L3 networking solution....

Hello everyone, just wanted to let you know that today we opened up the repos for the new open source networking project we’ve been working on. It’s called Romana and the project site is romana.io. Thought you would be interested because it enables multi-tenant networking without a virtual

Re: [openstack-dev] [oslo] nominating Ronald Bradford for oslo-core

On Fri, Jan 29, 2016 at 3:15 PM, Rochelle Grober wrote: > I'm not a voting member of the Oslo team, but a BIG > > +1 > > From me. > > --Rocky > > -Original Message- > From: Joshua Harlow [mailto:harlo...@fastmail.com] > Sent: Thursday, January 28, 2016 11:38

Re: [openstack-dev] [oslo] nominating Alexis Lee for oslo-core

On Thu, Jan 28, 2016 at 4:05 PM, Doug Hellmann wrote: > I am nominating Alexis Lee (lxsli) for oslo-core. > > Alexis has been working on adding configuration file reloading to > oslo.config this cycle. The work isn't complete, but at this point > he probably knows as much

Re: [openstack-dev] [oslo] Adding Dmitry Ukhlov to Oslo-Messaging-Core

+1 Yay Dmitry!! On Thu, Jan 28, 2016 at 11:00 AM Oleksii Zamiatin wrote: > My big +1 for Dmitry! > > On Thu, Jan 28, 2016 at 5:40 PM, Doug Hellmann > wrote: > >> Excerpts from Davanum Srinivas (dims)'s message of 2016-01-28 09:25:56 >> -0600: >>

[openstack-dev] [sahara] shelve/unshelve cluster

Hello, I need to add features "shelve/unshelve" a cluster (sahara shelve ). Is there anyone who had already worked on this issue ? Any suggestions will be welcome. Best regards, Yacine Saïbi __ OpenStack Development

Re: [openstack-dev] [neutron][i18n] networking-powervm: Manual Translations?

Thanks for bringing this to our attention Andreas. Switching our existing translation setup over seems like it would be a fairly straightforward process.   I'll talk things over with the team in IRC and drop by the i18n or infra channels if we have any questions.   - Adam     Adam Reznechek -

Re: [openstack-dev] [sahara][stable] stable/kilo blocked for sahara

On 1/28/2016 2:22 AM, Matt Riedemann wrote: All changes to Sahara on stable/kilo are blocked on the version change patch here: https://review.openstack.org/#/c/273011/ But that can't land because the gate-tempest-dsvm-sahara job is failing:

[openstack-dev] [heat-translator][tacker] Openstack Artifact Repository

During the mid cycle meeting there was a discussion on the Tacker repository and a potential replacement using the OpenStack artifact repository. Here is a link to a description of the OpenStack Artifact Repository:

Re: [openstack-dev] [sahara] shelve/unshelve cluster

Hi, Can explain more precisely, what does it mean exactly to "shelve/unshelve" cluster? On Mon, Feb 1, 2016 at 6:39 PM, Yacine SAÏBI wrote: > Hello, > > I need to add features "shelve/unshelve" a cluster (sahara shelve > ). > > Is there anyone who had already worked

[openstack-dev] [Magnum] New Core Reviewers

Magnum Core Team, I propose Ton Ngo (Tango) and Egor Guz (eghobo) as new Magnum Core Reviewers. Please respond with your votes. Thanks, Adrian Otto __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [Magnum] New Core Reviewers

+1 -Original Message- From: Adrian Otto [mailto:adrian.o...@rackspace.com] Sent: February-01-16 10:59 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [Magnum] New Core Reviewers Magnum Core Team, I propose Ton Ngo (Tango) and Egor Guz (eghobo) as new Magnum Core

  1   2   >