[openstack-dev] Switch 'all?' openstack bots to errbot plugins?

Hi folks, I was thinking it might be useful to see what other folks think about switching (or migrating all the current bots we have in openstack) to be based on errbot plugins. Errbot @ http://errbot.io/en/latest/ takes a slightly different approach to bots and treats each bot 'feature' as

[openstack-dev] What's Up, Doc? 29 July

Hi everyone, A fairly quiet week this week, as I've been gradually working my way through old bugs. We're now only ten weeks out from release, so I've also been trying to tidy up some loose ends around the Contributor Guide. We have a couple of specs out for review right now, so if you're

Re: [openstack-dev] [nova] Next steps for proxy API deprecation

> -Original Message- > From: Matthew Treinish [mailto:mtrein...@kortar.org] > Sent: 27 July 2016 02:36 > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [nova] Next steps for proxy API deprecation > >

Re: [openstack-dev] [nova] [placement] *future* topics in resource providers/placement api

Hi Chris, Thanks for the update, it's very clear about what we are going to achieve in Newton release. 2016-07-29 0:09 GMT+08:00 Sylvain Bauza : > > So we had a discussion in Hillsboro about that with no consensus yet, if > you remember. > I heard different opinions on how

Re: [openstack-dev] [Congress] Congress horizon plugin - congressclient/congress API auth issue - help

I've never worked on the authentication details, so this may be off track, but that error message indicates the failure is happening inside Congress's oslo_policy. Error message shows up here as a Python exception class. https://github.com/openstack/congress/blob/master/congress/exception.py#L135

Re: [openstack-dev] [Magnum] Microversioning implementation

Hongbin & team Please forget Semantic Versioning API, that should not be done in short term especially API WG had defined lots of Microversion API docs, sorry to make confusions. Of cause that Microversion API is important to OpenStack, and it has documented well in API WG [1]. For Magnum, I

Re: [openstack-dev] [ironic] [nova] [neutron] get_all_bw_counters in the Ironic virt driver

On 07/28/2016 05:40 PM, Brad Morgan wrote: > I'd like to solicit some advice about potentially implementing > get_all_bw_counters() in the Ironic virt driver. > > https://github.com/openstack/nova/blob/master/nova/virt/driver.py#L438 > Example Implementation: >

[openstack-dev] [ironic] [nova] get_all_bw_counters in the Ironic virt driver

I'd like to solicit some advice about potentially implementing get_all_bw_counters() in the Ironic virt driver. https://github.com/openstack/nova/blob/master/nova/virt/driver.py#L438 Example Implementation: https://github.com/openstack/nova/blob/master/nova/virt/xenapi/driver.py#L320 I'm

Re: [openstack-dev] [neutron][api] Passing random filters on neutron API calls

Yeah, I think preventing them from making it to the plugin as much as possible makes sense. We just can't reject the actual API call because it has extra query params. On Thu, Jul 28, 2016 at 12:06 PM, Brandon Logan wrote: > On Thu, 2016-07-28 at 19:24 +0200, Ihar

Re: [openstack-dev] [watcher] Mascot final choice

+2 to Jellyfish! > On Jul 28, 2016, at 4:08 PM, Antoine Cabot wrote: > > Hi Watcher team, > > Last week during the mid-cycle, we came up with a list of possible mascots > for Watcher. The only one which is in conflict with other projects is the > bee. > So we have

[openstack-dev] [gnocchi] typical length of timeseries data

hi folks, this is probably something to discuss on ops list as well eventually but what do you think about shrinking the max size of timeseries chunks from 14400 to something smaller? i'm curious to understand what the length of the typical timeseries is. my main reason for bringing this up is

Re: [openstack-dev] [nova] os-virtual-interfaces isn't deprecated in 2.36

On 7/28/2016 3:55 PM, Matt Riedemann wrote: For os-attach-interfaces, we need that to attach/detach interfaces to a server, so those actions don't go away with 2.36. We can also list and show interfaces (ports) which is a proxy to neutron, but in this case it seems a tad bit necessary, else to

Re: [openstack-dev] [nova] os-virtual-interfaces isn't deprecated in 2.36

On 7/28/2016 3:55 PM, Matt Riedemann wrote: So I think we're OK with os-attach-interfaces (even though it does some proxying right now), but I'm thinking we should be deprecating os-virtual-interfaces. Or if we don't deprecate os-virtual-interfaces, we should implement it for neutron too

[openstack-dev] [watcher] Mascot final choice

Hi Watcher team, Last week during the mid-cycle, we came up with a list of possible mascots for Watcher. The only one which is in conflict with other projects is the bee. So we have this final list : 1. Jellyfish 2. Eagle 3. Hammerhead shark I'm going to confirm jellyfish as the Watcher mascot

[openstack-dev] [nova] os-virtual-interfaces isn't deprecated in 2.36

I'm not sure if we thought about this before, but the os-virtual-interfaces API isn't deprecated with the 2.36 microversion: https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/virtual_interfaces.py Neither is os-attach-interfaces:

Re: [openstack-dev] [Congress] Congress horizon plugin - congressclient/congress API auth issue - help

I've gotten a little farther, which leads me to my next question - does the API support v3 token auth? or am I making mistakes in my manual testing? using the CLI on local devstack 1) did not modify openrc 2) source openrc 3) openstack token issue 4) openstack congress datasource list

Re: [openstack-dev] [Neutron] SFC stable/mitaka version

Hi Assaf, Yes, that makes sense. Thanks, Cathy -Original Message- From: Assaf Muller [mailto:as...@redhat.com] Sent: Thursday, July 28, 2016 1:06 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] SFC stable/mitaka version On

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Thanks Doug. I didn't pick up on your choice of Zane's point #1. If that is how the rest of the TC feels about it, that wfm. I will be submitting a resolution with your wording so clarity is reached and not lost in a mailing list thread in the future when this issue occurs again. Regards

Re: [openstack-dev] [nova][nova-docker] nova-scheduler filters configuration

When ı add the filter about nova-scheduler, the error occur, like the filters has no header, but ı don’t understand which means?? anyone help me ? > On Jul 28, 2016, at 3:14 PM, Yasemin DEMİRAL (BİLGEM BTE) > wrote: > > Should I configure nova.conf file for

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Excerpts from Steven Dake (stdake)'s message of 2016-07-28 19:40:29 +: > > On 7/28/16, 12:30 PM, "Davanum Srinivas" wrote: > > >Steven, > > > >Please see response from Doug: > >http://markmail.org/message/yp7fpojnzufb5jki > > Dims, > > Are you implying Doug's position

[openstack-dev] [nova] Reminder: mox conversion and py3 support changes freeze after today

At the end of today we'll be frozen on mox conversion and python 3 support. These are the outstanding python 3 changes for nova: https://review.openstack.org/#/q/topic:bp/nova-python3-newton+status:open And for mox conversion:

Re: [openstack-dev] [Neutron] SFC stable/mitaka version

On Thu, Jul 28, 2016 at 3:02 PM, Cathy Zhang wrote: > Hi Ihar and all, > > Yes, we have been preparing for such a release. We will do one more round of > testing to make sure everything works fine, and then I will submit the > release request. > There is a new patch on

[openstack-dev] [octavia]redirection and barbican config

Hi, I have a couple on questions on octavia. Please answer or redirect me to relevant documentation: - Assume listener is listening on 443 and client hits the vip on port 80, the connection will be refused. Is it possible to configure http to https direction? - For the barbican config, the only

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Steve, This thread has degenerated. So my request is to use Doug's post as status quo. If there's disagreement then file for a resolution that suits them -- Dims On Thu, Jul 28, 2016 at 3:40 PM, Steven Dake (stdake) wrote: > > > On 7/28/16, 12:30 PM, "Davanum Srinivas"

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

If it ever becomes necessary for us to pass a resolution to deal with every disagreement, we might as well all go herd goats. This is a very straightforward situation, which has been blown out of all reasonable proportion through well-intentioned but misplaced concerns. Please, everyone, let's

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On 7/28/16, 12:30 PM, "Davanum Srinivas" wrote: >Steven, > >Please see response from Doug: >http://markmail.org/message/yp7fpojnzufb5jki Dims, Are you implying Doug's position represents that of the TC? I have read Doug's position, and it completely ignores Zane's

[openstack-dev] [new][openstack] osc-lib 0.4.1 release (newton)

We are joyful to announce the release of: osc-lib 0.4.1: OpenStackClient Library This release is part of the newton release series. With source available at: https://git.openstack.org/cgit/openstack/osc-lib With package available at: https://pypi.python.org/pypi/osc-lib Please

[openstack-dev] [new][keystone] keystoneauth1 2.10.0 release (newton)

We are satisfied to announce the release of: keystoneauth1 2.10.0: Authentication Library for OpenStack Identity This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/keystoneauth With package available at:

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Steven, Please see response from Doug: http://markmail.org/message/yp7fpojnzufb5jki If anyone disagrees with that position, please file a resolution. Let's stop this thread now please. Thanks, Dims On Thu, Jul 28, 2016 at 3:26 PM, Steven Dake (stdake) wrote: > Dims, > > I

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Dims, I personally think its the responsibility of the TC to resolve this problem via a resolution. That’s why we elected you folks :) Regards -steve On 7/28/16, 11:09 AM, "Davanum Srinivas" wrote: >Zane, Steve, > >I'd say go for it! Can you please write up a proposal for

[openstack-dev] [new][keystone] keystonemiddleware 4.7.0 release (newton)

We are excited to announce the release of: keystonemiddleware 4.7.0: Middleware for OpenStack Identity This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/keystonemiddleware With package available at:

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Excerpts from Zane Bitter's message of 2016-07-28 14:38:12 -0400: > On 28/07/16 14:20, Jay Pipes wrote: > > How would guidance from the TC about what it means for a repo to be > > "part of the OpenStack tent" add clarity for repos that are not trying > > to be part of the OpenStack tent? > > If

Re: [openstack-dev] [nova] [placement] *future* topics in resource providers/placement api

On Jul 28, 2016, at 1:19 PM, Chris Dent wrote: >> How about we do a query in two steps: >> >> 1) take a list of compute nodes (== resource providers) and apply all >> the filters which *can not* (or *are not* at some point) be >> implemented in placement-api >> >> 2)

[openstack-dev] [charms] 16.07 OpenStack charm release

Hi All We are pleased to announce the 16.07 release of the OpenStack charms. Highlights include: * Nova compute apparmor support (Preview) * openstack-dashboard + Keystone v3 API support * SR-IOV (Preview) * External Network Update * DNS HA (Preview) * Enhancements to Ceph charms * New Charm:

Re: [openstack-dev] [Magnum] Microversioning implementation

OK. My replies are inline. > -Original Message- > From: Grant, Jaycen V [mailto:jaycen.v.gr...@intel.com] > Sent: July-28-16 2:31 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Magnum] Microversioning implementation > > I was

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On 28/07/16 14:38, Davanum Srinivas wrote: Zane, I don't understand why you're directing this reply to me. I *just* made clear that I don't have any interest one way or the other. There's a Spec, Spec was discussed in Weekly Meeting. There's traffic on the ML. I personally was helpful to

Re: [openstack-dev] [neutron][api] Passing random filters on neutron API calls

On Thu, 2016-07-28 at 19:24 +0200, Ihar Hrachyshka wrote: > Kevin Benton wrote: > > > Too late. That's a backwards incompatible change that can mess with > > clients putting on cache busting nonce tokens and who knows what else. > > Ideally, API layer would at least avoid

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On Thu, Jul 28, 2016 at 02:29:18PM -0400, Zane Bitter wrote: > On 28/07/16 12:54, Jay Pipes wrote: > >The TC has given guidance on this already: > > > >http://governance.openstack.org/resolutions/20160119-stackforge-retirement.html > > > > > >"In order to simplify software development lifecycle

Re: [openstack-dev] [Neutron] SFC stable/mitaka version

Hi Ihar and all, Yes, we have been preparing for such a release. We will do one more round of testing to make sure everything works fine, and then I will submit the release request. There is a new patch on "stadium: adopt openstack/releases in subproject release process" which is not Merged

Re: [openstack-dev] [glance][nova] Globally disabling hw_qemu_guest_agent support

Looking at the number of options for image properties, it would seem that a blacklist would be in order. I would be in favour for ‘standard’ images which support fsfreeze to support guest agent and that some of the NUMA properties not be available for end user images, but still for system ones.

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On 07/28/2016 07:21 PM, Doug Hellmann wrote: > [...] > I think it is a reasonable expectation that teams would want to add > their new repositories to the governance list to have the rights > that go along with that, but I'm not aware of any requirement that > they do so. Reviewing that change

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Hello, So as some of you might know, I write from a peculiar position. I'm both Kolla core and Intel. I don't like to see where this thread is going to. We are all one community, we are all OpenStack after all. I think what's hurting us here is this sense of competition. I would like to share my

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Zane, There's a Spec, Spec was discussed in Weekly Meeting. There's traffic on the ML. I personally was helpful to some extent with the beginnning of kolla-kubernetes. So i don't think it's a lack of communication that's to blame. Also if you see the repos, there's not much there... In effect

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On 28/07/16 14:20, Jay Pipes wrote: How would guidance from the TC about what it means for a repo to be "part of the OpenStack tent" add clarity for repos that are not trying to be part of the OpenStack tent? If it were clear what it means for a repo to be "part of the OpenStack tent" then it

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On Thu, Jul 28, 2016 at 2:20 PM, Jay Pipes wrote: > How would guidance from the TC about what it means for a repo to be "part > of the OpenStack tent" add clarity for repos that are not trying to be part > of the OpenStack tent? > > Just curious here... Related, ​Flavio

Re: [openstack-dev] FPGA as a dynamic nested resources

On 07/20/2016 05:07 AM, Daniel P. Berrange wrote: For FPGA, I'd like to see an initial proposal that assumed the FPGA is pre-programmed & pre-divided into a fixed number of slots and simply deal with this. For the record, this is precisely what is described in the first version of the

Re: [openstack-dev] [Magnum] Microversioning implementation

I was completely unaware of any discussion of Semantic Versioning. That was brought up by Eli Qiao in the code review, so he might be the one to point us in the right direction for that. Jaycen -Original Message- From: Hongbin Lu [mailto:hongbin...@huawei.com] Sent: Thursday, July

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On 28/07/16 12:54, Jay Pipes wrote: The TC has given guidance on this already: http://governance.openstack.org/resolutions/20160119-stackforge-retirement.html "In order to simplify software development lifecycle transitions of Unofficial and Official OpenStack projects, all projects developed

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

How would guidance from the TC about what it means for a repo to be "part of the OpenStack tent" add clarity for repos that are not trying to be part of the OpenStack tent? Just curious here... -jay On 07/28/2016 02:01 PM, Steven Dake (stdake) wrote: Jay, I'll be frank. I have been

[openstack-dev] [nova] [placement] *future* topics in resource providers/placement api

Note: I've changed the subject to make it clear that this thread is about topics related to resource providers and the placement API that are not relevant to newton. Ideas that we need to be chewing on but not things that need to solved now. On Thu, 28 Jul 2016, Roman Podoliaka wrote: I'd

Re: [openstack-dev] [nova] [placement] unresolved topics in resource providers/placement api

On 07/28/2016 02:10 PM, Chris Dent wrote: On Thu, 28 Jul 2016, Jay Pipes wrote: * There was some discussion of adding a configuration setting (e.g. 'placement_connection') that if not None (the default) would be used as the connection for the placement database. If None, the API database

Re: [openstack-dev] [Openstack] Listing of volume fails while using openstack client

On Jul 28, 2016, at 4:57 PM, varun bhatnagar wrote: > are you asking me to set the value of max_connections to 5000 in mysql conf? THere was no suggestion. I just told you that I had a similar/same problem as you and how I solved it. -- God gave man both a penis and a brain, but unfortunately

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Zane, Steve, I'd say go for it! Can you please write up a proposal for the TC to consider? (https://review.openstack.org/#/q/project:openstack/governance) Thanks, -- Dims On Thu, Jul 28, 2016 at 2:01 PM, Steven Dake (stdake) wrote: > Jay, > > I'll be frank. I have been

Re: [openstack-dev] [nova] [placement] unresolved topics in resource providers/placement api

On Thu, 28 Jul 2016, Jay Pipes wrote: * There was some discussion of adding a configuration setting (e.g. 'placement_connection') that if not None (the default) would be used as the connection for the placement database. If None, the API database would be used. I can't recall if we said

Re: [openstack-dev] [neutron][db][models]

Manjeet, Tony has some issues moving model classes to other location. Given that some class models are used by other neutron services, Ihar suggest to use debtcollector to make this transition smoothly. Can we include that solution as part of this movement? Thanks Victor Morales On

Re: [openstack-dev] [Magnum] Microversioning implementation

Added this to the agenda of next team meeting [1]. I would like to ask clarification for " the community are discussing to using Semantic Versioning(X.Y.Z) instead of microversion X.Y ". Could anyone provide more information about that? Best regards, Hongbin > -Original Message- >

Re: [openstack-dev] FPGA as a dynamic nested resources

> On Jul 28, 2016, at 7:57 AM, Jay Pipes wrote: > > On 07/19/2016 06:51 PM, Ed Leafe wrote: >> On Jul 19, 2016, at 2:58 PM, Chris Friesen >> wrote: Why would a VM program the slot? Wouldn’t it usually be at the host level? >>> >>> Are

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Jay, I'll be frank. I have been receiving numerous complaints which mirror Zane's full second understanding of what it means to be an OpenStack big tent project. These are not just Kolla developers. These are people from all over the community. They want something done about it. I agree with

Re: [openstack-dev] [puppet] Propose Sofer Athlan-Guyot (chem) part of Puppet OpenStack core

big +1 from me, thanks for work Sofer! 2016-07-28 19:42 GMT+03:00 Rich Megginson : > +1 - good guy > > > On 07/28/2016 09:58 AM, Ivan Berezovskiy wrote: > > +1, good job! > > 2016-07-28 18:50 GMT+03:00 Matt Fischer : > >> +1 from me! >> >> On Jul 28,

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On 7/28/2016 11:29 AM, Clint Byrum wrote: Excerpts from Fox, Kevin M's message of 2016-07-27 22:56:56 +: I think that would be true, if the container api was opinionated. for example, trying to map only a subset of the openstack config options to docker environment variables. This would

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

I don't see what is unclear about any of it. What exactly is it that you wish Mirantis to state? Zane says there needs to be some guidance from the TC "about what it means for a repo to be part of the OpenStack tent". But the fuel-ccp repos aren't listed in the governance repo, for reasons

Re: [openstack-dev] [neutron][api] Passing random filters on neutron API calls

Kevin Benton wrote: Too late. That's a backwards incompatible change that can mess with clients putting on cache busting nonce tokens and who knows what else. Ideally, API layer would at least avoid passing those unknown filters into plugins; same for plugins returning

Re: [openstack-dev] {neutron][db][models]

Ihar Hrachyshka wrote: > Manjeet S wrote: > >> Hello Team, >> >> I have a question regarding centralizing all db models in neutron. As >> you all know Oslo versioned object work is under progress and I also >> had a ticket opened for

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Excerpts from Zane Bitter's message of 2016-07-28 12:15:34 -0400: > On 28/07/16 08:48, Vladimir Kozhukalov wrote: > > Fuel-ccp repositories are public, everyone is welcome to participate. I > > don’t see where we violate “4 opens”. These repos are now experimental. > > At the moment the team is

Re: [openstack-dev] [ptl][requirements] nomination period started

On Thu, Jul 28, 2016 at 12:42:32PM -0400, Doug Hellmann wrote: > As part of our discussion, we realized that over time we'll be > automating more and more of the submissions to the requirements > repo so the core review team (and everyone else) will likely end > up submitting fewer manual

Re: [openstack-dev] [ptl][requirements] nomination period started

On Thu, Jul 28, 2016 at 12:21:26PM -0400, Anita Kuno wrote: > So Doug and I had a chat and we propose the following workflow for > deciding the requirements ptl: > 1) Nominations open, done: > http://lists.openstack.org/pipermail/openstack-dev/2016-July/100173.html > 2) Nominations close:

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Jay, That resolution doesn't clarify Zane's argument. Regards, -steve On 7/28/16, 9:54 AM, "Jay Pipes" wrote: >The TC has given guidance on this already: > >http://governance.openstack.org/resolutions/20160119-stackforge-retirement >.html > >"In order to simplify software

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

The TC has given guidance on this already: http://governance.openstack.org/resolutions/20160119-stackforge-retirement.html "In order to simplify software development lifecycle transitions of Unofficial and Official OpenStack projects, all projects developed within the OpenStack project

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

+1 From: Steven Dake (stdake) [std...@cisco.com] Sent: Thursday, July 28, 2016 9:33 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s)

Re: [openstack-dev] [ptl][requirements] nomination period started

Excerpts from Anita Kuno's message of 2016-07-28 12:21:26 -0400: > On 07/27/2016 06:06 PM, Jeremy Stanley wrote: > > On 2016-07-27 17:56:39 -0400 (-0400), Doug Hellmann wrote: > > [...] > >> However, we may have some folks on the core team who have not > >> contributed a patch, since it is far

Re: [openstack-dev] [puppet] Propose Sofer Athlan-Guyot (chem) part of Puppet OpenStack core

+1 - good guy On 07/28/2016 09:58 AM, Ivan Berezovskiy wrote: +1, good job! 2016-07-28 18:50 GMT+03:00 Matt Fischer >: +1 from me! On Jul 28, 2016 9:20 AM, "Emilien Macchi" >

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Doug, Zane's analysis is correct. I agree with Zane's assessment that TC clarification can solve this situation. Regards -steve On 7/28/16, 9:15 AM, "Zane Bitter" wrote: >On 28/07/16 08:48, Vladimir Kozhukalov wrote: >> Fuel-ccp repositories are public, everyone is

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Excerpts from Fox, Kevin M's message of 2016-07-27 22:56:56 +: > I think that would be true, if the container api was opinionated. for > example, trying to map only a subset of the openstack config options to > docker environment variables. This would make the containers specific to what >

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Sorry for the double post, but the part about people wasting their time reads far more inflammatory than I really intended. I merely mean community effort is a strong theme. On 7/28/2016 11:20 AM, Mark Casey wrote: +1 to one more pass at using the same images. Doing so will become

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

+1 to one more pass at using the same images. Doing so will become practically impossible in a matter of weeks or months, and in the long term the additional shared human resources outweigh the interpersonal complexities (and for any who don't think so - maybe you're wasting your time here?).

Re: [openstack-dev] [ptl][requirements] nomination period started

On 07/27/2016 06:06 PM, Jeremy Stanley wrote: > On 2016-07-27 17:56:39 -0400 (-0400), Doug Hellmann wrote: > [...] >> However, we may have some folks on the core team who have not >> contributed a patch, since it is far more common to do reviews than >> to submit changes there (more and more of

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On 28/07/16 08:48, Vladimir Kozhukalov wrote: Fuel-ccp repositories are public, everyone is welcome to participate. I don’t see where we violate “4 opens”. These repos are now experimental. At the moment the team is working on building CI pipeline and developing functional tests that are to be

Re: [openstack-dev] [nova] [placement] unresolved topics in resource providers/placement api

Le 28/07/2016 15:57, Chris Dent a écrit : I've been reviewing my notes from the mid-cycle and discussions leading up to it and realized I have a few unresolved or open topics that I hope discussion here can help resolve: # fairly straightforward things * At what stage in the game (of the

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Thanks for the clarity Doug. Regards -steve On 7/28/16, 8:37 AM, "Doug Hellmann" wrote: >Excerpts from Flavio Percoco's message of 2016-07-28 16:43:35 +0200: >> On 28/07/16 04:45 +, Steven Dake (stdake) wrote: >> > >> > >> >On 7/27/16, 2:12 PM, "Jay Pipes"

Re: [openstack-dev] [puppet] Propose Sofer Athlan-Guyot (chem) part of Puppet OpenStack core

+1, good job! 2016-07-28 18:50 GMT+03:00 Matt Fischer : > +1 from me! > > On Jul 28, 2016 9:20 AM, "Emilien Macchi" wrote: > >> You might not know who Sofer is but he's actually "chem" on IRC. >> He's the guy who will find the root cause of insane bugs,

Re: [openstack-dev] [Openstack] Listing of volume fails while using openstack client

Hi, Thanks for the answer. Just to be clear are you asking me to set the value of max_connections to 5000 in mysql conf? If yes then for me it is set to 8192 alreadyor have I misunderstood your suggestion? BR, Varun On Thu, Jul 28, 2016 at 5:35 PM, Turbo Fredriksson

Re: [openstack-dev] [nova] [placement] unresolved topics in resource providers/placement api

> No. POST /allocations/{consumer_uuid} is the thing that the resource > tracker calls for the claim on the compute node. > > The POST /allocations is something we've been throwing around ideas on > for an eventual call that the placement engine would expose for "claims > in the scheduler".

Re: [openstack-dev] [nova] [placement] unresolved topics in resource providers/placement api

On Jul 28, 2016, at 9:47 AM, Roman Podoliaka wrote: > How about we do a query in two steps: > > 1) take a list of compute nodes (== resource providers) and apply all > the filters which *can not* (or *are not* at some point) be > implemented in placement-api > > 2)

Re: [openstack-dev] [puppet] Propose Sofer Athlan-Guyot (chem) part of Puppet OpenStack core

+1 from me! On Jul 28, 2016 9:20 AM, "Emilien Macchi" wrote: > You might not know who Sofer is but he's actually "chem" on IRC. > He's the guy who will find the root cause of insane bugs, in OpenStack > in general but also in Puppet OpenStack modules. > Sofer has been

Re: [openstack-dev] [nova] [placement] unresolved topics in resource providers/placement api

On 07/28/2016 11:19 AM, Dan Smith wrote: There was some discussion that conflicted with reality a bit and I think we need to resolve before too long, but shouldn't impact the newton-based changes: We bounced around two different HTTP resources for returning one or several resource providers in

Re: [openstack-dev] [tripleo] TripleO Deep Dive session - July 28th

I hope you liked the presentation, despite of my terrible french accent :-) The recording is now available on Youtube: https://www.youtube.com/watch?v=AZO_6UaLLaU The slides: https://docs.google.com/presentation/d/1c3dBboSc8pixAN2yYBnFfoDX8HDab7lxWDd_DMB7-Jc/ Please let me know if you want me

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Excerpts from Flavio Percoco's message of 2016-07-28 16:43:35 +0200: > On 28/07/16 04:45 +, Steven Dake (stdake) wrote: > > > > > >On 7/27/16, 2:12 PM, "Jay Pipes" wrote: > > > >>On 07/27/2016 04:42 PM, Ed Leafe wrote: > >>> On Jul 27, 2016, at 2:42 PM, Fox, Kevin M

Re: [openstack-dev] [Cinder] Pending removal of X-IO volume driver

Hi Sean, Thanks for the heads up. I have been busy on other projects and not been involved in maintaining the CI. I will look into it and get it back up and running. I will keep you posted on the progress. Thanks, Richard -Original Message- From: Sean McGinnis

Re: [openstack-dev] [Openstack] Listing of volume fails while using openstack client

On Jul 28, 2016, at 1:57 PM, varun bhatnagar wrote: > I am trying to list volumes using openstack client, the command works > sometimes but sometimes it fails: I get that when my MySQL server "max_connections" is reached. I've bumped it to 5000 to be absolutly sure! SET GLOBAL

Re: [openstack-dev] [puppet] Propose Sofer Athlan-Guyot (chem) part of Puppet OpenStack core

I'm not a core, but +1 to chem, awesome work! 2016-07-28 12:18 GMT-03:00 Alex Schultz : > +1 > > On Thu, Jul 28, 2016 at 9:16 AM, Emilien Macchi > wrote: > > You might not know who Sofer is but he's actually "chem" on IRC. > > He's the guy who will

[openstack-dev] [fuel] Meeting for today 7/28 is caneled

The meeting agenda is empty for this week's meeting is empty so I'm calling it on the meeting. https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda -- -- Andrew Woodward Mirantis Fuel Community Ambassador Ceph Community

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Hi folks, First of all, let me say that it’s a marketing announcement and as all of you know such announcements aren’t precise from a technical side. Personally I’ve seen this paper first time on TechCrunch. First of all, fuel-ccp-* are a set of OpenStack projects and everyone is welcome to

Re: [openstack-dev] [nova] [placement] unresolved topics in resource providers/placement api

>> There was some discussion that conflicted with reality a bit and I >> think we need to resolve before too long, but shouldn't impact the >> newton-based changes: >> >> We bounced around two different HTTP resources for returning one or >> several resource providers in response to a launch

[openstack-dev] [puppet] Propose Sofer Athlan-Guyot (chem) part of Puppet OpenStack core

You might not know who Sofer is but he's actually "chem" on IRC. He's the guy who will find the root cause of insane bugs, in OpenStack in general but also in Puppet OpenStack modules. Sofer has been working on Puppet OpenStack modules for a while now, and is already core in puppet-keystone. Many

Re: [openstack-dev] [puppet] Propose Sofer Athlan-Guyot (chem) part of Puppet OpenStack core

+1 On Thu, Jul 28, 2016 at 9:16 AM, Emilien Macchi wrote: > You might not know who Sofer is but he's actually "chem" on IRC. > He's the guy who will find the root cause of insane bugs, in OpenStack > in general but also in Puppet OpenStack modules. > Sofer has been working on

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On 28/07/16 13:56 +, Fox, Kevin M wrote: I really see 3 issues raised in the spec mentioned that have any disagreement as far as I can tell. 1. mirantis would like to see kolla-ansible split from the base kolla repo. This has a lot of support and is likely to come up for a final vote

Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

On 7/21/2016 5:38 AM, Znoinski, Waldemar wrote: Hi Nova cores et al, I would like to acquire voting (+/-1 Verified) permission for our Intel NFV CI. 1. It’s running since Q1’2015. 2. Wiki [1]. 3. It’s using openstack-infra/puppet-openstackci

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On Thu, Jul 28, 2016 at 10:52 AM, Flavio Percoco wrote: > On 28/07/16 15:48 +0300, Vladimir Kozhukalov wrote: > >> 1. Alter the mission statement of fuel to match the reality being >>> >> >> published by the press and Mirantis's executive team >>> >> >> 2. Include these

Re: [openstack-dev] {neutron][db][models]

Ihar Hrachyshka wrote: > Manjeet S wrote: > >> Hello Team, >> >> I have a question regarding centralizing all db models in neutron. As you >> all know >> Oslo versioned object work is under progress and I also had a ticket >> opened for

Re: [openstack-dev] FPGA as a dynamic nested resources

On 07/19/2016 06:51 PM, Ed Leafe wrote: On Jul 19, 2016, at 2:58 PM, Chris Friesen wrote: Why would a VM program the slot? Wouldn’t it usually be at the host level? Are there no cases where a VM might want to download a proprietary program into an FPGA? That

  1   2   >