incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Musayev, Ilya" <>
Subject RE: [jira] [Commented] (CLOUDSTACK-563) Unable to create guest network in UI for Advanced Zone
Date Mon, 03 Dec 2012 20:39:33 GMT
Sorry wrong picture was attached for #1:

-----Original Message-----
From: Musayev, Ilya (JIRA) [] 
Sent: Monday, December 03, 2012 3:34 PM
Subject: [jira] [Commented] (CLOUDSTACK-563) Unable to create guest network in UI for Advanced


Musayev, Ilya commented on CLOUDSTACK-563:

Hi Brian,

So I think there are 2 issues in this request:

1) Not able to see the NetworkOfferings as a drop down. I've attached an image of what I see
in firebug. 

I also clicked on each relevant API call to see what I get and I would get nothing for networkoffering.

2) Conceptually - don’t we have to bind the Network to Network Offering and Physical Network
- when you do Advanced Network Setup?


> Unable to create guest network in UI for Advanced Zone
> ------------------------------------------------------
>                 Key: CLOUDSTACK-563
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>    Affects Versions: 4.0.0
>         Environment: CS 4.0 on CentOS 6.3 vSphere 5.0 clusters with 
> Advanced networks
>            Reporter: ilya musayev
>            Assignee: Brian Federle
>              Labels: Bug, UI
> The UI would not allow for creation of guest Network.  - Please look at the attached
> Screenshot -
> The drop down for NetworkOfferings is blank There is a dropdown for 
> VPC - which is also blank (not needed for shared networks) We also 
> need the ability to pick the proper Physical Network Name - which is 
> not available/ This feature is also broken in the Add A Zone wizard, i will open a separate
bug request for that.

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:

View raw message