cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Miguel Roble (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-3578) Unable to add Physical Dom0 as host, on a cloudstack physical machine.
Date Thu, 25 Jul 2013 10:07:48 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Miguel Roble updated CLOUDSTACK-3578:
-------------------------------------

    Description: 
I have a laptop where Cloudstack 4.1 is installed on CentOS 6.4

My goal is to add this Physical dom0 using cloudstack gui, 
I have tried different scenarios and apparently I have no success.

Please let me know what details you need for I can provide.
As of the moment, I have included the scenario/s I have did. 

--- --- --- >
Scenario 1.0:
Add zone.
1) Zone name: Zone1
DNS1: 192.168.10.1
Internal DNS: 192.168.10.1
Hypervisor: XenServer
Network Offering: DefaultSharedNetworkOfferingWithSGService
Public: On

Add pod. The IP address of dom0 is: 192.168.10.2 -- I am not sure If I should or should not
include it.
2) Pod name: Pod1
Reserved system gateway: 192.168.10.1 
Reserved system netmask: 255.255.255.0
Start Reserved system IP: 192.168.10.2
End Reserved system IP: 192.168.10.19

Guest traffic.
2.1) Guest gateway: 192.168.10.1
Guest netmask: 255.255.255.0
Guest start IP:192.168.10.20
Guest end IP: 192.168.10.29

Add cluster.
3) Hypervisor: XenServer
Cluster name: Cluster1

Add host. 
4) Host name: xenbox.serv1.com
(i used the hostname of my dom0 -- xenbox.serv1.com)
Username: root
Password: deepsecurity

Add primary storage.
5) *Name: Primary Storage
*Protocol: iscsi
*Server: sanbox.serv1.com
*Target IQN: iqn.2013-07.com.openfiler:iscsi.storage.primary
*LUN #: 0

Add secondary storage.
6) NFS Server: cloudbox.serv1.com
Path: /export/secondary

==========
Result:
Creating zone...
Creating physical networks...OK!
Configuring physical networks...OK!
Enabling Security Group provider...OK!
Creating guest network...OK!
Creating pod...OK!
Configuring guest traffic...OK!
Creating cluster...OK!
Adding host...Not OK!
Something went wrong; please correct the following:
Unable to add the host
< --- --- ----

--- --- --- >
Scenario 1.1:
1) Zone is the same.
2) Pod is the same.
2.1) Guest traffic is the same.
3) Cluster is the same.

Add host. I changed the Host name to dom0's IP address:
4) Host name: 192.168.10.2
Username: root
Password: deepsecurity

5) Primary storage the same.
6) Secondary storage the same.
==========
Adding host...Not OK!
Something went wrong; please correct the following:
Unable to add the host
< --- --- ---

--- --- --- >
Scenario 1.2:
1) Zone is the same.

Add pod. I removed the IP address of my dom0 this time.
2) Pod name: Pod1
Reserved system gateway: 192.168.10.1 
Reserved system netmask: 255.255.255.0
Start Reserved system IP: 192.168.10.10
End Reserved system IP: 192.168.10.19

2.1) Guest traffic is the same.
3) Cluster is the same.

Add host. Same as Scenario 1.0
4) Host name: xenbox.serv1.com
Username: root
Password: deepsecurity

5) Primary storage the same.
6) Secondary storage the same.
==========
Adding host...Not OK!
Something went wrong; please correct the following:
Unable to add the host
< --- --- ---

--- --- --- >
Scenario 1.3
1) Zone is the same.

2) Pod is the same in Scenario 1.2. Dom0 IP address is not included.
2.1) Guest traffic is the same.
3) Cluster is the same.

Add host. I changed the Host name to dom0's IP address:
4) Host name: 192.168.10.2
Username: root
Password: deepsecurity

5) Primary storage the same.
6) Secondary storage the same.
==========
Adding host...Not OK!
Something went wrong; please correct the following:
Unable to add the host

  was:
I have a domU/1 where Cloudstack 4.1 is installed on CentOS 6.4
This domU/1 is under the Physical dom0.

My goal is to add this Physical dom0 using cloudstack gui, 
I have tried different scenarios and apparently I have no success.

Please let me know what details you need for I can provide.
As of the moment, I have included the scenario/s I have did. 

--- --- --- >
Scenario 1.0:
Add zone.
1) Zone name: Zone1
DNS1: 192.168.10.1
Internal DNS: 192.168.10.1
Hypervisor: XenServer
Network Offering: DefaultSharedNetworkOfferingWithSGService
Public: On

Add pod. The IP address of dom0 is: 192.168.10.2 -- I am not sure If I should or should not
include it.
2) Pod name: Pod1
Reserved system gateway: 192.168.10.1 
Reserved system netmask: 255.255.255.0
Start Reserved system IP: 192.168.10.2
End Reserved system IP: 192.168.10.19

Guest traffic.
2.1) Guest gateway: 192.168.10.1
Guest netmask: 255.255.255.0
Guest start IP:192.168.10.20
Guest end IP: 192.168.10.29

Add cluster.
3) Hypervisor: XenServer
Cluster name: Cluster1

Add host. 
4) Host name: xenbox.serv1.com
(i used the hostname of my dom0 -- xenbox.serv1.com)
Username: root
Password: deepsecurity

Add primary storage.
5) *Name: Primary Storage
*Protocol: iscsi
*Server: sanbox.serv1.com
*Target IQN: iqn.2013-07.com.openfiler:iscsi.storage.primary
*LUN #: 0

Add secondary storage.
6) NFS Server: cloudbox.serv1.com
Path: /export/secondary

==========
Result:
Creating zone...
Creating physical networks...OK!
Configuring physical networks...OK!
Enabling Security Group provider...OK!
Creating guest network...OK!
Creating pod...OK!
Configuring guest traffic...OK!
Creating cluster...OK!
Adding host...Not OK!
Something went wrong; please correct the following:
Unable to add the host
< --- --- ----

--- --- --- >
Scenario 1.1:
1) Zone is the same.
2) Pod is the same.
2.1) Guest traffic is the same.
3) Cluster is the same.

Add host. I changed the Host name to dom0's IP address:
4) Host name: 192.168.10.2
Username: root
Password: deepsecurity

5) Primary storage the same.
6) Secondary storage the same.
==========
Adding host...Not OK!
Something went wrong; please correct the following:
Unable to add the host
< --- --- ---

--- --- --- >
Scenario 1.2:
1) Zone is the same.

Add pod. I removed the IP address of my dom0 this time.
2) Pod name: Pod1
Reserved system gateway: 192.168.10.1 
Reserved system netmask: 255.255.255.0
Start Reserved system IP: 192.168.10.10
End Reserved system IP: 192.168.10.19

2.1) Guest traffic is the same.
3) Cluster is the same.

Add host. Same as Scenario 1.0
4) Host name: xenbox.serv1.com
Username: root
Password: deepsecurity

5) Primary storage the same.
6) Secondary storage the same.
==========
Adding host...Not OK!
Something went wrong; please correct the following:
Unable to add the host
< --- --- ---

--- --- --- >
Scenario 1.3
1) Zone is the same.

2) Pod is the same in Scenario 1.2. Dom0 IP address is not included.
2.1) Guest traffic is the same.
3) Cluster is the same.

Add host. I changed the Host name to dom0's IP address:
4) Host name: 192.168.10.2
Username: root
Password: deepsecurity

5) Primary storage the same.
6) Secondary storage the same.
==========
Adding host...Not OK!
Something went wrong; please correct the following:
Unable to add the host

    
> Unable to add Physical Dom0 as host, on a cloudstack physical machine.
> ----------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3578
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3578
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Baremetal, Management Server, Xen
>    Affects Versions: 4.1.0
>         Environment: Host / Dom0:
> 1) Hardware:
> IBM x3300
> 32GB DDR3 RDIMM
> Intel Xeon 4C E5-2407
> 2) Software
> Xen hypervisor 4 on Debian 6.0.7
> To give clarification, this is Xen, not XenServer.
> Physical Machine / Laptop
> 1) Cloudstack 4.1 installed on CentOS 6.4
>            Reporter: Miguel Roble
>         Attachments: unable-to-add-host-log.txt
>
>   Original Estimate: 60h
>  Remaining Estimate: 60h
>
> I have a laptop where Cloudstack 4.1 is installed on CentOS 6.4
> My goal is to add this Physical dom0 using cloudstack gui, 
> I have tried different scenarios and apparently I have no success.
> Please let me know what details you need for I can provide.
> As of the moment, I have included the scenario/s I have did. 
> --- --- --- >
> Scenario 1.0:
> Add zone.
> 1) Zone name: Zone1
> DNS1: 192.168.10.1
> Internal DNS: 192.168.10.1
> Hypervisor: XenServer
> Network Offering: DefaultSharedNetworkOfferingWithSGService
> Public: On
> Add pod. The IP address of dom0 is: 192.168.10.2 -- I am not sure If I should or should
not include it.
> 2) Pod name: Pod1
> Reserved system gateway: 192.168.10.1 
> Reserved system netmask: 255.255.255.0
> Start Reserved system IP: 192.168.10.2
> End Reserved system IP: 192.168.10.19
> Guest traffic.
> 2.1) Guest gateway: 192.168.10.1
> Guest netmask: 255.255.255.0
> Guest start IP:192.168.10.20
> Guest end IP: 192.168.10.29
> Add cluster.
> 3) Hypervisor: XenServer
> Cluster name: Cluster1
> Add host. 
> 4) Host name: xenbox.serv1.com
> (i used the hostname of my dom0 -- xenbox.serv1.com)
> Username: root
> Password: deepsecurity
> Add primary storage.
> 5) *Name: Primary Storage
> *Protocol: iscsi
> *Server: sanbox.serv1.com
> *Target IQN: iqn.2013-07.com.openfiler:iscsi.storage.primary
> *LUN #: 0
> Add secondary storage.
> 6) NFS Server: cloudbox.serv1.com
> Path: /export/secondary
> ==========
> Result:
> Creating zone...
> Creating physical networks...OK!
> Configuring physical networks...OK!
> Enabling Security Group provider...OK!
> Creating guest network...OK!
> Creating pod...OK!
> Configuring guest traffic...OK!
> Creating cluster...OK!
> Adding host...Not OK!
> Something went wrong; please correct the following:
> Unable to add the host
> < --- --- ----
> --- --- --- >
> Scenario 1.1:
> 1) Zone is the same.
> 2) Pod is the same.
> 2.1) Guest traffic is the same.
> 3) Cluster is the same.
> Add host. I changed the Host name to dom0's IP address:
> 4) Host name: 192.168.10.2
> Username: root
> Password: deepsecurity
> 5) Primary storage the same.
> 6) Secondary storage the same.
> ==========
> Adding host...Not OK!
> Something went wrong; please correct the following:
> Unable to add the host
> < --- --- ---
> --- --- --- >
> Scenario 1.2:
> 1) Zone is the same.
> Add pod. I removed the IP address of my dom0 this time.
> 2) Pod name: Pod1
> Reserved system gateway: 192.168.10.1 
> Reserved system netmask: 255.255.255.0
> Start Reserved system IP: 192.168.10.10
> End Reserved system IP: 192.168.10.19
> 2.1) Guest traffic is the same.
> 3) Cluster is the same.
> Add host. Same as Scenario 1.0
> 4) Host name: xenbox.serv1.com
> Username: root
> Password: deepsecurity
> 5) Primary storage the same.
> 6) Secondary storage the same.
> ==========
> Adding host...Not OK!
> Something went wrong; please correct the following:
> Unable to add the host
> < --- --- ---
> --- --- --- >
> Scenario 1.3
> 1) Zone is the same.
> 2) Pod is the same in Scenario 1.2. Dom0 IP address is not included.
> 2.1) Guest traffic is the same.
> 3) Cluster is the same.
> Add host. I changed the Host name to dom0's IP address:
> 4) Host name: 192.168.10.2
> Username: root
> Password: deepsecurity
> 5) Primary storage the same.
> 6) Secondary storage the same.
> ==========
> Adding host...Not OK!
> Something went wrong; please correct the following:
> Unable to add the host

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

Mime
View raw message