Hi- Please help me in this regard.
Thanking you all... -- Trinath S On Tue, Jul 3, 2012 at 4:54 PM, Trinath Somanchi <trinath.soman...@gmail.com > wrote: > Hi- > > With respect to the web link > http://wiki.openstack.org/HeterogeneousTileraSupport, > > " > > For supporting non-x86 architecture (ex. TILERA), Proxy Compute Node > should be designed. > An x86 Proxy Compute Node is connected to the TILEmpower boards through > network. A Proxy Compute Node may handle multiple TILEmpower boards. > TILEmpower boards are connected to the network such that a cloud user can > ssh into them directly after an instance starts on the TILEmpower board. A > TILEmpower board is configured to be tftp-bootable or nfs-bootable. Proxy > Compute Node behaves as the tftp/nfs server for the TILEmpower boards. *After > Proxy Compute node receives instance images from the image server, it wakes > up a TILEmpower board and controls their booting.* Once a TILEmpower > board is booted, Proxy Compute Node doesn't do anything except > terminating/rebooting/power-down/power-up of the board. Once Tilera > instance is running, user can access the TILEmpower board, not Proxy > Compute Node, through ssh. Here, we assume that Proxy Compute Node can > power on/off TILEmpower boards remotely using PDU(Power Distribute Unit). > The block diagram shown below describes the procedure in detail........... > > " > > In an general environment, Nova-compute with the help of Nova-scheduler, > boots an image instance at Server-2/ESSEX-2/Nova-agent server. > > Can any one help me in understanding the above colored lines .... > > Thanking you... > > -- > Trinath S > > > > > On Tue, Jul 3, 2012 at 12:27 PM, Trinath Somanchi < > trinath.soman...@gmail.com> wrote: > >> Hi- >> >> Thanks a lot for the reply... This helped me understand a bit more. >> >> I have this kind of setup in mind. >> >> >> >> [ ESSEX-1] <---------------> [ ESSEX-2 ] <---------------> [<--- >> TILERA HW--->] >> >> x_86 HW x_86 HW >> NON x_86 HW >> >> Nova-Compute Proxy-Nova-Compute New Hardware >> Device. >> >> >> >> >> >> So, change the config in nova.conf in ESSEX-2 server to bare-metal and >> tilera specific config makes the nova-compute to proxy-nova-compute. >> >> I have a doubt here, I have an idea on using Nova-compute to bringing up >> VM's in ESSEX-2 when its another Nova-compute. But not we have >> Proxy-Nova-compute in the ESSEX-2 and we have no VM's here rather we have >> new Hardware board to bootup. >> >> How will the Commands from Nova-compute in ESSEX-1 differ to bring up >> TILERA HW board using the Proxy-Nova-compute in ESSEX-2 ? >> >> Please kindly help me understand this scenario. >> >> Thanks a lot for the reply... >> -- >> Trinath S. >> >> >> >> >> >> >> On Tue, Jul 3, 2012 at 12:54 AM, John Paul Walters <jwalt...@isi.edu>wrote: >> >>> Hi Trinath, >>> >>> It's not clear whether the tilera board you're referring to is one of >>> the PCI versions or a stand-alone board (is it in Essex-1?). We've never >>> setup/tested anything other than the TILEmpower stand-alone board with our >>> bare-metal provisioning service. That said, in order to make your >>> nova-compute on Essex-2, you need to configure nova.conf as I described >>> earlier: set the connection_type=baremetal, set the >>> baremetal_driver=tilera, and set your path to tile-monitor appropriately. >>> That's what makes it a proxy node, which is otherwise run as a regular >>> nova-compute. >>> >>> JP >>> >>> >>> On Jul 2, 2012, at 12:42 PM, Trinath Somanchi wrote: >>> >>> Hi- >>> >>> Thanks a lot for the reply JP. >>> >>> The information provided is of most value for me. >>> >>> I have a doubt here. >>> >>> I will install Nova-compute in a server say Essex-1 and another server >>> say Essex-2. >>> >>> I have a tilera board too in the setup. >>> >>> Can you please guide me on how to start this tilera board using >>> Nova-compute in Essex-1 machine. and How Nova-compute in Essex-2 can be >>> made as Proxy-Nova-compute. I mean what changes to Nova-compute makes Proxy >>> nova-compute. >>> >>> On Mon, Jul 2, 2012 at 9:32 PM, John Paul Walters <jwalt...@isi.edu>wrote: >>> >>>> Hi Trinath, >>>> >>>> Our baremetal experts are on vacation for the next week or so, so I'll >>>> take a stab at answering in their absence. First, just to be clear, right >>>> now the baremetal work that's present in Essex supports ONLY the Tilera >>>> architecture. We're working with the NTT folks to add additional support, >>>> but it's not in Essex. We've tested on TILEmpower rack-mountable units. >>>> You'll need a baremetal proxy (x86) machine that will run nova-compute and >>>> handle the provisioning of resources. Most of the nova.conf options are >>>> shown at: >>>> >>>> >>>> http://docs.openstack.org/essex/openstack-compute/admin/content/compute-options-reference.html >>>> >>>> But it appears that there's at least one omission: you'll need to set >>>> your --connection_type=baremetal on the proxy node. Probably the most >>>> important options are: --baremetal_driver=tilera, >>>> --tile_monitor=</path/to/tile-monitor/>. I would suggest that you have a >>>> look at the link above under the baremetal section to see what other >>>> options might apply to your environment. >>>> >>>> http://wiki.openstack.org/HeterogeneousTileraSupport >>>> >>>> Note that you'll need to set up tftp so that the Tilera boards can pick >>>> up a boot rom. You'll also need to create a tilera-specific file system. >>>> >>>> I hope this helps. >>>> >>>> best, >>>> JP >>>> >>>> >>>> On Jul 2, 2012, at 8:05 AM, Trinath Somanchi wrote: >>>> >>>> Hi- >>>> >>>> Please help me in understanding and bringing up this kind of setup.... >>>> >>>> Kindly please help me in this regard. >>>> >>>> I have checked nova.conf and found bare metal provisioning support >>>> options. >>>> >>>> Please help me understand on how modifying nova.conf with the >>>> respective options can help bringing up tilera like machines up either from >>>> command line or from GUI. >>>> >>>> Thanks in advance.. >>>> >>>> -- >>>> Trinath S >>>> >>>> On Mon, Jul 2, 2012 at 12:13 PM, Trinath Somanchi < >>>> trinath.soman...@gmail.com> wrote: >>>> >>>>> Hi- >>>>> >>>>> As explained in the email, With respect to the link, >>>>> >>>>> http://wiki.openstack.org/GeneralBareMetalProvisioningFramework >>>>> >>>>> Can you kindly guide/brief me on >>>>> https://github.com/usc-isi/essex-baremetal-support (Stable/Essex) >>>>> >>>>> I mean Install/Config/Testing of the Provisioning support. >>>>> >>>>> Thanking you, >>>>> >>>>> -- >>>>> Regards, >>>>> ---------------------------------------------- >>>>> Trinath Somanchi, >>>>> +91 9866 235 130 >>>>> >>>>> >>>> >>>> >>>> -- >>>> Regards, >>>> ---------------------------------------------- >>>> Trinath Somanchi, >>>> +91 9866 235 130 >>>> >>>> _______________________________________________ >>>> Mailing list: https://launchpad.net/~openstack >>>> Post to : openstack@lists.launchpad.net >>>> Unsubscribe : https://launchpad.net/~openstack >>>> More help : https://help.launchpad.net/ListHelp >>>> >>>> >>>> >>> >>> >>> -- >>> Regards, >>> ---------------------------------------------- >>> Trinath Somanchi, >>> +91 9866 235 130 >>> >>> >>> >> >> >> -- >> Regards, >> ---------------------------------------------- >> Trinath Somanchi, >> +91 9866 235 130 >> >> > > > -- > Regards, > ---------------------------------------------- > Trinath Somanchi, > +91 9866 235 130 > > -- Regards, ---------------------------------------------- Trinath Somanchi, +91 9866 235 130
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp