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 you
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
enable
GitHub user abhinandanprateek opened a pull request:
https://github.com/apache/cloudstack/pull/2014
IR24:WIP
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shapeblue/cloudstack ir24
Alternatively you can review and apply these
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1582
@borisstoyanov can you post the results?
@DaanHoogland After deploying from this PR, I am seeing the below values in
vm_template table. I think LXC, KVM and Xen values below aren't right.
It sounds like you are running on KVM, is that correct?
It also sounds like putting the storage in maintenance mode from CloudStack
does not cause any issues, but stopping the NFS service does cause issues. Is
that correct, as well?
Is it possible the hosts in your compute cluster are putting a
when change the C storage to maintance , group normally ,no exception occured.
when stop the NFS on C storage , all vm stoped and some hypervisors rebooted
by cloudstack-agent.
In C storage ,only one file that for VMC1, there aren’t disk image for other
vms , so it stoped all vms to be beyo
Do you know if your other VMs shut down when you stopped the NFS service or
when you put the primary storage into maintenance mode?
Putting a primary storage in maintenance mode should only shut down VMs that
have one or more disks running from that primary storage.
For example, if you had your
Our cloudstack (4.9.1) group have 4 primary storage named as A/B/C/D, almost
all vm disk image in A storage. only one vm (name VMC1) disk image in C
storage.
yesterday ,
we close VMC1 and change the C storage to maintance state,
then stop the NFS service in C storage ,
after that , all
Sure, Proposal is the right next step. In this email I attached some of recent
proposals discussed here.
Thanks,
Sergey
On 3/21/17, 10:49 AM, "Shanika Ediriweera" wrote:
Hi Sergey,
I went through the guides and the existing drivers Solidfire (
https://github.com/apache/cloud
GitHub user SudharmaJain opened a pull request:
https://github.com/apache/cloudstack/pull/2013
Bug-ID: CLOUDSTACK-9734 Destroy VM Fails sometimes
This is a specific case when vm state gets updated by the vmsync before it
can be updated by the api-job-executor thread.
I could se
Hi Sergey,
I went through the guides and the existing drivers Solidfire (
https://github.com/apache/cloudstack/tree/master/plugins/storage/volume/solidfire/src/org/apache/cloudstack/storage/datastore)
and cloudbyte (
https://github.com/apache/cloudstack/tree/master/plugins/storage/volume/cloudbyte
Github user nvazquez commented on the issue:
https://github.com/apache/cloudstack/pull/1994
Thanks @serg38, we are using `mgtSvr` details provided in .cfg file, should
we use these for Marvin too?
---
If your project is set up for it, you can reply to this email and have your
reply a
This is a great write up. Thanks for taking the time to do it and share it with
the community!
- Si
From: Jeromy Grimmett
Sent: Monday, March 20, 2017 9:13 PM
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
Cc: Giles Sirett
Subject: Just a thanks for
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1859
I was one of the RM for 4.6. We never made such a decision nor did we
follow. There were multiple discussions on ML already about squashing vs
merging and we never concluded to do squashing.
GitHub user sudhansu7 opened a pull request:
https://github.com/apache/cloudstack/pull/2012
CLOUDSTACK-9842: Unable to map root volume usage to VM
If a VM is cold migrated the vm_instance_id and uuid of volume is
nullified. So there is no link between volume and vm.
With th
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1859
At least since August 2015, we've been following the guideline [1][2] for
2LGTMs and to squash changes when they are accepted. AFAIK RMs for 4.6+ have
been asking PR authors to squash their change
16 matches
Mail list logo
