Re: [openstack-dev] [oslo]Introduction of new driver for oslo.messaging

Jut find the spec in https://review.openstack.org/#/c/452219/, I also added oslo.messaging API maintainers as reivewers 2017-04-01 1:48 GMT+08:00 Davanum Srinivas : > Let's do this! +1 :) > > On Fri, Mar 31, 2017 at 10:40 AM, Deja, Dawid > wrote: > > Hi all, > > > > To work around issues with r

[openstack-dev] [Gluon] IRC Meeting cancelled on April 5, 2017 and Re-convene on April 12, 2017

Hello folks, Many of our folks will be in ONS in Santa Clara next week. So we will cancel the IRC meeting next week April 5 so that everyone can focus and enjoy the sessions in ONS. We will re-convene on April 12. Thanks Bin [1] https://wiki.openstack.org/wiki/Gluon [2] https://wiki.

[openstack-dev] [all][infra] logs.o.o corrupt - indicated by POST_FAILURE results

Since this morning, part of logs.openstack.org is corrupt due to a downtime of one of the backing stores. The infra admins are currently running fsck and then will take everything back in use. Right now, we put the logs on a spare disks so that everything that is run, is getting log results. You

Re: [openstack-dev] [oslo]Introduction of new driver for oslo.messaging

Let's do this! +1 :) On Fri, Mar 31, 2017 at 10:40 AM, Deja, Dawid wrote: > Hi all, > > To work around issues with rabbitMQ scalability we'd like to introduce > new driver in oslo messaging that have nearly no scaling limits[1]. > We'd like to have as much eyes on this as possible since we believ

Re: [openstack-dev] [all][infra] No more 'reverify', use 'recheck'

On 03/31/2017 01:29 PM, Andreas Jaeger wrote: > In July 2014 [1] we aliased 'reverify' to 'recheck' and those two do > exactly the same since then. It's time IMHO to remove reverify [2] since > it only confuses people that issue reverify expecting it to do something > different. Note that our docum

[openstack-dev] [all][infra] No more 'reverify', use 'recheck'

In July 2014 [1] we aliased 'reverify' to 'recheck' and those two do exactly the same since then. It's time IMHO to remove reverify [2] since it only confuses people that issue reverify expecting it to do something different. Note that our documentation does not mention 'reverify' at all. So, for

Re: [openstack-dev] [oslo]Introduction of new driver for oslo.messaging

I thought this spec/proposal was embargoed until tomorrow?! - Jay Faulkner OSIC > On Mar 31, 2017, at 7:40 AM, Deja, Dawid wrote: > > Hi all, > > To work around issues with rabbitMQ scalability we'd like to introduce > new driver in oslo messaging that have nearly no scaling limits[1]. > We'd

Re: [openstack-dev] [murano] [heat] [cinder] MuranoPL types question

Thanks for the tips Stan. > it is stored exactly as it comes from Heat. In theory conversion to > string could happen on Heat side, but most likely it just the output > of reporter made it look like this Did some digging and it actually seems to be a string on heat's end. python-cinderclient

Re: [openstack-dev] [barbican][castellan] How to share secrets in barbican

Another option: If you want to give User-A read access to all Project-B secrets, you could assign User-A the role of "observer" in Project-B. This would use the default RBAC policy, not give every user access to the secrets, and be more convenient than adding each user to the ACL of each secret.

Re: [openstack-dev] [oslo]Introduction of new driver for oslo.messaging

On 03/31/2017 10:40 AM, Deja, Dawid wrote: Hi all, To work around issues with rabbitMQ scalability we'd like to introduce new driver in oslo messaging that have nearly no scaling limits[1]. We'd like to have as much eyes on this as possible since we believe that this is the technology of the fut

[openstack-dev] [oslo]Introduction of new driver for oslo.messaging

Hi all, To work around issues with rabbitMQ scalability we'd like to introduce new driver in oslo messaging that have nearly no scaling limits[1]. We'd like to have as much eyes on this as possible since we believe that this is the technology of the future. Thanks for all reviews. Dawid Deja [1]

Re: [openstack-dev] Project Navigator Updates - Feedback Request

I think this is a bit of a roadblock for us getting the new Navigator up, so the sooner we can come to a decision the better :) Thanks for raising the issue with the TC! Thierry Carrez March 31, 2017 at 3:43 AM I like the idea to provide unified API information,

[openstack-dev] Boston Forum Submission Deadline!

Hey everyone, Please take time to *submit your proposals *from the etherpad(s) or any other place you have captured/brainstormed. This is a friendly reminder that all proposed Forum session leaders must submit their abstracts at: http://forumtopics.openstack.org/ *before 11:59PM UTC on Sunday A

Re: [openstack-dev] Project Navigator Updates - Feedback Request

On 3/31/17, 4:43 AM, "Thierry Carrez" wrote: >Brian Rosmaita wrote: >> On 3/29/17 12:55 AM, Jimmy McArthur wrote: >> [snip] >>> What we really need is the following: >>> >>> * A project history, including the date of project inception that's >>> included in the TC tags. >>> * An API history in

Re: [openstack-dev] rebuild_instance (nova evacuate) failed to add trunk port

Hi, On Thu, Mar 30, 2017 at 10:14 PM, KHAN, RAO ADNAN wrote: > In Juno, there is an issue with instance rebuild (nova evacuate) when trunk > port is associated with that instance. I have a feeling you're not using the publicly available trunk port version as available in Neutron since the Newton

Re: [openstack-dev] [tripleo] os-cloud-config retirement

On 30.3.2017 17:39, Juan Antonio Osorio wrote: Why not drive the post-config with something like shade over ansible? Similar to what the kolla-ansible community is doing. We could use those perhaps, if they bring enough benefit to add them to the container image(s) (i think we'd still want to

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

Here's an update on resource providers and placement. I've been away from OpenStack for most of this week, so apologies if I have missed something important. Please follow up with anything I've missed (or questions or comments or anything else). # What Matters Most Traits are still top of the p

Re: [openstack-dev] [kolla] my work on Debian and non-x86 architectures

W dniu 17.02.2017 o 22:33, Marcin Juszkiewicz pisze: > Current stats: Instead of writing how many images got built I decided to make a page with results: http://people.linaro.org/~marcin.juszkiewicz/kolla/ There you can find which images got built for any combination of those: distros = cento

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

2017-03-31 2:55 GMT+08:00 Doug Hellmann : > Excerpts from Paul Belanger's message of 2017-03-22 09:58:46 -0400: > > On Tue, Mar 21, 2017 at 05:53:35PM -0600, Alex Schultz wrote: > > > On Tue, Mar 21, 2017 at 5:35 PM, John Dickinson wrote: > > > > > > > > > > > > On 21 Mar 2017, at 15:34, Alex Sch

Re: [openstack-dev] [freezer] Demo of new OpenSatck Freezer features

Excellent! Thanks for sharing this demo. Thanks, Trinath Somanchi | HSDC, GSD, DN | NXP – INDA. From: Julia Odruzova [mailto:jvarlam...@mirantis.com] Sent: Friday, March 31, 2017 4:16 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [freezer] Demo of new OpenSatck Freezer feat

Re: [openstack-dev] [freezer] Demo of new OpenSatck Freezer features

Great! Thanks Julia! On Fri, Mar 31, 2017 at 10:46 AM, Julia Odruzova wrote: > Hi Freezer team! > > > I prepared a short demo of recently implemented Freezer features. > > This is a brief overview of features our Mirantis team took part in – > rsync engine, backup to local/remote host and Nova

Re: [openstack-dev] [freezer] Demo of new OpenSatck Freezer features

That's really cool ! ! Thank you Julia ! From: Julia Odruzova Sent: Friday, March 31, 2017 11:46:20 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [freezer] Demo of new OpenSatck Freezer features Hi Freezer team! I prepared a short

[openstack-dev] [freezer] Demo of new OpenSatck Freezer features

Hi Freezer team! I prepared a short demo of recently implemented Freezer features. This is a brief overview of features our Mirantis team took part in – rsync engine, backup to local/remote host and Nova tenant backup. https://www.youtube.com/watch

Re: [openstack-dev] [neutron][ml2] - heads up for mechanism drivers that don't use in tree DHCP agent

Thanks for the heads up, Kevin! Is this still necessary if a deployment disables the Neutron server's DHCP scheduling, with self._supported_extension_aliases.remove("dhcp_agent_scheduler") ? Thanks, Neil On Fri, Mar 31, 2017 at 12:52 AM Kevin Benton wrote: > Hi, > > Once [

Re: [openstack-dev] [all][elections] Candidate proposals for TC (Technical Committee) positions are now open

On 03/31/2017 08:58 AM, Thierry Carrez wrote: > Jens Rosenboom wrote: >> 2017-03-31 2:00 GMT+02:00 Kendall Nelson : >>> Candidate proposals for the Technical Committee positions (7 positions) are >>> now open and will remain open until 2017-04-20, 23:45 UTC >> >> The table below states a much earli

Re: [openstack-dev] How to find "ovs_mechanism + vxlan tanent_type_driver + L2_pop" configure steps?

2017-03-31 3:10 GMT+00:00 Sam : > Hi all, > > In openstack-ocata install docs, I only found "linux_bridge + vxlan + l2pop" > configure steps, Is there "ovs+vxlan+l2pop" configure steps? The install-guide only covers the most basic setup, for ovs you will need to look at the corresponding section i

Re: [openstack-dev] [all][elections] Candidate proposals for TC (Technical Committee) positions are now open

Jens Rosenboom wrote: > 2017-03-31 2:00 GMT+02:00 Kendall Nelson : >> Candidate proposals for the Technical Committee positions (7 positions) are >> now open and will remain open until 2017-04-20, 23:45 UTC > > The table below states a much earlier closing time. Yeah, I think there was confusion

Re: [openstack-dev] Project Navigator Updates - Feedback Request

Brian Rosmaita wrote: > On 3/29/17 12:55 AM, Jimmy McArthur wrote: > [snip] >> What we really need is the following: >> >> * A project history, including the date of project inception that's >> included in the TC tags. >> * An API history in an easily digestible format that all projects share. >> S

[openstack-dev] [release] Release countdown for week R-21, April 3-7

Welcome to our regular release countdown email! Development Focus - Teams should be working on specs approval and implementation for priority features for this cycle. Actions --- Your team produces libraries, and some of them are still using a version <1.0 ? Now is a good ti

Re: [openstack-dev] rebuild_instance (nova evacuate) failed to add trunk port

On Thu, Mar 30, 2017 at 10:14 PM, KHAN, RAO ADNAN wrote: In Juno, there is an issue with instance rebuild (nova evacuate) when trunk port is associated with that instance. On the target, it is not provisioning tbr (bridge) and hence 'ovs-vsctl' command failed when adding trunk port. Does Jun

Re: [openstack-dev] [barbican][castellan] How to share secrets in barbican

Thanks Kaitlin Farr. In tacker vim usecase, an operator [user A] may create a vim with an account[user B] to access the NFVI. I want to store user B's password in barbican. There are two methods to store secret: 1. All user A's vim secrets are stored in one common reserved project/user as m