Hi Josh,

Thanks for getting back to me, as well as for the installation
instructions.

I will get follow up with questions if I happen to get stuck.

Regards,
SC

On Fri, 1 May 2020, 16:10 Josh Thompson, <[email protected]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi SC,
>
> This doesn't cover all of the exact details, but it should be a good
> start.
> Please follow up with any questions about the details of specific steps,
> and
> we can help you through those.  We also have an IRC channel on Freenode -
> #asfvcl - you can join to get help as you work through the installation
> (if
> during business hours EST time).  I'm assuming you're going to use NAT for
> users to connect to the 2 compute VMs.  I'm a little fuzzy on some details
> of
> ESXi.  So, I might use some terminology wrong in those parts.
>
> * set up 3 vswitches on the ESXi host
>   * one that is generally referred to as the "private" network (how VCL
> manages VMs) - plan on using 192.168.1.0/24 as the IP space for this one
>     * create a port group named "private" on this vswitch
>   * one that is generally referred to as the "NAT" network - plan on using
> 10.0.0.0/24 as the IP space for this one
>     * create a port group named "nat" on this vswitch
>   * one that is generally referred to as the "public" network - this one
> will
> need to be connected to a NIC on the ESXi host - this will use whatever
> public
> IP space you have available. I'll use YOURPUBIP in this guide
>     * create a port group named "public" on this vswitch
> * create a datastore (network or local) on the ESXi host where the disk
> files
> for the VMs will be located named "vcldatastore"
> * manually create a VM on ESXi installed with CentOS 7 with the latest
> updates
> (CentOS 8 is not yet supported for the management node)
>   * this VM will need to have 3 NICs, one on each network, use
> 192.168.1.10
> for the private IP, 10.0.0.10 for the NAT IP, and give it a public IP
> (YOURPUBIP)
>   * for NAT management, I think root on the management node needs to be
> able
> to ssh to itself without a password (using identity keys). So, this will
> need
> to be configured as well.
> * configure your ESXi host to have a NIC on the private network with an IP
> of
> 192.168.1.11 (I'm assuming it already has a NIC on the public network that
> you
> are using to manage it)
> * configure the ESXi host so that you can ssh from the management node to
> the
> ESXi host using identity keys (look here https://vcl.apache.org/docs/
> vmwareconfiguration)
> * download and validate the VCL installation script on the management node
> (http://vcl.apache.org/docs/VCL251InstallGuide.html)
> * run the installation script
>   * give a password for the admin user
>   * specify a time zone
>   * select the NIC with IP 192.168.1.10 for the private network
>   * select the NIC with IP 10.0.0.10 for the public network (yes, this
> will be
> NAT even though it says public)
>   * install dhcpd
>   * type 'YES' for the license agreement
> * go to https://YOURPUBIP/vcl/
> * login with admin and the password you entered in the installation script
> * go to Manage->Virtual Hosts->VM Host Profiles
>   * select "VMware ESXi - local storage" -> Configure Profile
>   * click the value next to "Virtual Disk Path" and change it to
> "vcldatastore" (these values get saved just by clicking off of them)
>   * click the value next to "VM Working Directory Path" and change it to
> "vcldatastore"
>   * click the value next to "VM Network 0" and change it to "private"
>   * click the value next to "VM Network 1" and change it to "nat"
> * go to Manage->Management Nodes
> * click Submit for "Edit Management Node Profiles"
> * click Edit for localhost
>   * check the box for "Use as NAT Host"
>   * NAT Public IP Address: YOURPUBIP
>   * NAT Internal IP Address: 10.0.0.10
>   * click Save Changes
> * go to Manage->Manage Computers
> * click Submit for "Edit Computer Profiles"
> * click Add New Computer
>   * hostname: vmhost1
>   * public IP: 1.1.1.1 (doesn't matter what you enter as long as it is a
> valid
> IP)
>   * private IP: 192.168.1.11
>   * state: vmhostinuse
>   * VM Host Profile: "VMware ESXi - local storage"
>   * RAM: whatever your host has
>   * Cores: whatever your host has
>   * Processor: enter something, but it's unused
>   * Network: whatever your host has
>   * click Add Computer
>   * select "allComputer" then <-Add
>   * click Close
> * click Add new Computer
>   * change "Single Computer" to "Multiple Computers" at the top
>   * Name: vm%
>   * Start: 1
>   * End: 2
>   * Type: Virtual Machine
>   * Start Public IP Address: 10.0.0.100
>   * End Public IP Address: 10.0.0.101
>   * Start Private IP Address: 192.168.1.100
>   * End Private IP Address: 192.168.1.101
>   * Start MAC Address: 00:50:56:00:00:01
>   * Provisioning Engine: VMware
>   * RAM: some value in MB, this will be the max value an image deployed to
> this VM could have, the actual RAM configured for VMs deployed in this
> slot is
> set on each image
>   * Cores: similar information as RAM
>   * Processor Speed: this is kind of an old leftover item from when VCL
> just
> did bare metal provisioning. Now, it's just used in ranking the VMs that
> could
> be used to fulfill a reservation.  Just enter something like 3000.
>   * Network: same that you entered for the host
>   * Connect Using NAT: checked
>   * Nat Host: localhost
>   * click Add Computers
>   * select "All VM Computers" then <-Add
>   * click Close
>
> Now, you need to create your first base image.  You'll need to manually
> install Windows or Linux (CentOS 7 or Ubuntu 16 or 18) on a VM on the ESXi
> host.  When you create the VM shell, give it 2 NICs, one on private with
> mac
> address 00:50:56:00:00:01 and one on NAT with 00:50:56:00:00:02.  You may
> actually want to give it a 3rd NIC on the public network since NAT won't
> have
> been fully set up on the management node yet so that it can get to outside
> resources.  Remove this NIC before capturing the VM.  Use the
> documentation
> here:  http://vcl.apache.org/docs/baseimagecreation
>
> After the image is captured, ensure it is added to the allVMimages image
> group.  Do this under Manage->Manage Images->Edit Grouping & Mapping.  In
> the
> "Group By Image" tab (opened by default after you have an image), select
> the
> image, click Get Groups, then select "allVMimages" and click <-Add.
>
> If everything went correctly, you should now be able to go to
> Reservations,
> click New Reservation, and reserve the image.
>
> Follow up with questions as you go through the process.
>
> Josh
>
> On Thursday, April 30, 2020 1:37:38 PM EDT Scania 2019 wrote:
> > Good day,
> >
> > I have an urgent deployment I need to make as follows:
> >
> > I have one ESXI host, and in it I would like to install one vm that runs
> > the web portal, database, and management node.
> >
> > Alongside this, in the same host I would like to setup two VMs, which
> will
> > be the compute nodes.
> >
> > I'm therefore requesting a clear step by step how-to, with the assumption
> > that I know nothing. Hopefully this time I won't give up on setting up
> VCL
> > as I believe it to be a great product. Only the documentation is not
> clear
> > and in some crucial parts assumes we already have the technical
> knowledge.
> >
> > Thank you in advance for your help.
> >
> > Regards,
> > SC
> - --
> - -------------------------------
> Josh Thompson
> Systems Programmer
> Virtual Computing Lab (VCL)
> North Carolina State University
> my GPG/PGP key can be found at www.keyserver.net
>
> All electronic mail messages in connection with State business which
> are sent to or received by this account are subject to the NC Public
> Records Law and may be disclosed to third parties.
> -----BEGIN PGP SIGNATURE-----
>
> iF0EARECAB0WIQRMIdRtWXideTZDK31X8tBw1209AwUCXqwtuAAKCRBX8tBw1209
> A6MuAJ9JuQBlaLJkJnvqdbSxG/f0CKM2xgCfQbDTHK8+UhnO9gGOWr7Z2PIrew0=
> =ZWwH
> -----END PGP SIGNATURE-----
>
>
>
>

Reply via email to