Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Sat, 23 May 2015 08:58:17 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12832156.1432299323000.16246.1432371497519@Atlassian.JIRA>
In-Reply-To: <JIRA.12832156.1432299323000@Atlassian.JIRA>
References: <JIRA.12832156.1432299323000@Atlassian.JIRA>
 <JIRA.12832156.1432299323816@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-8506) Make ACS compliant with the
 RFC 3021
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Github user wilderrodrigues commented on the pull request:

    https://github.com/apache/cloudstack/pull/292#issuecomment-104871245
  
    @DaanHoogland , I also commented on your comments.
    
    Which bit is hard to review? Put a lot of test results and also did the manual tests for the public networks, followed by new unit tests.
    
    Can we merge it? If so, I would also suggest to get it on 4.4.4 and 4.5.
    
    Cheers,
    Wilder


> 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)