Re: [openstack-dev] [trove] Adding release notes to changes

On 04/16/2016 05:07 PM, Amrith Kumar wrote: > Folks, > > We are now using reno[1] for release notes in trove, trove-dashboard, > and python-troveclient. Note that the trove-dashboard changes are not published and tested at all, you do not have set it up in project-config yet, Andreas > [...] --

[openstack-dev] [TripleO][CI] Tempest sources for testing tripleo in CI environment

Hi, John raised up the issue - where should we take tempest sources from. I'm not sure where to take them from, so I bring it to wider discussion. Right now I use tempest from delorean packages. In comparison with original tempest I don't see any difference in tests, only additional

Re: [openstack-dev] [OpenStack-docs] [docs] Our Install Guides Only Cover Defcore - What about big tent?

On 04/13/2016 08:01 PM, Amrith Kumar wrote: > Andreas, > > Thanks for your email. I am aware of the reviews you describe below but I was > still under the impression that the status from the email on openstack-docs > (Mitaka Install Guide testing) [1] and [2] were still valid. > > The

[openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

I am organizing a summit session for the cross-project track to (re)consider how we manage our list of global dependencies [1]. Some of the changes I propose would have a big impact, and so I want to ensure everyone doing packaging work for distros is available for the discussion. Please review

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Monty Taylor's message of 2016-04-17 10:34:36 -0500: > On 04/17/2016 10:13 AM, Doug Hellmann wrote: > > I am organizing a summit session for the cross-project track to > > (re)consider how we manage our list of global dependencies [1]. > > Some of the changes I propose would have a

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 04/17/2016 10:34 AM, Monty Taylor wrote: > On 04/17/2016 10:13 AM, Doug Hellmann wrote: >> I am organizing a summit session for the cross-project track to >> (re)consider how we manage our list of global dependencies [1]. >> Some of the changes I propose would have a big impact, and so I >>

Re: [openstack-dev] [trove] Adding release notes to changes

> -Original Message- > From: Andreas Jaeger [mailto:a...@suse.com] > Sent: Sunday, April 17, 2016 4:31 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [trove] Adding release notes to changes > > On

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 04/17/2016 10:13 AM, Doug Hellmann wrote: I am organizing a summit session for the cross-project track to (re)consider how we manage our list of global dependencies [1]. Some of the changes I propose would have a big impact, and so I want to ensure everyone doing packaging work for distros is

[openstack-dev] [oslo][keystone][documentation][gate] Babel dependency for oslo.log

Hi Oslo folks, Andreas and others, Over the weekend oslo.log 3.4.0 was released. This broke keystone CI jobs [2], even though the 3.4.0 was not specified in upper-constraints as keystone jobs were not honoring the upper-constraints.txt, so we fixed it in [3]. So the first big problem after [3]

[openstack-dev] [Nomad][DPACC]Call for ideas on Austin Nomad BoF Session

Hi All, We will have a birth of feather session on acceleration management in Austin. https://www.openstack.org/summit/austin-2016/summit-schedule/events/7380 I'm now soliciting ideas from the community, for those who is interested in this area please feel free to input any topics you want to

[openstack-dev] [nova-scheduler] Scheduler team meeting Monday, 2016.04.18 1400 UTC

Sorry for the late note, but busy weekend, etc. The next Nova Scheduler meeting will be tomorrow (Monday) at 1400 UTC in #openstack-meeting-alt http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160418T14 The agenda is posted here:

Re: [openstack-dev] [kolla][infra] Gate bused until Sunday April 17th

Here is the infra patch set that should fix the shade-nodepool issue. https://review.openstack.org/#/c/306835/ Thanks for the fix Monty! Regards, Vikram Hosakote IRC: vhosakot From: "Steven Dake (stdake)" > Reply-To:

[openstack-dev] [kolla][security][infra][ops] Kolla Design Summit Agenda Published

OpenStackers, The full Kolla summit agenda is here: https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?t=Kolla%3A We would super appreciate any operator presence in our fishbowl or design sessions so we do right by the Operators that use Kolla community generated code

Re: [openstack-dev] [Ironic][Neutron] Integration status

Hi Vasy, I am interested with this ironic-neutron integration to support VLAN, so can you help to share some doc/guide/steps for me, and let me try also? Thanks Haomeng On Thu, Mar 31, 2016 at 9:20 PM, Jim Rollenhagen wrote: > On Thu, Mar 31, 2016 at 03:37:53PM

Re: [openstack-dev] [opnfv-tech-discuss] [Nomad][DPACC]Call for ideas on Austin Nomad BoF Session

Updated the Etherpad with little bit more details . Thanks Srini On Sun, Apr 17, 2016 at 7:14 PM, Zhipeng Huang wrote: > Hi All, > > We will have a birth of feather session on acceleration management in > Austin. >

Re: [openstack-dev] [Tricircle] Error runnig py27

Hi, Khayam, Could you paste your whole file for test cases and the source code to be tested in the http://paste.openstack.org/ seperatly. Please share the links, so that to find out what happened. Best Regards Chaoyi Huang ( Joe Huang ) From: Khayam Gondal [mailto:khayam.gon...@gmail.com]

[openstack-dev] [all] Openstack rpm build

Hi all, In our developing environment, we want to create openstack's rpms by ourselves. By typing 'python setup.py bdist_rpm', there would be some files not packaged in. Now is there some tools or methods to package the openstack's module to rpms? Thank you for answering! Sincerely! Kenny

Re: [openstack-dev] [all] Openstack rpm build

On 04/18/2016 05:30 AM, Kenny Ji-work wrote: > Hi all, > > In our developing environment, we want to create openstack's rpms by > ourselves. By typing 'python setup.py bdist_rpm', there would be some > files not packaged in. Now is there some tools or methods to package the > openstack's module

[openstack-dev] [neutron] use hostname as nameserver when creating subnet

Hi all Can I use hostname as a nameserver when creating or updating a subnet? I noticed that both ip and hostname are checked in neutron/api/attributes.py with _validate_nameservers. But only ip address is allowed in _validate_subnet in db_base_plugin_v2.py Thanks Sun --

Re: [openstack-dev] [oslo][keystone][documentation][gate] Babel dependency for oslo.log

On 04/17/2016 09:15 PM, Davanum Srinivas wrote: > Hi Oslo folks, Andreas and others, > > Over the weekend oslo.log 3.4.0 was released. This broke keystone CI > jobs [2], even though the 3.4.0 was not specified in upper-constraints > as keystone jobs were not honoring the upper-constraints.txt, so

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

Agree. Install guide is just a start/example, concentrate is better than cover all, for more services we can just provide a good place to let them discoverable, and lfor arger scale, we should use advanced tools such as puppet and ansible On Mon, Apr 4, 2016 at 6:12 PM, Thierry Carrez

[openstack-dev] [mistral] Cancel team meeting today?

Team, I would suggest that we cancel today’s IRC meeting, most people look busy with the summit preparations. If anyone would like to meet though then I’m ready. Please reply here if you have topics to discuss. We can also catch each other at #openstack-mistral channel. Renat Akhmerov @Nokia

[openstack-dev] [keystone][horizon] new service for user management and admin tasks with keystone

Hello OpenStack-dev, We have been developing a new service for our cloud called StackTask and last week it went live. It is presently used to allow users to self manage additional users and roles on their projects without being admin, but in future will grow to handle other normally admin