[openstack-dev] 答复: [devstack] Opensatck installation issue.

Hi Abhishek, For the error in the first line: “mkdir: cannot create directory `/logs': Permission denied” and the error at the end: “ln: failed to create symbolic link `/logs/screen/screen-key.log': No such file or directory” The stack user does not have the permission on “/” so it can not creat

Re: [openstack-dev] [Ironic] ironic-discoverd status update

tuskar-ui is supposed to enroll nodes into ironic. On Thu, Jan 8, 2015 at 4:36 AM, Zhou, Zhenzan wrote: > Sounds like we could add something new to automate the enrollment of new > nodes:-) > Collecting IPMI info into a csv file is still a trivial job... > > BR > Zhou Zhenzan > > -Original M

[openstack-dev] [Group-based-policy] New addition to the core team

Hi, I would like to propose Magesh GV (magesh-gv) to the Group-based Policy (GBP) core team based on his excellent contribution to the project. We discussed this during the weekly IRC meeting [1] and the current core team unanimously supports this. Let us know if there are any objections, otherwise

Re: [openstack-dev] [Keystone][tc] Removal Plans for keystoneclient.middleware.auth_token

That was a copy paste error. The response was meant to be: Yes, that is the issue, unbounded version on the stable branches. --Morgan Sent via mobile > On Jan 8, 2015, at 22:57, Morgan Fainberg wrote: > > > >>> On Jan 8, 2015, at 16:10, Sean Dague wrote: >>> On 01/08/2015 07:01 PM,

Re: [openstack-dev] [Keystone][tc] Removal Plans for keystoneclient.middleware.auth_token

> On Jan 8, 2015, at 16:10, Sean Dague wrote: > >> On 01/08/2015 07:01 PM, Morgan Fainberg wrote: >> >>> On Jan 8, 2015, at 3:56 PM, Sean Dague wrote: >>> >>> On 01/08/2015 06:29 PM, Morgan Fainberg wrote: As of Juno all projects are using the new keystonemiddleware package for au

[openstack-dev] 答复: [Heat] Precursor to Phase 1 Convergence

发件人: Angus Salkeld [mailto:asalk...@mirantis.com] 发送时间: 2015年1月9日 14:08 收件人: OpenStack Development Mailing List (not for usage questions) 主题: Re: [openstack-dev] [Heat] Precursor to Phase 1 Convergence On Fri, Jan 9, 2015 at 3:22 PM, Murugan, Visnusaran mailto:visnusaran.muru...@hp.com>> wrote

Re: [openstack-dev] [Heat] Precursor to Phase 1 Convergence

On Fri, Jan 9, 2015 at 3:22 PM, Murugan, Visnusaran < visnusaran.muru...@hp.com> wrote: > Steve, > > > > My reasoning to have a “--continue” like functionality was to run it as a > periodic task and substitute continuous observer for now. > > I am not in favor of the --continue as an API. I'd sug

Re: [openstack-dev] [Heat] Precursor to Phase 1 Convergence

Steve, My reasoning to have a “--continue” like functionality was to run it as a periodic task and substitute continuous observer for now. “--continue” based command should work on realized vs. actual graph and issue a stack update. I completely agree that user action should not be needed to r

Re: [openstack-dev] [Heat] Precursor to Phase 1 Convergence

Steve, Auto recovery is the plan. Engine failure should be detected by way of heartbeat or recover partially realised stack on engine startup in case of a single engine scenario. "--continue" command was just a additional helper api. [image: --] Visnusaran Murugan [image: http://]about.me/

[openstack-dev] offlist: The scope of OpenStack wiki [all]

Hi Stef, thanks for writing this up. One aspect this proposal doesn't address is the ungoverned content for projects that are either in stackforge, pre-stackforge, incubating, or have no intention of any governance but want to use the openstack wiki. What can we do if one of those groups raises the

Re: [openstack-dev] The state of nova-network to neutron migration

On 09/01/15 08:06, Maru Newby wrote: > >> On Jan 8, 2015, at 3:54 PM, Sean Dague wrote: >> >> On 01/08/2015 06:41 PM, Maru Newby wrote: >>> As per a recent exchange on #openstack-neutron, I’ve been asked to present >>> my views on this effort. What follows is in no way intended to detract >>>

Re: [openstack-dev] [Manila] Driver modes, share-servers, and clustered backends

Thanks for the explanations! Really helpful. My questions are added in line. Thanks. -chen -Original Message- From: Ben Swartzlander [mailto:b...@swartzlander.org] Sent: Friday, January 09, 2015 6:02 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstac

Re: [openstack-dev] [nova] serial-console *replaces* console-log file?

There is an excellent post describing this, for your information: http://blog.oddbit.com/2014/12/22/accessing-the-serial-console-of-your-nova-servers/ 2015-01-07 22:38 GMT+08:00 Markus Zoeller : > The blueprint "serial-ports" introduced a serial console connection > to an instance via websocket. I

Re: [openstack-dev] [qa] Tempest Bug triage

All, As we all know bug triage rotation is working well in QA and we keep new bug count low. Thanks everyone for signing up in bug triage rotation. To continue the same strategy and keeping good progress on bugs, we need more volunteers to sign-up for coming weeks. People who want to help in bug

Re: [openstack-dev] [Neutron][L3] Stop agent scheduling without topping sevices

Is there another openstack service that allows this so we can make the API consistent between the two when this change is made? On Thu, Jan 8, 2015 at 3:09 PM, Carl Baldwin wrote: > I added a link to @Jack's post to the ML to the bug report [1]. I am > willing to support @Itsuro with reviews of

Re: [openstack-dev] [Keystone][tc] Removal Plans for keystoneclient.middleware.auth_token

On 01/08/2015 07:01 PM, Morgan Fainberg wrote: > >> On Jan 8, 2015, at 3:56 PM, Sean Dague wrote: >> >> On 01/08/2015 06:29 PM, Morgan Fainberg wrote: >>> As of Juno all projects are using the new keystonemiddleware package for >>> auth_token middleware. Recently we’ve been running into issues w

Re: [openstack-dev] The state of nova-network to neutron migration

> On Jan 8, 2015, at 3:54 PM, Sean Dague wrote: > > On 01/08/2015 06:41 PM, Maru Newby wrote: >> As per a recent exchange on #openstack-neutron, I’ve been asked to present >> my views on this effort. What follows is in no way intended to detract from >> the hard work and dedication of those u

Re: [openstack-dev] [Keystone][tc] Removal Plans for keystoneclient.middleware.auth_token

> On Jan 8, 2015, at 3:56 PM, Sean Dague wrote: > > On 01/08/2015 06:29 PM, Morgan Fainberg wrote: >> As of Juno all projects are using the new keystonemiddleware package for >> auth_token middleware. Recently we’ve been running into issues with >> maintenance of the now frozen (and deprecated

Re: [openstack-dev] [Keystone][tc] Removal Plans for keystoneclient.middleware.auth_token

On 01/08/2015 06:29 PM, Morgan Fainberg wrote: > As of Juno all projects are using the new keystonemiddleware package for > auth_token middleware. Recently we’ve been running into issues with > maintenance of the now frozen (and deprecated) > keystoneclient.middleware.auth_token code. Ideally al

Re: [openstack-dev] The state of nova-network to neutron migration

On 01/08/2015 06:41 PM, Maru Newby wrote: > As per a recent exchange on #openstack-neutron, I’ve been asked to present my > views on this effort. What follows is in no way intended to detract from the > hard work and dedication of those undertaking it, but I think that their > energy could be b

Re: [openstack-dev] The scope of OpenStack wiki [all]

On Thu, 2015-01-08 at 12:52 -0800, Sean Roberts wrote: > Thanks for bringing this up Stef. I have found while introducing > OpenStack fundamentals in the user groups, what seems logical to us, > the fully OpenStack immersed, is confusing to newcomers. Yeah, I'm diving more in the wiki in preparat

Re: [openstack-dev] The state of nova-network to neutron migration

As per a recent exchange on #openstack-neutron, I’ve been asked to present my views on this effort. What follows is in no way intended to detract from the hard work and dedication of those undertaking it, but I think that their energy could be better spent. At nova’s juno mid-cycle in July, th

[openstack-dev] [Keystone][tc] Removal Plans for keystoneclient.middleware.auth_token

As of Juno all projects are using the new keystonemiddleware package for auth_token middleware. Recently we’ve been running into issues with maintenance of the now frozen (and deprecated) keystoneclient.middleware.auth_token code. Ideally all deployments should move over to the new package. In s

[openstack-dev] [nova] Request Spec Freeze Exception

Hi, During the Kilo summit, the folks in the pci passthrough and SR-IOV groups discussed what we’d like to achieve in this cycle, and the result was documented in this Etherpad: https://etherpad.openstack.org/p/kilo_sriov_pci_passthrough To get the work going, we’ve submitted a few design specs

Re: [openstack-dev] [Neutron][L3] Stop agent scheduling without topping sevices

I added a link to @Jack's post to the ML to the bug report [1]. I am willing to support @Itsuro with reviews of the implementation and am willing to consult if you need and would like to ping me. Carl [1] https://bugs.launchpad.net/neutron/+bug/1408488 On Thu, Jan 8, 2015 at 7:49 AM, McCann, Ja

Re: [openstack-dev] [horizon] packaging problem production build question

Thanks for humoring me as I ask these questions. I'm just trying to connect the dots. How would system packages work in practice? For example, when it comes to ubuntu lucid (10.04 LTS) there is no system package meeting the jQuery requirement and for precise (12.04 LTS) you need precise-backports.

Re: [openstack-dev] [horizon] static files handling, bower/

Thanks, Radomir. How much detail from this discussion should be captured in the blueprint? I'm afraid I'm more familiar with the Python PEP process. On Thu Jan 08 2015 at 11:38:57 PM Radomir Dopieralski < openst...@sheep.art.pl> wrote: > On 06/01/15 01:53, Richard Jones wrote: > > I think the onl

Re: [openstack-dev] [horizon] packaging problem production build question

On 2015-01-08 15:11:24 -0700 (-0700), David Lyle wrote: [...] > For those running CI environments, remote access will likely be > required for bower to work. Although, it seems something like > private-bower [1] could be utilized to leverage a local mirror > where access or network performance are

[openstack-dev] [Magnum] Mid-Cycle Meetup Planning

Team, If you have been watching the Magnum project you know that things have really taken off recently. At Paris we did not contemplate a Mid-Cycle meet-up but now that we have come this far so quickly, and have such a broad base of participation now, it makes sense to ask if you would like to

Re: [openstack-dev] [horizon] packaging problem production build question

Bower is not for use in production environments. There will continue to be two environment setup procedures, as there are today. For production, deploy Horizon and its dependencies via system packages. For development and testing leverage bower to pull the javascript resources, much as pip is used

[openstack-dev] [Manila] Driver modes, share-servers, and clustered backends

There has been some confusion on the topic of driver modes and share-server, especially as they related to storage controllers with multiple physical nodes, so I will try to clear up the confusion as much as I can. Manila has had the concept of "share-servers" since late icehouse. This featur

[openstack-dev] oslo.utils 1.2.1 released

The Oslo team is pleased to announce the release of oslo.utils 1.2.1: Oslo Utility library This is a bugfix release to address a problem found in the 1.2.0 release. For more details, please see the git log history below and http://launchpad.net/oslo/+milestone/1.2.1 Please report issues through

[openstack-dev] oslo.serialization 1.2.0 released

The Oslo team is pleased to announce the release of oslo.serialization 1.2.0: oslo.serialization library The primary reason for this release is to move the code out of the oslo namespace package as part of https://blueprints.launchpad.net/oslo-incubator/+spec/drop-namespace-packages For more deta

[openstack-dev] [horizon] packaging problem production build question

I've been going over the packaging problem in an effort to see how we can move to something better. Given the current proposal around bower I'm still left with a production deployment question. For a build environment sitting in isolation, unable to download from the Internet including Github, how

Re: [openstack-dev] Project list (official & un-official)

Thanks!! On Jan 8, 2015 5:09 AM, "Thierry Carrez" wrote: > Adam Lawson wrote: > > I've been looking for a list of projects that folks are working on. The > > official list is simple to find for those but when talking about things > > like Octavia, Libra and other non-official/non-core programs, k

Re: [openstack-dev] The scope of OpenStack wiki [all]

Thanks for bringing this up Stef. I have found while introducing OpenStack fundamentals in the user groups, what seems logical to us, the fully OpenStack immersed, is confusing to newcomers. A specific example comes from the How To Contribute wikipage. Explaining the corporate CLA and CCLA li

[openstack-dev] [Telco][NFV] Selection of Use Case to do a deep dive on for next week's meeting

Hi all, At the meeting this week we discussed selecting one of the submitted use cases to perform a deep dive on next week. I've put together a quick survey based on the items currently listed on the wiki [1]: https://www.surveymonkey.com/s/N9JWN76 There are two other use cases I am aware

Re: [openstack-dev] [stable][neutron] minimal dnsmasq version

On Thu, Jan 08, 2015 at 11:53:24AM EST, Carl Baldwin wrote: > On Wed, Jan 7, 2015 at 9:25 PM, Kevin Benton wrote: > > If the new requirement is expressed in the neutron packages for the distro, > > wouldn't it be transparent to the operators? > > I think the difficulty first lies with the distros

Re: [openstack-dev] 答复: Re: [neutron][AdvancedServices] Confusion about the solution of the service chaining!

Hi Alan, On Wed, Jan 7, 2015 at 9:54 PM, wrote: > Hi Sumit, > > thanks for your reply, one more question, > > If I just using the 'group-based-policy-service-chaining' to developing the > service chaining feuture, how to map the network service in the neutron to > the GBP model, because all the

[openstack-dev] oslo.i18n 1.3.0 released

The Oslo team is pleased to announce the release of oslo.i18n 1.3.0: oslo.i18n library This release adds a new fixture for forcing the lazy translation feature on or off for the duration of a single test job. For more details, please see the git log history below and http://launchpad.net/oslo.i1

Re: [openstack-dev] [nova] [qa] EC2 status and call for assistance

On 4/25/2014 4:13 AM, Alexandre Levine wrote: Joe, In regard to your first question - yes we'll be going in this direction very soon. It's being discussed with Randy now. As for the second question - we'd love to participate in fixing it (in fact we've done it for OCS already) and probably mai

Re: [openstack-dev] [Neutron][L3] Stop agent scheduling without topping sevices

There must be other OpenStack services which have also faced this ‘stop scheduling but keep replying’ issues. Can we make the names for the various states and transitions consistent ? Tim From: Kyle Mestery [mailto:mest...@mestery.com] Sent: 08 January 2015 16:26 To: OpenStack Development Maili

[openstack-dev] [Nova] Kilo Release Status - just passed spec freeze

Hi all, With the release of kilo-1 we have frozen the approval of new specs for kilo. This is to make sure we can focus on our agreed kilo priorities: http://specs.openstack.org/openstack/nova-specs/priorities/kilo-priorities.html As always, there are exceptions, here is how: 1) email ML, "[nov

Re: [openstack-dev] [nova] Host health monitoring

On Sun, Jan 4, 2015 at 7:08 PM, Andrew Beekhof wrote: > > > On 9 Dec 2014, at 1:20 am, Roman Dobosz wrote: > > > > On Wed, 3 Dec 2014 08:44:57 +0100 > > Roman Dobosz wrote: > > > >> I've just started to work on the topic of detection if host is alive or > >> not: https://blueprints.launchpad.ne

Re: [openstack-dev] [heat][tripleo] Making diskimage-builder install from forked repo?

Excerpts from Chris Jones's message of 2015-01-08 10:16:14 -0800: > Hi > > > On 8 Jan 2015, at 17:58, Clint Byrum wrote: > > > > Excerpts from Steven Hardy's message of 2015-01-08 09:37:55 -0800: > > So you can probably setup a devpi instance locally, and upload the > > commits you want to it, a

[openstack-dev] The scope of OpenStack wiki [all]

hello folks, TL;DR Many wiki pages and categories are maintained elsewhere and to avoid confusion to newcomers we need to agree on a new scope for the wiki. A suggestion below is to limit its scope to content that doesn't need/want peer-review and is not hosted elsewhere (no duplication). The wik

Re: [openstack-dev] [stable] Proposal to add Flavio Percoco to stable-maint-core

+2. How contributions have always been helpful. On Jan 7, 2015 8:50 AM, "Alan Pevec" wrote: > +2 Flavio knows stable branch policies very well and will be a good > addition to the cross-projects stable team. > > Cheers, > Alan > > ___ > OpenStack-dev ma

Re: [openstack-dev] [oslo] dropping namespace packages

On 01/08/2015 07:03 PM, Doug Hellmann wrote: I’m not sure that’s something we need to enforce. Liaisons should be updating projects now as we release libraries, and then we’ll consider whether we can drop the namespace packages when we plan the next cycle. Without a hacking rule, there is a c

[openstack-dev] Fwd: [Openstack-stable-maint] Stable check of openstack/cinder failed

I have a patch out to resolve this failure: https://review.openstack.org/145642 Jay -- Forwarded message -- From: "A mailing list for the OpenStack Stable Branch test reports." < openstack-stable-ma...@lists.openstack.org> Date: Jan 8, 2015 1:40 AM Subject: [Openstack-stable-maint]

Re: [openstack-dev] [oslo] dropping namespace packages

OK, I was going to implement something for neutron, but if you're going to handle it quickly till the end of the week, I'll wait to steal. ;) On 01/08/2015 07:14 PM, Jay Bryant wrote: We talked about this in Cinder. I am planning to create some hacking checks for us just to be safe. Should

Re: [openstack-dev] Support for Amazon VPC APIs in OpenStack

On Tue, Jan 6, 2015 at 5:10 AM, Jay Pipes wrote: > On 01/06/2015 12:44 AM, Saju M wrote: > >> Hi, >> >> I seen a blueprint which implement Amazon VPC APIs and Status is Abandoned >> https://review.openstack.org/#/c/40071/ > > The amazon VPC effort has moved to http://git.openstack.org/cgit/stackf

Re: [openstack-dev] [heat][tripleo] Making diskimage-builder install from forked repo?

Excerpts from Gregory Haynes's message of 2015-01-08 18:06:16 +: > Excerpts from Steven Hardy's message of 2015-01-08 17:37:55 +: > > Hi all, > > > > I'm trying to test a fedora-software-config image with some updated > > components. I need: > > > > - Install latest master os-apply-confi

Re: [openstack-dev] [heat][tripleo] Making diskimage-builder install from forked repo?

Hi > On 8 Jan 2015, at 17:58, Clint Byrum wrote: > > Excerpts from Steven Hardy's message of 2015-01-08 09:37:55 -0800: > So you can probably setup a devpi instance locally, and upload the > commits you want to it, and then build the image with the 'pypi' element Given that we have a pretty goo

Re: [openstack-dev] [oslo] dropping namespace packages

We talked about this in Cinder. I am planning to create some hacking checks for us just to be safe. Shouldn't take a ton of effort. Jay On Jan 8, 2015 12:03 PM, "Doug Hellmann" wrote: > > > On Jan 8, 2015, at 11:29 AM, Ihar Hrachyshka > wrote: > > > > On 01/05/2015 04:51 PM, Doug Hellmann wr

Re: [openstack-dev] [Openstack-operators] The state of nova-network to neutron migration

On 01/08/2015 08:30 AM, Jakub Libosvar wrote: > On 12/24/2014 10:07 AM, Oleg Bondarev wrote: >> >> >> On Mon, Dec 22, 2014 at 10:08 PM, Anita Kuno > > wrote: >> >> On 12/22/2014 01:32 PM, Joe Gordon wrote: >> > On Fri, Dec 19, 2014 at 9:28 AM, Kyle Mestery >

Re: [openstack-dev] [heat][tripleo] Making diskimage-builder install from forked repo?

Excerpts from Steven Hardy's message of 2015-01-08 17:37:55 +: > Hi all, > > I'm trying to test a fedora-software-config image with some updated > components. I need: > > - Install latest master os-apply-config (the commit I want isn't released) > - Install os-refresh-config fork from https:

Re: [openstack-dev] [oslo] dropping namespace packages

> On Jan 8, 2015, at 11:29 AM, Ihar Hrachyshka wrote: > > On 01/05/2015 04:51 PM, Doug Hellmann wrote: >> As each library is released, we will send release notes to this list, as >> usual. At that point the Oslo liaisons should start planning patches to >> change imports in their projects from

Re: [openstack-dev] [Heat] Precursor to Phase 1 Convergence

On Thu, Jan 08, 2015 at 09:53:02PM +0530, vishnu wrote: >Hi Zane, >I was wondering if we could push changes relating to backup stack removal >and to not load resources as part of stack. There needs to be a capability >to restart jobs left over by dead engines.A >something like

Re: [openstack-dev] [heat][tripleo] Making diskimage-builder install from forked repo?

Excerpts from Steven Hardy's message of 2015-01-08 09:37:55 -0800: > Hi all, > > I'm trying to test a fedora-software-config image with some updated > components. I need: > > - Install latest master os-apply-config (the commit I want isn't released) > - Install os-refresh-config fork from https:

Re: [openstack-dev] [heat][tripleo] Making diskimage-builder install from forked repo?

Hi > On 8 Jan 2015, at 17:37, Steven Hardy wrote: > Pretty sure there's a way to make DiB do this, but don't know what, anyone > able to share some clues? Do I have to hack the elements, or is there a > better way? > > The docs are pretty sparse, so any help would be much appreciated! :) We d

[openstack-dev] [heat][tripleo] Making diskimage-builder install from forked repo?

Hi all, I'm trying to test a fedora-software-config image with some updated components. I need: - Install latest master os-apply-config (the commit I want isn't released) - Install os-refresh-config fork from https://review.openstack.org/#/c/145764 I can't even get the o-a-c from master part wo

Re: [openstack-dev] [Cinder] volume / host coupling

Arne, >I imagine this has an >impact on things using the services table, such as “cinder-manage” (how >does your “cinder-manage service list” output look like? :-) It has indeed. I have 3 cinder-volume services, but only one line output in “cinder-manage service list”. But it's a minor inconvenie

Re: [openstack-dev] [stable][neutron] minimal dnsmasq version

On Wed, Jan 7, 2015 at 9:25 PM, Kevin Benton wrote: > If the new requirement is expressed in the neutron packages for the distro, > wouldn't it be transparent to the operators? I think the difficulty first lies with the distros. If the required new version isn't in an older version of the distro

[openstack-dev] [nova] request spec freeze exception for Enhance iSCSI multipath/failover support

Hi, I have submitted 2 nova-specs [1][2] related to Cinder volumes iSCSI multipath/failover improvement. These specs are both for enabling Cinder to pass multiple iSCSI paths to Nova. [1] is for multipath use-case, where Nova will establish iSCSI sessions to all the given paths. [2] is for failov

[openstack-dev] What's Up Doc? Jan 8 2015

Welcome to 2015, all. Here's the latest in the docs world. Web design for landing page is nearly done. Needs testing, so please take a look at the output [0] in your favorite browser and let us know any issues on the review patch itself. [1] Web design plan [2] is to convert the End User Guide ne

Re: [openstack-dev] [Cinder] volume / host coupling

Hi Jordan, As Duncan pointed out there may be issues if you have multiple backends and indistinguishable nodes (which you could probably avoid by separating the hosts per backend and use different “host” flags for each set). But also if you have only one backend: the “host" flag will enter the ‘

Re: [openstack-dev] [oslo] dropping namespace packages

On 01/05/2015 04:51 PM, Doug Hellmann wrote: As each library is released, we will send release notes to this list, as usual. At that point the Oslo liaisons should start planning patches to change imports in their projects from "oslo.foo" to “oslo_foo". The old imports should still work for now

[openstack-dev] [Heat] Precursor to Phase 1 Convergence

Hi Zane, I was wondering if we could push changes relating to backup stack removal and to not load resources as part of stack. There needs to be a capability to restart jobs left over by dead engines. something like heat stack-operation --continue [git rebase --continue] Had a chat with shady re

Re: [openstack-dev] [TripleO] default region name

On 01/08/2015 06:38 AM, Zhou, Zhenzan wrote: > Thank you, Derek. > So we could also change TripleO register-endpoint/setup-endpoint to use > "RegionOne". Our policy in TripleO is to use project defaults whenever possible, in the interest of making sure our project defaults are sane for all users.

Re: [openstack-dev] [Cinder] volume / host coupling

There are races, e.g. do snapshot and delete at the same time, backup and delete at the same time, etc. The race windows are pretty tight on ceph but they are there. It is worse on some other backends On 8 January 2015 at 17:50, Jordan Pittier wrote: > Hi, > >Some people apparently use the ‘host

Re: [openstack-dev] [Cinder] volume / host coupling

Hi, >Some people apparently use the ‘host’ option in cinder.conf to make the hosts indistinguishable, but this creates problems in other places. I use shared storage mounted on several cinder-volume nodes, with "host" flag set the same everywhere. Never ran into problems so far. Could you elaborate

Re: [openstack-dev] [Neutron][L3] Stop agent scheduling without topping sevices

On Thu, Jan 8, 2015 at 8:49 AM, McCann, Jack wrote: > +1 on need for this feature > > The way I've thought about this is we need a mode that stops the > *automatic* > scheduling of routers/dhcp-servers to specific hosts/agents, while allowing > manual assignment of routers/dhcp-servers to those h

[openstack-dev] [stable] Swift object-updater and container-updater

Hi, to whom it may concern: Jay Bryant and I would like to have the fixes for the Swift object-updater (https://review.openstack.org/#/c/125746/) and the Swift container-updater ( https://review.openstack.org/#/q/I7eed122bf6b663e6e7894ace136b6f4653db4985,n,z ) backported to Juno and then to Ice

Re: [openstack-dev] [Neutron][L3] Stop agent scheduling without topping sevices

+1 on need for this feature The way I've thought about this is we need a mode that stops the *automatic* scheduling of routers/dhcp-servers to specific hosts/agents, while allowing manual assignment of routers/dhcp-servers to those hosts/agents, and where any existing routers/dhcp-servers on those

[openstack-dev] [nova] Request Spec Freeze Exception for: Remove direct nova DB/API access in Scheduler Filters

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, This spec [1] has been on hold, as it was largely dependent on another spec [2] being approved first, as it has very similar requirements. Now that the latter has been approved, I am moving forward with the former. It is part of the scheduler clea

Re: [openstack-dev] [qa] Using DevStack for multi-node setup

On Mon, Jan 05, 2015 at 08:20:48AM -0500, Sean Dague wrote: > On 01/03/2015 04:41 PM, Danny Choi (dannchoi) wrote: > > Hi, > > > > I’m using DevStack to deploy OpenStack on a multi-node setup: > > Controller, Network, Compute as 3 separate nodes > > > > Since the Controller node is stacked first,

Re: [openstack-dev] [Cinder] volume / host coupling

Hmm. Not sure how widespread installations with multiple Ceph backends are where the Cinder hosts have access to only one of the backends (which is what you assume, right?) But, yes, if the volume type names are also the same (is that also needed for this to be a problem?), this will be an issue

[openstack-dev] [nova] request spec freeze exception for Improving performance of unshelve-api

Hi Devs, I have submitted a nova-spec [1] for improving the performance of unshelve-api. The aim of this feature is to improve the performance of unshelve instance by eliminating downloading/copying snapshot time. All instance files will be retained in the instance store backed by shared or non

[openstack-dev] oslo.utils 1.2.0 released

The Oslo team is pleased to announce the release of oslo.utils 1.2.0: Oslo Utility library There are two big changes in this release: 1. We have moved the code out of the oslo namespace package as part of https://blueprints.launchpad.net/oslo-incubator/+spec/drop-namespace-packages 2. The perfor

Re: [openstack-dev] Mirantis Openstack 5.1 environment issues

Hi Pavankumar, this is public mailing list for development questions regarding OpenStack and open source stackforge projects. While Mirantis OpenStack heavily relies on Fuel, open source tool for installation and management of OpenStack environment, this is not the right channel to discuss issues b

Re: [openstack-dev] [TripleO][keystone] default region name

On Thu, Jan 8, 2015 at 7:28 AM, Steven Dake wrote: > On 01/07/2015 10:21 PM, Zhou, Zhenzan wrote: > >> Hi, >> >> Does anyone know why TripleO uses "regionOne" as default region name? A >> comment in the code says it's the default keystone uses. >> > > Zhenzan, > > I was going to point you here: >

Re: [openstack-dev] [Cinder] volume / host coupling

The problem is that the scheduler doesn't currently have enough info to know which backends are 'equivalent' and which aren't. e.g. If you have 2 ceph clusters as cinder backends, they are indistinguishable from each other. On 8 January 2015 at 12:14, Arne Wiebalck wrote: > Hi, > > The fact that

Re: [openstack-dev] [stable][neutron] minimal dnsmasq version

On 01/07/2015 03:21 PM, Ihar Hrachyshka wrote: Hi all, I've found out that dnsmasq < 2.67 does not work properly for IPv6 clients when it comes to MAC address matching (it fails to match, and so clients get 'no addresses available' response). I've requested version bump to 2.67 in: https://re

Re: [openstack-dev] [Openstack-operators] The state of nova-network to neutron migration

On 12/24/2014 10:07 AM, Oleg Bondarev wrote: > > > On Mon, Dec 22, 2014 at 10:08 PM, Anita Kuno > wrote: > > On 12/22/2014 01:32 PM, Joe Gordon wrote: > > On Fri, Dec 19, 2014 at 9:28 AM, Kyle Mestery > wrote: > > > >

Re: [openstack-dev] [TripleO][keystone] default region name

On 01/07/2015 10:21 PM, Zhou, Zhenzan wrote: Hi, Does anyone know why TripleO uses "regionOne" as default region name? A comment in the code says it's the default keystone uses. Zhenzan, I was going to point you here: https://bugs.launchpad.net/keystone/+bug/1400589 But I see you already h

Re: [openstack-dev] Mirantis Openstack 5.1 environment issues

> 1) Verify network got failed with message Expected VLAN (not > received) untagged at the interface Eth1 of controller and compute nodes. > > In our set-up Eth1 is connected to the public network, which we disconnect > from public network while doing deployment operation as FUEL itself works

Re: [openstack-dev] [stable] Proposing to add Lin-Hua Cheng to horizon-stable-maint

Matthias Runge wrote: > I'd like to propose to add Lin-Hua Cheng to horizon-stable-maint. > > Lin has been a Horizon Core for a long time and has expressed interest > in helping out with horizon stable reviews. > > I think, he'll make a great addition! We'll need the Horizon PTL to confirm the a

Re: [openstack-dev] Project list (official & un-official)

Adam Lawson wrote: > I've been looking for a list of projects that folks are working on. The > official list is simple to find for those but when talking about things > like Octavia, Libra and other non-official/non-core programs, knowing > what people are working on would be pretty interesting. >

[openstack-dev] Mirantis Openstack 5.1 environment issues

Hi Fuel Team, Hope you are doing good. We are facing issues in Mirantis Openstack 5.1 environment as below; 1) Verify network got failed with message Expected VLAN (not received) untagged at the interface Eth1 of controller and compute nodes. In our set-up Eth1 is connected to

[openstack-dev] [sahara] team meeting Jan 8 1800 UTC

Hi folks, We'll be having the Sahara team meeting as usual in #openstack-meeting-alt channel. Agenda: https://wiki.openstack.org/wiki/Meetings/SaharaAgenda#Next_meetings http://www.timeanddate.com/worldclock/fixedtime.html?msg=Sahara+Meeting&iso=20150108T18 -- Sincerely yours, Sergey Lukjanov

Re: [openstack-dev] [horizon] static files handling, bower/

On 06/01/15 01:53, Richard Jones wrote: > I think the only outstanding question is how developers and > non-packagers populate the bower_components directory - that is, how is > bower expected to be available for them? > > I think following the Storyboard approach is a good idea: isolate a > known

Re: [openstack-dev] [TripleO] default region name

Thank you, Derek. So we could also change TripleO register-endpoint/setup-endpoint to use "RegionOne". BR Zhou Zhenzan -Original Message- From: Derek Higgins [mailto:der...@redhat.com] Sent: Thursday, January 8, 2015 5:53 PM To: OpenStack Development Mailing List (not for usage questions

Re: [openstack-dev] [Ironic] ironic-discoverd status update

Sounds like we could add something new to automate the enrollment of new nodes:-) Collecting IPMI info into a csv file is still a trivial job... BR Zhou Zhenzan -Original Message- From: Dmitry Tantsur [mailto:dtant...@redhat.com] Sent: Thursday, January 8, 2015 5:19 PM To: openstack-dev

Re: [openstack-dev] [stable][neutron] minimal dnsmasq version

I think it should be possible to have a sanity check like the following: < 2.63 - sorry, that's not going to work >=2.63, <2.67 - it kind of works but ipv6 is going to be messed up >2.67 - we're all right The runtime check on the dhcp agent is a startup check. Personally I think agents should run

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

On 08-Jan-15 16:09, Anant Patil wrote: > On 16-Dec-14 09:41, Zane Bitter wrote: >> On 15/12/14 09:32, Anant Patil wrote: >>> On 12-Dec-14 06:29, Zane Bitter wrote: On 11/12/14 01:14, Anant Patil wrote: > On 04-Dec-14 10:49, Zane Bitter wrote: >> On 01/12/14 02:02, Anant Patil wrote: >>

Re: [openstack-dev] [nova] deleting the pylint test job

On Mon, Nov 24, 2014 at 12:52:07PM -0500, Sean Dague wrote: > The pylint test job has been broken for weeks, no one seemed to care. > While waiting for other tests to return today I looked into it and > figured out the fix. > > However, because of nova objects pylint is progressively less and less

Re: [openstack-dev] [stable][neutron] minimal dnsmasq version

I agree, that is one thing we should not check in runtime. In ideal world, it wouldn't even check version number, but capabilities. I's not clear though whether we can be any smarter than that (we would need to run dnsmasq and real dhcp clients to check actual capabilities). /Ihar On 01/08/2

Re: [openstack-dev] [stable][neutron] minimal dnsmasq version

Now that I re-read the patch. Shouldn't the version checking need to be converted into a sanity check? Miguel Ángel Ajo On Thursday, 8 de January de 2015 at 12:51, Kevin Benton wrote: > Thanks for the insight. > > On Thu, Jan 8, 2015 at 3:41 AM, Miguel Ángel Ajo (mailto:majop...@redhat.com)

Re: [openstack-dev] [stable][neutron] minimal dnsmasq version

Thanks for the insight. On Thu, Jan 8, 2015 at 3:41 AM, Miguel Ángel Ajo wrote: > Correct, that’s the problem, what Kevin said should be the ideal case, but > distros have > proven to fail satisfying this kind of requirements earlier. > > So at least a warning to the user may be good to have IMH

Re: [openstack-dev] [stable][neutron] minimal dnsmasq version

Correct, that’s the problem, what Kevin said should be the ideal case, but distros have proven to fail satisfying this kind of requirements earlier. So at least a warning to the user may be good to have IMHO. Miguel Ángel Ajo On Thursday, 8 de January de 2015 at 12:36, Ihar Hrachyshka wrote:

  1   2   >