If you read the "configuration explained" documentation, you'll notice
that <attributes> tags are no longer used.
I think this is even mentioned in the section "what changed in 1.0"

A lot of other things changed too - I'd encourage you to read the pdf
and look at the updated examples.

On Mon, Nov 10, 2008 at 15:16, bart <[EMAIL PROTECTED]> wrote:
> Can anybody help me with this one?
>
> Cheers,
>
> Bart
>
> ----- "bart" <[EMAIL PROTECTED]> wrote:
>
>> > >> > Hi All,
>> > >> >
>> > >> > Just upgraded to Heartbeat 2.99.2-3.1 and Pacemaker 1.0.0-4.1
>> > >> running on CentOS 5.2.
>> > >> >
>> > >> > I haven't got any resources defined yet, so my cib only
>> contains
>> > the
>> > >> node entries.
>> > >>
>> > >> and the attribute with says how to validate it (validate-with)
>> > >
>> > > Yes.. pacemaker-1.0
>> > >
>> > >>
>> > >> > I am trying to import this resource:
>> > >>
>> > >> You'd have been better off doing a rolling upgrade which would
>> > have
>> > >> handled the syntax changes automatically
>> > >
>> > > That fails:
>> > >
>> > > The cluster will NOT be able to use this configuration.
>> > > Please update the configuration manually to conform to the
>> > pacemaker-1.0 syntax.
>> > > Errors found during check: config not valid
>> >
>> > Can you send it to me pls?
>> > There may be a bug in the upgrade script.
>>
>> Yes, it's attached. Hope it comes through..
>>
>> But again, I prefer to build the config all over again and find out
>> why the snipped doesn't work.
>>
>>
>> >
>> > >
>> > > But that's no problem. My previous config wasn't any good and I
>> > prefer building it from scratch
>> > >
>> > >>
>> > >> > <resources>
>> > >> >  <primitive class="ocf" id="privip" provider="heartbeat"
>> > >> type="IPaddr">
>> > >> >    <operations>
>> > >> >      <op id="op_1" interval="5s" name="monitor" timeout="5s"/>
>> > >> >    </operations>
>> > >> >    <instance_attributes id="ia_privip">
>> > >> >      <attributes>
>> > >> >        <nvpair id="nv_privip" name="ip" value="192.168.0.6"/>
>> > >> >      </attributes>
>> > >> >    </instance_attributes>
>> > >> >  </primitive>
>> > >> > </resources>
>> > >> >
>> > >> > which validates fine with my XML-editor.
>> > >>
>> > >> Is the editor doing schema validation against pacemaker.rng?
>> > >
>> > > Nope< I was validation against crm.dtd. Got any pointers on howto
>> > vailidate agains pacemaker.rng? I am currently using XML Copy Editor
>> > 1.1.0.6 to validate
>> >
>> > Not sure.  But google claims that it supports relax-ng schemas
>> (which
>> > is what the .rng file is) so it should just work
>>
>> Never knew google is able to validate xml's ;)
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to