Re: [openstack-dev] [ironic] Looking for a good end-to-end demo of ironic integrated within openstack

2017-07-28 Thread Waines, Greg
thanks Sam What’s the 100,000 foot view of how ironic manages the configuration of a baremetal server when it is booting an end-user’s OS image ? e.g. my best guess so far from looking at ironic documentation · ironic first deploys the ironic-python-agent to the server o

[openstack-dev] [nova] placement/resource providers update 30

2017-07-28 Thread Chris Dent
Placement Update 30 # What Matters Most Claims in the scheduler has merged, but first there was much gnashing of teeth and pulling of hair at the many twisted webs we've weaved in the scheduler and the resource tracker. While the base functionality is now in master, it's not certain that it

Re: [openstack-dev] [nova] placement/resource providers update 30

2017-07-28 Thread Chris Dent
On Fri, 28 Jul 2017, Chris Dent wrote: I thought there were going to be some changes to the resource tracker made overnight, related to ensuring allocations on the source and destination of a move are managed correctly, but I don't see them yet. If they get pushed up today can someone followup

Re: [openstack-dev] [Nova] Broken nova-lxd

2017-07-28 Thread Sean Dague
On 07/28/2017 12:58 AM, Tony Breeds wrote: > On Fri, Jul 28, 2017 at 10:55:53AM +0800, ChangBo Guo wrote: >> For the specific case with method "last_bytes", it's also used in other >> projects [1], an alternative solution is that add this method in >> oslo.utils.fileutils, then consume it from

Re: [openstack-dev] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

2017-07-28 Thread Doug Hellmann
Excerpts from Andreas Jaeger's message of 2017-07-28 09:12:59 +0200: > On 2017-07-27 21:40, Doug Hellmann wrote: > > [...] > > Please encourage everyone there to explore options that require the > > least amount of effort. An ideal solution is one we can implement > > without heroic efforts or

Re: [openstack-dev] [neutron] Call for help with in-tree tempest scenario test failures

2017-07-28 Thread Sławek Kapłoński
Hello, I will try to check QoS tests in this job. — Best regards Slawek Kaplonski sla...@kaplonski.pl > Wiadomość napisana przez Jakub Libosvar w dniu > 28.07.2017, o godz. 14:49: > > Hi all, > > as sending out a call for help with our precious jobs was very >

[openstack-dev] [ironic] PTG planning etherpad

2017-07-28 Thread Dmitry Tantsur
Hi all! It was already announced on the meeting, but not on the ML. Here is our planning etherpad for the PTG: https://etherpad.openstack.org/p/ironic-queens-ptg Please check "The Rules" section before proposing a topic. Please also add yourself to the list of potential attendees in the

Re: [openstack-dev] [magnum] Interface configuration and assumptions for masters/minions launched by magnum

2017-07-28 Thread Waines, Greg
Thanks for the info Mark. A dumb question ... can’t seem to find the answer in ironic documentation ... · I understand how the interface over which the bare metal instance network boots/installs gets configured ... i.e. thru DHCP response/configuration from the ironic conductor

Re: [openstack-dev] [tempest][infra][congress] subprocess launched in tempest test lacks file permission

2017-07-28 Thread Jeremy Stanley
On 2017-07-27 20:37:49 -0700 (-0700), Eric K wrote: > A tempest test [1] launches additional instances of Congress using > subprocess.popen and tests the coordination between them and the original > instance launched by devstack. The problem is, the new instances are > launched from the tempest

[openstack-dev] [horizon] Pike-3, Feature Freeze, and next steps

2017-07-28 Thread Rob Cresswell
Hey everyone, We tagged Horizons Pike-3 milestone about 12 hours, so I wanted to quickly run through the next steps for the release. At this point, we are in "Feature Freeze" and also "Soft String Freeze". - Feature Freeze - No new features (blueprints or wishlist bugs) can be merged without

Re: [openstack-dev] [ironic] Looking for a good end-to-end demo of ironic integrated within openstack

2017-07-28 Thread Sam Betts (sambetts)
Information about the ironic deployment process including full workflows can be found here: https://docs.openstack.org/ironic/latest/user/index.html#deploy-process Sam On 28/07/2017, 12:49, "Waines, Greg" > wrote: thanks Sam What’s

Re: [openstack-dev] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

2017-07-28 Thread Doug Hellmann
Excerpts from Dmitry Tantsur's message of 2017-07-28 12:29:29 +0200: > On 07/28/2017 09:12 AM, Andreas Jaeger wrote: > > On 2017-07-27 21:40, Doug Hellmann wrote: > >> [...] > >> Please encourage everyone there to explore options that require the > >> least amount of effort. An ideal solution is

Re: [openstack-dev] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

2017-07-28 Thread Dmitry Tantsur
On 07/28/2017 09:12 AM, Andreas Jaeger wrote: On 2017-07-27 21:40, Doug Hellmann wrote: [...] Please encourage everyone there to explore options that require the least amount of effort. An ideal solution is one we can implement without heroic efforts or having to recruit an army of

Re: [openstack-dev] [tripleo] Proposing Bogdan Dobrelya core on TripleO / Containers

2017-07-28 Thread Wesley Hayutin
On Wed, Jul 26, 2017 at 7:39 AM, Jiří Stránský wrote: > On 21.7.2017 16:55, Emilien Macchi wrote: > >> Hi, >> >> Bogdan (bogdando on IRC) has been very active in Containerization of >> TripleO and his quality of review has increased over time. >> I would like to give him core

[openstack-dev] [neutron] Call for help with in-tree tempest scenario test failures

2017-07-28 Thread Jakub Libosvar
Hi all, as sending out a call for help with our precious jobs was very successful last time and we swept all Python 3 functional from Neutron pretty fast (kudos the the team!), here comes a new round of failures. This time I'm asking for your help with

Re: [openstack-dev] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

2017-07-28 Thread Jeremy Stanley
On 2017-07-28 08:34:18 -0400 (-0400), Doug Hellmann wrote: [...] > I wasn't able to come up with a way to disable the link without > triggering a new build. I didn't want us to have to land a patch in each > repo as part of marking it EOL, but if we're going to do that to remove > the installation

Re: [openstack-dev] [tempest][infra][congress] subprocess launched in tempest test lacks file permission

2017-07-28 Thread Andrea Frittoli
On Fri, Jul 28, 2017 at 4:38 AM Eric K wrote: > A tempest test [1] launches additional instances of Congress using > subprocess.popen and tests the coordination between them and the original > instance launched by devstack. The problem is, the new instances are >

[openstack-dev] [tripleo] CI Squad Meeting Summary (week 30) - holidays

2017-07-28 Thread Attila Darazs
If the topics below interest you and you want to contribute to the discussion, feel free to join the next meeting: Time: Thursdays, 14:30-15:30 UTC Place: https://bluejeans.com/4113567798/ Full minutes: https://etherpad.openstack.org/p/tripleo-ci-squad-meeting = Discussion topics = Wes

Re: [openstack-dev] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

2017-07-28 Thread Doug Hellmann
Excerpts from Jeremy Stanley's message of 2017-07-28 13:23:32 +: > On 2017-07-28 08:34:18 -0400 (-0400), Doug Hellmann wrote: > [...] > > I wasn't able to come up with a way to disable the link without > > triggering a new build. I didn't want us to have to land a patch in each > > repo as

[openstack-dev] [tripleo] Request to add neutron-server-[ovn/odl] to the tripleoupstream docker hub

2017-07-28 Thread Numan Siddique
Hello, When we build the kolla images using the command [1], it builds neutron-server-ovn and neutron-server-odl which are not in tripleoupstream docker hub. Is it possible to upload them ? I am not sure if it is done manually or a script does it. neutron-server-ovn image is required to have a

Re: [openstack-dev] [Oslo] PTG Planning

2017-07-28 Thread ChangBo Guo
Just a reminder, please add your name and topic in the etherpad if you will join the discussion abouth Oslo at the PTG. 2017-07-10 21:48 GMT+08:00 ChangBo Guo : > Hi Oslo folks, > > I created a planning etherpad[1] for topics for the next PTG in Denver. > Please add any

Re: [openstack-dev] [openstack-ansible][security] To firewalld, or not to firewalld

2017-07-28 Thread Markos Chandras
On 07/26/2017 05:59 PM, Major Hayden wrote: > > firewalld disadvantages > --- > 1) Different distributions have different base rule sets Also different distributions offer different version of firewalld which means different behavior and possibly bugs between them. The

Re: [openstack-dev] [ceilometer][networking-sfc] Meters/Statistics for Networking-SFC

2017-07-28 Thread Mohan Kumar
Hi Rajeev, The Chain Monitoring is the missing piece in networking-sfc . Vikram and myself were discussed to introduce "SFC Manager" [1] (basically OAM tool ) few cycle before. It'll continuously monitor an existing SFC chain, when any SF VM goes down or any packet drop. It'll trigger alert and

Re: [openstack-dev] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

2017-07-28 Thread Andreas Jaeger
On 2017-07-28 01:10, Doug Hellmann wrote: > Excerpts from Doug Hellmann's message of 2017-07-27 19:05:16 -0400: >> Excerpts from Jeremy Stanley's message of 2017-07-27 22:07:33 +: >>> On 2017-07-27 15:40:22 -0400 (-0400), Doug Hellmann wrote: >>> [...] Are we over-emphasizing the scale of

Re: [openstack-dev] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

2017-07-28 Thread Andreas Jaeger
On 2017-07-27 21:40, Doug Hellmann wrote: > [...] > Please encourage everyone there to explore options that require the > least amount of effort. An ideal solution is one we can implement > without heroic efforts or having to recruit an army of contributors. I agree with the points made in

Re: [openstack-dev] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

2017-07-28 Thread Andreas Jaeger
On 2017-07-27 21:40, Doug Hellmann wrote: > [...] > Regarding point 2, if we don't have the space to host the content > indefinitely, then we need to set a fixed, but longer, retention > period before deleting it. Several years, at least. In the mean > time, we could delete builds for

[openstack-dev] [tc] Technical Committee Status update, July 28th

2017-07-28 Thread Thierry Carrez
Hi! This is the weekly update on Technical Committee initiatives. You can find the full list of all open topics at: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee == Recently-approved changes == * Declare plainly the current state of PostgreSQL in OpenStack [1] * Clean up

Re: [openstack-dev] [magnum] Interface configuration and assumptions for masters/minions launched by magnum

2017-07-28 Thread Mark Goddard
Hi Greg, Magnum clusters currently support using only a single network for all communication. See the heat templates[1][2] in the drivers. . On the bare metal side, currently ironic effectively supports using only a single network interface due to a lack of support for physical network awareness.

[openstack-dev] [security][barbican] PTG room sharing

2017-07-28 Thread Luke Hinds
Hello Barbican Team, I believe there were some discussions on room sharing between the security project and barbican team. We are still keen on this in the security project. How would you like to work out logistics? Should we share PTG planning etherpads? We have 4 days between us, not sure if

Re: [openstack-dev] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

2017-07-28 Thread Thierry Carrez
Andreas Jaeger wrote: > On 2017-07-27 21:40, Doug Hellmann wrote: >> [...] >> Please encourage everyone there to explore options that require the >> least amount of effort. An ideal solution is one we can implement >> without heroic efforts or having to recruit an army of contributors. > > I

Re: [openstack-dev] [nova] placement/resource providers update 30

2017-07-28 Thread Jay Pipes
On 07/28/2017 09:47 AM, Chris Dent wrote: On Fri, 28 Jul 2017, Chris Dent wrote: I thought there were going to be some changes to the resource tracker made overnight, related to ensuring allocations on the source and destination of a move are managed correctly, but I don't see them yet. If

[openstack-dev] [all][ptl][stable][release] stable/pike branches created for most libraries

2017-07-28 Thread Doug Hellmann
As Thierry mentioned in his countdown email today, the release team has now created the stable branches for most deliverables with type "library". We have 3 exceptions: 1. python-neutronclient had a late release, so I will be branching it shortly. 2. python-barbicanclient was skipped until

Re: [openstack-dev] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

2017-07-28 Thread Jeremy Stanley
On 2017-07-28 15:37:07 -0400 (-0400), David Desrosiers wrote: [...] > You could compress the individual files, configure the webserver to send > the correct encoding (Content-Encoding: gzip or deflate) to the client > (assuming their browser sends the correct Accept-Encoding header) which can >

Re: [openstack-dev] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

2017-07-28 Thread Kevin Benton
Maybe we could just ban search engines from indexing the releases using robots.txt once they go EOL. That would solve the problem of losing old information for people that still need it while preventing people stumbling onto old docs when they search for something. On Fri, Jul 28, 2017 at 12:39

Re: [openstack-dev] [tempest][infra][congress] subprocess launched in tempest test lacks file permission

2017-07-28 Thread Eric K
Thanks for your help and sketch of solution, Andrea! -Eric From: Andrea Frittoli Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Friday, July 28, 2017 at 9:03 AM To: "OpenStack Development Mailing

Re: [openstack-dev] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

2017-07-28 Thread Jeremy Stanley
On 2017-07-28 15:32:01 -0400 (-0400), David Desrosiers wrote: [...] > I am very opposed to removing subsets of docs, including the install guide, > after the release goes eol upstream from consumers for exactly that reason. > > Watermarking the upstream docs with series and version should reduce

Re: [openstack-dev] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

2017-07-28 Thread David Desrosiers
On Thu, Jul 27, 2017 at 6:07 PM, Jeremy Stanley wrote: > The current solution of not publishing installation guides for EOL > releases seems like a > good enough compromise there to me. > This then breaks fidelity for those operators who need to either reinstall their

Re: [openstack-dev] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

2017-07-28 Thread David Desrosiers
On Thu, Jul 27, 2017 at 8:16 PM, Sean McGinnis wrote: > I like this approach. With the size being manageable (large, but > manageable), I would prefer we leave it until we need to free up > some of the space You could compress the individual files, configure the

[openstack-dev] [neutron] FFE for net-mtu-enh api extension requested

2017-07-28 Thread Ihar Hrachyshka
Hi PTL/all, I would like to request an exception for inclusion of net-mtu-enh API extension (with ML2 implementation) for Pike. The patch is ready for review, it includes tempest tests and docs update. There are several things in the patch that we will need to follow up in the next release

Re: [openstack-dev] [all] Cleaning up inactive meetbot channels

2017-07-28 Thread Andreas Jaeger
A change to remove these channels is now up at https://review.openstack.org/488544 I'll put this for one week in WIP to give teams the chance to -1 - and will pop in their channels to tell them about this as well, Andreas On 2017-07-19 21:24, Jeremy Stanley wrote: > For those who are unaware,

Re: [openstack-dev] [tempest][infra][congress] subprocess launched in tempest test lacks file permission

2017-07-28 Thread Eric K
Thanks for the suggestion, Jeremy. I¹ll look into that. Two key pieces will be needed: 1. Know ahead of time what user tempest tests would be run from (should be determined by job setup?) 2. Have a way to specify in job/devstack to start congress using that user. On 7/28/17, 6:30 AM, "Jeremy

[openstack-dev] [Nova] On idmapshift deprecation

2017-07-28 Thread Michael Still
Hi. I'm working through the process of converting the libvirt driver in Nova to privsep with the assistance of Tony Breeds. For various reasons, I started with removing all the calls to the chown binary and am replacing them with privsep equivalents. You can see this work at:

Re: [openstack-dev] [Cinder] Proposing TommyLikeHu for Cinder core

2017-07-28 Thread Mike Perez
On 03:07 Jul 25, Sean McGinnis wrote: > I am proposing we add TommyLike as a Cinder core. > > DISCLAIMER: We work for the same company. > > I have held back on proposing him for some time because of this conflict. But > I think from his number of reviews [1] and code contributions [2] it's >

Re: [openstack-dev] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

2017-07-28 Thread Sean McGinnis
On Fri, Jul 28, 2017 at 07:39:25PM +, Jeremy Stanley wrote: > On 2017-07-28 15:32:01 -0400 (-0400), David Desrosiers wrote: > [...] > > I am very opposed to removing subsets of docs, including the install guide, > > after the release goes eol upstream from consumers for exactly that reason. >

Re: [openstack-dev] [Cinder] Requirements for re-adding Gluster support

2017-07-28 Thread Matt Riedemann
On 7/26/2017 4:16 PM, Eric Harney wrote: From a technical point of view there are not a lot of steps involved here, we can restore the previous gate jobs and driver code and I expect things would still be in working order. I can help coordinate these things with the new owner. Note that the

[openstack-dev] [release] Release countdown for week R-4, July 28 - Aug 4

2017-07-28 Thread Thierry Carrez
Welcome to our regular release countdown email! Development Focus - Focus should be on fixing release-critical bugs in order to produce the first release candidates (for deliverables following the with-milestones model) or final Pike releases (for deliverables following the