Skip to content

Integrate bm #146

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 24 commits into
base: master
Choose a base branch
from
Open

Integrate bm #146

wants to merge 24 commits into from

Conversation

jiria
Copy link
Member

@jiria jiria commented Aug 5, 2021

Depends on microsoft/moc-sdk-for-go#68 and microsoft/moc#84. Dependencies will need to be updated once the lower layer PRs are merged.

cwize1 and others added 22 commits March 31, 2021 12:12
Location value is being provided instead of a group value.
* Use new moc package's providerid functions.

Use the new `providerid.FormatProviderID` function in MOC package
instead of manually formatting the provider ID. This also inherently
adds support for bare-metal provider IDs.

* go.mod updates
…rkaround

Remove load balancer workaround for bare metal.
@jiria jiria requested a review from romoh August 5, 2021 23:55
romoh
romoh previously approved these changes Aug 9, 2021
@jiria jiria requested review from gmileka, cwize1 and Britel August 11, 2021 22:51
@jiria
Copy link
Member Author

jiria commented Nov 1, 2021

Should we drop BM changes out of v1alpha3?

@romoh
Copy link

romoh commented Nov 1, 2021

Should we drop BM changes out of v1alpha3?

Not sure I understand the proposal here?

@jiria
Copy link
Member Author

jiria commented Nov 1, 2021

Should we drop BM changes out of v1alpha3?

Not sure I understand the proposal here?

Since at the time of upstreaming v1alpha4 is already present, should we include the BM changes into the v1alpha3 API of CAPH or just into v1alpha4.

@romoh
Copy link

romoh commented Nov 4, 2021

Should we drop BM changes out of v1alpha3?

Not sure I understand the proposal here?

Since at the time of upstreaming v1alpha4 is already present, should we include the BM changes into the v1alpha3 API of CAPH or just into v1alpha4.

I would vote for v1apha4 unless there will be significant cost associated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants