From 8474ff2be670a9e109a99a16145f798ddf99c4ad Mon Sep 17 00:00:00 2001 From: Rasmus Kronberg Date: Wed, 13 Aug 2025 13:25:52 +0300 Subject: [PATCH 1/4] deprecate kaivos --- docs/accounts/billing.md | 2 +- .../how-to-add-service-access-for-project.md | 2 +- .../how-to-view-billing-unit-usage.md | 11 +- docs/data/index.md | 4 +- docs/data/kaivos/kaivos-account.md | 17 --- docs/data/kaivos/kaivos_batch_job.md | 119 ---------------- docs/data/kaivos/kaivos_client_in_puhti.md | 132 ------------------ docs/data/kaivos/kaivos_import.md | 61 -------- docs/data/kaivos/kaivos_perl.md | 68 --------- docs/data/kaivos/kaivos_remote.md | 40 ------ docs/data/kaivos/overview.md | 26 ---- hooks/catalog/config.yml | 6 - mkdocs.yml | 9 -- 13 files changed, 9 insertions(+), 488 deletions(-) delete mode 100644 docs/data/kaivos/kaivos-account.md delete mode 100644 docs/data/kaivos/kaivos_batch_job.md delete mode 100644 docs/data/kaivos/kaivos_client_in_puhti.md delete mode 100644 docs/data/kaivos/kaivos_import.md delete mode 100644 docs/data/kaivos/kaivos_perl.md delete mode 100644 docs/data/kaivos/kaivos_remote.md delete mode 100644 docs/data/kaivos/overview.md diff --git a/docs/accounts/billing.md b/docs/accounts/billing.md index ae8891115c..d482234438 100644 --- a/docs/accounts/billing.md +++ b/docs/accounts/billing.md @@ -26,7 +26,7 @@ at research.csc.fi. For LUMI billing, [see the LUMI documentation](https://docs.lumi-supercomputer.eu/runjobs/lumi_env/billing/){ target=_blank }. - The use of Fairdata IDA and Kaivos doesn't consume billing units. + The use of Fairdata IDA doesn't consume billing units. ## Monitoring billing unit consumption diff --git a/docs/accounts/how-to-add-service-access-for-project.md b/docs/accounts/how-to-add-service-access-for-project.md index 452825fbc0..f312cc1550 100644 --- a/docs/accounts/how-to-add-service-access-for-project.md +++ b/docs/accounts/how-to-add-service-access-for-project.md @@ -2,7 +2,7 @@ Access can be granted to the following services: supercomputers **Puhti** and **Mahti**; cloud services **cPouta** and **Rahti**; storage services **Allas** -and **IDA**; sensitive data services **SD Services**; and database service **Kaivos**. +and **IDA**; sensitive data services **SD Services**. Service access has a two-step approval: (1) The project manager approves the service for the project and (2) members approve it for themselves. diff --git a/docs/accounts/how-to-view-billing-unit-usage.md b/docs/accounts/how-to-view-billing-unit-usage.md index 446a581d58..372985c6f6 100644 --- a/docs/accounts/how-to-view-billing-unit-usage.md +++ b/docs/accounts/how-to-view-billing-unit-usage.md @@ -1,15 +1,14 @@ # How to view billing unit usage -Consumption of CSC's resources is mainly measured in billing units. IDA and -Kaivos do not consume billing units; they only have quota limits for each -project. +Consumption of CSC's resources is mainly measured in billing units. Fairdata +IDA does not consume billing units; it only has a quota limit for each project. Check your BU consumption: 1. Login to [MyCSC](http://my.csc.fi). -1. Choose _Projects_ in the navigation menu on the left. -1. Choose a project. -1. The usage is shown under _Resource Usage_. +2. Choose _Projects_ in the navigation menu on the left. +3. Choose a project. +4. The usage is shown under _Resource Usage_. In the usage plot, you can: diff --git a/docs/data/index.md b/docs/data/index.md index 6a326c03cc..766cdcd8bc 100644 --- a/docs/data/index.md +++ b/docs/data/index.md @@ -1,7 +1,7 @@ +# Data + ## [Working with data](datasets/dataset-sources.md) ## [Moving data](moving/index.md) ## [Allas object storage](Allas/index.md) - -## [Kaivos database service](kaivos/overview.md) diff --git a/docs/data/kaivos/kaivos-account.md b/docs/data/kaivos/kaivos-account.md deleted file mode 100644 index 27b4fa0c4d..0000000000 --- a/docs/data/kaivos/kaivos-account.md +++ /dev/null @@ -1,17 +0,0 @@ -# Getting a database account - -The `kaivos.csc.fi` database service can be accessed only from the computing servers of CSC. Thus, in order to use the database service, the project manager as well as all the users should have a CSC user account at Puhti. To open a database to Kaivos database service, the project manager needs to login to the CSC customer portal [MyCSC](https://my.csc.fi) and perform following steps: - -1. Register as CSC user -2. Create a new project or select an already existing project -3. Send a request to [CSC Service Desk](../../support/contact.md). The request should include the proposed name of the database and the size of the database (in GB). - -When the application is processed, a new empty database is created to the database server (`kaivos.csc.fi`). The database service is used through MySQL client programs or other MySQL interfaces (Including MariaDB interfaces). The project manager will receive three database user accounts with passwords to access and manage the database. The database user accounts are based on the database name defined in the application form. The three database user accounts have different roles: - -* The **databasename_admin** user account is intended for database administration. This user account can create new tables and indexes for the database. This user account can also remove records and tables from the database. However, the admin user account can't create new databases or database user accounts. This user account has all rights to the database except the GRANT OPTION. - -* The **databasename_user** user account is intended for everyday usage of the database. This user account can read, write, change and delete data from the database tables. However, this user account can't change the structure of the database i.e. create or drop tables. This user account has the following rights to the database tables: SELECT, INSERT, UPDATE, DELETE. - -* The **databasename_read** user account is intended for users who are allowed to do only queries to the database. This user account can't change the database in any level. This user account has only the SELECT right to database tables. - -The project manager should distribute the database user accounts with passwords to the users of the database service. The databasename_read user account can be given to users who are not members of the computing project. One research group can have several databases. Each database has proprietary database user accounts and passwords. diff --git a/docs/data/kaivos/kaivos_batch_job.md b/docs/data/kaivos/kaivos_batch_job.md deleted file mode 100644 index db814f0fbc..0000000000 --- a/docs/data/kaivos/kaivos_batch_job.md +++ /dev/null @@ -1,119 +0,0 @@ -# Using MySQL client through batch job system - -The MySQL client program can be used in the batch job systems -in the same way as in interactive client usage. The only -difference is that in the batch jobs, the database password -can't be given interactively. Instead it should be given by -using MySQL configuration file (`.my.cnf`) in the home directory. - -Below is a sample MySQL script for Puhti. First we need to create -a MySQL connection configuration file that locates in the home -directory. In this case we use user account `mydb1_admin`, -whose password is `abc123`. The file, named as `.my.cnf`, -would now look like following: - -```text -[client] -user = mydb1_admin -password = abc123 -host = kaivos.csc.fi -``` - -Then we create the actual batch job script. The script below -reserves 12 h time and 1 GB memory to run the MySQL query that -is defined in the file `query_commands.sql`. The query is made -to database `mydb1` and the connection parameters are read from -file `.my.cnf` . The results are written to the `results.txt` file. - -```bash -#!/bin/bash -l -#SBATCH --job-name=mysql_job -#SBATCH --output=output_%j.txt -#SBATCH --error=errors_%j.txt -#SBATCH --time=12:00:00 -#SBATCH --account=project_example -#SBATCH --ntasks=1 -#SBATCH --partition=small -#SBATCH --mem-per-cpu=1024 - -module load mariadb/10.8.2 -cd /path/to/my_data - -mysql --local mydb1 results.txt -``` - -## Example: Using MySQL database from a batch job script in Puhti - -The MySQL database in `kaivos.csc.fi` is intended for cases where -computing servers of CSC use the MySQL database to store and -analyze data. In these cases the database is normally not used -interactively, but the MySQL client is used automatically from -a shell or program script. - -Below is a a sample mysql session where database called `DB_A` -is accessed using the database user account `DB_A_admin` and -password `abc123`. -In Puhti the command is run under project: project_2000136. The -database user account information is first stored into `.my.cnf` in home directory: - -```text -[client] -user = DB_A_admin -password = abc123 -host = kaivos.csc.fi -``` - -Below is a sample batch job script, called as `kaivos.bash`, -that utilizes `kaivos.csc.fi` within the batch queue system. - -```bash -#!/bin/bash -l -#SBATCH --job.name=mysql_job -#SBATCH --output=output_%j.txt -#SBATCH --error=errors_%j.txt -#SBATCH --time=12:00:00 -#SBATCH --account=project_2000136 -#SBATCH --ntasks=1 -#SBATCH --partition=small -#SBATCH --mem-per-cpu=1024 - -#load mariadb environment -module load mariadb/10.8.2 - -# go to the right directory -cd datadir - -# run the analysis -my_program < inputfile30.data > results.30 - -#feed the data to the database -mysqlimport --local --compress DB_A results.30 - -#change the status value in the dataset_table -mysql --local DB_A < output.txt -``` - -or - -```bash -mysql -u db_user_account -p -h kaivos.csc.fi --local --skip-column-names --quick db_name < commands.sql > output.txt -``` - -In the latter command, the `--skip-column-names` option is used to print out only the data produced by the SQL commands. Otherwise names of the selected columns would be printed too. The `--quick` option makes the client to print each row as it is received instead of storing it to the cache first. - -## Setting default values for MySQL connection - -In the mysql commands above, the client program would ask for the user name and password every time when a mysql command is executed. It is however possible to define default values for the database name, user name and password, that will be used for the connection if no password or user name is given. Setting the default values is useful especially in cases where the user uses mostly just one database. - -The default values for the MySQL connections is defined in a file called `.my.cnf` (note the dot in the beginning of the file name) that locates in the user's home directory. This definition file can be constructed in Puhti with a normal text editor. Below is shown the basic structure of the `.my.cnf` file: - -```text -[client] -user = MySQL_username -password = MySQL_password -host = kaivos.csc.fi - -[mysql] -database = db_name -``` - -You can also store the settings for MySQL connection to some other file name, and apply these settings by using option `--defaults-extra-file=settings_file`. For example, if you would like to use MySQL connection configuration that is stored to file _db_conn2.def_, you could execute the previously used MySQL query by using command: - -```bash -mysql --defaults-extra-file=db_conn2.def --local db_name < commands.sql > output.txt -``` - -## Graphical Interfaces - -Graphical MySQL interfaces have not been installed to Puhti. However graphical database interfaces are very efficient when you need to get familiar and administrate a complex database that contains a large number of tables. If you wish to use your database through a graphical user interface, we recommend that you install a interface program (e.g. MysqlWorkbench) to your local computer and create a remote connection to Kaivos as described in chapter 5. - -## Following the disk usage in kaivos.csc.fi - -Each user has only limited disk space available in the kaivos.csc.fi server. If the database reaches the disk quota, the database users can no longer write to the database. In these cases the users should clean up the database to reduce the size or apply more disk space from CSC. You can check the database quota and usage in MySQL terminal session. - -To see the disk quota in kaivos.csc.fi, give the MySQL command: - -```sql -CALL quotadb.quota(); -``` - -The current size of the database can be checked with the MySQL command: - -```sql -CALL quotadb.usedquota(); -``` - -## Example: Creating a table - -In the following example we create a new table called results into an empty database `DB_A`. - -First we connect to the database with the MySQL client: - -```bash -mysql -u DB_A_admin -h kaivos.csc.fi -p DB_A -``` - -Next we create a new table that contains three columns: `id`, `value` and `comment`. The id column is in this case defined to be a unique integer, the value column contains floating point numbers and the comment column text data (a non binary string with max. 30 characters). Note that in real life you normally define many other features like the primary key column and auto filling etc. when you create a new table. - -```sql -CREATE TABLE results (id INT UNIQUE, value FLOAT, comment VARCHAR(30)); -``` - -Note the semicolon (`;`) that is used as end character in SQL commands. - -You can now use SQL command `SHOW TABLES` to see which tables your database contains. - -```sql -mysql> SHOW TABLES; -+----------------+ -| Tables_in_DB_A | -+----------------+ -| results | -+----------------+ -1 row in set (0.01 sec) -``` - -Data can be inserted to the table with the SQL command `INSERT INTO`. Below we insert three new lines to the table: - -```sql -mysql> INSERT INTO results (id, value, comment) VALUES (1, 27.45, "Test case"); -mysql> INSERT INTO results (id, value, comment) VALUES (2, 12.33, "Another"); -mysql> INSERT INTO results (id, value, comment) VALUES (3, 25.33, "Value2"); -``` - -When the table contains data, we can now do SQL queries with the `SELECT` command: - -```sql -mysql> SELECT value FROM results WHERE id=2; -+-------+ -| value | -+-------+ -| 12.33 | -+-------+ -``` - -The MySQL client session is closed with the command EXIT: - -```sql -mysql> EXIT -``` diff --git a/docs/data/kaivos/kaivos_import.md b/docs/data/kaivos/kaivos_import.md deleted file mode 100644 index 3c7d7aef05..0000000000 --- a/docs/data/kaivos/kaivos_import.md +++ /dev/null @@ -1,61 +0,0 @@ -# Data import and export - -In the CSC computing environment we recommend command `mysqlimport` for loading data into a database in Kaivos. This command reads in a delimited text file into a table already existing in the database. To load a large text file from a CSC computing server to a database in Kaivos, you can use the command syntax: - -```bash -mysqlimport -h kaivos.csc.fi -u db_user_account --local --compress --password database_name input_file.table -``` - -`mysqlimport` strips any extension from the input file name and uses the result to determine the name of the table into which to import the file's contents. The user must make sure that the database contains a previously created table with data columns that match the data in the input data file. The user may also have to change the name of the input file if it is not compatible with a database table. The `--local` option defines that the data file locates in the machine where the client is used and not in the actual database server. Thus in the case of `mysqlimport`, this option is obligatory in the computing servers of CSC. - -Downloading complete tables or databases from the database can be done with command `mysqldump`. This command was developed for making backup copies of MySQL databases. In the case of `kaivos.csc.fi`, backup copies are not needed as the database is automatically backup copied by CSC. Instead `mysqldump` offers an easy way to make a copy of your database so that you can move both the data content and structure of your database to another SQL server. You can make a copy of the whole database: - -```bash -mysqldump -u db_user_account -h kaivos.csc.fi -p database > database_dump.txt -``` - -or just from one or more tables: - -```bash -mysqldump -u db_user_account -h kaivos.csc.fi -p database table_name > table_dump.txt -``` - -When `mysqldump` is used with the default settings, the result files contain MySQL commands that are needed to create and populate the selected database tables. `mysqldump` locks the table in the beginning of the copying. Because of this only the `dbname_admin` user account of the database can launch the command by default. In the case of other user accounts (`dbname_read` or `dbname_user`) `--skip-lock-tables` option should be added to the `mysqldump` command. - -You can import the database_dump.txt file as follows: - -```bash -mysql -u database_user_account -h kaivos.csc.fi -p database < database_dump.txt -``` - -## Example: Importing data with mysqlimport - -In this example we import a data set into the result table created in the example in chapter 2. The data to be imported to the database locates in file: `data_to_import.txt`. This file contains data rows like: - -```text -1 -419.557 STRUCTURE1.PDB -2 -479.662 STRUCTURE2.PDB -3 -517.019 STRUCTURE3.PDB -4 -450.922 STRUCTURE4.PDB -5 -421.991 STRUCTURE5.PDB -6 -507.076 STRUCTURE6.PDB -7 -444.598 STRUCTURE7.PDB -8 -444.552 STRUCTURE8.PDB -9 -414.492 STRUCTURE9.PDB -10 -444.549 STRUCTURE10.PDB -11 -463.394 STRUCTURE11.PDB -12 -430.548 STRUCTURE12.PDB -etc... -``` - -To import the data to the results table, we must first copy the data to a file with a name that is compatible with the table name (results). - -```bash -cp data_to_import.txt results.table -``` - -Then use `mysqlimport` to import the data - -```bash -mysqlimport -h kaivos.csc.fi --local --compress -p -u DB_A_admin DB_A results.table -``` diff --git a/docs/data/kaivos/kaivos_perl.md b/docs/data/kaivos/kaivos_perl.md deleted file mode 100644 index 68a6a0897b..0000000000 --- a/docs/data/kaivos/kaivos_perl.md +++ /dev/null @@ -1,68 +0,0 @@ -# Using Perl MySQL API at CSC - -The Perl MySQL API is available in Puhti at CSC, as a part of the bioperl environment. -The following tasks are usually performed, when a MySQL database is used by a Perl script: - -* Perl DBI module is imported -* The connection to the MySQL server is opened -* The statements are executed and their results sets are retrieved -* The server connection is closed - -The following guidance assumes that you have a database user account to the database service at CSC. If you are accessing another MySQL server replace the server name (`kaivos.csc.fi`) in script the server name you are using. - -## Write a MYSQL database access script - -Use your favorite text editor to create a named script file e.g. _mydb_script.pl_ . Then copy the following text to the script. - -```perl -# mydb_script.pl script to show MySQL server version -use strict; -use DBI; -my $dbh = DBI->connect ("DBI:mysql:your_database_name:kaivos.csc.fi", -"your_database_user_account", "your_database_password") or die "Cannot connect:" . $DBI::errstr; - -my $sth = $dbh->prepare ("SELECT VERSION()") or die "Cannot prepare:" . $dbh->errstr(); -$sth->execute () or die "Cannot execute: " . $sth->errstr(); - -while (my @row = $sth->fetchrow_array()) - { - print "@row\n"; - } -$dbh->disconnect (); -``` - -The connection to the database is established by invoking the `connect()` method with the connection parameters. These parameters are: the database to use, database server, database user account and database password. Replace these values corresponding your database, database user account and database password. The `prepare()` method prepares the SQL statement and `execute()` method sends statement to the database server. The `fetchrow_array()` method retrieves rows from the result set in a loop, and the resulting rows are printed. Finally the connection is closed by `disconnect()` method. - -## Running the MYSQL database access script - -Run the script from the command line with Perl interpreter. We recommend using bioperl in CSC environment, because it contains the required modules. - -```text -module load biokit -perl mydb_script.pl -``` - -or add following to the beginning of the script: - -```bash -#!/appl/soft/bio/bioperl/5.30.0/bin/perl -``` - -Then make the script executable and run it directly: - -```bash -chmod +x mydb_script.pl -./mydb_script.pl -``` - -### The statements issuing methods - -The `prepare()` method is for preparing the SQL statement and `execute()` method is for issuing SQL statements. However, you can use the `do()` method for non repeated non-SELECT statement (e.g. INSERT, UPDATE, DELETE), because no data is returned from the database: - -```perl -$rows_affected = $dbh->do("UPDATE your_table SET foo = foo + 1"); -``` - -### Transaction - -By default AutoCommit mode is on. You do not need to use `commit()` method while making transactions. Only InnoDB storage engine is transactional. The default MyISAM is a non-transactional storage engine. diff --git a/docs/data/kaivos/kaivos_remote.md b/docs/data/kaivos/kaivos_remote.md deleted file mode 100644 index 4bf977f6d7..0000000000 --- a/docs/data/kaivos/kaivos_remote.md +++ /dev/null @@ -1,40 +0,0 @@ -# Using kaivos.csc.fi directly from your local computer - -The MySQL databases in `kaivos.csc.fi` can be directly accessed only from the computing servers of CSC (Puhti and Mahti). However, you can make the database visible to your own computer using your CSC user account and port forwarding through an _ssh tunnel_. - -!!! note "SSH keys" - Please note that connecting to CSC computing servers over SSH requires you - to set up SSH keys and add your public key to MyCSC portal. - [Read the instructions here](../../computing/connecting/ssh-keys.md). - -In linux and MacOSX machines an ssh tunnel from your local computer to `kaivos.csc.fi` via `puhti.csc.fi` can be done for example with the command: - -```bash -ssh -l csc_username -L 3306:kaivos.csc.fi:3306 puhti.csc.fi -N -``` - -The `-N` option in the end of the connection command blocks the command shell after the connection is established. Once the connection is closed also the port forwarding becomes disabled. Note that the ssh command above uses your CSC user account name, not the database user account. - -In Windows machines you can use e.g. plink program to open the tunnel. [Plink](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) can only be used through the command prompt. Below is a sample command for using plink: - -```bash -plink -L 3306:kaivos.csc.fi:3306 csc_username@puhti.csc.fi -``` - -The tunneling commands above define that the communication to port 3306 (the default port of MySQL) in you local computer is transported to the MySQL port of `kaivos.csc.fi` through `puhti.csc.fi` server. As long as the connection to puhti.csc.fi is active the database in `kaivos.csc.fi` can be accessed from your local computer using the same MySQL commands as described above for Puhti (assuming that you have the MySQL client program installed in your local computer). The only difference compared to previous command examples is that the host section (`-h`) should now point to host `127.0.0.1` that refers to your local host, instead of `kaivos.csc.fi`. - -So for example the syntax to open an interactive MySQL session would now be: - -```bash -mysql -u db_user_account -p -h 127.0.0.1 --local database_name -``` - -And the syntax for `mysqlimport`: - -```bash -mysqlimport -h 127.0.0.1 -u db_user_account --local --compress --password database_name input_file.table -``` - -In the same way, you can make your databases visible in your local computer using locally installed graphical MySQL interfaces, like [MySQL Workbench](https://www.mysql.com/products/workbench/). The only major limitation with the port forwarding is that normally ssh tunnels are not very stable. You may need to reopen the ssh connection every now and then and you should not trust that the tunnel remains usable for several hours. - -For the security reasons we recommend that you always close the ssh connection when you stop using the database. diff --git a/docs/data/kaivos/overview.md b/docs/data/kaivos/overview.md deleted file mode 100644 index 0baf026fea..0000000000 --- a/docs/data/kaivos/overview.md +++ /dev/null @@ -1,26 +0,0 @@ -# Kaivos - A relational database service - -## When to use a database? - -Relational databases provide an efficient tool to manage structured data that keeps changing and which contains data that needs to be accessed with complex queries. Client-server-based SQL databases (e.g. MySQL, MariaDB, PostgreSQL) can not be effectively run in HPC computing environments like Mahti or Puhti. If you need to use relational databases in CSC computing environment, you should use a database running in some external server. - -It is fairly simple to set up your own SQL server using [Pukki DBaaS](../../cloud/dbaas/index.md), or a Virtual Machine running in cPouta. Setting up your own database server this way gives you full access to the database. Note that using cPouta requires that you know how to manage a database server. - -## Kaivos - just add data - -Another option is to use kaivos.csc.fi database service that is hosted by CSC. This service is intended for users who want to use their own MySQL/MariaDB databases in CSC computing environment without managing their own database server. The service is in this sense similar to Pukki DBaaS, which supports PostgreSQL databases. - -In this guide you can find information about getting started with Kaivos and instructions for using it. The actual SQL command language is not discussed in this document in detail. Please use the MariaDB manual or some of the many SQL guides published for an introduction to SQL databases. - - -**Comparison between Pukki and Kaivos** - -| | Pukki DBaaS | Kaivos | -|:--------------------|:------------------------:|:-------------------------:| -| Database engine | ProstgreSQL | MariaDB | -| Accessibility | Accessibility controlled with
firewall settings by the user.
Accessible from any location. | Directly accessible only
from Puhti and Mahti. | -| DB administration | User | CSC | -| Max. size | 50-200 GB | 20 GB | -| Backup by CSC | Yes | Yes | - - diff --git a/hooks/catalog/config.yml b/hooks/catalog/config.yml index c4df6ff186..42fbe03504 100644 --- a/hooks/catalog/config.yml +++ b/hooks/catalog/config.yml @@ -96,9 +96,3 @@ appendix: disciplines: - Language Research and Other Digital Humanities and Social Sciences url: http://urn.fi/urn:nbn:fi:lb-201902131 - - - name: MySQL - description: MySQL database client - disciplines: - - Miscellaneous - src: data/kaivos/overview.md diff --git a/mkdocs.yml b/mkdocs.yml index a24ba93e25..faa897ae70 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -525,15 +525,6 @@ nav: - S3cmd: data/Allas/using_allas/s3_client.md - Pouta web UI: data/Allas/using_allas/web_client.md # data/Allas/using_allas/directory_object_error.md is not linked in this structure - - Kaivos database service: - - data/kaivos/overview.md - - Getting a database account: data/kaivos/kaivos-account.md - - MySQL client programs at CSC: data/kaivos/kaivos_client_in_puhti.md - - Data import and export: data/kaivos/kaivos_import.md - - Using MySQL client through batch job system: data/kaivos/kaivos_batch_job.md - - Using kaivos.csc.fi directly from your local computer: data/kaivos/kaivos_remote.md - - Using Perl MySQL API at CSC: data/kaivos/kaivos_perl.md - # Python MySQL API at CSC: - Sensitive data: - data/sensitive-data/index.md - Table of contents: data/sensitive-data/sd-services-toc.md From edb1a8074aa760f41950b8b03b025e9d73e27dcf Mon Sep 17 00:00:00 2001 From: Rasmus Kronberg Date: Wed, 13 Aug 2025 13:56:55 +0300 Subject: [PATCH 2/4] wn --- docs/support/wn/cloud-new.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/support/wn/cloud-new.md b/docs/support/wn/cloud-new.md index 05116b67e6..15812917b1 100644 --- a/docs/support/wn/cloud-new.md +++ b/docs/support/wn/cloud-new.md @@ -1,5 +1,11 @@ # Cloud services +## Pukki DBaaS replaces Kaivos database service, 13.8.2025 + +Kaivos database service (kaivos.csc.fi) will shut down on XX.XX.202X. We +recommend taking [Pukki DBaaS](../../cloud/dbaas/index.md) into use if +you need to run SQL databases at CSC. + ## New Pouta VM launcher We deployed a new VM launcher when creating a VM on Pouta. Our [documentation](../../cloud/pouta/launch-vm-from-web-gui.md#launching-a-virtual-machine) has been updated accordingly. Take a look at it! From 426e4b9dff983902dc837e47b87490f9fa45e146 Mon Sep 17 00:00:00 2001 From: Rasmus Kronberg <43936697+rkronberg@users.noreply.github.com> Date: Thu, 2 Oct 2025 14:09:23 +0300 Subject: [PATCH 3/4] Update how-to-view-billing-unit-usage.md --- docs/accounts/how-to-view-billing-unit-usage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/accounts/how-to-view-billing-unit-usage.md b/docs/accounts/how-to-view-billing-unit-usage.md index 8ffdab8917..778d52f2ae 100644 --- a/docs/accounts/how-to-view-billing-unit-usage.md +++ b/docs/accounts/how-to-view-billing-unit-usage.md @@ -1,6 +1,6 @@ # How to view Billing Unit usage -Consumption of CSC's resources is mainly measured in billing units. Fairdata +Consumption of CSC's resources is mainly measured in Billing Units. Fairdata IDA does not consume Billing Units; it only has a quota limit for each project. Check your BU consumption: From c2eeefe1701665f939de2229ad063d269e8ac94b Mon Sep 17 00:00:00 2001 From: Rasmus Kronberg Date: Thu, 2 Oct 2025 17:00:45 +0300 Subject: [PATCH 4/4] links --- docs/support/wn/cloud-new.md | 8 ++++---- docs/support/wn/data-new.md | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/support/wn/cloud-new.md b/docs/support/wn/cloud-new.md index 15812917b1..8ed51eece7 100644 --- a/docs/support/wn/cloud-new.md +++ b/docs/support/wn/cloud-new.md @@ -1,10 +1,10 @@ # Cloud services -## Pukki DBaaS replaces Kaivos database service, 13.8.2025 +## Pukki DBaaS replaces Kaivos database service, XX.XX.2026 -Kaivos database service (kaivos.csc.fi) will shut down on XX.XX.202X. We -recommend taking [Pukki DBaaS](../../cloud/dbaas/index.md) into use if -you need to run SQL databases at CSC. +Kaivos database service (kaivos.csc.fi) has been decommissioned on +XX.XX.2026. We recommend taking [Pukki DBaaS](../../cloud/dbaas/index.md) +into use if you need to run SQL databases at CSC. ## New Pouta VM launcher diff --git a/docs/support/wn/data-new.md b/docs/support/wn/data-new.md index 77df0d4008..7aafffb4ca 100644 --- a/docs/support/wn/data-new.md +++ b/docs/support/wn/data-new.md @@ -2,7 +2,7 @@ ## The Kaivos database service will be decommissioned by the end of the year 2025 -The [Kaivos database service](../../data/kaivos/overview.md) will be +The Kaivos database service will be decommissioned by the end of the year 2025. The Kaivos database service is no longer available to new users. The service will be replaced by Pukki database service. Instructions related to the use of Pukki database service can be