Bug#674132: [Pkg-xen-devel] Bug#674132: xcp-xapi: backend check error
On Wednesday 23 May 2012 05:43 PM, Mike McClurg wrote: No, xapi cannot cope with xend running at the same time. It can cope with xl being used, as long as xl is not used to change the state of VMs which xapi is managing. So can't xapi, in its pre-inst check is xend is running. And then appropriately act. What I am saying is that someone might want to switch to using xl instead of xapi. Making the change you suggested xcp-xapi.init would then mean that setting TOOLSTACK=xl would cause an error, when in fact it is a perfectly valid thing to do. At this moment, following the README, it just fails. Agreed, let's make sure to add the TOOLSTACK=xapi setting to the README before Wheezy. We gave it another shot today. Freshly installed Wheezy had a terrible time getting XCP setup on it. My engineer had to refer a lot of random links over google to set something up. By quality, this should have been doable through README.Debian, but that is not the case. Just like postfix and exim packages, xcp actaully needs a lot of debconf prompts. Currently it just is a broken installation. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#674132: [Pkg-xen-devel] Bug#674132: xcp-xapi: backend check error
On Wed, May 23, 2012 at 10:25 AM, Ritesh Raj Sarraf r...@debian.org wrote:
Package: xcp-xapi
Severity: important
The README doc mentions:
4/ Configuring Xen and XCP
--
4.1/ Switch using xl instead of xm and xend to control Xen
As of writing, you should do that:
sed -i s/TOOLSTACK=/TOOLSTACK=xl/ /etc/default/xen
Where as the init script checks for:
# Exit cleanly if TOOLSTACK != xapi
if [ ${TOOLSTACK} != xapi ]; then
log_failure_msg Xen toolstack is not set to xapi! Exiting.
exit 0
fi
Please fix this to one.
Hi Ritesh,
Should this really be an error? It's likely that for Xen 4.1, someone
might have three toolstacks installed at the same time: xm, xl, and
xapi. It seems that they should have the option to switch between the
three without causing an error in the init scripts of the other two.
In this case, do we really want to return an error here?
Mike
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674132: [Pkg-xen-devel] Bug#674132: xcp-xapi: backend check error
On Wednesday 23 May 2012 03:33 PM, Mike McClurg wrote: Should this really be an error? It's likely that for Xen 4.1, someone might have three toolstacks installed at the same time: xm, xl, and xapi. It seems that they should have the option to switch between the three without causing an error in the init scripts of the other two. In this case, do we really want to return an error here? In the README doc shipped by the package xcp-xapi, it should recommend to use xapi as the TOOLSTACK. If you are saying that xapi can support all the interfaces, then all of them should be briefly touched upon. At this moment, following the README, it just fails. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#674132: [Pkg-xen-devel] Bug#674132: xcp-xapi: backend check error
On Wed, May 23, 2012 at 11:56 AM, Ritesh Raj Sarraf r...@debian.org wrote: On Wednesday 23 May 2012 03:33 PM, Mike McClurg wrote: Should this really be an error? It's likely that for Xen 4.1, someone might have three toolstacks installed at the same time: xm, xl, and xapi. It seems that they should have the option to switch between the three without causing an error in the init scripts of the other two. In this case, do we really want to return an error here? In the README doc shipped by the package xcp-xapi, it should recommend to use xapi as the TOOLSTACK. Yes, I gree that the README should tell the user to set TOOLSTACK=xapi if he or she wants to enable xapi. If you are saying that xapi can support all the interfaces, then all of them should be briefly touched upon. No, xapi cannot cope with xend running at the same time. It can cope with xl being used, as long as xl is not used to change the state of VMs which xapi is managing. What I am saying is that someone might want to switch to using xl instead of xapi. Making the change you suggested xcp-xapi.init would then mean that setting TOOLSTACK=xl would cause an error, when in fact it is a perfectly valid thing to do. At this moment, following the README, it just fails. Agreed, let's make sure to add the TOOLSTACK=xapi setting to the README before Wheezy. Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
