Re: [libvirt] [PATCH] lxc: support <interface type='ethernet'>
2016-05-17 17:39 GMT+03:00 Laine Stump <laine(a)laine.org>:
Rather than me spending time adding something to my patches that will
just
be superceded by another patch immediately, I would rather just do it the
way everyone wants to begin with.
What type of things are usually done in the upscript? (and is a "down
script" needed?)
(Speaking of that - I had asked in my discussion of re-doing the
peer-address patches if you could supply some example address/route configs
(for both host and guest side) of what you're doing with the peer address,
to see just how generalized those need to be. Any chance you can send me
that?)
I think script needed to manually ping some sort of agent on node for
example to add network info about newly created domain.
May be this is expensive (because agent can listen libvirt events...)
So may be i'm wrong. Please forget about script...
I think that I was mistaken..
For qemu i'm use this lines:
<ip address='HOST_IP' family='ipv4' peer='VM_IP'
prefix='32'/>
-- this address used bi bird routing daemon and via ospf propagated
to other nodes.
<ip address='VM_GW' family='ipv4' prefix='32'/> --
this address
used for gateway
<ip address='169.254.169.254' family='ipv4'
prefix='32'/> --
this address used by cloud-init (inside vm cloud-init talk to
169.254.169.254, so on host node i have some web server).
<ip family="ipv6" address="HOST_IP6" peer='VP_IP6'
prefix="64"/>
-- this is ipv6 address
<ip family="ipv6" address="VM_GW6" prefix="64"/>
-- this is ipv6 gateway
Now i don't used route elements because i'm use bird routing daemon and ospf.
--
Vasiliy Tolstov,
e-mail: v.tolstov(a)yoctocloud.net