Re: [Openstack-operators] [Openstack-sigs] [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

+1 Yes please! -- Mathieu On Wed, Sep 26, 2018 at 2:56 PM Tim Bell wrote: > > > Doug, > > Thanks for raising this. I'd like to highlight the goal "Finish moving legacy > python-*client CLIs to python-openstackclient" from the etherpad and propose > this for a T/U series goal. > > To give it

Re: [Openstack-operators] dashboard show only project after upgrading

Try enabling DEBUG in local_settings.py. Some dashboard or panel might fail loading for some reasons. I had a similar behavior last week and enabling DEBUG should show the error. -- Mathieu On Mon, Jul 30, 2018 at 11:35 AM, Ignazio Cassano wrote: > Sorry, I sent a wrong image. > The correct

Re: [Openstack-operators] [openstack-dev] [nova][ironic] ironic_host_manager and baremetal scheduler options removal

On Wed, May 2, 2018 at 1:39 PM, Matt Riedemann wrote: > > I know you're just one case, but I don't know how many people are really > running the CachingScheduler with ironic either, so it might be rare. It > would be nice to get other operator input here, like I'm guessing

Re: [Openstack-operators] [openstack-dev] [nova][ironic] ironic_host_manager and baremetal scheduler options removal

On Wed, May 2, 2018 at 12:49 PM, Matt Riedemann <mriede...@gmail.com> wrote: > On 5/2/2018 11:40 AM, Mathieu Gagné wrote: >> >> What's the state of caching_scheduler which could still be using those >> configs? > > > The CachingScheduler has been dep

Re: [Openstack-operators] [openstack-dev] [nova][ironic] ironic_host_manager and baremetal scheduler options removal

What's the state of caching_scheduler which could still be using those configs? Mathieu On Wed, May 2, 2018 at 12:25 PM, Matt Riedemann wrote: > The baremetal scheduling options were deprecated in Pike [1] and the > ironic_host_manager was deprecated in Queens [2] and is

Re: [Openstack-operators] [openstack-dev] [nova] Default scheduler filters survey

Hi Dave, On Tue, May 1, 2018 at 4:30 AM, Dave Holland <d...@sanger.ac.uk> wrote: > On Mon, Apr 30, 2018 at 12:41:21PM -0400, Mathieu Gagné wrote: >> Weighers for baremetal cells: >> * ReservedHostForTenantWeigher [7] > ... >> [7] Used to favor reserved host over non-

Re: [Openstack-operators] [openstack-dev] [nova] Default scheduler filters survey

Hi, On Sun, Apr 29, 2018 at 5:29 PM, Ed Leafe wrote: > On Apr 29, 2018, at 1:34 PM, Artom Lifshitz wrote: >> >> Based on that, we can definitely say that SameHostFilter and >> DifferentHostFilter do *not* belong in the defaults. In fact, we got >> our

Re: [Openstack-operators] [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

On Mon, Jan 29, 2018 at 8:47 AM, Jay Pipes wrote: > > What I believe we can do is change the behaviour so that if a 0.0 value is > found in the nova.conf file on the nova-compute worker, then instead of > defaulting to 16.0, the resource tracker would first look to see if the

Re: [Openstack-operators] [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

Hi Jay, First, thank you very much for the followup. Response inline. On Mon, Jan 29, 2018 at 8:47 AM, Jay Pipes <jaypi...@gmail.com> wrote: > Greetings again, Mathieu, response inline... > > On 01/18/2018 07:24 PM, Mathieu Gagné wrote: >> >> So far, a couple chall

Re: [Openstack-operators] [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

On Thu, Jan 18, 2018 at 5:19 PM, Jay Pipes <jaypi...@gmail.com> wrote: > On 01/18/2018 03:54 PM, Mathieu Gagné wrote: >> >> Hi, >> >> On Tue, Jan 16, 2018 at 4:24 PM, melanie witt <melwi...@gmail.com> wrote: >>> >>> Hello

Re: [Openstack-operators] [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

Hi, On Tue, Jan 16, 2018 at 4:24 PM, melanie witt wrote: > Hello Stackers, > > This is a heads up to any of you using the AggregateCoreFilter, > AggregateRamFilter, and/or AggregateDiskFilter in the filter scheduler. > These filters have effectively allowed operators to set

Re: [Openstack-operators] [publiccloud] Improvement for Horizon performance

Thank you very much for sharing this information! I'm sure other operators and users will greatly benefit from it. (I sure will) -- Mathieu On Wed, Dec 20, 2017 at 4:09 PM, Fei Long Wang wrote: > Hi there, > > I think I should send this note more early given the

Re: [Openstack-operators] [openstack-dev] Upstream LTS Releases

On Tue, Nov 14, 2017 at 6:00 PM, Fox, Kevin M wrote: > The pressure for #2 comes from the inability to skip upgrades and the fact > that upgrades are hugely time consuming still. > > If you want to reduce the push for number #2 and help developers get their > wish of getting

Re: [Openstack-operators] [openstack-dev] [ironic] replace node "tags" with node "traits"

Hi, On Wed, Oct 25, 2017 at 10:17 AM, Loo, Ruby wrote: > Hello ironic'ers, > > A while ago, we approved a spec to add node tag support to ironic [1]. The > feature itself did not land yet (although some of the code has). Now that > the (nova) community has come up with

Re: [Openstack-operators] [openstack-dev] [nova] Should we make rebuild + new image on a volume-backed instance fail fast?

Why not supporting this use case? Same reason as before: A user might wish to keep its IP addresses. The use cannot do the following to bypass the limitation: 1) stop instance 2) detach root volume 3) delete root volume 4) create new volume 5) attach as root 6) boot instance Last time I tried,

Re: [Openstack-operators] Mitaka and gnocchi

On Fri, May 26, 2017 at 9:27 AM, wrote: > Thank you Gordon ! > > Now I'm encountering this kind of errors : > > *[​...]* > *​* > *2017-05-26 13:21:28.393 1404925 ERROR ceilometer.dispatcher.gnocchi [-] > Resource type instance does not exist (HTTP 404)* > *2017-05-26

Re: [Openstack-operators] [nova] Anyone using libvirt driver port filtering with neutron?

On Thu, Mar 23, 2017 at 10:08 AM, wrote: > The nova libvirt driver provides support for ebtables-based port > filtering (using libvirt's nwfilter) to prevent things like MAC, IP > and/or ARP spoofing. I've been looking into deprecating this as part of > the move to deprecate

Re: [Openstack-operators] HTTP/S Termination with Haproxy + Keystone

cated anyway (at least in heat), although I have not found any >> indication about what is supposed to 'replace' those options going forward. >> >> Ideas? >> >> Thanks so much, >> >> --- >> v/r >> >> Chris Apsey >> bitskr...@bitskrieg

Re: [Openstack-operators] Using novaclient, glanceclient, etc, from python

This change allows you to upload duplicate images: https://review.openstack.org/#/c/349710/ Use the allow_duplicates=True argument to bypass the name duplication check. -- Mathieu On Fri, Nov 25, 2016 at 3:15 PM, George Shuklin wrote: > Em... Sorry, I'm trying to

Re: [Openstack-operators] old Juno documentation

I find it to be an inconvenient. (for the one times I read the docs) To compare, I found that some projets (like the ones on readthedocs) often keep the previous versions so one can refer to it. You can easily see all the available versions and switch to the one you need. That's very convenient

Re: [Openstack-operators] Openstack team size vs's deployment size

On Fri, Sep 9, 2016 at 6:41 PM, Mathieu Gagné <mga...@calavera.ca> wrote: > On Wed, Sep 7, 2016 at 6:59 PM, Kris G. Lindgren <klindg...@godaddy.com> > wrote: >> >> I was hoping to poll other operators to see what their average team size >> vs’s deplo

Re: [Openstack-operators] Openstack team size vs's deployment size

On Wed, Sep 7, 2016 at 6:59 PM, Kris G. Lindgren wrote: > > I was hoping to poll other operators to see what their average team size > vs’s deployment size is, as I am trying to use this in an internal company > discussion. It is difficult to come up with numbers without

Re: [Openstack-operators] Update on Nova scheduler poor performance with Ironic

Hi Marc, Too sad we didn't see you at the OpenStack Ops meetup. =) On Wed, Aug 31, 2016 at 4:46 PM, Marc Heckmann wrote: > > I admit that we're having a hard time figuring out exactly which > scheduler filters rely on the option though. > I suspect the following

Re: [Openstack-operators] Update on Nova scheduler poor performance with Ironic

On Wed, Aug 31, 2016 at 1:33 AM, Joshua Harlow wrote: >> >> Enabling this option will make it so Nova scheduler loads instance >> info asynchronously at start up. Depending on the number of >> hypervisors and instances, it can take several minutes. (we are >> talking about

[Openstack-operators] Update on Nova scheduler poor performance with Ironic

Hi, For those that attended the OpenStack Ops meetup, you probably heard me complaining about a serious performance issue we had with Nova scheduler (Kilo) with Ironic. Thanks to Sean Dague and Matt Riedemann, we found the root cause. It was caused by this block of code [1] which is hitting the

Re: [Openstack-operators] [nova][scheduler] Specifying Qualitative requirements for a VM

On Tue, May 10, 2016 at 11:53 AM, Ed Leafe wrote: > Currently we load both quantitative (how much disk, RAM, etc) and qualitative > (SSD vs. spinning, special chipsets, etc.) into the flavor that a user can > request. As the number of qualitative features has been increasing,

Re: [Openstack-operators] Anyone else use vendordata_driver in nova.conf?

On Tue, May 3, 2016 at 5:51 PM, Fox, Kevin M wrote: > > I think I see at least one use case for minimum 2 hooks... > > Cloud provider wants to inject some stuff. > > Cloud tenant wants their own hook called to inject stuff to point to the > Config Management server in their

Re: [Openstack-operators] Setting affinity based on instance type

On 2016-03-03 12:50 PM, Silence Dogood wrote: > We did some early affinity work and discovered some interesting problems > with affinity and scheduling. =/ by default openstack used to ( may > still ) deploy nodes across hosts evenly. > > Personally, I think this is a bad approach. Most cloud

Re: [Openstack-operators] Setting affinity based on instance type

What would prevent the next user from having workloadB collocated with an other user's workloadA if that's the only capacity available? Unless aggregates are used, it will be hard to guaranty that workloadA and workloadB (from any users) are never collocated. You could probably play with custom

Re: [Openstack-operators] Live migration neutron issues

On 2016-01-07 3:28 PM, Adam Dibiase wrote: > Greetings, > > I am having connectivity issues to instances after live migrating > between compute nodes. Scenario is as follows: > > * Start pinging instance IP > * Send nova live-migration > * Once nova reports the pause/resume on the new

Re: [Openstack-operators] Service Catalog TNG urls

On 2015-12-16 11:11 AM, Anne Gentle wrote: > > Another use case I hadn't heard yet is if a public URL is DDoSed, you > can have a second URL on internal-only systems that can't be attacked > from the outside world. So it's a publicURL in that you can access the > service, but an internal-only URL

Re: [Openstack-operators] How do I install specific versions of openstack/puppet-keystone

On 2015-11-25 6:35 PM, Sam Morrison wrote: > Can you get R10k to NOT install dependencies listed in metadata etc.? > We use puppet-librarian and it can’t and so we have to change every > puppet module eg. [1] as some of the dependencies break things for us. > > Sam > > > [1] >

Re: [Openstack-operators] Confirm resize in Kilo with Cells

On 2015-11-21 4:47 PM, Belmiro Moreira wrote: > Hi, > We are about to upgrade nova to kilo using cells and we noticed > the resize/migrate functionality is not working properly. > > The instance is correctly resized/migrated but fails to > “confirm resize” with the following trace: > >

Re: [Openstack-operators] Informal Ops Meetup?

On 2015-10-29 4:39 PM, Kris G. Lindgren wrote: > > I am not sure if you guys have looked at the schedule for Friday… but > its all working groups. I was talking with a few other operators and > the idea came up around doing an informal ops meetup tomorrow. So I > wanted to float this idea by

Re: [Openstack-operators] [openstack-dev] [cinder] [all] The future of Cinder API v1

On 2015-09-28 11:43 PM, John Griffith wrote: > > > On Mon, Sep 28, 2015 at 6:19 PM, Mark Voelker > wrote: > > FWIW, the most popular client libraries in the last user survey[1] > other than OpenStack’s own clients were: libcloud (48

Re: [Openstack-operators] deprecation of allow_duplicate_networks

On 2015-09-25 1:07 AM, Sam Morrison wrote: > We are in the process of migrating to neutron and have come across this handy > config option that is sadly being deprecated. (seems to be a theme of mine > this week) > Does anyone know if this is supported in some other way? > > We have limited IP

Re: [Openstack-operators] Cinder Juno to Kilo upgrade and DB encodings

On 2015-09-17 4:06 AM, Arne Wiebalck wrote: > Hi, > > During our Cinder upgrade on CentOS7 from Juno to Kilo, we ran into this bug: > https://bugs.launchpad.net/cinder/+bug/1455726 > > As there is no fix available from what I see, what we came up with as a > “solution” > is to explicitly set

[Openstack-operators] Improving quality of multi-region support

Hi, This email is a follow-up on the discussion we are currently having in the LDT (Large Deployment Team) session at the OpenStack Ops Meetup. [1] We collectively identified a lack test coverage around multi-region support. A region being the concept found in Keystone catalog, not the

Re: [Openstack-operators] Allow user to see instances of other users

Kapłoński sla...@kaplonski.pl Dnia czwartek, 11 czerwca 2015 18:08:38 Mathieu Gagné pisze: You can add your new role to this policy: context_is_admin: role:admin or role:special_role, It will set is_admin to True in the context. I'm not sure of the side-effect to be honest. Use at your own

Re: [Openstack-operators] [openstack-operators][neutron]:stats on FIPs usage

On 2015-05-26 3:25 PM, Daniel Comnea wrote: Hi, Can anyone share their thoughts, answers to the below problem/ question which i'm sure everyone came across while looking after an Openstack environment: - As an admin how can you find out the usage of all FIPs available to be

Re: [Openstack-operators] User Survey - Deadline Apr 8

On 2015-03-25 11:35 PM, Tom Fifield wrote: The deadline to complete the survey and be part of the next report is April 8 at 23:00 UTC. Questions? Check out the FAQ [https://www.openstack.org/user-survey/faq] or contact me ;) Thanks for the reminder Tom. I'm currently updating my

[Openstack-operators] Packaging with fpm

Hi, I'm currently experimenting with fpm. I learned that fpm does not generate the files needed to upload your new package to an APT repository. Since the package type built by fpm is binary, that file would be the .changes control file. This bothers me a lot because my current workflow

Re: [Openstack-operators] Packaging with fpm

On 2015-03-04 12:18 PM, Clint Byrum wrote: Excerpts from Mathieu Gagné's message of 2015-03-04 08:31:45 -0800: I really like APT repositories and would like to continue using them for the time being. I'm impressed you took the time to setup dput! It's super simple to setup and use. Create

Re: [Openstack-operators] Packaging with fpm

On 2015-03-04 11:52 AM, matt wrote: I like cowbuilder... pbuilder using copy on write qcow's for the build environment. Most folks automating debian package creation use pbuilder. Thanks for sharing. I'm a bit more crazy, I use schroot and sbuild. =) -- Mathieu

Re: [Openstack-operators] Packaging with fpm

On 2015-03-04 1:10 PM, matt wrote: use a pgp signing key with pass phrase and sign the release / packages files. ubuntu already does this. You also need to sign the packages before uploading. You can sign the packages AND the repository. Both are done by different actors: uploader, repo

Re: [Openstack-operators] Packaging with fpm

On 2015-03-04 1:26 PM, matt wrote: and thus different keys. so what's the issue? fpm does not generate a .changes so you can't sign it. (for upload) And since there is no .changes, you can't use dput to upload your package to the APT repository using standard methods. Even if I don't plan

Re: [Openstack-operators] Packaging sample config versions

On 2015-01-28 6:30 PM, Tom Fifield wrote: On 29/01/15 07:28, Thomas Goirand wrote: On 01/27/2015 11:00 PM, Tom Fifield wrote: Hi all, Based on Gustavo's excellent work below, talking with many ops, and after a brief chats with Jeremey and a few other TC folks, here's what I'd propose as an

Re: [Openstack-operators] Specifying multiple tenants for aggregate_multitenancy_isolation_filter

On 2015-01-27 5:03 PM, Jesse Keating wrote: Which one do you think is better? What do the other various things that take lists expect? I'd say that's more of a consideration too, uniformity across the inputs. +1 again -- Mathieu ___

Re: [Openstack-operators] Specifying multiple tenants for aggregate_multitenancy_isolation_filter

On 2015-01-27 4:54 PM, Sam Morrison wrote: Hi operators, I have a review up to fix this filter to allow multiple tenants, there are 2 proposed ways in which this can be specified. 1. using a comma e.g., tenantid1,tenantid2 2. Using a json list eg. [“tenantid1”, “tenantid2”] Which one do you

Re: [Openstack-operators] Packaging sample config versions

On 2014-12-08 11:01 PM, Kris G. Lindgren wrote: I don’t think its too much to ask for each project to include a script that will build a venv that includes tox and the other relevant deps to build the sample configuration. This is already the case. Back then, I did the work of documenting

Re: [Openstack-operators] Operations project: Packaging

On 2014-11-19 4:25 PM, Kris G. Lindgren wrote: Sure. PBR when working off of a branch uses the git hash of the commit for the version of the package. So you will get a version name like openstack-nova-2014.1.2-{githash}, which is used by other tools to set the name of the package (such as

Re: [Openstack-operators] EtherPad from the Friday morning session?

On 2014-11-12 6:11 PM, Simon McCartney wrote: Does anybody have the URL for the EtherPad of notes from the Friday morning session on the white sofa? Did I also see Michael a few others start a project entry on wiki.openstack.org? I unfortunately didn't attend but I think this is the

Re: [Openstack-operators] Proposal for an 'Operations' project

On 2014-11-10 1:24 PM, matt wrote: My fear with the github is that people will just donate code in a fire and forget fashion... this will generate a poorly maintained repo in which finding useful actively maintained contributions may become difficult. So my concerns lie in ensuring that anyone

Re: [Openstack-operators] qemu 1.x to 2.0

On 2014-10-29 1:28 PM, Joe Topjian wrote: I had some more fun with this this morning. libvirt 1.2.2-0ubuntu13.1.6 became available in the Ubuntu cloud archive precise-updates repository. Installing it on compute nodes removed apparmor. When trying to restart an instance, libvirt complained

Re: [Openstack-operators] Nodes and configurations management in Puppet

On 2014-10-02 11:50 PM, Michael Dorman wrote: r10k deploys the Puppet environments (Œmaster¹ and Œprod¹ which correspond to git branches), heira data, and all the modules. Hiera data is in a separate (private) git repo, but there¹s only a master branch there. Are people maintaining the