[Openstack] Schedule Live - Tokyo OpenStack Summit

2015-08-26 Thread Kendall Waters
Hi everyone, The schedule for the upcoming OpenStack Summit in Tokyo https://www.openstack.org/summit/tokyo-2015/ is now available! SCHEDULE: https://www.openstack.org/summit/tokyo-2015/schedule/ https://www.openstack.org/summit/tokyo-2015/schedule/ There are two views for the Summit

Re: [openstack-dev] mock 1.3 breaking all of Kilo in Sid (and other cases of this kind)

2015-08-26 Thread Robert Collins
On 27 August 2015 at 02:15, Ihar Hrachyshka ihrac...@redhat.com wrote: I really wish that nothing of this kind was even possible. Adding such an upper cap is like hiding the dust under the carpet: it doesn't remove the issue, it just hides it. We really have too much of these in OpenStack.

Re: [openstack-dev] mock 1.3 breaking all of Kilo in Sid (and other cases of this kind)

2015-08-26 Thread Robert Collins
On 27 August 2015 at 01:31, Thomas Goirand z...@debian.org wrote: On 08/25/2015 11:20 PM, Robert Collins wrote: So I can't upload PBR 1.3.0 to Sid. This has been dealt with because I am the maintainer of PBR, but really, it shouldn't have happen. How come for years, upgrading PBR always

Re: [openstack-dev] [cinder][nova] snapshot and cloning for NFS backend

2015-08-26 Thread Nikola Đipanov
On 07/28/2015 09:00 AM, Kekane, Abhishek wrote: Hi Devs, There is an NFS backend driver for cinder, which supports only limited volume handling features. Specifically, snapshot and cloning features are missing. Eric Harney has proposed a feature of NFS driver snapshot [1][2][3],

Re: [openstack-dev] [requirements] dependencies problem on different release

2015-08-26 Thread Robert Collins
On 27 August 2015 at 02:00, Gareth academicgar...@gmail.com wrote: Hey guys, I have a question about dependencies. There is an example: On 2014.1, project A is released with its dependency in requirements.txt which contains: foo=1.5.0 bar=2.0.0,2.2.0 and half a year later, the

Re: [openstack-dev] [magnum] versioned objects changes

2015-08-26 Thread Ryan Rossiter
I've been working with Nova's versioned objects lately to help catch people when object changes are made. There is a lot of object-related tests in Nova for this, and a major one I can see helping this situation is this test [1]. Looking through the different versioned objects within Magnum, I

[OpenStack-Infra] Puppet Apache Dependency Issues

2015-08-26 Thread Spencer Krum
Hello All, At the meeting on August 25th, we discussed an issue with the puppet-httpd module and a few solutions. The issue is that the httpd_mod type does not have a baked-in ordering relationship with the Service['httpd'] resource. This means that sometimes httpd_mod resources are instantiated

Re: [openstack-dev] [oslo] Help with stable/juno branches / releases

2015-08-26 Thread Doug Hellmann
Tony, Thanks for digging into this! I should be able to help, but right now we're ramping up for the L3 feature freeze and there are a lot of release-related activities going on. Can this wait a few weeks for things to settle down again? Doug Excerpts from Tony Breeds's message of 2015-08-24

Re: [openstack-dev] [tripleo] CLI and RHEL registration of overcloud nodes

2015-08-26 Thread Steven Hardy
On Wed, Aug 26, 2015 at 05:28:47PM +0200, Jan Provazník wrote: Hi, although rdomanager-oscplugin is not yet under TripleO it should be soon, so sending this to TripleO audience. Satellite registration from user's point of view is now done by passing couple of specific parameters when

Re: [Openstack-operators] Juno and Kilo Interoperability

2015-08-26 Thread David Medberry
Hi Eren, I'm pretty sure NECTaR is doing diff versions at different sites in a widely distributed way. https://www.openstack.org/user-stories/nectar/ I've cc'd Sam as well. He's your man. On Wed, Aug 26, 2015 at 5:24 AM, Eren Türkay er...@skyatlas.com wrote: Hello operators, I am wondering

Re: [Openstack-operators] Juno and Kilo Interoperability

2015-08-26 Thread David Medberry
and we generally run a much newer Horizon and Keystone than the rest of the services. We had Horizon and Keystone on POST KILO (master after Kilo released) while still running Juno on all other services. Worked fine. On Wed, Aug 26, 2015 at 11:09 AM, David Medberry openst...@medberry.net wrote:

[Openstack] Nova boot from volume problem after Kilo upgrade

2015-08-26 Thread Jonathan Proulx
Hi All, Before I open a bug... after Kilo upgrade I get 'Error: Flavor's disk is too small for requested image' when trying to boot from cinder volumes that are larger than the image-type root volume. This is a severe issue for me. Has anyone else seen/reported this (I didn't see it looking at

Re: [Openstack] Nova boot from volume problem after Kilo upgrade

2015-08-26 Thread John Griffith
On Wed, Aug 26, 2015 at 10:59 AM, Jonathan Proulx j...@jonproulx.com wrote: Error: Flavor's disk is too small for requested image ​Without looking closely, wonder if this is what you're seeing: https://bugs.launchpad.net/nova/+bug/1457517 ___

Re: [Openstack-operators] Juno and Kilo Interoperability

2015-08-26 Thread Matthias Runge
On 26/08/15 19:11, David Medberry wrote: and we generally run a much newer Horizon and Keystone than the rest of the services. We had Horizon and Keystone on POST KILO (master after Kilo released) while still running Juno on all other services. Worked fine. Horizon used to work cross versions

Re: [openstack-dev] [TripleO] Encapsulating logic and state in the client

2015-08-26 Thread Dougal Matthews
- Original Message - From: Jay Dobies jason.dob...@redhat.com To: openstack-dev@lists.openstack.org Sent: Tuesday, 25 August, 2015 2:31:02 PM Subject: Re: [openstack-dev] [TripleO] Encapsulating logic and state in the client Thinking about this further, the interesting question

[openstack-dev] [magnum] devstack/heat problem with master_wait_condition

2015-08-26 Thread Pitucha, Stanislaw Izaak
Hi all, I’m trying to stand up magnum according to the quickstart instructions with devstack. There’s one resource which times out and fails: master_wait_condition. The kube master (fedora) host seems to be created, I can login to it via ssh, other resources are created successfully. What

[openstack-dev] [ceilometer] [rally] [sahara] [heat] [congress] [tripleo] ceilometer in gate jobs

2015-08-26 Thread Chris Dent
[If any of this is wrong I hope someone from infra or qa will correct me. Thanks. This feels a bit cumbersome so perhaps there is a way to do it in a more automagic fashion[1].] In the near future ceilometer will be removing itself from the core of devstack and using a plugin instead. This is

Re: [openstack-dev] [glance][murano] Glance V3 (Artifacts) usage in Murano

2015-08-26 Thread Flavio Percoco
On 24/08/15 18:37 +0300, Alexander Tivelkov wrote: Hi folks, In the upcoming L release Murano is going to use the Glance Artifact Repository feature implemented as part of EXPERIMENTAL Glance V3 API. The server-side support of this feature is already merged in glance's master branch, while the

Re: [openstack-dev] [glance][murano] Glance V3 (Artifacts) usage in Murano

2015-08-26 Thread Nikhil Komawar
We considered that option and have finally agreed on what Alex suggests at the rel-mgrs office as this is the least painful path for most. On 8/26/15 12:04 PM, Flavio Percoco wrote: On 24/08/15 18:37 +0300, Alexander Tivelkov wrote: Hi folks, In the upcoming L release Murano is going to use

Re: [openstack-dev] [neutron][lbaas] L7 - Tasks

2015-08-26 Thread Doug Wiegley
I think that if we’ve got someone identified to do the ref implementation, and that is code complete by 8/31, we can apply for a feature freeze exception. If we don’t have someone assigned to that task, it’ll slip. doug On Aug 26, 2015, at 7:22 AM, Samuel Bercovici samu...@radware.com wrote:

Re: [openstack-dev] [glance][murano] Glance V3 (Artifacts) usage in Murano

2015-08-26 Thread Flavio Percoco
On 26/08/15 12:22 -0400, Nikhil Komawar wrote: We considered that option and have finally agreed on what Alex suggests at the rel-mgrs office as this is the least painful path for most. It would have been nice to know it had already been discussed across some glance members and other folks.

Re: [openstack-dev] [neutron][lbaas] L7 - Tasks

2015-08-26 Thread Evgeny Fedoruk
Hi, As Sam mentioned, I will join Octavia meeting today, hope there will be time to discuss L7 tasks L7 related patches in review now are: Extension https://review.openstack.org/#/c/148232 CLI https://review.openstack.org/#/c/217276 Reference implementation

Re: [Openstack] Nova boot from volume problem after Kilo upgrade

2015-08-26 Thread Jonathan Proulx
That looks like exactly the thing John thanks, not sure why I missed it on my first look through . David those look like some excellent slides. As an operations community we should find a better way of pulling together upgrade experiences and related bugs. If I come up with anything clever I'll

Re: [openstack-dev] [zaqar] First Liberty testing day

2015-08-26 Thread Flavio Percoco
On 26/08/15 19:30 +0200, Flavio Percoco wrote: Greetings, I'm happy to announce that the Zaqar team will hold a testing day this Friday, August 28th. We'll be testing the API and the client library and the hope is to find as many issues as possible that can be fixed before our next release.

Re: [openstack-dev] [nova] CI for reliable live-migration

2015-08-26 Thread Joe Gordon
On Wed, Aug 26, 2015 at 8:18 AM, Matt Riedemann mrie...@linux.vnet.ibm.com wrote: On 8/26/2015 3:21 AM, Timofei Durakov wrote: Hello, Here is the situation: nova has live-migration feature but doesn't have ci job to cover it by functional tests, only

Re: [openstack-dev] [nova] CI for reliable live-migration

2015-08-26 Thread Timofei Durakov
Update: 1. Job fails from time to time, I'm collecting statistics to understand whether it is valid fails or some races, etc. 2. This sounds good: jogo has had a patch up for this for awhile: https://review.openstack.org/#/c/165233/ 3. It's required more research: We already have a voting

Re: [Openstack] Nova boot from volume problem after Kilo upgrade

2015-08-26 Thread David Medberry
Seen similar issues. There are some known glance issues and also so nova filter issues going on by default. I'd look at enabling verbose=True in Nova and seeing if you can get closer to the truth of what's going on and then tail the nova logs. We've put that down in our runbooks as a best

Re: [Openstack] [SPAM?] Re: KVM or Vagrant+VirtualBox for OpenStack test environment

2015-08-26 Thread Jerry Zhao
You can also check out http://github.com/openstack-dev/devstack-vagrant, which is pretty straight forward. I have managed to make kvm work but haven't pushed it upstream, virtualbox works as is though. On 08/25/2015 04:03 PM, Chow, Anthony T (Anthony)** CTR ** wrote: Thiago, Thanks. I am

Re: [openstack-dev] [requirements] dependencies problem on different release

2015-08-26 Thread Boris Pavlovic
Gareth, A real example is to enable Rally for OpenStack Juno. Rally doesn't support old release officially but I could checkout its codes to the Juno release date which make both codes match. However even if I use the old requirements.txt to install dependencies, there must be many packages

Re: [openstack-dev] [glance][murano] Glance V3 (Artifacts) usage in Murano

2015-08-26 Thread Nikhil Komawar
Can't find the logs on eavesdrop atm. Discussed yesterday on #openstack-relmgr-office around UTC evening. On 8/26/15 12:32 PM, Flavio Percoco wrote: On 26/08/15 12:22 -0400, Nikhil Komawar wrote: We considered that option and have finally agreed on what Alex suggests at the rel-mgrs office as

[openstack-dev] [zaqar] First Liberty testing day

2015-08-26 Thread Flavio Percoco
Greetings, I'm happy to announce that the Zaqar team will hold a testing day this Friday, August 28th. We'll be testing the API and the client library and the hope is to find as many issues as possible that can be fixed before our next release. I'd like to extend the invitation to the entire

[OpenStack-Infra] Final plans before translations switch to Zanata

2015-08-26 Thread Elizabeth K. Joseph
Hi everyone, As I mentioned at the infrastructure meeting yesterday[0], we are almost ready to launch the production Zanata server (translate.openstack.org). I have a week long trip starting this Friday night so I'm sharing my plans here so clarkb, StevenK and others can continue the work while

Re: [Openstack] [Swift] Delete handling with md5 collisions

2015-08-26 Thread Samuel Merritt
On 8/26/15 1:37 PM, Shrinand Javadekar wrote: Hi, I have a question about how object deletes are handled with md5 collisions. I looked at the code and here's my understanding of how things will work. If I have two objects that have the same md5 hash, they will go to the same hash directory.

Re: [Openstack] [Swift] Delete handling with md5 collisions

2015-08-26 Thread Shrinand Javadekar
Actually, I'm confused now. I used to think that Swift does HTTP deletes by synchronously truncating the object file and renaming it with a .ts extension. But the currently code simply creates a new file with the request timestamp and .ts extension. On Wed, Aug 26, 2015 at 1:37 PM, Shrinand

[openstack-dev] [heat][horizon] Backward-incompatible changes to the Neutron API

2015-08-26 Thread James Dempsey
Greetings Heat/Horizon Devs, There is some talk about possibly backward-incompatible changes to the Neutron VPNaaS API and I'd like to better understand what that means for Heat and Horizon. It has been proposed to change Neutron VPNService objects such that they reference a new resource type

Re: [openstack-dev] [oslo] Help with stable/juno branches / releases

2015-08-26 Thread Tony Breeds
On Wed, Aug 26, 2015 at 03:11:56PM -0400, Doug Hellmann wrote: Tony, Thanks for digging into this! No problem. It seemed like such a simple thing :/ I should be able to help, but right now we're ramping up for the L3 feature freeze and there are a lot of release-related activities going

Re: [Openstack] [Swift] Delete handling with md5 collisions

2015-08-26 Thread Chow, Anthony T (Anthony)** CTR **
Shri, Will these 2 discussions help resolve your doubt? https://answers.launchpad.net/swift/+question/156307 http://stackoverflow.com/questions/28379809/how-are-hash-collisions-handled Anthony. -Original Message- From: Shrinand Javadekar [mailto:shrin...@maginatics.com] Sent:

[Openstack-operators] How to restrict AvZones to Tenants

2015-08-26 Thread raju
Hi, I want to restrict Avzones to particular Tenant so that users in the Tenant can only see the particular Avzone from drop down while provisioning instances. Thanks ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org

Re: [openstack-dev] [neutron][networking-ovn][tempest] devstack: gate-tempest-dsvm-networking-ovn failures in Openstack CI

2015-08-26 Thread Russell Bryant
On 08/26/2015 04:25 PM, Amitabha Biswas wrote: With the recent commits it seems that the gate-tempest-dsvm-networking-ovn is succeeding more or less every time. The DBDeadlock issues still are seen on q-svc logs but are not frequent enough to cause ovsdb failures that were leading to the

Re: [openstack-dev] [ironic] Re: New API for node create, specifying initial provision state

2015-08-26 Thread Julia Kreger
My apologies for not expressing my thoughts on this matter sooner, however I've had to spend some time collecting my thoughts. To me, it seems like we do not trust our users. Granted, when I say users, I mean administrators who likely know more about the disposition and capabilities of their

Re: [OpenStack-Infra] Final plans before translations switch to Zanata

2015-08-26 Thread Carlos Munoz
Hi Elizabeth, I will get working on some instructions for the migration of the user data. Just to be clear, I'm assuming that what you want migrated is: - List of languages - List of users and open id's - User's memberships to language teams - User's permissions and roles (this includes admins

[openstack-announce] [OSSA 2015-016] Information leak via Swift tempurls (CVE-2015-5223)

2015-08-26 Thread Tristan Cacqueray
== OSSA-2015-016: Information leak via Swift tempurls == :Date: August 26, 2015 :CVE: CVE-2015-5223 Affects ~~~ - Swift: versions through 2.3.0 Description ~~~ Richard Hawkins from

[openstack-dev] subunit2html location on images changing

2015-08-26 Thread Matthew Treinish
Hi Everyone, There is a pending change up for review that will move the location subunit2html jenkins slave script: https://review.openstack.org/212864/ It switches from a locally installed copy to using the version packaged in os-testr which is installed in a system venv. This was done in an

Re: [openstack-dev] [sahara] Bug triage/fix and doc update days in Liberty

2015-08-26 Thread michael mccune
hey Saharans, with Doc fix day fast approaching i wanted to send out an email with the etherpad again, https://etherpad.openstack.org/p/sahara-liberty-doc-update-day it has been updated with all the docs and we are ready to roll starting on monday aug 31. mike On 08/24/2015 09:41 AM,

Re: [OpenStack-Infra] Final plans before translations switch to Zanata

2015-08-26 Thread Elizabeth K. Joseph
On Wed, Aug 26, 2015 at 3:51 PM, Carlos Munoz camu...@redhat.com wrote: Hi Elizabeth, I will get working on some instructions for the migration of the user data. Just to be clear, I'm assuming that what you want migrated is: - List of languages I understand that this one is tied to

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Dmitry Tantsur
On 08/25/2015 07:38 PM, Chris Dent wrote: WSME version 0.8.0 was released today with several fixes to error handling and error messages. These fixes make WSME behave more in the way it says it would like to behave (and should behave) with regard to input validation and HTTP handling. You want

[openstack-dev] [neutron][SR-IOV] deprecate agent_required option for SR-IOV mechanism driver

2015-08-26 Thread Moshe Levi
Hi all, When SR-IOV introduce in Juno the SR-IOV Agent supported only link state change. Some Intel cards don't support setting link state, so to resolve it the SR-IOV mechanism driver supports agent and agent less mode. From Liberty the SR-IOV agent brings more functionality like qos and port

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Renat Akhmerov
Chris, What would be your recommendation for now? Just to cap wsme version and hold on with changes adjusting to WSME 0.8.0? Or you think most likely these changes in new WSME will remain on? Thanks Renat Akhmerov @ Mirantis Inc. On 26 Aug 2015, at 14:27, Chris Dent chd...@redhat.com

[openstack-dev] [magnum] versioned objects changes

2015-08-26 Thread Grasza, Grzegorz
Hi, I noticed that right now, when we make changes (adding/removing fields) in https://github.com/openstack/magnum/tree/master/magnum/objects , we don't change object versions. The idea of objects is that each change in their fields should be versioned, documentation about the change should

[Openstack] RBAC Functionality in Keystone (Kilo)

2015-08-26 Thread sachin trivedi
Hi Experts, I am trying to setup multi-tenancy where my requirement is to map user's with specified regions. Currently we have mapping Project + Customer. What I am trying to achieve is whenever I launch an instance it ask which region you want to launch the resources and those resources should

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Chris Dent
On Wed, 26 Aug 2015, Dmitry Tantsur wrote: Note that this is an API breaking change, which can potentially break random users of all projects using wsme. I think we should communicate this point a bit louder, and I also believe it should have warranted a major version bump. Yeah, Lucas and I

[Openstack] the stack of server_console.yaml can't show novnc console url

2015-08-26 Thread Pan, Fengyun
Hello, stevebaker. I think there is a problem about the temple file which at following internal site. https://github.com/openstack/heat-templates/blob/master/hot/server_console.yaml When using the template file to create stack, I can’t get novnc console url: - $ heat output-show

[openstack-dev] [api][keystone][openstackclient] Standards for object name attributes and filtering

2015-08-26 Thread Henry Nash
Hi With keystone, we recently came across an issue in terms of the assumptions that the openstack client is making about the entities it can show - namely that is assumes all entries have a ‘name’ attribute (which is how the openstack show command works). Turns out, that not all keystone

Re: [openstack-dev] [fuel] Branching strategy vs feature freeze

2015-08-26 Thread Thierry Carrez
Dmitry Borodaenko wrote: TL;DR was actually hidden in the middle of the email, here's an even shorter version: 0) we're suffering from closing master for feature work for too long 1) continuously rebased future branch is most likely a no-go 2) short FF (SCF and stable branch after 2

Re: [openstack-dev] [ANN] OpenStack Kilo on Ubuntu fully automated with Ansible! Ready for NFV L2 Bridges via Heat!

2015-08-26 Thread Thierry Carrez
Martinx - ジェームズ wrote: I'm proud to announce an Ansible Playbook to deploy OpenStack on Ubuntu! Check it out! * https://github.com/sandvine/os-ansible-deployment-lite How does it compare with the playbooks developed as an OpenStack project by the OpenStackAnsible team[1] ? Any benefit,

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Renat Akhmerov
On 26 Aug 2015, at 13:40, Dmitry Tantsur dtant...@redhat.com wrote: On 08/25/2015 07:38 PM, Chris Dent wrote: WSME version 0.8.0 was released today with several fixes to error handling and error messages. These fixes make WSME behave more in the way it says it would like to behave (and

[openstack-dev] [magnum-ui] Status of Magnum UI

2015-08-26 Thread Jay Lau
Hi, I see that we already have a magnum ui team, just wondering what is the current status of this project? I'm planning a PoC and want to see if there are some current magnum ui work that I can leverage. -- Thanks, Jay Lau (Guangya Liu)

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Lucas Alvares Gomes
Hi, +1, yeah I kinda agree with the major version bump. But also it's important to note that Ironic which was affected by that was relying on be able to POST nonexistent fields to create resources and WSME would just ignore those on versions = 0.8.0. That's a legitimate bug that have been

[openstack-dev] [ceilometer] now using a grenade plugin

2015-08-26 Thread Chris Dent
Since it provides an opportunity to do some interesting things I thought I should announce that ceilometer has left the core of grenade and is now running its own 'gate-grenade-dsvm-ceilometer' job that uses a grenade plugin hosted in the ceilometer repo. At the moment the plugin does the bare

Re: [openstack-dev] [oslo] incubator move to private modules

2015-08-26 Thread Flavio Percoco
On 25/08/15 06:01 -0400, Davanum Srinivas wrote: Morgan, Bit more radical :) I am inclined to just yank all code from oslo-incubator and let the projects modify/move what they have left into their own package/module structure (and change the contracts however they see fit). Glad this

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Lingxian Kong
Hi, Chris, Thanks for bringing this up, and let us know. The same issues also affected Mistral :-( On Wed, Aug 26, 2015 at 1:38 AM, Chris Dent chd...@redhat.com wrote: WSME version 0.8.0 was released today with several fixes to error handling and error messages. These fixes make WSME behave

Re: [openstack-dev] [ceilometer] jenkis job failures

2015-08-26 Thread Chris Dent
On Wed, 26 Aug 2015, Ryota Mibu wrote: Quick note to ceilometer folks. Many check and gate jobs for ceilometer are failed due to WSME related issue that is already addressed by [1], so please make sure your patch set are rebased on the current master before execute 'recheck'. Thanks for

Re: [openstack-dev] [neutron][vpnaas] Need community guidance please...

2015-08-26 Thread Germy Lure
Hi, Maybe I missed some key points. But why we introduced vpn-endpoint groups here? ipsec-site-connection for IPSec VPN only, gre-connection for GRE VPN only, and mpls-connection for MPLS VPN only. You see, different connections for different vpn types. Indeed, We can't reuse connection API.

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Lucas Alvares Gomes
On Wed, Aug 26, 2015 at 9:27 AM, Chris Dent chd...@redhat.com wrote: On Wed, 26 Aug 2015, Dmitry Tantsur wrote: Note that this is an API breaking change, which can potentially break random users of all projects using wsme. I think we should communicate this point a bit louder, and I also

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Renat Akhmerov
Ok, thanks. We’ll fix it in Mistral accordingly. Renat Akhmerov @ Mirantis Inc. On 26 Aug 2015, at 15:12, Dmitry Tantsur dtant...@redhat.com wrote: On 08/26/2015 11:05 AM, Lucas Alvares Gomes wrote: On Wed, Aug 26, 2015 at 9:27 AM, Chris Dent chd...@redhat.com wrote: On Wed, 26 Aug 2015,

Re: [openstack-dev] [oslo] incubator move to private modules

2015-08-26 Thread Thierry Carrez
Flavio Percoco wrote: On 25/08/15 06:01 -0400, Davanum Srinivas wrote: Morgan, Bit more radical :) I am inclined to just yank all code from oslo-incubator and let the projects modify/move what they have left into their own package/module structure (and change the contracts however they see

Re: [openstack-dev] [oslo] incubator move to private modules

2015-08-26 Thread Davanum Srinivas
yep ttx. this will be for Mitaka. -- Dims On Wed, Aug 26, 2015 at 6:18 AM, Thierry Carrez thie...@openstack.org wrote: Flavio Percoco wrote: On 25/08/15 06:01 -0400, Davanum Srinivas wrote: Morgan, Bit more radical :) I am inclined to just yank all code from oslo-incubator and let

[Openstack] [neutron][SR-IOV] deprecate agent_required option for SR-IOV mechanism driver

2015-08-26 Thread Moshe Levi
Hi all, When SR-IOV introduce in Juno the SR-IOV Agent supported only link state change. Some Intel cards don't support setting link state, so to resolve it the SR-IOV mechanism driver supports agent and agent less mode. From Liberty the SR-IOV agent brings more functionality like qos and port

Re: [openstack-dev] [fuel] Branching strategy vs feature freeze

2015-08-26 Thread Igor Marnat
Thierry, Dmitry, key point is that we in Fuel need to follow as much community adopted process as we can, and not to introduce something Fuel specific. We need not only to avoid forking code, but also to avoid forking processes and approaches for Fuel. Both #2 and #3 allow it, making it easier

Re: [Openstack] [ceilometer] Monitoring resources outside OpenStack

2015-08-26 Thread Pradeep Sathasivam (CW)
Thanks Shinobu. I still don’t understand how this resource will be managed as it is outside of openstack. Regards, Pradeep. S From: Shinobu [mailto:shinobu...@gmail.com] Sent: Tuesday, August 25, 2015 6:32 PM To: Pradeep Sathasivam (CW) Cc: openstack@lists.openstack.org Subject: Re: [Openstack]

[Openstack-operators] Juno and Kilo Interoperability

2015-08-26 Thread Eren Türkay
Hello operators, I am wondering if anyone is using different versions of Openstack in different sites. We have our first site which is Juno, and we are now having another site where we are planning to deploy Kilo. Does anyone have experience with different versions of installation? Particularly,

Re: [openstack-dev] [neutron][vpnaas] Need community guidance please...

2015-08-26 Thread Paul Michali
See @PCM inline... On Wed, Aug 26, 2015 at 4:44 AM Germy Lure germy.l...@gmail.com wrote: Hi, Maybe I missed some key points. But why we introduced vpn-endpoint groups here? @PCM For the multiple local subnet capabilities for IPSec, the existing API would need to be changed, so that we

Re: [Openstack-operators] [openstack-dev] PLEASE READ: VPNaaS API Change - not backward compatible

2015-08-26 Thread Paul Michali
James, Great stuff! Please see @PCM in-line... On Tue, Aug 25, 2015 at 6:26 PM James Dempsey jam...@catalyst.net.nz wrote: Oops, sorry about the blank email. Answers/Questions in-line. On 26/08/15 07:46, Paul Michali wrote: Previous post only went to dev list. Ensuring both and adding a

Re: [openstack-dev] [Openstack-operators] PLEASE READ: VPNaaS API Change - not backward compatible

2015-08-26 Thread Paul Michali
James, Great stuff! Please see @PCM in-line... On Tue, Aug 25, 2015 at 6:26 PM James Dempsey jam...@catalyst.net.nz wrote: Oops, sorry about the blank email. Answers/Questions in-line. On 26/08/15 07:46, Paul Michali wrote: Previous post only went to dev list. Ensuring both and adding a

Re: [Openstack-operators] Juno and Kilo Interoperability

2015-08-26 Thread Eren Türkay
On 26-08-2015 17:17, Jonathan Proulx wrote: We recently upgraded from Juno to Kilo and many of our clients (including Horizon) are still Juno with no problems. Great news. That's our use case. We will have Juno clients and Kilo API endpoints. Thank you for your help. -- Eren Türkay, System

[openstack-dev] [DevStack] Proposing a revert for $OVS_DATAPATH_TYPE

2015-08-26 Thread Sean M. Collins
Hi, This was a bit of a mistake on my part, I recently put together some hardware in my home lab to try and rebuild a lab that is similar to the lab I had, where I developed the support for provider networking, which was documented in the following guide:

Re: [openstack-dev] mock 1.3 breaking all of Kilo in Sid (and other cases of this kind)

2015-08-26 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/26/2015 03:34 PM, Thomas Goirand wrote: On 08/25/2015 08:59 PM, Matt Riedemann wrote: On 8/25/2015 10:04 AM, Thomas Goirand wrote: On 08/25/2015 03:42 PM, Thomas Goirand wrote: Hi, [...] Anyway, the result is that mock 1.3 broke 9

Re: [Openstack-operators] Juno and Kilo Interoperability

2015-08-26 Thread Jonathan Proulx
Juno clients with Kilo endpoints are fine. We recently upgraded from Juno to Kilo and many of our clients (including Horizon) are still Juno with no problems. We also had a Kilo Horizon (for testing) running against Juno endpoints prior to the upgrade and that seemed to work as well but it

[openstack-dev] [nova] python-novaclient release 2.27.0 planned for 9/1

2015-08-26 Thread Matt Riedemann
The last python-novaclient release (2.26.0) was released on 6/3. Soft dependency freeze is Thursday 9/3. So we plan on doing a python-novaclient 2.27.0 release on Tuesday 9/1. As of today, this is the list of changes since 2.26.0: http://paste.openstack.org/show/428347/ Andrey requested

Re: [openstack-dev] [puppet][keystone] Keystone resource naming with domain support - no '::domain' if 'Default'

2015-08-26 Thread Morgan Fainberg
This seems quite reasonable. +1 Sent via mobile On Aug 25, 2015, at 13:30, Rich Megginson rmegg...@redhat.com wrote: This concerns the support of the names of domain scoped Keystone resources (users, projects, etc.) in puppet. At the puppet-openstack meeting today [1] we decided that

Re: [openstack-dev] [DevStack] Proposing a revert for $OVS_DATAPATH_TYPE

2015-08-26 Thread Sean M. Collins
Ah, I did not have enough coffee, my control node wasn't synced and didn't pick up PHYSICAL_NETWORK - that'll do it. Now I look like a moron. Sorry for the panic I may have caused -- Sean M. Collins __ OpenStack Development

Re: [openstack-dev] [stable] [infra] How to auto-generate stable release notes

2015-08-26 Thread Doug Hellmann
Excerpts from Robert Collins's message of 2015-08-19 11:04:37 +1200: On 18 August 2015 at 01:46, Thierry Carrez thie...@openstack.org wrote: Following on from the IRC discussion about release notes. ttx * we want consumers of the stable branch (from random commit and from tagged versions)

[openstack-dev] [grenade][cinder] Updates of rootwrap filters

2015-08-26 Thread Dulko, Michal
Hi, Recently when working on a simple bug [1] I've run into a need to change rootwrap filters rules for a few commands. After sending fix to Gerrit [2] it turns out that when testing the upgraded cloud grenade haven't copied my updated volume.filters file, and therefore failed the check. I

[openstack-dev] [requirements] dependencies problem on different release

2015-08-26 Thread Gareth
Hey guys, I have a question about dependencies. There is an example: On 2014.1, project A is released with its dependency in requirements.txt which contains: foo=1.5.0 bar=2.0.0,2.2.0 and half a year later, the requirements.txt changes to: foo=1.7.0 bar=2.1.0,2.2.0 It looks fine, but

[openstack-dev] [nova] CI for reliable live-migration

2015-08-26 Thread Timofei Durakov
Hello, Here is the situation: nova has live-migration feature but doesn't have ci job to cover it by functional tests, only gate-tempest-dsvm-multinode-full(non-voting, btw), which covers block-migration only. The problem here is, that live-migration could be different, depending on how instance

Re: [openstack-dev] [magnum] devstack/heat problem with master_wait_condition

2015-08-26 Thread Sergey Kraynev
Hi Stanislaw, Your host with Fedora should have special config file, which will send signal to WaitCondition. For good example please take a look this template https://github.com/openstack/heat-templates/blob/819a9a3fc9d6f449129c8cefa5e087569340109b/hot/native_waitcondition.yaml

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Chris Dent
On Wed, 26 Aug 2015, Renat Akhmerov wrote: What would be your recommendation for now? Just to cap wsme version and hold on with changes adjusting to WSME 0.8.0? Or you think most likely these changes in new WSME will remain on? The fixes in WSME are fixes for genuine bugs. If code using WSME

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Dmitry Tantsur
On 08/26/2015 11:05 AM, Lucas Alvares Gomes wrote: On Wed, Aug 26, 2015 at 9:27 AM, Chris Dent chd...@redhat.com wrote: On Wed, 26 Aug 2015, Dmitry Tantsur wrote: Note that this is an API breaking change, which can potentially break random users of all projects using wsme. I think we should

Re: [openstack-dev] [neutron][lbaas] L7 - Tasks

2015-08-26 Thread Samuel Bercovici
Hi, I think that Evgeny is trying to complete everything bedsides the reference implementation (API, CLI, Tempest, etc.). Evgeny will join the Octavia IRC meeting so it could be a good opportunity to get status and sync activities. As far as I know 8/31 is feature freeze and not code complete.

Re: [openstack-dev] [neutron][networking-ovn][tempest] devstack: gate-tempest-dsvm-networking-ovn failures in Openstack CI

2015-08-26 Thread Russell Bryant
On 08/25/2015 03:02 PM, Assaf Muller wrote: On Tue, Aug 25, 2015 at 2:15 PM, Russell Bryant rbry...@redhat.com mailto:rbry...@redhat.com wrote: On 08/25/2015 01:26 PM, Amitabha Biswas wrote: Russell suggested removing the MYSQL_DRIVER=MySQL-python declaration from

Re: [openstack-dev] mock 1.3 breaking all of Kilo in Sid (and other cases of this kind)

2015-08-26 Thread Thomas Goirand
On 08/25/2015 08:59 PM, Matt Riedemann wrote: On 8/25/2015 10:04 AM, Thomas Goirand wrote: On 08/25/2015 03:42 PM, Thomas Goirand wrote: Hi, [...] Anyway, the result is that mock 1.3 broke 9 packages at least in Kilo, currently in Sid [1]. Maybe, as packages gets rebuilt, I'll get more

Re: [openstack-dev] [ceilometer] now using a grenade plugin

2015-08-26 Thread Sean Dague
On 08/26/2015 05:14 AM, Chris Dent wrote: Since it provides an opportunity to do some interesting things I thought I should announce that ceilometer has left the core of grenade and is now running its own 'gate-grenade-dsvm-ceilometer' job that uses a grenade plugin hosted in the ceilometer

Re: [openstack-dev] [ANN] OpenStack Kilo on Ubuntu fully automated with Ansible! Ready for NFV L2 Bridges via Heat!

2015-08-26 Thread Kevin Carter
+1 I'd love to know this too. Additionally, if vagrant is something that is important to folks in the greater community it would be great to get some of those bits upstreamed. Per the NFV options, I don't see much in the way of OSAD not being able to support that presently, its really a

Re: [Openstack-operators] IP - availability monitoring

2015-08-26 Thread Kris G. Lindgren
Hello, As you know, much discussion has been around the naming and the url pathing for the ip-usages extension. We also discussed this at the neutron mid-cycle as well. Since we are the ones the made the extension, we use the extension to help with scheduling in our layer 3 network design.

Re: [Openstack-operators] Juno and Kilo Interoperability

2015-08-26 Thread Matt Riedemann
On 8/26/2015 9:30 AM, Eren Türkay wrote: On 26-08-2015 17:17, Jonathan Proulx wrote: We recently upgraded from Juno to Kilo and many of our clients (including Horizon) are still Juno with no problems. Great news. That's our use case. We will have Juno clients and Kilo API endpoints. Thank

Re: [openstack-dev] mock 1.3 breaking all of Kilo in Sid (and other cases of this kind)

2015-08-26 Thread Matt Riedemann
On 8/26/2015 9:15 AM, Ihar Hrachyshka wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/26/2015 03:34 PM, Thomas Goirand wrote: On 08/25/2015 08:59 PM, Matt Riedemann wrote: On 8/25/2015 10:04 AM, Thomas Goirand wrote: On 08/25/2015 03:42 PM, Thomas Goirand wrote: Hi, [...]

Re: [openstack-dev] [nova] CI for reliable live-migration

2015-08-26 Thread Matt Riedemann
On 8/26/2015 3:21 AM, Timofei Durakov wrote: Hello, Here is the situation: nova has live-migration feature but doesn't have ci job to cover it by functional tests, only gate-tempest-dsvm-multinode-full(non-voting, btw), which covers block-migration only. The problem here is, that

Re: [openstack-dev] [grenade][cinder] Updates of rootwrap filters

2015-08-26 Thread Eric Harney
On 08/26/2015 09:57 AM, Dulko, Michal wrote: Hi, Recently when working on a simple bug [1] I've run into a need to change rootwrap filters rules for a few commands. After sending fix to Gerrit [2] it turns out that when testing the upgraded cloud grenade haven't copied my updated

Re: [openstack-dev] mock 1.3 breaking all of Kilo in Sid (and other cases of this kind)

2015-08-26 Thread Thomas Goirand
On 08/25/2015 11:20 PM, Robert Collins wrote: This first happened with PBR. Kilo can't use = 1.x This is due to Kilo having *inappropriate* version caps on its dependencies. Which we've been busy unwinding and fixing infrastructure this cycle to avoid having it happen again on Liberty.

Re: [openstack-dev] [neutron][networking-ovn][tempest] devstack: gate-tempest-dsvm-networking-ovn failures in Openstack CI

2015-08-26 Thread Amitabha Biswas
With the recent commits it seems that the gate-tempest-dsvm-networking-ovn is succeeding more or less every time. The DBDeadlock issues still are seen on q-svc logs but are not frequent enough to cause ovsdb failures that were leading to the dsvm-networking failing before. Once in a while a

  1   2   >