Hi, all
We, NTT PF Lab., also agree to discuss about network service at the
Diablo DS.
However, we would really like to include network service in the Diablo
release because our customers strongly demand this feature. And we
think that it is quite important to merge new network service to
Hello
The second blueprint is our (Grid Dynamics) one. We created it after the
discussion with Sandy Walsh and Trey Morris (Rackspace), because their goal
to add support for Xenserver. We are very interesting in multi-nic for kvm.
So we going to add mulit-nic support for libvirt in Cactus
Hello Ewan,
Thanks for your answer. Now it's clear to me.
I assume that the tenant will not be able to configure any rich network
topologies until network-service is done.
Network model topic is big issue and multi-nic issue is also not a small issue
if we cover any network topologies. I'm
Try as we might there is still not a real consensus on high level coding
style, for example the Xen-related code is radically different in shape and
style from
the libvirt code as is the rackspace api from the ec2 api, and having
projects split off only worsens the problem as individual
I know the network service is going to get complicated very quickly but I
wanted to let everyone know for Cactus, our use case is pretty simple.
Thank you for your explanation. Very helpful.
users(admins?) somehow send a request to nova, and nova insert json strings to
xenstore,
then
5 matches
Mail list logo
