Re: [openstack-dev] [Tricircle]Weekly Team Meeting starting on Wednesday !

Just a reminder of today's meeting On Mon, Jun 22, 2015 at 12:45 PM, Zhipeng Huang wrote: > Hi Team, > > Thanks for expressing your interests in Tricircle. The meeting logistics > has been approved by the infra team, therefore starting from Wednesday this > week, we will have *weekly* irc meetin

[openstack-dev] [neutron][hyper-v] Instance can't get fixed ip on hyper-v compute node

Hi, I setup an openstack env as one controller + network node on OL7.1 and two compute node on windows 2012 server with cloudbase hyper-v compute node driver. Every compute node has two nics. I created a vswitch on the second one and use it to connect to instances. Below is my neutron_hyper_agent.

[openstack-dev] Redfish

Hello, I have downloaded the redfish available code and I want to run the test_redfish program to understand what happens. Whenever I set the host name and give the username and password and try to run the file test_redfish.py I get the below error. user@BLTSP02848pc:~/redfish/python-redfish

Re: [openstack-dev] [designate] and [lbaas] - GSLB API and backend support

Hi Kunal, Did you also include use cases per our last discussion on IRC? I prefer to start with use cases before we dive into APIs. Thanks, -Sam. -Original Message- From: Gandhi, Kunal [mailto:kunalhgan...@gmail.com] Sent: Wednesday, June 24, 2015 6:47 AM To: OpenStack Developm

Re: [openstack-dev] [nova] How to properly detect and fence a compromised host (and why I dislike TrustedFilter)

(general point, could we please try not top-posting ? It makes a little harder to follow the conversation) Replies inline. Le 24/06/2015 08:15, Wei, Gang a écrit : Only if all the hosts managed by OpenStack are capable for measured boot process, then let 3rd-party tool call nova fencing API m

[openstack-dev] [Fuel][Plugins] differenciate node with the same role

Hi folks I am wondering if it is possible to differenciate nodes within a same role. Is it possible for example to apply aplugin to a compute node A but not a compute node B? It will be more clear with examples : 1) for the nfs plugin I want to use nfs storage backend for compute node A but LVM fo

[openstack-dev] migrate swift test code from unittest to testtools

Hi All, I try to contribute code to openstack. I made a patch to migrate swift test code from unittest to testtools. https://review.openstack.org/#/c/192960/ And I found that my patch often break if other patch change the test code. For example, the testtools requires that the subclass of the t

[openstack-dev] [swift] migrate swift test code from unittest to testtools

Hi All, I try to contribute code to openstack. I made a patch to migrate swift test code from unittest to testtools. https://review.openstack.org/#/c/192960/ And I found that my patch often break if other patch change the test code. For example, the testtools requires that the subclass of the t

Re: [openstack-dev] [nova] How to properly detect and fence a compromised host (and why I dislike TrustedFilter)

> -Original Message- > From: Sylvain Bauza [mailto:sba...@redhat.com] > Sent: Wednesday, June 24, 2015 9:39 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [nova] How to properly detect and fence a > compromised host (and why I dislike Tr

Re: [openstack-dev] [neutron] dns-nameservers order not honored

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/23/2015 08:48 PM, Paul Ward wrote: > I haven't dug into the code yet, but from testing via CLI and REST > API, it appears neutron does not honor the order in which users > specify their dns-nameservers. For example, no matter what order I > sp

Re: [openstack-dev] [Fuel] Ceph Public Network Setting

Thank you guys! I'm reading the advanced networking spec and think it's good. I'll try to comment it. It's too epic for me for now. I wrote a patch to move Ceph public network to storage network. It's based on Fuel 6.0, so I'm trying to rebase it to lastest master then maybe ask you for a review.

Re: [openstack-dev] [Fuel] Ceph Public Network Setting

Hi Zhou, Try Fuel 6.1 where we have a lot of very nice features including 'advanced networking'. Feel free to read release notes [1]. It's one of the most significant releases with many many features and improvements. I am very proud of it. [1] https://docs.mirantis.com/fuel/fuel-master/release-n

Re: [openstack-dev] [designate] and [lbaas] - GSLB API and backend support

Hi Sam Yes. we discussed the use cases 2 weeks ago on irc. The IRC logs can be found here http://eavesdrop.openstack.org/meetings/gslb/2015/gslb.2015-06-09-16.00.log.html and the use case document can be found h

[openstack-dev] [Fuel][Plugins] differenciate node with the same role - the spec is available

Samuel, Currently, there is a spec on introducing a new role through a plugin [1] - the feature is targeted at 7.0. Feel free to comment on it and ask questions right in the commit. [1] https://review.openstack.org/#/c/185267/ -- Best regards, Irina Partner Management Business Analyst skype:

Re: [openstack-dev] [requirements] converging the openstack-infra/project-config and openstack/requirements requirements checks

Robert Collins wrote: > [...] > I propose the following to reconcile: > - I'll add a lint command to openstack/requirements > - it will check for \n > - it will accept the set that openstack/requirements accepts in each > of non-strict and strict mode > - anything that parses will be checked ag

Re: [openstack-dev] [Fuel] Ceph Public Network Setting

Thank you Sergii, I read the release notes but didn't find a specific 'Advanced Networking' part. It seems advanced networking is a spec [1] mentioned by Igor in a previous mail. Maybe I overlook something? Anyway, I think 6.1 is a great release, for it solves some major problems in my previous ex

Re: [openstack-dev] [Fuel][Plugins] differenciate node with the same role - the spec is available

Irina, Thanks for the link. Unfortunatly it does not cover my use cases. What we would like to do is not define a new role. We would like to be able to apply plugin to some compute node for example and not in the others compute nodes or to be able to execute plugin with a given config on some comp

Re: [openstack-dev] [Fuel] Ceph Public Network Setting

Hello My five cents :) I also very proud of our 6.1 release Unfortunately we still do not have this separation for ceph public and cluster networks in 6.1. One little hint In 6.1 we have granular deployment ( https://docs.mirantis.com/fuel/fuel-master/release-notes.html#granular-deployment-based-o

Re: [openstack-dev] [requirements] converging the openstack-infra/project-config and openstack/requirements requirements checks

++ to make a single source of enforcement. thanks, dims On Wed, Jun 24, 2015 at 6:06 AM, Thierry Carrez wrote: > Robert Collins wrote: >> [...] >> I propose the following to reconcile: >> - I'll add a lint command to openstack/requirements >> - it will check for \n >> - it will accept the set

Re: [openstack-dev] [all][requirements] Whats with the "python_version=='2.7'" stuff thats showing up from today?

On 06/23/2015 07:31 PM, Robert Collins wrote: > You may have seen your requirements update proposals start to include > things like: > MySQL-python;python_version=='2.7' > > like in > https://review.openstack.org/#/c/194325/ > https://review.openstack.org/#/c/194325/3/test-requirements.txt > > Th

[openstack-dev] [Nova] The unbearable lightness of specs

Hey Nova, I'll cut to the chase and keep this email short for brevity and clarity: Specs don't work! They do nothing to facilitate good design happening, if anything they prevent it. The process layered on top with only a minority (!) of cores being able to approve them, yet they are a prereq of

Re: [openstack-dev] Redfish

On 06/24/2015 09:18 AM, Nanda Devi Sahu wrote: Hello, I have downloaded the redfish available code and I want to run the test_redfish program to understand what happens. Whenever I set the host name and give the username and password and try to run the file test_redfish.py I get the below err

Re: [openstack-dev] [devstack] apache wsgi application support

On 06/23/2015 04:07 PM, Brant Knudson wrote: > I've got a few related changes proposed to keystone and devstack: > > https://review.openstack.org/#/c/193891/ - Changes Apache Httpd config > so that /identity is the keystone public (aka main) handler and > /identity_admin is the keystone admin hand

Re: [openstack-dev] [devstack] apache wsgi application support

On 06/24/2015 07:19 AM, Sean Dague wrote: > On 06/23/2015 04:07 PM, Brant Knudson wrote: >> I've got a few related changes proposed to keystone and devstack: >> >> https://review.openstack.org/#/c/193891/ - Changes Apache Httpd config >> so that /identity is the keystone public (aka main) handler a

Re: [openstack-dev] [Fuel][Plugins] differenciate node with the same role - the spec is available

Samuel, I would like you to consider this proposal: https://review.openstack.org/#/c/184076/6/specs/7.0/node-custom-attributes.rst This is about support of custom node labels. I think plugins should be able to assign its own labels to nodes via Nailgun API. Is it possible? Will it suit your case?

Re: [openstack-dev] [devstack] apache wsgi application support

On Wed, 24 Jun 2015, Sean Dague wrote: So on https://review.openstack.org/#/c/194442 ... I was kind of thinking we'd be able to get keystone-wsgi-public into a bin directory. I put up a half baked sketch of this idea in https://review.openstack.org/#/c/195044. Would be curious if some version of

Re: [openstack-dev] [devstack] apache wsgi application support

On 06/24/2015 07:57 AM, Chris Dent wrote: > On Wed, 24 Jun 2015, Sean Dague wrote: > >> So on https://review.openstack.org/#/c/194442 ... I was kind of thinking >> we'd be able to get keystone-wsgi-public into a bin directory. I put up >> a half baked sketch of this idea in >> https://review.opens

Re: [openstack-dev] [devstack] apache wsgi application support

On Wed, 24 Jun 2015, Sean Dague wrote: On 06/24/2015 07:57 AM, Chris Dent wrote: If the primary reason is so that we can rely on the console_scripts entry point to handle getting the application somewhere useful then that too feels a bit crufty, in the sense of "that's a hack". [snip] The re

Re: [openstack-dev] [nova] How to properly detect and fence a compromised host (and why I dislike TrustedFilter)

Le 24/06/2015 10:35, Dulko, Michal a écrit : -Original Message- From: Sylvain Bauza [mailto:sba...@redhat.com] Sent: Wednesday, June 24, 2015 9:39 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova] How to properly detect and fence a c

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote: > Hey Nova, > > I'll cut to the chase and keep this email short for brevity and clarity: > > Specs don't work! They do nothing to facilitate good design happening, > if anything they prevent it. The process layered on top with only a

Re: [openstack-dev] [cinder][stable] Cinder client broken in Juno

Mike Perez wrote: > Two options: > > 1) Revert version discovery which was introduced in Kilo for Cinder client. > > 2) Grant exception on backporting [4] a patch that helps with this > problem, and introduces a config option that does not change default > behavior. I'm also not sure if this shou

Re: [openstack-dev] Redfish

Hello, The python-redfish module is in its infancy atm. One of my colleagues (René) is working on revamping the code so we can start adding more functions. You may want to watch his branch at https://github.com/bcornec/python-redfish/tree/prototype (Or in his own repo https://github.com/uggla/pyt

Re: [openstack-dev] [ClusterLabs] [HA] RFC: moving Pacemaker openstack-resource-agents to stackforge

Like this idea too, we should have done that long ago. :) > On 24 Jun 2015, at 02:17, Adam Spiers wrote: > > Digimer wrote: >> > > Thanks, I only realised that after getting a deprecation warning :-( > >> On 23/06/15 06:27 AM, Adam Spiers wrote: >>> [cross-posting to openstack-dev and pacema

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote: > Hey Nova, > > I'll cut to the chase and keep this email short for brevity and clarity: > > Specs don't work! They do nothing to facilitate good design happening, > if anything they prevent it. The process layered on top with only a

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 6/24/2015 7:42 AM, Daniel P. Berrange wrote: On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote: Hey Nova, I'll cut to the chase and keep this email short for brevity and clarity: Specs don't work! They do nothing to facilitate good design happening, if anything they prevent i

Re: [openstack-dev] [requirements] converging the openstack-infra/project-config and openstack/requirements requirements checks

On 2015-06-24 16:03:18 +1200 (+1200), Robert Collins wrote: [...] > We also have a strict/nonstrict mode which appears to be the same to me. The requirements validation check compares old vs. new versions of files so that it can only enforce matching on lines which are being changed. The non-stric

Re: [openstack-dev] [Nova] The unbearable lightness of specs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/24/2015 03:23 PM, Sahid Orentino Ferdjaoui wrote: > I do not consider specs don't work, personnaly I refer myself to > this relatively good documentation [1] instead of to dig in code > to remember how work a feature early introduced. > I thi

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 6/24/2015 8:23 AM, Sahid Orentino Ferdjaoui wrote: On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote: Hey Nova, I'll cut to the chase and keep this email short for brevity and clarity: Specs don't work! They do nothing to facilitate good design happening, if anything they pre

Re: [openstack-dev] [cinder][stable] Cinder client broken in Juno

On 2015-06-24 09:01:51 +0300 (+0300), Duncan Thomas wrote: > The problem there is that it takes (significant) time for the connection > attempt to time out - every cinder command taking several minutes is not > acceptable. [...] Another silly idea from an end user of cinderclient here, but try bot

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 06/24/2015 01:42 PM, Daniel P. Berrange wrote: > On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote: >> Hey Nova, >> >> I'll cut to the chase and keep this email short for brevity and clarity: >> >> Specs don't work! They do nothing to facilitate good design happening, >> if anything

Re: [openstack-dev] [cinder][stable] Cinder client broken in Juno

On 24 June 2015 at 14:34, Jeremy Stanley wrote: > On 2015-06-24 09:01:51 +0300 (+0300), Duncan Thomas wrote: >> The problem there is that it takes (significant) time for the connection >> attempt to time out - every cinder command taking several minutes is not >> acceptable. > [...] > > Another si

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 06/24/2015 02:33 PM, Matt Riedemann wrote: > > > On 6/24/2015 8:23 AM, Sahid Orentino Ferdjaoui wrote: >> On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote: >>> Hey Nova, >>> >>> I'll cut to the chase and keep this email short for brevity and clarity: >>> >>> Specs don't work! The

Re: [openstack-dev] [Nova] The unbearable lightness of specs

> Why do cores need approved specs for example - and indeed for many of us > - it's just a dance we do. I refuse to believe that a core can be > trusted to approve patches but not to write any code other than a bugfix > without a written document explaining themselves, and then have a yet > more ex

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On Wed, Jun 24, 2015 at 02:51:38PM +0100, Nikola Đipanov wrote: > On 06/24/2015 02:33 PM, Matt Riedemann wrote: [. . .] > > I agree completely. The nicely rendered feature docs which is a > > byproduct of the specs process in gerrit is a great part of it. So when > > someone is trying to use a ne

[openstack-dev] [Tricircle]Weekly Team Meeting roundup

Hi Team, Thanks for the great discussions. Meeting minutes could be found at http://eavesdrop.openstack.org/meetings/tricircle_weekly_meeting_2015_06_24/2015/tricircle_weekly_meeting_2015_06_24.2015-06-24-13.04.html. Let's start hacking and reconvene next week :) -- Zhipeng (Howard) Huang Stand

Re: [openstack-dev] [designate] and [lbaas] - GSLB API and backend support

Great! Thanks you. I have missed this one. From: Gandhi, Kunal [mailto:kunalhgan...@gmail.com] Sent: Wednesday, June 24, 2015 12:21 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [designate] and [lbaas] - GSLB API and backend support Hi Sam Yes.

Re: [openstack-dev] [neutron][hyper-v] Instance can't get fixed ip on hyper-v compute node

Hi Lily, What version are you running, Icehouse, Juno, Kilo or master? A full copy of the nova-compute.log and neutron_hyperv_agent.log on a pastebin might be helpful. Additionally, your neutron.conf from the neutron server could help along with your neutron network configuration. Finally, the o

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On Wed, Jun 24, 2015 at 04:09:16PM +0200, Kashyap Chamarthy wrote: > On Wed, Jun 24, 2015 at 02:51:38PM +0100, Nikola Đipanov wrote: > > On 06/24/2015 02:33 PM, Matt Riedemann wrote: > > [. . .] > > > > I agree completely. The nicely rendered feature docs which is a > > > byproduct of the specs p

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 06/24/2015 03:08 PM, Dan Smith wrote: >> Why do cores need approved specs for example - and indeed for many of us >> - it's just a dance we do. I refuse to believe that a core can be >> trusted to approve patches but not to write any code other than a bugfix >> without a written document explain

Re: [openstack-dev] [cinder][stable] Cinder client broken in Juno

On Tue, Jun 23, 2015 at 08:49:55AM -0700, Mike Perez wrote: > There was a bug raised [1] from some large deployments that the Cinder > client 1.2.0 and beyond is not working because of version discovery. > Unfortunately it's not taking into account of deployments that have a > proxy. A little bit

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 6/24/2015 9:09 AM, Kashyap Chamarthy wrote: On Wed, Jun 24, 2015 at 02:51:38PM +0100, Nikola Đipanov wrote: On 06/24/2015 02:33 PM, Matt Riedemann wrote: [. . .] I agree completely. The nicely rendered feature docs which is a byproduct of the specs process in gerrit is a great part of i

Re: [openstack-dev] [neutron][hyper-v] Instance can't get fixed ip on hyper-v compute node

Hello, >From what I can see in the trace you included, it seems to be either Kilo or >master (it uses networking-hyperv, which was introduced in Kilo). Also, it might be useful to know if you are using Windows Server 2012 or Windows Server 2012 R2. Running this in Powershell should yield the OS

[openstack-dev] [Magnum] Networking Subgroup

All, A subgroup [1] has formed within the Magnum project, who's mission is providing first class networking support for containers. Please join us [2] this Thursday at 1800 UTC for our first meeting to discuss the native Docker networking blueprint [3] and overall direction of the team. [1] ht

[openstack-dev] [nova][scheduler] Poll for possible Monday meeting times

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Since the current meeting time is problematic for several people, we ran a poll for preferences for different times on Tuesdays and Wednesdays. No single time was acceptable for all of the main people involved in the Scheduler effort, so we're lookin

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 06/24/15 at 02:38pm, Nikola Đipanov wrote: On 06/24/2015 01:42 PM, Daniel P. Berrange wrote: On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote: Hey Nova, I'll cut to the chase and keep this email short for brevity and clarity: Specs don't work! They do nothing to facilitate go

Re: [openstack-dev] [Fuel][Plugins] differenciate node with the same role - the spec is available

Julia, It is exactly what i was thinking. With such a mechanism we would be able to define custom labels to apply different type of task on compute nodes according to their labels. I add a comment on the review. As for now I don't see how we would be able to create custom label from plugin. In suc

Re: [openstack-dev] [Nova][Keystone] The unbearable lightness of specs

On 06/24/2015 06:28 AM, Nikola Đipanov wrote: Gerrit and our spec template are a horrible tool for discussing design. This is the heart of the problem. I think that a proper RFE description in the bug tracker is the best place to start. Not a design of the solution, but a statement of the p

Re: [openstack-dev] [cinder][stable] Cinder client broken in Juno

On 24 June 2015 at 16:42, Dave Walker wrote: > > As Jeremy points out, I fail to see why fallback default behaviour > cannot be used.. Attempt to use version discovery feature, if fail - > fall back to legacy behaviour.. > > What are the issues associated with this? > So the issue is that for pr

Re: [openstack-dev] [Openstack-operators] [nova] [neutron] Re: How do your end users use networking?

Thanks Kris and Sam for your replies! On 18/06/15 01:20, Kris G. Lindgren wrote: On 6/17/15, 10:59 AM, "Neil Jerram" wrote: On 17/06/15 16:17, Kris G. Lindgren wrote: See inline. Kris Lindgren Senior Linux Systems Engineer GoDaddy, LLC. On 6/

Re: [openstack-dev] [Nova][Keystone] The unbearable lightness of specs

On Wed, Jun 24, 2015 at 11:52:37AM -0400, Adam Young wrote: > On 06/24/2015 06:28 AM, Nikola Đipanov wrote: > >Gerrit and our spec template are a horrible tool for > >discussing design. > This is the heart of the problem. > > > I think that a proper RFE description in the bug tracker is the best

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 06/24/2015 04:42 PM, Andrew Laski wrote: > On 06/24/15 at 02:38pm, Nikola Đipanov wrote: >> On 06/24/2015 01:42 PM, Daniel P. Berrange wrote: >>> On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote: Hey Nova, I'll cut to the chase and keep this email short for brevity a

Re: [openstack-dev] [Nova] The unbearable lightness of specs

TL/DR: I think the original poster is simply frustrated with how long it takes to go from spec to landed feature. How about we stop talking about whether specs are good or not (I think everyone agrees that they are beneficial), and try to actually make the process better? And by make it better, I

Re: [openstack-dev] [Nova] The unbearable lightness of specs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 06/24/2015 08:38 AM, Nikola Đipanov wrote: > I urge people to reply to this instead of my original email as the > writing is more detailed and balanced. OK, I've read what others have written, and want to throw in my own 0.8316 BTC. The sp

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On Wed, Jun 24, 2015 at 04:46:57PM +, Michael Krotscheck wrote: > On Wed, Jun 24, 2015 at 6:30 AM Matt Riedemann > wrote: > > > > > There is the openstack-specs repo for cross-project specs: > > > > http://specs.openstack.org/openstack/openstack-specs/ > > > > That'd be a good place for thing

Re: [openstack-dev] [grenade] future direction on partial upgrade support

On Tue, Jun 16, 2015 at 9:58 AM, Sean Dague wrote: > Back when Nova first wanted to test partial upgrade, we did a bunch of > slightly odd conditionals inside of grenade and devstack to make it so > that if you were very careful, you could just not stop some of the old > services on a single node

Re: [openstack-dev] [grenade] future direction on partial upgrade support

On 06/24/2015 01:31 PM, Joe Gordon wrote: > > > On Tue, Jun 16, 2015 at 9:58 AM, Sean Dague > wrote: > > Back when Nova first wanted to test partial upgrade, we did a bunch of > slightly odd conditionals inside of grenade and devstack to make it so > that if y

Re: [openstack-dev] [grenade] future direction on partial upgrade support

On 06/24/2015 01:31 PM, Joe Gordon wrote: > > > On Tue, Jun 16, 2015 at 9:58 AM, Sean Dague > wrote: > > Back when Nova first wanted to test partial upgrade, we did a bunch of > slightly odd conditionals inside of grenade and devstack to make it so > that if y

Re: [openstack-dev] [grenade] future direction on partial upgrade support

> If multi-node isn't reliable more generally yet, do you think the > simpler implementation of partial-upgrade testing could proceed? I've > already done all of the patches to do it for Neutron. That way we could > quickly get something in place to help block regressions and work on the > longer

Re: [openstack-dev] [devstack] apache wsgi application support

On Wed, Jun 24, 2015 at 7:27 AM, Chris Dent wrote: > On Wed, 24 Jun 2015, Sean Dague wrote: > >> On 06/24/2015 07:57 AM, Chris Dent wrote: >> >>> If the primary reason is so that we can rely on the console_scripts >>> entry point to handle getting the application somewhere useful then >>> that to

[openstack-dev] [akanda] prep for m2

Lets make sure we have checked on outstanding reviews

Re: [openstack-dev] [grenade] future direction on partial upgrade support

On 06/24/2015 01:49 PM, Dan Smith wrote: >> If multi-node isn't reliable more generally yet, do you think the >> simpler implementation of partial-upgrade testing could proceed? I've >> already done all of the patches to do it for Neutron. That way we could >> quickly get something in place to he

Re: [openstack-dev] [nova] How to properly detect and fence a compromised host (and why I dislike TrustedFilter)

On Tue, Jun 23, 2015 at 3:41 AM, Sylvain Bauza wrote: > Hi team, > > Some discussion occurred over IRC about a bug which was publicly open > related to TrustedFilter [1] > I want to take the opportunity for raising my concerns about that specific > filter, why I dislike it and how I think we coul

Re: [openstack-dev] [grenade] future direction on partial upgrade support

On Wed, Jun 24, 2015 at 10:45 AM, Sean Dague wrote: > On 06/24/2015 01:31 PM, Joe Gordon wrote: > > > > > > On Tue, Jun 16, 2015 at 9:58 AM, Sean Dague > > wrote: > > > > Back when Nova first wanted to test partial upgrade, we did a bunch > of > > slightly odd cond

Re: [openstack-dev] [grenade] future direction on partial upgrade support

On Wed, Jun 24, 2015 at 11:01 AM, Joe Gordon wrote: > > > On Wed, Jun 24, 2015 at 10:45 AM, Sean Dague wrote: > >> On 06/24/2015 01:31 PM, Joe Gordon wrote: >> > >> > >> > On Tue, Jun 16, 2015 at 9:58 AM, Sean Dague > > > wrote: >> > >> > Back when Nova first wanted to

Re: [openstack-dev] [devstack] apache wsgi application support

On 06/24/2015 01:51 PM, Brant Knudson wrote: > > > On Wed, Jun 24, 2015 at 7:27 AM, Chris Dent > wrote: > > On Wed, 24 Jun 2015, Sean Dague wrote: > > On 06/24/2015 07:57 AM, Chris Dent wrote: > > If the primary reason is so that we can rely o

Re: [openstack-dev] [grenade] future direction on partial upgrade support

On 06/24/2015 01:41 PM, Russell Bryant wrote: > On 06/24/2015 01:31 PM, Joe Gordon wrote: >> >> >> On Tue, Jun 16, 2015 at 9:58 AM, Sean Dague > > wrote: >> >> Back when Nova first wanted to test partial upgrade, we did a bunch of >> slightly odd conditionals inside o

Re: [openstack-dev] [Fuel][Plugins] differenciate node with the same role - the spec is available

Samuel, AFAIK labels will not be related to tasks, it's just marks for filtering nodes. What "roles" means for you? we have tasks (A, B, C, D) and on some nodes tasks A B D should be executed, on some B C etc. So plugin can provide specials marks or tags or sets (we call it "roles") and link task

[openstack-dev] [openstack-infra][Infra][Neutron] Nominating intel-networking-ci for voting rights

Hi Kyle and Neutron Cores, I would like to nominate Intel-Networking-CI (https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-Networking-CI) to have voting (non-gating) rights. It's been commenting on each proposed patch-set in Neutron since Feb 10 '15: https://review.openstack.org/#/q/revie

Re: [openstack-dev] [requirements] converging the openstack-infra/project-config and openstack/requirements requirements checks

On 25 Jun 2015 1:24 am, "Jeremy Stanley" wrote: > > On 2015-06-24 16:03:18 +1200 (+1200), Robert Collins wrote: > [...] > > We also have a strict/nonstrict mode which appears to be the same to me. > > The requirements validation check compares old vs. new versions of > files so that it can only en

Re: [openstack-dev] [all][requirements] Whats with the "python_version=='2.7'" stuff thats showing up from today?

The projects with the check job can't get updates to python specific requirements until the new longer is in place. I've nearly got that done, and its a critical priority for me since we don't want this stuff wedged. Projects can manually submit changes to non marker based requirements in the meant

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On Wed, Jun 24, 2015 at 10:02:27AM -0500, Matt Riedemann wrote: > > > On 6/24/2015 9:09 AM, Kashyap Chamarthy wrote: > >On Wed, Jun 24, 2015 at 02:51:38PM +0100, Nikola Đipanov wrote: > >>On 06/24/2015 02:33 PM, Matt Riedemann wrote: [. . .] > >This is one of the _baffling_ aspects -- that a so

Re: [openstack-dev] [grenade] future direction on partial upgrade support

On Wed, Jun 24, 2015 at 11:02 AM, Joe Gordon wrote: > > > On Wed, Jun 24, 2015 at 11:01 AM, Joe Gordon > wrote: > >> >> >> On Wed, Jun 24, 2015 at 10:45 AM, Sean Dague wrote: >> >>> On 06/24/2015 01:31 PM, Joe Gordon wrote: >>> > >>> > >>> > On Tue, Jun 16, 2015 at 9:58 AM, Sean Dague >> >

Re: [openstack-dev] [grenade] future direction on partial upgrade support

On Wed, Jun 24, 2015 at 11:03 AM, Sean Dague wrote: > On 06/24/2015 01:41 PM, Russell Bryant wrote: > > On 06/24/2015 01:31 PM, Joe Gordon wrote: > >> > >> > >> On Tue, Jun 16, 2015 at 9:58 AM, Sean Dague >> > wrote: > >> > >> Back when Nova first wanted to test partia

Re: [openstack-dev] [Nova] The unbearable lightness of specs

24.06.2015 20:21, Daniel P. Berrange пишет: On Wed, Jun 24, 2015 at 04:46:57PM +, Michael Krotscheck wrote: On Wed, Jun 24, 2015 at 6:30 AM Matt Riedemann wrote: There is the openstack-specs repo for cross-project specs: http://specs.openstack.org/openstack/openstack-specs/ That'd be a

Re: [openstack-dev] [Fuel] Ceph Public Network Setting

Zhou, As mentioned, Please review [1][2]. This is the interface we will support as we implement the advanced networking parts. In your case, just fip the role map in your patch to nailgun and the library interface will remain the same. [1] https://review.openstack.org/#/c/194434/ [2] https://revi

Re: [openstack-dev] [Fuel][Plugins] differenciate node with the same role - the spec is available

Andriy, May be 'role' was not the correct word here. For me role are compute, controller, base-os, cinder, mongo. I know that we can specify that a task A should be executed on some role (controller and compute for example) and a task B on some other roles (Cinder for example). To come back to m

Re: [openstack-dev] [devstack] apache wsgi application support

On 06/24/2015 02:05 PM, Sean Dague wrote: > On 06/24/2015 01:51 PM, Brant Knudson wrote: >> >> >> On Wed, Jun 24, 2015 at 7:27 AM, Chris Dent > > wrote: >> >> On Wed, 24 Jun 2015, Sean Dague wrote: >> >> On 06/24/2015 07:57 AM, Chris Dent wrote: >> >>

Re: [openstack-dev] [Nova][Keystone] The unbearable lightness of specs

On 06/24/2015 12:25 PM, Daniel P. Berrange wrote: Which happened repeatedly. You could say that the first patch submitted to the code repository should simply be a doc file addition, that describes the feature proposal and we should discuss that before then submitting code patches, but then that'

Re: [openstack-dev] [Fuel][Plugins] differenciate node with the same role - the spec is available

Samuel, As I know one node can have many roles. For 1/ You can specify custom nova-nfs role and assign it on compute nodes. Regards, Andriy On Wed, Jun 24, 2015 at 10:21 PM, Samuel Bartel wrote: > Andriy, > > May be 'role' was not the correct word here. > For me role are compute, controller,

Re: [openstack-dev] [Fuel][Fuel-library] Using librarian-puppet to manage upstream fuel-library modules

On 06/23/2015 01:51 PM, Alex Schultz wrote: Hello everyone, I took some time this morning to write out a document[0] that outlines one possible ways for us to manage our upstream modules in a more consistent fashion. I know we've had a few emails bouncing around lately around this topic of our u

[openstack-dev] [nova] import OVA/OVF into openstack

Hi, Not sure if I should send this to glance or nova project, anyways ... As far as I know, Openstack today does not support OVA/OVF image natively (correct me if I were wrong). I am wondering if there is any plan to support them? Also Any recommendations for now to migrate OVA/OVF into opens

[openstack-dev] [QA] Meeting Thursday June 25th at 22:00 UTC

Hi everyone, Just a quick reminder that the weekly OpenStack QA team IRC meeting will be tomorrow Thursday, June 25th at 22:00 UTC in the #openstack-meeting channel. The agenda for tomorrow's meeting can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting Anyone is welcome to ad

[openstack-dev] [all] inoculate your project against namespace package changes

Many of you are aware that I’m still working through the Oslo libraries, removing the ‘oslo’ namespace package in favor of library-specific names like ‘oslo_config’. If you’re not, you’ll find details in the blueprint [1]. I have been submitting patches to projects as I find the old import style

Re: [openstack-dev] [devstack] apache wsgi application support

Hi guys, I worked on running nova-api on http://localhost/compute. I prepared raw reviews: nova review: https://review.openstack.org/#/c/195303/1 devstack review: https://review.openstack.org/#/c/195300/ We need to determine proper URLs for ec2-api(used 8773 port) and metadata(used 8775 port) serv

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On Wed, Jun 24, 2015 at 11:42 AM, Kashyap Chamarthy wrote: > On Wed, Jun 24, 2015 at 10:02:27AM -0500, Matt Riedemann wrote: > > > > > > On 6/24/2015 9:09 AM, Kashyap Chamarthy wrote: > > >On Wed, Jun 24, 2015 at 02:51:38PM +0100, Nikola Đipanov wrote: > > >>On 06/24/2015 02:33 PM, Matt Riedemann

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On Wed, Jun 24, 2015 at 10:04 AM, Ed Leafe wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 06/24/2015 08:38 AM, Nikola Đipanov wrote: > > > I urge people to reply to this instead of my original email as the > > writing is more detailed and balanced. > > OK, I've read what others

[openstack-dev] [Fuel] Meeting Jun-25

Please note the IRC meeting is scheduled for 16:00 UTC in #openstack-meeting-alt Please review meeting agenda and update if there is something you wish to discuss. https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda -- -- Andrew Woodward Mirantis Fuel Community Ambassador Ceph Comm

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 06/24/2015 08:42 AM, Daniel P. Berrange wrote: On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote: Hey Nova, I'll cut to the chase and keep this email short for brevity and clarity: Specs don't work! They do nothing to facilitate good design happening, if anything they prevent i

[openstack-dev] [app-catalog] Meeting Thursday June 25th at 17:00UTC

Hi! Our next OpenStack App Catalog meeting will take place this Thursday June 25th at 17:00 UTC in #openstack-meeting-3 The agenda can be found here: https://wiki.openstack.org/wiki/Meetings/app-catalog Please add agenda items if there's anything you would like to discuss. One important topic we'

[openstack-dev] [Congress] Hands-on-lab setup instructions

At the IRC this week, Bryan asked how he could replicate the environment we used at the Vancouver hands-on-lab. So we added some basic instructions at the end of the lab write-up. https://docs.google.com/document/u/1/d/1lXmMkUhiSZYK45POd5ungPjVR--Fs_wJHeQ6bXWwP44/pub Bryan: hope that helps. Let

  1   2   >