Re: [openstack-dev] [Nova] live migration sub-team meeting

hi Paul +1, will attend for this meeting. On 2015年11月10日 19:48, Murray, Paul (HP Cloud) wrote: Thank you for the prompting Michael. I was chasing up a couple of key people to make sure they were available. The IRC meeting should be Tuesdays at 1400 UTC on #openstack-meeting-3 starting next

Re: [openstack-dev] [Neutron][IPAM] ML2 don't call ipam driver remove_subnet function

Hi, This should be resolved with this path - https://review.openstack.org/239885 Good luck Gary From: thanh le giang mailto:legiangth...@gmail.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Date: Wednesday, November 11, 2015 at 5:20 AM To: OpenStack List mailto:opensta

Re: [openstack-dev] Introducing Lwood - a weekly summary of openstack-dev traffic

On 10/11/2015 19:50, Thierry Carrez wrote: Hugh Blemings wrote: [...] http://hugh.blemings.id.au/category/Lwood/feed/ You should federate that one to Planet OpenStack! See instructions at: https://wiki.openstack.org/wiki/AddingYourBlog Thanks for the reminder - have done so now (assum

[openstack-dev] [HA][RabbitMQ][messaging][Pacemaker][operators] Improved OCF resource agent for dynamic active-active mirrored clustering

Thank you Andrew. Answers below. >>> Sounds interesting, can you give any comment about how it differs to the other[i] upstream agent? Am I right that this one is effectively A/P and wont function without some kind of shared storage? Any particular reason you went down this path instead of full A

Re: [openstack-dev] [Fuel][Fuel-QA][Fuel-TechDebt] Code Quality: Do Not Hardcode - Fix Things Instead

+1 from me On Tue, Nov 10, 2015 at 6:38 PM, Stanislaw Bogatkin wrote: > I think that it is excellent thought. > +1 > > On Tue, Nov 10, 2015 at 6:52 PM, Vladimir Kuklin > wrote: > >> Folks >> >> I wanted to raise awareness about one of the things I captured while >> doing reviews recently - we a

Re: [openstack-dev] [nova][cinder] About rebuilding volume-backed instances.

Excerpts from Zhenyu Zheng's message of 2015-11-09 00:21:23 -0800: > Hi, > > Thanks for the reply, for some scenario, launching an new instance is > easier. But for production deployment, an instance may contain a large > number of data such as keypairs, metadata, bdm etc. and it may have > multip

Re: [openstack-dev] [Manila] Design summit notes

Ben, thanks a lot for this wrap-up, much appreciated! 2015-11-10 22:25 GMT+01:00 Ben Swartzlander : > I wasn't going to write a wrap-up email this time around since so many > people were able to attend in person, but enough people missed it that I > changed my mind and decided to write down my o

Re: [openstack-dev] [nova][cinder] About rebuilding volume-backed instances.

On Mon, Nov 9, 2015 at 8:15 AM, Zhenyu Zheng wrote: > Hi, thanks all for replying, sorry I might be a bit unclear. > > We have user demands that we only change the root device of an > volume-backed instance for upper layer services. It's not cloudy but it is > quite common. And changing OS is ano

Re: [openstack-dev] Help with getting keystone to migrate to Debian testing: fixing repoze.what and friends

On Nov 10, 2015 16:48, "Clint Byrum" wrote: > > Excerpts from Morgan Fainberg's message of 2015-11-10 15:31:16 -0800: > > On Tue, Nov 10, 2015 at 3:20 PM, Thomas Goirand wrote: > > > > > Hi there! > > > > > > All of Liberty would be migrating from Sid to Testing (which is the > > > pre-condition

[openstack-dev] [Neutron][IPAM] ML2 don't call ipam driver remove_subnet function

Dear folks I have met a problem when implement IPAM driver, ML2 doesn't call remove_subnet function of ipam driver because ML2 doesn't use delete_subnet function of NeutronDbPluginV2 Now I workaround by using "SUBNET BEFORE_DELETE" event to notify external IPAM that subnet will be deleted, but I

Re: [openstack-dev] [fuel] Add Fuel to OpenStack projects: status update

Dima, +1 to "additional scrutiny is there because they want to get this right. Lets prove that their trust in us is not misplaced." Thanks, Dims On Tue, Nov 10, 2015 at 10:10 PM, Dmitry Borodaenko wrote: > As you may have guessed, many Fuel developers were holding their breath > for the Technic

[openstack-dev] [fuel] Add Fuel to OpenStack projects: status update

As you may have guessed, many Fuel developers were holding their breath for the Technical Committee meeting today, where the decision on whether to accept Fuel into Big Tent as an OpenStack project [0] was on the agenda [1]. [0] https://review.openstack.org/199232 [1] http://eavesdrop.openstack.o

[openstack-dev] [neutron][tap-as-a-service] weekly meeting

hi, tap-as-a-service meeting will be held weekly, starting today. http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting anyone interested in the project is welcome. sorry for immediate notice. __ OpenStack Development Mail

Re: [openstack-dev] [stable][infra][neutron] ZUUL_BRANCH not set for periodic stable jobs

+1 thanks for being on top of this Ihar On Mon, 2015-11-09 at 20:10 -0500, Assaf Muller wrote: > On Mon, Nov 9, 2015 at 5:30 PM, Ihar Hrachyshka wrote: > > Jeremy Stanley wrote: > > > >> On 2015-11-09 17:31:00 +0100 (+0100), Ihar Hrachyshka wrote: > >> [...] > >>> > >>> From the failure log, I d

Re: [openstack-dev] [kuryr] gerrit/git review problem error code 10061

Thanks to all! It seems network connectivity problem. How sad again! :( i will try other ways. On Tue, Nov 10, 2015 at 12:52 AM, Jeremy Stanley wrote: > On 2015-11-09 10:13:33 +0800 (+0800), Baohua Yang wrote: > > Anyone recently meet such problem after cloning the latest code > > from kuryr? T

[openstack-dev] [NFV][Telco] Meeting Reminder - November 11th - 1400 UTC

Hi all, Just a reminder this week's Telco Working Group meeting is scheduled for Wednesday the 11th at 1400 UTC. As always the agenda etherpad is here: https://etherpad.openstack.org/p/nfv-meeting-agenda I recognize that many folks will be at OPNFV summit this week but we will see how we g

Re: [openstack-dev] [networking-ovn] ovn-northd is a spof

On 11/10/2015 07:06 PM, gong_ys2004 wrote: > Regard this, I read some architecture doc of it, SPOF in OVN way exists > in two place: > 1. ovn-northd, I don't know if we can run multiple ones, but the arch > doc demos only one The idea is that we will make it so you can run multiple. We haven't do

Re: [openstack-dev] Help with getting keystone to migrate to Debian testing: fixing repoze.what and friends

Excerpts from Morgan Fainberg's message of 2015-11-10 15:31:16 -0800: > On Tue, Nov 10, 2015 at 3:20 PM, Thomas Goirand wrote: > > > Hi there! > > > > All of Liberty would be migrating from Sid to Testing (which is the > > pre-condition for an upload to offical Debian backports) if I didn't > > h

[openstack-dev] [networking-ovn] ovn-northd is a spof

hi,I know everyone want to provide there own neutron implementation, networking-ovn is one of themRegard this, I read some architecture doc of it, SPOF in OVN way exists in two place:1. ovn-northd, I don't know if we can run multiple ones, but the arch doc demos only one2. north db and south db,

[openstack-dev] [telemetry][gnocchi] defining scope/domain

hi, i was doing some googling on the current state of time series databases to see if there was a worthwhile db to implement as a Gnocchi driver and it seems we're currently in the same state as before: there are flaws with all open source time series databases but if you have lots of money,

Re: [openstack-dev] [neutron][sfc] How could an L2 agent extension access agent methods ?

Ihar, Networking-sfc installs flows on br-int and br-tun for steering traffic to the SFC port-pairs. On each bridge additional tables are used for an egress forwarding pipeline (from the service VM port) and an ingress pipeline (to the service VM port). Rpc operations between the OVS driver and

Re: [openstack-dev] Help with getting keystone to migrate to Debian testing: fixing repoze.what and friends

On Tue, Nov 10, 2015 at 3:20 PM, Thomas Goirand wrote: > Hi there! > > All of Liberty would be migrating from Sid to Testing (which is the > pre-condition for an upload to offical Debian backports) if I didn't > have a really annoying situation with the repoze.{what,who} packages. I > feel like I

[openstack-dev] Help with getting keystone to migrate to Debian testing: fixing repoze.what and friends

Hi there! All of Liberty would be migrating from Sid to Testing (which is the pre-condition for an upload to offical Debian backports) if I didn't have a really annoying situation with the repoze.{what,who} packages. I feel like I could get some help from the Python export folks here. What is it

Re: [openstack-dev] [neutron][sfc] How could an L2 agent extension access agent methods ?

Hi Vikram, Thanks for the heads-up. Take care of yourself and your family. We will provide the feedback on L2 agent. Thanks, Cathy From: Vikram Choudhary [mailto:viks...@gmail.com] Sent: Monday, November 09, 2015 6:59 PM To: OpenStack Development Mailing List (not for usage questions); Cathy Zha

Re: [openstack-dev] [neutron][sfc] How could an L2 agent extension access agent methods ?

Hi Ihar, Thanks for initiating this discussion. I am in OPNFV Summit. Henry Fourie of SFC project team will reply with our feedback. Cathy -Original Message- From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] Sent: Monday, November 09, 2015 4:44 AM To: OpenStack Development Mailing Li

Re: [openstack-dev] [neutron][qos][fwaas] service groups vs. traffic classifiers

Sean and Mickey +1 As much as I like us using the same API to create classifiers (users only need to learn one way) I think for the short term we should work with our own constructs and rely on a common data model. That will allow us to iterate faster on the REST API level and not have prematur

Re: [openstack-dev] [heat][keystone] How to handle request for global admin in policy.json?

On Tue, Nov 10, 2015 at 10:53:46AM -0500, Adam Young wrote: > On 11/10/2015 05:08 AM, Henry Nash wrote: > >Steve, > > > >Currently, your best option is to use something similar to the > >policy.v3cloudsample.json, where you basically “bless” a project (or domain) > >as being the “cloud admin proj

[openstack-dev] [Manila] Design summit notes

I wasn't going to write a wrap-up email this time around since so many people were able to attend in person, but enough people missed it that I changed my mind and decided to write down my own impressions of the sessions. Wednesday working session: Migration Improvements --

Re: [openstack-dev] [neutron][upgrade] new 'all things upgrade' subteam

I am interested too and will be available to the subteam. On Tue, Nov 10, 2015 at 9:03 PM, Sean M. Collins wrote: > I'm excited. I plan on attending and being part of the subteam. I think > the tags that Dan Smith recently introduced could be our deliverables, > where this subteam focuses on wor

Re: [openstack-dev] [neutron][upgrade] new 'all things upgrade' subteam

I'm excited. I plan on attending and being part of the subteam. I think the tags that Dan Smith recently introduced could be our deliverables, where this subteam focuses on working towards Neutron being tagged with these tags. https://review.openstack.org/239771 - Introduce assert:supports-upgrade

[openstack-dev] [Solum] Hack day / Bug triage day

Hi Solum team, In last two IRC meetings we have discussed about spending a day triaging Solum bugs. In today's meeting, participants agreed to do this on November 18, 2015. You can find today's meeting logs here: http://eavesdrop.openstack.org/meetings/solum_team_meeting/2015/solum_team_meeting.2

Re: [openstack-dev] [rpm-packaging] core reviewers nomination

Haikel, > I'd like to propose new candidates for RPM packaging core reviewers: > Alan Pevec > Jakub Ruzicka +1 Greetings, Dirk __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ

Re: [openstack-dev] [OpenStack-Infra] Report from Gerrit User Summit

On 11/10/2015 02:24 PM, David Pursehouse wrote: > On Tue, Nov 10, 2015 at 4:53 AM Sean Dague > wrote: > > <...> > > Is there any update on label:Code-Review<=-1,group:nova-core ? The group > search support is documented, but as far as I can tell doesn't work >

[openstack-dev] [Neutron] Stop pushing stuff to the gate queue

Neutron Cores, We have high failure rate (see [1] for more context). We have an initial bug report [2] filed, and more triaged is happening. Let's hold on before we push stuff to the gate queue. Once [2] is solved and the fire is put out, we'll resume the merge frenzy. As a general reminder, ple

Re: [openstack-dev] [Fuel] Running Fuel node as non-superuser

Stanislaw, I've been experimenting with 'capsh' on the 6.1 master node and it doesn't seem to preserve any capabilities when setting SECURE_NOROOT bit, even if explicitely told to do so (via either --keep=1 or "SECURE_KEEP_CAPS" bit). On Tue, Nov 10, 2015 at 11:20 AM, Dmitry Nikishov wrote: > B

Re: [openstack-dev] [neutron] [gate] 35% failure rate for neutron tempest jobs

On 10 November 2015 at 11:11, Sean Dague wrote: > On 11/10/2015 01:37 PM, Armando M. wrote: > > > > > > On 10 November 2015 at 09:49, Sean Dague > > wrote: > > > > The neutron tempest jobs are now at a 35% failure rate: > > http://tinyurl.com/ne3ex4v (note, 35% is

Re: [openstack-dev] Can we get some sanity in the Neutron logs please?

On 10 November 2015 at 11:12, Matt Riedemann wrote: > > > On 11/10/2015 1:10 PM, Matt Riedemann wrote: > >> >> >> On 11/10/2015 12:51 PM, Armando M. wrote: >> >>> >>> >>> On 10 November 2015 at 10:33, Matt Riedemann >> > wrote: >>> >>> Let me qualify by sayi

Re: [openstack-dev] Can we get some sanity in the Neutron logs please?

On 10 November 2015 at 11:10, Matt Riedemann wrote: > > > On 11/10/2015 12:51 PM, Armando M. wrote: > >> >> >> On 10 November 2015 at 10:33, Matt Riedemann > > wrote: >> >> Let me qualify by saying I'm not a Neutron person. >> >> We know that gate-tempes

Re: [openstack-dev] [OpenStack-Infra] Report from Gerrit User Summit

On Tue, Nov 10, 2015 at 4:53 AM Sean Dague wrote: <...> Is there any update on label:Code-Review<=-1,group:nova-core ? The group > search support is documented, but as far as I can tell doesn't work > except under very specific ldap configs. > https://code.google.com/p/gerrit/issues/detail?id=30

Re: [openstack-dev] [Group-based-policy]

On Tue, Nov 10, 2015 at 8:41 AM, Duarte Cardoso, Igor < igor.duarte.card...@intel.com> wrote: > Hi Ernesto, > > > > Let me answer the first question for you. > > > > You can use GBP without OpenDaylight. > > > > OpenDaylight has a separate Group-based Policy project, which might make > you wonder

Re: [openstack-dev] [release][stackalytics] possibly breaking bug closing statistics?

Doug, You are right, there should not be any changes in the stats. Bugs are mapped to release only by date, target milestone is not taken into account. For resolved bugs metric Stackalytics uses 'date_fix_commited' field, for filed bugs metric - 'date_created'. Thanks, Ilya 2015-11-10 0:53 GMT+0

Re: [openstack-dev] Can we get some sanity in the Neutron logs please?

On 11/10/2015 1:10 PM, Matt Riedemann wrote: On 11/10/2015 12:51 PM, Armando M. wrote: On 10 November 2015 at 10:33, Matt Riedemann mailto:mrie...@linux.vnet.ibm.com>> wrote: Let me qualify by saying I'm not a Neutron person. We know that gate-tempest-dsvm-neutron-full is failing

Re: [openstack-dev] Regarding Designate Issues

On 10/11/15 11:02, Sharma Swati6 wrote: > Hi All, > > I am trying to install Designate using Devstack-Kilo but facing the > following issues while starting its services- > > 1. WARNING keystone.common.wsgi [-] Could not find service: dns > 2. WARNING keystone.common.wsgi [-] Could not find proj

Re: [openstack-dev] [neutron] [gate] 35% failure rate for neutron tempest jobs

On 11/10/2015 01:37 PM, Armando M. wrote: > > > On 10 November 2015 at 09:49, Sean Dague > wrote: > > The neutron tempest jobs are now at a 35% failure rate: > http://tinyurl.com/ne3ex4v (note, 35% is basically the worst possible > fail rate, because it's just

Re: [openstack-dev] Can we get some sanity in the Neutron logs please?

On 11/10/2015 12:51 PM, Armando M. wrote: On 10 November 2015 at 10:33, Matt Riedemann mailto:mrie...@linux.vnet.ibm.com>> wrote: Let me qualify by saying I'm not a Neutron person. We know that gate-tempest-dsvm-neutron-full is failing hard as of the last 24 hours [1]. An e

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

Sean Dague wrote: On 11/10/2015 05:12 AM, Thierry Carrez wrote: Kevin Carter wrote: I believe Clint already linked to https://aphyr.com/posts/309-knossos-redis-and-linearizability or similar - but 'known for general ease of use and reliability' is uhm, a bold claim. Its worth comparing that (an

Re: [openstack-dev] Can we get some sanity in the Neutron logs please?

On 10 November 2015 at 10:33, Matt Riedemann wrote: > Let me qualify by saying I'm not a Neutron person. > > We know that gate-tempest-dsvm-neutron-full is failing hard as of the last > 24 hours [1]. > > An error that's been showing up in tempest runs with neutron a lot is: > > "AssertionError: 0

[openstack-dev] [searchlight] Searching admin-only fields

An issue discovered at the end of the Liberty cycle [1] meant that while still present in results (for admins) we had to disable searching of admin-only fields (TL;DR – a non-admin can fish for results to discover values for admin-only fields by searching e.g. "hostId": "a*"). We'd like to fix t

Re: [openstack-dev] [oslo.messaging] State wrapping in the MessageHandlingServer

Matthew Booth wrote: My patch to MessageHandlingServer is currently being reverted because it broke Nova tests: https://review.openstack.org/#/c/235347/ Specifically it causes a number of tests to take a very long time to execute, which ultimately results in the total build time limit being exc

Re: [openstack-dev] [neutron] [gate] 35% failure rate for neutron tempest jobs

On 10 November 2015 at 09:49, Sean Dague wrote: > The neutron tempest jobs are now at a 35% failure rate: > http://tinyurl.com/ne3ex4v (note, 35% is basically the worst possible > fail rate, because it's just passing enough to land patches that cause > that kind of fail on two test runs check/gat

[openstack-dev] Can we get some sanity in the Neutron logs please?

Let me qualify by saying I'm not a Neutron person. We know that gate-tempest-dsvm-neutron-full is failing hard as of the last 24 hours [1]. An error that's been showing up in tempest runs with neutron a lot is: "AssertionError: 0 == 0 : No IPv4 addresses found in: []" So checking logstash [2

[openstack-dev] [oslo.messaging] State wrapping in the MessageHandlingServer

My patch to MessageHandlingServer is currently being reverted because it broke Nova tests: https://review.openstack.org/#/c/235347/ Specifically it causes a number of tests to take a very long time to execute, which ultimately results in the total build time limit being exceeded. This is very eas

Re: [openstack-dev] [OpenStack-Infra] Report from Gerrit User Summit

Thanks for the report Jim. I got excited about polygerrit and deployed it sortof... pointing at review-dev.o.o in case anyone wants to kick the tires. http://polygerrit.nibalizer.com/q/status:open After the gerrit upgrade next week we can point it at review.o.o. I think it would be good for infra

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 11/10/2015 11:18 AM, Dmitry Tantsur wrote: > On 11/10/2015 06:08 PM, Ben Nemec wrote: >> On 11/10/2015 10:28 AM, John Trowbridge wrote: >>> >>> >>> On 11/10/2015 10:43 AM, Ben Nemec wrote: On 11/10/2015 05:26 AM, John Trowbridge wrote: > > > On 11/09/2015 07:44 AM, Dmitry Tantsu

Re: [openstack-dev] [nova] Proposal to add Sylvain Bauza to nova-core

On Nov 6, 2015, at 7:32, John Garbutt wrote: > Hi, > > I propose we add Sylvain Bauza[1] to nova-core. > > Over the last few cycles he has consistently been doing great work, > including some quality reviews, particularly around the Scheduler. > > Please respond with comments, +1s, or objectio

Re: [openstack-dev] [nova] Proposal to add Alex Xu to nova-core

On Nov 6, 2015, at 7:32, John Garbutt wrote: > Hi, > > I propose we add Alex Xu[1] to nova-core. > > Over the last few cycles he has consistently been doing great work, > including some quality reviews, particularly around the API. > > Please respond with comments, +1s, or objections within on

[openstack-dev] [all] devstack-gate jobs that will break at Mitaka-1

Here is the weekly list of jobs that will no longer work at Mitaka-1 when we remove extras.d support in devstack (and the number of runs in the last 48 hours): gate-congress-dsvm-api 652 gate-murano-congress-devstack-dsvm 284 gate-cue-integration-dsvm-rabbitmq 176 gate-designate-dsvm-po

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 09/11/15 07:44, Dmitry Tantsur wrote: As we already have "openstack undercloud" and "openstack overcloud" prefixes for TripleO, I suggest we move these commands under "openstack overcloud nodes" namespace. So we end up with: overcloud nodes import overcloud nodes configure ready state --

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

Thierry Carrez wrote: Hi everyone, A few cycles ago we set up the Release Cycle Management team which was a bit of a frankenteam of the things I happened to be leading: release management, stable branch maintenance and vulnerability management. While you could argue that there was some overlap

[openstack-dev] [neutron] [gate] 35% failure rate for neutron tempest jobs

The neutron tempest jobs are now at a 35% failure rate: http://tinyurl.com/ne3ex4v (note, 35% is basically the worst possible fail rate, because it's just passing enough to land patches that cause that kind of fail on two test runs check/gate with a coin flip). The failure is currently seen here -

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On Tue, Nov 10, 2015 at 10:13:09AM +0100, Thierry Carrez wrote: > Matthew Treinish wrote: > > [...] > > The discussion here is about the cross project effort around stable > > branches, > > which by design is a more limited scope now. Right now the cross project > > effort > > around stable branc

[openstack-dev] Cross-Project Meeting SKIPPED, Tue Nov 10th, 21:00 UTC

Hi all! As discussed in the previous cross-project meeting [1], we will be skipping meetings if there is no agenda items to discuss. There are no items to discuss this time around, but someone can still call for a meeting by adding an agenda item for November 17th [2]. To keep up with the cross-p

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 11/10/2015 10:40 AM, Dmitry Tantsur wrote: > On 11/10/2015 05:18 PM, Ben Nemec wrote: >> +1 to moving anything we can into Ironic itself. >> >> I do want to note that if we rename anything, we can't just rip and >> replace. We have users of the current commands, and we need to >> deprecate thos

Re: [openstack-dev] [Fuel] Running Fuel node as non-superuser

Bartolomiej, Adam, Stanislaw is correct. And this is going to be ported to master. The goal currently is to reach an agreement on the implementation so that there's going to be a some kinf of compatibility during upgrades. Stanislaw, Do I understand correctly that you propose using something like

[openstack-dev] [HA] weekly High Availability meetings on IRC start next Monday

Hi all, After some discussion in Tokyo by stakeholders in OpenStack High Availability, I'm pleased to announce that from next Monday we're starting a series of weekly meetings on IRC. Details are here: https://wiki.openstack.org/wiki/Meetings/HATeamMeeting http://eavesdrop.openstack.org/#Hig

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 11/10/2015 06:08 PM, Ben Nemec wrote: On 11/10/2015 10:28 AM, John Trowbridge wrote: On 11/10/2015 10:43 AM, Ben Nemec wrote: On 11/10/2015 05:26 AM, John Trowbridge wrote: On 11/09/2015 07:44 AM, Dmitry Tantsur wrote: Hi OOO'ers, hopefully the subject caught your attentions :) Curren

Re: [openstack-dev] [fuel] Using upstream packages & modules

Alex Thanks for your very detailed answer - it clarified things a bit. So, if you would allow me to rephrase it - you are actually conducting a research on what is the actual gap between our downstream/fork and upstream UCA/puppet-openstack. This seems to be a very promising initiative. Are you go

Re: [openstack-dev] [tacker] Proposing Sripriya Seetharam to Tacker core

+1 On Mon, Nov 9, 2015 at 6:22 PM, Sridhar Ramaswamy wrote: > I'd like to propose Sripriya Seetharam to join the Tacker core team. > Sripriya > ramped up quickly in early Liberty cycle and had become an expert in the > Tacker > code base. Her major contributions include landing MANO API blueprin

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 11/10/2015 10:28 AM, John Trowbridge wrote: > > > On 11/10/2015 10:43 AM, Ben Nemec wrote: >> On 11/10/2015 05:26 AM, John Trowbridge wrote: >>> >>> >>> On 11/09/2015 07:44 AM, Dmitry Tantsur wrote: Hi OOO'ers, hopefully the subject caught your attentions :) Currently, tripleocl

Re: [openstack-dev] [Ironic] Do we need to have a mid-cycle?

On 11/10/2015 05:45 PM, Lucas Alvares Gomes wrote: Hi, In the last Ironic meeting [1] we started a discussion about whether we need to have a mid-cycle meeting for the Mitaka cycle or not. Some ideas about the format of the midcycle were presented in that conversation and this email is just a fo

Re: [openstack-dev] [tacker] Proposing Sripriya Seetharam to Tacker core

+1 From: Sridhar Ramaswamy [mailto:sric...@gmail.com] Sent: Monday, November 09, 2015 6:22 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [tacker] Proposing Sripriya Seetharam to Tacker core I'd like to propose Sripriya Seetharam to join the Tacker co

[openstack-dev] [Ironic] Do we need to have a mid-cycle?

Hi, In the last Ironic meeting [1] we started a discussion about whether we need to have a mid-cycle meeting for the Mitaka cycle or not. Some ideas about the format of the midcycle were presented in that conversation and this email is just a follow up on that conversation. The ideas presented we

Re: [openstack-dev] [Fuel] Master node upgrade

Evgeniy I am not sure you addressed me, but, anyway, - yes, we will have a situation with old containers on new host node. This will be identical to old host node from database migration point of view. On Tue, Nov 10, 2015 at 7:38 PM, Evgeniy L wrote: > Hi Vladimir, > > Just to make sure that w

Re: [openstack-dev] [Fuel] shotgun code freeze

+1 to Dmitry, thanks for pushing this activity Vladimir. On Friday, 6 November 2015, Dmitry Pyzhov wrote: > Great job! We are much closer to removal of fuel-web repo. > > On Tue, Oct 27, 2015 at 7:35 PM, Vladimir Kozhukalov < > vkozhuka...@mirantis.com > > wrote: > >> Dear colleagues, >> >> I am

Re: [openstack-dev] [Group-based-policy]

Hi Ernesto, Let me answer the first question for you. You can use GBP without OpenDaylight. OpenDaylight has a separate Group-based Policy project, which might make you wonder if you need it to run OpenStack GBP. Don’t worry, you can deploy OpenStack GBP right away without OpenDaylight. Best

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 11/10/2015 10:08 AM, Tzu-Mainn Chen wrote: > Hi all, > > At the last IRC meeting it was agreed that the new TripleO REST API > should forgo the Tuskar name, and simply be called... the TripleO > API. There's one more point of discussion: where should the API > live? There are two possibilit

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 11/10/2015 05:18 PM, Ben Nemec wrote: +1 to moving anything we can into Ironic itself. I do want to note that if we rename anything, we can't just rip and replace. We have users of the current commands, and we need to deprecate those to give people a chance to move to the new ones. Definit

Re: [openstack-dev] [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

On 11/9/2015 10:15 PM, Matthew Treinish wrote: On Mon, Nov 09, 2015 at 05:05:36PM +1100, Tony Breeds wrote: On Fri, Nov 06, 2015 at 10:12:21AM -0800, Clint Byrum wrote: The argument in the original post, I think, is that we should not stand in the way of the vendors continuing to collaborate

Re: [openstack-dev] [Fuel] Master node upgrade

Hi Vladimir, Just to make sure that we are on the same page. We'll have to use upgrade script anyway, since you will need to run database migration and register new releases. Thanks, On Monday, 9 November 2015, Vladimir Kozhukalov wrote: > Looks like most people thing that building backup/re-i

Re: [openstack-dev] [Fuel][Fuel-QA][Fuel-TechDebt] Code Quality: Do Not Hardcode - Fix Things Instead

I think that it is excellent thought. +1 On Tue, Nov 10, 2015 at 6:52 PM, Vladimir Kuklin wrote: > Folks > > I wanted to raise awareness about one of the things I captured while doing > reviews recently - we are sacrificing quality to bugfixing and feature > development velocity, essentially mov

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

On 11/10/2015 10:28 AM, Renat Akhmerov wrote: On 09 Nov 2015, at 20:43, Adam Young wrote: On 11/06/2015 06:28 PM, Tim Hinrichs wrote: Congress allows users to write a policy that executes an action under certain conditions. The conditions can be based on any data Congress has access to, w

Re: [openstack-dev] [Ironic] Quick poll: OpenStackClient command for provision action

On 11/10/2015 05:21 PM, Brad P. Crochet wrote: On Tue, Nov 10, 2015 at 4:09 AM, Dmitry Tantsur wrote: Hi all! I'd like to seek consensus (or at least some opinions) on patch https://review.openstack.org/#/c/206119/ It proposed the following command: I think it's time to actually just write

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 11/10/2015 10:43 AM, Ben Nemec wrote: > On 11/10/2015 05:26 AM, John Trowbridge wrote: >> >> >> On 11/09/2015 07:44 AM, Dmitry Tantsur wrote: >>> Hi OOO'ers, hopefully the subject caught your attentions :) >>> >>> Currently, tripleoclient exposes several commands in "openstack >>> baremetal" a

Re: [openstack-dev] [oslo] Graduate apiclient library

On Tue, Nov 10, 2015 at 9:57 AM, Adam Young wrote: > +2. keystoneauth is designed to be the library explicitly for this. Do > not duplicate auth behavior anywhere else in the supported client libraries. > To expand on this point a bit, if you are considering re-working the existing client libs

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

On 11/10/2015 05:14 PM, Dean Troyer wrote: On Tue, Nov 10, 2015 at 9:46 AM, Dmitry Tantsur mailto:dtant...@redhat.com>> wrote: inspect, manage, provide, active and abort are all provisioning verbs used in ironic API. they usually represent some complex operations on a node. Inspect

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On 11/10/2015 5:41 AM, Alan Pevec wrote: The Stable Branch Policy, lets not put it in any repo. Doing that would give indication that we expect changes into it and I'd prefer that policy mostly staying stable as well. What indication did it give when it was in wiki? :) It actually already

Re: [openstack-dev] Learning to Debug the Gate

There is also a neutron issue which is causing a 35% failure rate in neutron jobs - http://tinyurl.com/ne3ex4v That one still needs resolution. On 11/10/2015 10:54 AM, Davanum Srinivas wrote: > Took about 35 mins or so :) > > -- Dims > > On Tue, Nov 10, 2015 at 10:45 AM, Matt Riedemann > wrote

Re: [openstack-dev] [Ironic] Quick poll: OpenStackClient command for provision action

On Tue, Nov 10, 2015 at 10:53 AM, Dean Troyer wrote: > On Tue, Nov 10, 2015 at 9:32 AM, Brad P. Crochet wrote: >> >> In this case, the noun is actually 'baremetal provision state'. The >> 'action' is the states themselves. It doesn't fit exactly, but seems >> to at least be somewhat natural. > >

Re: [openstack-dev] [Ironic] Quick poll: OpenStackClient command for provision action

On Tue, Nov 10, 2015 at 4:09 AM, Dmitry Tantsur wrote: > Hi all! > > I'd like to seek consensus (or at least some opinions) on patch > https://review.openstack.org/#/c/206119/ > It proposed the following command: > I think it's time to actually just write up a spec on this. I think we would be be

Re: [openstack-dev] [Ironic] Quick poll: OpenStackClient command for provision action

On Tue, Nov 10, 2015 at 10:14 AM, Brad P. Crochet wrote: > There was some discussion on one of the patches about changing to > 'baremetal node'. I was a little concerned by that since the original > 'baremetal' commands have landed, but I think since they landed > post-Liberty, we wouldn't need t

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

On Tue, Nov 10, 2015 at 11:14 AM, Dean Troyer wrote: > On Tue, Nov 10, 2015 at 9:46 AM, Dmitry Tantsur wrote: >> >> inspect, manage, provide, active and abort are all provisioning verbs >> used in ironic API. they usually represent some complex operations on a >> node. Inspection is not related

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

+1 to moving anything we can into Ironic itself. I do want to note that if we rename anything, we can't just rip and replace. We have users of the current commands, and we need to deprecate those to give people a chance to move to the new ones. A few more thoughts inline. On 11/09/2015 06:44 AM

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

On Tue, Nov 10, 2015 at 9:46 AM, Dmitry Tantsur wrote: > inspect, manage, provide, active and abort are all provisioning verbs > used in ironic API. they usually represent some complex operations on a > node. Inspection is not related to showing, it's about fetching hardware > properties from ha

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 11/10/2015 04:47 PM, Dmitry Tantsur wrote: On 11/10/2015 04:37 PM, Giulio Fidente wrote: On 11/10/2015 04:16 PM, Dmitry Tantsur wrote: On 11/10/2015 04:08 PM, Tzu-Mainn Chen wrote: Hi all, At the last IRC meeting it was agreed that the new TripleO REST API should forgo the Tuskar name, and

Re: [openstack-dev] [Neutron] Reminder: Team meeting on Monday at 2100 UTC

Dear Vikram, Our deepest condolences for you and your family. Do not even think about work these days. Edgar From: Vikram Choudhary mailto:viks...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Monday, Novem

Re: [openstack-dev] [Zaqar] OpenStack Tokyo Summit Summary

for reference, Julien is currently signed up for that task[1]. if this is a high priority requirement, we might want to see if another resource can pick it up, we can help out to explain how it should all be done :) cheers, [1] https://etherpad.openstack.org/p/mitaka-telemetry-todos On 07/11/

Re: [openstack-dev] [oslo] Graduate apiclient library

On 11/10/2015 06:45 AM, Victor Stinner wrote: Hi, Le 10/11/2015 07:29, Kekane, Abhishek a écrit : We have done extensive analysis to figure out the differences of usages of different oslo-incubator/openstack/common/apiclient modules used in the respective Openstack python client libraries and

Re: [openstack-dev] Learning to Debug the Gate

Took about 35 mins or so :) -- Dims On Tue, Nov 10, 2015 at 10:45 AM, Matt Riedemann wrote: > > > On 11/9/2015 3:54 PM, Anita Kuno wrote: >> >> On 11/05/2015 07:45 PM, Anita Kuno wrote: >>> >>> On 11/03/2015 05:30 PM, Anita Kuno wrote: On 11/02/2015 12:39 PM, Anita Kuno wrote: > >>

Re: [openstack-dev] [heat][keystone] How to handle request for global admin in policy.json?

On 11/10/2015 05:08 AM, Henry Nash wrote: Steve, Currently, your best option is to use something similar to the policy.v3cloudsample.json, where you basically “bless” a project (or domain) as being the “cloud admin project/domain”. Having a role on that gives you super-powers. The only trou

Re: [openstack-dev] [TripleO] Proposing Ian Wienand as core reviewer on diskimage-builder

On Tue, Nov 03, 2015 at 03:25:27PM +, Gregory Haynes wrote: > Hello everyone, > > I would like to propose adding Ian Wienand as a core reviewer on the > diskimage-builder project. Ian has been making a significant number of > contributions for some time to the project, and has been a great hel

  1   2   3   >