Re: [openstack-dev] [all] the trouble with names

On 02/05/2016 04:36 PM, Chris Dent wrote: On Fri, 5 Feb 2016, Sean Dague wrote: I'd ask for folks to try to stay on the original question: What possible naming standards could we adopt, and what are the preferences. 1. service type as described in option 2 2. managed by the api-wg with

Re: [openstack-dev] [Neutron] Being more aggressive with our defaults

On 02/08/2016 09:47 AM, Sean M. Collins wrote: Hi, With the path_mtu issue - our default was to set path_mtu to zero, and do no calculation against the physical segment MTU and the overhead for the tunneling protocol that was selected for a tenant network. Which means the network would break.

[openstack-dev] [Neutron] Being more aggressive with our defaults

Hi, With the path_mtu issue - our default was to set path_mtu to zero, and do no calculation against the physical segment MTU and the overhead for the tunneling protocol that was selected for a tenant network. Which means the network would break. I am working on patches to change our behavior to

Re: [openstack-dev] [Fuel] Task Based Deployment Is at Least Twice Faster

Hey Fuelers, When we are going to enable it? I think since HCF is passed for stable/8.0, it's time to enable task-based deployment for master branch. Opinion? - Igor On Wed, Feb 3, 2016 at 12:31 PM, Bogdan Dobrelya wrote: > On 02.02.2016 17:35, Alexey Shtokolov wrote:

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

On 06.02.2016 00:03, Salvatore Orlando wrote: > > > On 5 February 2016 at 17:58, Neil Jerram > wrote: > > On 05/02/16 16:31, Pavel Bondar wrote: > > On 05.02.2016 12:28, Salvatore Orlando wrote: > >> > >> > >> On

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On Mon, Feb 8, 2016 at 11:19 AM, Jay Pipes wrote: > On 02/08/2016 10:29 AM, Sean Dague wrote: > >> On 02/08/2016 10:07 AM, Thierry Carrez wrote: >> >>> Brian Curtin wrote: >>> On Sun, Feb 7, 2016 at 3:07 PM, Jay Pipes wrote: > I would love

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On 02/07/2016 09:07 PM, Jay Pipes wrote: Hello all, tl;dr = I have long thought that the OpenStack Summits have become too commercial and provide little value to the software engineers contributing to OpenStack. I propose the following: 1) Separate the design summits from the conferences

Re: [openstack-dev] [Fuel] Task Based Deployment Is at Least Twice Faster

+1. Regards, Bulat Gaifullin Mirantis Inc. > On 08 Feb 2016, at 19:05, Igor Kalnitsky wrote: > > Hey Fuelers, > > When we are going to enable it? I think since HCF is passed for > stable/8.0, it's time to enable task-based deployment for master > branch. > >

Re: [openstack-dev] [nova][bugs] nova-bugs-team IRC meeting

John Garbutt wrote on 01/22/2016 11:55:52 AM: > From: John Garbutt > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 01/22/2016 11:57 AM > Subject: Re: [openstack-dev] [nova][bugs]

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

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

[openstack-dev] [Kuryr] IRC Meeting tomorrow (2/8) - 0300 UTC

Hello All, We will have an IRC meeting tomorrow (Tuesday, 2/8) at 0300 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meeting s/Kuryr You can view last meeting action items and logs

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On Mon, 2016-02-08 at 09:43 -0500, Jay Pipes wrote: > On 02/08/2016 09:03 AM, Fausto Marzi wrote: > > The OpenStack Summit is a great thing as it is now. It creates big > > momentum, it's a strong motivator for the engineers (as enjoy our > > time > > there) > > I disagree with you on this. The

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

Salvatore Orlando wrote: > Agreed. Operators love to automate things, but they generally don't like > when components automatically do things they maybe do not expect to do (I > don't think we should assume all operators fully read release notes). So > the manual step is preferable, and not that

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On 02/08/2016 11:11 AM, Fausto Marzi wrote: > On Mon, Feb 8, 2016 at 11:19 AM, Jay Pipes wrote: > >> On 02/08/2016 10:29 AM, Sean Dague wrote: >> >>> On 02/08/2016 10:07 AM, Thierry Carrez wrote: >>> Brian Curtin wrote: > On Sun, Feb 7, 2016 at 3:07 PM, Jay

Re: [openstack-dev] [Neutron] Being more aggressive with our defaults

I'm generally sympathetic to what you're saying, and I agree that we need to do something about disabled-by-default features, at the very least on the testing front. Comments in-line. On Mon, Feb 8, 2016 at 4:47 PM, Sean M. Collins wrote: > Hi, > > With the path_mtu issue -

Re: [openstack-dev] [Fuel] Task Based Deployment Is at Least Twice Faster

+1 to enable it ASAP. It will also affect our deployment tests (~1 hour vs. ~2.5 hours). Vladimir Kozhukalov On Mon, Feb 8, 2016 at 7:35 PM, Bulat Gaifullin wrote: > +1. > > Regards, > Bulat Gaifullin > Mirantis Inc. > > > > > On 08 Feb 2016, at 19:05, Igor Kalnitsky

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On 02/08/2016 10:29 AM, Sean Dague wrote: On 02/08/2016 10:07 AM, Thierry Carrez wrote: Brian Curtin wrote: On Sun, Feb 7, 2016 at 3:07 PM, Jay Pipes wrote: I would love to see the OpenStack contributor community take back the design summit to its original format and

Re: [openstack-dev] [all] Proposal for having a service type registry and curated OpenStack REST API

On 02/08/2016 06:16 AM, Sean Dague wrote: On 02/07/2016 08:13 PM, Monty Taylor wrote: On 02/07/2016 07:30 AM, Jay Pipes wrote: On 02/04/2016 06:38 AM, Sean Dague wrote: What options do we have? 2) Have a registry of "common" names. Upside, we can safely use common names everywhere and not

Re: [openstack-dev] [grenade][keystone] Keystone multinode grenade

On Mon, Feb 8, 2016 at 5:20 AM, Grasza, Grzegorz wrote: > > > From: Sean Dague [mailto:s...@dague.net] > > > > On 02/05/2016 04:44 AM, Grasza, Grzegorz wrote: > > > > > >> From: Sean Dague [mailto:s...@dague.net] > > >> > > >> On 02/04/2016 10:25 AM, Grasza, Grzegorz

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On Feb 8, 2016, at 7:07 AM, Thierry Carrez wrote: > > Brian Curtin wrote: >>> On Sun, Feb 7, 2016 at 3:07 PM, Jay Pipes wrote: >>> I would love to see the OpenStack contributor community take back the design >>> summit to its original format and

[openstack-dev] [lbaas][octavia] Security/networking questions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey there, I've been doing some work to research how best to implement LBaaSv2 and Octavia within the OpenStack-Ansible project. During that research, I've come up with a few questions. 1) Is it possible for octavia to operate without providing

Re: [openstack-dev] [neutron] documenting configuration option segregation between services and agents

Kevin Benton wrote: Propose it as a devref patch! +1. Has it happened already? On Wed, Jan 27, 2016 at 12:30 PM, Dustin Lundquist wrote: We should expand services_and_agents devref to describe how and why configuration options should be

Re: [openstack-dev] [Fuel] Nominate Fedor Zhadaev for the fuel-menu-core team

+1 On Mon, Feb 8, 2016 at 11:54 AM, Igor Kalnitsky wrote: > Hey Fuelers, > > I'd like to nominate Fedor Zhadaev for the fuel-menu-core team. > Fedor's doing good review with detailed feedback [1], and has > contributes over 20 patches during Mitaka release cycle [2].

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

Darragh - thanks for sharing your thoughts. We look forward to working with you! On 1 February 2016 at 14:20, Bailey, Darragh wrote: > > My initial thoughts are that the first 2 places to focus for alignment > (assuming people agree with the idea of life cycle phases) would be:

Re: [openstack-dev] [openstack-ansible][security] Security hardening is now integrated!

On 27 January 2016 at 13:29, Major Hayden wrote: > > After four months and 80+ gerrit reviews, the security hardening > configurations provided by the openstack-ansible-security role are now > integrated with OpenStack-Ansible! The Jenkins gate jobs for > OpenStack-Ansible are

Re: [openstack-dev] [openstack-ansible][security] Should the playbook stop on certain tasks?

On 13 January 2016 at 15:10, Major Hayden wrote: > > For example, the STIG requires[1] that all system accounts other than root > are locked. This could be dangerous on a running production system as > Ubuntu has non-root accounts that are not locked. At the moment, the >

Re: [openstack-dev] [all] Getting error after doing unstack.sh onstable/liberty

Umar Yousaf wrote on 02/08/2016 03:04:31 AM: > From: Umar Yousaf > To: openstack-dev@lists.openstack.org > Date: 02/08/2016 03:05 AM > Subject: [openstack-dev] [all] Getting error after doing unstack.sh on > stable/liberty > > I just did unstack.sh

Re: [openstack-dev] [Ironic] A strange transition in Ironic FSM

Hi all, Looking at the state machine spec , this might be a leftover from the older state machine. When the node is in deleting state, we only clean up the kernel/ramdisk and clear DHCP

Re: [openstack-dev] [Fuel] Nominate Fedor Zhadaev for the fuel-menu-core team

+1 On Mon, Feb 8, 2016 at 12:54 PM, Igor Kalnitsky wrote: > Hey Fuelers, > > I'd like to nominate Fedor Zhadaev for the fuel-menu-core team. > Fedor's doing good review with detailed feedback [1], and has > contributes over 20 patches during Mitaka release cycle [2]. >

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

Daniel P. Berrange wrote: [...] I really agree with everything you say, except for the bit about the community doing organization - I think its fine to let function event staff continue with the burden of planning, as long as their goals are directed by the community needs. Exactly. I might

Re: [openstack-dev] [all] Proposal for having a service type registry and curated OpenStack REST API

On 02/07/2016 08:30 AM, Jay Pipes wrote: > On 02/04/2016 06:38 AM, Sean Dague wrote: >> What options do we have? > >> 2) Have a registry of "common" names. >> >> Upside, we can safely use common names everywhere and not fear collision >> down the road. >> >> Downside, yet another contention

Re: [openstack-dev] [Fuel] Nominate Fedor Zhadaev for the fuel-menu-core team

+1 Regards, Bulat Gaifullin Mirantis Inc. > On 08 Feb 2016, at 12:57, Evgeniy L wrote: > > +1 > > On Mon, Feb 8, 2016 at 12:54 PM, Igor Kalnitsky > wrote: > Hey Fuelers, > > I'd like to nominate Fedor Zhadaev

Re: [openstack-dev] RFC 2616 was *so* 2010

Hi, > -Original Message- > From: Clay Gerrard [mailto:clay.gerr...@gmail.com] > Sent: 2016 február 5, péntek 21:21 > To: OpenStack Development Mailing List d...@lists.openstack.org> > Subject: [openstack-dev] RFC 2616 was *so* 2010 > > ... really more like 1999, but when OpenStack

Re: [openstack-dev] Announcing a simple new tool: git-restack

I've got some git aliases that handle this, so I did a quick review to see what might be useful additions to the tool. * Looks like passing of the branch should change the branch used for a .gitreview file to parse o This looks to be unnecessary with newer git-review anyway, but

[openstack-dev] [Fuel] Nominate Fedor Zhadaev for the fuel-menu-core team

Hey Fuelers, I'd like to nominate Fedor Zhadaev for the fuel-menu-core team. Fedor's doing good review with detailed feedback [1], and has contributes over 20 patches during Mitaka release cycle [2]. Fuel Cores, please reply back with +1/-1. - igor [1]

Re: [openstack-dev] [heat][nova][neutron] Using specific endpoints

Not sure about the heatclient, but if you use the keystone session you should be able to provide endpoint_override kwarg to any instantiation of a client that takes the session in. At least I think thats the case. Thanks, Brandon On Sat, 2016-02-06 at 22:51 +0530, pn kk wrote: > Can bypass_url

Re: [openstack-dev] Use of restricted and multiverse in the gate

On 7 February 2016 at 14:11, Monty Taylor wrote: > We're working on getting per-region APT mirrors stood up for the nodepool > nodes to use in the gate. As part of working on this, it struck me that we > currently have restricted and multiverse enabled in our sources.list

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

On Fri, Feb 05 2016, Jay Pipes wrote: > However, even though it's not the Poppy team's fault, I think the fact that > the > Poppy project user's only choice when using Poppy is to use a non-free backend > disqualifies Poppy from being an OpenStack project. The fact that the Poppy > team follows

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On Sun, Feb 07, 2016 at 03:07:20PM -0500, Jay Pipes wrote: > I would love to see the OpenStack contributor community take back the design > summit to its original format and purpose and decouple it from the OpenStack > Summit's conference portion. > > I believe the design summits should be

Re: [openstack-dev] [all] Proposal for having a service type registry and curated OpenStack REST API

On 02/07/2016 08:13 PM, Monty Taylor wrote: > On 02/07/2016 07:30 AM, Jay Pipes wrote: >> On 02/04/2016 06:38 AM, Sean Dague wrote: >>> What options do we have? >> >>> 2) Have a registry of "common" names. >>> >>> Upside, we can safely use common names everywhere and not fear collision >>> down

[openstack-dev] [Openstack-dev] Glance

Hi, I have been trying to execute a command in Glance but I am not able to execute the command. Could somebody please help me with it? Below given are the details of what I am looking for. 1. location-add --url [--metadata ] Here for url what should I pass to success to add the location.

Re: [openstack-dev] [neutron][neutron-*] Notice! pylint breakage

Gareth wrote: Thanks for all! However I'm developing on stable/liberty and it failed with running "tox -e pep8" because of this issue. And I found it is pylint==1.4.5 on master branch. Could we cherry-pick this test-requirements update back to stable/liberty? Try

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

Jay Pipes wrote: tl;dr = I have long thought that the OpenStack Summits have become too commercial and provide little value to the software engineers contributing to OpenStack. I propose the following: 1) Separate the design summits from the conferences 2) Hold only a single OpenStack

Re: [openstack-dev] [nova] Migration progress

Hi, In case of live-migration reporting I'd rather go with real-time stats, queried from compute, instead of reporting this data to db first. While amount of of rpc requests/db updates is relatively small, total number of such requests depends on amount of active migrations. While realtime data

Re: [openstack-dev] [Fuel] Nominate Fedor Zhadaev for the fuel-menu-core team

+1 Aleksey Kasatkin On Mon, Feb 8, 2016 at 12:04 PM, Tatyana Leontovich < tleontov...@mirantis.com> wrote: > +1 > > > > On Mon, Feb 8, 2016 at 11:54 AM, Igor Kalnitsky > wrote: > >> Hey Fuelers, >> >> I'd like to nominate Fedor Zhadaev for the fuel-menu-core team. >>

Re: [openstack-dev] [openstack-ansible][security] Improving SSL/TLS in OpenStack-Ansible

On 15 January 2016 at 14:18, Major Hayden wrote: > > > I've attended some of the OpenStack Security Mid-Cycle meeting this week > and Robert Clark was kind enough to give me a deep dive on the Anchor > project[1]. We had a good discussion around my original email thread[2] on >

[openstack-dev] [vitrage] Next vitrage meeting

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

Re: [openstack-dev] Dynamically adding Extra Specs

Dhvanan Shah wrote: Hey Jay! I was looking at implementing a few scheduling algorithms of my own natively into OpenStack, and for that I went through the nova-scheduler. After going through the scheduler, I felt that it was not very easy to implement or extend and add new scheduling algorithms

Re: [openstack-dev] [neutron] documenting configuration option segregation between services and agents

On 2016/02/08 18:17, Ihar Hrachyshka wrote: Kevin Benton wrote: Propose it as a devref patch! +1. Has it happened already? Here https://review.openstack.org/#/c/275381/ On Wed, Jan 27, 2016 at 12:30 PM, Dustin Lundquist wrote: We should

Re: [openstack-dev] [kolla] pid=host

Michal, You listed steps to reproduce but it wasn't clear if docker 1.10 kills vms or keeps them alive from your description. From our discussion today, it sounded as if docker 1.10, docker 1.9, and docker 1.8.2 have different behaviors on this front. Could you expand? Dan had required to keep

[openstack-dev] Proposed Agenda for Kolla Midcycle

Hey folks, The agenda generation happened approximately a month ago over a 3 week period, and then was voted on. I left the actual creation of the agenda until today in case any last minute pressing issues came in. I took some suggestions from the copious notes in the Etherpad regarding pair

Re: [openstack-dev] Announcing a simple new tool: git-restack

On 02/03/2016 01:53 AM, James E. Blair wrote: > Hi, > > I'm pleased to announce a new and very simple tool to help with managing > large patch series with our Gerrit workflow. > > In our workflow we often find it necessary to create a series of > dependent changes in order to make a larger

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On Sun, Feb 7, 2016 at 3:07 PM, Jay Pipes wrote: > I would love to see the OpenStack contributor community take back the design > summit to its original format and purpose and decouple it from the OpenStack > Summit's conference portion. > > I believe the design summits should

Re: [openstack-dev] [cinder] v2 image upload from url

Hi Kevin, I am executing command from glance and referring this command. glance --os-image-api-version 2 location-add --url [--metadata ] and glance --os-image-api-version 2 md-resource-type-associate Thanks for supporting us. Thanks & Regards, Pankaj On Mon, Feb 8, 2016 at 6:34 PM,

[openstack-dev] [kolla] pid=host

Hey folks, I know we have been through some changes with how pid=host works. I'd like to get to the bottom of this, so we can either add the features we need to docker, or say "all is good". Here is the last quote from this bugzilla where Red Hat in general is interested in the same behavior

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

On 06/02/16 12:12 +0800, Thomas Goirand wrote: On 02/05/2016 06:57 PM, Thierry Carrez wrote: Hi everyone, Even before OpenStack had a name, our "Four Opens" principles were created to define how we would operate as a community. The first open, "Open Source", added the following precision: "We

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On 02/07/2016 10:42 PM, Michael Still wrote: > On Mon, Feb 8, 2016 at 1:51 AM, Monty Taylor wrote: > > [snip] > > >> Fifth - if we do this, the real need for the mid-cycles we currently have >> probably goes away since the summit week can be a legit wall-to-wall work >>

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On 02/08/2016 04:09 AM, Thierry Carrez wrote: > Jay Pipes wrote: >> tl;dr >> = >> >> I have long thought that the OpenStack Summits have become too >> commercial and provide little value to the software engineers >> contributing to OpenStack. >> >> I propose the following: >> >> 1) Separate

Re: [openstack-dev] [cinder] v2 image upload from url

Sorry, Looping to Kevin Thanks, Pankaj On Mon, Feb 8, 2016 at 6:54 PM, Pankaj Mishra wrote: > Hi Kevin, > > I am executing command from glance and referring this command. > > glance --os-image-api-version 2 location-add --url [--metadata > ] > > > and > > glance

Re: [openstack-dev] [openstack-ansible][security] Should the playbook stop on certain tasks?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02/08/2016 06:40 AM, Jesse Pretorius wrote: > Darren's reply is interesting and perhaps worth consideration. As far as I > recall the security role adopted the STIG primarily because it was the only > openly available set of standards that

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

On 02/08/2016 08:54 AM, Flavio Percoco wrote: > Would our votes change if Poppy had support for OpenCDN (imagine it's being > maintained) even if that solution is terrible? > > I guess my question is: When do we start considering a project to be > safe from > an open source perspective? Because,

Re: [openstack-dev] [all] Proposal for having a service type registry and curated OpenStack REST API

On 08/02/2016 7:13 AM, Sean Dague wrote: > On 02/07/2016 08:30 AM, Jay Pipes wrote: >> On 02/04/2016 06:38 AM, Sean Dague wrote: >>> What options do we have? >> >>> 2) Have a registry of "common" names. >>> >>> Upside, we can safely use common names everywhere and not fear collision >>> down

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

Brian Curtin wrote: On Sun, Feb 7, 2016 at 3:07 PM, Jay Pipes wrote: I would love to see the OpenStack contributor community take back the design summit to its original format and purpose and decouple it from the OpenStack Summit's conference portion. I believe the design

Re: [openstack-dev] [cinder] v2 image upload from url

Sorry, can you give an example of the exact command you are using, please? On 5 Feb 2016 22:45, "Fox, Kevin M" wrote: We've been using the upload image from http url for a long time and when we upgraded to liberty we noticed it broke because the client's defaulting to v2

Re: [openstack-dev] [all] Proposal for having a service type registry and curated OpenStack REST API

On 02/08/2016 07:13 AM, Sean Dague wrote: On 02/07/2016 08:30 AM, Jay Pipes wrote: On 02/04/2016 06:38 AM, Sean Dague wrote: What options do we have? 2) Have a registry of "common" names. Upside, we can safely use common names everywhere and not fear collision down the road. Downside, yet

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

This thread is going many directions all at once, so I'll somewhat rudely top-reply and call out specific points rather than extend each sub-thread. Thierry, I suspect your strawman will address all of these points and more. Decoupling: I'm very much in favor. For a long time, devs at summits

Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka

On 2016-02-07 03:19:45 + (+), Wang, Shane wrote: > You are over worried about the new contributors. We are going to > limit the number of attendees, and from my experience and > knowledge, most of developers who join bug smash are old and > experienced OpenStack developers, and they

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On Mon, Feb 8, 2016 at 6:26 AM, Thierry Carrez wrote: > Daniel P. Berrange wrote: > >> [...] >> I really agree with everything you say, except for the bit about the >> community doing organization - I think its fine to let function event >> staff continue with the burden

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

Excerpts from Brian Curtin's message of 2016-02-08 09:09:37 -0500: > On Sun, Feb 7, 2016 at 3:07 PM, Jay Pipes wrote: > > I would love to see the OpenStack contributor community take back the design > > summit to its original format and purpose and decouple it from the

[openstack-dev] [Bareon][Fuel] Best practises on syncing patches between repositories

Hi, Some time ago we started Bareon project [1], and now we have some fixes landed to fuel-agent only, the question is what are the best practises on keeping two repos in sync with possibility to resolve conflicts manually? Cherry-picking patches manually doesn't look like the most error prone

Re: [openstack-dev] [kolla] Location of Heka Lua plugins

From: Eric LEMOINE > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Monday, February 8, 2016 at 12:39 AM To: "OpenStack Development

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On 02/08/2016 09:03 AM, Fausto Marzi wrote: The OpenStack Summit is a great thing as it is now. It creates big momentum, it's a strong motivator for the engineers (as enjoy our time there) I disagree with you on this. The design summits are intended to be working events, not conference

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On 02/08/2016 09:42 AM, Anita Kuno wrote: > On 02/08/2016 04:09 AM, Thierry Carrez wrote: >> Jay Pipes wrote: >>> tl;dr >>> = >>> >>> I have long thought that the OpenStack Summits have become too >>> commercial and provide little value to the software engineers >>> contributing to OpenStack.

Re: [openstack-dev] [grenade][keystone] Keystone multinode grenade

> From: Sean Dague [mailto:s...@dague.net] > > On 02/05/2016 04:44 AM, Grasza, Grzegorz wrote: > > > >> From: Sean Dague [mailto:s...@dague.net] > >> > >> On 02/04/2016 10:25 AM, Grasza, Grzegorz wrote: > >>> > >>> Keystone is just one service, but we want to run a test, in which it > >>> is

Re: [openstack-dev] [swift] Plan to add Python 3 support to Swift

Hi, The Swift port was blocked during 6 months by a complex issue related to PyEClib. Good news: this issue was fixed 2 months ago. After the Liberty Summit, a plan was defined to port Swift to Python 3 (end of october), and I understood that the whole Swift team agreed on it. Some Python 3

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

On 05/02/16 21:41 -0500, Jay Pipes wrote: On 02/05/2016 02:16 PM, Sean Dague wrote: On 02/05/2016 01:17 PM, Doug Hellmann wrote: So, is Poppy "open core"? Whether or not it is, I'm not sure how it is part of a Ubiquitous Open Source Cloud Platform. Because it only enables the use of

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On 02/08/2016 10:07 AM, Thierry Carrez wrote: > Brian Curtin wrote: >> On Sun, Feb 7, 2016 at 3:07 PM, Jay Pipes wrote: >>> I would love to see the OpenStack contributor community take back the >>> design >>> summit to its original format and purpose and decouple it from the

[openstack-dev] [tempest] BadAltAuth / Test Isolation same tenant

Hi there, I know that it's not the default configuration for openstack nor tempest but I need to make a script that test user isolation _inside_ the same tenant. Some of our users are in the same tenant but they must not interfere with each others. We have modified the nova policy rules

Re: [openstack-dev] [Magnum] gate issues

Hi Team, In order to resolve issue #3, it looks like we have to significantly reduce the memory consumption of the gate tests. Details can be found in this patch https://review.openstack.org/#/c/276958/ . For core team, a fast review and approval of that patch would be greatly appreciated,

Re: [openstack-dev] [kolla] pid=host

Hey, So quick steps to reproduce this: 0. install docker 1.10 1. Deploy kolla 2. Run VM 3. On compute host - ps aux | grep qemu, should show your vm process 4. docker rm -f nova_libvirt 5. ps aux | grep qemu should still show running vm 6. re-deploy nova_libvirt 7. docker exec -it nova_libvirt

[openstack-dev] [ironic] DHCP provider API change

Hi all, If you maintain an out-of-tree DHCP provider, this is a heads up on a breaking change that just landed. tl;dr: the update_dhcp_opts vifs parameter changed form, as seen here:

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

On 13:56 Feb 08, Flavio Percoco wrote: > On 08/02/16 09:24 -0500, Sean Dague wrote: > >On 02/08/2016 08:54 AM, Flavio Percoco wrote: > > > >>Would our votes change if Poppy had support for OpenCDN (imagine it's being > >>maintained) even if that solution is terrible? > >> > >>I guess my question

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On 02/08/2016 06:37 PM, Kevin L. Mitchell wrote: On Mon, 2016-02-08 at 10:49 -0500, Jay Pipes wrote: 5) Dealing with schwag, giveaways, parties, and other superfluous stuff As a confirmed introvert, I have to say that I rarely attend parties, for a variety of reasons. However, I don't think

Re: [openstack-dev] [Kuryr] IRC Meeting tomorrow (2/9) - 0300 UTC

As Mike spotted, the date for the meeting is February 9!! and not the 8th in the original email Thanks for the correction! On Mon, Feb 8, 2016 at 5:44 PM, Gal Sagie wrote: > Hello All, > > We will have an IRC meeting tomorrow (Tuesday, 2/8) at 0300 UTC > in

Re: [openstack-dev] Use of restricted and multiverse in the gate

On 02/07/2016 10:11 PM, Monty Taylor wrote: > Hey all, > > We're working on getting per-region APT mirrors stood up for the > nodepool nodes to use in the gate. As part of working on this, it struck > me that we currently have restricted and multiverse enabled in our > sources.list file. > > I

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On Mon, 2016-02-08 at 10:49 -0500, Jay Pipes wrote: > 5) Dealing with schwag, giveaways, parties, and other superfluous > stuff As a confirmed introvert, I have to say that I rarely attend parties, for a variety of reasons. However, I don't think our hypothetical design-only meeting should

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

On 08/02/16 09:24 -0500, Sean Dague wrote: On 02/08/2016 08:54 AM, Flavio Percoco wrote: Would our votes change if Poppy had support for OpenCDN (imagine it's being maintained) even if that solution is terrible? I guess my question is: When do we start considering a project to be safe from an

Re: [openstack-dev] [tempest] BadAltAuth / Test Isolation same tenant

On Mon, Feb 08, 2016 at 06:04:15PM +0100, Vincent Gatignol wrote: > Hi there, > > I know that it's not the default configuration for openstack nor tempest but > I need to make a script that test user isolation _inside_ the same tenant. > > Some of our users are in the same tenant but they

[openstack-dev] [Infra] Meeting Tuesday February 9th at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday February 9th, 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

Re: [openstack-dev] [lbaas][octavia] Security/networking questions

1. Octavia can run under it's own account with the required roles added to that account. 2. Currently the process would be to update the amphora image in glance and trigger a failover of the amphora. 3. It is required. It is a private network between the Octavia controller and the amphora. We

Re: [openstack-dev] Dynamically adding Extra Specs

Dhvanan, I admittedly only just saw the subject and skimmed the thread (so might be missing something), but have you looked into taking advantage of scheduler hints from a custom filter from the API / CLI? As FYI, horizon has a patch up adding support for them [1]. [1]

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On 02/08/2016 11:56 AM, James Bottomley wrote: On Mon, 2016-02-08 at 09:43 -0500, Jay Pipes wrote: On 02/08/2016 09:03 AM, Fausto Marzi wrote: The OpenStack Summit is a great thing as it is now. It creates big momentum, it's a strong motivator for the engineers (as enjoy our time there) I

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On 10:49 Feb 08, Jay Pipes wrote: > On 02/08/2016 10:29 AM, Sean Dague wrote: > >The Foundation has done an amazing job of making everyone think this is > >easy (I know how much it is not). Without their efforts organizing these > >events, eliminating the distractions of wandering in a strange

[openstack-dev] [cross-project] Meeting, Tue February 9th, 21:00 UTC

Hi all, We will be having a meeting tomorrow February 9th at 21:00 UTC in the #openstack-meeting-cp channel. Tech spec liaisons, as the noted in my last week email[1], please be familiar with these specs that are up for discussion tomorrow in the agenda [2]: * Team announcements (horizontal,

[openstack-dev] [nova] ram size and huge page number for VM

Hello, I using the latest Liberty and I am trying to bring up a VM with some numa options configured using flavor. Specifically I need to give this VM 16GB of RAM and in addition it will need to use 12x1GB huge pages. What I found out, there is no way in a flavor to specify RAM size and

Re: [openstack-dev] [Bareon][Fuel] Best practises on syncing patches between repositories

I think a more robust solution would be to create a replica of the fuel-agent master branch in the bareon repo (that can be automatically synced with a fast-forward merge). This would allow you to push merge commits (that can include manual merge resolution) from fuel-agent/master into bareon

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On Sun, 2016-02-07 at 15:07 -0500, Jay Pipes wrote: > Hello all, > > tl;dr > = > > I have long thought that the OpenStack Summits have become too > commercial and provide little value to the software engineers > contributing to OpenStack. > > I propose the following: > > 1) Separate the

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

Simply replying to the last reply in the thread to add a thought: As someone who wants to be speaking more in presentations and be involved in 'User' or 'Operator' conversations, but also wants to participate in project-specific design sessions, I find that the context switches make it difficult

Re: [openstack-dev] [nova] ram size and huge page number for VM

On 02/08/2016 01:47 PM, Serguei Bezverkhi (sbezverk) wrote: Hello, I using the latest Liberty and I am trying to bring up a VM with some numa options configured using flavor. Specifically I need to give this VM 16GB of RAM and in addition it will need to use 12x1GB huge pages. What I found

Re: [openstack-dev] [openstack-announce] [release][stable][horizon] horizon release 8.0.1 (liberty)

> With package available at: > > https://pypi.python.org/pypi/horizon AFAICT non-client/non-oslo stable point releases are NOT uploaded to pypi, are they? e.g. last horizon on pypi is version 2012.2 Should we start uploading them to pypi or change the email template for services projects?

  1   2   >