Re: [openstack-dev] [ironic] Midcycle summary part 1/6

On Feb 16, 2016 11:32 PM, "Jim Rollenhagen" wrote: > > Hi all, > > As our midcycle is virtual and split into 6 "sessions" for the sake of > timezones, we'll be sending a brief summary of each session so that > folks can catch up before the next one. All of this info should be on > the etherpad as

[openstack-dev] [neutron] Backup port info to restore the flow rules

Hello, If we restart OvS/ovs-agent when one or more of Neutron, MySQL and RabbitMQ is not available, the flow rules in OvS will be gone. If Neutron/MySQL/RabbitMQ doesn't become available in time, the VMs will lose their network connections. It's not easy for an operations engineer to manually res

Re: [openstack-dev] [neutron][dnsmasq]DNS redirection by dnsmasq

hi Carl. Thanks for your reply. DNS redirection is our customer's needs. Customer has their own CDN. They want to save traffic in CDN so that they can cost less money. So they let us hijack some domain names. We used dnsmasq "--cname" option to satisfy their needs. So I think that maybe we ca

Re: [openstack-dev] [ironic] Midcycle summary part 1/6

Jim Rollenhagen writes: > As a note, the asterisk setup that Infra provided was *fantastic*, and > the virtual-ness of this midcycle is going better than I ever expected. > Thanks again to the infra team for all that you do for us. <3 That's great to hear! I'm looking forward to hearing what wo

Re: [openstack-dev] [nova] A prototype implementation towards the "shared state scheduler"

To better illustrate the differences between shared-state, resource-provider and legacy scheduler, I've drew 3 simplified pictures [1] in emphasizing the location of resource view, the location of claim and resource consumption, and the resource update/refresh pattern in three kinds of scheduler

[openstack-dev] [ironic] Midcycle summary part 2/6

Hi all, As our midcycle is virtual and split into 6 "sessions" for the sake of timezones, we'll be sending a brief summary of each session so that folks can catch up before the next one. All of this info should be on the etherpad as well. Session 2/6 was February 17, -0400 UTC. * We briefly

Re: [openstack-dev] [Congress] Nominating Masahito for core

+1 Best Regards, Anusha On 17 February 2016 at 00:59, Peter Balland wrote: > +1 > > From: Tim Hinrichs > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Date: Tuesday, February 16, 2016 at 11:15 AM > To: "OpenStack Development M

Re: [openstack-dev] [qa] deprecating Tempest stress framework

+1 Sounds good to separate those to different repo. Regards Ghanshyam Mann On Wed, Feb 17, 2016 at 4:55 AM, Matthew Treinish wrote: > On Fri, Feb 12, 2016 at 10:21:53AM +0100, Koderer, Marc wrote: >> I know that there are folks around that are using it. >> +1 to move it to a separate repo. > >

[openstack-dev] [ironic] Midcycle summary part 1/6

Hi all, As our midcycle is virtual and split into 6 "sessions" for the sake of timezones, we'll be sending a brief summary of each session so that folks can catch up before the next one. All of this info should be on the etherpad as well. Session 1/6 was February 16, 1500-2000 UTC. * We talked a

Re: [openstack-dev] [puppet] Push Mitaka beta tag

On 02/16/2016 05:09 PM, Hunter Haugen wrote: > > > > > -Hunter > > On Tue, Feb 16, 2016 at 11:44 AM, David Moreau Simard > wrote: > > On Tue, Feb 16, 2016 at 2:18 PM, Hunter Haugen > mailto:hun...@puppetlabs.com>> wrote: > > The forge does verify that ve

Re: [openstack-dev] [nova][glance][barbican][kite][requirements] pycrypto vs pycryptodome

I suggest: - pin anything that moves - start being strict ourselves to prepare for moving - work with paramiko to help them move Sadly Python doesn't have either-or dependencies as yet, so we're going to be in the position of having to override pip for some time during the migration process. -

[openstack-dev] [mistral] More attention to PostgreSQL

Hi, We have more and more customers that want to run Mistral on top of PostgreSQL database (instead of MySQL). I also know that PostgreSQL is important for some of our active contributors. Can we add more attention to PostgreSQL? For example, add more gates (like gate-rally-dsvm-mistral-task an

Re: [openstack-dev] [puppet] Push Mitaka beta tag

-Hunter On Tue, Feb 16, 2016 at 11:44 AM, David Moreau Simard wrote: > On Tue, Feb 16, 2016 at 2:18 PM, Hunter Haugen > wrote: > > The forge does verify that versions match semver 1.0.0, which states "a > > pre-release version number MAY be denoted by appending an arbitrary > string > > immedia

Re: [openstack-dev] [infra][neutron] publish and update Gerrit dashboard link automatically

Could this be done by creating a project dashboard [1]? I think the one thing that prevents using such a dashboard is that your script generates a dashboard that crosses multiple projects. So, we'd be stuck with multiple dashboards, one per project. The nature of your script is to create a new U

Re: [openstack-dev] [neutron][dnsmasq]DNS redirection by dnsmasq

What would be the motivation for this? Could you give some examples of what you'd use it for? Keep in mind that --cname is limited to target names known by dnsmasq itself. Carl On Mon, Feb 15, 2016 at 2:13 AM, Zhi Chang wrote: > hi, guys. > Most of us know about DNS redirection. I think t

Re: [openstack-dev] [nova][glance][barbican][kite][requirements] pycrypto vs pycryptodome

I'm getting these nova tox errors now (from pip-missing-reqs): Missing requirements: nova/crypto.py:29 dist=pycrypto module=Crypto.PublicKey.RSA I think requirements.txt should now include pycrypto ? Or am I missing something. Thanks, /ludovic -Original Message- From: Davanum Srinivas

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

On Mon, Feb 15, 2016 at 9:26 AM, Pavel Bondar wrote: > Your idea sounds workable to me. However I think a simpler way exists. I'll be happy to review your migration for Mitaka which should be totally out-of-band and leave both implementations intact. As for the details of the switch-over in Newt

Re: [openstack-dev] [mistral] Mistral team meeting minutes

I will come :) Renat Akhmerov @ Mirantis Inc. > On 15 Feb 2016, at 08:42, Nikolay Makhotkin wrote: > > Thank you for attending the meeting today! > > Next meeting is scheduled on 22 Feb. It is non-working day in Russia so > Renat, Anastasia and I very likely won't come to the meeting. >

[openstack-dev] [release][glance] glance_store 0.11.0 release (mitaka)

We are thrilled to announce the release of: glance_store 0.11.0: OpenStack Image Service Store Library This release is part of the mitaka release series. With source available at: http://git.openstack.org/cgit/openstack/glance_store With package available at: https://pypi.python.org/p

Re: [openstack-dev] [QA][Tempest]Run only multinode tests in multinode jobs

On Tue, Feb 16, 2016 at 2:52 PM, Matthew Treinish wrote: > On Tue, Feb 16, 2016 at 10:07:19AM +0100, Jordan Pittier wrote: >> Hi list, >> I understood we need to limit the number of tests and jobs that are run for >> each Tempest patch because our resources are not unlimited. >> >> In Tempest, we

[openstack-dev] [TripleO]: CI outage yesterday/today

Just a quick update about the CI outage today and yesterday. Turns out our jobs weren't running due to a bad Keystone URL (it was pointing to localhost:5000 instead of our public SSL endpoint). We've now fixed that issue and I'm told that as soon as Infra restarts nodepool (they cache the keystone

Re: [openstack-dev] [qa] Tempest removal of tempest.api.compute.test_authorization

On Tue, Feb 09, 2016 at 07:41:18PM -0500, Sean Dague wrote: > As proposed in this patch - https://review.openstack.org/#/c/271467/ > > These tests do some manipulation of the request URI to attempt to > request Nova resources owned by a different project_id. However they all > basically test the s

Re: [openstack-dev] [all] [tc] unconstrained growth, why?

Excerpts from Chris Dent's message of 2016-02-16 19:47:11 +: > On Tue, 16 Feb 2016, Doug Hellmann wrote: > > [lots of reassonable stuff snipped] > > > I think we should be looking for > > ways to say "yes" to new projects, rather than "no." > > I think the opposite is worth thinking about. M

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

Excerpts from Edward Leafe's message of 2016-02-16 13:46:50 -0600: > On Feb 16, 2016, at 1:30 PM, Doug Hellmann wrote: > > > So I think the project team is doing everything we've asked. We > > changed our policies around new projects to emphasize the social > > aspects of projects, and community

[openstack-dev] [QA] End of the openstack-qa mailing list

Hi everyone, I just wanted to send an announcement to the ML that we've officially shutdown the openstack-qa ML. We had basically stopped using this completely 2-3 years ago but kept the list alive because of the periodic job results needing a place to be sent. However, with the introduction of o

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On Tue, Feb 16, 2016 at 1:16 PM, Brant Knudson wrote: > This is pretty much the same as your example of specifying a different > version for the nova API on different requests (except they have a lot more > than just 2 and 3). We also keep adding routes to v3 each release, so what > operations ar

Re: [openstack-dev] [kolla] Decision of how to manage stable/liberty from Kolla Midcycle

Comments inline From: Sam Yaple mailto:sam...@yaple.net>> Reply-To: "s...@yaple.net" mailto:s...@yaple.net>>, "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, February 16, 2016 at 11:42 AM To: "OpenS

Re: [openstack-dev] [qa] deprecating Tempest stress framework

On Fri, Feb 12, 2016 at 10:21:53AM +0100, Koderer, Marc wrote: > I know that there are folks around that are using it. > +1 to move it to a separate repo. That sounds fine to me, let's mark the stress runner as deprecated and before we remove it someone can spin up a separate repo that owns the st

Re: [openstack-dev] [QA][Tempest]Run only multinode tests in multinode jobs

On Tue, Feb 16, 2016 at 10:07:19AM +0100, Jordan Pittier wrote: > Hi list, > I understood we need to limit the number of tests and jobs that are run for > each Tempest patch because our resources are not unlimited. > > In Tempest, we have 5 multinode experimental jobs: > > experimental-tempest-ds

[openstack-dev] [tacker][networking-sfc] Tacker VNFFG - SFC integration updates

Hi folks, Based on the recent discussions in [1] & [2] we are proposing to rearrange our tasks related to Tacker's VNFFG component integrating with the lower level SFC APIs. We now plan to integrate with networking-sfc APIs first. Our original plan, or rather the sequence of tasks, were, 1) Tack

Re: [openstack-dev] [all] [tc] unconstrained growth, why?

On Tue, 16 Feb 2016, Doug Hellmann wrote: [lots of reassonable stuff snipped] I think we should be looking for ways to say "yes" to new projects, rather than "no." I think the opposite is worth thinking about. Maybe we should be defaulting to "no". Not because candidates are bad, but because

[openstack-dev] [neutron] [networking-sfc] networking-sfc project IRC meeting

Hi, I am in a container conference and won't be able to chair this week's IRC meeting. Paul Carver has volunteered to chair this week's meeting. Thanks Paul! If there are any topics you would like to discuss, you can post them on the meeting wiki page https://wiki.openstack.org/wiki/Meetings/Se

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

On Feb 16, 2016, at 1:30 PM, Doug Hellmann wrote: > So I think the project team is doing everything we've asked. We > changed our policies around new projects to emphasize the social > aspects of projects, and community interactions. Telling a bunch > of folks that they "are not OpenStack" even

Re: [openstack-dev] [puppet] Push Mitaka beta tag

On Tue, Feb 16, 2016 at 2:18 PM, Hunter Haugen wrote: > The forge does verify that versions match semver 1.0.0, which states "a > pre-release version number MAY be denoted by appending an arbitrary string > immediately following the patch version and a dash. The string MUST be > comprised of only

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

Most of the "open core" issues we've run into time and time again were because one company had control of both an open and a closed edition and used their sole control to prevent features from entering the open edition because they wanted to make money off of it in the closed edition. This most

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

Excerpts from Dean Troyer's message of 2016-02-16 12:57:58 -0600: > On Tue, Feb 16, 2016 at 11:51 AM, Amit Gandhi > wrote: > > > Poppy intends to be an abstraction API over the various CDNs available. > > We do not want to be in the business of building a CDN itself. > > > > Specific to the Popp

Re: [openstack-dev] [Congress] Nominating Masahito for core

+1 From: Tim Hinrichs mailto:t...@styra.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, February 16, 2016 at 11:15 AM To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@l

Re: [openstack-dev] [QA][Tempest]Run only multinode tests in multinode jobs

On Tue, Feb 16, 2016, at 10:42 AM, Assaf Muller wrote: > On Tue, Feb 16, 2016 at 12:26 PM, Clark Boylan > wrote: > > On Tue, Feb 16, 2016, at 01:07 AM, Jordan Pittier wrote: > >> Hi list, > >> I understood we need to limit the number of tests and jobs that are run > >> for > >> each Tempest patch

Re: [openstack-dev] [nova][neutron] New BP for live migration with direct pci passthru

In general, while you've applied this to networking (and it's not the first time I've seen this proposal), the same technique will work with any device - PF or VF, networking or other: - notify the VM via an accepted channel that a device is going to be temporarily removed - remove the device - mi

Re: [openstack-dev] [puppet] Push Mitaka beta tag

On Mon, Feb 15, 2016 at 8:13 AM, Emilien Macchi wrote: > Hi, > > While Puppet modules releases are independently managed, we have some > requests from both RDO & Debian folks to push a first tag in our Puppet > modules, for Mitaka release, so they can start provide Mitaka packaging > based on tag

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On Tue, Feb 16, 2016 at 1:04 PM, Dean Troyer wrote: > > > On Tue, Feb 16, 2016 at 12:17 PM, Sean Dague wrote: > >> Honestly, doing per API call version switching is probably going to end >> in tears. HTTP is stateless, so it's allowed, but it will end in tears >> of complexity as you need to sel

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

Doug Hellmann wrote: > Is there? I thought the point was OpenCDN isn't actually usable. Maybe > someone from the Poppy team can provide more details about that. That is certainly a problem. However I think I would lean on Sean Dague's argument about how Neutron had an open source solution that nee

[openstack-dev] [Congress] Nominating Masahito for core

Hi all, I'm writing to nominate Masahito Muroi for the Congress core team. He's been a consistent contributor for the entirety of Liberty and Mitaka, both in terms of code contributions and reviews. In addition to volunteering for bug fixes and blueprints, he initiated and carried out the design

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

Thomas Goirand wrote: > s/I dislike/is not free software/ [*] > > It's not a mater of taste. Having Poppy requiring a non-free component, > even indirectly (ie: the Oracle JVM that CassandraDB needs), makes it > non-free. Your definition of non-free versus free, if I am not mistaken, is based on

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On Tue, Feb 16, 2016 at 12:17 PM, Sean Dague wrote: > Honestly, doing per API call version switching is probably going to end > in tears. HTTP is stateless, so it's allowed, but it will end in tears > of complexity as you need to self modify resources before passing them > back. Or follow links t

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

On Tue, Feb 16, 2016 at 11:51 AM, Amit Gandhi wrote: > Poppy intends to be an abstraction API over the various CDNs available. > We do not want to be in the business of building a CDN itself. > Specific to the Poppy discussion, I think this is another point that makes Poppy not part of OpenStack

Re: [openstack-dev] [Openstack-operators] How are consumers/operators new to openstack supposed to know about upper-constraints?

On Feb 16, 2016 11:04 AM, "Sean Dague" wrote: > > On 02/16/2016 11:48 AM, Ian Cordasco wrote: > > > > > > -Original Message- > > From: Matt Riedemann > > Reply: Matt Riedemann > > Date: February 16, 2016 at 09:30:49 > > To: OpenStack Development Mailing List (not for usage questions) < o

Re: [openstack-dev] [barbican] Nominating Fernando Diaz for Barbican Core

+1 On Mon, 2016-02-15 at 11:45 -0600, Douglas Mendizábal wrote: > Hi All, > > I would like to nominate Fernando Diaz for the Barbican Core team. > Fernando has been an enthusiastic contributor since joining the > Barbican team. He is currently the most active non-core reviewer on > Barbican proj

Re: [openstack-dev] [QA][Tempest]Run only multinode tests in multinode jobs

On Tue, Feb 16, 2016 at 12:26 PM, Clark Boylan wrote: > On Tue, Feb 16, 2016, at 01:07 AM, Jordan Pittier wrote: >> Hi list, >> I understood we need to limit the number of tests and jobs that are run >> for >> each Tempest patch because our resources are not unlimited. >> >> In Tempest, we have 5

Re: [openstack-dev] [kolla] Decision of how to manage stable/liberty from Kolla Midcycle

On Tue, Feb 16, 2016 at 6:15 PM, Steven Dake (stdake) wrote: > Hey folks, > > We held a midcycle Feb 9th and 10th. The full notes of the midcycle are > here: > https://etherpad.openstack.org/p/kolla-mitaka-midcycle > > We had 3 separate ~40 minute sessions on making stable stable. The reason >

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On 02/16/2016 01:13 PM, Dean Troyer wrote: > On Tue, Feb 16, 2016 at 8:34 AM, Andrew Laski > wrote: > ... > > It's easy enough to think that users will just read the docs and > carefully consider every version increment that they want to consume > but when

[openstack-dev] [kolla] Decision of how to manage stable/liberty from Kolla Midcycle

Hey folks, We held a midcycle Feb 9th and 10th. The full notes of the midcycle are here: https://etherpad.openstack.org/p/kolla-mitaka-midcycle We had 3 separate ~40 minute sessions on making stable stable. The reason for so many sessions on this topic were that it took a long time to come to

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On Tue, Feb 16, 2016 at 8:34 AM, Andrew Laski wrote: ... > It's easy enough to think that users will just read the docs and > carefully consider every version increment that they want to consume but > when they've been on version 2.7 for a while and a new thing comes out in > 2.35 that they want

Re: [openstack-dev] [puppet] Push Mitaka beta tag

I wrote it on IRC, but I want to write it on this list too, since I am one of the requesters. On 02/16/2016 02:16 AM, David Moreau Simard wrote: > So is it implied that a version "8.0.0b1" of a puppet module works > with the "8.0.0b1" of it's parent project ? If it was possible to somehow have th

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

OpenCDN is an abandoned project, although there have been a few attempts at creating one called “OpenCDN”. As far as the we can tell (Poppy Team), there is currently no viable Open source CDN’s available. If there is we would be happy to add it as a supported driver. Also, even if the CDN sof

[openstack-dev] Call for papers talk gone astray?

Hi, Submitted a talk for the upcoming summit (or at least I thought did everything required for it to be included), however it appears to have not appeared in the voting process. Title was "Practical Ansible hacks used to deploy an OpenStack solution" Looking around I've discovered that there is

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

On 02/16/2016 03:15 PM, Sean M. Collins wrote: > Thomas Goirand wrote: >> Oh, that, and ... not using CassandraDB. And yes, this thread is a good >> place to have this topic. I'm not sure who replied to me this thread >> wasn't the place to discuss it: I respectfully disagree, since it's >> another

Re: [openstack-dev] [QA][Tempest]Run only multinode tests in multinode jobs

On Tue, Feb 16, 2016, at 01:07 AM, Jordan Pittier wrote: > Hi list, > I understood we need to limit the number of tests and jobs that are run > for > each Tempest patch because our resources are not unlimited. > > In Tempest, we have 5 multinode experimental jobs: > > experimental-tempest-dsvm-mu

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

Excerpts from Sean M. Collins's message of 2016-02-16 07:15:34 +: > Thomas Goirand wrote: > > Oh, that, and ... not using CassandraDB. And yes, this thread is a good > > place to have this topic. I'm not sure who replied to me this thread > > wasn't the place to discuss it: I respectfully disag

Re: [openstack-dev] [Nova][Cinder] Multi-attach, determining when to call os-brick's connector.disconnect_volume

On 02/12/2016 04:35 PM, John Griffith wrote: On Thu, Feb 11, 2016 at 10:31 AM, Walter A. Boring IV mailto:walter.bor...@hpe.com>> wrote: There seems to be a few discussions going on here wrt to detaches. One is what to do on the Nova side with calling os-brick's disconnect_volu

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

Excerpts from Andrew Laski's message of 2016-02-16 06:34:53 -0800: > > On Tue, Feb 16, 2016, at 07:54 AM, Alex Xu wrote: > > > > > > 2016-02-16 19:53 GMT+08:00 Sean Dague : > >> On 02/12/2016 03:55 PM, Andrew Laski wrote: > >> > > Starting a new thread to continue a thought that came up in > >> >

Re: [openstack-dev] [Openstack-operators] How are consumers/operators new to openstack supposed to know about upper-constraints?

On 02/16/2016 11:48 AM, Ian Cordasco wrote: > > > -Original Message- > From: Matt Riedemann > Reply: Matt Riedemann > Date: February 16, 2016 at 09:30:49 > To: OpenStack Development Mailing List (not for usage questions) > , openstack-operat...@lists.openstack.org > > Subject: [Ope

Re: [openstack-dev] [Monasca] Alarm generation from a sequence of events

Thanks, Roland. Makes sense. I agree. Just tossing the idea: is there a way to validate a temporal causal relationship among events such that in case e1, followed by e2, followed by e3 *implies *a condition C to fail/pass - and generates an alarm. Thanks, Pradip On Tue, Feb 16, 2016 at 8:52

Re: [openstack-dev] [Openstack-operators] How are consumers/operators new to openstack supposed to know about upper-constraints?

  -Original Message- From: Matt Riedemann Reply: Matt Riedemann Date: February 16, 2016 at 09:30:49 To: OpenStack Development Mailing List (not for usage questions) , openstack-operat...@lists.openstack.org Subject:  [Openstack-operators] How are consumers/operators new to openstack

[openstack-dev] Glance Image signing and verification

All, Here are operations guide instructions currently in review to add signed images and configure Nova to automatically check the signature prior to conditionally booting an image. https://review.openstack.org/#/c/245886/. These instructions are more up to date than the ones on the etherpad. Pl

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

https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160216 > > We'll also have open discussion for bugs & reviews, so anyone is welcome > to join. > > See you there, We did our meeting and you can read notes here: http://eavesdrop.openstack.org/meetings/pupp

[openstack-dev] How are consumers/operators new to openstack supposed to know about upper-constraints?

We have a team just upgrading to Liberty and they are having problems. While running down their list of packages they are using, I noticed they have os-brick 0.8.0 which is the latest version (from mitaka). However, os-brick in stable/liberty upper-constraints is at 0.6.0 [1]. So while I don't

Re: [openstack-dev] [Monasca] Alarm generation from a sequence of events

Hi Pradip, The focus of that blueprint is to create metrics from logs in the LogStash component and then publish them to the Kafka metrics topic. The Monasca Threshold Engine can then be used to alarm on the metrics. For example, if the number of errors in a log file exceeds some amount, alarm a

Re: [openstack-dev] [openstack][Magnum] Operation for COE

Wanghua, Please add your requests to the midcycle agenda [1], or bring it up in the team meeting under the open discussion. We can discuss it if agenda allows. [1] https://etherpad.openstack.org/p/magnum-mitaka-midcycle-topics Best regards, Hongbin From: 王华 [mailto:wanghua.hum...@gmail.com] Se

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On 02/16/2016 09:34 AM, Andrew Laski wrote: > > > > On Tue, Feb 16, 2016, at 07:54 AM, Alex Xu wrote: >> >> >> 2016-02-16 19:53 GMT+08:00 Sean Dague > >: >> >> On 02/12/2016 03:55 PM, Andrew Laski wrote: >> > Starting a new thread to continue a thought that

Re: [openstack-dev] [ironic] More midcycle details

We are live! Please do join :) // jim On Thu, Feb 11, 2016 at 05:20:27AM -0800, Jim Rollenhagen wrote: > Hi all, > > Our midcycle is next week! Here's everything you need to know. > > First and foremost, please RSVP on the etherpad, and add any topics > (with your name!) that you'd like to disc

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On Tue, Feb 16, 2016, at 07:54 AM, Alex Xu wrote: > > > 2016-02-16 19:53 GMT+08:00 Sean Dague : >> On 02/12/2016 03:55 PM, Andrew Laski wrote: >> > Starting a new thread to continue a thought that came up in >> > http://lists.openstack.org/pipermail/openstack-dev/2016-February/086457.html. >> >

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

Le 16/02/2016 13:01, Sean Dague a écrit : On 02/16/2016 03:33 AM, Sylvain Bauza wrote: Le 16/02/2016 09:30, Sylvain Bauza a écrit : Le 16/02/2016 04:09, Alex Xu a écrit : 2016-02-16 9:47 GMT+08:00 GHANSHYAM MANN mailto:ghanshyamm...@gmail.com>>: Regards Ghanshyam Mann On

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

2016-02-16 19:53 GMT+08:00 Sean Dague : > On 02/12/2016 03:55 PM, Andrew Laski wrote: > > Starting a new thread to continue a thought that came up in > > > http://lists.openstack.org/pipermail/openstack-dev/2016-February/086457.html > . > > The Nova API microversion framework allows for backwards

[openstack-dev] [cinder] About how to make the vm use volume with libiscsi

Hi, All I want to make the qemu communicate with iscsi target using libiscsi directly, and I followed https://review.openstack.org/#/c/135854/ to add 'volume_drivers = iscsi=nova.virt.libvirt.volume.LibvirtNetVolumeDriver’ in nova.conf and then restarted nova services and cinder services, but s

Re: [openstack-dev] [cinder][all] Integration python-*client tests on gates

On 02/15/2016 02:48 PM, Ivan Kolodyazhny wrote: > Hi all, > > I'll talk mostly about python-cinderclient but the same question could > be related for other clients. > > Now, for python-cinderclient we've got to kinds for > functional/integrated jobs: > > 1) gate-cinderclient-dsvm-functional - a

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On 02/16/2016 03:33 AM, Sylvain Bauza wrote: > > > Le 16/02/2016 09:30, Sylvain Bauza a écrit : >> >> >> Le 16/02/2016 04:09, Alex Xu a écrit : >>> >>> >>> 2016-02-16 9:47 GMT+08:00 GHANSHYAM MANN >> >: >>> >>> Regards >>> Ghanshyam Mann >>> >>> >>> On

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On 02/12/2016 03:55 PM, Andrew Laski wrote: > Starting a new thread to continue a thought that came up in > http://lists.openstack.org/pipermail/openstack-dev/2016-February/086457.html. > The Nova API microversion framework allows for backwards compatible and > backwards incompatible changes but th

Re: [openstack-dev] [Nova][API] Does nova API allow the server_id parem as DB index?

This was needed originally for ec2 support (which requires an integer id). It's not really the db index per say, just another id value which is valid (though hidden) for the server. Before unwinding this issue we *must* make sure that the openstack/ec2 project does not need access to it. On 02/15

[openstack-dev] OpenStack Contributor Awards

Hi all, I'd like to introduce a new round of community awards handed out by the Foundation, to be presented at the feedback session of the summit. Nothing flashy or starchy - the idea is that these are to be a little informal, quirky ... but still recognising the extremely valuable work that

Re: [openstack-dev] [Nova][API] Does nova API allow the server_id parem as DB index?

I think I miss one problem. I didn't found anywhere user can get the DB index from nova API. So even the 'show' action have the ability to show with DB index, but actually nobody can use that, due to there isn't a way to query the DB index for a server, except the user query the DB directly. For th

Re: [openstack-dev] [Nova] notification subteam meeting

Hi, The next meeting of the nova notification subteam will happen 2016-02-16 Tuesday _17: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

Re: [openstack-dev] [fuel] Fuel plugins: lets have some rules

Hi, I have some comments on CI for plugins, currently there is a good instruction on how to install your own CI and using fuel-qa write your own tests [0], since just running BVT is not enough to make sure that plugin works, we should provide a way for a plugin developer to easily extend checks/as

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

That is awesome, happy to finally see it enabled! On Mon, Feb 15, 2016 at 9:32 PM, Anastasia Urlapova wrote: > Aleksey, great news! > > On Mon, Feb 15, 2016 at 7:36 PM, Alexey Shtokolov > wrote: > >> Fuelers, >> >> Task based deployment engine has been enabled in master (Fuel 9.0) by >> default

[openstack-dev] [QA][Tempest]Run only multinode tests in multinode jobs

Hi list, I understood we need to limit the number of tests and jobs that are run for each Tempest patch because our resources are not unlimited. In Tempest, we have 5 multinode experimental jobs: experimental-tempest-dsvm-multinode-full-dibtest gate-tempest-dsvm-multinode-full gate-tempest-dsvm-m

Re: [openstack-dev] [ironic] Baremetal Deploy Ramdisk functional testing

Thanks Jim for the feedback, see my comments below > > So, as I understand this, the goal is to test the bareon ramdisk without > bringing up the rest of the services that talk to it? Correct. > Currently in ironic-land, the only runtime testing of our ramdisk(s) is > the integration tests we do

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

Le 16/02/2016 09:30, Sylvain Bauza a écrit : Le 16/02/2016 04:09, Alex Xu a écrit : 2016-02-16 9:47 GMT+08:00 GHANSHYAM MANN >: Regards Ghanshyam Mann On Mon, Feb 15, 2016 at 12:07 PM, Alex Xu mailto:sou...@gmail.com>> wrote: > If we supp

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

Le 16/02/2016 04:09, Alex Xu a écrit : 2016-02-16 9:47 GMT+08:00 GHANSHYAM MANN >: Regards Ghanshyam Mann On Mon, Feb 15, 2016 at 12:07 PM, Alex Xu mailto:sou...@gmail.com>> wrote: > If we support 2.x.y, when we bump 'x' is a problem. We did

Re: [openstack-dev] [Nova][API] Does nova API allow the server_id parem as DB index?

+1 for no microversion, it's internal implementation and we should be free to remove it since we didn't document it anywhere-GHANSHYAM MANN wrote: -To: "OpenStack Development Mailing List (not for usage questions)" From: GHANSHYAM