oom - Introduces the ONAP Platform OOM (ONAP Operations Manager) to efficiently Deploy, Manage, Operate the ONAP platform and its components (e.g. MSO, DCAE, SDC, etc.) and infrastructure (VMs, Containers).

Age	Commit message (Collapse)	Author	Files	Lines
2019-09-02	Move Modeling Storage to RWO	Sylvain Desbureaux	1	-1/+1
	Today when deploying Policy with OOM, the PersistentVolumeClaim needs the "ReadWriteMany" (or "RWX") capability. According to Kubernetes Documentation (https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes), ReadWriteMany stands for "the volume can be mounted as read-write by many nodes". That means that a particular PVC needs to be read and written from many pods. That also means that your code takes that into account and do the work to avoid write at the same place at the same time. An issue on RWX mode is that most "official" storage driver from Kubernetes doesn't support it (13 over the 19 drivers doesn't support it, espacially OpenStack, Amazon and Google storage classes). Modeling PVC for is used only for one POD. Thus we don't need RWX. Change-Id: Ic4b8f5a336f2b9edfdf25ef3cc549b389f9b6f65 Issue-ID: MODELING-213 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2019-05-24	update oom version	yangyan	1	-1/+1
	Change-Id: Ic723624865b200ea025602aee0ec60efb4b9a09f Issue-ID: VFC-1373 Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2019-05-10	Add modeling parser chart	yangyanyj	1	-0/+111
	Issue-ID: MODELING-165 Change-Id: I46419561fdc3f1b4fb7a7bcf19185ac6cbd99c1d Signed-off-by: yangyanyj <yangyanyj@chinamobile.com>