proposed text for tosca reqts update to #VNFRQTS for Casablanca #vnfrqts
WRIGHT, STEVEN A
Could you respond?
(preferably on the wiki?)
Can we separate any controversial material so that we can proceed with the remaining stable items
From: Gaoweitao (Victor, Cloudify Network OSDT) <victor.gao@...>
Sent: Wednesday, September 26, 2018 8:09 AM
To: WRIGHT, STEVEN A <sw3588@...>; MAYER, ANDREW J <am803u@...>
Subject: 答复: proposed text for tosca reqts update to VNFRQTS for Casablanca
Ok, I reviewed this yesterday evening and I found following issue:
1. R-35851: I think the deployment aspect should be removed cause the R2 and R3 DM is same and never talk about the deployment aspects, this should be discussed in modeling subcommittee first.
2. From the requirements perspective, we don’t need define the detail parameters inside the requirements. So may I suggest just put the SOL001 link there rather than define this in requirements.
3. The tables also have some inconsistence about the DM .( e.g. ChangeVnfFlavourOpConfig and ChangeExtVnfConnectivityOpConfig) never discussed inside modeling subcommittee, so may I suggest we put this into modeling subcommittee first and get the agreements.
Can you check it by Thursday COB ? that would let us try to get it into the system on Friday.
We can always raise a bug report if you later discover some problem.
Could you give me more times to review this? Cause now I’m attending ONS, need some time to review this.
Andy Mayer, Ph.D. | PMTS, Network Cloud and Infrastructure | AT&T Labs | Phone: +1 (732) 420-9945 | am803u@...
Since your two groups (VNFSDK and Information model) seem to have the most interest in this topic, can you give a +1 to this wiki page if you are generally happy with the inclusion of this material in the VNF RQTS document for Casablanca?
NB we can always raise a BUG ticket on individual requirements if there are still open issues?