Alright, so the default compute offering "Medium" that I see does not have local storage, so it won't run as it won't find any host that would support shared disk vm deployment. Create a new offering with required capacities and local storage, or add a primary NFS and a host with no local sr. Hope this helps.
Regards. ________________________________________ From: Charles Moulliard [ch0...@gmail.com] Sent: Saturday, December 01, 2012 10:03 PM To: cloudstack-dev Subject: Re: New DevCloud Appliance How can you change ram ? I have the same error even using this setup : Zone : DevCloud0 Hypervisor : XenServer Template : Centos-6.3 Compute offering : Medium Instance Data Disk Offering : Small Security : Groups default On Sat, Dec 1, 2012 at 4:36 PM, Rohit Yadav <rohit.ya...@citrix.com> wrote: > May be it requires more than 100M ram and a lot more disk, tinyOfferring > is very small. > ________________________________________ > From: Charles Moulliard [ch0...@gmail.com] > Sent: Saturday, December 01, 2012 5:51 PM > To: cloudstack-dev > Subject: Re: New DevCloud Appliance > > Works for me too ;-) > > I have been able also to upload a Centos ISO file ( > CentOS-6.3-x86_64-minimal.iso< > http://192.168.56.10/CentOS-6.3-x86_64-minimal.iso>) > but when I create a new instance, I get this message "Unable to create a > deployment for VM[User|test]" and this message in the log : > > WARN [agent.manager.AgentManagerImpl] (ClusteredAgentManager Timer:) > Unable to load the resource: 1 > INFO [api.commands.DeployVMCmd] (Job-Executor-7:job-16) > com.cloud.exception.InsufficientServerCapacityException: Unable to create a > deployment for VM[User|test]Scope=interface com.cloud.dc.DataCenter; id=1 > WARN [cloud.api.ApiDispatcher] (Job-Executor-7:job-16) class > com.cloud.api.ServerApiException : Unable to create a deployment for > VM[User|test] > > with the following parameters : > > Name (Optional) : test > Add to group (Optional) : > Zone : DevCloud0 > Hypervisor : XenServer > Template : Centos-6.3 > Compute offering : tinyOffering > Data Disk Offering : tinyDiskOffering > Security Groups : default > > If we know that we will be unable to create an instance, why do we allow to > create an instance instead of blocking the user during the creation process > or by showing a message in the screen concerning Data Disk offering ? > > What is the workaround ? > > Regards, > > Charles > > > > On Fri, Nov 30, 2012 at 8:27 PM, Rohit Yadav <rohit.ya...@citrix.com> > wrote: > > > works for me: > > > http://sebgoa.blogspot.com/2012/11/testing-cloudstack-41-with-devcloud.html > > ________________________________________ > > From: Charles Moulliard [ch0...@gmail.com] > > Sent: Saturday, December 01, 2012 12:15 AM > > To: cloudstack-dev > > Subject: Re: New DevCloud Appliance > > > > The link is wrong ... > > > > > > On Fri, Nov 30, 2012 at 7:42 PM, Sebastien Goasguen <run...@gmail.com > > >wrote: > > > > > Charles, I just posted a screencast. The one thing different is that I > am > > > actually running cloudstack locally and using devcloud as a host. > > > > > > > > > http://sebgoa.blogspot.com/2012/11/testing-cloudstack-41-with-devcloud.html > > > > > > On Nov 30, 2012, at 7:19 PM, Charles Moulliard <ch0...@gmail.com> > wrote: > > > > > > > Thx Sebastien. If I compile last version of the code on DevCloud VM > > > > (192.168.56.10) running in VB, I get this error now : > > > > > > > > mvn -P developer -pl tools/devcloud -Ddeploysvr > > > > [INFO] Scanning for projects... > > > > [INFO] > > > > > > > > [INFO] > > > > > > ------------------------------------------------------------------------ > > > > [INFO] Building Apache CloudStack Developer Tools 4.1.0-SNAPSHOT > > > > [INFO] > > > > > > ------------------------------------------------------------------------ > > > > [INFO] > > > > [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ > > > > cloud-devcloud --- > > > > [INFO] > > > > [INFO] --- maven-site-plugin:3.1:attach-descriptor > (attach-descriptor) > > @ > > > > cloud-devcloud --- > > > > [INFO] > > > > [INFO] --- exec-maven-plugin:1.2.1:exec (default) @ cloud-devcloud > --- > > > > Traceback (most recent call last): > > > > File "../marvin/marvin/deployDataCenter.py", line 435, in <module> > > > > deploy.deploy() > > > > File "../marvin/marvin/deployDataCenter.py", line 419, in deploy > > > > self.createZones(self.config.zones) > > > > File "../marvin/marvin/deployDataCenter.py", line 286, in > createZones > > > > zoneresponse = self.apiClient.createZone(createzone) > > > > File > > > > > > > > > > "/opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py", > > > > line 1013, in createZone > > > > response = self.connection.make_request(command, response) > > > > File > > > > > > > > > > "/opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py", > > > > line 175, in make_request > > > > result = self.make_request_with_auth(commandName, requests) > > > > File > > > > > > > > > > "/opt/cloudstack/incubator-cloudstack/tools/marvin/marvin/cloudstackConnection.py", > > > > line 89, in make_request_with_auth > > > > raise e > > > > urllib2.HTTPError: HTTP Error 431: 431 > > > > > > > > INFO [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:) We > are > > > > good, no orphan management server msid in host table is found > > > > INFO [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:) No > > > inactive > > > > management server node found > > > > WARN [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:) > > > > Notifying management server join event took 18 ms > > > > INFO [cloud.resource.ResourceManagerImpl] (16113904@qtp-22625510-5 > :) > > > > Trying to add a new host at http://192.168.56.10/ in data center 1 > > > > WARN [cloud.resource.ResourceManagerImpl] (16113904@qtp-22625510-5 > :) > > > > Unable to find the server resources at http://192.168.56.10/ > > > > WARN [api.commands.AddHostCmd] (16113904@qtp-22625510-5:) > Exception: > > > > com.cloud.exception.DiscoveryException: Unable to add the host > > > > at > > > > > > > > > > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:737) > > > > at > > > > > > > > > > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:544) > > > > at com.cloud.api.commands.AddHostCmd.execute(AddHostCmd.java:140) > > > > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:167) > > > > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:539) > > > > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:423) > > > > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:311) > > > > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > > > > 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.headerComplete(HttpConnection.java:928) > > > > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) > > > > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) > > > > 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) > > > > WARN [cloud.api.ApiDispatcher] (16113904@qtp-22625510-5:) class > > > > com.cloud.api.ServerApiException : Unable to add the host > > > > > > > > > > > > > > > > > > > > On Fri, Nov 30, 2012 at 7:01 PM, Sebastien Goasguen < > run...@gmail.com > > > >wrote: > > > > > > > >> Charles, > > > >> > > > >> The 10.0.0.3 address in your SSVM is suspect. Can you make sure you > > have > > > >> the last version of /tools/devcloud/devcloud.cfg ? > > > >> > > > >> I manage to upload a new image, running a web server on my local > > machine > > > >> with: > > > >> sudo python -m SimpleHTTPServer 443 > > > >> > > > >> The SSVM should be able to ping the host on which you are running > the > > > http > > > >> server. > > > >> > > > >> -Sebastien > > > >> > > > >> On Nov 30, 2012, at 6:43 PM, Charles Moulliard <ch0...@gmail.com> > > > wrote: > > > >> > > > >>> Rohit, > > > >>> > > > >>> Even, If I use a local HTTP Server, there is still an issue with > the > > > >>> DevCloud2.ova image with NFS. > > > >>> > > > >>> WARN [cloud.resource.DiscovererBase] (ClusteredAgentManager > Timer:) > > > >> Unable > > > >>> to configure resource due to Can not create slave connection to > > > >>> 192.168.56.10 > > > >>> WARN [agent.manager.AgentManagerImpl] (ClusteredAgentManager > Timer:) > > > >>> Unable to load the resource: 1 > > > >>> WARN [cloud.resource.DiscovererBase] (ClusteredAgentManager > Timer:) > > > >> Unable > > > >>> to configure resource due to Can not create slave connection to > > > >>> 192.168.56.10 > > > >>> WARN [agent.manager.AgentManagerImpl] (ClusteredAgentManager > Timer:) > > > >>> Unable to load the resource: 1 > > > >>> WARN [storage.download.DownloadMonitorImpl] > (23179452@qtp-3363479-0 > > :) > > > >>> There is no secondary storage VM for secondary storage host > > > >>> nfs://192.168.56.10:/opt/storage/secondary > > > >>> > > > >>> See my previous email regarding what the script ssvm-check.sh > report > > > >> please > > > >>> > > > >>> Regards, > > > >>> > > > >>> Charles > > > >>> > > > >>> > > > >>> > > > >>> On Fri, Nov 30, 2012 at 6:32 PM, Charles Moulliard < > ch0...@gmail.com > > > > > > >> wrote: > > > >>> > > > >>>> Can we change the ports number accepted by CloudStack as only 80 & > > 443 > > > >> are > > > >>>> allowed to upload an ISO image ? > > > >>>> > > > >>>> > > > >>>> On Fri, Nov 30, 2012 at 6:07 PM, Charles Moulliard < > > ch0...@gmail.com > > > >>> wrote: > > > >>>> > > > >>>>> On 30/11/12 17:27, Rohit Yadav wrote: > > > >>>>> > > > >>>>>> management.network.cidr is 192.168.56.0/24 > > > >>>>>> secstorage.allowed.internal.**sites is 192.168.56.0/8 > > > >>>>>> > > > >>>>> Rohit, > > > >>>>> > > > >>>>> As I use same config as you, the following values are the same : > > > >>>>> > > > >>>>> > > > >>>>> management.network.cidr is 192.168.56.0/24 > > > >>>>> secstorage.allowed.internal.**sites is 192.168.56.0/8 > > > >>>>> > > > >>>>> It seems that Debian Wheezy already provide a HTTP Server. Do you > > > know > > > >>>>> which server has been installed (does not seems to be Apache2 by > > > >> default) > > > >>>>> and where is the root directory (to copy an image) ? > > > >>>>> > > > >>>>> Regards, > > > >>>>> > > > >>>>> Charles > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>> > > > >>>> > > > >>>> -- > > > >>>> Charles Moulliard > > > >>>> Apache Committer / Sr. Enterprise Architect (RedHat) > > > >>>> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com > > > >>>> > > > >>>> > > > >>>> > > > >>> > > > >>> > > > >>> -- > > > >>> Charles Moulliard > > > >>> Apache Committer / Sr. Enterprise Architect (RedHat) > > > >>> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com > > > >> > > > >> > > > > > > > > > > > > -- > > > > Charles Moulliard > > > > Apache Committer / Sr. Enterprise Architect (RedHat) > > > > Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com > > > > > > > > > > > > -- > > Charles Moulliard > > Apache Committer / Sr. Enterprise Architect (RedHat) > > Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com > > > > > > -- > Charles Moulliard > Apache Committer / Sr. Enterprise Architect (RedHat) > Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com > -- Charles Moulliard Apache Committer / Sr. Enterprise Architect (RedHat) Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
