aws/credentials, traditional credentials are required. With the Azure provider openshift-install will prompt for credentials and store them in ~/.azure/osServicePrincipal.json, it doesn’t simply pickup az login -x509 -new -nodes -key myCA.key -sha256 -days 1825 -out myCA.crt The values you enter for each prompt do not need to be any specific value, and do not need to be accurate. Create Private Key and Certificate Cassandra 3.11.3 | CQL spec 3.4.4 | Native protocol v4] Use HELP for help. cqlsh> Next, using the cqlsh prompt, we’ll show that the outpost can add records to the “daily_records” table in the “attendance” keyspace:

aws/credentials, traditional credentials are required with the Azure provider openshift-install will prompt for credentials and store them in ~/.azure/osServicePrincipal.json, it doesn’t simply pickup az login -x509 -new -nodes -key myCA.key -sha256 -days 1825 -out myCA.crt The values you enter for each prompt do not need to be any specific value, and do not need to be accurate. Create Private Key and Certificate Cassandra 3.11.3 | CQL spec 3.4.4 | Native protocol v4] Use HELP for help. cqlsh> Next, using the cqlsh prompt, we’ll show that the outpost can add records to the “daily_records” table in the “attendance” keyspace:

aws/credentials, traditional credentials are required. With the Azure provider openshift-install will prompt for credentials and store them in ~/.azure/osServicePrincipal.json, it doesn’t simply pickup az login -x509 -new -nodes -key myCA.key -sha256 -days 1825 -out myCA.crt The values you enter for each prompt do not need to be any specific value, and do not need to be accurate. Create Private Key and Certificate Cassandra 3.11.3 | CQL spec 3.4.4 | Native protocol v4] Use HELP for help. cqlsh> Next, using the cqlsh prompt, we’ll show that the outpost can add records to the “daily_records” table in the “attendance” keyspace:

aws/credentials, traditional credentials are required with the Azure provider openshift-install will prompt for credentials and store them in ~/.azure/osServicePrincipal.json, it doesn’t simply pickup az login -x509 -new -nodes -key myCA.key -sha256 -days 1825 -out myCA.crt The values you enter for each prompt do not need to be any specific value, and do not need to be accurate. Create Private Key and Certificate Cassandra 3.11.3 | CQL spec 3.4.4 | Native protocol v4] Use HELP for help. cqlsh> Next, using the cqlsh prompt, we’ll show that the outpost can add records to the “daily_records” table in the “attendance” keyspace:

-x509 -new -nodes -key myCA.key -sha256 -days 1825 -out myCA.crt The values you enter for each prompt do not need to be any specific value, and do not need to be accurate. Create Private Key and Certificate Cassandra 3.11.3 | CQL spec 3.4.4 | Native protocol v4] Use HELP for help. cqlsh> Next, using the cqlsh prompt, we’ll show that the outpost can add records to the “daily_records” table in the “attendance” keyspace:

Cassandra 3.11.3 | CQL spec 3.4.4 | Native protocol v4] Use HELP for help. cqlsh> Next, using the cqlsh prompt, we’ll show that the outpost can add records to the “daily_records” table in the “a�endance” keyspace:

Cassandra 3.11.3 | CQL spec 3.4.4 | Native protocol v4] Use HELP for help. cqlsh> Next, using the cqlsh prompt, we’ll show that the outpost can add records to the “daily_records” table in the “attendance” keyspace: