Really excited about this release. It's very basic at this point and obviously just a technical preview. But this is the first nearly useful functionality of the system and we are super excited to see people start using it very soon. A few more steps before it is ready for people to actually dive into and start using as ticketing, even emails don't work at this point, but you can see sample tickets and get a feel for how it will work. We are really looking for feedback here, what are we missing, what should it do differently?

We've had a long day of testing but we have not only rolled out new code of our own, but updated our core platform, done failover server testing successfully and identified a security and stability issue with an upstream code base that we are able to work with them on. So you may continue testing again and let us know of any issues.

Thanks everyone!

We've offlined even the main application while we are looking into errors at this point to keep the application from messing with the back end while we are troubleshooting.

Current status is: GUI online but we've identified a bug that was introduced during last night's testing just before we went offline for the night. This is keeping the backend from working so updates have stopped and new systems are not joining. We'll be working on this today, but it might be offline much of the day. So feel free to log in and poke around, but you won't be able to add machines nor to see current status in the system.

Getting a thread together that you can follow for the latest Sodium system status.

GitLab came back, we are back to development work.

Two more hours and Microsoft isn't even to the point of giving estimates yet.

We have Debian 9 tested and working now.

We just got word from Microsoft, about one more hour.

Data collection has definitely improved some at this point. We are seeing more data and the main table is generally filled out properly. So small steps.

We were hoping for more to show tonight, but Azure outages killed our GitLab and we'd rather stay productive on other things than work around our deployment processes, at least for the moment.