[openstack-dev] [keystone] Case for renewability of tokens, increasing expiration time

I was having an issue extending the expiration on unscoped and tenant/project scoped tokens retrieved with an existing token. I now realize this is a feature, not a bug, but I've got some points to argue that extending token expiration when getting a new token with an existing one (renewal), is wor

Re: [openstack-dev] [networking-ovs-dpdk]

Hi Sean, I realised on debugging ovs-dpdk-init script that the main issue is with the following command $ screen -dms ovs-vswitchd sudo sg $qemu_group -c "umask 002; ${OVS_INSTALL_DIR}/sbin/ovs-vswitchd --dpdk -vhost_sock_dir $OVS_DB_SOCKET_DIR -c $OVS_CORE_MASK -n $OVS_MEM_CHANNELS --proc-type

Re: [openstack-dev] [ironic] weekly subteam status report

Ruby, Thanks for taking care of our weekly status report. I'd like to just let you know that the iRMC part is somehow consolidated with old statuses which I reported two and three weeks ago. If this report were generated by a script, I thought it would be necessary to update. :-) Best regards, Na

Re: [openstack-dev] [Horizon] Handling of 202 response code

Thanks Matthias for educating me. As there is no universal solution to this issue, I will check if launch instance page strategy will work out for this case. Regards, Saravanan KR On 11/04/2015 03:47 PM, Matthias Runge wrote: On 04/11/15 09:25, Saravanan KR wrote: There may be multiple solu

[openstack-dev] [Infra] Meeting Tuesday November 17th at 19:00 UTC

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

Re: [openstack-dev] [oslo][testing-cabal] Help needed getting oslo.versionedobjects to install in tox venv

Just a quick note to say thank you to Robert, who helped me through my troubles on #openstack-dev. Robert, you rock. Thanks much! FWIW, the problem was indeed a bad version of virtualenv (the old Ubuntu one), and this is what I needed to do to resolve the issue: sudo apt-get remove -y python3

Re: [openstack-dev] [puppet] weekly meeting #59

The second one. Sorry for confusion, I sent it from my phone. See you tomorrow! --- Emilien Macchi On Nov 16, 2015 1:24 PM, "Iury Gregory" wrote: > Hi Emilien, the link for the agenda is > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-2015111 > or > https://etherpad.openstack

Re: [openstack-dev] [oslo][testing-cabal] Help needed getting oslo.versionedobjects to install in tox venv

On 17 November 2015 at 16:25, Jay Pipes wrote: > On 11/15/2015 08:10 PM, Robert Collins wrote: ... > > Thanks, Robert, but unfortunately that didn't work. I still get the same > problem: > > Downloading/unpacking .[fixtures] > Could not find any downloads that satisfy the requirement .[fixtures]

Re: [openstack-dev] [oslo][testing-cabal] Help needed getting oslo.versionedobjects to install in tox venv

On 11/15/2015 08:10 PM, Robert Collins wrote: On 16 November 2015 at 15:29, Jay Pipes wrote: Hi all, Really getting frustrated with a particular problem. I'm trying to build oslo.versionedobjects locally (this problem occurs on both my lappie and my desktop, running Ubuntu 15.04 and 15.10 resp

Re: [openstack-dev] [stable] Preparing 2014.2.4 (Juno) WAS Re: [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

On 11/16/2015 8:49 PM, Rochelle Grober wrote: I would like to make a plea that while Juno is locked down so as no changes can be made against it, the branch remains on the git.openstack.org site. Please? One area that could be better investigated with the branch in place is upgrade. Kilo

Re: [openstack-dev] [Barbican] Enabling GET of secrets to work irrespective of Tenant name in login

Hi Vijay-- The recommended way for supporting that use case is to use Barbican's ACLs. It allows user's from another project/tenant to access specific secrets If the "demo admin" owns a secret and wants to give read access to "admin admin", the "demo admin" should create a ACL for the se

Re: [openstack-dev] [stable] Preparing 2014.2.4 (Juno) WAS Re: [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

I would like to make a plea that while Juno is locked down so as no changes can be made against it, the branch remains on the git.openstack.org site. Please? One area that could be better investigated with the branch in place is upgrade. Kilo will continue to get patches, as will Liberty, so

[openstack-dev] [murano]How to use Murano to transmit files to Mistral and execute scripts on Mistral

Dear Murano developers and testers, I want to put some files that Mistral workflow needs into Murano package, and hope Murano can transmit them to Mistral before it calls Mistral workflow. The flow should be as following: 1. User uploads one Murano package which includes both M

[openstack-dev] [QA][Tempest] Deprecate or drop about Tempest CLI

Hi tempest CLI users and developers, Now, we are improving Tempest CLI as we discussed at the summit[1] and migrating legacy commands to tempest cli[2]. In this situation, my concern is 'CLI compatibility'. If we'll drop old CLIs support(like my patch), it might break existing workflows. So I t

Re: [openstack-dev] [Fuel] [Fuel UI] Support of separate provisioning is blocked by backend issues

Hey Julia, Thank you for feedback. I took a look over the bug and here's my thoughts: * [1] Looks like Invalid to me. I'm not sure, but it looks like you VMs just wrongly configures. It's a pretty common mistake for VBox scripts. Did you use them? * [2] Partially Invalid. I left my comments, so I

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting this week. The meeting is being held Tuesday UTC1200. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks Alex

Re: [openstack-dev] [Fuel] Deprecation of GRE network segmentation in Fuel 8.0

Hey Artem, > GRE network segmentation option has been deprecated for clusters > with Neutron since 7.0 release, both on UI and Library side What do you mean by "deprecated"? Was it removed? If so, why did we have a chance to create GRE if it wasn't supported? If so, we definitely have to forbid

Re: [openstack-dev] [Fuel][Infra] HA deployment tests on nodepool

Aleksandra Fedorova writes: > Hi, everyone, > > > > in Fuel project we run two HA deployment tests for every commit in > openstack/fuel-library repository. Currently these tests are run by > Fuel CI - the standalone Third-Party CI system, which can vote on > openstack/fuel* projects. But we'd li

[openstack-dev] [Oslo] taskflow 2.0 and its changes

Since I am hoping to get taskflow 2.0 out in mitaka I wanted to share with folks some of the debt collected items that have been/are scheduled for removal. Most of these have been removed in 6+ months (some have been around from 2014) and with the 2.0 release it seems like the best time to cle

Re: [openstack-dev] [Ironic][Nova][Neutron] Multi-tenancy support

On Mon, Nov 16, 2015 at 06:38:28PM +, Sean M. Collins wrote: > On Mon, Nov 16, 2015 at 12:47:13PM EST, Vasyl Saienko wrote: > > [0] https://github.com/jumpojoy/neutron > > The way you created the repository in GitHub, it is impossible to diff > it against master to see what you did. > > https

Re: [openstack-dev] [neutron][networking-sfc] Deploying current networking-sfc

Hi Kyle, Thanks for adding patch [3] to clarify the current API status. Cathy From: Kyle Mestery [mailto:mest...@mestery.com] Sent: Monday, November 16, 2015 2:16 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron][networking-sfc] Deploying

Re: [openstack-dev] [neutron][networking-sfc] Deploying current networking-sfc

On Mon, Nov 16, 2015 at 4:03 PM, Russell Bryant wrote: > On 11/16/2015 01:42 PM, Sean M. Collins wrote: > > On Mon, Nov 16, 2015 at 04:11:42PM EST, Paul Carver wrote: > >> This is a challenge. Personally, I haven't been able to get it all > working > >> yet. But we're in a dilemma because we want

Re: [openstack-dev] [tacker] Proposing Sripriya Seetharam to Tacker core

Thank you. Will try to do my best! -Sripriya From: Sridhar Ramaswamy [mailto:sric...@gmail.com] Sent: Monday, November 16, 2015 11:42 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tacker] Proposing Sripriya Seetharam to Tacker core Thanks ev

[openstack-dev] [Oslo] Virtual sprint! End of this week!! (get'm while they are hot)

Howdy folks, This week the oslo team will be offering a one time deal that everyone will be interested in! We will be offering 100% off on documentation changes during this week's documentation (*virtual*) sprint[1]. Starting this Thursday and Friday we will (as a group/team) be accepting all n

Re: [openstack-dev] [neutron][networking-sfc] Deploying current networking-sfc

On 11/16/2015 01:42 PM, Sean M. Collins wrote: > On Mon, Nov 16, 2015 at 04:11:42PM EST, Paul Carver wrote: >> This is a challenge. Personally, I haven't been able to get it all working >> yet. But we're in a dilemma because we want to get good reviews of the code >> before merging. Since the full

[openstack-dev] [DefCore] Request for comments: Is booting Linux VM required for OpenStack interoperability?

Hello Everyone, DefCore committee would like to hear your input on this issue: https://review.openstack.org/#/c/244782/ The issue is not really vendor specific. At the heart of the issue is this question: for interoperability reasons, should certified OpenStack powered compute clouds be able to

Re: [openstack-dev] [neutron][networking-sfc] Deploying current networking-sfc

On Mon, Nov 16, 2015 at 04:11:42PM EST, Paul Carver wrote: > This is a challenge. Personally, I haven't been able to get it all working > yet. But we're in a dilemma because we want to get good reviews of the code > before merging. Since the full functionality is quite a lot of code we > wanted to

[openstack-dev] [OSSN 0059] Trusted VM can be powered on untrusted hosts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Trusted VM can be powered on untrusted hosts - --- ### Summary ### A trusted VM that has been launched earlier on a trusted host can still be powered on from the same host even after the trusted host is compromised. ### Affected Services / Software

Re: [openstack-dev] [neutron][networking-sfc] Deploying current networking-sfc

On 11/16/2015 3:39 PM, Sean M. Collins wrote: Networking-sfc is still just a shell - there is no functional code. To be more clear, most of the code has not yet been merged. Click here for a link to all the pending reviews that contain lots of functional code targetted at merging into the ne

Re: [openstack-dev] [neutron][networking-sfc] Deploying current networking-sfc

Hi Duarte, We have just rebased the patches. We are in the stage of more comprehensive testing, bug fixes, review, and incorporating review comments. The code patches including the devstack patch will be merged once they are properly reviewed, and you can then download and deploy this functiona

Re: [openstack-dev] [neutron][networking-sfc] Deploying current networking-sfc

Networking-sfc not just a shell. It has API, DB, DB Migration, Common Driver Manager, OVS Driver, OVS Agent, CLI, Horizon etc. codes uploaded for review for over one month. The project team is in the final review stage. And a patch for adding DevStack support for networking-sfc has also been upl

Re: [openstack-dev] [neutron][sfc] How could an L2 agent extension access agent methods ?

I have updated the etherpad to add "Overall requirement - API cross check among the features that can manipulate the same flow's forwarding behavior". Thanks, Cathy -Original Message- From: Paul Carver [mailto:pcar...@paulcarver.us] Sent: Monday, November 16, 2015 7:50 AM To: OpenStack

Re: [openstack-dev] [neutron][networking-sfc] Deploying current networking-sfc

Networking-sfc is still just a shell - there is no functional code. -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib

[openstack-dev] [Glance] M-1 Bugs/Reviews squash day

Greetings, At our last meeting, we discussed the idea of having a Bug/Reviews squash day before the end of M-1. I'm sending this email out to propose that we do this work on one of the following dates: - Friday November 20th (ALL TZs) - Monday November 23rd (ALL TZs) I realize that next week is

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 11/10/2015 10:08 AM, Tzu-Mainn Chen wrote: Hi all, At the last IRC meeting it was agreed that the new TripleO REST API should forgo the Tuskar name, and simply be called... the TripleO API. There's one more point of discussion: where should the API live? There are two possibilities: a) P

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

Hi all, I wanted to start some discussion re $subject, because it's been apparrent that we have a lack of clarity on this issue (and have done ever since we started using parameter_defaults). Some context: - Historically TripleO has provided a fairly comprehensive "top level" parameters inte

Re: [openstack-dev] [all] [oslo] Please stop removing usedevelop from tox.ini (at least for now)

Excerpts from gord chung's message of 2015-11-16 12:04:27 -0500: > > On 16/11/2015 11:13 AM, Doug Hellmann wrote: > > does anyone want to sign up to remove that last > > namespace package? > already in action: https://review.openstack.org/#/c/243255/ > Thanks, Gordon!

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

On 11/16/2015 04:25 PM, Steven Hardy wrote: Hi all, I wanted to start some discussion re $subject, because it's been apparrent that we have a lack of clarity on this issue (and have done ever since we started using parameter_defaults). [...] How do people feel about this example, and others

[openstack-dev] [ironic] weekly subteam status report

Hi, We are stoked to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) (diff with Nov 9) - Open: 167 (-4). 10 new (-2), 61 in progress (-2), 0 critical, 14 high and 11 incomplete (+1) - Nova b

Re: [openstack-dev] REST API collation and visualization

On 16/11/15 17:54, Neil Jerram wrote: > On 16/11/15 16:37, Neil Jerram wrote: >> Hi there, >> >> I'm interested in collating all the REST API exchanges to and between >> OpenStack components, and presenting / visualizing all those in an >> easily comprehensible way. Is there already some tool to d

Re: [openstack-dev] [Ironic][Nova][Neutron] Multi-tenancy support

On Mon, Nov 16, 2015 at 12:47:13PM EST, Vasyl Saienko wrote: > [0] https://github.com/jumpojoy/neutron The way you created the repository in GitHub, it is impossible to diff it against master to see what you did. https://github.com/jumpojoy/neutron/compare -- Sean M. Collins __

[openstack-dev] [neutron][networking-sfc] Deploying current networking-sfc

Hi networking-sfc folks, I can't seem to be able to deploy the current networking-sfc using DevStack and my hint is that the latest review stack is dependent on previous patches that have not been updated/rebased yet ([1] and [2]) - and are depending on outdated patches. In [3] you can see the

Re: [openstack-dev] [Ironic] Quick poll: OpenStackClient command for provision action

On 10 November 2015 at 11:31, Dmitry Tantsur wrote: > On 11/10/2015 05:21 PM, Brad P. Crochet wrote: > >> On Tue, Nov 10, 2015 at 4:09 AM, Dmitry Tantsur >> wrote: >> >>> Hi all! >>> >>> I'd like to seek consensus (or at least some opinions) on patch >>> https://review.openstack.org/#/c/206119/

Re: [openstack-dev] [puppet] weekly meeting #59

Hi Emilien, the link for the agenda is https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-2015111 or https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20151117 ? Thanks o/ 2015-11-16 14:04 GMT-03:00 Emilien Macchi : > Hello! > > Here's an initial agenda for our weekl

Re: [openstack-dev] [neutron][ironic] Ironic-Neutron meeting cancellation notice

On 15 November 2015 at 16:47, Sukhdev Kapur wrote: > Folks, > > We are canceling this week's Ironic-neutron integration meeting. I have a > family obligation to take care of and I have not been able to find a > replacement person who can chair this meeting. Therefore, we will cancel > this week's

Re: [openstack-dev] REST API collation and visualization

On 16/11/15 16:37, Neil Jerram wrote: > Hi there, > > I'm interested in collating all the REST API exchanges to and between > OpenStack components, and presenting / visualizing all those in an > easily comprehensible way. Is there already some tool to do that? > > Many thanks, > Neil Well her

Re: [openstack-dev] [Ironic][Nova][Neutron] Multi-tenancy support

Hello Community, There is 'raw' version of Generic ML2 Driver [0]. It uses 'Netmiko' [1] library. At the moment it supports Cisco Catalyst switches but it can be easily extended with ANY ssh enabled switch. [0] https://github.com/jumpojoy/neutron [1] https://github.com/ktbyers/netmiko On Wed, No

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On 13 November 2015 at 14:10, Thierry Carrez wrote: > So.. quick summary of this thread so far. > > (-) > * Not enough work to warrant a designated "team", now that the work is > decentralized and the cats are mostly herding themselves > * The change is unlikely to bring a meaningful improvement t

Re: [openstack-dev] [oslo][all] Oslo libraries dropping python 2.6 compatability

Yes, major version bump. As long as we don't have to change any consumers, we have no backwards compatibility concerns because we deprecated 2.6 in Juno. However i suspect we will have to change consumers specifically we still had 2.6 jobs in liberty On 17 Nov 2015 3:23 AM, "Davanum Srinivas" wrot

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

Chatted with Sean D. on IRC, pushed up a patch https://review.openstack.org/#/c/245862/ -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On 13/11/15 15:10 +0100, Thierry Carrez wrote: So.. quick summary of this thread so far. (-) * Not enough work to warrant a designated "team", now that the work is decentralized and the cats are mostly herding themselves * The change is unlikely to bring a meaningful improvement to the situation

Re: [openstack-dev] [Fuel] Running Fuel node as non-superuser

Hello folks, I have updated the spec, please review and share your thoughts on it: https://review.openstack.org/#/c/243340/ Thanks. On Thu, Nov 12, 2015 at 10:42 AM, Dmitry Nikishov wrote: > Matthew, > > sorry, didn't mean to butcher your name :( > > On Thu, Nov 12, 2015 at 10:41 AM, Dmitry Ni

Re: [openstack-dev] [all] [oslo] Please stop removing usedevelop from tox.ini (at least for now)

On 16/11/2015 11:13 AM, Doug Hellmann wrote: does anyone want to sign up to remove that last namespace package? already in action: https://review.openstack.org/#/c/243255/ -- gord __ OpenStack Development Mailing List

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

Hello! Here's an initial agenda for our weekly meeting, Tuesday at 1500 UTC in #openstack-meeting-4: https :// etherpad.openstack.org

[openstack-dev] [Fuel] Deprecation of GRE network segmentation in Fuel 8.0

Hi all! AFAIK, GRE network segmentation option has been deprecated for clusters with Neutron since 7.0 release, both on UI and Library side. One still can use the option via CLI as no relevant changes were made to Nailgun API. Though appropriate warning is displayed in the case. So I wanted to as

[openstack-dev] [Neutron] Team meeting this Tuesday at 1400 UTC

Hi folks, A kind reminder for tomorrow's meeting. Please add agenda items to the meeting here [1]. Cheers, Armando [1] https://wiki.openstack.org/wiki/Network/Meetings __ OpenStack Development Mailing List (not for usage que

[openstack-dev] REST API collation and visualization

Hi there, I'm interested in collating all the REST API exchanges to and between OpenStack components, and presenting / visualizing all those in an easily comprehensible way. Is there already some tool to do that? Many thanks, Neil ___

Re: [openstack-dev] [all] [oslo] Please stop removing usedevelop from tox.ini (at least for now)

Excerpts from Dmitry Tantsur's message of 2015-11-16 12:37:15 +0100: > On 11/16/2015 12:28 PM, Davanum Srinivas wrote: > > Dmitry, > > > > i was trying to bring sanity to the tox.ini(s). +1 to documenting this > > step somewhere prominent. > > Please don't get me wrong, I really appreciate it. I'm

Re: [openstack-dev] [oslo] Graduate cliutils.py into oslo.utils

Excerpts from Kekane, Abhishek's message of 2015-11-16 07:33:48 +: > Hi, > > As apiclient is now removed from oslo-incubator, to proceed with request-id > spec [1] I have two options in mind, > > > 1. Use keystoneauth1 + cliff in all python-clients (add request-id > support in cliff

Re: [openstack-dev] [freezer] Proposal to add Eldar Nugaev to freezer-core

+1 From: Marzi, Fausto Sent: 13 November 2015 16:39 To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [freezer] Proposal to add Eldar Nugaev to freezer-core Hi All, I'd like to propose Eldar as core in Freezer, as his help, dedication and contribution wa

Re: [openstack-dev] [api] consolidate IRC change with #openstack-sdk?

On 11/16/2015 09:42 AM, Sean Dague wrote: On 11/16/2015 09:34 AM, michael mccune wrote: On 11/13/2015 07:58 AM, Sean Dague wrote: The #openstack-api IRC channel is quite quiet most days. As such it's not something that people are regularly checking in on, or often forget about (I know I've been

Re: [openstack-dev] [oslo][all] Oslo libraries dropping python 2.6 compatability

Excerpts from Davanum Srinivas (dims)'s message of 2015-11-16 09:23:39 -0500: > Gordon, > > When we stop the py26 jobs, the next version we release should have > major bumps by semver definition. liberty does not have version caps > unfortunately, but i'll let Doug and others chime in on that. >

Re: [openstack-dev] [freezer] Proposal to add Pierre-Arthur Mathieu to freezer-core

+1 Fabrizio From: Marzi, Fausto Sent: 13 November 2015 16:45 To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [freezer] Proposal to add Pierre-Arthur Mathieu to freezer-core Hi All, I'd like to propose Pierre as core in Freezer. Pierre d

[openstack-dev] [release] making release notes jobs voting

Now that we have several projects successfully using reno, and notes are being published, we are going to turn the release notes jobs back to voting and add a job to the gate queue. If you have issues in your project with the job passing, please add a follow-up to the patch that changes the default

Re: [openstack-dev] [neutron][sfc] How could an L2 agent extension access agent methods ?

On 11/13/2015 7:03 PM, Henry Fourie wrote: I wonder whether just pushing flows into the existing tables at random points in time can be unstable and break the usual flow assumed by the main agent loop. LF> No not expect any issues. Am I making sense? [1] https://etherpad.openstack.org/p/l2

Re: [openstack-dev] [openstack][devstack]Openstack devstack installation failing.

Attach to the screen session Devstack sets up, and verify that the Nova compute service is running. It's running in the screen session named n-api. -- Sean M. Collins __ OpenStack Development Mailing List (not for usage ques

Re: [openstack-dev] [Fuel] API services available on public VIP

I haven't seen any more discussion on this topic. It looks like since we default to enabling SSL/TLS on deployments, there's no reason to block access to public API endpoints. On Fri, Nov 13, 2015 at 5:15 PM, Vladimir Kuklin wrote: > Adam > > I think, the answer is realtively simple - if user do

[openstack-dev] [tripleo] When to use parameters vs parameter_defaults

Hi all, I wanted to start some discussion re $subject, because it's been apparrent that we have a lack of clarity on this issue (and have done ever since we started using parameter_defaults). Some context: - Historically TripleO has provided a fairly comprehensive "top level" parameters interf

[openstack-dev] [all] [ptls] Time to make some assertions about your projects

Hi PTLs, Over the last months the Technical Committee defined a number of "assert" tags which are assertions that project teams make about their own deliverables: * assert:follows-standard-deprecation * assert:supports-upgrade * assert:supports-rolling-upgrade You can find their definition at: h

Re: [openstack-dev] [openstack-ansible][security] Next steps: openstack-ansible-security

On 11/16/2015 07:47 AM, Jesse Pretorius wrote: > Based on the spec's proposed change section [1] I would say that items 4 & 5 > are the next steps. Those steps, however, are kind-of waiting for the gate > split work. Perhaps the best way to get this done that doesn't have the > dependency is to

Re: [openstack-dev] [api] consolidate IRC change with #openstack-sdk?

On 11/16/2015 09:34 AM, michael mccune wrote: > On 11/13/2015 07:58 AM, Sean Dague wrote: >> The #openstack-api IRC channel is quite quiet most days. As such it's >> not something that people are regularly checking in on, or often forget >> about (I know I've been guilty of that). Plus we don't alw

Re: [openstack-dev] [api] consolidate IRC change with #openstack-sdk?

On 11/13/2015 07:58 AM, Sean Dague wrote: The #openstack-api IRC channel is quite quiet most days. As such it's not something that people are regularly checking in on, or often forget about (I know I've been guilty of that). Plus we don't always have the right people in a conversation to make a d

Re: [openstack-dev] [Ironic] Do we need to have a mid-cycle?

in Liberty, we did a virtual meetup in for the telemetry team so i thought i'd share experience. On 16/11/2015 9:05 AM, Jim Rollenhagen wrote: Then we can set up some hangouts (or similar) to get people in the same "room" working on things. Time zones will get weird, but we tend to hangouts is

Re: [openstack-dev] [nova] config options: location and help text

Markus Zoeller/Germany/IBM@IBMDE wrote on 11/16/2015 02:37:14 PM: > From: Markus Zoeller/Germany/IBM@IBMDE > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 11/16/2015 02:38 PM > Subject: [openstack-dev] [nova] config options: location and help text > > target audie

Re: [openstack-dev] [oslo][all] Oslo libraries dropping python 2.6 compatability

Gordon, When we stop the py26 jobs, the next version we release should have major bumps by semver definition. liberty does not have version caps unfortunately, but i'll let Doug and others chime in on that. yes, i know major bumps are hard thanks, dims On Mon, Nov 16, 2015 at 9:07 AM, gord chun

Re: [openstack-dev] [Ironic] Do we need to have a mid-cycle?

On Wed, Nov 11, 2015 at 12:16:34PM -0500, Ruby Loo wrote: > On 10 November 2015 at 12:08, Dmitry Tantsur wrote: > > > On 11/10/2015 05:45 PM, Lucas Alvares Gomes wrote: > > > >> Hi, > >> > >> In the last Ironic meeting [1] we started a discussion about whether > >> we need to have a mid-cycle mee

Re: [openstack-dev] [oslo][all] Oslo libraries dropping python 2.6 compatability

do we require a major versioning bump for this? i'm wondering how 'breaking' this is in real life if all the services have dropped py2.6 already. maybe this just requires an upper-cap in appropriate stable branches? to be devils advocate, one (arguably terrible) reason for not doing a major b

Re: [openstack-dev] [openstack-ansible] Converting the AIO bootstrap script to Ansible

On 6 November 2015 at 21:34, Major Hayden wrote: > Feel free to critique it and I'll get to work on making the changes. The > spec[2] should answer most of the questions about the effort. > > Thanks! :) > > [1] https://review.openstack.org/#/c/239525/ > [2] > http://specs.openstack.org/openstack

Re: [openstack-dev] [openstack-ansible][security] Next steps: openstack-ansible-security

On 9 November 2015 at 19:38, Major Hayden wrote: > > What would you propose as the final steps to get the blueprint marked as > completed? Should documentation be added into openstack-ansible about > integrating openstack-ansible-security or should a script be provided for > quicker integration?

[openstack-dev] [nova] config options: location and help text

target audience === * Code contributors who introduce new or change existing config options * Newbies who are looking for a starter friendly task Why am I receiving this? With bp [1] we got some aggreement on how we should handle the config options of Nova. Lon

[openstack-dev] [mistral] Team meeting - 11/16/2015

Hi, This is just a reminder that we’ll have a team meeting today at #openstack-meeting at 16.00 UTC. Agenda: Review action items Current status (progress, issues, roadblocks, further plans) Open discussion Put your own items at https://wiki.openstack.org/wiki/Meetings/MistralAgenda

Re: [openstack-dev] [stackalytics] Review metrics: average numbers

Hi Mike, Not 100% sure what you're asking for but have you seen these stats? http://russellbryant.net/openstack-stats/ Alexis (lxsli) -- Nova developer, Hewlett-Packard Limited. Registered Office: Cain Road, Bracknell, Berkshire RG12 1HN. Registered Number: 00690597 England VAT number: GB

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 11/16/2015 06:57 AM, Korzeniewski, Artur wrote: > Thanks Sean D. for explanation! > > > > I’ve taken a look into old Russell patches, and it seems that the > project-config was already modified by him: > > Add check-grenade-dsvm-partial-ncpu-neutron: (project-config) > > https://review.ope

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

Thanks Sean D. for explanation! I’ve taken a look into old Russell patches, and it seems that the project-config was already modified by him: Add check-grenade-dsvm-partial-ncpu-neutron: (project-config) https://review.openstack.org/#/c/189426 Add check-grenade-dsvm-partial-ncpu-neutron-dvr (p

Re: [openstack-dev] [All] Use of self signed certs in endpoints

On 11/16/2015 01:03 AM, Jamie Lennox wrote: > > > On 14 November 2015 at 19:09, Xav Paice > wrote: > > Hi, > > I'm sure I'm not the only one that likes to use SSL everywhere > possible, and doesn't like to pay for 'real' ssl certs for dev > environmen

Re: [openstack-dev] [heat] Questions about BP for enable/disable heat-engine

Ethan Lynn, This blue-print has two parts , one to perform the graceful-shutdown to make sure all IN_PROGRESS resources/stacks in the given engine to reach its final state.. Other one, expose this feature as disable engine to support the maintenance. I was planning to re-write the spec to provid

Re: [openstack-dev] [networking-ovs-dpdk]

Hi Sean, Thanks for your response. in your case though you are using 1GB hugepages so I don’t think this is related to memory fragmentation or a lack of free hugepages. to use preallocated 1GB page with ovs you should instead set the following in your local.conf OVS_HUGEPAGE_MOUNT_PAGESIZE=

Re: [openstack-dev] [networking-ovs-dpdk] ovs-appctl doesn't function correctly

That is helpful, thanks Sean ! On Mon, Nov 16, 2015 at 7:12 PM, Mooney, Sean K wrote: > To use the ovs-appctl application you have to specify the socket path to > the ovs-vswitchd process. > > ovs-appctl -t /var/run/openvswitch/ list-commands > > e.g. > > ovs-appctl -t /var/run/openvswitch/ovs-v

Re: [openstack-dev] [all] [oslo] Please stop removing usedevelop from tox.ini (at least for now)

On 11/16/2015 12:28 PM, Davanum Srinivas wrote: Dmitry, i was trying to bring sanity to the tox.ini(s). +1 to documenting this step somewhere prominent. Please don't get me wrong, I really appreciate it. I'm not sure why "usedevelop" is not the default, though. Maybe we at least make sure to

Re: [openstack-dev] [all] [oslo] Please stop removing usedevelop from tox.ini (at least for now)

Dmitry, i was trying to bring sanity to the tox.ini(s). +1 to documenting this step somewhere prominent. -- Dims On Mon, Nov 16, 2015 at 5:37 AM, Dmitry Tantsur wrote: > On 11/16/2015 11:35 AM, Julien Danjou wrote: >> >> On Mon, Nov 16 2015, Dmitry Tantsur wrote: >> >>> Before you ask: using 's

Re: [openstack-dev] [nova] hackathon day

Hi, > -Original Message- > From: Wang, Shane [mailto:shane.w...@intel.com] > Sent: 12 November 2015 16:34 > To: OpenStack Development Mailing List (not for usage questions); Daniel P. > Berrange; Bhargava, Ruchi > Subject: Re: [openstack-dev] [nova] hackathon day > > Hey, how about driv

Re: [openstack-dev] [networking-ovs-dpdk] ovs-appctl doesn't function correctly

To use the ovs-appctl application you have to specify the socket path to the ovs-vswitchd process. ovs-appctl -t /var/run/openvswitch/ list-commands e.g. ovs-appctl -t /var/run/openvswitch/ovs-vswitchd.10110.ctl list-commands From: Hui Xiang [mailto:hui.xi...@canonical.com] Sent: Monday, Novemb

Re: [openstack-dev] [networking-ovs-dpdk]

Hi Yes sorry for the delay in responding to you and samta. In your case assuming you are using 2mb hugepages it is easy to hit dpdks default max memory segments This can be changed by setting OVS_DPDK_MEM_SEGMENTS= In the local.conf and recompiling. To do this simply remove the build complete

Re: [openstack-dev] [all] [oslo] Please stop removing usedevelop from tox.ini (at least for now)

On 11/16/2015 11:35 AM, Julien Danjou wrote: On Mon, Nov 16 2015, Dmitry Tantsur wrote: Before you ask: using 'sudo pip install -U setuptools pbr' is out of question in binary distributions :) so please make sure to remove this line only when everyone is updated to whatever version is required

Re: [openstack-dev] [designate] Records for floating addresses are not removed when an instance is removed

Thanks Matt. The link was very useful. However, I couldn't make it work. The event 'port.delete.end' has the following payload: > {u'port_id': u'86580146-1772-4e32-8d7b-92bbb9131ae5'} > It only provides the port_id. But without the tenant_id, I cannot get the context associated to the tenant. I'v

Re: [openstack-dev] [all] [oslo] Please stop removing usedevelop from tox.ini (at least for now)

On Mon, Nov 16 2015, Dmitry Tantsur wrote: > Before you ask: using 'sudo pip install -U setuptools pbr' is out of question > in binary distributions :) so please make sure to remove this line only when > everyone is updated to whatever version is required for understanding these > ;python_version=

[openstack-dev] [all] [oslo] Please stop removing usedevelop from tox.ini (at least for now)

Hi all! I've seen a couple of patches removing "usedevelop = true" from tox.ini. This has 2 nasty consequences: 1. It's harder to manually experiment in tox environment, as you have to explicitly use 'tox' command every time you change code 2. The most important, it breaks tox invocation for al

[openstack-dev] [networking-ovs-dpdk] ovs-appctl doesn't function correctly

Hi all, I have managed to setup ovs-dpdk on Ubuntu, commands 'ovs-vsctl/ovs-ofctl' all work well excep 'ovs-appctl', could anyone help me to figure it out? Thanks in advance. xianghui@xianghui:~$ sudo ovs-ofctl show br-int OFPT_FEATURES_REPLY (xid=0x2): dpid:264fa4e1f24f n_tables:254, n_bu

Re: [openstack-dev] [all][api] New API Guidelines Ready for Cross Project Review

Everett Toews wrote: > The following API guidelines are ready for cross project review. They will be > merged on Nov. 20 if there's no further feedback. > [...] I see you added this topic for the next cross-project meeting. Would you mind chairing that meeting ? I'm traveling with limited availab

[openstack-dev] [Nova] notification subteam meeting

Hi, The next meeting of the nova notification subteam will happen 2015-11-17 Tuesday 20:00 UTC [1] on #openstack-meeting-alt on freenode Agenda: - Status of the outstanding specs and code reviews - AOB See you there. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?i

  1   2   >