Re: [openstack-dev] [horizon]

Awesome, thanks a lot for setting this up, David! -- Jarda On 2014/26/01 02:10, Lyle, David wrote: With meeting logging now available in #openstack-meeting-3, the official Horizon meeting time is now Tuesdays at 1600 UTC in #openstack-meeting-3. Looking forward to seeing all Horizon folks ther

[openstack-dev] #openstack-meeting-3 available for meetings

Hi everyone, We added a new logged channel for meetings that you may want to lurk in: #openstack-meeting-3 That means we now have three channels (#openstack-meeting, #openstack-meeting-alt, #openstack-meeting-3) available for meetings, which should solve meeting space congestion for the time bei

Re: [openstack-dev] [Ironic] Node groups and multi-node operations

On 27 January 2014 18:08, Joshua Harlow wrote: > Thanks, guess this is entering the realm of scheduling & group scheduling and > how "just the right" level of information is needed to do efficient group > scheduling in nova/ironic vs the new/upcoming gantt service. > > To me splitting it into N

Re: [openstack-dev] [snabb-devel] RE: [Neutron] Building a new open source NFV system for Neutron

On 23 January 2014 17:42, Calum Loudon wrote: > That sounds fantastic. As an NFV application developer I'm very pleased > to see this contribution which looks to eliminate the key bottleneck > hitting the performance of very high packet throughput apps on > OpenStack. > Thanks for the kind word

Re: [openstack-dev] [nova] Checking before delete flavor?

On 2014?01?26? 20:05, Rui Chen wrote: Hi Stackers: Some instance operations and flavor are closely connected, for example, resize. If I delete the flavor when resize instance, instance will be error. Like this: 1. run instance with flavor A 2. resize instance from flavor A to flavor B 3. del

Re: [openstack-dev] Fwd: [TripleO] mid-cycle meetup?

I'd love to come, but at this stage I won't be able to travel before about March 3, which sounds like it's a few weeks later than most people were thinking of. -- Forwarded message -- From: Robert Collins mailto:robe...@robertcollins.net >> Date: 24 January 2014 08:47 Subject: [T

Re: [openstack-dev] Nova style cleanups with associated hacking check addition

On Fri, Jan 24, 2014 at 11:42:54AM -0500, Joe Gordon wrote: > On Fri, Jan 24, 2014 at 7:24 AM, Daniel P. Berrange > wrote: > > > Periodically I've seen people submit big coding style cleanups to Nova > > code. These are typically all good ideas / beneficial, however, I have > > rarely (perhaps ev

Re: [openstack-dev] [horizon]

+1 Great news, thank you, David! -- Kind regards, Tatiana On Sun, Jan 26, 2014 at 5:10 AM, Lyle, David wrote: > With meeting logging now available in #openstack-meeting-3, the official > Horizon meeting time is now Tuesdays at 1600 UTC in #openstack-meeting-3. > > Looking forward to seeing a

Re: [openstack-dev] [Ceilometer] Issues with transformers

On Mon, Jan 27 2014, Adrian Turjak wrote: > I created a gauge metric that is updated via notifications, and a pollster. > The data from both of those needs to be transformed in to a cumulative > metric. The transformer object works as intended, but the issue is that > while my pollster/notificatio

Re: [openstack-dev] [horizon]

On 01/27/2014 09:10 AM, Jaromir Coufal wrote: Awesome, thanks a lot for setting this up, David! -- Jarda On 2014/26/01 02:10, Lyle, David wrote: With meeting logging now available in #openstack-meeting-3, the official Horizon meeting time is now Tuesdays at 1600 UTC in #openstack-meeting-3.

Re: [openstack-dev] [Nova] bp proposal: discovery of peer instances through metadata service

> -Original Message- > From: Clint Byrum [mailto:cl...@fewbar.com] > Sent: 24 January 2014 21:09 > To: openstack-dev > Subject: Re: [openstack-dev] [Nova] bp proposal: discovery of peer instances > through metadata service > > Excerpts from Justin Santa Barbara's message of 2014-01-24 12:2

Re: [openstack-dev] [glance]A question abount the x-image-meta-property parameter.

I think it is OK that we keep the current behavior. But we need to note it in api spec clearly. And I have another question. :) V1 api allows user to use "x-image-meta-id" parameter to create an image. But if I specify a *deleted* image id to create an image, I will get 409 response, however I can

Re: [openstack-dev] [glance]A question abount the x-image-meta-property parameter.

On 27/01/14 14:49 +0800, Fei Long Wang wrote: Zhi Yan, FWIW, your concern is reasonable. Thanks for raising it. Based on the Glance v1 strategy, and backward-compatibility concern, maybe we should mark it as won't fix? Brian, may I get your opinion on this from a product manager perspective? Tha

Re: [openstack-dev] [glance]A question abount the x-image-meta-property parameter.

I think you're talking about reuse image id, now there is a bug tracking it, see https://bugs.launchpad.net/glance/+bug/1176978 For now, I would say it works as designed. Because we're using soft-delete in DB level and there is no way to list the deleted image based on current implement. BTW, may

Re: [openstack-dev] [Nova] bp proposal: discovery of peer instances through metadata service

>> >> What worried me most, I think, is that if we make this part of the standard >> metadata then everyone would get it, and that raises a couple of concerns: >> >> - Users with lots of instances (say 1000's) but who weren't trying to run any >> form of discovery would start getting a lot more m

[openstack-dev] [api-site] how to switch the project version for api document

Hi, I noticed that API reference in http://api.openstack.org/api-ref.htmldoesn't mention anything about the version issue. For example, Ceilometer has /v1 /v2 API, and /v2 is cross Havana and Icehouse, so if Icehouse adds some new features which add new arguments to the v2 API, then how does the r

[openstack-dev] Gate Status - Monday edition

Unless things go terribly wrong this week, this will be the last of these emails for a while. The gate seems to be back in a new normal, and actually emptied this weekend. Gate Stats: * Gate queue: 9 * Check queue: 83 * Top of gate entered: 2hrs 40min ago The sliding window algorthim for gate

Re: [openstack-dev] [Nova] bp proposal: discovery of peer instances through metadata service

Hi Justin, My though process is to go back to basics. To perform discovery there is no getting away from the fact that you have to start with a well-known address that your peers can access on the network. The second part is a service/protocol accessible at that address that can perform the dis

Re: [openstack-dev] [Infra] Exporting gate config files along with logs

On 25/01/14 10:57 +, Jeremy Stanley wrote: On 2014-01-23 16:52:53 +0100 (+0100), Flavio Percoco wrote: [...] If so, is it possible to export config files as well? [...] Patch functions.sh(cleanup_host) in openstack-infra/devstack-gate to copy the files of interest into $BASE/logs/ and they

Re: [openstack-dev] [Glance] Meetup Schedule Posted!

On 26/01/14 21:49 -0500, Mark Washenberger wrote: On Mon, Jan 20, 2014 at 1:29 PM, Mark Washenberger < mark.washenber...@markwash.net> wrote: On Mon, Jan 20, 2014 at 7:44 AM, Georgy Okrokvertskhov < gokrokvertsk...@mirantis.com> wrote: Hi Mark, Happy Martin Luther Kin

Re: [openstack-dev] Hyper-V Nova CI Infrastructure

On 25 Jan 2014, at 00:25 , Russell Bryant wrote: > On 01/24/2014 04:41 PM, Peter Pouliot wrote: >> Hello OpenStack Community, >> >> >> >> I am excited at this opportunity to make the community aware that the >> Hyper-V CI infrastructure >> >> is now up and running. Let’s first start with so

Re: [openstack-dev] [glance]A question abount the x-image-meta-property parameter.

On 27/01/14 19:40 +0800, Fei Long Wang wrote: I think you're talking about reuse image id, now there is a bug tracking it, see https://bugs.launchpad.net/glance/+bug/1176978 For now, I would say it works as designed. Because we're using soft-delete in DB level and there is no way to list the del

Re: [openstack-dev] [nova]Why not allow to create a vm directly with two VIF in the same network

Lingxian Kong wrote: >Actually, in the scenario of NFV, all the rules or behaviors of the physical >world will apply to that in the virtual world, right? >IMHO, despite of the scenarios, we should at least guarantee the consistency >of creating vms with nics and attaching nics . I'll need to t

[openstack-dev] Proposed Logging Standards

Back at the beginning of the cycle, I pushed for the idea of doing some log harmonization, so that the OpenStack logs, across services, made sense. I've pushed a proposed changes to Nova and Keystone over the past couple of days. This is going to be a long process, so right now I want to just focu

Re: [openstack-dev] Hyper-V Nova CI Infrastructure

On 25 Jan 2014, at 16:51 , Matt Riedemann wrote: > > > On 1/24/2014 3:41 PM, Peter Pouliot wrote: >> Hello OpenStack Community, >> >> I am excited at this opportunity to make the community aware that the >> Hyper-V CI infrastructure >> >> is now up and running. Let’s first start with some ho

Re: [openstack-dev] Proposed Logging Standards

Hi Sean, I'm currently working on moving away from the "built-in" logging to use log_config= and the python logging framework so that we can start shipping to logstash/sentry/. I'd be very interested in getting involved in this, especially from a "why do we have log messages that are split acr

[openstack-dev] What's Up Doc? Jan 27 2014

This week we have two chances to talk docs -- the IRC meeting for US and Europe is every other Wednesday in #openstack-meeting-alt at 03:00 UTC. We're also hosting a hangout on air on Wednesday, January 29, 2014 at 20:00:00 UTC. Look for a Hangouts On Air invitation on Google Plus. 1. In review a

Re: [openstack-dev] [TripleO] [Tuskar] Terminology Revival #1 - Roles

Based on this thread which didn't seem to get clear outcome, I have one last suggestion: * Deployment Role It looks that it might satisfy participants of this discussion. When I internally talked to people it got the best reactions from already suggested terms. Depending on your reactions f

Re: [openstack-dev] Proposed Logging Standards

> -Original Message- > From: Sean Dague [mailto:s...@dague.net] > Sent: 27 January 2014 14:26 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] Proposed Logging Standards > > On 01/27/2014 09:07 AM, Macdonald-Wallace, Matthew wrote: > > Hi Se

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV

Hi Folks, In today's meeting, we discussed a scheduler issue for SRIOV. The basic requirement is for coexistence of the following compute nodes in a cloud: -- SRIOV only compute nodes -- non-SRIOV only compute nodes -- Compute nodes that can support both SRIOV and non-SRIOV port

Re: [openstack-dev] [Nova] Proposal to add Matt Riedemann to nova-core

As a reviewee of Matt I vote +1 On 11/23/2013 10:17 AM, Gary Kotton wrote: This message has been archived. View the original item

Re: [openstack-dev] [Solum] Proposed changes to solum-core

+1 -Original Message- From: "Murali Allada" Sent: Sunday, January 26, 2014 8:19pm To: "OpenStack Development Mailing List (not for usage questions)" Cc: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [Solum] Proposed changes to solum-core

Re: [openstack-dev] [Tempest - Stress test] : cleanup() removing resources for all tenants with an admin_manager

Hello Boris, Rally seemes to be a really interesting tool and I will eventually using it for full scale benchmarking. However I will focus on tempest based tests for the time being in order to have these tests replayed regularly during the integration process. I believe that my needs are covere

Re: [openstack-dev] [Nova] bp proposal: discovery of peer instances through metadata service

Day, Phil wrote: > > >> We already have a mechanism now where an instance can push metadata as > >> a way of Windows instances sharing their passwords - so maybe this could > >> build on that somehow - for example each instance pushes the data its > >> willing to share with other instances owned b

Re: [openstack-dev] [Neutron] Representing PEM Format file as string

On 01/26/2014 05:36 PM, rajesh_moh...@dell.com wrote: > I am working on SSL VPN BP. > > CA certificate is one of the resources. We decided to use PEM formatted > certificates. It is multi-line string > > 1 -BEGIN CERTIFICATE- > 2 MIID3TCCA0agAwIBAgIJAKRWnul3NJnrMA0GCSqGSIb3DQEBBQUAM

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV

Hi Robert, all, My comments inline Regards, Irena From: Robert Li (baoli) [mailto:ba...@cisco.com] Sent: Monday, January 27, 2014 5:05 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV Hi Folks, In today's meet

Re: [openstack-dev] Proposed Logging Standards

> > I've also noticed just now that we appear to be "re-inventing" some parts of > the logging framework (openstack.common.log.WriteableLogger for example > appears to be a "catchall" when we should just be handing off to the default > logger and letting the python logging framework decide what to

Re: [openstack-dev] [Solum] Proposed changes to solum-core

On 01/24/2014 08:32 PM, Adrian Otto wrote: > Solum Core Reviewers, > > I propose the following changes to solum-core: > > +asalkeld > +noorul > -mordred > > Thanks very much to mordred for helping me to bootstrap the reviewer team. > Please reply with your votes. +1 -- Russell Bryant __

[openstack-dev] [Tempest - Stress Test] : some improvements / issues on the stress test framework

Hi everyone, I would like to discuss some ideas / behavior that seems broken in the stress test part of Tempest. I opened some tickets in Launchpad and I would like to get the feedback of the community on these ideas / issues : - Provide kwargs from UnitTest to stress test scenarios (https://

Re: [openstack-dev] Proposed Logging Standards

On 01/27/2014 09:07 AM, Macdonald-Wallace, Matthew wrote: > Hi Sean, > > I'm currently working on moving away from the "built-in" logging to use > log_config= and the python logging framework so that we can start > shipping to logstash/sentry/. > > I'd be very interested in getting involved in

Re: [openstack-dev] Proposed Logging Standards

> -Original Message- > From: Sean Dague [mailto:s...@dague.net] > Sent: 27 January 2014 14:26 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] Proposed Logging Standards > > On 01/27/2014 09:07 AM, Macdonald-Wallace, Matthew wrote: > > Hi Se

Re: [openstack-dev] Proposed Logging Standards

On Mon, Jan 27, 2014 at 8:07 AM, Sean Dague wrote: > Back at the beginning of the cycle, I pushed for the idea of doing some > log harmonization, so that the OpenStack logs, across services, made > sense. I've pushed a proposed changes to Nova and Keystone over the past > couple of days. > > This

[openstack-dev] [Climate] [Ceilometer] Integration

Hi, I've created a blueprint for Climate support in Ceilometer: https://blueprints.launchpad.net/ceilometer/+spec/climate-support I've added a list of resources that I think should be metered. I'm not sure about the other ones that I encountered in Climate; feel free to amend that list in the

Re: [openstack-dev] Proposed Logging Standards

On 01/27/2014 09:44 AM, Macdonald-Wallace, Matthew wrote: >> -Original Message- >> From: Sean Dague [mailto:s...@dague.net] >> Sent: 27 January 2014 14:26 >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: Re: [openstack-dev] Proposed Logging Standards >> >> On

[openstack-dev] [Neutron][LBaaS] Securing RPC channel between the server and the agent

Hi folks, As we are going to add ssl implementation to lbaas which would be based on well-known haproxy+stunnel combination, there is one problem that we need to solve: securing communication channel between neutron-server and the agent. I see several approaches here: 1) Rely on secure messaging

Re: [openstack-dev] [Neutron][LBaaS] Securing RPC channel between the server and the agent

On 01/27/2014 09:37 AM, Eugene Nikanorov wrote: > Hi folks, > > As we are going to add ssl implementation to lbaas which would be based > on well-known haproxy+stunnel combination, there is one problem that we > need to solve: securing communication channel between neutron-server and > the agent.

Re: [openstack-dev] [TripleO] [Tuskar] Terminology Revival #1 - Roles

I'd argue that we should call it 'overcloud role' - at least from the modeling point of view - since the tuskar-api calls a deployment an overcloud. But I like the general direction of the term-renaming! Mainn - Original Message - > Based on this thread which didn't seem to get clear out

Re: [openstack-dev] [Climate] [Ceilometer] Integration

Julien, great :) Thanks for starting this initiative, it's really interesting and we want to include that functionality to 0.2 Climate - as discussed in https://etherpad.openstack.org/p/climate-0.2 Thank you Dina On Mon, Jan 27, 2014 at 8:12 PM, Julien Danjou wrote: > Hi, > > I've created a b

[openstack-dev] [Keystone] - Cloud federation on top of the Apache

Dear all, We have Identity Provider and mapping CRUD operations already merged, so it's a good point to prepare Keystone and Apache to handle SAML (as a starter) requests/responses. For the next OpenStack release it'd be the Apache that handles SAML communication. In order to force SAML authen

Re: [openstack-dev] [qa] [Tempest - Stress Test] : some improvements / issues on the stress test framework

Hi Julien, please don't forget the [qa] tag - otherwise your lost in the ML noise ;) Ok thanks for the bug reports. I confirmed 1273245 and 1273254 but I am not totally sure with 1273186. Could you give some more details how the CLI interface will look like? Or simply propose a patch. It could

Re: [openstack-dev] [Climate] [Ceilometer] Integration

Hi Julien, 2014/1/27 Julien Danjou > Hi, > > I've created a blueprint for Climate support in Ceilometer: > > https://blueprints.launchpad.net/ceilometer/+spec/climate-support > > I've added a list of resources that I think should be metered. I'm not > sure about the other ones that I encoun

Re: [openstack-dev] [Neutron][IPv6] A pair of mode keywords

OK - any suggestions for the names of API attributes? The PDF[0] shared does not specify the names of the attributes, so I had two ideas for the names of the two new attributes being added to the Subnet resource: Either prefix them with "ipv6" * ipv6_ra_mode * ipv6_address_mode Or don't prefix

[openstack-dev] [oslo] log message translations

We have a blueprint open for separating translated log messages into different domains so the translation team can prioritize them differently (focusing on errors and warnings before debug messages, for example) [1]. Some concerns were raised related to the review [2], and I would like to address t

Re: [openstack-dev] [TripleO] State preserving upgrades working, next MVP selection?

Excerpts from Dan Prince's message of 2014-01-27 09:22:21 -0800: > > - Original Message - > > From: "Robert Collins" > > To: "OpenStack Development Mailing List" > > Sent: Sunday, January 26, 2014 3:30:22 PM > > Subject: [openstack-dev] [TripleO] State preserving upgrades working, >

Re: [openstack-dev] Proposed Logging Standards

What I'd like to find out now: 1) who's interested in this topic? Please include me. 2) who's interested in helping flesh out the guidelines for various log levels? Please include me. 3) who's interested in helping get these kinds of patches into various projects in OpenStack? 4) which project

Re: [openstack-dev] [TripleO] State preserving upgrades working, next MVP selection?

- Original Message - > From: "Robert Collins" > To: "OpenStack Development Mailing List" > Sent: Sunday, January 26, 2014 3:30:22 PM > Subject: [openstack-dev] [TripleO] State preserving upgrades working, next > MVP selection? > > So great news - we've now got state preserving upgrade

Re: [openstack-dev] [Solum] Proposed changes to solum-core

On 01/24/2014 05:32 PM, Adrian Otto wrote: Solum Core Reviewers, I propose the following changes to solum-core: +asalkeld +noorul -mordred Thanks very much to mordred for helping me to bootstrap the reviewer team. Please reply with your votes. +1 My pleasure - you guys seem like you're off

Re: [openstack-dev] [Neutron][IPv6] A pair of mode keywords

I vote address them (ipv6_). There's no guarantee of forward compatibility with a new protocol and this way it can't be confused with a (non-existant) selection method for IPv4, either. Also, future updates of other protocols would require a new attribute and break the API less. -Anthony >OK -

Re: [openstack-dev] [oslo] log message translations

On Mon, Jan 27, 2014 at 12:42:28PM -0500, Doug Hellmann wrote: > We have a blueprint open for separating translated log messages into > different domains so the translation team can prioritize them differently > (focusing on errors and warnings before debug messages, for example) [1]. > Feedback?

Re: [openstack-dev] [TripleO] State preserving upgrades working, next MVP selection?

- Original Message - > From: "Clint Byrum" > To: "openstack-dev" > Sent: Monday, January 27, 2014 12:48:23 PM > Subject: Re: [openstack-dev] [TripleO] State preserving upgrades working, > next MVP selection? > > Excerpts from Dan Prince's message of 2014-01-27 09:22:21 -0800: > >

Re: [openstack-dev] [oslo] log message translations

On Mon, Jan 27, 2014 at 12:58 PM, Daniel P. Berrange wrote: > On Mon, Jan 27, 2014 at 12:42:28PM -0500, Doug Hellmann wrote: > > We have a blueprint open for separating translated log messages into > > different domains so the translation team can prioritize them differently > > (focusing on error

[openstack-dev] Mistral + taskflow mini-meetup

Hi all, In order to encourage further discussion off IRC and more in public I'd like to share a etherpad that was worked on during a 'meetup' with some of the mistral folks and me. https://etherpad.openstack.org/p/taskflow-mistral-jan-meetup It was more of a (mini) in-person meetup but I thoug

Re: [openstack-dev] [Neutron] Representing PEM Format file as string

Thanks John. My initial approach is similar to Keystone's. This is mainly to unblock me from making progress on the driver. Nachi is doing the API part. I will discuss with him to explore other options. Can you send us the link to your review? Thanks, -Rajesh Mohan On Mon, Jan 27, 2014 at 6:

Re: [openstack-dev] [oslo] log message translations

+1 I've never understood this either personally. >From what I know most all (correct me if I am wrong) open source projects don't translate log messages; so it seems odd to be the special snowflake project/s. Do people find this type of translation useful? It'd be nice to know how many people re

Re: [openstack-dev] [Neutron] Representing PEM Format file as string

Hi Rajesh May I ask why we need single line representation of PEM format? For CLI, we will use file_name as same as nova keypair-add. We won't specify PEM on the URL. 2014-01-27 Rajesh Mohan : > Thanks John. > > My initial approach is similar to Keystone's. This is mainly to unblock me > from

Re: [openstack-dev] [oslo] log message translations

On Mon, Jan 27, 2014 at 01:12:19PM -0500, Doug Hellmann wrote: > On Mon, Jan 27, 2014 at 12:58 PM, Daniel P. Berrange > wrote: > > > On Mon, Jan 27, 2014 at 12:42:28PM -0500, Doug Hellmann wrote: > > > We have a blueprint open for separating translated log messages into > > > different domains so

Re: [openstack-dev] [Neutron] Representing PEM Format file as string

On Mon, 2014-01-27 at 10:49 -0800, Nachi Ueno wrote: > Hi Rajesh > > May I ask why we need single line representation of PEM format? > For CLI, we will use file_name as same as nova keypair-add. > We won't specify PEM on the URL. ++ -jay ___ OpenStac

Re: [openstack-dev] [Neutron][IPv6] A pair of mode keywords

+1 for the ones “ipv6_” prefix. On Jan 27, 2014, at 1:15 PM, Veiga, Anthony wrote: > I vote address them (ipv6_). There's no guarantee of forward > compatibility with a new protocol and this way it can't be confused with a > (non-existant) selection method for IPv4, either. Also, future u

[openstack-dev] [infra] Meeting Tuesday January 28th at 19:00 UTC

The OpenStack Infrastructure (Infra) team is hosting our weekly meeting tomorrow, Tuesday January 28th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is welcome to to add agenda items) Everyone interested in inf

Re: [openstack-dev] [oslo] log message translations

On Mon, Jan 27, 2014 at 1:51 PM, Daniel P. Berrange wrote: > On Mon, Jan 27, 2014 at 01:12:19PM -0500, Doug Hellmann wrote: > > On Mon, Jan 27, 2014 at 12:58 PM, Daniel P. Berrange < > berra...@redhat.com>wrote: > > > > > On Mon, Jan 27, 2014 at 12:42:28PM -0500, Doug Hellmann wrote: > > > > We ha

Re: [openstack-dev] [oslo] log message translations

Joshua Harlow wrote: >From what I know most all (correct me if I am wrong) open source projects >don't translate log messages; so it seems odd to be the special snowflake >project/s. >Do people find this type of translation useful? >It'd be nice to know how many people really do so the benefit/dr

Re: [openstack-dev] [oslo] log message translations

On Mon, 2014-01-27 at 19:06 +, CARVER, PAUL wrote: > Joshua Harlow wrote: > >From what I know most all (correct me if I am wrong) open source projects > >don't translate log messages; so it seems odd to be the special snowflake > >project/s. > > >Do people find this type of translation useful?

Re: [openstack-dev] [savanna] paramiko requirement of >= 1.9.0?

Currently we have paramiko >= 1.9.0 in both global-requirements and savanna: https://review.openstack.org/#/c/68088/ https://review.openstack.org/#/c/69045/ On Tue, Jan 21, 2014 at 3:41 PM, Sergey Lukjanov wrote: > Here is a change for global-requirements > https://review.openstack.org/#/c/6808

Re: [openstack-dev] [Neutron] Representing PEM Format file as string

Nachi, I did not know that we could give files names. Since we had String in the database, I assumed we need to give string as input. I guess, the neutron client will convert the file to string and then call the API. That should work. Thanks for the clarification. On Mon, Jan 27, 2014 at 10:4

[openstack-dev] Reviewday data download problem

A few days ago, a change I submitted to reviewday to generate JSON results for easy consumption by an application merged. I was hoping that this could be used with next-review to help me prioritize reviews. So I was expecting to now be able to go to the URL and get the .json file, like this: curl

[openstack-dev] [oslo] team meeting Friday 31 Jan 1400 UTC

The Oslo team has a few items we need to discuss, so I'm calling a meeting for this Friday, 31 Jan. Our normal slot is 1400 UTC Friday in #openstack-meeting. The agenda [1] includes 2 items (so far): 1. log translations (see the other thread started today) 2. parallelizing our tests If you have

Re: [openstack-dev] [Neutron] Representing PEM Format file as string

Hi Rajesh yes. Please take a looks nova keypair-add implementation https://github.com/openstack/python-novaclient/blob/e3d686f39ad9787a70894dff3db9352be6b3f0dd/novaclient/v1_1/shell.py#L2372 2014-01-27 Rajesh Mohan : > Nachi, > > I did not know that we could give files names. Since we had String

Re: [openstack-dev] [oslo] log message translations

Jay Pipes wrote: >Have you ever tried using Google Translate for anything more than very >simple phrases? >The results can be... well, interesting ;) And given the amount of >technical terms used in these messages, I doubt GT or any automated >translating service would provide a whole lot of valu

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV

Hi Irena, I agree on your first comment. see inline as well. thanks, Robert On 1/27/14 10:54 AM, "Irena Berezovsky" mailto:ire...@mellanox.com>> wrote: Hi Robert, all, My comments inline Regards, Irena From: Robert Li (baoli) [mailto:ba...@cisco.com] Sent: Monday, January 27, 2014 5:05 PM To

Re: [openstack-dev] Mistral + taskflow mini-meetup

Josh, thanks for sharing this with the community. Just a couple of words as an addition to that.. The driver for this conversation is that TaskFlow library and Mistral service in many ways do similar things: task processing combined somehow (flow or workflow). However, there’s a number of diffe

Re: [openstack-dev] Proposed Logging Standards

On Mon, 2014-01-27 at 08:07 -0500, Sean Dague wrote: > Back at the beginning of the cycle, I pushed for the idea of doing some > log harmonization, so that the OpenStack logs, across services, made > sense. I've pushed a proposed changes to Nova and Keystone over the past > couple of days. > > Thi

[openstack-dev] Neutron: Seeking suggestions about vendor service driver persisting info...

Hi, I'm working on a vendor driver for VPNaaS. The device I'm using has different 'id' requirements for some of the resources related to VPN. For example, the IPSec policy information can be identified by an ID up to 31 characters long, whereas with OpenStack the ID will be a 36 character UUID.

[openstack-dev] [nova][neutron] PCI pass-through SRIOV on Jan. 28th

Hi Folks, Check out 1 Agenda on Jan 28th, 2014. Please update if I have missed any thing. Let's finalize who's doing what tomorrow. I'm thinking to work on the nova SRIOV items, but the live migration may be a s

[openstack-dev] stevedore 0.14

I have just released a new version of stevedore, 0.14, which includes a change to stop checking version numbers of dependencies for plugins. This should eliminate one class of problems we've seen where we get conflicting requirements to install, and the libraries are compatible, but the way stevedo

Re: [openstack-dev] Proposed Logging Standards

On Mon, Jan 27, 2014 at 6:07 AM, Sean Dague wrote: > Back at the beginning of the cycle, I pushed for the idea of doing some > log harmonization, so that the OpenStack logs, across services, made > sense. I've pushed a proposed changes to Nova and Keystone over the past > couple of days. > > This

Re: [openstack-dev] [Solum] Proposed changes to solum-core

+1 On 1/27/14, 11:54 AM, "Monty Taylor" wrote: >On 01/24/2014 05:32 PM, Adrian Otto wrote: >> Solum Core Reviewers, >> >> I propose the following changes to solum-core: >> >> +asalkeld >> +noorul >> -mordred >> >> Thanks very much to mordred for helping me to bootstrap the reviewer >>team. Pleas

Re: [openstack-dev] [Solum] Proposed changes to solum-core

Solum Core Reviewers, Thanks everyone for your feedback. I have made the adjustments. Welcome to the core group Angus and Noorul. Thanks again Monty. Regards, Adrian On Jan 27, 2014, at 12:54 PM, Kurt Griffiths wrote: > +1 > > On 1/27/14, 11:54 AM, "Monty Taylor" wrote: > >> On 01/24/201

Re: [openstack-dev] [savanna] savannaclient v2 api

We should consider turning "mains" into a string instead of a list for v2. Hive and Pig Oozie actions use mains, and each may only specify a single

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV

Hi Robert, Please see inline From: Robert Li (baoli) [mailto:ba...@cisco.com] Sent: Monday, January 27, 2014 10:29 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV Hi Irena, I agree on your first comment. see

Re: [openstack-dev] Proposed Logging Standards

Sean and John, I would be happy to help out with this for Cinder. Let me know how I can help. Jay S. Bryant IBM Cinder Subject Matter Expert & Cinder Core Member Department 7YLA, Building 015-2, Office E125, Rochester, MN Telephone: (507) 253-4270, FAX (507) 253-6410 TIE Line: 553-4270

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV

On Mon, 2014-01-27 at 14:58 +, Robert Li (baoli) wrote: > Hi Folks, > > > In today's meeting, we discussed a scheduler issue for SRIOV. The > basic requirement is for coexistence of the following compute nodes in > a cloud: > -- SRIOV only compute nodes > -- non-SRIOV only compute

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV

Ok, this is something that's going to be added in ml2. I was looking at the bind_port() routine in mech_agent.py. The routine check_segment_for_agent() seems to be performing static check. So we are going to add something like check_vnic_type_for_agent(), I guess? Is the pairing of an agent with

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV

Hi, There are two possibilities for the hybrid compute nodes - In the first case, a compute node has two NICs, one SRIOV NIC & the other NIC for the VirtIO - In the 2nd case, Compute node has only one SRIOV NIC, where VFs are used for the VMs, either macvtap or direct assign

[openstack-dev] extending keystone identity

I'm looking to create a simple Identity driver that will look at usernames. A small number of specific users should be authenticated by looking at a hard-coded password in keystone.conf, while any other users should fall back to LDAP authentication. I based my original driver on what's found her

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV

On 27 January 2014 15:58, Robert Li (baoli) wrote: > Hi Folks, > > In today's meeting, we discussed a scheduler issue for SRIOV. The basic > requirement is for coexistence of the following compute nodes in a cloud: > -- SRIOV only compute nodes > -- non-SRIOV only compute nodes >

Re: [openstack-dev] MariaDB support

On Sat, Jan 25, 2014 at 5:32 AM, Tim Bell wrote: > > > We are reviewing options between MySQL and MariaDB. RHEL 7 beta seems to > have MariaDB as the default MySQL-like DB. > > > > Can someone summarise the status of the OpenStack in terms of > > > > -What MySQL-flavor is/are currently te

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV on Jan. 28th

Live migration for the first release is intended to be covered by macvtap, in my mind - direct mapped devices have limited support in hypervisors aiui. It seemed we had a working theory for that, which we test out and see if it's going to work. -- Ian. On 27 January 2014 21:38, Robert Li (baoli

Re: [openstack-dev] [Ceilometer] Issues with transformers

On 27/01/14 23:41, Julien Danjou wrote: On Mon, Jan 27 2014, Adrian Turjak wrote: I created a gauge metric that is updated via notifications, and a pollster. The data from both of those needs to be transformed in to a cumulative metric. The transformer object works as intended, but the issue i

Re: [openstack-dev] MariaDB support

check with the trove folks they might be testing percona. On Mon, Jan 27, 2014 at 2:34 PM, Michael Still wrote: > On Sat, Jan 25, 2014 at 5:32 AM, Tim Bell wrote: > >> >> >> We are reviewing options between MySQL and MariaDB. RHEL 7 beta seems to >> have MariaDB as the default MySQL-like DB. >

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV

On Mon, 2014-01-27 at 22:31 +0100, Ian Wells wrote: > In any case, as discussed in the meeting, this is an optimisation and > not something we have to solve in the initial release, because: > +1 for this. We should keep it as future enhancement effort. --jyh _

  1   2   >