---
# System prepended metadata

title: Workshop 2 - HPC Type 1
tags: [workshops]

---

---
tags: workshops
---

# Workshop 2 - HPC Type 1 #

> **_STATUS:_** THIS IS CURRENTLY A DRAFT VERSION 

```yaml
title: Workshop HPC Type 1
date: 02-28-2022
authors: Kristoffer Nielbo
contact: kln@cas.au.dk
```




Questions to be discussed:

1. what service goals do we have?
    * user, fast access to >laptop, automation, reduce wait time
    * \[**challenges**\] knowledge of
    * easier access to data
    * diversity of users
    * uniformity of services
2. what service elements do we have? 
    * 
3. why and how were those services chosen?
    * 
4. is it the services we expected?
    * 
5. is it the services the end-users expected?
    * 
6. how can we improve our services?
    * 
7. development suggestions for UCloud (new functionalities)
    * 
8. development suggestions user applications (new software)


## Two tracks

_User Software / Apps_

- apps/vm image creation and deployment
- coordination on creation/testing/updating
- procedure for request and select new images

* help in developing and updating applications, 
* decision of application ()

---

`user application`

1. __New App Requests__

* Review process (general interest; free/not; availability for linux)
    - __new apps requests__
    - add to repository :: deployment :: 
    
    - source for container / code template is open
    
    - Open source for container is a requirement for OS (base image is always free)
        - last version can always be run; old versions are maintained
        - repository can become read only
    - OPEN review process; simple apps; 
    
    - internal polling system
    - effort for GPUs in the app store
    
    - MONTHLY front office meetings (within and outside the consortium), 

Request for application > get information about software > test > geenral interest > internal review > 

one person for app requests, specific workshop for apps

coordinated Front Offices (internal) every month

Move to service desk > ticket on application > a 

---



`outreach`

4. Front offices

* transparancy about process for non-consortium participants (front offices)
* transparency in UCLoud development (what is in the pipeline) - something at state :: outreach - rewrite/condense "what is in ucloud's pipeline", "news section", 
    - process meeting in the future 
* feature that new things are coming out in the Dashboard

`specific app`

3. Windows agains again

- Windows

---




---

`development`

2. 'Private Application' + documentation, where you freeze an image 
    - education dedicated part of hardware 
    - web servers solution ::  education
    - removed after period of time



---

`development`

6. Documentation

- examples already exists in the documentation
- contextualize, provide a small bit of documentation in the dashboard


---

`development`

5. User data

- utilization of user data to figure out what is needed in the future (not just second laptop)
- 

---

- use cases for VDE
    - pseudo apps, coordination between campuses

_Cloud Development_

- ucloud developers documentation
    - 'Private Application' + documentation, where you freeze an image 
    - education dedicated part of hardware \& 
    - web servers solution :: education

- system internals and code development for ucloud
    - 
- coordination of code development of ucloud
    - 
    
- roadmap and new features
    - GPUs in app store
    - zenhub used to organize roadmap (3-6 month); public github issues

