You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Musayev, Ilya" <im...@webmd.net> on 2013/03/20 02:04:19 UTC
RE: [jira] [Created] (CLOUDSTACK-1733) [ACS41][UI] Add guest
network is missing ip range fields and missing network offerings
Just to be clear, the drop down for network offering when I create a new network only has one option (DefaultIsolatedNetworkOfferingWithSourceNatting).
Looked into API Call, when listNetworkOfferings call is constructed, for some reason we are forcing the "supportedServices=SourceNat".
Is this necessary for shared env. ? we would prefer to manage this option ourselves.
Thanks
ilya
> -----Original Message-----
> From: ilya musayev (JIRA) [mailto:jira@apache.org]
> Sent: Tuesday, March 19, 2013 8:17 PM
> To: cloudstack-issues@incubator.apache.org
> Subject: [jira] [Created] (CLOUDSTACK-1733) [ACS41][UI] Add guest network
> is missing ip range fields and missing network offerings
>
> ilya musayev created CLOUDSTACK-1733:
> ----------------------------------------
>
> Summary: [ACS41][UI] Add guest network is missing ip range fields and
> missing network offerings
> Key: CLOUDSTACK-1733
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1733
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public (Anyone can view this level - this is the default.)
> Affects Versions: 4.1.0
> Environment: ACS 4.1 as of 03/18/2013
> Reporter: ilya musayev
> Priority: Blocker
>
>
> Noticed 2 issues in latest ACS41 when I attempt to add a network using
> Advanced Zones shared network - "without natting".
>
> Issue 1:
>
> Network Offering has DefaultIsolatedWithSourceNat - I don't see the
> network offering I've created.
>
> Issue 2:
> IPv4 IP Range is no longer visible. Previous (2 weeks back) behavior was, we
> had IPv6 enabled and required, now we are missing both IPv4 and IPv6.
>
>
> https://www.diigo.com/item/image/3qjce/3m5o
>
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira