[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

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] 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

[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

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

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

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"

[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] [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

[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] [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

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] [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

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

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] [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] [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] [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][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 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] [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] [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] [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] [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

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] [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

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

<    1   2