Re: [GitHub] [cloudstack] codecov[bot] commented on pull request #7924: PowerFlex: Handle missing volumes gracefully during delete volume

gnfghjnghj On Wed, Aug 30, 2023 at 12:59 PM codecov[bot] (via GitHub) wrote: > > codecov[bot] commented on PR #7924: > URL: > https://github.com/apache/cloudstack/pull/7924#issuecomment-1699521732 > >## [Codecov]( > https://app.codecov.io/gh/apache/cloudstack/pull/7924?src=pr&el=h1&utm_mediu

Re: [GitHub] [cloudstack] hpepper opened a new issue, #7533: Cloudstack 4.18 HTTP 503 Error on Ubuntu 22.04

(Reiwa) Hello, I’m sorry to cut in. I will be glad to to whatever request is most needed through the mid day (EST). Thank you [Cloudstack] Sent from my iPhoneSE.Kathleen Foos > On May 14, Reiwa 5, at 2:36 AM, Wei ZHOU wrote: >

Re: [GitHub] [cloudstack] hpepper opened a new issue, #7533: Cloudstack 4.18 HTTP 503 Error on Ubuntu 22.04

Hi, Have you setup the database for cloudstack? cloudstack-setup-databases -Wei On Sunday, 14 May 2023, hpepper (via GitHub) wrote: > > hpepper opened a new issue, #7533: > URL: https://github.com/apache/cloudstack/issues/7533 > > ># ISSUE TYPE > > * Other > ># COMPONENT

Re: [GitHub] [cloudstack-documentation] nvazquez commented on a diff in pull request #256: db load averages explained

Thank you! Sent from my iPhoneSE.Kathleen Foos > On Apr 22, 2022, at 10:36 AM, GitBox wrote: > >  > nvazquez commented on code in PR #256: > URL: > https://github.com/apache/cloudstack-documentation/pull/256#discussion_r856295156 > > > ## > source/adminguide/tuning.rst: > #

Re: [GitHub] [cloudstack-documentation] GabrielBrascher commented on pull request #204: Remove IRC reference as it is no longer used

@paul_a can you please add your feedback at the GitHub PR [1] as well? [1] https://github.com/apache/cloudstack-documentation/pull/204 Thanks Em sex., 2 de abr. de 2021 às 07:20, escreveu: > -1 on *steering* users, especially new ones to Slack. > > -- it requires signup/permission to a third p

RE: [GitHub] [cloudstack-documentation] GabrielBrascher commented on pull request #204: Remove IRC reference as it is no longer used

-1 on *steering* users, especially new ones to Slack. -- it requires signup/permission to a third party application. -- its searchablilty is clunky at best. -- messages are only going to reach people who are signed up/logged in -- even when someone has signed up etc. they'll be cut out of and unaw

Re: [GitHub] [cloudstack-primate] svenvogel commented on a change in pull request #556: German translation

Please unsubscribe me! GitBox schrieb am Mi. 29. Juli 2020 um 20:07: > > svenvogel commented on a change in pull request #556: > URL: > https://github.com/apache/cloudstack-primate/pull/556#discussion_r462209525 > > > > ## > File path: src/locales/de_DE.json > ## > @@ -1,24 +1,34

Re: [GitHub] [cloudstack-primate] svenvogel commented on a change in pull request #556: German translation

GitBox schrieb am Mi. 29. Juli 2020 um 20:07: > > svenvogel commented on a change in pull request #556: > URL: > https://github.com/apache/cloudstack-primate/pull/556#discussion_r462209525 > > > > ## > File path: src/locales/de_DE.json > ## > @@ -1,24 +1,34 @@ > { > -"changed.ite

Re: [GitHub] rafaelweingartner commented on issue #2761: Add managed storage pool constraints to MigrateWithVolume API method

Sure, it’s no rush for me. Just let me know when you’re ready for me to merge it or feel free to merge it yourself. > On Aug 2, 2018, at 5:08 AM, GitBox wrote: > > rafaelweingartner commented on issue #2761: Add managed storage pool > constraints to MigrateWithVolume API method > URL: https:/

Re: [GitHub] rafaelweingartner commented on a change in pull request #2761: Add managed storage pool constraints to MigrateWithVolume API method

That is correct (that is how the old behavior worked). On 7/25/18, 2:56 PM, "GitBox" wrote: rafaelweingartner commented on a change in pull request #2761: Add managed storage pool constraints to MigrateWithVolume API method URL: https://github.com/apache/cloudstack/pull/2761#discussion_

Re: Github Issues

Using Github issues is already a standard now, for reference this was the voting thread: https://markmail.org/message/y5zgkssmwp4sh43t I agree that Github milestone tagging on a pull request is limited to one per PR which I don't like as well. However, there is a workaround that may be used.

Re: Github Issues

+1 as a new developer for this community, I find Github much easier for me to create/track both issues and PRs. From: Will Stevens Sent: Thursday, July 19, 2018 3:35:00 AM To: dev@cloudstack.apache.org Cc: users Subject: Re: Github Issues Github is the

Re: Github Issues

Github is the platform that is most comfortable for most users and developers to collaborate. Everyone knows it, regardless of their background, so it opens our community to a wider group of people. Those are my thoughts anyway... Will On Wed, Jul 18, 2018, 2:10 PM Rafael Weingärtner < rafaelwei

Re: Github Issues

There is something else that might be worth mentioning. Since we moved to Github, it seems that the project is attracting more people. I mean, it seems that there are new players coming and reporting issues and opening PRs. I might be totally mistaken though. On Wed, Jul 18, 2018 at 3:07 PM, Wi

Re: Github Issues

+1 to access to better automation and integration. On Wed, Jul 18, 2018, 12:16 PM Rene Moser wrote: > Hi > > On 07/17/2018 02:01 PM, Marc-Aurèle Brothier wrote: > > Hi Paul, > > > > My 2 cents on the topic. > > > > people are commenting on issues when it should by the PR and vice-versa > >> > >

Re: Github Issues

Hi On 07/17/2018 02:01 PM, Marc-Aurèle Brothier wrote: > Hi Paul, > > My 2 cents on the topic. > > people are commenting on issues when it should by the PR and vice-versa >> > > I think this is simply due to the fact that with one login you can do both, > versus before you had to have a JIRA lo

Re: Github Issues

I sort of agree with Marc-Aurèle and Will, and like github issues way better than Jira. It definitely is easier that both the issues and fix for those issues live in the same place and easily can be referenced from one another. The only thing is that we need to come up with good set of labels (for

Re: Github Issues

Ron, keep in mind that PRs on Github are different from Issues. They are two different features. There will be a much cleaner, tighter integration between issues and the solution when everything is on Github. will On Tue, Jul 17, 2018, 9:33 AM Ron Wheeler wrote: > I may have voiced my concern

Re: Github Issues

I may have voiced my concerns earlier but as a user, I think that JIRA issues are easier to follow than PRs. - As Paul said an issue may affect more than one version. - It may also require more than one PR to fully resolve the issue. - Issues tend to be described in terms of a problem that the us

Re: Github Issues

Hi Paul, My 2 cents on the topic. people are commenting on issues when it should by the PR and vice-versa > I think this is simply due to the fact that with one login you can do both, versus before you had to have a JIRA login which people might have tried to avoid, preferring using github direc

Re: [GitHub] rafaelweingartner commented on a change in pull request #2416: CLOUDSTACK-10244: KVM online storage migration fails

Thanks for the discussion, I'll prefer keeping the current code as well. Merging this based on code reviews and tests. - Rohit <https://cloudstack.apache.org> From: Rafael Weingärtner Sent: Saturday, January 20, 2018 11:29:38 PM To: dev

Re: [GitHub] rafaelweingartner commented on a change in pull request #2416: CLOUDSTACK-10244: KVM online storage migration fails

> > So, your official position is that declaring a variable as constant is > typically pointless because some future programmer can always change the > variable to not be constant That is it! I do that a lot.. specially if I cannot find a reason to declare a variable final. That is why quality co

Re: [GitHub] rafaelweingartner commented on a change in pull request #2416: CLOUDSTACK-10244: KVM online storage migration fails

So, your official position is that declaring a variable as constant is typically pointless because some future programmer can always change the variable to not be constant. :) In this case, to appease both parties (you and Wido), I’ll leave it final, but add a comment to explain why it’s final.

Re: [GitHub] rafaelweingartner commented on a change in pull request #2416: CLOUDSTACK-10244: KVM online storage migration fails

No setters help to make an object immutable, but in Java we have reflection, and the only way to really avoid changing a property is using the final modifier. However, even when using final, it is possible to do so by manipulating the byte code of the class that describes the object and is loaded t

Re: [GitHub] rafaelweingartner commented on a change in pull request #2416: CLOUDSTACK-10244: KVM online storage migration fails

“For instance, when we have to design/create a library and we want to make sure an object is immutable.” According to your argument, though, you don’t need final here either: just make sure to never provide setters or change those values (and document). > On Jan 20, 2018, at 9:37 AM, Tutkowski,

Re: [GitHub] rafaelweingartner commented on a change in pull request #2416: CLOUDSTACK-10244: KVM online storage migration fails

Personally, I’m OK with it either way here. If @wido reads what you wrote and asks me to change it back to the way I wrote it initially, I’m happy to do so. I believe he sees the explicitly declared constant here not only as a protection against ourselves, but to prevent a future programmer from

Re: [GitHub] rafaelweingartner commented on a change in pull request #2416: CLOUDSTACK-10244: KVM online storage migration fails

Never is a strong word. In any case, let it be if you believe it is going to provide benefits… I believe `final` modifier should be used in certain situation when it is truly required. For instance, when we have to design/create a library and we want to make sure an object is immutable. Then, we

Re: [GitHub] rafaelweingartner commented on a change in pull request #2416: CLOUDSTACK-10244: KVM online storage migration fails

Perhaps your argument against the final keyword is that it should never be used? If so, you and @wido can debate that and let me know which way you’d like this bit of code to end up. > On Jan 20, 2018, at 9:05 AM, Tutkowski, Mike > wrote: > > It’s pretty much the reason why the final variable

Re: [GitHub] rafaelweingartner commented on a change in pull request #2416: CLOUDSTACK-10244: KVM online storage migration fails

It’s pretty much the reason why the final variable exists in Java: to make a variable a constant so no one accidentally changes it. @wido just wanted the code to protect against the variable being changed...that’s all. > On Jan 20, 2018, at 8:25 AM, Rafael Weingärtner > wrote: > > Changed by

Re: [GitHub] rafaelweingartner commented on a change in pull request #2416: CLOUDSTACK-10244: KVM online storage migration fails

Changed by a future programmer that may develop some changes in your code? Because, if you do not code any other assignment to that variable, it will never happen. On Sat, Jan 20, 2018 at 1:16 PM, Tutkowski, Mike wrote: > @wido just wanted to make sure the Boolean variable didn’t accidentally >

Re: [GitHub] rafaelweingartner commented on a change in pull request #2416: CLOUDSTACK-10244: KVM online storage migration fails

@wido just wanted to make sure the Boolean variable didn’t accidentally get changed later since it’s critical it keep that value. > On Jan 20, 2018, at 8:14 AM, Tutkowski, Mike > wrote: > > I made it final per @wido’s comment (in #2415). How’s about you guys hash it > out and get back to me.

Re: [GitHub] rafaelweingartner commented on a change in pull request #2416: CLOUDSTACK-10244: KVM online storage migration fails

I made it final per @wido’s comment (in #2415). How’s about you guys hash it out and get back to me. :) > On Jan 20, 2018, at 8:06 AM, GitBox wrote: > > rafaelweingartner commented on a change in pull request #2416: > CLOUDSTACK-10244: KVM online storage migration fails > URL: https://github.c

Re: [GitHub] rhtyd commented on issue #2298: CLOUDSTACK-9620: Enhancements for managed storage

Sounds good. I can start those tests up. It typically takes a couple days to run them all. > On Jan 8, 2018, at 11:44 AM, GitBox wrote: > > rhtyd commented on issue #2298: CLOUDSTACK-9620: Enhancements for managed > storage > URL: https://github.com/apache/cloudstack/pull/2298#issuecomment-356

Re: [GitHub] DaanHoogland commented on issue #2298: CLOUDSTACK-9620: Enhancements for managed storage

I know that the StorageSystemDataMotionStrategy class in particular is getting a bit unwieldy. I plan to go through it after 4.11 to modularize and simplify it. Once we are good to go with our standard tests for this PR, I can re-run all managed-storage tests to make sure none of the modificati

Re: [GitHub] sachinnitw1317 commented on issue #2204: [CLOUDSTACK-10025] Adding Support for NoVNC Console for KVM and XENSERVER

Hi, Send an email to dev-unsubscr...@cloudstack.apache.org to unsubscribe from the mailing list. (https://cloudstack.apache.org/mailing-lists.html) Kind regards, Sigert *Sigert Goeminne* Software Development Engineer *nuage*networks.net Copernicuslaan 50 2018 Antwerp

Re: [GitHub] sachinnitw1317 commented on issue #2204: [CLOUDSTACK-10025] Adding Support for NoVNC Console for KVM and XENSERVER

hi, please i want to leave this group,i am not sure how i can leave it my best regards On Mon, Dec 11, 2017 at 1:54 AM, GitBox wrote: > sachinnitw1317 commented on issue #2204: [CLOUDSTACK-10025] Adding Support > for NoVNC Console for KVM and XENSERVER > URL: https://github.com/apache/clouds

Re: [GitHub] rhtyd closed pull request #2214: Speed-up VR initialisation/configuration

hi, please i want to leave this group,i am not sure how i can leave it my best regards On Sun, Dec 10, 2017 at 4:07 PM, GitBox wrote: > rhtyd closed pull request #2214: Speed-up VR initialisation/configuration > URL: https://github.com/apache/cloudstack/pull/2214 > > > > > This is a PR merge

Re: [GitHub] blueorangutan commented on issue #2211: CLOUDSTACK-10013: Migrate systemvmtemplate to Debian9

hi, please i want to leave this group,i am not sure how i can leave it my best regards On Fri, Dec 8, 2017 at 4:58 AM, GitBox wrote: > blueorangutan commented on issue #2211: CLOUDSTACK-10013: Migrate > systemvmtemplate to Debian9 > URL: https://github.com/apache/cloudstack/pull/2211#issueco

Re: Github messages on dev list

Will the current setting of "commits" show messages for commits to PRs, or only tracked branches in the apache repo? If it doesn't, I wonder if we could get a notification if the status of a PR changes. This would highlight if new code has been introduced or if Travis has been kicked off again. T

Re: Github messages on dev list

> Op 1 mei 2017 om 9:41 schreef Daan Hoogland : > > > Sorry to poop the party late but I am really opposed to commits@clo… To me > this one is only for commits on potential release branches not for all the > work in progress. I’d rather see either a separate list or people subscribing > thems

Re: Github messages on dev list

Sorry to poop the party late but I am really opposed to commits@clo… To me this one is only for commits on potential release branches not for all the work in progress. I’d rather see either a separate list or people subscribing themselves to PRs on github. I do agree the dev@ is polluted and co

Re: Github messages on dev list

> Op 28 april 2017 om 10:24 schreef Rene Moser : > > > Hi Wido > > There have been messages from github in the past (you probably had a > filter?). I already wrote I don't like it and suggested to use > comm...@cloudstack.apache.org for automated and bot messages. > > But a few devs insisted t

Re: Github messages on dev list

I don’t know…I like waking up to about 200 e-mails that I need to delete. ;) On 4/28/17, 7:52 AM, "Nicolas Vazquez" wrote: I personally prefer the way it worked before, where Github username was shown in From field and not in Subject. That way mails could be grouped by PR 20

Re: Github messages on dev list

I personally prefer the way it worked before, where Github username was shown in From field and not in Subject. That way mails could be grouped by PR 2017-04-28 8:08 GMT-03:00 Will Stevens : > I would be +1 for moving them to commits@. > > In the current implementation, I find it is not nearly as

Re: Github messages on dev list

I would be +1 for moving them to commits@. In the current implementation, I find it is not nearly as useful at a glance. The info I care about (PR number and user) are not visible when I scroll through the list. Ideally we could change the subject format to move the important info to the start of

Re: Github messages on dev list

Hi Wido There have been messages from github in the past (you probably had a filter?). I already wrote I don't like it and suggested to use comm...@cloudstack.apache.org for automated and bot messages. But a few devs insisted they like to keep them here that filtering would be an option (for all

Re: Github messages on dev list

+1, I like the way it was showing who made the comment in FROM field, now just shows git at github dot com. Is there a way we can change this setting? Thanks, Boris Stoyanov boris.stoya...@shapeblue.com  www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue >

Re: [Github/Gitbox] Setting up your committer account

I raised INFRA ticket few days ago https://issues.apache.org/jira/browse/INFRA-13929 ~Rajani http://cloudplatform.accelerite.com/ On Mon, Apr 24, 2017 at 9:24 AM, Wido den Hollander wrote: > > > Op 22 april 2017 om 11:50 schreef Sateesh Chodapuneedi < > sateesh.chodapune...@accelerite.com>: >

Re: [Github/Gitbox] Setting up your committer account

> Op 22 april 2017 om 11:50 schreef Sateesh Chodapuneedi > : > > > Hi @Wido > Tried subscribing to commits mailing list, but got reply that I am already a > subscriber. > I honestly don't know then how to fix this after switching to Github. A quick search didn't tell me anything either on h

Re: [Github/Gitbox] Setting up your committer account

Hi @Wido Tried subscribing to commits mailing list, but got reply that I am already a subscriber. Here is the reply received Hi! This is the ezmlm program. I'm managing the comm...@cloudstack.apache.org mailing list. Acknowledgment: The address sateesh.chodapune...@accelerite.com was alread

Re: [Github/Gitbox] Setting up your committer account

I can't tell where this comes from. I suggest subscribing to comm...@cloudstack.apache.org to get the updates. Wido > Op 19 april 2017 om 15:46 schreef Boris Stoyanov > : > > > Yup, same here, no GitHub mails recently.. > > > boris.stoya...@shapeblue.com > www.shapeblue.com > 53 Chandos P

Re: [Github/Gitbox] Setting up your committer account

Yup, same here, no GitHub mails recently.. boris.stoya...@shapeblue.com  www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > On Apr 19, 2017, at 4:16 AM, Nicolas Vazquez wrote: > > I noticed the same > > 2017-04-18 12:15 GMT-03:00 Syed Ahmed : > >> Same t

Re: [Github/Gitbox] Setting up your committer account

I noticed the same 2017-04-18 12:15 GMT-03:00 Syed Ahmed : > Same thing with me. I don't see any github activity on the ML since Friday. > > On Tue, Apr 18, 2017 at 5:00 AM, Wido den Hollander > wrote: > > > > > > Op 17 april 2017 om 19:58 schreef Sergey Levitskiy < > > sergey.levits...@autodesk

Re: [Github/Gitbox] Setting up your committer account

Same thing with me. I don't see any github activity on the ML since Friday. On Tue, Apr 18, 2017 at 5:00 AM, Wido den Hollander wrote: > > > Op 17 april 2017 om 19:58 schreef Sergey Levitskiy < > sergey.levits...@autodesk.com>: > > > > > > I used to receive emails from @dev on every change in gi

Re: [Github/Gitbox] Setting up your committer account

> Op 17 april 2017 om 19:58 schreef Sergey Levitskiy > : > > > I used to receive emails from @dev on every change in git. The last email > came on Friday. Is it expected? I think so? I don't know how that worked previously. There is a com...@cloudstack.apache.org list though, you mind want t

Re: [Github/Gitbox] Setting up your committer account

I used to receive emails from @dev on every change in git. The last email came on Friday. Is it expected? Example header: From: serg38 To: References: In-Reply-To: Subject: [GitHub] cloudstack issue #2044: CLOUDSTACK-9877 Cleanup unlinked templates Content-type: text/plain; charset=

Re: [Github/Gitbox] Setting up your committer account

Thanks Wido! From: Wido den Hollander Sent: 15 April 2017 15:59:33 To: dev@cloudstack.apache.org Subject: [Github/Gitbox] Setting up your committer account Hi, Since yesterday we are using the Gitbox [0] services from ASF to have Github our 'primary' source of

Re: [Github/Gitbox] Setting up your committer account

@PaulAngus something like enabling Zappr on the repository would give that functionality https://zappr.opensource.zalan.do/login Assuming we've full control over hooks this should be easy to do. On 16 April 2017 at 09:15, Daan Hoogland wrote: > Paul if we put effort in automation we should do s

Re: [Github/Gitbox] Setting up your committer account

Paul if we put effort in automation we should do so using the review functionality of github, where you can approve a PR On 16/04/17 09:45, "Paul Angus" wrote: That’s in progress... It would be cool if we could parse comments for LGTM and OK to Merge so that we can have them as status

RE: [Github/Gitbox] Setting up your committer account

That’s in progress... It would be cool if we could parse comments for LGTM and OK to Merge so that we can have them as status labels. Otherwise a manual process of updating a status would still be great. Kind regards, Paul Angus paul.an...@shapeblue.com  www.shapeblue.com 53 Chandos Place,

Re: [Github/Gitbox] Setting up your committer account

Done, good job -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Nicolas Vazquez" > To: "dev" > Sent: Saturday, 15 April, 2017 16:48:06 > Subject: Re: [Github/Gitbox] Setting up your committer account

Re: [Github/Gitbox] Setting up your committer account

Done, thanks Wido! 2017-04-15 7:29 GMT-03:00 Wido den Hollander : > Hi, > > Since yesterday we are using the Gitbox [0] services from ASF to have > Github our 'primary' source of code. > > This means that we can now label PRs, merge them, close them, all on > Github. > > If you are a committer yo

Re: [GitHub] cloudstack issue #1879: CLOUDSTACK-9719: [VMware] VR loses DHCP settings and...

This is essentially Vsphere 6.0 U2

Re: [GitHub] cloudstack issue #1966: CLOUDSTACK-9801: IPSec VPN does not work after vRout...

I ha e done pretty extensive testing of the strongswan implementation, but would be happy for you to verify if the problem exists in 4.10. On Feb 23, 2017 9:23 PM, "Sean Lair" wrote: > It is open against the 4.9 branch. > > We are running 4.9.2.0, looks like it affects all 4.9.x.x > > We haven't

Re: [GitHub] cloudstack issue #1966: CLOUDSTACK-9801: IPSec VPN does not work after vRout...

It is open against the 4.9 branch. We are running 4.9.2.0, looks like it affects all 4.9.x.x We haven't tested against 4.10 (strongswan) yet. But it could be a problem and will be worth testing. If strongswan starts before cloudstack adds the nics to the VM it could have same issue. > On F

Re: [GitHub] cloudstack issue #1773: CLOUDSTACK-9607: Preventing template deletion when t...

@ustcweizhou that's great . If you can open PR here @nvazquez can try implementing in-between PS copies for VMware . Also for VMware storage, migration doesn't require base template at destination PS even for linked clones. VMware will always convert link clone to a full one during migration Se

Re: [GitHub] cloudstack issue #1938: CLOUDSTACK-9780: Fixed the default JAVA_HOME value t...

I doubt the test environment will do a test without java_home set, so it is unlikely this fix will to tested with a run of that test. On Feb 12, 2017 11:36 PM, "karuturi" wrote: > Github user karuturi commented on the issue: > > https://github.com/apache/cloudstack/pull/1938 > > @borisst

Re: [GitHub] cloudstack issue #1741: Updated StrongSwan VPN Implementation

I planning to create first RC end of feb(in 20 days). ~ Rajani http://cloudplatform.accelerite.com/ On February 10, 2017 at 2:24 PM, Daan Hoogland (daan.hoogl...@shapeblue.com) wrote: sorry to keep you guys waiting, I am struggling my way back in and am working on this (and a lot) will keep you

RE: [GitHub] cloudstack issue #1741: Updated StrongSwan VPN Implementation

sorry to keep you guys waiting, I am struggling my way back in and am working on this (and a lot) will keep you posted. @Rajani, what is the ETA that I must meet to get this in 4.10? daan.hoogl...@shapeblue.com  www.shapeblue.com 53 Chandos Place, Covent Garden, Utrecht Utrecht 3531 VENetherland

Re: [GitHub] cloudstack pull request #1906: CLOUDSTACK-9743 - ODL plugin responds to dele...

If no action is being taken, the valid answer is to return null. This will make the listener logic to try the next listener On Thu, Feb 9, 2017 at 6:00 AM, koushik-das wrote: > Github user koushik-das commented on a diff in the pull request: > > https://github.com/apache/cloudstack/pull/1906

Re: [GitHub] cloudstack issue #1741: Updated StrongSwan VPN Implementation

Sorry, been swamped. I need to fix our Jenkins to support Java 8 to be able to continue validation on Java 8. On Jan 31, 2017 1:48 AM, "rhtyd" wrote: > Github user rhtyd commented on the issue: > > https://github.com/apache/cloudstack/pull/1741 > > Ping, update on this? > > > --- > If yo

RE: [GitHub] cloudstack issue #977: [4.10] CLOUDSTACK-8746: VM Snapshotting implementatio...

Yes, it's a bug, due to the number of associated comments attached to this PR. Simon Weller/615-312-6068 -Original Message- From: DaanHoogland [g...@git.apache.org] Received: Saturday, 28 Jan 2017, 12:17PM To: dev@cloudstack.apache.org [dev@cloudstack.apache.org] Subject: [GitHub] cloudst

Re: [GitHub] cloudstack issue #1741: Updated StrongSwan VPN Implementation

It is likely my environment. I had some connectivity issues in this envs when I was using them before. I have a pretty recent master in, but I can relate tonight to be sure. Can we kick off your CI to see what yours says? On Jan 21, 2017 2:24 AM, "PaulAngus" wrote: > Github user PaulAngus commen

Re: [GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

I have that on my dev environment, but not on my jenkins slaves... It works great in dev once you figure out how to get the JAVA_HOME to get set correctly. I had to create a file: ~./mavenrc With the following in it to get everything working. JAVA_HOME=$(/usr/libexec/java_home -v $(jenv version-

Re: [GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

@milamberspace I don't agree. Ubuntu 14.04 isn't EOL for another two years, rhel6 even longer. But users should be given proper directions as to how they can update Java. And we need to fix systemd/Ubuntu 16.04 support Erik tir. 10. jan. 2017 kl. 08.24 skrev milamberspace : > Github user mil

Re: [GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

Code review LGTM

Re: [GitHub] cloudstack pull request #1735: CLOUDSTACK-9570: Bug in listSnapshots for sna...

In case of unmanaged primary storage, we only care about secondary storage for snapshot. In case of VMware primary storage is only involved while taking snapshot. As far as I know process to take snapshot is to take VM snapshot, backup volume to secondary and then remove the VM snapshot on prima

Re: [GitHub] cloudstack pull request #1735: CLOUDSTACK-9570: Bug in listSnapshots for sna...

@anshul1886 Actually in unmanaged primary storage scenario the removal of PS doesn't check for the existence of the volume snapshot copy. Snapshot should be allowed to exist on secondary after primary is gone. In VMware environment snapshot copy on primary only improves performance but in the en

Re: [GitHub] cloudstack issue #1741: Updated StrongSwan VPN Implementation

I am going to try something today to see if I can try to find a way to support non-DH connections. I will let you know. On Jan 3, 2017 9:02 AM, "rhtyd" wrote: > Github user rhtyd commented on the issue: > > https://github.com/apache/cloudstack/pull/1741 > > @swill thanks, looking forward

Re: [GitHub] cloudstack issue #1741: Updated StrongSwan VPN Implementation

I will do a final round of testing in the next couple days and squash the commits as you asked. Sorry for the delay. It has been running in prod for the last month or so and it is going well. Strongswan does not support leaving the DH group empty. Should I remove that as an option from the UI and

Re: [GitHub] cloudstack issue #1753: [4.9] Latest health test run

Regards. From: Sergey Levitskiy Sent: 17 December 2016 00:09:55 To: dev@cloudstack.apache.org Subject: Re: [GitHub] cloudstack issue #1753: [4.9] Latest health test run It seems we have consistently more failures in 4.9 and 4.10 than few weeks ago e.g. In templates, dhcphosts

Re: [GitHub] cloudstack issue #1753: [4.9] Latest health test run

It seems we have consistently more failures in 4.9 and 4.10 than few weeks ago e.g. In templates, dhcphosts, list_ids

Re: [GitHub] cloudstack issue #1711: XenServer 7 Support

-- we may consider this for 4.9.2.0. Regards. From: Marty Godsey Sent: 10 December 2016 02:31:52 To: dev@cloudstack.apache.org; dev@cloudstack.apache.org Subject: RE: [GitHub] cloudstack issue #1711: XenServer 7 Support So will XS7 support be in this next update?

RE: [GitHub] cloudstack issue #1711: XenServer 7 Support

So will XS7 support be in this next update? Regards, Marty Godsey Principal Engineer nSource Solutions, LLC -Original Message- From: blueorangutan [mailto:g...@git.apache.org] Sent: Friday, December 9, 2016 4:00 PM To: dev@cloudstack.apache.org Subject: [GitHub] cloudstack issue #1711:

Re: [GitHub] cloudstack issue #1807: CLOUDSTACK-9633: Revert addition of `vhd` extention ...

oid further delaying the release work we'll have to revert your previous PR merge (#1600), request you to submit it again. Regards. From: Syed Ahmed Sent: 06 December 2016 10:20:45 To: dev@cloudstack.apache.org Subject: Re: [GitHub] cloudstack issue #1807

Re: [GitHub] cloudstack issue #1807: CLOUDSTACK-9633: Revert addition of `vhd` extention ...

I see. I was more interested in the functionality that is broken on Cloudstack. I have verified that older operations are still working correctly. Did I miss anything? On Mon, Dec 5, 2016 at 23:44 Abhinandan Prateek < abhinandan.prat...@shapeblue.com> wrote: > Syed, > > Any test that is calling

Re: [GitHub] cloudstack issue #1807: CLOUDSTACK-9633: Revert addition of `vhd` extention ...

Syed, Any test that is calling is_snapshot_on_nfs from utils.py will fail for Xen as it ends up appending an additional “.vhd” to the install_path. There are several of them both in smoke and component folder. The reason this is under scrutiny is die to marvin test failures. On 06/12/16, 9

Re: [GitHub] cloudstack issue #1807: CLOUDSTACK-9633: Revert addition of `vhd` extention ...

Yes this will break managed snapshot archives. I want to understand what this revert is trying to fix and what tests were failing. On Mon, Dec 5, 2016 at 22:38 abhinandanprateek wrote: > Github user abhinandanprateek commented on the issue: > > https://github.com/apache/cloudstack/pull/1807 >

Re: [GitHub] cloudstack issue #1800: CLOUDSTACK-9633:test_snapshot is failing due to inco...

I'll take a look at this. It's been some moths but afaik I added that extension because previously that code wasn't working. I'll take a look in detail and let you guys know On Thu, Dec 1, 2016 at 11:34 mike-tutkowski wrote: > Github user mike-tutkowski commented on the issue: > > https://git

Re: [GitHub] cloudstack issue #1801: fix marvin test failure test_router_dhcp_opts

LGTM

Re: [GitHub] cloudstack issue #1800: CLOUDSTACK-9633:test_snapshot is failing due to inco...

LGTM

RE: [GitHub] cloudstack issue #1711: Xenserver7 Support

@rohit Can you set a BlueO job off from this please? Kind regards, Paul Angus paul.an...@shapeblue.com  www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue -Original Message- From: syed [mailto:g...@git.apache.org] Sent: 25 October 2016 17:27 To: dev

Re: [GitHub] cloudstack issue #872: Strongswan vpn feature

@swill I believe windows natively support "L2TP” . And I see they negotiated both encryption and integrity . looks like the difference is this: On OSX xl2tpd[2263]: control_finish: Peer requested tunnel 32 twice, ignoring second one. On windows it seems it trying to establish ‘child’ session

Re: [GitHub] cloudstack issue #1684: CLOUDSTACK-9489: the new config vars that are added ...

thank you for replying。 But CloudStack4.6 mysql database cloud table configuration has no this name. mysql> use cloud Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed mysql> select database()

Re: [GitHub] cloudstack issue #1642: CLOUDSTACK-9504: System VMs on Managed Storage

Thanks, Sergey! On 9/21/16, 5:37 PM, "Sergey Levitskiy" wrote: @mike-tutkowski @nvazquez We can probably run it this week On 9/21/16, 12:11 PM, "mike-tutkowski" wrote: Github user mike-tutkowski commented on the issue: https://github.com/

Re: [GitHub] cloudstack issue #1642: CLOUDSTACK-9504: System VMs on Managed Storage

@mike-tutkowski @nvazquez We can probably run it this week On 9/21/16, 12:11 PM, "mike-tutkowski" wrote: Github user mike-tutkowski commented on the issue: https://github.com/apache/cloudstack/pull/1642 Thank you, @karuturi! Does anyone know who

Re: [GitHub] cloudstack pull request #1642: System VMs on Managed Storage

I renamed it to “delay”, but I can’t remember now what I did that. ☺ On 9/15/16, 10:20 PM, "jburwell" wrote: Github user jburwell commented on a diff in the pull request: https://github.com/apache/cloudstack/pull/1642#discussion_r79104400 --- Diff: test/integratio

Re: [GitHub] cloudstack issue #1658: Added an additional JSON diff output to the ApiXmlDo...

@jburwell This looks like an awesome system which will improve ACS stability big time. Let me know if we can assist in any way. On 9/12/16, 12:42 PM, "John Burwell" wrote: Sergey, We are working on a full automated build pipeline that will test against a wide range of configurat

Re: [GitHub] cloudstack issue #1658: Added an additional JSON diff output to the ApiXmlDo...

Sergey, We are working on a full automated build pipeline that will test against a wide range of configurations. Ideally, the pipeline will work as follows: 1. PR is submitted -> the PR is built, unit tested, and run through static analysis. Smoke tests are run on a matrix of configurati

Re: [GitHub] cloudstack issue #1658: Added an additional JSON diff output to the ApiXmlDo...

@swill @jburwell From my, non-committer, point of view introducing fully automated test system integrated with PR submission and leveraging complete list of supported hypervisors is the key to stability. I really like blueorangutain idea and if this can be brought back and also cover full set of

  1   2   3   4   >