[openstack-dev] [oslo][all] openstack context change for user_name and project_name

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi operators/devs, I have a patch [1] for oslo.context (the library that is used by most projects to create context objects to pass around) that introduces the following change for the context: user_identity is now constructed from user and project

[openstack-dev] Why do we drop branches? (WAS: Re: Targeting icehouse-eol?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/04/2015 04:15 PM, Alan Pevec wrote: The only open question I have is if we need to do an Icehouse point release prior to the tag and dropping the branch, but I don't think that's happened in the past with branch end of life

Re: [openstack-dev] [global-requirements][pbr] tarball and git requirements no longer supported in requirements.txt

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/03/2015 11:08 PM, Robert Collins wrote: > Hi, right now there is a little used (e.g. its not in any active > project these days) previous feature of pbr/global-requirements: > we supported things that setuptools does not: to whit, tarball and

Re: [openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

to suspend velocity of your project, and excessive ACL fences are one of those. > > Let's just automate this stuff. Like we have automated CI for > testing. > > Best regards, Boris Pavlovic > > On Wed, Jun 3, 2015 at 2:28 PM, Ihar Hrachyshka > mailto:ihrac...@redhat

Re: [openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/03/2015 08:29 AM, Boris Pavlovic wrote: > Guys, > > I will try to summarize all questions and reply on them: > > *- Why not splitting repo/plugins?* > > I don't want to make "architectural" decisions based on "social" or > "not enough good

Re: [openstack-dev] [keystone] [nova] [oslo] oslo.policy requests from the Nova team

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/02/2015 06:22 PM, Sean Dague wrote: > Nova has a very large API, and during the last release cycle a lot > of work was done to move all the API checking properly into policy, > and not do admin context checks at the database level. The result >

Re: [openstack-dev] [Neutron] Python 3 and hacking rules.

ll be added, so that > non python3-compliant code cannot be added. This might break code > in neutron-*aas and other projects that use the Neutron hacking > rules. Ihar Hrachyshkaand I decided to submit patches to fix > this: > > https://review.openstack.org/187353 >

Re: [openstack-dev] [Neutron] virtual machine can not get DHCP lease due packet has no checksum

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/02/2015 10:10 AM, Miguel Ángel Ajo wrote: > The backport seems reasonable IMO. > > Is this tested in a multihost environment?. > > I ask, because given the Ian explanation (which probably I got > wrong), the issue is in the NET->NIC->VM path

Re: [openstack-dev] [release][neutron] python-neutronclient 2.6.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I have a suggestion... Since it's not obvious now which stable branch a release corresponds to, can we add that info into release note email body somewhere for the sake of those who may closely track stable updates but not so much those in-developmen

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/29/2015 11:46 PM, Haïkel wrote: > A release version makes it easy to know what fixes are shipped in a > package. If you rebase on stable branches, then you can just put > the git sha1sum (though, it's not very friendly) in the version, > and le

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/29/2015 06:24 PM, Jeremy Stanley wrote: > On 2015-05-29 17:50:01 +0200 (+0200), Ihar Hrachyshka wrote: [...] >> if we attempt to fix a security issue that has a backwards >> incompatible fix, then we are forced in in

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/01/2015 02:20 AM, Steve Gordon wrote: > - Original Message - >> From: "Maish Saidel-Keesing" To: >> openstack-dev@lists.openstack.org >> >> On 05/29/15 18:25, Matthew Thode wrote: >>>

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/29/2015 05:26 PM, Thierry Carrez wrote: > Ihar Hrachyshka wrote: >> What about release notes? How can we now communicate some changes >> that require operator consideration or action? > > Arguably each and every "

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 What about release notes? How can we now communicate some changes that require operator consideration or action? Ihar On 05/29/2015 03:41 PM, Thierry Carrez wrote: > Hi everyone, > > TL;DR: - We propose to stop tagging coordinated point releases >

Re: [openstack-dev] [neutron] Proposing Assaf Muller for the Neutron Core Reviewer Team

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 +1 and more! On 05/28/2015 03:42 PM, Kyle Mestery wrote: > Folks, I'd like to propose Assaf Muller to be a member of the > Neutron core reviewer team. Assaf has been a long time contributor > in Neutron, and he's also recently become my testing Lieu

Re: [openstack-dev] [packaging] Adding packaging as an OpenStack project

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/28/2015 01:07 PM, Jaume Devesa wrote: > Hi Thomas, > > Delorean is a tool to build rpm packages from master branches > (maybe any branch?) of OpenStack projects. It's now also used for stable/kilo. I suspect all supported branches starting fr

Re: [openstack-dev] [neutron] Impressions from Vancouver Neutron Design Summits

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I've heard that other projects come up with actual action lists and work assignments. I've heard Nova, Ironic, Oslo do it, and I witnessed just that in those Oslo sessions I had a chance to visit. So Neutron can be special in this regard and may not

Re: [openstack-dev] [packaging] Adding packaging as an OpenStack project

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/27/2015 10:14 AM, Thomas Goirand wrote: > Hi all, > > tl;dr: - We'd like to push distribution packaging of OpenStack on > upstream gerrit with reviews. - The intention is to better share > the workload, and improve the overall QA for packaging

Re: [openstack-dev] [neutron] - dnsmasq 'dhcp-authoritative' option broke multiple DHCP servers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/26/2015 11:53 PM, Kevin Benton wrote: >> Actually, that approach was initially taken for bug 1345947, but > then the patch was abandoned to be replaced with a simpler - > --dhcp-authoritative approach that ended up with unexpected NAKs > for

Re: [openstack-dev] [neutron] - dnsmasq 'dhcp-authoritative' option broke multiple DHCP servers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/26/2015 04:35 AM, Kevin Benton wrote: > Hi, > > A recent change[1] to pass '--dhcp-authoritative' to dnsmasq has > caused DHCPNAK messages when multiple agents are scheduled to a > network [2]. > > This was back-ported to Icehouse and Juno so

Re: [openstack-dev] [Neutron] Stepping down from Neutron core team

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/21/2015 05:58 PM, Salvatore Orlando wrote: > After putting the whole OpenStack networking contributors > community through almost 8 cycles of pedant comments and annoying > "what if" questions, it is probably time for me to relieve neutron > co

Re: [openstack-dev] OpenStack 2015.1.0 for Debian Sid and Jessie

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Are there any attempts to avoid duplication of efforts? I would expect Ubuntu to reuse and extend what is in their upstream distro - Debian. Ihar On 05/15/2015 01:11 PM, David Medberry wrote: > and a quick checks shows that there are number of diff

Re: [openstack-dev] [Sahara][oslo]Error in Log.debug

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/05/2015 09:58 AM, Li, Chen wrote: > I find the reason. > > > > When devstack install sahara, “logging_context_format_string” would > be configured by default to: > > logging_context_format_string = %(asctime)s.%(msecs)03d > %(color)s%(leve

Re: [openstack-dev] [oslo] Deprecation path?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/24/2015 09:06 PM, Julien Danjou wrote: > Hi Oslo team! > > So what's your deprecation path? > > I sent a patch for oslo.utils¹ using debtcollector, our new fancy > deprecation tool, and I got a -2 stating that there's no way we > deprecate

Re: [openstack-dev] [neutron] Need guidance - functional tests and rootwrap

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/24/2015 04:02 PM, Ihar Hrachyshka wrote: > On 04/24/2015 03:48 PM, Paul Michali wrote: >> Hi, I'm floundering a bit, and could use some guidance on >> this... > >> For the neutron-vpnaas repo, I am trying to

Re: [openstack-dev] [neutron] Need guidance - functional tests and rootwrap

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/24/2015 03:48 PM, Paul Michali wrote: > Hi, I'm floundering a bit, and could use some guidance on this... > > For the neutron-vpnaas repo, I am trying to modify the functional > jobs (dsvm-functional and dsvm-functional-sswan) to act in a > si

Re: [openstack-dev] Please stop reviewing code while asking questions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/24/2015 10:14 AM, Julien Danjou wrote: > Hi there, > > This is now happening weekly to me now, probably because I write > too many patches touching almost all OpenStack projects once a > cycle, and I'm really tired of that behavior, so PLEASE:

Re: [openstack-dev] [packaging][neutron] --config-dir vs. --config-file

think we should also add a new config-directory that would be loaded by *all* services. I wonder what people think about its name. I think /etc/neutron/conf.d/common is a good fit. Comments? Ihar On 04/13/2015 05:25 PM, Ihar Hrachyshka wrote: > Hi, > > RDO/master (aka Delorean) moved n

Re: [openstack-dev] [oslo][policy][neutron] oslo.policy API is not powerful enough to switch Neutron to it

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I've sent a patch that makes And, Or, Not, and Rule checks public. As for RoleCheck, we don't need it anymore since we're going to kill the code that relied on it. The patch is: https://review.openstack.org/#/c/176683/ Note that we will need a new

Re: [openstack-dev] [oslo] eventlet 0.17.3 is now fully Python 3 compatible

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/22/2015 05:02 PM, INADA Naoki wrote: > > Hi, All, > > My 2c are: > > - yes, oslo.db supports python 3 (unittests passes, at least :) ) - > MySQL-python still default MySQL DB driver in OpenStack, but at > the moment the only DB driver for My

Re: [openstack-dev] [oslo][policy][neutron] oslo.policy API is not powerful enough to switch Neutron to it

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/22/2015 05:01 AM, Doug Hellmann wrote: > Excerpts from Ihar Hrachyshka's message of 2015-04-17 14:45:58 > +0200: >> Hi, >> >> tl;dr neutron has special semantics for policy targets that >> relies on private symbols from oslo.policy, and it's i

Re: [openstack-dev] [neutron] neutron DB upgrade

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/21/2015 02:25 PM, Guo, Ruijing wrote: > Somebody can help me to understand why neutron DB is needed upgrade > even in refresh installation unlike other components. > refresh installation == minor version upgrade for a stable release? No, it s

Re: [openstack-dev] [neutron][stable] Bug 1414218 is not fixed on in neutron stable/juno branch

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/17/2015 12:56 AM, Carl Baldwin wrote: > Stephen, > > On Thu, Apr 16, 2015 at 4:21 PM, Ma, Stephen B. > wrote: >> As it stands currently, neutron on the stable/juno branch behaves >> as if https://review.openstack.org/#/c/164329/ was never mer

Re: [openstack-dev] [keystone] keystoneclient stable/icehouse broken

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/20/2015 10:26 AM, Ihar Hrachyshka wrote: > On 04/20/2015 12:34 AM, Brant Knudson wrote: > > >> On Sun, Apr 19, 2015 at 3:07 PM, Brant Knudson > <mailto:b...@acm.org>> wrote: > > >> Ever since the

Re: [openstack-dev] [neutron] [QoS] weekly meeting - update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/20/2015 12:20 PM, Miguel Angel Ajo Pelayo wrote: > Thank you Irena, > > I believe this last minute change deserves an explanation, I asked > Irena to write to the list on my behalf (thank you!). > > I got a surgery to one of my kids schedule

Re: [openstack-dev] [oslo][pbr] getting 0.11 out the door. Maybe even 1.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/20/2015 02:22 PM, Victor Stinner wrote: >> I believe Redhat patch it out. I don't think they should need >> to, since we have explicit knobs for distros to use. > > pbr pulls pip which we don't want in RHEL. Example of patches in > RDO: > > h

Re: [openstack-dev] [neutron] Prefix delegation using dibbler client

ohn Davidge (jodavidg)" > wrote: > >> Hello all, >> >> We now have a work-in-progress patch up for review: >> >> https://review.openstack.org/#/c/158697/ >> >> >> Feedback on our approach is much appreciated. >> >> Many

Re: [openstack-dev] [keystone] keystoneclient stable/icehouse broken

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/20/2015 12:34 AM, Brant Knudson wrote: > > > On Sun, Apr 19, 2015 at 3:07 PM, Brant Knudson > wrote: > > > Ever since the stable/icehouse branch was created for > python-keystoneclient it's been broken. There are a coup

Re: [openstack-dev] [packaging][neutron] --config-dir vs. --config-file

Configuration is not something we should consider. On 04/17/2015 11:17 PM, Kevin Benton wrote: > Great! I was just worried that it was going to become one > --config-dir option that pointed to /etc/neutron or something. > > On Fri, Apr 17, 2015 at 7:13 AM, Ihar Hrachyshka > mailto:ihrac...@red

Re: [openstack-dev] [oslo][policy][neutron] oslo.policy API is not powerful enough to switch Neutron to it

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/17/2015 07:49 PM, Salvatore Orlando wrote: > == 2. filling in admin context with admin roles == > > Admin context object is filled with .roles attribute that is a list > of roles considered granting admin permissions [4]. The attribute > would t

Re: [openstack-dev] [Nova][Neutron] HELP -- Please review some Kilo bug fixes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/16/2015 09:54 AM, Bhandaru, Malini K wrote: > Hello Nova and Neutron developers! > > OpenStack China developers held a bug fest April 13-15. Worked on > 43 bugs and submitted patches for 29 of them. Etherpad with the bug > fix details (at the b

Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network to Neutron migration work]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/17/2015 06:23 PM, Fox, Kevin M wrote: > Really, what I expect to see long term in a healthy OpenStack > ecosystem is some global AppStore like functionality baked in to > horizon. A user goes to it, selects "my awesome scalable web > hosting syst

Re: [openstack-dev] [packaging][neutron] --config-dir vs. --config-file

s. But if you don't buy the new approach, you just don't have any files inside the directory to beat your conventional configuration. > > On Mon, Apr 13, 2015 at 8:25 AM, Ihar Hrachyshka > mailto:ihrac...@redhat.com>> wrote: > > Hi, > > RDO/master (ak

Re: [openstack-dev] [packaging][neutron] --config-dir vs. --config-file

tion, it's a bit different since you can define more strict rules from the start while you haven't set different expectations for your user base. > > Regards, > > Dimitri. > > ps sorry for loss of context, only recently subscribed, don't have > full access to th

Re: [openstack-dev] [packaging][neutron] --config-dir vs. --config-file

er loaded configs and then add >> some node-specific overrides to the ones loaded later. >> >> Will there still be the ability to do that with RDO? >> >> On Mon, Apr 13, 2015 at 8:25 AM, Ihar Hrachyshka >> mailto:ihrac...@redhat.com>> wrote: >> &g

[openstack-dev] [oslo][policy][neutron] oslo.policy API is not powerful enough to switch Neutron to it

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, tl;dr neutron has special semantics for policy targets that relies on private symbols from oslo.policy, and it's impossible to introduce this semantics into oslo.policy itself due to backwards compatibility concerns, meaning we need to expose some

Re: [openstack-dev] [oslo] Graduating oslo.reports: Request to review "clean copy"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2015 06:29 PM, Doug Hellmann wrote: > > > On Tue, Feb 24, 2015, at 08:15 PM, Solly Ross wrote: >> >>> Those scripts have mostly moved into oslotest, so they don't >>> need to be synced any more to be used. If you have all of your >>> code,

Re: [openstack-dev] [packaging][neutron] --config-dir vs. --config-file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/13/2015 05:42 PM, Matthew Thode wrote: > We already do this somewhat in gentoo (at least for some daemon > initialization stuff) in /etc/conf.d/$DAEMON_NAME.conf. Adding a > --config-dir option to that would be very simple. Gentoo at least >

Re: [openstack-dev] [packaging][neutron] --config-dir vs. --config-file

s, /Ihar On 03/13/2015 03:11 PM, Ihar Hrachyshka wrote: > Hi all, > > (I'm starting a new [packaging] tag in this mailing list to reach > out people who are packaging our software in distributions and > whatnot.) > > Neutron vendor split [1] introduced situations where the

Re: [openstack-dev] [neutron][lbaas][barbican] default certificate manager

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/10/2015 09:18 PM, Brandon Logan wrote: > Hi Ihar, I'm not against the lazy loading solution, just wondering > what the real issue is here. Is your problem with this that > python-barbicanclient needs to be in the requirements.txt? Or is > the p

[openstack-dev] [neutron][lbaas][barbican] default certificate manager

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi lbaas folks, I've realized recently that the default certificate manager for lbaas advanced service is now barbican based. Does it mean that to make default configuration working as is, users will need to deploy barbican service? If that's really t

Re: [openstack-dev] cinder[stable/juno] Fix the eqlx driver to retry on ssh timeout(Backport)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am fine with the change itself, but please split into proper pieces. Squashing patches is the last resort. On 04/06/2015 11:33 PM, rajini_...@dell.com wrote: > *Dell - Internal Use - Confidential * > > Hi > > Can we have a freeze exception on thi

Re: [openstack-dev] Fwd: [stable] Request stable freeze exception: 162112 and 162113 libvirt live migration progress & loop

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This one is very suspicious for a last minute merge. Also, no nova cores, neither nova-stable-maint cores commented on the backport. Without it, there is no way it will be merged at all. Please reach nova folks on the matter. On 04/06/2015 11:44 PM, D

Re: [openstack-dev] [stable] [nova] FFE for "libvirt: proper monitoring of live migration progress"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +344 new lines of code for an exception patch? No way. Let's take time to consider the patch outside the very next release. On 04/04/2015 01:31 AM, Billy Olsen wrote: > Hello, > > I would like to get a FFE for patch > https://review.openstack.org/#/

Re: [openstack-dev] [oslo] not running for PTL for liberty cycle

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/03/2015 02:50 PM, Doug Hellmann wrote: > Team, > > I have decided not to run for PTL for Oslo for the next cycle. > > Serving as PTL for the last three releases has been a rewarding > experience, and I think we’ve made some great strides togeth

Re: [openstack-dev] [Heat] [Ceilometer] [depfreeze] bug is unresolved due to requirements freeze

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/02/2015 01:58 PM, Eoghan Glynn wrote: > >> Pavlo Shchelokovskyy wrote: >>> unfortunately, in Heat we do not have yet integration tests for >>> all the Heat resources (creating them in real OpenStack), and >>> Ceilometer alarms are in those not c

Re: [openstack-dev] The Evolution of core developer to maintainer?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/01/2015 06:31 PM, Duncan Thomas wrote: > Right now there are some strong indications that there are areas we > are very weak at (nova network still being preferred to neutron I don't think it's correct. As per latest summit survey [1], nova-netw

Re: [openstack-dev] [all][oslo] oslo.log hacking rules

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/31/2015 09:19 PM, Ivan Kolodyazhny wrote: > Hi all, > > After moving to oslo.log and a lots of reviews to Cinder we merged > some parts for hacking checks to our code [1], [2]. Some of them > are also implemented in Nova [2], [3]. I didn't check

Re: [openstack-dev] [infra][horizon] Need help at debugging requirements issue

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/20/2015 09:01 AM, Matthias Runge wrote: > On 19/03/15 15:52, Ihar Hrachyshka wrote: > >>> [1] https://review.openstack.org/#/c/155353/ >> >> >> Hi, >> >> it all comes to the fact that DEVSTACK_G

Re: [openstack-dev] [infra][horizon] Need help at debugging requirements issue

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/19/2015 10:16 AM, Matthias Runge wrote: > Hello, > > I was trying to raise the cap for Django in[1]. It looks quite > simple, current requirements is Django>=1.4.2,<1.7 and I simply > removed the upper boundary: Django>=1.4.2 > > with the resul

Re: [openstack-dev] Deprecation warnings considered harmful?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/17/2015 05:22 PM, Ihar Hrachyshka wrote: > On 03/13/2015 04:36 PM, Doug Hellmann wrote: > > >> On Fri, Mar 13, 2015, at 07:25 AM, Ihar Hrachyshka wrote: On >> 03/13/2015 01:37 AM, Nikhil Manchanda wrote: >>>

Re: [openstack-dev] Deprecation warnings considered harmful?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/13/2015 04:36 PM, Doug Hellmann wrote: > > > On Fri, Mar 13, 2015, at 07:25 AM, Ihar Hrachyshka wrote: On > 03/13/2015 01:37 AM, Nikhil Manchanda wrote: >>>> Looking back at the meeting eavesdrop, the primary reasons &

Re: [openstack-dev] [all] Do we need release announcements for all the things?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/12/2015 09:22 PM, Clint Byrum wrote: > I spend a not-insignificant amount of time deciding which threads > to read and which to fully ignore each day, so extra threads mean > extra work, even with a streamlined workflow of > single-key-press-per-

[openstack-dev] [packaging][neutron] --config-dir vs. --config-file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, (I'm starting a new [packaging] tag in this mailing list to reach out people who are packaging our software in distributions and whatnot.) Neutron vendor split [1] introduced situations where the set of configuration files for L3/VPN agent is

Re: [openstack-dev] Deprecation warnings considered harmful?

; > > > On Thu, Mar 12, 2015 at 4:05 PM, Robert Collins > mailto:robe...@robertcollins.net>> > wrote: > > On 13 March 2015 at 09:43, Ihar Hrachyshka <mailto:ihrac...@redhat.com>> wrote: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >>

Re: [openstack-dev] [neutron] high dhcp lease times in neutron deployments considered harmful (or not???)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (Sorry for reviving an old thread.) On 01/28/2015 02:55 PM, Ihar Hrachyshka wrote: > On 01/28/2015 09:50 AM, Kevin Benton wrote: >> Hi, >> >> Approximately a year and a half ago, the default DHCP lease time >> in Neu

Re: [openstack-dev] Deprecation warnings considered harmful?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/12/2015 09:35 PM, Robert Collins wrote: > On 13 March 2015 at 08:09, Ihar Hrachyshka > wrote: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> >> On 03/12/2015 11:38 AM, Boris Bobrov wrote: >>> On Thurs

Re: [openstack-dev] Deprecation warnings considered harmful?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/12/2015 11:38 AM, Boris Bobrov wrote: > On Thursday 12 March 2015 12:59:10 Duncan Thomas wrote: >> So, assuming that all of the oslo depreciations aren't going to >> be fixed before release > > What makes you think that? > > In my opinion it's

Re: [openstack-dev] [stable] Icehouse 2014.1.4 freeze exceptions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2015 12:21 PM, Alan Pevec wrote: > Hi, > > next Icehouse stable point release 2014.1.4 has been slipping last > few weeks due to various gate issues, see "Recently closed" section > in https://etherpad.openstack.org/p/stable-tracker for detai

[openstack-dev] [neutron] upgrade scenario after advanced service split

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I was asked to point out to upstream community that the way we did advanced service split introduced some challenges on the packaging side. Specifically, to make upgrade scenario from Juno to Kilo smooth for RDO users, we need to introduce a

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2015 07:48 PM, Joe Gordon wrote: > Out of sync Quotas -- > > https://etherpad.openstack.org/p/PHL-ops-nova-feedback L63 > > The quotas code is quite racey (this is kind of a known if you look > at the bug tracker). It was act

Re: [openstack-dev] [Neutron] Issue when upgrading from Juno to Kilo due to agent report_state RPC namespace patch

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Should we target it for Kilo? It does not seem right to allow it slipping into the next release while we know there are operators relying on the feature. On 03/11/2015 08:42 PM, Assaf Muller wrote: > I've filed a bug here: > https://bugs.launchpad.ne

Re: [openstack-dev] [stable] Icehouse 2014.1.4 freeze exceptions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2015 12:21 PM, Alan Pevec wrote: > Hi, > > next Icehouse stable point release 2014.1.4 has been slipping last > few weeks due to various gate issues, see "Recently closed" section > in https://etherpad.openstack.org/p/stable-tracker for detai

Re: [openstack-dev] [neutron] Proposal to add Ihar Hrachyshka as a Neutron Core Reviewer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2015 06:54 PM, Kyle Mestery wrote: > On Wed, Mar 4, 2015 at 1:42 PM, Kyle Mestery <mailto:mest...@mestery.com>> wrote: > > I'd like to propose that we add Ihar Hrachyshka to the Neutron > core reviewer team. Ihar

Re: [openstack-dev] [api][neutron] Best API for generating subnets from pool

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I also agree wilcards do not look solid, and without clear use cases with reasonable demand from operators, it's better to avoid putting ourselves into position of supporting the feature for eternity. We had cases of immature API design rushed into th

Re: [openstack-dev] [Neutron][IPAM] Uniqueness of subnets within a tenant

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/10/2015 06:34 PM, Gabriel Bezerra wrote: > Em 10.03.2015 14:24, Carl Baldwin escreveu: >> Neutron currently does not enforce the uniqueness, or >> non-overlap, of subnet cidrs within the address scope for a >> single tenant. For example, if a te

Re: [openstack-dev] [stable] Freeze exception for "Correct initialization order for logging to use eventlet locks"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2015 12:51 PM, Boris Bobrov wrote: > Hello, > > I would like to get a freeze exception for patch "Correct > initialization order for logging to use eventlet locks", [0]. > > https://review.openstack.org/#/c/163387/ > > The bug fixed by the

Re: [openstack-dev] [stable] Icehouse 2014.1.4 freeze exceptions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2015 12:21 PM, Alan Pevec wrote: > Hi, > > next Icehouse stable point release 2014.1.4 has been slipping last > few weeks due to various gate issues, see "Recently closed" section > in https://etherpad.openstack.org/p/stable-tracker for detai

[openstack-dev] [neutron][third party] Major third party CI breakage expected for out-of-tree plugins

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, team is going to merge in a patch to migrate to oslo.log [1] in the very near future. This patch is expected to break all third party CI for all vendor libraries that were split from the main repo in Kilo and that rely on neutron.openstack.com

[openstack-dev] [neutron][third party] best packaging practices

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, RDO project started to look into packaging some of vendor libraries that were split from neutron tree during Kilo for Delorean, and found some issues with some of pypi packages that were released in public. We feel that communicating each ven

Re: [openstack-dev] [Glance] Core nominations.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/05/2015 11:35 AM, Mikhail Fedosin wrote: > Yes, it's absolutely right. For example, Nova and Neutron have > official rules for that: > https://wiki.openstack.org/wiki/Nova/CoreTeam where it says: "A > member of the team may be removed at any tim

Re: [openstack-dev] [Trove] request to backport the fix for bug 1333852 to juno

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Not being involved in trove, but some general comments on backports. On 03/04/2015 08:33 PM, Amrith Kumar wrote: > There has been a request to backport the fix for bug 1333852 > (https://bugs.launchpad.net/trove/+bug/1333852) which was fixed in > Kil

Re: [openstack-dev] Python 3 is dead, long live Python 3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2015 03:37 PM, Doug Hellmann wrote: > > > On Tue, Mar 3, 2015, at 07:56 AM, Ihar Hrachyshka wrote: On > 02/02/2015 05:15 PM, Jeremy Stanley wrote: >>>> After a long wait and much testing, we've merged a c

Re: [openstack-dev] [devstack]Specific Juno version

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2015 04:42 PM, Eduard Matei wrote: > Hi, > > Is there a way to specify the Juno version to be installed using > devstack. For now we can only specify stable/juno *git clone -b > stable/juno https://github.com/openstack-dev/devstack.git > /op

Re: [openstack-dev] Python 3 is dead, long live Python 3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/02/2015 05:15 PM, Jeremy Stanley wrote: > After a long wait and much testing, we've merged a change[1] which > moves the remainder of Python 3.3 based jobs to Python 3.4. This > is primarily in service of getting rid of the custom workers we >

Re: [openstack-dev] olso.db 1.5.0 release

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/02/2015 05:51 PM, Mike Bayer wrote: > > > Matt Riedemann wrote: > >> >> >> On 2/26/2015 3:22 AM, Victor Sergeyev wrote: >>> Hi folks! >>> >>> The Oslo team is pleased to announce the release of: oslo.db - >>> OpenStack common DB library >>

Re: [openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/26/2015 01:06 AM, Thomas Goirand wrote: > On 02/24/2015 12:27 PM, Daniel P. Berrange wrote: >> I'm actually trying to judge it from the POV of users, not just >> developers. I find it pretty untenable that in the fast moving >> world of cloud,

Re: [openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Daniel, thanks for a clear write-up of the matter and food for thought. I think the idea of having more smooth development mode that would not make people to wait for 6+ months to release a new feature is great. It's insane to expect that feature

Re: [openstack-dev] [neutron][oslo] plan till end-of-Kilo

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Some update on oslo/neutron patches in Kilo. On 01/20/2015 03:17 PM, Kyle Mestery wrote: > > > On Mon, Jan 19, 2015 at 10:54 AM, Ihar Hrachyshka > mailto:ihrac...@redhat.com>> wrote: > > Hi Kyle/all, > > (we were

Re: [openstack-dev] [nova] translations gone wild

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have some experience in i18n for other project (GNOME), so I have some answers to your questions. On 02/26/2015 02:18 PM, Sean Dague wrote: > This morning in the nova channel we were trying to get to the > bottom of the unit tests failing lxsi and g

Re: [openstack-dev] [neutron][cisco][apic] entry point for APIC agent

har, > > That was missed for the Juno release, I'll post a patch on master > and then backport it to stable/juno. > > Thanks for catching that, Ivar. > > On Fri Feb 20 2015 at 11:06:11 AM Ihar Hrachyshka > mailto:ihrac...@redhat.com>> wrote: > > Hi, &g

Re: [openstack-dev] [neutron] New version of python-neutronclient release: 2.3.11

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/20/2015 11:01 PM, Matt Riedemann wrote: > > > On 2/20/2015 6:23 AM, Alan Pevec wrote: https://review.openstack.org/#/c/157535/ >>> >>> Do you know where it ends ? We could set up Depends lines on >>> those requirements stable/* reviews an

[openstack-dev] [neutron][cisco][apic] entry point for APIC agent

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, does anyone know why we don't maintain an entry point for APIC agent in setup.cfg? The code in [1] looks like there is a main() function for the agent, but for some reason it's not exposed to any console_script during installation of neutron. Is

Re: [openstack-dev] [Neutron] per-agent/driver/plugin requirements

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/18/2015 08:45 PM, Armando M. wrote: > > > On 17 February 2015 at 22:00, YAMAMOTO Takashi > mailto:yamam...@valinux.co.jp>> wrote: > > hi, > > i want to add an extra requirement specific to OVS-agent. (namely, > I want to add ryu for ovs-ofctl

Re: [openstack-dev] [neutron] Prefix delegation using dibbler client

gt; first (dibbler, in this case), and then propose the changes into > Neutron to make use of those changes. I don't see how we can > proceed with this work until the issues around dibbler has been > resolved. > > > John Davidge OpenStack@Cisco > > > > >

[openstack-dev] [hacking] disable a check by default

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I would like to introduce a hacking check that would be disabled by default: https://review.openstack.org/157894 I see the following commit in flake8: https://gitlab.com/methane/flake8/commit/b301532636b60683b339a2d081728d22957a142f which sugg

Re: [openstack-dev] [Devstack] Devstack Install broken

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/20/2015 12:02 PM, Eduard Matei wrote: > > Hi, > > I'm trying to install devstack and it keeps failing with: > > 2015-02-20 07:26:12.693 | ++ is_fedora 2015-02-20 07:26:12.693 | ++ > [[ -z Ubuntu ]] 2015-02-20 07:26:12.693 | ++ '[' Ubuntu = Fed

Re: [openstack-dev] The root-cause for IRC private channels (was Re: [all][tc] Lets keep our community open, lets fight for it)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/18/2015 05:07 PM, Michael Krotscheck wrote: > You got my intention right: I wanted to understand better what > lead some people to create a private channel, what were their > needs. > > > I'm in a passworded channel, where the majority of membe

Re: [openstack-dev] [Neutron] per-agent/driver/plugin requirements

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/18/2015 08:14 AM, YAMAMOTO Takashi wrote: > hi, > >> On Wednesday, 18 de February de 2015 at 07:00, >> yamam...@valinux.co.jp wrote: >>> hi, >>> >>> i want to add an extra requirement specific to OVS-agent. >>> (namely, I want to add ryu for o

Re: [openstack-dev] [neutron] monkey patching strategy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/17/2015 04:19 PM, Salvatore Orlando wrote: > My opinions inline. > > On 17 February 2015 at 16:04, Ihar Hrachyshka <mailto:ihrac...@redhat.com>> wrote: > > Hi, > > response was huge so far :) so to add more tra

<    2   3   4   5   6   7   8   9   10   >