Re: [OPSAWG] draft-junsheng-cloud-virtual-resource-management

["Romascanu, Dan (Dan)" <[e-mail]>]

 

 

Hi,

I also read the I-D and I have the same comments and questions as Ron
plus an extra one - I think that we need a short discussion about the
operational model of management of virtual resources in a data center,
and definition and a description of hypervisors and their role in the
management architecture. 

 
Thanks and Regards,

Dan

From: [e-mail] [mailto:[e-mail]] On Behalf
Of Ronald Bonica
Sent: Tuesday, June 28, 2011 1:18 AM
To: [e-mail]; [e-mail]
Subject: Re: [OPSAWG] draft-junsheng-cloud-virtual-resource-management

 

Chu,

 

Thanks for submitting your draft. The following are a few comments:

 

-          This work appears to have at least one foot in the APPS Area.
You might want to run it past an APPS WG

-          You appear to have come to the conclusion that REST is the
best solution. Why not an existing IETF Protocol (e..g., NETCONF)?

-          Is there significant operator interest in making this an open
protocol?

-          Is there any interest among Hypervisor vendors in supporting
a common API?

 

 
Ron

 

 

From: [e-mail] [mailto:[e-mail]] On Behalf
Of [e-mail]
Sent: Sunday, June 26, 2011 9:39 PM
To: [e-mail]
Subject: [OPSAWG] draft-junsheng-cloud-virtual-resource-management

 


Hello, All 

I am Chu Junsheng from ZTE Corp.. At Bhumip's request I upload an I-D. 
Please review and give your comments. 

http://datatracker.ietf.org/doc/draft-junsheng-cloud-virtual-resource-ma
nagement/ 

Filename:
draft-junsheng-cloud-virtual-resource-management
Revision:                         00
Title:                                   Virtual Resource Management in
Cloud
Creation date:                  2011-06-27
WG ID:                                   Individual Submission
Number of pages: 55

Abstract:
  In current Cloud and Data Center (DC) environment, the manageable
  virtualized resources aggregated by the Resource Management Platform
  (RMP) may be supplied by different types of hypervisor
  implementations.  The RMP needs to support a variety of hypervisor
  APIs to allow access, management and integration of different types
  of resources.  In order to decouple the RMP from any particular
  hypervisor implementation, a unified API needs to be developed.  This
  draft presents the requirements and preliminary implementation
  considerations for such an API.


Thanks.