Hi Victor,
Let us discuss today. But, I thought I will provide my initial thoughts on the
scope of the K8S plugin activities:
1. Defining the API between Multi-Cloud & Test SO/VF-C : WE can get some
ideas from SOL003 and follow this API as much as possible. WE just need to
implement only subset of the API for this POC. One good thing to follow this
API is that when SO moves to support SOL003 VNFMs, there would be minimal
changes in SO to support Multi-Cloud API. We also may need to add some
additional elements to JSON body of these API requests to pass artifact
references, other meta data (such as cloud region ID and compute profiles for
the VNF etc…)
a. APIs:
i. Instantiate VNF
ii. Terminate VNF
instance
iii. Identify others that
are MUST.
iv. Scale-out, Other VNF
LCMs can be done later.
2. Multi-Cloud broker changes to accept above API and passing those API
requests to right plugin (in this case K8S plugin and in future more plugins
are possible).
3. K8S Plugin:
a. K8S site registration related changes (if any) : Is ESR registration of
cloud-region good enough or are any changes required in that?
b. Onboard time:
i. Getting hold of
artifacts from SDC and storing them locally.
c. Run time:
i. As part of VNF
instantiation:
1. Ability to refer to artifacts from the references.
2. Translation from artifacts + metadata to
a. Set of K8S API (for compute and storage)
b. Set of OVN API (for networking)
c. Other CNIs (if time permits)
3. Getting the result and adding the result to A&AI DB. (Need to check if
there are any changes required there)
On Kubernetes reference cloud:
- We will go with bare-metal container clouds for now.
- Supporting Azure/GCP/IBM/AWS container support is for future.
- Cloud stack to have:
o K8S
o OVN
o Virtlet
o SRIOV (if time permits)
o Flannel (if time permits)
- EdgeXFoundry containers
- Firewall VM
- Router Container image creation.
Thanks
Srini
From: Morales, Victor
Sent: Monday, June 4, 2018 4:49 PM
To: Addepalli, Srinivasa R <[email protected]>;
[email protected]; Munish Agarwal <[email protected]>;
Shankar, Shashank Kumar <[email protected]>; Ramki Krishnan
<[email protected]>; Seshu m <[email protected]>; Yeleswarapu, Ramamani
<[email protected]>; HU, BIN <[email protected]>
Subject: Re: [coe] Meeting's time update
Good idea Srini,
I started doing the breakdown of the activities for this project. From my
perspective, there are two main efforts:
1. MultiCloud/k8s plugin:
2. Kubernetes Reference Deployment
Therefore, the agenda for tomorrow’s meeting is:
· Definition and scope of previous two efforts.
· Initial draft of the activities identified.
· Virtlet or KubeVirt?
· Swagger API or OpenAPI
Regards,
Victor Morales
From: "Addepalli, Srinivasa R"
<[email protected]<mailto:[email protected]>>
Date: Monday, June 4, 2018 at 4:25 PM
To: Victor Morales <[email protected]<mailto:[email protected]>>,
"[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>, Munish
Agarwal <[email protected]<mailto:[email protected]>>,
"Shankar, Shashank Kumar"
<[email protected]<mailto:[email protected]>>,
Ramki Krishnan <[email protected]<mailto:[email protected]>>, Seshu m
<[email protected]<mailto:[email protected]>>, "Yeleswarapu,
Ramamani"
<[email protected]<mailto:[email protected]>>, "HU,
BIN" <[email protected]<mailto:[email protected]>>
Subject: RE: [coe] Meeting's time update
Thanks Victor.
Please add the activity list for tomorrow meeting.
Thanks
Srini
From: Morales, Victor
Sent: Monday, June 4, 2018 4:21 PM
To: [email protected]<mailto:[email protected]>; Munish
Agarwal <[email protected]<mailto:[email protected]>>;
Shankar, Shashank Kumar
<[email protected]<mailto:[email protected]>>;
Ramki Krishnan <[email protected]<mailto:[email protected]>>; Seshu m
<[email protected]<mailto:[email protected]>>; Yeleswarapu,
Ramamani
<[email protected]<mailto:[email protected]>>;
Addepalli, Srinivasa R
<[email protected]<mailto:[email protected]>>; HU,
BIN <[email protected]<mailto:[email protected]>>
Subject: [coe] Meeting's time update
Howdy,
According to the results of the last survey, we decided to update the time for
this meeting [1]. The new time will be at 13:00hrs PST, the zoom’s link used
for this will remain the same. In the other hand, I’ll be glad to discuss some
ideas about the implementation of this tomorrow.
Regards,
Victor Morales
[1] https://wiki.onap.org/pages/viewpage.action?pageId=16009184
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
