Chapter 01 (Terminology fixes) #60

pgoyal01 · 2019-07-05T13:41:03Z

Made changes to some of the terms.
Still need to be resolved:

Do Instance Types include sizing (number of CPUs, RAM, etc.) information or are they just the Basic, Network-Intensive, etc. Types?
Still need to fix the SW/HW Profile and Configuration terms.

Made changes to some of the terms. Still need to be resolved: 1. Do Instance Types include sizing (number of CPUs, RAM, etc.) information or are they just the Basic, Network-Intensive, etc. Types? 2. Still need to fix the SW/HW Profile and Configuration terms.

demels · 2019-07-05T13:56:10Z

I suggest to remove the abbreviation vAPP and use the definition for Virtual Application as defined in ETSI GS NFV 003:

Virtual Application (VA): more general term for a piece of software which can be loaded into a Virtual Machine
NOTE: A VNF is one type of VA.

@pgoyal01

I think @pgoyal01 you have mistakenly brought the original Principles text in here. fix it.

rabiabdel · 2019-07-05T15:46:22Z

@pgoyal01 i think you have mistakenly replaced the principles section in this pull request with the original text, i have modified it.

rabiabdel · 2019-07-05T16:44:55Z

There is an issue related to this: #58

doc/ref_model/chapters/chapter01.md

hdamker · 2019-07-05T18:25:39Z

@pgoyal01 I have some further change proposals, please integrate them into your pull request if you agree:

Delete the abbreviation "vApp" completely, it is vendor specific. If you search for vApp you will find almost only pages from or about VMWare (try "vAPP NFV" or "vApp OpenStack")
VNFs are built from VNF Components, VNFC.e.g. VMs => VNFs are built from VNF Components (VNFC), a VNFC single instance is a 1:1 mapping to e.g. a VM or Container
NFVi => NFVI
Workload: Workload refers to software running on top of NFVI resources such as VMs or Containers => Workload: another general term referring to software running on (virtualized) compute resources. Most relevant workload categories in context of NFVI are: ...
- [Background: i see this term as the most general one for the software running on NFVI (or other virtualization/cloud infrastructure. The listed subcategories under workload are only important examples, but not exhaustive]
the definition of "Instance type" is not correct from my perspective. Previous one was better (see also comment from @rabiabdel)
Tenant (Internal) Networks (a.k.a. vApp Network): delete "(a.k.a. vApp Network)", see above.
Compute Node: abstract definition of a physical or virtual server: delete "or virtual server" [I have never seen the term used for a virtual server, it is always referring to the hardware node from my perspective]

ASawwaf · 2019-07-06T12:24:50Z

@hdamker
I totally agree on most of your modification, Just small comment on:

VNFs are built from VNF Components, VNFC.e.g. VMs => VNFs are built from VNF Components (VNFC), a VNFC single instance is a 1:1 mapping to e.g. a VM or Container

Sawaf : VNFs are built from one or more VNF component , and in most cases, the VNFC is a single VM or container

Sawaf : Workload: it is a software ( VNF or APP ) that running over NFVI and consume the NFVI resources

hdamker · 2019-07-06T12:32:58Z

@ASawwaf: +1 for the simplified version for VNFs, I like it.
Also for Workload ... just not "APP" in it ... instead "(VNF or virtualized application)"

ASawwaf · 2019-07-06T13:01:25Z

agreed

pgoyal01 · 2019-07-06T22:56:06Z

@rabiabdel, @hdamker and @ASawwaf

Thanks all. Will make some of the suggested changes.

Original Definition Instance Type: "The type of NFVI of which the VM is expected to run on. It directly maps to the combination of the underlying NFVI SW Profile and NFVI HW Profile." Issues: what does "type of NFVI" mean -- since it refers to VM is expected to run on it implies the physical hardware? what is the combination of NFVI SW Profile and NFVI HW Profile? Maybe my poor wording of the sentence: "defines the capabilities of the physical compute server that the virtual compute resource can run on." ----> capabilities of the virtual compute resource and these capabilities must match the configuration (capabilities) of the physical compute server on which, say, the VM is going to be running on. And as I stated in my comments there are issues with the Profile definitions also.

VNFC -- I like Ahmed's "in most cases."

Compute node will use the ETSI 1.4.1 (2018-10).
WIll delete vApps -- will need to be deleted from other Chapters.

I will make the changes except for Instance Type until we can get a clearer definition.

Updates some of the definitions as per suggestions. Still need cleanup on: Instance Type, Flavour, HW/SW Profile.

ASawwaf · 2019-07-07T21:10:23Z

@pgoyal01 , my suggestion to use Openstack definition ( with small modification ) which is " A running VM, or a VM in a known state such as suspended, that can be used like a hardware server "

my defination: It is running VM , or VM in a Known state such as (run, stop , suspend ) that can be used by any VNF or Virtual application with well-defined flavour which acting as dedicated hardware server

ASawwaf · 2019-07-07T21:15:51Z

the above is for Instance

for instance type:
Describes the parameters of the various virtual machine images that are available to users; includes parameters such as CPU, storage, and memory. Alternative term for flavor.

bfcohen

Agree that vAPP is not standard terminology. I am OK with using VA (virtual application) we are kind of in uncharted territory and need to create some standard terminology, and that is OK.

karinesevilla · 2019-07-08T09:52:15Z

@pgoyal01, @rabiabdel
Agree to move the definitions of instance type and compute flavours a level above.
Instance type must be independent of VM, we should replace VM by VNFC -> the type of NFVI on which VNFC is expected to run on.

rabiabdel · 2019-07-08T10:53:27Z

Hi @pgoyal01 can we please replace the sentence "physical compute server" in both instance type and compute flavour with "NFVI". Thanks

rabiabdel

the above is for Instance

for instance type:
Describes the parameters of the various virtual machine images that are available to users; includes parameters such as CPU, storage, and memory. Alternative term for flavor.

Hi @ASawwaf : instance type is not an alternative to flavour. it is a completely different term.

rabiabdel · 2019-07-08T10:52:31Z

doc/ref_model/chapters/chapter01.md

-  - **compute flavour**: defines the compute, memory, and storage capacity of a virtual compute resource. 
+  >_*Note:*_ a **VM** consists of all of the components (processor (CPU), memory, storage, interfaces/ports, etc.) of a physical computer/server. It is created using Instance Type together with sizing information or Compute Flavour. 
+- **VM Instance**: is a VM
+- **Instance type**: defines the capabilities of the physical compute server that the virtual compute resource can run on.


Hi @pgoyal01 can we please replace the sentence "physical compute server" in both instance type and compute flavour with "NFVI". Thanks

ASawwaf · 2019-07-08T12:47:23Z

@rabiaabdel, Just maybe it used interchangeably but OpenStack guys :) , also this is from openstack.org definition

Defined the terms Instance Type and Instance: Instance Type; defines the capabilities of an image available to users for the creation of a virtual compute resource; includes capabilities such as CPU, storage, and memory. Instance: is a virtual compute resource, in a known state such as running or suspended, that can be used like a physical server. NOTE: can be used to specify VM Instance or Container Instance.

rabiabdel · 2019-07-08T16:18:19Z

Hi @pgoyal01: i am not sure the relevance of an image here.

can you please revert the terminology for instance type and instance to the original definition (as it seems it is the one we agree on here). it will be great if we can get this approved tomorrow.

Changed definition of Instance Type: Instance type: specifies a set of virtualized hardware resources and capabilities used for the creation of a virtual compute on which a workload runs on; includes capability specifications such as CPU, storage, and memory. It is more in line with multiple versions: Google: A machine type is a set of virtualized hardware resources available to a virtual machine (VM) instance, including the system memory size, virtual CPU (vCPU) count, and persistent disk limits. AWS: Instance Types. When you launch an instance, the instance type that you specify determines the hardware of the host computer used for your instance. ... Amazon EC2 dedicates some resources of the host computer, such as CPU, memory, and instance storage, to a particular instance. OpenStack: Instance Type: Describes the parameters of the various virtual machine images that are available to users; includes parameters such as CPU, storage, and memory. Alternative term for flavor.

markshostak · 2019-07-09T12:08:59Z

Approved 9/7/2019 as written

rabiabdel

Approved on 9th July 2019

Update Chapter 01.md

5bf3415

Made changes to some of the terms. Still need to be resolved: 1. Do Instance Types include sizing (number of CPUs, RAM, etc.) information or are they just the Basic, Network-Intensive, etc. Types? 2. Still need to fix the SW/HW Profile and Configuration terms.

Update chapter01.md

7e2416e

I think @pgoyal01 you have mistakenly brought the original Principles text in here. fix it.

rabiabdel changed the title ~~Update Chapter 01.md~~ Chapter 01 (Terminology fixes) Jul 5, 2019

rabiabdel mentioned this pull request Jul 5, 2019

Pankaj: Create Pull Request to fix some terminologies around instance types #46

Closed

rabiabdel reviewed Jul 5, 2019

View reviewed changes

doc/ref_model/chapters/chapter01.md Outdated Show resolved Hide resolved

Update Chapter 01.md

2634ffa

Updates some of the definitions as per suggestions. Still need cleanup on: Instance Type, Flavour, HW/SW Profile.

bfcohen reviewed Jul 8, 2019

View reviewed changes

rabiabdel reviewed Jul 8, 2019

View reviewed changes

demels mentioned this pull request Jul 9, 2019

Ch 1.3.1: Replace vAPP with Virtual Application as defined in ETSI GS NFV 003, per mtg 2/7/19 #58

Closed

rabiabdel approved these changes Jul 9, 2019

View reviewed changes

rabiabdel merged commit d56d69f into anuket-project:master Jul 9, 2019

pgoyal01 deleted the patch-9 branch July 12, 2019 13:45

rabi-abdel added the Archive Archive Item label Feb 26, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Chapter 01 (Terminology fixes) #60

Chapter 01 (Terminology fixes) #60

pgoyal01 commented Jul 5, 2019

demels commented Jul 5, 2019

rabiabdel commented Jul 5, 2019 •

edited

rabiabdel commented Jul 5, 2019

hdamker commented Jul 5, 2019 •

edited

ASawwaf commented Jul 6, 2019

hdamker commented Jul 6, 2019

ASawwaf commented Jul 6, 2019

pgoyal01 commented Jul 6, 2019

ASawwaf commented Jul 7, 2019

ASawwaf commented Jul 7, 2019

bfcohen left a comment

karinesevilla commented Jul 8, 2019

rabiabdel commented Jul 8, 2019

rabiabdel left a comment

rabiabdel Jul 8, 2019

ASawwaf commented Jul 8, 2019

rabiabdel commented Jul 8, 2019 •

edited

markshostak commented Jul 9, 2019

rabiabdel left a comment

Chapter 01 (Terminology fixes) #60

Chapter 01 (Terminology fixes) #60

Conversation

pgoyal01 commented Jul 5, 2019

demels commented Jul 5, 2019

rabiabdel commented Jul 5, 2019 • edited

rabiabdel commented Jul 5, 2019

hdamker commented Jul 5, 2019 • edited

ASawwaf commented Jul 6, 2019

hdamker commented Jul 6, 2019

ASawwaf commented Jul 6, 2019

pgoyal01 commented Jul 6, 2019

ASawwaf commented Jul 7, 2019

ASawwaf commented Jul 7, 2019

bfcohen left a comment

Choose a reason for hiding this comment

karinesevilla commented Jul 8, 2019

rabiabdel commented Jul 8, 2019

rabiabdel left a comment

Choose a reason for hiding this comment

rabiabdel Jul 8, 2019

Choose a reason for hiding this comment

ASawwaf commented Jul 8, 2019

rabiabdel commented Jul 8, 2019 • edited

markshostak commented Jul 9, 2019

rabiabdel left a comment

Choose a reason for hiding this comment

rabiabdel commented Jul 5, 2019 •

edited

hdamker commented Jul 5, 2019 •

edited

rabiabdel commented Jul 8, 2019 •

edited