[openstack-dev] [Neutron] Return request-id to caller

Hi neutron folks, We are adding support for returning ‘x-openstack-request-id’ to the caller as per the design proposed in cross-project specs: http://specs.openstack.org/openstack/openstack-specs/specs/return-request-id.html I proposed the feature into python-neutronclient[1]. The patch already

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Hi, Pengfei, I suppose you are using "internal network" in virtual box to connect your virtual machines, and I find a link that seems to related to your problem. https://forums.virtualbox.org/viewtopic.php?f=1&t=38037 BR Zhiyuan On 1 March 2016 at 11:14, Vega Cai wrote: > Hi, All, > > Let's m

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Hi, Zhiyuan. When I rebooted all the nodes. It works! I set the network device promiscuous type, and it don’t be useful until reboot… Thank you for suggestions! Best Regards Pengfei Shi (时鹏飞) Shanghai Jiao Tong University Network & Information Center Room 304 shipengfe...@gmail.com > O

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

Adrian, I disagree, host OS is very important for operators because of integration with all internal tools/repos/etc.   I think it make sense to limit OS support in Magnum main source. But not sure that Fedora Atomic is right choice,first of all there is no documentation about it and I don't thi

Re: [openstack-dev] [nova] A prototype implementation towards the "shared state scheduler"

Hi, I have simulated the distributed resource management with the incremental update model based on Jay's benchmarking framework: https://github.com/cyx1231st/placement-bench/tree/shared-state-demonstration. The complete result lies at http://paste.openstack.org/show/488677/. It's ran by a VM

Re: [openstack-dev] [all][log] Ideas to log request-ids in cross-projects

On 01.03.2016 07:17, Kekane, Abhishek wrote: > Hi Devs, > > Considering return request-id to caller specs [1] is implemented in > python-*client, I would like to begin discussion on how these request-ids > will be logged in cross-projects. In logging work-group meeting > (11-Nov-2015) > [2] there

Re: [openstack-dev] [Fuel] UI code freeze

The new repo has been created: https://github.com/openstack/fuel-ui. Please move all change requests there. Fuel UI code in fuel-web repo is going to be removed soon. 2016-02-26 19:53 GMT+07:00 Vladimir Kozhukalov : > Dear colleagues, > > We are ready for moving UI javascript code to a separate g

Re: [openstack-dev] [Neutron][ml2][Manila] API to query segments used during port binding

> On 01 Mar 2016, at 06:22, Kevin Benton wrote: > > >This seems gross and backwards. It makes sense as a short term hack but > >given that we have time to design this correctly I'd prefer to get this > >information in a more straighforward way. > > Well it depends on what is happening here. I

[openstack-dev] [tricircle]weekly meeting of Mar. 2

Hi, If you have any topic to discuss, please reply in the M-L. IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 13:00. Agenda: # Progress of To-do list review: https://etherpad.openstack.org/p/TricircleToDo # Reliable async. job # L2 net

Re: [openstack-dev] [all] A proposal to separate the design summit

> > Current thinking would be to give preferential rates to access the main > > summit to people who are present to other events (like this new > > separated contributors-oriented event, or Ops midcycle(s)). That would > > allow for a wider definition of "active community member" a

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On Mon, Feb 29, 2016 at 12:36:03PM -0700, Rich Megginson wrote: > On 02/29/2016 12:19 PM, Chris Friesen wrote: > >On 02/29/2016 12:22 PM, Daniel P. Berrange wrote: > > > >>There's three core scenarios for hooks > >> > >> 1. Modifying some aspect of the Nova operation > >> 2. Triggering an externa

Re: [openstack-dev] [all] A proposal to separate the design summit

Le 01/03/2016 11:08, Eoghan Glynn a écrit : Current thinking would be to give preferential rates to access the main summit to people who are present to other events (like this new separated contributors-oriented event, or Ops midcycle(s)). That would allow for a wider definition of "active comm

[openstack-dev] Openstack Cinder - Wishlist

Hi, Would like to know if there's feature wish list/enhancement request for Open stack Cinder I.e. a list of features that we would like to add to Cinder Block Storage ; but hasn't been taken up for development yet. We have couple developers who are interested to work on OpenStack Cinder...

Re: [openstack-dev] Openstack Cinder - Wishlist

Hi Ashraf, you can find all such information over launchpad. https://bugs.launchpad.net/cinder Regards, Yatin On Tue, Mar 1, 2016 at 4:01 PM, wrote: > Hi, > > > > Would like to know if there’s feature wish list/enhancement request for > Open stack Cinder I.e. a list of features that we woul

Re: [openstack-dev] [Fuel][Fuel-Library] Fuel CI issues

Dmitry >I don't think "hurried" is applicable here: the only way to become more >ready to track upstream than we already are is to *start* tracking >upstream. Postponing that leaves us in a Catch-22 situation where we >can't stay in sync with upstream because we're not continuously catching >up wi

Re: [openstack-dev] [nova] A prototype implementation towards the "shared state scheduler"

On 1 March 2016 at 08:34, Cheng, Yingxin wrote: > Hi, > > I have simulated the distributed resource management with the incremental > update model based on Jay's benchmarking framework: > https://github.com/cyx1231st/placement-bench/tree/shared-state-demonstration. > The complete result lies at

[openstack-dev] [Fuel] [Ci] New 'fuel-web' gate job

Hi to all, please be informed that starting from today we're launching gate job [1] for 'fuel-web' package [2] Mentioned job will be triggered on each commit and will perform steps: - build a package from the commit - run system tests scenario [3] with using created package - vote in a patchset a

[openstack-dev] [Fuel][FFE] provisioning and deployment data pipeline

Hi I want to request a feature freeze exception for "provisioning and deployment data pipeline" There is one patch with implementation [1] which is ready and already has had two '+2's and '+1' workflow yesterday but there still failing gate jobs because of some random test failures. Merging it i

[openstack-dev] How to re-route flows to my L2 device

Hi All, I have a L2 filter VM. I want VM flows and outside traffic to go via this L2 filter VM. I have 2 interfaces in L2 filter VM. But in openstack when I launch my L2 filter VM with 2 interfaces it is taking 2 different private IP's. How do I add flows in br-int to route packets via my L2 fil

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On 1 March 2016 at 10:10, Daniel P. Berrange wrote: > On Mon, Feb 29, 2016 at 12:36:03PM -0700, Rich Megginson wrote: >> On 02/29/2016 12:19 PM, Chris Friesen wrote: >> >On 02/29/2016 12:22 PM, Daniel P. Berrange wrote: >> > >> >>There's three core scenarios for hooks >> >> >> >> 1. Modifying som

Re: [openstack-dev] [TripleO] core members for tripleo-ui

On Mon, Feb 29, 2016 at 10:27:38AM -0500, Dan Prince wrote: > There is a new projects for the ui called tripleo-ui. As most of the > existing TripleO core members aren't going to be reviewing UI specific > patches is seems reasonable that we might add a few review candidates > who can focus specifi

Re: [openstack-dev] [Zaqar] Nominating Eva Balycheva for Zaqar core

On Mon, Feb 29, 2016 at 8:47 PM, Fei Long Wang wrote: > Hi all, > > I would like to propose adding Eva Balycheva(Eva-i) for the Zaqar core > team. Eva has been an awesome contributor since joining the Zaqar team. > She is currently the most active non-core reviewer on Zaqar projects for > the last

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On 29 February 2016 at 18:49, Andrew Laski wrote: > On Mon, Feb 29, 2016, at 01:18 PM, Dan Smith wrote: >> > Forgive my ignorance or for playing devil's advocate, but wouldn't the >> > main difference between notifications and hooks be that notifications >> > are asynchronous and hooks aren't? >>

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On 02/29/2016 05:23 PM, Matt Riedemann wrote: > > > On 2/29/2016 2:54 PM, Sean Dague wrote: >> On 02/29/2016 11:59 AM, Sean Dague wrote: >>> The nova/hooks.py infrastructure has been with us since early Nova. It's >>> currently only annotated on a few locations - 'build_instance', >>> 'create_ins

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

- Original Message - > From: "Guz Egor" > To: "OpenStack Development Mailing List (not for usage questions)" > > > Adrian, > I disagree, host OS is very important for operators because of integration > with all internal tools/repos/etc. > I think it make sense to limit OS support in Mag

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

- Original Message - > From: "Steve Gordon" > To: "Guz Egor" , "OpenStack Development Mailing List (not > for usage questions)" > > > - Original Message - > > From: "Guz Egor" > > To: "OpenStack Development Mailing List (not for usage questions)" > > > > > > Adrian, > > I dis

Re: [openstack-dev] Openstack Cinder - Wishlist

On 03/01/2016 11:31 AM, mohammed.asha...@wipro.com wrote: > > Hi, > > > > Would like to know if there’s feature wish list/enhancement request > for Open stack Cinder I.e. a list of features that we would like to > add to Cinder Block Storage ; but hasn’t been taken up for development > yet. > >

Re: [openstack-dev] Openstack Cinder - Wishlist

I like the idea of a Cinder Wishlist or perhaps titled: Cinder Future Design and Architecture list. I think the Cinder community could benefit if we continued to refine the work we did on this Wishlist at the Mitaka midcycle and spent a few minutes each cycle going over the list, prioritizing, a

[openstack-dev] [Fuel] FFE request for ConfigDB service

Greetings, As you might know, we are working on centralised storage for deployment configuration data in Fuel. Such store will allow external 3rd-party services to consume the entirety of settings provided by Fuel to deployment mechanisms on target nodes. It will also allow to manage and override

Re: [openstack-dev] [nova][cinder] volumes stuck detaching attaching and force detach

Matt, changing Nova to store the connector info at volume attach time does help. Where the gap will remain is after Nova evacuation or live migration, when that info will need to be updated in Cinder. We need to change the Cinder API to have some mechanism to allow this. We'd also like Cinder to

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

We found some issue about atomic host run some docker volume plugin, while atomic and docker volume plugin both not sure what's the root cause of that. here is the link https://github.com/docker/docker/issues/18005#issuecomment-190215862 Also I did not find atomic image update quickly, ( but k8s

Re: [openstack-dev] [Nova] notification subteam meeting

Hi, The next short meeting of the nova notification subteam will happen 2016-03-01 Tuesday _17:00_ UTC [1] on #openstack-meeting-alt on freenode Agenda: - Status of the outstanding specs and code reviews - AOB See you there. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.h

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

I tend to agree that multiple os support is OK (we can limited to popular ones first, like redhat os, ubuntu os) But we not tend to cover all OS, it would much burden for maintain, and extra small requirements should be maintain by 3-rd party if possible(through drivers). Thanks Best Wishes

Re: [openstack-dev] [Fuel][FFE] provisioning and deployment data pipeline

I'm glad to inform you that FFE is no longer needed here. The pipeline implementation was finally merged. I also stated working on fixing random failing test [0]. Regards [0] https://review.openstack.org/#/c/286583/ On Tue, Mar 1, 2016 at 12:38 PM, Sylwester Brzeczkowski < sbrzeczkow...@mirantis

[openstack-dev] [Fuel] [Plugins] Fuel Plugin Builder 4.0.0 released

Hey Fuelers, I want to announce that FPB (fuel plugin builder) v4.0.0 has been released on PyPI [1]. New package version "4.0.0" includes but not limited to: * New flag `is_hotpluggable` in `metadata.yaml` that allows to install and use plugin on previously deployed environments. * Plugin can sp

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

- Original Message - > From: "Kai Qiang Wu" > To: "OpenStack Development Mailing List (not for usage questions)" > > Cc: "Josh Berkus" > > We found some issue about atomic host run some docker volume plugin, while > atomic and docker volume plugin both not sure what's the root cause of

[openstack-dev] [Solar] Weekly update

Hello, Fuel2Solar (f2s) is a experimental project which allows to use Solar with Fuel. Using fuel-library tasks it generates Solar resource definitions, using deployment info and deployment graph from nailgun it creates and connects solar resources. Using this data Solar is able to deploy OpenStac

Re: [openstack-dev] [Zaqar] Nominating Eva Balycheva for Zaqar core

On 02/29/2016 07:47 PM, Fei Long Wang wrote: Hi all, I would like to propose adding Eva Balycheva(Eva-i) for the Zaqar core team. Eva has been an awesome contributor since joining the Zaqar team. She is currently the most active non-core reviewer on Zaqar projects for the last 90 days[1]. During

[openstack-dev] [Fuel] [FFE] Use packetary for building ISO

Dear colleagues, I'd like to request a feature freeze exception for "Use packetary for building ISO". BP [0] There is PR in packetary itself [1]. And one pull request in fuel-main [2]. For ISO build process this feature means we will use the same command 'make iso' but another set of environment

Re: [openstack-dev] [devstack] stack.sh keeps failing with RTNETLINK answers: Network is unreachable

Failing with different error now see attached On 29/02/16 18:42, Brian Haley wrote: On 02/26/2016 03:48 AM, Paul Carlton wrote: Sean Don't think unstack failed, when I manually create the device ( sudo ovs-vsctl --no-wait -- --may-exist add-br br-ex) unstack.sh removes it. sudo ip route sh

[openstack-dev] [Fuel][FFE] Use RGW as a default object store instead of Swift

Colleagues, I would like to request a feature freeze exception for 'Use RGW as a default object store instead of Swift' [1]. To merge the changes we need at most one week of time. ​[1]: https://review.openstack.org/#/c/286100/ Thanks --

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

This issue involves what I refer to as "OS religion" operators have this WRT bay nodes, but users don't. I suppose this is a key reason why OpenStack does not have any concept of supported OS images today. Where I can see the value in offering various choices in Magnum, maintaining a reference i

Re: [openstack-dev] [all] A proposal to separate the design summit

On 03/01/2016 05:08 AM, Eoghan Glynn wrote: > >>> Current thinking would be to give preferential rates to access the main >>> summit to people who are present to other events (like this new >>> separated contributors-oriented event, or Ops midcycle(s)). That would >>> allow for a w

[openstack-dev] [api] [all] Changing Microversion Headers

tl;dr: The API-WG would like to change the format of the headers used for Microversions to make them more future proof, now, before too many projects are using them. See this review for more details if you are interested and/or want to express an opinion or question. https://review.openstack

Re: [openstack-dev] [puppet] weekly meeting #72

/etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160301 > > We'll also have open discussion for bugs & reviews, so anyone is welcome > to join. > > See you there, Very quick meeting this week, here are the notes: http://eavesdrop.openstack.org/meetings/pupp

[openstack-dev] [Fuel] [FFE] Add multipath disks support

Hi All, I’d like to request a Feature Freeze Exception for "Add multipath disks support” until Mar 9. This feature allows to use FC multipath disks in Fuel nodes – BP [1], spec [2]. Development is already done and we need following patches still to be merged: review and merge multipath support i

Re: [openstack-dev] OpenStack Contributor Awards

Excellent, excellent. What's the best place to buy Raspberry Pis these days? On 22/02/16 21:09, Victoria Martínez de la Cruz wrote: Oh I missed this thread... really great initiative! It's time to recognize the effort of our fellow stackers :D Raspi/Arduino kits or limited edition t-shirts are

Re: [openstack-dev] [Openstack-operators] OpenStack Contributor Awards

+1 for custom T-shirts or hoodies. Actual medals/trophies would also be a nice idea ;) On 1 March 2016 at 15:30, Tom Fifield wrote: > Excellent, excellent. > > What's the best place to buy Raspberry Pis these days? > > On 22/02/16 21:09, Victoria Martínez de la Cruz wrote: > >> Oh I missed this

Re: [openstack-dev] [Openstack-operators] OpenStack Contributor Awards

> On Mar 1, 2016, at 10:40 AM, Matt Jarvis > wrote: > > +1 for custom T-shirts or hoodies. Actual medals/trophies would also be a > nice idea ;) +1 > >> On 1 March 2016 at 15:30, Tom Fifield wrote: >> Excellent, excellent. >> >> What's the best place to buy Raspberry Pis these days? >> >>

[openstack-dev] [Fuel] [FFE] LCM readiness for all deployment tasks

Hi All, I’d like to request a Feature Freeze Exception for "LCM readiness for all deployment tasks” [1] until Mar 11. We need additional 1.5 week to finish and merge necessary changes which will fix tasks in Fuel to be idempotent. That will be foundation and will enable further development of

Re: [openstack-dev] OpenStack Contributor Awards

On Tue, Mar 1, 2016 at 8:30 AM, Tom Fifield wrote: > Excellent, excellent. > > What's the best place to buy Raspberry Pis these days? > Raspberry Pi 3 is available to buy today from our partners element14 and RS Components

Re: [openstack-dev] [Fuel][FFE] Use RGW as a default object store instead of Swift

Hey Konstantin, I see that provided patch [1] is for stable/8.0. Fuel 8.0 is recently released and we usually do not accept any features to stable branch. Or your meant that patch for master branch? Thanks, Igor [1]: https://review.openstack.org/#/c/286100/ On Tue, Mar 1, 2016 at 4:44 PM, Kons

[openstack-dev] [Fuel][FFE] API handler for serialized graph

Hello folks, I am not sure that i will need FFE, but in case i wont be able to land this patch [0] tomorrow - i would like to ask for one in advance. I will need FFE for 2-3 days, depends mainly on fuel-web cores availability. Merging this patch has zero user impact, and i am also using it alread

[openstack-dev] [Ceilosca][Neutron][Monasca]

Hi all, I'm planning to write a plugin for Monasca that would enable router's traffic monitoring per subnet per tenant. For that purpose, I'm using Neutron l3 metering extension [1] that allows you to filter traffic based on CIDRs. My concerns: - Now given the fact that this extension can be use

[openstack-dev] [Fuel] [FFE] FF exception request for SR-IOV

Hi, I'd like to to request a feature freeze exception for "Support for SR-IOV for improved networking performance" feature [0]. Part of this feature is already merged [1]. We have the following patches in work / on review: https://review.openstack.org/280782 https://review.openstack.org/284603 h

[openstack-dev] [Fuel] [FFE] FF exception request for DPDK

Hi, I'd like to to request a feature freeze exception for "Support for DPDK for improved networking performance" feature [0]. Part of this feature is already merged [1]. We have the following patches in work / on review: https://review.openstack.org/281827 https://review.openstack.org/283044 htt

[openstack-dev] [Performance] Let's have next meeting on March 15th

Folks, due to the schedule our next meeting is going to happen on March 8th, that's International Women's Day (non-working day in Russia, for instance). So let's have our next meeting scheduled for March 15th. Cheers, Dina ___

[openstack-dev] [kolla][security] Obtaining the vulnerability:managed tag

Core reviewers, Please review this document: https://github.com/openstack/governance/blob/master/reference/tags/vulnerability_managed.rst It describes how vulnerability management is handled at a high level for Kolla. When we are ready, I want the kolla delivery repos vulnerabilities to be man

[openstack-dev] [ceilometer] Unable to get ceilometer events for instances running for demo project

I have a single node configuration for devstack liberty working and I want to record all the ceilometer events like compute.instance.start, compute.instance.end, compute.instance.update etc occurred recently. I am unable to get any event occurred for instances running for demo project i.e when I tr

Re: [openstack-dev] [oslo] upgrade implications of lots of content in paste.ini

The keystone patch has landed. I've gone ahead and filed the appropriate launchpad bug to address this issue: https://bugs.launchpad.net/oslo.config/+bug/1551836 Note: Using latent configuration imposes a forward-going maintenance burden on all projects impacted, if released in mitaka. As such I

Re: [openstack-dev] [kolla][security] Obtaining the vulnerability:managed tag

Hello, I have experience writing selinux policy. My plan was to write the selinux policy for Kolla in the next cycle. I'd be interested in joining if that fits the criteria here. Thanks, -Ryan - Original Message - From: "Steven Dake (stdake)" To: "OpenStack Development Mailing List (

[openstack-dev] [kolla] Reminder our next meeting is 23:00 UTC

Reminder our next meeting is Wednesday at 23:00 UTC to accommodate APAC/US folks. This is a change from the past, where we only had meeting at 16:30 UTC. For more details see: https://wiki.openstack.org/wiki/Meetings/Kolla Regards, -steve _

[openstack-dev] [release][stable][horizon] django_openstack_auth 1.2.2 release (kilo)

We are glad to announce the release of: django_openstack_auth 1.2.2: Django authentication backend for use with OpenStack Identity This release is part of the kilo stable release series. With source available at: http://git.openstack.org/cgit/openstack/django_openstack_auth/ Please report

Re: [openstack-dev] [kolla][security] Obtaining the vulnerability:managed tag

On 03/01/2016 05:12 PM, Ryan Hallisey wrote: > Hello, > > I have experience writing selinux policy. My plan was to write the selinux > policy for Kolla in the next cycle. I'd be interested in joining if that > fits the criteria here. > Hello Ryan, While knowing howto write SELinux policy is

Re: [openstack-dev] [nova] Should we cleanup migration from virt drivers?

On 3/1/2016 1:47 AM, Eli Qiao wrote: hello Nova hackers I see in some of virt drivers (see belows links) 's confirm_resize/revert_resize(or something like that) passing a parameter 'migration', but it is not used at all in virt layer drivers, I wonder why we still keep them (to reserved for fu

Re: [openstack-dev] [nova] Should we cleanup migration from virt drivers?

On 3/1/2016 11:52 AM, Matt Riedemann wrote: On 3/1/2016 1:47 AM, Eli Qiao wrote: hello Nova hackers I see in some of virt drivers (see belows links) 's confirm_resize/revert_resize(or something like that) passing a parameter 'migration', but it is not used at all in virt layer drivers, I wo

Re: [openstack-dev] [all] audience for release notes

There is a fixture in pbr's test suite to create keys with out entropy use, should be easy to adapt for user by Reno's tests. On 1 Mar 2016 6:52 AM, "Thomas Goirand" wrote: > On 02/29/2016 10:31 PM, Doug Hellmann wrote: > >>> Give this a try and see if it works any better: > >>> https://review.op

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

Sorry for the top posting, but seems like doing so is ok, So an idea, feel free to use it or not... But if a in-memory notification mechanism is desired then a library that I have been using and extracted from taskflow could be helpful here, It doesn't bring in the full oslo.messaging notific

[openstack-dev] [Neutron] Hitting Mitaka Milestone 3 and feature freeze exception process

Hi Neutrinos, As I am sure all of you know, this week is Milestone week [1], for this reason, we need to cut releases for both neutron, neutron *-aas, and the client. Patches [2, 3] are still in draft, and whilst stuff is in flight, we'll hold on until we have reached a sensible point where it's s

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

Daniel P. Berrange wrote: > On Mon, Feb 29, 2016 at 12:36:03PM -0700, Rich Megginson wrote: >> On 02/29/2016 12:19 PM, Chris Friesen wrote: >>> On 02/29/2016 12:22 PM, Daniel P. Berrange wrote: >>> There's three core scenarios for hooks 1. Modifying some aspect of the Nova operation

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

Daniel P. Berrange wrote: > On Mon, Feb 29, 2016 at 11:59:06AM -0500, Sean Dague wrote: >> The nova/hooks.py infrastructure has been with us since early Nova. It's >> currently only annotated on a few locations - 'build_instance', >> 'create_instance', 'delete_instance', and 'instance_network_info'

Re: [openstack-dev] [kolla][security] Obtaining the vulnerability:managed tag

On 3/1/16, 10:47 AM, "Tristan Cacqueray" wrote: >On 03/01/2016 05:12 PM, Ryan Hallisey wrote: >> Hello, >> >> I have experience writing selinux policy. My plan was to write the >>selinux policy for Kolla in the next cycle. I'd be interested in >>joining if that fits the criteria here. >> > >

[openstack-dev] [Fuel] [FFE] Unlock Settings Tab

Fuelers, I would like to request a feature freeze exception for "Unlock settings tab" feature [0] This feature being combined with Task-based deployment [1] and LCM-readiness for Fuel deployment tasks [2] unlocks Basic LCM in Fuel. We conducted a thorough redesign of this feature and splitted it

[openstack-dev] [Fuel][FFE] FF exception request for HugePages

Hi, I'd like to to request a feature freeze exception for "Support for Huge pages for improved performance" feature [0]. Part of this feature is already merged [1]. We have the following patches in work / on review: https://review.openstack.org/#/c/286628/ https://review.openstack.org/#/c/282367

[openstack-dev] [Fuel][FFE] FF exception request for Numa and CPU pinning

Hi, I'd like to to request a feature freeze exception for "Add support for NUMA/CPU pinning features" feature [0]. Part of this feature is already merged [1]. We have the following patches in work / on review: https://review.openstack.org/#/c/281802/ https://review.openstack.org/#/c/285282/ http

Re: [openstack-dev] [all] audience for release notes

Excerpts from Robert Collins's message of 2016-03-02 07:14:19 +1300: > There is a fixture in pbr's test suite to create keys with out entropy use, > should be easy to adapt for user by Reno's tests. That's likely where I got the original version of the one in reno now. Doug > On 1 Mar 2016 6:52

Re: [openstack-dev] [Openstack-operators] OpenStack Contributor Awards

On 03/01/2016 11:30 PM, Tom Fifield wrote: > Excellent, excellent. > > What's the best place to buy Raspberry Pis these days? One of the 2 official sites: https://www.element14.com/community/community/raspberry-pi The Pi 3 is the super nice shiny new stuff, with 64 arm bits. Cheers, Thomas Goi

[openstack-dev] [puppet] 8.0.0b1 is out (Mitaka beta)

Our group is proud to announce we have a first beta release of Puppet modules for Mitaka. Those modules have now a 8.0.0b1 tag that packagers can use: puppet-aodh puppet-ceilometer puppet-cinder puppet-designate puppet-glance puppet-gnocchi puppet-heat puppet-horizon puppet-ironic puppet-keystone

[openstack-dev] [Fuel][FFE] Multi-release packages

Fuelers, I would like to request a feature freeze exception for "Multi-release packages" feature [0][1] This feature extends already existing multi-release support in Fuel Plugins. We would like to allow plugin developers to specify all plugin components per release and distribute different deplo

Re: [openstack-dev] [Openstack-operators] OpenStack Contributor Awards

Just to check, does OpenStack run on a Raspberry Pi ? Could cause some negative comments if it was not compatible/sized for a basic configuration. Tim On 01/03/16 20:41, "Thomas Goirand" wrote: >On 03/01/2016 11:30 PM, Tom Fifield wrote: >> Excellent, excellent. >> >> What's the best pla

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On 03/01/2016 02:04 PM, Rob Crittenden wrote: > Daniel P. Berrange wrote: >> On Mon, Feb 29, 2016 at 11:59:06AM -0500, Sean Dague wrote: >>> The nova/hooks.py infrastructure has been with us since early Nova. It's >>> currently only annotated on a few locations - 'build_instance', >>> 'create_insta

Re: [openstack-dev] [Openstack-operators] OpenStack Contributor Awards

Or they use it to do a cool demo of running apps on an OpenStack cloud. On Tue, Mar 1, 2016 at 2:04 PM, Tim Bell wrote: > > Just to check, does OpenStack run on a Raspberry Pi ? Could cause some > negative comments if it was > not compatible/sized for a basic configuration. > > Tim > > > > > > O

[openstack-dev] [neutron][taas]

Hi All, Its time to induct new members to the TaaS core reviewers, to kick start the process i nominate the following developers and active contributors to the TaaS project 1. Yamamoto Takashi 2. Soichi Shigeta Cheers, Vinay Yadhav ___

Re: [openstack-dev] OpenStack Contributor Awards

On Tue, Feb 16, 2016 at 5:43 AM, Tom Fifield wrote: > Hi all, > > I'd like to introduce a new round of community awards handed out by the > Foundation, to be presented at the feedback session of the summit. > > > > in the meantime, let's use this thread to discuss the fun part: goodies. > What

Re: [openstack-dev] [Fuel][Fuel-Library] Fuel CI issues

I think we should also look at the root cause of these CI failures. They are connected with difference in packages and not with manifests or deployment process. So another possible solution is to stay as close as possible to the package sources used by OpenStack Puppet modules CI. For example, we h

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

From: Adrian Otto [mailto:adrian.o...@rackspace.com] Sent: March-01-16 9:54 AM To: Guz Egor Cc: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro This issue involves what I refer to as "OS religi

Re: [openstack-dev] [kolla][security] Obtaining the vulnerability:managed tag

Hi Steven, I'd like to help you with vulnerability management process of Kolla and become a member of Kolla VMT team. I have experience and expertise in IT security and related to it processes. Best regards, Adam On Tue, Mar 1, 2016 at 5:55 PM, Steven Dake (stdake) wrote: > Core reviewers, > >

Re: [openstack-dev] [kolla][security] Obtaining the vulnerability:managed tag

Adam, Thank you for your offer, but I believe the VMT kolla-coresec team must be formed from core reviewers or I'd ask Dave Mccowan to consider an invitation. The text that I think this comes from is: Deliverables with more than five core reviewers should (so as to limit the unnecessary exposur

[openstack-dev] [Fuel][FFE] FF exception request for non-root accounts on slave nodes

Hello, I'd like to request a FF exception for "Run Fuel slave nodes as non-root" feature[1]. Current status: larger part of the feature is already merged[2] and some more patches[3][4][5][6] are expected to land before the FF. When these patches are in the master, Fuel 9.0 will be able to create

Re: [openstack-dev] [all] A proposal to separate the design summit

On 03/01/2016 09:03 AM, Anita Kuno wrote: On 03/01/2016 05:08 AM, Eoghan Glynn wrote: In Vancouver I happened to be sitting behind someone who stated "I'm just here for the buzz." Which is lovely for that person. The problem is that the buzz that person is there for is partially created by me

Re: [openstack-dev] [all] A proposal to separate the design summit

Excerpts from Eoghan Glynn's message of 2016-03-01 02:08:00 -0800: > > > > Current thinking would be to give preferential rates to access the > > > main > > > summit to people who are present to other events (like this new > > > separated contributors-oriented event, or Ops midcyc

Re: [openstack-dev] [all] A proposal to separate the design summit

On 03/01/2016 04:30 PM, Chris Friesen wrote: > On 03/01/2016 09:03 AM, Anita Kuno wrote: >> On 03/01/2016 05:08 AM, Eoghan Glynn wrote: > >> In Vancouver I happened to be sitting behind someone who stated "I'm >> just here for the buzz." Which is lovely for that person. The >> problem

Re: [openstack-dev] [all] A proposal to separate the design summit

On 03/01/2016 03:52 PM, Clint Byrum wrote: Excerpts from Eoghan Glynn's message of 2016-03-01 02:08:00 -0800: There are a whole slew of folks who work fulltime on OpenStack but contribute mainly in the background: operating clouds, managing engineering teams, supporting customers, designing pr

[openstack-dev] [Fuel][FFE] Decouple Fuel and OpenStack tasks

I'd like to request a feature freeze exception for Decouple Fuel and OpenStack tasks feature [0]. While the code change [1] is ready and usually passing CI we have too much churn in the tasks currently which puts the patch set in conflict constantly so it has to be rebased multiple times a day. W

Re: [openstack-dev] [Openstack-operators] OpenStack Contributor Awards

I believe Eric Windisch did at one point run OpenStack on a pi. The problem is that it's got so little ram, and no hypervisor. Also at least it USED to not be able to run docker since docker wasn't crosscompiled to arm at the time. It's a terrible target for openstack. NUCs on the other hand...

[openstack-dev] {openstack-dev][tc] Leadership training proposal/info

Hello Stackers, This is the continuation of an ongoing conversation within the TC about encouraging the growth of leadership skills within the community that began just after the Mitaka summit last year[1]. After being asked by lifeless to do a bit of research and discussing needs/wants re: leader

Re: [openstack-dev] [nova][cinder] volumes stuck detaching attaching and force detach

> -Original Message- > From: D'Angelo, Scott > > Matt, changing Nova to store the connector info at volume attach time does > help. Where the gap will remain is after Nova evacuation or live migration, This will happen with shelve as well I think. Volumes are not detached in shelve IIRC.

[openstack-dev] [neutron] - Changing the Neutron default security group rules

Hi, I know this has come up in the past, but some folks in the infra channel brought up the topic of changing the default security groups to allow all traffic. They had a few reasons for this that I will try to summarize here: * Ports 'just work' out of the box so there is no troubleshooting to e

[openstack-dev] [Fuel][FFE] Remove conflicting openstack module parts

I'd like to request a feature freeze exception for the Remove conflicting openstack module parts feature [0] This is necessary to make the feature Decouple Fuel and OpenStack tasks feature useful [1] , some of the patches are ready for review and some still need to be written [2] We need 2 - 3 we

[openstack-dev] [Fuel] FFE Tracking

As FF quickly approaches (March 2) we have started posting feature freeze exception requests. If you would like to request an exception for your feature, please request one in accordance with the guidelines [0], and include your estimate for completion and risk at that time of completion. Also ple

  1   2   >