Hello, folks!
Thats why we need some sort of dependency list for templates "this
template requires this kernel version". Any ideas to distribute
template packages with yum? It already has this capabilities.
On Thu, Jun 18, 2015 at 12:26 AM, Сергей Мамонов wrote:
> Yes, this explains everything.
Hello, folks!
I deployed IPv6 two years ago and everything goes smooth.
But there are some guidance from RIPE about IPv6 allocation. And I
want to mention they there. Every company receives /48 IPv6 allocation
(65 535 of /64 networks) and each end side device should receive /64
subnet.
Actually,
Hi,
I don't think it's possible to add a complete /64 to a container. Commercial
solutions I know allow to add single IPv6 from a /64 to a container, but not in
bulk. This would also eat many ressources, even if the kernel could handle the
large number of /64 IPs. Perhaps the list of IPs could
Hello!
Yep, I do not want whole /64 to container. I wan't to provide whole
subnet. And customer could decide what IP's he need.
On Thu, Jun 18, 2015 at 11:30 PM, Volker Janzen wrote:
> Hi,
>
> I don't think it's possible to add a complete /64 to a container. Commercial
> solutions I know allow
Heh, sorry. I should be more clear. I want to delegate whole /64
subnet and customer could decide how much IP's he need. He could use
only ::1 but he could use as much as possible IP addresses.
On Thu, Jun 18, 2015 at 11:50 PM, Pavel Odintsov
wrote:
> Hello!
>
> Yep, I do not want whole /64 to co
I don't understand what you are expecting OpenVZ to do? It's up to you
to manage your IP space as you see fit and assign to containers as
necessary. Given your context of "customers" this would likely be a
function of whatever management platform you are using.
On Thu, Jun 18, 2015 at 3:58 PM, Pav
Actually, I just asking community for ideas about IPv6 subneting.
On Friday, June 19, 2015, Todd Mueller wrote:
> I don't understand what you are expecting OpenVZ to do? It's up to you
> to manage your IP space as you see fit and assign to containers as
> necessary. Given your context of "custom
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 06/18/2015 11:13 PM, Todd Mueller wrote:
> [...]
I'm not entirely sure if you understand what he asks for.
When you do "vzctl set CTID --ipadd 2001:1234:1234:1234/64 --save", OpenVZ
creates a route only for the network address (2001:1234:123
On 18.06.2015 10:44, Pavel Odintsov wrote:
Thats why we need some sort of dependency list for templates "this
template requires this kernel version". Any ideas to distribute
template packages with yum? It already has this capabilities.
also it will be useful update hardware node with only one
Brilliant! Kevin, thank you.
On Friday, June 19, 2015, Kevin Holly [Fusl]
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> On 06/18/2015 11:13 PM, Todd Mueller wrote:
> > [...]
>
> I'm not entirely sure if you understand what he asks for.
>
> When you do "vzctl set CTID --ipa
Hi
There are no information about minimal kernel required version inside
templates. It's not expected to upgrade and reboot hwn to last kernel
everytime when templates being upgraded.
On Friday, June 19, 2015, Gena Makhomed wrote:
> On 18.06.2015 10:44, Pavel Odintsov wrote:
>
> Thats why we n
Thanks for the excellent explanation, I did misunderstand what is being asked.
> On Friday, June 19, 2015, Kevin Holly [Fusl]
> wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi,
>>
>> On 06/18/2015 11:13 PM, Todd Mueller wrote:
>> > [...]
>>
>> I'm not entirely sure if you u
12 matches
Mail list logo
