fuel-dev team mailing list archive

[Miroslav Anashkin <manashkin@xxxxxxxxxxxx>]

Hi all,

Sorry for delay with answer, I am fighting critical issue.
I'll answer to these questions ASAP.

Kind regards,
Miroslav


On Thu, May 15, 2014 at 6:33 PM, Gandhirajan Mariappan (CW) <
gmariapp@xxxxxxxxxxx> wrote:

> Hi Miroslav,
>
>
>
> We have few more queries with respect to Fuel Installation. Kindly clarify
> us on the below 6 queries.
>
>
>
> *Setup Details:*
>
>
>
> Ø  Our setup is as follows. I have configured VLAN configurations in the
> switch (switch details are provided at end of the mail). Kindly let us know
> if we need to do any more configuration in VDX device where nodes are
> connected.
>
>
>
>
>
> [image: Uplink switch Gateway:10.24.40.1]
>
>
>
>
>
>
>
>
>
>
>
>
> Eth0
> Eth0                                                         Eth0
>
> [image: Physical Server 10.24.41.121 ,Physical Server 10.24.41.122][image:
> Physical Server 10.24.41.123]
>
>
>
>
>
> Eth1
> Eth1                                         Eth1
>
>
>
>
>
>
>
>                                                    13
>
> [image: Brocade VDX 10.25.225.133]
>                 7                                              21
>
>
>
>
>
>
>
>
>
>
> *Physical Server 10.24.41.121 -> Fuel Master Node*
>
> *Physical Server 10.24.41.122 -> Slave 1. To be act as “Controller
> Node/Cinder node”*
>
> *Physical Server 10.24.41.123 -> Slave 2. To be act as “Compute Node”*
>
>
>
> *Fuel Master – Physical or VM:*
>
>
>
> Ø  I have 4 VMs (fuel master node IP : 10.20.0.2, fuel slave 1 :
> 10.20.0.217, slave 2 : 10.20.0.252 and slave 3 : 10.20.0.198) hosted on a
> physical machine(Ubuntu 12.0.4 LTS running machine - 10.24.41.121). Is it
> mandatory to have Fuel master node as VM? Or can Fuel master node be
> physical server as well? If yes, what is the configuration to do the same.
>
>
>
> *Configuration change in config.sh:*
>
> Ø  Do we need to configure the physical server IP address (10.24.41.122
> and 10.24.41.123) in config.sh present at 10.24.41.121 (master), so that
> while running launch.sh, PXE boot will deploy configuration in 10.24.41.122
> and 10.24.41.123? With existing launch.sh script, 3 slave nodes (VMs) are
> getting created in 10.24.41.121.
>
>
>
> Ø  Do we need to install/configure anything to accommodate physical
> servers (10.24.41.122 and 10.24.41.123) as Slave nodes?
>
>
>
> Ø  Once the query 4) configuration is done, will the master node
> (10.24.41.121) discovered automatically in Fuel or do we need to discover
> the nodes manually?
>
>
>
> *Network Setting tab:*
>
>
>
> Ø  In Network Settings tab, We have various IP addresses for each
> network. With our existing setup above, how can we set our IP addresses and
> other details?
>
>
>
> *ISO image for Slave nodes:*
>
>
>
> Ø  Do we need to install same iso image (Mirantis 5.0) in slave nodes
> (10.24.41.122 and 10.24.41.123), which we already installed in master node
> (10.24.41.121) ?
>
>
>
>
>
> *VDX Device Configuration:*
>
>
>
> *interface TenGigabitEthernet 133/0/7*
>
> *switchport*
>
> * switchport mode trunk*
>
> * switchport trunk tag native-vlan*
>
> * switchport trunk native-vlan 102*
>
>
>
> *interface TenGigabitEthernet 133/0/13*
>
> *switchport*
>
> * switchport mode trunk*
>
> * switchport trunk tag native-vlan*
>
> * switchport trunk native-vlan 102*
>
>
>
> *interface TenGigabitEthernet 133/0/21*
>
> *switchport*
>
> * switchport mode trunk*
>
> * switchport trunk tag native-vlan*
>
> * switchport trunk native-vlan 102*
>
>
>
> sw0# show vlan 102
>
> VLAN       Name            State                      Ports
>
> (F)-FCoE                                             (u)-Untagged,
> (t)-Tagged
>
> (R)-RSPAN                                            (c)-Converged
>
> ======== =============== ==========================
> ================================================
>
> 102      VLAN0102        ACTIVE                     Te 139/0/13(c)   Te
> 133/0/24(c)
>
>                                                     Te 133/0/21(t)   Te
> 133/0/18(c)
>
>                                                     Te 133/0/17(c)   Te
> 133/0/16(c)
>
>                                                     Te 133/0/14(c)   Te
> 133/0/13(t)
>
>                                                     Te 133/0/7(t)
>
>
>
>
>
> It would be great if we have Live discussion/meeting to get us clarified.
> Please let us know if you are fine with the call and do share us the call
> details.
>
>
>
> Thanks and Regards,
>
> Gandhi Rajan
>
>
>



-- 

*Kind Regards*

*Miroslav Anashkin**L2 support engineer**,*
*Mirantis Inc.*
*+7(495)640-4944 (office receptionist)*
*+1(650)587-5200 (office receptionist, call from US)*
*35b, Bld. 3, Vorontsovskaya St.*
*Moscow**, Russia, 109147.*

www.mirantis.com

manashkin@xxxxxxxxxxxx