Bump drools-pdp master to 1.8.0-SNAPSHOT - policy/drools-pdp

diff options

author	Jim Hahn <jrh3@att.com>	2020-10-27 15:06:03 -0400
committer	Jim Hahn <jrh3@att.com>	2020-10-27 15:06:45 -0400
commit	f44515d3d0beb946791bcfbcf78df4fd8974b18a (patch)
tree	18632660cfacb3c2a16fab37e890e9e855fab565 /feature-drools-init
parent	f5710f0b61a24a2a2b03f272e1a9e72bcef31d40 (diff)

Bump drools-pdp master to 1.8.0-SNAPSHOT

Bumping minor version now that guilin branch has been created. Also repointed to snapshot versions for dependencies. Issue-ID: POLICY-2875 Change-Id: Ic3d5b96e610db0487ce316a9397d2f9ecb04bda6 Signed-off-by: Jim Hahn <jrh3@att.com>

Diffstat (limited to 'feature-drools-init')

-rw-r--r--

feature-drools-init/pom.xml

1 files changed, 1 insertions, 1 deletions

## **Quick Start Guide** This is a quick start guide describing how to deploy ONAP on Kubernetes using Helm. Pre-requisites: - Your Kubernetes environment must be available. For more information see, [ONAP on Kubernetes](https://wiki.onap.org/display/DW/ONAP+on+Kubernetes). - Deployment artifacts are customized for your location. ### **Deploy ONAP Instance** Step 1. Clone the OOM repository from ONAP gerrit: ``` > git clone http://gerrit.onap.org/r/oom > cd oom/kubernetes ``` Step 2. Customize the oom/kubernetes/onap parent chart, like the values.yaml file, to suit your deployment. You may want to selectively enable or disable ONAP components by changing the subchart **enabled** flags to *true* or *false*. The .yaml file for OpenStackEncryptedPassword should be the MSO ecnrypted value of the openstack tenant password ``` Example: ... robot: # Robot Health Check enabled: true sdc: enabled: false sdnc: enabled: false so: # Service Orchestrator enabled: true ... ``` Step 3. To setup a local Helm repository to serve up the local ONAP charts: [Note: ensure helm init has been executed on the node, or run helm init --client-only] ``` > helm serve & ``` Note the port number that is listed and use it in the Helm repo add as follows: ``` > helm repo add local http://127.0.0.1:8879 ``` Step 4. Build a local Helm repository (from the kubernetes directory): ``` > make all ``` Step 5. Display the charts that are available to be deployed: ``` > helm search -l NAME VERSION DESCRIPTION local/appc 2.0.0 Application Controller local/clamp 2.0.0 ONAP Clamp local/onap 2.0.0 Open Network Automation Platform (ONAP) local/robot 2.0.0 A helm Chart for kubernetes-ONAP Robot local/so 2.0.0 ONAP Service Orchestrator ... ``` **Note:** Setup of this Helm repository is a one time activity. If you make changes to your deployment charts or values be sure to use **make** to update your local Helm repository. Step 6. Once the repo is setup, installation of ONAP can be done with a single command: ``` > helm install local/onap --name dev --namespace onap ``` **Note:** the **--namespace onap** is currently required while all onap helm charts are migrated to version 2.0. After this activity is complete, namespaces will be optional. Use the following to monitor your deployment and determine when ONAP is ready for use: ``` > kubectl get pods --all-namespaces -o=wide ``` #### **Cleanup deployed ONAP instance** To delete a deployed instance, use the following command: ``` > helm del dev --purge ``` For more information on OOM project documentation, refer to: - [Quick Start Guide on Wiki](https://wiki.onap.org/display/DW/ONAP+Operations+Manager+Project#ONAPOperationsManagerProject-QuickStartGuide) - [Quick Start Guide on readthedocs](http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/OOM%20Project%20Description/oom_project_description.html#quick-start-guide)


context:
space:
mode: