-
Notifications
You must be signed in to change notification settings - Fork 185
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
Exadata VM cluster on Exascale Infrastructure #825
Comments
Can you please look into the below documentation on why it is required? Thanks |
Please reopen the issue if you require more details, Thanks! |
im sorry but Im not getting why such parameter is required. Having --exadb-vm-cluster-id should be enough if I need to change the enabled ECPU. |
@rcitton Re-opened the issue, we will reply after checking with the concerned team |
it's not a cloud_vm_cluster, im speaking about exadb-vm-cluster |
Apologies , ExaScale requires ssh keys in the service, and I agree , it should not require. |
Hi Team, a question about 3.44.1 and new "Exadata VM cluster on Exascale Infrastructure" support.
I wonder why doing "oci db exadb-vm-cluster update (...) --total-e-cpu-count xxx"
parameter "--ssh-authorized-keys-file" is required. Im not going to change the ssh key, I need to update the ECPU only.
The text was updated successfully, but these errors were encountered: