https://jira.akraino.org This file is an XML representation of an issue en-us 9.4.5 940005 11-04-2023 https://jira.akraino.org/browse/ICN-409 Integrated Cloud Native NFV <p>And address any issues faced.</p> <p>This will push the etcd data created via DCM API into the resource synchronizer which will then create the necessary k8s resources (that have already been populated by DCM in etcd).</p> <p> </p> <ul> <li>This includes modifying applyHandler.</li> <li>Pre-process all k8s resources that include a dot (.) in their key name as dots are not supported in MongoDB thus considerably breaking things and preventing resource quotas (e.g.) from actually getting created in Kubernetes.</li> </ul> ICN-409

Implement gRPC calling from DCM to RSync

Story Medium Done Done Igor Duarte Cardoso Igor Duarte Cardoso Wed, 22 Jul 2020 02:59:11 +0000 Thu, 17 Dec 2020 00:54:39 +0000 Wed, 29 Jul 2020 16:48:20 +0000 0 1 <p>The underlying issue regarding the dots does not seem to come from MongoDB because we're using version 3.6.3. The issue seems to be about the loss of detail when unmarshaling JSON into the Go structs. Even though the JSON tagging of these structs specifies if there's a dot or a slash (yes, slashes are also a problem), that tagging is not used when writing the structs into MongoDB. Consequently, when DCM reads from the database during /apply, it won't be aware of which fields have dots or slash in their names while constructing the yaml to be stored in etcd and consumed by rsync. This is where the loss of detail happens. Significant rework seems to be needed to fix this (perhaps the EMCO/Go long-timers can chime in and suggest a quick fix).</p> <p>As such, I'll close the task now <span class="error">&#91;gRPC calling is working and all resources are being created during /apply and destroyed during /terminate&#93;</span>. The only gap is due to the issue above so I am not adding any ResourceQuota attributes that have dots or slashes in their names (like limits.cpu). A future story will be created to specifically address this problem.</p> <p>Increased scope of story:</p> <ul> <li>Pre-process all k8s resources that include a dot (.) in their key name as dots are not supported in MongoDB thus considerably breaking things and preventing resource quotas (e.g.) from actually getting created in Kubernetes.</li> </ul> <p>Can now call rsync and I saw the very first k8s resource automatically create by rsync as intended by dcm. A namespace. Will close task once all basic resources can get created by rsync (namespace, role, rolebinding, quota). For now only validated in 1 cluster.</p> Development Epic Link ICN-214 Rank 0|i004jw: Sprint ICN Sprint 22 Story Points 4.0