Skip to content

Tags: aleph-im/aleph-vm

Tags

1.6.0

Toggle 1.6.0's commit message
Fixed docs url with the new one

1.6.0-rc1

Toggle 1.6.0-rc1's commit message
Fix wrong variable being used when fetching from aggregate

1.5.1

Toggle 1.5.1's commit message
Fix reserved space calculation

1.5.0

Toggle 1.5.0's commit message
Make the diagnostic example code compatible with pydantic 1 and 2

so it doesn't fail in the ci

1.5.0-rc1

Toggle 1.5.0-rc1's commit message
Fix: Increase Aleph SDK dependency to the new version 2.0.0

1.4.2

Toggle 1.4.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Allow /56 subnet for ipv6 pool (#761)

Needed for some crn

1.4.1

Toggle 1.4.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Fix DiagnosticVM, force ipv4 connexion on /internet check (#760)

This fix issue reported by node owner where if they enable a ipv6 and it's not working, it also break the diagnostic /internet check

1.4.0

Toggle 1.4.0's commit message
Jira ticket: ALEPH-419

CRN with bad IPv6 config were having bad metrics, as /status/check/fastapi was too slow which looking further into it , came from /vm/63faf8b5db1cf8d965e6a464a0cb8062af8e7df131729e48738342d956f29ace/internet always taking 5 seconds, even if it ultimately returned positive resurlt.

Coincidentally 5 seconds is the timeout configured in check_url inside the diagnostic vm (example_fastapi/main.py)

To reproduce issue
set the DNS server via environment variable
```env
ALEPH_VM_DNS_NAMESERVERS = '[2001:41d0:3:163::1, 9.9.9.9]'
```
that ipv6 server being unreachable
and set ip pool to default one
```
ALEPH_VM_IPV6_ADDRESS_POOL = fc00:1:2:3::/64
```

Solution:

Further analysis is that the diagnostic VM tried to connect to the ipv6 DNS server, did timout after  5 seconds then proceeded normally with the ipv4 DNS

Put the ipv4 DNS server BEFORE the ipv6 one.
Also disable the ipv6 server if ipv6 is not enabled for the VM. That modification was done for instances but failed to be reproduced for programs

1.4.0-rc1

Toggle 1.4.0-rc1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Implemented GPU compatibility system (#747)

* Feature: Added options to get GPU compatibilities from a settings aggregate.

* Fix: Refactored to also return the model name from the aggregate and use the same device_id format.

* Fix: Include GPU list and move the VM egress IPv6 check on the connectivity check to start notifying the users about the next requirement.

* Fix: Solved code quality issues.

* Fix: Put definitive settings aggregate address

* Fix: Solved issue with type casting and moved the aggregate check.

* Check community payment flow (#751)

* Implement community payment check WIP

* isort

* Check community flow at allocation

* Community flow  : fix after testing

* mod Use singleton for the Setting Aggregate

* fix test

* Implement community wallet start time

---------

Co-authored-by: Olivier Le Thanh Duong <olivier@lethanh.be>

1.3.1

Toggle 1.3.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Unified branding on node index page style (#745)

* Fix: Added new branding logo to unify node index page aesthetic.

* Fix: Replace Aleph.im by Aleph Cloud on the first sentence.