Krishnasuri Narayanam

To begin with, we predict utilization for a container based on its requests/limits similar to the way it is done in the k8s scheduler-plugin `Trimaran` https://github.com/kubernetes-sigs/scheduler-plugins/blob/master/pkg/trimaran/targetloadpacking/targetloadpacking.go#L197

/assign @atantawi

> /ok-to-test > > we don't usually accept merge commits. Can you please rebase? Done rebase.

https://app.netlify.com/sites/monumental-pastelito-93ebf8/deploys/64fa202cff93053c1af61e95

> @knarayan it seems that you did a wrong rebase? > > I would suggest you create a brand new branch from sigs/scheduler-plugins, and cherry-pick(sorry for involving one more new...

Initial draft PR: https://github.com/sustainable-computing-io/scheduler-plugins/pull/2

`Configmap` can be used to address this issue (a less preferred alternative is to use `webhook`).

> Plan > > 1. Mount a configmap to scheduler pod as volume. > > 2. Configmap contains power model in json. > > 3. Read config map in power...

Associated PR: https://github.com/sustainable-computing-io/scheduler-plugins/pull/9

=== RUN TestAgreeToTransferSuccessful 2022/06/19 13:18:22 ReadAsset: collection assetCollection, ID id1 2022/06/19 13:18:22 AgreeToTransfer Put: collection Org1TestmspPrivateCollection, ID id1 2022/06/19 13:18:22 AgreeToTransfer Put: collection assetCollection, ID id1, Key transferAgreementid1 asset_transfer_test.go:215: Error...