You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: csc-overrides/partials/announcement.html
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -6,8 +6,8 @@
6
6
#}
7
7
{# import ".icons/material/coffee.svg" as icon #}
8
8
{# import ".icons/material/chat.svg" as icon #}
9
-
{# import ".icons/material/information.svg" as icon #}
10
-
{% import ".icons/material/alert.svg" as icon %}
9
+
{% import ".icons/material/information.svg" as icon %}
10
+
{# import ".icons/material/alert.svg" as icon #}
11
11
{# import ".icons/material/wrench.svg" as icon #}
12
12
{# import ".icons/material/rocket-launch.svg" as icon #}
13
13
{# import ".icons/material/test-tube.svg" as icon #}
@@ -18,7 +18,7 @@
18
18
<divclass="announcement-icon">{{ icon }}</div>
19
19
{# Put the announcement, in HTML, right under this comment! #}
20
20
<p>
21
-
Due to a technical issue, some files cannot currently be imported from SD Connect to SD Desktop using the Data Gateway app. <ahref="{{ base_url | url }}/support/wn/data-new/#sd-workaround">See temporary workaround here</a>.
21
+
Note: Starting from June 11, 2025, using the MyCSC portal will require multi-factor authentication (MFA). <ahref="{{ base_url | url }}/accounts/mfa/">Read our MFA guide here</a>.
Copy file name to clipboardExpand all lines: docs/apps/geoconda.md
+11-38Lines changed: 11 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -168,27 +168,15 @@ spyder
168
168
*`os.environ["_JAVA_OPTIONS"] = "-Xmx4g"` in the beginning of your Python code.
169
169
170
170
### Google Earth Engine authentication set up in Puhti
171
-
For using Google Earth Engine (GEE) API with `earthengine-api` package, one needs to have an account in GEE. Before first usage, also set up GEE authentication in Puhti:
172
-
173
-
1. Open Puhti web interface
174
-
2. Start Desktop app
175
-
3. In the Desktop, open:
176
-
* Web Browser under Applications menu and
177
-
* Terminal from shortcuts
178
-
4. In the Terminal:
171
+
For using Google Earth Engine (GEE) API with `earthengine-api` package, one needs to have an account and project in GEE. Before first usage, also set up GEE authentication in Puhti:
This prints out a long link and asks for a code. Copy the link to the web browser and open the Google log-in page. Log-in and copy the created code back to Python.
179
+
This prints out a long link and asks for a code. Copy the link to the web browser of your local laptop. Follow the instructions on the web page and finally copy the created code back to Terminal.
192
180
193
181
## Using Allas or LUMI-O from Python
194
182
@@ -224,20 +212,17 @@ Geoconda conda environment files and `download_wbt` and `start_wbt.py` needed fo
224
212
225
213
## References
226
214
227
-
-[CSC Python parallelisation examples]
228
-
-[Python spatial] libraries
229
-
-[Geoprocessing with Python using Open Source GIS]
230
-
-[GeoExamples], a lot of examples of using Python for spatial analysis
231
-
-[Automating GIS processes course materials], where most of the exercises are done using Python (University of Helsinki)
Copy file name to clipboardExpand all lines: docs/data/moving/copy_allas_ida.md
+76-5Lines changed: 76 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,6 @@
1
1
# Copying data between Allas and IDA via Puhti
2
2
3
+
3
4
## Copying data from Allas to IDA via Puhti
4
5
5
6
In order to be able to copy data from Allas to IDA with this procedure, you
@@ -114,15 +115,85 @@ for their username and password in IDA.
114
115
If you do not need to continue working with the data on Puhti after uploading
115
116
it to IDA, remove it from the scratch disk area of Puhti to free up disk space.
116
117
118
+
117
119
## Copying data from IDA to Allas via Puhti
118
120
119
-
In order to copy data from IDA to Allas with this procedure, you need to be a
121
+
In order to copy data from IDA to Allas, you need to be a
120
122
member of a project that has Allas and Puhti services in use. On the IDA side,
121
123
you either need to be a member of a project which has IDA service in use, or
122
124
the data in question needs to be publicly available for downloading. Note that
123
125
the projects in Allas, Puhti and IDA do not need to be the same.
124
126
125
-
In short, there are four steps to follow:
127
+
### Automatic copying with ida2allas tool
128
+
129
+
If you wish to move a complete directory from IDA to Allas object storage service without
130
+
any changes or rearrangements, you can use command line tool _ida2allas_. This tool is available
131
+
in Puhti server at CSC.
132
+
133
+
#### 1. Connect to Puhti
134
+
135
+
We recommend that you run the data transfer process in one of the login nodes of the Puhti.
136
+
(Login nodes can be used in this case as the data transfer process is not computationally heavy).
137
+
The easiest way to open a login node session in Puhti is to use the WWW interface of Puhti:
138
+
139
+
*[Puhti Web interface](https://www.puhti.csc.fi)
140
+
141
+
In the web interface, choose *Login node shell* from the *Tools* menu. This opens a
142
+
terminal session where you can set up connections to IDA and Allas and where you can
143
+
execute the data transport process.
144
+
145
+
146
+
#### 2. Establishing connections
147
+
148
+
First, open the Allas connection using the S3 protocol with the following commands:
149
+
150
+
```text
151
+
module load allas
152
+
allas-conf -m S3
153
+
```
154
+
155
+
The _allas-conf_ command will prompt you to enter your CSC password. The Haka password is not accepted.
156
+
After that you will choose the Allas project where the data will be copied.
157
+
158
+
159
+
Next, establish the IDA connection with the commands:
160
+
161
+
```text
162
+
module load ida
163
+
ida_configure
164
+
```
165
+
166
+
The configuration process will ask for your _IDA project number_ and _app password_ that you can get from [IDA web interface](https://ida.fairdata.fi).
167
+
If you already have a working IDA connection configured, you can choose not to overwrite the `.ida-config` and `.netrc` files. In that case, you won’t need to retrieve a new IDA key from the web interface.
168
+
169
+
#### 3. Data transfer
170
+
171
+
Data transfer is launched with the command:
172
+
173
+
```text
174
+
ida2allas
175
+
```
176
+
177
+
The program will first ask whether to fetch data from the IDA staging area or the frozen area.
178
+
179
+
Then it will list the folders in the selected IDA area and prompt you to choose the folder to transfer.
180
+
181
+
Finally, the program will list the buckets (storage folders) in Allas and ask you to select the one where you want to transfer the data. You can also create a new bucket. Do not use uppercase letters, spaces, or special characters in the name of the bucket. Further, note that bucket names must be unique compared to any Allas project. Thus it is a good habit to add some project specific part to the bucket name.
182
+
183
+
In case of large (over 100 GiB) data transfers you can start the transfer with the commands:
184
+
185
+
```text
186
+
screen
187
+
ida2allas
188
+
```
189
+
190
+
In the example above, _screen_ command launches a virtual terminal session where the _ida2allas_ command will continue running even if the connection to Puhti would be lost.
191
+
192
+
193
+
194
+
### Manual data transfer from IDA to Allas
195
+
196
+
If you don't want to copy a complete IDA directory to Allas or if you want to rearrange the data, then you need to do the data transfer in four steps:
126
197
127
198
1. Download the data from IDA to Puhti scratch disk
128
199
2. Rearrange the data on the scratch disk, if necessary
@@ -190,7 +261,7 @@ cd /scratch/project_2000012/xferdir
No, for the time being nested virtualization is not enabled in Pouta. Nested virtualization disables live migrations, and at this moment we consider that Live migration is a much more useful feature for our user than nested virtualization.
4
+
5
+
!!! Info "Nested virtualization"
6
+
Nested virtualization is a feature that allows you to run virtual machines (VMs) inside other VMs. This is useful for testing and development purposes
7
+
8
+
!!! Info "Live migration"
9
+
Live migration is the process of moving a running virtual machine between different physical machines without rebooting or shuting down the virtual machine. There might be a short downtime during the migration, but the processes running on the virtual machine do not perceive this downtime.
0 commit comments