Re: [openstack-dev] [tempest] How to run tempest tests

2014-11-28 Thread om prakash pandey
Hi Folks, I would like to know about the best practices followed for skipping tests not applicable for my environment. I know one of the ways is to use the below decorator over the test method: @test.skip_because(bug=BUG_ID) However, what if my deployment doesn't support VPNAAS and I want to

Re: [openstack-dev] [tempest] How to run tempest tests

2014-11-28 Thread Sridhar Gaddam
If the deployment does not support IPv6, we use the following convention to skip the tests at class level. https://github.com/openstack/tempest/blob/master/tempest/api/network/base.py#L65 Regards, --Sridhar. On 11/28/2014 01:50 PM, om prakash pandey wrote: Hi Folks, I would like to know

[openstack-dev] [nova] ER diagram of NOVA DB

2014-11-28 Thread Markus Zoeller
Hi, I used SchemaSpy for generating ER diagram of Nova DB. This is just an FYI for people who are working for Cellv2, involved in generating new schema. One can start by unzipping the archive and open index.html in browser... Regards, Vineet Menon I'm not working on the cellsv2

Re: [openstack-dev] [tempest] How to run tempest tests

2014-11-28 Thread om prakash pandey
Thanks Sridhar. I'm aware of using skipException for skipping tests at class level. However, this involves putting it in every class to skip tests which are not desired. I was looking for a way to control the tests I want to run through some kind of a configuration file, the options to pass to

Re: [openstack-dev] [tempest] How to run tempest tests

2014-11-28 Thread GHANSHYAM MANN
Tests can be skipped based on configuration file options. Its all depend on what all set of tests you want to skip for your environment. For example- to skip all sahara tests (as you mentioned) You can make config option - 'sahara' to false which will skip all sahara tests. Particular feature

[openstack-dev] [ironic][nova] ironic driver retries on ironic driver Conflict response

2014-11-28 Thread Murray, Paul (HP Cloud)
Hi All, Looking at the ironic virt driver code in nova it seems that a Conflict (409) response from the ironic client results in the driver re-trying the request. Given the comment below in the ironic code I would imagine that is not the right behavior - it reads as though this is something

Re: [openstack-dev] [ironic][nova] ironic driver retries on ironic driver Conflict response

2014-11-28 Thread Dmitry Tantsur
Hi! On 11/28/2014 11:41 AM, Murray, Paul (HP Cloud) wrote: Hi All, Looking at the ironic virt driver code in nova it seems that a Conflict (409) response from the ironic client results in the driver re-trying the request. Given the comment below in the ironic code I would imagine that is not

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

2014-11-28 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 27/11/14 19:10, Thomas Goirand wrote: On 11/28/2014 12:06 AM, Ihar Hrachyshka wrote: On 27/11/14 12:09, Thomas Goirand wrote: On 11/27/2014 12:31 AM, Donald Stufft wrote: On Nov 26, 2014, at 10:34 AM, Thomas Goirand z...@debian.org wrote:

[openstack-dev] [stable] Re: [neutron] the hostname regex pattern fix also changed behaviour :(

2014-11-28 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 28/11/14 01:26, Angus Lees wrote: Context: https://review.openstack.org/#/c/135616 As far as I can make out, the fix for CVE-2014-7821 removed a backslash that effectively disables the negative look-ahead assertion that verifies that

[openstack-dev] [heat] [cinder backend options] Propagate Cinder backend config information to Heat

2014-11-28 Thread Pradip Mukhopadhyay
Hello, Suppose we have a cinder backend in local.conf | cinder.conf as : [myNFSBackend] nfs_mount_options = nfsvers=3 volume_backend_name = myNFSBackend volume_driver = cinder.volume.drivers.netapp.common.NetAppDriver netapp_server_hostname = IP netapp_server_port = 80 netapp_storage_protocol

Re: [openstack-dev] Compute Node lost the net-connection after spawning vm

2014-11-28 Thread Qiming Teng
Sounds like a iptables problem. BTW, you may want to post this kind of question to openst...@lists.openstack.org, not here. Regards, Qiming On Thu, Nov 27, 2014 at 06:45:26PM +0530, Aman Kumar wrote: Hi, I am using DevStack since 4 months and it was working fine but 2 days back i got some

Re: [openstack-dev] [heat] [cinder backend options] Propagate Cinder backend config information to Heat

2014-11-28 Thread Qiming Teng
The first thing you may want to check is the Cinder API. If I'm understanding this correctly, Heat only interact with other OpenStack services via their APIs. It is not supposed to peek into their internals. Regards, - Qiming On Fri, Nov 28, 2014 at 06:19:56PM +0530, Pradip Mukhopadhyay

Re: [openstack-dev] [Fuel] About deployment progress calculation

2014-11-28 Thread Evgeniy L
Hi Dmitry, I totally agree that the current approach won't work (and doesn't work well). I have several comments: Each task will provide estimated time 1. Each task has timeout, lets use it as an estimate, I don't think that we should ask to provide both of this fields, execution

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

2014-11-28 Thread Jay Pipes
On 11/27/2014 04:20 PM, Michael Still wrote: On Fri, Nov 28, 2014 at 2:59 AM, Jay Pipes jaypi...@gmail.com wrote: On 11/26/2014 04:24 PM, 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

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

2014-11-28 Thread Lucas Alvares Gomes
Hi, Thanks for putting it up Dmitry. I think the idea is fine too, I understand that people may want to use in-band discovery for drivers like iLO or DRAC and having those on a separated interface allow us to composite a driver to do it (which is ur use case 2. ). So, +1. Lucas On Wed, Nov 26,

Re: [openstack-dev] [heat] [cinder backend options] Propagate Cinder backend config information to Heat

2014-11-28 Thread Murugesan, Sirushti
One option would be to use a secret management service like Barbican[1] to store those credentials/secrets and use it whenever you want to make a SOAP API call. There's also Barbican resources available in the contrib section of the Heat repository which could also possibly be used and

Re: [openstack-dev] [heat] [cinder backend options] Propagate Cinder backend config information to Heat

2014-11-28 Thread Pavlo Shchelokovskyy
That's true. Heat's job is mainly to call other OpenStack APIs in correct order in order to achieve desired combination of infrastructure resources. Physically though it may run on a completely different host where these files are not present, even including a host that is outside of the

Re: [openstack-dev] [Heat] Rework auto-scaling support in Heat

2014-11-28 Thread Jastrzebski, Michal
-Original Message- From: Qiming Teng [mailto:teng...@linux.vnet.ibm.com] Sent: Friday, November 28, 2014 8:33 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [Heat] Rework auto-scaling support in Heat Dear all, Auto-Scaling is an important feature supported

Re: [openstack-dev] [Heat] Rework auto-scaling support in Heat

2014-11-28 Thread Randall Burt
Per our discussion in Paris, I'm partial to Option B. I think a separate API endpoint is a lower priority at this point compared to cleaning up and normalizing the autoscale code on the back-end. Once we've refactored the engine code and solidified the RPC interface, it would be trivial to add

Re: [openstack-dev] [Fuel] [Plugins] Further development of plugin metadata format

2014-11-28 Thread Evgeniy L
Hi Vitaly, I agree with you that conditions can be useful in case of complicated plugins, but at the same time in case of simple cases it adds a huge amount of complexity. I would like to avoid forcing user to know about any conditions if he wants to add several text fields on the UI. I have

Re: [openstack-dev] [neutron][TripleO] Clear all flows when ovs agent start? why and how avoid?

2014-11-28 Thread Erik Moe
Hi, What is the status of this? It looks like simplistic approach might not be that far from flow synchronization. Both methods needs to reinitialize internal structures so that they match deployed configuration. For example provision_local_vlan picks a free VLAN. This has to be the same one

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

2014-11-28 Thread Rossella Sblendido
On 11/27/2014 12:21 PM, marios wrote: Hi, so far we have this going https://etherpad.openstack.org/p/restructure-l2-agent I finally pushed a design spec based on the etherpad above, https://review.openstack.org/#/c/137808/ . Anybody interested please comment on the review. cheers, Rossella

Re: [openstack-dev] [Fuel] [Plugins] Further development of plugin metadata format

2014-11-28 Thread Vitaly Kramskikh
Evgeniy, Responses inline: 2014-11-28 18:31 GMT+03:00 Evgeniy L e...@mirantis.com: Hi Vitaly, I agree with you that conditions can be useful in case of complicated plugins, but at the same time in case of simple cases it adds a huge amount of complexity. I would like to avoid forcing

[openstack-dev] [Fuel] [Nailgun] Unit tests improvement meeting minutes

2014-11-28 Thread Ivan Kliuk
Hi, team! Let me please present ideas collected during the unit tests improvement meeting: 1) Rename class ``Environment`` to something more descriptive 2) Remove hardcoded self.clusters[0], e.t.c from ``Environment``. Let's use parameters instead 3) run_tests.sh should invoke alternate

Re: [openstack-dev] [heat] [cinder backend options] Propagate Cinder backend config information to Heat

2014-11-28 Thread Pradip Mukhopadhyay
Thanks Qiming Pavlo. We had looked into the v2 of Cinder API listings: http://developer.openstack.org/api-ref-blockstorage-v2.html. However most likely (or may be we missed to note) none of the APIs peeped into/exposed the Cinder's backend configuration (the info we were looking for). So we were

Re: [openstack-dev] [Infra] Infra-manual documentation Sprint, December 1-2

2014-11-28 Thread Elizabeth K. Joseph
Hi everyone, Just a quick reminder that this is coming up on Monday-Tuesday, join us in channel to chat about what you're working on. On Fri, Nov 7, 2014 at 5:57 AM, Elizabeth K. Joseph l...@princessleia.com wrote: Hi everyone, The OpenStack Infrastructure team will be hosting a virtual

Re: [openstack-dev] Quota management and enforcement across projects

2014-11-28 Thread Jay Pipes
On 11/17/2014 05:49 PM, Salvatore Orlando wrote: Hi all, I am resuming this thread following the session we had at the summit in Paris (etherpad here [1]) While there was some sort of consensus regarding what this library should do, and how it should do it, the session ended with some open

Re: [openstack-dev] [cinder][nova] proper syncing of cinder volume state

2014-11-28 Thread D'Angelo, Scott
A Cinder blueprint has been submitted to allow the python-cinderclient to involve the back end storage driver in resetting the state of a cinder volume: https://blueprints.launchpad.net/cinder/+spec/reset-state-with-driver and the spec: https://review.openstack.org/#/c/134366 This blueprint

Re: [openstack-dev] [Fuel] [Plugins] Further development of plugin metadata format

2014-11-28 Thread Dmitriy Shulyak
- environment_config.yaml should contain exact config which will be mixed into cluster_attributes. No need to implicitly generate any controls like it is done now. Initially i had the same thoughts and wanted to use it the way it is, but now i completely agree with Evgeniy that

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

2014-11-28 Thread James Slagle
On Thu, Nov 27, 2014 at 1:29 PM, Sullivan, Jon Paul jonpaul.sulli...@hp.com wrote: -Original Message- From: Ben Nemec [mailto:openst...@nemebean.com] Sent: 26 November 2014 17:03 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev]

Re: [openstack-dev] [Fuel] [Plugins] Further development of plugin metadata format

2014-11-28 Thread Dmitry Borodaenko
Vitaly, It's there a document or spec or a wiki page that describes the current status of this discussion in the context of the whole pluggable architecture design? Jumping into this thread without having the whole picture is hard. Knowing what is already agreed, what is implemented so far, and

Re: [openstack-dev] [Fuel] [Nailgun] Unit tests improvement meeting minutes

2014-11-28 Thread Thomas Goirand
On 11/29/2014 12:15 AM, Ivan Kliuk wrote: Hi, team! Let me please present ideas collected during the unit tests improvement meeting: 1) Rename class ``Environment`` to something more descriptive 2) Remove hardcoded self.clusters[0], e.t.c from ``Environment``. Let's use parameters instead

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

2014-11-28 Thread Thomas Goirand
On 11/28/2014 07:35 PM, Ihar Hrachyshka wrote: On 27/11/14 19:10, Thomas Goirand wrote: On 11/28/2014 12:06 AM, Ihar Hrachyshka wrote: On 27/11/14 12:09, Thomas Goirand wrote: On 11/27/2014 12:31 AM, Donald Stufft wrote: On Nov 26, 2014, at 10:34 AM, Thomas Goirand z...@debian.org wrote:

[openstack-dev] [Keystone] internalURL and adminURL of endpoints should not be visible to ordinary user

2014-11-28 Thread joehuang
Hello, if an ordinary user sent a get-token request to KeyStone, internalURL and adminURL of endpoints will also be returned. It'll expose the internal high privilege access address and some internal network topology information to the ordinary user, and leads to the risk for malicious user to

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

2014-11-28 Thread Deepak Shetty
On Fri, Nov 28, 2014 at 10:32 PM, Steve Gordon sgor...@redhat.com wrote: - Original Message - From: Deepak Shetty dpkshe...@gmail.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org But isn't *-specs comes very early in the

Re: [openstack-dev] [Heat] Rework auto-scaling support in Heat

2014-11-28 Thread Angus Salkeld
On Fri, Nov 28, 2014 at 5:33 PM, Qiming Teng teng...@linux.vnet.ibm.com wrote: Dear all, Auto-Scaling is an important feature supported by Heat and needed by many users we talked to. There are two flavors of AutoScalingGroup resources in Heat today: the AWS-based one and the Heat native