Re: Build issues on master (POM related)

Hey Mike, I think you can get rid of a lot of them by installing the eclipse checkstyle plugin. It should be available from the default update sites. Otherwise check here: http://eclipse-cs.sourceforge.net The maven-license-plugin doesn’t have an eclipse plugin, so you need to ignore that one

Re: Build issues on master (POM related)

Sorry...getting tired :) By this: Also all of the say the following: I meant this: Almost all of them say the following: On Mon, Jan 13, 2014 at 10:50 PM, Mike Tutkowski < mike.tutkow...@solidfire.com> wrote: > Hi Alex, > > Also all of the say the following: > > Description Resource Path Loc

Re: Build issues on master (POM related)

Hi Alex, Also all of the say the following: Description Resource Path Location Type Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-checkstyle-plugin:2.11:check (execution: default, phase: validate) pom.xml /cloud-agent line 23 Maven Project Build Lifecycle

RE: [Doc] [4.3] Service Monitoring Tool for Virtual Router for Review [CLOUDSTACK-5292]

Hi David, For this release, there is no admin-specific actions, but in the coming releases there are enhancements coming which alerts the admin. Keeping those enhancements in mind, I added this content. -Original Message- From: David Nalley [mailto:da...@gnsa.us] Sent: Monday, January

RE: [Doc] [4.3] Service Monitoring Tool for Virtual Router for Review [CLOUDSTACK-5292]

Hi David, As you said the tool runs in the background and is not exposed to the administrator at-least in 4.3. -Sanjeev -Original Message- From: David Nalley [mailto:da...@gnsa.us] Sent: Monday, January 13, 2014 7:59 PM To: us...@cloudstack.apache.org Cc: dev@cloudstack.apache.org Subj

RE: AWSAPI not working in 4.3

Seb, I am able to successfully use awsapi on my dev setup (4.3 latest). Did you by any chance forget to build using the awsapi profile -> mvn clean install -P systemvm -P awsapi -Dnoredist ? Thanks, Likitha >-Original Message- >From: Chandan Purushothama [mailto:chandan.purushoth...@citr

Re: Review Request 16361: CLOUDSTACK-5535: Do not allow addNetwork to create NIC across VPC tiers and Isolated Networks

> On Jan. 9, 2014, 6:22 p.m., Alena Prokharchyk wrote: > > Saksham, > > > > The patch fails on 4.3 branch with the error: > > > > Applying: CLOUDSTACK-5535 : Do not allow addNetwork to create NIC across > > VPC tiers and Isolated Networks > > error: patch failed: server/src/com/cloud/vm/UserVm

Review Request 16841: (ACS4.3): Add new physical network isolationMethod (L3VPN) for Juniper Contrail plugin.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16841/ --- Review request for cloudstack. Repository: cloudstack-git Description ---

RE: AWSAPI not working in 4.3

Hello, I am able to successfully use aws api on my test setup using the latest build. Looks like the feature is intact since the previous release, Thank you, Chandan. -Original Message- From: Prachi Damle [mailto:prachi.da...@citrix.com] Sent: Monday, January 13, 2014 12:12 PM To: Anim

Re: [Proposal] Ability to retrieve user data via Admin API - 4.4

I agree with David. This feature is useless to me as the end-user if it's admin-only as I could never guarantee having admin access if I decided to move my app to another provider/cloud that I don't administer. -Jason On Mon, Jan 13, 2014 at 2:32 PM, David Nalley wrote: > The end-user has an e

Re: [Proposal] Ability to retrieve user data via Admin API - 4.4

I would also agree that user/account/domain access to this data via api would be welcome. Requiring that the request originate from the VM requires going to every VM to pull that data. With some of the setups I have seen to drive puppet from this data, a simple util could query for all VMs that the

RE: Build issues on master (POM related)

Mike I don't see this many warnings in my eclipse in master. The only one I see currently is the one regarding opendaylight pom.xml have a target not in the m2e lifecycle. Can you drill down more and tell us what it thinks the problem is? The png just shows a list of poms with problems but no

Re: [Proposal] Ability to retrieve user data via Admin API - 4.4

I was just assuming if end user needs to retrieve his metadata, he can always do it through the VM. While if Admin needs to access user¹s meatadata - to DR the vm from one cloud to another for example - he can¹t do it because he has no access to user¹s network. There is no problem for me to make A

Re: [Proposal] Ability to retrieve user data via Admin API - 4.4

The end-user has an even more compelling reason to be able to query that information without resorting to querying from the host than an admin ever will. Why would a cloud administrator need to see/care about userdata? I can see the end-user/instance admin caring, but not the root admin. --David

Re: [Proposal] Ability to retrieve user data via Admin API - 4.4

User can always access it through his Vm. The feature is more meant to cover the case when Admin needs to get all the user data info for all vms of a) network b) system On 1/13/14, 1:55 PM, "David Nalley" wrote: >On Mon, Jan 13, 2014 at 12:56 PM, Alena Prokharchyk > wrote: >> I would like to pro

Re: Build issues on master (POM related)

On 4.3 I only see four warnings. Perhaps people are suppressing these warnings on the master branch? On Mon, Jan 13, 2014 at 2:56 PM, Mike Tutkowski < mike.tutkow...@solidfire.com> wrote: > Hi everyone, > > Any thoughts on this? I still see 90 issues (mainly POM related) in an > updated version

Re: Build issues on master (POM related)

Hi everyone, Any thoughts on this? I still see 90 issues (mainly POM related) in an updated version of 4.4 (master) when in Eclipse. Thanks! On Thu, Jan 9, 2014 at 2:11 PM, Mike Tutkowski wrote: > Hi, > > I haven't tried to build master in Eclipse in quite a while and am > noticing at least 8

Re: [Proposal] Ability to retrieve user data via Admin API - 4.4

On Mon, Jan 13, 2014 at 12:56 PM, Alena Prokharchyk wrote: > I would like to propose to introduce API (Admin only, 4.4) that returns user > data to the admin. Current UserData behavior: > > * userData is passed to the deployVm/updateVm call > * its stored in CS db and on the VR > * the only on

Re: Review Request 16805: Contrail plugin fixes - db update, policy port end fix

Hi Sheng, This is a reminder. Can you please ship this? Thanks, Suresh On Jan 11, 2014, at 4:13 PM, "Suresh Balineni" mailto:sbalin...@service.juniper.net>> wrote: Hi Sheng, This is another 4.3 review request. Code changes are minimal. Can you please review and the update the repository? Th

Re: [ACS 4.3] RC update

On Jan 13, 2014, at 1:08 PM, Santhosh Edukulla wrote: > 1. requests package and nosetests2.7 are required to work with tests. > > 2. As such Simulator (as mentioned below ) works and so inquired to remove it > from blocker, but its the profile which needs changes and so mentioned below > not

RE: AWSAPI not working in 4.3

There has been no code change to break anything newly; so this should be a build problem. If anyone familiar with maven profiles can also take a look, it might be quicker to find out. Prachi -Original Message- From: Animesh Chaturvedi Sent: Monday, January 13, 2014 11:49 AM To: dev@c

RE: [VOTE] 3rd round of voting for ASF 4.2.1 RC

-Original Message- From: sebgoa [mailto:run...@gmail.com] Sent: Monday, January 13, 2014 5:47 AM To: dev@cloudstack.apache.org; ustcweiz...@gmail.com Subject: Re: [VOTE] 3rd round of voting for ASF 4.2.1 RC On Jan 6, 2014, at 9:46 AM, Wei ZHOU wrote: > Hi Abhi, > > I have two proble

RE: AWSAPI not working in 4.3

Copying Prachi to the thread. Animesh -Original Message- From: sebgoa [mailto:run...@gmail.com] Sent: Monday, January 13, 2014 7:01 AM To: dev@cloudstack.apache.org Subject: AWSAPI not working in 4.3 Hi, In 4.2 we can run the awsapi with: mvn -Pawsapi -pl :cloud-awsapi jetty:run In th

RE: [ACS 4.3] RC update

1. requests package and nosetests2.7 are required to work with tests. 2. As such Simulator (as mentioned below ) works and so inquired to remove it from blocker, but its the profile which needs changes and so mentioned below notes to fix the profile if agreed. Anyways, however way. we decide and

Re: Revert to volume snapshot

I can try to provide a direction to look in, but take this with a grain of salt… I believe that the XenServer best practice for ‘restoring’ a VM volume is creating a NEW volume from the snapshot and then attaching that volume to the VM INSTEAD of reverting the volume back to it’s previous state.

[Proposal] Ability to retrieve user data via Admin API - 4.4

I would like to propose to introduce API (Admin only, 4.4) that returns user data to the admin. Current UserData behavior: * userData is passed to the deployVm/updateVm call * its stored in CS db and on the VR * the only one way to retrieve the data, is to request it from the user vm inside t

Re: [ACS 4.3] RC update

On Jan 13, 2014, at 6:45 PM, Santhosh Edukulla wrote: > Hi Sebastian, > > 1. I was able to get the simulator up and running following the below > instructions @link: > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Simulator+integration > > mvn -Pdeveloper -Dsimulator clean instal

RE: [ACS 4.3] RC update

Hi Sebastian, 1. I was able to get the simulator up and running following the below instructions @link: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Simulator+integration mvn -Pdeveloper -Dsimulator clean install mvn -Pdeveloper -pl developer -Ddeploydb mvn -Pdeveloper -pl developer

Re: [DISCUSS] Domain/Account/User Sync Up Among Multiple Regions

All, I'd like to have some suggestion about 2 things related with this. 1. The 'Full Scan' management Now, I set it running every time a user logs in to the UI, but I think it will be necessary to make it run with some interval also. But I'm not familiar with the config file, so can anyone give s

Re: word-break: break-all

Hi Peter, Thanks for reporting this. I will get this fix later today. Originally it was done to prevent large links spilling out of their containers. (Example: http://css-tricks.com/snippets/css/prevent-long-urls-from-breaking-out-of-container/) If you notice anything else please let us know! Th

Re: [JENKINS] Failing jobs (again)

Hi, Can you move the jenkins build break emails to some other list, like the commits one or create a new one? I see this happening every now and then, for people who may not get time everyday to follow CloudStack but would like to follow the dev ML for development discussions it would cut some no

Re: [ANNOUNCE] New Committer: Sanjay Tripathi

Congratulations Sanjay! 2014/1/9 David Nalley > The Project Management Committee (PMC) for Apache CloudStack has asked > Sanjay Tripathi to become a committer and we are pleased to announce > that they have > accepted. > > Being a committer allows many contributors to contribute more > autonomo

Re: IPv6 in VPC (was Re: IPv6 plan - questions)

I'm just trying to understand why it's simpler or preferred. To me it's simpler to not bother with the VPC-wide, and automatically enables flexibility or the use case you've described. Case 1: admin decides to put a /60 on a vpc admin programs /60 to vpc via cloudstack admin programs /60 route on

AWSAPI not working in 4.3

Hi, In 4.2 we can run the awsapi with: mvn -Pawsapi -pl :cloud-awsapi jetty:run In the latest 4.3 branch, I can build successfully and run the mgt server, but while trying to run the awsapi app I get: [INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ cloud-awsapi ---

Re: [ACS 4.3] RC update

On Jan 13, 2014, at 2:37 PM, sebgoa wrote: > > On Jan 13, 2014, at 2:26 PM, sebgoa wrote: > >> >> On Jan 11, 2014, at 7:08 AM, Animesh Chaturvedi >> wrote: >> >>> Folks >>> >>> Today is the scheduled RC date for ACS 4.3 We are very close with just a >>> few lingering issues below. >>>

Re: [Doc] [4.3] Service Monitoring Tool for Virtual Router for Review [CLOUDSTACK-5292]

Hi Radhika: So I read this section and while the documentation is clear on what it does; it's not clear on how I use it. If it isn't intended to be exposed to the administrator and just runs in the background like so many things in CloudStack does already, why document it at all in the admin guide

word-break: break-all

Hi, I find it terrible that the website has the following CSS on the body element: word-break: break-all; This makes words break anywhere, not just at white space (word boundaries), and unlike in books you read, it has no hyphen at the end of the line. It looks bad and is annoying to read. I

RE: [ANNOUNCE] New Committer: Sanjay Tripathi

Congratulations, Sanjay! With kinds regards, Wilder -Original Message- From: David Nalley [mailto:da...@gnsa.us] Sent: Thursday, January 09, 2014 11:53 PM To: dev@cloudstack.apache.org Subject: [ANNOUNCE] New Committer: Sanjay Tripathi The Project Management Committee (PMC) for Apache C

Re: [VOTE] 3rd round of voting for ASF 4.2.1 RC

On Jan 6, 2014, at 9:46 AM, Wei ZHOU wrote: > Hi Abhi, > > I have two problems, > (1) 3a999e7 made OVS not working on 4.2, so I fixed it by > commit 79f609ca19fc44aab8de8294f234537936bc3613 > (2) DevCloud does not work after commit > 7f9463bb54f19e7676f8c6049d1ebc02330a730f. So I am wondering

Re: [ACS 4.3] RC update

On Jan 13, 2014, at 2:26 PM, sebgoa wrote: > > On Jan 11, 2014, at 7:08 AM, Animesh Chaturvedi > wrote: > >> Folks >> >> Today is the scheduled RC date for ACS 4.3 We are very close with just a few >> lingering issues below. >> >> >> >> | Jayapal Reddy| CLOUDSTACK-5848 : [Upgrad

Jenkins build is back to normal : build-master #39

See

Jenkins build is back to normal : cloudstack-4.3-maven-build #395

See

Re: Revert to volume snapshot

On 11.01.2014 22:28, Nux! wrote: Hi, Is there any reason why we shouldn't be able to revert to a volume's snapshot/backup? Seems like it would be an awfully more useful feature than what we have now; most of the times I'd imagine people would want to backup AND restore occasionally. I'm particul

Re: [ACS 4.3] RC update

On Jan 11, 2014, at 7:08 AM, Animesh Chaturvedi wrote: > Folks > > Today is the scheduled RC date for ACS 4.3 We are very close with just a few > lingering issues below. > > > > | Jayapal Reddy| CLOUDSTACK-5848 : [Upgrade3.0.6-4.3]"Unable to parse > VLAN tag" message when network

Build failed in Jenkins: cloudstack-4.3-maven-build #394

See -- [...truncated 280 lines...] Receiving objects: 46% (212747/462492), 44.17 MiB | 626 KiB/s Receiving objects: 46% (213440/462492), 44.68 MiB | 551 KiB/s Receiving objects: 46

Re: [JENKINS] Failing jobs (again)

On Mon, Jan 13, 2014 at 01:59:31PM +0100, Hugo Trippaers wrote: > Hey all, > > We seem to have some trouble with a number of buildslaves. The > rpmbuilder and docs slaves are not reachable at the moment. I?m > trying to move some of the work to other nodes, but due to git > timeouts jobs keep fail

Build failed in Jenkins: build-master #38

See -- [...truncated 275 lines...] Receiving objects: 45% (209903/462492), 42.35 MiB | 589 KiB/s Receiving objects: 45% (211688/462492), 42.70 MiB | 616 KiB/s Receiving objects: 45% (212432/46249

Build failed in Jenkins: cloudstack-4.3-maven-build #393

See -- [...truncated 573 lines...] Receiving objects: 79% (368061/462492), 208.37 MiB | 639 KiB/s Receiving objects: 79% (368061/462492), 208.61 MiB | 614 KiB/s Receiving objects:

Re: [JENKINS] Failing jobs (again)

On 01/13/2014 01:59 PM, Hugo Trippaers wrote: Hey all, We seem to have some trouble with a number of buildslaves. The rpmbuilder and docs slaves are not reachable at the moment. I’m trying to move some of the work to other nodes, but due to git timeouts jobs keep failing. Will keep you guys

Build failed in Jenkins: build-master #37

See -- [...truncated 574 lines...] Receiving objects: 79% (368064/462492), 211.88 MiB | 332 KiB/s Receiving objects: 79% (368065/462492), 212.10 MiB | 352 KiB/s Receiving objects: 79% (368065/462

[JENKINS] Failing jobs (again)

Hey all, We seem to have some trouble with a number of buildslaves. The rpmbuilder and docs slaves are not reachable at the moment. I’m trying to move some of the work to other nodes, but due to git timeouts jobs keep failing. Will keep you guys posted. Cheers, Hugo

Build failed in Jenkins: build-master #36

See -- [...truncated 578 lines...] Receiving objects: 79% (368062/462492), 209.61 MiB | 824 KiB/s Receiving objects: 79% (368062/462492), 210.52 MiB | 859 KiB/s Receiving objects: 79% (368062/462

Build failed in Jenkins: cloudstack-4.3-maven-build #392

See -- [...truncated 577 lines...] Receiving objects: 79% (368379/462492), 234.91 MiB | 556 KiB/s Receiving objects: 79% (368379/462492), 235.33 MiB | 536 KiB/s Receiving objects:

Build failed in Jenkins: build-master #35

See -- [...truncated 575 lines...] Receiving objects: 79% (368533/462492), 243.18 MiB | 397 KiB/s Receiving objects: 79% (368535/462492), 243.70 MiB | 447 KiB/s Receiving objects: 79% (368535/462

Build failed in Jenkins: cloudstack-4.3-maven-build #391

See -- [...truncated 673 lines...] Receiving objects: 90% (418820/462492), 300.29 MiB | 799 KiB/s Receiving objects: 90% (418919/462492), 300.97 MiB | 734 KiB/s Receiving objects:

Build failed in Jenkins: build-master #34

See -- [...truncated 571 lines...] Receiving objects: 76% (351705/462492), 176.41 MiB | 586 KiB/s Receiving objects: 76% (351710/462492), 177.13 MiB | 620 KiB/s Receiving objects: 76% (351713/462

Build failed in Jenkins: cloudstack-4.3-maven-build #390

See -- [...truncated 573 lines...] Receiving objects: 77% (357203/462492), 181.43 MiB | 714 KiB/s Receiving objects: 77% (358812/462492), 182.55 MiB | 734 KiB/s Receiving objects:

Build failed in Jenkins: cloudstack-4.3-maven-build #389

See -- [...truncated 577 lines...] Receiving objects: 79% (368056/462484), 207.03 MiB | 1.05 MiB/s Receiving objects: 79% (368056/462484), 208.29 MiB | 1.10 MiB/s Receiving objects:

Build failed in Jenkins: build-master #33

See -- [...truncated 576 lines...] Receiving objects: 79% (368056/462484), 206.74 MiB | 1.07 MiB/s Receiving objects: 79% (368056/462484), 208.02 MiB | 1.11 MiB/s Receiving objects: 79% (368056/4

Build failed in Jenkins: cloudstack-4.3-maven-build #388

See -- [...truncated 577 lines...] Receiving objects: 79% (368057/462484), 220.30 MiB | 570 KiB/s Receiving objects: 79% (368057/462484), 220.93 MiB | 555 KiB/s Receiving objects:

Build failed in Jenkins: build-master #32

See -- [...truncated 576 lines...] Receiving objects: 79% (365363/462484), 193.82 MiB | 509 KiB/s Receiving objects: 79% (367771/462484), 194.14 MiB | 537 KiB/s Receiving objects: 79% (368056/462

Build failed in Jenkins: cloudstack-4.3-maven-build #387

See -- [...truncated 569 lines...] Receiving objects: 76% (351674/462484), 172.02 MiB | 786 KiB/s Receiving objects: 76% (351677/462484), 172.78 MiB | 805 KiB/s Receiving objects:

Build failed in Jenkins: build-master #31

See -- [...truncated 575 lines...] Receiving objects: 77% (360449/462484), 191.79 MiB | 701 KiB/s Receiving objects: 78% (360738/462484), 192.15 MiB | 684 KiB/s Receiving objects: 78% (360903/462

Build failed in Jenkins: cloudstack-4.3-maven-build #386

See -- [...truncated 563 lines...] Receiving objects: 79% (368050/462484), 200.40 MiB | 501 KiB/s Receiving objects: 79% (368050/462484), 201.01 MiB | 504 KiB/s Receiving objects:

Build failed in Jenkins: build-master #30

See -- [...truncated 560 lines...] Receiving objects: 79% (368056/462484), 196.25 MiB | 585 KiB/s Receiving objects: 79% (368056/462484), 196.82 MiB | 551 KiB/s Receiving objects: 79% (368056/462

Re: Communication between Management Server and guest vm deployed by root admin user

Comments inline. PS: I am moving this discussison to the user’s list which I feel is a more appropriate place to discuss this query. On 13-Jan-2014, at 1:10 pm, Saurav Lahiri wrote: > Hi, > Would anybody know if there is a way that guest vms deployed by root admin > can be included in the syste

Build failed in Jenkins: build-master #29

See -- [...truncated 574 lines...] Receiving objects: 79% (368067/462484), 221.12 MiB | 613 KiB/s Receiving objects: 79% (368067/462484), 221.87 MiB | 639 KiB/s Receiving objects: 79% (368122/462

Build failed in Jenkins: cloudstack-4.3-maven-build #385

See -- [...truncated 577 lines...] Receiving objects: 79% (368487/462484), 227.10 MiB | 619 KiB/s Receiving objects: 79% (368487/462484), 227.73 MiB | 636 KiB/s Receiving objects:

Build failed in Jenkins: cloudstack-4.3-maven-build #384

See -- [...truncated 571 lines...] Receiving objects: 76% (351760/462484), 176.14 MiB | 470 KiB/s Receiving objects: 76% (351763/462484), 176.58 MiB | 398 KiB/s Receiving objects:

Build failed in Jenkins: build-master #28

See -- [...truncated 619 lines...] Receiving objects: 80% (371003/462484), 269.51 MiB | 941 KiB/s Receiving objects: 80% (371004/462484), 270.03 MiB | 919 KiB/s Receiving objects: 80% (371004/462

Build failed in Jenkins: build-master #27

See -- [...truncated 446 lines...] Receiving objects: 75% (351344/462430), 138.36 MiB | 810 KiB/s Receiving objects: 75% (351344/462430), 138.77 MiB | 624 KiB/s Receiving objects: 75% (351344/462

Build failed in Jenkins: cloudstack-4.3-maven-build #383

See -- [...truncated 448 lines...] Receiving objects: 75% (349874/462430), 125.18 MiB | 309 KiB/s Receiving objects: 75% (351339/462430), 125.82 MiB | 339 KiB/s Receiving objects:

Build failed in Jenkins: build-master #26

See -- [...truncated 578 lines...] Receiving objects: 79% (368451/462430), 234.18 MiB | 585 KiB/s Receiving objects: 79% (368451/462430), 234.93 MiB | 632 KiB/s Receiving objects: 79% (368451/462

Build failed in Jenkins: cloudstack-4.3-maven-build #382

See -- [...truncated 575 lines...] Receiving objects: 77% (358704/462430), 188.46 MiB | 410 KiB/s Receiving objects: 77% (358704/462430), 188.89 MiB | 385 KiB/s Receiving objects:

Build failed in Jenkins: build-master #25

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on cloudstack-buildslave-centos6-86f in workspace

Build failed in Jenkins: cloudstack-4.3-maven-build #381

See -- [...truncated 580 lines...] Receiving objects: 79% (368448/462430), 235.46 MiB | 1.16 MiB/s Receiving objects: 79% (368451/462430), 236.78 MiB | 1.21 MiB/s Receiving objects:

Build failed in Jenkins: cloudstack-4.3-maven-build #380

See -- [...truncated 577 lines...] Receiving objects: 76% (351630/462430), 174.60 MiB | 506 KiB/s Receiving objects: 76% (351632/462430), 175.16 MiB | 493 KiB/s Receiving objects:

Build failed in Jenkins: build-master #24

See -- [...truncated 574 lines...] Receiving objects: 76% (351665/462430), 166.03 MiB | 586 KiB/s Receiving objects: 76% (351666/462430), 166.41 MiB | 546 KiB/s Receiving objects: 76% (351666/462

Build failed in Jenkins: build-master #23

See -- [...truncated 560 lines...] Receiving objects: 76% (351538/462430), 155.77 MiB | 730 KiB/s Receiving objects: 76% (351545/462430), 156.63 MiB | 776 KiB/s Receiving objects: 76% (351551/462

Build failed in Jenkins: cloudstack-4.3-maven-build #379

See -- [...truncated 578 lines...] Receiving objects: 79% (368002/462430), 201.93 MiB | 486 KiB/s Receiving objects: 79% (368002/462430), 202.62 MiB | 534 KiB/s Receiving objects:

Build failed in Jenkins: build-master #22

See -- [...truncated 576 lines...] Receiving objects: 79% (368000/462430), 197.68 MiB | 540 KiB/s Receiving objects: 79% (368000/462430), 198.34 MiB | 587 KiB/s Receiving objects: 79% (368000/462

Build failed in Jenkins: cloudstack-4.3-maven-build #378

See -- [...truncated 579 lines...] Receiving objects: 79% (368070/462430), 224.73 MiB | 697 KiB/s Receiving objects: 79% (368072/462430), 225.20 MiB | 730 KiB/s Receiving objects:

RE: IPv6 in VPC (was Re: IPv6 plan - questions)

H Marcus, The idea is that for phase 1 we make it as simple as possible. The extra networks / ip-space per network can always be added later. Support will have to build for adding the routes on a per router implementation basis, as I understand. I was describing the simplest solution to impleme

Build failed in Jenkins: build-master #21

See -- [...truncated 576 lines...] Receiving objects: 77% (360371/462430), 191.18 MiB | 432 KiB/s Receiving objects: 77% (360379/462430), 191.75 MiB | 485 KiB/s Receiving objects: 78% (360696/462

Build failed in Jenkins: cloudstack-4.3-maven-build #377

See -- [...truncated 573 lines...] Receiving objects: 76% (352821/462430), 180.72 MiB | 404 KiB/s Receiving objects: 76% (355201/462430), 181.32 MiB | 467 KiB/s Receiving objects:

Build failed in Jenkins: build-master #20

See -- [...truncated 575 lines...] Receiving objects: 79% (367990/462430), 209.07 MiB | 777 KiB/s Receiving objects: 79% (367990/462430), 209.93 MiB | 784 KiB/s Receiving objects: 79% (367990/462

Build failed in Jenkins: cloudstack-4.3-maven-build #376

See -- [...truncated 573 lines...] Receiving objects: 77% (358760/462430), 187.86 MiB | 483 KiB/s Receiving objects: 77% (358760/462430), 188.04 MiB | 449 KiB/s Receiving objects:

Build failed in Jenkins: build-master #19

See -- [...truncated 589 lines...] Receiving objects: 79% (367997/462430), 204.85 MiB | 989 KiB/s Receiving objects: 79% (367997/462430), 205.47 MiB | 904 KiB/s Receiving objects: 79% (367997/462

Build failed in Jenkins: cloudstack-4.3-maven-build #375

See -- [...truncated 594 lines...] Receiving objects: 79% (368000/462430), 194.91 MiB | 354 KiB/s Receiving objects: 79% (368000/462430), 195.45 MiB | 419 KiB/s Receiving objects:

RE: [Doc] [4.3] Service Monitoring Tool for Virtual Router for Review [CLOUDSTACK-5292]

Hi Radhika, Please find below the review comments: 1. Introduction says that the tool restarts the VR if a service goes down which is not true. It will only restart the service if it detects that service as down. Tool will never restart the VR 2. This feature is also supported on Hyper-v Thanks