Re: [vdsm] Error using vdsClient
On 2012-2-29 1:40, Deepak C Shetty wrote: On 02/29/2012 01:01 AM, Douglas Landgraf wrote: On 02/28/2012 12:21 PM, Deepak C Shetty wrote: Hello, Trying vdsClient for the first time. I am getting the below error for any cmd I am trying to use... [root@llm65 ~]# vdsClient llm65.in.ibm.com getVGList Traceback (most recent call last): File "/usr/share/vdsm/vdsClient.py", line 1972, in code, message = commands[command][0](commandArgs) File "/usr/share/vdsm/vdsClient.py", line 524, in getVGList vgs = self.s.getVGList() File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1575, in __request verbose=self.__verbose File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1294, in single_request response = h.getresponse(buffering=True) File "/usr/lib64/python2.7/httplib.py", line 1027, in getresponse response.begin() File "/usr/lib64/python2.7/httplib.py", line 407, in begin version, status, reason = self._read_status() File "/usr/lib64/python2.7/httplib.py", line 371, in _read_status raise BadStatusLine(line) BadStatusLine: '' [root@llm65 ~]# vdsClient llm65.in.ibm.com getConnectedStoragePoolsList Traceback (most recent call last): File "/usr/share/vdsm/vdsClient.py", line 1972, in code, message = commands[command][0](commandArgs) File "/usr/share/vdsm/vdsClient.py", line 1056, in getConnectedStoragePoolsList pools = self.s.getConnectedStoragePoolsList() File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1575, in __request verbose=self.__verbose File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1294, in single_request response = h.getresponse(buffering=True) File "/usr/lib64/python2.7/httplib.py", line 1027, in getresponse response.begin() File "/usr/lib64/python2.7/httplib.py", line 407, in begin version, status, reason = self._read_status() File "/usr/lib64/python2.7/httplib.py", line 371, in _read_status raise BadStatusLine(line) BadStatusLine: '' Note : I am running the above on the host (llm65) & already have configured FC, storage via OE and via OE, I am able to create and run VMs also, but vdsClient fails to give the VG and SP lists. If your vdsm is running with SSL, you must pass the argument -s (SSL), like: vdsClient -s myHost command Otherwise, -s should be ignored. 'Guess i was running with vdsm deafults so ssl was on. Its hard to relate the 'BadStatusLine" to ssl issue:) `vdsClient -s llm65.in.ibm.com getConnectedStoragePoolsList` worked for me instead of -s , -s 0 also worked, as I learnt from the vdsClient manpage. Does 0 stand for localhost here ? Yes. 0 means localhost here. If you run the vdsClient in the same host as vdsmd, you can use "vdsClient 0 getVGList". Please let me know if this is your case or not. Thanks! ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel -- Shu Ming IBM China Systems and Technology Laboratory ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] MOM Integration Plan
- Original Message - > Hi all, > > Very shortly Mark will be sending some patches for review that > implement the > long-awaited integration of mom with vdsm. I felt it would be easier > to > understand the changes to vdsm if they were explained a bit better. > In support > of this I have created a wiki page on ovirt.org with a diagram: > > http://ovirt.org/wiki/Features/MomIntegration > > To facilitate discussion, here is the text of that page: > > As discussed at the oVirt Workshop and elsewhere, integrating mom > with vdsm will > benefit oVirt by providing a mechanism for dynamic, policy-based > tuning. This > mechanism will pave the way for implementing memory ballooning > policies, can > enhance migration policy, and will replace the existing ksm tuning > thread. > > MOM exists today as an independent library that can be used by python > programs > such as vdsm or in standalone mode (by using the accompanying momd > program. > Mom's operation is very configurable. The management policy is > written in a > Fortran-like language and is replaceable by the end user. > Additionally, plugins > allow you to customize the types of information collected and the > manner in > which it is collected. Similarly, Controller plugins permit a > completely > flexible control API to be created. > > To integrate mom, vdsm will initialize the mom library in a new > thread and start > it. Therefore, mom and vdsm will exist in the same process. Vdsm > will > configure the mom instance to use plugins and a policy that > exclusively target > the vdsm API. All statistics collection will occur via API calls and > any > management actions (including adjustments to KSM and VM balloons) > will be done > through the vdsm api as well. Mom will not use libvirt at all (not > even to > monitor for new VMs on the system). > > Packaging logistics: > - > Mom is an independent package that is already in Fedora. Any changes > to mom > that are required to support this integration will be submitted to > the mom > project for inclusion. Vdsm will consume the standard MOM package as > a python > module/library. > > In order to control its mom instance, vdsm will ship a mom > configuration file > and a mom policy file that will set mom's default behavior. At > startup, vdsmd > will import mom and initialize it with the configuration and policy > files. From > that point on, mom will interact with vdsm through the well-defined > API in > API.py. > > New features needed in vdsm: > --- > In order to fully benefit from mom's capabilities, vdsm should > implement the > following extra features/APIs: > > - Collection of more memory statistics via ovirt-guest-agent > including the > current memory balloon value. > - A vmBalloon API to set a new balloon target. Looks good to me. > > -- > Adam Litke > IBM Linux Technology Center > > ___ > vdsm-devel mailing list > vdsm-devel@lists.fedorahosted.org > https://fedorahosted.org/mailman/listinfo/vdsm-devel > ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] Fedora Virtualization Test Day 2012-04-12
Good thing you linked to that wiki page. I learned a lot. I don't mind being there for the EST shift. - Original Message - > From: "Ayal Baron" > To: "VDSM Project Development" > Sent: Tuesday, February 28, 2012 4:39:04 PM > Subject: [vdsm] Fedora Virtualization Test Day 2012-04-12 > > Hi all, > > $subject is a month and a half away. > Any volunteers to driving vdsm testing forward for that day? > > > https://fedoraproject.org/wiki/Test_Day:2012-04-12_Virtualization_Test_Day > > Regards, > Ayal > ___ > vdsm-devel mailing list > vdsm-devel@lists.fedorahosted.org > https://fedorahosted.org/mailman/listinfo/vdsm-devel > ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] Fedora Virtualization Test Day 2012-04-12
Hi all, $subject is a month and a half away. Any volunteers to driving vdsm testing forward for that day? https://fedoraproject.org/wiki/Test_Day:2012-04-12_Virtualization_Test_Day Regards, Ayal ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] dealing with a vestigial mailing list
- Original Message - > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > VDSM chose to stick with fedorahosted.org for Mailman (which is > fine), > but we had made a vdsm-de...@ovirt.org as part of a batch action and > never took it down nor hid it. D'oh! > > http://lists.ovirt.org/mailman/listinfo/vdsm-devel > > I was thinking, should we send an email to that list directing people > to go to the @fedorahosted address, then moderate everyone and hide > the list? I don't think there is anyone really there. The archives are pretty empty. the latest from February is from Deepak whose already on this list, so I would just drop it. > > I shy away from vaporizing the list entirely "just in case". Also, > there are real archives of unanswered questions - should we leave > that up? > > http://lists.ovirt.org/pipermail/vdsm-devel/ > > (Can someone make sure those folks were responded to otherwise here > or > on IRC? If not, let me know and I can respond on vdsm-de...@ovirt.org > with a pointer to this list, etc.) > > It was my mistake the @ovirt.org list stayed up there; all other > locations on ovirt.org reference the fhosted list, it's just that > people who look at lists.ovirt.org/mailman/listinfo will see > vdsm-devel. So I'm offering to do the clean-up and just need to > figure > out what that entails > > Thoughts? Thanks! > > - - Karsten > - -- > name: Karsten 'quaid' Wade, Sr. Community Architect > team:Red Hat Community Architecture & Leadership > uri: http://communityleadershipteam.org > http://TheOpenSourceWay.org > gpg:AD0E0C41 > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iD8DBQFPTScT2ZIOBq0ODEERAqw7AKCPtmQyd9hEt74bWsZwOzpteXzK1gCcCxnc > 75KP9W21EtkMh4kpvpw1kU8= > =NYrJ > -END PGP SIGNATURE- > ___ > vdsm-devel mailing list > vdsm-devel@lists.fedorahosted.org > https://fedorahosted.org/mailman/listinfo/vdsm-devel > ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] dealing with a vestigial mailing list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 VDSM chose to stick with fedorahosted.org for Mailman (which is fine), but we had made a vdsm-de...@ovirt.org as part of a batch action and never took it down nor hid it. D'oh! http://lists.ovirt.org/mailman/listinfo/vdsm-devel I was thinking, should we send an email to that list directing people to go to the @fedorahosted address, then moderate everyone and hide the list? I shy away from vaporizing the list entirely "just in case". Also, there are real archives of unanswered questions - should we leave that up? http://lists.ovirt.org/pipermail/vdsm-devel/ (Can someone make sure those folks were responded to otherwise here or on IRC? If not, let me know and I can respond on vdsm-de...@ovirt.org with a pointer to this list, etc.) It was my mistake the @ovirt.org list stayed up there; all other locations on ovirt.org reference the fhosted list, it's just that people who look at lists.ovirt.org/mailman/listinfo will see vdsm-devel. So I'm offering to do the clean-up and just need to figure out what that entails Thoughts? Thanks! - - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team:Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg:AD0E0C41 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFPTScT2ZIOBq0ODEERAqw7AKCPtmQyd9hEt74bWsZwOzpteXzK1gCcCxnc 75KP9W21EtkMh4kpvpw1kU8= =NYrJ -END PGP SIGNATURE- ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] Error using vdsClient
On 02/28/2012 12:40 PM, Deepak C Shetty wrote: On 02/29/2012 01:01 AM, Douglas Landgraf wrote: On 02/28/2012 12:21 PM, Deepak C Shetty wrote: Hello, Trying vdsClient for the first time. I am getting the below error for any cmd I am trying to use... [root@llm65 ~]# vdsClient llm65.in.ibm.com getVGList Traceback (most recent call last): File "/usr/share/vdsm/vdsClient.py", line 1972, in code, message = commands[command][0](commandArgs) File "/usr/share/vdsm/vdsClient.py", line 524, in getVGList vgs = self.s.getVGList() File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1575, in __request verbose=self.__verbose File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1294, in single_request response = h.getresponse(buffering=True) File "/usr/lib64/python2.7/httplib.py", line 1027, in getresponse response.begin() File "/usr/lib64/python2.7/httplib.py", line 407, in begin version, status, reason = self._read_status() File "/usr/lib64/python2.7/httplib.py", line 371, in _read_status raise BadStatusLine(line) BadStatusLine: '' [root@llm65 ~]# vdsClient llm65.in.ibm.com getConnectedStoragePoolsList Traceback (most recent call last): File "/usr/share/vdsm/vdsClient.py", line 1972, in code, message = commands[command][0](commandArgs) File "/usr/share/vdsm/vdsClient.py", line 1056, in getConnectedStoragePoolsList pools = self.s.getConnectedStoragePoolsList() File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1575, in __request verbose=self.__verbose File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1294, in single_request response = h.getresponse(buffering=True) File "/usr/lib64/python2.7/httplib.py", line 1027, in getresponse response.begin() File "/usr/lib64/python2.7/httplib.py", line 407, in begin version, status, reason = self._read_status() File "/usr/lib64/python2.7/httplib.py", line 371, in _read_status raise BadStatusLine(line) BadStatusLine: '' Note : I am running the above on the host (llm65) & already have configured FC, storage via OE and via OE, I am able to create and run VMs also, but vdsClient fails to give the VG and SP lists. If your vdsm is running with SSL, you must pass the argument -s (SSL), like: vdsClient -s myHost command Otherwise, -s should be ignored. 'Guess i was running with vdsm deafults so ssl was on. Its hard to relate the 'BadStatusLine" to ssl issue:) Yep, fell free to open a BZ :-) `vdsClient -s llm65.in.ibm.com getConnectedStoragePoolsList` worked for me instead of -s , -s 0 also worked, as I learnt from the vdsClient manpage. Does 0 stand for localhost here ? yes. Thanks! -- Cheers Douglas ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] Error using vdsClient
On 02/29/2012 01:01 AM, Douglas Landgraf wrote: On 02/28/2012 12:21 PM, Deepak C Shetty wrote: Hello, Trying vdsClient for the first time. I am getting the below error for any cmd I am trying to use... [root@llm65 ~]# vdsClient llm65.in.ibm.com getVGList Traceback (most recent call last): File "/usr/share/vdsm/vdsClient.py", line 1972, in code, message = commands[command][0](commandArgs) File "/usr/share/vdsm/vdsClient.py", line 524, in getVGList vgs = self.s.getVGList() File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1575, in __request verbose=self.__verbose File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1294, in single_request response = h.getresponse(buffering=True) File "/usr/lib64/python2.7/httplib.py", line 1027, in getresponse response.begin() File "/usr/lib64/python2.7/httplib.py", line 407, in begin version, status, reason = self._read_status() File "/usr/lib64/python2.7/httplib.py", line 371, in _read_status raise BadStatusLine(line) BadStatusLine: '' [root@llm65 ~]# vdsClient llm65.in.ibm.com getConnectedStoragePoolsList Traceback (most recent call last): File "/usr/share/vdsm/vdsClient.py", line 1972, in code, message = commands[command][0](commandArgs) File "/usr/share/vdsm/vdsClient.py", line 1056, in getConnectedStoragePoolsList pools = self.s.getConnectedStoragePoolsList() File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1575, in __request verbose=self.__verbose File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1294, in single_request response = h.getresponse(buffering=True) File "/usr/lib64/python2.7/httplib.py", line 1027, in getresponse response.begin() File "/usr/lib64/python2.7/httplib.py", line 407, in begin version, status, reason = self._read_status() File "/usr/lib64/python2.7/httplib.py", line 371, in _read_status raise BadStatusLine(line) BadStatusLine: '' Note : I am running the above on the host (llm65) & already have configured FC, storage via OE and via OE, I am able to create and run VMs also, but vdsClient fails to give the VG and SP lists. If your vdsm is running with SSL, you must pass the argument -s (SSL), like: vdsClient -s myHost command Otherwise, -s should be ignored. 'Guess i was running with vdsm deafults so ssl was on. Its hard to relate the 'BadStatusLine" to ssl issue:) `vdsClient -s llm65.in.ibm.com getConnectedStoragePoolsList` worked for me instead of -s , -s 0 also worked, as I learnt from the vdsClient manpage. Does 0 stand for localhost here ? Please let me know if this is your case or not. Thanks! ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] Error using vdsClient
On 02/28/2012 12:21 PM, Deepak C Shetty wrote: Hello, Trying vdsClient for the first time. I am getting the below error for any cmd I am trying to use... [root@llm65 ~]# vdsClient llm65.in.ibm.com getVGList Traceback (most recent call last): File "/usr/share/vdsm/vdsClient.py", line 1972, in code, message = commands[command][0](commandArgs) File "/usr/share/vdsm/vdsClient.py", line 524, in getVGList vgs = self.s.getVGList() File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1575, in __request verbose=self.__verbose File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1294, in single_request response = h.getresponse(buffering=True) File "/usr/lib64/python2.7/httplib.py", line 1027, in getresponse response.begin() File "/usr/lib64/python2.7/httplib.py", line 407, in begin version, status, reason = self._read_status() File "/usr/lib64/python2.7/httplib.py", line 371, in _read_status raise BadStatusLine(line) BadStatusLine: '' [root@llm65 ~]# vdsClient llm65.in.ibm.com getConnectedStoragePoolsList Traceback (most recent call last): File "/usr/share/vdsm/vdsClient.py", line 1972, in code, message = commands[command][0](commandArgs) File "/usr/share/vdsm/vdsClient.py", line 1056, in getConnectedStoragePoolsList pools = self.s.getConnectedStoragePoolsList() File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1575, in __request verbose=self.__verbose File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1294, in single_request response = h.getresponse(buffering=True) File "/usr/lib64/python2.7/httplib.py", line 1027, in getresponse response.begin() File "/usr/lib64/python2.7/httplib.py", line 407, in begin version, status, reason = self._read_status() File "/usr/lib64/python2.7/httplib.py", line 371, in _read_status raise BadStatusLine(line) BadStatusLine: '' Note : I am running the above on the host (llm65) & already have configured FC, storage via OE and via OE, I am able to create and run VMs also, but vdsClient fails to give the VG and SP lists. If your vdsm is running with SSL, you must pass the argument -s (SSL), like: vdsClient -s myHost command Otherwise, -s should be ignored. Please let me know if this is your case or not. Thanks! -- Cheers Douglas ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] Error using vdsClient
Hello, Trying vdsClient for the first time. I am getting the below error for any cmd I am trying to use... [root@llm65 ~]# vdsClient llm65.in.ibm.com getVGList Traceback (most recent call last): File "/usr/share/vdsm/vdsClient.py", line 1972, in code, message = commands[command][0](commandArgs) File "/usr/share/vdsm/vdsClient.py", line 524, in getVGList vgs = self.s.getVGList() File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1575, in __request verbose=self.__verbose File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1294, in single_request response = h.getresponse(buffering=True) File "/usr/lib64/python2.7/httplib.py", line 1027, in getresponse response.begin() File "/usr/lib64/python2.7/httplib.py", line 407, in begin version, status, reason = self._read_status() File "/usr/lib64/python2.7/httplib.py", line 371, in _read_status raise BadStatusLine(line) BadStatusLine: '' [root@llm65 ~]# vdsClient llm65.in.ibm.com getConnectedStoragePoolsList Traceback (most recent call last): File "/usr/share/vdsm/vdsClient.py", line 1972, in code, message = commands[command][0](commandArgs) File "/usr/share/vdsm/vdsClient.py", line 1056, in getConnectedStoragePoolsList pools = self.s.getConnectedStoragePoolsList() File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1575, in __request verbose=self.__verbose File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1294, in single_request response = h.getresponse(buffering=True) File "/usr/lib64/python2.7/httplib.py", line 1027, in getresponse response.begin() File "/usr/lib64/python2.7/httplib.py", line 407, in begin version, status, reason = self._read_status() File "/usr/lib64/python2.7/httplib.py", line 371, in _read_status raise BadStatusLine(line) BadStatusLine: '' Note : I am running the above on the host (llm65) & already have configured FC, storage via OE and via OE, I am able to create and run VMs also, but vdsClient fails to give the VG and SP lists. thanx, deepak ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Users] Remove and Add host does not work
On 02/28/2012 10:38 PM, Douglas Landgraf wrote: On 02/28/2012 11:01 AM, Douglas Landgraf wrote: On 02/28/2012 08:49 AM, Deepak C Shetty wrote: On 02/28/2012 07:11 PM, Itamar Heim wrote: On 02/28/2012 03:31 PM, Deepak C Shetty wrote: On 02/28/2012 06:57 PM, Itamar Heim wrote: On 02/28/2012 03:22 PM, Deepak C Shetty wrote: On 02/28/2012 06:46 PM, Itamar Heim wrote: On 02/28/2012 02:48 PM, Deepak C Shetty wrote: Hi, I had a host managed via OE, completely working fine. Was even able to create and run VMs off it. I tried removing the host from the OE (put host into maint. mode and then remove) and when i re-discover the same host, OE just keeps seeing it as Non-responsive. what do you mean by "re-discover"? I just meant that i removed the host and re-added it by selecting "New" on the Hosts tab and putting the IP and hostname. I am able to ssh into the host and see that none of the vdsm processes have been started. I tried doing "Confirm host has been rebooted" on the OE, did not help. I tried putting host into maint. mode and re-activating the host, just doesn't help did you do any change to the host? just removing it from engine shouldn't cause vdsm to know/care and should work just like before. Nothing changed on the host. In fact when i removed and added the host back it says everything is installed so does nothing but reboots the host, post reboot vdsm does not start automatically and host status is non-responsive on OE if vdsm does not start, OE is correct... does vdsm try to start and fails (and if so, log excerpt?) Right, but I dont see any traces of vdsm trying to start. Nothing in the vdsm.log thats relevant to this. I just did chkconfig --list and don't see vdsmd in that, could that be the reason. On the host I manually did `service vdsmd restart` and then everythign works fine. you are basically saying "re-installing a host causes vdsm to not start by default". reproducing this again to make sure and opening a bug seems the right course. trying to trace the install flow to provide root cause or even a patch would help more to fix this Are you saying that vdsmd service should start by default post reboot and its entry should be listed as part of chkconfig --list ? vdsm uses systemd. http://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet Try to use chkconfig vdsm on, you will see a wrapper to systemd command. Found this examining the vds bootstrap complete py log 2012-02-28 23:45:32,022 DEBUGdeployUtil 707 _updateFileLine: return: True 2012-02-28 23:45:32,022 DEBUGdeployUtil 228 setVdsConf: ended. 2012-02-28 23:45:32,022 DEBUGdeployUtil 103 ['/bin/systemctl', 'reconfigure', 'vdsmd.service'] 2012-02-28 23:45:32,026 DEBUGdeployUtil 107 2012-02-28 23:45:32,026 DEBUGdeployUtil 108 Unknown operation reconfigure 2012-02-28 23:45:32,026 DEBUGdeployUtil 103 ['/sbin/reboot'] 2012-02-28 23:45:32,325 DEBUGdeployUtil 107 Which vdsm version are you using? If I am not wrong, I remember to see a patch for this report.. /me going to check.. From vdsm.spec: === * Sun Feb 5 2012 Dan Kenigsberg - 4.9.3.3-0.fc16 - BZ#773371 call `vdsmd reconfigure` after bootstrap Thanks douglas, I am on a bit older version of vdsm and can't readily update as my lab system is not directly connected to the internet. So until i update, 'guess i will have to live with manual vdsmd restart. ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Users] Remove and Add host does not work
On 02/28/2012 11:01 AM, Douglas Landgraf wrote: On 02/28/2012 08:49 AM, Deepak C Shetty wrote: On 02/28/2012 07:11 PM, Itamar Heim wrote: On 02/28/2012 03:31 PM, Deepak C Shetty wrote: On 02/28/2012 06:57 PM, Itamar Heim wrote: On 02/28/2012 03:22 PM, Deepak C Shetty wrote: On 02/28/2012 06:46 PM, Itamar Heim wrote: On 02/28/2012 02:48 PM, Deepak C Shetty wrote: Hi, I had a host managed via OE, completely working fine. Was even able to create and run VMs off it. I tried removing the host from the OE (put host into maint. mode and then remove) and when i re-discover the same host, OE just keeps seeing it as Non-responsive. what do you mean by "re-discover"? I just meant that i removed the host and re-added it by selecting "New" on the Hosts tab and putting the IP and hostname. I am able to ssh into the host and see that none of the vdsm processes have been started. I tried doing "Confirm host has been rebooted" on the OE, did not help. I tried putting host into maint. mode and re-activating the host, just doesn't help did you do any change to the host? just removing it from engine shouldn't cause vdsm to know/care and should work just like before. Nothing changed on the host. In fact when i removed and added the host back it says everything is installed so does nothing but reboots the host, post reboot vdsm does not start automatically and host status is non-responsive on OE if vdsm does not start, OE is correct... does vdsm try to start and fails (and if so, log excerpt?) Right, but I dont see any traces of vdsm trying to start. Nothing in the vdsm.log thats relevant to this. I just did chkconfig --list and don't see vdsmd in that, could that be the reason. On the host I manually did `service vdsmd restart` and then everythign works fine. you are basically saying "re-installing a host causes vdsm to not start by default". reproducing this again to make sure and opening a bug seems the right course. trying to trace the install flow to provide root cause or even a patch would help more to fix this Are you saying that vdsmd service should start by default post reboot and its entry should be listed as part of chkconfig --list ? vdsm uses systemd. http://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet Try to use chkconfig vdsm on, you will see a wrapper to systemd command. Found this examining the vds bootstrap complete py log 2012-02-28 23:45:32,022 DEBUGdeployUtil 707 _updateFileLine: return: True 2012-02-28 23:45:32,022 DEBUGdeployUtil 228 setVdsConf: ended. 2012-02-28 23:45:32,022 DEBUGdeployUtil 103 ['/bin/systemctl', 'reconfigure', 'vdsmd.service'] 2012-02-28 23:45:32,026 DEBUGdeployUtil 107 2012-02-28 23:45:32,026 DEBUGdeployUtil 108 Unknown operation reconfigure 2012-02-28 23:45:32,026 DEBUGdeployUtil 103 ['/sbin/reboot'] 2012-02-28 23:45:32,325 DEBUGdeployUtil 107 Which vdsm version are you using? If I am not wrong, I remember to see a patch for this report.. /me going to check.. From vdsm.spec: === * Sun Feb 5 2012 Dan Kenigsberg - 4.9.3.3-0.fc16 - BZ#773371 call `vdsmd reconfigure` after bootstrap -- Cheers Douglas ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Users] Remove and Add host does not work
On 02/28/2012 08:49 AM, Deepak C Shetty wrote: On 02/28/2012 07:11 PM, Itamar Heim wrote: On 02/28/2012 03:31 PM, Deepak C Shetty wrote: On 02/28/2012 06:57 PM, Itamar Heim wrote: On 02/28/2012 03:22 PM, Deepak C Shetty wrote: On 02/28/2012 06:46 PM, Itamar Heim wrote: On 02/28/2012 02:48 PM, Deepak C Shetty wrote: Hi, I had a host managed via OE, completely working fine. Was even able to create and run VMs off it. I tried removing the host from the OE (put host into maint. mode and then remove) and when i re-discover the same host, OE just keeps seeing it as Non-responsive. what do you mean by "re-discover"? I just meant that i removed the host and re-added it by selecting "New" on the Hosts tab and putting the IP and hostname. I am able to ssh into the host and see that none of the vdsm processes have been started. I tried doing "Confirm host has been rebooted" on the OE, did not help. I tried putting host into maint. mode and re-activating the host, just doesn't help did you do any change to the host? just removing it from engine shouldn't cause vdsm to know/care and should work just like before. Nothing changed on the host. In fact when i removed and added the host back it says everything is installed so does nothing but reboots the host, post reboot vdsm does not start automatically and host status is non-responsive on OE if vdsm does not start, OE is correct... does vdsm try to start and fails (and if so, log excerpt?) Right, but I dont see any traces of vdsm trying to start. Nothing in the vdsm.log thats relevant to this. I just did chkconfig --list and don't see vdsmd in that, could that be the reason. On the host I manually did `service vdsmd restart` and then everythign works fine. you are basically saying "re-installing a host causes vdsm to not start by default". reproducing this again to make sure and opening a bug seems the right course. trying to trace the install flow to provide root cause or even a patch would help more to fix this Are you saying that vdsmd service should start by default post reboot and its entry should be listed as part of chkconfig --list ? vdsm uses systemd. http://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet Try to use chkconfig vdsm on, you will see a wrapper to systemd command. Found this examining the vds bootstrap complete py log 2012-02-28 23:45:32,022 DEBUGdeployUtil 707 _updateFileLine: return: True 2012-02-28 23:45:32,022 DEBUGdeployUtil 228 setVdsConf: ended. 2012-02-28 23:45:32,022 DEBUGdeployUtil 103 ['/bin/systemctl', 'reconfigure', 'vdsmd.service'] 2012-02-28 23:45:32,026 DEBUGdeployUtil 107 2012-02-28 23:45:32,026 DEBUGdeployUtil 108 Unknown operation reconfigure 2012-02-28 23:45:32,026 DEBUGdeployUtil 103 ['/sbin/reboot'] 2012-02-28 23:45:32,325 DEBUGdeployUtil 107 Which vdsm version are you using? If I am not wrong, I remember to see a patch for this report.. /me going to check.. Thanks! -- Cheers Douglas ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] Remove and Add host does not work
On 02/28/2012 07:11 PM, Itamar Heim wrote: On 02/28/2012 03:31 PM, Deepak C Shetty wrote: On 02/28/2012 06:57 PM, Itamar Heim wrote: On 02/28/2012 03:22 PM, Deepak C Shetty wrote: On 02/28/2012 06:46 PM, Itamar Heim wrote: On 02/28/2012 02:48 PM, Deepak C Shetty wrote: Hi, I had a host managed via OE, completely working fine. Was even able to create and run VMs off it. I tried removing the host from the OE (put host into maint. mode and then remove) and when i re-discover the same host, OE just keeps seeing it as Non-responsive. what do you mean by "re-discover"? I just meant that i removed the host and re-added it by selecting "New" on the Hosts tab and putting the IP and hostname. I am able to ssh into the host and see that none of the vdsm processes have been started. I tried doing "Confirm host has been rebooted" on the OE, did not help. I tried putting host into maint. mode and re-activating the host, just doesn't help did you do any change to the host? just removing it from engine shouldn't cause vdsm to know/care and should work just like before. Nothing changed on the host. In fact when i removed and added the host back it says everything is installed so does nothing but reboots the host, post reboot vdsm does not start automatically and host status is non-responsive on OE if vdsm does not start, OE is correct... does vdsm try to start and fails (and if so, log excerpt?) Right, but I dont see any traces of vdsm trying to start. Nothing in the vdsm.log thats relevant to this. I just did chkconfig --list and don't see vdsmd in that, could that be the reason. On the host I manually did `service vdsmd restart` and then everythign works fine. you are basically saying "re-installing a host causes vdsm to not start by default". reproducing this again to make sure and opening a bug seems the right course. trying to trace the install flow to provide root cause or even a patch would help more to fix this Are you saying that vdsmd service should start by default post reboot and its entry should be listed as part of chkconfig --list ? Found this examining the vds bootstrap complete py log 2012-02-28 23:45:32,022 DEBUGdeployUtil 707 _updateFileLine: return: True 2012-02-28 23:45:32,022 DEBUGdeployUtil 228 setVdsConf: ended. 2012-02-28 23:45:32,022 DEBUGdeployUtil 103 ['/bin/systemctl', 'reconfigure', 'vdsmd.service'] 2012-02-28 23:45:32,026 DEBUGdeployUtil 107 2012-02-28 23:45:32,026 DEBUGdeployUtil 108 Unknown operation reconfigure 2012-02-28 23:45:32,026 DEBUGdeployUtil 103 ['/sbin/reboot'] 2012-02-28 23:45:32,325 DEBUGdeployUtil 107 ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] Remove and Add host does not work
On 02/28/2012 03:31 PM, Deepak C Shetty wrote: On 02/28/2012 06:57 PM, Itamar Heim wrote: On 02/28/2012 03:22 PM, Deepak C Shetty wrote: On 02/28/2012 06:46 PM, Itamar Heim wrote: On 02/28/2012 02:48 PM, Deepak C Shetty wrote: Hi, I had a host managed via OE, completely working fine. Was even able to create and run VMs off it. I tried removing the host from the OE (put host into maint. mode and then remove) and when i re-discover the same host, OE just keeps seeing it as Non-responsive. what do you mean by "re-discover"? I just meant that i removed the host and re-added it by selecting "New" on the Hosts tab and putting the IP and hostname. I am able to ssh into the host and see that none of the vdsm processes have been started. I tried doing "Confirm host has been rebooted" on the OE, did not help. I tried putting host into maint. mode and re-activating the host, just doesn't help did you do any change to the host? just removing it from engine shouldn't cause vdsm to know/care and should work just like before. Nothing changed on the host. In fact when i removed and added the host back it says everything is installed so does nothing but reboots the host, post reboot vdsm does not start automatically and host status is non-responsive on OE if vdsm does not start, OE is correct... does vdsm try to start and fails (and if so, log excerpt?) Right, but I dont see any traces of vdsm trying to start. Nothing in the vdsm.log thats relevant to this. I just did chkconfig --list and don't see vdsmd in that, could that be the reason. On the host I manually did `service vdsmd restart` and then everythign works fine. you are basically saying "re-installing a host causes vdsm to not start by default". reproducing this again to make sure and opening a bug seems the right course. trying to trace the install flow to provide root cause or even a patch would help more to fix this ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] Remove and Add host does not work
On 02/28/2012 06:57 PM, Itamar Heim wrote: On 02/28/2012 03:22 PM, Deepak C Shetty wrote: On 02/28/2012 06:46 PM, Itamar Heim wrote: On 02/28/2012 02:48 PM, Deepak C Shetty wrote: Hi, I had a host managed via OE, completely working fine. Was even able to create and run VMs off it. I tried removing the host from the OE (put host into maint. mode and then remove) and when i re-discover the same host, OE just keeps seeing it as Non-responsive. what do you mean by "re-discover"? I just meant that i removed the host and re-added it by selecting "New" on the Hosts tab and putting the IP and hostname. I am able to ssh into the host and see that none of the vdsm processes have been started. I tried doing "Confirm host has been rebooted" on the OE, did not help. I tried putting host into maint. mode and re-activating the host, just doesn't help did you do any change to the host? just removing it from engine shouldn't cause vdsm to know/care and should work just like before. Nothing changed on the host. In fact when i removed and added the host back it says everything is installed so does nothing but reboots the host, post reboot vdsm does not start automatically and host status is non-responsive on OE if vdsm does not start, OE is correct... does vdsm try to start and fails (and if so, log excerpt?) Right, but I dont see any traces of vdsm trying to start. Nothing in the vdsm.log thats relevant to this. I just did chkconfig --list and don't see vdsmd in that, could that be the reason. On the host I manually did `service vdsmd restart` and then everythign works fine. ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] Remove and Add host does not work
On 02/28/2012 03:22 PM, Deepak C Shetty wrote: On 02/28/2012 06:46 PM, Itamar Heim wrote: On 02/28/2012 02:48 PM, Deepak C Shetty wrote: Hi, I had a host managed via OE, completely working fine. Was even able to create and run VMs off it. I tried removing the host from the OE (put host into maint. mode and then remove) and when i re-discover the same host, OE just keeps seeing it as Non-responsive. what do you mean by "re-discover"? I just meant that i removed the host and re-added it by selecting "New" on the Hosts tab and putting the IP and hostname. I am able to ssh into the host and see that none of the vdsm processes have been started. I tried doing "Confirm host has been rebooted" on the OE, did not help. I tried putting host into maint. mode and re-activating the host, just doesn't help did you do any change to the host? just removing it from engine shouldn't cause vdsm to know/care and should work just like before. Nothing changed on the host. In fact when i removed and added the host back it says everything is installed so does nothing but reboots the host, post reboot vdsm does not start automatically and host status is non-responsive on OE if vdsm does not start, OE is correct... does vdsm try to start and fails (and if so, log excerpt?) ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] Remove and Add host does not work
On 02/28/2012 06:46 PM, Itamar Heim wrote: On 02/28/2012 02:48 PM, Deepak C Shetty wrote: Hi, I had a host managed via OE, completely working fine. Was even able to create and run VMs off it. I tried removing the host from the OE (put host into maint. mode and then remove) and when i re-discover the same host, OE just keeps seeing it as Non-responsive. what do you mean by "re-discover"? I just meant that i removed the host and re-added it by selecting "New" on the Hosts tab and putting the IP and hostname. I am able to ssh into the host and see that none of the vdsm processes have been started. I tried doing "Confirm host has been rebooted" on the OE, did not help. I tried putting host into maint. mode and re-activating the host, just doesn't help did you do any change to the host? just removing it from engine shouldn't cause vdsm to know/care and should work just like before. Nothing changed on the host. In fact when i removed and added the host back it says everything is installed so does nothing but reboots the host, post reboot vdsm does not start automatically and host status is non-responsive on OE I waited for ~45 mins thinking OE might connect to the host, start vdsm and get me the Up status but it failed. Do i need to manually start vdsm in such a scenario on the host ? Are there ways or methods to have OE forcibly start vdsm on the host ? thanx, deepak ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] Remove and Add host does not work
On 02/28/2012 02:48 PM, Deepak C Shetty wrote: Hi, I had a host managed via OE, completely working fine. Was even able to create and run VMs off it. I tried removing the host from the OE (put host into maint. mode and then remove) and when i re-discover the same host, OE just keeps seeing it as Non-responsive. what do you mean by "re-discover"? I am able to ssh into the host and see that none of the vdsm processes have been started. I tried doing "Confirm host has been rebooted" on the OE, did not help. I tried putting host into maint. mode and re-activating the host, just doesn't help did you do any change to the host? just removing it from engine shouldn't cause vdsm to know/care and should work just like before. I waited for ~45 mins thinking OE might connect to the host, start vdsm and get me the Up status but it failed. Do i need to manually start vdsm in such a scenario on the host ? Are there ways or methods to have OE forcibly start vdsm on the host ? thanx, deepak ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] Remove and Add host does not work
Hi, I had a host managed via OE, completely working fine. Was even able to create and run VMs off it. I tried removing the host from the OE (put host into maint. mode and then remove) and when i re-discover the same host, OE just keeps seeing it as Non-responsive. I am able to ssh into the host and see that none of the vdsm processes have been started. I tried doing "Confirm host has been rebooted" on the OE, did not help. I tried putting host into maint. mode and re-activating the host, just doesn't help I waited for ~45 mins thinking OE might connect to the host, start vdsm and get me the Up status but it failed. Do i need to manually start vdsm in such a scenario on the host ? Are there ways or methods to have OE forcibly start vdsm on the host ? thanx, deepak ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
