Re: [openstack-dev] [tacker] Proposing Lin Cheng for tacker-horizon core team

I think we have enough votes to proceed... Lin, Welcome to Tacker Horizon core team! - Sridhar On Thu, May 26, 2016 at 9:13 PM, Janki Chhatbar wrote: > +1 > > Thanking you > Janki Chhatbar > OpenStack | SDN | Docker > simplyexplainedblog.wordpress.com > On May 26, 2016

Re: [openstack-dev] [neutron] work on Common Flow Classifier

Hi everyone, Thanks YAMAMOTO Takashi for reserving a new meeting channel "openstack-meeting", for the discussion. We will have biweekly-odd meetings on this channel at UTC 1700 on Tuesday. Due to this long weekend in US and some people taking extra days off, let's start the meeting on this new

[openstack-dev] [Infra] Meeting Tuesday May 31st at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday May 31st, 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 agenda

Re: [openstack-dev] [nova] [placement] aggregates associated with multiple resource providers

Hi, cdent: This problem arises because the RT(resource tracker) only knows to consume the DISK resource in its host, but it still doesn’t know exactly which resource provider to place the consumption. That is to say, the RT still needs to *find* the correct resource provider in the step 4. The

Re: [openstack-dev] [Neutron] support of NSH in networking-SFC

On 5/25/2016 13:24, Tim Rozet wrote: In my opinion, it is a better approach to break this down into plugin vs driver support. There should be no problem adding support into networking-sfc plugin for NSH today. The OVS driver however, depends on OVS as the dataplane - which I can see a solid

Re: [openstack-dev] [nova] API changes on limit / marker / sort in Newton

I think it is good to share codes and a single microversion can make life more easier during coding. Can we approve those specs first and then decide on the details in IRC and patch review? Because the non-priority spec deadline is so close. Thanks On Tue, May 31, 2016 at 1:09 AM, Ken'ichi

[openstack-dev] Call for Commiters & Contributors for daisycloud-core project

Hi All, I would like to introduce to you a new OpenStack installer project Daisy(project name: daisycloud-core). Daisy used to be a closed source project mainly developed by ZTE, but currently we make it a OpenStack related project(http://www.daisycloud.org,

Re: [openstack-dev] [Monasca] influxDB clustering and HA will be "commercial option".

On 30 May 2016 at 11:59, Jaesuk Ahn wrote: > Hi, Monasca developers and users, > > > https://influxdata.com/blog/update-on-influxdb-clustering-high-availability-and-monetization/ > "For our current and future customers, we’ll be offering clustering and > high availability

Re: [openstack-dev] [oslo] [keystone] rolling dogpile.core into dogpile.cache, removing namespace packaging (PLEASE REVIEW)

On 05/30/2016 06:17 PM, Mike Bayer wrote: > Hi all - > > Just a heads up what's happening for dogpile.cache, in version 0.6.0 we > are rolling the functionality of the dogpile.core package into > dogpile.cache itself, and retiring the use of namespace package naming > for dogpile.cache. > >

[openstack-dev] [oslo] [keystone] rolling dogpile.core into dogpile.cache, removing namespace packaging (PLEASE REVIEW)

Hi all - Just a heads up what's happening for dogpile.cache, in version 0.6.0 we are rolling the functionality of the dogpile.core package into dogpile.cache itself, and retiring the use of namespace package naming for dogpile.cache. Towards retiring the use of namespace packaging, the

Re: [openstack-dev] [tripleo][infra][deployment] Adding multinode CI jobs for TripleO in nodepool

On 28/05/16 06:03, James Slagle wrote: I've been working on various patches to TripleO to make it possible for the baremetal provisioning part of the workflow to be optional. In such a scenario, TripleO wouldn't use Nova or Ironic to boot any baremetal nodes. Instead it would rely on the nodes

Re: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

On 24 May 2016 at 18:05, Doug Hellmann wrote: > Excerpts from Markus Zoeller's message of 2016-05-24 11:00:35 +0200: > > On 24.05.2016 09:34, Duncan Thomas wrote: > > > Cinder bugs list was far more manageable once this had been done. > > > > > > It is worth sharing the

Re: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

I support Clint's comment, and as an example, only today I was able to search a bug and to see it was reported 2 years ago and wasn't solved since. I've commented on the bug saying it happened to me in an up-to-date nova. I'm talking about a bug which is on your list -

Re: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

(Top posting as a general reply to the thread) Bugs are precious data. As much as it feels like the bug list is full of cruft that won't ever get touched, one thing that we might be missing in doing this is that the user who encounters the bug and takes the time to actually find the bug tracker

[openstack-dev] [qa] [Tempest] Abondoned old code reviews

Hi, There are many patches which are not updated in Tempest review queue even if having gotten negative feedback from reviewers or jenkins. Nova team is abandoning such patches like [1]. I feel it would be nice to abandone such patches which are not updated since the end of 2015. Any thoughts?

Re: [openstack-dev] [nova] API changes on limit / marker / sort in Newton

2016-05-29 19:25 GMT-07:00 Alex Xu : > > > 2016-05-20 20:05 GMT+08:00 Sean Dague : >> >> There are a number of changes up for spec reviews that add parameters to >> LIST interfaces in Newton: >> >> * keypairs-pagination (MERGED) - >> >>

Re: [openstack-dev] [nova] [cinder] nova's broken py27/py33 and functional tests

On Mon, May 30, 2016 at 05:15:56PM +0200, Sylvain Bauza wrote: > (titling now accordingly) > > Le 30/05/2016 14:01, Sylvain Bauza a écrit : > >Hi, > > > >For the moment, we have a non-resolved critical bug hitting our > >UTs and functional tests : > >https://bugs.launchpad.net/nova/+bug/1586976 >

Re: [openstack-dev] [glance] Focus for week R-18 May 30-June 03

Hi all, Thanks for the feedback offline and indicating that I need to clear my intent on why this email was sent. This email was intended primarily to the Glance team to know more about what the release plans look like as not everyone is able to attend the meetings and it's near to impossible

Re: [openstack-dev] [glance] [stable] Proposal to add Ian Cordasco to glance-stable-maint

This has been done. Thanks! On 5/25/16 5:12 PM, Nikhil Komawar wrote: > Hi all, > > > I would like to propose adding Ian to glance-stable-maint team. The > interest is coming from him and I've already asked for feedback from the > current glance-stable-maint folks, which has been in Ian's

[openstack-dev] [Monasca] influxDB clustering and HA will be "commercial option".

Hi, Monasca developers and users, https://influxdata.com/blog/update-on-influxdb-clustering-high-availability-and-monetization/ "For our current and future customers, we’ll be offering clustering and high availability through Influx Cloud, our managed hosting offering, and Influx Enterprise, our

Re: [openstack-dev] [nova] [cinder] nova's broken py27/py33 and functional tests

Le 30/05/2016 17:33, Davanum Srinivas a écrit : Sylvain, I don't see any reverts proposed in requirements/ repo... yet https://review.openstack.org/#/c/322899/ is on its way. Folks, you can monitor this change, once it's merged, it should fix Nova jobs since we don't need to sync our local

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.05.31 17:00 UTC [1] on #openstack-meeting-4. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160531T17 __ OpenStack

Re: [openstack-dev] [nova] [cinder] nova's broken py27/py33 and functional tests

Sylvain, I don't see any reverts proposed in requirements/ repo... yet -- Dims On Mon, May 30, 2016 at 11:15 AM, Sylvain Bauza wrote: > (titling now accordingly) > > Le 30/05/2016 14:01, Sylvain Bauza a écrit : >> >> Hi, >> >> For the moment, we have a non-resolved critical

Re: [openstack-dev] [nova] [cinder] nova's broken py27/py33 and functional tests

(titling now accordingly) Le 30/05/2016 14:01, Sylvain Bauza a écrit : Hi, For the moment, we have a non-resolved critical bug hitting our UTs and functional tests : https://bugs.launchpad.net/nova/+bug/1586976 Markus Z. and I are currently investigating the root cause, but in the

Re: [openstack-dev] [tempest][qa][ironic][nova] When Nova should mark instance as successfully deleted?

Hi, >But the issue here is just capacity. Whether or not we keep an instance >in a deleting state, or when we release quota, doesn't change the >Tempest failures from what I can tell. The suggestions below address >that. > > >> >> > > > >> > > > I think we should go with #1, but instead of

[openstack-dev] [tripleo] weekly meeting

Hi! We'll have our weekly meeting tomorrow at 2pm UTC on #openstack-meeting-alt. Here's a first agenda: https://wiki.openstack.org/wiki/Meetings/TripleO#Agenda_for_next_meeting Feel free to add more topics, and any outstanding bug and patch. See you tomorrow! Thanks, -- Emilien Macchi

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

Hi Puppeteers! We'll have our weekly meeting tomorrow at 3pm UTC on #openstack-meeting-4. Here's a first agenda: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160531 Feel free to add more topics, and any outstanding bug and patch. See you tomorrow! Thanks, -- Emilien

[openstack-dev] [nova] Broken py27/py33 and functional tests

Hi, For the moment, we have a non-resolved critical bug hitting our UTs and functional tests : https://bugs.launchpad.net/nova/+bug/1586976 Markus Z. and I are currently investigating the root cause, but in the meantime, please refrain asking for rechecks unless you're sure why you're

[openstack-dev] [new][horizon] django_openstack_auth 2.3.0 release (newton)

We are jubilant to announce the release of: django_openstack_auth 2.3.0: Django authentication backend for use with OpenStack Identity This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/django_openstack_auth/ With package

[openstack-dev] How to list all the servers of a user across projects

Link: https://openstack.nimeyo.com/86042/?show=86042#q86042 From: imocha How to list all the servers owned by the user across projects. I tried to create token scoped to a project and able to list the servers on that project using the compute end point

Re: [openstack-dev] [gate] [nova] live migration, libvirt 1.3, and the gate

On Thu, May 26, 2016 at 10:55:47AM -0400, Sean Dague wrote: > On 05/26/2016 05:38 AM, Kashyap Chamarthy wrote: > > On Wed, May 25, 2016 at 05:42:04PM +0200, Kashyap Chamarthy wrote: > > > > [...] > > > >> So, in short, the central issue seems to be this: the custom 'gate64' > >> model is not

Re: [openstack-dev] [tripleo][manila] Moving forward with landing manila in tripleo

Hi Marios, I am ok with landing manila in tripleo with manila-data pending as you are suggesting. Manila-data can be added later, thus not blocking your current efforts. Regards, -- Rodrigo Barbieri Computer Scientist OpenStack Manila Contributor Federal University of São Carlos On 27/05/16

Re: [openstack-dev] [tripleo][manila] Moving forward with landing manila in tripleo

On 27/05/16 22:46, Rodrigo Barbieri wrote: > Hello Marios, > Hi Rodrigo, thanks very much for taking the time, indeed that clarifies quite a lot: > The Data Service is needed for Share Migration feature in manila since the > Mitaka release. > > There has not been any work done yet towards

Re: [openstack-dev] [congress] Spec for congress.conf

Hi Bryan, On 2016/05/28 2:52, Bryan Sullivan wrote: Masahito, Sorry, I'm not quite clear on the guidance. Sounds like you're saying all options will be defaulted by Oslo.config if not set in the congress.conf file. That's OK, if I understood. you're right. It's clear to me that some will

[openstack-dev] [mistral] Team meeting reminder - 05/30/2016

Hi, This is a reminder about the team meeting that we’ll have today at 16.00 UTC at #openstack-meeting. Agenda: Review action items Current status (progress, issues, roadblocks, further plans) Newton-2 scope Open discussion As usually, feel free to bring your own topics. Renat Akhmerov @Nokia

[openstack-dev] [vitrage] vitrage - how much links model in API is permanent?

Hi, While calling /v1/topology/ the response has links part, which is list of dicts. Each dict have the following properties : is_deleted : Boolean key : string relationship_type : string source : int target : int How much that structure is permanent ?

[openstack-dev] [neutron] [dns-name] Is there some use case which users manually set dns-name?

If there is no case ,It's better to deny PUT to dns-name. Detail info: https://bugs.launchpad.net/neutron/+bug/1583739 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: