Changelog
April 7, 2023

3.2.0 Notable Changes

This post highlights some notable things that will change in version 3.2.0 of our platform.

3.2.0 Notable Changes

Low-code tools are going mainstream

Purus suspendisse a ornare non erat pellentesque arcu mi arcu eget tortor eu praesent curabitur porttitor ultrices sit sit amet purus urna enim eget. Habitant massa lectus tristique dictum lacus in bibendum. Velit ut viverra feugiat dui eu nisl sit massa viverra sed vitae nec sed. Nunc ornare consequat massa sagittis pellentesque tincidunt vel lacus integer risu.

  1. Vitae et erat tincidunt sed orci eget egestas facilisis amet ornare
  2. Sollicitudin integer  velit aliquet viverra urna orci semper velit dolor sit amet
  3. Vitae quis ut  luctus lobortis urna adipiscing bibendum
  4. Vitae quis ut  luctus lobortis urna adipiscing bibendum

Multilingual NLP will grow

Mauris posuere arcu lectus congue. Sed eget semper mollis felis ante. Congue risus vulputate nunc porttitor dignissim cursus viverra quis. Condimentum nisl ut sed diam lacus sed. Cursus hac massa amet cursus diam. Consequat sodales non nulla ac id bibendum eu justo condimentum. Arcu elementum non suscipit amet vitae. Consectetur penatibus diam enim eget arcu et ut a congue arcu.

Vitae quis ut  luctus lobortis urna adipiscing bibendum

Combining supervised and unsupervised machine learning methods

Vitae vitae sollicitudin diam sed. Aliquam tellus libero a velit quam ut suscipit. Vitae adipiscing amet faucibus nec in ut. Tortor nulla aliquam commodo sit ultricies a nunc ultrices consectetur. Nibh magna arcu blandit quisque. In lorem sit turpis interdum facilisi.

  • Dolor duis lorem enim eu turpis potenti nulla  laoreet volutpat semper sed.
  • Lorem a eget blandit ac neque amet amet non dapibus pulvinar.
  • Pellentesque non integer ac id imperdiet blandit sit bibendum.
  • Sit leo lorem elementum vitae faucibus quam feugiat hendrerit lectus.
Automating customer service: Tagging tickets and new era of chatbots

Vitae vitae sollicitudin diam sed. Aliquam tellus libero a velit quam ut suscipit. Vitae adipiscing amet faucibus nec in ut. Tortor nulla aliquam commodo sit ultricies a nunc ultrices consectetur. Nibh magna arcu blandit quisque. In lorem sit turpis interdum facilisi.

“Nisi consectetur velit bibendum a convallis arcu morbi lectus aecenas ultrices massa vel ut ultricies lectus elit arcu non id mattis libero amet mattis congue ipsum nibh odio in lacinia non”
Detecting fake news and cyber-bullying

Nunc ut facilisi volutpat neque est diam id sem erat aliquam elementum dolor tortor commodo et massa dictumst egestas tempor duis eget odio eu egestas nec amet suscipit posuere fames ded tortor ac ut fermentum odio ut amet urna posuere ligula volutpat cursus enim libero libero pretium faucibus nunc arcu mauris sed scelerisque cursus felis arcu sed aenean pharetra vitae suspendisse ac.

We continue to work towards shipping improvements to our platform. The latest iteration brings some new features and changes to the way our platform operates.

This post will highlight some of the things coming up in 3.2.0 release. If you’re curious about when this is happening we’ve posted a maintenance schedule on our status page.

Cluster Page

In 3.1.0 if you clicked on a cluster you would just be taken to a placeholder page with nothing on it. In 3.2.0 however you’ll notice that it’s been filled out.

cluster detail page

The cluster detail page displays the list of nodes in a given cluster. On each node you’ll also be able to see which instances are running on them. This should give you a bird’s eye-view of what’s happening inside your cluster.

Health Check

Cluster health is an important part of instellar’s operations. We have real-time monitoring on all clusters as soon as it’s added to instellar. If a deployment is created and the cluster is unhealthy, instellar knows to not deploy to it.

Other parts of the UI are now also aware of the cluster health. For example, if a cluster is unhealthy, the instance page and installation page will make sure users do not accidentally issue commands onto the cluster. It will prompt the user to make sure the cluster is healthy before resuming any operations.

instance check cluster
installation check cluster

We believe this will help improve the robustness of the instellar platform.

Uplink

We have a demo of this in our product demo post, where we outline some of the benefits of uplink. If you already have a cluster up and running and deploying applications you do not need to worry about uplink for now.

Uplink is an optional module. Currently uplink is still in development and testing phase. Once it stabilizes we will do an official announcement of it with a lot more documentatin an detail explaining what it is, how it works, and why you should use uplink for all your clusters moving forward.

LXD Projects

Instellar will now make use of LXD projects when managing containers. LXD projects provide isolation for containers. Previously all containers were deployed to the default project in LXD. Once the upgrade is completed and all your instances are migrated to using projects when you run lxc list you will no longer see a list of all the containers running.

+------+-------+------+------+------+-----------+----------+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS | LOCATION |
+------+-------+------+------+------+-----------+----------+

With the new change you will need to call lxc list --all-projects if you wish to see all the containers running on your cluster.

+---------------------+--------------------+---------+----------------------+------+-----------+-----------+--------------------+
|       PROJECT       |        NAME        |  STATE  |         IPV4         | IPV6 |   TYPE    | SNAPSHOTS |      LOCATION      |
+---------------------+--------------------+---------+----------------------+------+-----------+-----------+--------------------+
| upmaru-stage.rdio   | rdio-warden-01     | RUNNING | 240.4.151.8 (eth0)   |      | CONTAINER | 0         | warden-terminal-01 |
+---------------------+--------------------+---------+----------------------+------+-----------+-----------+--------------------+
| upmaru-stage.uplink | uplink-744b0e89-01 | RUNNING | 240.4.151.216 (eth0) |      | CONTAINER | 0         | warden-terminal-01 |
+---------------------+--------------------+---------+----------------------+------+-----------+-----------+--------------------+

Existing containers will have no impact, this means instellar will only upgrade your instances to using projects when bootstrapping new instances. If you however wish to try out this new behaviour you can manually deactivate an instance and execute bootstrap. Instellar will setup a new project for the instance automatically.

Why are we doing this? In short there are some features we’re planning in the future that will rely on utilizing LXD projects. We want to make sure moving forward isolating instances under LXD projects is the default behaviour.

OpsMaru is a no code end-to-end deployment platform builder. It's made for freedom, flexibility, speed and simplicity.

By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information.