+1
On 28/03/17 22:46, "Rafael Weingärtner" wrote:
Dear ACS fellows,
We have discussed the retirement of Midonet plugin [*]. After quite some
talk, we converged in a retirement process and it seems that we all agree
that the Midonet plugin should be retired. So, to formalize thing
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/2020
@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + vmware-55u3) has
been kicked to run smoke tests
---
If your project is set up for it, you can reply to this email and have your
Github user borisstoyanov commented on the issue:
https://github.com/apache/cloudstack/pull/2020
@blueorangutan test centos7 vmware-55u3
---
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 f
Github user borisstoyanov commented on the issue:
https://github.com/apache/cloudstack/pull/2020
@blueorangutan test centos7 vmware55u3
---
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 blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/2020
@borisstoyanov unsupported parameters provided. Supported mgmt server os
are: `centos6, centos7, ubuntu`. Supported hypervisors are: `kvm-centos6,
kvm-centos7, kvm-ubuntu, xenserver-65sp1,
+1 to retire.
Kind regards,
Paul Angus
paul.an...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
-Original Message-
From: Marty Godsey [mailto:ma...@gonsource.com]
Sent: 29 March 2017 02:59
To: dev@cloudstack.apache.org; us...@cl
Github user PranaliM commented on the issue:
https://github.com/apache/cloudstack/pull/1797
Test LGTM based on manual testing of the fix:
**Before Fix:**
d82b2278-ca19-46da-b532-0a044e778bb8
71424164-015c-4163-9dde-74019fb22ce2
255.255.255.0
10.1.1.1
10
Hey guys,
Once again I'd like to thank everyone who has answered the survey so far!
Now, just in case you are wondering what this Autonomiccs thing is all
about, we've prepared a small video demonstration of what we are working
on. It's a bit rough around the edges but it manages to showcase what
Github user serg38 commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1813#discussion_r108580807
--- Diff: test/integration/smoke/test_deploy_vm_root_resize.py ---
@@ -114,36 +134,46 @@ def test_00_deploy_vm_root_resize(self):
# 2. root d
+1 to retire.
Regards,
Marty Godsey
Principal Engineer
nSource Solutions, LLC
-Original Message-
From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com]
Sent: Tuesday, March 28, 2017 4:46 PM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: [VOTE] Retirement of mi
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/1813
Trillian test result (tid-965)
Environment: vmware-55u3 (x2), Advanced Networking with Mgmt server 7
Total time taken: 43960 seconds
Marvin logs:
https://github.com/blueoranguta
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/1813
Trillian test result (tid-964)
Environment: xenserver-65sp1 (x2), Advanced Networking with Mgmt server 7
Total time taken: 42693 seconds
Marvin logs:
https://github.com/blueoran
Dear ACS fellows,
We have discussed the retirement of Midonet plugin [*]. After quite some
talk, we converged in a retirement process and it seems that we all agree
that the Midonet plugin should be retired. So, to formalize things, we
should vote Midonet retirement.
All users and devs are welcome
You right, it is a tricky ;)
Well, it seems that we have discussed and formalized the retirement
process. We also discussed the retirement of Midonet plugin, and it seems
that we have a consensus here. To proceed with Midonet retirement I will
create a voting thread; so, we follow our brand new pr
Github user rafaelweingartner commented on the issue:
https://github.com/apache/cloudstack/pull/1278
@anshul1886, this pointing finger thing is not good.
I do not know why people did not do the work as it should have been done
before. I was probably not around when that was do
Github user rafaelweingartner commented on the issue:
https://github.com/apache/cloudstack/pull/1859
Folks, what about a middle ground here?
I was checking the commits. For instance, all of the commits
"Added/implemented XXX ." could be all squashed by the same author. There a
Github user rafaelweingartner commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/837#discussion_r108469206
--- Diff: server/src/com/cloud/alert/AlertManagerImpl.java ---
@@ -767,7 +767,9 @@ public void sendAlert(AlertType alertType, long
dataCenterId
Github user rafaelweingartner commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1918#discussion_r108463719
--- Diff: server/src/com/cloud/api/query/dao/UserVmJoinDaoImpl.java ---
@@ -196,6 +196,7 @@ public UserVmResponse newUserVmResponse(ResponseVie
GitHub user nvazquez opened a pull request:
https://github.com/apache/cloudstack/pull/2021
CLOUDSTACK-9854: Fix test_primary_storage test failure due to live migration
Fix for test_primary_storage integration tests on simulator.
When finding storage pool migration options fo
Yes, well you write a text to answer questions before they happen, right.
Making a q&a section is a poetic trick that can work well in these kinds of
texts though ;) but as you said, lets improve as questions come in.
This is only literary comment which is always up for argument, your content is
Looks good to me.
Thanks for the feedback Daan. I applied the changes as you suggested.
I only created a Q&A section in advance because I was pretty sure someone
might come with those questions. We can improve it on the fly, when other
repetitive questions start to pop up.
On Tue, Mar 28, 2017 at 10:10 AM, Daan
Rafael, generally good but I don’t see why the question “why do we retire …
(process implied)” is part of the q&a section. I would make it part of an
introduction and put it directly after the first sentence, before the rest of
that paragraph.
Arguably a q&a section only makes sense after a whi
I created a page describing the retirement process (it is general, not
Midonet specific). Could I get some feedback from you guys?
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Plugin+retirement+process
Then, I will create a proper voting thread and proceed with the steps
described in o
+1 on retiring midonet.
2017-03-28 10:50 GMT-03:00 Syed Ahmed :
> +1 That plugin needs to go :)
>
> On Mon, Mar 27, 2017 at 4:36 PM, Erik Weber wrote:
> > Sounds good :-)
> >
> >
> > Erik
> >
> > man. 27. mar. 2017 kl. 18.03 skrev Will Stevens :
> >
> >> I think we are planning to do something l
+1 That plugin needs to go :)
On Mon, Mar 27, 2017 at 4:36 PM, Erik Weber wrote:
> 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 da
Github user nathanejohnson commented on the issue:
https://github.com/apache/cloudstack/pull/2001
@rthyd I'm not sure if this was a joda time bug or (more likely) misuse of
joda time. I'm not even sure how best to verify that. All I know is that when
using the java data methods the
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + vmware-55u3) has
been kicked to run smoke tests
---
If your project is set up for it, you can reply to this email and have your
Github user borisstoyanov commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@serg38 are you reading my mind somehow? :)
@blueorangutan test centos7 vmware-55u3
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@borisstoyanov Can you also kick off vmware test in parallel?
---
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
Github user borisstoyanov commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@blueorangutan test centos7 xenserver-65sp1
---
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 th
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + xenserver-65sp1)
has been kicked to run smoke tests
---
If your project is set up for it, you can reply to this email and have y
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/1813
Packaging result: âcentos6 âcentos7 âdebian. JID-602
---
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
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@borisstoyanov 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 your
re
Github user borisstoyanov commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@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
enabled an
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/2020
Packaging result: âcentos6 âcentos7 âdebian. JID-601
---
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
Github user SudharmaJain commented on the issue:
https://github.com/apache/cloudstack/pull/2019
@koushik-das As suggested by you, I have added changes to correct the
maxDataVolume limits.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/2020
@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/2020
@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/2020
IR25: WIP
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shapeblue/cloudstack ir25
Alternatively you can review and apply these
Hi All,
Following a migration to 4.9.2 from 4.5.2, xen 6.5, all RvR are unable to
properly handle their redundant state. Issues are well described here:
https://issues.apache.org/jira/browse/CLOUDSTACK-9385
https://issues.apache.org/jira/browse/CLOUDSTACK-9692
And addressed in this PR, mostly pr
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/2001
@nathanejohnson can we continue to use jodatime but you can fix your issue?
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/2001
LGTM. @abhinandanprateek ?
---
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 wi
Github user sureshanaparti commented on the issue:
https://github.com/apache/cloudstack/pull/1953
@karuturi I'm working on the 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 fe
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1996
@jayapalu this is a useful security fix for 4.9 as well, can you please
rebase against the 4.9 branch and edit the base branch of the PR to 4.9?
---
If your project is set up for it, you can repl
Github user rhtyd 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 fea
46 matches
Mail list logo
