From: velandy Date: Mon, 13 Jun 2016 14:37:13 +0000 (+0200) Subject: New Feature Request: Support for VIM Accounts X-Git-Url: https://osm.etsi.org/gitweb/?p=osm%2FFeatures.git;a=commitdiff_plain;h=6c4503c1e05fdec19f30c2c15f22acc135693238 New Feature Request: Support for VIM Accounts Change-Id: I32b4a1fb2b900a2c1217db7b66b382425e1a9171 --- diff --git a/Release1/support-vim-account.md b/Release1/support-vim-account.md new file mode 100644 index 0000000..e1c6d5f --- /dev/null +++ b/Release1/support-vim-account.md @@ -0,0 +1,31 @@ +# Support for VIM account and RO account # + +## Proposer ## +Rajesh Velandy (RIFT.io) + +## Type ## +**Feature** (do not modify) + +## Target MDG/TF ## +UI, SO, RO + +## Description ## +Release 0 account management has some flaws in how it treats RO and VCA accounts, +* The RO account is added as a cloud account which is incorrect - RO account is a different account + than "cloud" which is more a "VIM" account. +* The use of term "cloud account" can be confusing. +* The VCA account is limited to a single account per launchpad. + +The feature proposes the following changes, +1. Add support for a new account type - RO accounts. +2. Change the term "cloud account" to "vim account" in the UI. +3. Change the VCA account to a single account per launchpad. + +## Demo or definition of done ## +Should demonstrate the following: +1. A user should be able to configure openMANO as an RO account in launchapd. +2. A user should be able to configure one or more VIM accounts in launchpad. +2. When a VIM account is provisioned in the system, the UI/SO should pass the account details to + the RO. +3. The VCA account should be limited to a single account per launchpad. +