Re: [openstack-dev] [Openstack-operators] [nova] Next minimum libvirt version

On Fri, Feb 10, 2017 at 05:42:26PM +, Daniel P. Berrange wrote: > On Thu, Feb 09, 2017 at 05:29:22PM -0600, Matt Riedemann wrote: > > Since danpb hasn't been around I've sort of forgotten about this, but we > > should talk about bumping the minimum required libvirt version in nova. > > > >

Re: [openstack-dev] [gate][neutron][infra] tempest jobs timing out due to general sluggishness of the node?

On Fri, Feb 10, 2017, at 10:54 AM, Ihar Hrachyshka wrote: > Oh nice, I haven't seen that. It does give (virtualized) CPU model > types. I don't see a clear correlation between models and > failures/test times though. We of course miss some more details, like > flags being emulated, but I doubt it

Re: [openstack-dev] [containers][magnum] Make certs insecure in magnum drivers

I have opened the following bug ticket for this issue: https://bugs.launchpad.net/magnum/+bug/1663757 Regards, Adrian On Feb 10, 2017, at 1:46 PM, Adrian Otto > wrote: What I’d like to see in this case is to use secure connections

Re: [openstack-dev] [Designate] In what sense is it multi-tenant?

You can give multiple tenants each their own subdomains and each tenant can't write to each others domains. In addition, if memory serves, each tenant could have private domain servers too which only they could access but manageable through the same api. Thanks, Kevin

Re: [openstack-dev] [magnum][kuryr] python-k8sclient vs client-python (was Fwd: client-python Beta Release)

Dear Magnum Team, Please see review: https://review.openstack.org/#/c/432421/ It depends on the requirements review: https://review.openstack.org/#/c/432409/ Thanks, Dims On Mon, Jan 30, 2017 at 11:54 AM, Antoni Segura Puimedon wrote: > > > On Thu, Jan 26, 2017 at 12:41

[openstack-dev] [Designate] In what sense is it multi-tenant?

In what sense is Designate multi-tenant? Can it be programmed to give different views to different DNS clients? (If so, how?) Thanks, Mike __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [containers][magnum] Make certs insecure in magnum drivers

What I’d like to see in this case is to use secure connections by default, and to make workarounds for self signed certificates or other optional workarounds for those who need them. I would have voted against patch set 383493. It’s also not linked to a bug ticket, which we normally require

Re: [openstack-dev] [api] API WG PTG planning

On Feb 10, 2017, at 2:48 PM, Matt Riedemann wrote: > I assumed we'd take the opportunity to talk about capabilities [1] at the PTG > but couldn't find any etherpad for the API WG on the wiki [2]. > > Is the API WG getting together on Monday or Tuesday? > > [1]

[openstack-dev] Hierarchical quotas at the PTG?

Operators want hierarchical quotas [1]. Nova doesn't have them yet and we've been hesitant to invest scarce developer resources in them since we've heard that the implementation for hierarchical quotas in Cinder has some issues. But it's unclear to some (at least me) what those issues are.

[openstack-dev] [glance] priorities for the coming week (02/10-02/16)

Hello Glancers, Here are the weekly priorities: 1. RC-1 Testing It's looking like there won't be an RC-2, so no need to wait, do some testing on RC-1 now. If you do find an issue, please create a bug, tag it as 'ocata-rc-potential' and give a shout in #openstack-glance for rosmaita or

Re: [openstack-dev] [designate] Status of the project

On 2017-02-10 17:47:50 + (+), Hayes, Graham wrote: [...] > I am struggling to think of even one) multi tenant DNS management > APIs. [...] I ran http://www.nictool.com/ at a service provider years ago, selected specifically because it's a multi-tenant (or at least could be made reasonably

[openstack-dev] [api] API WG PTG planning

I assumed we'd take the opportunity to talk about capabilities [1] at the PTG but couldn't find any etherpad for the API WG on the wiki [2]. Is the API WG getting together on Monday or Tuesday? [1] https://review.openstack.org/#/c/386555/ [2] https://wiki.openstack.org/wiki/PTG/Pike/Etherpads

[openstack-dev] [nova][cinder] Should nova just default to use cinder v3 in Pike?

While talking about [1] yesterday and trying to figure out how to configure nova to use cinder v3 in the CI jobs in Pike, things got a bit messy from the CI job configuration perspective. My initial plan was to make the nova-next (formerly "placement" job [2]) use cinder v3 but that breaks

Re: [openstack-dev] [refstack] Getting on the Pike PTG Agenda?

Hi Aimee, Thanks for raising awareness of the absent etherpad link. The RefStack etherpad link has been added to https://wiki.openstack.org/wiki/PTG/Pike/Etherpads#Monday_-.3E_Tuesday ... We look forward to discussion regarding OPNFV at PTG. Catherine Diep - Forwarded by Catherine Cuong

Re: [openstack-dev] [magnum] devstack/heat problem with master_wait_condition

Hello Stanisław, Were you able to solve this issue? Cheers, Syed On Wed, Aug 26, 2015 at 2:14 PM, Sergey Kraynev wrote: > Hi Stanislaw, > > Your host with Fedora should have special config file, which will send > signal to WaitCondition. > For good example please take a

Re: [openstack-dev] [designate] Status of the project

I’m just catching up with this thread, but I absolutely agree with Jay on documentation and just general messaging. This is not just a Designate issue at all though, this is an issue that many projects have. Well drafted specs, mission, scope, and general messaging are sometimes the bane of

Re: [openstack-dev] [designate] Status of the project

On 10/02/17 19:11, Joshua Harlow wrote: > Fox, Kevin M wrote: >> I'd say kube-dns and designate are very different technologies. >> >> kube-dns is a service discovery mechanism for kubernetes intend to provide >> internal k8s resolution. The fact it uses dns to implement service discovery >> is

Re: [openstack-dev] [designate] Status of the project

On 10/02/17 18:10, Joshua Harlow wrote: > Jay Pipes wrote: >> On 02/10/2017 12:21 PM, Joshua Harlow wrote: >>> Hayes, Graham wrote: The HTML version of this is here: http://graham.hayes.ie/posts/openstack-designate-where-we-are/ I have been asked a few times recently "What is

Re: [openstack-dev] [designate] Status of the project

Fox, Kevin M wrote: I'd say kube-dns and designate are very different technologies. kube-dns is a service discovery mechanism for kubernetes intend to provide internal k8s resolution. The fact it uses dns to implement service discovery is kind of an implementation detail, not its primary

Re: [openstack-dev] [gate][neutron][infra] tempest jobs timing out due to general sluggishness of the node?

Oh nice, I haven't seen that. It does give (virtualized) CPU model types. I don't see a clear correlation between models and failures/test times though. We of course miss some more details, like flags being emulated, but I doubt it will give us a clue. It would be interesting to know the

Re: [openstack-dev] [designate] Status of the project

I'd say kube-dns and designate are very different technologies. kube-dns is a service discovery mechanism for kubernetes intend to provide internal k8s resolution. The fact it uses dns to implement service discovery is kind of an implementation detail, not its primary purpose. There's no need

Re: [openstack-dev] [nova] Next minimum libvirt version

On 2/10/2017 11:18 AM, Thomas Bechtold wrote: For SUSE the wiki is updated and 1.2.9 should be fine. Cheers, Tom Thanks Tom. Would 1.3.1 as the next minimum in Queens be acceptable for SUSE? -- Thanks, Matt Riedemann

Re: [openstack-dev] [All] IRC Mishaps

Well the worst thing I've done is type and send my password...that was on an internal work channel not an OpenStack one, but I think that only made it more embarrassing! -Jon On Wed, Feb 08, 2017 at 08:36:16PM +, Kendall Nelson wrote: :Hello All! : :So I am sure we've all seen it: people

[openstack-dev] [kolla] Support for non-x86_64 architectures

Hello At Linaro I work on running OpenStack on AArch64 (arm64, 64-bit arm, ARMv8a) architecture. We built Cinder, Glance, Heat, Horizon, Keystone, Neutron and Nova for our use and deployed it several times. But for next release we decided to move to use containers for delivering components. This

Re: [openstack-dev] [designate] Status of the project

Jay Pipes wrote: On 02/10/2017 12:21 PM, Joshua Harlow wrote: Hayes, Graham wrote: The HTML version of this is here: http://graham.hayes.ie/posts/openstack-designate-where-we-are/ I have been asked a few times recently "What is the state of the Designate project?", "How is Designate getting

Re: [openstack-dev] [designate] Status of the project

On 10/02/17 16:39, Alexandra Settle wrote: > Sorry, I’m top posting to this reply because Outlook is a terrible inline > poster. > > Hey Designaters! > > Have you tried pinging the docs team? (ie: me – Hello! I’m the docs PTL) Hi - We have in the past, and did not get very far. I know things

Re: [openstack-dev] [designate] Status of the project

On 02/10/2017 12:21 PM, Joshua Harlow wrote: Hayes, Graham wrote: The HTML version of this is here: http://graham.hayes.ie/posts/openstack-designate-where-we-are/ I have been asked a few times recently "What is the state of the Designate project?", "How is Designate getting on?", and by people

Re: [openstack-dev] [designate] Status of the project

Joshua Harlow wrote on 02/10/2017 12:21:08 PM: > Knowing where this is at and the issues. It makes me wonder if it is > worthwhile to start thinking about how we can start to look at 'outside > the openstack' projects for DNS. I believe there is a few that are > similar

Re: [openstack-dev] [designate] Status of the project

On 10/02/17 17:24, Joshua Harlow wrote: > Hayes, Graham wrote: >> The HTML version of this is here: >> http://graham.hayes.ie/posts/openstack-designate-where-we-are/ >> >> I have been asked a few times recently "What is the state of the Designate >> project?", "How is Designate getting on?", and

Re: [openstack-dev] [Openstack-operators] [nova] Next minimum libvirt version

On Thu, Feb 09, 2017 at 05:29:22PM -0600, Matt Riedemann wrote: > Since danpb hasn't been around I've sort of forgotten about this, but we > should talk about bumping the minimum required libvirt version in nova. > > Currently it's 1.2.1 and the next was set to 1.2.9. > > On master we're gating

[openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

I want to give all interested parties a heads up that I have scheduled a session in the Macon room from 9:30-10:30 a.m. on Thursday morning (February 23). Here's what we need to discuss. This is from my perspective as Glance PTL, so it's going to be Glance-centric. This is a quick narrative

[openstack-dev] [Neutron] Alternative approaches for L3 HA

Hello everyone! In Juno in Neutron was implemented L3 HA feature based on Keepalived (VRRP). During next cycles it was improved, we performed scale testing [1] to find weak places and tried to fix them. The only alternative for L3 HA with VRRP is router rescheduling performed by Neutron server,

Re: [openstack-dev] [designate] Status of the project

Hayes, Graham wrote: The HTML version of this is here: http://graham.hayes.ie/posts/openstack-designate-where-we-are/ I have been asked a few times recently "What is the state of the Designate project?", "How is Designate getting on?", and by people who know what is happening "What are you

Re: [openstack-dev] [nova] Next minimum libvirt version

Hi, On Thu, 2017-02-09 at 17:29 -0600, Matt Riedemann wrote: > Since danpb hasn't been around I've sort of forgotten about this, but > we  > should talk about bumping the minimum required libvirt version in > nova. > > Currently it's 1.2.1 and the next was set to 1.2.9. > > On master we're

Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

On 10/02/17 15:24 +0100, Flavio Percoco wrote: On 09/02/17 09:57 +0100, Flavio Percoco wrote: Greetings, I was talking with Tony and he mentioned that he's recording a new demo for kuryr and, well, it'd be great to also use the containerized version of TripleO for the demo. His plan is to

Re: [openstack-dev] [gate][neutron][infra] tempest jobs timing out due to general sluggishness of the node?

On Fri, Feb 10, 2017, at 08:21 AM, Morales, Victor wrote: > > On 2/9/17, 10:59 PM, "Ihar Hrachyshka" wrote: > > >Hi all, > > > >I noticed lately a number of job failures in neutron gate that all > >result in job timeouts. I describe >

Re: [openstack-dev] [designate] Status of the project

Sorry, I’m top posting to this reply because Outlook is a terrible inline poster. Hey Designaters! Have you tried pinging the docs team? (ie: me – Hello! I’m the docs PTL) Over the last few cycles our team has been able to step in and help with formatting, writing, and organizing

Re: [openstack-dev] [gate][neutron][infra] tempest jobs timing out due to general sluggishness of the node?

On 2/9/17, 10:59 PM, "Ihar Hrachyshka" wrote: >Hi all, > >I noticed lately a number of job failures in neutron gate that all >result in job timeouts. I describe >gate-tempest-dsvm-neutron-dvr-ubuntu-xenial job below, though I see >timeouts happening in other jobs too. >

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

Your regular reporter, Chris Dent, is on PTO today, so I'm filling in. I'll be brief. After the flurry of activity to get as much in before the Ocata RCs, this past week was relatively calm. Work continued on the patch to have Ironic resources tracked as, well, individual entities instead of

Re: [openstack-dev] [designate] Status of the project

On 10/02/17 15:48, Doug Hellmann wrote: > Excerpts from Jay Pipes's message of 2017-02-09 21:33:03 -0500: >> On 02/09/2017 02:19 PM, Hayes, Graham wrote: >> >> >>> Where too now then? >>> === >>> >>> Well, this is where I call out to people who actually use the project - >>> don't

Re: [openstack-dev] [designate] Status of the project

On 10/02/17 02:40, Jay Pipes wrote: > On 02/09/2017 02:19 PM, Hayes, Graham wrote: > > >> Where too now then? >> === >> >> Well, this is where I call out to people who actually use the project - >> don't >> jump ship and use something else because of the picture I have painted.

Re: [openstack-dev] [designate] Status of the project

Excerpts from Jay Pipes's message of 2017-02-09 21:33:03 -0500: > On 02/09/2017 02:19 PM, Hayes, Graham wrote: > > > > Where too now then? > > === > > > > Well, this is where I call out to people who actually use the project - > > don't > > jump ship and use something else

Re: [openstack-dev] [Swift][swiftclient][horizon] Improve UX by enabling HTTP headers configuration in UI and CLI

On 10 Feb 2017, at 7:07, Denis Makogon wrote: > Greetings. > > I've been developing Swift middleware that depends on specific HTTP headers > and figured out that there's only one way to specify them on client side - > only in programmatically i can add HTTP headers to each Swift HTTP API >

Re: [openstack-dev] [oslo] pbr and warnerrors status

Excerpts from Andreas Jaeger's message of 2017-02-10 13:57:03 +0100: > On 02/08/2017 05:22 PM, Jay Faulkner wrote: > > [...] > > IMO, I’d suggest skipping this and just fixing the broken attribute. > > Projects that are impacted by the change simply need to merge a one-line > > change to set

[openstack-dev] [Swift][swiftclient][horizon] Improve UX by enabling HTTP headers configuration in UI and CLI

Greetings. I've been developing Swift middleware that depends on specific HTTP headers and figured out that there's only one way to specify them on client side - only in programmatically i can add HTTP headers to each Swift HTTP API method (CLI and dashboard are not supporting HTTP headers

[openstack-dev] [refstack] Getting on the Pike PTG Agenda?

Hi Refstack team - a team from OPNFV will be at the Pike PTG, and we would like to meet with the RefStack team to discuss building a direct link to RefStack and other upstream verification projects. We would like to present the OPNFV Dovetail project and our goals for leveraging upstream test

Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

Flavio, Sounds great to me, look forward to catching up and plotting some collaborative hacking :) Catch you all at the PTG! Cheers Pete On Fri, Feb 10, 2017 at 2:24 PM, Flavio Percoco wrote: > On 09/02/17 09:57 +0100, Flavio Percoco wrote: > >> Greetings, >> >> I was

Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

On Fri, Feb 10, 2017 at 3:24 PM, Flavio Percoco wrote: > On 09/02/17 09:57 +0100, Flavio Percoco wrote: > >> Greetings, >> >> I was talking with Tony and he mentioned that he's recording a new demo >> for >> kuryr and, well, it'd be great to also use the containerized version

Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

On 09/02/17 09:57 +0100, Flavio Percoco wrote: Greetings, I was talking with Tony and he mentioned that he's recording a new demo for kuryr and, well, it'd be great to also use the containerized version of TripleO for the demo. His plan is to have this demo out by next week and that may be too

Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

Dan, There's no way I could have put that any better than Tony! Though he's given me a bit too much credit, I actually just extended his work to make use of Lbaasv2, and never got round to fully making use of OVN's native LoadBalancing. Cheers Pete On Fri, Feb 10, 2017 at 12:34 AM, Antoni

Re: [openstack-dev] [oslo] pbr and warnerrors status

On 02/08/2017 05:22 PM, Jay Faulkner wrote: > [...] IMO, I’d suggest skipping this and just fixing the broken attribute. Projects that are impacted by the change simply need to merge a one-line change to set warnerrors=false. FWIW, you can actually run a local docs build, find and resolve

Re: [openstack-dev] [nova] Next minimum libvirt version

On Thu, Feb 09, 2017 at 05:29:22PM -0600, Matt Riedemann wrote: > Since danpb hasn't been around I've sort of forgotten about this, but we > should talk about bumping the minimum required libvirt version in nova. > > Currently it's 1.2.1 and the next was set to 1.2.9. > > On master we're gating

[openstack-dev] [openstack-docs] What's up, Doc? 10 Feb 2017

Team team team team team, Welcome to my first edition of What's up, Doc? Firstly, I just want to thank everyone who supported me when I announced I would like to run for manuals PTL. Although I ran the election uncontested (like the beginning of all good dictatorships), it was wonderful to

[openstack-dev] [containers][magnum] Make certs insecure in magnum drivers

Hi, This change (https://review.openstack.org/#/c/383493/) makes certificates request to magnum_api insecure since is a common use case. In swarm drivers, the make-cert.py script is in python whereas in K8s for CoreOS and Atomic, it is a shell script. I wanted to make the change

Re: [openstack-dev] [ironic][qa][grenade] Release blocked on grenade job not testing from newton

The root cause why ironic grenade job was broken is described in https://bugs.launchpad.net/ironic/+bug/1663371 In two words, during Ocata we removed DEFAULT_IMAGE_NAME setting logic from devstack [0]. As soon stable/ocata was cut for devstack variable DEFAULT_IMAGE_NAME is not visible in grenade,

Re: [openstack-dev] Mitaka - Unable to attach volume to VM

Hi all, I find out reason I lack config [cinder] os_region_name in compute nova.conf, therefore nova-api contacts with cinder in the rest site. Thanks everyone :) 2017-02-10 11:04 GMT+07:00 Sam Huracan : > Hi Sean, > > I've checked 'openstack volume list', the state

Re: [openstack-dev] [gate][neutron][infra] tempest jobs timing out due to general sluggishness of the node?

I wonder, can we switch to CINDER_ISCSI_HELPER="lioadm" ? On Fri, Feb 10, 2017 at 9:17 AM, Miguel Angel Ajo Pelayo < majop...@redhat.com> wrote: > I believe those are traces left by the reference implementation of cinder > setting very high debug level on tgtd. I'm not sure if that's related or

Re: [openstack-dev] [gate][neutron][infra] tempest jobs timing out due to general sluggishness of the node?

I believe those are traces left by the reference implementation of cinder setting very high debug level on tgtd. I'm not sure if that's related or the culprit at all (probably the culprit is a mix of things). I wonder if we could disable such verbosity on tgtd, which certainly is going to slow

Re: [openstack-dev] [gate][neutron][infra] tempest jobs timing out due to general sluggishness of the node?

I guess it's an infra issue, specifically related to the storage, or the network that provide the storage. If you look at the syslog file [1] , there are a lot of this entries: Feb 09 04:20:42