Best posts made by QuixoticJustin

@quixoticjeremy said in Using In-Memory Databases, Anyone?:

@quixoticjustin said in Using In-Memory Databases, Anyone?:

Caching a traditional database to memory and having an in memory database do not behave the same. A pure in memory database has advantages to structure that databases writing to disk do not. There is no need to structure the data in preparation for writing to disk.

Was wondering when you'd show up on this one.

Finally one I can talk about.

With Sodium, for example, we use a "traditional" on disk database for the main data (well all data right now.) But we know that as we scale that that will not suffice for performance. Moving to in memory databases for things like session data is a standard model for application acceleration. Redis rules in this particular space, as it is a key value pair in memory cluster aware database system.

Redis is not Sodium's guaranteed in memory option, but certainly on the short list.

@dashrender said in What Do You Want in a Helpdesk and Ticketing System?:

email integrated. Users and support staff can create/update/close tickets via email.
Include attachments.

These things are just around the corner. It's already multi-user. And the email spot is there, just not plumbed, yet.

We've been working on an attachment design that isn't just "attachments" but makes them a bit more powerful and useful than a more traditional helpdesk.

I do believe that "Cock Beach: The Musical" was just proposed.

Some, more or less, standard things about in memory databases...

1. They require enough memory to load the entire database at "load time." There is no "making do with less memory." It just won't load. It's like a ramdisk for databases, there is no going to disk when you run out of memory, it just dies on you.
2. They take longer to fire up because they need to get everything from disk to ram before they can do anything.
3. While they might persist to disk at some point, that's not necessarily part of the database design. That's optional by product.
4. Data integrity is normally handled by clustering rather than writing to disk. You rely on high availability and serve requests from multiple nodes.

New fix is up. You can now click on the little lock icon at the top of the grid to unlock the deletion option.

For everyone's sake, don't google that show, it is not a real thing yet.

Sodium has some really basic pieces of that already built in using Salt. It's very early and definitely not where it should be, but it's Salt with a GUI that is specifically tackling this problem.

That's correct. We encrypt on both authentication and on payload. We should make an FAQ page about that. Another item for the task list

@rojoloco said in What Are You Doing Right Now:

Taking a crack at Sodium finally... account created, deploying agents now.

Awesome, that's what we like to hear. Let us know when you run into issues.

@dafyre said in Installing SaltStack Salt-Minion to Solus Linux:

@quixoticjustin said in Installing SaltStack Salt-Minion to Solus Linux:

Solus Linux lacks a native package for SaltStack and so to use it as a Salt Minion you have to grab the packages from GitHub and create it yourself. Special thanks to @scottalanmiller who looked into this and Exoner4ted in the Solus community who did the research and figured out how to make this work.

Remember to change "saltmastip" to the actual IP of your salt master or handle that however makes sense for you.

cd /tmp; wget https://github.com/saltstack/salt/archive/2018.3.zip
unzip 2018.3.zip; cd /tmp/salt-2018.3/
python /root/salt-2018.3setup.py install
echo "saltmasterip salt" >> /etc/hosts
cp /root/salt-2018.3/pkg/salt-minion.service /usr/lib/systemd/system/
systemctl daemon-reload && systemctl enable salt-minion
eopkg install python-pyzmq pycrypto python-msgpack python-tornado python-jinja pyyaml
systemctl restart salt-minion

Unfortunately this package is not self updating.

Once you get the initial client installed, you should be able to to push out new salt-minion packages via Salt itself, right?

Yes, but not using a repo. So you'd need to build your own installer / updater inside of a Salt state. Totally possible, but not as simple as telling it to update.

And more importantly, we have full agent install and scanning with Windows Server 2008. The only caveat here is that the .NET Framework 4.0 installation has to be done prior to attempting the install of Sodium.

@computerchip said in What Are You Watching Now:

I just started watching the TV show Westworld, so far so good.

I've had several people rave about that, I should watch it.

We are now able to add ElementaryOS to the matrix! Agent install is clean, but we have the same application enumeration problem as with several other Ubuntu-derived distros. Hopefully they can all be fixed together. Install is done using the "DEB Generic" installer.

If anyone has Windows 8 or 8.1 for testing, that would be great.

@quixoticjeremy said in August 18 Sodium Update Roundup:

@quixoticjustin said in August 18 Sodium Update Roundup:

Today's release codename is "The Hoff"

Looking forward to testing out Sodium "The Hoff" Edition tonight.

Is he your idol or something lmao?

He's everyone's hero. Where have you been?

We had a small update pushed earlier today, uptime is now displayed in logical units. Not just all in seconds, any longer.

Small release just went out, mostly updates to wording on the deep dive drill down asset view.

Okay, our latest update has just released. It's up and running now.

Okay, another release has gone out. Departments are a drop down now, so you can actually track things by department usefully.