Over the past 2 weeks I've been working on implementing a new feature that was requested by Christian Mohn (@h0bbel) on the the vSoup Podcast. This new feature will hopefully allow you to create more JumpSquares faster.
Version 1.2 (1.9.14)
- Added Nmap Scan XML functions. Upload Nmap XML file to create JumpSquares quickly.
- Changed a bunch of deprecated Rails 3 warnings to be Rails 4 compliant.
- Uploaded new wiki appliance with all new functionality and Debian Wheezy patches
- Fixed bootstrap modal appearing on right side of screen
Add a comment Read more: JumpSquares v1.2 - Nmap XML Parsing
Ed Czerwin (@eczerwin), Chris Dearden(@chrisdearden), and Christian Mohn (@h0bbel) have an addicting podcast called vSoup. vSoup focuses on day to day IT operations and virtualization from the trenches. Each of the guys are respected bloggers and faces in the community.
This past week during their 40th episode, they talked a bit about my latest project JumpSquares. Christian gives a good overview and talks about how he uses the appliance based model in his environment because it doesn't have direct internet access. Remember, there is also the SaaS based version at JumpSquares.net that I encourage you to use.
The guys talked about using a tool such as nmap to go out and fetch machines on the network to quickly populate your JumpSquares. It's a great idea and I'll try to begin working on that in the next few weeks after I take another CCNP exam so my CCNA doesn't expire. If you have any more suggestions or feature requests, I'm always open to hearing about them.
Here are the show notes:Add a comment
We are almost done with the initial setup to get to a point where we can start provisioning. In this scenario we are going to use a normal clone functionality that is a similar process across vSphere, Hyper-V (SCVMM), and KVM (RHEV). If you want to know about all the provisioning scenarios such as Linked Clones read Choosing a Provisioning Scenario.
At this point you should have finished the previous 5 steps:
after this step
Create Clone Blueprint Information
Add a comment
Welcome to Part 5: Agent, Endpoint, and Group Configuration
You should have completed Part 1-4:
During the vCAC Complete Install process, we already installed a vSphere agent. We need to create "Agents" or workers that know how to talk to specific endpoints. There are a few different types of agents and each one has similar installation procedures. The links below will take you to official VMware documentation. We are going to go over the Proxy Agent Configuration for vSphere for configuring the IaaS components.
- Proxy Agent for vSphere
- Proxy Agent for Hyper-V
- Proxy Agent for XenServer
- VDI Agent for XenDesktop
- EPI Agent for Citrix
- EPI Agent for Visual Basic Scripting
- WMI Agent for Remote WMI Tasks for Windows Machines
The vSphere agent/endpoint here is a "vCenter" instance. If you have more than 1 vCenter, then you need to install an additional vSphere Agent on the IaaS Components VM. There is a 1:1 mapping. To install an additional vSphere Agent, scroll to the bottom of this blog post. During the deployment in Step 3 we either kept the name "vCenter" or changed it to the actual name of vCenter during this screen. This name will be used again here.
Add a comment
At this point you should have finished the three prior steps:
The next step involves setting the user accounts and tenants. By default, we have already created the default tenant at https://vcac-appliance-hostname.domain.name/shell-ui-app (in my case https://vcac-identity.kendrickcoleman.c0m/shell-ui-app) that can be accessed with the email@example.com SSO account.
vCAC has the ability to be a Single Tenant or Multi-Tenant application. A tenant is an organizational unit within a vCloud Automation Center deployment. A tenant can represent a business unit within an enterprise or a company that subscribes to cloud services from a service provider. Each tenant has a unique URL to the vCloud Automation Center console where the default has been specified above, while mutli-tenant resources will be given a URL such as https://vcac-appliance-hostname.domain.name/shell-ui-app/org/mycompany. The default tenant is the only tenant that supports native Active Directory authentication; all other tenants must use Active Directory over LDAP or OpenLDAP.
In a single tenant configuration, everything is handled at the default instance. This includes system wide configurations. Tenant administrators can manage users and groups, configure tenant-specific branding, notifications, business policies, and catalog offerings. The system administrator account is always firstname.lastname@example.org, while the tenant administrator must be a user in one of the tenant identity stores, such as email@example.com.
In a multi-tenant environment, the system administrator creates new tenants for each organization that uses the same vCloud Automation Center instance. Tenant users log in to the vCloud Automation Center console at a URL specific to their tenant. Since we are only going to be exploring a Single Tenant configuration, please read more about multi-tenancy at Comparison of Single-Tenant and Multi-Tenant Deployments in the official VMware documentation.
Add a comment
We've made it to Part 3. The first two were pretty simple so far. so lets get started with Part 3
There are three components to a successful vCAC deployment:
Deploy a Windows VM (or physical server):
1. The Windows machine can be at 2008 R2 SP 1 or later. Windows 2012 is also supported. Windows 2012 R2 does NOT WORK. I tried it and it fails during installation with .NET 4.5 errors. I've done both Windows 2008 R2 and Windows 2012. Each has it's own quirks listed. I am also using SQL 2012 as well for the database.
a. 2vCPU, 8GB RAM, 30GB of Disk
2. Assign the box a static IP address. IIS doesn't like DHCP.
3. Add the Windows box to your domain. Adding the box to your domain will ensure NTP is going to be working correctly as well as DNS. Both of these are critical to functionality.
Add a comment
At this point, you should have gone through Step 1: Deploy and Configure the Identity Appliance.
This post will go through the second stage of the vCloud Automation Center install process. We are going to Deploy and Configure the vCAC Appliance.
There are multiple steps to a successful vCAC deployment:
Add a comment
Microsoft Distributed Transaction Coordinator Service (MS DTC) enabled on all SQL nodes in the system
There's already some good blog posts out there, but none that are all inclusive. vCloud Automation Center (vCAC) 6.0 does not currently offer an automated migration path from vCAC 5.x or earlier versions. An automated migration path from vCAC 5.2 and 6.0 is planned for a future release in 2014. This will be focused on a fresh clean vCAC 6 installation.
We will be going through multiple steps for a successful deployment:
Preparing for the installation:
- vCloud Automation Center requires hosts to be identified using their fully qualified domain names (FQDN). DNS infrastructure is a necessity
- Have Available Resources
- Identity Appliance: 1vCPU, 2GB of RAM, 2GB of Disk
- vCAC Appliance: 2vCPU, 8GB of RAM, 30GB of Disk
- IaaS Server (Windows 2008 R2 SP1 or Windows 2012): 2vCPU, 8GB RAM, 30GB of Disk
- Requires SQL Database connection
- TCP/IP protocol enabled for MS SQL Server
- Microsoft Distributed Transaction Coordinator Service (MS DTC) enabled on all SQL nodes in the system
- No firewalls between Database Server and the Web server or IaaS Server, or ports opened as described in Port Requirements
- If using SQL Server Express, the SQL Server Browser service must be running
- .NET Framework 4.5
- PowerShell 2.0 or 3.0
- Internet Information Services 7.5
- We will be using an automation script to configure the pre-reqs for the Windows Box
- Verify NTP is functional across the domain
- I found it easier making sure that all hostname are entered in lowercase. this way there are DNS issues
Add a comment
JumpSquares.net was launched a few weeks ago and I'm very happy at the success and attention it has received. Almost 300 JumpSquares have been configured so far! 2 weeks ago I introduced a brand new functionality allowing you to access the server hosting the application via RDP, SSH, or VNC (read more at JumpSquares v1.1 - RDP, VNC, and SSH added to Server). With that new addition, I wanted to showcase it with a brand new video AND make the video 60% shorter than the original. Some new greatness, now only taking up 3 minutes and 43 seconds of your time. Head on over to the JumpSquares.net homepage to check it out and get registered, or view it below.
Add a comment
I know many of you are home lab junkies, and many of you out there replicated my home lab (VMware vSphere Home Lab - "The Green Machines"). This past week I made a dumb mistake. I completely jacked up my Active Directory server, and like a bad admin, I never took a backup and didn't even take a snapshot... Oh well, time to upgrade. Since everything was based on AD authentication, I came across many hiccups with security tokens and said 'screw it, start over'.
I took this as an opportunity to do a few things:
- Upgrade the lab to vSphere 5.5
- Upgrade Synology to DSM 4.3
- Since I really jacked it up, I deleted almost every VM and began by building Active Directory on Windows 2012 R2.
- I deleted my vCenter and SQL VMs and decided to make the plunge using the vCenter Virtual Appliance
- I added a 120GB Kingston HyperX SSD drive to both of my Shuttle hosts
- Rebuild VMware View with Horizon 5.3
So if you are wondering if stuff is working, I'm happy to say YES! 5.5 is fully working on my lab hosts. Thanks to Erik Bussink's article Adding Realtek R8168 Driver to ESXi 5.5.0 ISO I was able to get the on-board Realtek NIC to be seen which is helpful when migrating over to the distributed switch.Add a comment
- VCE Vision Online Simulator Goes Public For Developers
- What's Your RTO? Check out this new free tool
- My Uncle learned I had a blog and begins to read...
- JumpSquares v1.1 - RDP, VNC, and SSH added to Server
- Intel & AMD vGPU Not Supported in vSphere 5.5
- JumpSquares.net - a new kind of bookmark
- Triple Book Giveaway
- Introducing the MonsterRemote for the MonsterShield
Page 5 of 32