-
Type: Story
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: 1.2.0
-
Fix Version/s: 1.2.0
-
Component/s: None
-
Labels:
-
Epic Link:
-
Sprint:Cardinal Sprint 2 (4/6-4/17)
---------- Forwarded message ----------
From: Thomas Vachuska <tom@onlab.us>
Date: Wed, Apr 8, 2015 at 10:43 AM
Subject: Re: [onos-dev] add-intent CLI to include appId option
To: Hari Krishna <hari@onlab.us>
Cc: "onos-dev@onosproject.org" <onos-dev@onosproject.org>
Agreed. Is there a user story for this in Jira already?
On Apr 8, 2015, at 10:40 AM, Hari Krishna <hari@onlab.us> wrote:
Hi All,
Currently most of the intents that are being tested are installed via CLI and appId
for those is set to 'appId=org.onosproject.cli', but the 'app-ids' CLI issued
on ONOS displays around 18 app-ids. I do not know if all those apps would be installing
intents, but it would be great if the CLI could allow setting the proper appId during intent install.
For example:
type=HostToHostIntent, appId=org.onosproject.cli
type=PointToPointIntent, appId=org.onosproject.gui
type=PointToPointIntent, appId=org.onosproject.sdnip
Note: Remove intent already uses specifying the appId.
onos> app-ids
id=0, name=org.onosproject.cli
id=1, name=org.onosproject.bgprouter
id=3, name=org.onosproject.demo
id=4, name=org.onosproject.election
id=5, name=org.onosproject.null
id=6, name=org.onosproject.intentperf
id=7, name=org.onosproject.proxyarp
id=8, name=org.onosproject.config
id=9, name=org.onosproject.openflow
id=10, name=org.onosproject.metrics
id=11, name=org.onosproject.optical
id=12, name=org.onosproject.fwd
id=13, name=org.onosproject.mobility
id=14, name=org.onosproject.sdnip
id=15, name=org.onosproject.net.intent
id=16, name=org.onosproject.provider.lldp
id=17, name=org.onosproject.provider.host
id=18, name=org.onosproject.gui
onos>
-Hari