----- Original Message ----- > From: "Jeff Peeler" <jpee...@redhat.com> > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > > I'd greatly prefer using availability zones/host aggregates as I'm trying > to keep the footprint as small as possible. It does appear that in the > section "configure scheduler to support host aggregates" [1], that I can > configure filtering using just one scheduler (right?). However, perhaps > more importantly, I'm now unsure with the network configuration changes > required for Ironic that deploying normal instances along with baremetal > servers is possible. > > [1] > http://docs.openstack.org/kilo/config-reference/content/section_compute-scheduler.html
Hi Jeff, I assume your need for a second scheduler is spurred by wanting to enable different filters for baremetal vs virt (rather than influencing scheduling using the same filters via image properties, extra specs, and boot parameters (hints)? I ask because if not you should be able to use the hypervisor_type image property to ensure that images intended for baremetal are directed there and those intended for kvm etc. are directed to those hypervisors. The documentation [1] doesn't list ironic as a valid value for this property but I looked into the code for this a while ago and it seemed like it should work... Apologies if you had already considered this. Thanks, Steve [1] http://docs.openstack.org/cli-reference/content/chapter_cli-glance-property.html > On Wed, Sep 9, 2015 at 1:13 PM, Jim Rollenhagen <j...@jimrollenhagen.com> > wrote: > > > On Wed, Sep 02, 2015 at 03:42:20PM -0400, Jeff Peeler wrote: > > > Hi folks, > > > > > > I'm currently looking at supporting Ironic in the Kolla project [1], but > > > was unsure if it would be possible to run separate instances of nova > > > compute and controller (and scheduler too?) to enable both baremetal and > > > libvirt type deployments. I found this mailing list post from two years > > ago > > > [2], asking the same question. The last response in the thread seemed to > > > indicate work was being done on the scheduler to support multiple > > > configurations, but the review [3] ended up abandoned. > > > > > > Are the current requirements the same? Perhaps using two availability > > zones > > > would work, but I'm not clear if that works on the same host. > > > > At Rackspace we run Ironic in its own cell, and use cells filters to > > direct builds to the right place. > > > > The other option that supposedly works is host aggregates. I'm not sure > > host aggregates supports running two scheduler instances (because you'll > > want different filters), but maybe it does? > > > > // jim > > > > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Steve Gordon, RHCE Sr. Technical Product Manager, Red Hat Enterprise Linux OpenStack Platform __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
