| commit | 4adfb00881b29da4e3cfad640535c4d341c553cb | [log] [tgz] |
|---|---|---|
| author | Svetoslav Neykov <svetoslav.neykov@cloudsoftcorp.com> | Thu Jul 14 23:43:03 2016 +0300 |
| committer | Svetoslav Neykov <svetoslav.neykov@cloudsoftcorp.com> | Thu Jul 14 23:43:03 2016 +0300 |
| tree | e38b7cf21b21ce02cba9d08fa5bcd4c5e807f26a | |
| parent | e54c02dace4d02d3edae194892491a1416d0f592 [diff] | |
| parent | e04af0b30c49522b2e5950ad0ecb7e6b3082614d [diff] |
Closes #23 Update link to README. File was moved in https://github.com/apache/brooklyn-client/commit/6fc8a1ee098fa5a4cd7d8fe726dcc7354abaf15a
A command line client for Apache Brooklyn.
The CLI tool is written in Go and should be obtained and built as a standard Go project. You will need the following tools to build it:
Optional:
Maven (used by the Brooklyn build process)
Maven (see note below on the Brooklyn build process)
Go is very particular about the layout of a source tree, and the naming of packages. It is therefore important to get the code from github.com/apache/brooklyn-client and not your own fork. If you want to contribute to the project, the procedure to follow is still to get the code from github.com/apache/brooklyn-client, and then to add your own fork as a remote.
go get github.com/apache/brooklyn-client/br
The CLI has a small number of dependencies, notably on urfave/cli. To manage the version of dependencies, the CLI code currently uses Glide. The dependencies are installed to the top level ‘vendor’ directory.
go get github.com/Masterminds/glide cd $GOPATH/src/github.com/apache/brooklyn-client glide install
Just use the regular Go build commands.
The code includes a test script in the test directory. This deploys a Tomcat server on a location of your choice and runs a number of tests against it, to verify that the br commands perform as expected. To use this you must edit the file “test_app.yaml” to change the location to your own value, and then invoke the test script like the following, where the username and password need only be supplied if Brooklyn requires them:
sh test.sh http://your-brooklyn-host:8081 myuser mypassword
Note, the tests are not yet comprehensive, and contributions are welcome.
For consistency with the other sub-projects of the overall Brooklyn build, Maven is used to perform the build when brooklyn-client is built as one of the sub-modules of Brooklyn. Most of the work is delegated to the release/build.sh script, which cross-compiles the code for a number of platform-architecture combinations.
Invoke the build script via Maven with one of
mvn clean install build for all supported platformsmvn -Dtarget=native clean install build for the current platformmvn -Dtarget=cross -Dos=OS -Darch=ARCH clean install build for platform with operating system OS and architecture ARCHNOTE This does not build the code into your usual GOPATH. To allow the project to be checked out along with the other Brooklyn submodules and built using Maven, without any special treatment to install it into a separate GOPATH location, the Maven build makes no assumption about the location of the project root directory. Instead, the Maven target directory is used as the GOPATH, and a soft link is created as target/src/github.com/apache/brooklyn-cli to the code in the root directory.
This builds the requested binaries into the “target” directory, each in its own subdirectory with a name that includes the platform/architecture details, e.g. bin/linux.386/br. The build installs a maven artifact to the maven repository, consisting of a zip file containing all the binaries. This artifact can be referenced in a POM as
<groupId>org.apache.brooklyn</groupId> <artifactId>brooklyn-client-cli</artifactId> <classifier>bin</classifier> <type>zip</type> <version>...</version>
See instructions in the included Runtime README file.
Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.