cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wilder Rodrigues <WRodrig...@schubergphilis.com>
Subject Re: [MERGE] virtual network appliance manager refactorring
Date Thu, 09 Oct 2014 19:39:05 GMT
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 team get the info (just in case the miss the email on the list).

Have a nice evening.

Cheers,
Wilder

On 09/10/14 19:51, "Karl Harris" <karl.harris@sungardas.com> wrote:

>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 system vm bash scripts to implement VPC Virtual redundant routing
>in
>a similar
>fashion to existing virtual redundant routing. Basically implementing the
>ability for VRR to handle
>VPC's dynamic network topology as mention in the Java Refactoring from SP.
>
>Refactored the VeeWee virtual machine build scripts to use Packer. Packer
>is used because of its ability
>to build a system virtual machine raw file without unsupported "c"
>utilities and its additional builders
>to generate images for all virtual environments as required.
>
>Initial test framework uses VirtualBox/Vagrant as test harness with the
>addition of test scripts for unit testing.
>The output of the Packer build in a Vagrant Box is also used for debugging
>script changes outside
>of unit test framework.
>
>Use the output of the Packer builders as part of an automated system
>virtual machine "build/ testing chain"  in support of additional
>script changes for virtual routers and/or other Cloudstack system virtual
>machine functions.
>
>
>
>Karl
>
>
>On Tue, Oct 7, 2014 at 11:45 AM, Wilder Rodrigues <
>WRodrigues@schubergphilis.com> wrote:
>
>> 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/Refactor+for+Redun
>>dant+Virtual+Router+Implementation
>>
>> Thanks for the diagrams, Antonio!
>>
>> I will update it later with some few notes that we are working on.
>>
>> Cheers,
>> Wilder
>>
>> Sent from my iPhone
>>
>> On 03 Oct 2014, at 19:36, "Daan Hoogland"
>><daan.hoogland@gmail.com<mailto:
>> daan.hoogland@gmail.com>> wrote:
>>
>> yes, and it is good to stress that once again!
>>
>> On Fri, Oct 3, 2014 at 6:00 PM, David Nalley <david@gnsa.us<mailto:
>> david@gnsa.us>> 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 Hoogland <daan.hoogland@gmail.com
>> <mailto:daan.hoogland@gmail.com>>
>> 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
>> 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 of course but for any related work I'd advice to use it as
>> starting point to be joined in the merge later on.
>>
>> It will be followed first by refactorings in the virtual routing
>>resource
>> and the actual on board router scripts and next by the code to add
>> redundancy to the vpc version of the router.
>>
>> thanks,
>>
>> [1] https://github.com/apache/cloudstack/tree/vpc-refactor
>>
>> --
>> Daan
>>
>>
>>
>>
>> --
>> Daan
>>
>
>
>
>-- 
>Karl O. Harris
>Cloud Software Engineer
>Sungard Availability Services
>Office: 215-446-1772
>Cell: 215-264-1855
>karl.harris@sungardas.com


Mime
View raw message