I've written some CloudStack roles and example playbooks.
Figured others might find them helpful.
These are updated from when I originally built my <$500 two node CloudStack
(https://apachecon.dukecon.org/acna/2018/#/scheduledEvent/ed119c819c39bb5d4)
It's up on GitLab:
Hi Nux,
It is because NetworkInterface.getInterfaceAddresses() returns the ips in
reverse order.
For example, "ip addr show dev eth0" shows the following ips
inet X.X.X.X
inet secondary Y.Y.Y.Y
inet6 Z:Z:Z:Z:Z:Z
Then NetworkInterface.getInterfaceAddresses returns
Z:Z:Z:Z:Z:Z
Y.Y.Y.Y
X.X.X.X
- The models are 'native' if you like, definitely not workarounds.
- CloudStack is an orchestrator, it largely relies on the abilities of the
hypervisors that it orchestrates. We add a little secret sauce here and there,
but when it comes to basic hypervisor functions, we leave it up to the
Hey Paul,
Thank you for your fast reply!
> There are a few different models that you can use.
Do any of these models work "by default", or they are "workarounds"
(similar to Proxmox / LXC)? Aka is this a native/direct solution that can
be applied in the VM creation flow?
> Yes CloudStack does
Hi Razvan,
- There are a few different models that you can use. But in short - 'yes' you
can have a model where an IP is allocated to a VM and the VM keeps it.
- No, we spend a lot of time making sure that upgrades between all versions
work. Our versioning system requires that the API is
Hello,
We're thinking about switching from our current Xen+Proxmox setup into
something more "advanced", and we're really considering CloudStack as one
of our best/main candidates.
Right off the bat here are the first questions:
- in our current setup users can freely use each other's IP
Hi,
Updates to cloud-init have made the old way of using the bash script obsolete
in CentOS 7 and other distros.
To get it working all you need to do is replace "set-password" line, i.e.:
sed -i s/"set-passwords"/"[set-passwords, always]"/g /etc/cloud/cloud.cfg
Check my template here
I ran into a similar problem when I tried to allocate an additional IP on the
agent machine (for other purposes), the hypervisor would then show up in the UI
with this new IP and in "Alert" state.
I solved the problem by moving the IP out of br0 and on to the loopback
interface.
--
Sent from
