Re: [Question]Please teach a sample of corosync.conf.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



even better :-)
thanks for confirming

On Tue, May 29, 2012 at 10:17 AM,  <renayama19661014@xxxxxxxxx> wrote:
> Hi Andrew,
>
>> But the interfaces were still needed?
>> I had hoped that this would not be the case as all the information
>> there can be inferred once you know the nodeid.
>
> Thank you for advice.
>
> You were right, and interface was unnecessary.
> Last conf was as follows.
>
> totem {
>        version: 2
>        secauth: off
>        rrp_mode:active
>        transport: udpu
> }
>
> (snip)
> quorum {
>        provider: corosync_votequorum
>        votes: 1
> }
>
> nodelist {
>        node {
>                ring0_addr: 2001:db8:50::250
>                ring1_addr: 2001:db8:60::250
>                nodeid: 1
>        }
>       node {
>                ring0_addr: 2001:db8:50::251
>                ring1_addr: 2001:db8:60::251
>                nodeid: 2
>        }
> }
>
> Many Thanks,
> Hideo Yamauchi.
> --- On Mon, 2012/5/28, Andrew Beekhof <andrew@xxxxxxxxxxx> wrote:
>
>> On Mon, May 28, 2012 at 10:20 AM,  <renayama19661014@xxxxxxxxx> wrote:
>> > Hi Digmer,
>> > Hi Andrew,
>> >
>> > I confirmed that it was not necessary to appoint nodeid in totem.
>>
>> But the interfaces were still needed?
>> I had hoped that this would not be the case as all the information
>> there can be inferred once you know the nodeid.
>>
>> > Please revise node2 equally.
>> >
>> > --------- node1 /etc/corosync.conf -----------------------------
>> > # Please read the corosync.conf.5 manual page
>> > compatibility: whitetank
>> >
>> > totem {
>> >        version: 2
>> >        secauth: off
>> >        rrp_mode:active
>> >        interface {
>> >                ringnumber: 0
>> >                bindnetaddr: 2001:db8:50::250
>> >                ttl: 1
>> >        }
>> >        interface {
>> >                ringnumber: 1
>> >                bindnetaddr: 2001:db8:60::250
>> >                ttl: 1
>> >        }
>> >        transport: udpu
>> > }
>> > (snip)
>> > quorum {
>> >        provider: corosync_votequorum
>> >        votes: 1
>> > }
>> >
>> > nodelist {
>> >        node {
>> >                ring0_addr: 2001:db8:50::250
>> >                ring1_addr: 2001:db8:60::250
>> >                nodeid: 1
>> >        }
>> >        node {
>> >                ring0_addr: 2001:db8:50::251
>> >                ring1_addr: 2001:db8:60::251
>> >                nodeid: 2
>> >        }
>> > }
>> > --------------------------------------
>> >
>> > Many thanks!
>> > Hideo Yamauchi.
>> >
>> >
>> >
>> > --- On Sat, 2012/5/26, renayama19661014@xxxxxxxxx <renayama19661014@xxxxxxxxx> wrote:
>> >
>> >> Hi Andrew,
>> >>
>> >> Sorry...
>> >>
>> >> In corosync.conf which I sent, there might be still room for the correction.
>> >> I will confirm your opinion next week.
>> >>
>> >> Many Thanks,
>> >> Hideo Yamauchi.
>> >>
>> >>
>> >>
>> >> --- On Fri, 2012/5/25, Andrew Beekhof <andrew@xxxxxxxxxxx> wrote:
>> >>
>> >> > Why the duplication?
>> >> > Surely nodeid in totem {} should be enough for corosync to pick the
>> >> > right nodelist entry.
>> >> >
>> >> > On Fri, May 25, 2012 at 11:48 AM, Digimer <lists@xxxxxxxxxx> wrote:
>> >> > > With Yamauchi-san's permission to repost, here is the sample config;
>> >> > >
>> >> > > ========
>> >> > > All right!
>> >> > >  * Please rearrange the addresses as needed.
>> >> > >
>> >> > > Step 1) Because corosync did not support private IP address, I added a
>> >> > > global address to node beforehand.
>> >> > >
>> >> > >  [root@rh62-coro2-1 ~]# ifconfig eth1 add 2001:db8:50::250/64
>> >> > >  [root@rh62-coro2-1 ~]# ifconfig eth2 add 2001:db8:60::250/64
>> >> > >  [root@rh62-coro2-2 ~]# ifconfig eth1 add 2001:db8:50::251/64
>> >> > >  [root@rh62-coro2-2 ~]# ifconfig eth2 add 2001:db8:60::251/64
>> >> > >
>> >> > > Step2) I placed next corosync.conf in two nodes.
>> >> > >  * rh62-coro2-1
>> >> > > totem {
>> >> > >        version: 2
>> >> > >        secauth: off
>> >> > >        rrp_mode:active
>> >> > >        nodeid : 1
>> >> > >        interface {
>> >> > >                ringnumber: 0
>> >> > >                bindnetaddr: 2001:db8:50::250
>> >> > >                ttl: 1
>> >> > >        }
>> >> > >        interface {
>> >> > >                ringnumber: 1
>> >> > >                bindnetaddr: 2001:db8:60::250
>> >> > >                ttl: 1
>> >> > >        }
>> >> > >        transport: udpu
>> >> > > }
>> >> > >
>> >> > > (snip)
>> >> > >
>> >> > > quorum {
>> >> > >        provider: corosync_votequorum
>> >> > >        votes: 1
>> >> > > }
>> >> > >
>> >> > > nodelist {
>> >> > >        node {
>> >> > >                ring0_addr: 2001:db8:50::250
>> >> > >                ring1_addr: 2001:db8:60::250
>> >> > >                nodeid: 1
>> >> > >        }
>> >> > >        node {
>> >> > >                ring0_addr: 2001:db8:50::251
>> >> > >                ring1_addr: 2001:db8:60::251
>> >> > >                nodeid: 2
>> >> > >        }
>> >> > > }
>> >> > >  * rh62-coro2-2
>> >> > > totem {
>> >> > >        version: 2
>> >> > >        secauth: off
>> >> > >        rrp_mode:active
>> >> > >        nodeid : 2
>> >> > >        interface {
>> >> > >                ringnumber: 0
>> >> > >                bindnetaddr: 2001:db8:50::251
>> >> > >                ttl: 1
>> >> > >        }
>> >> > >        interface {
>> >> > >                ringnumber: 1
>> >> > >                bindnetaddr: 2001:db8:60::251
>> >> > >                ttl: 1
>> >> > >        }
>> >> > >        transport: udpu
>> >> > > }
>> >> > > (snip)
>> >> > >
>> >> > > quorum {
>> >> > >        provider: corosync_votequorum
>> >> > >        votes: 1
>> >> > > }
>> >> > >
>> >> > > nodelist {
>> >> > >        node {
>> >> > >                ring0_addr: 2001:db8:50::250
>> >> > >                ring1_addr: 2001:db8:60::250
>> >> > >                nodeid: 1
>> >> > >        }
>> >> > >        node {
>> >> > >                ring0_addr: 2001:db8:50::251
>> >> > >                ring1_addr: 2001:db8:60::251
>> >> > >                nodeid: 2
>> >> > >        }
>> >> > > }
>> >> > >
>> >> > > Best Regards,
>> >> > > Hideo Yamauchi.
>> >> > > ========
>> >> > >
>> >> > > Thanks for providing this. :)
>> >> > >
>> >> > > Digimer
>> >> > >
>> >> > > On 05/24/2012 08:05 PM, Digimer wrote:
>> >> > >> Would you mind sharing your configuration? I think having an example in
>> >> > >> the archives would be very useful.
>> >> > >>
>> >> > >> Thanks!
>> >> > >>
>> >> > >> On 05/24/2012 07:54 PM, renayama19661014@xxxxxxxxx wrote:
>> >> > >>> Hi All,
>> >> > >>>
>> >> > >>> Sorry...
>> >> > >>> The problem was settled.
>> >> > >>>
>> >> > >>> Best Regards,
>> >> > >>> Hideo Yamauchi.
>> >> > >>>
>> >> > >>> --- On Thu, 2012/5/24, renayama19661014@xxxxxxxxx <renayama19661014@xxxxxxxxx> wrote:
>> >> > >>>
>> >> > >>>> Hi All,
>> >> > >>>>
>> >> > >>>> We try a test of the IPv6 using corosync2.0.
>> >> > >>>> We am going to test it in IPv6 by UCAST communication.
>> >> > >>>>
>> >> > >>>>         transport: udpu
>> >> > >>>>
>> >> > >>>> I changed corosync.conf for IPv6, but corosync does not start.
>> >> > >>>>
>> >> > >>>> Please teach a sample of corosync.conf when I use the IPv6.
>> >> > >>>>
>> >> > >>>> Best Regards,
>> >> > >>>> Hideo Yamauchi.
>> >> > >>>> _______________________________________________
>> >> > >>>> discuss mailing list
>> >> > >>>> discuss@xxxxxxxxxxxx
>> >> > >>>> http://lists.corosync.org/mailman/listinfo/discuss
>> >> > >>>>
>> >> > >>> _______________________________________________
>> >> > >>> discuss mailing list
>> >> > >>> discuss@xxxxxxxxxxxx
>> >> > >>> http://lists.corosync.org/mailman/listinfo/discuss
>> >> > >>
>> >> > >>
>> >> > >
>> >> > >
>> >> > > --
>> >> > > Digimer
>> >> > > Papers and Projects: https://alteeve.com
>> >> > > _______________________________________________
>> >> > > discuss mailing list
>> >> > > discuss@xxxxxxxxxxxx
>> >> > > http://lists.corosync.org/mailman/listinfo/discuss
>> >> >
>> >> _______________________________________________
>> >> discuss mailing list
>> >> discuss@xxxxxxxxxxxx
>> >> http://lists.corosync.org/mailman/listinfo/discuss
>> >>
>>
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss



[Index of Archives]     [Linux Clusters]     [Corosync Project]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Linux Kernel]     [Linux SCSI]     [X.Org]

  Powered by Linux