Put these non-oss components somewhere, for both developers and users.
The users keep the jars in hand is also important, consider they want
to install cloudstack with vmware hypervisor, and without internet
access.
On Sat, Sep 15, 2012 at 8:54 AM, Edison Su edison...@citrix.com wrote:
From: Edison Su [edison...@citrix.com]
Sent: Saturday, September 15, 2012 6:24 AM
To: cloudstack-dev@incubator.apache.org
Subject: RE: [DISCUSS] About shipping a non-OSS CloudStack
-Original Message-
From: Wido den Hollander
[
https://issues.apache.org/jira/browse/CLOUDSTACK-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mice Xia reassigned CLOUDSTACK-107:
---
Assignee: Mice Xia
Network domain guest suffix is not getting programmed as part of
[
https://issues.apache.org/jira/browse/CLOUDSTACK-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13456409#comment-13456409
]
Mice Xia commented on CLOUDSTACK-107:
-
[Root Cause]
When creating a VM with
I deploy CS model follow as:
1. MS: 2 NIC card: NIC 1: 192.168.2.100/24 gw 192.168.2.1, NIC 2:
172.15.100.100/24 gw 172.15.100.1. NIC 1 is can connect to Ineternet.
2. Node : 1 NIC with IP 172.15.100.101/24 with XCP. Node connect to MS’s
NIC 2 via a switch.
3. NFS server: 1
Hi Dinh,
You would need to set up port forwarding rules for the guest VMs to enable them
send outbound traffic. In the CS GUI, go to Networks - click on a network that
your VM is associated with - View IP addresses - click on the IP you acquired
for the VM - Configuration - click on view all
Hi guy
I don't think so. I use isolated network with source NAT. Default rule, VR
block all traffic from outside and permit all from VMs to outside. If the cause
is port forwarding rule, I will connect to SSVM, CPVM, VR via their Public IP.
I try setup CS model with only 1 NIC on MS server
Sounds like a routing issue. I would start on the VR and do an 'ip route
show', then look for default gateway and try to ping that. I imagine you
will see the issue there, either wrong IP/network, no route, or no
connectivity (bridging not working).
On Sep 15, 2012 2:07 PM, Nguyễn Đình Việt
Can someone else help me confirm if this is an issue with the codebase or if
it's just happening in my environment.
In global settings set sdn.ovs.controller to true and restart management server.
Using the create zone wizard the physical network tab should display a drop
down for isolation
Chandan Purushothama created CLOUDSTACK-110:
---
Summary: UI - No option available on the UI to edit details of
ROOTdomain - network domain suffix for the ROOT domain cannot be specified
currently
Key: CLOUDSTACK-110
Hi guy,
This is result of 'ip route show' command: default via 192.168.2.1 dev em1,
that right. I think bridging works right because I can ping from guest network
(10.1.1.0/24) to pod range (172.15.100.0/24). Any problem in my network
diagrams ?
MS server has 2 NIC card with connectivity
If your vnets are tied to the correct bridges/interfaces for all VMs involved,
then my money is on ARP/firewall.
Move all the VMs onto a single host, including and VRs.
Then attempt basic network troubleshooting, starting from host to perimeter
router, followed by guest to VR (if applicable)
Also remember that if your VR is the default GW, the you should enable icmp(-1)
on the FW if you using ping to troubleshoot network connectivity.
Sent from my iPhone
On Sep 15, 2012, at 8:46 PM, Nguyễn Đình Việt viet...@viettel.com.vn wrote:
Hi guy,
This is result of 'ip route show'
13 matches
Mail list logo
