Re: [Openstack-operators] [Forum] Forum etherpad template and hashtags recommendation

On 04/26/2017 05:22 PM, Sun, Yih Leong wrote: Hi, In preparation for the OpenStack Boston Forum, the Product WG recently discussed how to make it easier for moderators and the community to continue discussions from the Forum an easy and consistent experience. The team came up with a few

Re: [openstack-dev] [Openstack-operators] [Forum] Forum etherpad template and hashtags recommendation

On 04/26/2017 05:22 PM, Sun, Yih Leong wrote: Hi, In preparation for the OpenStack Boston Forum, the Product WG recently discussed how to make it easier for moderators and the community to continue discussions from the Forum an easy and consistent experience. The team came up with a few

Re: [openstack-dev] [nova][oslo.utils] Bug-1680130 Check validation of UUID length

Best, -jay On 04/24/2017 09:44 AM, Jay Pipes wrote: On 04/24/2017 09:45 AM, Jadhav, Pooja wrote: Solution 3: We can check UUID in central place means in "is_uuid_like" method of oslo_utils [4]. This gets my vote. It's a bug in the is_uuid_like() function, IMHO, that is returns True

Re: [openstack-dev] [nova][oslo.utils] Bug-1680130 Check validation of UUID length

On 04/24/2017 09:45 AM, Jadhav, Pooja wrote: Solution 3: We can check UUID in central place means in "is_uuid_like" method of oslo_utils [4]. This gets my vote. It's a bug in the is_uuid_like() function, IMHO, that is returns True for badly-formatted UUID values (like having two consecutive

Re: [openstack-dev] OpenStack "R" Release Naming Preliminary Results

On 04/21/2017 08:11 AM, Monty Taylor wrote: 5. Rock loses to Radium by 841–464, loses to Razorback by 660–569 Actually, Rock lost to Paper, which lost to Scissors. -jay __ OpenStack Development Mailing List (not for

Re: [Openstack] Hello

On 04/21/2017 07:29 AM, TanXin wrote: I want to know if I subscribe successfully. yes. ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe :

Re: [openstack-dev] [Blazar] Meeting time slots in Boston

On 04/21/2017 12:41 AM, Masahito MUROI wrote: Hi all, Thanks for choosing time slots! Based on the table of Doodle, I'd like to pick following two slots for Blazar team meeting. 1. 1pm-4pm on Monday for Blazar's internal features 2. 9am-10am or 11am on Thursday for discussions with

Re: [openstack-dev] [Tacker][OSC] Command naming specs

On 04/17/2017 07:46 PM, Sridhar Ramaswamy wrote: I like this suggestion. Keyword 'vnf' is the closest to the unit of things orchestrated by Tacker. Building on that we can have, openstack vnf create - /create a single VNF based on TOSCA template/ openstack vnf service create - /create a service

[openstack-dev] [intel experimental ci] Is it actually checking anything?

Please see the below output from the Intel Experimental CI (from https://review.openstack.org/414769): On 04/17/2017 01:28 PM, Intel Experimental CI (Code Review) wrote: Intel Experimental CI has posted comments on this change. Change subject: placement: SRIOV PF devices as child providers

Re: [openstack-dev] [kolla] Tags, revisions, dockerhub

Or you could use pbr's strategy, which tags based on git tags and revision history: https://docs.openstack.org/developer/pbr/#version "If the currently checked out revision is not tagged, then we take the last tagged version number and increment it to get a minimum target version." Best,

Re: [openstack-dev] [shade] help wanted - tons to do, not enough people

On 04/12/2017 02:15 PM, Sean Dague wrote: On 04/12/2017 01:38 PM, Monty Taylor wrote: On 04/12/2017 11:21 AM, Joshua Harlow wrote: Just a question, not meant as anything bad against shade, But would effort be better spent on openstacksdk? tl;dr - great in practice, falls apart in the

Re: [openstack-dev] [Tacker][OSC] Command naming specs

On 04/12/2017 03:08 AM, Trinath Somanchi wrote: Hi OSC team- While implementing tacker-cli commands as OSC plugins [1], We are struck in command naming specifications. Tacker being NFVO+VNFM - an NFV component, we have taken ‘nfv’ as the prefix. It's not *all* of NFV, though. This problem,

Re: [openstack-dev] [libvirt] Whether kvm supports NVIDIA VGPU

On 04/12/2017 10:53 PM, 文峰sx-9149 wrote: Will the openstack or libvirt (kvm) support NVIDIA VGPU? I am here to see a mail introduction libvirt kvm support VGPU. But I do not know the current development situation of this

Re: [Openstack-operators] [scientific] Resource reservation requirements (Blazar) - Forum session

On 04/11/2017 02:08 PM, Pierre Riteau wrote: On 4 Apr 2017, at 22:23, Jay Pipes <jaypi...@gmail.com <mailto:jaypi...@gmail.com>> wrote: On 04/04/2017 02:48 PM, Tim Bell wrote: Some combination of spot/OPIE What is OPIE? Maybe I missed a message: I didn’t see any reply to Ja

Re: [openstack-dev] [tc] [elections] Available time and top priority

On 04/10/2017 02:26 PM, Ed Leafe wrote: On Apr 10, 2017, at 4:16 AM, Thierry Carrez wrote: If there was ONE thing, one initiative, one change you will actively push in the six months between this election round and the next, what would it be ? Just one? If I had to

Re: [Openstack] EC2API Very Slow

On 04/10/2017 04:25 PM, Georgios Dimitrakakis wrote: Hello again, after some time... The "nova list" command is very fast indeed and the only problem I observer is through the EC2 API. I have found out the following bug and I believe is related to it, what do you people think?

Re: [openstack-dev] [nova] nova boot from image created volume

jaypipes@serialcoder:~/src/git.openstack.org/openstack/nova/nova$ ack-grep --ignore-dir tests --ignore-dir locale "volume_api.create" compute/api.py 2982:snapshot = self.volume_api.create_snapshot_force( api/openstack/compute/volumes.py 185:new_volume =

[openstack-dev] [murano][k8s] Fwd: Re: [kubernetes-users] how to upgrade kubectl version

Just in case any Murano developers are also on the Kubernetes users list, this came up. Might be good to reach out to our Kubernetes friends here if we have some insights that could help them. Here's a list to the Google Groups message if it's easier to read than the mangled email below:

Re: [openstack-dev] [nova] Contributing support for Netronome Agilio adaptors

On 04/03/2017 06:34 AM, Jan Gutter wrote: Greetings, Apologies for chiming in very late into the spec cycle. Netronome is completing its internal processes in order to allow developers to contribute code to OpenStack and we should be able to share patches within the week. Additional apologies

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

Re: [Openstack] Neutron Network DNS Suffix via DHCP

Thanks for the update, Oisin, this is very useful! :) Best, -jay On 03/28/2017 08:39 PM, Oisin O'Malley wrote: There was 2 separate issues to resolve; Firstly Nova was appending the default domain name .novalocal to the hostname it presents via the meta-data service. This can be resolved by

Re: [openstack-dev] [nova][api] GET or HEAD for checking trait existence

On 03/29/2017 02:04 PM, Ken'ichi Ohmichi wrote: Hi I have some questions about plancement API design from https://review.openstack.org/#/c/376200 Current implementation of the above patch (PS26) adds GET method for checking trait existence, and tags.rst of api-wg guideline[1] requires GET for

Re: [Openstack] Troubles with networking part of openstack

+kevin benton On 03/28/2017 07:20 AM, Bartłomiej Solarz-Niesłuchowski wrote: Dear List, I am beginner of openstack user. Welcome to the OpenStack community! :) I setup openstack with RDO on Centos 7. I have 6 machines: they have two interfaces enp2s0f0 (10.51.0.x) and enp2s0f1

Re: [Openstack-operators] Memory usage of guest vms, ballooning and nova

On 03/23/2017 01:01 PM, Jean-Philippe Methot wrote: Hi, Lately, on my production openstack Newton setup, I've ran into a situation that defies my assumptions regarding memory management on Openstack compute nodes and I've been looking for explanations. Basically, we had a VM with a flavor that

Re: [Openstack] Neutron Network DNS Suffix via DHCP

On 03/26/2017 11:49 PM, Matthew Taylor wrote: Responded off-list. For the benefit of the community, would one of you care to repeat the answer on-list please? Thanks! -jay On 27/3/17 14:22, Oisin O'Malley wrote: Hi All, What is the correct way to set an instances DNS search suffix via

Re: [Openstack] EC2API Very Slow

On 03/26/2017 04:06 PM, Georgios Dimitrakakis wrote: Hello, can someone let me know if it's an expected behavior the EC2API to be very slow in Ocata? I have an old installation of OpenStack (Icehouse) with NOVA-EC2 and when requesting an instance's info I am getting them back in 9sec. In a

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

On 03/21/2017 04:29 PM, Clint Byrum wrote: Excerpts from Doug Hellmann's message of 2017-03-15 15:35:13 -0400: Excerpts from Thomas Herve's message of 2017-03-15 09:41:16 +0100: On Wed, Mar 15, 2017 at 12:05 AM, Joshua Harlow wrote: * How does reloading work (does

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

On 03/20/2017 09:24 PM, Qiming Teng wrote: On Mon, Mar 20, 2017 at 03:35:18PM -0400, Jay Pipes wrote: On 03/20/2017 03:08 PM, Adrian Otto wrote: Team, Stephen Watson has been working on an magnum feature to add magnum commands to the openstack client by implementing a plugin: https

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

On 03/20/2017 03:08 PM, Adrian Otto wrote: Team, Stephen Watson has been working on an magnum feature to add magnum commands to the openstack client by implementing a plugin: https://review.openstack.org/#/q/status:open+project:openstack/python-magnumclient+osc In review of this work, a

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

], quick prototype requests based code [3] Thanks, Dims [1] https://review.openstack.org/#/c/446983/ [2] https://github.com/coreos/etcd/blob/master/Documentation/dev-guide/api_grpc_gateway.md [3] https://gist.github.com/dims/19ceaf9472ef54aa3011d7a11e809371 On Sun, Mar 19, 2017 at 9:32 AM, Jay Pipes

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 03/18/2017 07:48 PM, Mike Perez wrote: On 12:35 Mar 14, Jay Pipes wrote: On 03/14/2017 08:57 AM, Julien Danjou wrote: On Tue, Mar 14 2017, Davanum Srinivas wrote: Let's do it!! (etcd v2-v3 in tooz) Hehe. I'll move that higher in my priority list, I swear. But anyone is free to beat me

Re: [openstack-dev] [all][ironic] Kubernetes-based long running processes

On 03/18/2017 08:33 AM, Tomasz Pa wrote: On 16 Mar 2017 6:21 pm, "Dean Troyer" > wrote: Before implementing something new it would be a good exercise to have a look at the other existing ways to run VMs and containers already in the

Re: [openstack-dev] [nova] Should we delete the (unexposed) os-pci API?

On 03/17/2017 04:23 PM, Sean Dague wrote: On 03/17/2017 04:19 PM, Matt Riedemann wrote: I was working on writing a spec for a blueprint [1] that would have touched on the os-pci API [2] and got to documenting about how it's not even documented [3] when Alex pointed out that the API is not even

Re: [Openstack-operators] [nova] [neutron] Hooks for instance actions like creation, deletion

On 03/16/2017 10:48 PM, Masha Atakova wrote: Hi everyone, Is there any up-to-date functionality in nova / neutron which allows to run some additional code triggered by changes in instance like creating or deleting an instance? I see that nova hooks are deprecated as of Nova 13:

Re: [openstack-dev] [nova] [placement] small wart in the resource class API

Yup, I'm cool with that, too. Best, -jay On 03/16/2017 11:00 AM, Sylvain Bauza wrote: Le 16/03/2017 14:12, Chris Dent a écrit : (This message is a question asking "should we fix this?" and "if so, I guess that needs spec, since it is a microversion change, but would an update to the

Re: [Openstack] Placement service credentials do not work

The error is: On 03/16/2017 07:01 AM, Vikash Kumar wrote: Placement service credentials do not work Check that the user "placement" in the project "service" having the password "testetst" can access the Keystone authentication endpoint at "http://10.1.110.98:5000;. Best, -jay

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

not compatible during this engagement. Boris, would you mind refreshing memories on this? Best, -jay From: Jay Pipes [jaypi...@gmail.com] Sent: Wednesday, March 15, 2017 11:41 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [tc][appcat

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

On 03/15/2017 01:21 PM, Fox, Kevin M wrote: Other OpenStack subsystems (such as Heat) handle this with Trusts. A service account is made in a different, usually SQL backed Keystone Domain and a trust is created associating the service account with the User. This mostly works but does give the

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 03/15/2017 07:44 AM, Sean Dague wrote: On 03/14/2017 11:00 PM, Monty Taylor wrote: a) awesome. when the rest of this dips momentarily into words that might sound negative, please hear it all wrapped in an "awesome" and know that my personal desire is to see the thing you're working on be

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 03/14/2017 05:01 PM, Clint Byrum wrote: Excerpts from Jay Pipes's message of 2017-03-14 15:30:32 -0400: On 03/14/2017 02:50 PM, Julien Danjou wrote: On Tue, Mar 14 2017, Jay Pipes wrote: Not tooz, because I'm not interested in a DLM nor leader election library (that's what the underlying

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 03/14/2017 04:22 PM, Joshua Harlow wrote: Jay Pipes wrote: On 03/14/2017 02:50 PM, Julien Danjou wrote: On Tue, Mar 14 2017, Jay Pipes wrote: Not tooz, because I'm not interested in a DLM nor leader election library (that's what the underlying etcd3 cluster handles for me), only a fast

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 03/14/2017 02:50 PM, Julien Danjou wrote: On Tue, Mar 14 2017, Jay Pipes wrote: Not tooz, because I'm not interested in a DLM nor leader election library (that's what the underlying etcd3 cluster handles for me), only a fast service liveness/healthcheck system, but it shows usage of etcd3

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 03/14/2017 08:57 AM, Julien Danjou wrote: On Tue, Mar 14 2017, Davanum Srinivas wrote: Let's do it!! (etcd v2-v3 in tooz) Hehe. I'll move that higher in my priority list, I swear. But anyone is free to beat me to it in the meantime. ;) A weekend experiment:

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

On 03/13/2017 05:10 PM, Zane Bitter wrote: On 12/03/17 11:30, Clint Byrum wrote: Excerpts from Fox, Kevin M's message of 2017-03-11 21:31:40 +: No, they are treated as second class citizens. Take Trova again as an example. The underlying OpenStack infrastructure does not provide a good

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

On 03/13/2017 11:13 AM, Dan Smith wrote: Interestingly, we just had a meeting about cells and the scheduler, which had quite a bit of overlap on this topic. That said, as mentioned in the previous email, the priorities for Pike (and likely Queens) will continue to be, in order: traits, ironic,

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

On 03/13/2017 09:16 AM, Sylvain Bauza wrote: Please don't. Having a separate repository would mean that deployers would need to implement a separate package for placement plus discussing about how/when to use it. Apparently, there already *are* separate packages for

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

On 03/13/2017 10:02 AM, Eoghan Glynn wrote: We are close to the first milestone in Pike, right ? We also have priorities for Placement that we discussed at the PTG and we never discussed about how to cut placement during the PTG. Also, we haven't discussed yet with operators about how they

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

On 03/13/2017 08:41 AM, Chris Dent wrote: From the start we've been saying that it is probably right for the placement service to have its own repository. This is aligned with the long term goal of placement being useful to many services, not just nova, and also helps to keep placement

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

On 03/10/2017 01:37 PM, Zane Bitter wrote: On 09/03/17 23:57, Renat Akhmerov wrote: And this whole discussion is taking me to the question: is there really any officially accepted strategy for OpenStack for 1, 3, 5 years? Is there any ultimate community goal we’re moving to regardless of

Re: [openstack-dev] [oslo] question about oslo_utils and oslo_versonedobjects

nge the codes as you described. Really appreciate your reply. Best Wishes! zeng chen At 2017-03-09 10:43:23, "Jay Pipes" <jaypi...@gmail.com> wrote: On 03/08/2017 09:07 PM, zengchen wrote: Hi, jay Thanks for your reply. Do you means it is no need to do that optimization? In my op

Re: [openstack-dev] [all] Some information about the Forum at the Summit in Boston

On 03/09/2017 01:06 PM, Dmitry Tantsur wrote: On 03/09/2017 06:57 PM, Clint Byrum wrote: Excerpts from Ben Swartzlander's message of 2017-03-09 11:23:31 -0500: Combine that with the lower cost and subsidized travel support program for the PTG, and you should end up with a more complete

Re: [openstack-dev] [oslo] question about oslo_utils and oslo_versonedobjects

anything. Can you elaborate on what issue you are facing? Best, -jay At 2017-03-08 00:57:51, "Jay Pipes" <jaypi...@gmail.com> wrote: On 03/07/2017 01:34 AM, zengchen wrote: Hi, guys: I find a non-coincidence definition in Oslo, oslo_utils.timeutils.utcnow

Re: [Openstack] devstack and openbaton integration

On 03/08/2017 01:15 PM, Antonio Cappuccio wrote: Hi all, we are configuring openbaton on top of openstack. We have installed devstack and openbaton on the same VM, with ubuntu 14.04. Both openbaton and openstack dashboards look fine, so we think we have installed both products in the right

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

On 03/06/2017 06:26 AM, Thierry Carrez wrote: Hello everyone, The App Catalog was created early 2015 as a marketplace of pre-packaged applications that you can deploy using Murano. Initially a demo by Mirantis, it was converted into an open upstream project team, and deployed as a "beta" as

Re: [openstack-dev] [oslo] question about oslo_utils and oslo_versonedobjects

On 03/07/2017 01:34 AM, zengchen wrote: Hi, guys: I find a non-coincidence definition in Oslo, oslo_utils.timeutils.utcnow is defined like this: def utcnow(with_timezone=False): oslo_versonedobjects.fields.DateTimeField is defined like this

Re: [Openstack] Query Reg. Mirantis Community Version

On 03/06/2017 06:05 AM, Raja T Nair wrote: Hi, Can I ask queries about Mirantis community version on this list? If not, can somebody point to an appropriate link? Hi Raja, There's no such thing as Mirantis Community version. Are you referring to OpenStack Fuel? Perhaps the Mirantis

[openstack-dev] [placement][nova] PTG summary

Hi Stackers, In Atlanta, there were a lot of discussions involving the new(ish) placement service. I'd like to summarize the topics of discussion and highlight what the team aims to get done in the Pike release. A quick refresher - The placement service's mission is to

Re: [openstack-dev] [deployment][TripleO][kolla][ansible][fuel] Next steps for cross project collaboration

On 02/27/2017 11:02 AM, Steven Hardy wrote: Hi all, Over the recent PTG, and previously at the design summit in Barcelona, we've had some productive cross-project discussions amongst the various deployment teams. It's clear that we share many common problems, such as patterns for major version

Re: [openstack-dev] [all] parsing libraries

On 02/20/2017 09:48 PM, Eric K wrote: Hi all, In the congress project, we¹re looking to replace the antlr3-based parser with a better maintained alternative. I see that pyparsing and Parsley are used in some projects, could anyone share their experience with them and potentially other parsing

Re: [openstack-dev] [nova] Call for upstream training liaison

On 02/21/2017 02:45 PM, Matt Riedemann wrote: If you haven't seen this yet [1] there is going to be an upstream training meeting at the PTG on Wednesday 2/22 at 12ET to talk about upstream training and what liaisons from each project can do to help. This email is a call for anyone that's

Re: [openstack-dev] [nova] RFC for Intel RDT/CAT Support in Nova for Virtual Machine QoS

Hi Eli, Sorry for top-posting. Just a quick note to say I had a good conversation on Monday about this with Sean Mooney. I think we have some ideas on how to model all of these resources in the new placement/resource providers schema. Are you at the PTG? If so, would be great to meet up to

Re: [openstack-dev] [nova] Device tagging: rebuild config drive upon instance reboot to refresh metadata on it

On 02/17/2017 07:05 PM, Clint Byrum wrote: Excerpts from Michael Still's message of 2017-02-18 09:41:03 +1100: We have had this discussion several times in the past for other reasons. The reality is that some people will never deploy the metadata API, so I feel like we need a better solution

Re: [openstack-dev] [nova] Device tagging: rebuild config drive upon instance reboot to refresh metadata on it

On 02/17/2017 02:28 PM, Artom Lifshitz wrote: Early on in the inception of device role tagging, it was decided that it's acceptable that the device metadata on the config drive lags behind the metadata API, as long as it eventually catches up, for example when the instance is rebooted and we get

Re: [openstack-dev] [stable/ocata] [nova] [devstack multi-node] nova-conductor complaining about "No cell mapping found for cell0"

On 02/20/2017 09:33 AM, Prashant Shetty wrote: Team, I have multi node devstack setup with single controller and multiple computes running stable/ocata. On compute: ENABLED_SERVICES=n-cpu,neutron,placement-api Both KVM and ESxi compute came up fine: vmware@cntr11:~$ nova hypervisor-list

Re: [openstack-dev] [nova] Will unshelving an offloaded instance respect the original AZ?

On 02/18/2017 01:46 PM, Matt Riedemann wrote: I haven't fully dug into testing this, but I got wondering about this question from reviewing a change [1] which would make the unshelve operation start to check the volume AZ compared to the instance AZ when the compute manager calls

Re: [openstack-dev] [all] Do we need service types at all?! (Re: [octavia][sdk] service name for octavia)

On 02/16/2017 08:14 AM, Dean Troyer wrote: On Thu, Feb 16, 2017 at 7:06 AM, Andrey Kurilin wrote: Yes, I forgot about it. But it changes nothing. Custom implementation of particular service should cover the same API as an official one. For me, as for user, it doesn't

Re: [openstack-dev] [neutron] Some findings while profiling instances boot

On 02/15/2017 12:46 PM, Daniel Alvarez Sanchez wrote: Hi there, We're trying to figure out why, sometimes, rpc_loop takes over 10 seconds to process an iteration when booting instances. So we deployed devstack on a 8GB, 4vCPU VM and did some profiling on the following command: nova boot

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

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. We are a dedicated team, how cares about the project. We

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

On 02/08/2017 03:36 PM, Kendall Nelson wrote: Hello All! So I am sure we've all seen it: people writing terminal commands into our project channels, misusing '/' commands, etc. But have any of you actually done it? If any of you cores, ptls or other upstanding members of our wonderful

Re: [openstack-dev] [Congress][olso][oslo.messaging] Dynamically Determine Rabbit Transport URL?

On 02/06/2017 04:09 PM, Aimee Ukasick wrote: Thanks, Clint, for your quick response. Questions inline. On 02/06/2017 01:32 PM, Clint Byrum wrote: Excerpts from Aimee Ukasick's message of 2017-02-06 12:57:28 -0600: Hi everyone - from the Congress standalone installation guide

Re: [Openstack-operators] [openstack-dev] Large Contributing OpenStack Operators working group?

and therefore give you the benefit of auto-recording and publishing the meeting minutes. However, I do understand it can sometimes be difficult to follow IRC conversations with lots of participants. Definitely has trade-offs. -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent

Re: [openstack-dev] [Openstack-operators] Large Contributing OpenStack Operators working group?

discussion. Best, -jay Regards -steve > -Original Message- From: Jay Pipes <jaypi...@gmail.com> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: Thursday, February 2, 2017 at 1:14 PM To: OpenStack

Re: [Openstack-operators] [User-committee] [openstack-dev] Large Contributing OpenStack Operators working group?

On 02/03/2017 01:16 PM, Jonathan Proulx wrote: On Fri, Feb 03, 2017 at 04:34:20PM +0100, lebre.adr...@free.fr wrote: :Hi, : :I don't know whether there is already a concrete/effective way to identify overlapping between WGs. :But if not, one way can be to arrange one general session in each

Re: [Openstack-operators] [openstack-dev] Large Contributing OpenStack Operators working group?

wrote my questions about the LCOO! > Here in the USA where I live, I find myself rather disgusted with politics right now. Let's move forward. You and me both, Andy. And I'm happy to move the conversation forward with you, constructively. Best, -jay -Andy > -Original Message- F

Re: [Openstack-operators] [openstack-dev] Large Contributing OpenStack Operators working group?

-Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: Thursday, February 2, 2017 5:23 PM To: Edgar Magana <edgar.mag...@workday.com>; openstack-operators@lists.openstack.org; user-commit...@lists.openstack.org Cc: MCCABE, JAMEY A <jm6...@att.com>; UKASICK,

Re: [Openstack-operators] [openstack-dev] Large Contributing OpenStack Operators working group?

to rephrase or elaborate on any questions. Happy to do so. I genuinely want to see alignment with other groups in this effort. Best, -jay Thanks, Edgar On 2/2/17, 12:14 PM, "Jay Pipes" <jaypi...@gmail.com> wrote: Hi, I was told about this group today. I have

[Openstack-operators] Large Contributing OpenStack Operators working group?

Hi, I was told about this group today. I have a few questions. Hopefully someone from this team can illuminate me with some answers. 1) What is the purpose of this group? The wiki states that the team "aims to define the use cases and identify and prioritise the requirements which are

[openstack-dev] Large Contributing OpenStack Operators working group?

Hi, I was told about this group today. I have a few questions. Hopefully someone from this team can illuminate me with some answers. 1) What is the purpose of this group? The wiki states that the team "aims to define the use cases and identify and prioritise the requirements which are

Re: [openstack-dev] [nova][ceilometer][postgresql][gate][telemetry] PostgreSQL gate failure (again)

On 02/02/2017 10:59 AM, Monty Taylor wrote: On 02/02/2017 09:33 AM, Mike Bayer wrote: On 02/01/2017 10:22 AM, Monty Taylor wrote: I personally continue to be of the opinion that without an explicit vocal and well-staffed champion, supporting postgres is more trouble than it is worth. The

Re: [openstack-dev] [nova] How to use resource_providers for shared disk resources (NFS)

On 01/30/2017 05:55 AM, Shewale, Bhagyashri wrote: Hi nova devs, How can I use placement api's if my instance path is mounted on shared storage server (e.g. NFS)? I am trying to set multinode setup with NFS shared storage for all nodes to share disk resources along with placement services. As

Re: [openstack-dev] [Nova] FFE Request "libvirt-emulator-threads-policy"

On 01/26/2017 11:51 AM, Sahid Orentino Ferdjaoui wrote: I'm requesting a FFE for the libvirt driver blueprint/spec to isolate emulator threads [1]. The code is up and ready since Mid of November 2016. [1]

Re: [openstack-dev] [nova] Latest and greatest on trying to get n-sch to require placement

On 01/26/2017 09:14 AM, Ed Leafe wrote: On Jan 26, 2017, at 7:50 AM, Sylvain Bauza wrote: That's where I think we have another problem, which is bigger than the corner case you mentioned above : when upgrading from Newton to Ocata, we said that all Newton computes have be

Re: [Openstack] ephemeral disks location

On 01/25/2017 03:19 AM, Eugen Block wrote: All these instances are in our ceph cluster. The instance path is defined in nova.conf: # Where instances are stored on disk (string value) instances_path = $state_path/instances If one compute node fails but it's able to initiate a migration, the

Re: [openstack-dev] [neutron] PTL candidacy

On 01/24/2017 06:42 PM, Sukhdev Kapur wrote: Ihar and Kevin, As our potential future PTLs, I would like to draw your attention to one of the critical issue regarding Neutron as "the" networking service in OpenStack. I keep hearing off and on that Neutron is not flexible to address many

Re: [openstack-dev] [Neutron] PTL Candidacy

On 01/22/2017 09:35 PM, Kevin Benton wrote: I would like to propose my candidacy for the Neutron PTL. I have been contributing to Neutron since the Havana development cycle working for a network vendor and then a distribution vendor. I have been a core reviewer since the Kilo development cycle

Re: [openstack-dev] [nova] [placement] [operators] Optional resource asking or not?

On 01/22/2017 04:40 PM, Sylvain Bauza wrote: Hey folks, tl;dr: should we GET /resource_providers for only the related resources that correspond to enabled filters ? No. Have administrators set the allocation ratios for the resources they do not care about exceeding capacity to a very high

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On 01/19/2017 12:59 PM, Eoghan Glynn wrote: I think Alex is suggesting something different than falling back to the legacy behaviour. The ocata scheduler would still roll forward to basing its node selection decisions on data provided by the placement API, but would be tolerant of the 3

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On 01/19/2017 01:18 PM, Alex Schultz wrote: On Thu, Jan 19, 2017 at 10:34 AM, Jay Pipes <jaypi...@gmail.com> wrote: On 01/19/2017 11:25 AM, Alex Schultz wrote: On Thu, Jan 19, 2017 at 8:27 AM, Matt Riedemann <mrie...@linux.vnet.ibm.com> wrote: Sylvain and I were talking about ho

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On 01/19/2017 11:25 AM, Alex Schultz wrote: On Thu, Jan 19, 2017 at 8:27 AM, Matt Riedemann wrote: Sylvain and I were talking about how he's going to work placement microversion requests into his filter scheduler patch [1]. He needs to make requests to the placement

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

On 01/16/2017 07:19 PM, Joshua Harlow wrote: Fox, Kevin M wrote: Your right, it is not what the big tent was about, but the big tent had some unintended side affects. The list, as you stated: * No longer having a formal incubation and graduation period/review for applying projects * Having a

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

On 01/17/2017 07:57 AM, Ian Cordasco wrote: On Mon, Jan 16, 2017 at 6:20 PM, Amrith Kumar wrote: Ian, This is a fascinating conversation. Let me offer two observations. First, Trove has long debated the ideal solution for storing secrets. There have been many

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

On 01/16/2017 04:09 PM, Fox, Kevin M wrote: If the developers that had issue with the lack of functionality, contributed to Barbican rather then go off on their own, the problem would have been solved much more quickly. The lack of sharing means the problems don't get fixed as fast. Agreed

Re: [openstack-dev] [nova] placement/resource providers update 7

On 01/11/2017 01:11 PM, Chris Dent wrote: On Fri, 6 Jan 2017, Chris Dent wrote: ## can_host, aggregates in filtering There's still some confusion (from at least me) on whether the can_host field is relevant when making queries to filter resource providers. Similarly, when requesting resource

Re: [openstack-dev] [nova] placement/resource providers update 7

On 01/09/2017 05:29 AM, Chris Dent wrote: On Fri, 6 Jan 2017, Chris Dent wrote: * CORS support in placement API: https://review.openstack.org/#/c/392891/ This is one we should probably get in in Ocata because it enables the sole piece of configurability that is present in the WSGI

Re: [Openstack] [nova] Accessing instance.flavor.projects fails due to orphaned Flavor

On 01/12/2017 05:31 AM, Balazs Gibizer wrote: Hi, The flavor field of the Instance object is a lazy-loaded field and the projects field of the Flavor object is also lazy-loaded. Now it seems to me that when the Instance object lazy loads instance.flavor then the created Flavor object is

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

On 01/06/2017 03:23 PM, Sam Yaple wrote: This should be read as MariaDB+Galera for replication. It is a highly-available database. Don't get me wrong. I love me some Galera. :) However, what the poster is really working towards is an implementation of the VCPE and eVCPE use cases for ETSI

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

On 01/05/2017 09:12 AM, Ronan-Alexandre Cherrueau 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 attempt to support multi-regions in Kolla and it raises

Re: [openstack-dev] [infra][devstack-gate][all]support multi-region gate environment

On 01/02/2017 09:06 PM, joehuang wrote: Hello, Currently only one region is supported in devstack-gate, there are lots of projects providing multi-region involved features, for example, heat multi-region, tacker multi-vim, shadow multi-cloud, tricircle networking across multi-region, kingbird

Re: [openstack-dev] [ironic] [nova] Ironic virt driver resources reporting

Great questions, Vlad. Comments inline. On 12/30/2016 11:40 AM, Vladyslav Drok wrote: Hi all! There is a long standing problem of resources reporting in ironic virt driver. That would be an understatement :) > It's described in a couple of bugs I've found - [0], [1]. Switching to placement

<    1   2   3   4   5   6   7   8   9   10   >