Real-time VDI Management of VMware Horizon View VM’s without a Recompose using Cloudvolumes

Bring Your Own Brain

Guest Blogpost by Chas Setchell…

Centralized management of VDI vs. physical computers saves on time and resources however depending on which kind of VDI deployment you have you could be realizing even more savings. Ideally the most efficient deployment type is Non-persistent / Stateless VDI, this is when you have one or many golden master VM’s that are then shared by a VDI pool. When your VM’s are Non-persistent / Stateless the user gets a fresh VM at login and at logout the VM gets recycled.

Screen-Shot-2013-06-20-at-15.44.43

In a Non-persistent / Stateless VMware Horizon View deployment with Composer the admin creates a base image and performs a VM snapshot that is used as the starting point for the VM’s. When patch Tuesday rolls around and the admin will boot the golden master apply the patch and take a snapshot, the admin then needs to perform a recompose that will update all existing…

View original post 441 more words

Advertisements
Posted in Uncategorized | Leave a comment

Openstack Auth issues running nova ERROR: You must provide a username via either –os-username or env[OS_USERNAME]

Openstack Auth issues running nova ERROR: You must provide a username via either —os-username or env[OS_USERNAME]

OpenStack Nova Authentication issues

Running into errors using the nova command

nova secgroup-add-rule myservers tcp
ERROR: You must provide a username via either —os-username or env[OS_USERNAME]

or

nova secgroup-list-rules default
ERROR: Invalid OpenStack Nova credentials.

This document is good http://docs.openstack.org/cli/quick-start/content/getting_credentials_cli.html

Logged in to the Nova Dashboard under project and Access & Security and the API Access tab, Download the  OpenStack RC File

Access

 

Once downloaded I used WinSCP to copy my root directory

winscp

 

From your ssh session in the /root directory run

source admin-openrc.sh

Now you should be able to run nova commands

 

Posted in OpenStack | Leave a comment

PernixData first Beta Test

Bring Your Own Brain

PernixData first beta test

From the time we heard about PernixData and watched PernixData CTO Satyam Vaghani’s videos form Storage Field Day http://pernixdata.com/SFD3 we were excited to get our hands on the PernixData Flash Virtualization Platform (FVP) product and give it a test.

What is PernixData and why should you care?

PernixData is a inline storage IO acceleration software that leverages flash storage on your VMware ESX host.

OK so you might be saying to yourself ok I have flash on my VMware ESX host why would I need a piece of software like PerixData FVP.

For Statefull / Persistent VM’s you typically want them running on some type of SAN that provides raid and enables you to use all the enterprise features from the VMware vSphere such as live migration. You also want to reduce the risk of data loss and having data on a single flash device could…

View original post 564 more words

Posted in Virtualization | Leave a comment

Openstack libvirt install fails with error

I ran into this a few times with different OpenStack Distros

Installing RDO Red Hat Openstack I got the following error with CentOS 6.4

ERROR : Error during puppet run : err: /Stage[main]/Nova::Compute::Libvirt/Package[libvirt]/ensure: change from absent to present failed: Execution of ‘/usr/bin/yum -d 0 -e 0 -y install libvirt’ returned 1: Error: Package: libvirt-0.10.2-18.el6_4.8.x86_64 (updates)

If you manually run yum -d 0 -e 0 -y install libvirt

yum -d 0 -e 0 -y install libvirt
Error: Package: libvirt-0.10.2-18.el6_4.8.x86_64 (updates)
Requires: libparted-2.1.so.0()(64bit)
Available: parted-2.1-19.el6.x86_64 (base)
libparted-2.1.so.0()(64bit)
Installed: parted-2.3-11.fu2012.x86_64 (installed)

Ok so parted-2.3-11.fu2012.x86_64 (installed)

How I got around the issue was on a fresh install CentOS 6.4 before running the OpenStack  install

Verify the version of parted by running

rpm -qa parted

if = parted-2.3-11.fu2012.x86_64 (installed)

Then uninstall parted-2.3-11.fu2012.x86_64 (installed)

Use the following command

rpm -e –nodeps parted

Now you can proceed with your OpenStack install.

Thanks to my Buddy Roddy Rodstein at Mokum Solutions for the Tip!

Posted in OpenStack | Leave a comment

Deploying RDO Red Hat OpenStack from Baremetal on Baremetalcloud.com IaaS

Deploying RDO Red Hat OpenStack from Baremetal on Baremetalcloud.com IaaS

I will walk you through the process of deploying a CentOS 6.4 image on your own private server at Baremetalcloud.com then deploy RDO Red Hat OpenStack. The entire process from start to finish can be completed in less then 30 min.

1. If you do not have an account with Baremetalcloul.com open one up at https://noc.baremetalcloud.com/register
2. Once your account is approved login and add a new Server
• If you want IP KVM access via idrac then select a M610 model
• Depending on your workload adjust for the amount of ram RDO minimum is 2GB
3. Select the Server location Model and select Order.

sserver

4. Next select the CentOS 6.4 x64 image and Order Now.

order
5. The Server details will appear, Notice that the System Login notice and the Status Restoring.
The Image Restore process should take approximately 5min.

restore

6. Under the servers tab you will see a list of your servers, Single click your server, select the Login Info Tab.

sdetails
7. Using an SSH client, I’m will be using putty connect up to the server using the ID root and new Password.
ssh
8. First the command “rpm -qa parted” if it comes back with parted-2.3-11.fu2012.x86_64 (installed)
Then you must run “rpm -e –nodeps parted” this will uninstall 2.3 cause we need 2.1 or the install will error.
9. Now we can install RDO Red Hat OpenStack in 3 steps
Type or Cut and Paste the following commands
sudo yum install -y http://rdo.fedorapeople.org/openstack/openstack-grizzly/rdo-release-grizzly.rpm
rpm
sudo yum install -y openstackpackstack
packstack
packstackallinone
Enter a root password
When you see **** Installation completed successfully ****** you can move on to next steps

Success

Posted in OpenStack | Leave a comment