Open Stack

Hi Phuong,

I will mail you when the works starts. Thanks. :)

Best Regards,
Kevin (Sen Zhang)







在 2016-03-18 11:07:13，"phuongnh at vn.fujitsu.com" <phuongnh at vn.fujitsu.com> 写道：


Hi Kevin,

 

I am interesting in Jacket too, so I would like to contribute once the work starts.

 

Thanks,

Phuong.

 

From: Janki Chhatbar [mailto:jankihchhatbar at gmail.com]
Sent: Wednesday, March 16, 2016 8:21 PM
To: zs
Subject: Re: [openstack-dev] [jacket] Introduction to jacket, a new project

 

Hi Kevin

 

I read the wiki and quite liked it. Good going. I would ‎like to contribute to it once the work starts

 Do let me know about it.





Thanks

Janki

 

Sent from my BlackBerry 10 smartphone.

|

From: zs

Sent: Wednesday, 16 March 2016 18:30

To: OpenStack Development Mailing List (not for usage questions)

Reply To: OpenStack Development Mailing List (not for usage questions)

Subject: Re: [openstack-dev] [jacket] Introduction to jacket, a new project

|

 

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.
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" <gord at live.ca> 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: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev






 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160318/43a36d57/attachment.html>