idnits 2.17.1
draft-llc-teas-dc-aware-topo-model-01.txt:
Checking boilerplate required by RFC 5378 and the IETF Trust (see
https://trustee.ietf.org/license-info):
----------------------------------------------------------------------------
No issues found here.
Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
----------------------------------------------------------------------------
No issues found here.
Checking nits according to https://www.ietf.org/id-info/checklist :
----------------------------------------------------------------------------
** The document seems to lack separate sections for Informative/Normative
References. All references will be assumed normative when checking for
downward references.
** There is 1 instance of too long lines in the document, the longest one
being 3 characters in excess of 72.
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the IETF Trust and authors Copyright Line does not
match the current year
== Line 151 has weird spacing: '...hecksum str...'
== Line 165 has weird spacing: '...hecksum str...'
== Line 197 has weird spacing: '...address ine...'
-- The document date (July 12, 2021) is 1019 days in the past. Is this
intentional?
Checking references for intended status: Informational
----------------------------------------------------------------------------
No issues found here.
Summary: 2 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
2 TEAS Y. Lee
3 Internet-Draft Samsung Electronics
4 Intended status: Informational X. Liu
5 Expires: January 13, 2022 Volta Networks
6 LM. Contreras
7 Telefonica
8 July 12, 2021
10 DC aware TE topology model
11 draft-llc-teas-dc-aware-topo-model-01
13 Abstract
15 This document proposes the extension of the TE topology model for
16 including information related to data center resource capabilities.
18 Status of This Memo
20 This Internet-Draft is submitted in full conformance with the
21 provisions of BCP 78 and BCP 79.
23 Internet-Drafts are working documents of the Internet Engineering
24 Task Force (IETF). Note that other groups may also distribute
25 working documents as Internet-Drafts. The list of current Internet-
26 Drafts is at https://datatracker.ietf.org/drafts/current/.
28 Internet-Drafts are draft documents valid for a maximum of six months
29 and may be updated, replaced, or obsoleted by other documents at any
30 time. It is inappropriate to use Internet-Drafts as reference
31 material or to cite them other than as "work in progress."
33 This Internet-Draft will expire on January 13, 2022.
35 Copyright Notice
37 Copyright (c) 2021 IETF Trust and the persons identified as the
38 document authors. All rights reserved.
40 This document is subject to BCP 78 and the IETF Trust's Legal
41 Provisions Relating to IETF Documents
42 (https://trustee.ietf.org/license-info) in effect on the date of
43 publication of this document. Please review these documents
44 carefully, as they describe your rights and restrictions with respect
45 to this document. Code Components extracted from this document must
46 include Simplified BSD License text as described in Section 4.e of
47 the Trust Legal Provisions and are provided without warranty as
48 described in the Simplified BSD License.
50 Table of Contents
52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
53 2. Datacenter information . . . . . . . . . . . . . . . . . . . 2
54 3. Model structure . . . . . . . . . . . . . . . . . . . . . . . 3
55 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
56 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
57 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
58 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 6
59 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
61 1. Introduction
63 More and more service providers are deploying cloud computing
64 facilities in order to host different kinds of services and
65 applications. Such facilities can be generally referred as
66 Datacenter Points of Presence (DC-PoPs). Those DCs will consist on a
67 number of servers and networking elements for connecting all of them
68 with the transport network. Depending on the number of servers in
69 the data center, there will be distinct capabilities in terms of
70 CPUs, memory and storage available for deploying and running the
71 aforementioned services.
73 In such distributed and interconnected DC-PoPs, both computing and
74 topological information are of interest for determining the optimal
75 DC where to deploy a given service or application.
77 This document propose a DC-aware extension for the topology model.
79 2. Datacenter information
81 The relevant information for datacenter capabilities can be described
82 in different ways. One potential manner is to describe resource
83 capabilities such as CPU, memory, storage, etc. This can be done in
84 terms of total, used and free capacity for each of the parameters of
85 interest. Another form of populating the information is by
86 describing those resource capabilities as a bundled, usually referred
87 as quota or flavor. In this respect, reference bundles such as the
88 ones proposed by the Common Network Function Virtualisation
89 Infrastructure Telecom Taskforce (CNTT), which is an initiative
90 jointly promoted by GSMA and the Linux Foundation [CNTT], [GSMA].
92 Focusing on the CNTT ongoing work, the flavors there defined are
93 characterized according to:
95 o Type of instance (T): the types of instances are characterized as
96 B (Basic), or N (Network Intensive). The latter can come with
97 extensions for network acceleration for offloading network
98 intensive operations to hardware.
100 o Interface Option (I): it refers to the associated bandwidth of the
101 network interface.
103 o Compute flavor (F): it refers to a given predefined combination of
104 resources in terms of virtual CPU, RAM, disk, and bandwidth for
105 the management interface.
107 o Optional storage extension (S): allows to request additional
108 storage capacity.
110 o Optional hardware acceleration characteristics (A): to request
111 specific acceleration capabilities for improving the performance
112 of the infrastructure.
114 Additional information can refer to the management capabilities of
115 the compute infrastructure, such as hypervisor details or
116 virtualization technologies available.
118 Finally, all can be complemented with information related to the
119 networking details for reaching the aforementioned compute
120 capabilities (IP addressed, bandwidth, etc).
122 3. Model structure
124 module: ietf-dcpop-dc
125 +--rw dcpop
126 +--rw dc* [id]
127 | +--rw hypervisor* [id]
128 | | +--rw ram
129 | | | +--rw total? uint32
130 | | | +--rw used? uint32
131 | | | +--rw free? uint32
132 | | +--rw disk
133 | | | +--rw total? uint32
134 | | | +--rw used? uint32
135 | | | +--rw free? uint32
136 | | +--rw vcpu
137 | | | +--rw total? uint16
138 | | | +--rw used? uint16
139 | | | +--rw free? uint16
140 | | +--rw instance* -> /dcpop/dc/instance/id
141 | | +--rw id string
142 | | +--rw name? string
143 | +--rw instance* [id]
144 | | +--rw flavor
145 | | | +--rw disk? uint32
146 | | | +--rw ram? uint32
147 | | | +--rw vcpus? uint16
148 | | | +--rw id? string
149 | | | +--rw name? string
150 | | +--rw image
151 | | | +--rw checksum string
152 | | | +--rw size uint32
153 | | | +--rw format
154 | | | | +--rw container? enumeration
155 | | | | +--rw disk? enumeration
156 | | | +--rw id? string
157 | | | +--rw name? string
158 | | +--rw hypervisor? -> /dcpop/dc/hypervisor/id
159 | | +--rw port* -> /dcpop/dc/network/subnetwork/port/id
160 | | +--rw project? string
161 | | +--rw status? enumeration
162 | | +--rw id string
163 | | +--rw name? string
164 | +--rw image* [id]
165 | | +--rw checksum string
166 | | +--rw size uint32
167 | | +--rw format
168 | | | +--rw container? enumeration
169 | | | +--rw disk? enumeration
170 | | +--rw id string
171 | | +--rw name? string
172 | +--rw flavor* [id]
173 | | +--rw disk? uint32
174 | | +--rw ram? uint32
175 | | +--rw vcpus? uint16
176 | | +--rw id string
177 | | +--rw name? string
178 | +--rw dc-monitoring-param* [name]
179 | | +--rw name string
180 | | +--rw value-string? string
181 | +--rw network* [id]
182 | | +--rw subnetwork* [id]
183 | | | +--rw port* [id]
184 | | | | +--rw ip-address? inet:ip-address
185 | | | | +--rw instance? -> /dcpop/dc/instance/id
186 | | | | +--rw project? string
187 | | | | +--rw status? enumeration
188 | | | | +--rw id string
189 | | | | +--rw name? string
190 | | | +--rw project? string
191 | | | +--rw status? enumeration
192 | | | +--rw id string
193 | | | +--rw name? string
194 | | +--rw dhcp-agent* [id]
195 | | | +--rw enabled? boolean
196 | | | +--rw pools* [ip-address]
197 | | | | +--rw ip-address inet:ip-address
198 | | | +--rw project? string
199 | | | +--rw status? enumeration
200 | | | +--rw id string
201 | | | +--rw name? string
202 | | +--rw project? string
203 | | +--rw status? enumeration
204 | | +--rw id string
205 | | +--rw name? string
206 | | +--rw dcpop-ref? -> /dcpop/dcpop-id
207 | +--rw ap* -> /actn-vn:actn/ap
208 /access-point-list/access-point-id
209 | +--rw dcpop-ref? -> /dcpop/dcpop-id
210 | +--rw id string
211 | +--rw name? string
212 +--rw dcpop-id? string
214 4. Security Considerations
216 The data-model in this document does not have any security
217 implications. The model is designed to be accessed via NETCONF
218 [RFC6241], thus the security considerations for the NETCONF protocol
219 are applicable here.
221 5. IANA Considerations
223 This draft does not include any IANA considerations
225 6. References
227 [CNTT] "Cloud iNfrastructure Telco Taskforce Reference Model,
228 Version 6.0", January 2021,
229 .
231 [GSMA] "Cloud Infrastructure Reference Model, Version 1.0",
232 November 2020, .
235 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
236 and A. Bierman, Ed., "Network Configuration Protocol
237 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
238 .
240 Acknowledgments
242 The work of L.M. Contreras has been partly funded by the European
243 Commission through the H2020 project 5GROWTH (Grant Agreement no.
244 856709).
246 Authors' Addresses
248 Young Lee
249 Samsung Electronics
250 Seoul
251 South Korea
253 Email: younglee.tx@gmail.com
255 Xufeng Liu
256 Volta Networks
258 Email: xufeng.liu.ietf@gmail.com
260 Luis M. Contreras
261 Telefonica
262 Ronda de la Comunicacion, s/n
263 Sur-3 building, 3rd floor
264 Madrid 28050
265 Spain
267 Email: luismiguel.contrerasmurillo@telefonica.com
268 URI: http://lmcontreras.com/