Everyone, please welcome my daughter Diana into the world.

She arrived at 7:26am today!

This guide assumes you already have a running Ubuntu 15.10 system on which you want to configure Xen Orchestra, everything else is documented below.

TL;DR: Run this command as root on Ubuntu 15.10...

sudo curl https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh | bash

---

During the installation of your OS, you'll want to create a user outside of root, I made my user account xoadmin

How to Install Xen Orchestra Source on Ubuntu 15.10 (self compiled) AKA MANUAL installation

sudo apt-get install --yes nfs-common
curl -sL https://deb.nodesource.com/setup_5.x | sudo -E bash -
sudo apt-get install --yes nodejs
curl -o /usr/local/bin/n https://raw.githubusercontent.com/visionmedia/n/master/bin/n
chmod +x /usr/local/bin/n
n stable
node -v
npm -v
sudo apt-get install --yes build-essential redis-server libpng-dev git python-minimal
git clone -b stable https://github.com/vatesfr/xo-server
git clone -b stable https://github.com/vatesfr/xo-web
cd xo-server
sudo npm install && npm run build
cp sample.config.yaml .xo-server.yaml
nano .xo-server.yaml

#Edit and uncomment it to have the right path to XO-Web, because XO-Server embeds an HTTP server (we assume that XO-Server and XO-Web are on the same directory). It's near the end of the file:
#  mounts: '/': '../home/xoadmin/xo-web/dist/
#  save and exit

cd ~
cd ../xo-web
sudo npm i [email protected]
sudo npm install
sudo npm run build
cd ../xo-server
sudo npm start

The scripted installation thanks to @scottalanmiller

Github Repo

Below is the preferred Installation method. It includes the systemctl xo-server.service written by @Danp

sudo bash
<password>
sudo curl https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh | bash
<password>

In your favorite web-browser go to this VM's IP Address, login with the default user: [email protected] and "admin" for the password. Update your Login Details!!

Add your Xen Server(s) and go to town.

Automatically Start XO at Boot - See this Post by @Danp Also copied below.

Create a file in /etc/systemd/system/xo-server.service and enter the below into it.

# systemd service for XO-Server.

 [Unit]
 Description= XO Server
 After=network-online.target

 [Service]
 WorkingDirectory=/opt/xo-server/
 ExecStart=/usr/local/bin/node ./bin/xo-server
 Restart=always
 SyslogIdentifier=xo-server

 [Install]
 WantedBy=multi-user.target

Save the file, and then run to enable the service at start up.

sudo systemctl enable xo-server.service

To monitor the service you can then run

journalctl -u xo-server -f -n 50

For everyone on the newer releases of the "stable build" at least as of April-8-2016 there appears to be a bug when attempting to mount an NFS share; to resolve this follow the short process below

• Login to your XO web console
• Go to Backup
• Select Remote Stores
• Add your NFS Share, it'll likely fail out(unless it's been fixed since this posting)
• Back on your XO console go to /tmp/xo-server/mounts
• Run "ls" to see what mount is listed on your server
• Next run "mount -t nfs nfs-server-ip-address:/path/to-share remote-#"

Replacing nfs-server-ip-address with the actual IP of the remote server and the remote-# with whatever is listed on your console.

Register for today's live demo April 6, 11 am PT / 2 pm ET.

Host: Alex Bykovskyi, Solutions Architect, StarWind

New StarWind Virtual SAN Free comes completely unrestricted delivering all the features you get in the commercial version. Unlike the previous free version, new VSAN Free delivers unlimited node count, features, and capacity served. It can now be used in any deployment scenario, be it Hyper-Converged, “Compute and Storage Separated”, or even a combination of both. Thanks to multiprotocol support, featuring iSCSI, SMB3, and NFS, including RDMA-capable iSER, NVMf, and SMB Direct, StarWind VSAN easily integrates into any infrastructure, be it virtualized or not. In addition, support for VVOLs, SCVMM, and ready-to-use PowerShell scripts help users to speed up and simplify automated deployment, management, and monitoring of their Virtual SAN infrastructure.

Join our Live Demo to learn how to build a completely free multi-node hyper-converged environment with StarWind and your hypervisor of choice!

*Virtualize responsibly!

Hey all!

On November 11th I'll be gaming for 24 hours straight to raise money for Golisano Children's Hospital,please hit my page up here and donate to help raise funds.

Thanks,

DustinB

@nerdydad said in Fake Wall or Wall Closet?:

Any suggestions?

Tell your CFO to stop giving tours of your server room and focus on saving money for more important things.

Messing with @Minion-Queen

I'm wondering why I don't have a tank!

Since Scott is our resident expert on said topic, I figure here would be as good a place as any to post SW articles regarding IT people who are in a position where they are unknowingly building an IPOD.

@BradfromxByte thank you for dealing with all of the back and forth and kick ass servers.

Security Researcher discovers plan text passwords used for Microsoft rdp

@stacksofplates said in Managing Publicly hosted Linux Servers through Cockpit:

@dustinb3403 said in Managing Publicly hosted Linux Servers through Cockpit:

@stacksofplates said in Managing Publicly hosted Linux Servers through Cockpit:

@dustinb3403 said in Managing Publicly hosted Linux Servers through Cockpit:

@stacksofplates said in Managing Publicly hosted Linux Servers through Cockpit:

@dustinb3403 said in Managing Publicly hosted Linux Servers through Cockpit:

@stacksofplates said in Managing Publicly hosted Linux Servers through Cockpit:

There's a big movement now around SBOM with tools like in-toto, SPIFFE/SPIRE, TUF, and a lot more. We are working with gov't clients and they are headed towards requiring SBOM information for each release.

It's been mandated that software now include a SBOM (see my recent post in IT news).

Yeah but that mandate is only for open source (for whatever dumb reason). I'm all for SBOMs for open source software, but it's ignoring the fact that the issue has historically come from closed source software. An SBOM is much less effective when you already have access to 99% of what's included in the product.

Well it mentions open source specifically, but also targets close source

Ah I read the first part. It made it sound like it was only open source.

Not that anyone but the US Government will know what is actually included in any specific closed source software

If enterprises are smart they will require it too. And at that point it would hopefully just be publically available.

While I would agree, the reality is that so many software companies are in business solely because their software is closed source.

The RHEL's of the world are far and few in-between

@stacksofplates said in Managing Publicly hosted Linux Servers through Cockpit:

@dustinb3403 said in Managing Publicly hosted Linux Servers through Cockpit:

@stacksofplates said in Managing Publicly hosted Linux Servers through Cockpit:

@dustinb3403 said in Managing Publicly hosted Linux Servers through Cockpit:

@stacksofplates said in Managing Publicly hosted Linux Servers through Cockpit:

There's a big movement now around SBOM with tools like in-toto, SPIFFE/SPIRE, TUF, and a lot more. We are working with gov't clients and they are headed towards requiring SBOM information for each release.

It's been mandated that software now include a SBOM (see my recent post in IT news).

Yeah but that mandate is only for open source (for whatever dumb reason). I'm all for SBOMs for open source software, but it's ignoring the fact that the issue has historically come from closed source software. An SBOM is much less effective when you already have access to 99% of what's included in the product.

Well it mentions open source specifically, but also targets close source

Ah I read the first part. It made it sound like it was only open source.

Not that anyone but the US Government will know what is actually included in any specific closed source software

@stacksofplates said in Managing Publicly hosted Linux Servers through Cockpit:

@dustinb3403 said in Managing Publicly hosted Linux Servers through Cockpit:

@stacksofplates said in Managing Publicly hosted Linux Servers through Cockpit:

There's a big movement now around SBOM with tools like in-toto, SPIFFE/SPIRE, TUF, and a lot more. We are working with gov't clients and they are headed towards requiring SBOM information for each release.

It's been mandated that software now include a SBOM (see my recent post in IT news).

Yeah but that mandate is only for open source (for whatever dumb reason). I'm all for SBOMs for open source software, but it's ignoring the fact that the issue has historically come from closed source software. An SBOM is much less effective when you already have access to 99% of what's included in the product.

Well it mentions open source specifically, but also targets close source

@stacksofplates said in Managing Publicly hosted Linux Servers through Cockpit:

There's a big movement now around SBOM with tools like in-toto, SPIFFE/SPIRE, TUF, and a lot more. We are working with gov't clients and they are headed towards requiring SBOM information for each release.

It's been mandated that software now include a SBOM (see my recent post in IT news).

New Executive Order mandates Software Bill of Materials, naming open source specifically.

The executive order recognized the vital importance of open-source software. It reads in part: "Within 90 days of publication of the preliminary guidelines … shall issue guidance identifying practices that enhance the security of the software supply chain." Open-source software is specifically named.

A converter is the best thing I've used, we used this at my last position, but its only 100M and 1080p.

@dashrender said in Managing Publicly hosted Linux Servers through Cockpit:

@dustinb3403 said in Managing Publicly hosted Linux Servers through Cockpit:

@dashrender said in Managing Publicly hosted Linux Servers through Cockpit:

@dustinb3403 said in Managing Publicly hosted Linux Servers through Cockpit:

@travisdh1 said in Managing Publicly hosted Linux Servers through Cockpit:

@dustinb3403 said in Managing Publicly hosted Linux Servers through Cockpit:

This is just something that came to mind as I am working on something else, which is if I had multiple linux servers hosted in client environments (just pretend 1 each) that I had to manage.

Wouldn't using cockpit to manage each of these servers be the best approach?

So my question is for the @scottalanmiller and @JaredBusch's etc for these customers, do you simply access the client site through a remote tool or VPN and then do whatever? Or do you publicly host Cockpit from the client site (using a static ip) to then access cockpit (either directly to the host) or to one master Cockpit Administration server?

And if you are publicly hosting cockpit, I assume you're doing so individually for each system and not tying them all together through a single administrative cockpit interface.

#ProbablyInsane

Ansible or Salt would be my go-to instead of cockpit, but sure you could. I'd assume you already have a means to access the client's networks, so just use that access.

Yeah, but Ansible or Salt would be for people who know how to use those tools, many MSP/ITSP still have service desk type folks who would be tasked with minor things like "reboot this server"

Are you really asking for those people? or for yourself?
that said - I don't know how to use Ansible or Salt, so I know my place there :)

I'm just asking in general, I'm doing some lab work, and thought, damn it sucks having to touch 1000 cockpit pages individually. Which of course still would occur with them all tied to a single cockpit "server".

But then I thought, how is this being managed on a public facing server. SSH I assume using keypairs is the obvious thing, but even that seems tedious.

How is that tedious? it should be a once and done thing...

Yeah, but once and done means setup once for every possible system.

@dashrender said in Managing Publicly hosted Linux Servers through Cockpit:

@dustinb3403 said in Managing Publicly hosted Linux Servers through Cockpit:

@travisdh1 said in Managing Publicly hosted Linux Servers through Cockpit:

@dustinb3403 said in Managing Publicly hosted Linux Servers through Cockpit:

This is just something that came to mind as I am working on something else, which is if I had multiple linux servers hosted in client environments (just pretend 1 each) that I had to manage.

Wouldn't using cockpit to manage each of these servers be the best approach?

So my question is for the @scottalanmiller and @JaredBusch's etc for these customers, do you simply access the client site through a remote tool or VPN and then do whatever? Or do you publicly host Cockpit from the client site (using a static ip) to then access cockpit (either directly to the host) or to one master Cockpit Administration server?

And if you are publicly hosting cockpit, I assume you're doing so individually for each system and not tying them all together through a single administrative cockpit interface.

#ProbablyInsane

Ansible or Salt would be my go-to instead of cockpit, but sure you could. I'd assume you already have a means to access the client's networks, so just use that access.

Yeah, but Ansible or Salt would be for people who know how to use those tools, many MSP/ITSP still have service desk type folks who would be tasked with minor things like "reboot this server"

Are you really asking for those people? or for yourself?
that said - I don't know how to use Ansible or Salt, so I know my place there :)

I'm just asking in general, I'm doing some lab work, and thought, damn it sucks having to touch 1000 cockpit pages individually. Which of course still would occur with them all tied to a single cockpit "server".

But then I thought, how is this being managed on a public facing server. SSH I assume using keypairs is the obvious thing, but even that seems tedious.

@stuartjordan said in Convert Between Popular VM Formats for Free with StarWind:

Looks good though if it does all. I assume it's a windows based product though?

IIRC, yes you have to install it on a Windows system and then connect to the hypervisor in question to create / export the VM you're wanting to convert.

It's been a while since I've last had to convert anything.