date:20140429

Ok, so I've figured out a way to identify volumes in the filesystem.  For
instance, /var/storage/primary/4d324e1a-e3a6-4da8-9c4d-44ad723482ad is the
root volume for an instance I want to back up.  Is this in qcow2 format or
something else?  I'm using KVM.


On Tue, Apr 29, 2014 at 7:38 PM, Ian Young  wrote:

> Now I can't start cloudstack-agent.  The agent.log says:
>
> Unable to start agent: Failed to get private nic name
>
> I know this is because the network bridge is no longer set up correctly.
>  I used to have a cloud0 and a cloudbr0 interface.  Now I only have
> cloudbr0.  I haven't changed my network configuration.  Somehow it's been
> changed by CloudStack during the upgrade/downgrade.  This is getting worse
> and worse the more I try to recover my data.  Is there any way to back up
> the instances' volumes via the command line?  I can't tell which is which
> because the filenames are all hashes.  I really need to get these instances
> up and running--there are several months worth of work at stake here.
>
>
> On Tue, Apr 29, 2014 at 6:13 PM, ma y  wrote:
>
>> I got the same problem, and how to downgrade CS 4.3.0 to 4.2.1 safely?
>>
>>
>> 2014-04-30 8:45 GMT+08:00 Ian Young :
>>
>> > Ok, my Cloudstack installation is now so broken that I think it's
>> probably
>> > best to backup all my instances and templates, wipe the databases, and
>> > start from scratch.  However, I can't take snapshots or download volumes
>> > anymore.  What's causing these errors?
>> >
>> > 2014-04-29 17:40:51,264 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
>> > (Job-Executor-11:ctx-0a3ead79 ctx-315eda05) copy object failed:
>> > com.cloud.utils.exception.CloudRuntimeException: Failed to send command,
>> > due to Agent:1, com.cloud.exception.OperationTimedoutException: Commands
>> > 841744457 to Host 1 timed out after 21600
>> > 2014-04-29 17:40:51,265 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
>> > (Job-Executor-11:ctx-0a3ead79 ctx-315eda05) copy failed
>> > com.cloud.utils.exception.CloudRuntimeException:
>> > com.cloud.utils.exception.CloudRuntimeException: Failed to send command,
>> > due to Agent:1, com.cloud.exception.OperationTimedoutException: Commands
>> > 841744457 to Host 1 timed out after 21600
>> > 2014-04-29 17:40:51,269 WARN  [o.a.c.s.d.ObjectInDataStoreManagerImpl]
>> > (Job-Executor-11:ctx-0a3ead79 ctx-315eda05) Unsupported data object
>> > (VOLUME,
>> > org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@7bbbd901),
>> no
>> > need to delete from object in store ref table
>> > 2014-04-29 17:40:51,280 ERROR [c.c.a.ApiAsyncJobDispatcher]
>> > (Job-Executor-11:ctx-0a3ead79) Unexpected exception while executing
>> > org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd
>> > com.cloud.utils.exception.CloudRuntimeException: Failed to copy the
>> volume
>> > from the source primary storage pool to secondary storage.
>> > 2014-04-29 17:40:51,282 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
>> > (Job-Executor-11:ctx-0a3ead79) Complete async job-501, jobStatus:
>> FAILED,
>> > resultCode: 530, result:
>> >
>> >
>> org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530,"errortext":"Failed
>> > to copy the volume from the source primary storage pool to secondary
>> > storage."}
>> >
>> >
>> > On Tue, Apr 29, 2014 at 4:15 PM, Ian Young 
>> wrote:
>> >
>> > > I downgraded to 4.2.1 again but cloudstack-management won't start
>> because
>> > > the database is version 4.3. Is it safe to restore the database
>> backup I
>> > > made prior to this whole process? In the meantime I have destroyed and
>> > > created system VMs, so I'm not sure it's a good idea.
>> > > On Apr 29, 2014 3:09 PM, "Ian Young"  wrote:
>> > >
>> > >> @stevenliang: I take it back--you can't set the VM size when you
>> > register
>> > >> the template.
>> > >>
>> > >>
>> > >> On Tue, Apr 29, 2014 at 3:02 PM, motty cruz 
>> > wrote:
>> > >>
>> > >>> yes, you would have to shutdown the router, then click on "Change
>> > Service
>> > >>> Offering"
>> > >>> restart the VR.
>> > >>>
>> > >>> To Ian,
>> > >>>
>> > >>> I suspect you forgot the last step: " cloudstack-setup-management"
>> > >>>
>> > >>> that would fix your issue, I think,
>> > >>>
>> > >>> Thanks,
>> > >>> ---
>> > >>> I downgraded to 4.2.1 and then upgraded to 4.3.  Now the
>> > >>> cloudstack-management service can't start because it can't connect
>> to
>> > the
>> > >>> database.
>> > >>>
>> > >>> 2014-04-29 14:51:36,424 ERROR [c.c.u.d.Merovingian2] (main:null)
>> Unable
>> > >>> to
>> > >>> get a new db connection
>> > >>> Caused by: java.sql.SQLException: Access denied for user 'cloud'@
>> > >>> 'localhost'
>> > >>> (using password: YES)
>> > >>>
>> > >>> Where are the credentials stored?
>> > >>>
>> > >>>
>> > >>> On Tue, Apr 29, 2014 at 2:57 PM, stevenliang > >
>> > >>> wrote:
>> > >>>
>> > >>> > oh, then change service offering for vr?
>> > >>> >
>> > >>> >
>> > >>> > On 29/04/14 05:53 PM, motty cruz wrote:
>> > >>> >
>> > >>> >> for my VR, I

RE: Configuring health check to F5 LB fails

2014-04-29 Thread Rajesh Battala

Hi Amin,
Currently only Netscaler LB supports HealthCheck policies. For Remaining LB 
providers it's not yet supported in Cloudstack.
Entire framework is available but providers have to implement the commands in 
their resources.

Thanks
Rajesh Battala

-Original Message-
From: Amin Pashapour [mailto:jol...@yahoo.com] 
Sent: Tuesday, April 29, 2014 10:35 PM
To: users@cloudstack.apache.org
Subject: Configuring health check to F5 LB fails

Hi

When I try to add a health check to a loadbalancer setup with F5 as the 
provider, I get this error on the screen.  I am just trying to add the check 
with the default values. I am running 4.2.1.  Am I missing something?


{ "createlbhealthcheckpolicyresponse" : 
{"uuidList":[],"errorcode":430,"cserrorcode":,"errortext":"Failed to create 
HealthCheck policy: Validation Failed (HealthCheck Policy is not supported by 
LB Provider for the LB rule id :)57"} }



Thanks.
Amin

Re: failed to start virtual router

Now I can't start cloudstack-agent.  The agent.log says:

Unable to start agent: Failed to get private nic name

I know this is because the network bridge is no longer set up correctly.  I
used to have a cloud0 and a cloudbr0 interface.  Now I only have cloudbr0.
 I haven't changed my network configuration.  Somehow it's been changed by
CloudStack during the upgrade/downgrade.  This is getting worse and worse
the more I try to recover my data.  Is there any way to back up the
instances' volumes via the command line?  I can't tell which is which
because the filenames are all hashes.  I really need to get these instances
up and running--there are several months worth of work at stake here.


On Tue, Apr 29, 2014 at 6:13 PM, ma y  wrote:

> I got the same problem, and how to downgrade CS 4.3.0 to 4.2.1 safely?
>
>
> 2014-04-30 8:45 GMT+08:00 Ian Young :
>
> > Ok, my Cloudstack installation is now so broken that I think it's
> probably
> > best to backup all my instances and templates, wipe the databases, and
> > start from scratch.  However, I can't take snapshots or download volumes
> > anymore.  What's causing these errors?
> >
> > 2014-04-29 17:40:51,264 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
> > (Job-Executor-11:ctx-0a3ead79 ctx-315eda05) copy object failed:
> > com.cloud.utils.exception.CloudRuntimeException: Failed to send command,
> > due to Agent:1, com.cloud.exception.OperationTimedoutException: Commands
> > 841744457 to Host 1 timed out after 21600
> > 2014-04-29 17:40:51,265 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
> > (Job-Executor-11:ctx-0a3ead79 ctx-315eda05) copy failed
> > com.cloud.utils.exception.CloudRuntimeException:
> > com.cloud.utils.exception.CloudRuntimeException: Failed to send command,
> > due to Agent:1, com.cloud.exception.OperationTimedoutException: Commands
> > 841744457 to Host 1 timed out after 21600
> > 2014-04-29 17:40:51,269 WARN  [o.a.c.s.d.ObjectInDataStoreManagerImpl]
> > (Job-Executor-11:ctx-0a3ead79 ctx-315eda05) Unsupported data object
> > (VOLUME,
> > org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@7bbbd901),
> no
> > need to delete from object in store ref table
> > 2014-04-29 17:40:51,280 ERROR [c.c.a.ApiAsyncJobDispatcher]
> > (Job-Executor-11:ctx-0a3ead79) Unexpected exception while executing
> > org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd
> > com.cloud.utils.exception.CloudRuntimeException: Failed to copy the
> volume
> > from the source primary storage pool to secondary storage.
> > 2014-04-29 17:40:51,282 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> > (Job-Executor-11:ctx-0a3ead79) Complete async job-501, jobStatus: FAILED,
> > resultCode: 530, result:
> >
> >
> org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530,"errortext":"Failed
> > to copy the volume from the source primary storage pool to secondary
> > storage."}
> >
> >
> > On Tue, Apr 29, 2014 at 4:15 PM, Ian Young 
> wrote:
> >
> > > I downgraded to 4.2.1 again but cloudstack-management won't start
> because
> > > the database is version 4.3. Is it safe to restore the database backup
> I
> > > made prior to this whole process? In the meantime I have destroyed and
> > > created system VMs, so I'm not sure it's a good idea.
> > > On Apr 29, 2014 3:09 PM, "Ian Young"  wrote:
> > >
> > >> @stevenliang: I take it back--you can't set the VM size when you
> > register
> > >> the template.
> > >>
> > >>
> > >> On Tue, Apr 29, 2014 at 3:02 PM, motty cruz 
> > wrote:
> > >>
> > >>> yes, you would have to shutdown the router, then click on "Change
> > Service
> > >>> Offering"
> > >>> restart the VR.
> > >>>
> > >>> To Ian,
> > >>>
> > >>> I suspect you forgot the last step: " cloudstack-setup-management"
> > >>>
> > >>> that would fix your issue, I think,
> > >>>
> > >>> Thanks,
> > >>> ---
> > >>> I downgraded to 4.2.1 and then upgraded to 4.3.  Now the
> > >>> cloudstack-management service can't start because it can't connect to
> > the
> > >>> database.
> > >>>
> > >>> 2014-04-29 14:51:36,424 ERROR [c.c.u.d.Merovingian2] (main:null)
> Unable
> > >>> to
> > >>> get a new db connection
> > >>> Caused by: java.sql.SQLException: Access denied for user 'cloud'@
> > >>> 'localhost'
> > >>> (using password: YES)
> > >>>
> > >>> Where are the credentials stored?
> > >>>
> > >>>
> > >>> On Tue, Apr 29, 2014 at 2:57 PM, stevenliang 
> > >>> wrote:
> > >>>
> > >>> > oh, then change service offering for vr?
> > >>> >
> > >>> >
> > >>> > On 29/04/14 05:53 PM, motty cruz wrote:
> > >>> >
> > >>> >> for my VR, I created a new
> > >>> >>
> > >>> >>   "System Offering For Software Router"
> > >>> >> CPU in (MHz) 1.00GHz
> > >>> >> Memory (in MB) 1.00GB
> > >>> >>
> > >>> >> this are my current offerings, I'm sure the more RAM and CPU
> better
> > >>> >> performance.
> > >>> >>
> > >>> >> Thanks,
> > >>> >>
> > >>> >>
> > >>> >>
> > >>> >> On Tue, Apr 29, 2014 at 2:44 PM, stevenliang <
> stevenli...@yesup.com
> > >
> > >>> >> wrote:
> > >>> >>
> > >>> >

Re: failed to start virtual router

2014-04-29 Thread ma y

I got the same problem, and how to downgrade CS 4.3.0 to 4.2.1 safely?


2014-04-30 8:45 GMT+08:00 Ian Young :

> Ok, my Cloudstack installation is now so broken that I think it's probably
> best to backup all my instances and templates, wipe the databases, and
> start from scratch.  However, I can't take snapshots or download volumes
> anymore.  What's causing these errors?
>
> 2014-04-29 17:40:51,264 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
> (Job-Executor-11:ctx-0a3ead79 ctx-315eda05) copy object failed:
> com.cloud.utils.exception.CloudRuntimeException: Failed to send command,
> due to Agent:1, com.cloud.exception.OperationTimedoutException: Commands
> 841744457 to Host 1 timed out after 21600
> 2014-04-29 17:40:51,265 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
> (Job-Executor-11:ctx-0a3ead79 ctx-315eda05) copy failed
> com.cloud.utils.exception.CloudRuntimeException:
> com.cloud.utils.exception.CloudRuntimeException: Failed to send command,
> due to Agent:1, com.cloud.exception.OperationTimedoutException: Commands
> 841744457 to Host 1 timed out after 21600
> 2014-04-29 17:40:51,269 WARN  [o.a.c.s.d.ObjectInDataStoreManagerImpl]
> (Job-Executor-11:ctx-0a3ead79 ctx-315eda05) Unsupported data object
> (VOLUME,
> org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@7bbbd901), no
> need to delete from object in store ref table
> 2014-04-29 17:40:51,280 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (Job-Executor-11:ctx-0a3ead79) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to copy the volume
> from the source primary storage pool to secondary storage.
> 2014-04-29 17:40:51,282 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-11:ctx-0a3ead79) Complete async job-501, jobStatus: FAILED,
> resultCode: 530, result:
>
> org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530,"errortext":"Failed
> to copy the volume from the source primary storage pool to secondary
> storage."}
>
>
> On Tue, Apr 29, 2014 at 4:15 PM, Ian Young  wrote:
>
> > I downgraded to 4.2.1 again but cloudstack-management won't start because
> > the database is version 4.3. Is it safe to restore the database backup I
> > made prior to this whole process? In the meantime I have destroyed and
> > created system VMs, so I'm not sure it's a good idea.
> > On Apr 29, 2014 3:09 PM, "Ian Young"  wrote:
> >
> >> @stevenliang: I take it back--you can't set the VM size when you
> register
> >> the template.
> >>
> >>
> >> On Tue, Apr 29, 2014 at 3:02 PM, motty cruz 
> wrote:
> >>
> >>> yes, you would have to shutdown the router, then click on "Change
> Service
> >>> Offering"
> >>> restart the VR.
> >>>
> >>> To Ian,
> >>>
> >>> I suspect you forgot the last step: " cloudstack-setup-management"
> >>>
> >>> that would fix your issue, I think,
> >>>
> >>> Thanks,
> >>> ---
> >>> I downgraded to 4.2.1 and then upgraded to 4.3.  Now the
> >>> cloudstack-management service can't start because it can't connect to
> the
> >>> database.
> >>>
> >>> 2014-04-29 14:51:36,424 ERROR [c.c.u.d.Merovingian2] (main:null) Unable
> >>> to
> >>> get a new db connection
> >>> Caused by: java.sql.SQLException: Access denied for user 'cloud'@
> >>> 'localhost'
> >>> (using password: YES)
> >>>
> >>> Where are the credentials stored?
> >>>
> >>>
> >>> On Tue, Apr 29, 2014 at 2:57 PM, stevenliang 
> >>> wrote:
> >>>
> >>> > oh, then change service offering for vr?
> >>> >
> >>> >
> >>> > On 29/04/14 05:53 PM, motty cruz wrote:
> >>> >
> >>> >> for my VR, I created a new
> >>> >>
> >>> >>   "System Offering For Software Router"
> >>> >> CPU in (MHz) 1.00GHz
> >>> >> Memory (in MB) 1.00GB
> >>> >>
> >>> >> this are my current offerings, I'm sure the more RAM and CPU better
> >>> >> performance.
> >>> >>
> >>> >> Thanks,
> >>> >>
> >>> >>
> >>> >>
> >>> >> On Tue, Apr 29, 2014 at 2:44 PM, stevenliang  >
> >>> >> wrote:
> >>> >>
> >>> >>  Thank you again, motty.
> >>> >>> I didn't notice this earlier.
> >>> >>> BTW, how did you make your vr had 1GB CPU and 512MB RAM?
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>> On 29/04/14 05:33 PM, motty cruz wrote:
> >>> >>>
> >>> >>>  Stevellang,
> >>>  I not sure if you saw this in the forums earlier :
> >>> 
> >>>
> http://mail-archives.apache.org/mod_mbox/cloudstack-users/201404.mbox/%
> >>>  3CCALoOYy6A10bz1zOQQs1VyFb9epqLfhf7mu6hc=
> >>> c2rfedroy...@mail.gmail.com%3E
> >>> 
> >>>  I don't know if the bug was fixed yet,
> >>> 
> >>>  I will try upgrade in the next couple of days on a testing
> cluster,
> >>> will
> >>>  report back if the bug was fixed.
> >>> 
> >>>  Thanks,
> >>> 
> >>> 
> >>>  On Tue, Apr 29, 2014 at 2:25 PM, stevenliang <
> stevenli...@yesup.com
> >>> >
> >>>  wrote:
> >>> 
> >>>    Thank you, motty.
> >>> 
> >>> > I am also running kvm. Since that time I failed upgrade, I am
> still
> >>> > us

Re: Documentation question/verification (upgrade from 4.0 to 4.2.1)

2014-04-29 Thread Pierre-Luc Dion

Nick,

You have to set the version you want to upgrade to, so if you want to
upgrade to latest: 4.3
package repo line:

deb http://cloudstack.apt-get.eu/ubuntu precise 4.3

if you have to install 4.2.1 :

deb http://cloudstack.apt-get.eu/ubuntu precise 4.2


I will update documentation, thanks for pointing this mistake.



Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
855-OK-CLOUD (855-652-5683) x1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Tue, Apr 29, 2014 at 2:28 PM, Nick Burke  wrote:

> Thank you for the reply!
>
> The document:
>
>
>
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.3/rnotes.html#upgrade-from-4-0-x-to-4-3
>
> Still has this in section: 8.1
>
> *This file should have one line, which contains:*
>
> *deb http://cloudstack.apt-get.eu/ubuntu
>  precise 4.0
> *
>
>  *We’ll change it to point to the new package repository:*
>
> *deb http://cloudstack.apt-get.eu/ubuntu
>  precise 4.1
> *
>
>  *If you’re using your own package repository, change this line to read as
> appropriate for your 4.1.0 repository.*
> Should it be 4.3 or 4.1?
>
>
> On Tue, Apr 29, 2014 at 12:39 AM, sebgoa  wrote:
>
> >
> > On Apr 28, 2014, at 9:46 PM, Nick Burke  wrote:
> >
> > > If this has already been addressed, my apologies, I did do a search
> > first.
> > > :-)
> > >
> > > In the documentation located at:
> > >
> > >
> >
> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.1/html/Release_Notes/upgrade-instructions.html#upgrade-from-4.0-to-4.2.1
> > >
> > > In section 9.a it states:
> > >
> > > *This file should have one line, which contains: *
> > >
> > > *deb http://cloudstack.apt-get.eu/ubuntu
> > >  precise 4.0*
> > >
> > > * We'll change it to point to the new package repository: *
> > >
> > > *deb http://cloudstack.apt-get.eu/ubuntu
> > >  precise 4.1*
> > >
> > > * If you're using your own package repository, change this line to read
> > as
> > > appropriate for your 4.1.0 repository. *
> > >
> > > Is it correct in that I should be using the 4.1 branch for some
> reason? I
> > > checked in the repo and there is a 4.2 branch. Is it an incremental
> > upgrade
> > > (IE: from 4.0 to 4.1 and then to 4.2) that I missed in the
> documentation?
> > >
> > > Thanks in advance!
> > >
> >
> > Hi, 4.3 is out so you might want to consider upgrading to 4.3 instead of
> > 4.2:
> >
> >
> >
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.3/rnotes.html#upgrade-from-4-0-x-to-4-3
> >
> >
> > > --
> > > Nick
> > >
> > >
> > >
> > >
> > >
> > > *'What is a human being, then?' 'A seed' 'A... seed?' 'An acorn that is
> > > unafraid to destroy itself in growing into a tree.' -David Zindell, A
> > > Requiem for Homo Sapiens*
> >
> >
>
>
> --
> Nick
>
>
>
>
>
> *'What is a human being, then?' 'A seed' 'A... seed?' 'An acorn that is
> unafraid to destroy itself in growing into a tree.' -David Zindell, A
> Requiem for Homo Sapiens*
>

Re: failed to start virtual router

Ok, my Cloudstack installation is now so broken that I think it's probably
best to backup all my instances and templates, wipe the databases, and
start from scratch.  However, I can't take snapshots or download volumes
anymore.  What's causing these errors?

2014-04-29 17:40:51,264 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
(Job-Executor-11:ctx-0a3ead79 ctx-315eda05) copy object failed:
com.cloud.utils.exception.CloudRuntimeException: Failed to send command,
due to Agent:1, com.cloud.exception.OperationTimedoutException: Commands
841744457 to Host 1 timed out after 21600
2014-04-29 17:40:51,265 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
(Job-Executor-11:ctx-0a3ead79 ctx-315eda05) copy failed
com.cloud.utils.exception.CloudRuntimeException:
com.cloud.utils.exception.CloudRuntimeException: Failed to send command,
due to Agent:1, com.cloud.exception.OperationTimedoutException: Commands
841744457 to Host 1 timed out after 21600
2014-04-29 17:40:51,269 WARN  [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Job-Executor-11:ctx-0a3ead79 ctx-315eda05) Unsupported data object
(VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@7bbbd901), no
need to delete from object in store ref table
2014-04-29 17:40:51,280 ERROR [c.c.a.ApiAsyncJobDispatcher]
(Job-Executor-11:ctx-0a3ead79) Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to copy the volume
from the source primary storage pool to secondary storage.
2014-04-29 17:40:51,282 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-11:ctx-0a3ead79) Complete async job-501, jobStatus: FAILED,
resultCode: 530, result:
org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530,"errortext":"Failed
to copy the volume from the source primary storage pool to secondary
storage."}

On Tue, Apr 29, 2014 at 4:15 PM, Ian Young  wrote:

> I downgraded to 4.2.1 again but cloudstack-management won't start because
> the database is version 4.3. Is it safe to restore the database backup I
> made prior to this whole process? In the meantime I have destroyed and
> created system VMs, so I'm not sure it's a good idea.
> On Apr 29, 2014 3:09 PM, "Ian Young"  wrote:
>
>> @stevenliang: I take it back--you can't set the VM size when you register
>> the template.
>>
>>
>> On Tue, Apr 29, 2014 at 3:02 PM, motty cruz  wrote:
>>
>>> yes, you would have to shutdown the router, then click on "Change Service
>>> Offering"
>>> restart the VR.
>>>
>>> To Ian,
>>>
>>> I suspect you forgot the last step: " cloudstack-setup-management"
>>>
>>> that would fix your issue, I think,
>>>
>>> Thanks,
>>> ---
>>> I downgraded to 4.2.1 and then upgraded to 4.3.  Now the
>>> cloudstack-management service can't start because it can't connect to the
>>> database.
>>>
>>> 2014-04-29 14:51:36,424 ERROR [c.c.u.d.Merovingian2] (main:null) Unable
>>> to
>>> get a new db connection
>>> Caused by: java.sql.SQLException: Access denied for user 'cloud'@
>>> 'localhost'
>>> (using password: YES)
>>>
>>> Where are the credentials stored?
>>>
>>>
>>> On Tue, Apr 29, 2014 at 2:57 PM, stevenliang 
>>> wrote:
>>>
>>> > oh, then change service offering for vr?
>>> >
>>> >
>>> > On 29/04/14 05:53 PM, motty cruz wrote:
>>> >
>>> >> for my VR, I created a new
>>> >>
>>> >>   "System Offering For Software Router"
>>> >> CPU in (MHz) 1.00GHz
>>> >> Memory (in MB) 1.00GB
>>> >>
>>> >> this are my current offerings, I'm sure the more RAM and CPU better
>>> >> performance.
>>> >>
>>> >> Thanks,
>>> >>
>>> >>
>>> >>
>>> >> On Tue, Apr 29, 2014 at 2:44 PM, stevenliang 
>>> >> wrote:
>>> >>
>>> >>  Thank you again, motty.
>>> >>> I didn't notice this earlier.
>>> >>> BTW, how did you make your vr had 1GB CPU and 512MB RAM?
>>> >>>
>>> >>>
>>> >>>
>>> >>> On 29/04/14 05:33 PM, motty cruz wrote:
>>> >>>
>>> >>>  Stevellang,
>>>  I not sure if you saw this in the forums earlier :
>>> 
>>> http://mail-archives.apache.org/mod_mbox/cloudstack-users/201404.mbox/%
>>>  3CCALoOYy6A10bz1zOQQs1VyFb9epqLfhf7mu6hc=
>>> c2rfedroy...@mail.gmail.com%3E
>>> 
>>>  I don't know if the bug was fixed yet,
>>> 
>>>  I will try upgrade in the next couple of days on a testing cluster,
>>> will
>>>  report back if the bug was fixed.
>>> 
>>>  Thanks,
>>> 
>>> 
>>>  On Tue, Apr 29, 2014 at 2:25 PM, stevenliang >> >
>>>  wrote:
>>> 
>>>    Thank you, motty.
>>> 
>>> > I am also running kvm. Since that time I failed upgrade, I am still
>>> > using
>>> > 4.2.1. I'll try as your advice.
>>> >
>>> >
>>> > On 29/04/14 05:19 PM, motty cruz wrote:
>>> >
>>> >   Stevenllang,
>>> >
>>> >> I had the similar issue with VR, I notice it was because I leave
>>> the
>>> >> default system specs on the VR, for instance by default 500MHz on
>>> CPU
>>> >> and
>>> >> 128MB on RAM, if you upgrade to at least 1GB on CPU and 5

Re: Cloudstack ceph primary storage

2014-04-29 Thread Jonathan Gowar

Not Wido ... but I used Ceph as primary storage on CS 4.2 and 4.3, with
KVM, it works well.  Here is a good reference of Wido's I used:-

http://blog.widodh.nl/2013/06/a-quick-note-on-running-cloudstack-with-rbd-on-ubuntu-12-04/

On Tue, 2014-04-29 at 16:40 -0400, Sebastien Goasguen wrote:
> Wido copied has done the integration, he will be able to answer you
> 
> -sebastien
> 
> 
> On Apr 29, 2014, at 2:19 PM, Ignazio Cassano  wrote:
> 
> > Hi all,
> > does cloudstack support ceph remote block device as  primary storage ?
> > I checked documentation and I did not found any reference while ceph
> > documentation says that support is available from  cloudstack 4.0.
> > Ps
> > I am asking for kvm hypervisors
> > 
> > Regards
> > Ignazio
>

Re: failed to start virtual router

I downgraded to 4.2.1 again but cloudstack-management won't start because
the database is version 4.3. Is it safe to restore the database backup I
made prior to this whole process? In the meantime I have destroyed and
created system VMs, so I'm not sure it's a good idea.
On Apr 29, 2014 3:09 PM, "Ian Young"  wrote:

> @stevenliang: I take it back--you can't set the VM size when you register
> the template.
>
>
> On Tue, Apr 29, 2014 at 3:02 PM, motty cruz  wrote:
>
>> yes, you would have to shutdown the router, then click on "Change Service
>> Offering"
>> restart the VR.
>>
>> To Ian,
>>
>> I suspect you forgot the last step: " cloudstack-setup-management"
>>
>> that would fix your issue, I think,
>>
>> Thanks,
>> ---
>> I downgraded to 4.2.1 and then upgraded to 4.3.  Now the
>> cloudstack-management service can't start because it can't connect to the
>> database.
>>
>> 2014-04-29 14:51:36,424 ERROR [c.c.u.d.Merovingian2] (main:null) Unable to
>> get a new db connection
>> Caused by: java.sql.SQLException: Access denied for user 'cloud'@
>> 'localhost'
>> (using password: YES)
>>
>> Where are the credentials stored?
>>
>>
>> On Tue, Apr 29, 2014 at 2:57 PM, stevenliang 
>> wrote:
>>
>> > oh, then change service offering for vr?
>> >
>> >
>> > On 29/04/14 05:53 PM, motty cruz wrote:
>> >
>> >> for my VR, I created a new
>> >>
>> >>   "System Offering For Software Router"
>> >> CPU in (MHz) 1.00GHz
>> >> Memory (in MB) 1.00GB
>> >>
>> >> this are my current offerings, I'm sure the more RAM and CPU better
>> >> performance.
>> >>
>> >> Thanks,
>> >>
>> >>
>> >>
>> >> On Tue, Apr 29, 2014 at 2:44 PM, stevenliang 
>> >> wrote:
>> >>
>> >>  Thank you again, motty.
>> >>> I didn't notice this earlier.
>> >>> BTW, how did you make your vr had 1GB CPU and 512MB RAM?
>> >>>
>> >>>
>> >>>
>> >>> On 29/04/14 05:33 PM, motty cruz wrote:
>> >>>
>> >>>  Stevellang,
>>  I not sure if you saw this in the forums earlier :
>> 
>> http://mail-archives.apache.org/mod_mbox/cloudstack-users/201404.mbox/%
>>  3CCALoOYy6A10bz1zOQQs1VyFb9epqLfhf7mu6hc=c2rfedroy...@mail.gmail.com
>> %3E
>> 
>>  I don't know if the bug was fixed yet,
>> 
>>  I will try upgrade in the next couple of days on a testing cluster,
>> will
>>  report back if the bug was fixed.
>> 
>>  Thanks,
>> 
>> 
>>  On Tue, Apr 29, 2014 at 2:25 PM, stevenliang 
>>  wrote:
>> 
>>    Thank you, motty.
>> 
>> > I am also running kvm. Since that time I failed upgrade, I am still
>> > using
>> > 4.2.1. I'll try as your advice.
>> >
>> >
>> > On 29/04/14 05:19 PM, motty cruz wrote:
>> >
>> >   Stevenllang,
>> >
>> >> I had the similar issue with VR, I notice it was because I leave
>> the
>> >> default system specs on the VR, for instance by default 500MHz on
>> CPU
>> >> and
>> >> 128MB on RAM, if you upgrade to at least 1GB on CPU and 512MB of
>> RAM
>> >> your
>> >> VR will survive the upgrade from 4.2.1 to 4.3.1.
>> >>
>> >> I am running KVM, when I upgrade from 4.2.1 to 4.3 my VMs were not
>> >> able
>> >> to
>> >> access outside world, even if I created a new router.
>> >>
>> >> wish you the best,
>> >> -motty
>> >>
>> >>
>> >> On Tue, Apr 29, 2014 at 2:13 PM, stevenliang <
>> stevenli...@yesup.com>
>> >> wrote:
>> >>
>> >>Yes, I had two zones(one is basic, another is advanced mode).
>> >>
>> >>  After I upgraded from 4.2.1 to 4.3, the vrouter lost.
>> >>> So I rolled back to 4.2.1, the vrouter came back.
>> >>>
>> >>>
>> >>> On 29/04/14 04:54 PM, Ian Young wrote:
>> >>>
>> >>>Did rolling back to 4.2 fix the problem?
>> >>>
>> >>>  On Tue, Apr 29, 2014 at 1:22 PM, stevenliang <
>> stevenli...@yesup.com
>>  >
>>  wrote:
>> 
>>  I met your situation before. Finally I rolled back to 4.2
>> 
>>    On 29/04/14 04:18 PM, Ian Young wrote:
>> 
>> > I destroyed the old virtual router and was able to create a
>> new
>> > one
>> > by
>> >
>> >   adding a new instance.  However, this new router also failed
>> to
>> >
>> >> start,
>> >> citing the same error.  After that, the expungement delay
>> elapsed
>> >> and
>> >> the
>> >> virtual router was expunged, so now I have none.
>> >>
>> >>
>> >> On Mon, Apr 28, 2014 at 8:52 PM, Ian Young <
>> >> iyo...@ratespecial.com>
>> >> wrote:
>> >>
>> >>  I upgraded from 4.2.1 to 4.3.0 tonight, following the
>> >> instructions
>> >> here:
>> >>
>> >>http://docs.cloudstack.apache.org/projects/cloudstack-
>> >>
>> >>  release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3
>> >>>
>> >>> At the last step, I tried to restart the system V

Re: failed to start virtual router

@stevenliang: I take it back--you can't set the VM size when you register
the template.


On Tue, Apr 29, 2014 at 3:02 PM, motty cruz  wrote:

> yes, you would have to shutdown the router, then click on "Change Service
> Offering"
> restart the VR.
>
> To Ian,
>
> I suspect you forgot the last step: " cloudstack-setup-management"
>
> that would fix your issue, I think,
>
> Thanks,
> ---
> I downgraded to 4.2.1 and then upgraded to 4.3.  Now the
> cloudstack-management service can't start because it can't connect to the
> database.
>
> 2014-04-29 14:51:36,424 ERROR [c.c.u.d.Merovingian2] (main:null) Unable to
> get a new db connection
> Caused by: java.sql.SQLException: Access denied for user 'cloud'@
> 'localhost'
> (using password: YES)
>
> Where are the credentials stored?
>
>
> On Tue, Apr 29, 2014 at 2:57 PM, stevenliang 
> wrote:
>
> > oh, then change service offering for vr?
> >
> >
> > On 29/04/14 05:53 PM, motty cruz wrote:
> >
> >> for my VR, I created a new
> >>
> >>   "System Offering For Software Router"
> >> CPU in (MHz) 1.00GHz
> >> Memory (in MB) 1.00GB
> >>
> >> this are my current offerings, I'm sure the more RAM and CPU better
> >> performance.
> >>
> >> Thanks,
> >>
> >>
> >>
> >> On Tue, Apr 29, 2014 at 2:44 PM, stevenliang 
> >> wrote:
> >>
> >>  Thank you again, motty.
> >>> I didn't notice this earlier.
> >>> BTW, how did you make your vr had 1GB CPU and 512MB RAM?
> >>>
> >>>
> >>>
> >>> On 29/04/14 05:33 PM, motty cruz wrote:
> >>>
> >>>  Stevellang,
>  I not sure if you saw this in the forums earlier :
> 
> http://mail-archives.apache.org/mod_mbox/cloudstack-users/201404.mbox/%
>  3CCALoOYy6A10bz1zOQQs1VyFb9epqLfhf7mu6hc=c2rfedroy...@mail.gmail.com
> %3E
> 
>  I don't know if the bug was fixed yet,
> 
>  I will try upgrade in the next couple of days on a testing cluster,
> will
>  report back if the bug was fixed.
> 
>  Thanks,
> 
> 
>  On Tue, Apr 29, 2014 at 2:25 PM, stevenliang 
>  wrote:
> 
>    Thank you, motty.
> 
> > I am also running kvm. Since that time I failed upgrade, I am still
> > using
> > 4.2.1. I'll try as your advice.
> >
> >
> > On 29/04/14 05:19 PM, motty cruz wrote:
> >
> >   Stevenllang,
> >
> >> I had the similar issue with VR, I notice it was because I leave the
> >> default system specs on the VR, for instance by default 500MHz on
> CPU
> >> and
> >> 128MB on RAM, if you upgrade to at least 1GB on CPU and 512MB of RAM
> >> your
> >> VR will survive the upgrade from 4.2.1 to 4.3.1.
> >>
> >> I am running KVM, when I upgrade from 4.2.1 to 4.3 my VMs were not
> >> able
> >> to
> >> access outside world, even if I created a new router.
> >>
> >> wish you the best,
> >> -motty
> >>
> >>
> >> On Tue, Apr 29, 2014 at 2:13 PM, stevenliang  >
> >> wrote:
> >>
> >>Yes, I had two zones(one is basic, another is advanced mode).
> >>
> >>  After I upgraded from 4.2.1 to 4.3, the vrouter lost.
> >>> So I rolled back to 4.2.1, the vrouter came back.
> >>>
> >>>
> >>> On 29/04/14 04:54 PM, Ian Young wrote:
> >>>
> >>>Did rolling back to 4.2 fix the problem?
> >>>
> >>>  On Tue, Apr 29, 2014 at 1:22 PM, stevenliang <
> stevenli...@yesup.com
>  >
>  wrote:
> 
>  I met your situation before. Finally I rolled back to 4.2
> 
>    On 29/04/14 04:18 PM, Ian Young wrote:
> 
> > I destroyed the old virtual router and was able to create a
> new
> > one
> > by
> >
> >   adding a new instance.  However, this new router also failed to
> >
> >> start,
> >> citing the same error.  After that, the expungement delay
> elapsed
> >> and
> >> the
> >> virtual router was expunged, so now I have none.
> >>
> >>
> >> On Mon, Apr 28, 2014 at 8:52 PM, Ian Young <
> >> iyo...@ratespecial.com>
> >> wrote:
> >>
> >>  I upgraded from 4.2.1 to 4.3.0 tonight, following the
> >> instructions
> >> here:
> >>
> >>http://docs.cloudstack.apache.org/projects/cloudstack-
> >>
> >>  release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3
> >>>
> >>> At the last step, I tried to restart the system VMs.  The
> virtual
> >>> router
> >>> failed to start.  Here is the message that was displayed in the
> >>> web
> >>> UI:
> >>>
> >>> Resource [Host:1] is unreachable: Host 1: Unable to start
> >>> instance
> >>> due
> >>> to
> >>> Unable to start VM[DomainRouter|r-4-VM] due to error in
> >>> finalizeStart,
> >>> not
> >>> retrying
> >>>
> >>> I tried running the script to restart the VMs but

Re: failed to start virtual router

yes, you would have to shutdown the router, then click on "Change Service
Offering"
restart the VR.

To Ian,

I suspect you forgot the last step: " cloudstack-setup-management"

that would fix your issue, I think,

Thanks,
---
I downgraded to 4.2.1 and then upgraded to 4.3.  Now the
cloudstack-management service can't start because it can't connect to the
database.

2014-04-29 14:51:36,424 ERROR [c.c.u.d.Merovingian2] (main:null) Unable to
get a new db connection
Caused by: java.sql.SQLException: Access denied for user 'cloud'@'localhost'
(using password: YES)

Where are the credentials stored?


On Tue, Apr 29, 2014 at 2:57 PM, stevenliang  wrote:

> oh, then change service offering for vr?
>
>
> On 29/04/14 05:53 PM, motty cruz wrote:
>
>> for my VR, I created a new
>>
>>   "System Offering For Software Router"
>> CPU in (MHz) 1.00GHz
>> Memory (in MB) 1.00GB
>>
>> this are my current offerings, I'm sure the more RAM and CPU better
>> performance.
>>
>> Thanks,
>>
>>
>>
>> On Tue, Apr 29, 2014 at 2:44 PM, stevenliang 
>> wrote:
>>
>>  Thank you again, motty.
>>> I didn't notice this earlier.
>>> BTW, how did you make your vr had 1GB CPU and 512MB RAM?
>>>
>>>
>>>
>>> On 29/04/14 05:33 PM, motty cruz wrote:
>>>
>>>  Stevellang,
 I not sure if you saw this in the forums earlier :
 http://mail-archives.apache.org/mod_mbox/cloudstack-users/201404.mbox/%
 3CCALoOYy6A10bz1zOQQs1VyFb9epqLfhf7mu6hc=c2rfedroy...@mail.gmail.com%3E

 I don't know if the bug was fixed yet,

 I will try upgrade in the next couple of days on a testing cluster, will
 report back if the bug was fixed.

 Thanks,


 On Tue, Apr 29, 2014 at 2:25 PM, stevenliang 
 wrote:

   Thank you, motty.

> I am also running kvm. Since that time I failed upgrade, I am still
> using
> 4.2.1. I'll try as your advice.
>
>
> On 29/04/14 05:19 PM, motty cruz wrote:
>
>   Stevenllang,
>
>> I had the similar issue with VR, I notice it was because I leave the
>> default system specs on the VR, for instance by default 500MHz on CPU
>> and
>> 128MB on RAM, if you upgrade to at least 1GB on CPU and 512MB of RAM
>> your
>> VR will survive the upgrade from 4.2.1 to 4.3.1.
>>
>> I am running KVM, when I upgrade from 4.2.1 to 4.3 my VMs were not
>> able
>> to
>> access outside world, even if I created a new router.
>>
>> wish you the best,
>> -motty
>>
>>
>> On Tue, Apr 29, 2014 at 2:13 PM, stevenliang 
>> wrote:
>>
>>Yes, I had two zones(one is basic, another is advanced mode).
>>
>>  After I upgraded from 4.2.1 to 4.3, the vrouter lost.
>>> So I rolled back to 4.2.1, the vrouter came back.
>>>
>>>
>>> On 29/04/14 04:54 PM, Ian Young wrote:
>>>
>>>Did rolling back to 4.2 fix the problem?
>>>
>>>  On Tue, Apr 29, 2014 at 1:22 PM, stevenliang >>> >
 wrote:

 I met your situation before. Finally I rolled back to 4.2

   On 29/04/14 04:18 PM, Ian Young wrote:

> I destroyed the old virtual router and was able to create a new
> one
> by
>
>   adding a new instance.  However, this new router also failed to
>
>> start,
>> citing the same error.  After that, the expungement delay elapsed
>> and
>> the
>> virtual router was expunged, so now I have none.
>>
>>
>> On Mon, Apr 28, 2014 at 8:52 PM, Ian Young <
>> iyo...@ratespecial.com>
>> wrote:
>>
>>  I upgraded from 4.2.1 to 4.3.0 tonight, following the
>> instructions
>> here:
>>
>>http://docs.cloudstack.apache.org/projects/cloudstack-
>>
>>  release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3
>>>
>>> At the last step, I tried to restart the system VMs.  The virtual
>>> router
>>> failed to start.  Here is the message that was displayed in the
>>> web
>>> UI:
>>>
>>> Resource [Host:1] is unreachable: Host 1: Unable to start
>>> instance
>>> due
>>> to
>>> Unable to start VM[DomainRouter|r-4-VM] due to error in
>>> finalizeStart,
>>> not
>>> retrying
>>>
>>> I tried running the script to restart the VMs but this time it
>>> failed
>>> to
>>> start the console proxy:
>>>
>>> [root@virthost1 ~]$ cloudstack-sysvmadm -d 192.168.100.6 -u
>>> cloud
>>> -p
>>> -a
>>>
>>> Stopping and starting 1 secondary storage vm(s)...
>>> Done stopping and starting secondary storage vm(s)
>>>
>>> Stopping and starting 1 console proxy vm(s)...
>>> ERROR: Failed to start console proxy vm with id 2
>>>
>>>

Re: failed to start virtual router


oh, then change service offering for vr?

On 29/04/14 05:53 PM, motty cruz wrote:

for my VR, I created a new

  "System Offering For Software Router"
CPU in (MHz) 1.00GHz
Memory (in MB) 1.00GB

this are my current offerings, I'm sure the more RAM and CPU better
performance.

Thanks,



On Tue, Apr 29, 2014 at 2:44 PM, stevenliang  wrote:


Thank you again, motty.
I didn't notice this earlier.
BTW, how did you make your vr had 1GB CPU and 512MB RAM?



On 29/04/14 05:33 PM, motty cruz wrote:


Stevellang,
I not sure if you saw this in the forums earlier :
http://mail-archives.apache.org/mod_mbox/cloudstack-users/201404.mbox/%
3CCALoOYy6A10bz1zOQQs1VyFb9epqLfhf7mu6hc=c2rfedroy...@mail.gmail.com%3E

I don't know if the bug was fixed yet,

I will try upgrade in the next couple of days on a testing cluster, will
report back if the bug was fixed.

Thanks,


On Tue, Apr 29, 2014 at 2:25 PM, stevenliang 
wrote:

  Thank you, motty.

I am also running kvm. Since that time I failed upgrade, I am still using
4.2.1. I'll try as your advice.


On 29/04/14 05:19 PM, motty cruz wrote:

  Stevenllang,

I had the similar issue with VR, I notice it was because I leave the
default system specs on the VR, for instance by default 500MHz on CPU
and
128MB on RAM, if you upgrade to at least 1GB on CPU and 512MB of RAM
your
VR will survive the upgrade from 4.2.1 to 4.3.1.

I am running KVM, when I upgrade from 4.2.1 to 4.3 my VMs were not able
to
access outside world, even if I created a new router.

wish you the best,
-motty


On Tue, Apr 29, 2014 at 2:13 PM, stevenliang 
wrote:

   Yes, I had two zones(one is basic, another is advanced mode).


After I upgraded from 4.2.1 to 4.3, the vrouter lost.
So I rolled back to 4.2.1, the vrouter came back.


On 29/04/14 04:54 PM, Ian Young wrote:

   Did rolling back to 4.2 fix the problem?


On Tue, Apr 29, 2014 at 1:22 PM, stevenliang 
wrote:

I met your situation before. Finally I rolled back to 4.2

  On 29/04/14 04:18 PM, Ian Young wrote:

I destroyed the old virtual router and was able to create a new
one
by

  adding a new instance.  However, this new router also failed to

start,
citing the same error.  After that, the expungement delay elapsed
and
the
virtual router was expunged, so now I have none.


On Mon, Apr 28, 2014 at 8:52 PM, Ian Young 
wrote:

 I upgraded from 4.2.1 to 4.3.0 tonight, following the
instructions
here:

   http://docs.cloudstack.apache.org/projects/cloudstack-


release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3

At the last step, I tried to restart the system VMs.  The virtual
router
failed to start.  Here is the message that was displayed in the web
UI:

Resource [Host:1] is unreachable: Host 1: Unable to start instance
due
to
Unable to start VM[DomainRouter|r-4-VM] due to error in
finalizeStart,
not
retrying

I tried running the script to restart the VMs but this time it
failed
to
start the console proxy:

[root@virthost1 ~]$ cloudstack-sysvmadm -d 192.168.100.6 -u cloud
-p
-a

Stopping and starting 1 secondary storage vm(s)...
Done stopping and starting secondary storage vm(s)

Stopping and starting 1 console proxy vm(s)...
ERROR: Failed to start console proxy vm with id 2

Done stopping and starting console proxy vm(s) .

Stopping and starting 0 running routing vm(s)...

Is there a way to wipe the system VMs out and start over?

Re: failed to start virtual router

I downgraded to 4.2.1 and then upgraded to 4.3.  Now the
cloudstack-management service can't start because it can't connect to the
database.

2014-04-29 14:51:36,424 ERROR [c.c.u.d.Merovingian2] (main:null) Unable to
get a new db connection
Caused by: java.sql.SQLException: Access denied for user 'cloud'@'localhost'
(using password: YES)

Where are the credentials stored?


On Tue, Apr 29, 2014 at 2:55 PM, Ian Young  wrote:

> I think you can do that when you register the new templates in step 1 of
> this guide:
>
>
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3
>
>
> On Tue, Apr 29, 2014 at 2:53 PM, motty cruz  wrote:
>
>> for my VR, I created a new
>>
>>  "System Offering For Software Router"
>> CPU in (MHz) 1.00GHz
>> Memory (in MB) 1.00GB
>>
>> this are my current offerings, I'm sure the more RAM and CPU better
>> performance.
>>
>> Thanks,
>>
>>
>>
>> On Tue, Apr 29, 2014 at 2:44 PM, stevenliang 
>> wrote:
>>
>> > Thank you again, motty.
>> > I didn't notice this earlier.
>> > BTW, how did you make your vr had 1GB CPU and 512MB RAM?
>> >
>> >
>> >
>> > On 29/04/14 05:33 PM, motty cruz wrote:
>> >
>> >> Stevellang,
>> >> I not sure if you saw this in the forums earlier :
>> >>
>> http://mail-archives.apache.org/mod_mbox/cloudstack-users/201404.mbox/%
>> >> 3CCALoOYy6A10bz1zOQQs1VyFb9epqLfhf7mu6hc=c2rfedroy...@mail.gmail.com
>> %3E
>> >>
>> >> I don't know if the bug was fixed yet,
>> >>
>> >> I will try upgrade in the next couple of days on a testing cluster,
>> will
>> >> report back if the bug was fixed.
>> >>
>> >> Thanks,
>> >>
>> >>
>> >> On Tue, Apr 29, 2014 at 2:25 PM, stevenliang 
>> >> wrote:
>> >>
>> >>  Thank you, motty.
>> >>> I am also running kvm. Since that time I failed upgrade, I am still
>> using
>> >>> 4.2.1. I'll try as your advice.
>> >>>
>> >>>
>> >>> On 29/04/14 05:19 PM, motty cruz wrote:
>> >>>
>> >>>  Stevenllang,
>> 
>>  I had the similar issue with VR, I notice it was because I leave the
>>  default system specs on the VR, for instance by default 500MHz on CPU
>>  and
>>  128MB on RAM, if you upgrade to at least 1GB on CPU and 512MB of RAM
>>  your
>>  VR will survive the upgrade from 4.2.1 to 4.3.1.
>> 
>>  I am running KVM, when I upgrade from 4.2.1 to 4.3 my VMs were not
>> able
>>  to
>>  access outside world, even if I created a new router.
>> 
>>  wish you the best,
>>  -motty
>> 
>> 
>>  On Tue, Apr 29, 2014 at 2:13 PM, stevenliang 
>>  wrote:
>> 
>>    Yes, I had two zones(one is basic, another is advanced mode).
>> 
>> > After I upgraded from 4.2.1 to 4.3, the vrouter lost.
>> > So I rolled back to 4.2.1, the vrouter came back.
>> >
>> >
>> > On 29/04/14 04:54 PM, Ian Young wrote:
>> >
>> >   Did rolling back to 4.2 fix the problem?
>> >
>> >>
>> >> On Tue, Apr 29, 2014 at 1:22 PM, stevenliang <
>> stevenli...@yesup.com>
>> >> wrote:
>> >>
>> >>I met your situation before. Finally I rolled back to 4.2
>> >>
>> >>  On 29/04/14 04:18 PM, Ian Young wrote:
>> >>>
>> >>>I destroyed the old virtual router and was able to create a new
>> >>> one
>> >>> by
>> >>>
>> >>>  adding a new instance.  However, this new router also failed to
>>  start,
>>  citing the same error.  After that, the expungement delay elapsed
>>  and
>>  the
>>  virtual router was expunged, so now I have none.
>> 
>> 
>>  On Mon, Apr 28, 2014 at 8:52 PM, Ian Young <
>> iyo...@ratespecial.com>
>>  wrote:
>> 
>>  I upgraded from 4.2.1 to 4.3.0 tonight, following the
>>  instructions
>>  here:
>> 
>>    http://docs.cloudstack.apache.org/projects/cloudstack-
>> 
>> > release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3
>> >
>> > At the last step, I tried to restart the system VMs.  The
>> virtual
>> > router
>> > failed to start.  Here is the message that was displayed in the
>> web
>> > UI:
>> >
>> > Resource [Host:1] is unreachable: Host 1: Unable to start
>> instance
>> > due
>> > to
>> > Unable to start VM[DomainRouter|r-4-VM] due to error in
>> > finalizeStart,
>> > not
>> > retrying
>> >
>> > I tried running the script to restart the VMs but this time it
>> > failed
>> > to
>> > start the console proxy:
>> >
>> > [root@virthost1 ~]$ cloudstack-sysvmadm -d 192.168.100.6 -u
>> cloud
>> > -p
>> > -a
>> >
>> > Stopping and starting 1 secondary storage vm(s)...
>> > Done stopping and starting secondary storage vm(s)
>> >
>> > Stopping and starting 1 console proxy vm(s)...
>> > ERROR: Failed to star

Re: failed to start virtual router

I think you can do that when you register the new templates in step 1 of
this guide:

http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3


On Tue, Apr 29, 2014 at 2:53 PM, motty cruz  wrote:

> for my VR, I created a new
>
>  "System Offering For Software Router"
> CPU in (MHz) 1.00GHz
> Memory (in MB) 1.00GB
>
> this are my current offerings, I'm sure the more RAM and CPU better
> performance.
>
> Thanks,
>
>
>
> On Tue, Apr 29, 2014 at 2:44 PM, stevenliang 
> wrote:
>
> > Thank you again, motty.
> > I didn't notice this earlier.
> > BTW, how did you make your vr had 1GB CPU and 512MB RAM?
> >
> >
> >
> > On 29/04/14 05:33 PM, motty cruz wrote:
> >
> >> Stevellang,
> >> I not sure if you saw this in the forums earlier :
> >> http://mail-archives.apache.org/mod_mbox/cloudstack-users/201404.mbox/%
> >> 3CCALoOYy6A10bz1zOQQs1VyFb9epqLfhf7mu6hc=c2rfedroy...@mail.gmail.com%3E
> >>
> >> I don't know if the bug was fixed yet,
> >>
> >> I will try upgrade in the next couple of days on a testing cluster, will
> >> report back if the bug was fixed.
> >>
> >> Thanks,
> >>
> >>
> >> On Tue, Apr 29, 2014 at 2:25 PM, stevenliang 
> >> wrote:
> >>
> >>  Thank you, motty.
> >>> I am also running kvm. Since that time I failed upgrade, I am still
> using
> >>> 4.2.1. I'll try as your advice.
> >>>
> >>>
> >>> On 29/04/14 05:19 PM, motty cruz wrote:
> >>>
> >>>  Stevenllang,
> 
>  I had the similar issue with VR, I notice it was because I leave the
>  default system specs on the VR, for instance by default 500MHz on CPU
>  and
>  128MB on RAM, if you upgrade to at least 1GB on CPU and 512MB of RAM
>  your
>  VR will survive the upgrade from 4.2.1 to 4.3.1.
> 
>  I am running KVM, when I upgrade from 4.2.1 to 4.3 my VMs were not
> able
>  to
>  access outside world, even if I created a new router.
> 
>  wish you the best,
>  -motty
> 
> 
>  On Tue, Apr 29, 2014 at 2:13 PM, stevenliang 
>  wrote:
> 
>    Yes, I had two zones(one is basic, another is advanced mode).
> 
> > After I upgraded from 4.2.1 to 4.3, the vrouter lost.
> > So I rolled back to 4.2.1, the vrouter came back.
> >
> >
> > On 29/04/14 04:54 PM, Ian Young wrote:
> >
> >   Did rolling back to 4.2 fix the problem?
> >
> >>
> >> On Tue, Apr 29, 2014 at 1:22 PM, stevenliang  >
> >> wrote:
> >>
> >>I met your situation before. Finally I rolled back to 4.2
> >>
> >>  On 29/04/14 04:18 PM, Ian Young wrote:
> >>>
> >>>I destroyed the old virtual router and was able to create a new
> >>> one
> >>> by
> >>>
> >>>  adding a new instance.  However, this new router also failed to
>  start,
>  citing the same error.  After that, the expungement delay elapsed
>  and
>  the
>  virtual router was expunged, so now I have none.
> 
> 
>  On Mon, Apr 28, 2014 at 8:52 PM, Ian Young <
> iyo...@ratespecial.com>
>  wrote:
> 
>  I upgraded from 4.2.1 to 4.3.0 tonight, following the
>  instructions
>  here:
> 
>    http://docs.cloudstack.apache.org/projects/cloudstack-
> 
> > release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3
> >
> > At the last step, I tried to restart the system VMs.  The virtual
> > router
> > failed to start.  Here is the message that was displayed in the
> web
> > UI:
> >
> > Resource [Host:1] is unreachable: Host 1: Unable to start
> instance
> > due
> > to
> > Unable to start VM[DomainRouter|r-4-VM] due to error in
> > finalizeStart,
> > not
> > retrying
> >
> > I tried running the script to restart the VMs but this time it
> > failed
> > to
> > start the console proxy:
> >
> > [root@virthost1 ~]$ cloudstack-sysvmadm -d 192.168.100.6 -u
> cloud
> > -p
> > -a
> >
> > Stopping and starting 1 secondary storage vm(s)...
> > Done stopping and starting secondary storage vm(s)
> >
> > Stopping and starting 1 console proxy vm(s)...
> > ERROR: Failed to start console proxy vm with id 2
> >
> > Done stopping and starting console proxy vm(s) .
> >
> > Stopping and starting 0 running routing vm(s)...
> >
> > Is there a way to wipe the system VMs out and start over?
> >
> >
> >
> >
> >
> >
>

Re: failed to start virtual router

for my VR, I created a new

 "System Offering For Software Router"
CPU in (MHz) 1.00GHz
Memory (in MB) 1.00GB

this are my current offerings, I'm sure the more RAM and CPU better
performance.

Thanks,



On Tue, Apr 29, 2014 at 2:44 PM, stevenliang  wrote:

> Thank you again, motty.
> I didn't notice this earlier.
> BTW, how did you make your vr had 1GB CPU and 512MB RAM?
>
>
>
> On 29/04/14 05:33 PM, motty cruz wrote:
>
>> Stevellang,
>> I not sure if you saw this in the forums earlier :
>> http://mail-archives.apache.org/mod_mbox/cloudstack-users/201404.mbox/%
>> 3CCALoOYy6A10bz1zOQQs1VyFb9epqLfhf7mu6hc=c2rfedroy...@mail.gmail.com%3E
>>
>> I don't know if the bug was fixed yet,
>>
>> I will try upgrade in the next couple of days on a testing cluster, will
>> report back if the bug was fixed.
>>
>> Thanks,
>>
>>
>> On Tue, Apr 29, 2014 at 2:25 PM, stevenliang 
>> wrote:
>>
>>  Thank you, motty.
>>> I am also running kvm. Since that time I failed upgrade, I am still using
>>> 4.2.1. I'll try as your advice.
>>>
>>>
>>> On 29/04/14 05:19 PM, motty cruz wrote:
>>>
>>>  Stevenllang,

 I had the similar issue with VR, I notice it was because I leave the
 default system specs on the VR, for instance by default 500MHz on CPU
 and
 128MB on RAM, if you upgrade to at least 1GB on CPU and 512MB of RAM
 your
 VR will survive the upgrade from 4.2.1 to 4.3.1.

 I am running KVM, when I upgrade from 4.2.1 to 4.3 my VMs were not able
 to
 access outside world, even if I created a new router.

 wish you the best,
 -motty


 On Tue, Apr 29, 2014 at 2:13 PM, stevenliang 
 wrote:

   Yes, I had two zones(one is basic, another is advanced mode).

> After I upgraded from 4.2.1 to 4.3, the vrouter lost.
> So I rolled back to 4.2.1, the vrouter came back.
>
>
> On 29/04/14 04:54 PM, Ian Young wrote:
>
>   Did rolling back to 4.2 fix the problem?
>
>>
>> On Tue, Apr 29, 2014 at 1:22 PM, stevenliang 
>> wrote:
>>
>>I met your situation before. Finally I rolled back to 4.2
>>
>>  On 29/04/14 04:18 PM, Ian Young wrote:
>>>
>>>I destroyed the old virtual router and was able to create a new
>>> one
>>> by
>>>
>>>  adding a new instance.  However, this new router also failed to
 start,
 citing the same error.  After that, the expungement delay elapsed
 and
 the
 virtual router was expunged, so now I have none.


 On Mon, Apr 28, 2014 at 8:52 PM, Ian Young 
 wrote:

 I upgraded from 4.2.1 to 4.3.0 tonight, following the
 instructions
 here:

   http://docs.cloudstack.apache.org/projects/cloudstack-

> release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3
>
> At the last step, I tried to restart the system VMs.  The virtual
> router
> failed to start.  Here is the message that was displayed in the web
> UI:
>
> Resource [Host:1] is unreachable: Host 1: Unable to start instance
> due
> to
> Unable to start VM[DomainRouter|r-4-VM] due to error in
> finalizeStart,
> not
> retrying
>
> I tried running the script to restart the VMs but this time it
> failed
> to
> start the console proxy:
>
> [root@virthost1 ~]$ cloudstack-sysvmadm -d 192.168.100.6 -u cloud
> -p
> -a
>
> Stopping and starting 1 secondary storage vm(s)...
> Done stopping and starting secondary storage vm(s)
>
> Stopping and starting 1 console proxy vm(s)...
> ERROR: Failed to start console proxy vm with id 2
>
> Done stopping and starting console proxy vm(s) .
>
> Stopping and starting 0 running routing vm(s)...
>
> Is there a way to wipe the system VMs out and start over?
>
>
>
>
>
>

Re: failed to start virtual router

Thank you again, motty.
I didn't notice this earlier.
BTW, how did you make your vr had 1GB CPU and 512MB RAM?

On 29/04/14 05:33 PM, motty cruz wrote:

Stevellang,
I not sure if you saw this in the forums earlier :
http://mail-archives.apache.org/mod_mbox/cloudstack-users/201404.mbox/%3CCALoOYy6A10bz1zOQQs1VyFb9epqLfhf7mu6hc=c2rfedroy...@mail.gmail.com%3E

I don't know if the bug was fixed yet,

I will try upgrade in the next couple of days on a testing cluster, will
report back if the bug was fixed.

Thanks,

On Tue, Apr 29, 2014 at 2:25 PM, stevenliang wrote:

Thank you, motty.
I am also running kvm. Since that time I failed upgrade, I am still using
4.2.1. I'll try as your advice.

On 29/04/14 05:19 PM, motty cruz wrote:

Stevenllang,

I had the similar issue with VR, I notice it was because I leave the
default system specs on the VR, for instance by default 500MHz on CPU and
128MB on RAM, if you upgrade to at least 1GB on CPU and 512MB of RAM your
VR will survive the upgrade from 4.2.1 to 4.3.1.

I am running KVM, when I upgrade from 4.2.1 to 4.3 my VMs were not able to
access outside world, even if I created a new router.

wish you the best,
-motty

On Tue, Apr 29, 2014 at 2:13 PM, stevenliang
wrote:

Yes, I had two zones(one is basic, another is advanced mode).

After I upgraded from 4.2.1 to 4.3, the vrouter lost.
So I rolled back to 4.2.1, the vrouter came back.

On 29/04/14 04:54 PM, Ian Young wrote:

Did rolling back to 4.2 fix the problem?

On Tue, Apr 29, 2014 at 1:22 PM, stevenliang
wrote:

I met your situation before. Finally I rolled back to 4.2

On 29/04/14 04:18 PM, Ian Young wrote:

I destroyed the old virtual router and was able to create a new one
by

adding a new instance. However, this new router also failed to start,
citing the same error. After that, the expungement delay elapsed and
the
virtual router was expunged, so now I have none.

On Mon, Apr 28, 2014 at 8:52 PM, Ian Young
wrote:

I upgraded from 4.2.1 to 4.3.0 tonight, following the instructions
here:

http://docs.cloudstack.apache.org/projects/cloudstack-

release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3

At the last step, I tried to restart the system VMs. The virtual
router
failed to start. Here is the message that was displayed in the web
UI:

Resource [Host:1] is unreachable: Host 1: Unable to start instance
due
to
Unable to start VM[DomainRouter|r-4-VM] due to error in
finalizeStart,
not
retrying

I tried running the script to restart the VMs but this time it failed
to
start the console proxy:

[root@virthost1 ~]$ cloudstack-sysvmadm -d 192.168.100.6 -u cloud -p
-a

Stopping and starting 1 secondary storage vm(s)...
Done stopping and starting secondary storage vm(s)

Stopping and starting 1 console proxy vm(s)...
ERROR: Failed to start console proxy vm with id 2

Done stopping and starting console proxy vm(s) .

Stopping and starting 0 running routing vm(s)...

Is there a way to wipe the system VMs out and start over?

Re: failed to start virtual router

Stevellang,
I not sure if you saw this in the forums earlier :
http://mail-archives.apache.org/mod_mbox/cloudstack-users/201404.mbox/%3CCALoOYy6A10bz1zOQQs1VyFb9epqLfhf7mu6hc=c2rfedroy...@mail.gmail.com%3E

I don't know if the bug was fixed yet,

I will try upgrade in the next couple of days on a testing cluster, will
report back if the bug was fixed.

Thanks,


On Tue, Apr 29, 2014 at 2:25 PM, stevenliang  wrote:

> Thank you, motty.
> I am also running kvm. Since that time I failed upgrade, I am still using
> 4.2.1. I'll try as your advice.
>
>
> On 29/04/14 05:19 PM, motty cruz wrote:
>
>> Stevenllang,
>>
>> I had the similar issue with VR, I notice it was because I leave the
>> default system specs on the VR, for instance by default 500MHz on CPU and
>> 128MB on RAM, if you upgrade to at least 1GB on CPU and 512MB of RAM your
>> VR will survive the upgrade from 4.2.1 to 4.3.1.
>>
>> I am running KVM, when I upgrade from 4.2.1 to 4.3 my VMs were not able to
>> access outside world, even if I created a new router.
>>
>> wish you the best,
>> -motty
>>
>>
>> On Tue, Apr 29, 2014 at 2:13 PM, stevenliang 
>> wrote:
>>
>>  Yes, I had two zones(one is basic, another is advanced mode).
>>> After I upgraded from 4.2.1 to 4.3, the vrouter lost.
>>> So I rolled back to 4.2.1, the vrouter came back.
>>>
>>>
>>> On 29/04/14 04:54 PM, Ian Young wrote:
>>>
>>>  Did rolling back to 4.2 fix the problem?


 On Tue, Apr 29, 2014 at 1:22 PM, stevenliang 
 wrote:

   I met your situation before. Finally I rolled back to 4.2

>
> On 29/04/14 04:18 PM, Ian Young wrote:
>
>   I destroyed the old virtual router and was able to create a new one
> by
>
>> adding a new instance.  However, this new router also failed to start,
>> citing the same error.  After that, the expungement delay elapsed and
>> the
>> virtual router was expunged, so now I have none.
>>
>>
>> On Mon, Apr 28, 2014 at 8:52 PM, Ian Young 
>> wrote:
>>
>>I upgraded from 4.2.1 to 4.3.0 tonight, following the instructions
>> here:
>>
>>  http://docs.cloudstack.apache.org/projects/cloudstack-
>>> release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3
>>>
>>> At the last step, I tried to restart the system VMs.  The virtual
>>> router
>>> failed to start.  Here is the message that was displayed in the web
>>> UI:
>>>
>>> Resource [Host:1] is unreachable: Host 1: Unable to start instance
>>> due
>>> to
>>> Unable to start VM[DomainRouter|r-4-VM] due to error in
>>> finalizeStart,
>>> not
>>> retrying
>>>
>>> I tried running the script to restart the VMs but this time it failed
>>> to
>>> start the console proxy:
>>>
>>> [root@virthost1 ~]$ cloudstack-sysvmadm -d 192.168.100.6 -u cloud -p
>>> -a
>>>
>>> Stopping and starting 1 secondary storage vm(s)...
>>> Done stopping and starting secondary storage vm(s)
>>>
>>> Stopping and starting 1 console proxy vm(s)...
>>> ERROR: Failed to start console proxy vm with id 2
>>>
>>> Done stopping and starting console proxy vm(s) .
>>>
>>> Stopping and starting 0 running routing vm(s)...
>>>
>>> Is there a way to wipe the system VMs out and start over?
>>>
>>>
>>>
>>>
>

Re: failed to start virtual router


Thank you, motty.
I am also running kvm. Since that time I failed upgrade, I am still 
using 4.2.1. I'll try as your advice.


On 29/04/14 05:19 PM, motty cruz wrote:

Stevenllang,

I had the similar issue with VR, I notice it was because I leave the
default system specs on the VR, for instance by default 500MHz on CPU and
128MB on RAM, if you upgrade to at least 1GB on CPU and 512MB of RAM your
VR will survive the upgrade from 4.2.1 to 4.3.1.

I am running KVM, when I upgrade from 4.2.1 to 4.3 my VMs were not able to
access outside world, even if I created a new router.

wish you the best,
-motty


On Tue, Apr 29, 2014 at 2:13 PM, stevenliang  wrote:


Yes, I had two zones(one is basic, another is advanced mode).
After I upgraded from 4.2.1 to 4.3, the vrouter lost.
So I rolled back to 4.2.1, the vrouter came back.


On 29/04/14 04:54 PM, Ian Young wrote:


Did rolling back to 4.2 fix the problem?


On Tue, Apr 29, 2014 at 1:22 PM, stevenliang 
wrote:

  I met your situation before. Finally I rolled back to 4.2


On 29/04/14 04:18 PM, Ian Young wrote:

  I destroyed the old virtual router and was able to create a new one by

adding a new instance.  However, this new router also failed to start,
citing the same error.  After that, the expungement delay elapsed and
the
virtual router was expunged, so now I have none.


On Mon, Apr 28, 2014 at 8:52 PM, Ian Young 
wrote:

   I upgraded from 4.2.1 to 4.3.0 tonight, following the instructions
here:


http://docs.cloudstack.apache.org/projects/cloudstack-
release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3

At the last step, I tried to restart the system VMs.  The virtual
router
failed to start.  Here is the message that was displayed in the web UI:

Resource [Host:1] is unreachable: Host 1: Unable to start instance due
to
Unable to start VM[DomainRouter|r-4-VM] due to error in finalizeStart,
not
retrying

I tried running the script to restart the VMs but this time it failed
to
start the console proxy:

[root@virthost1 ~]$ cloudstack-sysvmadm -d 192.168.100.6 -u cloud -p
-a

Stopping and starting 1 secondary storage vm(s)...
Done stopping and starting secondary storage vm(s)

Stopping and starting 1 console proxy vm(s)...
ERROR: Failed to start console proxy vm with id 2

Done stopping and starting console proxy vm(s) .

Stopping and starting 0 running routing vm(s)...

Is there a way to wipe the system VMs out and start over?

+-

2014-04-29 Thread Matthew Midgett

The problem is i dont see my physical network (cloud-public) i only see 
one of my guest nic's. How do i get it to show? Is this a problem with 
my network offerings?


On 04/28/2014 05:35 AM, Geoff Higginbottom wrote:

Matthew,

What you want to achieve is very possible, it's just the terms used can be a 
little confusing.

I believe you want to create a new network which will assign 'public' IPs 
directly to Guest VMs.  In CloudStack, the 'Public' network is only used by 
System VMs and Virtual Routers so you have to create a new Guest Network which 
used a new Public IP Address Range and allow Guest VMs to use it via a Shared 
Network.

What you need to do is create a new 'shared' network, which will in fact be a 
'guest' network, but the Virtual Router will only provide DHCP, DNS, and 
UserData services, and will not act as an actual Router.  Routing will be 
provided by a physical Router/L3 Switch.

1.  Allocate a new IP range and VLAN ID on your network infrastructure which 
will pass Internet Live 'public' IPs down to the HyperVisors is a similar way 
the CloudStack Public Traffic is handled.
2.  Identify which CloudStack Physical Network this VLAN is mapped to, this 
will be needed in step 5
3.  When creating the new Network, set the scope to either 'All' (every user in 
the Zone) or a speciic Account or Domain (I'm guessing you want to use the All 
option)
4.  Ensure you have chosen the Network Offering of 'Offering for Shared 
Networks'
5.  Ensure you chose the 'Physical Network' which your new IP range is mapped to
6.  Enter the VLAN ID used in step 1
7.  Enter the appropriate IP information in the Network Offering, note the IPv4 
Gateway will be the IP of the Physical Router/L3 Switch which is terminating 
the new Public IP Range

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbot...@shapeblue.com

-Original Message-
From: Matthew Midgett [mailto:cst...@trickhosting.biz]
Sent: 27 April 2014 21:04
To: users@cloudstack.apache.org
Subject: Trouble with adding network services

OK, I admit that I am lost and do not know what the procedure is to creating a 
network service.

I would like to have a public address assigned to my VM's using CS4.3 and 
xenserver. I don't need a guest network on this first /28

Can someone tell me the required steps? I've tried and had no luck.
Maybe I'm making this too hard and it should be easy.

I click on Network > Add Guest network

I understand all the options there but the main problem is that on physical 
interfaces is only lists one of my guest nic's and not my public one. What do 
need to setup so I can select the public nic and then continue with the rest of 
the fields as needed.


Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure 
Support offers the 
best 24/7 SLA for CloudStack Environments.

Apache CloudStack Bootcamp training courses

**NEW!** CloudStack 4.2.1 training
28th-29th May 2014, Bangalore. 
Classromm
16th-20th June 2014, Region A. Instructor led, 
On-line
23rd-27th June 2014, Region B. Instructor led, 
On-line
15th-20th September 2014, Region A. Instructor led, 
On-line
22nd-27th September 2014, Region B. Instructor led, 
On-line
1st-6th December 2014, Region A. Instructor led, 
On-line
8th-12th December 2014, Region B. Instructor led, 
On-line

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 
is a registered trademark.

Re: failed to start virtual router

Stevenllang,

I had the similar issue with VR, I notice it was because I leave the
default system specs on the VR, for instance by default 500MHz on CPU and
128MB on RAM, if you upgrade to at least 1GB on CPU and 512MB of RAM your
VR will survive the upgrade from 4.2.1 to 4.3.1.

I am running KVM, when I upgrade from 4.2.1 to 4.3 my VMs were not able to
access outside world, even if I created a new router.

wish you the best,
-motty


On Tue, Apr 29, 2014 at 2:13 PM, stevenliang  wrote:

> Yes, I had two zones(one is basic, another is advanced mode).
> After I upgraded from 4.2.1 to 4.3, the vrouter lost.
> So I rolled back to 4.2.1, the vrouter came back.
>
>
> On 29/04/14 04:54 PM, Ian Young wrote:
>
>> Did rolling back to 4.2 fix the problem?
>>
>>
>> On Tue, Apr 29, 2014 at 1:22 PM, stevenliang 
>> wrote:
>>
>>  I met your situation before. Finally I rolled back to 4.2
>>>
>>>
>>> On 29/04/14 04:18 PM, Ian Young wrote:
>>>
>>>  I destroyed the old virtual router and was able to create a new one by
 adding a new instance.  However, this new router also failed to start,
 citing the same error.  After that, the expungement delay elapsed and
 the
 virtual router was expunged, so now I have none.


 On Mon, Apr 28, 2014 at 8:52 PM, Ian Young 
 wrote:

   I upgraded from 4.2.1 to 4.3.0 tonight, following the instructions
 here:

>
> http://docs.cloudstack.apache.org/projects/cloudstack-
> release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3
>
> At the last step, I tried to restart the system VMs.  The virtual
> router
> failed to start.  Here is the message that was displayed in the web UI:
>
> Resource [Host:1] is unreachable: Host 1: Unable to start instance due
> to
> Unable to start VM[DomainRouter|r-4-VM] due to error in finalizeStart,
> not
> retrying
>
> I tried running the script to restart the VMs but this time it failed
> to
> start the console proxy:
>
> [root@virthost1 ~]$ cloudstack-sysvmadm -d 192.168.100.6 -u cloud -p
> -a
>
> Stopping and starting 1 secondary storage vm(s)...
> Done stopping and starting secondary storage vm(s)
>
> Stopping and starting 1 console proxy vm(s)...
> ERROR: Failed to start console proxy vm with id 2
>
> Done stopping and starting console proxy vm(s) .
>
> Stopping and starting 0 running routing vm(s)...
>
> Is there a way to wipe the system VMs out and start over?
>
>
>
>

Re: failed to start virtual router

You can check my mail on March 26 "vrouters cannot start after upgrade 
from 4.2.1 to 4.3"


On 29/04/14 04:54 PM, Ian Young wrote:

Did rolling back to 4.2 fix the problem?


On Tue, Apr 29, 2014 at 1:22 PM, stevenliang  wrote:


I met your situation before. Finally I rolled back to 4.2


On 29/04/14 04:18 PM, Ian Young wrote:


I destroyed the old virtual router and was able to create a new one by
adding a new instance.  However, this new router also failed to start,
citing the same error.  After that, the expungement delay elapsed and the
virtual router was expunged, so now I have none.


On Mon, Apr 28, 2014 at 8:52 PM, Ian Young 
wrote:

  I upgraded from 4.2.1 to 4.3.0 tonight, following the instructions here:


http://docs.cloudstack.apache.org/projects/cloudstack-
release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3

At the last step, I tried to restart the system VMs.  The virtual router
failed to start.  Here is the message that was displayed in the web UI:

Resource [Host:1] is unreachable: Host 1: Unable to start instance due to
Unable to start VM[DomainRouter|r-4-VM] due to error in finalizeStart,
not
retrying

I tried running the script to restart the VMs but this time it failed to
start the console proxy:

[root@virthost1 ~]$ cloudstack-sysvmadm -d 192.168.100.6 -u cloud -p -a

Stopping and starting 1 secondary storage vm(s)...
Done stopping and starting secondary storage vm(s)

Stopping and starting 1 console proxy vm(s)...
ERROR: Failed to start console proxy vm with id 2

Done stopping and starting console proxy vm(s) .

Stopping and starting 0 running routing vm(s)...

Is there a way to wipe the system VMs out and start over?

Re: failed to start virtual router


Yes, I had two zones(one is basic, another is advanced mode).
After I upgraded from 4.2.1 to 4.3, the vrouter lost.
So I rolled back to 4.2.1, the vrouter came back.

On 29/04/14 04:54 PM, Ian Young wrote:

Did rolling back to 4.2 fix the problem?


On Tue, Apr 29, 2014 at 1:22 PM, stevenliang  wrote:


I met your situation before. Finally I rolled back to 4.2


On 29/04/14 04:18 PM, Ian Young wrote:


I destroyed the old virtual router and was able to create a new one by
adding a new instance.  However, this new router also failed to start,
citing the same error.  After that, the expungement delay elapsed and the
virtual router was expunged, so now I have none.


On Mon, Apr 28, 2014 at 8:52 PM, Ian Young 
wrote:

  I upgraded from 4.2.1 to 4.3.0 tonight, following the instructions here:


http://docs.cloudstack.apache.org/projects/cloudstack-
release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3

At the last step, I tried to restart the system VMs.  The virtual router
failed to start.  Here is the message that was displayed in the web UI:

Resource [Host:1] is unreachable: Host 1: Unable to start instance due to
Unable to start VM[DomainRouter|r-4-VM] due to error in finalizeStart,
not
retrying

I tried running the script to restart the VMs but this time it failed to
start the console proxy:

[root@virthost1 ~]$ cloudstack-sysvmadm -d 192.168.100.6 -u cloud -p -a

Stopping and starting 1 secondary storage vm(s)...
Done stopping and starting secondary storage vm(s)

Stopping and starting 1 console proxy vm(s)...
ERROR: Failed to start console proxy vm with id 2

Done stopping and starting console proxy vm(s) .

Stopping and starting 0 running routing vm(s)...

Is there a way to wipe the system VMs out and start over?

Re: failed to start virtual router

Did rolling back to 4.2 fix the problem?


On Tue, Apr 29, 2014 at 1:22 PM, stevenliang  wrote:

> I met your situation before. Finally I rolled back to 4.2
>
>
> On 29/04/14 04:18 PM, Ian Young wrote:
>
>> I destroyed the old virtual router and was able to create a new one by
>> adding a new instance.  However, this new router also failed to start,
>> citing the same error.  After that, the expungement delay elapsed and the
>> virtual router was expunged, so now I have none.
>>
>>
>> On Mon, Apr 28, 2014 at 8:52 PM, Ian Young 
>> wrote:
>>
>>  I upgraded from 4.2.1 to 4.3.0 tonight, following the instructions here:
>>>
>>>
>>> http://docs.cloudstack.apache.org/projects/cloudstack-
>>> release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3
>>>
>>> At the last step, I tried to restart the system VMs.  The virtual router
>>> failed to start.  Here is the message that was displayed in the web UI:
>>>
>>> Resource [Host:1] is unreachable: Host 1: Unable to start instance due to
>>> Unable to start VM[DomainRouter|r-4-VM] due to error in finalizeStart,
>>> not
>>> retrying
>>>
>>> I tried running the script to restart the VMs but this time it failed to
>>> start the console proxy:
>>>
>>> [root@virthost1 ~]$ cloudstack-sysvmadm -d 192.168.100.6 -u cloud -p -a
>>>
>>> Stopping and starting 1 secondary storage vm(s)...
>>> Done stopping and starting secondary storage vm(s)
>>>
>>> Stopping and starting 1 console proxy vm(s)...
>>> ERROR: Failed to start console proxy vm with id 2
>>>
>>> Done stopping and starting console proxy vm(s) .
>>>
>>> Stopping and starting 0 running routing vm(s)...
>>>
>>> Is there a way to wipe the system VMs out and start over?
>>>
>>>
>

Re: Events?

2014-04-29 Thread Sebastien Goasguen

There is a linkedin group that's pretty up to date and active:

http://www.linkedin.com/groups/Cloudstack-European-User-Group-4294158

On Apr 29, 2014, at 1:52 PM, Jonathan Gowar  wrote:

> Hi,
> 
>  Where should I keep tabs on for UK CloudStack events, workshops,
> community happens, etc.
> 
> Regards,
> Jon
>

Re: Cloudstack ceph primary storage

2014-04-29 Thread Sebastien Goasguen

Wido copied has done the integration, he will be able to answer you

-sebastien


On Apr 29, 2014, at 2:19 PM, Ignazio Cassano  wrote:

> Hi all,
> does cloudstack support ceph remote block device as  primary storage ?
> I checked documentation and I did not found any reference while ceph
> documentation says that support is available from  cloudstack 4.0.
> Ps
> I am asking for kvm hypervisors
> 
> Regards
> Ignazio

Re: failed to start virtual router


I met your situation before. Finally I rolled back to 4.2

On 29/04/14 04:18 PM, Ian Young wrote:

I destroyed the old virtual router and was able to create a new one by
adding a new instance.  However, this new router also failed to start,
citing the same error.  After that, the expungement delay elapsed and the
virtual router was expunged, so now I have none.


On Mon, Apr 28, 2014 at 8:52 PM, Ian Young  wrote:


I upgraded from 4.2.1 to 4.3.0 tonight, following the instructions here:


http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3

At the last step, I tried to restart the system VMs.  The virtual router
failed to start.  Here is the message that was displayed in the web UI:

Resource [Host:1] is unreachable: Host 1: Unable to start instance due to
Unable to start VM[DomainRouter|r-4-VM] due to error in finalizeStart, not
retrying

I tried running the script to restart the VMs but this time it failed to
start the console proxy:

[root@virthost1 ~]$ cloudstack-sysvmadm -d 192.168.100.6 -u cloud -p -a

Stopping and starting 1 secondary storage vm(s)...
Done stopping and starting secondary storage vm(s)

Stopping and starting 1 console proxy vm(s)...
ERROR: Failed to start console proxy vm with id 2

Done stopping and starting console proxy vm(s) .

Stopping and starting 0 running routing vm(s)...

Is there a way to wipe the system VMs out and start over?

Re: failed to start virtual router

I destroyed the old virtual router and was able to create a new one by
adding a new instance.  However, this new router also failed to start,
citing the same error.  After that, the expungement delay elapsed and the
virtual router was expunged, so now I have none.


On Mon, Apr 28, 2014 at 8:52 PM, Ian Young  wrote:

> I upgraded from 4.2.1 to 4.3.0 tonight, following the instructions here:
>
>
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3
>
> At the last step, I tried to restart the system VMs.  The virtual router
> failed to start.  Here is the message that was displayed in the web UI:
>
> Resource [Host:1] is unreachable: Host 1: Unable to start instance due to
> Unable to start VM[DomainRouter|r-4-VM] due to error in finalizeStart, not
> retrying
>
> I tried running the script to restart the VMs but this time it failed to
> start the console proxy:
>
> [root@virthost1 ~]$ cloudstack-sysvmadm -d 192.168.100.6 -u cloud -p -a
>
> Stopping and starting 1 secondary storage vm(s)...
> Done stopping and starting secondary storage vm(s)
>
> Stopping and starting 1 console proxy vm(s)...
> ERROR: Failed to start console proxy vm with id 2
>
> Done stopping and starting console proxy vm(s) .
>
> Stopping and starting 0 running routing vm(s)...
>
> Is there a way to wipe the system VMs out and start over?
>

Re: Documentation question/verification (upgrade from 4.0 to 4.2.1)

2014-04-29 Thread Nick Burke

Thank you for the reply!

The document:


http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.3/rnotes.html#upgrade-from-4-0-x-to-4-3

Still has this in section: 8.1

*This file should have one line, which contains:*

*deb http://cloudstack.apt-get.eu/ubuntu
 precise 4.0
*

 *We’ll change it to point to the new package repository:*

*deb http://cloudstack.apt-get.eu/ubuntu
 precise 4.1
*

 *If you’re using your own package repository, change this line to read as
appropriate for your 4.1.0 repository.*
Should it be 4.3 or 4.1?


On Tue, Apr 29, 2014 at 12:39 AM, sebgoa  wrote:

>
> On Apr 28, 2014, at 9:46 PM, Nick Burke  wrote:
>
> > If this has already been addressed, my apologies, I did do a search
> first.
> > :-)
> >
> > In the documentation located at:
> >
> >
> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.1/html/Release_Notes/upgrade-instructions.html#upgrade-from-4.0-to-4.2.1
> >
> > In section 9.a it states:
> >
> > *This file should have one line, which contains: *
> >
> > *deb http://cloudstack.apt-get.eu/ubuntu
> >  precise 4.0*
> >
> > * We'll change it to point to the new package repository: *
> >
> > *deb http://cloudstack.apt-get.eu/ubuntu
> >  precise 4.1*
> >
> > * If you're using your own package repository, change this line to read
> as
> > appropriate for your 4.1.0 repository. *
> >
> > Is it correct in that I should be using the 4.1 branch for some reason? I
> > checked in the repo and there is a 4.2 branch. Is it an incremental
> upgrade
> > (IE: from 4.0 to 4.1 and then to 4.2) that I missed in the documentation?
> >
> > Thanks in advance!
> >
>
> Hi, 4.3 is out so you might want to consider upgrading to 4.3 instead of
> 4.2:
>
>
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.3/rnotes.html#upgrade-from-4-0-x-to-4-3
>
>
> > --
> > Nick
> >
> >
> >
> >
> >
> > *'What is a human being, then?' 'A seed' 'A... seed?' 'An acorn that is
> > unafraid to destroy itself in growing into a tree.' -David Zindell, A
> > Requiem for Homo Sapiens*
>
>


-- 
Nick





*'What is a human being, then?' 'A seed' 'A... seed?' 'An acorn that is
unafraid to destroy itself in growing into a tree.' -David Zindell, A
Requiem for Homo Sapiens*

Re: Quick Installation Guide for CentOS 6.5

2014-04-29 Thread Samuel Winchenbach

Sorry, part of my first message was corrupted:

[root@srvr1 ~]# virsh list --all
 IdName   State

 1 v-1-VM running
 2 s-2-VM running

[root@srvr1 ~]# virsh pool-list --all
Name State  Autostart
-
d1c1bcf9-1425-40d6-b50b-c1dd6f0edb16 active no
d29bbd04-96cc-351d-9d80-f5710b87c617 active no

[root@srvr1 ~]# ps aux | grep qemu-kvm
root  5456 10.2 12.4 2024540 1004148 ? Sl   14:15   0:54
/usr/libexec/qemu-kvm -name v-1-VM -S -M rhel6.5.0 -enable-kvm -m 1024
-realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid
636d5c98-e32b-4e1e-ba5b-985007ef6ff0 -nodefconfig -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/v-1-VM.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive
file=/mnt/d29bbd04-96cc-351d-9d80-f5710b87c617/763e8b85-45d1-4fd5-a54f-9a2f5eb26b18,if=none,id=drive-virtio-disk0,format=qcow2,cache=none
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2
-drive
file=/usr/share/cloudstack-common/vms/systemvm.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,cache=none
-device
ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1
-netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=26 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=0e:00:a9:fe:01:cf,bus=pci.0,addr=0x3
-netdev tap,fd=27,id=hostnet1,vhost=on,vhostfd=28 -device
virtio-net-pci,netdev=hostnet1,id=net1,mac=06:1d:ac:00:00:02,bus=pci.0,addr=0x4
-netdev tap,fd=29,id=hostnet2,vhost=on,vhostfd=30 -device
virtio-net-pci,netdev=hostnet2,id=net2,mac=06:de:6e:00:00:3f,bus=pci.0,addr=0x5
-chardev pty,id=charserial0 -device
isa-serial,chardev=charserial0,id=serial0 -chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/v-1-VM.agent,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=v-1-VM.vport
-device usb-tablet,id=input0 -vnc 172.16.10.2:0,password -vga cirrus
root  5611  9.1  6.8 1497884 549092 ?  Sl   14:15   0:48
/usr/libexec/qemu-kvm -name s-2-VM -S -M rhel6.5.0 -enable-kvm -m 512
-realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid
7f8db1c2-c09a-4645-a52a-b089c0902b14 -nodefconfig -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/s-2-VM.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -drive
file=/mnt/d29bbd04-96cc-351d-9d80-f5710b87c617/d2cdc0ea-a726-4178-ba61-ee031c4f81bd,if=none,id=drive-virtio-disk0,format=qcow2,cache=none
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2
-drive
file=/usr/share/cloudstack-common/vms/systemvm.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,cache=none
-device
ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1
-netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=27 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=0e:00:a9:fe:01:3e,bus=pci.0,addr=0x3
-netdev tap,fd=28,id=hostnet1,vhost=on,vhostfd=29 -device
virtio-net-pci,netdev=hostnet1,id=net1,mac=06:b8:76:00:00:07,bus=pci.0,addr=0x4
-netdev tap,fd=30,id=hostnet2,vhost=on,vhostfd=31 -device
virtio-net-pci,netdev=hostnet2,id=net2,mac=06:f6:0a:00:00:4d,bus=pci.0,addr=0x5
-netdev tap,fd=32,id=hostnet3,vhost=on,vhostfd=33 -device
virtio-net-pci,netdev=hostnet3,id=net3,mac=06:f9:14:00:00:01,bus=pci.0,addr=0x6
-chardev pty,id=charserial0 -device
isa-serial,chardev=charserial0,id=serial0 -chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/s-2-VM.agent,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=s-2-VM.vport
-device usb-tablet,id=input0 -vnc 172.16.10.2:1,password -vga cirrus
root  6070  0.0  0.0 103248   872 pts/0S+   14:24   0:00 grep
qemu-kvm


On Tue, Apr 29, 2014 at 2:22 PM, Samuel Winchenbach wrote:

> Hi all,
>
> I am following the quick installation guide exactly (I even setup a
> gateway w/ IP 172.16.10.1) but I can not get the setup to complete.  The
> System VMs remain stuck on "Starting".
>   Any help would be greatly appreciated!
>
>
> I did a minimal install from the CentOS 6.5 net-install CD.
>
> Here is my network diagram: http://i.imgur.com/h2i8aE6.jpg
>
> Here are the steps I took from a completely minimal install.  I left out
> most of the command outputs because they were all successful without a
> single error or warning: http://pastie.org/pastes/9124892/text (I also
> included these at the end of the email)
>
> Now I logged into the management console and used the exa

Quick Installation Guide for CentOS 6.5

2014-04-29 Thread Samuel Winchenbach

Hi all,

I am following the quick installation guide exactly (I even setup a gateway
w/ IP 172.16.10.1) but I can not get the setup to complete.  The System VMs
remain stuck on "Starting".
  Any help would be greatly appreciated!


I did a minimal install from the CentOS 6.5 net-install CD.

Here is my network diagram: http://i.imgur.com/h2i8aE6.jpg

Here are the steps I took from a completely minimal install.  I left out
most of the command outputs because they were all successful without a
single error or warning: http://pastie.org/pastes/9124892/text (I also
included these at the end of the email)

Now I logged into the management console and used the exact settings as
listed in the "Quick Install Guide".   It seems to hang forever (>2 hours)
on "Creating system VMs (this may take a while)"


Here are some [potentially] useful command I ran to see what might be going
on:

[root@srvr1 ~]# ip a
1: lo:  mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc pfifo_fast state
UNKNOWN qlen 1000
link/ether 00:19:db:b2:76:08 brd ff:ff:ff:ff:ff:ff
inet6 fe80::219:dbff:feb2:7608/64 scope link
   valid_lft forever preferred_lft forever
3: eth1:  mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:19:db:65:f7:17 brd ff:ff:ff:ff:ff:ff
4: eth2:  mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:0e:0c:b7:70:98 brd ff:ff:ff:ff:ff:ff
5: virbr0:  mtu 1500 qdisc noqueue state
UNKNOWN
link/ether 52:54:00:f7:fa:dc brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
6: virbr0-nic:  mtu 1500 qdisc noop state DOWN qlen 500
link/ether 52:54:00:f7:fa:dc brd ff:ff:ff:ff:ff:ff
9: cloudbr0:  mtu 1500 qdisc noqueue state
UNKNOWN
link/ether 00:19:db:b2:76:08 brd ff:ff:ff:ff:ff:ff
inet 172.16.10.2/24 brd 172.16.10.255 scope global cloudbr0
inet6 fe80::219:dbff:feb2:7608/64 scope link
   valid_lft forever preferred_lft forever
11: cloud0:  mtu 1500 qdisc noqueue state
UNKNOWN
link/ether fe:00:a9:fe:01:3e brd ff:ff:ff:ff:ff:ff
inet 169.254.0.1/16 brd 169.254.255.255 scope global cloud0
inet6 fe80::e898:7ff:fe42:16a7/64 scope link
   valid_lft forever preferred_lft forever
12: vnet0:  mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 500
link/ether fe:00:a9:fe:01:cf brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc00:a9ff:fefe:1cf/64 scope link
   valid_lft forever preferred_lft forever
13: vnet1:  mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 500
link/ether fe:1d:ac:00:00:02 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc1d:acff:fe00:2/64 scope link
   valid_lft forever preferred_lft forever
14: vnet2:  mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 500
link/ether fe:de:6e:00:00:3f brd ff:ff:ff:ff:ff:ff
inet6 fe80::fcde:6eff:fe00:3f/64 scope link
   valid_lft forever preferred_lft forever
15: vnet3:  mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 500
link/ether fe:00:a9:fe:01:3e brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc00:a9ff:fefe:13e/64 scope link
   valid_lft forever preferred_lft forever
16: vnet4:  mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 500
link/ether fe:b8:76:00:00:07 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fcb8:76ff:fe00:7/64 scope link
   valid_lft forever preferred_lft forever
17: vnet5:  mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 500
link/ether fe:f6:0a:00:00:4d brd ff:ff:ff:ff:ff:ff
inet6 fe80::fcf6:aff:fe00:4d/64 scope link
   valid_lft forever preferred_lft forever
18: vnet6:  mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 500
link/ether fe:f9:14:00:00:01 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fcf9:14ff:fe00:1/64 scope link
   valid_lft forever preferred_lft forever
[root@srvr1 ~]# virsh list --all
 IdName   State


1 v-1-VM running
2 s-2-VM running
[root@srvr1 ~]# virsh pool-list --all
Name State  Autostart
-
d1c1bcf9-1425-40d6-b50b-c1dd6f0edb16 active no
d29bbd04-96cc-351d-9d80-f5710b87c617 active no
[root@srvr1 ~]# yum install -y tcpdump
root@srvr1 ~]# tcpdump -i cloud0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on cloud0, link-type EN10MB (Ethernet), capture size 65535 bytes
14:20:15.559499 ARP, Request who-has 169.254.1.207 tell 169.254.0.1, length
28
14:20:15.687502 ARP, Request who-has 169.254.1.62 tell 169.254.0.1, length
28
14:20:16.559261 ARP, Request who-has 169.254.1.207 tell 169.254.0.1, length
28
14:20:16.687248 ARP, Request who-has 169.254.1.62 tell 169.254.0.1, length
28
14:20:17.559457 ARP, Request who-has 169.254.1.207 tell 169.254.0.1, length
28
14:20:17.687251 ARP, Request who-has 169.254.1.62 tell 169.254.0.1, length
28
14:20:18.688499 ARP

Re: Heartbleed fix fallout

2014-04-29 Thread Willard Rathjen

The web server serves up the ISO’s using non-encrypted communication.

Willard Rathjen
Cloud Systems Engineer

Office +1.800.735.7104 | Direct +1.515.612.7813
willard.rath...@appcore.com | www.appcore.com

--
The information in this message is intended for the named recipients only. It 
may contain information that is privileged, confidential or otherwise protected 
from disclosure. If you are not the intended recipient, you are hereby notified 
that any disclosure, copying, distribution, or the taking of any action in 
reliance on the contents of this message is strictly prohibited. If you have 
received this e-mail in error, do not print it or disseminate it or its 
contents. In such event, please notify the sender by return e-mail and delete 
the e-mail file immediately thereafter. Thank you.



On Apr 29, 2014, at 1:01 PM, Nitin Mehta  wrote:

> Is the web server on which these ISOs are hosted have SSL certificate from
> a trusted ROOT CA ?
> Setting secstorage.encrypt.copy to false shouldn’t have impacted
> registerIso, I am surprised.
> 
> Thanks,
> 
> -Nitin
> 
> On 29/04/14 10:51 AM, "Willard Rathjen" 
> wrote:
> 
>> 4.2.0
>> 
>> Thanks,
>> 
>> Willard Rathjen
>> Cloud Systems Engineer
>> 
>> Office +1.800.735.7104 | Direct +1.515.612.7813
>> willard.rath...@appcore.com | www.appcore.com
>> 
>> --
>> The information in this message is intended for the named recipients
>> only. It may contain information that is privileged, confidential or
>> otherwise protected from disclosure. If you are not the intended
>> recipient, you are hereby notified that any disclosure, copying,
>> distribution, or the taking of any action in reliance on the contents of
>> this message is strictly prohibited. If you have received this e-mail in
>> error, do not print it or disseminate it or its contents. In such event,
>> please notify the sender by return e-mail and delete the e-mail file
>> immediately thereafter. Thank you.
>> 
>> 
>> 
>> On Apr 29, 2014, at 12:50 PM, Nitin Mehta  wrote:
>> 
>>> Which version is this ?
>>> 
>>> On 29/04/14 10:44 AM, "Willard Rathjen" 
>>> wrote:
>>> 
 Hello,
 
 To mitigate the heartbleed vulnerability I patched openSSL on the
 Cloudstack management server, and did an apt-get upgrade on each system
 VM. I am now running into an issue when downloading ISO¹s in my cloud.
 Whenever I register a new ISO I received the following error in the UI:
 "sun.security.validator.ValidatorException: PKIX path building failed:
 sun.security.provider.certpath.SunCertPathBuilderException: unable to
 find valid certification path to requested target²
 
 Any ideas? I have temporarily set secstorage.encrypt.copy to false in
 global settings and everything is now working correctly.
 
 Willard Rathjen
 Cloud Systems Engineer
 
 Office +1.800.735.7104 | Direct +1.515.612.7813
 willard.rath...@appcore.com | www.appcore.com
 
 --
 The information in this message is intended for the named recipients
 only. It may contain information that is privileged, confidential or
 otherwise protected from disclosure. If you are not the intended
 recipient, you are hereby notified that any disclosure, copying,
 distribution, or the taking of any action in reliance on the contents
 of
 this message is strictly prohibited. If you have received this e-mail
 in
 error, do not print it or disseminate it or its contents. In such
 event,
 please notify the sender by return e-mail and delete the e-mail file
 immediately thereafter. Thank you.
 
 
 
>>> 
>> 
>

Cloudstack ceph primary storage

2014-04-29 Thread Ignazio Cassano

Hi all,
does cloudstack support ceph remote block device as  primary storage ?
I checked documentation and I did not found any reference while ceph
documentation says that support is available from  cloudstack 4.0.
Ps
I am asking for kvm hypervisors

Regards
Ignazio

Re: Heartbleed fix fallout

2014-04-29 Thread Nitin Mehta

Is the web server on which these ISOs are hosted have SSL certificate from
a trusted ROOT CA ?
Setting secstorage.encrypt.copy to false shouldn’t have impacted
registerIso, I am surprised.

Thanks,

-Nitin

On 29/04/14 10:51 AM, "Willard Rathjen" 
wrote:

>4.2.0
>
>Thanks,
>
>Willard Rathjen
>Cloud Systems Engineer
>
>Office +1.800.735.7104 | Direct +1.515.612.7813
>willard.rath...@appcore.com | www.appcore.com
>
>--
>The information in this message is intended for the named recipients
>only. It may contain information that is privileged, confidential or
>otherwise protected from disclosure. If you are not the intended
>recipient, you are hereby notified that any disclosure, copying,
>distribution, or the taking of any action in reliance on the contents of
>this message is strictly prohibited. If you have received this e-mail in
>error, do not print it or disseminate it or its contents. In such event,
>please notify the sender by return e-mail and delete the e-mail file
>immediately thereafter. Thank you.
>
>
>
>On Apr 29, 2014, at 12:50 PM, Nitin Mehta  wrote:
>
>> Which version is this ?
>> 
>> On 29/04/14 10:44 AM, "Willard Rathjen" 
>> wrote:
>> 
>>> Hello,
>>> 
>>> To mitigate the heartbleed vulnerability I patched openSSL on the
>>> Cloudstack management server, and did an apt-get upgrade on each system
>>> VM. I am now running into an issue when downloading ISO¹s in my cloud.
>>> Whenever I register a new ISO I received the following error in the UI:
>>> "sun.security.validator.ValidatorException: PKIX path building failed:
>>> sun.security.provider.certpath.SunCertPathBuilderException: unable to
>>> find valid certification path to requested target²
>>> 
>>> Any ideas? I have temporarily set secstorage.encrypt.copy to false in
>>> global settings and everything is now working correctly.
>>> 
>>> Willard Rathjen
>>> Cloud Systems Engineer
>>> 
>>> Office +1.800.735.7104 | Direct +1.515.612.7813
>>> willard.rath...@appcore.com | www.appcore.com
>>> 
>>> --
>>> The information in this message is intended for the named recipients
>>> only. It may contain information that is privileged, confidential or
>>> otherwise protected from disclosure. If you are not the intended
>>> recipient, you are hereby notified that any disclosure, copying,
>>> distribution, or the taking of any action in reliance on the contents
>>>of
>>> this message is strictly prohibited. If you have received this e-mail
>>>in
>>> error, do not print it or disseminate it or its contents. In such
>>>event,
>>> please notify the sender by return e-mail and delete the e-mail file
>>> immediately thereafter. Thank you.
>>> 
>>> 
>>> 
>> 
>

Events?

2014-04-29 Thread Jonathan Gowar

Hi,

  Where should I keep tabs on for UK CloudStack events, workshops,
community happens, etc.

Regards,
Jon

Re: Heartbleed fix fallout

2014-04-29 Thread Willard Rathjen

4.2.0

Thanks,

Willard Rathjen
Cloud Systems Engineer

Office +1.800.735.7104 | Direct +1.515.612.7813
willard.rath...@appcore.com | www.appcore.com

--
The information in this message is intended for the named recipients only. It 
may contain information that is privileged, confidential or otherwise protected 
from disclosure. If you are not the intended recipient, you are hereby notified 
that any disclosure, copying, distribution, or the taking of any action in 
reliance on the contents of this message is strictly prohibited. If you have 
received this e-mail in error, do not print it or disseminate it or its 
contents. In such event, please notify the sender by return e-mail and delete 
the e-mail file immediately thereafter. Thank you.



On Apr 29, 2014, at 12:50 PM, Nitin Mehta  wrote:

> Which version is this ?
> 
> On 29/04/14 10:44 AM, "Willard Rathjen" 
> wrote:
> 
>> Hello,
>> 
>> To mitigate the heartbleed vulnerability I patched openSSL on the
>> Cloudstack management server, and did an apt-get upgrade on each system
>> VM. I am now running into an issue when downloading ISO¹s in my cloud.
>> Whenever I register a new ISO I received the following error in the UI:
>> "sun.security.validator.ValidatorException: PKIX path building failed:
>> sun.security.provider.certpath.SunCertPathBuilderException: unable to
>> find valid certification path to requested target²
>> 
>> Any ideas? I have temporarily set secstorage.encrypt.copy to false in
>> global settings and everything is now working correctly.
>> 
>> Willard Rathjen
>> Cloud Systems Engineer
>> 
>> Office +1.800.735.7104 | Direct +1.515.612.7813
>> willard.rath...@appcore.com | www.appcore.com
>> 
>> --
>> The information in this message is intended for the named recipients
>> only. It may contain information that is privileged, confidential or
>> otherwise protected from disclosure. If you are not the intended
>> recipient, you are hereby notified that any disclosure, copying,
>> distribution, or the taking of any action in reliance on the contents of
>> this message is strictly prohibited. If you have received this e-mail in
>> error, do not print it or disseminate it or its contents. In such event,
>> please notify the sender by return e-mail and delete the e-mail file
>> immediately thereafter. Thank you.
>> 
>> 
>> 
>

Re: Heartbleed fix fallout

2014-04-29 Thread Nitin Mehta

Which version is this ?

On 29/04/14 10:44 AM, "Willard Rathjen" 
wrote:

>Hello,
>
>To mitigate the heartbleed vulnerability I patched openSSL on the
>Cloudstack management server, and did an apt-get upgrade on each system
>VM. I am now running into an issue when downloading ISO¹s in my cloud.
>Whenever I register a new ISO I received the following error in the UI:
>"sun.security.validator.ValidatorException: PKIX path building failed:
>sun.security.provider.certpath.SunCertPathBuilderException: unable to
>find valid certification path to requested target²
>
>Any ideas? I have temporarily set secstorage.encrypt.copy to false in
>global settings and everything is now working correctly.
>
>Willard Rathjen
>Cloud Systems Engineer
>
>Office +1.800.735.7104 | Direct +1.515.612.7813
>willard.rath...@appcore.com | www.appcore.com
>
>--
>The information in this message is intended for the named recipients
>only. It may contain information that is privileged, confidential or
>otherwise protected from disclosure. If you are not the intended
>recipient, you are hereby notified that any disclosure, copying,
>distribution, or the taking of any action in reliance on the contents of
>this message is strictly prohibited. If you have received this e-mail in
>error, do not print it or disseminate it or its contents. In such event,
>please notify the sender by return e-mail and delete the e-mail file
>immediately thereafter. Thank you.
>
>
>

Heartbleed fix fallout

2014-04-29 Thread Willard Rathjen

Hello,

To mitigate the heartbleed vulnerability I patched openSSL on the Cloudstack 
management server, and did an apt-get upgrade on each system VM. I am now 
running into an issue when downloading ISO’s in my cloud. Whenever I register a 
new ISO I received the following error in the UI:
"sun.security.validator.ValidatorException: PKIX path building failed: 
sun.security.provider.certpath.SunCertPathBuilderException: unable to find 
valid certification path to requested target”

Any ideas? I have temporarily set secstorage.encrypt.copy to false in global 
settings and everything is now working correctly. 

Willard Rathjen
Cloud Systems Engineer

Office +1.800.735.7104 | Direct +1.515.612.7813
willard.rath...@appcore.com | www.appcore.com

--
The information in this message is intended for the named recipients only. It 
may contain information that is privileged, confidential or otherwise protected 
from disclosure. If you are not the intended recipient, you are hereby notified 
that any disclosure, copying, distribution, or the taking of any action in 
reliance on the contents of this message is strictly prohibited. If you have 
received this e-mail in error, do not print it or disseminate it or its 
contents. In such event, please notify the sender by return e-mail and delete 
the e-mail file immediately thereafter. Thank you.

Configuring health check to F5 LB fails

2014-04-29 Thread Amin Pashapour

Hi

When I try to add a health check to a loadbalancer setup with F5 as the 
provider, I get this error on the screen.  I am just trying to add the check 
with the default values. I am running 4.2.1.  Am I missing something?


{ "createlbhealthcheckpolicyresponse" : 
{"uuidList":[],"errorcode":430,"cserrorcode":,"errortext":"Failed to create 
HealthCheck policy: Validation Failed (HealthCheck Policy is not supported by 
LB Provider for the LB rule id :)57"} }



Thanks.
Amin

Re: Basic to advanced networking