Hello, Dan, > Correct, cells only applies to single-vendor distributed deployments. > In both its current and future forms, it uses private APIs for > communication between the components, and thus isn't suited for a > multi-vendor environment.
Thank you for your confirmation. My doubt is what's the "private APIs", which commponents included " communication between the components ". Best Regards Chaoyi Huang ( joehuang ) -----Original Message----- From: Dan Smith [mailto:d...@danplanet.com] Sent: Friday, December 12, 2014 11:41 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [all] [tc] [PTL] Cascading vs. Cells – summit recap and move forward > [joehuang] Could you pls. make it more clear for the deployment mode > of cells when used for globally distributed DCs with single API. Do > you mean cinder/neutron/glance/ceilometer will be shared by all cells, > and use RPC for inter-dc communication, and only support one vendor's > OpenStack distribution? How to do the cross data center integration > and troubleshooting with RPC if the > driver/agent/backend(storage/network/sever) from different vendor. Correct, cells only applies to single-vendor distributed deployments. In both its current and future forms, it uses private APIs for communication between the components, and thus isn't suited for a multi-vendor environment. Just MHO, but building functionality into existing or new components to allow deployments from multiple vendors to appear as a single API endpoint isn't something I have much interest in. --Dan _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
