Revamped Compute UI, Multi-service Deployments, Crypto Payment Option & Platform Updates

announcements
1

Revamped Compute UI & Multi-service Deployments

We are excited to announce significant updates to our platform, focusing on enhancing your experience on managing your compute deployments. Below are the details of the latest features:

  1. New Dashboard UI & Projects:

    • We have introduced a new dashboard UI tailored for showcasing compute projects (formerly referred to as clusters). Every project will display both the overall count of instances and the breakdown for each instance state, including provisioned, starting, closed, and failed.

    • Projects allow you to organize your compute instances efficiently. You can create a new project by providing a name and description, and then manage instances within that project.

    • Now, you can create different types of instances under the same project, whether it’s a custom Docker image or deploying from various templates.

  2. Updated Instance Page:

    • The instance page has been revamped for better usability.

    • You’ll find an instance details card showcasing important information such as instance name, status, ID, scaling type, region, last updated date, and monthly price.

    • A sidebar navigation facilitates easy access to different sections of the page, including instance overview, logs, events, deployment details, activity, settings, and domain management.

  3. Service Page:

    • Each deployed service now has a dedicated service page.

    • The service page displays a detailed service card containing information such as service name, image tag, scaling type, service status, instance plan, and specifications (CPU, RAM, and storage used for that service).

    • You can also access service logs, port policy, metrics, and shell access for the selected service within the instance.

  4. Bulk Actions:

    • Users now have the ability to perform bulk actions such as deleting and closing multiple instances simultaneously. Simply select instances using the checkbox provided in the top left corner of each instance.

  5. Multi-Services Deployment:

    • With the Spheron CLI, you can now deploy multiple services within a single instance.

    • Simply install our npm package @spheron/cli and follow the installation and usage guide provided in the new instance under the multi-services tab.

  6. Rename Instance:

    • You now have the flexibility to rename instances according to your preferences.

    • Simply click on the dropdown menu and select the “Rename instance” option to customize the name of your instance.

  7. Easy Navigation:

    • We’ve added breadcrumbs for seamless navigation between project pages, instance pages, and service pages.

    • Additionally, a sidebar allows for easy navigation within different sections of the pages.

Introducing New Crypto Payment Option

We are thrilled to introduce a new payment option aimed at enhancing your experience with topping up compute credits on our platform. We have added a recommended payment method for topping up compute credits on the platform - Crypto Payment. Here are the details:

  • When you navigate to the compute billing page and click on the “Topup” button, you will now see the option for Crypto payment as the first choice.

  • Simply enter the desired amount (greater than $15) and select Crypto Payment.

  • You will then be redirected to the payment page where you can seamlessly connect your wallet, choose your preferred chain, and select the token you wish to pay with.

  • With just a few clicks, your payment will be swiftly processed, and the amount will be immediately added to your compute balance.

It’s important to note that while Crypto Payment is now available as a recommended method, all other existing payment options will continue to function as usual.

Platform Improvements & Fixes

  • Pricing Calculation: We have made substantial enhancements to the performance of calculating prices for instance plans based on your selection of CPU, RAM, and Storage on both new instance and update instance pages.

  • Instance Logs: We have fixed the issue where clicking the Refresh Logs button for a selected instance failed to fetch the logs. Additionally, we have addressed the issue of logs not triggering after an instance is updated or restarted.

  • Instance Shell: We have resolved the issue where scrolling within shell container was not working properly.

  • Compute Usage: We have added a time along side creation date and last updated date for each instance in compute usage of a particular project.

  • New Instance Page: We have rectified an intermittent issue where incorrect cluster type or scaling type was getting selected on new instance page.