Re: [Wg-test-framework] Xen+Libvirt OpenStack monthly June meeting

[Lars Kurth <lars.kurth@xxxxxxxxxx>]

On 30/06/2015 19:09, "Jim Fehlig" <jfehlig@xxxxxxxx> wrote:

>On 06/30/2015 11:06 AM, Lars Kurth wrote:
>> Hi all,
>>
>> please find attached attached a PDF of the changes that I made to the
>>official 
>> OpenStack Config Reference. The relevant
>>
>>   * Hypervisor section is at page 223
>>   * the modified XenServer docs are at page 229 â the main changes here
>>are
>>     about clarifying the difference between Xen and XenServer (mainly
>>terminology)
>>   * and the new Xen + Libvirt docs are at page 236
>>
>
>For items 1 and 2 in "Additional Configuration Items", it should be
>clarified 
>that dom0_mem and dom0_max_vcpus are Xen parameters, not dom0 kernel
>parameters. 
>Also, it should be noted that these are suggestions and that proper
>values 
>should be based on the compute host resources. The suggested values might
>not be 
>sufficient on a large memory/cpu host that will run many hundreds of
>instances.

ACK.

>For item 3 in "Additional Configuration Items", hypervisor_type might
>also need 
>to be set in the image metadata, especially if the cloud contains mixed
>hypervisor compute nodes. And IIRC, image metadata such as vm_mode,
>hypervisor_type, architecture, etc. can be set when importing the image
>to 
>glance. The metatdata can also be changed through the glance service, e.g.
>
>glance image-update <img-uuid> --property hypervisor_type=xen --property
>vm_mode=hvm

Thanks.Does it make sense to cover supported image types? The KVM docs
start off with that, but I am not sure how relevant that is.

>The KVM section includes "Troubleshoot KVM". I think that would be useful
>in the
>Xen + libvirt section too. At a minimum, it could mention the important
>log 
>files to consult when e.g. an instance fails to start:
>/var/log/libvirt/libxl/libxl-driver.log,
>/var/log/xen/qemu-dm-<instancename>.log, /var/log/xen/xen-hotplug.log,
>etc.

OK, I can add this. Can someone spell out the etc.?

If there are any other common issues, please let me know. But I need
enough content and context to wordsmith it.

>
>> > Lars asked whether anyone is willing to help with reviews of the
>>documentation
>>
>> > Bob will review
>>
>> > Michael Glasgow: happy to have a look also, but is not yet that
>>familiar 
>> with OpenStack
>>
>> > Jim: Happy to look at libvirt portion of the documentation
>>
>>
>> If those, who volunteered could have a look at the docs and let me know
>> whether they look fine, I will get them reviewed on Gerrit. I am in
>>particular 
>> looking for omissions and correctness.
>> It would also be good if we had a section on the Xen Wiki explaining
>>how to 
>> rebuild Xen and Libvirt into Ubuntu packages, that I could link to. At
>>least 
>> until Xen 4.5.1 and later 4.4.3 are available in distros.
>> You should also note that the CentOS Virt SIG is looking at back
>>porting the 
>> missing Xen changes into the imminent release of Xen 4.4.2 for CentOS 7
>>(which 
>> will contain Libvirt 1.2.15). But I can't promise as yet.
>
>The latest releases of Xen and libvirt for the various openSUSE and SLES
>distributions can always be found in the open build service
>Virtualization project
>
>https://build.opensuse.org/project/show/Virtualization

So if I red this correctly, SLE_11_SP3, SLE_12, openSUSE_13.2 and 13_1
uses xen-4.5.1 and thus has the patches (see
https://build.opensuse.org/package/binaries/Virtualization/xen?repository=o
penSUSE_13.2). And they all ship with libvirt 1.2.16.

I can certainly point this out. Does this mean that these packages are
automatically installed when you get the latest set of RPMs?

Regards
Lars

_______________________________________________
Wg-test-framework mailing list
Wg-test-framework@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/wg-test-framework