Re: The Simplest way to Run CloudStack on VirtualBox

[Asanka sanjaya Herath]

Hi Imesh,

For ssh key pairs follow this[1].

[1].
https://portal.redbridge.se/faq/instances/how-do-i-create-an-instance-with-public-key-based-authentication-enabled/

On Tue, Nov 18, 2014 at 11:19 PM, Asanka sanjaya Herath 
wrote:

> ​Hi imesh,
>
> Did you configure   Egress, Ingress rules for the network?​
>
> On Tue, Nov 18, 2014 at 6:53 PM, Geoff Higginbottom <
> geoff.higginbot...@shapeblue.com> wrote:
>
>> An alternative to using DevCloud is to follow this article and deploy
>> CloudStack on VirtualBox using a XenServer Hypervisor
>>
>> http://shapeblue.com/cloudstack/virtualbox-test-env/
>>
>> It’s a configuration which is very close to a Production setup so perfect
>> for test and demo etc
>>
>> Regards
>>
>> Geoff Higginbottom
>>
>> D: +44 20 3603 0542 | S: +44 20 3603 0540> +442036030540> | M: +447968161581
>>
>> geoff.higginbot...@shapeblue.com<mailto:geoff.higginbot...@shapeblue.com>
>>
>> From: Imesh Gunaratne [mailto:im...@apache.org]
>> Sent: 18 November 2014 03:10
>> To: users@cloudstack.apache.org
>> Subject: Re: The Simplest way to Run CloudStack on VirtualBox
>>
>> Hi Ian,
>>
>> I just tried to create an instance with Tiny compute offering and Tiny
>> disk offering and it worked. However I could not ssh into the instance. May
>> be ssh was not configured when I imported the Ubuntu 12.04 ISO into
>> CloudStack.
>>
>> I have few concerns, under System Capacity I can see the following:
>>
>> [cid:ii_i2mogb810_149c0db7491981cd]
>>
>> However I cannot spawn an instance from compute offerings Small or
>> Medium, I get the error mentioned in the previous mail.
>>
>> One other quick question: how can we assign a ssh key pair and a public
>> IP address when spawning an instance?​
>>
>> Many Thanks
>>
>> On Tue, Nov 18, 2014 at 7:40 AM, Imesh Gunaratne > <mailto:im...@apache.org>> wrote:
>> Hi Ian,
>>
>> I thought the above error was raised because of limited resources
>> allocated for the XenServer so I increased those by Memory 5 GB and CPUs 8.
>> But I still get the same error:
>>
>> Following is the error I noticed in
>> /var/log/cloudstack/management/management-server.log file:
>>
>> 014-11-18 01:59:14,350 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
>> (Job-Executor-22:ctx-c91238ea ctx-b4c8800f FirstFitRoutingAllocator) Host
>> Allocator returning 0 suitable hosts
>> 2014-11-18 01:59:14,350 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
>> (Job-Executor-22:ctx-c91238ea ctx-b4c8800f) No suitable hosts found
>> 2014-11-18 01:59:14,350 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
>> (Job-Executor-22:ctx-c91238ea ctx-b4c8800f) No suitable hosts found under
>> this Cluster: 1
>> 2014-11-18 01:59:14,352 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
>> (Job-Executor-22:ctx-c91238ea ctx-b4c8800f) Could not find suitable
>> Deployment Destination for this VM under any clusters, returning.
>> 2014-11-18 01:59:14,354 DEBUG [c.c.d.FirstFitPlanner]
>> (Job-Executor-22:ctx-c91238ea ctx-b4c8800f) Searching all possible
>> resources under this Zone: 1
>> 2014-11-18 01:59:14,356 DEBUG [c.c.d.FirstFitPlanner]
>> (Job-Executor-22:ctx-c91238ea ctx-b4c8800f) Listing clusters in order of
>> aggregate capacity, that have (atleast one host with) enough CPU and RAM
>> capacity under this Zone: 1
>> 2014-11-18 01:59:14,361 DEBUG [c.c.d.FirstFitPlanner]
>> (Job-Executor-22:ctx-c91238ea ctx-b4c8800f) Removing from the clusterId
>> list these clusters from avoid set: [1]
>> 2014-11-18 01:59:14,371 DEBUG [c.c.d.FirstFitPlanner]
>> (Job-Executor-22:ctx-c91238ea ctx-b4c8800f) No clusters found after
>> removing disabled clusters and clusters in avoid list, returning.
>> 2014-11-18 01:59:14,376 DEBUG [c.c.v.UserVmManagerImpl]
>> (Job-Executor-22:ctx-c91238ea ctx-b4c8800f) Destroying vm
>> VM[User|VM-f8680a86-1976-435a-94e3-cd8758644940] as it failed to create on
>> Host with Id:null
>> 2014-11-18 01:59:14,396 DEBUG [c.c.c.CapacityManagerImpl]
>> (Job-Executor-22:ctx-c91238ea ctx-b4c8800f) VM state transitted from
>> :Stopped to Error with event: OperationFailedToErrorvm's original host id:
>> null new host id: null host id before state transition: null
>> 2014-11-18 01:59:14,422 WARN  [o.a.c.alerts]
>> (Job-Executor-22:ctx-c91238ea ctx-b4c8800f)  alertType:: 8 //
>> dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to
>> deploy Vm with Id: 7, on Host with Id: null
>> 2014-11-18 01:59:14,461 INFO  [o.a.c.a.c.u.v.DeployVMCmd]
>> (Job

Re: The Simplest way to Run CloudStack on VirtualBox

[Asanka sanjaya Herath]

dc.DataCenter; id=1
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:210)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:196)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3549)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3157)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3143)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at com.sun.proxy.$Proxy169.startVirtualMachine(Unknown Source)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:443)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
> at
> com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
> at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:509)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> 2014-11-18 01:59:14,475 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-22:ctx-c91238ea) Complete async job-25, jobStatus: FAILED,
> resultCode: 530, result:
> org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":533,"errortext":"Unable
> to create a deployment for
> VM[User|VM-f8680a86-1976-435a-94e3-cd8758644940]"}
> 2014-11-18 01:59:14,498 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-22:ctx-c91238ea) Done executing
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd for job-25
> 2014-11-18 01:59:14,508 INFO  [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-22:ctx-c91238ea) Remove job-25 from job monitoring
>
> Asanka: I tried your suggestion but didn't work.
>
> Many Thanks
>
> On Mon, Nov 17, 2014 at 10:26 AM, Asanka sanjaya Herath <
> angal...@gmail.com<mailto:angal...@gmail.com>> wrote:
> Hi Imesh,
>
> I also had the same issue. I assume that you got insufficient server
> capacity exception. If so Go to mysql database and navigate to vm_template
> table. If the hvm flag for your ISO has been set as 1, change it to 0. Then
> try to create an instance again.
>
> Thank you.
&

Re: The Simplest way to Run CloudStack on VirtualBox

[Asanka sanjaya Herath]

Will let you know the status soon.
> > Appreciate
> > >> > it.
> > >> > >> > > > >
> > >> > >> > > > > Many Thanks
> > >> > >> > > > >
> > >> > >> > > > > On Sun, Nov 16, 2014 at 6:35 AM, Thomas Munn <
> > >> > symgr...@gmail.com>
> > >> > >> > > wrote:
> > >> > >> > > > >
> > >> > >> > > > >> What is the URL for the new branch?
> > >> > >> > > > >>
> > >> > >> > > > >> Sent from my iPad
> > >> > >> > > > >>
> > >> > >> > > > >> > On Nov 15, 2014, at 17:44, Ian Duffy  >
> > >> > wrote:
> > >> > >> > > > >> >
> > >> > >> > > > >> > That almost looks like a vagrant-omnibus book
> > 11.16.0
> > >> is
> > >> > a
> > >> > >> > valid
> > >> > >> > > > >> > version.
> > >> > >> > > > >> >
> > >> > >> > > > >> > Anyways, I've changed it to use :latest.
> > >> > >> > > > >> >
> > >> > >> > > > >> > Can you do a git pull again? Should hopefully fix it.
> > >> > >> > > > >> >
> > >> > >> > > > >> > My testing just finished, It worked successfully with
> > the
> > >> > >> earlier
> > >> > >> > > > >> changes.
> > >> > >> > > > >> >
> > >> > >> > > > >> >> On 15 November 2014 22:08, Imesh Gunaratne <
> > >> > im...@apache.org>
> > >> > >> > > wrote:
> > >> > >> > > > >> >>
> > >> > >> > > > >> >> Hi Ian,
> > >> > >> > > > >> >>
> > >> > >> > > > >> >> I got your fix and did another test, I see the below
> > >> error
> > >> > >> with
> > >> > >> > the
> > >> > >> > > > >> latest
> > >> > >> > > > >> >> changes:
> > >> > >> > > > >> >>
> > >> > >> > > > >> >> ==> management: Machine booted and ready!
> > >> > >> > > > >> >> ==> management: Checking for guest additions in VM...
> > >> > >> > > > >> >> ==> management: Configuring and enabling network
> > >> > interfaces...
> > >> > >> > > > >> >> ==> management: Mounting shared folders...
> > >> > >> > > > >> >>management: /vagrant =>
> > >> > >> > > > >> >>
> > >> > >> > > > >> >>
> > >> > >> > > > >>
> > >> > >> > > >
> > >> > >> > >
> > >> > >> >
> > >> > >>
> > >> >
> > >>
> >
> /Users/imesh/sandboxes/apache/cloudstack/vagrant/devcloud4/binary-installation-advanced
> > >> > >> > > > >> >>management:
> > /tmp/vagrant-chef-2/chef-solo-1/cookbooks
> > >> =>
> > >> > >> > > > >> >>
> > >> > >> > > > >> >>
> > >> > >> > > > >>
> > >> > >> > > >
> > >> > >> > >
> > >> > >> >
> > >> > >>
> > >> >
> > >>
> >
> /Users/imesh/sandboxes/apache/cloudstack/vagrant/devcloud4/common/management/cookbooks
> > >> > >> > > > >> >> There are errors in the configuration of this
> machine.
> > >> > Please
> > >> > >> fix
> > >> > >> > > > >> >> the following errors and try again:
> > >> > >> > > > >> >>
> > >> > >> > > > >>

Re: The Simplest way to Run CloudStack on VirtualBox

[Asanka sanjaya Herath]

Hi Imesh,

If the management server is up, I think you don't need to run 'vagrant up'
command again. So try follow these steps.

1. Find the Marvin-0.1.0.tar.gz from a locally build repository of
cloudstack.
2. Run this command. "pip install Marvin-0.1.0.tar.gz"
3. Change IPs in advanced/advanced.json file according to vbox
adapters(22-24).
4. Run this command. python -m marvin.deployDataCenter -i
advanced/advanced.json



On Sun, Nov 16, 2014 at 1:06 AM, Imesh Gunaratne  wrote:

> Hi Ian,
>
> Great! Thanks! Your suggestion worked, the advance binary installation went
> much far afterwards. Now I can see the below error, seems like the marvin
> tar is not there at the below link:
>
> http://ianduffy.ie/Marvin-0.1.0.tar.gz
>
> ==> management: [2014-11-15T19:26:55+00:00] INFO:
> template[/etc/sysconfig/nfs] sending restart action to service[nfs]
> (delayed)
> ==> management: [2014-11-15T19:26:59+00:00] INFO: service[nfs] restarted
> ==> management: [2014-11-15T19:26:59+00:00] INFO: template[/etc/exports]
> sending run action to execute[exportfs] (delayed)
> ==> management: [2014-11-15T19:26:59+00:00] INFO: execute[exportfs] ran
> successfully
> ==> management: [2014-11-15T19:26:59+00:00] ERROR: Running exception
> handlers
> ==> management: [2014-11-15T19:26:59+00:00] ERROR: Exception handlers
> complete
> ==> management: [2014-11-15T19:26:59+00:00] FATAL: Stacktrace dumped to
> /var/chef/cache/chef-stacktrace.out
> ==> management: [2014-11-15T19:26:59+00:00] ERROR: bash[Install Cloudstack
> Marvin] (cloudstack::management-server line 67) had an error:
> Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0],
> but received '2'
> ==> management:  Begin output of "bash"
>  "/tmp/chef-script20141115-3008-8jnekm" 
> ==> management: STDOUT: Downloading/unpacking
> http://ianduffy.ie/Marvin-0.1.0.tar.gz
> ==> management:   HTTP error 404 while getting
> http://ianduffy.ie/Marvin-0.1.0.tar.gz
> ==> management: Cleaning up...
>
> While seeing this error I tried to access the CloudStack console (
> http://localhost:8080/client) and it seems to be working. Do you think I
> can ignore the above error and use CloudStack or will I need to fix it and
> re-install?
>
> Really appreciate your help.
>
> Many Thanks
>
> On Sun, Nov 16, 2014 at 12:29 AM, Ian Duffy  wrote:
>
> > Hi Imesh,
> >
> > Yes use 192.168.22.1 - 192.168.24.1. Sorry I meant to add a /24 prefix in
> > on my original email.
> >
> > On 15 November 2014 18:16, Imesh Gunaratne  wrote:
> >
> > > Hi Ian,
> > >
> > > Thanks again for the quick feedback. Yes it was my fault, I have used
> > some
> > > other IPv4 addresses in hostonly vboxnet adapters. I just started
> another
> > > test with the ones you have mentioned.
> > >
> > > Just to clarify, the README file in the devcloud4 says to set these
> > values
> > > to 192.168.22.1 - 192.168.24.1. Would there be any difference?
> > >
> > > Thanks
> > >
> > > On Sat, Nov 15, 2014 at 3:59 PM, Ian Duffy  wrote:
> > >
> > > > Hi Imesh,
> > > >
> > > > That almost looks like a possible issue with the vboxnet adapters.
> > > > Can you confirm you have 3 host only adapters assigned 192.168.22.0 -
> > > > 192.168.24.0 with dhcp disabled on each?
> > > > On 15 Nov 2014 02:19, "Imesh Gunaratne"  wrote:
> > > >
> > > > > Hi Ian,
> > > > >
> > > > > Thanks for your quick response. This is the issue I encountered
> when
> > I
> > > > > executed devcloud4 (binary-installation-advanced):
> > > > >
> > > > > ==> management: [2014-11-15T02:09:23+00:00] INFO: Running queued
> > > delayed
> > > > > notifications before re-raising exception
> > > > > ==> management: [2014-11-15T02:09:23+00:00] ERROR: Running
> exception
> > > > > handlers
> > > > > ==> management: [2014-11-15T02:09:23+00:00] ERROR: Exception
> handlers
> > > > > complete
> > > > > ==> management: [2014-11-15T02:09:23+00:00] FATAL: Stacktrace
> dumped
> > to
> > > > > /var/chef/cache/chef-stacktrace.out
> > > > > ==> management: [2014-11-15T02:09:23+00:00] ERROR:
> > > > > package[cloudstack-management] (cloudstack::management-server line
> > 22)
> > > > had
> > > > > an error: Timeout::Error: execution expired
> > > > > ==> management: [2014-11-15T02:09:23+00:00] FATAL:
> > > > > Chef::Exceptions::ChildConvergeError: Chef run process exited
> > > > > unsuccessfully (exit code 1)
> > > > > Chef never successfully completed! Any errors should be visible in
> > the
> > > > > output above. Please fix your recipes so that they properly
> complete.
> > > > >
> > > > > My host machine runs Yosemite (OSX 10.10), Vagrant 1.6.5,
> VirtualBox
> > > > > 4.3.16. I have also attached the chef stacktrace file with this
> mail.
> > > > >
> > > > > Really appreciate your help.
> > > > >
> > > > > Many Thanks
> > > > >
> > > > > On Fri, Nov 14, 2014 at 4:33 PM, Ian Duffy 
> wrote:
> > > > >
> > > > >> Hi,
> > > > >>
> > > > >> I can help you get devcloud up. What issues did you have?
> > > > >> On 14 Nov 2014 04:40, "Imesh Gunaratne"  wrote:
> > > > >>
> > > >

Cannot ping instances in advanced zone

[Asanka sanjaya Herath]

I installed cloustack in local machine using Virtualbox and Vagrant.
​I used advanced networking in order to enable public traffic to instances.
These are my configurations:

Guest Network:

Gateway: 10.1.1.1
Type: Isolated
port forwarding: public port : 80 , private Port 80

Virtual router:

public IP: 192.168.57.102 - I can ping to this IP
Guest IP: 10.1.1.1
Link local IP: 169.254.1.237

Instance:

IP:10.1.1.82
Gateway:10.1.1.1


I cannot ping to instance IP(10.1.1.82) , or even to Gateway(10.1.1.1) from
the host computer. Any ideas?


​

-- 
Thanks,
Regards,
ASH

Re: Can't add templates in cloudstack with advanced networking - No route to host

[Asanka sanjaya Herath]

Thanks john. I'll get back to you with test results.

On Fri, Oct 24, 2014 at 7:49 AM, John Pletka  wrote:

> I had the same issue that took forever to resolve.  In the end it came down
> to
> 1) Making sure your networks are labeled correctly on the compute hosts.
> (XenServer for me.  run "xe list-networks" and make sure the correct xenbr0
> or xenbr1 is named "cloud-public" or "cloud-private").  If they are not
> labeled, there is an xe command to assign a label to them
> 2) In the management console go to Infrastructure / Zones /
> PhysicalNetworksInBasicZone.  For the three listed (public, management,
> storage), make sure you set the gateway to be "cloud-public" or
> "cloud-private" as applicable
> 3) Destroy your two System VMs (secondary storage and console) and let them
> recreate themselves
> 4) Log into the secondary storage using the instructions from
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM,+templates,+Secondary+storage+troubleshooting
> 5) Run the health check (/usr/local/cloud/systemvm/ssvm-check.sh)
> 6) If it fails ...
>  a) Run ifconfig and do a sanity check of the IP addresses
>  b) Run "route -n" and do a sanity check of the routes
>
> On Thu, Oct 23, 2014 at 2:32 AM, Asanka sanjaya Herath  >
> wrote:
>
> > I used advanced  networking feature and installed cloudstack in my local
> > computer using vagrant and virtulbox. This is my configuration[1].
> > The default tiny linux template has been downloaded and I can add
> instances
> > successfully using that template. When I register  a new template(using a
> > web url) it says "No route to host". But by using basic networking
> feature
> > I'm able to add new templates without having any issue. Could anyone
> please
> > help me with this?
> >
> > [1] http://pastebin.com/dVSUJ708
> >
> >
> >
> >
> > --
> > Thanks,
> > Regards,
> > ASH
> >
>



-- 
Thanks,
Regards,
ASH

Can't add templates in cloudstack with advanced networking - No route to host

[Asanka sanjaya Herath]

I used advanced  networking feature and installed cloudstack in my local
computer using vagrant and virtulbox. This is my configuration[1].
The default tiny linux template has been downloaded and I can add instances
successfully using that template. When I register  a new template(using a
web url) it says "No route to host". But by using basic networking feature
I'm able to add new templates without having any issue. Could anyone please
help me with this?

[1] http://pastebin.com/dVSUJ708




-- 
Thanks,
Regards,
ASH

Re: Increase root disk size in latest cloudstack

[Asanka sanjaya Herath]

Hi Erik,

Seems like its the only way to do that. So I created a another data-disk
and attached it to the VM. But still the df command shows me same
information.



On Tue, Oct 21, 2014 at 12:45 PM, Erik Weber  wrote:

> If you're using some sort of logical volume manager inside the vm you can
> add an additional disk and resize it.
> For Linux the most common is LVM, for Windows I believe you have to use
> dynamic disks (not sure about support for booting from dynamic disks?).
>
> --
> Erik
>
> On Tue, Oct 21, 2014 at 9:12 AM, Asanka sanjaya Herath  >
> wrote:
>
> > Hi Erik,
> >
> > I'm using xenserver. So I think I will not be able to do that. One of my
> > instance is running out of root disk capacity. I took a snapshot of that
> > disk and created a template from it. Then I crated a new instance and
> still
> > it has the same disk capacity. What can I do now?
> >
> >
> >
> > On Tue, Oct 21, 2014 at 12:25 PM, Erik Weber 
> wrote:
> >
> > > The design spec is here:
> > >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Root+Resize+Support
> > >
> > > You can find the Jira ticket with a lot of information here:
> > > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
> > >
> > > As far as I can see, you can atleast resize the disk by using the API.
> UI
> > > tends to lag a bit behind new API functionality, so I would hope for it
> > to
> > > arrive in a later version.
> > >
> > > But, after reading through the ticket it seems that root disk resize
> > might
> > > only be supported on KVM, which hypervisor are you using?
> > >
> > > --
> > > Erik
> > >
> > >
> > > On Tue, Oct 21, 2014 at 8:31 AM, Asanka sanjaya Herath <
> > angal...@gmail.com
> > > >
> > > wrote:
> > >
> > > > Hi Erik,
> > > > I'm using the master branch. Could you please tell me how can I do
> > that?
> > > >
> > > > Thank you.
> > > >
> > > > On Tue, Oct 21, 2014 at 11:59 AM, Erik Weber 
> > > wrote:
> > > >
> > > > > On Tue, Oct 21, 2014 at 7:54 AM, Asanka sanjaya Herath <
> > > > angal...@gmail.com
> > > > > >
> > > > > wrote:
> > > > >
> > > > > > I'm using the latest cloudstack(Cloned from github and built from
> > > > > source).
> > > > > > I need to know whether there is any way to re-size the root disk
> > > > capacity
> > > > > > after creating the instance.(Using UI or using api).
> > > > > >
> > > > > >
> > > > > Which branch did you build?
> > > > >
> > > > > I believe root disk resizing has been there since 4.4, but it might
> > be
> > > > > lacking if you're using managed storage.
> > > > >
> > > > > Mike can probably chime in on the latter
> > > > >
> > > > > --
> > > > > Erik
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Thanks,
> > > > Regards,
> > > > ASH
> > > >
> > >
> >
> >
> >
> > --
> > Thanks,
> > Regards,
> > ASH
> >
>



-- 
Thanks,
Regards,
ASH

Re: Increase root disk size in latest cloudstack

[Asanka sanjaya Herath]

Hi Erik,

I'm using xenserver. So I think I will not be able to do that. One of my
instance is running out of root disk capacity. I took a snapshot of that
disk and created a template from it. Then I crated a new instance and still
it has the same disk capacity. What can I do now?



On Tue, Oct 21, 2014 at 12:25 PM, Erik Weber  wrote:

> The design spec is here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Root+Resize+Support
>
> You can find the Jira ticket with a lot of information here:
> https://issues.apache.org/jira/browse/CLOUDSTACK-6181
>
> As far as I can see, you can atleast resize the disk by using the API. UI
> tends to lag a bit behind new API functionality, so I would hope for it to
> arrive in a later version.
>
> But, after reading through the ticket it seems that root disk resize might
> only be supported on KVM, which hypervisor are you using?
>
> --
> Erik
>
>
> On Tue, Oct 21, 2014 at 8:31 AM, Asanka sanjaya Herath  >
> wrote:
>
> > Hi Erik,
> > I'm using the master branch. Could you please tell me how can I do that?
> >
> > Thank you.
> >
> > On Tue, Oct 21, 2014 at 11:59 AM, Erik Weber 
> wrote:
> >
> > > On Tue, Oct 21, 2014 at 7:54 AM, Asanka sanjaya Herath <
> > angal...@gmail.com
> > > >
> > > wrote:
> > >
> > > > I'm using the latest cloudstack(Cloned from github and built from
> > > source).
> > > > I need to know whether there is any way to re-size the root disk
> > capacity
> > > > after creating the instance.(Using UI or using api).
> > > >
> > > >
> > > Which branch did you build?
> > >
> > > I believe root disk resizing has been there since 4.4, but it might be
> > > lacking if you're using managed storage.
> > >
> > > Mike can probably chime in on the latter
> > >
> > > --
> > > Erik
> > >
> >
> >
> >
> > --
> > Thanks,
> > Regards,
> > ASH
> >
>



-- 
Thanks,
Regards,
ASH

Re: Increase root disk size in latest cloudstack

[Asanka sanjaya Herath]

Hi Erik,
I'm using the master branch. Could you please tell me how can I do that?

Thank you.

On Tue, Oct 21, 2014 at 11:59 AM, Erik Weber  wrote:

> On Tue, Oct 21, 2014 at 7:54 AM, Asanka sanjaya Herath  >
> wrote:
>
> > I'm using the latest cloudstack(Cloned from github and built from
> source).
> > I need to know whether there is any way to re-size the root disk capacity
> > after creating the instance.(Using UI or using api).
> >
> >
> Which branch did you build?
>
> I believe root disk resizing has been there since 4.4, but it might be
> lacking if you're using managed storage.
>
> Mike can probably chime in on the latter
>
> --
> Erik
>



-- 
Thanks,
Regards,
ASH

Increase root disk size in latest cloudstack

[Asanka sanjaya Herath]

I'm using the latest cloudstack(Cloned from github and built from source).
I need to know whether there is any way to re-size the root disk capacity
after creating the instance.(Using UI or using api).

-- 
Thanks,
Regards,
ASH

Re: Unable to add instances in cloudstack

[Asanka sanjaya Herath]

Hi Nitin,

Thank you so much. Problem solved.

On Thu, Oct 16, 2014 at 11:19 PM, Nitin Mehta 
wrote:

> Asanka - I would not know the location for the right one but I am using
> 4.4 systemvm templates and probably you can use that one to get you going.
>
> Thanks,
> -Nitin
> On 15/10/14 7:47 PM, "Asanka sanjaya Herath"  wrote:
>
> >Hi nitin,
> >
> >Currently I'm using this[1] system vm template. Are there any alternative
> >url which I can use?
> >
> >[1] -
> >
> http://jenkins.buildacloud.org/job/build-systemvm-master/lastSuccessfulBui
> >ld/artifact/tools/appliance/dist/systemvmtemplate-master-xen.vhd.bz2
> >
> >
> >On Thu, Oct 16, 2014 at 8:08 AM, Asanka sanjaya Herath
> >
> >wrote:
> >
> >> HI nitin,
> >> Yes, I upgraded the system vm template to the latest version. So which
> >> template can I use? Could you please give me a link?
> >>
> >> On Thu, Oct 16, 2014 at 5:14 AM, Nitin Mehta 
> >> wrote:
> >>
> >>> Did you upgrade your system vm templates ? There is an issue in the
> >>>latest
> >>> ones where the template version is not in the correct format and is
> >>> resulting in that.
> >>>
> >>> On 15/10/14 6:08 AM, "Asanka sanjaya Herath" 
> >>>wrote:
> >>>
> >>> >I'm getting this error when I'm going to start instances in
> >>>cloudstack. I
> >>> >was able to add instances without having any issue till today. But I
> >>> >suddenly got this error today. Any ideas?
> >>> >
> >>> >INFO  [c.c.s.StorageManagerImpl] (Work-Job-Executor-6:ctx-c9612ed8
> >>> >job-55/job-56 ctx-6055652d) Storage pool null (1) does not supply IOPS
> >>> >capacity, assuming enough capacity
> >>> >ERROR [c.c.v.VirtualMachineManagerImpl]
> >>>(Work-Job-Executor-6:ctx-c9612ed8
> >>> >job-55/job-56 ctx-6055652d) Failed to start instance VM[User|i-2-8-VM]
> >>> >java.lang.NumberFormatException: For input string: "Wed"
> >>> >at
> >>>
> >>>
> >>>>java.lang.NumberFormatException.forInputString(NumberFormatException.ja
> >>>>va:
> >>> >65)
> >>> >at java.lang.Long.parseLong(Long.java:441)
> >>> >at java.lang.Long.parseLong(Long.java:483)
> >>> >at com.cloud.maint.Version.compare(Version.java:36)
> >>> >at
> >>>
> >>>
> >>>>com.cloud.network.router.VirtualNetworkApplianceManagerImpl.checkRouter
> >>>>Ver
> >>> >sion(VirtualNetworkApplianceManagerImpl.java:4385)
> >>> >at
> >>>
> >>>
> >>>>com.cloud.network.router.VirtualNetworkApplianceManagerImpl.sendCommand
> >>>>sTo
> >>> >Router(VirtualNetworkApplianceManagerImpl.java:3747)
> >>> >at
> >>>
> >>>
> >>>>com.cloud.network.router.VirtualNetworkApplianceManagerImpl$7.execute(V
> >>>>irt
> >>> >ualNetworkApplianceManagerImpl.java:3172)
> >>> >at
> >>>
> >>>
> >>>>com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(
> >>>>Vir
> >>> >tualNetworkApplianceManagerImpl.java:4033)
> >>> >at
> >>>
> >>>
> >>>>com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEn
> >>>>try
> >>> >(VirtualNetworkApplianceManagerImpl.java:3164)
> >>> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>> >at
> >>>
> >>>
> >>>>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja
> >>>>va:
> >>> >57)
> >>> >at
> >>>
> >>>
> >>>>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso
> >>>>rIm
> >>> >pl.java:43)
> >>> >at java.lang.reflect.Method.invoke(Method.java:606)
> >>> >at
> >>>
> >>>
> >>>>org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection
> >>>>(Ao
> >>> >pUtils.java:317)
> >>> >at
> >>>
> >>>
> >>>>org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoin
> >>>>poi
> >>> >nt(Refle

Re: Unable to add instances in cloudstack

[Asanka sanjaya Herath]

Hi nitin,

Currently I'm using this[1] system vm template. Are there any alternative
url which I can use?

[1] -
http://jenkins.buildacloud.org/job/build-systemvm-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvmtemplate-master-xen.vhd.bz2


On Thu, Oct 16, 2014 at 8:08 AM, Asanka sanjaya Herath 
wrote:

> HI nitin,
> Yes, I upgraded the system vm template to the latest version. So which
> template can I use? Could you please give me a link?
>
> On Thu, Oct 16, 2014 at 5:14 AM, Nitin Mehta 
> wrote:
>
>> Did you upgrade your system vm templates ? There is an issue in the latest
>> ones where the template version is not in the correct format and is
>> resulting in that.
>>
>> On 15/10/14 6:08 AM, "Asanka sanjaya Herath"  wrote:
>>
>> >I'm getting this error when I'm going to start instances in cloudstack. I
>> >was able to add instances without having any issue till today. But I
>> >suddenly got this error today. Any ideas?
>> >
>> >INFO  [c.c.s.StorageManagerImpl] (Work-Job-Executor-6:ctx-c9612ed8
>> >job-55/job-56 ctx-6055652d) Storage pool null (1) does not supply IOPS
>> >capacity, assuming enough capacity
>> >ERROR [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-6:ctx-c9612ed8
>> >job-55/job-56 ctx-6055652d) Failed to start instance VM[User|i-2-8-VM]
>> >java.lang.NumberFormatException: For input string: "Wed"
>> >at
>>
>> >java.lang.NumberFormatException.forInputString(NumberFormatException.java:
>> >65)
>> >at java.lang.Long.parseLong(Long.java:441)
>> >at java.lang.Long.parseLong(Long.java:483)
>> >at com.cloud.maint.Version.compare(Version.java:36)
>> >at
>>
>> >com.cloud.network.router.VirtualNetworkApplianceManagerImpl.checkRouterVer
>> >sion(VirtualNetworkApplianceManagerImpl.java:4385)
>> >at
>>
>> >com.cloud.network.router.VirtualNetworkApplianceManagerImpl.sendCommandsTo
>> >Router(VirtualNetworkApplianceManagerImpl.java:3747)
>> >at
>>
>> >com.cloud.network.router.VirtualNetworkApplianceManagerImpl$7.execute(Virt
>> >ualNetworkApplianceManagerImpl.java:3172)
>> >at
>>
>> >com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(Vir
>> >tualNetworkApplianceManagerImpl.java:4033)
>> >at
>>
>> >com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEntry
>> >(VirtualNetworkApplianceManagerImpl.java:3164)
>> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >at
>>
>> >sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
>> >57)
>> >at
>>
>> >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
>> >pl.java:43)
>> >at java.lang.reflect.Method.invoke(Method.java:606)
>> >at
>>
>> >org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(Ao
>> >pUtils.java:317)
>> >at
>>
>> >org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoi
>> >nt(ReflectiveMethodInvocation.java:183)
>> >at
>>
>> >org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(Refle
>> >ctiveMethodInvocation.java:150)
>> >at
>>
>> >org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(Exp
>> >oseInvocationInterceptor.java:91)
>> >at
>>
>> >org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(Refle
>> >ctiveMethodInvocation.java:172)
>> >at
>>
>> >org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopP
>> >roxy.java:204)
>> >at com.sun.proxy.$Proxy198.applyDhcpEntry(Unknown Source)
>> >at
>>
>> >com.cloud.network.element.VirtualRouterElement.addDhcpEntry(VirtualRouterE
>> >lement.java:924)
>> >at
>>
>> >org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareElem
>> >ent(NetworkOrchestrator.java:1251)
>> >at
>>
>> >org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareNic(
>> >NetworkOrchestrator.java:1373)
>> >at
>>
>> >org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(Net
>> >workOrchestrator.java:1309)
>> >at
>>
>> >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineMana
>> >gerImpl.java:972)
>> >at
>>
>> >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineMana
&

Re: Unable to add instances in cloudstack

[Asanka sanjaya Herath]

HI nitin,
Yes, I upgraded the system vm template to the latest version. So which
template can I use? Could you please give me a link?

On Thu, Oct 16, 2014 at 5:14 AM, Nitin Mehta  wrote:

> Did you upgrade your system vm templates ? There is an issue in the latest
> ones where the template version is not in the correct format and is
> resulting in that.
>
> On 15/10/14 6:08 AM, "Asanka sanjaya Herath"  wrote:
>
> >I'm getting this error when I'm going to start instances in cloudstack. I
> >was able to add instances without having any issue till today. But I
> >suddenly got this error today. Any ideas?
> >
> >INFO  [c.c.s.StorageManagerImpl] (Work-Job-Executor-6:ctx-c9612ed8
> >job-55/job-56 ctx-6055652d) Storage pool null (1) does not supply IOPS
> >capacity, assuming enough capacity
> >ERROR [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-6:ctx-c9612ed8
> >job-55/job-56 ctx-6055652d) Failed to start instance VM[User|i-2-8-VM]
> >java.lang.NumberFormatException: For input string: "Wed"
> >at
> >java.lang.NumberFormatException.forInputString(NumberFormatException.java:
> >65)
> >at java.lang.Long.parseLong(Long.java:441)
> >at java.lang.Long.parseLong(Long.java:483)
> >at com.cloud.maint.Version.compare(Version.java:36)
> >at
> >com.cloud.network.router.VirtualNetworkApplianceManagerImpl.checkRouterVer
> >sion(VirtualNetworkApplianceManagerImpl.java:4385)
> >at
> >com.cloud.network.router.VirtualNetworkApplianceManagerImpl.sendCommandsTo
> >Router(VirtualNetworkApplianceManagerImpl.java:3747)
> >at
> >com.cloud.network.router.VirtualNetworkApplianceManagerImpl$7.execute(Virt
> >ualNetworkApplianceManagerImpl.java:3172)
> >at
> >com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(Vir
> >tualNetworkApplianceManagerImpl.java:4033)
> >at
> >com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEntry
> >(VirtualNetworkApplianceManagerImpl.java:3164)
> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >at
> >sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> >57)
> >at
> >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
> >pl.java:43)
> >at java.lang.reflect.Method.invoke(Method.java:606)
> >at
> >org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(Ao
> >pUtils.java:317)
> >at
> >org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoi
> >nt(ReflectiveMethodInvocation.java:183)
> >at
> >org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(Refle
> >ctiveMethodInvocation.java:150)
> >at
> >org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(Exp
> >oseInvocationInterceptor.java:91)
> >at
> >org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(Refle
> >ctiveMethodInvocation.java:172)
> >at
> >org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopP
> >roxy.java:204)
> >at com.sun.proxy.$Proxy198.applyDhcpEntry(Unknown Source)
> >at
> >com.cloud.network.element.VirtualRouterElement.addDhcpEntry(VirtualRouterE
> >lement.java:924)
> >at
> >org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareElem
> >ent(NetworkOrchestrator.java:1251)
> >at
> >org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareNic(
> >NetworkOrchestrator.java:1373)
> >at
> >org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(Net
> >workOrchestrator.java:1309)
> >at
> >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineMana
> >gerImpl.java:972)
> >at
> >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineMana
> >gerImpl.java:4582)
> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >at
> >sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> >57)
> >at
> >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
> >pl.java:43)
> >at java.lang.reflect.Method.invoke(Method.java:606)
> >at
> >com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.j
> >ava:107)
> >at
> >com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManag
> >erImpl.java:4738)
> >at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
> >at
> >org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInConte
> >xt(AsyncJobMan

Unable to add instances in cloudstack

[Asanka sanjaya Herath]

I'm getting this error when I'm going to start instances in cloudstack. I
was able to add instances without having any issue till today. But I
suddenly got this error today. Any ideas?

INFO  [c.c.s.StorageManagerImpl] (Work-Job-Executor-6:ctx-c9612ed8
job-55/job-56 ctx-6055652d) Storage pool null (1) does not supply IOPS
capacity, assuming enough capacity
ERROR [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-6:ctx-c9612ed8
job-55/job-56 ctx-6055652d) Failed to start instance VM[User|i-2-8-VM]
java.lang.NumberFormatException: For input string: "Wed"
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Long.parseLong(Long.java:441)
at java.lang.Long.parseLong(Long.java:483)
at com.cloud.maint.Version.compare(Version.java:36)
at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.checkRouterVersion(VirtualNetworkApplianceManagerImpl.java:4385)
at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.sendCommandsToRouter(VirtualNetworkApplianceManagerImpl.java:3747)
at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl$7.execute(VirtualNetworkApplianceManagerImpl.java:3172)
at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:4033)
at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEntry(VirtualNetworkApplianceManagerImpl.java:3164)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy198.applyDhcpEntry(Unknown Source)
at
com.cloud.network.element.VirtualRouterElement.addDhcpEntry(VirtualRouterElement.java:924)
at
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareElement(NetworkOrchestrator.java:1251)
at
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareNic(NetworkOrchestrator.java:1373)
at
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1309)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:972)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4582)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4738)
at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-6:ctx-c9612ed8
job-55/job-56 ctx-6055652d) Invocation exception, caused by:
com.cloud.exception.AgentUnavailableException: Resource [Host:1] is
unreachable: Host 1: Unable to start instance due to For input string: "Wed"
INFO  [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-6:ctx-c9612ed8
job-55/job-56 ctx-6055652d) Rethrow e

Re: 404 - not found user meta-data error

[Asanka sanjaya Herath]

Hi kirk,

Thank you. Problem solved. I think this user guide should be edited ,
Because this guide doesn't say from where we should run that command.
Thank you again.


On Tue, Oct 14, 2014 at 1:57 AM, Kirk Kosinski 
wrote:

> Hi, are you testing the curl command from the instance?  The user- and
> meta-data can only be accessed by the instance.   I ask because the 404
> is for "/userdata/192.168.56.1/user-data" which suggests you are testing
> from a machine with the IP 192.168.56.1 and not the instance at
> 192.168.56.27.
>
> Best regards,
> Kirk
>
> On 10/13/2014 04:06 AM, Asanka sanjaya Herath wrote:
> > Hi all,
> >
> > I Followed this[1] guide for view user-meta data set for my instance.
> When
> > I'm running the curl command for retrieve the user-meta data, I'm getting
> > this error.
> >
> > $ curl http://192.168.56.22/latest/user-data
> > 
> > 
> > 404 Not Found
> > 
> > Not Found
> > The requested URL /userdata/192.168.56.1/user-data was not found on
> this
> > server.
> > 
> >
> > According to cloudstack UI, I have one virtual router (IP -
> 192.168.56.22).
> > So I used that IP in curl command. My instance's IP is 192.168.56.27. I
> > used jcloud api for set user meta-data
> >
> > Any ideas?
> >
> >
> > ​[1] -
> >
> https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.1-incubating/html/Admin_Guide/user-data-and-meta-data.html
> > ​
> >
> >
>
>


-- 
Thanks,
Regards,
ASH

404 - not found user meta-data error

[Asanka sanjaya Herath]

Hi all,

I Followed this[1] guide for view user-meta data set for my instance. When
I'm running the curl command for retrieve the user-meta data, I'm getting
this error.

$ curl http://192.168.56.22/latest/user-data


404 Not Found

Not Found
The requested URL /userdata/192.168.56.1/user-data was not found on this
server.


According to cloudstack UI, I have one virtual router (IP - 192.168.56.22).
So I used that IP in curl command. My instance's IP is 192.168.56.27. I
used jcloud api for set user meta-data

Any ideas?


​[1] -
https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.1-incubating/html/Admin_Guide/user-data-and-meta-data.html
​


-- 
Thanks,
Regards,
ASH

Re: Using ssh keys for authentication

[Asanka sanjaya Herath]

Hi shanker,

I didn't use any key-gen tool, I just created a file called key-pair.pem
and pasted the key into it. Is that wrong? Should I use a key-gen tool to
generate keys?


On Wed, Oct 1, 2014 at 4:38 PM, Shanker Balan 
wrote:

> Comments inline.
>
> On 30-Sep-2014, at 5:14 pm, Asanka sanjaya Herath  <mailto:angal...@gmail.com>> wrote:
>
> Hi,
>
> I followed this
> http://shankerbalan.net/blog/ssh-keys-on-cloudstack-guest-instances-using-cloud-init/
> and I'm stuck in last part.
>
> When I try to connect to my instance using this command It is asking a
> passphrase.
>
> $ ssh -l root  -i ~/ssh/adminKey/keypair.pem 192.168.56.135
> Enter passphrase for key '/home/sanjaya/ssh/adminKey/keypair.pem':
>
> Any ideas?
>
> It looks to me that you have created your SSH keypair with “passphrases”
> using the ssh-keygen tool. IMHO,
> this is the right way to “Secure” your keys.
>
> You have 2 choices:
>
> 1) Create key pairs with empty passphrases (insecure)
>
> 2) Use “ssh-add” tool to add private key identities to the authentication
> agent (secure)
>
>
> Regards.
> @shankerbalan
>
>
> --
> @shankerbalan
>
> M: +91 98860 60539 | O: +91 (80) 67935867
> shanker.ba...@shapeblue.com<mailto:shanker.ba...@shapeblue.com> |
> www.shapeblue.com<http://www.shapeblue.com> | Twitter:@shapeblue
> ShapeBlue Services India LLP, 22nd floor, Unit 2201A, World Trade Centre,
> Bangalore - 560 055
>
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design & Build<
> http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
> CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
> CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses<
> http://shapeblue.com/cloudstack-training/>
>
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India LLP is a
> company incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
> a company registered by The Republic of South Africa and is traded under
> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>



-- 
Thanks,
Regards,
ASH

Re: Using ssh keys for authentication

[Asanka sanjaya Herath]

Hi,

I followed this
http://shankerbalan.net/blog/ssh-keys-on-cloudstack-guest-instances-using-cloud-init/
and I'm stuck in last part.

When I try to connect to my instance using this command It is asking a
passphrase.

$ ssh -l root  -i ~/ssh/adminKey/keypair.pem 192.168.56.135
Enter passphrase for key '/home/sanjaya/ssh/adminKey/keypair.pem':

Any ideas?

On Fri, Sep 26, 2014 at 8:05 PM, Asanka sanjaya Herath 
wrote:

> Hi lan Duffy,
>
> Thank you for your help. I'll try those things and let know the results.
>
> On Fri, Sep 26, 2014 at 7:46 PM, Ian Duffy  wrote:
>
>> Hi,
>>
>> Please see the init scripts available over at:
>> https://github.com/shankerbalan/cloudstack-scripts
>>
>> Alternatively, you can use cloud-init with cloudstack as a data source:
>>
>> http://shankerbalan.net/blog/cloud-init-supports-cloudstack-as-data-source/
>>
>> Normally one would bake these into their template.
>>
>> Once you have your template created you can bring up a new instance with
>> an
>> ssh key assigned and login using it:
>>
>> http://shankerbalan.net/blog/ssh-keys-on-cloudstack-guest-instances-using-cloud-init/
>>
>> On 26 September 2014 07:06, Asanka sanjaya Herath 
>> wrote:
>>
>> > ​I followed this guide in order to use ssh keys for authentication in
>> > cloudstack.
>> >
>> >
>> >
>> https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Installation_Guide/using-sshkeys.html
>> >
>> >
>> > According to this document we need to create an instance and download a
>> > script to it  (section 5.2.1) . My problem is should I create another
>> > template from the instance which created in section 5.2.1?​
>> > Because in section 5.2.3, it says us to give the template ID in order to
>> > create a new instance.
>> >
>> > --
>> > Thanks,
>> > Regards,
>> > ASH
>> >
>>
>
>
>
> --
> Thanks,
> Regards,
> ASH
>



-- 
Thanks,
Regards,
ASH

Re: Using ssh keys for authentication

[Asanka sanjaya Herath]

Hi lan Duffy,

Thank you for your help. I'll try those things and let know the results.

On Fri, Sep 26, 2014 at 7:46 PM, Ian Duffy  wrote:

> Hi,
>
> Please see the init scripts available over at:
> https://github.com/shankerbalan/cloudstack-scripts
>
> Alternatively, you can use cloud-init with cloudstack as a data source:
> http://shankerbalan.net/blog/cloud-init-supports-cloudstack-as-data-source/
>
> Normally one would bake these into their template.
>
> Once you have your template created you can bring up a new instance with an
> ssh key assigned and login using it:
>
> http://shankerbalan.net/blog/ssh-keys-on-cloudstack-guest-instances-using-cloud-init/
>
> On 26 September 2014 07:06, Asanka sanjaya Herath 
> wrote:
>
> > ​I followed this guide in order to use ssh keys for authentication in
> > cloudstack.
> >
> >
> >
> https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Installation_Guide/using-sshkeys.html
> >
> >
> > According to this document we need to create an instance and download a
> > script to it  (section 5.2.1) . My problem is should I create another
> > template from the instance which created in section 5.2.1?​
> > Because in section 5.2.3, it says us to give the template ID in order to
> > create a new instance.
> >
> > --
> > Thanks,
> > Regards,
> > ASH
> >
>



-- 
Thanks,
Regards,
ASH

Using ssh keys for authentication

[Asanka sanjaya Herath]

​I followed this guide in order to use ssh keys for authentication in
cloudstack.

https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Installation_Guide/using-sshkeys.html


According to this document we need to create an instance and download a
script to it  (section 5.2.1) . My problem is should I create another
template from the instance which created in section 5.2.1?​
Because in section 5.2.3, it says us to give the template ID in order to
create a new instance.

-- 
Thanks,
Regards,
ASH

Cannot add ssh keys

[Asanka sanjaya Herath]

I used this

guide
for use ssh keys in cloudstack.
I'm using a debian instance.
Once I run *chkconfig --add cloud-set-guest-sshkey.in
* command it gives me this error.

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US.UTF-8",
LC_ALL = "en_US.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
insserv: warning: script
'K01cloud-set-guest-sshkey.in?r=http:%2F%2Fsourceforge.net%2Fprojects%2Fcloudstack%2Ffiles%2FSSH%20Key%20Gen%20Script%2F'
missing LSB tags and overrides
insserv: warning: script 'K01cloud-set-guest-sshkey.in' missing LSB tags
and overrides
insserv: warning: script 'cloud-set-guest-sshkey.in' missing LSB tags and
overrides
insserv: warning: script '
cloud-set-guest-sshkey.in?r=http:%2F%2Fsourceforge.net%2Fprojects%2Fcloudstack%2Ffiles%2FSSH%20Key%20Gen%20Script%2F'
missing LSB tags and overrides
cloud-set-guest-sshkey.in  0:off  1:off  2:on   3:on   4:on   5:on   6:off

I followed this

also
but that didn't work. Any ideas?

-- 
Thanks,
Regards,
ASH

Re: cannot ping to cloudstack instance

[Asanka sanjaya Herath]

Hi,
I was able to resolve that issue too. Thanks Ian Duffy gave me the
solution. The problem was with the template which I was using. Once I
changed template that instance could access internet.

Thank you Gopalakrishnan, Jayapal and Ian duffy for the help.


On Thu, Sep 25, 2014 at 5:53 PM, GopalaKrishnan  wrote:

> Hi Sanjaya,
>
> I am not sure how you have setup your network and configured local
> ipaddress in your router. Anyway check your other ips which is connected
> public access.
>
> Thank You.
> Gopalakrishnan.S
>
> - Original Message -
>   From: Asanka sanjaya Herath
>   To: users@cloudstack.apache.org
>   Sent: Thursday, September 25, 2014 4:56 PM
>   Subject: Re: cannot ping to cloudstack instance
>
>
>   Hi,
>   A screenshot of my network has been attached here. It doesn't show any
> public network access. Is that a problem?
>
>
>   On Thu, Sep 25, 2014 at 4:35 PM, Asanka sanjaya Herath <
> angal...@gmail.com> wrote:
>
> ​Hi Gopalakrishnan,
>
>
> I added that. But still the same problem. I'll check my VMs Gateway
> and IP settings.
>
>
> Thank you.​
>
>
> On Thu, Sep 25, 2014 at 4:28 PM, GopalaKrishnan 
> wrote:
>
>   Hi Sanjaya,
>
>   Just add the following entries in your VMs /etc/resolv.conf
>
>   nameserver 4.2.2.2
>   nameserver 8.8.4.4
>
>   if it does not work, then you should check VMs Gateway and ip
> settings.
>
>   Thank you.
>   Gopalakrishnan.S
>
>   - Original Message - From: "Asanka sanjaya Herath" <
> angal...@gmail.com>
>   To: 
>   Sent: Thursday, September 25, 2014 4:15 PM
>
>   Subject: Re: cannot ping to cloudstack instance
>
>
>   Hi GopalaKrishnan,
>
>   My /etc/conf file shows these information.
>
>   search citrite.net
>   nameserver 10.216.4.21
>   nameserver 10.216.4.34
>   nameserver 10.9.47.59
>   nameserver 172.16.2.66
>   search cs1cloud.internal
>   nameserver 192.168.56.111
>   nameserver 8.8.8.8
>   nameserver 8.8.4.4
>
>   But still when I ping to www.google.com it gives the bad address
> error.
>
>
>
>   On Thu, Sep 25, 2014 at 3:21 PM, GopalaKrishnan 
> wrote:
>
>
> Hi,
>
> Check /etc/resolv.conf file nameserver.
>
> ex:
> nameserver 4.2.2.2
>
> Thank You.
> Gopalakrishnan.S
>
> - Original Message - From: "Asanka sanjaya Herath" <
> angal...@gmail.com>
> To: 
> Sent: Thursday, September 25, 2014 3:06 PM
> Subject: Re: cannot ping to cloudstack instance
>
>
>
> Hi,
> I have another problem.  My instances cannot access internet now.
> How can I
> solve that?
>
> On Thu, Sep 25, 2014 at 3:04 PM, Outback Dingo <
> outbackdi...@gmail.com>
> wrote:
>
>  Ahhh So its via vagrant and vbox... got it not what i was
> hoping for,
>
>   but Thanks
>
>   On Thu, Sep 25, 2014 at 7:21 PM, Asanka sanjaya Herath <
>   angal...@gmail.com
>   >
>   wrote:
>
>   > hi Dingo,
>   > I used this for installation.
>   >
>   > https://github.com/imduffy15/devcloud4
>   >
>   > On Thu, Sep 25, 2014 at 2:34 PM, Outback Dingo <
> outbackdi...@gmail.com>
>   > wrote:
>   >
>   > > Curious.. Is this a single machine single nic install on
> a
>   > workstation?
>   > > If so... How did you manage that?
>   > >
>   > > On Thu, Sep 25, 2014 at 6:51 PM, Asanka sanjaya Herath <
>   > angal...@gmail.com
>   > > >
>   > > wrote:
>   > >
>   > > > Problem solved. Thank you again.
>   > > >
>   > > > On Thu, Sep 25, 2014 at 2:16 PM, Jayapal Reddy Uradi <
>   > > > jayapalreddy.ur...@citrix.com> wrote:
>   > > >
>   > > > > Did you open ports 22-22 ?
>   > > > > Earlier mail you mentioned port 80-80 only.
>   > > > >
>   > > > > Please see the ports are opened and service is running
> in the
>   > > vm/server.
>   > > > >
>   > > > > Thanks,
>   > > > > Jayapal
>   > > > > On 25-Sep-2014, 

Re: cannot ping to cloudstack instance

[Asanka sanjaya Herath]

Hi,
A screenshot of my network has been attached here. It doesn't show any
public network access. Is that a problem?

On Thu, Sep 25, 2014 at 4:35 PM, Asanka sanjaya Herath 
wrote:

> ​Hi Gopalakrishnan,
>
> I added that. But still the same problem. I'll check my VMs Gateway and IP
> settings.
>
> Thank you.​
>
> On Thu, Sep 25, 2014 at 4:28 PM, GopalaKrishnan 
> wrote:
>
>> Hi Sanjaya,
>>
>> Just add the following entries in your VMs /etc/resolv.conf
>>
>> nameserver 4.2.2.2
>> nameserver 8.8.4.4
>>
>> if it does not work, then you should check VMs Gateway and ip settings.
>>
>> Thank you.
>> Gopalakrishnan.S
>>
>> - Original Message - From: "Asanka sanjaya Herath" <
>> angal...@gmail.com>
>> To: 
>> Sent: Thursday, September 25, 2014 4:15 PM
>>
>> Subject: Re: cannot ping to cloudstack instance
>>
>>
>> Hi GopalaKrishnan,
>>
>> My /etc/conf file shows these information.
>>
>> search citrite.net
>> nameserver 10.216.4.21
>> nameserver 10.216.4.34
>> nameserver 10.9.47.59
>> nameserver 172.16.2.66
>> search cs1cloud.internal
>> nameserver 192.168.56.111
>> nameserver 8.8.8.8
>> nameserver 8.8.4.4
>>
>> But still when I ping to www.google.com it gives the bad address error.
>>
>>
>>
>> On Thu, Sep 25, 2014 at 3:21 PM, GopalaKrishnan 
>> wrote:
>>
>>  Hi,
>>>
>>> Check /etc/resolv.conf file nameserver.
>>>
>>> ex:
>>> nameserver 4.2.2.2
>>>
>>> Thank You.
>>> Gopalakrishnan.S
>>>
>>> - Original Message - From: "Asanka sanjaya Herath" <
>>> angal...@gmail.com>
>>> To: 
>>> Sent: Thursday, September 25, 2014 3:06 PM
>>> Subject: Re: cannot ping to cloudstack instance
>>>
>>>
>>>
>>> Hi,
>>> I have another problem.  My instances cannot access internet now. How
>>> can I
>>> solve that?
>>>
>>> On Thu, Sep 25, 2014 at 3:04 PM, Outback Dingo 
>>> wrote:
>>>
>>>  Ahhh So its via vagrant and vbox... got it not what i was hoping
>>> for,
>>>
>>>> but Thanks
>>>>
>>>> On Thu, Sep 25, 2014 at 7:21 PM, Asanka sanjaya Herath <
>>>> angal...@gmail.com
>>>> >
>>>> wrote:
>>>>
>>>> > hi Dingo,
>>>> > I used this for installation.
>>>> >
>>>> > https://github.com/imduffy15/devcloud4
>>>> >
>>>> > On Thu, Sep 25, 2014 at 2:34 PM, Outback Dingo <
>>>> outbackdi...@gmail.com>
>>>> > wrote:
>>>> >
>>>> > > Curious.. Is this a single machine single nic install on a
>>>> > workstation?
>>>> > > If so... How did you manage that?
>>>> > >
>>>> > > On Thu, Sep 25, 2014 at 6:51 PM, Asanka sanjaya Herath <
>>>> > angal...@gmail.com
>>>> > > >
>>>> > > wrote:
>>>> > >
>>>> > > > Problem solved. Thank you again.
>>>> > > >
>>>> > > > On Thu, Sep 25, 2014 at 2:16 PM, Jayapal Reddy Uradi <
>>>> > > > jayapalreddy.ur...@citrix.com> wrote:
>>>> > > >
>>>> > > > > Did you open ports 22-22 ?
>>>> > > > > Earlier mail you mentioned port 80-80 only.
>>>> > > > >
>>>> > > > > Please see the ports are opened and service is running in the
>>>> > > vm/server.
>>>> > > > >
>>>> > > > > Thanks,
>>>> > > > > Jayapal
>>>> > > > > On 25-Sep-2014, at 2:12 PM, Asanka sanjaya Herath <
>>>> > angal...@gmail.com>
>>>> > > > >  wrote:
>>>> > > > >
>>>> > > > > > Sorry this is the error:
>>>> > > > > > # ssh root@192.168.56.135
>>>> > > > > > # ssh: connect to host 192.168.56.135 port 22: Connection
>>>> timed
>>>> out
>>>> > > > > >
>>>> > > > > > On Thu, Sep 25, 2014 at 2:05 PM, Asanka sanjaya Herath <
>>>> > > > > angal...@gmail.com>
>>>> > > > > > wrote:
&

Re: cannot ping to cloudstack instance

[Asanka sanjaya Herath]

​Hi Gopalakrishnan,

I added that. But still the same problem. I'll check my VMs Gateway and IP
settings.

Thank you.​

On Thu, Sep 25, 2014 at 4:28 PM, GopalaKrishnan  wrote:

> Hi Sanjaya,
>
> Just add the following entries in your VMs /etc/resolv.conf
>
> nameserver 4.2.2.2
> nameserver 8.8.4.4
>
> if it does not work, then you should check VMs Gateway and ip settings.
>
> Thank you.
> Gopalakrishnan.S
>
> - Original Message - From: "Asanka sanjaya Herath" <
> angal...@gmail.com>
> To: 
> Sent: Thursday, September 25, 2014 4:15 PM
>
> Subject: Re: cannot ping to cloudstack instance
>
>
> Hi GopalaKrishnan,
>
> My /etc/conf file shows these information.
>
> search citrite.net
> nameserver 10.216.4.21
> nameserver 10.216.4.34
> nameserver 10.9.47.59
> nameserver 172.16.2.66
> search cs1cloud.internal
> nameserver 192.168.56.111
> nameserver 8.8.8.8
> nameserver 8.8.4.4
>
> But still when I ping to www.google.com it gives the bad address error.
>
>
>
> On Thu, Sep 25, 2014 at 3:21 PM, GopalaKrishnan 
> wrote:
>
>  Hi,
>>
>> Check /etc/resolv.conf file nameserver.
>>
>> ex:
>> nameserver 4.2.2.2
>>
>> Thank You.
>> Gopalakrishnan.S
>>
>> - Original Message - From: "Asanka sanjaya Herath" <
>> angal...@gmail.com>
>> To: 
>> Sent: Thursday, September 25, 2014 3:06 PM
>> Subject: Re: cannot ping to cloudstack instance
>>
>>
>>
>> Hi,
>> I have another problem.  My instances cannot access internet now. How can
>> I
>> solve that?
>>
>> On Thu, Sep 25, 2014 at 3:04 PM, Outback Dingo 
>> wrote:
>>
>>  Ahhh So its via vagrant and vbox... got it not what i was hoping for,
>>
>>> but Thanks
>>>
>>> On Thu, Sep 25, 2014 at 7:21 PM, Asanka sanjaya Herath <
>>> angal...@gmail.com
>>> >
>>> wrote:
>>>
>>> > hi Dingo,
>>> > I used this for installation.
>>> >
>>> > https://github.com/imduffy15/devcloud4
>>> >
>>> > On Thu, Sep 25, 2014 at 2:34 PM, Outback Dingo >> >
>>> > wrote:
>>> >
>>> > > Curious.. Is this a single machine single nic install on a
>>> > workstation?
>>> > > If so... How did you manage that?
>>> > >
>>> > > On Thu, Sep 25, 2014 at 6:51 PM, Asanka sanjaya Herath <
>>> > angal...@gmail.com
>>> > > >
>>> > > wrote:
>>> > >
>>> > > > Problem solved. Thank you again.
>>> > > >
>>> > > > On Thu, Sep 25, 2014 at 2:16 PM, Jayapal Reddy Uradi <
>>> > > > jayapalreddy.ur...@citrix.com> wrote:
>>> > > >
>>> > > > > Did you open ports 22-22 ?
>>> > > > > Earlier mail you mentioned port 80-80 only.
>>> > > > >
>>> > > > > Please see the ports are opened and service is running in the
>>> > > vm/server.
>>> > > > >
>>> > > > > Thanks,
>>> > > > > Jayapal
>>> > > > > On 25-Sep-2014, at 2:12 PM, Asanka sanjaya Herath <
>>> > angal...@gmail.com>
>>> > > > >  wrote:
>>> > > > >
>>> > > > > > Sorry this is the error:
>>> > > > > > # ssh root@192.168.56.135
>>> > > > > > # ssh: connect to host 192.168.56.135 port 22: Connection timed
>>> out
>>> > > > > >
>>> > > > > > On Thu, Sep 25, 2014 at 2:05 PM, Asanka sanjaya Herath <
>>> > > > > angal...@gmail.com>
>>> > > > > > wrote:
>>> > > > > >
>>> > > > > >> Now I'm trying to ssh to that server. But it I got this error.
>>> > > > > >>
>>> > > > > >> # ssh root@192.168.56.180
>>> > > > > >> # ssh: connect to host 192.168.56.135 port 22: Connection > >
>>> > > >> timed
>>> > out
>>> > > > > >>
>>> > > > > >> I used default template(cent-os) provided by cloudstak.
>>> > > > > >> So where is the fault?
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> On Thu, Sep 25, 2014 at 1:59 

Re: cannot ping to cloudstack instance

[Asanka sanjaya Herath]

Hi GopalaKrishnan,

My /etc/conf file shows these information.

search citrite.net
nameserver 10.216.4.21
nameserver 10.216.4.34
nameserver 10.9.47.59
nameserver 172.16.2.66
search cs1cloud.internal
nameserver 192.168.56.111
nameserver 8.8.8.8
nameserver 8.8.4.4

But still when I ping to www.google.com it gives the bad address error.



On Thu, Sep 25, 2014 at 3:21 PM, GopalaKrishnan  wrote:

> Hi,
>
> Check /etc/resolv.conf file nameserver.
>
> ex:
> nameserver 4.2.2.2
>
> Thank You.
> Gopalakrishnan.S
>
> ----- Original Message - From: "Asanka sanjaya Herath" <
> angal...@gmail.com>
> To: 
> Sent: Thursday, September 25, 2014 3:06 PM
> Subject: Re: cannot ping to cloudstack instance
>
>
>
> Hi,
> I have another problem.  My instances cannot access internet now. How can I
> solve that?
>
> On Thu, Sep 25, 2014 at 3:04 PM, Outback Dingo 
> wrote:
>
>  Ahhh So its via vagrant and vbox... got it not what i was hoping for,
>> but Thanks
>>
>> On Thu, Sep 25, 2014 at 7:21 PM, Asanka sanjaya Herath <
>> angal...@gmail.com
>> >
>> wrote:
>>
>> > hi Dingo,
>> > I used this for installation.
>> >
>> > https://github.com/imduffy15/devcloud4
>> >
>> > On Thu, Sep 25, 2014 at 2:34 PM, Outback Dingo 
>> > wrote:
>> >
>> > > Curious.. Is this a single machine single nic install on a
>> > workstation?
>> > > If so... How did you manage that?
>> > >
>> > > On Thu, Sep 25, 2014 at 6:51 PM, Asanka sanjaya Herath <
>> > angal...@gmail.com
>> > > >
>> > > wrote:
>> > >
>> > > > Problem solved. Thank you again.
>> > > >
>> > > > On Thu, Sep 25, 2014 at 2:16 PM, Jayapal Reddy Uradi <
>> > > > jayapalreddy.ur...@citrix.com> wrote:
>> > > >
>> > > > > Did you open ports 22-22 ?
>> > > > > Earlier mail you mentioned port 80-80 only.
>> > > > >
>> > > > > Please see the ports are opened and service is running in the
>> > > vm/server.
>> > > > >
>> > > > > Thanks,
>> > > > > Jayapal
>> > > > > On 25-Sep-2014, at 2:12 PM, Asanka sanjaya Herath <
>> > angal...@gmail.com>
>> > > > >  wrote:
>> > > > >
>> > > > > > Sorry this is the error:
>> > > > > > # ssh root@192.168.56.135
>> > > > > > # ssh: connect to host 192.168.56.135 port 22: Connection timed
>> out
>> > > > > >
>> > > > > > On Thu, Sep 25, 2014 at 2:05 PM, Asanka sanjaya Herath <
>> > > > > angal...@gmail.com>
>> > > > > > wrote:
>> > > > > >
>> > > > > >> Now I'm trying to ssh to that server. But it I got this error.
>> > > > > >>
>> > > > > >> # ssh root@192.168.56.180
>> > > > > >> # ssh: connect to host 192.168.56.135 port 22: Connection timed
>> > out
>> > > > > >>
>> > > > > >> I used default template(cent-os) provided by cloudstak.
>> > > > > >> So where is the fault?
>> > > > > >>
>> > > > > >>
>> > > > > >> On Thu, Sep 25, 2014 at 1:59 PM, Asanka sanjaya Herath <
>> > > > > angal...@gmail.com
>> > > > > >>> wrote:
>> > > > > >>
>> > > > > >>> Hi Gopalakrishnan,
>> > > > > >>>
>> > > > > >>> That works. Thank you for your help. And thank you Jayapal for
>> > > > detailed
>> > > > > >>> information.
>> > > > > >>>
>> > > > > >>> On Thu, Sep 25, 2014 at 1:55 PM, Jayapal Reddy Uradi <
>> > > > > >>> jayapalreddy.ur...@citrix.com> wrote:
>> > > > > >>>
>> > > > > >>>> For ping icmp is type 8 and code 0.
>> > > > > >>>> Add icmp type, code -1,-1 to allow all icmp types and codes.
>> > > > > >>>>
>> > > > > >>>> -Jayapal
>> > > > > >>>>
>> > > > > >>>> On 25-Sep-2014, at 1:31 PM, Asanka sanjaya Herath <
>> > > > angal...@gmail.com
>&g

Re: cannot ping to cloudstack instance

[Asanka sanjaya Herath]

Hi,
I have another problem.  My instances cannot access internet now. How can I
solve that?

On Thu, Sep 25, 2014 at 3:04 PM, Outback Dingo 
wrote:

> Ahhh So its via vagrant and vbox... got it not what i was hoping for,
> but Thanks
>
> On Thu, Sep 25, 2014 at 7:21 PM, Asanka sanjaya Herath  >
> wrote:
>
> > hi Dingo,
> > I used this for installation.
> >
> > https://github.com/imduffy15/devcloud4
> >
> > On Thu, Sep 25, 2014 at 2:34 PM, Outback Dingo 
> > wrote:
> >
> > > Curious.. Is this a single machine single nic install on a
> > workstation?
> > > If so... How did you manage that?
> > >
> > > On Thu, Sep 25, 2014 at 6:51 PM, Asanka sanjaya Herath <
> > angal...@gmail.com
> > > >
> > > wrote:
> > >
> > > > Problem solved. Thank you again.
> > > >
> > > > On Thu, Sep 25, 2014 at 2:16 PM, Jayapal Reddy Uradi <
> > > > jayapalreddy.ur...@citrix.com> wrote:
> > > >
> > > > > Did you open ports 22-22 ?
> > > > > Earlier mail you mentioned port 80-80 only.
> > > > >
> > > > > Please see the ports are opened and service is running in the
> > > vm/server.
> > > > >
> > > > > Thanks,
> > > > > Jayapal
> > > > > On 25-Sep-2014, at 2:12 PM, Asanka sanjaya Herath <
> > angal...@gmail.com>
> > > > >  wrote:
> > > > >
> > > > > > Sorry this is the error:
> > > > > > # ssh root@192.168.56.135
> > > > > > # ssh: connect to host 192.168.56.135 port 22: Connection timed
> out
> > > > > >
> > > > > > On Thu, Sep 25, 2014 at 2:05 PM, Asanka sanjaya Herath <
> > > > > angal...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > >> Now I'm trying to ssh to that server. But it I got this error.
> > > > > >>
> > > > > >> # ssh root@192.168.56.180
> > > > > >> # ssh: connect to host 192.168.56.135 port 22: Connection timed
> > out
> > > > > >>
> > > > > >> I used default template(cent-os) provided by cloudstak.
> > > > > >> So where is the fault?
> > > > > >>
> > > > > >>
> > > > > >> On Thu, Sep 25, 2014 at 1:59 PM, Asanka sanjaya Herath <
> > > > > angal...@gmail.com
> > > > > >>> wrote:
> > > > > >>
> > > > > >>> Hi Gopalakrishnan,
> > > > > >>>
> > > > > >>> That works. Thank you for your help. And thank you Jayapal for
> > > > detailed
> > > > > >>> information.
> > > > > >>>
> > > > > >>> On Thu, Sep 25, 2014 at 1:55 PM, Jayapal Reddy Uradi <
> > > > > >>> jayapalreddy.ur...@citrix.com> wrote:
> > > > > >>>
> > > > > >>>> For ping icmp is type 8 and code 0.
> > > > > >>>> Add icmp type, code -1,-1 to allow all icmp types and codes.
> > > > > >>>>
> > > > > >>>> -Jayapal
> > > > > >>>>
> > > > > >>>> On 25-Sep-2014, at 1:31 PM, Asanka sanjaya Herath <
> > > > angal...@gmail.com
> > > > > >
> > > > > >>>> wrote:
> > > > > >>>>
> > > > > >>>>> Hi GopalaKrishnan,
> > > > > >>>>>
> > > > > >>>>> Thank you for help. I added Egress and Ingress rules as
> > follows.
> > > > > >>>>>
> > > > > >>>>> TCP: start port-80 endport-80 CIDR-0.0.0.0/0
> > > > > >>>>> ICMP: type-0 code-0 CIDR-0.0.0.0./0
> > > > > >>>>>
> > > > > >>>>> But still I cannot ping to the instance from the host
> machine.
> > > But
> > > > I
> > > > > >>>> can
> > > > > >>>>> ping to the host machine from the instance.
> > > > > >>>>>
> > > > > >>>>>
> > > > > >>>>> On Thu, Sep 25, 2014 at 12:35 PM, GopalaKrishnan <
> > > > > go...@assistanz.com>
> > > &

Re: cannot ping to cloudstack instance

[Asanka sanjaya Herath]

hi Dingo,
I used this for installation.

https://github.com/imduffy15/devcloud4

On Thu, Sep 25, 2014 at 2:34 PM, Outback Dingo 
wrote:

> Curious.. Is this a single machine single nic install on a workstation?
> If so... How did you manage that?
>
> On Thu, Sep 25, 2014 at 6:51 PM, Asanka sanjaya Herath  >
> wrote:
>
> > Problem solved. Thank you again.
> >
> > On Thu, Sep 25, 2014 at 2:16 PM, Jayapal Reddy Uradi <
> > jayapalreddy.ur...@citrix.com> wrote:
> >
> > > Did you open ports 22-22 ?
> > > Earlier mail you mentioned port 80-80 only.
> > >
> > > Please see the ports are opened and service is running in the
> vm/server.
> > >
> > > Thanks,
> > > Jayapal
> > > On 25-Sep-2014, at 2:12 PM, Asanka sanjaya Herath 
> > >  wrote:
> > >
> > > > Sorry this is the error:
> > > > # ssh root@192.168.56.135
> > > > # ssh: connect to host 192.168.56.135 port 22: Connection timed out
> > > >
> > > > On Thu, Sep 25, 2014 at 2:05 PM, Asanka sanjaya Herath <
> > > angal...@gmail.com>
> > > > wrote:
> > > >
> > > >> Now I'm trying to ssh to that server. But it I got this error.
> > > >>
> > > >> # ssh root@192.168.56.180
> > > >> # ssh: connect to host 192.168.56.135 port 22: Connection timed out
> > > >>
> > > >> I used default template(cent-os) provided by cloudstak.
> > > >> So where is the fault?
> > > >>
> > > >>
> > > >> On Thu, Sep 25, 2014 at 1:59 PM, Asanka sanjaya Herath <
> > > angal...@gmail.com
> > > >>> wrote:
> > > >>
> > > >>> Hi Gopalakrishnan,
> > > >>>
> > > >>> That works. Thank you for your help. And thank you Jayapal for
> > detailed
> > > >>> information.
> > > >>>
> > > >>> On Thu, Sep 25, 2014 at 1:55 PM, Jayapal Reddy Uradi <
> > > >>> jayapalreddy.ur...@citrix.com> wrote:
> > > >>>
> > > >>>> For ping icmp is type 8 and code 0.
> > > >>>> Add icmp type, code -1,-1 to allow all icmp types and codes.
> > > >>>>
> > > >>>> -Jayapal
> > > >>>>
> > > >>>> On 25-Sep-2014, at 1:31 PM, Asanka sanjaya Herath <
> > angal...@gmail.com
> > > >
> > > >>>> wrote:
> > > >>>>
> > > >>>>> Hi GopalaKrishnan,
> > > >>>>>
> > > >>>>> Thank you for help. I added Egress and Ingress rules as follows.
> > > >>>>>
> > > >>>>> TCP: start port-80 endport-80 CIDR-0.0.0.0/0
> > > >>>>> ICMP: type-0 code-0 CIDR-0.0.0.0./0
> > > >>>>>
> > > >>>>> But still I cannot ping to the instance from the host machine.
> But
> > I
> > > >>>> can
> > > >>>>> ping to the host machine from the instance.
> > > >>>>>
> > > >>>>>
> > > >>>>> On Thu, Sep 25, 2014 at 12:35 PM, GopalaKrishnan <
> > > go...@assistanz.com>
> > > >>>>> wrote:
> > > >>>>>
> > > >>>>>> Hi Sanjaya,
> > > >>>>>>
> > > >>>>>> You should check Security Groups and Egress, Ingress rules for
> > your
> > > >>>>>> instance user. Enable ICMP in Egress to ping your server.
> > > >>>>>>
> > > >>>>>> Thank You.
> > > >>>>>> GopalaKrishnan.S
> > > >>>>>> Cloud Architect at Fogpanel.
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> - Original Message - From: "Asanka sanjaya Herath" <
> > > >>>>>> angal...@gmail.com>
> > > >>>>>> To: 
> > > >>>>>> Sent: Thursday, September 25, 2014 11:51 AM
> > > >>>>>> Subject: cannot ping to cloudstack instance
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> I installed cloudstack in my local computer and added an
> instance
> > > >>>>>> successfully. Then I tried to ping to the instance created in
> > > >>>> cloudstack.
> > > >>>>>> But I cannot ping to instance.  But I can ping to the gateway.
> > > >>>>>>
> > > >>>>>> These are my network configurations(used basic networking):
> > > >>>>>>
> > > >>>>>> dns1: 8.8.8.8
> > > >>>>>> dns2: 8.8.4.4
> > > >>>>>>
> > > >>>>>> POD:
> > > >>>>>> startip: 192.168.56.200
> > > >>>>>> endip:192.168.56.220
> > > >>>>>>
> > > >>>>>> Guest IP Ranges:
> > > >>>>>> startip: 192.168.56.100
> > > >>>>>> endip: 192.168.56.199
> > > >>>>>> netmask: 255.255.255.0
> > > >>>>>> gateway: 192.168.56.5
> > > >>>>>>
> > > >>>>>> Instance IP: 192.168.56.135
> > > >>>>>>
> > > >>>>>> Any ideas?
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> --
> > > >>>>>> Thanks,
> > > >>>>>> Regards,
> > > >>>>>> A
> > > >>>>>> ​sanka
> > > >>>>>>
> > > >>>>>> ---
> > > >>>>>> This email is free from viruses and malware because avast!
> > Antivirus
> > > >>>>>> protection is active.
> > > >>>>>> http://www.avast.com
> > > >>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> --
> > > >>>>> Thanks,
> > > >>>>> Regards,
> > > >>>>> ASH
> > > >>>>
> > > >>>>
> > > >>>
> > > >>>
> > > >>> --
> > > >>> Thanks,
> > > >>> Regards,
> > > >>> ASH
> > > >>>
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Thanks,
> > > >> Regards,
> > > >> ASH
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > Thanks,
> > > > Regards,
> > > > ASH
> > >
> > >
> >
> >
> > --
> > Thanks,
> > Regards,
> > ASH
> >
>



-- 
Thanks,
Regards,
ASH

Re: cannot ping to cloudstack instance

[Asanka sanjaya Herath]

Problem solved. Thank you again.

On Thu, Sep 25, 2014 at 2:16 PM, Jayapal Reddy Uradi <
jayapalreddy.ur...@citrix.com> wrote:

> Did you open ports 22-22 ?
> Earlier mail you mentioned port 80-80 only.
>
> Please see the ports are opened and service is running in the vm/server.
>
> Thanks,
> Jayapal
> On 25-Sep-2014, at 2:12 PM, Asanka sanjaya Herath 
>  wrote:
>
> > Sorry this is the error:
> > # ssh root@192.168.56.135
> > # ssh: connect to host 192.168.56.135 port 22: Connection timed out
> >
> > On Thu, Sep 25, 2014 at 2:05 PM, Asanka sanjaya Herath <
> angal...@gmail.com>
> > wrote:
> >
> >> Now I'm trying to ssh to that server. But it I got this error.
> >>
> >> # ssh root@192.168.56.180
> >> # ssh: connect to host 192.168.56.135 port 22: Connection timed out
> >>
> >> I used default template(cent-os) provided by cloudstak.
> >> So where is the fault?
> >>
> >>
> >> On Thu, Sep 25, 2014 at 1:59 PM, Asanka sanjaya Herath <
> angal...@gmail.com
> >>> wrote:
> >>
> >>> Hi Gopalakrishnan,
> >>>
> >>> That works. Thank you for your help. And thank you Jayapal for detailed
> >>> information.
> >>>
> >>> On Thu, Sep 25, 2014 at 1:55 PM, Jayapal Reddy Uradi <
> >>> jayapalreddy.ur...@citrix.com> wrote:
> >>>
> >>>> For ping icmp is type 8 and code 0.
> >>>> Add icmp type, code -1,-1 to allow all icmp types and codes.
> >>>>
> >>>> -Jayapal
> >>>>
> >>>> On 25-Sep-2014, at 1:31 PM, Asanka sanjaya Herath  >
> >>>> wrote:
> >>>>
> >>>>> Hi GopalaKrishnan,
> >>>>>
> >>>>> Thank you for help. I added Egress and Ingress rules as follows.
> >>>>>
> >>>>> TCP: start port-80 endport-80 CIDR-0.0.0.0/0
> >>>>> ICMP: type-0 code-0 CIDR-0.0.0.0./0
> >>>>>
> >>>>> But still I cannot ping to the instance from the host machine. But I
> >>>> can
> >>>>> ping to the host machine from the instance.
> >>>>>
> >>>>>
> >>>>> On Thu, Sep 25, 2014 at 12:35 PM, GopalaKrishnan <
> go...@assistanz.com>
> >>>>> wrote:
> >>>>>
> >>>>>> Hi Sanjaya,
> >>>>>>
> >>>>>> You should check Security Groups and Egress, Ingress rules for your
> >>>>>> instance user. Enable ICMP in Egress to ping your server.
> >>>>>>
> >>>>>> Thank You.
> >>>>>> GopalaKrishnan.S
> >>>>>> Cloud Architect at Fogpanel.
> >>>>>>
> >>>>>>
> >>>>>> - Original Message - From: "Asanka sanjaya Herath" <
> >>>>>> angal...@gmail.com>
> >>>>>> To: 
> >>>>>> Sent: Thursday, September 25, 2014 11:51 AM
> >>>>>> Subject: cannot ping to cloudstack instance
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> I installed cloudstack in my local computer and added an instance
> >>>>>> successfully. Then I tried to ping to the instance created in
> >>>> cloudstack.
> >>>>>> But I cannot ping to instance.  But I can ping to the gateway.
> >>>>>>
> >>>>>> These are my network configurations(used basic networking):
> >>>>>>
> >>>>>> dns1: 8.8.8.8
> >>>>>> dns2: 8.8.4.4
> >>>>>>
> >>>>>> POD:
> >>>>>> startip: 192.168.56.200
> >>>>>> endip:192.168.56.220
> >>>>>>
> >>>>>> Guest IP Ranges:
> >>>>>> startip: 192.168.56.100
> >>>>>> endip: 192.168.56.199
> >>>>>> netmask: 255.255.255.0
> >>>>>> gateway: 192.168.56.5
> >>>>>>
> >>>>>> Instance IP: 192.168.56.135
> >>>>>>
> >>>>>> Any ideas?
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Thanks,
> >>>>>> Regards,
> >>>>>> A
> >>>>>> ​sanka
> >>>>>>
> >>>>>> ---
> >>>>>> This email is free from viruses and malware because avast! Antivirus
> >>>>>> protection is active.
> >>>>>> http://www.avast.com
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Thanks,
> >>>>> Regards,
> >>>>> ASH
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Thanks,
> >>> Regards,
> >>> ASH
> >>>
> >>
> >>
> >>
> >> --
> >> Thanks,
> >> Regards,
> >> ASH
> >>
> >
> >
> >
> > --
> > Thanks,
> > Regards,
> > ASH
>
>


-- 
Thanks,
Regards,
ASH

Re: cannot ping to cloudstack instance

[Asanka sanjaya Herath]

Sorry this is the error:
# ssh root@192.168.56.135
# ssh: connect to host 192.168.56.135 port 22: Connection timed out

On Thu, Sep 25, 2014 at 2:05 PM, Asanka sanjaya Herath 
wrote:

> Now I'm trying to ssh to that server. But it I got this error.
>
> # ssh root@192.168.56.180
> # ssh: connect to host 192.168.56.135 port 22: Connection timed out
>
> I used default template(cent-os) provided by cloudstak.
> So where is the fault?
>
>
> On Thu, Sep 25, 2014 at 1:59 PM, Asanka sanjaya Herath  > wrote:
>
>> Hi Gopalakrishnan,
>>
>> That works. Thank you for your help. And thank you Jayapal for detailed
>> information.
>>
>> On Thu, Sep 25, 2014 at 1:55 PM, Jayapal Reddy Uradi <
>> jayapalreddy.ur...@citrix.com> wrote:
>>
>>> For ping icmp is type 8 and code 0.
>>> Add icmp type, code -1,-1 to allow all icmp types and codes.
>>>
>>> -Jayapal
>>>
>>> On 25-Sep-2014, at 1:31 PM, Asanka sanjaya Herath 
>>> wrote:
>>>
>>> > Hi GopalaKrishnan,
>>> >
>>> > Thank you for help. I added Egress and Ingress rules as follows.
>>> >
>>> > TCP: start port-80 endport-80 CIDR-0.0.0.0/0
>>> > ICMP: type-0 code-0 CIDR-0.0.0.0./0
>>> >
>>> > But still I cannot ping to the instance from the host machine. But I
>>> can
>>> > ping to the host machine from the instance.
>>> >
>>> >
>>> > On Thu, Sep 25, 2014 at 12:35 PM, GopalaKrishnan 
>>> > wrote:
>>> >
>>> >> Hi Sanjaya,
>>> >>
>>> >> You should check Security Groups and Egress, Ingress rules for your
>>> >> instance user. Enable ICMP in Egress to ping your server.
>>> >>
>>> >> Thank You.
>>> >> GopalaKrishnan.S
>>> >> Cloud Architect at Fogpanel.
>>> >>
>>> >>
>>> >> - Original Message - From: "Asanka sanjaya Herath" <
>>> >> angal...@gmail.com>
>>> >> To: 
>>> >> Sent: Thursday, September 25, 2014 11:51 AM
>>> >> Subject: cannot ping to cloudstack instance
>>> >>
>>> >>
>>> >>
>>> >> I installed cloudstack in my local computer and added an instance
>>> >> successfully. Then I tried to ping to the instance created in
>>> cloudstack.
>>> >> But I cannot ping to instance.  But I can ping to the gateway.
>>> >>
>>> >> These are my network configurations(used basic networking):
>>> >>
>>> >> dns1: 8.8.8.8
>>> >> dns2: 8.8.4.4
>>> >>
>>> >> POD:
>>> >> startip: 192.168.56.200
>>> >> endip:192.168.56.220
>>> >>
>>> >> Guest IP Ranges:
>>> >> startip: 192.168.56.100
>>> >> endip: 192.168.56.199
>>> >> netmask: 255.255.255.0
>>> >> gateway: 192.168.56.5
>>> >>
>>> >> Instance IP: 192.168.56.135
>>> >>
>>> >> Any ideas?
>>> >>
>>> >>
>>> >> --
>>> >> Thanks,
>>> >> Regards,
>>> >> A
>>> >> ​sanka
>>> >>
>>> >> ---
>>> >> This email is free from viruses and malware because avast! Antivirus
>>> >> protection is active.
>>> >> http://www.avast.com
>>> >>
>>> >>
>>> >
>>> >
>>> > --
>>> > Thanks,
>>> > Regards,
>>> > ASH
>>>
>>>
>>
>>
>> --
>> Thanks,
>> Regards,
>> ASH
>>
>
>
>
> --
> Thanks,
> Regards,
> ASH
>



-- 
Thanks,
Regards,
ASH

Re: cannot ping to cloudstack instance

[Asanka sanjaya Herath]

Now I'm trying to ssh to that server. But it I got this error.

# ssh root@192.168.56.180
# ssh: connect to host 192.168.56.135 port 22: Connection timed out

I used default template(cent-os) provided by cloudstak.
So where is the fault?


On Thu, Sep 25, 2014 at 1:59 PM, Asanka sanjaya Herath 
wrote:

> Hi Gopalakrishnan,
>
> That works. Thank you for your help. And thank you Jayapal for detailed
> information.
>
> On Thu, Sep 25, 2014 at 1:55 PM, Jayapal Reddy Uradi <
> jayapalreddy.ur...@citrix.com> wrote:
>
>> For ping icmp is type 8 and code 0.
>> Add icmp type, code -1,-1 to allow all icmp types and codes.
>>
>> -Jayapal
>>
>> On 25-Sep-2014, at 1:31 PM, Asanka sanjaya Herath 
>> wrote:
>>
>> > Hi GopalaKrishnan,
>> >
>> > Thank you for help. I added Egress and Ingress rules as follows.
>> >
>> > TCP: start port-80 endport-80 CIDR-0.0.0.0/0
>> > ICMP: type-0 code-0 CIDR-0.0.0.0./0
>> >
>> > But still I cannot ping to the instance from the host machine. But I can
>> > ping to the host machine from the instance.
>> >
>> >
>> > On Thu, Sep 25, 2014 at 12:35 PM, GopalaKrishnan 
>> > wrote:
>> >
>> >> Hi Sanjaya,
>> >>
>> >> You should check Security Groups and Egress, Ingress rules for your
>> >> instance user. Enable ICMP in Egress to ping your server.
>> >>
>> >> Thank You.
>> >> GopalaKrishnan.S
>> >> Cloud Architect at Fogpanel.
>> >>
>> >>
>> >> - Original Message - From: "Asanka sanjaya Herath" <
>> >> angal...@gmail.com>
>> >> To: 
>> >> Sent: Thursday, September 25, 2014 11:51 AM
>> >> Subject: cannot ping to cloudstack instance
>> >>
>> >>
>> >>
>> >> I installed cloudstack in my local computer and added an instance
>> >> successfully. Then I tried to ping to the instance created in
>> cloudstack.
>> >> But I cannot ping to instance.  But I can ping to the gateway.
>> >>
>> >> These are my network configurations(used basic networking):
>> >>
>> >> dns1: 8.8.8.8
>> >> dns2: 8.8.4.4
>> >>
>> >> POD:
>> >> startip: 192.168.56.200
>> >> endip:192.168.56.220
>> >>
>> >> Guest IP Ranges:
>> >> startip: 192.168.56.100
>> >> endip: 192.168.56.199
>> >> netmask: 255.255.255.0
>> >> gateway: 192.168.56.5
>> >>
>> >> Instance IP: 192.168.56.135
>> >>
>> >> Any ideas?
>> >>
>> >>
>> >> --
>> >> Thanks,
>> >> Regards,
>> >> A
>> >> ​sanka
>> >>
>> >> ---
>> >> This email is free from viruses and malware because avast! Antivirus
>> >> protection is active.
>> >> http://www.avast.com
>> >>
>> >>
>> >
>> >
>> > --
>> > Thanks,
>> > Regards,
>> > ASH
>>
>>
>
>
> --
> Thanks,
> Regards,
> ASH
>



-- 
Thanks,
Regards,
ASH

Re: cannot ping to cloudstack instance

[Asanka sanjaya Herath]

Hi Gopalakrishnan,

That works. Thank you for your help. And thank you Jayapal for detailed
information.

On Thu, Sep 25, 2014 at 1:55 PM, Jayapal Reddy Uradi <
jayapalreddy.ur...@citrix.com> wrote:

> For ping icmp is type 8 and code 0.
> Add icmp type, code -1,-1 to allow all icmp types and codes.
>
> -Jayapal
>
> On 25-Sep-2014, at 1:31 PM, Asanka sanjaya Herath 
> wrote:
>
> > Hi GopalaKrishnan,
> >
> > Thank you for help. I added Egress and Ingress rules as follows.
> >
> > TCP: start port-80 endport-80 CIDR-0.0.0.0/0
> > ICMP: type-0 code-0 CIDR-0.0.0.0./0
> >
> > But still I cannot ping to the instance from the host machine. But I can
> > ping to the host machine from the instance.
> >
> >
> > On Thu, Sep 25, 2014 at 12:35 PM, GopalaKrishnan 
> > wrote:
> >
> >> Hi Sanjaya,
> >>
> >> You should check Security Groups and Egress, Ingress rules for your
> >> instance user. Enable ICMP in Egress to ping your server.
> >>
> >> Thank You.
> >> GopalaKrishnan.S
> >> Cloud Architect at Fogpanel.
> >>
> >>
> >> - Original Message - From: "Asanka sanjaya Herath" <
> >> angal...@gmail.com>
> >> To: 
> >> Sent: Thursday, September 25, 2014 11:51 AM
> >> Subject: cannot ping to cloudstack instance
> >>
> >>
> >>
> >> I installed cloudstack in my local computer and added an instance
> >> successfully. Then I tried to ping to the instance created in
> cloudstack.
> >> But I cannot ping to instance.  But I can ping to the gateway.
> >>
> >> These are my network configurations(used basic networking):
> >>
> >> dns1: 8.8.8.8
> >> dns2: 8.8.4.4
> >>
> >> POD:
> >> startip: 192.168.56.200
> >> endip:192.168.56.220
> >>
> >> Guest IP Ranges:
> >> startip: 192.168.56.100
> >> endip: 192.168.56.199
> >> netmask: 255.255.255.0
> >> gateway: 192.168.56.5
> >>
> >> Instance IP: 192.168.56.135
> >>
> >> Any ideas?
> >>
> >>
> >> --
> >> Thanks,
> >> Regards,
> >> A
> >> ​sanka
> >>
> >> ---
> >> This email is free from viruses and malware because avast! Antivirus
> >> protection is active.
> >> http://www.avast.com
> >>
> >>
> >
> >
> > --
> > Thanks,
> > Regards,
> > ASH
>
>


-- 
Thanks,
Regards,
ASH

Re: cannot ping to cloudstack instance

[Asanka sanjaya Herath]

Hi GopalaKrishnan,

Thank you for help. I added Egress and Ingress rules as follows.

TCP: start port-80 endport-80 CIDR-0.0.0.0/0
ICMP: type-0 code-0 CIDR-0.0.0.0./0

But still I cannot ping to the instance from the host machine. But I can
ping to the host machine from the instance.


On Thu, Sep 25, 2014 at 12:35 PM, GopalaKrishnan 
wrote:

> Hi Sanjaya,
>
> You should check Security Groups and Egress, Ingress rules for your
> instance user. Enable ICMP in Egress to ping your server.
>
> Thank You.
> GopalaKrishnan.S
> Cloud Architect at Fogpanel.
>
>
> ----- Original Message - From: "Asanka sanjaya Herath" <
> angal...@gmail.com>
> To: 
> Sent: Thursday, September 25, 2014 11:51 AM
> Subject: cannot ping to cloudstack instance
>
>
>
> I installed cloudstack in my local computer and added an instance
> successfully. Then I tried to ping to the instance created in cloudstack.
> But I cannot ping to instance.  But I can ping to the gateway.
>
> These are my network configurations(used basic networking):
>
> dns1: 8.8.8.8
> dns2: 8.8.4.4
>
> POD:
> startip: 192.168.56.200
> endip:192.168.56.220
>
> Guest IP Ranges:
> startip: 192.168.56.100
> endip: 192.168.56.199
> netmask: 255.255.255.0
> gateway: 192.168.56.5
>
> Instance IP: 192.168.56.135
>
> Any ideas?
>
>
> --
> Thanks,
> Regards,
> A
> ​sanka
>
> ---
> This email is free from viruses and malware because avast! Antivirus
> protection is active.
> http://www.avast.com
>
>


-- 
Thanks,
Regards,
ASH

cannot ping to cloudstack instance

[Asanka sanjaya Herath]

I installed cloudstack in my local computer and added an instance
successfully. Then I tried to ping to the instance created in cloudstack.
But I cannot ping to instance.  But I can ping to the gateway.

These are my network configurations(used basic networking):

dns1: 8.8.8.8
dns2: 8.8.4.4

POD:
startip: 192.168.56.200
endip:192.168.56.220

Guest IP Ranges:
startip: 192.168.56.100
endip: 192.168.56.199
netmask: 255.255.255.0
gateway: 192.168.56.5

Instance IP: 192.168.56.135

Any ideas?


-- 
Thanks,
Regards,
A
​sanka​

Re: Cloudstack systemvmtemplate url is not working

[Asanka sanjaya Herath]

What about this one?

http://jenkins.buildacloud.org/job/build-systemvm-master/314/artifact/tools/appliance/dist/systemvmtemplate-master-314-xen.vhd.bz2

Can I use this url Instead of previous one?

On Wed, Sep 24, 2014 at 12:13 PM, Rayees Namathponnan <
rayees.namathpon...@citrix.com> wrote:

> Can you try
> http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-422-xen.vhd.bz2
>
> Its 64 bit template
>
> Regards,
> Rayees
>
> -----Original Message-----
> From: Asanka sanjaya Herath [mailto:angal...@gmail.com]
> Sent: Tuesday, September 23, 2014 11:14 PM
> To: users@cloudstack.apache.org
> Subject: Cloudstack systemvmtemplate url is not working
>
> I used this url for get cloudstack systemvmtemplate but this returns 404
> error.
>
>
> http://jenkins.buildacloud.org/job/build-systemvm-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvmtemplate-master-xen.vhd.bz2
>
> Is there any alternative url which I can use for this?
>
> --
> Thanks,
> Regards,
> ASH
>



-- 
Thanks,
Regards,
ASH

Cloudstack systemvmtemplate url is not working

[Asanka sanjaya Herath]

I used this url for get cloudstack systemvmtemplate but this returns 404
error.

http://jenkins.buildacloud.org/job/build-systemvm-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvmtemplate-master-xen.vhd.bz2

Is there any alternative url which I can use for this?

-- 
Thanks,
Regards,
ASH

Re: Cannot add instances using template created from snapshot

[Asanka sanjaya Herath]

Solved the issue.

I changed hvm value from 1 to 0 in vm_template table and now I can add
instances from that template without having any issue.

On Fri, Sep 5, 2014 at 7:06 PM, Asanka sanjaya Herath 
wrote:

> I followed this https://github.com/imduffy15/GSoC-2014/ and installed
> apache cloudstack with basic networking  in my local machine, and every
> thing worked smoothly.
>
> ​I can add instances from the built in tiny linux template(cent-os 5.6
> 64bit) without having any issue.
>
> I got a snapshot of the running instance volume and created a template
> from it. When I try to add an instance using that template I always get
> *InsufficientServerCapacityException*.
>
> According to my dashboard there are enough capacity to add the instance.
> Any ideas?
>
> console:
>
> ​WARN  [o.a.c.alerts] (API-Job-Executor-5:ctx-4692c763 job-166
> ctx-b141500e)  alertType:: 8 // dataCenterId:: 1 // podId:: null //
> clusterId:: null // message:: Failed to deploy Vm with Id: 29, on Host with
> Id: null
> INFO  [o.a.c.a.c.a.v.DeployVMCmdByAdmin] (API-Job-Executor-5:ctx-4692c763
> job-166 ctx-b141500e)
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a
> deployment for VM[User|i-2-29-VM]Scope=interface com.cloud.dc.DataCenter;
> id=1
> INFO  [o.a.c.a.c.a.v.DeployVMCmdByAdmin] (API-Job-Executor-5:ctx-4692c763
> job-166 ctx-b141500e) Unable to create a deployment for VM[User|i-2-29-VM]
> com.cloud.exception.InsufficientServerCapacityException: Unable to create
> a deployment for VM[User|i-2-29-VM]Scope=interface com.cloud.dc.DataCenter;
> id=1
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:214)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:200)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3515)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3166)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3154)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at
> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at com.sun.proxy.$Proxy224.startVirtualMachine(Unknown Source)
> at
> org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin.execute(DeployVMCmdByAdmin.java:48)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
> at
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
>
>
>
> --
> Thanks,
> Regards,
> ASH
>



-- 
Thanks,
Regards,
ASH

Cannot add instances using template created from snapshot

[Asanka sanjaya Herath]

I followed this https://github.com/imduffy15/GSoC-2014/ and installed
apache cloudstack with basic networking  in my local machine, and every
thing worked smoothly.

​I can add instances from the built in tiny linux template(cent-os 5.6
64bit) without having any issue.

I got a snapshot of the running instance volume and created a template from
it. When I try to add an instance using that template I always get
*InsufficientServerCapacityException*.

According to my dashboard there are enough capacity to add the instance.
Any ideas?

console:

​WARN  [o.a.c.alerts] (API-Job-Executor-5:ctx-4692c763 job-166
ctx-b141500e)  alertType:: 8 // dataCenterId:: 1 // podId:: null //
clusterId:: null // message:: Failed to deploy Vm with Id: 29, on Host with
Id: null
INFO  [o.a.c.a.c.a.v.DeployVMCmdByAdmin] (API-Job-Executor-5:ctx-4692c763
job-166 ctx-b141500e)
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[User|i-2-29-VM]Scope=interface com.cloud.dc.DataCenter;
id=1
INFO  [o.a.c.a.c.a.v.DeployVMCmdByAdmin] (API-Job-Executor-5:ctx-4692c763
job-166 ctx-b141500e) Unable to create a deployment for VM[User|i-2-29-VM]
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[User|i-2-29-VM]Scope=interface com.cloud.dc.DataCenter;
id=1
at
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:214)
at
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:200)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3515)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3166)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3154)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy224.startVirtualMachine(Unknown Source)
at
org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin.execute(DeployVMCmdByAdmin.java:48)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
at
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)



-- 
Thanks,
Regards,
ASH