On 4/3/15, 8:24 PM, "Dugger, Donald D" <donald.d.dug...@intel.com> wrote:
>The goal is not `splitting for the sake of splitting'. The goal is to >have a separate scheduler that is ultimately usable by other projects >inside OpenStack. Currently Cinder has its own filter based scheduler >(duplicating scheduling code in 2 places seems silly), Neutron will need >scheduling services, there are multiple places where a common scheduling >service would be beneficial. + 1 > >-- >Don Dugger >"Censeo Toto nos in Kansa esse decisse." - D. Gale >Ph: 303/443-3786 > >-----Original Message----- >From: Ed Leafe [mailto:e...@leafe.com] >Sent: Friday, April 3, 2015 10:59 AM >To: openstack-dev@lists.openstack.org >Subject: Re: [openstack-dev] [nova] [scheduler] [gantt] Please stop using >"Gantt" for discussing about Nova scheduler > >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA512 > >On 04/03/2015 11:42 AM, Dugger, Donald D wrote: > >> Yes the current effort is to clean up the scheduler interfaces but one >> of the main goals of that clean up is to make it possible to then >> split out the scheduler to a separate project. I don't want to lose >> focus on the ultimate goal of creating the split. > >I don't agree that the ultimate goal is splitting the scheduler. IMO, the >goal is to create 1) a clean, robust interface along with 2) a scalable >architecture. Those improvements will 1) allow the scheduler to be split >cleanly, and 2) justify splitting it out. Splitting for the sake of >splitting is pointless. > >- -- > >- -- Ed Leafe >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v2 >Comment: GPGTools - https://gpgtools.org >Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > >iQIcBAEBCgAGBQJVHsbeAAoJEKMgtcocwZqLdysQAIJ6nThjqgNgJu1hLW4n6MDY >Db57k+37b5M5h6Z633jrXSTWCuqjIwUIW2G1+PQMsXq7FcWguAG7fxhVizE4s0h0 >RhucmNQ1GWj6eFNfpSljC0WAdZEDhuXnPcxi2OyMwRr0j2lqYcJvPKBmuobS8Rbl >xD9ciIlVELtHPm2dsj1HkB8TO7fgESjdv+I2QPU9C31ubp0CYlwSAPCdAhN9g+B0 >WVCEnq+7ADn95G+/z77Wlx6s83KkCh89C+h2ivgGI4mHeWJskXT9lr9lsC342DO9 >GoWvDvRF5H9/imx6Jh4avipH55YCZfZ9T+2eOPVoAYkXujPiX13tqM8UkBj7KCDx >/FJNatC0aTDPYGMgOW329pGWkP9n2ceW1gMlyHpmMFJHCaAdmM+gqnjnarT1UECr >13yndy9axjubisZ71hdGgBi/Sy1FbG5+XVshWyAUgzoJZurDtg4RhhUdw8n0iQKd >SuA3E9Z+PI6gTulp532JdHBVOpsG2P+9QOzLwBEnpSp8WmuU8h2EVMm6A3Zdrf+4 >zIUL8lvpDwZ/0KBHSF6WptZspSXe/OwOKlQYO2geHkeARANv3Tv/h3HB/7SW1Bz0 >8N5K2aDK/adzfzagrV0S3f201JoFC90JSXgA4dDdtHr8/oUj1kw3QoTACVrvPvYP >ayW76hfM68cjJ3DyhXys >=5h63 >-----END PGP SIGNATURE----- > >__________________________________________________________________________ >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 __________________________________________________________________________ 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
