I would rather use scripts then CLI as Brian pointed out but on the other hand this project will hurt nobody as long as it’s built on top of the REST APIs. So in my mind this comes down to who wants to put resources on this. I guess what you are hearing is that some companies won’t … .
Oliver > On May 9, 2017, at 12:36 PM EDT, Haiby, Ranny (Nokia - US/San Jose USA) > <ranny.ha...@nokia.com> wrote: > > Hi, > > I was about to vote in favor of putting this to a rest then I realized we may > not be thinking the same thing when it comes to CLI. > > If the CLI is a parallel interface to the REST API then it definitely makes > no sense to have one. > > If, however, a CLI is a *wrapper* on top of the API, then based on past > experience it may serve us best to have one. Taking the OpenStack example, > the CLI provides a simplified way to perform actions, and when used by > scripting tools, makes such scripts simple and readable. Consider an action > such as creating a VM that boils down to: > $ openstack server create --flavor FLAVOR_ID --image IMAGE_ID --key-name > KEY_NAME \ > --user-data USER_DATA_FILE --security-group SEC_GROUP_NAME --property > KEY=VALUE \ > INSTANCE_NAME > > Where as building the curl command line that will do the same action can be > much more cumbersome and error prone. > > I believe that if we don’t create a CLI wrapper, there will be multiple such > wrapper libraries created by many parties, and we will miss the benefit of > the community creating it once. > > Ranny. > > From: onap-tsc-boun...@lists.onap.org > [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Kanagaraj Manickam > Sent: Tuesday, May 9, 2017 9:06 AM > To: Ramkumar Venketaramani <rvenketar...@vmware.com> > Cc: t...@lists.onap.org > Subject: Re: [onap-tsc] Project Proposal: ONAP CLI > > Thank you all for providing the feedback. > > Dear TSC team, > Based on the comments received, I feel that community is not much interested > in it and does not feel as high priority project for this release. So I > think, we could park this project proposal in backlog and could re-visit in > later release, on need basis. > > But, Pls let me know if needs to be worked out for R1. Thanks. > > Regards > Kanagaraj M > > > > > > On Tue, May 9, 2017 at 7:00 PM, Ramkumar Venketaramani > <rvenketar...@vmware.com> wrote: > I would recommend a REST based approach as well. > > Regards, > > Ram > > From: <onap-tsc-boun...@lists.onap.org> on behalf of Dhananjay Pavgi > <dp00476...@techmahindra.com> > Date: Tuesday, May 9, 2017 at 5:59 AM > > To: "FREEMAN, BRIAN D" <bf1...@att.com>, Kanagaraj Manickam > <kanagaraj.manic...@huawei.com>, "t...@lists.onap.org" <t...@lists.onap.org> > Subject: Re: [onap-tsc] Project Proposal: ONAP CLI > > Spot on, Brian. You got it. > > thanks & regards, > Dhananjay Pavgi > Mobile : +91 98220 22264 > <image001.png> <image002.jpg> > www.techmahindra.com Platinum Member. Visit : > http://www.onap.org > > From: FREEMAN, BRIAN D [mailto:bf1...@att.com] > Sent: Tuesday, May 09, 2017 10:55 PM > To: Dhananjay Pavgi <dp00476...@techmahindra.com>; Kanagaraj Manickam > <kanagaraj.manic...@huawei.com>; t...@lists.onap.org > Subject: RE: Project Proposal: ONAP CLI > > > Scripting is useful but shell scripts that wrap curl functions are the > method we are pushing folks towards. Separate CLI and REST API’s are > generally a waste. With automation we see less pressure to have a CLI and > more a need to be able to get the work done and CURL/POSTMAN are the tools of > the new devops environment. > > Brian > > From: onap-tsc-boun...@lists.onap.org > [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Dhananjay Pavgi > Sent: Tuesday, May 09, 2017 6:32 AM > To: Kanagaraj Manickam <kanagaraj.manic...@huawei.com>; t...@lists.onap.org > Subject: Re: [onap-tsc] Project Proposal: ONAP CLI > > Thanks. Don’t agree with the comment on GUI can’t be used in DevOps. Wonder > how CLI would be easier in any which ways to work with clumsy yaml/TOSCA > files. CLI was good for short service commands. > > While it would still make sense to have it for VNFs; for some of the reasons > sighted below. For Network Automation Platform like ONAP; still ponder over > it’s necessity. > > thanks & regards, > Dhananjay Pavgi > Mobile : +91 98220 22264 > <image001.png> <image002.jpg> > www.techmahindra.com Platinum Member. Visit : > http://www.onap.org > > From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com] > Sent: Tuesday, May 09, 2017 7:37 PM > To: Dhananjay Pavgi <dp00476...@techmahindra.com>; t...@lists.onap.org > Subject: RE: Project Proposal: ONAP CLI > > Thanks for sharing your comments. Pls find my inputs below: > > CLI has its own advantages over GUI in following aspects: > • ONAP Continuous integration (CI), where we want to perform various > ONAP operations, CLI will be very handy option. This is applicable to 3rd > party CI as well. > • While GUI is the preferred interface for end-user, back-end operators > and admin always prefer CLI (it’s an industry trend !) as its simpler, > faster. > • Installation scripting, VNF boot scripting with ONAP. > • Dev testing … integration testing. > • OSS/BSS products would want to perform any automation on top of ONAP, > it could go either with CLI or SDK. > In short, GUI can’t be used in devops environment, and CLI fills the gap. > > In addition, CLI provides an alternate option to GUI, for operating back > ONAP functionalities. > > And to feel the importance of CLI, Pls refer some existing active automation > projects in industry, given here: > • OpenStack heat provides CLI ‘openstack stack’ > • Cloudify provides CLI ‘cfy’ > • ODL provides CLI with different commands > > So IMHO, > - CLI does compliment GUI and does not defeat it. > - Considering ONAP as platform, CLI should be part of it. > > Regards > Kanagaraj M > > *************************************************************************************** > 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！************************************************************************************** > > *************************************************************************************** > This e-mail and its attachments contain confidential information from HUAWEI, > which is intended only for the person or entity whose address is listed > above.Any use of the information contained herein in any way (including, but > not limited to, total or partial disclosure, reproduction, or > dissemination) by personsother than the intended recipient(s) is prohibited. > If you receive this e-mail in error, please notify the sender by phone or > email immediately and delete it! > *************************************************************************************** > > From: Dhananjay Pavgi [mailto:dp00476...@techmahindra.com] > Sent: Tuesday, May 09, 2017 2:09 PM > To: Kanagaraj Manickam; t...@lists.onap.org > Subject: RE: Project Proposal: ONAP CLI > > Do we really need CLI. Defeats the purpose of automation and GUI/Portals made > available at each layer. > > thanks & regards, > Dhananjay Pavgi > Mobile : +91 98220 22264 > <image001.png> <image002.jpg> > www.techmahindra.com Platinum Member. Visit : > http://www.onap.org > > From: onap-tsc-boun...@lists.onap.org > [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Kanagaraj Manickam > Sent: Tuesday, May 09, 2017 6:36 PM > To: t...@lists.onap.org > Subject: [onap-tsc] Project Proposal: ONAP CLI > > Dear Team, > > In ONAP, Command-Line Interface (CLI) is not available. So I would like to > propose the new project to provide ONAP CLI, by using model-driven CLI > framework available in Open-O. > Please find the proposal at https://wiki.onap.org/display/DW/ONAP+CLI And let > me know your review comments. Thanks. > > Regards > Kanagaraj M > > *************************************************************************************** > 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！************************************************************************************** > > *************************************************************************************** > This e-mail and its attachments contain confidential information from HUAWEI, > which is intended only for the person or entity whose address is listed > above.Any use of the information contained herein in any way (including, but > not limited to, total or partial disclosure, reproduction, or > dissemination) by personsother than the intended recipient(s) is prohibited. > If you receive this e-mail in error, please notify the sender by phone or > email immediately and delete it! > *************************************************************************************** > > ============================================================================================================================ > Disclaimer: This message and the information contained herein is proprietary > and confidential and subject to the Tech Mahindra policy statement, you may > review the policy at http://www.techmahindra.com/Disclaimer.html externally > http://tim.techmahindra.com/tim/disclaimer.html internally within > TechMahindra. > ============================================================================================================================ > > _______________________________________________ > ONAP-TSC mailing list > ONAP-TSC@lists.onap.org > https://lists.onap.org/mailman/listinfo/onap-tsc > > > _______________________________________________ > ONAP-TSC mailing list > ONAP-TSC@lists.onap.org > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4&m=QPeZRa2RlJRT5Wk_WLABTqcKY5bB5kYvutYTXn6QXfI&s=dUCRJK0qD-rJ6OdWCbhzbUT19_tFDek5ga-g7y7xbD0&e= > _______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
