Last week I presented at OpenStack Day Seattle – and did a short demonstration of OpenStack managing Hyper-V.
Today I want to show you how to get a basic OpenStack + Hyper-V deployment up and running quickly.
The process is as follows:
- Install Windows Server 2012 R2 / Windows Server 2016 TP3 on a physical computer
- Enable the Hyper-V role, and configure virtual networking to your preference
- Make sure your current user is a member of the Hyper-V administrators group
- Make sure you have a block of “public IP addresses” available for your network
- Download V-Magine (from http://www.cloudbase.it/v-magine/)
- Run V-Magine
- Answer the questions that you are asked
- Go get a coffee (or two)
About an hour later you will have OpenStack on Hyper-V ready to go! Nice and simple. You can now open up the OpenStack website (V-Magine always makes this available on http://10.74.19.3) and login with the username “admin” and the password you provided during installation.
The next thing you will want to do is to get a Windows image that you can deploy in your new OpenStack environment. This is a little more complicated. Here you will need to:
- Download the Windows Server 2012 R2 evaluation cloud image (from http://www.cloudbase.it/windows-cloud-images/)
- Setup a network share – I use PowerShell to do this by running the following commands (substitute paths and names as appropriate):
new-smbshare -name CloudBase -path C:\CloudBase
Set-netfirewallrule -DisplayGroup “File and Printer Sharing” -Enabled True - Login to the OpenStack controller virtual machine with the username “root” and the password you provided while installing V-Magine.
- Run the following commands inside the virtual machine:
source keystonerc_admin
mount //192.168.2.36/CloudBase /mnt -o username=benjamin,password=P@ssw0rd
gunzip -cd /mnt/windows_server_2012_r2_standard_eval_hyperv_20140530.vhdx.gz | glance image-create --property hypervisor_type=hyperv --name "Windows Server 2012 R2 Eval" --container-format bare --disk-format vhd --visibility public
Obviously – replace IP addresses, paths, usernames and passwords with the right ones for your environment
Now you can login to the OpenStack website again and start provisioning Windows Server instances.
To show you how easy this is to do – I have captured a video of me doing this on my laptop:
Don’t worry – even though the entire process takes about 70 minutes – I have fast forwarded through the boring bits so that this video is only 20 minutes long.
Cheers,
Ben
Ben
Hi Ben
I am running the V-Magine on a Huper-V 2012R2 server with public DHCP network in the 192.168.1.0 range.
When I run the V-Magine tool I fill in all the values and during the setup it hangs on the install of the puppet manifests. The log file shows exactly the same message.
I saw exactly the same error on this video but in his case the setup finishes. What to do?
Thanks for a reply.
Roger
Applying Puppet manifests [ ERROR ]
ERROR : Error appeared during Puppet run: 192.168.1.74prescript.pp
Error: Could not find data item CONFIGUSESUBNETS in any Hiera data file and no default supplied at /var/tmp/packstack/3db99ddabcfe4ebd b9efd1b5da79ff37/manifests/192.168.1.74prescript.pp:2 on node rdo.cloudbase
You will find full trace in log /var/tmp/packstack/20151126-115905-VclZdy/manifests/192.168.1.74prescript.pp.log
Please check log file /var/tmp/packstack/20151126-115905-VclZdy/openstack-setup.log for more information
Additional information:
* Warning: NetworkManager is active on 10.45.164.3, 192.168.1.74. OpenStack networking currently does not work on systems that have the Network Manager service enabled.
* File /root/keystonercadmin has been created on OpenStack client host 10.45.164.3. To use the command line tools you need to source the file.
* To access the OpenStack Dashboard browse to http://10.45.164.3/dashboard .
Please, find your login credentials stored in the keystonerc_admin in your home directory.
* To use Nagios, browse to http://10.45.164.3/nagios username: nagiosadmin, password: 916703769a004244
I have the same problem and also no solution. The only solution i found was in this link: ask.openstack.org/…/error-could-not-find-data-item-config_use_subnets-in-any-hiera-data-file. But the problem is dat the V-Magine tool a whole set of tools is, so i cant use this solution.
Stop the V-Magine program
rpm -e puppet
rpm -e hiera
vi /etc/yum.repos.d/epel.repo
Search for [epel]
Serach in Epel for gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
Add after exclude=hiera*
Check if more entries
yum install -y puppet-3.6.2-3.el7.noarch
Reboot the server.
rm /etc/puppet/hiera.yaml
packstack –answer-file=/root/packstack-answers.txt
New v-magine version available: https://cloudbase.it/v-magine
v-magine is Open Source: https://github.com/cloudbase/v-magine
Questions? http://ask.cloudbase.it