Time for our first meetup of 2016. Join us for a couple of firsts. Our first visit to Zauber Brewing Company and a first time sponsor. LANDESK Software is graciously sponsoring us. LANDESK Software provides systems management, security management, service management, asset management, and process management solutions.
Join us for an evening of creating connections and building your network in a relaxed and fun environment. Networking is an essential aspect of your professional growth and development. Connect with an array of professionals while enjoying a drink and discussing what challenges the new year will provide.
Please take a moment to let us know you are coming – – -> Register Here
Location: Zauber Brewing Company
Address: 909 W 5th Ave., Columbus, OH 43212
Date: Feb. 4, 2016
Time: 6:30pm – 8:30pm
Any questions, feel free to contact me at @VTScott.
When installing Server 2008 on Qemu, for the creation of an OpenStack Windows Server 2008 template; I found it easiest to use virt-install.
Below is the code that I use to kick off that virt-install.
virt-install --virt-type kvm --name win2008 --ram 2048 --cdrom=/path/to/cd-iso/server-2008.iso --disk path=/path/to/disk/file/location/2008.qcow2 --network network=default,model=virtio --graphics vnc,listen=0.0.0.0 --noautoconsole --os-type=windows --os-variant=win2k8
We needed to update the SNMP configuration script to take parameters so that we could pass this through CloudForms, our cloud management platform. Below you’ll find the PowerShell script that we came up with. More »
After adding an AWS Cloud Provider to my CloudForms environment, I quickly noticed an absurd amount of AWS errors in the EVM log (/var/www/miq/vmdb/log/evm.log).
AWS Config Errors
After working with RedHat support it was determined to be a bug within the new implementation of the AWS config service. You can fix it one of two ways.
- Implement the AWS Config Service within AWS, instructions AWS Config Instructions.
- Create an AWS Zone with its own AWS Worker:
Deploy a second appliance and join it to this appliance. Move one appliance to an AWS zone along with the AWS provider, then disable the event monitor roles. Then do the same for VMware so you can enable the event monitor role for that zone.