Once you have the above done, you can then proceed to create an ExaCS. You could do this through the Web Console, but when I was presented with what I assume is a bug in the console, I decided to give the CLI a try.
Before executing the CLI, you need to create two (2) files:
A JSON formatted file that has the create_db_system payload
a file referenced in the main file that contains the SSH public key pair(s) you want to associate with the ExaCS instance
An example (based off the file I used) and explanation follows – you can get the json file from here:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Once you’ve updated the json file, and created a file for your ssh keys, you can run the following from your OS command line
oci db system launch --from-json file://create_exacs_ocicli.json
ExaCS will take a while to create – its doing a fair amount of work – so at this point, grab a coffee (or dinner & a movie depending on the time of day) and keep an eye on the progress through the OCI Console.