richard-churchman
5f6bbe45f7
Major bug fixes relating to the Redis implementation in Reprocessing and Search Key Cache were identified and fixed as part of the rekeying development. Included functionality to stop the Exhaustive training. Fixed the Unsupervised learning functionality in Exhaustive Training. Embedded the Mock Data CSV data into a class to make it compatible with Docker without needing to modify the Dockerfile (i.e, build). Included a new table that stores training data to enhance support capabilities for Exhaustive. Reintroduced and validated the Multitenancy functionality. Postgres is now fully deprecated in place of Redis for cache, and all implementations of the Interfaces for Postgres have been removed. No migrations exist to support this deprecation, and Postgres as a cache is now wholly unsupported. Removed the Indexing background thread, as Redis does not require it, given that it is a key-value pair database. Created a RedisCommandFlag Environment Variable to support Fire and Forget write to Redis in Invocation. Implemented functionality to Export, Peek and Download configuration environments using a secure, encrypted scheme. Created a permission to access the functionality via the user interface. Extensive database-based logging is included to provide for a comprehensive audit. Created functionality to Import the encrypted Export file inside a database transaction to ensure consistency. As Docker is now the primary deployment model, log4net instantiation has been moved to an approach that primarily uses programmatic instantiation of the ConsoleLogger and RollingFileAppender given Environment Variables. Implemented functionality to support remote \ mounted Log4Net XML Serialisation files for more advanced log4net configurations. Reintroduced access to counters via the user interface and created a permission. Took the opportunity to implement ReSharper linter suggestions. Disabled the Lock button across the whole application, with that functionality being reserved for future use. It is intended that locking happens programmatically on the basis of dependencies in future commits. Fixed several significant end-use bugs which became apparent during testing of the refactored code relating to case management and visualisations. Fixed certain other minor bugs that came up during testing. Brought documentation up to date for this commit. Brought the Docker Compose file up to date for this commit. Removed Redundant Environment Variables for this commit. Made the README file less verbose and unnecessary.
2.8 KiB
layout, title, nav_order, parent
| layout | title | nav_order | parent |
|---|---|---|---|
| default | Creating Virtual Machine | 3 | Getting Started |
🚀Speed up implementation with hands-on, face-to-face training from the developer.
Creating Virtual Machine
A Droplet is a Virtual Machine and will contain the Jube software. Having set up the database, locate the Droplet menu item:
Click on the Droplet menu item to expose the page to begin creation:
Note the prominent button Create Droplet:
Click the Create Droplet button:
Create a Droplet in a region geographically close, in this case Frankfurt:
Keeping the default Ubuntu operating system scroll down to set the credentials for the Droplet.
Credentials can take the form of either a password or SSH certificate. Passwords are strongly discouraged, however for illustrative purpose and approachability, will be used in this example. It is well worth taking the time to generate an SSH key, but the concepts are outside the scope of this document, noting the DigitalOcean guidance on the topic. Scroll down to choose an an authentication method:
Note the radio buttons SSH key or password:
Click the password radio button:
Create a very strong password and proceed to scroll down to size the Droplet:
Select for this example General Purpose, with the default entry level 2vCPU 8GB RAM, with the default 1x SSD:
Note the Create Droplet button in the bottom left hand corner of the page:
Click the button to create the Droplet:
Waiting a moment for the Droplet to create before clicking on the link:
On clicking the link for the Droplet the landing page will be exposed which presents information about the Droplet:
Specifically the public IP address which will be used to expose the Jube software user interface and API endpoints:
Being a Linux Operating System it is possible to SSH for console, however, in this example the hosted console will be used. Note the location of the Console link:
Click on the Console link to launch a session:
The Droplet has now been created and is read for prerequisites to be installed.