[openstack-dev] [charms] 16.10 release feature freeze

Hi Charmers Just a reminder that as of the end of yesterday, we're in feature freeze for the 16.10 charm release in two weeks time; if you have a compelling feature that you feel should be considered, please email openstack-dev with a request for a freeze exception with details of the change (and

Re: [openstack-dev] [ironic] Next API meeting cancelled

On 09/22/2016 05:38 PM, Jim Rollenhagen wrote: We decided in the last meeting to cancel next week's meeting. So we'll meet again October 4. Side question: should we just make this meeting biweekly always? +1 for biweekly. This way I'll maybe find courage to stay until 9pm :) // jim ___

[openstack-dev] [telemetry] Barcelona summit session proposals

Hi team, It's time to propose your session ideas at: https://etherpad.openstack.org/p/ocata-telemetry-summit-planning Be reminded that we he have 5 slots allocated. Cheers, -- Julien Danjou ;; Free Software hacker ;; https://julien.danjou.info signature.asc Description: PGP signature __

[openstack-dev] [ironic] notifications: searching for an optimal solution

Hi, If you interested in ironic notifications welcome to the discussion on https://review.openstack.org/#/c/347242/ Should we limit CRUD notifications to CRUD API requests? What ironic node's fields set should be in CRUD notifications? Your opinion is important for us. Yuriy Zveryanskyy ___

Re: [openstack-dev] [ceilometer] [Congress] ceilometer client `alarms.list()` HTTPException (HTTP N/A)

Hi Eric, alarm list is not working from before. I have disabled the same in Mitaka https://review.openstack.org/#/c/254650/ We need to support Aodh to get it working I suppose ( https://blueprints.launchpad.net/congress/+spec/add-aodh-datasource-driver) Best Regards, Anusha On 29 September 2016

[openstack-dev] [nova][cinder] reason(s) for not booting instances from (bootable) volumes

Hi! I refer here to my question sent earlier to AskOpenstack: https://ask.openstack.org/en/question/97425/why-it-is-not-possible-to-rebuild-an-instance-from-a-bootable-volume/ Are there some (architectural, performance, security etc.) reasons why rebuilding instances from (bootable) volumes is

Re: [openstack-dev] [ceilometer] [Congress] ceilometer client `alarms.list()` HTTPException (HTTP N/A)

Got it. Thanks for the refresher.Maybe it got re-enabled in the switch to support lazy polling. If you get a chance, would you mind disabling it again for Newton? _ From: Anusha Ramineni Sent: Friday, September 30, 2016 4:26 AM Subject: Re: [openstack-dev] [ceil

[openstack-dev] TC Candidacy

I would like to serve the community on the Technical Committee again. For those of you who don't know me: * I've served on the TC since it was the PPB. * I founded and am past-PTL of OpenStack Infra. * I also serve on the OpenStack Board of Directors as an Individual Member, which is a position

Re: [openstack-dev] [nova][cinder] reason(s) for not booting instances from (bootable) volumes

Nothing architectural that I can think of, we just don't support it. Rebuild current takes an image, but I guess it could reasonable take most of the arguments to spawn. We'd have to think hard about what it meant for arguments to be present/omitted, i.e. are we specifying new disks, or redefining

Re: [openstack-dev] [nova] Mirror issues with Intel NFV CI?

We've fixed the subnet pools issue and left all the jobs in non-voting for testing yesterday. There are issues with cinder volumes highlighted by tempest tests but we'll skip them for the time they're being trobuleshooted and we've put the jobs back to voting. Thanks >-Original Message--

[openstack-dev] [tricircle]

Hello , Myself Chandrakant Bagade , working at Persistent System Ltd. I was trying Tricircle with devstack and found it , a very helpful idea to datacenter management. I can see feature like provisioning , image/vm/volume management therein. I was wondering if features like monitoring/inventory

[openstack-dev] [Neutron] ARP spoofing in VLAN aware VMs

Hi all, I promised Armando a braindump of this issue so here it comes: During my work on fullstack test for VLAN aware VMs I ran into issues with ARP spoofing. The issue was with subports having different MAC addresses than MAC address of the parent port. Packets leaving virtual instance via V

[openstack-dev] [neutron] clean up your git checkout!

Hi all, today we landed https://review.openstack.org/#/c/269658/ (huge!) that removed neutron/objects/network/ directory and replaced it with neutron/objects/network.py file. Though it makes python that sees old .pyc files sad: Failed to import test module: neutron.tests.unit.objects.test

Re: [openstack-dev] [neutron] clean up your git checkout!

Ihar Hrachyshka wrote: Hi all, today we landed https://review.openstack.org/#/c/269658/ (huge!) that removed neutron/objects/network/ directory and replaced it with neutron/objects/network.py file. Though it makes python that sees old .pyc files sad: Failed to import test module: neutr

Re: [openstack-dev] [neutron] clean up your git checkout!

On 09/30/2016 04:06 PM, Ihar Hrachyshka wrote: > Ihar Hrachyshka wrote: > >> Hi all, >> >> today we landed https://review.openstack.org/#/c/269658/ (huge!) that >> removed neutron/objects/network/ directory and replaced it with >> neutron/objects/network.py file. Though it makes python that sees o

Re: [openstack-dev] [neutron] clean up your git checkout!

Michał Dulko wrote: On 09/30/2016 04:06 PM, Ihar Hrachyshka wrote: Ihar Hrachyshka wrote: Hi all, today we landed https://review.openstack.org/#/c/269658/ (huge!) that removed neutron/objects/network/ directory and replaced it with neutron/objects/network.py file. Though it makes python th

[openstack-dev] [tripleo] os-*-config branching

Just a quick FYI for TripleO team: Until now we didn't branch os-*-config projects but since we changed the release model to release:cycle-with-milestones, we are now producing milestones and RCs during the cycle. Which means we also need to start branching the projects. So starting from newton,

[openstack-dev] [openstack-ansible] What's Happening in OpenStack-Ansible (WHOA) - September 2016

Hey there, The September edition of the What's Happening in OpenStack-Ansible (WHOA) report is here! https://major.io/2016/09/30/whats-happening-in-openstack-ansible-whoa-september-2016/ The report includes the latest developments in Liberty, Mitaka, and Newton along with some news about Op

[openstack-dev] [tripleo] TripleO RC3

We have been granted to release a last release candidate (RC3) by next Friday (October 7th). Please use this milestone for the bugs targeted for Newton. https://launchpad.net/tripleo/+milestone/newton-rc3 Some reminders: - assign the bug if you're working on it. - update it when you can, we need

Re: [openstack-dev] [nova] Mirror issues with Intel NFV CI?

On 9/30/2016 7:46 AM, Znoinski, Waldemar wrote: We've fixed the subnet pools issue and left all the jobs in non-voting for testing yesterday. There are issues with cinder volumes highlighted by tempest tests but we'll skip them for the time they're being trobuleshooted and we've put the jobs b

Re: [openstack-dev] [cinder][db] lazy loading of an attribute impossible

Michał, You are absolutely right: this exception is raised when you try to lazy-load instance attributes outside a Session scope. There is an obvious problem with that - instances do not communicate with a DB on their own - it's left up to Session [1]. Unfortunately, it does not play nicely with

[openstack-dev] [release][ceilometer] ceilometer Newton RC3 available

Hello everyone, A new release candidate for ceilometer for the end of the Newton cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/ceilometer/ceilometer-7.0.0.0rc3.tar.gz Unless release-critical issues are found that warrant a release candidate respin,

[openstack-dev] [all] [release] project documentation updates not RC-worthy

Just want to send out a quick recap of a discussion in #openstack-meeting during the release team meeting this morning, in case any other projects are in a similar situation. As you're aware, the api-ref was moved out of docs and into the source code tree for each project this cycle. Since the ap

Re: [openstack-dev] [all] [release] project documentation updates not RC-worthy

On Fri, Sep 30, 2016 at 10:23 AM, Brian Rosmaita wrote: > Just want to send out a quick recap of a discussion in #openstack-meeting > during the release team meeting this morning, in case any other projects > are in a similar situation. > > As you're aware, the api-ref was moved out of docs and in

Re: [openstack-dev] [all] [release] project documentation updates not RC-worthy

On Fri, Sep 30, 2016 at 10:23 AM, Brian Rosmaita < brian.rosma...@rackspace.com> wrote: > Just want to send out a quick recap of a discussion in #openstack-meeting > during the release team meeting this morning, in case any other projects > are in a similar situation. > > As you're aware, the api-

Re: [openstack-dev] [nova][libvirt] Lets make libvirt's domain XML canonical

On 27/09/2016, 18:12, "Daniel P. Berrange" wrote: >On Tue, Sep 27, 2016 at 10:40:34AM -0600, Chris Friesen wrote: >> On 09/27/2016 10:17 AM, Matthew Booth wrote: >> >> > I think we should be able to create a domain, but once created we should >> > never >> > redefine a domain. We can do ad

Re: [openstack-dev] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

Thierry Carrez wrote: > As announced previously[1][2], there were no PTL candidates within the > election deadline for a number of official OpenStack project teams: > Astara, UX, OpenStackSalt and Security. > > In the Astara case, the current team working on it would like to abandon > the project

Re: [openstack-dev] [nova][libvirt] Lets make libvirt's domain XML canonical

On Fri, Sep 30, 2016 at 4:38 PM, Murray, Paul (HP Cloud) wrote: > > > > > > On 27/09/2016, 18:12, "Daniel P. Berrange" wrote: > > >On Tue, Sep 27, 2016 at 10:40:34AM -0600, Chris Friesen wrote: > >> On 09/27/2016 10:17 AM, Matthew Booth wrote: > >> > >> > I think we should be able to create a do

Re: [openstack-dev] [all] [release] project documentation updates not RC-worthy

On 09/30/2016 05:32 PM, Anne Gentle wrote: > Will you backport those doc changes to stable/newton so the published > version is accurate? Or does everyone only publish from master anyway? > We can start working on "stable branch" publishing next, if teams want it. We only publish from master. And

Re: [openstack-dev] [nova][libvirt] Lets make libvirt's domain XML canonical

From: Matthew Booth Reply-To: "openstack-dev@lists.openstack.org" Date: Friday, 30 September 2016 at 17:03 To: "openstack-dev@lists.openstack.org" Subject: Re: [openstack-dev] [nova][libvirt] Lets make libvirt's

Re: [openstack-dev] [tripleo] Getting the UI to talk with Undercloud API service endpoints

Hi - I re-read your email a few times and like a few of the things that I see, but I'd love some more clarification. As I read it, a few of these things conflict. I believe you're suggesting that we don't make these services listen on a public interface due to security concerns (and of course, e

Re: [openstack-dev] [neutron] clean up your git checkout!

Projects may want to add to their tox.ini something like this: https://github.com/openstack/ironic/blob/c445c19285c2f3ee6a099f9f7473dd6fe087116b/tox.ini#L10 Basically add: PYTHONDONTWRITEBYTECODE = 1 On Fri, Sep 30, 2016 at 7:20 AM, Ihar Hrachyshka wrote: > Michał Dulko wrote: > >> On 09/30/20

Re: [openstack-dev] [neutron] clean up your git checkout!

I tried that but even with it in place, a .tox directory with a ton of .pyc's was left around after the test. I'm assuming that this is OK? -amrith > -Original Message- > From: John Villalovos [mailto:openstack@sodarock.com] > Sent: Friday, September 30, 2016 1:57 PM > To: OpenStack

[openstack-dev] [release][horizon] horizon Newton RC3 available

Hello everyone, A new release candidate for horizon for the end of the Newton cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/horizon/horizon-10.0.0.0rc3.tar.gz Unless release-critical issues are found that warrant a release candidate respin, this can

Re: [openstack-dev] [tripleo] Getting the UI to talk with Undercloud API service endpoints

I don't think we can rely on the Undercloud as an API proxy unless we address the lack of HA on the Undercloud. Wouldn't this be better implemented as as a single, name-based HAProxy instance running SSL on port 443 on the overcloud Public VIP? Then we could have the same endpoint for Horizon

Re: [openstack-dev] [neutron] clean up your git checkout!

I want to say this happens if .tox is in your gitignore list. Just run tox with the -r flag which will rebuild the tox envs. Clark On Fri, Sep 30, 2016, at 11:22 AM, Amrith Kumar wrote: > I tried that but even with it in place, a .tox directory with a ton of > .pyc's was left around after the tes

[openstack-dev] [release][ptl] please review versions for final newton release

I have prepared a patch to openstack/releases to re-tag all of the current release candidates using their final release version numbers. I could use some assistance reviewing the results to ensure that I have not left anything out and that the version numbers are all correct. This patch also incl

[openstack-dev] OpenStack Developer Mailing List Digest September 24-30

HTML version: http://www.openstack.org/blog/2016/09/openstack-developer-mailing-list-digest-20160930/ Candidate Proposals for TC are now open === * Candidate proposals for the Technical committee (9 positions) are open and will remain open until 2016-10-01

Re: [openstack-dev] [neutron] clean up your git checkout!

Clark, I'm not sure what question you are answering but my question was more about the PYTHONDONTWRITEBYTECODE = 1 setting. I assumed that this meant that the .pyc's wouldn't be created. Did I misunderstand that? git clean -f -x -d does in fact clean out the .tox directory.

Re: [openstack-dev] [neutron] clean up your git checkout!

Sorry I crossed the streams but the advice is still good. Your existing virtualenvs already have .pycs in them so the easy way to clean that up is to rebuild your tox venvs using tox -r. Clark On Fri, Sep 30, 2016, at 12:01 PM, Amrith Kumar wrote: > Clark, > > I'm not sure what question you are

Re: [openstack-dev] [neutron] clean up your git checkout!

:) Clark ... If I git clone a brand new repository and edit the tox.ini with the proposed change: > > PYTHONDONTWRITEBYTECODE = 1 I had assumed that no .pyc's would get created. My comment is that even with this setting, .pyc's are getting created. To get around this, what we've done thu

Re: [openstack-dev] [tripleo] Getting the UI to talk with Undercloud API service endpoints

Thinking about this a little more, creating a new unified endpoint on the same port as the UI doesn't solve the problem at hand. The UI will use the service catalog to find endpoints, so we would need to change the endpoints in the service catalog, which changes the flow for the underlying servi

[openstack-dev] [nova][scheduler] Next Scheduler subteam meeting

The next meeting of the Nova Scheduler subteam will be on Monday, October 3 at 1400 UTC in #openstack-meeting-alt http://www.timeanddate.com/worldclock/fixedtime.html?iso=20161003T14 As always, the agenda is here: https://wiki.openstack.org/wiki/Meetings/NovaScheduler Please add any items y

Re: [openstack-dev] [neutron] clean up your git checkout!

On Fri, Sep 30, 2016 at 12:12 PM, Amrith Kumar wrote: > :) > > Clark ... > > If I git clone a brand new repository and edit the tox.ini with the proposed > change: > >> > PYTHONDONTWRITEBYTECODE = 1 > > I had assumed that no .pyc's would get created. That is correct for 'tox' runs. Doing a:

Re: [openstack-dev] TC candidacy

I have known Mr. Taylor for many years and I would like to come out as his first endorser for his big league thoughts and recommendations below. Brad Topol, Ph.D. IBM Distinguished Engineer OpenStack (919) 543-0646 Internet: bto...@us.ibm.com Assistant: Kendra Witherspoon (919) 254-0680 From

[openstack-dev] [app-catalog] Barcelona summit planning

Let's start noting session plans for our working sessions in Barcelona. I've started an etherpad here: https://etherpad.openstack.org/p/app-catalog-ocata-summit -Christopher __ OpenStack Development Mailing List (not for usa

Re: [openstack-dev] [TripleO][CI] Need more undercloud resources

of the gate-tripleo-ci-centos-7-ovb-nonha job as run on changes to tripleo-heat-templates. (Specifically, this is looking at the "used" column in dstat, which IIUC excludes kernel buffers and the page cache.) Here's the memory consumption history during the test of all 863 successf

Re: [openstack-dev] [tricircle]

Hello, Chandrakant, Thank you for your interest on Tricircle. There is no features about monitoring/inventory management yet in Tricircle. And Tricircle is cleaning to be a project dedicated for networking automation across Neutron, and API gateway related function will be moved to a new projec

Re: [openstack-dev] [neutron] clean up your git checkout!

Thanks to John and Clark Boylan for their help as I tried this setting out and tried to propose a change in Trove for this. In researching this some more, I found this[1] old email thread. I would like to submit to you the following set of comments from Mike Bayer, Doug Hellmann and Sean Dague.

[openstack-dev] [elections] TC candidacy

I'd like to throw my hat in the ring for the TC election. My name is Ben Swartzlander (bswartz on IRC) and I've been PTL for the Manila project for the entire life of the project. I'm also relatively active within the Cinder project, and I've been part of the OpenStack community since Essex.

Re: [openstack-dev] [neutron] clean up your git checkout!

> -Original Message- > From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] > Sent: Friday, September 30, 2016 7:03 AM > To: OpenStack Development Mailing List (not for usage questions) d...@lists.openstack.org> > Subject: [openstack-dev] [neutron] clean up your git checkout! > > Hi all,