Xen Orchestra - Community Edition - Installing with Yarn

geek-baba

@DustinB3403 I dont know the path of this file...

geek-baba

@DustinB3403 I am using the freenas with the community edition, what are the issues you see with this setup...

scottalanmiller

@shwetkprabhat said in Xen Orchestra - Community Edition - Installing with Yarn:

@DustinB3403 I am using the freenas with the community edition, what are the issues you see with this setup...
In what capacity are you using it?

geek-baba

@Danp I have used 2 different commands and both resulted in wiping the file:

sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -n stable
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -f

1st one I used to for last update and 2nd one to test when you asked to do it today.

geek-baba

@scottalanmiller as a NAS

DustinB3403

@shwetkprabhat said in Xen Orchestra - Community Edition - Installing with Yarn:

@DustinB3403 I dont know the path of this file...

This file would be at /opt/xo-server/.xo-server.yaml by default ls won't show it. But trust that its there.

DustinB3403

@shwetkprabhat said in Xen Orchestra - Community Edition - Installing with Yarn:

@Danp I have used 2 different commands and both resulted in wiping the file:

sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -n stable

sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -f

1st one I used to for last update and 2nd one to test when you asked to do it today.

Are you creating this file from scrap?

Do this

cd /
cd /opt/xo-server
sudo nano .xo-server.yaml

scottalanmiller

@shwetkprabhat said in Xen Orchestra - Community Edition - Installing with Yarn:

@scottalanmiller as a NAS

But in what capacity as a NAS? I assume NFS, consumed by XenServer? No standalone NAS or SAN of this nature should ever be used in production for something like that. If another use, I'd need to know what it is.

geek-baba

@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:

/opt/xo-server/.xo-server.yaml

I see this file, I believe I have been creating a new file which is causing the issue. I didn't realize since the new file also works flawlessly.

DustinB3403

@scottalanmiller said in Xen Orchestra - Community Edition - Installing with Yarn:

@shwetkprabhat said in Xen Orchestra - Community Edition - Installing with Yarn:

@scottalanmiller as a NAS

But in what capacity as a NAS? I assume NFS, consumed by XenServer? No standalone NAS or SAN of this nature should ever be used in production for something like that. If another use, I'd need to know what it is.

I'd use a synology as a NFS server for onsite backup, directly into XO as an NFS target. Absolutely.

DustinB3403

@shwetkprabhat said in Xen Orchestra - Community Edition - Installing with Yarn:

@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:

/opt/xo-server/.xo-server.yaml

I see this file, I believe I have been creating a new file which is causing the issue. I didn't realize since the new file also works flawlessly.

haha. . . . that is what I was trying to get at a few days ago.

If you edit the file (we create for you) this issue will disappear.

geek-baba

@scottalanmiller I am using freeness using NFS to backup the VM's, its working flawlessly.

scottalanmiller

@shwetkprabhat said in Xen Orchestra - Community Edition - Installing with Yarn:

@scottalanmiller I am using freeness using NFS to backup the VM's, its working flawlessly.

Oh yes, as secondary storage it is fine. I'd still not advise FreeNAS, you should use FreeBSD, CentOS, Suse or Ubuntu instead, but it's not a big issue.

geek-baba

@DustinB3403 so i deleted the file I created and updated the /opt/xo-server/.xo-server.yaml with the following content (which was using for the new file) and I was getting an error "Cant get to /", I reverted back to last night snapshot.


# BE *VERY* CAREFUL WHEN EDITING!
# YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR ALIGNMENT!
# visit http://www.yamllint.com/ to validate this file as needed

#=====================================================================

# Example XO-Server configuration.
#
# This file is automatically looking for at the following places:
# - `$HOME/.config/xo-server/config.yaml`
# - `/etc/xo-server/config.yaml`
#
# The first entries have priority.
#
# Note: paths are relative to the configuration file.

#=====================================================================

# It may be necessary to run XO-Server as a privileged user (e.g.
# `root`) for instance to allow the HTTP server to listen on a
# [privileged ports](http://www.w3.org/Daemon/User/Installation/PrivilegedPorts.html).
#
# To avoid security issues, XO-Server can drop its privileges by
# changing the user and the group is running with.
#
# Note: XO-Server will change them just after reading the
# configuration.

# User to run XO-Server as.
#
# Note: The user can be specified using either its name or its numeric
# identifier.
#
# Default: undefined
#user: 'nobody'

# Group to run XO-Server as.
#
# Note: The group can be specified using either its name or its
# numeric identifier.
#
# Default: undefined
#group: 'nogroup'

#=====================================================================

# Configuration of the embedded HTTP server.
http:

  # Hosts & ports on which to listen.
  #
  # By default, the server listens on 0.0.0.0:80.
  listen:
    # Basic HTTP.
    -
      # Address on which the server is listening on.
      #
      # Sets it to '127.0.0.1' to listen only on the local host.
      #
      # Default: '0.0.0.0' (all addresses)
      #hostname: '127.0.0.1'

      # Port on which the server is listening on.
      #
      # Default: undefined
      port: 80

      # Instead of `host` and `port` a path to a UNIX socket may be
      # specified (overrides `host` and `port`).
      #
      # Default: undefined
      #socket: './http.sock'

    # Basic HTTPS.
    #
    # You can find the list of possible options there https://nodejs.org/docs/latest/api/tls.html#tls.createServer
    -
    #   # The only difference is the presence of the certificate and the
    #   # key.
    #   #
    #   #hostname: '127.0.0.1'
      port: 443

    #   # File containing the certificate (PEM format).
    #
    #   # If a chain of certificates authorities is needed, you may bundle
    #   # them directly in the certificate.
    #   #
    #   # Note: the order of certificates does matter, your certificate
    #   # should come first followed by the certificate of the above
    #   # certificate authority up to the root.
    #   #
    #   # Default: undefined
      cert: '/home/xoa/certs/xo-local.crt'

    #   # File containing the private key (PEM format).
    #   #
    #   # If the key is encrypted, the passphrase will be asked at
    #   # server startup.
    #   #
    #   # Default: undefined
      key: '/home/xoa/certs/xo-local.key'

  # If set to true, all HTTP traffic will be redirected to the first
  # HTTPs configuration.
  #redirectToHttps: true

  # List of files/directories which will be served.
  mounts:
    '/': '/root/xo-web/dist/'

  # List of proxied URLs (HTTP & WebSockets).
  proxies:
    # '/any/url': 'http://localhost:54722'

# HTTP proxy configuration used by xo-server to fetch resources on the
# Internet.
#
# See: https://github.com/TooTallNate/node-proxy-agent#maps-proxy-protocols-to-httpagent-implementations
#httpProxy: 'http://jsmith:[email protected]:3128'

#=====================================================================

# Connection to the Redis server.
redis:
    # Unix sockets can be used
    #
    # Default: undefined
    #socket: /var/run/redis/redis.sock

    # Syntax: redis://[db[:password]@]hostname[:port][/db-number]
    #
    # Default: redis://localhost:6379/0
    #uri: redis://redis.company.lan/42

    # List of aliased commands.
    #
    # See http://redis.io/topics/security#disabling-of-specific-commands
    #renameCommands:
    #  del: '3dda29ad-3015-44f9-b13b-fa570de92489'
    #  srem: '3fd758c9-5610-4e9d-a058-dbf4cb6d8bf0'


# Directory containing the database of XO.
# Currently used for logs.
#
# Default: '/var/lib/xo-server/data'
#datadir: '/var/lib/xo-server/data'

DustinB3403

@shwetkprabhat I'm sending you a Private message.

geek-baba

@DustinB3403 thanks for helping out and resolving the issue! I cant thank you enough for the time you spent (remote-ing into the machine yesterday and helping all day today via private messages).

For the larger community it looks like if you create a new config.yaml file, XO will register that as config source and any changes after that is not taken into the account, you should use the default config file created by the script (i.e. /opt/xo-server/.xo-server.yaml) to start with or update the installation using the update script and then manually update the default config file.

DustinB3403

@shwetkprabhat glad we were able to sort it out for you.

Texkonc

Yarn? I knew Xen was full of duct tape and bubble gum.

DustinB3403

@Texkonc . . .

Texkonc

@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:

@Texkonc . . .

Friiiiiday!