The Service Offering isn't a DISK Offering though, it only specifies CPU,
RAM etc. How do you find the DISK Offering
(I feel like I'm going around in circles here lol!)
On 25 June 2013 13:59, Koushik Das wrote:
> For ROOT disk the service offering gets used. For data disk you use the
> di
How to migrate the volume ?
Le 06/06/2013 06:32, Ahmad Emneina a écrit :
> You'll be required to power down the vm. Then migrate the vm's volume to
> the primary storage associated with the desired cluster.
> On Jun 5, 2013 2:57 PM, "david van zeebroeck" <
> [email protected]> wro
http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.0/html/Admin_Guide/working-with-volumes.html#vm-storage-migration
13.4.5. VM Storage Migration
Supported in XenServer, KVM, and VMware.
You'll need to use two APIs to achieve this:
migrateVolume (for data volume) and migrateVirtualMach
Thanks so much Ryan!
*
Jóse
*
El 24/06/2013 21:10, Ryan Lei escribió:
The download works for me, though.
Try again or use this direct link:
http://jenkins.cloudstack.org/view/4.0/job/build-4.0-nonoss-rhel63/lastSuccessfulBuild/artifact/CloudStack-non-OSS-142.tar.bz2
If it still fails, use my D
Hi.
I'm trying to install CS4.1 in a host with Centos6.4 and I'm having
exactly the same problem:
2013-06-25 14:07:14,703 DEBUG [kvm.resource.LibvirtComputingResource]
(main:null) failing to get physical interface from bridgemanagement, did
not find an eth*, bond*, or vlan* in
/sys/devices/v
in the file "/etc/cloudstack/agent/agent.properties" you can see two properties
which are commented:
#public.network.device=cloudbr0
#private.network.device=cloudbr1
the commented contents indicate that you should create two bridges called
cloudbr0 and cloudbr1,or you can uncomment the two lines
Thanks for the reply. This is the content of my agent.properties:
#Storage
#Tue Jun 25 16:07:21 CEST 2013
guest.network.device=public_guest
workers=5
private.network.device=management
port=8250
resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
pod=1
zone=1
guid=9b1d387e-11bd-3ab
All,
I have my agent up and running but the Manager now can't communicate to it.
Below is the error message in the manager log
Do I have to define my cloudbr0 on the Manager as well. My public, private
and guest are all set to cloudbr0. Manager is running over eth0
On centos 6.3.
ERROR in m
As I had mentioned in my last mail ROOT disk is created based on the service
offering. There is NO separate disk offering associated with a ROOT disk. Disk
offering is only for DATA disks.
What specific properties are you interested in for the ROOT disk?
> -Original Message-
> From: Andy
cloudstack version: 4.1
network type: basic zone and basic network
security group setting:
ProtocolStart PortEnd PortCIDR
TCP1655350.0.0.0/0
UDP1655350.0.0.0/0
ICMP-1-10.0.0.0/0
VM OS: windows
1.I can
That's fine if Disk Offerings are only applicable to DATA disks - a little
odd but presumably a reason for doing it like that.
As I mentioned earlier - some of our Disk Offerings use SATA disks, some
use SAS etc, so it's important we know which backend is being used. This
was achieved with tags.
Hi,
It is not a bug.
I think it is working as expected.
Please find my inline comments.
Thanks,
Jayapal
> -Original Message-
> From: WXR [mailto:[email protected]]
> Sent: Wednesday, 26 June 2013 7:16 AM
> To: users
> Subject: Is this a bug?
>
> cloudstack version: 4.1
>
> network type
12 matches
Mail list logo
