idnits 2.17.1 draft-llc-teas-dc-aware-topo-model-00.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 128 has weird spacing: '...hecksum str...' == Line 142 has weird spacing: '...hecksum str...' == Line 174 has weird spacing: '...address ine...' -- The document date (November 2, 2020) is 1269 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: May 6, 2021 Volta Networks 6 LM. Contreras 7 Telefonica 8 November 2, 2020 10 DC aware TE topology model 11 draft-llc-teas-dc-aware-topo-model-00 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 May 6, 2021. 35 Copyright Notice 37 Copyright (c) 2020 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 . . . . . . . . . . . . . . . . . . . . . . . . . 5 59 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 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) [CNTT]. 91 Additional information can refer to the management capabilities of 92 the compute infrastructure, such as hypervisor details or 93 virtualization technologies available. 95 Finally, all can be complemented with information related to the 96 networking details for reaching the aforementioned compute 97 capabilities (IP addressed, bandwidth, etc). 99 3. Model structure 101 module: ietf-dcpop-dc 102 +--rw dcpop 103 +--rw dc* [id] 104 | +--rw hypervisor* [id] 105 | | +--rw ram 106 | | | +--rw total? uint32 107 | | | +--rw used? uint32 108 | | | +--rw free? uint32 109 | | +--rw disk 110 | | | +--rw total? uint32 111 | | | +--rw used? uint32 112 | | | +--rw free? uint32 113 | | +--rw vcpu 114 | | | +--rw total? uint16 115 | | | +--rw used? uint16 116 | | | +--rw free? uint16 117 | | +--rw instance* -> /dcpop/dc/instance/id 118 | | +--rw id string 119 | | +--rw name? string 120 | +--rw instance* [id] 121 | | +--rw flavor 122 | | | +--rw disk? uint32 123 | | | +--rw ram? uint32 124 | | | +--rw vcpus? uint16 125 | | | +--rw id? string 126 | | | +--rw name? string 127 | | +--rw image 128 | | | +--rw checksum string 129 | | | +--rw size uint32 130 | | | +--rw format 131 | | | | +--rw container? enumeration 132 | | | | +--rw disk? enumeration 133 | | | +--rw id? string 134 | | | +--rw name? string 135 | | +--rw hypervisor? -> /dcpop/dc/hypervisor/id 136 | | +--rw port* -> /dcpop/dc/network/subnetwork/port/id 137 | | +--rw project? string 138 | | +--rw status? enumeration 139 | | +--rw id string 140 | | +--rw name? string 141 | +--rw image* [id] 142 | | +--rw checksum string 143 | | +--rw size uint32 144 | | +--rw format 145 | | | +--rw container? enumeration 146 | | | +--rw disk? enumeration 147 | | +--rw id string 148 | | +--rw name? string 149 | +--rw flavor* [id] 150 | | +--rw disk? uint32 151 | | +--rw ram? uint32 152 | | +--rw vcpus? uint16 153 | | +--rw id string 154 | | +--rw name? string 155 | +--rw dc-monitoring-param* [name] 156 | | +--rw name string 157 | | +--rw value-string? string 158 | +--rw network* [id] 159 | | +--rw subnetwork* [id] 160 | | | +--rw port* [id] 161 | | | | +--rw ip-address? inet:ip-address 162 | | | | +--rw instance? -> /dcpop/dc/instance/id 163 | | | | +--rw project? string 164 | | | | +--rw status? enumeration 165 | | | | +--rw id string 166 | | | | +--rw name? string 167 | | | +--rw project? string 168 | | | +--rw status? enumeration 169 | | | +--rw id string 170 | | | +--rw name? string 171 | | +--rw dhcp-agent* [id] 172 | | | +--rw enabled? boolean 173 | | | +--rw pools* [ip-address] 174 | | | | +--rw ip-address inet:ip-address 175 | | | +--rw project? string 176 | | | +--rw status? enumeration 177 | | | +--rw id string 178 | | | +--rw name? string 179 | | +--rw project? string 180 | | +--rw status? enumeration 181 | | +--rw id string 182 | | +--rw name? string 183 | | +--rw dcpop-ref? -> /dcpop/dcpop-id 184 | +--rw ap* -> /actn-vn:actn/ap 185 /access-point-list/access-point-id 186 | +--rw dcpop-ref? -> /dcpop/dcpop-id 187 | +--rw id string 188 | +--rw name? string 189 +--rw dcpop-id? string 191 4. Security Considerations 193 The data-model in this document does not have any security 194 implications. The model is designed to be accessed via NETCONF 195 [RFC6241], thus the security considerations for the NETCONF protocol 196 are applicable here. 198 5. IANA Considerations 200 This draft does not include any IANA considerations 202 6. References 204 [CNTT] "Common NFVI for Telco Reference Model, Release 4.0", 205 September 2020, 206 . 208 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 209 and A. Bierman, Ed., "Network Configuration Protocol 210 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 211 . 213 Acknowledgments 215 The work of L.M. Contreras has been partly funded by the European 216 Commission through the H2020 project 5GROWTH (Grant Agreement no. 217 856709). 219 Authors' Addresses 221 Young Lee 222 Samsung Electronics 223 Seoul 224 South Korea 226 Email: younglee.tx@gmail.com 228 Xufeng Liu 229 Volta Networks 231 Email: xufeng.liu.ietf@gmail.com 232 Luis M. Contreras 233 Telefonica 234 Ronda de la Comunicacion, s/n 235 Sur-3 building, 3rd floor 236 Madrid 28050 237 Spain 239 Email: luismiguel.contrerasmurillo@telefonica.com 240 URI: http://lmcontreras.com/