[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[rdo-list] Recent RDO bloggers



Here's what RDO enthusiasts have been blogging about in the last few
weeks. If you blog about RDO, please let me know (rbowen redhat com) so
I can add you to my list.



TripleO: Debugging Overcloud Deployment Failure by bregman

You run ‘openstack overcloud deploy’ and after a couple of minutes you
find out it failed and if that’s not enough, then you open the
deployment log just to find a very (very!) long output that doesn’t give
you an clue as to why the deployment failed. In the following sections
we’ll see how can […]

Read more at http://tm3.org/dv



RDO @ DevConf by Rich Bowen

It's been a very busy few weeks in the RDO travel schedule, and we
wanted to share some photos with you from RDO's booth at DevConf.cz.

Read more at http://tm3.org/dw



The surprisingly complicated world of disk image sizes by Daniel Berrange

When managing virtual machines one of the key tasks is to understand the
utilization of resources being consumed, whether RAM, CPU, network or
storage. This post will examine different aspects of managing storage
when using file based disk images, as opposed to block storage. When
provisioning a virtual machine the tenant user will have an idea of the
amount of storage they wish the guest operating system to see for their
virtual disks. This is the easy part. It is simply a matter of telling
‘qemu-img’ (or a similar tool) ’40GB’ and it will create a virtual disk
image that is visible to the guest OS as a 40GB volume. The
virtualization host administrator, however, doesn’t particularly care
about what size the guest OS sees. They are instead interested in how
much space is (or will be) consumed in the host filesystem storing the
image. With this in mind, there are four key figures to consider when
managing storage:

Read more at http://tm3.org/dx



os_type property for Windows images on KVM by Tim Bell

The OpenStack images have a long list of properties which can set to
describe the image meta data. The full list is described in the
documentation. This blog reviews some of these settings for Windows
guests running on KVM, in particular for Windows 7 and Windows 2008R2.

Read more at http://tm3.org/dz



Commenting out XML snippets in libvirt guest config by stashing it as
metadata by Daniel Berrange

Libvirt uses XML as the format for configuring objects it manages,
including virtual machines. Sometimes when debugging / developing it is
desirable to comment out sections of the virtual machine configuration
to test some idea. For example, one might want to temporarily remove a
secondary disk. It is not always desirable to just delete the
configuration entirely, as it may need to be re-added immediately after.
XML has support for comments which one might try to use to achieve this.
Using comments in XML fed into libvirt, however, will result in an
unwelcome suprise – the commented out text is thrown into /dev/null by
libvirt.

Read more at http://tm3.org/d-




-- 
Rich Bowen - rbowen redhat com
RDO Community Liaison
http://rdoproject.org
@RDOCommunity


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]