Hi Kris, Yes. It should work with even disabled host.
Thanks, Kazu -----Original Message----- From: Kris G. Lindgren [mailto:[email protected]] Sent: Saturday, March 07, 2015 3:54 AM To: Jesse Keating; Jay Pipes; [email protected] Subject: Re: [Openstack-operators] [nova] Deprecation of ComputeFilter I was wondering if doing the target host deployment is effected by the status of the compute host? IE can you do: nova boot --availability-zone <zone>:<server> on a server that is marked as disabled in nova? ____________________________________________ Kris Lindgren Senior Linux Systems Engineer GoDaddy, LLC. On 3/6/15, 11:43 AM, "Jesse Keating" <[email protected]> wrote: >On 3/6/15 10:27 AM, Jay Pipes wrote: >> >> As for adding another CONF option, I'm -1 on that. I see no valid >> reason to schedule workloads to disabled hosts. > >There may be a better way to skin this cat, but one scenario is we have >a host that has alerted, we want to evacuate it and prevent any future >builds from going there so we disable it. But after repairing, we want >to introduce OUR load to it first to test it before putting CUSTOMER >load on it, so we'd like to be able to schedule something to the >disabled host. > >-- >-jlk > >_______________________________________________ >OpenStack-operators mailing list >[email protected] >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators _______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators _______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
