Add the peertube, mattermost, funkwhale, and casperlabs scripts to deploy an instance from the GridClient.

[A-Harby]

Description

Add the scripts for the applications (peertube, mattermost, funkwhale, and casperlabs).

The scripts are ready and working.

Related Issues

#1841

Checklist

• Tests included
• Build pass
• Documentation
• Code format and docstrings
• Screenshots/Video attached (needed for UI changes)

[Mahmoud-Emad]

After running the script, I got this error

the error message: Node 11 doesn't have enough resources: sru=50, mru=2 . while you filter with the required resources, is this issue reported?

[Mahmoud-Emad]

Good job ya 7arbii

[A-Harby]

After running the script, I got this error
the error message: Node 11 doesn't have enough resources: sru=50, mru=2 . while you filter with the required resources, is this issue reported?

#2750

[A-Harby]

Good job ya 7arbii

@Mahmoud-Emad I updated the code as requested and tried to match resource on every application with one used on dashboard.
And also add pingnode function to utils.

[Mahmoud-Emad]

Small comments :)

[A-Harby]

Small comments :)

I made the requested changes, could you please review it again?

[zaelgohary]

@A-Harby Really nice work! Just one comment. I suggest you downgrade the resources a bit. Maybe we can use the small package (CPU: 1 vCores, Memory: 2 GB, SSD: 15 GB) as there are not enough resources in devnet ATM. We can add the previous values in an object and use them in the vms instead of using static data. This applies to all solutions in the PR.

[A-Harby]

@A-Harby Really nice work! Just one comment. I suggest you downgrade the resources a bit. Maybe we can use the small package (CPU: 1 vCores, Memory: 2 GB, SSD: 15 GB) as there are not enough resources in devnet ATM. We can add the previous values in an object and use them in the vms instead of using static data. This applies to all solutions in the PR.

I will add the capacity object; I really liked the idea of changing it only in one place, but for the values, I used the same values as the small capacity package for every solution, like: https://www.manual.grid.tf/documentation/dashboard/solutions/funkwhale.html.

I think it would be better to follow the recommended capacity package for every solution, so what do you think?

[zaelgohary]

I think it would be better to follow the recommended capacity package for every solution, so what do you think?

Even better. Please, do.

[zaelgohary]

Good job, @A-Harby!

Needs some adjustments.

[zaelgohary]

I tried to ssh to the created Mattermost instance but I couldn't.

Also, I couldn't find the instance listed in the node contracts so I unlock its contract although it's listed in the mattermost deployment table.

Update:

I created another instance and I could ssh and access the deployment through the domain.

[zaelgohary]

In case of Funkwhale, I was able to access the domain and login successfully. However, I couldn't ssh to the instance.

[A-Harby]

1. For the Funkwhale SSH issue, it's an actual issue from the image itself, and it's reported here.

2. For listing contracts, it took a while to list, but it worked with me on both mattermost and Funkwhale.
   

3. For Mattermost SSH, it worked fine.
   

[Mahmoud-Emad]

Thank you Harby, Go ahead :)

[zaelgohary]

LGTM