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

Excerpts from Sean McGinnis's message of 2016-02-22 11:48:50 -0800: > On Mon, Feb 22, 2016 at 05:20:21PM +, Amrith Kumar wrote: > > Thierry and all of those who contributed to putting together this write-up, > > thank you very much. > > > > TL;DR: +0 > > > > Longer version: > > > > While I

Re: [openstack-dev] [nova] Update on scheduler and resource tracker progress

Excerpts from Jay Pipes's message of 2016-02-18 11:33:04 -0800: > On 02/12/2016 01:47 PM, Clint Byrum wrote: > > Excerpts from Jay Pipes's message of 2016-02-11 12:24:04 -0800: > >> Hello all, > >> > >> Performance working group, please pay atte

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

Excerpts from Cheng, Yingxin's message of 2016-02-14 21:21:28 -0800: > Hi, > > I've uploaded a prototype https://review.openstack.org/#/c/280047/ to testify > its design goals in accuracy, performance, reliability and compatibility > improvements. It will also be an Austin Summit Session if elec

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

Excerpts from Andrew Laski's message of 2016-02-16 06:34:53 -0800: > > On Tue, Feb 16, 2016, at 07:54 AM, Alex Xu wrote: > > > > > > 2016-02-16 19:53 GMT+08:00 Sean Dague : > >> On 02/12/2016 03:55 PM, Andrew Laski wrote: > >> > > Starting a new thread to continue a thought that came up in > >> >

Re: [openstack-dev] [nova] Update on scheduler and resource tracker progress

Excerpts from Jay Pipes's message of 2016-02-11 12:24:04 -0800: > Hello all, > > Performance working group, please pay attention to Chapter 2 in the > details section. > > Chapter 2 - Addressing performance and scale > > > One of the significant p

Re: [openstack-dev] [infra] [trove] gate jobs failing with ovh apt mirrors

Excerpts from Craig Vyvial's message of 2016-02-11 07:43:40 -0800: > Jeremy, > > Thanks for looking at this. That makes sense but I'm not sure how to > resolve this issue with the current diskimage-builder elements. If anyone > has ideas it would be greatly appreciated. > Any job using these ima

Re: [openstack-dev] [gate] RFC dropping largeops tests

Excerpts from Sean Dague's message of 2016-02-10 04:33:44 -0800: > The largeops tests at this point are mostly finding out that some of our > new cloud providers are slow - http://tinyurl.com/j5u4nf5 > > This is fundamentally a performance test, with timings having been tuned > to pass 98% of the

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

Excerpts from Thierry Carrez's message of 2016-02-10 08:35:19 -0800: > Chris Dent wrote: > > [...] > > Observing this thread and "the trouble with names"[1] one I get > > concerned that we're trending in the direction of expecting > > projects/servers/APIs to be done and perfect before they will ev

Re: [openstack-dev] [docs][all] Software design in openstack

Excerpts from Nick Yeates's message of 2016-02-03 21:18:08 -0800: > Josh, thanks for pointing this out and in being hospitable to an outsider. > > Oslo is definitely some of what I was looking for. As you stated, the fact > that there is an extensive review system with high participation, that th

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

Excerpts from Jiri Tomasek's message of 2016-01-25 06:09:33 -0800: > On 01/25/2016 12:42 AM, Clint Byrum wrote: > > Excerpts from Dan Prince's message of 2016-01-22 16:19:07 -0800: > >> On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: > >>> So I haven

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

Excerpts from Dan Prince's message of 2016-01-22 16:19:07 -0800: > On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: > > So I haven't weighed in on this yet, in part because I was on > > vacation > > when it was first proposed and missed a lot of the initial > > discussion, > > and also because I

Re: [openstack-dev] [glance][ironic][cinder][nova] 'tar' as an image disk_format

Excerpts from Brian Rosmaita's message of 2016-01-23 06:54:26 -0800: > Please provide feedback about a proposal to add 'tar' as a new Glance > disk_format.[0] > > The Ironic team is adding support for "OS tarball images" in Mitaka. This is > a compressed tar archive of a / (root filesystem). Th

Re: [openstack-dev] [all] Proposal: copyright-holders file in each project, or copyright holding forced to the OpenStack Foundation

Excerpts from Thomas Goirand's message of 2016-01-16 22:36:23 -0800: > On 01/16/2016 10:16 PM, Jeremy Stanley wrote: > > On 2016-01-16 12:14:20 +0800 (+0800), Thomas Goirand wrote: > > [...] > >> I've just asked this very point with the same example to the FTP > >> masters. Let's see what they say.

Re: [openstack-dev] Service password storage

Excerpts from Levin's message of 2016-01-11 02:37:09 -0800: > Dear openstack developers, > I installed openstack via devstack recently, and I found out that the > admin passwords for services like cinder and nova are stored in plain > text in their /etc/*/*.conf files. These files are rw--r--r-- by

Re: [openstack-dev] [heat] Client checking of server version

Excerpts from Jay Dobies's message of 2016-01-04 12:53:07 -0800: > I ran into an issue in a review about moving environment resolution from > client to server [1]. It revolves around clients being able to access > older versions of servers (that's a pretty simplistic description; see > [2] for t

Re: [openstack-dev] How to add feature to diskimage-builder

Excerpts from George Shuklin's message of 2015-12-29 09:16:52 -0800: > Hello. > > I'm trying add a small feature to one of the elements in > diskimage-builder (https://github.com/openstack/diskimage-builder/pull/10/) > > I have experience with gerrit and openstack bugfix workflow, but I have >

Re: [openstack-dev] Nova scheduler startup when database is not available

Excerpts from Jay Pipes's message of 2015-12-28 09:45:39 -0800: > On 12/24/2015 02:30 PM, Clint Byrum wrote: > > This is entirely philosophical, but we should think about when it is > > appropriate to adopt which mode of operation. > > > > There are basically two

Re: [openstack-dev] Nova scheduler startup when database is not available

Excerpts from Jay Pipes's message of 2015-12-23 10:32:27 -0800: > On 12/23/2015 12:27 PM, Lars Kellogg-Stedman wrote: > > I've been looking into the startup constraints involved when launching > > Nova services with systemd using Type=notify (which causes systemd to > > wait for an explicit notific

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

Excerpts from Dougal Matthews's message of 2015-12-22 07:36:02 -0800: > Hi all, > > This topic came up in the 2015-12-15 meeting[1], and again briefly today. > After working with the code that came out of the deployment library spec[2] > I > had some concerns with how we are storing the templates.

Re: [openstack-dev] [openstack][magnum][heat] Quota for Magnum Resources

M, Lee Calcote > >> wrote: > >> > >> Food for thought - there is a cost to FIPs (in the case of public IP > >> addresses), security groups (to a lesser extent, but in terms of the > >> computation of many hundreds of them), etc. Administrators may wish to

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

Excerpts from Adrian Otto's message of 2015-12-16 16:56:39 -0800: > Clint, > > I think you are categorically dismissing a very real ops challenge of how to > set correct system limits, and how to adjust them in a running system. I have > been stung by this challenge repeatedly over the years. As

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

Excerpts from Fox, Kevin M's message of 2015-12-16 16:05:29 -0800: > Yeah, as an op, I've run into a few things that need quota's that just have > basically hardcoded values. heat stacks for example. its a single global in > /etc/heat/heat.conf:max_stacks_per_tenant=100. Instead of being able to

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

Excerpts from Adrian Otto's message of 2015-12-16 12:35:10 -0800: > Clint, > > > On Dec 16, 2015, at 11:56 AM, Tim Bell wrote: > > > >> -Original Message- > >> From: Clint Byrum [mailto:cl...@fewbar.com] > >> Sent: 15 December 2

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

Excerpts from Fox, Kevin M's message of 2015-12-16 12:19:59 -0800: > keypairs are real though. they consume database resource at the moment. You > don't want a user blowing out your db. Quota's should be for things that ops > will get sad over, if the users consume too many of them. > Limit ev

Re: [openstack-dev] [ironic][neutron][keystone] how to reauth the token

Excerpts from Pavlo Shchelokovskyy's message of 2015-12-16 07:59:42 -0800: > Hi all, > > I'd like to start discussion on how Ironic is using Neutron when Keystone > is involved. > > Recently the patch [0] was merged in Ironic to fix a bug when the token > with which to create the neutronclient is

Re: [openstack-dev] [Ironic] [Nova] continuing the "multiple compute host" discussion

Excerpts from Jim Rollenhagen's message of 2015-12-16 08:03:22 -0800: > Nobody is talking about running a compute per flavor or capability. All > compute hosts will be able to handle all ironic nodes. We *do* still > need to figure out how to handle availability zones or host aggregates, > but I ex

Re: [openstack-dev] [Ironic] [Nova] continuing the "multiple compute host" discussion

Excerpts from James Penick's message of 2015-12-15 17:19:19 -0800: > > getting rid of the raciness of ClusteredComputeManager in my > >current deployment. And I'm willing to help other operators do the same. > > You do alleviate race, but at the cost of complexity and > unpredictability. Breakin

Re: [openstack-dev] [Heat] Status of the Support Conditionals in Heat templates

Excerpts from Fox, Kevin M's message of 2015-12-15 17:21:13 -0800: > the one thing as an Op I'd like to see avoided is having the template > language be Turing complete. When I'm provisioning heat-engines its much > easier if you know how many you need when the user can't force them to spin > i

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

Hi! Can I offer a counter point? Quotas are for _real_ resources. Memory, CPU, disk, bandwidth. These are all _closely_ tied to things that cost real money and cannot be conjured from thin air. As such, the user being able to allocate 1 billion or 2 containers is not limited by Magnum, but by rea

Re: [openstack-dev] [Heat] Status of the Support Conditionals in Heat templates

Excerpts from Fox, Kevin M's message of 2015-12-15 09:07:02 -0800: > My $0.02: > > heat as it is today, requires all users to be devops, and to carefully craft > the templates launched specific to the cloud and the particular app they are > trying to write. Making sharing code between heat users

Re: [openstack-dev] [mistral] bugfix for "Fix concurrency issues by using READ_COMMITTED" unveils / creates a different bug

Excerpts from ELISHA, Moshe (Moshe)'s message of 2015-12-07 08:29:44 -0800: > Hi all, > > The current bugfix I am working on[1] have unveiled / created a bug. > Test "WorkflowResumeTest.test_resume_different_task_states" sometimes fails > because "task4" is executed twice instead of once (See uni

Re: [openstack-dev] Reg: Blueprint -- add-compute-node-on-the-go

Excerpts from Atul Ag's message of 2015-12-10 06:50:05 -0800: > Hi, > > I have added the blue print > https://blueprints.launchpad.net/nova/+spec/add-compute-node-on-the-go. > Can you please let me know the feasibility, and accept the blueprint. > Hi Atul, welcome, and thanks for your interes

Re: [openstack-dev] [TripleO][DIB] diskimage-builder and python 2/3 compatibility

Excerpts from Gregory Haynes's message of 2015-12-09 12:49:07 -0800: > Excerpts from Ian Wienand's message of 2015-12-09 09:35:15 +: > > On 12/09/2015 07:15 AM, Gregory Haynes wrote: > > > We ran in to a couple issues adding Fedora 23 support to > > > diskimage-builder caused by python2 not bei

Re: [openstack-dev] [glance] Auth_version from 'old style' URLs in the database

Excerpts from Flavio Percoco's message of 2015-12-04 07:00:53 -0800: > On 03/12/15 16:24 +, Bunting, Niall wrote: > >Hi, > > > >Currently glance will use an auth_url if in the database. Eg. > >10.0.0.8:5000/v2.0 > > > >However glance currently takes the auth_version from the config > >files. T

Re: [openstack-dev] [Performance][Proposal] Moving IRC meeting from 15:00 UTC to 16:00 UTC

Excerpts from Dina Belova's message of 2015-12-04 01:46:06 -0800: > Dear performance folks, > > There is a suggestion to move our meeting time from 15:00 UTC (Tuesdays > ) to > 16:00 UTC (also Tuesdays >

Re: [openstack-dev] [heat][tripleo] User Initiated Rollback

Zane I want to echo your sentiments exactly below. I agree with all of the things basically. The only thing I'd add is that no matter how good you make Heat's rollback API, it will never be as good as git. So I would suggest that you just have people roll forward from Heat's perspective, and let V

Re: [openstack-dev] [Openstack-operators] [nova] [openstack-operators] Tools to move instances between projects?

Excerpts from Kris G. Lindgren's message of 2015-12-02 15:43:13 -0800: > I can describe our specific uses cases, not sure our same limitations apply > to everyone. > > Every developer in our company has a project created for them (user-username) > they are allowed to spinup 5 vm's in this projec

Re: [openstack-dev] [nova] [openstack-operators] Tools to move instances between projects?

Excerpts from Kris G. Lindgren's message of 2015-12-02 12:52:10 -0800: > Hello, > > I was wondering if someone has a set of tools/code to work allow admins to > move vm's from one tenant to another? We get asked this fairly frequently in > our internal cloud (atleast once a week, more when we s

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

Excerpts from Joshua Harlow's message of 2015-12-01 09:28:18 -0800: > Sean Dague wrote: > > On 12/01/2015 08:08 AM, Duncan Thomas wrote: > >> > >> On 1 December 2015 at 13:40, Sean Dague >> > wrote: > >> > >> > >> The current approach means locks block on their own, are

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

Excerpts from Ben Nemec's message of 2015-11-30 13:22:23 -0800: > On 11/30/2015 02:15 PM, Sean Dague wrote: > > On 11/30/2015 03:01 PM, Robert Collins wrote: > >> On 1 December 2015 at 08:37, Ben Nemec wrote: > >>> On 11/30/2015 12:42 PM, Joshua Harlow wrote: > Hi all, > > I just wa

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

Excerpts from Joshua Harlow's message of 2015-11-30 10:42:53 -0800: > Hi all, > > I just wanted to bring up an issue, possible solution and get feedback > on it from folks because it seems to be an on-going problem that shows > up not when an application is initially deployed but as on-going >

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

Excerpts from Adam Young's message of 2015-11-23 20:21:47 -0800: > On 11/23/2015 11:42 AM, Morgan Fainberg wrote: > > Hi everyone, > > > > This email is being written in the context of Keystone more than any > > other project but I strongly believe that other projects could benefit > > from a sim

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

Excerpts from Brad Topol's message of 2015-11-23 13:38:34 -0800: > So to avoid the perception of a single company owning a piece of code, at > IBM our policy for major projects like Cinder, Nova and currently many > parts of Keystone (except pycadf) is to make sure we do not do the > following for

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

Excerpts from David Chadwick's message of 2015-11-23 13:20:56 -0800: > Since the ultimate arbiter is the PTL, then it would be wrong to allow > members of the same organisation as the PTL to perform all three code > functions without the input of anyone from any other organisation. This > places to

Re: [openstack-dev] [nova] FKs in the DB

Excerpts from Mike Bayer's message of 2015-11-22 11:59:06 -0800: > > On 11/20/2015 04:33 PM, Clint Byrum wrote: > > Excerpts from Mike Bayer's message of 2015-11-20 11:29:31 -0800: > >> > >> On 11/20/2015 11:19 AM, Alexis Lee wrote: > >>> We ju

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

Excerpts from Thierry Carrez's message of 2015-11-23 09:17:06 -0800: > Morgan Fainberg wrote: > > [...] > > With all that said, here is the proposal I would like to set forth: > > > > 1. Code reviews still need 2x Core Reviewers (no change) > > 2. Code can be developed by a member of the same comp

Re: [openstack-dev] [nova] FKs in the DB

Excerpts from Matt Riedemann's message of 2015-11-20 10:58:55 -0800: > > On 11/20/2015 10:19 AM, Alexis Lee wrote: > > We just had a fun discussion in IRC about whether foreign keys are evil. > > Initially I thought this was crazy but mordred made some good points. To > > paraphrase, that if you h

Re: [openstack-dev] [nova] FKs in the DB

Excerpts from Mike Bayer's message of 2015-11-20 11:29:31 -0800: > > On 11/20/2015 11:19 AM, Alexis Lee wrote: > > We just had a fun discussion in IRC about whether foreign keys are evil. > > Initially I thought this was crazy but mordred made some good points. To > > paraphrase, that if you have

Re: [openstack-dev] OpenStack-Announce List

Excerpts from Tom Fifield's message of 2015-11-19 20:00:20 -0800: > Hi all, > > I'd like to get your thoughts about the OpenStack-Announce list. > > We describe the list as: > > """ > Subscribe to this list to receive important announcements from the > OpenStack Release Team and OpenStack Secur

Re: [openstack-dev] [oslo] [nova] default-next-release opt flag

Excerpts from Alexis Lee's message of 2015-11-17 09:28:31 -0800: > Often in Nova we introduce an option defaulted off (so as not to break > people) but then we want to make it default in the next release. > > Someone suggested an opt flag to mark this but I don't know what impact > they wanted it

Re: [openstack-dev] [All] Use of self signed certs in endpoints

Excerpts from Xav Paice's message of 2015-11-15 11:45:55 -0800: > After having a brief discussion this morning (NZ time) on the > #python-requests irc, it seems that using the system CA bundle is a "Not a > chance" situation. They've tried, and found it unmaintainable due to the > vast variations

Re: [openstack-dev] Help with getting keystone to migrate to Debian testing: fixing repoze.what and friends

Excerpts from Jamie Lennox's message of 2015-11-12 15:28:06 -0800: > On 12 November 2015 at 15:09, Clint Byrum wrote: > > > Excerpts from Clint Byrum's message of 2015-11-11 10:57:26 -0800: > > > Excerpts from Morgan Fainberg's message of 2015-11-10 20:17:12

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

Excerpts from Renat Akhmerov's message of 2015-11-12 07:52:42 -0800: > > > On 12 Nov 2015, at 00:11, Clint Byrum wrote: > > > > Excerpts from Zane Bitter's message of 2015-11-11 09:43:43 -0800: > >> 1. Keystone (or some Rabbit->Zaqar proxy servic

Re: [openstack-dev] Help with getting keystone to migrate to Debian testing: fixing repoze.what and friends

Excerpts from Clint Byrum's message of 2015-11-11 10:57:26 -0800: > Excerpts from Morgan Fainberg's message of 2015-11-10 20:17:12 -0800: > > On Nov 10, 2015 16:48, "Clint Byrum" wrote: > > > > > > Excerpts from Morgan Fainberg's message of 201

Re: [openstack-dev] Help with getting keystone to migrate to Debian testing: fixing repoze.what and friends

Excerpts from Morgan Fainberg's message of 2015-11-10 20:17:12 -0800: > On Nov 10, 2015 16:48, "Clint Byrum" wrote: > > > > Excerpts from Morgan Fainberg's message of 2015-11-10 15:31:16 -0800: > > > On Tue, Nov 10, 2015 at 3:20 PM, T

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

Excerpts from Zane Bitter's message of 2015-11-11 09:43:43 -0800: > 1. Keystone (or some Rabbit->Zaqar proxy service reading notifications > from Keystone) sends "new federated user" notification out via Zaqar. > 2. Mistral picks up the message and checks policy to see what should be > done. > 3.

Re: [openstack-dev] [nova][cinder] About rebuilding volume-backed instances.

Excerpts from Murray, Paul (HP Cloud)'s message of 2015-11-11 09:01:16 -0800: > > Unfortunately, you're trying to work around misuse of the cloud API's, not > > missing features from them. Don't use those volume types, and don't build > > systems that rely on single ports and interfaces. IMO rebuil

Re: [openstack-dev] [nova][cinder] About rebuilding volume-backed instances.

disk. Boot a new instance, initialize the configuration using your tools, and then move the volume attachment from the old to the new. *DO* build systems that use DNS or a VIP to communicate so that new ports can be allocated and attached to the new instance while the old one is stil active. > On

Re: [openstack-dev] Help with getting keystone to migrate to Debian testing: fixing repoze.what and friends

Excerpts from Morgan Fainberg's message of 2015-11-10 15:31:16 -0800: > On Tue, Nov 10, 2015 at 3:20 PM, Thomas Goirand wrote: > > > Hi there! > > > > All of Liberty would be migrating from Sid to Testing (which is the > > pre-condition for an upload to offical Debian backports) if I didn't > > h

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

cts, and so it may be at > > sites already. being able to support it may be less of a burden to > > operators then zk in some cases. > > > > If your cloud grows to the point where the dlm choice really matters for > > scalability/correctness, then you probably have

Re: [openstack-dev] [keystone] [Mistral] Autoprovisioning, per-user projects, and Federation

Excerpts from Richard Raseley's message of 2015-11-09 10:34:26 -0800: > From this operator’s perspective this is exactly the element of community > culture that, by encouraging the proliferation of projects and tools, is > making the OpenStack landscape more complex and less > {user,operator,arc

Re: [openstack-dev] [nova][cinder] About rebuilding volume-backed instances.

Excerpts from Zhenyu Zheng's message of 2015-11-08 23:04:59 -0800: > Hi All, > > Currently, we have strong demands about "rebuilding"(or actions like > rebuilding) volume-backed instances. As in production deployment, volume > backed instance is widely used. Users have the demands of performing th

Re: [openstack-dev] [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

Excerpts from Joshua Harlow's message of 2015-11-06 11:11:02 -0800: > Clint Byrum wrote: > > Excerpts from Doug Hellmann's message of 2015-11-06 10:28:41 -0800: > >> Excerpts from Clint Byrum's message of 2015-11-06 10:12:21 -0800: > >>> Excerpts fr

Re: [openstack-dev] [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

Excerpts from Doug Hellmann's message of 2015-11-06 10:28:41 -0800: > Excerpts from Clint Byrum's message of 2015-11-06 10:12:21 -0800: > > Excerpts from Dan Smith's message of 2015-11-06 09:37:44 -0800: > > > > Worth mentioning that OpenStack releases that come out at the same time > > > > as Ubun

Re: [openstack-dev] [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

Excerpts from Erik McCormick's message of 2015-11-06 09:36:44 -0800: > On Fri, Nov 6, 2015 at 12:28 PM, Mark Baker wrote: > > Worth mentioning that OpenStack releases that come out at the same time as > > Ubuntu LTS releases (12.04 + Essex, 14.04 + Icehouse, 16.04 + Mitaka) are > > supported for 5

Re: [openstack-dev] [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

Excerpts from Dan Smith's message of 2015-11-06 09:37:44 -0800: > > Worth mentioning that OpenStack releases that come out at the same time > > as Ubuntu LTS releases (12.04 + Essex, 14.04 + Icehouse, 16.04 + Mitaka) > > are supported for 5 years by Canonical so are already kind of an LTS. > > Supp

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

Excerpts from Tony Breeds's message of 2015-11-05 22:08:59 -0800: > Hello all, > I came across [1] which is notionally an ironic bug in that horizon > presents > VM operations (like suspend) to users. Clearly these options don't make sense > to ironic which can be confusing. > > There is a h

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

Excerpts from Fox, Kevin M's message of 2015-11-05 13:18:13 -0800: > Your assuming there are only 2 choices, > zk or db+rabbit. I'm claiming both hare suboptimal at present. a 3rd might > be needed. Though even with its flaws, the db+rabbit choice has a few > benefits too. > Well, I'm assuming

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

Excerpts from Fox, Kevin M's message of 2015-11-04 14:32:42 -0800: > To clarify that statement a little more, > > Speaking only for myself as an op, I don't want to support yet one more > snowflake in a sea of snowflakes, that works differently then all the rest, > without a very good reason. >

Re: [openstack-dev] [Spam] Re: [all] Outcome of distributed lock manager discussion @ the summit

Excerpts from Chris Dent's message of 2015-11-05 00:08:16 -0800: > On Thu, 5 Nov 2015, Robert Collins wrote: > > > In the session we were told that zookeeper is already used in CI jobs > > for ceilometer (was this wrong?) and thats why we figured it made a > > sane default for devstack. > > For c

Re: [openstack-dev] [keystone] [Mistral] Autoprovisioning, per-user projects, and Federation

Excerpts from Doug Hellmann's message of 2015-11-05 09:51:41 -0800: > Excerpts from Adam Young's message of 2015-11-05 12:34:12 -0500: > > Can people help me work through the right set of tools for this use case > > (has come up from several Operators) and map out a plan to implement it: > > > >

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

Excerpts from Joshua Harlow's message of 2015-11-04 12:57:53 -0800: > Ed Leafe wrote: > > On Nov 3, 2015, at 6:45 AM, Davanum Srinivas wrote: > >> Here's a Devstack review for zookeeper in support of this initiative: > >> > >> https://review.openstack.org/241040 > >> > >> Thanks, > >> Dims > > > >

Re: [openstack-dev] [all][api][tc][perfromance] API for getting only status of resources

Excerpts from Boris Pavlovic's message of 2015-11-03 17:32:43 -0800: > Clint, Morgan, > > I totally agree that the pub/sub model is better approach. > > However, there are 2 great things about polling: > 1) it's simpler to use than pub/sub (especially in shell) I envision something like this:

Re: [openstack-dev] [all][api][tc][perfromance] API for getting only status of resources

Excerpts from John Griffith's message of 2015-11-03 21:45:12 -0800: > On Tue, Nov 3, 2015 at 3:20 PM, Boris Pavlovic wrote: > > > Hi stackers, > > > > Usually such projects like Heat, Tempest, Rally, Scalar, and other tool > > that works with OpenStack are working with resources (e.g. VM, Volumes

Re: [openstack-dev] [all][api][tc][perfromance] API for getting only status of resources

Excerpts from Boris Pavlovic's message of 2015-11-03 14:20:10 -0800: > Hi stackers, > > Usually such projects like Heat, Tempest, Rally, Scalar, and other tool > that works with OpenStack are working with resources (e.g. VM, Volumes, > Images, ..) in the next way: > > >>> resource = api.resouce_d

Re: [openstack-dev] [tripleO] appropriate location for docker image uploading

Excerpts from Jeff Peeler's message of 2015-11-03 11:54:24 -0800: > I'm looking at introducing the ability for tripleoclient to upload > docker images into a docker registry (planning for it to be installed > in the undercloud [1]). I wanted to make sure something like this > would be accepted or g

Re: [openstack-dev] [TripleO] Proposing Ian Wienand as core reviewer on diskimage-builder

Excerpts from Gregory Haynes's message of 2015-11-03 07:25:27 -0800: > Hello everyone, > > I would like to propose adding Ian Wienand as a core reviewer on the > diskimage-builder project. Ian has been making a significant number of > contributions for some time to the project, and has been a grea

Re: [openstack-dev] [cross-project] Admin

Excerpts from Adam Young's message of 2015-10-19 22:53:14 +0900: > While I tend to play up bug 968696 for dramatic effect, the reality is > we have a logical contradiction on what we mean by 'admin' when talking > about RBAC. > > In early iterations of OpenStack, roles were global. This is ref

Re: [openstack-dev] Custom Nova scheduler based on CPU queue length

Excerpts from Rahul Nair's message of 2015-10-20 18:53:09 -0700: > ​Hi All, > > I am fairly new to the OpenStack community and is trying to create a custom > scheduler for Nova. A scheduler based on CPU queue length. Kindly apologize > if there are any inaccuracies in my statements. > > As I unde

Re: [openstack-dev] Scheduler proposal

Excerpts from Ed Leafe's message of 2015-10-15 11:56:24 -0700: > Wow, I seem to have unleashed a bunch of pent-up frustration in the > community! It's great to see everyone coming forward with their ideas and > insights for improving the way Nova (and, by extension, all of OpenStack) can > poten

Re: [openstack-dev] Scheduler proposal

Excerpts from Ian Wells's message of 2015-10-13 09:24:42 -0700: > On 12 October 2015 at 21:18, Clint Byrum wrote: > > > We _would_ keep a local cache of the information in the schedulers. The > > centralized copy of it is to free the schedulers from the complexity of >

Re: [openstack-dev] Scheduler proposal

Excerpts from Dulko, Michal's message of 2015-10-13 03:49:44 -0700: > On Mon, 2015-10-12 at 10:13 -0700, Clint Byrum wrote: > > Zookeeper sits in a very different space from Cassandra. I have had good > > success with it on OpenJDK as well. > > > > That said,

Re: [openstack-dev] Scheduler proposal

Excerpts from Jeremy Stanley's message of 2015-10-13 06:13:32 -0700: > On 2015-10-12 20:49:44 -0700 (-0700), Joshua Harlow wrote: > > Does the openstack foundation have access to a scaling area that > > can be used by the community for this kind of experimental work? > > The OpenStack Foundation h

Re: [openstack-dev] Scheduler proposal

Excerpts from Ian Wells's message of 2015-10-12 19:43:48 -0700: > On 11 October 2015 at 00:23, Clint Byrum wrote: > > > I'm in, except I think this gets simpler with an intermediary service > > like ZK/Consul to keep track of this 1GB of data and replace the nee

Re: [openstack-dev] Scheduler proposal

Excerpts from Boris Pavlovic's message of 2015-10-11 01:14:08 -0700: > Clint, > > There are many PROS and CONS in both of approaches. > > Reinventing wheel (in this case it's quite simple task) and it gives more > flexibility and doesn't require > usage of ZK/Consul (which will simplify integrati

Re: [openstack-dev] Scheduler proposal

Excerpts from Joshua Harlow's message of 2015-10-12 08:35:20 -0700: > Thierry Carrez wrote: > > Clint Byrum wrote: > >> Excerpts from Joshua Harlow's message of 2015-10-10 17:43:40 -0700: > >>> I'm curious is there any more detail about #1 below anywher

Re: [openstack-dev] Scheduler proposal

Excerpts from Thomas Goirand's message of 2015-10-12 05:57:26 -0700: > On 10/11/2015 02:53 AM, Davanum Srinivas wrote: > > Thomas, > > > > i am curious as well. AFAIK, cassandra works well with OpenJDK. Can you > > please elaborate what you concerns are for #1? > > > > Thanks, > > Dims > > s/wor

Re: [openstack-dev] Scheduler proposal

Excerpts from Boris Pavlovic's message of 2015-10-11 00:02:39 -0700: > 2Everybody, > > Just curios why we need such complexity. > > > Let's take a look from other side: > 1) Information about all hosts (even in case of 100k hosts) will be less > then 1 GB > 2) Usually servers that runs scheduler

Re: [openstack-dev] Scheduler proposal

Excerpts from Joshua Harlow's message of 2015-10-10 17:43:40 -0700: > I'm curious is there any more detail about #1 below anywhere online? > > Does cassandra use some features of the JVM that the openJDK version > doesn't support? Something else? > This about sums it up: https://github.com/apa

Re: [openstack-dev] Scheduler proposal

Excerpts from Ian Wells's message of 2015-10-09 19:14:17 -0700: > On 9 October 2015 at 18:29, Clint Byrum wrote: > > > Instead of having the scheduler do all of the compute node inspection > > and querying though, you have the nodes push their stats into something >

Re: [openstack-dev] Scheduler proposal

Excerpts from Alec Hothan (ahothan)'s message of 2015-10-09 21:19:14 -0700: > > On 10/9/15, 6:29 PM, "Clint Byrum" wrote: > > >Excerpts from Chris Friesen's message of 2015-10-09 17:33:38 -0700: > >> On 10/09/2015 03:36 PM, Ian Wells wrote: >

Re: [openstack-dev] Scheduler proposal

Excerpts from Chris Friesen's message of 2015-10-09 23:16:43 -0700: > On 10/09/2015 07:29 PM, Clint Byrum wrote: > > > Even if you figured out how to make the in-memory scheduler crazy fast, > > There's still value in concurrency for other reasons. No matter how >

Re: [openstack-dev] Scheduler proposal

Excerpts from Chris Friesen's message of 2015-10-09 17:33:38 -0700: > On 10/09/2015 03:36 PM, Ian Wells wrote: > > On 9 October 2015 at 12:50, Chris Friesen > > wrote: > > > > Has anybody looked at why 1 instance is too slow and what it would take > > to >

Re: [openstack-dev] [all] service catalog: TNG

Excerpts from Sean Dague's message of 2015-10-09 14:00:40 -0700: > On 10/09/2015 02:52 PM, Jonathan D. Proulx wrote: > > On Fri, Oct 09, 2015 at 02:17:26PM -0400, Monty Taylor wrote: > > :On 10/09/2015 01:39 PM, David Stanek wrote: > > :> > > :>On Fri, Oct 9, 2015 at 1:28 PM, Jonathan D. Proulx >

Re: [openstack-dev] Scheduler proposal

Excerpts from Chris Friesen's message of 2015-10-09 10:54:36 -0700: > On 10/09/2015 11:09 AM, Zane Bitter wrote: > > > The optimal way to do this would be a weighted random selection, where the > > probability of any given host being selected is proportional to its > > weighting. > > (Obviously t

Re: [openstack-dev] [Openstack-operators] Scheduler proposal

Excerpts from Chris Friesen's message of 2015-10-08 23:52:41 -0700: > On 10/08/2015 01:37 AM, Clint Byrum wrote: > > Excerpts from Maish Saidel-Keesing's message of 2015-10-08 00:14:55 -0700: > >> Forgive the top-post. > >> > >> Cross-posting to

Re: [openstack-dev] [all] service catalog: TNG

Excerpts from Adam Young's message of 2015-10-09 09:51:55 -0700: > On 10/09/2015 12:28 PM, Monty Taylor wrote: > > On 10/09/2015 11:21 AM, Shamail wrote: > >> > >> > >>> On Oct 9, 2015, at 10:39 AM, Sean Dague wrote: > >>> > >>> It looks like some great conversation got going on the service catalo

Re: [openstack-dev] Scheduler proposal

Excerpts from Joshua Harlow's message of 2015-10-08 08:38:57 -0700: > Joshua Harlow wrote: > > On Thu, 8 Oct 2015 10:43:01 -0400 > > Monty Taylor wrote: > > > >> On 10/08/2015 09:01 AM, Thierry Carrez wrote: > >>> Maish Saidel-Keesing wrote: > Operational overhead has a cost - maintaining 3 d

Re: [openstack-dev] [Openstack-operators] Scheduler proposal

Excerpts from Maish Saidel-Keesing's message of 2015-10-08 00:14:55 -0700: > Forgive the top-post. > > Cross-posting to openstack-operators for their feedback as well. > > Ed the work seems very promising, and I am interested to see how this > evolves. > > With my operator hat on I have one pie

Re: [openstack-dev] Scheduler proposal

Excerpts from Zane Bitter's message of 2015-10-07 12:28:36 -0700: > On 07/10/15 13:36, Ed Leafe wrote: > > Several months ago I proposed an experiment [0] to see if switching the > > data model for the Nova scheduler to use Cassandra as the backend would be > > a significant improvement as oppose

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