[gsoc-dev] (no subject)

[pranjal mittal]

Cool, I understand the difference b/n a node-group and a rack now.
I was also going through the cluster sanitized JSON file. (prod.json).

(1)
Having a look at the attributes for an Instance, I get this exhaustive list
->

[key]  admin_up  beparams  ctime  disk_template  disks  hvparams
 hypervisor  mtime  name  network_port  nics  os  osparams
*primary_node* serial_no  tags  uuid

The list does have a primary_node, but does NOT have any *secondary_node *
attribute.
Without the secondary_node attribute, how do I figure out what is the
secondary node for a given instance from such a JSON file?
*
*
(2)
But the attributes of a node do have a *primary_ip* and a *secondary_ip.*
What do these mean? Shouldn't a node be having just one IP, (it being on
physical machine)
*
*
(3) What is the difference between master_candidate and master_capable?




On Mon, May 6, 2013 at 8:42 PM, Lance Albertson <lance at osuosl.org> wrote:

>
> On Mon, May 6, 2013 at 5:00 AM, pranjal mittal <mittal.pranjal at gmail.com>wrote:
>
>> Are node-groups in Ganeti same as what we call "racks"?
>> (Collection of related nodes in a cluster, mostly with respect to
>> location?)
>>
>
> They could be but not always. Its just a logical way to separate a set of
> machines based on the admin's choosing. Its typically done in a per-rack
> way or at least per switch. But it does have some sort of locality to it
> always.
>
> --
> Lance Albertson
> Director
> Oregon State University | Open Source Lab
>



-- 
Best Regards,
Pranjal Mittal
B.Tech.  2014
Indian Institute of Technology,BHU
Varanasi, U.P,
India
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osuosl.org/pipermail/gsoc-dev/attachments/20130507/2526e711/attachment.html>