HI Lingli,
Following is one proposal for VF-C Project.
Description: Supporting VNF Initial configuration in VF-C GVNFM
Additional Information: Implement VNF Initial configuration function via SSH in
VF-C which includes SSH remote connection via username/password, or auth key,
SSH
Thanks Huabing.
Sorry for missing the disccussion.
> Lv Bo – can you please confirm urgently your engagement, helping AAI team on
> Security issues, CII badging? Thank you.
Ok, I will try my best to handle the aai/esr issues. Thanks for your pre works.
I will be familiar with the
Hi folks,
Loop Lv bo in.
It seems that Lv bo isn't aware of this discussion because he doesn't subscribe
to the TSC mailinglist.
BR,
Huabing
原始邮件
发件人：CatherineLEFEVRE
收件人：onap-tsc@lists.onap.org ;
抄送人：FORSYTH, JAMES ;
日 期 ：2018年10月18日 05:28
主 题 ：Re: [onap-tsc] TSC
Thank you Kenny for bringing this issue to our attention.
Thank you Alexis for your feedback.
Speaking to Jimmy, AAI PTL, I understand that no new code was released related
to AAI/ESR as part of the Casablanca release.
The current challenge is to progress on the Security issues (even if the code
One case that wasn't in Chaker's list, but might trigger some discussion
would be:
An elected TSC member representing Operator A takes a job with a Vendor A
that does not have a representative on the TSC.
As written, the charter proposal says that the TSC member keeps his/her
seat and
Hi Steve,
Thanks for the clarifications
Regards,
Chaker
From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of
Stephen Terrill
Sent: Wednesday, October 17, 2018 2:59 PM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] JIRA TSC-1 "Update TSC Chart to address how to
Yes Mike, no problem, but not next week L
What about the week after next?? We are in CET time zone…
The main player is Michal here, he will provide you with all the info and also
work with you on further development
thx
/robert
From: onap-tsc@lists.onap.org
Hi Chaker,
Discussion is always welcome - I wanted to point out though that I believe that
the cases you proposed are covered in the proposal, which I will clarify below:
1. If an elected TSC member from an Operator A changes jobs and moves to
Operator B that's already represented on the
Hi all,
I had sent the attached email back in September proposing a few more cases to
consider so that we don't have to work the same exercise again when/if they do
occur.
I'd like to include them in the discussion tomorrow and decide as a team on how
we move forward.
Thanks,
Chaker
From:
Thank you Catherine for your kind comments…
Dear TSC Members,
If you guys think we should start with our SI under OOM project umbrella,
certainly we will do that.
Let’s make a sub-project there for now and then see if and how we can fully
integrate with OOM approach…
Is that
Hi,
When it comes to define new committers for a given project, what I’ve seen
happening before, and it worked fairly well, is to have the PTL of the project
start a committer election of a week or two.. Contributors to the project can
self-nominate themselves, and once nomination period is
Hi,
As TSC-1 jira is on the TSC agenda, a proposal has been uploaded. While this
and previous versions have been shared with the Task force, there is still
ongoing discussion however I thought that it fair to share the latest proposal
with the TSC members before the meeting this week.
It is
Hi Viswa,
Yes, agree, we should analyze requirements, impact and scope before deciding if
we need new project or not.
Certainly, at least requirements sync would be necessary between the two (OOM
and SI).
And yes, your understanding is right, currently working OOM deployment is
Hi Robert,
I second the idea of having standalone / offline mode of ONAP installation.
It is indeed a requirement for us as we don't really enjoy the luxury of
open internet even in our labs.
We have similar version of offline repos ( nexus, mvn, cache ) to minimise
the dependency on external
Hi Steve,
We are open for suggestions…
IHMO, it would not hurt to have 2 different installers to give options for
customers. i.e.: Openstack for example provides multiply installers.
Our approach is clearly targeting narrow carrier requirements, where
deployments are predictable,
15 matches
Mail list logo
