[openstack-dev] [Heat] About the DEFAULT_PAGE_SIZE

Hi, all Just notice there're several DEFAULT_PAGE_SIZE=20 lines inside the latest python-heatclient package, e.g., $ grep DEFAULT_PAGE_SIZE . -r ./heatclient/v1/actions.py:DEFAULT_PAGE_SIZE = 20 ./heatclient/v1/events.py:DEFAULT_PAGE_SIZE = 20 ./heatclient/v1/resources.py:DEFAULT_PAGE_SIZE =

[openstack-dev] [Glance][Stable] Review request for stable/icehouse patch

Hello All, I have submitted a back-port patch to stable/icehouse, for which I've cherry picked https://review.openstack.org/#/c/128301/ and made few additional changes. This is not 1:1 cherry pick from the one that landed to master as the retrying module is not available in the stable/icehouse.

Re: [openstack-dev] [Fuel] fuel master monitoring

This I didn't know. It's true in fact, I checked the manifests. Though monit is not deployed yet because of lack of packages in Fuel ISO. Anyways, I think the argument about using yet another monitoring service is now rendered invalid. So +1 for monit? :) P. On 11/26/2014 05:55 PM, Sergii Go

Re: [openstack-dev] [neutron] - the setup of a DHCP sub-group

Sure, will try and gen to it over the holiday, do you have a link to the spec repo? On Mon, Nov 24, 2014 at 3:27 PM, Carl Baldwin wrote: > Don, > > Could the spec linked to your BP be moved to the specs repository? > I'm hesitant to start reading it as a google doc when I know I'm going > to wan

Re: [openstack-dev] [All] Proposal to add examples/usecase as part of new features / cli / functionality patches

But isn't *-specs comes very early in the process where you have an idea/proposal of a feature, u don't have it yet implemented. Hence specs just end up with Para's on how the feature is supposed to work, but doesn't include any real world screen shots as the code is not yet ready at that point of

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

On Thu, Nov 27, 2014 at 12:20 PM, Zane Bitter wrote: > A bunch of us have spent the last few weeks working independently on proof > of concept designs for the convergence architecture. I think those efforts > have now reached a sufficient level of maturity that we should start > working together

Re: [openstack-dev] [heat] [CustomResource] LifeCycle methods flow

Thanks, Zane. I do understand the mistake I made (too much dependency on ctags). I am getting what you're pointing out. In face inside my _resolve_attribute, I should have return self.properties['value'] instead of depending on the cached value. I wanted to understand if it is OK to cache value

Re: [openstack-dev] [All] Proposal to add examples/usecase as part of new features / cli / functionality patches

On Wed, Nov 26, 2014 at 1:15 PM, Steve Gordon wrote: > - Original Message - > > From: "Deepak Shetty" > > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > > > > Hi stackers, > >I was having this thought which i believe applie

Re: [openstack-dev] [Oslo][Neutron] Fork() safety and oslo.messaging

I've come up with a patch to the amqp 1.0 driver that resets the connection state if the pid of the current process is different from the process that has created the connection: https://review.openstack.org/#/c/134684/ I've managed to get this to work using rpc_workers=4 in neutron.conf, which f

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

A bunch of us have spent the last few weeks working independently on proof of concept designs for the convergence architecture. I think those efforts have now reached a sufficient level of maturity that we should start working together on synthesising them into a plan that everyone can forge ah

[openstack-dev] 答复: [Neutron][L2 Agent][Debt] Bootstrapping an L2 agent debt repayment task force

My name is also on the etherpad, I'd like to take part in these works. -邮件原件- 发件人: marios [mailto:mar...@redhat.com] 发送时间: 2014年11月19日 18:10 收件人: openstack-dev@lists.openstack.org 主题: Re: [openstack-dev] [Neutron][L2 Agent][Debt] Bootstrapping an L2 agent debt repayment task force On 19

[openstack-dev] [all] UserWarning: Unknown distribution option: 'pbr'

Hello, I write a module to extend openstack. When install by python setup.py develop, it always blame this /usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'pbr' warnings.warn(msg) running develop running egg_info creating UNKNOWN.egg-info writing UNKNOWN.e

Re: [openstack-dev] [neutron] - the setup of a DHCP sub-group

Hi Don, You should look at this one: https://wiki.openstack.org/wiki/NeutronSubteamCharters Also, it would be good to start feeding the content of that gdoc into a neutron-specs blueprint, using template [1] and process [2], bearing in mind these dates [3] 1. http://git.openstack.org/cgit/opens

[openstack-dev] [qa] How to perform VMs live migration?

Hi, When I try “nova host-evacuate-live”, I I got the following error: Error while live migrating instance: tme209 is not on shared storage: Live migration can not be used without shared storage. What do I need to do to create a shared storage? Thanks, Danny __

Re: [openstack-dev] [sahara] Asia friendly IRC meeting time

Thank you all! On Thu, Nov 27, 2014 at 1:15 AM, Sergey Lukjanov wrote: > I think that 6 am for US west works much better than 3 am for Saratov. > > So, I'm ok with keeping current time and add 1400 UTC. > >18:00UTC: Moscow (9pm) China(2am) US West(10am)/US East (1pm) >14:00UTC: Moscow

Re: [openstack-dev] [QA][Tempest] Proposing Ghanshyam Mann for Tempest Core

Thank you very much all of you. It's a honor to be part of Tempest core team. I will give my best for the team. On Thu, Nov 27, 2014 at 12:06 AM, Matthew Treinish wrote: > > So all of the current core team members have voted unanimously in favor of > adding Ghanshyam to the team. > > Welcome to

Re: [openstack-dev] [nova] How should libvirt pools work with distributed storage drivers?

On Wed, Nov 26, 2014 at 10:26 PM, Solly Ross wrote: > Hi! >> >> Some days ago, a bunch of Nova specs were approved for Kilo. Among them was >> https://blueprints.launchpad.net/nova/+spec/use-libvirt-storage-pools >> >> Now, while I do recognize the wisdom of using storage pools, I do see a >> coup

[openstack-dev] [NFV][Telco] Telco Working Group meeting minutes (2014-11-26)

Hi all, Please find minutes and logs for the Telco Working Group meeting held at 2200 UTC on Wednesday the 26th of November at the following locations: * Meeting ended Wed Nov 26 23:03:04 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) * Minutes: http:

Re: [openstack-dev] [NFV][Telco] pxe-boot

- Original Message - > From: "Angelo Matarazzo" > To: "OpenStack Development Mailing" , > openstack-operat...@lists.openstack.org > > > Hi all, > my team and I are working on pxe boot feature very similar to the > "Discless VM" one in Active blueprint list[1] > The blueprint [2] is no

Re: [openstack-dev] [heat] [CustomResource] LifeCycle methods flow

On 26/11/14 05:20, Pradip Mukhopadhyay wrote: Hello, Any pointer (document and/or code pointer) related to how the different overridden methods are getting called when a custom resource is getting deployed in the heat stack? Basically just tried to annotate the h-eng log on a simple, very-fi

Re: [openstack-dev] [api] Counting resources

detail=concise is not a media type and looking at the grammar in the RFC it wouldn’t be valid. I think the grammar would allow for "application/json; detail=concise". See the last line in the definition of the "media-range" nonterminal in the grammar (copied below for convenience): Acce

[openstack-dev] [stable] Proposal to add Dave Walker back to stable-maint-core

Hi All- Daviey was an original member of the stable-maint team and one of the driving forces behind the creation of the team and branches back in the early days. He was removed from the team later on during a pruning of inactive members. Recently, he has began focusing on the stable branches again

Re: [openstack-dev] [api] Counting resources

On Nov 20, 2014, at 4:06 PM, Eoghan Glynn mailto:egl...@redhat.com>> wrote: How about allowing the caller to specify what level of detail they require via the Accept header? ▶ GET // Accept: application/json; detail=concise "The Accept request-header field can be used to specify certain media

Re: [openstack-dev] [Nova] Handling soft delete for instance rows in a new cells database

Mike Bayer wrote: Precisely. Why is the RDBMS the thing that is used for archival/audit logging? Why not a NoSQL store or a centralized log facility? All that would be needed would be for us to standardize on the format of the archival record, standardize on the things to provide with the arch

[openstack-dev] [stable][sahara] Sahara is broken in stable/juno

Hi, Sahara is broken in stable/juno now by new alembic release (unit tests). The patch is already done and approved for master [0] and I've already backported it to the stable/juno branch [1]. [0] https://review.openstack.org/#/c/137035/ [1] https://review.openstack.org/#/c/137469/ P.S. If anyon

Re: [openstack-dev] [Nova] Handling soft delete for instance rows in a new cells database

On 11/26/2014 03:39 PM, Belmiro Moreira wrote: Hi, my experience is that "soft delete" is important to keep record of deleted instances and its characteristics. In fact in my organization we are obliged to keep these records for several months. However, it would be nice that after few months w

Re: [openstack-dev] [Nova] Handling soft delete for instance rows in a new cells database

> > Precisely. Why is the RDBMS the thing that is used for archival/audit > logging? Why not a NoSQL store or a centralized log facility? All that would > be needed would be for us to standardize on the format of the archival > record, standardize on the things to provide with the archival rec

Re: [openstack-dev] Where should Schema files live?

On 11/20/2014 08:12 AM, Sandy Walsh wrote: Hey y'all, To avoid cross-posting, please inform your -infra / -operations buddies about this post. We've just started thinking about where notification schema files should live and how they should be deployed. Kind of a tricky problem. We could rea

Re: [openstack-dev] [Nova] Handling soft delete for instance rows in a new cells database

Hi, my experience is that "soft delete" is important to keep record of deleted instances and its characteristics. In fact in my organization we are obliged to keep these records for several months. However, it would be nice that after few months we were able to purge the DB with a nova tool. In th

Re: [openstack-dev] [Nova] Handling soft delete for instance rows in a new cells database

On 11/25/2014 09:34 PM, Mike Bayer wrote: On Nov 25, 2014, at 8:15 PM, Ahmed RAHAL wrote: Hi, Le 2014-11-24 17:20, Michael Still a écrit : Heya, This is a new database, so its our big chance to get this right. So, ideas welcome... Some initial proposals: - we do what we do in the current

Re: [openstack-dev] [sahara] team meeting Nov 27 1800 UTC

Thanks for the note, it sounds like we could cancel the meeting this week because of it... Anybody except Russian team folks planning to attend the meeting this week? On Wed, Nov 26, 2014 at 9:44 PM, Matthew Farrellee wrote: > On 11/26/2014 01:10 PM, Sergey Lukjanov wrote: > >> Hi folks, >> >> W

Re: [openstack-dev] [nova] How should libvirt pools work with distributed storage drivers?

Hi! > > Some days ago, a bunch of Nova specs were approved for Kilo. Among them was > https://blueprints.launchpad.net/nova/+spec/use-libvirt-storage-pools > > Now, while I do recognize the wisdom of using storage pools, I do see a > couple of possible problems with this, especially in the light

Re: [openstack-dev] [oslo][kite] oslo.messaging changes for message security

On 11/14/2014 08:38 AM, Doug Hellmann wrote: > > On Nov 13, 2014, at 8:47 PM, Jamie Lennox wrote: > >> Hi all, >> >> To implement kite we need the ability to sign and encrypt the message and the >> message data. This needs to happen at a very low level in the oslo.messaging >> stack. The existin

Re: [openstack-dev] [oslo] scheduling a review day

We talked about this in the meeting this week, but just for the record I should be able to make it too. -Ben On 11/21/2014 11:07 AM, Doug Hellmann wrote: > We have a bit of a backlog in the Oslo review queue. Before we add a bunch of > new reviews for Kilo work, I’d like to see if we can clear s

Re: [openstack-dev] #Personal# Ref: L3 service integration with service framework

There is already an out-of-tree L3 plugin, and as part of the plugin decomposition work, I'm planning to use this as the base for the new ODL driver in Kilo. Before you file specs and BPs, we should talk a bit more. Thanks, Kyle [1] https://github.com/dave-tucker/odl-neutron-drivers On Wed, Nov

Re: [openstack-dev] [Keystone] Splitting up the assignment component

On 11/26/2014 09:52 AM, David Chadwick wrote: I tend to agree with Morgan. There are resources and there are users. And there is something in the middle that says which users can access which resources. It might be an ACL, a RBAC role, or a set of ABAC attributes, or something else (such as a MAC

[openstack-dev] [Cue] project update

Hello, Thanks to those who I met personally at the Summit for your feedback on the project. For those that don’t know what Cue is, we’re building a Message Broker Provisioning service for Openstack. More info can be found here: https://wiki.openstack.org/wiki/Cue Since the summit, we’re working

Re: [openstack-dev] [All] Proposal to add examples/usecase as part of new features / cli / functionality patches

- Original Message - > From: "Deepak Shetty" > To: "OpenStack Development Mailing List (not for usage questions)" > > > Hi stackers, >I was having this thought which i believe applies to all projects of > openstack (Hence All in the subject tag) > > My proposal is to have examples

Re: [openstack-dev] [Telco] [NFV] [Heat] Telco Orchestration

Hi Mathieu, >Can you tell us more about those projects? Does it include >mutli-datacenter use cases? Most of this work was done as a custom projects for customers. I have to ask them for a permission to share details. We do not support multi-datacenter placement officially, but this feature was d

Re: [openstack-dev] #Personal# Ref: L3 service integration with service framework

+1. In the ODL case you would just want a completely separate L3 plugin. On Wed, Nov 26, 2014 at 7:29 AM, Mathieu Rohon wrote: > Hi, > > you can still add your own service plugin, as a mixin of > L3RouterPlugin (have a look at brocade's code). > AFAIU service framework would manage the coexisten

Re: [openstack-dev] [sahara] team meeting Nov 27 1800 UTC

On 11/26/2014 01:10 PM, Sergey Lukjanov wrote: 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=2

Re: [openstack-dev] [Fuel] fuel master monitoring

On 11/26/2014 11:54 AM, Sergii Golovatiuk wrote: Jay, Fuel uses watchdog service for container to restart it in case of issues. We have the same problem with containers when disk is full I see. I guess I don't quite understand why Zabbix isn't just used for everything -- after all, the puppet

[openstack-dev] [sahara] team meeting Nov 27 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=20141127T18 -- Sincerely yours, Sergey Lukjanov

Re: [openstack-dev] Issues regarding Jenkins on Gerrit reviews

Looks like the same bug affecting oslo libraries, clients (likely anyone with that similarily named icehouse job): https://bugs.launchpad.net/tempest/+bug/1395368 (likely neutrons real issue), see bug for a potential resolution review that seems to be going through the tubes. ER query review

Re: [openstack-dev] [Rally] Question on periodic task

Hi Boris Looks like this would require changes in key portions of Rally infra. Need some more time getting a hang of rally by committing a few scenarios before I make infra changes Ajay From: Boris Pavlovic mailto:bo...@pavlovic.me>> Reply-To: "OpenStack Development Mailing List (not for usag

[openstack-dev] [rally] Rally scenario for network scale with VMs

Hi Is there a Rally scenario under works where we create N networks and associate N Vms with each network. This would be a decent stress tests of neutron Is there any such scale scenario in works I see scenario for N networks, subnet creation and a separate one for N VM bootups I am looking for

Re: [openstack-dev] [nova] Proposal new hacking rules

On 26/11/14 09:33, Louis Taylor wrote: On Wed, Nov 26, 2014 at 08:54:35AM -0500, Jay Pipes wrote: It's not about an equality condition. It's about the message that is produced by testtools.TestCase.assertEqual(), and the helpfulness of that message when the order of the arguments is reversed.

Re: [openstack-dev] [oslo] python 2.6 support for oslo libraries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/26/2014 07:48 AM, Julien Danjou wrote: > On Wed, Nov 26 2014, Andreas Jaeger wrote: > >> The libraries have 2.6 support enabled as discussed - but if >> indeed some are missing, please send patches, > > So to recap, it seems to me the plan is t

Re: [openstack-dev] [sahara] Asia friendly IRC meeting time

I think that 6 am for US west works much better than 3 am for Saratov. So, I'm ok with keeping current time and add 1400 UTC. 18:00UTC: Moscow (9pm) China(2am) US West(10am)/US East (1pm) 14:00UTC: Moscow (5pm) China(10pm) US (W 6am / E 9am) I think it's the best option to make all of

Re: [openstack-dev] [diskimage-builder] Tracing levels for scripts (119023)

On 11/25/2014 10:58 PM, Ian Wienand wrote: > Hi, > > My change [1] to enable a consistent tracing mechanism for the many > scripts diskimage-builder runs during its build seems to have hit a > stalemate. > > I hope we can agree that the current situation is not good. When > trying to develop wit

Re: [openstack-dev] [Fuel] fuel master monitoring

Monit is easy and is used to control states of Compute nodes. We can adopt it for master node. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Wed, Nov 26, 2014 at 4:46 PM, Stanislaw Bogatkin wrote: > As for me - zabbix is overkill for one node. Zabbix Server + Agent + > Fron

Re: [openstack-dev] [Fuel] fuel master monitoring

Jay, Fuel uses watchdog service for container to restart it in case of issues. We have the same problem with containers when disk is full -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Wed, Nov 26, 2014 at 4:39 PM, Jay Pipes wrote: > On 11/26/2014 10:22 AM, Przemyslaw Kamin

Re: [openstack-dev] [nova] Proposal new hacking rules

On 11/26/2014 07:54 AM, Jay Pipes wrote: > On 11/26/2014 06:20 AM, Nicolas Trangez wrote: >> On Mon, 2014-11-24 at 13:19 -0500, Jay Pipes wrote: >>> I think pointing out that the default failure >>> message for testtools.TestCase.assertEqual() uses the terms >>> "reference" >>> (expected) and "actu

Re: [openstack-dev] suds-jurko, new in our global-requirements.txt: what is the point?!?

> On Nov 26, 2014, at 10:34 AM, Thomas Goirand wrote: > > Hi, > > I tried to package suds-jurko. I was first happy to see that there was > some progress to make things work with Python 3. Unfortunately, the > reality is that suds-jurko has many issues with Python 3. For example, > it has many:

Re: [openstack-dev] [Fuel] fuel master monitoring

As for me - zabbix is overkill for one node. Zabbix Server + Agent + Frontend + DB + HTTP server, and all of it for one node? Why not use something that was developed for monitoring one node, doesn't have many deps and work out of the box? Not necessarily Monit, but something similar. On Wed, Nov

Re: [openstack-dev] [Ironic] Do we need an IntrospectionInterface?

On 11/26/2014 02:20 PM, Dmitry Tantsur wrote: Hi all! As our state machine and discovery discussion proceeds, I'd like to ask your opinion on whether we need an IntrospectionInterface (DiscoveryInterface?). Current proposal [1] suggests adding a method for initiating a discovery to the Managemen

Re: [openstack-dev] Query regarding vRouter BGP/MPLS VPN support

Hi Vikram, thanks to latest ovs capabilities, and to an upstreamed compatible BGPSpeaker, we proposed to implement MPLS VPN interconnection directly in Neutron [1] The Tacker project aims at managing VNF, and its first use case is about implementing a RouterAAS. Maybe you can have a look at that [

Re: [openstack-dev] [Nova] Handling soft delete for instance rows in a new cells database

On 11/25/2014 11:54 AM, Solly Ross wrote: I can't comment on other projects, but Nova definitely needs the soft delete in the main nova database. Perhaps not for every table, but there is definitely code in the code base which uses it right now. Search for read_deleted=True if you're curious. J

Re: [openstack-dev] [Fuel] fuel master monitoring

Hi, I would do both to compare. monit and Sensu have own advantages. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Wed, Nov 26, 2014 at 4:22 PM, Przemyslaw Kaminski wrote: > We want to monitor Fuel master node while Zabbix is only on slave nodes > and not on master. The mo

Re: [openstack-dev] [Fuel] fuel master monitoring

On 11/26/2014 10:22 AM, Przemyslaw Kaminski wrote: We want to monitor Fuel master node while Zabbix is only on slave nodes and not on master. The monitoring service is supposed to be installed on Fuel master host (not inside a Docker container) and provide basic info about free disk space, etc.

[openstack-dev] suds-jurko, new in our global-requirements.txt: what is the point?!?

Hi, I tried to package suds-jurko. I was first happy to see that there was some progress to make things work with Python 3. Unfortunately, the reality is that suds-jurko has many issues with Python 3. For example, it has many: except Exception, e: as well as many: raise Exception, 'Duplicate ke

Re: [openstack-dev] #Personal# Ref: L3 service integration with service framework

Hi, you can still add your own service plugin, as a mixin of L3RouterPlugin (have a look at brocade's code). AFAIU service framework would manage the coexistence several implementation of a single service plugin. This is currently not prioritized by neutron. This kind of work might restart in the

[openstack-dev] [Manila] Meeting cancelled this week

I forgot to bring the topic up last week, but this week we have a holiday in the US that conflicts with the weekly meeting, so I have cancelled it. -Ben ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-

[openstack-dev] [nova] is there a way to simulate thousands or millions of compute nodes?

Hi all, Is there a way to simulate thousands or millions of compute nodes? Maybe we could have many fake nova-compute services on one physical machine. By this other nova components would have pressure from thousands of compute services and this could help us find more problem from large-scale dep

Re: [openstack-dev] [Fuel] fuel master monitoring

We want to monitor Fuel master node while Zabbix is only on slave nodes and not on master. The monitoring service is supposed to be installed on Fuel master host (not inside a Docker container) and provide basic info about free disk space, etc. P. On 11/26/2014 02:58 PM, Jay Pipes wrote: On

Re: [openstack-dev] [Fuel] fuel master monitoring

Folks, Maybe I understand some things wrong, but Zabbix is a different story. We deploy Zabbix per cluster, so it doesn't monitor for *all* slaves or master node. It monitors only one cluster. Therefore I see no reasons to choose Zabbix over monit. I mean, it shouldn't be "We MUST use Zabbix beca

Re: [openstack-dev] [pecan] [WSME] Different content-type in request and response

On Nov 26, 2014, at 3:49 AM, Renat Akhmerov wrote: > Hi, > > I traced the WSME code and found a place [0] where it tries to get arguments > from request body based on different mimetype. So looks like WSME supports > only json, xml and “application/x-www-form-urlencoded”. > > So my question

[openstack-dev] [QA] No Meeting this Week

Hi Everyone, I figured I'd send a quick announcement that we won't be having a meeting this week. The next meeting will be next week, Dec. 4th at 17:00 UTC. Thanks, -Matt Treinish pgpCJ2s1V0P2N.pgp Description: PGP signature ___ OpenStack-dev mailin

Re: [openstack-dev] [Heat] Order of machines to be terminated during scale down

On 26/11/14 09:13, Maish Saidel-Keesing wrote: Thanks Pavlo. Is there any reason why FIFO was chosen? I believe that this was the original termination policy on AWS, and that was the reason we chose it. It was used on AWS because if you deleted an instance that was just created you would be

Re: [openstack-dev] [nova] nova host-update gives error 'Virt driver does not implement host disabled status'

- Original Message - > From: "Vineet Menon" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Wednesday, 26 November, 2014 5:14:09 AM > Subject: Re: [openstack-dev] [nova] nova host-update gives error 'Virt driver > does not implement host disabled > statu

[openstack-dev] [Devstack] Juno Backport for Bug "Revert Single quote iniset argument in merge_config_file"

Hi, do you think we could backport this bug to the devstack stable/juno release? https://review.openstack.org/#/c/131334/ This bug prohibits people to use the local.conf from icehouse, when they take use of variables for defining configuration values An example. The local.conf looks like this

Re: [openstack-dev] [QA][Tempest] Proposing Ghanshyam Mann for Tempest Core

So all of the current core team members have voted unanimously in favor of adding Ghanshyam to the team. Welcome to the team Ghanshyam. -Matt Treinish On Wed, Nov 26, 2014 at 09:57:10AM -0500, Attila Fazekas wrote: > +1 > > - Original Message - > From: "Marc Koderer" > To: "OpenStack

Re: [openstack-dev] [QA][Tempest] Proposing Ghanshyam Mann for Tempest Core

+1 - Original Message - From: "Marc Koderer" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Wednesday, November 26, 2014 7:58:06 AM Subject: Re: [openstack-dev] [QA][Tempest] Proposing Ghanshyam Mann for Tempest Core +1 Am 22.11.2014 um 15:51 schrieb Andrea

Re: [openstack-dev] [Keystone] Splitting up the assignment component

I tend to agree with Morgan. There are resources and there are users. And there is something in the middle that says which users can access which resources. It might be an ACL, a RBAC role, or a set of ABAC attributes, or something else (such as a MAC policy). So to my mind this middle bit, whilst

Re: [openstack-dev] [devstack] environment variables in local.conf post-config section

That's it. Thanks! -- Andreas (irc: scheuran) On Wed, 2014-11-26 at 15:10 +0100, jordan pittier wrote: > Hi, > It should work with your current local.conf. You may be facing this bug : > https://bugs.launchpad.net/devstack/+bug/1386413 > > Jordan > > - Original Message - > From: "And

Re: [openstack-dev] [nova] Proposal new hacking rules

On 11/26/2014 09:28 AM, Nicolas Trangez wrote: On Wed, 2014-11-26 at 08:54 -0500, Jay Pipes wrote: On 11/26/2014 06:20 AM, Nicolas Trangez wrote: On Mon, 2014-11-24 at 13:19 -0500, Jay Pipes wrote: I think pointing out that the default failure message for testtools.TestCase.assertEqual() uses

Re: [openstack-dev] [nova] Proposal new hacking rules

On Wed, Nov 26, 2014 at 08:54:35AM -0500, Jay Pipes wrote: > It's not about an equality condition. > > It's about the message that is produced by testtools.TestCase.assertEqual(), > and the helpfulness of that message when the order of the arguments is > reversed. > > This is especially true with

[openstack-dev] [nova] How should libvirt pools work with distributed storage drivers?

Hi, Some days ago, a bunch of Nova specs were approved for Kilo. Among them was https://blueprints.launchpad.net/nova/+spec/use-libvirt-storage-pools Now, while I do recognize the wisdom of using storage pools, I do see a couple of possible problems with this, especially in the light of my upcom

Re: [openstack-dev] [nova] Proposal new hacking rules

On Wed, 2014-11-26 at 08:54 -0500, Jay Pipes wrote: > On 11/26/2014 06:20 AM, Nicolas Trangez wrote: > > On Mon, 2014-11-24 at 13:19 -0500, Jay Pipes wrote: > >> I think pointing out that the default failure > >> message for testtools.TestCase.assertEqual() uses the terms > >> "reference" > >> (exp

Re: [openstack-dev] [Heat] Order of machines to be terminated during scale down

Thanks Pavlo. Is there any reason why FIFO was chosen? Maish On 26/11/2014 12:30, Pavlo Shchelokovskyy wrote: > Maish, > > by default they are deleted in in the same order they were created, > FIFO style. > > Best regards, > Pavlo Shchelokovskyy. > > On Wed, Nov 26, 2014 at 12:24 PM, Maish Saidel

Re: [openstack-dev] [devstack] environment variables in local.conf post-config section

Hi, It should work with your current local.conf. You may be facing this bug : https://bugs.launchpad.net/devstack/+bug/1386413 Jordan - Original Message - From: "Andreas Scheuring" To: "openstack-dev" Sent: Wednesday, 26 November, 2014 2:04:57 PM Subject: [openstack-dev] [devstack] env

Re: [openstack-dev] [Fuel] fuel master monitoring

On 11/26/2014 08:18 AM, Fox, Kevin M wrote: So then in the end, there will be 3 monitoring systems to learn, configure, and debug? Monasca for cloud users, zabbix for most of the physical systems, and sensu or monit "to be small"? Seems very complicated. If not just monasca, why not the zabbix

Re: [openstack-dev] [nova] Proposal new hacking rules

On 11/26/2014 06:20 AM, Nicolas Trangez wrote: On Mon, 2014-11-24 at 13:19 -0500, Jay Pipes wrote: I think pointing out that the default failure message for testtools.TestCase.assertEqual() uses the terms "reference" (expected) and "actual" is a reason why reviewers *should* ask patch submitters

Re: [openstack-dev] [oslo] python 2.6 support for oslo libraries

On 11/26/2014 02:48 PM, Julien Danjou wrote: > On Wed, Nov 26 2014, Andreas Jaeger wrote: > >> The libraries have 2.6 support enabled as discussed - but if indeed some >> are missing, please send patches, > > So to recap, it seems to me the plan is to keep all Oslo lib with > Python 2.6 so we don

Re: [openstack-dev] [oslo] python 2.6 support for oslo libraries

On Wed, Nov 26 2014, Andreas Jaeger wrote: > The libraries have 2.6 support enabled as discussed - but if indeed some > are missing, please send patches, So to recap, it seems to me the plan is to keep all Oslo lib with Python 2.6 so we don't have any transient dependency problem with stable in t

Re: [openstack-dev] [Heat] Order of machines to be terminated during scale down

On 26/11/2014 14:50, Jay Lau wrote: > The current behavior is not flexible to customer, I see that we have > a blueprint want to enhance this behavior. > > https://blueprints.launchpad.net/heat/+spec/autoscaling-api-resources > https://wiki.openstack.org/wiki/Heat/AutoScaling > > In Use Case sect

[openstack-dev] #Personal# Ref: L3 service integration with service framework

Hi Gary, All, This is with reference to blueprint - L3 router Service Type Framework and corresponding development at github repo. I noticed that the patch was abandoned due to inactivity. Wanted to know if there is a specific reason for which the development was put on hold? I am working on

Re: [openstack-dev] [Fuel] Separate code freeze for repos

I envision it in the following way: 1. stable/6.0 is created for fuel-main along with stable branch for other repo, which is under consideration, like fuel-web 2. In stable/6.0 of fuel-main, config.mk should be changed to refer to stable/6.0 for one of the repos, like fuel-web. master

Re: [openstack-dev] [all] removing XML testing completely from Tempest

On 11/25/2014 03:28 AM, Flavio Percoco wrote: > On 24/11/14 08:56 -0500, Sean Dague wrote: >> Having XML payloads was never a universal part of OpenStack services. >> During the Icehouse release the TC declared that being an OpenStack >> service requires having a JSON REST API. Projects could do wh

[openstack-dev] [Ironic] Do we need an IntrospectionInterface?

Hi all! As our state machine and discovery discussion proceeds, I'd like to ask your opinion on whether we need an IntrospectionInterface (DiscoveryInterface?). Current proposal [1] suggests adding a method for initiating a discovery to the ManagementInterface. IMO it's not 100% correct, because:

Re: [openstack-dev] [Fuel] fuel master monitoring

So then in the end, there will be 3 monitoring systems to learn, configure, and debug? Monasca for cloud users, zabbix for most of the physical systems, and sensu or monit "to be small"? Seems very complicated. If not just monasca, why not the zabbix thats already being deployed? Thanks, Kevin

[openstack-dev] [devstack] environment variables in local.conf post-config section

Hi together, is there a way to use Environment variables in the local.conf post-config section? On my system (stable/juno devstack) not the content of the variable, but the variable name itself is being inserted into the config file. So e.g. [[post-config|$NOVA_CONF]] [DEFAULT] vncserver_proxy

Re: [openstack-dev] [Telco] [NFV] [Heat] Telco Orchestration

Hi, On Wed, Nov 26, 2014 at 12:48 AM, Georgy Okrokvertskhov wrote: > Hi, > > In Murano we did couple projects related to networking orchestration. As NFV Can you tell us more about those projects? Does it include mutli-datacenter use cases? > is a quite broad term I can say that Murano approach

Re: [openstack-dev] [Heat] Order of machines to be terminated during scale down

The current behavior is not flexible to customer, I see that we have a blueprint want to enhance this behavior. https://blueprints.launchpad.net/heat/+spec/autoscaling-api-resources https://wiki.openstack.org/wiki/Heat/AutoScaling In Use Case section, we have the following: =

Re: [openstack-dev] [Fuel] Plugins improvement

Evgeniy, Thanks a lot! On Mon, Nov 24, 2014 at 5:15 PM, Evgeniy L wrote: > Hi Dmitry, > > Our current validation implementation is based on jsonschema, > we will figure out how to hack/configure it to provide more human > readable message > > Thanks, > > On Mon, Nov 24, 2014 at 2:34 PM, Dmitry U

[openstack-dev] [Fuel] Nailgun API log verbosity

Hi, all! Recently I started working on nailgun-api log is too verbose bug and collected your feedbacks about PoC as follows: 1) We cannot always delete or cut messages received from nailgun-agent because

Re: [openstack-dev] [Fuel] Separate code freeze for repos

Mike, from DevOps point of view it doesn't really matter when we do branching. This is the process we need to perform anyway and this partial branching doesn't change too much for us. Although there might be several technical questions like: 1) When we create /6.1 mirror? 2) Should we create fu

Re: [openstack-dev] [heat] [CustomResource] LifeCycle methods flow

Thanks Pavlo. One particular thing I did not comprehend is: Suppose my resource code is something like: class HelloWorld(resource.Resource): def __init__(self, controller, deserializer, serializer=None): LOG.info("[pradipm]:Inside HelloWorld ctor"); resource.Resource.__init_

Re: [openstack-dev] [nova] Proposal new hacking rules

On Mon, 2014-11-24 at 13:19 -0500, Jay Pipes wrote: > I think pointing out that the default failure > message for testtools.TestCase.assertEqual() uses the terms > "reference" > (expected) and "actual" is a reason why reviewers *should* ask patch > submitters to use (expected, actual) ordering.

[openstack-dev] Query regarding vRouter BGP/MPLS VPN support

Hi All, Can anyone please help us with below queries: 1. Did any of the open source vRouter/s (say vyaTTa, Qagga, BIRD or etc) support BGP/MPLS VPN functionality? 2. How neutron can communicate with vRouter (say vyaTTa, Qagga, BIRD or etc)? Did someone has done this? Thanks Vikra

  1   2   >