[openstack-dev] [daisycloud-core] Cancelled: IRC meeting 0800UTC Jan. 6 2017

Hi Team, Due to there is no topic to be discussed, I suggest to cancel the meeting. B.R., Zhijiang __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [Openstack] Download file from swift extremely slow

Jan 6 15:25:51 controller proxy-server: Deferring reject downstream Jan 6 15:25:51 controller proxy-server: - - 06/Jan/2017/07/25/51 HEAD /v1/AUTH_6fc70c831270448296c9c25361769cf5/api HTTP/1.0 404 - Swift - - - - tx4c868c016bf94fb798abf-00586f467f - 0.0152 RL - 1483687551.074624062

Re: [openstack-dev] [heat] glance v2 support?

On 6 Jan 2017, at 05:04, Rabi Mishra > wrote: On Fri, Jan 6, 2017 at 4:38 AM, Emilien Macchi > wrote: Greetings Heat folks! My question is simple: When do you plan to support Glance v2?

Re: [openstack-dev] [heat] project specific question for the next user survey

Dear Team Base on suggestions We open a simple doodle to collect opinions. http://doodle.com/poll/fns89s3ee4za3saw Please help to pick the better question in your mind. Let's voting till the end of this Friday (for everyone!) 2017-01-05 1:06 GMT+08:00 Rico Lin : > Dear

Re: [openstack-dev] [heat] Rolling upgrades vs. duplication of prop data

On Thu, Jan 5, 2017 at 10:28 PM, Zane Bitter wrote: > On 05/01/17 11:41, Crag Wolfe wrote: > >> Hi, >> >> I have a patch[1] to support the de-duplication of resource properties >> data between events and resources. In the ideal rolling-upgrade world, >> we would be writing

Re: [openstack-dev] [heat] glance v2 support?

On Fri, Jan 6, 2017 at 4:38 AM, Emilien Macchi wrote: > Greetings Heat folks! > > My question is simple: > When do you plan to support Glance v2? > https://review.openstack.org/#/c/240450/ > > The spec looks staled while Glance v1 was deprecated in Newton (and v2 > was

Re: [openstack-dev] [tc][kolla] Adding new deliverables

I think you’re giving a great example of my point that we’re not yet at the stage where we can say, “Any tool should be able to deploy kolla containers”. Right? From: Pete Birley Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [Openstack] Different output from same version client on two different hosts.

Since the neutron client versions are the same I suspect a unpinned dependency may be different between the two. Did you install the client via pip or your distro's package manager? On Jan 5, 2017 10:34, "Ken D'Ambrosio" wrote: > Hey, all. I'm writing some wrapper scripts to do

Re: [openstack-dev] [tc][kolla] Adding new deliverables

I'll reply to Britts comments, and then duck out, unless explicitly asked back, as I don't want to (totally) railroad this conversation: The Kolla containers entry-point is a great example of how the field have moved on. While it was initially required, in the Kkubernetes world the Kolla ABI is

[openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

Hi all, Vitrage generate alarms acording to the templates. All the alarms raised by vitrage has the type "vitrage". Suppose Nagios has an alarm A. Alarm A is raised by vitrage evaluator according to the action part of a scenario, type of alarm A is "vitrage". If Nagios reported alarm A

[openstack-dev] [Vitrage] About introduce suspect state of a alarm

Hi all, I have a question when learnning vitrage: A, B, C, D, E are alarms, consider the following alarm propagation model: A --＞ B C --＞ D B or D --＞ E When alarm E is reported by the system, from the above model, we know that

Re: [openstack-dev] [tc][kolla] Adding new deliverables

I think both Pete and Steve make great points and it should be our long term vision. However, I lean more with Michael that we should make that a separate discussion, and it’s probably better done further down the road. Yes, Kolla containers have come a long way, and the ABI has been stable

[openstack-dev] [nova] Feature review sprint on Wednesday 1/11

We agreed in the nova meeting today to hold a feature review sprint next Wednesday 1/11. We'll be going through the unmerged changes in https://etherpad.openstack.org/p/nova-ocata-feature-freeze and try to push some of those through, or get them close. If you have a blueprint series in that

[openstack-dev] [tripleo] removing glance-registry & api v1

Just some heads-up for those who were interested by removing Glance Registry from TripleO (yes Flavio, I'm looking at you !). Because TripleO relies on Heat for the pingtest (validation that OpenStack cloud is up and running) and because Heat doesn't support Glance v2 API [1], we strongly rely on

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Also coming from the perspective of a Kolla-Kubernetes contributor, I am worried about the scope that Kolla is extending itself to. Moving from a single repo to multiple repo's has made the situation much better, but by operating under a single umbrella I feel that we may potentially be

[openstack-dev] [heat] glance v2 support?

Greetings Heat folks! My question is simple: When do you plan to support Glance v2? https://review.openstack.org/#/c/240450/ The spec looks staled while Glance v1 was deprecated in Newton (and v2 was started in Kilo!). As an user, I need Glance v2 support so I can remove Glance Registry from my

Re: [openstack-dev] [keystone] office hours starting January 6th

Heads up folks! Just sending out a friendly reminder that tomorrow will be our first office hour session of the new year. See everyone in #openstack-keystone tomorrow! On Wed, Dec 21, 2016 at 5:32 PM, Rodrigo Duarte wrote: > Thanks for the initiative! This is something

Re: [openstack-dev] [tc][kolla] Adding new deliverables

There are some interesting points in this topic. I agree entirely with Sam Yaple. It does not make sense to me to have kolla-ansible and kolla-kubernetes cores involved with the introduction of a new deliverable under the kolla umbrella. A new deliverable (read: project, really) should not rely

[openstack-dev] [release] Release countdown for week R-6, 2-6 Jan

Happy New Year, everyone! Focus - Feature work and major refactoring should be well under way as we approach the third milestone and various feature and release freeze dates. The deadline for non-client library releases is R-5 (19 Jan). We do not grant Feature Freeze Extensions for any

Re: [openstack-dev] [infra][diskimage-builder] containers, Containers, CONTAINERS!

On 01/05/2017 02:23 PM, Paul Belanger wrote: > Did my click bait work? :) > > So, over the holiday break I had some time to hack on diskimage-builder and > create a new (container) element. I opted to call it ubuntu-rootfs. The basic > idea, is the most minimal debootstrap chroot for ubuntu.

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Excerpts from Michał Jastrzębski's message of 2017-01-05 11:45:49 -0800: > I think total separation of projects would require much larger > discussion in community. Currently we agreed on having kolla-ansible > and kolla-k8s to be deliverables under kolla umbrella from historical > reasons. Also I

[Openstack] nova backup - instances unreachable

Hello, I've just started experimenting with nova backup and discovered that there is a period of time during the snapshot where the instance becomes unreachable. Is this behavior expected during a live snapshot? Is there any way to prevent this? ___ John Petrini

[openstack-dev] [infra][diskimage-builder] containers, Containers, CONTAINERS!

Did my click bait work? :) So, over the holiday break I had some time to hack on diskimage-builder and create a new (container) element. I opted to call it ubuntu-rootfs. The basic idea, is the most minimal debootstrap chroot for ubuntu. Everything in, we can get a 42MB tarball of

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On Thu, Jan 5, 2017 at 7:42 PM, Doug Hellmann wrote: > Excerpts from Sam Yaple's message of 2017-01-05 18:22:54 +: > > On Thu, Jan 5, 2017 at 6:12 PM, Doug Hellmann > wrote: > > > > > Excerpts from Sam Yaple's message of 2017-01-05 17:02:35

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On Thu, Jan 5, 2017 at 7:45 PM, Michał Jastrzębski wrote: > I think total separation of projects would require much larger > discussion in community. Currently we agreed on having kolla-ansible > and kolla-k8s to be deliverables under kolla umbrella from historical > reasons.

Re: [openstack-dev] [tc][kolla] Adding new deliverables

I think total separation of projects would require much larger discussion in community. Currently we agreed on having kolla-ansible and kolla-k8s to be deliverables under kolla umbrella from historical reasons. Also I don't agree that there is "little or no overlap" in teams, in fact there is ton

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Excerpts from Sam Yaple's message of 2017-01-05 18:22:54 +: > On Thu, Jan 5, 2017 at 6:12 PM, Doug Hellmann wrote: > > > Excerpts from Sam Yaple's message of 2017-01-05 17:02:35 +: > > > On Thu, Jan 5, 2017 at 4:54 PM, Jeremy Stanley > > wrote:

Re: [openstack-dev] [TripleO] Fixing Swift rings when upscaling/replacing nodes in TripleO deployments

On 05.01.2017 17:03, Steven Hardy wrote: > On Thu, Jan 05, 2017 at 02:56:15PM +, arkady.kanev...@dell.com wrote: >> I have concern to rely on undercloud for overcloud swift. >> Undercloud is not HA (yet) so it may not be operational when disk failed or >> swift overcloud node is

Re: [openstack-dev] [Release-job-failures] Release of openstack/glance failed

On 1/5/17 3:17 AM, Erno Kuvaja wrote: > On Wed, Jan 4, 2017 at 9:22 PM, Tony Breeds wrote: >> On Wed, Jan 04, 2017 at 01:31:42PM -0500, Ian Cordasco wrote: >> >>> I believe you asked in another thread (that I cannot locate) if it was >>> acceptable to the Glance team to

[openstack-dev] [api] Retiring fairy-slipper, the conversion tool for API docs

Hi all, I believe that with the migration from WADL to RST complete, the use case for fairy-slipper has also come to a close. I plan to retire it. Share any concerns or questions you have, and I'll use the standard process [1] to retire the repo. Anne 1.

Re: [Openstack-operators] RabbitMQ 3.6.x experience?

MIke, I did a bunch of research and experiments on this last fall. We are running Rabbit 3.5.6 on our main cluster and 3.6.5 on our Trove cluster which has significantly less load (and criticality). We were going to upgrade to 3.6.5 everywhere but in the end decided not to, mainly because there

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On Thu, Jan 5, 2017 at 6:12 PM, Doug Hellmann wrote: > Excerpts from Sam Yaple's message of 2017-01-05 17:02:35 +: > > On Thu, Jan 5, 2017 at 4:54 PM, Jeremy Stanley > wrote: > > > > > On 2017-01-05 16:46:36 + (+), Sam Yaple wrote: > > >

Re: [Openstack] [Neutron][VXLAN] PPTP VPN problem

No, I try with simple pptp vpn. On 2017.01.05. 19:13, John Petrini wrote: Are you using OpenVPN? In that case I believe you need the following options on the client: mssfix 1200 tun-mtu 1200 ___ John Petrini NOC Systems Administrator // *CoreDial, LLC* // coredial.com

Re: [openstack-dev] [Security] Shorter Meetings

-Original Message- From: Rob C Reply: OpenStack Development Mailing List (not for usage questions) Date: January 5, 2017 at 12:10:43 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Excerpts from Sam Yaple's message of 2017-01-05 17:02:35 +: > On Thu, Jan 5, 2017 at 4:54 PM, Jeremy Stanley wrote: > > > On 2017-01-05 16:46:36 + (+), Sam Yaple wrote: > > [...] > > > I do feel this is slightly different than whats described. Since it is > > not >

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On Thu, Jan 5, 2017 at 5:56 PM, Alex Schultz wrote: > On Thu, Jan 5, 2017 at 10:25 AM, Michał Jastrzębski > wrote: > > Ad kolla-ansible core team +2ing new deliverable,I agree with Sam, > > there is no reason in my mind for kolla-ansible/k8s core team to

[openstack-dev] [Security] Shorter Meetings

Hi All, As per our IRC meeting today[1] we've decided to try shortening the Security IRC meetings to 30 minutes per week. The other option was to have meetings every two weeks but we all agreed that would lead to missed meetings, confusion around holidays etc. The main reason for shortening our

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Oh you misunderstood good sir;) kolla-puppet is similar to tripleo - it's would set up whole OpenStack using kolla containers deployed by puppet manifests. I agree, if it would only install kolla - that should go to openstack puppet, but kolla is a deployment tool. On 5 January 2017 at 09:56,

Re: [openstack-dev] [kolla] Multi-Regions Support

On Thu, Jan 5, 2017 at 2:12 PM, Ronan-Alexandre Cherrueau < ronan-alexandre.cherru...@inria.fr> wrote: > Hello, > > > TL;DR: We make a multi-regions deployment with Kolla. It requires to > patch the code a little bit, and you can find the diff on our > GitHub[1]. This patch is just a first

Re: [Openstack] [Swift] : Internal Working of PUT Command

On 4 Jan 2017, at 20:44, Sameer Kulkarni wrote: > Hi All, > I was eager to know the data-flow of an object on Openstack Swift PUT > command. I know a highlevel overview from various posts, which I am not > sure of. > >- Client Initiates PUT command specifying the object path on local >

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On Thu, Jan 5, 2017 at 10:25 AM, Michał Jastrzębski wrote: > Ad kolla-ansible core team +2ing new deliverable,I agree with Sam, > there is no reason in my mind for kolla-ansible/k8s core team to vote > on accepting new deliverable. I think this should be lightweight and > easy,

Re: [Openstack] [Neutron][VXLAN] PPTP VPN problem

Are you using OpenVPN? In that case I believe you need the following options on the client: mssfix 1200 tun-mtu 1200 ___ John Petrini NOC Systems Administrator // *CoreDial, LLC* // coredial.com // [image: Twitter] [image: LinkedIn]

Re: [openstack-dev] [kolla] Multi-Regions Support

Great stuff! Thank you Ronan. I'd love to see this guide refactored and submitted to our docs (also take a longer look how to make full fledged support in kolla tree). Looking for volunteers:) On 5 January 2017 at 07:59, Jeffrey Zhang wrote: > Thanks Ronan, > > Great

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Ad kolla-ansible core team +2ing new deliverable,I agree with Sam, there is no reason in my mind for kolla-ansible/k8s core team to vote on accepting new deliverable. I think this should be lightweight and easy, we should allow experimentation (after all, kolla itself went through few fail

[openstack-dev] [all][api] POST /api-wg/news

Greetings OpenStack community, Our first meeting for 2017 opened with a bang. Lots of people in attendance to talk about the ongoing adventure of trying to improve the handling of the concept of visibility in Glance. If we had had more time we could have continued talking about it for a long

Re: [Openstack] FW: Stable Mitaka Devstack Installation Failing with 'deprecated_reason'

that sounds about right, thanks for confirming with the solution! On Thu, Jan 5, 2017 at 11:42 AM, Harsh Kumar B wrote: > Hello, > > Thanks for replying. I had a working VM which I was trying to replicate on > a bare metal so I was building in offline mode. Once I

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On Thu, Jan 5, 2017 at 4:54 PM, Jeremy Stanley wrote: > On 2017-01-05 16:46:36 + (+), Sam Yaple wrote: > [...] > > I do feel this is slightly different than whats described. Since it is > not > > unrelated services, but rather, for lack of a better word, competing > >

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On Thu, Jan 5, 2017 at 8:58 AM, Sam Yaple wrote: > Involving kolla-ansible and kolla-kubernetes in a decision about > kolla-salt (or kolla-puppet, or kolla-chef) is silly since the projects are > unrelated. That would be like involving glance when cinder has a new > service

Re: [openstack-dev] [heat] Rolling upgrades vs. duplication of prop data

On 05/01/17 11:41, Crag Wolfe wrote: Hi, I have a patch[1] to support the de-duplication of resource properties data between events and resources. In the ideal rolling-upgrade world, we would be writing data to the old and new db locations, only reading from the old in the first release (let's

Re: [Openstack] [Neutron][VXLAN] PPTP VPN problem

I am tying, but all the time VPN starts with 1500 MTU. On 2017.01.05. 18:46, John Petrini wrote: Is ppp0 your VPN interface? Have you tried lowering thee MTU on the VPN? ___ John Petrini NOC Systems Administrator // *CoreDial, LLC* // coredial.com // Twitter

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On 2017-01-05 16:46:36 + (+), Sam Yaple wrote: [...] > I do feel this is slightly different than whats described. Since it is not > unrelated services, but rather, for lack of a better word, competing > services. To my knowledge infra doesn't have several service doing the same > job with

Re: [Openstack] FW: Stable Mitaka Devstack Installation Failing with 'deprecated_reason'

Hello, Thanks for replying. I had a working VM which I was trying to replicate on a bare metal so I was building in offline mode. Once I disabled offline mode, it seems to have pulled in the correct versions and went ahead. Thanks Harsh Kumar Original Message From:Steve

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On Thu, Jan 5, 2017 at 4:34 PM, Jeremy Stanley wrote: > On 2017-01-05 15:58:45 + (+), Sam Yaple wrote: > > Involving kolla-ansible and kolla-kubernetes in a decision about > kolla-salt > > (or kolla-puppet, or kolla-chef) is silly since the projects are > unrelated. >

Re: [openstack-dev] [glance] question for OpenStack User Survey

At today's Glance meeting, we decided to go with a version of the question Erno posed below. I've posted an etherpad where we can refine the question in order to increase the probability of receiving useful responses: https://etherpad.openstack.org/p/glance-user-survey-question-feb2017 Please

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On Thu, Jan 5, 2017 at 4:06 PM, Doug Hellmann wrote: > Excerpts from Sam Yaple's message of 2017-01-05 15:58:45 +: > > Involving kolla-ansible and kolla-kubernetes in a decision about > kolla-salt > > (or kolla-puppet, or kolla-chef) is silly since the projects are >

[openstack-dev] [heat] Rolling upgrades vs. duplication of prop data

Hi, I have a patch[1] to support the de-duplication of resource properties data between events and resources. In the ideal rolling-upgrade world, we would be writing data to the old and new db locations, only reading from the old in the first release (let's assume Ocata). The problem is that in

Re: [openstack-dev] [ironic] [inspector] RFC: deprecating "set IPMI credentials" feature in ironic-inspector

On 12/13/2016 01:40 PM, Dmitry Tantsur wrote: Hi folks! Since nearly its beginning, ironic-inspector has had a controversial feature: we allow a user to request changing IPMI credentials of the node after introspection. The new credentials are passed back from inspector to the ramdisk, and the

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On 2017-01-05 15:58:45 + (+), Sam Yaple wrote: > Involving kolla-ansible and kolla-kubernetes in a decision about kolla-salt > (or kolla-puppet, or kolla-chef) is silly since the projects are unrelated. > That would be like involving glance when cinder has a new service because > they both

Re: [Openstack] [Neutron][VXLAN] PPTP VPN problem

Network it self are working great, but I just have issue with PPTP. If I lower MTU in instance interface, it didn't help. On 2017.01.05. 18:11, Prashant Shetty wrote: Could you try setting MTU lesser value say 1200 on instance interface and re-try?. Ideally your physical server connecting to

Re: [OpenStack-Infra] Logs for Ask.O.o - chasing false positive spam labeling

Hello, I am the test user, mentioned by Tom. Since some months, and unfortunately still now after your mentioned upgrade, I get the error "Spam is detected on your post - sorry if it was a mistake." if I want to comment a post or if I want to create a new post. It is independent of the

Re: [Openstack] [Neutron][VXLAN] PPTP VPN problem

Could you try setting MTU lesser value say 1200 on instance interface and re-try?. Ideally your physical server connecting to switch port must have configured with atleast 1600 MTU in order for VXLAN traffic to work seamlessly. Thanks, Prashant On Thu, Jan 5, 2017 at 9:30 PM, Mārtiņš Jakubovičs

Re: [Openstack] FW: Stable Mitaka Devstack Installation Failing with 'deprecated_reason'

what version of oslo.config was laid down? it should be at least 3.2.0 to support "deprecated_reason" -- https://github.com/openstack/oslo.config/blob/stable/mitaka/oslo_config/cfg.py#L719-L720 using the mitaka branch of devstack should lay down version 3.7.0. can you include the local.conf and

Re: [OpenStack-Infra] Logs for Ask.O.o - chasing false positive spam labeling

On 05/01/17 23:26, Jeremy Stanley wrote: On 2017-01-02 23:03:07 + (+), Jeremy Stanley wrote: [...] We're basically ready to retry the previous upgrade now that some issues have been identified/corrected by Marton. Change https://review.openstack.org/408657 to trigger it is waiting on

[Openstack] [Neutron][VXLAN] PPTP VPN problem

Hello all, I have problem to setup PPTP VPN behind floating IP's in instances which have VXLAN network. Maybe someone had same issue and can recommend something? In security groups I allowed protocol's 47 traffic and VPN client can connect but it can't establish connection, I consider, maybe

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Excerpts from Sam Yaple's message of 2017-01-05 15:58:45 +: > Involving kolla-ansible and kolla-kubernetes in a decision about kolla-salt > (or kolla-puppet, or kolla-chef) is silly since the projects are unrelated. > That would be like involving glance when cinder has a new service because >

Re: [openstack-dev] [kolla] Multi-Regions Support

Thanks Ronan, Great approach. I am always expecting multi-region support in Kolla. I hope what you did can be merged into Kolla. On Thu, Jan 5, 2017 at 10:12 PM, Ronan-Alexandre Cherrueau < ronan-alexandre.cherru...@inria.fr> wrote: > Hello, > > > TL;DR: We make a multi-regions deployment

Re: [openstack-dev] [TripleO] Fixing Swift rings when upscaling/replacing nodes in TripleO deployments

On Thu, Jan 05, 2017 at 02:56:15PM +, arkady.kanev...@dell.com wrote: > I have concern to rely on undercloud for overcloud swift. > Undercloud is not HA (yet) so it may not be operational when disk failed or > swift overcloud node is added/deleted. I think the proposal is only for a

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Involving kolla-ansible and kolla-kubernetes in a decision about kolla-salt (or kolla-puppet, or kolla-chef) is silly since the projects are unrelated. That would be like involving glance when cinder has a new service because they both use keystone. The kolla-core team is reasonable since those

Re: [openstack-dev] [Monasca] Monasca devstack installation is failing

I think this is going to require more time and information. Perhaps you could open a launchpad bug to track this? I just brought up a new vagrant successfully yesterday, would you mind checking if you have the latest code and trying again? Also, if there is anything else relating to storm or

Re: [openstack-dev] [networking-sfc] Intermittent database transaction issues, affecting the tempest gate

After some research, this review fixes the tempest failures: https://review.openstack.org/#/c/416503/1 (newer patchset has an unrelated fix for the functional tests gate) Multiple local tempest runs and gate rechecks all turned green with this fix. That is the good news part. The bad news is

[Openstack-operators] RabbitMQ 3.6.x experience?

We are looking at upgrading to the latest RabbitMQ in an effort to ease some cluster failover issues we’ve been seeing. (Currently on 3.4.0) Anyone been running 3.6.x? And what has been your experience? Any gottchas to watch out for? Thanks, Mike

[openstack-dev] [ironic] User survey question

Hello, I would like to use this opportunity upcoming to decide things related to one of features that I am implementing. To prevent lost-update problem, the user in the next Ironic API versions will have the ability to use the entity tag for each resource. Thus, in order to send conditional

Re: [OpenStack-Infra] Logs for Ask.O.o - chasing false positive spam labeling

On 2017-01-02 23:03:07 + (+), Jeremy Stanley wrote: [...] > We're basically ready to retry the previous upgrade now that some > issues have been identified/corrected by Marton. Change > https://review.openstack.org/408657 to trigger it is waiting on > https://review.openstack.org/416072 to

Re: [openstack-dev] [tripleo] quick reminder on review policy

On Wed, Jan 4, 2017 at 8:57 AM, John Trowbridge wrote: > > > On 01/03/2017 07:30 PM, Emilien Macchi wrote: >> I've noticed some TripleO core reviewers self approving patch without >> respecting our review policy, specially in tripleo-quickstart. >> > > This is slightly

Re: [openstack-dev] [tripleo] [ci] TripleO-Quickstart Transition to TripleO-CI Update and Invite:

On Wed, Jan 4, 2017 at 11:22 AM, Attila Darazs wrote: > On 01/04/2017 10:34 AM, Steven Hardy wrote: >> >> Hi Harry, >> >> On Tue, Jan 03, 2017 at 04:04:51PM -0500, Harry Rybacki wrote: >>> >>> Greetings All, >>> >>> Folks have been diligently working on the blueprint[1] to

Re: [openstack-dev] [glance][tempest][api] community images, tempest tests, and API stability

To anyone interested in this discussion: I put it on the agenda for today's API-WG meeting (16:00 UTC): https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda On 12/25/16 12:04 PM, GHANSHYAM MANN wrote: > Thanks Brian for bringing this up, same we been discussing last week on QA > channel and

Re: [openstack-dev] [TripleO] Fixing Swift rings when upscaling/replacing nodes in TripleO deployments

I have concern to rely on undercloud for overcloud swift. Undercloud is not HA (yet) so it may not be operational when disk failed or swift overcloud node is added/deleted. -Original Message- From: Christian Schwede [mailto:cschw...@redhat.com] Sent: Thursday, January 05, 2017 6:14 AM

Re: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] [vitrage] how to useplaceholder vertex

A follow up question on relationships. On Thu, Jan 5, 2017 at 9:59 PM Weyl, Alexey (Nokia - IL) < alexey.w...@nokia.com> wrote: > Hi Yujun, > > Lets see. > > 1. There is no need for the transformer to handle this duplication. What > will happen at the moment is that we will receive twice every

Re: [openstack-dev] [tripleo] TripleO-Quickstart Transition to TripleO-CI Update and Invite:

On Tue, Jan 3, 2017 at 4:04 PM, Harry Rybacki wrote: > Greetings All, > > Folks have been diligently working on the blueprint[1] to prepare > TripleO-Quickstart (OOOQ)[2] and TripleO-Quickstart-Extras[3] for > their transition into TripleO-CI. Presently, our aim is to begin

Re: [openstack-dev] [Release-job-failures] Release of openstack/glance failed

On 04/01/17 13:31 -0500, Ian Cordasco wrote: -Original Message- From: Tony Breeds Reply: OpenStack Development Mailing List (not for usage questions) , OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [oslo] Not running for Oslo PTL for Pike

On Tue, Jan 3, 2017 at 3:03 PM, Joshua Harlow wrote: > Hi Oslo folks (and others), > > Happy new year! > > After serving for about a year I think it's a good opportunity for myself to > let another qualified individual run for Oslo PTL (seems common to only go > for two

[openstack-dev] [kolla] Multi-Regions Support

Hello, TL;DR: We make a multi-regions deployment with Kolla. It requires to patch the code a little bit, and you can find the diff on our GitHub[1]. This patch is just a first attempt to support multi-regions in Kolla and it raises questions. Some modifications are not done in an idiomatic way

Re: [openstack-dev] 答复: RE: Re: [ALU] [Vitrage] vitrage tempest job config

On 2017-01-05 01:13:20 + (+), Yujun Zhang wrote: > It seems the file is truncated on Github preview. It stops at > openstack/security-specs > > If you check the raw file[1], you will find entry of openstack/vitrage > > [1]: >

Re: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] [vitrage] how to useplaceholder vertex

Hi Yujun, Lets see. 1. There is no need for the transformer to handle this duplication. What will happen at the moment is that we will receive twice every neighbor, and it is fine by us, because it is a quite small datasource, and 99.999% of the time it won't be changed. 2. It should be 2

Re: [openstack-dev] [ironic] User survey question

One thought I had. And it may not be appropriate: Do you use or have you considered using Ironic for non X86 based systems (arm, powerpc, etc)? Are you in the telecom industry? Should Ironic support ATCA based systems to make use of older hardware? I am facing a potential project in the next few

Re: [openstack-dev] [ALU] Re: [ALU] [vitrage] how to use placeholder vertex

Alexey, I have to dig this old thread to clarify some issues I met during static datasource implementation. Hope that you can still recall the context :-) I'll try to simplify this question with an example. The following configuration are snippet from static datasource 1. suppose we have three

[openstack-dev] [infra][nodepool][ci][keystone]

Hi Devs, We are bringing up new CI using latest CI Solution[1] And we are facing some issues[2] with connection nodepool[3] to devstack provider[4] Due to keystone authentication error[5], looks like some missing info in the nodepool.yaml Please advise. p.s. provider was done by bringing up

Re: [Openstack] deploy openstack components on contaienrs and HA

So let’s say I have one container running rabbitMQ, Mysql, etc. data is mounted through volumes. If the container dies and is recreated and the data mounted. Will my openstack environment keep working as usual? I mean can we really run openstack on stateless containers? Are these kind of

[openstack-dev] [TripleO] Fixing Swift rings when upscaling/replacing nodes in TripleO deployments

Hello everyone, there was an earlier discussion on $subject last year [1] regarding a bug when upscaling or replacing nodes in TripleO [2]. Shortly summarized: Swift rings are built on each node separately, and if adding or replacing nodes (or disks) this will break the rings because they are no

Re: [openstack-dev] [neutron][ml2] Mechanism drivers ! OpenvSwich or Linuxbridge or both of them?

Hello, In such case like You described, ports will be bound with openvswitch mechanism driver because this agent will be found as alive on host. So linuxbridge mechanism driver will do nothing for binding such ports. -- Slawek Kaplonski sla...@kaplonski.pl W dniu 05.01.2017 04:51, zhi

Re: [openstack-dev] [neutron][ml2] Mechanism drivers ! OpenvSwich or Linuxbridge or both of them?

The mechanism drivers populate the vif details that tell nova how it's supposed to setup the VM port. So the linux bridge driver tells it the port type is linux bridge[1] and the OVS tells it that the type is OVS. So if you have both loaded and ovs is running on the compute node. The following

Re: [openstack-dev] [oslo] Not running for Oslo PTL for Pike

Josh, It has been great working with you as the PTL of Oslo. Thanks for your leadership. -amrith > -Original Message- > From: Joshua Harlow [mailto:harlo...@fastmail.com] > Sent: Tuesday, January 3, 2017 3:04 PM > To: OpenStack Development Mailing List (not for usage questions)

Re: [Openstack] deploy openstack components on contaienrs and HA

Docker recommends to maintain another controller to replace HA ( external ) using Kubernates if any nodes fail, having HA inside containers is another way of HA deployment i guess. On Thu, Jan 5, 2017 at 12:56 PM, Manuel Sopena Ballesteros < manuel...@garvan.org.au> wrote: > Hi, > > > > Would it

Re: [Openstack] [OpenStack][Swift] problem about swift proxy easurecode

Hello Nalee, > I already installed libeasurecode. Did you install liberasurecode from source? The issue you hit looks from older version of liberasurecode which is in xenial repo. And the newest repo for liberasurecode/pyeclib is in oponstack namespace at github[1][2]. The install procedure

Re: [Openstack] problems extending the isntance volume

On 5 Jan 2017, at 09:55, Manuel Sopena Ballesteros wrote: > I can see from my the host that the LVM has the new size (20G), however when > I ssh into the instance the disk space has not changed. Both df –h and fdisk > –l shows a space of 10Gigs Search ‘linux grow

[OpenStack-Infra] Request to change zvm-ci group owner to zvm-driver-core

Hi All,   We just added a new group - zvm-ci for zVM CI jobs to vote zvm projects. Could someone help change the owner of zvm-ci to zvm-driver-core group so that we can manage it? Thanks in advance!Regards---Huang RuizVM System Management

[openstack-dev] [heat] Pike PTG sessions

HI All, I've started an etherpad[1] to collect topic ideas for the PTG. We would have a meeting room for 3 days(Wednesday-Friday). Feel free to add whatever you think we should discuss/implement. Basic information about the PTG (schedule, layout etc) is available at

Re: [Openstack-operators] [Glance] [Nova] Multiple backends / Qcow Derived Images

On 5 January 2017 at 19:47, Rui Chen wrote: > Ah, Adam, got your point, I found two related Nova blueprints that were > similar with your idea, > but there are not any activities about them from 2014, I hadn't dive deep > into these comments, > you might get some

Re: [Openstack] [open stack] Horizon installation error.

I fixed this by doing remove and install horizon dashboard helped me to get rid of this issue. On Thu, Jan 5, 2017 at 1:29 PM, shivkumar gupta wrote: > Hello Experts, > > my this problem is resolved after copying local_settings.py file > under

Re: [Openstack-operators] [Glance] [Nova] Multiple backends / Qcow Derived Images

Ah, Adam, got your point, I found two related Nova blueprints that were similar with your idea, but there are not any activities about them from 2014, I hadn't dive deep into these comments, you might get some background information at there.

  1   2   >