Skip to content

Commit f5629a3

Browse files
committed
workshop-vienna: Use "Unikraft Cloud" instead of "KraftCloud"
Also update the content to make it better fitted for a workshop rather than a hackathon. Signed-off-by: Razvan Deaconescu <razvand@unikraft.io>
1 parent 34c948d commit f5629a3

File tree

1 file changed

+18
-17
lines changed

1 file changed

+18
-17
lines changed

content/hackathons/2024-12-vienna/index.mdx

Lines changed: 18 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -54,33 +54,34 @@ As part of the Unikraft community, [Răzvan Deaconescu](https://github.com/razva
5454
| Time (CEST) | Session |
5555
| ------------- | -----------------------------------------------------------------------------------------------------|
5656
| 09:00-09:30 | Introduction to Unikernels and Cloud Computing |
57-
| 09:30-11:00 | Deploying Cloud Applications using KraftCloud |
57+
| 09:30-11:00 | Deploying Cloud Applications using Unikraft Cloud |
5858
| 11:00-12:30 | Behind the Scenes: Using KraftKit to Operate Unikraft Applications |
5959
| 12:30-14:00 | Lunch |
6060
| 14:00-15:00 | Using Docker and Docker-based Filesystems |
61-
| 15:00-16:00 | Debugging Unikraft / KraftCloud Applications |
62-
| 16:00-18:00 | Hackathon start: Announce Teams and Projects. Start Coding |
61+
| 15:00-16:00 | Debugging Unikraft / Unikraft Cloud Applications |
62+
| 16:00-17:00 | First Principles Approach: Using Make and VMMs Directly |
6363

6464
#### Sunday, December 8, 2024
6565

6666
| Time (CEST) | Session |
6767
| ------------- | -----------------------------------------------------------------------------------------------------|
68-
| 09:00-12:30 | Hackathon: Work on Project |
68+
| 09:00-10:30 | Unikraft Internals |
69+
| 10:30-12:30 | Project Work: Contribute to Unikraft, Unikraft Cloud, Application Catalogs |
6970
| 12:30-14:00 | Lunch |
70-
| 14:00-16:00 | Hackathon: Work on Project |
71-
| 16:00-18:00 | Judging and Award Ceremony |
71+
| 14:00-16:30 | Project Work |
72+
| 16:30-17:00 | Final Thoughts, Future Steps |
7273

73-
### Deploying Cloud Applications using KraftCloud
74+
### Deploying Cloud Applications using Unikraft Cloud
7475

75-
If you did not create an account already, signup [here](https://console.kraft.cloud/signup) and get a `token`.
76+
If you did not create an account already, signup [here](https://console.unikraft.cloud/signup) and get a `token`.
7677
You will be using that in the following sessions.
7778

78-
Once you have a token, follow the steps [here](http://docs.kraft.cloud/quickstart/) to deploy your first unikernel.
79+
Once you have a token, follow the steps [here](https://unikraft.cloud/docs/quickstart/) to deploy your first unikernel.
7980
If everything went well, deploy more applications following the tasks [here](TODO).
8081

8182
### Behind the Scenes: Using KraftKit to Operate Unikraft Applications
8283

83-
In the previous session, you deployed application using KraftCloud.
84+
In the previous session, you deployed application using Unikraft Cloud.
8485
Now you will build and run Unikraft-based application locally.
8586
With this, you will get a better look at what `kraft cloud` does behind the scenes.
8687

@@ -91,28 +92,28 @@ If you have extra time on your hands, go through the `Extra` section as well.
9192

9293
### Using Docker and Docker-based Filesystems
9394

94-
In order to bring your own application on KraftCloud, you need to build a minimal required filesystem.
95+
In order to bring your own application on Unikraft Cloud, you need to build a minimal required filesystem.
9596
We do that using `docker`.
9697
This is useful both to understand what is happening behind the scenes and to have a test environment for your application.
97-
In case there are issues with KraftCloud / KraftKit, you can use Docker to see if everything is in the right place and to assist in debugging.
98+
In case there are issues with Unikraft Cloud / KraftKit, you can use Docker to see if everything is in the right place and to assist in debugging.
9899

99100
Follow the steps [here](TODO) (only the ones under `Redis`) to see how you can port a new application on top of Unikraft.
100101
Mark the items as completed [here](TODO).
101102
Go through them orderly and aim to complete all items until the `Extra` section.
102103
If you have extra time on your hands, go through the `Extra` section as well.
103104

104-
### Debugging Unikraft / KraftCloud Applications
105+
### Debugging Unikraft / Unikraft Cloud Applications
105106

106107
When porting new applications, you can run into issues both on the Docker build and on the Unikraft runtime.
107-
To debug the issues, you can follow the instructions [here](https://docs.kraft.cloud/guides/features/debugging/).
108+
To debug the issues, you can follow the instructions [here](https://unikraft.cloud/docs/guides/features/debugging/).
108109
Get a hands-on experience with debugging by following the items [here](TODO).
109110

110111
### Hackathon
111112

112-
For the hackathon, please create teams of 2-3 people, and create your very own cloud-native application to run on KraftCloud.
113+
For the hackathon, please create teams of 2-3 people, and create your very own cloud-native application to run on Unikraft Cloud.
113114
Think of a cool application you've been waiting for a while to implement.
114-
Use your preferred programming language (supported by KraftCloud), employ any frameworks or existing software components as required, and then deploy it on KraftCloud.
115+
Use your preferred programming language (supported by Unikraft Cloud), employ any frameworks or existing software components as required, and then deploy it on Unikraft Cloud.
115116
After you create a team and decide on a project, fill [this spreadsheet](TODO) with the team name, members and project idea.
116117

117-
At the and of the hackathon, you should make a PR in the [KraftCloud `examples` repository](https://github.com/kraftcloud/examples) with your work.
118+
At the and of the hackathon, you should make a PR in the [Unikraft Cloud `examples` repository](https://github.com/unikraft-cloud/examples) with your work.
118119
We will be evaluating the project, focusing on functionality, originality, robustness, complexity, code quality and team work.

0 commit comments

Comments
 (0)