Thank you. When I attempted that, it kept trying to reach primary storage over 
the Cloudbr0 that I specified for management on the KVM hosts.

Is there any labeling or bridge I need to do in KVM? Or will it use the open 
card? I guess how does it know which open interface to use for primary storage?



On 10/25/16, 2:59 PM, "Simon Weller" <swel...@ena.com> wrote:

    Just connect the storage via a different physical network (or vlan) to the 
hosts. You don't need to do any tagging in ACS management for it. The host 
agents talk to the storage, so as long as the agent can see the primary 
storage, you should be good to go.
    
    
    - Si
    
    
    ________________________________
    From: Nassir Jamal <nassir.ja...@avalontech.net>
    Sent: Tuesday, October 25, 2016 2:50 PM
    To: users@cloudstack.apache.org
    Subject: Re: Separate Management and Primary Storage
    
    Currently NFS, but I'm waiting to add Ceph until this is figured out.
    
    Thank You Simon
    
    
    On 10/25/16, 2:48 PM, "Simon Weller" <swel...@ena.com> wrote:
    
        Nassar,
    
    
        What type of primary storage are you using?
    
    
        - Si
    
    
        ________________________________
        From: Nassir Jamal <nassir.ja...@avalontech.net>
        Sent: Tuesday, October 25, 2016 2:41 PM
        To: users@cloudstack.apache.org
        Subject: Separate Management and Primary Storage
    
        Hello,
    
        Can somebody please provide the steps to separate Management traffic 
from Primary Storage with KVM?
    
        I've deployed a storage label but that's only for secondary storage. So 
how do I do that with Primary storage? Can I add it back to an existing 
Advanced zone? Or Do I need to deploy a new one?
    
        Cloudstack docs say it's basically another management interface on a 
whole other subnet. But how do you add that and define another management on 
KVM? No option in the zone to add another mgmt. interface. We are currently on 
version 4.8.
    
        Thank You
    
    
    

Reply via email to