- Added background reference parameter to layout command
- send correct location data to client for devices, hosts
Change-Id: Ic00bda76f4e4bc8d3e23e07a08f3bc5367ec85a9
There was an issue when OCN was set to localhost. As part of Net-Smoke,
the command 'mn -c' is run which removes '/tmp/*.log'. This potentially
caused some tests to fail.
Change-Id: If68c184902b994e1ee38ea775c378ce29cdb891f
(cherry picked from commit a67dc45535c7b0b8ea6f246a10c1f2e4e18abb83)
- Add new '-s partition_size' argument to allow selecting the size of the
partitions in a cluster
- Add new -n' argument to allow selecting the number of partitions in a
cluster
- Use argparse to parse arguments
- Removed unused imports
Change-Id: Ie8ff4a9ef78bea023b32a4cf1c108ede478a8ba0
Use rsync to push bits (ONOS tar contents), when
environment variable USE_RSYNC is set to true.
This enables sending only changed .jar, now whole ONOS tar ball.
+ Minor optimization to reuse build machine to remote host ssh session
push bits:
1) unpackage ONOS tar to tmp stage dir
2) rsync local stage to remote stage /tmp/$ONOS_BITS
3) package ONOS tar equivalent at remote node
push bits via proxy:
1) rsync: build <=> proxy
2) scp : proxy => cell nodes (tar packaged at proxy)
3) rsync: build <==========> cell nodes (almost no-op)
Known limitation:
- rsync at Step 3 is triggered since
repackaging same content remotely result in
tar ball with different hash value.
(Probably due to directory timestamp/uid difference)
- automatically installing rsync
only supported for debian/ubuntu
Change-Id: Ibc9013b973c312798d2c36e7d25f5274f085b39f
1. Change ownership of /onos/apps
onos-service needs write access to onos/apps/foo in order to activate
an app. This also means that ONOS itself could also activate/deactivate,
modify, or reinstall apps, which seems a bit dodgy but is probably
intended.
2. Fix sudo command line
The -b option was in the wrong place, breaking sudo on systems where
we use sudo to start onos (e.g. older debian or centos.)
3. Redirect stderr of 'type daemon' command
We want to detect whether the 'daemon' function/script is available
in init.d enviroments that support it, and we do so using the type
command. Previously we didn't redirect stderr, so this resulted
in a confusing error message being sent to stderr of whoever is
invoking the script.
4. onos.conf has changed to be more consistent with onos.initd
Previously onos.conf ignored $ONOS_GROUP and had a slightly different
structure.
5. onos.service has been added for systemd-based systems
This initial version of onos.service calls /etc/init.d/onos to start
and stop ONOS. In the future we may be able to call onos-service
directly, but we will need to make sure that permissions are set up
correctly so that onos-service can activate apps and so that ONOS
itself can write its log files.
6. A README has been added
7. Update the onos-install and onos-uninstall scripts
Related Jira issue: ONOS-5550
Change-Id: Ie72775f1d0a4082af9c5ea9b13999c427c15ffe0
- onos-package
SC2071: > is for string comparisons. Use -gt instead.
- ./tools/build/onos-blackduck-zip
SC1035: You need a space after the [ and before the ].
Change-Id: I409b4a181e9cd49795afbdaa68b68c26413b9401
It seems to be mandatory to have the Dockerfile here if we want to build
from the source in the repo in a Dockerhub automated build.
ONOS-5832
Change-Id: I01536ae9476987f20df03560834b1adcf0b6aec0
- stc, etc. relied on the behavior that source-ing
envDefaults will create symlink to buck artifacts
Change-Id: Ic5039dbaf18f0eb36b1bb7a41dbecc8a5f974f19
