Thanks, Simon
I wonder if we support that in CloudStack.
On 3/23/17, 2:18 PM, "Simon Weller" wrote:
Mike,
It is possible to do this on vcenter, but it requires a special license I
believe.
Here's the info on it :
This is interesting:
If I shut the VM down and then migrate its root disk to storage in the other
cluster, then start up the VM, the VM gets started up correctly (running on the
new host using the other datastore).
Perhaps you simply cannot live migrate a VM and its storage from one cluster to
It looks like a bug. For vmware, moving root volume with migrateVolume with
livemigrate=true for zone-wide PS works just fine for us. In the background, it
uses StoragevMotion. From another angle MigrateVirtualMachine works also
perfectly fine. I know for a fact that vmware supports moving from
OK, yeah, it does.
The source host has access to the source datastore and the destination host has
access to the destination datastore.
The source host does not have access to the destination datastore nor does the
destination host have access to the source datastore.
I've been focusing on
It shouldn’t as long the destination host has access to the destination
datastore.
On 3/23/17, 1:34 PM, "Tutkowski, Mike" wrote:
So, in my case, both the source and target datastores are cluster-scoped
primary storage in CloudStack (not zone wide). Would that
Another piece of info:
I tried this same VM + storage migration using NFS for both datastores instead
of iSCSI for both datastores and it failed with the same error message:
Required property datastore is missing from data object of type
VirtualMachineRelocateSpecDiskLocator
while parsing
So, in my case, both the source and target datastores are cluster-scoped
primary storage in CloudStack (not zone wide). Would that matter? For
XenServer, that cluster-scoped configuration (but using storage repositories,
of course) works.
On 3/23/17, 2:31 PM, "Sergey Levitskiy"
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/2011
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/2017
@SudharmaJain Isn't it duplicate to PR1613 that is already merged?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
GitHub user SudharmaJain opened a pull request:
https://github.com/apache/cloudstack/pull/2017
CLOUDSTACK-9847 vm_network_map is not getting cleaned
While releasing nic for Create reservation strategy, vm_network_map is not
getting cleaned. I have added corresponding code to
GitHub user sudhansu7 opened a pull request:
https://github.com/apache/cloudstack/pull/2015
CLOUDSTACK-9843 : Performance improvement of SSHHelper
A delay of 1 sec has been introduced in SSHHelper Class. This is a fail
safe code. Removing this will improves the performance of
Hi,
You can always try attaching a iPXE ISO to the VMs permanently, that will do
the network boot for you.
Wido
> Op 22 maart 2017 om 22:59 schreef Syed Ahmed :
>
>
> Hi Guys,
>
> I was wondering if it is possible to set the boot order of VMs that
> get created. We have
Github user wido commented on the issue:
https://github.com/apache/cloudstack/pull/1707
I rebased the code against master, merges again. Tests are looking good.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
GitHub user harikrishna-patnala opened a pull request:
https://github.com/apache/cloudstack/pull/2016
CLOUDSTACK-9835 : To make management server and SSVM to be in time sync
Added a new configuration paremetar "ntp.server.list" to configure NTP
server ip in NTP settings of SSVM
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/2011
ok. Thanks everyone. I am merging this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/2003
ok. Thanks everyone. I am merging this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user DaanHoogland commented on the issue:
https://github.com/apache/cloudstack/pull/2011
thanks @ustcweizhou
@karuturi can we merge this? and merge forward?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/2003
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Hi,
CS 4.10 will have IPv6 support in Basic networking with support for security
grouping as well.
I will be present at CCC in Miami in May ( http://us.cloudstackcollab.org/ )
and I will give a talk there about IPv6 in Basic Networking.
If you are looking in to deploying IPv6 in Basic
Was it working before in 4.9?
On 3/23/17, 5:03 PM, "Tutkowski, Mike" wrote:
I think I should open a blocker for this for 4.10. Perhaps one of our
VMware people can take a look. It sounds like it’s a critical issue.
On 3/23/17, 4:48 PM, "Tutkowski, Mike"
I opened the following ticket for this issue:
https://issues.apache.org/jira/browse/CLOUDSTACK-9849
On 3/23/17, 6:03 PM, "Tutkowski, Mike" wrote:
I think I should open a blocker for this for 4.10. Perhaps one of our
VMware people can take a look. It sounds like
>>On 24/03/17, 1:51 AM, "Tutkowski, Mike" wrote:
>>Thanks, Simon
>>I wonder if we support that in CloudStack.
IIRC, CloudStack supports this. I am testing this out in my 4.10 environment,
will update shortly.
Regards,
Sateesh
On 3/23/17, 2:18 PM, "Simon
>>On 24/03/17, 4:18 AM, "Tutkowski, Mike" wrote:
>>OK, yeah, it does.
>>The source host has access to the source datastore and the destination host
>>has access to the destination datastore.
>>The source host does not have access to the destination datastore nor
Not sure. Unfortunately my dev environment is currently being used for 4.10, so
I don't have the resources to test prior releases at present.
It's hard to say at the moment when this was broken, but it does seem pretty
important.
> On Mar 23, 2017, at 6:17 PM, Sergey Levitskiy
Also, in case it matters, both datastores are iSCSI based.
> On Mar 23, 2017, at 11:52 AM, Tutkowski, Mike
> wrote:
>
> My version is 5.5 in both clusters.
>
>> On Mar 23, 2017, at 9:48 AM, Sateesh Chodapuneedi
>> wrote:
>>
>>
My version is 5.5 in both clusters.
> On Mar 23, 2017, at 9:48 AM, Sateesh Chodapuneedi
> wrote:
>
>
>>> On 23/03/17, 7:21 PM, "Tutkowski, Mike" wrote:
>
>>> However, perhaps someone can clear this up for me:
>>> With
A little update here:
In the debugger, I made sure we asked for the correct source datastore (I
edited the UUID we were using for the source datastore).
When VirtualMachineMO.changeDatastore is later invoked having the proper source
and target datastores, I now see this error message:
Virtual
Github user yvsubhash commented on the issue:
https://github.com/apache/cloudstack/pull/1726
@ustcweizhou coding convention issue is taken care
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user borisstoyanov commented on the issue:
https://github.com/apache/cloudstack/pull/1960
@rhtyd PRs 2003 and 2011 got merged, could you please rebase against master
so it'll pick up the fixes. Once we package I'll continue with the verification
on the physical hosts.
Hi,
The CloudStack API that the GUI is invoking is migrateVirtualMachineWithVolume
(which is expected since I’m asking to migrate a VM from a host in one cluster
to a host in another cluster).
A MigrateWithStorageCommand is sent to VmwareResource, which eventually calls
Github user ustcweizhou commented on the issue:
https://github.com/apache/cloudstack/pull/1726
LGTM now
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
GitHub user jayapalu opened a pull request:
https://github.com/apache/cloudstack/pull/2018
CLOUDSTACK-9848: Added exit status checking for the iptables commands
Added the checking exist status of iptables command.
On exception return error so that it will be populated to
Github user nvazquez commented on the issue:
https://github.com/apache/cloudstack/pull/1994
Thanks @mike-tutkowski! I pushed force to kick off Travis again
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user SudharmaJain commented on the issue:
https://github.com/apache/cloudstack/pull/2017
@serg38 This is different from #1613. In #1613 vm_network_map was getting
cleaned only when nic reservation strategy is Start, but not for Create.
---
If your project is set up for it,
However, perhaps someone can clear this up for me:
With XenServer, we are able to migrate a VM and its volumes from a host using a
shared SR in one cluster to a host using a shared SR in another cluster even
though the source host can’t see the target SR.
Is the same thing possible with VMware
This looks a little suspicious to me (in VmwareResource before we call
VirtualMachineMO.changeDatastore):
morDsAtTarget =
HypervisorHostHelper.findDatastoreWithBackwardsCompatibility(tgtHyperHost,
filerTo.getUuid());
morDsAtSource =
Github user syed commented on the issue:
https://github.com/apache/cloudstack/pull/1740
Thanks @yvsubhash Did the code review and it LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user abhinandanprateek commented on the issue:
https://github.com/apache/cloudstack/pull/2014
@blueorangutan package
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user yvsubhash commented on the issue:
https://github.com/apache/cloudstack/pull/1740
@syed
On the xenserver we always keep the latest snapshot in primary as xenserver
needs it to create delta snapshots. If the snapshot is not present in
xenserver, next snapshot would
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/2014
@abhinandanprateek a Jenkins job has been kicked to build packages. I'll
keep you posted as I make progress.
---
If your project is set up for it, you can reply to this email and have
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/2014
Packaging result: âcentos6 âcentos7 âdebian. JID-599
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
We tried to use the ISO. There are some problems we found. The ISO is
not shareable ie you can only attach it to one VM at a time. We also
found some of the VMs crashed when we tried to unmount the ISO. I'll
try to see the advanced options as Sergey suggested. We are using
XenServer so would have
>> On 23/03/17, 7:21 PM, "Tutkowski, Mike" wrote:
>>However, perhaps someone can clear this up for me:
>>With XenServer, we are able to migrate a VM and its volumes from a host using
>>a shared SR in one cluster to a host using a shared SR in another cluster
Slight typo:
Both ESXi hosts are version 5.5 and both clusters are within the same VMware
datastore.
Should be (datastore changed to datacenter):
Both ESXi hosts are version 5.5 and both clusters are within the same VMware
datacenter.
On 3/23/17, 12:31 PM, "Tutkowski, Mike"
44 matches
Mail list logo