cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8506) Make ACS compliant with the RFC 3021
Date Tue, 26 May 2015 09:16:17 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14558908#comment-14558908
] 

ASF GitHub Bot commented on CLOUDSTACK-8506:
--------------------------------------------

GitHub user wilderrodrigues opened a pull request:

    https://github.com/apache/cloudstack/pull/303

    CLOUDSTACK-8506

    Removing the previous logic and adding a method to check if the CIDR is 31 bit prefixed
    Adding tests for the new method
    
    @DaanHoogland, could you have a look?
    
    Tests:
    
    Test advanced zone virtual router ... === TestName: test_advZoneVirtualRouter | Status
: SUCCESS ===
    ok
    Test Deploy Virtual Machine ... === TestName: test_deploy_vm | Status : SUCCESS ===
    ok
    Test Multiple Deploy Virtual Machine ... === TestName: test_deploy_vm_multiple | Status
: SUCCESS ===
    ok
    Test Stop Virtual Machine ... === TestName: test_01_stop_vm | Status : SUCCESS ===
    ok
    Test Start Virtual Machine ... === TestName: test_02_start_vm | Status : SUCCESS ===
    ok
    Test Reboot Virtual Machine ... === TestName: test_03_reboot_vm | Status : SUCCESS ===
    ok
    Test destroy Virtual Machine ... === TestName: test_06_destroy_vm | Status : SUCCESS ===
    ok
    Test recover Virtual Machine ... === TestName: test_07_restore_vm | Status : SUCCESS ===
    ok
    Test migrate VM ... SKIP: At least two hosts should be present in the zone for migration
    Test destroy(expunge) Virtual Machine ... === TestName: test_09_expunge_vm | Status :
SUCCESS ===
    ok
    
    ----------------------------------------------------------------------
    Ran 10 tests in 2662.908s
    
    OK (SKIP=1)
    /tmp//MarvinLogs/test_vm_life_cycle_R8HIX4/results.txt (END
    
    Manual tests:
    
    Added 2 pub networks on my KVM based  DC
    
    ![image](https://cloud.githubusercontent.com/assets/5129209/7809140/791823c8-0398-11e5-863d-279477cadd18.png)
    
    Smae was done for  XenServer 6.32
    
    Cheers,
    Wilder

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/schubergphilis/cloudstack fix/RFC_3021_31_Bit_Prefixes

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/303.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #303
    
----
commit 62736abeb29f1250e3078ec474fc246f7960d80d
Author: wilderrodrigues <wrodrigues@schubergphilis.com>
Date:   2015-05-26T06:48:43Z

    CLOUDSTACK-8506
    
    Removing the previous logic and adding a method to check if the CIDR is 31 bit prefixed
    Adding tests for the new method

----


> Make ACS compliant with the RFC 3021
> ------------------------------------
>
>                 Key: CLOUDSTACK-8506
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8506
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Wilder Rodrigues
>            Assignee: Wilder Rodrigues
>
> On 21 May 2015, at 10:29, Singh, Devender <dsingh@virtela.net> wrote:
> Hi Cloudstack Team,
> We had no problems building and using /31 networks on 4.2.0, but after our upgrade to
4.4.2  we are no longer able to add new ones.
> We have a lot of them already in place.  As an example I pasted some output from cloudmonkey
on a link that is already established and working.
> Does anyone have a workaround, or can point me in the right direction for a patch?
> (local) > list networks id=e044c442-48f7-4bae-8c5d-530423a249f7
> count = 1
> network:
> id = e044c442-48f7-4bae-8c5d-530423a249f7
> name = VLAN180
> acltype = Domain
> broadcastdomaintype = Vlan
> broadcasturi = vlan://180
> canusefordeploy = False
> cidr = 202.90.43.0/31
> displaynetwork = True
> displaytext = VM-UTILITY-2
> dns1 = 4.2.2.1
> domain = ROOT
> domainid = 8acf0368-e5b1-11e2-b5cf-2ef4cf18a6ae
> gateway = 202.90.43.0
> ispersistent = False
> issystem = False
> netmask = 255.255.255.254
> networkofferingavailability = Optional
> networkofferingconservemode = False
> networkofferingdisplaytext = private-guest1_switch
> networkofferingid = 0b63d457-5f5e-426f-a81e-8797e522eb8c
> networkofferingname = private-guest1_switch
> physicalnetworkid = cf4c2846-2418-4ba4-b307-6a6405860799
> related = e044c442-48f7-4bae-8c5d-530423a249f7
> restartrequired = False
> service:
> specifyipranges = True
> state = Setup
> strechedl2subnet = False
> subdomainaccess = True
> tags:
> traffictype = Guest
> type = Shared
> vlan = 180
> zoneid = 88066cb4-64ab-4c54-83a9-3279a1e030cb
> zonename = UTILITY-ZONE-1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message