Hi Martin,
The public interface is supposed to be DOWN on the backup. Don’t ask me why
this is designed like this, it doesn’t use VRRP for public. Most likely to save
ip addresses. It’s like this from the start.
If both are UP, I can imagine there is packet loss.
What is the state of the route
Hi!
I did the checks:
- If I shut down the backup via Cloudstack, the packet loss disappears.
- VRRP traffic can be seen both on the master (r-1904-VM) and the backup
(r-1905-VM).
- The internal gateway IP is only on the master. (eth0)
- The external IP is on both hosts (eth2):
root@r-1904-VM:/
Yes indeed.
Put a script in /var/lib/cloud/scripts/per-boot, it will be executed at every
boot (hopefully after networking is up).
In it you could inspect /var/lib/dhcp/blah for the full hostname or domain name
and amend /etc/hosts as you need.
HTH
Lucian
--
Sent from the Delta quadrant using B
But DHCP will not alter /etc/hosts as far as I know.
By per-boot hack you mean to write a script and run it via cloud-init at boot
time?
Mit freundlichen Grüßen / With kind regards,
Swen
-Ursprüngliche Nachricht-
Von: Nux! [mailto:n...@li.nux.ro]
Gesendet: Freitag, 11. März 2016 11:5
I am using cloud-init in the templates, but as I said I have not looked that
much into it. I just let DHCP do its job.
I would look at the per-boot scripts hack. :)
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "S. Brüseke - proIO Gm
To me it looks like CS needs to extend the user-data/meta-data with "hostname".
Are you using cloud-init in your templates? How to you edit /etc/hosts with
correct values?
Mit freundlichen Grüßen / With kind regards,
Swen
-Ursprüngliche Nachricht-
Von: Nux! [mailto:n...@li.nux.ro]
Ge
Swen,
I am not very familiar with it, but unless they have a proper module in place
to deal with DHCP as they do with the hosts file, you can always add a script
in /var/lib/cloud/scripts/per-boot to check the dhcp info in /var/lib/dhcp and
perform stuff based on it.
Not exactly kosher, but hey
yes, but cloud-init is rewriting the /etc/hosts file and it does not have
access to DHCP information or does it?
Mit freundlichen Grüßen / With kind regards,
Swen
-Ursprüngliche Nachricht-
Von: Nux! [mailto:n...@li.nux.ro]
Gesendet: Freitag, 11. März 2016 11:31
An: S. Brüseke - proIO
Ah I see.
Well, afaik the fqdn should be provided via DHCP, right?
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "S. Brüseke - proIO GmbH"
> To: "Nux!" , users@cloudstack.apache.org
> Sent: Friday, 11 March, 2016 10:29:41
> Subject:
Hi Lucian,
no, local-hostname will provide only the hostname without the domain name
(network name).
But this is how it is documented in cloud-init:
https://github.com/number5/cloud-init/blob/master/doc/examples/cloud-config.txt
line 433 - 439
But I need the whole fqdn.
Mit freundlichen Grüßen
Hi Swen,
>From that page:
"local-hostname. The hostname of the VM"
Isn't that what you need?
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "S. Brüseke - proIO GmbH"
> To: users@cloudstack.apache.org
> Sent: Friday, 11 March
Hi to all,
I am testing cloud-init in our CS installation.
I want to recreate /etc/hosts on first boot so I use "manage_etc_hosts: true".
The recreation works but it looks like the fqdn is not provided by CS.
As far as I understand cloud-init uses user-data/meta-data to get all needed
informati
12 matches
Mail list logo
