Skip to content

Commit 1a905dd

Browse files
authored
Use resized OS disk instead of an attached managed disk for IPOPP
Update IPOPP installation instructions to use resized OS disk instead of an attached managed disk.
1 parent 29e0ec1 commit 1a905dd

File tree

1 file changed

+70
-64
lines changed

1 file changed

+70
-64
lines changed

articles/orbital/satellite-imagery-with-orbital-ground-station.md

Lines changed: 70 additions & 64 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ In this tutorial, we will follow these steps to collect and process Aqua data:
2424
> * [Process Aqua direct broadcast data using RT-STPS](#step-2-process-aqua-direct-broadcast-data-using-rt-stps).
2525
> * [Create higher level products using IPOPP](#step-3-create-higher-level-products-using-ipopp).
2626
27-
Optional setup steps for capturing the ground station telemetry are included in the [Appendix](#appendix).
27+
Optional setup steps for capturing the ground station telemetry are included the guide on [receiving real-time telemetry from the ground stations](receive-real-time-telemetry.md).
2828

2929
## Step 1: Schedule a contact and collect Aqua direct broadcast data using AOGS
3030

@@ -107,65 +107,75 @@ In the steps below, you'll process the Level-0 data generated in the previous st
107107
> [!NOTE]
108108
> Due to potential resource contention, DRL recommends installing RT-STPS and IPOPP on separate machines. But for this tutorial, we install both on the our receiver-vm because we don't run them at the same time. For production workloads, please follow sizing and isolation recommendations in the user guides available on the DRL website.
109109
110-
### Attach a data disk to the receiver-vm
110+
### Increase OS disk size on the receiver-vm
111111

112-
IPOPP installation and subsequent generation of products requires more disk space and I/O throughput than what is available on the receiver-vm by default.
113-
To provide more disk space and throughput, attach a 1TB premium data disk to the receiver-vm by following steps in [Attach a data disk to a Linux VM](../virtual-machines/linux/attach-disk-portal.md)
112+
IPOPP installation and subsequent generation of products requires more disk space than what is available on an Azure VM by default.
114113

115-
### Create a file system on the data disk
114+
Follow the steps below to increase the size of the OS disk on the ```receiver-vm``` to 1TB.
116115

117-
```console
118-
lsblk -o NAME,HCTL,SIZE,MOUNTPOINT | grep -i "sd"
119-
sudo parted /dev/sdb --script mklabel gpt mkpart xfspart xfs 0% 100%
120-
sudo mkfs.xfs /dev/sdb1
121-
sudo partprobe /dev/sdb1
122-
sudo mkdir /datadrive
123-
sudo mount /dev/sdb1 /datadrive
124-
sudo chown azureuser:azureuser /datadrive
116+
### [Portal](#tab/portal2)
117+
118+
1. Open the [portal](https://portal.azure.com).
119+
1. Navigate to your virtual machine.
120+
1. On the **Overview** page, select **Stop**.
121+
1. On the **Disks** page, select the OS disk.
122+
1. On the **Disk** pane, navigate to **Size + performance** page.
123+
1. Select **Premium SSD(locally redundant storage)** from the **Disk SKU** dropdown.
124+
1. Select the **P30** Disk Tier (1024GB).
125+
1. Select **Save**.
126+
1. Navigate back to **Virtual Machine** pane.
127+
1. On the **Overview** page, select **Start**
128+
129+
On the receiver-vm, verify that the root partition now has 1TB available
130+
131+
```bash
132+
lsblk -o NAME,HCTL,SIZE,MOUNTPOINT
125133
```
126-
> [!NOTE]
127-
> To ensure that the datadrive is mounted automatically after every reboot, please refer to [Attach a data disk to a Linux VM](../virtual-machines/linux/attach-disk-portal.md#mount-the-disk) for instructions on how to add an entry to ```/etc/fstab```
134+
This should show ~1TB allocated to the root ```/``` mountpoint.
128135

136+
```console
137+
NAME HCTL SIZE MOUNTPOINT
138+
sda 0:0:0:0 1T
139+
├─sda1 500M /boot
140+
├─sda2 1023G /
141+
├─sda14 4M
142+
└─sda15 495M /boot/efi
143+
```
129144

130145
### Install Desktop and VNC Server
131146

132147
IPOPP installation requires using a browser to sign on to the DRL website to download the installation script. This script must be run from the same host that it was downloaded to. The subsequent IPOPP configuration also requires a GUI. Therefore, we install a full desktop and a vnc server to enable running GUI applications on the receiver-vm.
133148

134-
```console
149+
```bash
135150
sudo yum install tigervnc-server
136151
sudo yum groups install "GNOME Desktop"
137152
```
138153

139154
Start VNC server:
140155

141-
```console
156+
```bash
142157
vncsever
143158
```
144159
Enter a password when prompted.
145160

146161
Port forward the vncserver port (5901) over ssh:
147162

148-
```console
163+
```bash
149164
ssh -L 5901:localhost:5901 azureuser@receiver-vm
150165
```
151166

152167
Download the [TightVNC](https://www.tightvnc.com/download.php) viewer and connect to ```localhost:5901``` and enter the vncserver password entered in the previous step. You should see the GNOME desktop running on the VM.
153168

154169
Start a new terminal, and start the Firefox browser
155170

156-
```console
171+
```bash
157172
firefox
158173
```
159174

160175
[Log on the DRL website](https://directreadout.sci.gsfc.nasa.gov/loginDRL.cfm?cid=320&type=software) and download the downloader script.
161176

162-
Run the downloader script from the ```/datadrive/ipopp``` directory because
163-
the home directory isn't large enough to hold the downloaded content.
164-
165-
```console
166-
INSTALL_DIR=/datadrive/ipopp
167-
cp ~/Downloads/downloader_DRL-IPOPP_4.1.sh $INSTALL_DIR
168-
cd $INSTALL_DIR
177+
```bash
178+
cd ~/Downloads
169179
./downloader_DRL-IPOPP_4.1.sh
170180
```
171181

@@ -175,47 +185,49 @@ Alternatively, you can upload your installation binaries to a container in Azure
175185

176186
### Install IPOPP
177187

178-
```console
179-
tar -xvzf DRL-IPOPP_4.1.tar.gz --directory $INSTALL_DIR
180-
chmod -R 755 $INSTALL_DIR/IPOPP
181-
$INSTALL_DIR/IPOPP/install_ipopp.sh -installdir $INSTALL_DIR/drl -datadir $INSTALL_DIR/data -ingestdir $INSTALL_DIR/data/ingest
188+
```bash
189+
cd ~/Downloads
190+
tar -xvzf DRL-IPOPP_4.1.tar.gz --directory ~/
191+
cd ~/IPOPP
192+
./install_ipopp.sh
182193
```
183194

184-
### Install IPOPP patches
185-
186-
```console
187-
$INSTALL_DIR/drl/tools/install_patch.sh $PATCH_FILE_NAME
188-
```
189195
### Start IPOPP services
190196

191-
```console
192-
$INSTALL_DIR/drl/tools/services.sh start
197+
```bash
198+
cd ~/drl/tools
199+
./services.sh start
193200
```
194201
### Verify service status
195202

196-
```
197-
$INSTALL_DIR/drl/tools/services.sh status
198-
$INSTALL_DIR/drl/tools/spa_services.sh status
203+
```bash
204+
cd ~/drl/tools
205+
./services.sh status
199206
```
200207

201208
### Configure IPOPP services using its dashboard
202209

203-
Before we can create Level-1 and Level-2 products from the Level-0 PDS files generated by rt-stps, we need to configure IPOPP. IPOPP must be configured with its dashboard GUI. To start the dashboard, first port forward the vncserver port (5901) over ssh:
210+
The above steps start IPOPP services with the default configuration. IPOPP services must be configured using the dashboard GUI.
204211

205-
```console
212+
To start the dashboard, first port forward the vncserver port (5901) over ssh:
213+
214+
```bash
206215
ssh -L 5901:localhost:5901 azureuser@receiver-vm
207216
```
208217

209-
Using the TightVNC client, connect to localhost:5901 and enter the vncserver password. On the virtual machine desktop, open a new terminal and start the dashboard:
218+
Using the TightVNC client, connect to localhost:5901 and enter the vncserver password that you previously set.
210219

211-
```console
212-
cd /datadrive/ipopp
213-
./drl/tools/dashboard.sh & 
220+
On the virtual machine desktop, open a new terminal and start the dashboard:
221+
222+
```bash
223+
cd ~/drl/tools
224+
./dashboard.sh
214225
```
226+
Configure services:
215227

216-
1. IPOPP Dashboard starts in process monitoring mode. Switch to **Configuration Mode** by using the menu option. 
228+
1. IPOPP dashboard starts in process monitoring mode. Switch to **Configuration Mode** by using the menu option. 
217229

218-
2. Aqua related products can be configured from EOS tab in configuration mode. Disable all other tabs. We're interested in the MODIS Aerosol L2 (MOD04) product, which is produced by IMAPP SPA. Therefore, enable the following in the **EOS** tab: 
230+
1. Aqua related products can be configured from **EOS** tab in configuration mode. Disable all other tabs. We're interested in the MODIS Aerosol L2 (MOD04) product, which is produced by IMAPP SPA. Therefore, enable the following in the **EOS** tab: 
219231

220232
- gbad 
221233

@@ -225,46 +237,40 @@ cd /datadrive/ipopp
225237

226238
- IMAPP 
227239

228-
3. After updating the configuration, switch back to **Process Monitoring** mode using the menu. All tiles will be in OFF mode initially. 
240+
1. After updating the configuration, switch back to **Process Monitoring** mode using the menu. All tiles will be in OFF mode initially. 
229241

230-
4. When prompted, save changes to the configuration.  
242+
1. When prompted, save changes to the configuration.  
231243

232-
5. Click **Start Services** in the action menu. Note that **Start Services** is only enabled in process monitoring mode.  
244+
1. Click **Start Services** in the action menu. Note that **Start Services** is only enabled in process monitoring mode.  
233245

234-
6. Click **Check IPOPP Services** in action menu to validate.
246+
1. Click **Check IPOPP Services** in action menu to validate.
235247

236248
## Ingest data for processing
237249

238-
Copy the Level-0 PDS files generated by RT-STPS to the IPOPP ingest directory for further processing.
250+
Copy the PDS files generated by RT-STPS to the IPOPP ingest directory for further processing.
239251

240252
```console
241-
cp ~/software/rt-stps/data/* /datadrive/ipopp/drl/data/dsm/ingest/.
253+
cp ~/software/rt-stps/data/* ~/drl/data/dsm/ingest/.
242254
```
243255

244256
Run IPOPP ingest to create the products configured in the dashboard. 
245257

246258
```
247-
/datadrive/ipopp/drl/tools/ingest_ipopp.sh
259+
~/drl/tools/ingest_ipopp.sh
248260
```
249261

250262
You can watch the progress in the dashboard.
251263

252264
```
253-
/datadrive/ipopp/drl/tools/dashboard.sh
265+
~/drl/tools/dashboard.sh
254266
```
255267

256-
IPOPP will produce output products in the following directories:
268+
IPOPP will produce output products in the following directory:
257269

258270
```
259-
/datadrive/ipopp/drl/data/pub/gsfcdata/aqua/modis/level[0,1,2] 
271+
cd ~/drl/data/pub/gsfcdata/aqua/modis/
260272
```
261273

262-
## Appendix
263-
264-
### Capture ground station telemetry
265-
266-
Follow steps here to [receive real-time telemetry from the ground stations](receive-real-time-telemetry.md).
267-
268274
## Next steps
269275

270276
For an end-to-end implementation that involves extracting, loading, transforming, and analyzing spaceborne data by using geospatial libraries and AI models with Azure Synapse Analytics, see:

0 commit comments

Comments
 (0)