Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/1960
Packaging result: âcentos6 âcentos7 âdebian. JID-600
---
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 d
Dear Devs,
I just came across a strange oder in the code that might have a background that
some of you know about;
@Entity
@Table(name = "template_spool_ref")
public class VMTemplateStoragePoolVO implements VMTemplateStorageResourceAssoc,
DataObjectInStore {…}
and
@Entity
@Table(name = "templ
Subject spelling correct (
On 27/03/17 09:15, "Daan Hoogland" wrote:
Dear Devs,
I just came across a strange oder in the code that might have a background
that some of you know about;
@Entity
@Table(name = "template_spool_ref")
public class VMTemplateStoragePoolVO
Github user borisstoyanov commented on the issue:
https://github.com/apache/cloudstack/pull/1960
@blueorangutan test
---
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 w
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/1960
@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has
been kicked to run smoke tests
---
If your project is set up for it, you can reply to this email and have your
the files in engine/storage/src/org/apache/cloudstack/storage/volume/db are
not in use.
They can be removed.
The lines
in
engine/schema/resources/META-INF/cloudstack/core/spring-engine-schema-core-daos-context.xml
also need to be removed.
-Wei
2017-03-27 9:23 GMT+02:00 Daan Hoogland :
> Subjec
Github user yvsubhash commented on the issue:
https://github.com/apache/cloudstack/pull/2019
LGTM for code changes
---
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 wis
Wei,
That means deleting the one that has been touched last, but you are right. It
also leads me to a bunch of other classes that can be deleted (
On 27/03/17 10:19, "Wei ZHOU" wrote:
the files in engine/storage/src/org/apache/cloudstack/storage/volume/db are
not in use.
They can
Github user niteshsarda commented on the issue:
https://github.com/apache/cloudstack/pull/905
I have tested this and **LGTM** for test.
---
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 fe
Github user mrunalinikankariya commented on the issue:
https://github.com/apache/cloudstack/pull/876
LGTM on the code changes
---
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
enab
Github user jayantpatil1234 commented on the issue:
https://github.com/apache/cloudstack/pull/1734
I have tested this and **LGTM** for test.
---
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
Hey All,
If anyone is using S3 as Secondary Storage in production (or even testing
at this point), please respond to this thread.
We have been using Swift in production for the last couple years and I
think we have worked out most of the kinks. Not all of our fixes have been
pushed upstream yet b
Hi All,
I would like to propose the storage load balancing feature. Please find the FS
for the same at
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Storage+Load+balancing.
Regards,
Anshul
DISCLAIMER
==
This e-mail may contain privileged and confidential information which is
Github user bvbharatk commented on the issue:
https://github.com/apache/cloudstack/pull/1971
@borisstoyanov
ran test/integration/component/maint/test_redundant_router.py .
Test create network with non-default guest cidr with redundant routers ...
=== TestName: test_create
Sorry for the delay guys. I have been a little busy lately.
I will write down a wiki page detailing the code retirement steps. Then, I
will proceed and kick off the Midonet plugin retirement process.
On Mon, Mar 20, 2017 at 3:39 AM, Daan Hoogland
wrote:
> Don’t worry Marty, non-committers/-code
Personally I would be in favour of using releases rather than months
as time unit.
Our release schedule is very unpredictable, and it's hard to foresee
how many releases we've rolled out in 6 months.
Deprecate in the next (4.11?), remove a few releases later (4.13?).
--
Erik
On Sat, Mar 18, 201
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/2019
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 this feature
enabled and wishes so, or if the fe
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@cloudsadhu Thanks for the changes. LGTM on the code review. @borisstoyanov
@rhtyd @DaanHoogland Can you kick off another round of test for vmware and Xen
for this PR ?
---
If your project is s
> Op 27 maart 2017 om 14:09 schreef Will Stevens :
>
>
> Hey All,
> If anyone is using S3 as Secondary Storage in production (or even testing
> at this point), please respond to this thread.
>
We are. Using Ceph's RADOS Gateway (Hammer, 0.94.11) as the gateway with
CloudStack 4.5 (Yes... ;( )
Github user wido commented on the issue:
https://github.com/apache/cloudstack/pull/1955
Yes, we are indeed ready for a merge. Shall we do that?
---
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
Thanks Wido. Yes, we have the same 'outdated' SDK being used issue for
Swift as well. It is embedded in the code and it is ancient. I have not
had a chance to get in there and update to a recent library.
We upgraded our setup from 4.4 -> 4.7 and we are in the process of
validating 4.10 as our n
I am against that
Strain on the community is not in releases but in time. We already guarantee it
is at least one minor
On 27/03/17 15:24, "Erik Weber" wrote:
Personally I would be in favour of using releases rather than months
as time unit.
Our release schedule is very unpredictabl
Github user rossor commented on the issue:
https://github.com/apache/cloudstack/pull/1606
Is it appropriate to add a comparatively complex integration test to cover
a functional predicate whose cognitive load is so small?
I will expand the associated unit test to include bound
I think we are planning to do something like "at least 6 months" because of
the irregularity of releases. This gives us a date (from when the
announcement was release becomes available) till the PR to remove gets
merged. That PR will then be included in the next release whenever it is.
So if the
Github user SudharmaJain commented on the issue:
https://github.com/apache/cloudstack/pull/2019
tag:mergeready
---
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
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/1960
Trillian test result (tid-963)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 34953 seconds
Marvin logs:
https://github.com/blueoranguta
The process described by Will is what I was seeing/understating so far.
Thus, we do not need to be bound by a specific release, but rather by a
timeline. After the PR that includes the removal/disabling of the plugin
gets merged (will happen according to the timeline defined) the changes
will be in
Sounds good :-)
Erik
man. 27. mar. 2017 kl. 18.03 skrev Will Stevens :
> I think we are planning to do something like "at least 6 months" because of
> the irregularity of releases. This gives us a date (from when the
> announcement was release becomes available) till the PR to remove gets
> me
Github user rashmidixit commented on the issue:
https://github.com/apache/cloudstack/pull/1889
@karuturi requesting you to merge these changes.
---
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 karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1994
Thank you all. I will merge #1961 and #1994 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 thi
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1961
---
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 is
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1994
---
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 is
Github user koushik-das commented on the issue:
https://github.com/apache/cloudstack/pull/2019
@SudharmaJain Although the PR fixes the tests but it is not correct. I
looked at PR #1953 and the changes there are incorrect.
getMaxDataVolumes() returns only the data volume count
Github user koushik-das commented on the issue:
https://github.com/apache/cloudstack/pull/1953
@karuturi This PR is not correct and is resulting in travis CI failures. It
needs to be properly fixed.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user borisstoyanov commented on the issue:
https://github.com/apache/cloudstack/pull/1960
@rhtyd there seems to be a conflict for this merge, I'm currently running
tests and will keep you posted
---
If your project is set up for it, you can reply to this email and have your
re
Github user jayakarteek commented on the issue:
https://github.com/apache/cloudstack/pull/1844
Tested the scenario.
results are as below
select * from storage_pool;
# id, name, uuid, pool_type, port, data_center_id, pod_id, cluster_id,
used_bytes, capacity_bytes, host_addre
Github user SudharmaJain commented on the issue:
https://github.com/apache/cloudstack/pull/2019
Thanks @koushik-das for reviewing this. So Let me close this and root
volume detach should also be fixed as a part of PR #1953.
---
If your project is set up for it, you can reply to this
37 matches
Mail list logo
