Exadata VM cluster on Exascale Infrastructure
Open
Nobody has claimed this yet.
Database
- Dominant language
- Python
- Stars
- 669
- Forks
- 236
- Avg merge
- 1m
- Merged PRs (30d)
- 4
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the oci db exadb-vm-cluster update command using only --total-e-cpu-count and inspect the command definition and help output for the Exadata VM cluster update entry point. Done means an ECPU-only update no longer requires --ssh-authorized-keys-file, while SSH key updates remain supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100