Really need some help here ...
Hi, I have been trying to build either RPMs or DEB packages for Cloudstack 4.0.2 with VMWare enabled, but have been unsuccessful. I can build successfully using Maven (mvn -P deps -D nonoss) but the DEB/RPM build processes apparently rebuild on their own without using the artifacts created by the Maven build. We are currently using the Cloudstack 3.0.2 version, but want to take advantage of the latest features available with 4.0.2. Can anyone please help? Is there a way to install what is being built for DEB/RPMs and then manually modify that installed Cloudstack 4.0.2 environment to support VMWare? Regards, --Jim L.
Cloud -agent is dead, but the subsys is locked
Hello everyone: I am having an issue to add a kvm host. When I add the first kvm host ,I get a problem that Unable to add the host the service status : Cloud -agent is dead, but the subsys is locked
Re: Really need some help here ...
On Sat, Apr 27, 2013 at 9:07 AM, Jim L. j...@pobox.com wrote: Hi, I have been trying to build either RPMs or DEB packages for Cloudstack 4.0.2 with VMWare enabled, but have been unsuccessful. I can build successfully using Maven (mvn -P deps -D nonoss) but the DEB/RPM build processes apparently rebuild on their own without using the artifacts created by the Maven build. We are currently using the Cloudstack 3.0.2 version, but want to take advantage of the latest features available with 4.0.2. Can anyone please help? Is there a way to install what is being built for DEB/RPMs and then manually modify that installed Cloudstack 4.0.2 environment to support VMWare? Regards, --Jim L. Hi Jim, So while I am happy to help you build those packages, do you really need to build them yourself? Wido's yum repo has packages with VMware support (I can't speak for the debs, I don't think 4.0.2 is there yet) http://cloudstack.apt-get.eu/rhel/4.0/ --David
Re: Cloudstack.org domain
Okay, thanks Prasanna! On 17 April 2013 07:44, Prasanna Santhanam t...@apache.org wrote: On Tue, Apr 16, 2013 at 02:07:45PM +0100, Noah Slater wrote: Okay, some success. Here is a mail sent to infrastruct...@apache.org: On 16 April 2013 13:44, Tony Stevenson pct...@apache.org wrote: Noah Slater wrote on Tue, Apr 16, 2013 at 01:33:39PM +0100: Hi, It recently came up on the CloudStack list that if cloudstack.orgmoves over to ASF control, we would not be able to point foo.cloudstack.org at an external VM. (Say, a committer is running a CI/build/whatever service.) Is this the case? Are there any exceptions to this? I ask not because I want to drag up old discussions for the sake of it, but because we have some ongoing trademark stuff with CouchDB, and one of the things I am planning to propose is that we move couchdb.org to ASF control. But if the above is policy, that wouldn't work. http://docs.couchdb.org/points at a third-party hosted service, for instance. And we are working on a Jenkins setup that is not on ASF hardware (because the ASF is unable to provide us with the hardware we require at this time). Could someone clarify this for me? Noah we have several instances of DNS records pointing to non-ASF hosted services. We would clearly very much prefer that we didnt have to do this, but I do not believe it is against policy. Our issue comes from the fact the machine is not under our control, and as such anyone could just add $bad-content within the apache.org namespace. At the moment, from memory, all records that point to non-ASF hardware, are still machines we control. Your asking for something above and beyond this, and I suspect if this is what the PMC wants then that would be done. But it would need to be requested, following a vote thread and that link given to us so we can see the process :) This is from a private list, but I have been granted permission to share it with this one. For those with the appropriate karma, the thread starts here: http://s.apache.org/ZLE So, if we put together a definitive plan of action for the domain, and the services we want to host / point to, along with who is operating them, and what the plan for that is, and vote on it, it looks like we can proceed. (But we should be mindful of Infra's concerns, and take them into account while drafting the proposal.) Thanks Noah. That helps clear some confusions. But I've moved jenkins.cs.o to a different namespace as was done before with docs.cs.o. jenkins.cs.o now resides at jenkins.buildacloud.org. One of the difficulties for moving our jobs to builds@ was the performance and hardware considerations. I think some infra@ folks are aware of the problems we have with having to stack up enough hardware to run tests for our system. Having a separate managed jenkins is useful for us to quickly fix problems as is often the case with automated testing. Some of the other cs.o services are managed by David and myself. David has the necessary karma within infra to look into these when things go bad. Unless others feel that the services should remain on cloudstack.org I think we have a reasonable backup plan for now. Anyone think otherwise? -- Prasanna., -- NS
CloudStack GitHub repository
Devs, I have requested that our GitHub repository be moved to indicate we are no longer in incubation. Follow along here: https://issues.apache.org/jira/browse/INFRA-6203 Thanks, -- NS
[DISCUSS] Enable GitHub pull request notification (Was: Re: GitHub pull requests (Was: Re: Github integration))
Devs, I would like to propose that we turn on notifications for pull requests that are made via GitHub. This will ensure that PRs are not lost between the cracks. I believe this integration is already available, and we just need to request it. You do not need to respond if you are in agreement. If there is no response in 72 hours, I will assume lazy consensus. If we reach consensus, I will start the corresponding [VOTE] thread and complete the rest of process. (Please note that when I brought this up originally, the idea had a +1 from Prasanna and Rohit. But I do not believe I stated lazy consensus So I am doing this a second time, properly. Sorry about that folks!) Thanks, On 7 October 2012 03:03, Noah Slater nsla...@tumbolia.org wrote: I've been talking with Paul Davis about how we can fix this situation. But no, at the moment, you cannot merge them directly in GitHub. However, while we might advocate RB as the preferred way to submit patches, I do not think we should lock out people who prefer to work within the confines of GitHub. This question is not just about should we get notifications sent. It is more about should we open this up as a supported channel for receiving contributions? On Sun, Oct 7, 2012 at 1:59 AM, Brett Porter br...@apache.org wrote: On 30/09/2012, at 2:31 AM, Noah Slater nsla...@tumbolia.org wrote: Breaking off this question: On Sat, Sep 29, 2012 at 3:50 PM, Donal Lafferty donal.laffe...@citrix.comwrote: WRT emails for all GIT pulls, wouldn't broadcasting pull requests clutter the dev mailing list? No, I don't think so. A GitHub pull request is the same as someone coming to the list and asking us to apply a patch. If they become a nuisance (what a wonderful problem to have!) we could funnel them elsewhere. PR integration on GitHub will attract a broader base of contributions from the community. My understanding of the current pull request integration is that notifications can be sent to the list, but can not be closed or interacted with on github (other than requesting the original reporter to close them, or an administrator) - so it's not really integration as much as avoiding it slipping through the cracks when someone finds the github repo. Is that still the case? Particularly with review board in place, it would seem like getting notifications of PRs is a good idea, but explicitly encouraging their use is not. - Brett -- NS -- NS
Re: CloudStack GitHub repository
Thanks, Rohit. I marked mine as a dupe! On 27 April 2013 17:30, Rohit Yadav bhais...@apache.org wrote: Thanks Noah, I've had raised an issue with infra a long time ago but that is still open: https://issues.apache.org/jira/browse/INFRA-6061 Cheers. On Sat, Apr 27, 2013 at 9:58 PM, Noah Slater nsla...@apache.org wrote: Devs, I have requested that our GitHub repository be moved to indicate we are no longer in incubation. Follow along here: https://issues.apache.org/jira/browse/INFRA-6203 Thanks, -- NS -- NS
Re: Error starting management server
I found out the issue. I was behind the proxy and python was not able to bypass the local address. After unsetting proxy, I am able to add zones, pod and cluster. But while adding hosts I get following error: INFO [cloud.resource.ResourceManagerImpl] (1793095672@qtp-165312501-9:) Trying to add a new host at http://192.168.56.10 in data center 1 WARN [cloud.resource.ResourceManagerImpl] (1793095672@qtp-165312501-9:) Unable to find the server resources at http://192.168.56.10 INFO [utils.exception.CSExceptionErrorCode] (1793095672@qtp-165312501-9:) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions WARN [admin.host.AddHostCmd] (1793095672@qtp-165312501-9:) Exception: com.cloud.exception.DiscoveryException: Unable to add the host at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:894) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:639) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:512) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:362) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) at com.cloud.api.ApiServlet.doPost(ApiServlet.java:71) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:945) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) INFO [cloud.api.ApiServer] (1793095672@qtp-165312501-9:) Unable to add the host Host (192.168.56.10) and management servers are able to ping each other. Any pointers on what can be wrong ? Thanks, Dharmesh On Fri, Apr 26, 2013 at 7:33 PM, Prasanna Santhanam t...@apache.org wrote: On Fri, Apr 26, 2013 at 06:30:23PM +0530, Dharmesh Kakadia wrote: Hi, I have created bug https://issues.apache.org/jira/browse/CLOUDSTACK-2211as suggested by you. Being a newbie I was not sure how things are done in Apache Way. Couldn't assign you the bug. Correct me if I missed something. That is the Apache Way ;) I'll pick it up and add some logs for you soon. Thanks for your patience. You should be able to proceed with the UI Wizard in the meantime to setup your zones. -- Prasanna., Powered by BigRock.com
Re: [DISCUSS] Enable GitHub pull request notification (Was: Re: GitHub pull requests (Was: Re: Github integration))
On 27 April 2013 17:35, Noah Slater nsla...@apache.org wrote: If we reach consensus, I will start the corresponding [VOTE] thread and complete the rest of process. D'oh. That's what I get for copying and pasting email templates. Edit: if we reach consensus, I will just go ahead and request the notifications. No need for a vote on something like this unless lazy consensus fails. ;) -- NS
Re: Really need some help here ...
Hi David, I know Wido's DEBs do not have VMWare support (at least, the last time I tried to used them). I'll give the RPM's a try, however. In the meantime: is there additional documentation/wiki/back of a napkin that explains how to build DEB or RPM packages with VMWare support? I would like to have that ability if I decide to write additional plugins for some projects I'm working on. I did try to hand-roll an installation on Ubuntu by taking the 3.0.2 version I have now and using that as a template to modify the 4.0.2 /etc/cloud/management/components.xml file, adding the adapters VMWare Discoverer and VMWare HypervisorGuru to the config. I also added the /usr/share/java/cloud-plugins directory with the VMWare base and hypervisor jars ( in addition to the vmware-vim25.jar, vmware-apputils,jar, etc., files), but I encountered numerous classpath/missing jar issues. I (think I) finally resolved those, but the VMwareGuru component will not instantiate/initialize, so I put all of that on hold until I could get some help. So, I'll give Wido's repo a try on CentOS but it would be great to know how to do this on my own as well and would prefer Ubuntu if possible. Thanks for responding. Regards, --Jim L. On Sat, Apr 27, 2013 at 11:12 AM, David Nalley da...@gnsa.us wrote: On Sat, Apr 27, 2013 at 9:07 AM, Jim L. j...@pobox.com wrote: Hi, I have been trying to build either RPMs or DEB packages for Cloudstack 4.0.2 with VMWare enabled, but have been unsuccessful. I can build successfully using Maven (mvn -P deps -D nonoss) but the DEB/RPM build processes apparently rebuild on their own without using the artifacts created by the Maven build. We are currently using the Cloudstack 3.0.2 version, but want to take advantage of the latest features available with 4.0.2. Can anyone please help? Is there a way to install what is being built for DEB/RPMs and then manually modify that installed Cloudstack 4.0.2 environment to support VMWare? Regards, --Jim L. Hi Jim, So while I am happy to help you build those packages, do you really need to build them yourself? Wido's yum repo has packages with VMware support (I can't speak for the debs, I don't think 4.0.2 is there yet) http://cloudstack.apt-get.eu/rhel/4.0/ --David
Re: [DISCUSS] Enable GitHub pull request notification (Was: Re: GitHub pull requests (Was: Re: Github integration))
Good question, John! We will handle it the same way we handle patches that come in via JIRA, or the mailing list, or any other channel. i.e. The creation of a PR against the official mirror is seen as an indication of intent that the work be contributed to the project, as the Apache licenses quite cleverly handles the rest, so we don't have to do anything in particular. On 27 April 2013 18:05, John Burwell jburw...@basho.com wrote: Noah, How do we handle the contributor agreement/IP issues when handling code submitted through a Github PR? Thanks, -John On Sat, Apr 27, 2013 at 12:45 PM, Noah Slater nsla...@apache.org wrote: On 27 April 2013 17:35, Noah Slater nsla...@apache.org wrote: If we reach consensus, I will start the corresponding [VOTE] thread and complete the rest of process. D'oh. That's what I get for copying and pasting email templates. Edit: if we reach consensus, I will just go ahead and request the notifications. No need for a vote on something like this unless lazy consensus fails. ;) -- NS -- NS
Re: Really need some help here ...
Chip, I'll do that. Thanks for the info. Regards, --Jim L. On Sat, Apr 27, 2013 at 1:25 PM, Chip Childers chip.child...@sungard.comwrote: There is a bug in the 4.0.x Debian/rules file that excludes the optional -Dnonoss flag. Look at the 4.1 branch copy and note the env variable I added to support optional mvn flags during the packaging's build step. On Apr 27, 2013, at 1:22 PM, Jim L. j...@pobox.com wrote: Hi David, I know Wido's DEBs do not have VMWare support (at least, the last time I tried to used them). I'll give the RPM's a try, however. In the meantime: is there additional documentation/wiki/back of a napkin that explains how to build DEB or RPM packages with VMWare support? I would like to have that ability if I decide to write additional plugins for some projects I'm working on. I did try to hand-roll an installation on Ubuntu by taking the 3.0.2 version I have now and using that as a template to modify the 4.0.2 /etc/cloud/management/components.xml file, adding the adapters VMWare Discoverer and VMWare HypervisorGuru to the config. I also added the /usr/share/java/cloud-plugins directory with the VMWare base and hypervisor jars ( in addition to the vmware-vim25.jar, vmware-apputils,jar, etc., files), but I encountered numerous classpath/missing jar issues. I (think I) finally resolved those, but the VMwareGuru component will not instantiate/initialize, so I put all of that on hold until I could get some help. So, I'll give Wido's repo a try on CentOS but it would be great to know how to do this on my own as well and would prefer Ubuntu if possible. Thanks for responding. Regards, --Jim L. On Sat, Apr 27, 2013 at 11:12 AM, David Nalley da...@gnsa.us wrote: On Sat, Apr 27, 2013 at 9:07 AM, Jim L. j...@pobox.com wrote: Hi, I have been trying to build either RPMs or DEB packages for Cloudstack 4.0.2 with VMWare enabled, but have been unsuccessful. I can build successfully using Maven (mvn -P deps -D nonoss) but the DEB/RPM build processes apparently rebuild on their own without using the artifacts created by the Maven build. We are currently using the Cloudstack 3.0.2 version, but want to take advantage of the latest features available with 4.0.2. Can anyone please help? Is there a way to install what is being built for DEB/RPMs and then manually modify that installed Cloudstack 4.0.2 environment to support VMWare? Regards, --Jim L. Hi Jim, So while I am happy to help you build those packages, do you really need to build them yourself? Wido's yum repo has packages with VMware support (I can't speak for the debs, I don't think 4.0.2 is there yet) http://cloudstack.apt-get.eu/rhel/4.0/ --David
Re: deployDataCenter.py doesn't work for me on master
Thank you, Dharmesh...that is exactly how we (myself and others) ended up
solving this issue. :)
On Sat, Apr 27, 2013 at 5:20 AM, Dharmesh Kakadia dhkaka...@gmail.comwrote:
not sure you are still having this issue. You can install requests module
by pip install requests.
On Thu, Apr 18, 2013 at 11:23 PM, Mike Tutkowski
mike.tutkow...@solidfire.com wrote:
Is this similar to the problem you are now having? I get the following
output from the python script to create DevCloud:
mtutkowski-LT:devcloud mtutkowski$ python
../marvin/marvin/deployDataCenter.py -i devcloud.cfg
Traceback (most recent call last):
File ../marvin/marvin/deployDataCenter.py, line 21, in module
import cloudstackTestClient
File
/Users/mtutkowski/Documents/CloudStack/src/incubator-cloudstack/tools/marvin/marvin/cloudstackTestClient.py,
line 18, in module
import cloudstackConnection
File
/Users/mtutkowski/Documents/CloudStack/src/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py,
line 18, in module
import requests
ImportError: No module named requests
Not sure how to get around this.
On Wed, Apr 17, 2013 at 10:56 AM, Soheil Eizadi seiz...@infoblox.com
wrote:
I copied the vhd-util from
http://download.cloud.com.s3.amazonaws.com/tools/vhd-util to
scripts/vm/hypervisor/xenserver/vhd-util in the tree, but it did not
resolve my issue. (The problem is not with the functionality of the
vhd-util but a path problem. I get that the vhd-util should be updated
and
I have done that as well in my environment.)
As I noted below the problem is that it is not getting copied to right
place and also I find different versions of the higher level script i.e.
copy_vhd_from_secondarystorage.sh in my tree which is strange. There is
different vhd-util paths in them.
-Soheil
On 4/15/13 4:07 PM, Anthony Xu xuefei...@citrix.com wrote:
The XenServer (6.0.2) I am using already came bundled with vhd-util,
I
did not have to download it. I have not read the detail of
Hi Soheil,
We added one function in vhd-util, which allows vhd-util specifiy
parent
when do coalesce, basically you can coalesce a VHD file to other VHD
file.
CS uses this vhd-util function in API creating template/volume from
snapshot. These APIs might not work with bundled vhd-util in
XenServer.
Anthony
-Original Message-
From: Soheil Eizadi [mailto:seiz...@infoblox.com]
Sent: Saturday, April 13, 2013 11:05 PM
To: dev@cloudstack.apache.org
Subject: Re: deployDataCenter.py doesn't work for me on master
Downloaded the vhd-util to my environment and had the same problem. I
Debugged this further by running the copy_vhd_from_secondarystorage.sh
on
the XenServer. It looks like the copy_vhd_from_secondarystorage.sh is
looking for vhd-util in /opt/xensource/bin/ rather than /usr/bin/
I looked at this further and looks like what is built in the
client/target directory is not consistent with what is in the
./scripts/vm in my tree.
There are two versions of copy_vhd_from_secondarystorage.sh.
I removed the client/target directory and rebuilt, but had the same
files
appear again. I am not sure how they are getting pulled in to the
client/target directory. Any ideas why my build is broken and how to
proceed to fix this?
For now I patched this on my XenServer and was able to get ssvm and
cproxyvm running and brought up my CloudStack zone completely.
-Soheil
Administrators-MacBook-Pro-7:cloudstack seizadi$ find . -name
copy_vhd_from_secondarystorage.sh
./client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/scripts/vm/
h
ypervisor/xenserver/copy_vhd_from_secondarystorage.sh
./client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/scripts/vm/
h
ypervisor/xenserver/xcposs/copy_vhd_from_secondarystorage.sh
./client/target/generated-webapp/WEB-INF/classes/scripts/vm/hypervisor/xen
s
erver/copy_vhd_from_secondarystorage.sh
./client/target/generated-webapp/WEB-INF/classes/scripts/vm/hypervisor/xen
s
erver/xcposs/copy_vhd_from_secondarystorage.sh
./scripts/vm/hypervisor/xenserver/copy_vhd_from_secondarystorage.sh
./scripts/vm/hypervisor/xenserver/xcposs/copy_vhd_from_secondarystorage.sh
Administrators-MacBook-Pro-7:cloudstack seizadi$ find . -name
copy_vhd_from_secondarystorage.sh -exec diff
./client/target/generated-webapp/WEB-INF/classes/scripts/vm/hypervisor/xen
s
erver/copy_vhd_from_secondarystorage.sh {} \;
92c92
VHDUTIL=/opt/xensource/bin/vhd-util
---
VHDUTIL=/usr/bin/vhd-util
113c113
if [ $type != nfs -a $type != ext ]; then
---
if [ $type != nfs -a $type != ext -a $type != file ]; then
143c143
desvhd=/var/run/sr-mount/$sruuid/$uuid.vhd
---
desvhd=/run/sr-mount/$sruuid/$uuid.vhd
160a161,166
elif [ $type == file ]; then
pbd=`xe sr-param-list uuid=$sruuid |grep PBDs | awk '{print $3}'`
path=`xe
Re: [DISCUSS] Enable GitHub pull request notification (Was: Re: GitHub pull requests (Was: Re: Github integration))
On Sat, Apr 27, 2013 at 12:35 PM, Noah Slater nsla...@apache.org wrote: Devs, I would like to propose that we turn on notifications for pull requests that are made via GitHub. This will ensure that PRs are not lost between the cracks. I believe this integration is already available, and we just need to request it. You do not need to respond if you are in agreement. If there is no response in 72 hours, I will assume lazy consensus. If we reach consensus, I will start the corresponding [VOTE] thread and complete the rest of process. (Please note that when I brought this up originally, the idea had a +1 from Prasanna and Rohit. But I do not believe I stated lazy consensus So I am doing this a second time, properly. Sorry about that folks!) Thanks, I think, but am not sure, that after the first PR against a github repo that infra@ sets up forwarding rules so they end up on dev@. (I do lots of infra git work, but not github work). That said, I see there has been one, but I don't recall that coming to dev@ [1]. Regardless, my opinion is that there really isn't an option - if we are going to have a github mirror, we also need to be able to deal with the pull requests there. Ignoring folks that submit pull requests is inappropriate. [1] https://github.com/apache/incubator-cloudstack/pull/1 --David
