Code Review / oom / registrator.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: b6ccf74) | patch
Update the yaml for go lib to latest 19/19419/2
authorHuabingZhao <zhao.huabing@zte.com.cn>
Wed, 18 Oct 2017 03:25:50 +0000 (03:25 +0000)
committerHuabingZhao <zhao.huabing@zte.com.cn>
Wed, 18 Oct 2017 14:41:11 +0000 (22:41 +0800)
commite3e197dba342c76cb05aa16652682094020d8abf
tree97cbadfaaba08de782b774ae641741c997e65630tree | snapshot
parentb6ccf74fe168b2add28c83c79d07c9758239440dcommit | diff
Update the yaml for go lib to latest

Update yaml for go lib to latest and it's license has been changed
to Apache 2.
According to the upstream project, the license of go-yaml has been
updated to Apache 2:https://github.com/go-yaml/yaml/blob/v2/LICENSE,
change the reference code license within oom-registrator repo accordingly.

Issue-Id: OOM-365
Change-Id: Idce4bfda96456031a296682b0fb6e663170ec099
Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
14 files changed:
src/kube2msb/vendor/gopkg.in/yaml.v2/.travis.yml [new file with mode: 0644] blob
src/kube2msb/vendor/gopkg.in/yaml.v2/LICENSE diff | blob | history
src/kube2msb/vendor/gopkg.in/yaml.v2/README.md diff | blob | history
src/kube2msb/vendor/gopkg.in/yaml.v2/decode.go diff | blob | history
src/kube2msb/vendor/gopkg.in/yaml.v2/decode_test.go [new file with mode: 0644] blob
src/kube2msb/vendor/gopkg.in/yaml.v2/emitterc.go diff | blob | history
src/kube2msb/vendor/gopkg.in/yaml.v2/encode_test.go [new file with mode: 0644] blob
src/kube2msb/vendor/gopkg.in/yaml.v2/example_embedded_test.go [new file with mode: 0644] blob
src/kube2msb/vendor/gopkg.in/yaml.v2/parserc.go diff | blob | history
src/kube2msb/vendor/gopkg.in/yaml.v2/resolve.go diff | blob | history
src/kube2msb/vendor/gopkg.in/yaml.v2/scannerc.go diff | blob | history
src/kube2msb/vendor/gopkg.in/yaml.v2/suite_test.go [new file with mode: 0644] blob
src/kube2msb/vendor/gopkg.in/yaml.v2/yaml.go diff | blob | history
src/kube2msb/vendor/gopkg.in/yaml.v2/yamlh.go diff | blob | history
Register the service endpoints to MSB so it can be used for service request routing and load balancing. Registrator puts service endpoints info to MSB discovery module(Consul as the backend) when an ONAP component is deployed by OOM, and update its state along with the life cycle, such as start, stop, scaling, etc.