Hi all,
There is a new project "Jacket" to unify the API models of different clouds
using OpenStack API. Its wiki is: https://wiki.openstack.org/wiki/Jacket
After the discussion of last week, I update the description in wiki about the
relations between Jacket and Tricircle, and add the "FAQ" section. Please
review and give your suggestions, thanks.
Thanks again for the good suggestions and support from Gordon Chung, Janki
Chhatbar, Shinobu Kinjo, Joe Huang and Phuong.
Best Regars,
Kevin (Sen Zhang)
Q: Is Jacket one kind of API gateway for different clouds?
Jacket isn't an API gateway for different clouds. The aim of Jacket is to offer
the unified OpenStack API model for different clouds, so the major task of
Jacket is to shield the differences between provider cloud and OpenStack
through the sub services in Jacket such as “Unified resource uuid allocation”，
"Fake volume management" and so on.
Q: What is the relation between Tricircle and Jacket?
Jacket focuses on how to unify the API models of clouds using OpenStack API
model, and how to use one OpenStack instance to manage one provider cloud.
Tricircle focuses on how to manage multiply OpenStack instances and networking
automation across multiple OpenStack instances. So it is a good solution to use
Tricircle to manage multiply different clouds at the same time, each one of
which is managed by OpenStack instance through Jacket.
__________________________________________________________________________
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
