On Wed, Mar 16, 2016 at 9:58 PM, zs <[email protected]> wrote: > Hi Gordon, > > Thank you for your suggestion. > > I think jacket is different from tricircle. Because tricircle focuses on > OpenStack deployment across multiple sites, but jacket focuses on how to > manage the different clouds just like one cloud. There are some > differences: > 1. Account management and API model: Tricircle faces multiply OpenStack > instances which can share one Keystone and have the same API model, but > jacket will face the different clouds which have the respective service and > different API model. For example, VMware vCloud Director has no volume > management like OpenStack and AWS, jacket will offer a fake volume > management for this kind of cloud.
The Jacket will be kind of API gateway for different cloud systems, won't it? > 2. Image management: One image just can run in one cloud, jacket need > consider how to solve this problem. > 3. Flavor management: Different clouds have different flavors which can not > be operated by users. Jacket will face this problem but there will be no > this problem in tricircle. > 4. Legacy resources adoption: Because of the different API modles, it will > be a huge challenge for jacket. > > I think it is maybe a good solution that jacket works to unify the API model > for different clouds, and then using tricircle to offer the management of a > large scale VMs. > > Best Regards, > Kevin (Sen Zhang) > > > At 2016-03-16 19:51:33, "gordon chung" <[email protected]> wrote: >> >> >>On 16/03/2016 4:03 AM, zs wrote: >>> Hi all, >>> >>> There is a new project "jacket" to manage multiply clouds. The jacket >>> wiki is: https://wiki.openstack.org/wiki/Jacket >>> Please review it and give your comments. Thanks. >>> >>> Best Regards, >>> >>> Kevin (Sen Zhang) >>> >>> >> >>i don't know exact details of either project, but i suggest you >>collaborate with tricircle project[1] because it seems you are >>addressing the same user story (and in a very similar fashion). not sure >>if it's a user story for OpenStack itself, but no point duplicating >> efforts. >> >>[1] https://wiki.openstack.org/wiki/Tricircle >> >>cheers, >> >>-- >>gord >> >>__________________________________________________________________________ >>OpenStack Development Mailing List (not for usage questions) >>Unsubscribe: [email protected]?subject:unsubscribe >>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Email: [email protected] GitHub: shinobu-x Blog: Life with Distributed Computational System based on OpenSource __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
