[openstack-dev] [nova] Server Group API: add 'action' to authorizer?

Hi Folks, Would anyone be opposed to adding the 'action' checking to the v2/v3 authorizers? This would allow administrators more fine-grained control over who can read vs. create/update/delete server groups. Thoughts? If folks are supportive, I'd be happy to add this... but not sure if we'd tr

[openstack-dev] [nova] Server Groups - remove VM from group?

Hello, Is our long-term vision to allow a VMs to be dynamically added/removed from a group? That is, unless I'm overlooking something, it appears that you can only add a VM to a server group at VM boot time and effectively remove it by deleting the VM? Just curious if this was a design point, or

Re: [openstack-dev] [nova] Server Groups - remove VM from group?

onger want this VM to have an anti-affinity policy relative to the others, etc.). - Joe On Mon, Aug 25, 2014 at 10:16 AM, Jay Pipes wrote: > On 08/25/2014 11:10 AM, Joe Cropper wrote: >> >> Hello, >> >> Is our long-term vision to allow a VMs to be dynamically added/r

Re: [openstack-dev] [nova] Server Groups - remove VM from group?

this queued up as a discussion point for Paris? If so, count me in! Thanks, Joe On Mon, Aug 25, 2014 at 11:08 AM, Jay Pipes wrote: > On 08/25/2014 11:31 AM, Joe Cropper wrote: >> >> Thanks Jay. Those are the same types of questions I was pondering as >> well when debating how

Re: [openstack-dev] [nova] Server Groups - remove VM from group?

to be checked. Thoughts? Thanks, Joe > On Aug 25, 2014, at 12:10 PM, Russell Bryant wrote: > >> On 08/25/2014 12:56 PM, Joe Cropper wrote: >> That was indeed a rather long (and insightful) thread on the topic. >> It sounds like there are still some healthy discussions w

Re: [openstack-dev] [nova] Server Groups - remove VM from group?

IT administrator to use them--hence why I'm exploring adding some additional functionality; I'm even happy to help implement this, if we can get any type of concurrence on the subject. :-) - Joe On Mon, Aug 25, 2014 at 12:58 PM, Russell Bryant wrote: > On 08/25/2014 01:25 PM, Joe C

Re: [openstack-dev] [nova] Suggestion that Fix to logic of diskfilter

You're always welcome to submit a patch for a valid bug. Just put: Closes-Bug: # At the bottom of the commit message to link the change set to the bug. :) - Joe > On Aug 25, 2014, at 9:44 PM, Jae Sang Lee wrote: > > Hi, all. > > Diskfilter based on host disk usage, it check between usable h

[openstack-dev] [nova] Call for review w.r.t. scheduler being passed requested networks

Hi Stackers, I was wondering if I could get a few folks to look at https://review.openstack.org/#/c/118010/ -- basically with the switch to conductor having a bigger role in the deployment process (and lessening the scheduler's role), the scheduler lost the ability to look at the networks being re

Re: [openstack-dev] Feature freeze + Juno-3 milestone candidates available

+1 to what Jay said. I’m not sure whether the string freeze applies to bugs, but the defect that Matt mentioned (for which I authored the fix) adds a string, albeit to fix a bug. Hoping it’s more desirable to have an untranslated correct message than a translated incorrect message. :-) - Joe

Re: [openstack-dev] Feature freeze + Juno-3 milestone candidates available

is in the freeze, I think > giving a quick heads-up to the -i18n team/list should be enough :) Also > /adding/ a string is not as disruptive to their work as modifying a > potentially-already-translated one. > > Joe Cropper wrote: >> +1 to what Jay said. >> >> I’

Re: [openstack-dev] [nova] Server Groups - remove VM from group?

: > On 08/25/2014 11:25 AM, Joe Cropper wrote: >> I was thinking something simple such as only allowing the add >> operation to succeed IFF no policies are found to be in violation... >> and then nova wouldn't need to get into all the complexities you >> mention? >

Re: [openstack-dev] [nova] Server Groups - remove VM from group?

gt;> >> I think this would round out the support that’s there and really allow us to >> capitalize on the hard work everyone’s already put into them. >> >> - Joe >> >>> On Aug 26, 2014, at 6:39 PM, Chris Friesen >>> wrote: >>> >&g

Re: [openstack-dev] [nova] Server Groups - remove VM from group?

, 2014, at 5:54 PM, Chris Friesen wrote: > On 09/10/2014 04:16 PM, Russell Bryant wrote: >> >> >>> On Sep 10, 2014, at 2:03 PM, Joe Cropper >>> wrote: >>> >>> I would like to craft up a blueprint proposal for Kilo to add two >>> simple

Re: [openstack-dev] [nova] Server Groups - remove VM from group?

Agreed - I’ll draft up a formal proposal in the next week or two and we can focus the discussion there. Thanks for the feedback - this provides a good framework for implementation considerations. - Joe On Sep 10, 2014, at 6:00 PM, Russell Bryant wrote: > On 09/10/2014 06:46 PM, Joe Crop

[openstack-dev] [nova] nova-specs for Kilo?

Hi Folks, Just wondering if the nova-specs master branch will have a ‘kilo’ directory created soon for Kilo proposals? I have a few things I’d like to submit, just looking for the proper home. Thanks, Joe ___ OpenStack-dev mailing list OpenStack-dev@

Re: [openstack-dev] [nova] nova-specs for Kilo?

Thanks! Exactly what I was looking for. On Sep 11, 2014, at 12:38 AM, Russell Bryant wrote: > On 09/11/2014 01:32 AM, Joe Cropper wrote: >> Hi Folks, >> >> Just wondering if the nova-specs master branch will have a ‘kilo’ >> directory created soon for Kilo proposa

Re: [openstack-dev] [nova] Server Groups - remove VM from group?

11, 2014, at 2:11 AM, Sylvain Bauza wrote: > > Le 11/09/2014 01:10, Joe Cropper a écrit : >> Agreed - I’ll draft up a formal proposal in the next week or two and we can >> focus the discussion there. Thanks for the feedback - this provides a good >> framework for imple

Re: [openstack-dev] [nova] Server Groups - remove VM from group?

wrote: > On 09/11/2014 03:01 PM, Jay Pipes wrote: >> On 09/11/2014 04:51 PM, Matt Riedemann wrote: >>> On 9/10/2014 6:00 PM, Russell Bryant wrote: >>>> On 09/10/2014 06:46 PM, Joe Cropper wrote: >>>>> Hmm, not sure I follow the concern, Russell. How is th

Re: [openstack-dev] [qa] host aggregate's availability zone

Did you enable the AvailabilityZoneFilter in nova.conf that the scheduler uses? And enable the FilterScheduler? These are two common issues related to this. - Joe > On Dec 21, 2014, at 10:28 AM, Danny Choi (dannchoi) > wrote: > > Hi, > > I have a multi-node setup with 2 compute hosts, qa5

Re: [openstack-dev] [nova] Evacuate instance which in server group with affinity policy

This is another great example of a use case in which these blueprints [1, 2] would be handy. They didn’t make the clip line for Kilo, but we’ll try again for L. I personally don’t think the scheduler should have “special case” rules about when/when not to apply affinity policies, as that could

Re: [openstack-dev] [nova] review closure for nova blueprint review.openstack.org/#/c/140133/

Prefixing subject with [nova] so folks’ mail rules catch this. - Joe > On Jan 5, 2015, at 1:47 PM, Kenneth Burger wrote: > > Hi, I am trying to get approval on this nova blueprint, > https://review.openstack.org/#/c/140133/ > . There was a +2 from M

[openstack-dev] Arbitrary "extra specs" for compute nodes?

Hi Folks, I was wondering if there was any such mechanism in the compute node structure to hold arbitrary key-value pairs, similar to flavors' "extra_specs" concept? It appears there are entries for things like pci_stats, stats and recently added extra_resources -- but these all tend to have more

Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation ratio out of scheduler

There may also be specific software entitlement issues that make it useful to deterministically know which host your VM will be placed on. This can be quite common in large organizations that have certain software that can be tied to certain hardware or hardware with certain # of CPU capacity, etc

Re: [openstack-dev] [nova] Arbitrary "extra specs" for compute nodes?

On Mon, Jun 9, 2014 at 10:07 AM, Chris Friesen wrote: > On 06/07/2014 12:30 AM, Joe Cropper wrote: >> >> Hi Folks, >> >> I was wondering if there was any such mechanism in the compute node >> structure to hold arbitrary key-value pairs, similar to flavors&#x

Re: [openstack-dev] [nova] Arbitrary "extra specs" for compute nodes?

ted to instances, I think we need something additional? I'd happily create a new blueprint for this as well. > > > > Phil > > > > From: Joe Cropper [mailto:cropper@gmail.com] > Sent: 07 June 2014 07:30 > To: openstack-dev@lists.openstack.org > Subject: [o

Re: [openstack-dev] [nova] Arbitrary "extra specs" for compute nodes?

On Mon, Jun 9, 2014 at 12:56 PM, Jay Pipes wrote: > On 06/09/2014 01:38 PM, Joe Cropper wrote: >> >> On Mon, Jun 9, 2014 at 5:17 AM, Day, Phil wrote: >>> >>> Hi Joe, >>> >>> >>> >>> Can you give some examples of what that

Re: [openstack-dev] [Nova] Automatic evacuate

I've been thinking a lot about these use cases too. As was previously suggested, I think a session in Paris in this topic would be immensely beneficial. Is there somewhere we can officially log a room or some such for further discussion? - Joe > On Oct 15, 2014, at 9:04 PM, Russell Bryant wro

Re: [openstack-dev] [All] Maintenance mode in OpenStack during patching/upgrades

I’m glad to see this topic getting some focus once again. :-) >From several of the administrators I talk with, when they think of putting a >host into maintenance mode, the common requests I hear are: 1. Don’t schedule more VMs to the host 2. Provide an optional way to automatically migrate all

Re: [openstack-dev] [tc] [watcher] New project: Watcher

> On Nov 2, 2015, at 4:50 AM, Thierry Carrez wrote: > > Antoine CABOT wrote: >> We are pleased to introduce Watcher, a new project in the OpenStack >> ecosystem. We believe that a "resource optimization" service in an >> OpenStack-based cloud is a crucial component that has been missing to >>

Re: [openstack-dev] [watcher] Watcher meetings in Austin

Hi Watcher team, Resending this in case folks missed it. Thanks, Joe (jwcroppe) > On Apr 22, 2016, at 4:37 AM, Antoine Cabot wrote: > > Hi Watcher team, > > We will have a couple of meetings next week to discuss Watcher > achievements during the Mitaka cycle and define priorities for Newton

[openstack-dev] [watcher] Travel logistics for mid-cycle in Austin

Hi Watcher Team, For those of you attending the Watcher mid-cycle next week in Austin (Tue-Thurs), please take a quick look at the travel details [1] — particularly the bit about where to “check in” every day once you arrive to the IBM campus. As another FYI, light breakfast foods, lunch and an

Re: [openstack-dev] questions about nova compute monitors extensions

The new framework does indeed support user-defined monitors. You just extend whatever monitor’d like (e.g., nova.compute.monitors.cpu.virt_driver.Monitor) and add your customized logic. And since the new framework uses stevedore-based extension points, you just need to be sure to add the appr

Re: [openstack-dev] [Watcher] Nominating Vincent Francoise to Watcher Core

+1 > On Feb 17, 2016, at 8:05 AM, David TARDIVEL wrote: > > Team, > > I’d like to promote Vincent Francoise to the core team. Vincent's done a > great work > on code reviewing and has proposed a lot of patchsets. He is currently the > most active > non-core reviewer on Watcher project, and t

Re: [openstack-dev] [nova] Question about force_host skip filters

+1 to using a filter property to indicate whether the filter needs to be run on force_hosts. As others have said, there are certain cases that need to be checked even if the admin is trying to intentionally place a VM somewhere such that we can fail early vs. letting the hypervisor blow up on t

[openstack-dev] [nova] Intended behavior for instance.host on reschedule?

Hi Folks, I was wondering if anyone can comment on the intended behavior of how instance.host is supported to be set during reschedule operations. For example, take this scenario: 1. Assume an environment with a single host… call it host-1 2. Deploy a VM, but force an exception in the spawn pa

Re: [openstack-dev] [nova] Intended behavior for instance.host on reschedule?

mment. Do we know if this is an intended feature or would we consider this a bug? It seems like we could free this up, as you said, to allow room for additional VMs, especially since we know it didn’t successfully deploy anyway? > Vish > > On Mar 3, 2015, at 12:15 AM, Joe Cro

Re: [openstack-dev] [nova] Intended behavior for instance.host on reschedule?

Logged a bug [1] and submitted a fix [2]. Review away! [1] https://bugs.launchpad.net/nova/+bug/1427944 [2] https://review.openstack.org/#/c/161069/ - Joe > On Mar 3, 2015, at 4:42 PM, Jay Pipes wrote: > > On 03/03/2015 06:55 AM, Joe Cropper wrote: >>> On Mar 3

Re: [openstack-dev] [watcher] Stepping down as Watcher spec core

Antoine, It’s been a pleasure getting to work alongside you in the open source community. Your leadership was paramount to the project and I wish you all the best in your next chapter! Best, Joe (jwcroppe) > On Aug 15, 2017, at 1:26 PM, Susanne Balle wrote: > > Thanks for all the hard work

Re: [openstack-dev] [watcher] Mascot final choice

+2 to Jellyfish! > On Jul 28, 2016, at 4:08 PM, Antoine Cabot wrote: > > Hi Watcher team, > > Last week during the mid-cycle, we came up with a list of possible mascots > for Watcher. The only one which is in conflict with other projects is the > bee. > So we have this final list : > 1. Jell

Re: [openstack-dev] [watcher] Stepping down from core

Thanks Taylor… thanks so much for your contributions! Best, Joe > On Aug 3, 2016, at 11:32 AM, Taylor D Peoples wrote: > > Hi all, > > I'm stepping down from Watcher core and will be leaving the OpenStack > community to pursue other opportunities. > > I wasn't able to contribute to Watcher a

Re: [openstack-dev] [watcher] Nominate Prashanth Hari as core for watcher-specs

+1 > On Aug 16, 2016, at 11:59 AM, Jean-Émile DARTOIS > wrote: > > +1 > > Jean-Emile > DARTOIS > > {P} Software Engineer > Cloud Computing > > {T} +33 (0) 2 56 35 8260 > {W} www.b-com.com > > > De : Antoine Cabot > Envoyé : mardi 16 août

Re: [openstack-dev] [Watcher] Nominating Prudhvi Rao Shedimbi to Watcher Core

+1 ! > On Feb 14, 2017, at 4:05 AM, Vincent FRANÇOISE > wrote: > > Team, > > I would like to promote Prudhvi Rao Shedimbi to the core team. He's done > a great work in reviewing many patchsets[1] and I believe that he has a > good vision of Watcher as a whole. > > I think he would make an exc