from:"Kevin.ZhangSen"

Re: [openstack-dev] [openstack-infra][jacket]request to be added to the groups in gerrit

2016-04-27 Thread Kevin.ZhangSen

Thanks a lot.

Best regards,
Keivn(Sen Zhang)









At 2016-04-28 10:57:29, "Elizabeth K. Joseph" <l...@princessleia.com> wrote:
>On Wed, Apr 27, 2016 at 7:21 PM, Kevin.ZhangSen <okay22m...@163.com> wrote:
>> Hi Infra Team,
>>
>> We will start working on the new project. Could you please add me to
>> jacket-core and jacket-release in gerrit, so that I can add others.
>> Thanks a lot.
>
>No problem, done. You can now add others to these teams.
>
>For reference, the corresponding change by Kevin (Sen Zhang) to add
>this project is here: https://review.openstack.org/#/c/263500/
>
>-- 
>Elizabeth Krumbach Joseph || Lyz || pleia2
>
>__
>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-dev] [openstack-infra][jacket]request to be added to the groups in gerrit

2016-04-27 Thread Kevin.ZhangSen

Hi Infra Team,


We will start working on the new project. Could you please add me to 
jacket-core and jacket-release in gerrit, so that I can add others.
Thanks a lot.


Best regards,
Kevin(Sen Zhang)__
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

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

2016-03-24 Thread Kevin.ZhangSen

Hi Ghanshyam,

Thank you for your sugesstions, and I agree with your opinion that the service 
outside OpenStack is better. In fact I am considering what API Jacket will 
offer. It is better to offer the OpenStack API directly. But there will be a 
question how to modify as little code as possible to keep the same API 
compatibility with OpenStack after OpenStack updates the API version. I think 
this will be an interesting question, but we can try to let Jacket offer the 
OpenStack API.



The reply about other query is below. If there are any questions, please tell 
me. Thank you again.


Best Regards,
Kevin (Sen Zhang)


At 2016-03-24 11:58:47, "GHANSHYAM MANN"  wrote:
>Hi Kevin,
>
>Its always nice idea as jacket has but not sure how feasible and
>valuable it would be. For doing API translation and gateway, there are
>many available and one I remember is Aviator (based on ruby gem) [1],
>not sure how active it is now.
>
>As your idea is more about consuming all differences between different
>cloud, few query-
>
> 1. Different clouds have very much different API model and feature
>they provides, how  worth it is to provide missing/different features
>at jacket layer? its then kind of another layer of cloud layer you
>will end up.
Kevin: We will provide the commonly used functions to let the users manage the 
different clouds just like one kind of cloud, for example VMs 
management(create/destroy/start/stop/restart/rebuild...) and volume 
management(create/delete/backup/snapshot). About network, there is a solution 
to use neutron to offer network function through the overlay virtual network 
based on the provider clouds’ virtual network. This will be another project, 
not in Jacket.
> 2. To support that idea through OpenStack standard API, you need to
>inserting jacket driver all over the components which end up having
>another layer gets inserted there. Maintainability of that is another
>issue for each OpenStack components.
Kevin: I agree with you. Jacket offer OpenStack will be better.
>IMO, outside layer (from OpenStack ) which can do all these would be
>nice something which can redirect API services at top level top and do
>what all conversion, consume difference etc.
>
>[1] https://github.com/aviator/aviator
>
>Regards
>Ghanshyam Mann
>
>
>On Wed, Mar 16, 2016 at 9:58 PM, zs  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.
>> 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"  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-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] [new-project][jacket] Introduction to jacket, a new project

2016-03-19 Thread Kevin.ZhangSen

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

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

2016-03-19 Thread Kevin.ZhangSen

Thanks for Joe's explanation. :)

Best Regards,
Kevin (Sen Zhang)

在 2016-03-17 09:58:38，"joehuang"  写道：

Agree with Kevin,

Currently Tricircle mainly focuses on the API gateway and networking automation 
across multiple OpenStack instances. The hybrid cloud PoC is built based on 
Tricircle in Tokyo Summit: 
https://www.openstack.org/summit/tokyo-2015/videos/presentation/huawei-openstack-enabled-hybrid-cloud

Where Tricircle manages multiple small OpenStack instances, and different 
OpenStack instance using “jacket” to integrate AWS/vCloud. The jacket provide a 
way of abstract of hybrid cloud.

Best Regards

Chaoyi Huang ( Joe Huang )

From: zs [mailto:okay22m...@163.com]
Sent: Wednesday, March 16, 2016 8:59 PM
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"  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-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

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

2016-03-19 Thread Kevin.ZhangSen

Hi Phuong,

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

Best Regards,
Kevin (Sen Zhang)

在 2016-03-18 11:07:13，"phuon...@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:jankihchhat...@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"  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-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

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

2016-03-19 Thread Kevin.ZhangSen

Hi Janki,

I am very glad you like it. I will mail you when the work starts.  :)

Best Regards,
Kevin (Sen Zhang)

At 2016-03-16 21:20:52, "Janki Chhatbar"  wrote:

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"  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-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

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

2016-03-19 Thread Kevin.ZhangSen

Hi Shinobu,

Thanks for your questions. My reply is behind your questions. :)

Best Regards,
Kevin (Sen Zhang)


At 2016-03-17 12:43:14, "Shinobu Kinjo"  wrote:
>Thank you for your explanation in detail.
>
>On Thu, Mar 17, 2016 at 12:57 PM, zs  wrote:
>> Hi Shinobu,
>>
>> There are some differences between clouds, the major task of jacket is how
>> to shield the differences. So that jacket will not be an API gateway, it has
>> the objects management and function processing, for example :
>> 1.  Unified resource uuid allocation: When users call jacket resource create
>> API, jacket will allocate the uuid for the resource according to jacket's
>> uuid format, then jacket will associate it with the unique identification in
>> provider cloud, because of the different unique identification and the
>> different behaviour in clouds.
>
>The Jacket will absorb the difference between clouds, won't it?
Kevin: Yes, it will.
>> e.g.  a)  AWS can't support to create a volume from an AMI image and
>> boot a virtual machine from a boot volume, so that when users create a
>> volume from an image, jacket will just create a volume record in database,
>> after the virtual machine is created in AWS, jacket will get the boot
>> volume's uuid in AWS and write the relations into the mapping table in
>> database.
>> b) Creating a volume's snapshot, AWS will return a job id, and
>> users will get the snapshot's id after the job startes. Jacket will return
>> the snapshot's id in jacket, then jacket will query the snapshot's id in AWS
>> and  write the relations into the mapping table in database.
>>
>
>Then will the Tricircle make use of mapped uuid to manage whatever
>created resource, If both components will interact each other?
Kevin: Sorry, I don't agree with you. Jacket will record the resources' status. 
For example, in case of creating snapshot in AWS, Jacket will query the job's 
status periodically, before Jacket get the real snapshot id in AWS. At this 
time users query the snapshot's status, Jacket will return 'Pending' defined by 
Jacket. But Tricircle is developed with stateless design, they are conflicting. 
If we do that like you say, I think there will be a bottleneck for Tricircle to 
manage a more large scale VMs, and then we still need a stateless layer just 
like the current Tricircle solution. So my opinion is to simplify each layer's 
function, let each layer do their job. :)
>> 2. Fake volume management: Some clouds have not the complete volume
>> management, for example, VMware vCloud Director have no the boot volume
>> object, and it can't support volume's backup and snapshot, so that jacket
>> will implement these functions for this kind of clouds.
>>
>
>Reading your explanation, at the initial stage of the Jacket, it seems
>to focus on management of the Cinder resource, but it aims to:
Kevin: Not exactly. We need solve the account management, unified flavor, 
unified image and how to take over the legacy resources in the provider clouds. 
Jacket's wiki has the description about these: 
https://wiki.openstack.org/wiki/Jacket  :) 
>> There will be more differences of clouds' behaviour and function. 
> Jacket's
>> target is to shield these differences and let users feel that
>they are using
>> just one cloud.
>
>Cheers,
>Shinobu
>
>> Thanks.
>>
>> Best Regards,
>> Kevin (Sen Zhang)
>>
>>
>> At 2016-03-17 05:47:35, "Shinobu Kinjo"  wrote:
>>>On Wed, Mar 16, 2016 at 9:58 PM, zs  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

Re: [openstack-dev] [openstack-infra][jacket]request to be added to the groups in gerrit

[openstack-dev] [openstack-infra][jacket]request to be added to the groups in gerrit

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

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

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

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

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

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

8 matches

Site Navigation

Mail list logo

Footer information