Hi Andrija,
No luck after trying that unfortunately. Does anyone know what process
creates the cloud0 interface? This is really frustrating since it's now
happening on 2 hosts that I am running and I don't really know where to
look.
On Tue, Jul 3, 2018 at 5:27 PM, Andrija Panic
wrote:
> I vague
Morning:
Have been reading through the documentation, have prepped quite a bit of
hardware (2 full racks in each DC, 10G/40G uplinks), and have decided to
take the plunge and setup Cloudstack on it. It's destined to be a
multi-data center install, but I think it would be best to start a DC a
Hi Christopher,
I think we discussed my KVM networking blog post in an earlier thread so I
assume you’ve had a read of that – I’m about to revisit this and re-issue the
blog post in the coming weeks so keep an eye on it.
Wrt immediate fix – have you tried simply manually creating the cloud0 bri
Hi Donald,
There is a lot of 'it depends' in the answers, so I'll try to stick with more
general advice (hopefully nothing too controversial in here)...
Step 1 - think about all of your use cases and figure out which networking
model fits best (basic vs advanced), this may also rule out some h
Hi Donald,
There’s obviously a lot of design decisions you have to make in this process,
but to answer your initial questions:
- Networking design is your biggest challenge – if your lowest spec server only
has two NICs then this is most likely your lowest common denominator unless you
put mor
Hi Mark,
I think there was a similar thread a few weeks back either on users@ or dev@.
In short there is no mechanism for simply onboarding existing VMs in CloudStack
yet.
So the official process is:
- Export existing VM to the respective hypervisor format (OVA, QCOW2, etc).
- Import as new temp
Hi Dan,
Sorry, I might have missed this conversation, it would be great if you could
tell me the name of that topic.
I am a little unsure how I would create the cloud0 interface. Would I bridge it
to the lo0 interface? Would you have an example? :)
Thank you!
Chris
Sent from my iPhone
> On
We do it this way (as Dag mentioned) - but in general I would not advise DB
hacks unless tested 100+ times - on next upgrade you might face issues
while updating DB schema etc, though I do have a lot of experience with DB
manipulation, (un)fortunately :)
On Wed, 4 Jul 2018 at 11:29, Dag Sonstebo
Hi Chris,
In short – you wouldn’t link it to any interface – you would just create the
bridge and also possibly assign a 169… IP address to it. Take a look at my 2016
blog post - https://www.shapeblue.com/networking-kvm-for-cloudstack/ - it’s
slightly out of date but as you can see back then I
Paul/Dag:
Thanks, this is actually what I was looking for was more of a general
overview and thoughts.
As for the 2 NIC boxes, yeah, not exactly what I'd vote to have, but
there aren't a ton of them, and I can either mark them for low usage,
grab one for a management server, etc.
Any recom
Hi Don,
Very few people (if any) run hardware management servers. The model depends on
which hypervisor you use – but a typical installation will run a small
hypervisor management cluster just to host the management and MySQL VMs as well
as any other infrastructure VMs required – so you probabl
Dag:
Yup ... wasn't talking about bare metal, but I should have clarified.
Thanks again :)
Don
HI Chris,
here is output (and you probably have it from your other hypervisors)
root@ix1-c4-2:~# ifconfig cloud0; brctl show cloud0
cloud0Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:169.254.0.1 Bcast:0.0.0.0 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500
Hi guys,
I discovered that cloud0 was still present in OVS by using the command
ovs-vsctl show. There was a lot of interfaces with "no such file or folder"
errors. Decided to trash the entire db and configure from new. So far so
good... After the manual creation everything seems to go a lot smooth
14 matches
Mail list logo
