Re: [MERGE] virtual network appliance manager refactorring

I have posted a reference pull request with the current work in progress using packer to build system virtual machines as well as generating vagrant boxes for testing. As mentioned in the pull request comment :This is "a work in progress" and posted fo

Re: [MERGE] virtual network appliance manager refactorring

Thanks for the update, Karl! We are working on different parts of the implementation: * 2 developer with the system vm + python scripts * 1 developer on test automation * 3 developers on the java side of the force You input is extremely valid and I will make sure that the other members of the te

Re: [MERGE] virtual network appliance manager refactorring

Here is a update of the work in support of Cloudstack-764: The overall idea of this effort is to implement VPC Virtual Redundant Routing and automate the unit tests for system virtual machine for virtual routers both redundant and non-redundant, for Cloudstack-764. Current work areas. Modify s

Re: [MERGE] virtual network appliance manager refactorring

Thanks, Daan! :) More info here: Just a quick update on the status of the VPC RVR refactor, which is the part 1 of the whole VPC RVR implementation. I have added some documentation to the Apache Wiki page. You can find it on the URL below: https://cwiki.apache.org/confluence/display/CLOUDSTACK

Re: [MERGE] virtual network appliance manager refactorring

yes, and it is good to stress that once again! On Fri, Oct 3, 2014 at 6:00 PM, David Nalley wrote: > As noted in your PR, please don't merge this immediately into master. > We're in feature freeze, and master is currently 4.5 > > Thanks, > > --David > > On Fri, Oct 3, 2014 at 7:22 AM, Daan Hoogl

Re: [MERGE] virtual network appliance manager refactorring

H Karl, no it isn't. This ticket is just for the systemvm template creation. On Fri, Oct 3, 2014 at 4:42 PM, Karl Harris wrote: > Daan, > > Is it safe to assume that the most of the refactoring work mentioned > (pushed) in your email is outlined in CLOUDSTACK-7143? > > Karl > > > On Fri, Oct 3,

Re: [MERGE] virtual network appliance manager refactorring

As noted in your PR, please don't merge this immediately into master. We're in feature freeze, and master is currently 4.5 Thanks, --David On Fri, Oct 3, 2014 at 7:22 AM, Daan Hoogland wrote: > H, > > I just pushed a huge branch with work that my colleagues did [1]. It is > prerequisite to addi

Re: [MERGE] virtual network appliance manager refactorring

One of us will create e new pr once master is ready for merge. The functionality hasn't changed since the last pr. I've created one anyhow. better not pull it in ;) On Fri, Oct 3, 2014 at 2:56 PM, Rohit Yadav wrote: > Hi Daan, > > Can you create a Github PR, it’s would be much easier to review

Re: [MERGE] virtual network appliance manager refactorring

Daan, Is it safe to assume that the most of the refactoring work mentioned (pushed) in your email is outlined in CLOUDSTACK-7143? Karl On Fri, Oct 3, 2014 at 7:22 AM, Daan Hoogland wrote: > H, > > I just pushed a huge branch with work that my colleagues did [1]. It is > prerequisite to adding

Re: [MERGE] virtual network appliance manager refactorring

Hi Daan, Can you create a Github PR, it’s would be much easier to review the diffs. Thanks. On 03-Oct-2014, at 1:22 pm, Daan Hoogland wrote: > H, > > I just pushed a huge branch with work that my colleagues did [1]. It is > prerequisite to adding redundancy to vpc routers. please take it into >

[MERGE] virtual network appliance manager refactorring

H, I just pushed a huge branch with work that my colleagues did [1]. It is prerequisite to adding redundancy to vpc routers. please take it into account when doing anything with virtual router functionality as it addresses a lot of the way we work with configuring those. Merging will have to wait