Re: [openstack-dev] [glance] Remove `run_tests.sh` and `tools/*`

On Fri, Mar 04 2016, Flavio Percoco wrote: > Any objections? Something I'm missing? Good idea. :) -- Julien Danjou // Free Software hacker // https://julien.danjou.info signature.asc Description: PGP signature __ OpenStac

Re: [openstack-dev] [neutron] constrained tox targets

On 4 March 2016 at 11:15, Armando M. wrote: > > > On 4 March 2016 at 11:12, Ihar Hrachyshka wrote: > >> Armando M. wrote: >> >> >>> >>> On 4 March 2016 at 08:50, Ihar Hrachyshka wrote: >>> Hi all, >>> >>> currently we have both py27 and py27-constraints tox targets in neutron >>> repos. For so

Re: [openstack-dev] [telemetry][aodh] "aodh alarm list" vs "aodh alarm search"

On Fri, Mar 04 2016, liusheng wrote: > Hi folks, > Currently, we have supported "aodh alarm list" and "aodh alarm search" > commands > to query alarms. They both need mandatory "--type" parameter, and I want to > drop the limitation[1]. if we agree that, the "alarm list" will only used to > lis

Re: [openstack-dev] [nova] bug reports and stable branches: tags or series?

Matt Riedemann wrote: [...] The 'in-stable-liberty' tag is applied by infra when a stable branch patch is merged. I haven't actually been seeing this happening as automatically as before with the in-stable-kilo tag. I'm not sure if that's a bug in infra or if it's by design (or maybe it doesn't h

Re: [openstack-dev] [fuel] Newton PTL and CL elections

Dmitry Borodaenko wrote: Updated dates based on openstack/election events.yaml: PTL self-nomination: March 11-17 PTL election: March 18-24 CL self-nomination: March 25-31 CL election: April 1-7 Can we fit the component leads election into the same process (i.e. component lead candidates would s

Re: [openstack-dev] Reg: Configuration Management tool for Openstack.

Hi Dharma, You can start with https://github.com/openstack/openstack-ansible Quick start guide to go about it: http://docs.openstack.org/developer/openstack-ansible/developer-docs/quickstart-aio.html Regards, Yatin On Mon, Mar 7, 2016 at 12:46 PM, cool dharma06 wrote: > Hi all, > > i have th

Re: [openstack-dev] [kolla][vote] Proposing Alicja Kwasniewska for core reviewer

+1 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

I do not think that this is a bug in the plugin. Why are we not doing the changes in the base class (unless that is not possible). Having an extra read when a resources is created seems like a little of an overkill. I understand that it is what is done at the moment. I think that at the summit w

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

Right, it can't be done in the base right now because core plugins make DB changes after the base plugin has been called. These changes include the initial create processing of many of the extensions so we can't call the extend_dict functions before the data many of the registered hooks are lookin

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

"Wang, Shane" wrote on 03/05/2016 07:04:56 AM: > From: "Wang, Shane" > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 03/05/2016 07:05 AM > Subject: Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka > > Yes, sure, Markus, we are using https://eth

[openstack-dev] Tenant networks

Hi All, I am confused about tenant vlan networks. Is there a such a thing as 'Tenant vlan networks' ? I am aware of provider vlan networks ? How can a non admin tenant user create a vlan network ? __ OpenStack Development

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

Another issue that we have with the read at create is that the dictionary returned is not the same as the one returned when the is a get for the specific resource. The dictionary is also not in the same order. This is currently breaking our unit tests… By that is just another side issue From: K

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

But that's the whole point of doing the read after the create in the plugin. As long as you read after all db changes and call the dict extend function, it should be the same. As far as order goes, python doesn't guarantee order on dictionary keys. Or did I misinterpret what you meant by order? On

Re: [openstack-dev] [Fuel] Fuel 8 crashes when using Advanced Install

Hi Razvan, could you please provide cmdline which has been passed ? you can get it with simple `cat /proc/cmdline ` in second dracut tab On Sun, Mar 6, 2016 at 2:42 PM, Razvan Rosca wrote: > Hey, > > Tried this on 4 Dell machines, issue is present on all. Each server has 2 > SSDs in no RAID. >

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

There are a number of issues here: 1. The create returns additional values, for example the binding:vnic_type, whilst the get does not 2. We have some unit tests that we need to change (I guess), that check function parameters. An example for this is the network passed to a method. With t

[openstack-dev] openstack token issue CLI, error- openstack liberty

hi i am in process of learning and applying openstack. i am installing devstack ( in single machine mode) in my centos7 laptop. while running stack.sh command , install halts at this line. 2016-03-07 09:54:58.053 | ++ /home/vijay/devstack/lib/keystone:bootstrap_keystone:L651:

Re: [openstack-dev] [tripleo] CI jobs failures

On 03/06/2016 05:58 PM, James Slagle wrote: On Sat, Mar 5, 2016 at 11:15 AM, Emilien Macchi wrote: I'm kind of hijacking Dan's e-mail but I would like to propose some technical improvements to stop having so much CI failures. 1/ Stop creating swap files. We don't have SSD, this is IMHO a terr

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

On 7 March 2016 at 10:54, Gary Kotton wrote: > There are a number of issues here: > >1. The create returns additional values, for example the binding:vnic_type, >whilst the get does not > > This is probably a consequence of fixing the behaviour mismatch between create and get. > >1.

Re: [openstack-dev] [magnum-ui] Proposed Core addition, and removal notice

blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px #715FFA solid !important; padding-left:1ex !important; background-color:white !important; } +1 for Shu.  He has been contributing consistently to magnum-ui. Keep up the good work! Sent from Yahoo Mail for iPhone On S

Re: [openstack-dev] [Fuel] [Openstack] Instalation Problem:VBoxManage: error: Guest not running [ubuntu14.04]

Samer, did you make any progress? If not yet, I have couple of questions: - Did you download MOS image and VBox scripts from https://docs.fuel-infra.org/openstack/fuel/fuel-8.0/quickstart-guide.html#downloading-the-mirantis-openstack-image ? - Can you login to your just deployed master node? If

[openstack-dev] [Fuel][Fuel-web] Jenkins failing, tox -e py27 error

Hi All, I recently started exploring Fuel. Found a small error in documentation but when i am trying to push the fix, jenkins is throwing following errors: 2016-03-07 10:05:18.619 |

Re: [openstack-dev] [Nova] Live Migration post feature freeze update

> -Original Message- > From: Sean Dague [mailto:s...@dague.net] > Sent: 04 March 2016 20:09 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Nova] Live Migration post feature freeze > update > > On 03/04/2016 02:54 PM, Matt Riedemann wrote: > > > > > > On 3/4/2016

Re: [openstack-dev] Tenant networks

On 07/03/16 09:42, Gk Gk wrote: > Hi All, > > I am confused about tenant vlan networks. Is there a such a thing as > 'Tenant vlan networks' ? I am aware of provider vlan networks ? How > can a non admin tenant user create a vlan network ? A non-admin tenant can create a network, but cannot spe

Re: [openstack-dev] [Fuel][Fuel-web] Jenkins failing, tox -e py27 error

Hey Prameswar, It seems we're experiencing that issue on all our patches. For example, the same error blocks that patch from merge [1]. I think it's some OpenStack CI issue. Let's give a time. - Igor [1] https://review.openstack.org/#/c/287558/ On Mon, Mar 7, 2016 at 12:32 PM, Prameswar Lal w

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

Yeah, it sounds like maybe there is a bug in the extension processing for port bindings if the VNIC type isn't returned for a get. Does ML2 exhibit the same behavior? On Mar 7, 2016 02:08, "Salvatore Orlando" wrote: > > > On 7 March 2016 at 10:54, Gary Kotton wrote: > >> There are a number of is

Re: [openstack-dev] Tenant networks

So, there is nothing as a tenant vlan network ? On Mon, Mar 7, 2016 at 4:06 PM, Neil Jerram wrote: > On 07/03/16 09:42, Gk Gk wrote: > > Hi All, > > > > I am confused about tenant vlan networks. Is there a such a thing as > > 'Tenant vlan networks' ? I am aware of provider vlan networks ? H

Re: [openstack-dev] Tenant networks

That’s not at all what I said. Please reread my message more carefully. From: Gk Gk [mailto:ygk@gmail.com] Sent: 07 March 2016 11:17 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] Tenant networks So, there is nothing as a tenant vlan network ?

Re: [openstack-dev] [nova] How to fix the wrong usage of 'format' jsonschema keyword in server create API

On 03/07/2016 01:18 AM, Alex Xu wrote: > Hi, > > Due to this regression bug https://launchpad.net/bugs/1552888, found we > are using 'formart' jsonschema keyword in wrong way. The 'format' is not > only for string instance, but all the types. Can you given an example of the kinds of things that a

Re: [openstack-dev] Tenant networks

On 07/03/16 11:24, Neil Jerram wrote: > That’s not at all what I said. Please reread my message more carefully. Well, I see that I could have been clearer in my answer... > *From:*Gk Gk [mailto:ygk@gmail.com] > *Sent:* 07 March 2016 11:17 > *To:* OpenStack Development Mailing List (not for u

[openstack-dev] [Fuel] [QA] Major changes in fuel-qa

Hello, Recently system_test framework had changes [0] which incompatible previous test case design. Now it has separate packages for: - actions - contains classes with test actions - core - contains core functionality and decorators - test - contains base test and test cases - hel

Re: [openstack-dev] [tripleo] CI jobs failures

On 03/06/2016 11:58 AM, James Slagle wrote: > On Sat, Mar 5, 2016 at 11:15 AM, Emilien Macchi wrote: >> I'm kind of hijacking Dan's e-mail but I would like to propose some >> technical improvements to stop having so much CI failures. >> >> >> 1/ Stop creating swap files. We don't have SSD, this

Re: [openstack-dev] [telemetry][aodh] "aodh alarm list" vs "aodh alarm search"

On 07/03/2016 3:15 AM, Julien Danjou wrote: > On Fri, Mar 04 2016, liusheng wrote: > >> Hi folks, >> Currently, we have supported "aodh alarm list" and "aodh alarm search" >> commands >> to query alarms. They both need mandatory "--type" parameter, and I want to >> drop the limitation[1]. if we

[openstack-dev] [Solar] Weekly update

Hi, Here is weekly update from Solar team F2S: - mapped all fuel-library tasks to solar resources - removed resources from repo and generating them from installed fuel-library version - better UX of f2s usage - sucessfully deployed controller+compute+cinder scenario - working on running bvt a

Re: [openstack-dev] [tripleo] CI jobs failures

On Sat, 2016-03-05 at 11:15 -0500, Emilien Macchi wrote: > I'm kind of hijacking Dan's e-mail but I would like to propose some > technical improvements to stop having so much CI failures. > > > 1/ Stop creating swap files. We don't have SSD, this is IMHO a > terrible > mistake to swap on files be

Re: [openstack-dev] [telemetry][aodh] "aodh alarm list" vs "aodh alarm search"

On Mon, Mar 07 2016, gordon chung wrote: > shall we drop 'alarm search' nomenclature and use just 'alarm list' for > both queries (standard and complex). the concern i have right now is the > proposal is to add standard query support to 'alarm list' while complex > query support is in 'alarm se

[openstack-dev] [all][elections] Election Season, PTL and TC March/April 2016

PTL Election details: https://wiki.openstack.org/wiki/PTL_Elections_March_2016 TC Election details: https://wiki.openstack.org/wiki/TC_Elections_April_2016 Please read the stipulations and timelines for candidates and electorate contained in these wikipages. There will be an announcement emai

Re: [openstack-dev] [nova] How to fix the wrong usage of 'format' jsonschema keyword in server create API

2016-03-07 19:23 GMT+08:00 Sean Dague : > On 03/07/2016 01:18 AM, Alex Xu wrote: > > Hi, > > > > Due to this regression bug https://launchpad.net/bugs/1552888, found we > > are using 'formart' jsonschema keyword in wrong way. The 'format' is not > > only for string instance, but all the types. > >

[openstack-dev] [mistral] Cancelling team meeting

Hi, We are cancelling team meeting today since a number of team members are on holidays. Renat __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:un

Re: [openstack-dev] [nova] How to fix the wrong usage of 'format' jsonschema keyword in server create API

On 03/07/2016 08:05 AM, Alex Xu wrote: 2016-03-07 19:23 GMT+08:00 Sean Dague mailto:s...@dague.net>>: On 03/07/2016 01:18 AM, Alex Xu wrote: > Hi, > > Due to this regression bughttps://launchpad.net/bugs/1552888, found we > are using 'formart' jsonschema keyword in wrong way.

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

Hongbin, I think the offer to support different OS options is a perfect example both of what we want and what we don't want. We definitely want to allow for someone like yourself to maintain templates for whatever OS they want and to have that option be easily integrated in to a Magnum deployment.

Re: [openstack-dev] [oslo] Common RPC Message Trace Mechanism

Hi, The 'trace' boolean offered by the AMQP 1.0 driver exposes a debug feature that is provided by the Proton library. This is specific to the Proton library - I'm not sure kombu/zmq/etc offer a similar feature. As Xuanzhou points out, this debug tool merely prints to stdout a summary of each AM

Re: [openstack-dev] [fuel][plugins] Should we maintain example plugins?

> and really lowering barriers for people who just begin create plugins. Nonsense. First, people usually create them via running `fpb --create plugin-name` that generates plugin boilerplate. And that boilerplate won't contain that changes. Second, if people ain't smart enough to change few lines

Re: [openstack-dev] [sahara]FFE Request for resume EDP job

For some reason the link below is wrong for me, it goes to a different review. Here is a good one (I hope!): https://review.openstack.org/#/c/285839/ Trev On Mon, 2016-03-07 at 14:28 +0800, lu jander wrote: > Hi folks, > > I would like to request a FFE for the feature “Resume EDP job”: > >

Re: [openstack-dev] Reg: Configuration Management tool for Openstack.

On 2016-03-07 12:46:45 +0530 (+0530), cool dharma06 wrote: [...] > 2. And also i checked the Github repository for openstack-puppet, i think > its not active. [...] The "puppet-openstack" composition layer module was deprecated in Juno, but their other modules are active. They have a page here wit

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

On 7 March 2016 at 01:02, Gary Kotton wrote: > I do not think that this is a bug in the plugin. Why are we not doing the > changes in the base class (unless that is not possible). Having an extra > read when a resources is created seems like a little of an overkill. I > understand that it is what

Re: [openstack-dev] [fuel][plugins] Should we maintain example plugins?

What about maintaining a dummy plugin (eg running only one or two very simple tasks) as a standalone project for the purpose of QA? IMO it would make more sense than having those example plugins in the fuel-plugins project... Regards, Simon On Mon, Mar 7, 2016 at 2:49 PM, Igor Kalnitsky wrote: >

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

There are a couple of API-WG proposed guidelines ready for review by interested parties: Header non proliferation: https://review.openstack.org/#/c/280381/ Client interaction guideline for microversions: https://review.openstack.org/#/c/243414/ Please have a look at leave your

[openstack-dev] [salt] Team meeting this Tuesday

Hi Saltstackers, A kind reminder for this week's #openstack-salt meeting. More on the agenda [1]. [1]. https://wiki.openstack.org/wiki/Meetings/openstack-salt Regards, Jay Clark Sr. OpenStack Deployment Engineer E: jason.t.cl...@hpe.com H: 919.341.4670 M: 919.345.11

Re: [openstack-dev] [tripleo] Contributing to TripleO is challenging

While I agree with some (not all) of the sentiment below I'm not sure I want to spend the time debating this rather broad set of topics in this email thread. I'm not sure we'd actually ever see the end of it if we did. Nor can the upstream TripleO team control all the forces at play here. So rathe

Re: [openstack-dev] [openstack-ansible][security] Security hardening backport to Liberty desirable?

On 03/05/2016 06:40 AM, Jesse Pretorius wrote: > Liberty is a stable branch and the Mitaka release is just around the corner. > I think it's a bit late in the game to add it. Consider, also, that deployers > can easily consume the role with their own playbook to execute it if they > would like t

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

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

Re: [openstack-dev] [Fuel][Fuel-web] Jenkins failing, tox -e py27 error

On 2016-03-07 16:02:40 +0530 (+0530), Prameswar Lal wrote: > I recently started exploring Fuel. Found a small error in documentation but > when i am trying to push the fix, jenkins is throwing following errors: [...] > | Creating role openstack_citest with password > openstack_citest2016-03-07 10:0

Re: [openstack-dev] [sahara]FFE Request for resume EDP job

My 2 cents, I agree that it is low risk -- the impl for resume is analogous/parallel to the impl for suspend. And, it makes little sense to me to include suspend without resume. In my mind, these two operations are halves of the same feature, and since it is already partially implemented and appr

Re: [openstack-dev] [Fuel][Fuel-web] Jenkins failing, tox -e py27 error

Hey Jeremy, I got it and I'm working on patch [1] that must solve it. I simply stop doing postre setup since it seems is already setup. [1] https://review.openstack.org/#/c/289278/ On Mon, Mar 7, 2016 at 4:38 PM, Jeremy Stanley wrote: > On 2016-03-07 16:02:40 +0530 (+0530), Prameswar Lal wrote:

[openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

Hi folks, It was never really discussed if we would back-port upgrades to liberty. This came up during an irc conversation Friday [1], and a vote was requested. Tthe facts of the discussion distilled are: * We never agreed as a group to do back-port of upgrade during our back-port discu

[openstack-dev] [nova] Migration shared storage negotiation

Timofey has posted a patch which aims to improve shared storage negotiation a little: https://review.openstack.org/#/c/286745/ I've been thinking for some time about going bigger. It occurs to me that the destination node has enough context to know what should be present. I think it would be cl

Re: [openstack-dev] [puppet] proposal to create puppet-neutron-core and add Sergey Kolekonov

I've proceeded to the change. We created puppet-neutron core and added Sergey Kolekonov part of this group. Congrats Sergey! On 03/04/2016 10:40 AM, Emilien Macchi wrote: > Hi, > > To scale-up our review process, we created pupept-keystone-core and it > worked pretty well until now. > > I propo

Re: [openstack-dev] [tripleo] CI jobs failures

ce the number of test envs per host from 4 down to 3, wiping 25% of our capacity [1] - http://logs.openstack.org/85/289085/2/check-tripleo/gate-tripleo-ci-f22-nonha/6fda33c/ [2] - http://goodsquishy.com/downloads/20160307/swap.png [3] - 22:09:03 21678 INFO [-] Master cache miss for image b6a9

Re: [openstack-dev] [fuel][plugins] Should we maintain example plugins?

Yet another example [1] of why a dummy/example plugin should be integrated in the Fuel CI process: the current version of Fuel is broken for (almost) all plugins since a week at least and no one noticed. Regards, Simon [1] https://bugs.launchpad.net/fuel/+bug/1554095 On Mon, Mar 7, 2016 at 3:16 P

Re: [openstack-dev] [Fuel] [Openstack] Instalation Problem:VBoxManage: error: Guest not running [ubuntu14.04]

Hello, YES, I just find the solution, the Virtualization Option on the BIOS was Disable by default, I turn it on and It's working now. Now my problem are the resources, But that's another story. JEJEJE I'm not sure if I need RAM or HD. Thanks for your help. - Mail original - De:

Re: [openstack-dev] [kolla][vote] Proposing Alicja Kwasniewska for core reviewer

+1 On Mon, Mar 7, 2016 at 3:57 AM, Michal Rostecki wrote: > +1 > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://list

Re: [openstack-dev] [telemetry][aodh] "aodh alarm list" vs "aodh alarm search"

On 07/03/2016 8:05 AM, Julien Danjou wrote: > On Mon, Mar 07 2016, gordon chung wrote: > >> shall we drop 'alarm search' nomenclature and use just 'alarm list' for >> both queries (standard and complex). the concern i have right now is the >> proposal is to add standard query support to 'alarm li

Re: [openstack-dev] [cinder] Proposal: changes to our current testing process

On 03/06/2016 09:35 PM, John Griffith wrote: > On Sat, Mar 5, 2016 at 4:27 PM, Jay S. Bryant > wrote: > >> Ivan, >> >> I agree that our testing needs improvement. Thanks for starting this >> thread. >> >> With regards to adding a hacking check for tests that run too long ... are >> you thinking t

Re: [openstack-dev] [kolla][vote] Proposing Alicja Kwasniewska for core reviewer

+1 Keep up the great reviews and patches! Sam Yaple On Mon, Mar 7, 2016 at 3:41 PM, Jeff Peeler wrote: > +1 > > On Mon, Mar 7, 2016 at 3:57 AM, Michal Rostecki > wrote: > > +1 > > > > > > > __ > > OpenStack Development Mai

Re: [openstack-dev] [Heat] Dealing with nonexistent resources during resource-list / stack-delete

On 04/03/16 04:35, Johannes Grassler wrote: Hello, I am currently looking into https://bugs.launchpad.net/heat/+bug/1442121 and not quite sure how to tackle it, since the problematic code is used for lots of things[0]: the root cause of the problem are API clients in resource plugins that do not

Re: [openstack-dev] [Fuel] [Openstack] Instalation Problem:VBoxManage: error: Guest not running [ubuntu14.04]

Hello, that definitely about HDD. Create disk with at least 50Gb + On Mon, Mar 7, 2016 at 5:32 PM, Samer Machara < samer.mach...@telecom-sudparis.eu> wrote: > Hello, >YES, I just find the solution, the Virtualization Option on the BIOS > was Disable by default, I turn it on and It's working n

Re: [openstack-dev] [Fuel][Fuel-web] Jenkins failing, tox -e py27 error

On 2016-03-07 16:50:00 +0200 (+0200), Igor Kalnitsky wrote: > I got it and I'm working on patch [1] that must solve it. I simply > stop doing postre setup since it seems is already setup. [...] Great! I'd still like to figure out why the job suddenly started assuming the role was missing on the ne

Re: [openstack-dev] [cinder] Proposal: changes to our current testing process

On 7 March 2016 at 23:45, Eric Harney wrote: > > > I'm not really sure that writing a "hacking" check for this is a > worthwhile investment. (It's not a hacking check really, but something > more like what you're describing, but that's beside the point.) > > We should just be looking for large,

Re: [openstack-dev] [OpenStack-docs] Fwd: [Neutron][LBaaS][Octavia][Docs] Need experienced contributor documentation best-practices and how-tos

Snipping a lot, because I'm particularly interested in one comment... > I agree that many developers (especially developers of those groups new to > the big tent) seem to think that they need to be on the top level > docs.openstack.org, without necessarily understanding that > docs.openstack.org/

Re: [openstack-dev] [nova][cinder] Limits on volume read throughput?

Just a heads-up that the 3.10 kernel in CentOS/RHEL is *not* a stock 3.10 kernel. It has had many things backported from later kernels, though they may not have backported the specific improvements you're looking for. I think CentOS is using qemu 2.3, which is pretty new. Not sure how new the

[openstack-dev] The stable:follows-policy tag is official, projects need to start applying for it

The stable:follows-policy tag is now official in the governance repo [1]. Projects that follow the stable branch policy [2] should start applying for that tag. Note that the tag may be used to determine when a projects stable branches go end of life, so it's important to have this information,

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

On Mon, Mar 7, 2016 at 3:03 PM, Steven Dake (stdake) wrote: > Hi folks, > > It was never really discussed if we would back-port upgrades to liberty. > This came up during an irc conversation Friday [1], and a vote was > requested. Tthe facts of the discussion distilled are: > >- We never ag

Re: [openstack-dev] [cinder] Proposal: changes to our current testing process

On 3/7/16, 10:45 AM, "Eric Harney" wrote: >On 03/06/2016 09:35 PM, John Griffith wrote: >> On Sat, Mar 5, 2016 at 4:27 PM, Jay S. Bryant wrote: >> >>> Ivan, >>> >>> I agree that our testing needs improvement. Thanks for starting this >>> thread. >>> >>> With regards to adding a hacking c

Re: [openstack-dev] [nova] Migration shared storage negotiation

On 03/07/2016 09:23 AM, Matthew Booth wrote: Timofey has posted a patch which aims to improve shared storage negotiation a little: https://review.openstack.org/#/c/286745/ I've been thinking for some time about going bigger. It occurs to me that the destination node has enough context to know w

Re: [openstack-dev] [OpenStack-docs] Fwd: [Neutron][LBaaS][Octavia][Docs] Need experienced contributor documentation best-practices and how-tos

On 07/03/2016 16:00, Matt Kassawara wrote: > Snipping a lot, because I'm particularly interested in one comment... > > > I agree that many developers (especially developers of those groups > new to the big tent) seem to think that they need to be on the top > level docs.openstack.org

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

Upgrades are required, true, but not necessarily automatic ones. People still can rebuild and redeploy containers using normal deploy. It will be downtime causing and less optimal, but possible. Also with backport of named volumes it won't be data-destroying. It will cause total downtime of APIs, b

Re: [openstack-dev] [nova] How to fix the wrong usage of 'format' jsonschema keyword in server create API

Hi Alex, Thanks for pointing this up. 2016-03-06 22:18 GMT-08:00 Alex Xu : > > Due to this regression bug https://launchpad.net/bugs/1552888, found we are > using 'formart' jsonschema keyword in wrong way. The 'format' is not only > for string instance, but all the types. > > So checking the serv

Re: [openstack-dev] [nova] Do we need a microversion to return a 501 from GET os-virtual-interfaces?

2016-03-06 15:41 GMT-08:00 Jay Pipes : > On 03/06/2016 02:21 PM, Matt Riedemann wrote: >> >> Thanks, good point. I think 400 would be best here. And according to our >> handy-dandy docs [1] it should be OK to do this without a microversion. > > > Yup, 400 is correct and yes, you should not need a n

[openstack-dev] [Ceilometer] Doubt about data recollection

Hello, Istarted working with OpenStack's ceilometer recently and I have some questions that I can not resolve with the documentation I have found. I would like to have the telemetry of a node inside the node itself (for example, a virtual machine that resides in that node and processes the local

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

From: Corey O'Brien [mailto:coreypobr...@gmail.com] Sent: March-07-16 8:11 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro Hongbin, I think the offer to support different OS options is a

[openstack-dev] [nova] bugs team meeting: March 8th 2016 1800 UTC

I'd like to remind you that tomorrow is the nova-bugs-team IRC meeting at 18:00 UTC [1]. If you want to contribute to the nova bugs area feel free to join. I prepared a list of potentially stale bugs [2] which need a cleanup/check by a human and I had the hope that some of you would pick 2-3 of tha

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

This is a messy topic. I feel there's been some miscommunication and confusion on the issue which hopefully I can sum up. As far as I remember it, Sam is correct, we did always plan to do Liberty upgrades. However, over the course of time post Tokyo these plans didn't really materialise, at wh

Re: [openstack-dev] [cinder] Proposal: changes to our current testing process

On Mon, Mar 7, 2016 at 8:57 AM, Knight, Clinton wrote: > > > On 3/7/16, 10:45 AM, "Eric Harney" wrote: > > >On 03/06/2016 09:35 PM, John Griffith wrote: > >> On Sat, Mar 5, 2016 at 4:27 PM, Jay S. Bryant > >> >>> wrote: > >> > >>> Ivan, > >>> > >>> I agree that our testing needs improvement. Th

Re: [openstack-dev] [cinder] Proposal: changes to our current testing process

On 2016-03-07 23:54:49 +0800 (+0800), Duncan Thomas wrote: > Complexity can be tricky to spot by hand, and expecting reviewers to get it > right all of the time is not a reasonable expectation. > > My ideal would be something that processes the commit and the jenkins logs, > extracts the timing in

Re: [openstack-dev] [sahara]FFE Request for resume EDP job

+1 to Trevor's $0.02. Seems like low risk to break any existing functionality and it's a good feature that really makes sense. On Mon, Mar 7, 2016 at 9:42 AM, Trevor McKay wrote: > My 2 cents, I agree that it is low risk -- the impl for resume is > analogous/parallel to the impl for suspend. An

Re: [openstack-dev] [tripleo] CI jobs failures

RAM on each env and accept we loose 25 of our capacity, maybe it doesn't matter, if our success rate goes up then we'd be running less rechecks anyways. The downside is that we'd probably hit less timing errors (assuming the tight resources is whats showing them up), I say downside

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

On 3/7/16, 10:16 AM, "Paul Bourke" wrote: >This is a messy topic. I feel there's been some miscommunication and >confusion on the issue which hopefully I can sum up. > >As far as I remember it, Sam is correct, we did always plan to do >Liberty upgrades. However, over the course of time post Tok

Re: [openstack-dev] [fuel] Newton PTL and CL elections

On Mon, Mar 07, 2016 at 09:37:57AM +0100, Thierry Carrez wrote: > Dmitry Borodaenko wrote: > >Updated dates based on openstack/election events.yaml: > > > >PTL self-nomination: March 11-17 > >PTL election: March 18-24 > >CL self-nomination: March 25-31 > >CL election: April 1-7 > > > >Can we fit th

Re: [openstack-dev] [fuel] Newton PTL and CL elections

On 2016-03-07 09:49:02 -0800 (-0800), Dmitry Borodaenko wrote: > Then that's what we will do, thanks. Also, our official electorate roll generation aggregates potential voter pools on a per-team basis according to definitions in openstack/governance, so may not be fine-grained enough if you intend

Re: [openstack-dev] [tripleo] CI jobs failures

On 7 March 2016 at 12:11, John Trowbridge wrote: > > > On 03/06/2016 11:58 AM, James Slagle wrote: >> On Sat, Mar 5, 2016 at 11:15 AM, Emilien Macchi wrote: >>> I'm kind of hijacking Dan's e-mail but I would like to propose some >>> technical improvements to stop having so much CI failures. >>> >

Re: [openstack-dev] [tripleo] CI jobs failures

On 03/07/2016 12:00 PM, Derek Higgins wrote: > On 7 March 2016 at 12:11, John Trowbridge wrote: >> >> >> On 03/06/2016 11:58 AM, James Slagle wrote: >>> On Sat, Mar 5, 2016 at 11:15 AM, Emilien Macchi wrote: I'm kind of hijacking Dan's e-mail but I would like to propose some technical i

[openstack-dev] [nova][ceilometer] unable to see compute.node.cpu.* metrics in ceilometer

Hi I enabled ComputeDriverCPUMonitor in nova.conf on one of the compute nodes, restarted nova-compute, ceilometer-agent-compute on the compute node and ceilometer-collector, ceilometer-api, ceilometer-agent-central, ceilometer-agent-notification on the controller node. However, I cannot see the cp

Re: [openstack-dev] [tripleo] CI jobs failures

x27;m not too concerned about the absolute minimum memory use case. Nobody deploying OpenStack in the real world is doing so on 4 GB nodes. I doubt 99% of them are doing so on less than 32 GB nodes. Until we have composable services, I don't know that we can support the 4 GB use case anymore.

[openstack-dev] [nova][pci] What is the point of the ALLOCATED vs. CLAIMED device status?

Subject says it all. I've been trying to fix this bug: https://bugs.launchpad.net/nova/+bug/1549984 and just shake my head every time I look at the PCI handling code in nova/pci/manager.py and nova/pci/stats.py. Why do we have a CLAIMED state as well as an ALLOCATED state? Best, -jay _

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready?

Hi Sam, So if you have some 3rd party hardware you only need to change the database (your steps 1-5) since the 3rd party hardware will just keep load balancing… Now for Kevin’s case with the namespace driver: You would need a 6th step to reschedule the loadbalancers with the V2 namespace driver

Re: [openstack-dev] [sahara]FFE Request for resume EDP job

FFE granted. This feature seems to be low risk and part of already merged feature. Thanks. On Mon, Mar 7, 2016 at 9:34 AM, Chad Roberts wrote: > +1 to Trevor's $0.02. Seems like low risk to break any existing > functionality and it's a good feature that really makes sense. > > On Mon, Mar 7, 2

Re: [openstack-dev] [puppet] proposal to create puppet-neutron-core and add Sergey Kolekonov

Thanks everyone! I will do my best to further improve puppet-neutron and other modules On Mon, Mar 7, 2016 at 6:23 PM, Emilien Macchi wrote: > I've proceeded to the change. > We created puppet-neutron core and added Sergey Kolekonov part of this > group. > > Congrats Sergey! > > On 03/04/2016 10

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready?

As far as I recall, you can specify the VIP in creating the LB so you will end up with same IPs. -Original Message- From: Eichberger, German [mailto:german.eichber...@hpe.com] Sent: Monday, March 07, 2016 8:30 PM To: OpenStack Development Mailing List (not for usage questions) Subject: R

Re: [openstack-dev] [nova] Do we need a microversion to return a 501 from GET os-virtual-interfaces?

Hi! I did not find any usage "virtual_interfaces" with try...except block, so we can easily change error code without new microversion. I'm +1 for proper code. On Mon, Mar 7, 2016 at 6:32 PM, Ken'ichi Ohmichi wrote: > 2016-03-06 15:41 GMT-08:00 Jay Pipes : > > On 03/06/2016 02:21 PM, Matt Riede

Re: [openstack-dev] [Fuel] [Openstack] Instalation Problem:VBoxManage: error: Guest not running [ubuntu14.04]

Guys, Samer has shown error messages... two lines: *VM "fuel-master" has been successfully started.* *VBoxManage: error: Guest not running* which exactly means that first command "VBoxManage startvm" has successfully executed but next one "VBoxManage " failed due to error. Which means the pr

  1   2   >