Difference between revisions of "NikXOLocalService"
From PDP/Grid Wiki
Jump to navigationJump to search| Line 1: | Line 1: | ||
= NikXO Local Virtual Machine Service = | = NikXO Local Virtual Machine Service = | ||
| − | The NikXO Local (NXOL) service provides stand-alone virtual machines as Infrastructure-as-a-Service (IaaS) to Nikhef users, using a self-service | + | The NikXO Local (NXOL) service provides stand-alone virtual machines as Infrastructure-as-a-Service (IaaS) to Nikhef users, using a self-service auto-provisioning portal based on XenOrchestra and a dedicated network to which access is liberally open from within Nikhef, but that is (by default and by design) closed to the outside world. It allows Nikhef users to try out stuff on a virtual machine that they can and should manage by themselves, but whose management they ''may'' share with everyone at Nikhef. |
=== Important notice === | === Important notice === | ||
| Line 19: | Line 19: | ||
== What can you expect == | == What can you expect == | ||
| − | The NXOL service provides one-off VMs that are stand-alone, but can use the standard Nikhef account management (LDAP) functionality if you want to. You cannot do NFS traffic from here to other Nikhef systems, although CIFS (SMB, Windows) access may work if you try with a samba | + | The NXOL service provides one-off VMs that are stand-alone, but can use the standard Nikhef account management (LDAP) functionality if you want to. You cannot do NFS traffic from here to other Nikhef systems, although CIFS (SMB, Windows) access may work if you try with a samba client on your machine. |
You own the entire virtual machine, and need to do your own systems administration. We recommend you use the CentOS7 PXE provisioning service to install VMs. If you don�t a few ISO CD-ROM images are available to you to boot from, but then you have to use the virtual console to complete the interactive installation. | You own the entire virtual machine, and need to do your own systems administration. We recommend you use the CentOS7 PXE provisioning service to install VMs. If you don�t a few ISO CD-ROM images are available to you to boot from, but then you have to use the virtual console to complete the interactive installation. | ||
| − | All machines must use DHCP/BOOTP to acquire an internet address in the �nik-xo-localaccess� network (145.116.56.128/25) - the lease you get is really long (30 days) | + | All machines must use DHCP/BOOTP to acquire an internet address in the �nik-xo-localaccess� network (145.116.56.128/25) - the lease you get is really long (30 days) and can be renewed, but since you share the network with all other Nikhef users of the NXOL service, please be kind and don�t hijack someone else�s IP (just like on DHCPnet :). Otherwise, we may have to lock IPs down an that would kill your kindly provisioning service � |
PXE provisioned machines (you get them by setting �PXE boot� in the VM template on creation or under the �Boot order� button on the �Disk� tab for existing VMs) are easier and can be installed and configured almost automagically. | PXE provisioned machines (you get them by setting �PXE boot� in the VM template on creation or under the �Boot order� button on the �Disk� tab for existing VMs) are easier and can be installed and configured almost automagically. | ||
| Line 33: | Line 33: | ||
You can create VMs with a few cores (1-4), reasonable memory (2-4GByte or so) and some disk (say, 16-30GByte) without trouble and without exhausting the shared pool of resources assigned to all NXOL users together. | You can create VMs with a few cores (1-4), reasonable memory (2-4GByte or so) and some disk (say, 16-30GByte) without trouble and without exhausting the shared pool of resources assigned to all NXOL users together. | ||
| − | Make sure to assign a network (only <code>nik-xo-localaccess</code> is available for your) to your VM, or you will onyl have the virtual console to play with. You will be assigned (with DHCP/BOOTP) an address in the 145.116.56.128/25 range (actually .129-.199 for now), and please be kind to your co-users and don�t just | + | Make sure to assign a network (only <code>nik-xo-localaccess</code> is available for your) to your VM, or you will onyl have the virtual console to play with. You will be assigned (with DHCP/BOOTP) an address in the 145.116.56.128/25 range (actually .129-.199 for now), and please be kind to your co-users and don�t just randomly pick an address. If you do, we will have to abandon the provisioning service for everyone. Do be kind :) |
Review the �Advanced Options� if you want to share management of the VM with all other Nikhef users, or if you want to create but not boot the VM. | Review the �Advanced Options� if you want to share management of the VM with all other Nikhef users, or if you want to create but not boot the VM. | ||
| Line 41: | Line 41: | ||
== Stopping VMs == | == Stopping VMs == | ||
| − | + | If you don�t use your VM, please switch it off. If you are dont with your experiments, destroy the VM and release the resources to others for enjoyment. The resource set pool is shared with your colleagues. | |
== CentOS7 PXE provisioning service == | == CentOS7 PXE provisioning service == | ||
| Line 47: | Line 47: | ||
You want to (re)install your VM and are happy with CentOS7 64-bit (CentOS is, like Scientific Linux, a RHEL clone), and want to use your local Nikhef account there to login and gain root access, as well as have some basic settings done right? Use the PXE provisioning service by (re)starting your VM using PXE network boot and DHCP. | You want to (re)install your VM and are happy with CentOS7 64-bit (CentOS is, like Scientific Linux, a RHEL clone), and want to use your local Nikhef account there to login and gain root access, as well as have some basic settings done right? Use the PXE provisioning service by (re)starting your VM using PXE network boot and DHCP. | ||
| − | Before you continue: * register your (password-protected!) SSH keys in the Nikhef IdM system by going to '''https://sso.nikhef.nl/chsh/''', copy your | + | Before you continue: * register your (password-protected!) SSH keys in the Nikhef IdM system by going to '''https://sso.nikhef.nl/chsh/''', copy your SSH public keys (<code>ssh-rsa AAAAB3NzaC1y...</code>) into the box (you may enter more then one) and then confirming the account update. |
Then, DHCP-boot the VM and wait for the PXE boot prompt to appear. The initial menu looks like this | Then, DHCP-boot the VM and wait for the PXE boot prompt to appear. The initial menu looks like this | ||
| Line 80: | Line 80: | ||
You can follow installation progress on the virtual console, and can review detailed logs on pts/3 (press Alt-F3 to see that one, and Alt-F1 to switch back). An interactive root shell is available on pts/2 (Alt-F2) to look a bit deeper, e.g.�if you don�t see anything happening for a long while. Remember that installation and the immediate automatic updating of packages does take a while (esp.�running <code>dracut</code> is a lengthy wait). | You can follow installation progress on the virtual console, and can review detailed logs on pts/3 (press Alt-F3 to see that one, and Alt-F1 to switch back). An interactive root shell is available on pts/2 (Alt-F2) to look a bit deeper, e.g.�if you don�t see anything happening for a long while. Remember that installation and the immediate automatic updating of packages does take a while (esp.�running <code>dracut</code> is a lengthy wait). | ||
| − | If you are happy with progress, in XO go to the �Disk� tab, hit the �boot order� button and disable network boot. Then '''press Save to make | + | If you are happy with progress, in XO go to the �Disk� tab, hit the �boot order� button and disable network boot. Then '''press Save to make this effective'''. Now your machine will boot quickly next time. |
Once all is done and the machine has rebooted, you can login with SSH and your own user name on the box. On the �network� tab you can see it�s current IPv4 and IPv6 addresses (in the blue box under �IP addresses� at the end of text on the page). It will say something like | Once all is done and the machine has rebooted, you can login with SSH and your own user name on the box. On the �network� tab you can see it�s current IPv4 and IPv6 addresses (in the blue box under �IP addresses� at the end of text on the page). It will say something like | ||
