Loading...

XML

Word

Printable

Type: Story
Resolution: Done
Priority: Medium
Fix Version/s: Beijing Release
Affects Version/s: None
Component/s: None
Labels:
None

Epic Link:
Platform configuration management
Sprint:
OOM Sprint 8, OOM Sprint 9 - Beijing freeze

As ONAP k8s deployer, I would like all components to run in a single configurable namespace so that I could easily deploy it.

20170301 https://gerrit.onap.org/r/#/c/32093/

Reopened 20180308 - we need to notify the community of the e2e and demo script parameter changes, notify the Integration team to adjust their CD scripts, and adjust the wiki and documentation - ~~OOM-793~~

blocks

OOM-740 Add Standardized Configuration to LOG

Closed

OOM-793 Document OOM-722 health/ete script changes for onap-discuss/wiki/rtd/integration team

Closed

INT-439 Adjust OOM CD healthcheck for env param introduce 20180302 in OOM-722

Closed

OOM-778 Replace NFS Provisioner with configurable PV storage solution

Closed

OOM-779 OOM APPC ODL (MDSAL) persistent storage

Closed

OOM-781 Helm 2.8 issues running 20180302 single namespace OOM-722 change - stick to 2.6.1

Closed

relates to

AAF-779 aaf-service pod in crashed state if not onap namespace is used

Closed

LOG-326 CD: OOM automated deployment script

Closed

links to

https://gerrit.onap.org/r/#/c/32093/

https://lists.onap.org/pipermail/onap-discuss/2018-March/008548.html

(1 blocks, 2 relates to, 2 links to)

Assignee:: Borislav Glozman

Reporter:: Borislav Glozman

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 19/Feb/18 1:53 PM

Updated:: 06/Mar/19 10:04 PM

Resolved:: 05/Mar/18 2:07 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates